In this Topic Hide
When information arrives from the outside world at a bus stop it is translated into the B2MML standard and sent onto the Bus as a message.
Each message contains information and specifies an action that needs to be carried out using that information.
The name of each message contains the action that will be carried out and the type of information that the message contains. There are five different actions that can be performed:Get, Process, Change, Cancel and Acknowledge.
And three different types of information:
● Operations capability: What is available?
● Operations schedule: What needs to be done?
● Operations performance: What has been done?
By combining these we get messages types such as ProcessOperationsSchedule, ChangeOperationsSchedule and ProcessOperationsPerformance.
These are all the messages that the bus stops can publish and subscribe to.
Workcenter Bus Stop |
MES Bus Stop |
Archive Bus Stop |
|||
Publish |
Subscribe |
Publish |
Subscribe |
Subscribe |
|
| ProcessOperationsPerformance |
|
|
|
|
|
| ProcessOperationsSchedule |
|
|
|
|
|
| GetOperationsSchedule |
|
|
|
||
| CancelOperationsSchdedule |
|
|
|
|
|
| ProcessOperationsCapability |
|
|
|
|
|
| ProcessWorkResponse |
|
|
|
|
|
| AcknowledgeOperationsSchedule |
|
|
|
|
|
| ChangeOperationsSchedule |
|
|
|
|
|
The names of the messages describe what they do. The following list gives extra information where required:
The Workcenter bus stop sends a ProcessOperationsPerformance message under the following conditions:
● Message sent with response state set to Ready when a work order has been dispatched.
● Message sent with response state set to Running when a work order is updated by the UpdateBatch action where the CloseOrder has been set to false.
● Message sent with response state set to Completed when a work order is updated by the UpdateBatch action where the CloseOrder has been set to true.
This message can also be used to transfer files from production line to MES.
Can be used to transfer files from MES to production line.
The GetOperationsSchedule message is sent from the Workcenter bus stop to the MES bus stop to request an operations schedule for a specified operation. The MES application will respond with a ShowOperationsSchedule message which is downloaded using the DownloadOrderOperation action. Normally an EnqueueOrderOperation is used.
The Workcenter bus stop processes a CancelOperationsSchedule message automatically without any actions assigned to it. The Workcenter bus stop only needs to subscribe to these messages.
CancelOperationsSchedule messages will only affect existing, non-running work orders. These messages are ignored for running work orders.
This message is published onto the Bus from a Workcenter bus stop by the PublishAsOperationsCapability action.
This message is published onto the Bus from a Workcenter bus stop by the PublishAsWorkResponse action. It contains information such as equipment IDs, equipment states and equipment modes.
The Workcenter bus stop sends an AcknowledgeOperationsSchedule message back to MES acknowledging that the work orders contained in a ProcessOperationsSchedule message have been enqueued. This happens if an EnqueueOrderOperation or DownloadOrderOperation action is assigned to a ProcessOperationsSchedule message.
The Workcenter bus stop processes a ChangeOperationsSchedule message automatically without any actions assigned to it. The Workcenter bus stop only needs to subscribe to these messages.
ChangeOperationsSchedule messages will only affect existing, non-running work orders. These messages are ignored for running work orders.