Skip to content

Hierarchy Overview

LineInterpreter uses a tree of nodes to represent your physical production site. Every piece of data — production counts, alarms, shift records, dashboards — is tied to a position in this hierarchy. Configuring the hierarchy correctly is the foundation for everything else in the system.

Navigate to Settings → Line Setup → Hierarchy. The editor shows the full node tree. Clicking any node opens its configuration panel on the right. Nodes can be created, edited, and deleted directly in the editor.

Node typePurpose
OrganisationThe root node. Created automatically. Holds license and monitor point limit information.
SiteA physical location grouping one or more lines. No extra configuration required.
LineA production line. Carries run-rate targets, timezone, line type, downtime thresholds, and shift/notification settings.
LocationA named sub-location within a site, used to annotate where an alarm or downtime event occurred.
PLCA physical PLC (controller). Configured with a communication path and protocol.
Communication InstanceAn edge client node (ClientService instance). Identified by a unique node identifier string.
Monitor PointA data collection point on a line. Links a PLC and communication instance to a set of production, alarm, and quality tags.

A minimal working setup looks like this:

Organisation
└── Site
└── Line
└── Monitor Point ← linked to a PLC and Communication Instance
PLC (can sit anywhere — often directly under the Line)
Communication Instance (can sit anywhere - often directly under the Organisation or Site)
  1. Create the Site and Line nodes.
  2. Create the PLC node and enter its communication path.
  3. Create the Communication Instance node for the edge client.
  4. Create the Monitor Point under the Line, and link it to the PLC and Communication Instance.
  5. Configure production tags, alarm tags, and quality tags on the Monitor Point.
  6. Set the Primary Monitor Point on the Line to the newly created monitor point.