LogiX 3.10

Owned by Marcin Zelek (Unlicensed)
Last updated: Dec 12, 2022
5 min read

New designs with working on Downtimes

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 → https://ilabo.atlassian.net/wiki/spaces/LW/pages/2097381390

 

New design with order creation

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

 

Activities Edit mode improvement

In 3.9 there is now possibility to work also on Activities in status Released.

 

Classifications

One of the challenges in implementing a universal platform in a given organization is adapting it to its specific requirements without sacrificing overall consistency. This applies to both the application interface and data organization.

In the domain of the LogiX platform examples are:

  • Machines Downtimes classification, for purpose of detailed OEE losses reporting

  • Machines Downtimes classification which guides users during downtime registration

  • Classification of machines in terms of their function or role in the production process

  • Classification of machines in terms of their mechanical or electrical characteristics

One of the new upcoming core features of the LogiX platform addressing these issues is a concept called "Classifications". 

Intention of this functionality is to create a mechanism that allows categorization of various types of objects defined in LogiX (e.g. elements, downtime) into user-configurable structures. Such structures could be used for generating reports (e.g. machine energy report based on physical location in a factory, or downtime report broken down into factory-specific categories).

We will introduce it gradually. In the upcoming release, it will manifest as the possibility to have a specific classification for:

  • production events ("problems" in PackOS language) which will extend the build-in, standard one.

  • factory structure (i.e classification of lines alternative to default ISA-95 plant/area/line/machine structure). 

This version will not yet allow for creating and managing custom classifications from the user interface.

 

We can choose which classification we will use in ConfigHub/Plant for factory structure. In this version there’s only Default one, which is classification of lines alternative to default ISA-95 plant/area/line/machine structure

 

Data exporting

In Reports there’ll be now accessible new tab called Reports Download. These exports makes use of classifications to filter, classify and aggregate assets and events.

If we find report in which we are interested in, depending on it’s type we can choose on which data (Areas/Lines) with period and moment will be included in report.

Exported reports are always csv files.

 

More information about reports here → https://ilabo.atlassian.net/wiki/spaces/LW/pages/2111733763


Changes in orders creation

Right now after creating new order which got no Description field filled, SKU Description will be used instead.



Cleanings

In this version using Cleaning activity is now fully accessible! To configure signals and states for a line see https://ilabo.atlassian.net/wiki/spaces/LW/pages/1868759041

 

Public API extension

Expanding existing API thanks to classifications

 

Cockpit changes

  • process of setting downtime’s reason, corrective action or comment is now easier. After clicking on the downtime we are interested in there is now immediately possibility to set these.

 

  • 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)