Glossary
This section provides detailed explanations of terms frequently used in this manual and throughout the interface.
In some instances, the interface and the documentation use different terms for the same concept. Since they refer to the same item, please refer to the table below for consistency.
| Common in Interface | Common in Documentation | Definition |
|---|---|---|
| Asset | 자산 | A node in the equipment hierarchy — both are notations for English asset |
| Work Order | 작업지시 | A production instruction unit — both are notations for English work order |
| Edge | Gateway | Equipment that reads values from the field. The Edge manual prefers «Gateway», while the Platform manual prefers «Edge» |
If a search does not yield results, try searching again using the alternative term.
Asset Hierarchy — Structural Containment
All data in the Platform is structured based on the ISA-95 hierarchy. This determines which node is referred to by terms such as "Line 3 Compressor."
Enterprise ─ Site ─ Area ─ Line ─ Equipment ─ Tag ─ Point
기업 사이트 구역 라인 설비 태그 값
Enterprise
The topmost layer of the hierarchy. As there is only one per installation, it cannot be created or deleted; only its name and attributes can be modified.
Site
A single factory or business location. Most inquiry screens prompt for the Site first. There is no «All Sites» option for scope selection; instead, «All ...» for areas, lines, or equipment refers to everything within the selected Site.
Area · Line
Spatial or process units within a Site. These serve as axes for grouping equipment.
Equipment
The actual machinery corresponding to the leaves of the hierarchy. This is where tags are assigned.
Asset
A collective term for nodes at the levels mentioned above. Enterprises, Sites, and Equipment are all assets. The «Asset Tree» refers to this entire hierarchy. The level of a node is defined by asset_type(E · S · A · L · M) rather than the ID.
Asset Class
A code (asset_class_code) indicating the type of a node. Sites, areas, lines, and equipment each have their own classification lists, which are managed in the Site/Area/Line/Equipment classification tabs of Master Data.
Tag
A configuration that defines what to read and how frequently. It corresponds to a single PLC address. Values arriving from the field enter the system under this name.
Point
A single value actually stored after entering via a tag. If a tag is a «faucet», a point is the «water collected». This is the point referred to when a chart indicates 「1,204 data points」.
A tag is a configuration, so its count rarely changes. A point is a value, so the count increases every second. «How many tags are there?» and «How much data has accumulated?» are two different questions.
Data Ingestion Path
Edge
Equipment attached to field PLCs that reads values and uploads them to the upper Platform. Because it has its own storage, collection does not stop even if the connection to the upper level is lost → Edge Manual
OPC Connection
A single path by which the Edge connects to equipment. It defines which protocol to use and which address to connect to.
Collection Period
The polling interval defined for each tag. Shorter intervals increase the load on the PLC.
Monitoring and Incident Awareness
Alarm
A notification triggered when predefined conditions are met. Priorities are INFO · WARN · ERROR. A single band alarm can be set for one tag, while other conditions are set using EQL.
Acknowledge
There is one acknowledgement per occurrence. Once someone acknowledges it, the occurrence is considered acknowledged for everyone, and a record of who acknowledged it and when is maintained. The Alarm Acknowledge and Acknowledge All Alarms buttons on the screen perform this function.
Shelving · Maintenance Suppression · Out of Service
There are three ways an alarm may not appear in the list (per ISA-18.2); occurrences during these periods are recorded separately rather than in the alarm list → Alarm
| Term | Who | Duration |
|---|---|---|
| Shelving | Operator | Until a specified time. It reappears automatically. Safety and environmental alarms cannot be shelved |
| Maintenance Suppression | Equipment State — Equipment undergoing planned maintenance or repair (Repair Suppression) | Until maintenance or repair is complete. If still active at that time, it appears as a new occurrence |
| Out of Service | Administrator | Until it returns after passing a return inspection. It does not clear automatically |
This is distinct from redundant alarm suppression (a setting that bundles the same alarm pushes for a set number of minutes).
Diagnostic
Records of the Platform's own status. These are system-side events, such as «collection stopped», rather than equipment anomalies → Diagnostic
Event · Statement
Outputs generated when conditions defined by EQL are met. These serve as the raw material for alarms.
Metrics
OEE
Overall Equipment Effectiveness. Calculated as Availability × Performance × Quality.
RAM
Reliability metrics. Includes MTBF (Mean Time Between Failures), MTTR (Mean Time To Repair), and Failure Rate.
EMS
Energy metrics. Includes power consumption, peak demand, and carbon emissions.
Work Order
A single production instruction specifying what to produce and how much, and the time frame. OEE and quality are grouped by this unit.
Maintenance Order
A single maintenance task generated via call, plan, or external integration. The process flows from Call → Receipt → Start → Complete. The ID follows the MAINTENANCE_ORDER_000001 format, and the screen menu is also labeled Maintenance Order.
Failure Record
A single failure event (ISO 14224) with start and end times captured from tag signals. This is the basis for RAM metrics. It is a different record from a maintenance order — a failure records «what happened», while a maintenance order records «who did what».
Configuration and Automation
EQL (Event Query Language)
A proprietary query language that operates on a continuous event stream. While SQL views static tables, EQL produces results every moment based on continuously incoming values → EQL
Flow
An automation interface where external system integrations and domain object creation/updates are drawn as a graph. Nodes are dragged and connected with lines → Flow
Despite the similar names, they operate at different levels.
| Flow | Workflow | |
|---|---|---|
| Definition | Automation graph drawn by the user on the screen | Batch job run internally by the Data Lake |
| User | Field Personnel / Engineer | The Platform itself |
| Engine | Built-in Platform engine | Temporal · Kestra |
| Location | Flow | Data Lake Console |
«Workflow failed» usually refers to internal batches such as archiving or optimization and is unrelated to the Flow you have drawn.
Canvas
A screen where values are overlaid on field drawings → Canvas
UNS (Unified Namespace)
An expansion of the asset hierarchy directly into message topic paths. This shows how topics for Kafka, MQTT, and Sparkplug B are constructed → UNS
AI Integration
MCP (Model Context Protocol)
An open standard that allows AI agents to discover and call external system functions as «tools». Because the Platform speaks this standard, AI products do not need to know the internal workings of the Platform.
Ontology
A graph containing the relationships (supply, dependency, production) between assets. This provides the basis for answering «if this stops, what is affected?».
Storage
Data Lake
A section that groups time series, relational, and object stores with an analysis engine → Data Lake
Tiered Storage
A method of placing frequently accessed recent values in high-speed storage and older values in lower-cost storage.
TTL
The period until a value is automatically deleted → Data Retention Policy
Terms for Other Products
Four products within PlantPulse share the same asset hierarchy, tags, and points. Terms not listed here can be found in the other three manuals — Edge Glossary, AI Glossary, and Studio Glossary.