In Table 1, 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 1 – Predefined JobOrderParameters and JobResponseData

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

OrderNumbers

0:String[]

The OrderNumbers are used to reference company internal ERP orders the job order belongs to.

Shall be provided in JobOrderParameters if any planned produced material uses OrderNumber as Identification and shall contain all those OrderNumbers.

Shall be provided in JobResponseData if any produced material, any AsBuiltBOM or OutputPerformanceInfo uses OrderNumber as Identification and shall contain all those OrderNumbers.

X

X

Customers

0:String[]

This property is used to show the name of the customers of the Job order.

-

-

X

X

CustomerOrderNumbers

0:String[]

The CustomerOrderNumbers is used to reference to the customer orders this job order belongs to.

-

-

X

X

JobExecutionMode

JobExecutionMode

Describes the execution mode of the machine for that job order.

-

-

X

X

ReasonForStateChange

0:LocalizedText

Reason why a state change occurred. May be filled by the Comment parameter of the methods used to change the state.

-

-

X

X

RunsPlanned

0:UInt32

RunsPlanned indicates the number of runs that should be performed by the targeted machinery item when this job order is executed. A run can consist of several steps.

If the planned number of job order runs is not known to the machinery item it is set to 0. The number of planned job order runs not being known occurs in continuous production, that is if the machinery item is started with the respective job order and job order runs are repeated endlessly. The production process only ends when the machinery item is stopped by an external measure (operator or system).

-

-

X

-

PlannedProductionTime

0:Duration

The planned pure time period of the production (or value creation) without the consideration of setup and delay time periods.

Equals planned order quantity (POQ) times planned run time per item (PRI) in correspondence to ISO22400.

-

-

X

-

PlannedSetupTime

0:Duration

The planned time period before the production process can be started. (e.g. warm-up)

-

-

X

-

PlannedTimePerRun

0:Duration

The planned time period that is needed for the execution of one run of this job order.

-

-

X

-

PlannedQuantityPerRun

0:Double

The planned quantity produced by one run. This shall be higher than 0.

Note: If the quantity is measured in pieces, the EngineeringUnits has to be “piece” (H87).

Product-specific

-

X

-

PlannedOrderQuantity

0:Double

The planned order quantity (POQ) shall be the planned quantity of products for a production order (lot size, production order quantity). [Source: ISO 22400]

Product-specific

Overproduction

X

-

Overproduction

0:Boolean

Indicates if the machine continues the production even if the nominal output has been reached.

-

-

X

-

PlannedDuration

0:Duration

Planned time period needed for the execution of the job order. Consists of setup time, production time and planned delays. This information is provided by the MES/MOM.

-

-

X

-

JobAnnotation

0:LocalizedText[]

Description text provided to an operator to indicate the equipment or modification of the machine needed for the job order. Note: This is not interpretable by machines.

-

-

X

-

RunsCompleted

0:UInt32

RunsCompleted is a counter that increases after each completed run of this job order.

-

-

-

X

RunsStarted

0:UInt32

RunsStarted is a counter that indicates how many of the RunsPlanned have been started already. When the processing of all runs was successful, the number of RunsStarted should equal RunsCompleted and RunsPlanned. It is not corresponding to the quality of produced items.

-

-

-

X

ActualQuantityCurrentRun

0:Double

The actual total quantity that was produced in the current run. It can be incremented either sequentially or in steps.

Note: If the quantity is measured in pieces, the EngineeringUnits has to be “piece” (H87).

Product-specific

-

-

X

ActualUnitBusyTime

0:Duration

The elapsed time since the start of production of the job order.

This value is intended to be updated in a low frequency.

Corresponding ISO22400 definition: AUBT (actual unit busy time)

-

-

-

X

ActualUnitSetupTime

0:Duration

The elapsed time for the setup of the job order.

This value is intended to be updated in a low frequency.

Corresponding ISO22400 definition: AUST (actual unit setup time)

-

-

-

X

ActualUnitDelayTime

0:Duration

The elapsed time due to delays.

This value is intended to be updated in a low frequency.

Corresponding ISO22400 definition: ADET (actual unit delay time)

-

-

-

X

ActualProductionTime

0:Duration

The actual production time shall be the actual time during which the work unit produces the job. It includes only the value adding functions.

Corresponding ISO22400 definition: APT (actual production time)

Note: The actual production time includes time losses depending on speed and quality issues.

-

-

-

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 and scrap quantity and rework quantity.

[Source: ISO 22400]

Corresponding ISO22400 definition: PQ (produced quantity)]

Product-specific

-

-

X

EstimatedRemainingTime

0:Duration

Planned remaining time that is needed to complete this job order. This is an approx. value that can’t always be determined.

-

-

-

X

JobResult

JobResult

High-level result of the execution of the job order.

-

-

-

X

GoodQuantity

0:Double

The good quantity shall be the produced quantity that meets quality requirements. Note: Measuring work units use good quantity as number of successful 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 ISO22400 definition: GQ (good quantity)

Product-specific

-

-

X

AsBuiltBOM

BOMInformationDataType[]

The bill of material of the produced output of the job order.

-

-

-

X

OutputPerformanceInfo

OutputPerformanceInfoDataType[]

Performance information of the executed job order.

-

-

-

X

Note: PRI (planned run time per item) as defined in ISO22400 equals PlannedTimePerRun divided by PlannedQuantityPerRun.