Status Code Definitions
Table of Contents
- Overview
- Alarm Priority
- Diagnostic Level
- Communication Connection Status (OPC/Edge)
- Communication Latency Status (OPC Latency)
- Health Status (Site/Area/Line/Equipment)
- Connection Status Aggregation (Per Hierarchy Level)
- System Health Status
- Health Check Status (Infrastructure Components)
- Equipment Operating Status (OEE)
- Work Order Status (Full Lifecycle)
- Calendar (Shift) Status
- Tag Alarm Band Codes
- Entity Lifecycle Events
- Flow Node Relations
- Common Color Palette
Overview
This reference collects, on a single page, the meaning of every status badge, icon, and color shown throughout the Platform screens. When you run into a color or code during operation and are unsure what it means, look it up here.
This document is not a screen guide but a status code reference, mapping the codes displayed across the following screens.
Alarm Priority
Three severity levels for alarms.
| Code | Korean | Color | HEX | Description | Recommended Action |
|---|---|---|---|---|---|
INFO | 정보 | Green | #5eb561 | Informational alarm | No immediate action required; for reference |
WARN | 경고 | Orange | #eb7f0a | Attention required | Check the trend; prepare for inspection as the threshold is approached |
ERROR | 심각 | Red | #d9534f | Immediate action required | Inspect the affected asset or notify the system administrator |
Alarm Band to Priority Mapping
Alarm bands (threshold ranges) are mapped to priorities automatically.
| Alarm Band | Mapped Priority |
|---|---|
NORMAL | No alarm |
HIGH / LOW | INFO (Info) |
HIGH-HIGH / LOW-LOW | WARN (Warning) |
TRIP-HIGH / TRIP-LOW | ERROR (Critical) |
Alarm Active / Acknowledged State
| Field | Value | Meaning |
|---|---|---|
is_on | Y | Alarm active (ongoing) |
is_on | N | Alarm cleared (recovered) |
is_read | Y | Acknowledged |
is_read | N | Unread |
Even if an operator has acknowledged an alarm (
is_read=Y), it is still shown as an active alarm on screen as long as it has not recovered (is_on=Y).
Diagnostic Level
Severity of the system diagnostic logs shown on the Diagnostics screen.
| Code | Korean | Color | HEX | Description |
|---|---|---|---|---|
INFO | 정보 | Blue | #5bc0de | Normal operation information (startup/shutdown notices, etc.) |
WARN | 경고 | Orange | #f0ad4e | Potential problem; monitoring required |
ERROR | 심각 | Red | #d9534f | Critical condition; immediate inspection required |
On-screen colors may differ slightly depending on the theme setting of the operating environment.
Communication Connection Status (OPC/Edge)
The data reception status of OPC servers and Edge devices is determined from the last reception time.
| Code | Korean | Color | HEX | Threshold | Description |
|---|---|---|---|---|---|
OK | 연결됨 | Green | #2e7d32 | Less than 10 minutes | Data reception normal |
WARN | 연결지연 | Orange | #e65100 | 10 to 60 minutes | No data received; caution |
ERROR | 연결이상 | Red | #b71c1c | 60 minutes to 24 hours | No data for over an hour |
DISCONNECTED | 연결끊김 | Gray | #888 | More than 24 hours | No data for over 24 hours |
UNKNOWN | 미관측 | Light gray | #ccc | — | No reception history at all |
The 10-minute, 60-minute, and 24-hour thresholds are set by
StatusThresholds. A few older screens, such as the asset tree legend, labelOKas "정상연결" andUNKNOWNas "미연결" — only the names differ; the states are the same.
Quick Identification Tips
| Situation | Meaning |
|---|---|
| Immediately after registering a new OPC | UNKNOWN (never received) |
| Collection operating normally | OK |
| Brief disconnection (network/restart) | WARN |
| Disconnected for more than an hour | ERROR (inspect Connection Management immediately) |
| Disconnected for more than a day | DISCONNECTED (inspect device/network) |
Communication Latency Status (OPC Latency)
There are two sets of criteria for latency. Which one applies depends on the screen you are looking at.
① For status determination — average latency criteria
The criteria used when rating asset health (StatusEvaluator).
| Code | Korean | Color | Threshold (average latency) | Description |
|---|---|---|---|---|
OK | 정상 | Green | Less than 1 second | No response delay |
WARN | 지연 | Orange | 1 to 10 seconds | Response delay occurring |
ERROR | 심각지연 | Red | 10 seconds or more | Severe response delay |
UNKNOWN | 알수없음 | Gray | — | No latency measurement data |
② For trend charts — interval maximum latency criteria
The communication latency status trend chart on the Connection Status
screen counts by the maximum latency in that time interval (max_latency), not by the criteria above.
| Bar | Threshold (interval maximum latency) |
|---|---|
| 🟢 Normal | Less than 10 seconds |
| 🟠 Delayed | 10 to 60 seconds |
| 🔴 Severely delayed | 60 seconds or more |
The ⓘ help text on that chart reads "average latency under 1 second / 1~10 seconds / 10 seconds or more," but the bars are computed using ② (maximum, 10 s/60 s). The tooltip numbers and the bars use different criteria, so read the chart according to ②.
A connection averaging 3 seconds appearing green on the chart is not a fault — it is this difference.
Health Status (Site/Area/Line/Equipment)
Health status per hierarchy level. Determined by the highest level among the alarms raised beneath that level.
| Code | Korean | Color | HEX | Description |
|---|---|---|---|---|
NORMAL | 정상 | Green | #3d8b40 | No alarms |
WARN | 주의 | Orange | #eb7f0a | One or more warning alarms |
ERROR | 위험 | Red | #d9534f | One or more critical alarms |
UNKNOWN | 미상 | Light gray | #ccc | No evaluation data (e.g., just after registration) |
Determination logic: one or more critical alarms → ERROR, one or more warning alarms → WARN, otherwise → NORMAL. If no evaluation exists at all, UNKNOWN.
Connection Status Aggregation (Per Hierarchy Level)
The connection status of a hierarchy level such as site/area/line/equipment is determined by aggregating the status of every OPC/Edge belonging to that level.
| Code | Korean | Color | Description |
|---|---|---|---|
NORMAL | 연결됨 | Green | All children are OK |
WARN | 연결지연 | Orange | One or more children are WARN |
ERROR | 연결이상 | Red | One or more children are ERROR |
DISCONNECTED | 연결끊김 | Dark red (#4a0e0e) | One or more children are DISCONNECTED |
UNKNOWN | 미관측 | Light gray | No evaluation data among the children |
Determination logic (highest → lowest priority): DISCONNECTED → ERROR → WARN → NORMAL → UNKNOWN.
System Health Status
Overall Platform health. Determined by diagnostic log counts.
| Code | Korean | Color | Description |
|---|---|---|---|
NORMAL | 정상 | Green | No diagnostic logs |
INFO | 정보 | Blue | Only informational diagnostics raised |
WARN | 경고 | Orange | Warning diagnostics raised |
ERROR | 위험 | Red | Critical diagnostics raised; system inspection required |
The load watchdog runs its own three-level HEALTHY/DEGRADED/CRITICAL state machine on the Dashboard health rail and Diagnostics screens.
| Watchdog State | Meaning | Emits |
|---|---|---|
HEALTHY | Normal load | (one line logged on recovery) |
DEGRADED | Level 1 threshold exceeded for 30 seconds or more | One diagnostic log line (WARN) |
CRITICAL | Level 2 threshold exceeded for 30 seconds or more | One diagnostic log line (ERROR) |
Health Check Status (Infrastructure Components)
Shown in the "Infrastructure" section of the Dashboard health rail.
Result Codes
| Code | Korean | Meaning |
|---|---|---|
NORMAL | 정상 | Component operating normally |
ABNORMAL | 비정상 | Component fault detected |
UNKNOWN | 알수없음 | No health check result received |
Health Check Targets (per dashboard health rail labels)
| Label | Role |
|---|---|
| 인-메모리 캐시 | Operational data cache |
| 웹소켓 | Real-time push channel |
| MQTT | MQTT message channel |
| KAFKA | KAFKA message channel |
| 이벤트 스토어 | Persistent event and time series store |
| 시계열 엔진 | Time series data processing engine |
The component labels are the names shown verbatim on the operations screen. They are retained even when the internal implementation changes.
Equipment Operating Status (OEE)
Equipment operating status based on OEE (Overall Equipment Effectiveness).
| Code | Korean | Color | HEX | Description |
|---|---|---|---|---|
RUN | 가동 | Green | #15803D | Running normal production |
IDLE | 유휴 | Orange | #D97706 | Waiting (material shortage, awaiting order, etc.) |
FAULT | 고장 | Red | #B91C1C | Down due to equipment failure/fault |
STOP | 정지 | Dark gray | #374151 | Intentional stop by an operator |
SETUP | 셋업 | Blue | #1D4ED8 | Preparation/setup (die change, warm-up) |
PLANNED_STOP | 계획정지 | Blue | #1D4ED8 | Planned stop (lunch, scheduled inspection, holiday) |
PLANNED_START | 계획시작 | Blue | #1D4ED8 | Planned start of operation |
DOWN | 비가동 | Gray | #4B5563 | Non-operating state |
UNKNOWN | 알수없음 | Gray | #888 | State unknown |
Operating / Non-operating Classification
| Class | Included Codes |
|---|---|
| Operating | RUN, SETUP (production preparation), PLANNED_START |
| Non-operating | IDLE, FAULT, STOP, PLANNED_STOP, DOWN, UNKNOWN |
Availability in OEE is calculated as operating time ÷ planned operating time (planned stops are excluded from the denominator).
Work Order Status (Full Lifecycle)
The state machine for work orders. These five are the values actually persisted.
The work order list displays seven states by adding Delayed and Canceled, but those two are not persisted states — the screen derives them by comparing the waiting state against the current time. The derivation rules are in that document.
| Code | Korean | Color | HEX | Description |
|---|---|---|---|---|
WAIT | 대기 | Gray | #888 | Awaiting work order execution (default state right after creation) |
START | 진행중 | Green | #15803D | Work order in progress |
PAUSED | 일시정지 | Orange | #D97706 | Work temporarily suspended (can be resumed) |
END | 완료 | Dark gray | #374151 | Work completed normally |
ABORTED | 중단 | Dark red | #7f1d1d | Work terminated abnormally (quality issue, line isolation, etc.) |
State Transition Diagram
WAIT ─[start]─▶ START ─[pause]─▶ PAUSED
│ ▲ │
│ └─[resume]─────┘
│
├─[end]──────▶ END
│
└─[abort]────▶ ABORTED
▲
PAUSED ───[abort]──┘
PAUSED ───[end]────▶ END
| Transition | Automation Node |
|---|---|
WAIT → START | flow_start_work_order |
START → PAUSED | flow_pause_work_order |
PAUSED → START | flow_resume_work_order |
START/PAUSED → END | flow_end_work_order |
START/PAUSED → ABORTED | flow_abort_work_order (abort_code/notes option) |
For details on automation nodes, see Flow — Work Order State Transitions.
Calendar (Shift) Status
Status of work schedule (shift) entries.
| Code | Korean | Color | HEX | Description |
|---|---|---|---|---|
UPCOMING | 예정 | Gray | #888 | Future schedule |
PROGRESS | 진행중 | Green | #15803D | Shift currently in progress |
DONE | 완료 | Dark gray | #374151 | Ended shift |
Tag Alarm Band Codes
Codes indicating which alarm band range a tag is in.
Numeric
| Code | Korean | Meaning |
|---|---|---|
NORMAL | 정상 | No-alarm range |
HIGH | 상한 | User-defined high limit exceeded |
LOW | 하한 | Below user-defined low limit |
HIGH-HIGH | 상상한 | Critical high limit exceeded |
LOW-LOW | 하하한 | Below critical low limit |
TRIP-HIGH | 트립상한 | Trip high limit exceeded (immediate stop recommended) |
TRIP-LOW | 트립하한 | Below trip low limit (immediate stop recommended) |
Boolean
| Code | Korean | Description |
|---|---|---|
BOOL_TRUE | 참 | When the tag value is true |
BOOL_FALSE | 거짓 | When the tag value is false |
A separate priority (bool_true_priority / bool_false_priority) and message (bool_true_message / bool_false_message) can be defined for each boolean value.
Entity Lifecycle Events
Change event types for domain entities (assets, tags, work orders, shifts, etc.).
| Event | When It Occurs |
|---|---|
ENTITY_CREATED | Immediately after an entity is created |
ENTITY_UPDATED | Immediately after entity metadata is modified |
ENTITY_DELETED | Immediately after an entity is deleted |
The flow_on_entity_event trigger in Flow receives these events.
Asset-Level Events
| Event | Occurs On |
|---|---|
ASSET_DATA | Asset telemetry ingress |
ASSET_EVENT | Asset domain event |
ASSET_ALARM | Asset alarm raised |
ASSET_COMMAND | Asset command issued |
ASSET_AGGREGATION | Asset aggregation (e.g., 6-hour average) |
ASSET_CONTEXT | Asset context |
ASSET_HEALTH_STATUS | Asset health periodic evaluation result |
ASSET_CONNECTION_STATUS | Asset connection periodic evaluation result |
Flow Node Relations
Relation labels shown on the wires between nodes on the Flow screen. All are uppercase.
| Code | Meaning |
|---|---|
SUCCESS | Processing completed normally |
FAILURE | Processing failed (usually branches to an error handler) |
TRUE | Condition filter true |
FALSE | Condition filter false |
MATCH | Matching branch of a Switch node |
NO_MATCH | Non-match on a Switch node |
DEFAULT | No case matched on a Switch node |
THROTTLED | Blocked by a Throttle node |
EXHAUSTED | Retry maximum attempts exceeded |
SKIPPED | Trigger pattern did not match (not counted toward executions) |
Common Color Palette
Basic Three-Level Status Colors
| Status | Color Name | HEX |
|---|---|---|
| Normal | Green | #5eb561 |
| Warning | Orange | #eb7f0a |
| Critical/Danger | Red | #d9534f |
| Inactive/Unknown | Gray | #888 |
| Very critical (disconnected) | Dark red | #4a0e0e / #7f1d1d |
Equipment Status Colors (OEE)
| Status | Color Name | HEX |
|---|---|---|
| Running | Green | #15803D |
| Idle | Orange | #D97706 |
| Fault | Red | #B91C1C |
| Stopped | Dark gray | #374151 |
| Setup/Planned | Blue | #1D4ED8 |
| Non-operating | Gray | #4B5563 |
| Unknown | Gray | #888 |
Alarm Priority Colors (Separate Palette)
| Priority | HEX |
|---|---|
| Info (INFO) | #5bc0de (side panel) / #5eb561 (list badge) |
| Warning (WARN) | #f0ad4e (side panel) / #eb7f0a (list badge) |
| Critical (ERROR) | #d9534f (common) |
Even colors with the same meaning use slightly different tones depending on the screen area. Display consistency is maintained within a single screen.
Default Chart Series Color Order
Multiple chart series are assigned colors in the following order.
파랑 → 녹색 → 주황 → 보라 → 청록 → 빨강 → 노랑 → 회색 → ...
When a chart has many series, some colors may repeat.