Working with many activity types
PackOS can now distinguish different types of activities running on the line. Previously, it was always an order, and beginning with 3.3 the line can run:
Orders
Changeovers
Cleaning
Others, like 'Maintenance' will be introduced in the upcoming releases.
We’ve merged together the ‘Orders’ and ‘Schedule’ views, to create a single coherent view to manage line schedule and see historical activities
Dashboard will display all types of running activities:
When creating orders, you can provide ‘Changeover duration’ which will plan the corresponding changeover activity.
Info |
---|
Coming soon: This form will undergo a major redesign for improved user experience. |
When creating or importing orders you can also omit the ‘Line’ field, it can be filled later.
Newly created activities always go through the validation stage, which ensures that all necessary details has been provided. This is especially useful for orders imported through files or external systems - if created without some critical information (e.g. line number or SKU), orders will wait in ‘Draft’ until manually adjusted
You can see the changeover with connected order
Info |
---|
Coming soon: Changeover will display how much time is left, until the planned end |
Info |
---|
Coming soon: Changeover would be able to have a ‘type’ |
The configuration of line-level state adjustment has changed, please take a look here:
Line state vs Schedule
This allows for a different state, with different impact on OEE, after the changeover exceeds its planned duration
You can now create orders without line or end-date
Adding orders without end-date, which will be automatically filled based on expected performance (if available)
Orders without line will go to ‘Draft’, and will be promoted to ‘Released’ once the line is filled
Labour productivity
Expected effort can be configured (and imported) for each SKU as man-hours / volume.
You can find an updated import files with 3.3 mark here: Preparing a Material Master Import ✔️
e.g. if 8 man-hours is needed for 10 pallets, and order is planned for equivalent of 30 pallets, 24 man-hours will be determined as ‘expected effort’ for such order.
Man-hours can be reported for all types of activities using the ‘Report resources’ button next to the order:
Provided labour is displayed in running & completed orders:
Public API
A major improvement to Public API brings better ownership control handling, more activity types and products dictionary.
You can read about it here:
New documentation:
OEE detailed story → OEE Detailed Story
Mobile Cockpit Improvements
Major mobile app improvements include:
Ability to edit multiple downtimes at once
Graph of machines
Updated downtime edit form
Forms for labour & production reporting
Web Cockpit Improvements
New full-screen flow for changing downtimes
Configuration visibility improvements
Under the “Production” button in the Dashboard view:
You can now find the recent history of performances and active unit conversions.
Performance is pre-calculated to the line-level unit. This way you can easily compare that to the production volume e.g. to calculate OEE.
Handling indirect (recursive) packing structures
‘BaseUnit’ is gone, PackOS can now calculate indirect unit conversions automatically
If A → B and B → C is defined, PackOS will figure out A → C automatically, and block you from adding conflicting definitions
PackOS will also show inferred packing structures in the SKU user interface.
Order production settlement
Showing what counts has been rejected and why, before an order is completed
Improvement to completed order form
The following form:
Also include:
Summary of reported labour, with entries
Summary of manual production entries
Ability to adjust manually production / labour, for a completed order
Documentation:
Key bugfixes:
Working with different timezones will not be a problem anymore
In-progress improvements:
Line / machine production details
Like above, but unrelated to the order, directly explaining counts for each line and machine, which reasons why they has been rejected
Showing standard changeover times
When there is a changeover activity assigned to an order, the changover will show how much time remains until the planned duration is exceeded
Documentation
OEE aggregation: [Jan]
Labour: ETA: [Jan]
Working with new schedule (orders, changovers, cleaning): [Piotr]
Allow production on downtime: ETA: 8/04
Availability report: ETA: 8/04
Importing users and roles: ETA: 8/04
Others:
The production volume for running orders displayed in the dashboard is delayed ~60 s, with regards to line-level production. This may lead to inconsistent total production displayed to user.
Adding orders without end-date, which will be automatically filled based on expected performance.
Known bugs (ETA: 08/04):
In manual production/labour reporting form, after inserting manually date outside of the scope, the bar disappearsMobile app - adding new order form does not work properly
Unable to provide target changeover time
SKUs are not filtered
Production target “Planned orders” in dashboard does not work
If an order is activated, and it’s planned execution does not overlaps current day, it is not visible in the dashboard (started orders show up correctly)When updating the shift in ‘Work calendar’, the updated instance is added 1h after the provided date
Update of completed orders does not work.DescriptionPlanned quantity + unitPlanned start+endwill be editable, even after order has ended
After creating a new reason for the downtime, it creates and selects correctly, but an UI refresh is needed to see the change“Cancel” does not work when you open ‘Confirm resources’ or ‘Production reconciliation’ from the ‘Activities’ view