7 Predefined Job-Order-Input and Job-Order-Response Information
7.1 Overview
ISA95 job control (OPC 10031-4) defines mechanisms to add job order information using the 3:ISA95JobOrderDataType and mechanisms for getting the result or status of the job order using the 3:ISA95JobResponseDataType. Both DataTypes define arrays of properties of a job order: general, personnel, equipment, physical assets, and material. The 3:ISA95JobOrderDataType uses the general properties to describe the job order and the other properties to define the requirements, whereas the 3:ISA95JobResponseDataType uses the general properties to describe the output and the other properties to provide information on what has been used.
OPC 40001-3 (Machinery Job Mgmt) standardizes some of these parameters, which are application-specific from the perspective of OPC 10031-4. This specification gives recommendations for using these parameters and defines additional parameters.
7.2 Relevant Predefined Parameters
The PlannedQuantityOfRuns should not be used. Instead, use Material.Quantity and RunsPlanned.
The PlannedOrderQuantity should not be used. Instead, use Material.Quantity and RunsPlanned.
The predefined 3:JobOrderParameters of OPC 40001-3 in Table 27 should be used if the relevant information is available:
| ID | DataType of Value | Description | EngineeringUnits | Sub-parameters | In | Out |
| JobName | 0:LocalizedText[] | Human readable name of the job. Array shall always contain the same text, potentially in different languages. | - | - | X | X |
| ProducedQuantity | 0:Double | The produced quantity reflects the quantity that a work unit has produced in relation to a production order, including the count of good quantity, scrap quantity, and rework quantity. [Source: ISO 22400] Corresponding ISO 22400 definition: PQ (produced quantity)] | Product-specific | x | ||
| GoodQuantity | 0:Double | The good quantity shall be the produced quantity that meets quality requirements. (Note: Measuring work units use good quantity as the number of successfully executed measurement programs.) [Source ISO 22400] A quantity is considered as good as long as there is no contradicting evidence. Note that such evidence may arise in subsequent processing steps (on different machines), even if a quantity was considered as good. In this case, the data on the OPC UA Server are not changed retrospectively. Corresponding ISO 22400 definition: GQ (good quantity) | Product-specific | x |
Table 28 provides predefined key-value pairs for 3:JobOrderParameters and 3:JobResponseData, and indicates the data structure in which the key-value pairs are expected to be used. An “X” in “In” indicates that it may be used in 3:JobOrderParameters; an “X” in “Out” indicates that it may be used in 3:JobResponseData.
| ID | DataType of Value | Description | EngineeringUnits | Sub-parameters | In | Out |
| JobGroup | 0:String | This value can be used to group different jobs together; e.g., different jobs such as the verification job and operation job that should appear as one job on the HMI. | - | - | X | X |