View Issue Details

IDProjectCategoryView StatusLast Update
001033910031: ISA 95 Job ControlDocumentation Erratapublic2025-05-26 14:53
ReporterPatrick Berger Assigned ToWolfgang Mahnke  
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Summary0010339: Missing/wrong definition for GeneratesEvent ()
Description

According the State-Machine definition: "The StateMachineType shall have GeneratesEvent References to the targets of a HasEffect Reference for each of its Transitions."

ISA95 defines for all state transitions a HasEffect ISA95JobOrderStatusEventType. The ISA95JobResponseProviderObjectType has a GeneratesEvent on ISA95JobOrderStatusEventType.
However, ISA95JobOrderReceiverObjectType is a child of FiniteStateMachineType and not ISA95JobResponseProviderObjectType. Only Machinery combines ISA95JobOrderReceiverObjectType and ISA95JobResponseProviderObjectType with JobManagementType. In principle, ISA95JobOrderReceiverObjectType and ISA95JobResponseProviderObjectType are two different/independent object types.

As we understand it, GeneratesEvent is defined incorrectly and should go to ISA95JobOrderReceiverObjectType and not to ISA95JobResponseProviderObjectType.

The conformance unit "ISA-95 Job Control Job Response Provider Job Order Status Events" would still be valid because the events are extended to a β€œnew” source. Or you can define this so that ISA95JobOrderReceiverObjectType is the event source (state machine events are not mandatory).

Additional Information

https://reference.opcfoundation.org/Core/Part16/v105/docs/4.4.6
https://reference.opcfoundation.org/ISA95JOBCONTROL/v200/docs/6.2.1

TagsNo tags attached.

Activities

Wolfgang Mahnke

2025-05-26 14:53

manager   ~0022777

Formally, we need to add a GeneratesEvent to the ISA95JobOrderReceiverObjectType, although we are not really using the StateMachine as intended. Or we remove the HasEffect References from the Transitions.
Logically, the Event belongs more to the ISA95JobResponseProviderObjectType, as the Event contains the results provided via the response provider. The GeneratesEvent should stay on that type. Conformance Units do not have to change. The intention is mainly to generate it from there.

We need to make sure that the event does not get generated two times, once from the receiver object and once from the response provider object, if the server supports both. Probably add this to the description of the event type, also stating that the SourceNode should go to a higher level Object if available (like for example done in the Machinery spec).

Issue History

Date Modified Username Field Change
2025-05-26 12:39 Patrick Berger New Issue
2025-05-26 14:41 Wolfgang Mahnke Assigned To => Wolfgang Mahnke
2025-05-26 14:41 Wolfgang Mahnke Status new => assigned
2025-05-26 14:53 Wolfgang Mahnke Note Added: 0022777