OPC 10031-4 defines mechanisms to add job order information using the 2:ISA95JobOrderDataType and mechanisms getting the result or current status of the job order using the 2:ISA95JobResponseDataType. Both DataTypes define arrays of properties of a job order: general, personal, equipment, physical assets, and material. The 2:ISA95JobOrderDataType uses the general properties to describe the job order and the other properties to define the requirements, whereas the 2:ISA95JobResponseDataType uses the general properties to describe the output and the other properties to provide the information what has been used.

OPC UA Machinery Job Management (OPC 40001-3) standardizes some of those parameters, which are application-specific from the view of OPC 10031-4.

The guidelines and extensions specified in this section are designed to complement the foundational models, providing a structured framework for implementation. The Optional element (e.g. fields or parameters) of the OPC 10031-4 or OPC 40001-3 may be used as defined.

The WorkMasterID field of the ISA95JobOrderDataType contains the information about the WorkMaster (e.g. the recipe). The field ID is an identification of the Work Master. This should be used to identify a work master cross different opc ua server and must be unique its scope (e.g. company unique).

This specification use the 0:FileSystem folder to manage(e.g. upload /download files) the work master files on the server. To connect the WorkMasterID with the file additional predefined key-value pairs for 2:ISA95WorkMasterDataType.Parameter are defined in Table 18.

Table 18 – Predefined WorkMaster Parameters

ID	DataType of Value	Description	EngineeringUnits	Subparameters
LocalPath	String	Contains the file path on the OPC UA server. This must be identical with the relative path of the BrowsePath.	-	-
FileNodeId	0:NodeID	Contains the NodeId of the object of the file.	-	-
FileFormat	FileFormatType	Defines the file format of the work master file. This is used to ensure compatibility between the work master and the machine.

Note: Example of the LocalPath could be "/Directory1/FileA" with the corresponding BrowsePath as "{ StartingNode :”ns=1;s=FileSystem”; RelativePath: “Directory1/FileA"}”. It is recommended that the local file system also has a directory “../Directory1/FileA".

Note: A restart may change the nodeid of the file. So it is recommended to check the FildeNodeID before using the file in a WorkMaster. If possible use the LocalPath instead.

Note: The LocalPath must be used in a WorkMaster and the other Parameters are optional.

The following 2:ISA95JobOrderDataType fields shall be used:

• MaterialRequirements
• Priority
• StartTime
• EndTime

The following 2:ISA95JobOrderDataType fields may be used if the relevant information is available:

• JobName

This specification standardizes some of those parameters, which are application-specific from the view of OPC 10031-4.

In Table 19, predefined key-value pairs for 2:JobOrderParameters and 2:JobResponseData is provided. The table indicates, in which data structure the key-value pair is expected to be used. An “X” in “In” indicates it may be used in 2:JobOrderParameters an “X” in “Out” indicates it may be used in 2:JobResponseData.

Table 19 – Predefined JobOrderParameters and JobResponseData

ID	DataType of Value	Description	EngineeringUnits	Subparameters	In	Out
ReasonForSubState	ReasonDescriptionType	Provides an explanation for the current status of the job. This information may be used, for instance, to detail why the server is unable to perform a particular job.	-	-	x	x

The following 2:ISA95JobOrderDataType fields shall be used:

• ActualMaterial
• StartTime
• EndTime

The following 2:ISA95JobOrderDataType fields may be used if the relevant information is available:

• JobName