The ProductionJobStateMachineType shows the states a production job can be in and the possible transitions between those states.
The ProductionJobStateMachineType is formally defined in Table 39.
Table 39 – ProductionJobStateMachineType Definition
Attribute |
Value |
||||
BrowseName |
ProductionJobStateMachineType |
||||
IsAbstract |
False |
||||
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
Subtype of the ProductionStateMachineType defined in 8.4.8 i.e. inheriting the InstanceDeclarations of that Node. |
|||||
0:GeneratesEvent |
ObjectType |
InterruptionConditionType |
|
|
|
0:HasComponent |
Object |
AbortedToInitializing |
|
0:TransitionType |
No ModellingRule |
0:HasComponent |
Object |
EndedToInitializing |
|
0:TransitionType |
No ModellingRule |
0:HasComponent |
Object |
InitializingToAborted |
|
0:TransitionType |
No ModellingRule |
0:HasComponent |
Object |
InitializingToRunning |
|
0:TransitionType |
No ModellingRule |
0:HasComponent |
Object |
InterruptedToAborted |
|
0:TransitionType |
No ModellingRule |
0:HasComponent |
Object |
InterruptedToRunning |
|
0:TransitionType |
No ModellingRule |
0:HasComponent |
Object |
RunningToAborted |
|
0:TransitionType |
No ModellingRule |
0:HasComponent |
Object |
RunningToEnded |
|
0:TransitionType |
No ModellingRule |
0:HasComponent |
Object |
RunningToInterrupted |
|
0:TransitionType |
No ModellingRule |
0:HasComponent |
Object |
RunningToRunning |
|
0:TransitionType |
No ModellingRule |
When a new interruption occurs in the production job, an event of InterruptionConditionType can be sent to clarify the reason for the interruption. This is an option in addition to the Interrupted state of the ProductionStateMachineType. It is possible that other interruptions occur while the state machine is in the Interrupted state, e.g. the first interruption being due to a missing part and while the part is still missing, a utility change becomes necessary. In such a case, Events of InterruptionConditionType may be sent for each subsequent interruption. The transition InterruptedToRunning may only be used if no interruption is active. If the interrupted job is aborted (via InterruptedToAborted), the interruption may persist. If a job is then re-initialized via AbortedToInitializing, there are multiple possible cases. In one case the interruption is solved before the job enters the Initializing state. In this case, the same job can transition to Initializing. Another option, when the ProductionPlan is used statically, the job node can be overwritten with the new job being in the Initializing state. Depending on the production context, the interruption of the old job might persist. When the ProductionPlan is used dynamically, a new job node can be created. Whether the interruption can persist is again depending on the production context.
The ProductionJobStateMachineType allows to send Events of ProductionJobTransitionEventType with every transition, as indicated in Table 40. This makes it possible to send all relevant information of the ProductionJobType the state machine instance belongs to with the TransitionEvent.
The state Aborted indicates that the job has been irreversibly stopped before finishing. If the job enters this state, the state machines of any ProductionProgramType and ProductionPartType instances associated with it shall not remain in the state Running.
Ended is reached when the job has finished all its runs, so the value of RunsCompleted is the same as the one for RunsPlanned.
Initializing is the state in which the job is being prepared. That implies the job being scheduled for production in the near future. In this state, actions like e.g. loading and configuring programs, inserting tools and utilities and mounting workpieces may be conducted.
InitializingToRunning is triggered when the job starts. This can only be triggered if all preconditions to start the job are met. A job is usually started by starting a related control routine. This does not result in changes to the components and properties (other than State) of the ProductionJobType instance being started.
RunningToEnded is triggered when the last run of a job finishes. The value of RunsCompleted in the affected ProductionJobType instance is increased by one (and equal to the value of RunsPlanned) due to this transition. In the ProductionJobTransitionEventType, this increased value is sent. This transition also implies that all parts and programs related to the job will no longer change, so e.g. the quality information for each part is finally set.
EndedToInitializing is triggered when initialization of a new job starts. This transition is only used if the nodes in the ProductionPlan are never added or deleted, but remain static in the address space. In this case, all values of the ProductionJobType instance the state machine belongs to are changed to represent a different job. The values of this new job are sent with the ProductionJobTransitionEventType.
RunningToRunning is triggered when a new run of the job starts. The RunsCompleted of the affected ProductionJobType instance increases by one. The ProductionJobTransitionEventType shall send this increased value.
RunningToInterrupted is triggered when the job is interrupted. The point in time the interruption starts shall be when the machine tool gets the command to interrupt the job process. To indicate the reason for the interruption, an InterruptionConditionEventType with the appropriate ConditionClass may be sent. The components and properties (other than State) of the affected ProductionJobType instance stay unchanged.
InterruptedToRunning is triggered when an interruption ends and production continues running. This transition requires that no interruption is active, regardless of what interruption initially led to the RunningToInterrupted transition. The components and properties (other than State) of the affected ProductionJobType instance stay unchanged.
InterruptedToAborted is triggered when the job is aborted while in the Interrupted state. This transition does not require the reason for the interruption to be solved. The components and properties (other than State) of the affected ProductionJobType instance stay unchanged.
AbortedToInitializing is triggered if production is being re-initialized after an abort. This transition is only used if the nodes in the ProductionPlan are never added or deleted, but remain static in the address space. In this case, all values of the ProductionJobType instance the state machine belongs to are changed to represent a different job. The values of this new job are sent with the ProductionJobTransitionEventType.
Table 40 – ProductionJobStateMachineType Additional References
Source Path |
ReferenceType |
Is Forward |
Target Path |
||
AbortedToInitializing |
0:FromState |
True |
|
||
|
0:ToState |
True |
|
||
|
0:HasEffect |
True |
ProductionJobTransitionEventType |
||
EndedToInitializing |
0:FromState |
True |
|
||
|
0:ToState |
True |
|
||
|
0:HasEffect |
True |
ProductionJobTransitionEventType |
||
InitializingToAborted |
0:FromState |
True |
|
||
|
0:ToState |
True |
|
||
|
0:HasEffect |
True |
ProductionJobTransitionEventType |
||
InitializingToRunning |
0:FromState |
True |
|
||
|
0:ToState |
True |
|
||
|
0:HasEffect |
True |
ProductionJobTransitionEventType |
||
InterruptedToAborted |
0:FromState |
True |
|
||
|
0:ToState |
True |
|
||
|
0:HasEffect |
True |
ProductionJobTransitionEventType |
||
InterruptedToRunning |
0:FromState |
True |
|
||
|
0:ToState |
True |
|
||
|
0:HasEffect |
True |
ProductionJobTransitionEventType |
||
RunningToAborted |
0:FromState |
True |
|
||
|
0:ToState |
True |
|
||
|
0:HasEffect |
True |
ProductionJobTransitionEventType |
||
RunningToEnded |
0:FromState |
True |
|
||
|
0:ToState |
True |
|
||
|
0:HasEffect |
True |
ProductionJobTransitionEventType |
||
RunningToInterrupted |
0:FromState |
True |
|
||
|
0:ToState |
True |
|
||
|
0:HasEffect |
True |
ProductionJobTransitionEventType |
||
RunningToRunning |
0:FromState |
True |
|
||
|
0:ToState |
True |
|
||
|
0:HasEffect |
True |
ProductionJobTransitionEventType |