Consumptions and Data Collection#
The features in this integration are based on the PanaCIM v8831 specification.
Overview#
This feature will handle message 550 "TraceData", 551 "TraceData Component" or 553 "TraceData per Panel" enabling consumption data processing sent when a panel is released from a stage of a machine for a modular machine, or released from a non-modular machine.
Relevant Artifacts#
The table below describes the properties for this entity type:
| Name | Type | Is Mandatory | Data Type | Description |
|---|---|---|---|---|
| IoTMetadataDefinition | SmartTable | Yes | Metadata configuration for equipment integration | |
| AssembleMaterialFromConsumptionSummary | Service | Yes | Service to send process consumption data to MES |
How It Works#
When a message 55x is received from the PanaCIM equipment, the system takes the following actions:
- Check if feature is enabled.
- Process Consumption Summary by gathering from event's
materialslistidandqtyproperties and send that information to MES.
After MES operations are concluded a Response will be generated.
- If no error during the process error code 0 will be sent.
- If any error occurs error code 1 will be sent with respective error message.
Warning
With errorCode != 0 PanaCIM will lock the machine with an error message including the errorCode, and the user has to manually release the lock in PanaCIM.
Assumptions#
SmartTable IoTMetadataDefinition is configured, other than the general setup keys (check Setup for more information), with the following entries for each station:
| Resource | ResourceType | Area | Name | Value | Description |
|---|---|---|---|---|---|
| MES PanaCIM Station X Resource | usePanaCIMToConsumptions | 55XTraceData | ACtive trace data processing for consumptions. |
Prevent DataCollection and Consumptions from being made at the wrong step#
The event messages 602 with code B02 (representing a TrackOut) are sometimes received by Connect IoT before the consumption event for the same Resource, leading to consumptions being recorded in the wrong Step, or not recorded at all.
Two different message sequences were found from logs:
- 602 (TrackIn,B01), 602 (TrackOut,B02), 551 (Consumption)
- 602 (TrackIn,B01), 551 (Consumption), 602 (TrackOut,B02)
In order to support both sequences, the TrackOut processing of message 602 will be hold until the reception of Consumption message (551). To activate this feature, set key waitForTraceToDoTrackOut to true and set a timeout for the holding delay with key useWaitTimeout in case of Consumption not being sent for any reason. From real logs analysis of the sequence 602-602-551, the time interval between 602 and 551 is less than 2 secs, so a value of 4 seconds should be set to this key. If no value was specified for key useWaitTimeout, a timeout value of 5 seconds will be assumed.