This section shows a picture of the way the dynamical part of the IMA PROTO610 is “programmed”.
Original document by Fredrik D. Alink (1-10-2004)
Document revised on 1-9-2005
Document revised on 1-9-2005
| Work Order Process definitions |
Work Orders and their Processes are defined through type definitions. These definitions are maintained in and provided through the Process Control Business Server.
Within PROTO610, the following Workorder Types are defined:
- Default Actions
- These are defined for any Workorder Type, so they can be added to the next Types;
- Start
- The Workorder Type “Start” is used to schedule one Task after the other, without this, no choice could be made on a next Task;
- Logon
- The Workorder Type “Logon” is used to open Interfaces for additional Resources, that is, to Log-on an Interface to the Model;
- Scheduler
- The Workorder Type “Scheduler” makes it possible for a Resource to schedule his own Tasks;
- WFM
- The Workorder Type “WFM” makes it possible for a Co-ordinator to schedule any Resource's Tasks;
- Mailer
- The Workorder Type “Mailer” is used to handle mailing between Resources, mail messages can be created, sent using an Address List, viewed and answered;
- UserTypes
- The Workorder Type “UserTypes” is used to consult and maintain UserType information in the User Control Business Aspect Server;
- Resources
- The Workorder Type “Resources” is used to consult and maintain Resource information in the Resource Control Business Aspect Server;
- Archive
- The Workorder Type “Archive” is used to look into the Workorder Archive, all completed Workorders are kept in this Workorder Archive;
- Aspects
- The Workorder Type “Aspects” is used to consult and maintain Business Aspect structure information in the GME Control Business Aspect Server.
- Testing
- The Workorder Type “Testing” is there for test purposes, that is, it is used when developing new Tasks for PROTO610 and later;
On the following pages, per Workorder Type / Process Type, all available Action Types are detailed. For readability reasons, all Types are named by the elements as will be provided to the Workorders, so without the “Type” part.
The following legenda will be used in the schemes:
![[legenda]](doc70000.gif)
- Action:
- An Action is triggered by an Event conforming the schemes in Events and Actions, it results into zero (in this case the “nil” activity is “activated”) or more Activities to be performed from top to bottom;
- default Activity for Support:
- A black Activity is always performed (the local Object #condition has no value) and activates a Support from the Engine, it can be preceded by Presteps and followed by Poststeps;
- Activity if #condition = true:
- A green Activity is only performed if the local Object #condition has a value of “true”;
- Activity if #condition = false:
- A red Activity is only performed if the local Object #condition has a value of “false”;
- prestep for Service:
- Presteps for an Activity, if any, are performed from top to bottom and activate a Service from the running Process;
- poststep for Service:
- Poststeps for an Activity, if any, are performed from top to bottom and activate a Service from the running Process;
| to next page > |
