Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

Applies to LogiX v. 3.10 and above

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 LogiX 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

A core feature of the LogiX platform addressing these issues is a concept called "Taxonomies".

Taxonomies are arbitrarily defined hierarchical dictionaries for systematic organization and classifications of facts and entities represented in LogiX. Examples are:

  • Grouping production lines into categories according to organizational aspects other than ISA-95 factory structure (Site/Area/Line/Machine).

  • Grouping downtimes into categories according to organizational resources needed to resolve them.

  • Grouping machines into categories according to their kind and functional characteristics (e.g Sorters, Fillers, Packers, Labelers)

Each taxonomy is defined by:

  • taxonomy structure - (levels list or levels tree)

  • taxonomy content - hierarchy of nodes assigned to levels

    Example of a taxonomy (ISA95 taxonomy for a sample factory):

System classifications that are build-in into LogiX are also implemented and exposed as taxonomies. This includes:

  • standard ISA-95 factory structure (Site/Area/Line/Machine) which is obligatory for each Line and Machine configured in Logix. This taxonomy is used also to uniquely identify assets (i.e. while pointing root cause machine for line downtime). Levels of this taxonomy (Site/Area/Line/Machine) are read-only and cannot be altered.

  • standard production event (downtime) classification used to calculate OEE

Standard, 'Loss Type' categorization which is required to calculate OEE is defined as a simple list:

  • Utilization Loss

  • Availability Loss

  • Performance loss

  • Quality loss

In previous versions, each configured factory event ("problem") was assigned to a given category using dedicated 'Tags'.

In the current version, this list is defined as built-in taxonomy.

This taxonomy can be optionally further customized for each Logix deployment, to meet client needs by assigning sub-categories for each kind of loss.Ā 

Now the configuration of "problems" in terms of impact on OEE is defined by assigning a given problem to a taxonomy leaf, while Tags are still used to configure other aspects of signal processing.

Example of customized OEE-loss categorization:

  • Utilization LossĀ 

    • Unoccupied timeĀ 

      • IdleĀ 

      • Breaks

      • Legal

  • Availability Loss

    • Planned

      • Maintenance

      • Changeovers

      • Training

      • Others

    • Unplanned

      • Breakdown

      • Waiting

      • Others

  • Performance lossĀ 

  • Quality lossĀ 

2 Factory structure taxonomy. In this version, changes are visible only in the user interface for Config Hub, where plant structure can be viewed using the chosen taxonomy:

Ā (more on taxonomies soon in KB)

  • No labels