ArchitectureImPRO consists of Server, Client, and Editor. They are distributed in order to share the procedure resources freely, keep consistency, and edit procedures with ease. The Editor, however, is not implemented yet. Because CBP showes not only procedures but also related information, CBP are usually integrated with process computers. ImPRO server manages all procedure files that are not accessible from ImPRO client directly. This central management enhances consistency of procedures. For example, the crewmembers cannot have different version of procedure files. This design basis applies to plant parameters and device symbols too. Whenever ImPRO clients need these resources, ImPRO server delivers them to the consumers on demand. Each ImPRO client, however has its own simple configuration file telling where ImPRO server resides and what title the operator has. The communication between server and client is based on TCP/IP and UDP. Its TCP/IP port is 1999, whereas UDP port 234.233.232.231 for multicasting. Application protocol is specially designed to deliver resources quickly and to keep the consistency between clients and server.
There is no limitation in the number of users. But ImPRO categorizes an user into either a crewmember or a guest as he/she logins. Each crewmember is entitled by his role (i.e. RO TO SRO). The role can be configurable according to specific process. It is forbidden that the same user runs two ImPRO clients at the same time. Besides, only one ImPRO server can runs in a machine.
Procedure files are written according to PML(Procedure Markup Language), which is an instance of general XML1.0 specification. Plant Database is also built in XML1.0. The data can be retrieved with XQL.
One advantage PML is inherent verification of procedures due to formalism. This verificaction will be enhanced with development of ImPRO editor. At the present procedure files is viewed and edited by simple text editor. A device symbol is graghic presentation for a node in the plant database. The symbols are stored as java byte code and distributed. ImPRO editor will create device symbos with drawing tools. At the present they are written with a text editor and compiled.
Finally the process database of ImPRO server is dynamically updated by external programs. API(Application Program Interface) and examples programs for the integration are provided.
|
||