Output and consumption postings can be seen as information about the progress of your production execution
When you post output or consumption on your production order line, you basically tell your system that you started or finished an operation or that you have achieved a certain percentage of completion.
Fundamentals on output/consumption postings:
- Output/consumption postings can happen very often, sometimes, even automatically
- They reflect a constant data updating process
- No impact on an existing simulation:
- The simulation doesn't get outdated
- The simulation doesn't get invalid
- The progress information you see in the visual schedule is about the moment in time when you created your simulation.
- After posting output/consumption, you have to create a new simulation
The impact on the production order status
- You can only post output and consumption to a released production order
- Any output/consumption posting on a released production order results in showing a progress bar in the VAPS
Visualization of progress information in the VAPS
For production order routing lines of released production orders, a slim progress bar is displayed below the actual bar being based on the posted quantity consumption or the production time passed. The color of the progress bar appears as follows:
- finished: black and grayed out
- still in progress and output/consumption <= originally planned quantity: grey
- still in progress and output/consumption > originally planned quantity: red
Please note that
- You can only post output and consumption to a released production order
- Operations that are already in progress cannot be moved anymore
- The percentage of completion is shown in relation to the net working time.
Special case: Posting on an operation that is still on the standby resource
This is a highly exceptional case that should not occur under normal circumstances, but it's important to be aware of the possibility.
Important to know
- Posting output or consumption for an operation that is still assigned to a standby resource will automatically move the operation to the machine center specified in the routing. This is because posting signifies that the operation has started, and once started, it can no longer remain on a standby resource.
- If the specified machine center is already occupied by another operation, this may lead to an overload, which must be resolved manually by the planner.
Comments
0 comments
Please sign in to leave a comment.