Mapping for PackML MachineryItemState & MachineryOperationMode|OPC UA Companion Standards|Forum|OPC Foundation

Hi

Currently I’m struggling with creating a mapping to enable customers to calculate KPIs with different companion specifications (because they have different machines form different vendors at the shop floor)…

• Is it possible to mapp PackML-States to MachineryItemStates or should this solved with a combination of MachineryItemStates & MachineryOperationMode?
• MachineryOperationMode mode is extremley wide and unclear (should this be the intention of a standard?) – possible interpretatons are
  • production mode like automatic / manual (e.g. single step) / maintenance (e.g. limitted speed, re-calibrate axis positions…)
  • defined from a operation mode switch with impact to safety (e.g. SLS)

My fist idea was something like this

• PackML-Wait-States
  (MachineryItemState = OutOfService) & (MachineryOperationMode = None) -> ABORTED
  (MachineryItemState = OutOfService) & (MachineryOperationMode = Maintenance) -> HELD
  (MachineryItemState = NotExecuting) & (MachineryOperationMode = None) -> STOPPED, IDLE, COMPLETE
  (MachineryItemState = NotExecuting) & (MachineryOperationMode = Processing) -> SUSPENDED
• PackML-Acting-States
  (MachineryItemState = Executing) & (MachineryOperationMode = Setup) -> RESETING, STARTING, COMPLETING, UNSUSPENDING, UNHOLDING, CLEARING, STOPPING
  (MachineryItemState = Executing) & (MachineryOperationMode = None) -> ABORTING
  (MachineryItemState = Executing) & (MachineryOperationMode = Processing) -> EXECUTE, HOLDING, SUSPENDING

But the guidline for OEE with PackML defines something like this:

Time machine is producing product (EXECUTE + HOLDING + SUSPENDING)

HOLDING and SUPENDING because bringing the machine to a controlled stop with not creating scrap (so there could be partial produced goods inside the machine).

Time machine is in faliure (HELD + STOPPED + ABORDET)

This is strange:

• STOPPED isn’t defined as error-state
• HOLDING and ABORTING are acting states from a Hold or Abort command – in general there will be an Error to trigger this transition. so why are they not used for “time machine is in failure”? (this would have an impact to my mapping).

this would change the mapping to something like this

(MachineryItemState = Executing) & (MachineryOperationMode = Maintenance) -> HOLDING
(MachineryItemState = Executing) & (MachineryOperationMode = Processing) -> EXECUTE, SUSPENDING

what do you think? what would be the more appropriate interpretation? or am I completely wrong?

Best regards

Patrick