Production Plan#
As a BaSyx AAS Web UI user
I want to visualize Production Plan Submodels with their steps, actions, and statuses
so that I can monitor the execution progress of a production order at a glance.
Semantic ID#
This plugin is activated when a Submodel has the following semantic ID:
https://smartfactory.de/semantics/submodel/ProductionPlan#1/0
Feature Overview#
The Production Plan plugin provides a structured visualization of production plans defined by the SmartFactory Kaiserslautern (SFKL) Submodel template. It renders the hierarchical structure of a production order — broken down into steps and their associated actions — and displays the current execution status at every level.
The plugin gives operators and engineers a clear overview of which steps and actions have been completed, are in progress, or are still pending, as well as whether the overall plan has finished.
Production Plan Plugin showing steps, actions, and their statuses#
Key Features#
Plan status indicator: Shows the overall
IsFinishedstatus of the entire production planStep-by-step breakdown: Lists all production steps with their title, station, enterprise, and workcentre assignment
Step status: Displays the current status of each step (e.g.
open,executing,done)Action listing: Expands each step to show its actions with their individual title and status
Machine assignment: Shows the
MachineNamefor each action where available
Usage#
Navigate to a Submodel with the Production Plan semantic ID in the AAS Treeview
Open the Visualization tab
The plugin displays the overall plan completion status at the top
Each production step is shown with its title and current status
Expand a step to inspect its individual actions and their statuses
Submodel Structure#
The plugin expects the following structure, based on the SFKL Production Plan Submodel template:
Top-level Elements#
idShort |
Type |
Description |
|---|---|---|
|
|
Overall completion flag for the production plan |
|
|
One or more production steps |
Step Structure#
Each step collection contains:
idShort |
Type |
Description |
|---|---|---|
|
|
Human-readable name of the step |
|
|
Execution status of the step |
|
|
Target station for the step |
|
|
Enterprise responsible for the step |
|
|
Workcentre assigned to the step |
|
|
Collection of actions within the step |
|
|
Optional scheduling information |
|
|
Optional initial state definition |
|
|
Optional final state definition |
Scheduling Fields (optional)#
idShort |
Type |
Description |
|---|---|---|
|
|
Planned start date and time |
|
|
Planned end date and time |
|
|
Required setup time |
|
|
Cycle time for the step |
Action Structure#
Each action inside the Actions collection contains:
idShort |
Type |
Description |
|---|---|---|
|
|
Human-readable name of the action |
|
|
Execution status of the action |
|
|
Optional machine assigned to the action |
|
|
Optional input parameters |
|
|
Optional result data after execution |
|
|
Optional preconditions |
|
|
Optional effects |
|
|
Optional reference to the executing skill |
Status Values#
The Status property on both steps and actions uses string values. Typical values defined by the SFKL template are:
open– not yet startedexecuting– currently being executeddone– successfully completederror– execution failed