DuPont Activity Modeling Tool

Overview - Screen Shots

This is a high level view of the Activity Modeling Tool Paradigm built within the Generic Modeling Environment (GME). Shown is a demonstration environment configured to utilize available features. Here we show connections between the major system integration components: the Process Monitoring and Control (PM&C) variable database (Net_Data), the Steady State Simulation Software (Aspen), a Signal Processing element (Sim_Data_Holder), and the Graphical User Interface. These interconnections represent data flowing throughout the synthesized run-time pipeline.

Above we have added more defintion to the Aspen Simulation module. Aspen Plus Steady State Simulation Software is used to help model chemical engineering plant functionality. We have brought in variables that represent quantities we want to observe and push into the system. We represent the variables being modified in blue; note the use of a "Converter" to extract information from a composite data stream (temp and press "Converter" icons). The red icons denote quantities whose value we wish to see after the simulation has transpired.

The Net_Data_Interface model above allows for configuring interaction with the PM&C Variable database. We use the icons with text "var" beneath them to configure the variables we want, the intervals of acquisition, and other characteristics. We then use the same Converter concept introduced in the Aspen model to combine the data from its native format into a composite stream to ease the modeling complexity at higher levels. Finally, we route this information to a port that is visible in the higher level view of the system shown above. Note: information can also be pushed into the PM&C dB using input ports and directing this information into "variable" objects.

The Signal Flow aspect of the Graphical User Interface allows for routing the data coming from the higher level data flow stream into the User Interface that will be synthesized from the models. Four streams are shown being sent into an icon bearing the name GUI_PlotEnvironment. This will make candidate all of these streams so that the user might choose to display this in their remote GUI/Operator's Panel. Additionally, text entry, text display, buttons, and other components are chosen to exist within the GUI. Their connections are dependent on the nature of their functionality. Entry fields naturally source connections; display fields sink connections. The inclusion of these components is completely user configurable, both with respect to existence and where they are placed (coordinate wise) on the client's display.

The SignalTypes aspect of the GUI is also present in other basic components in the Activity Modeling Tool paradigm. This allows for strongly typing the data that the high level connections represent. A structure is shown to offer set-grouping to the four input port icons depicted stacked on the left colum of the display. This means that a structure has been defined elsewhere (corresponding specifically to the type of data stream required by the Plotting Environment mentioned in the previous screenshot), and data coming into these connection points must also adhere to these structure contents. Structures need not type connection points, though. As you can see, Strings and integers are used to conditionalize two of the other groups of signals (1_t and 1_p, and SIM).

The result of GUI model configuration through the previously shown Aspects allows for sufficiently configuring the Applet that can be remotely located to the framework performing the propagation of information on the data flow network, acqusition/pushing to the PM&C dB, and interfacing with the Simulation Software. Additional components added to the communication pipeline can all communicate together, and the reconfigurable GUI allows for interactive human input and observation.