For bigger screens showing Activities list is the same as on PackOS
cockpit_type Machine_graph is replacing machine_graph_priority,
changes in API for downtimes (which makes it incompatible with 3.8 version)
Our solution combines 'Work spectrum' and 'Downtimes' views into a single focused view.
This approach creates a simple go-to place for anyone interested in downtimes.
Work spectrum view is almost identical, but now allowing anyone to click on the line, or a particular machine
This action opens a similar view to 'Downtimes', for the selected line/machine:
You can still use all filters on the left, and use a zoom-in and zoom-out functionality to select a particular period of downtimes.
Selecting a downtime, opens a sidebar with a summary of all details, including videos and comments.
Selecting any part of the downtime description, opens a dedicated flow.
Selecting a problem, assigning a reason and corrective action follows a similar step-by-step flow to the one in Cockpit.
Now the operator is explicitly asked to select a line or machine in the first step
You can see more in here → Downtime management
Our solution is a step-by-step wizard which contains four (or three depending if it's cleaning or order) stages.
It should eliminate issues with this view like:
User could easily lost all of their data by clicking outside new window
Not clear order of filling fields which is causing filling the same field couple times (e.g. choosing SKU and flow first and then choosing Line where this SKU is not configured)
Ambiguous which fields are mandatory and which optional
Possibility to notice that the ID already exists only after filling out all mandatory fields
In 3.9 there is now possibility to work also on Activities in status Released.
For bigger screens showing Activities list is the same as on PackOS
cockpit_type Machine_graph is replacing machine_graph_priority,
changes in API for downtimes (which makes it incompatible with 3.8 version)