This table contains the manufacturing orders of your supply chain, either proposed by frePPLe or confirmed.
This table is populated with new proposed manufacturing orders when frePPLe generates a plan. It is also possible to load manufacturing orders that are already approved or confirmed in your ERP system.
Unique identifier for the manufacturing order.
This field will be empty for newly proposed manufacturing orders, but for approved or confirmed manufacturing orders that already exist in the ERP system this field should be populated with the identifier the ERP generated.
|operation||operation||The operation to perform.|
|start date||DateTime||The date when the operation is starting.|
|end date||DateTime||The date when the operation is ending.|
|quantity||number||The manufactured quantity.|
This field should have one of the following keywords :
proposed : The manufacturing order is proposed by frePPLe to meet the plan (optimization output).
approved : The manufacturing order is present in the ERP system but can still be rescheduled by frePPLe (optimization input).
confirmed : The manufacturing order is confirmed, it has been populated in your ERP system (optimization input).
closed : The manufacturing order has been completed.
|demands||demand||The demand(s) (and quantity) pegged to the manufacturing order. This is a generated field.|
|owner||number||In the case of a suboperation, the identifier of the operation calling this suboperation.|
The Inventory Status is a calculated field that highlights the urgency of the manufacturing order.
The cells have a background color that can be green, orange or red. Sorting
the manufacturing orders using the Inventory Status column (red ones first) allows the planner to
immediately focus on the manufacturing orders that should be treated first.
Read-only boolean flag indicating whether the operationplan is violating any material, lead time or capacity constraints.
This is very handy in interpreting unconstrained plans.
The criticality is a read-only field, calculated by the planning engine.
It represents an indication of the slack time in the usage of the manufacturing order.
A criticality of 0 indicates that the manufacturing order is on the critical path of one or more demands.
Higher criticality values indicate a delay of the manufacturing order will not immediately impact the shipment of any demand.
A criticality of 999 indicates a manufacturing order that isn’t used at all to meet any demand.
Note that the criticality is independent of whether the customer demand will be shipped on time or not.
The delay is a read-only field, calculated by the planning engine.
It compares the end data of the manufacturing order with the latest possible end date to ship all demands it feeds on time.