Skip to main content

Status Code Definitions

Table of Contents


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.

CodeKoreanColorHEXDescriptionRecommended Action
INFO정보Green#5eb561Informational alarmNo immediate action required; for reference
WARN경고Orange#eb7f0aAttention requiredCheck the trend; prepare for inspection as the threshold is approached
ERROR심각Red#d9534fImmediate action requiredInspect the affected asset or notify the system administrator

Alarm Band to Priority Mapping

Alarm bands (threshold ranges) are mapped to priorities automatically.

Alarm BandMapped Priority
NORMALNo alarm
HIGH / LOWINFO (Info)
HIGH-HIGH / LOW-LOWWARN (Warning)
TRIP-HIGH / TRIP-LOWERROR (Critical)

Alarm Active / Acknowledged State

FieldValueMeaning
is_onYAlarm active (ongoing)
is_onNAlarm cleared (recovered)
is_readYAcknowledged
is_readNUnread

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.

CodeKoreanColorHEXDescription
INFO정보Blue#5bc0deNormal operation information (startup/shutdown notices, etc.)
WARN경고Orange#f0ad4ePotential problem; monitoring required
ERROR심각Red#d9534fCritical 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.

CodeKoreanColorHEXThresholdDescription
OK연결됨Green#2e7d32Less than 10 minutesData reception normal
WARN연결지연Orange#e6510010 to 60 minutesNo data received; caution
ERROR연결이상Red#b71c1c60 minutes to 24 hoursNo data for over an hour
DISCONNECTED연결끊김Gray#888More than 24 hoursNo data for over 24 hours
UNKNOWN미관측Light gray#cccNo 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, label OK as "정상연결" and UNKNOWN as "미연결" — only the names differ; the states are the same.

Quick Identification Tips

SituationMeaning
Immediately after registering a new OPCUNKNOWN (never received)
Collection operating normallyOK
Brief disconnection (network/restart)WARN
Disconnected for more than an hourERROR (inspect Connection Management immediately)
Disconnected for more than a dayDISCONNECTED (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).

CodeKoreanColorThreshold (average latency)Description
OK정상GreenLess than 1 secondNo response delay
WARN지연Orange1 to 10 secondsResponse delay occurring
ERROR심각지연Red10 seconds or moreSevere response delay
UNKNOWN알수없음GrayNo 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.

BarThreshold (interval maximum latency)
🟢 NormalLess than 10 seconds
🟠 Delayed10 to 60 seconds
🔴 Severely delayed60 seconds or more
The chart tooltip shows the numbers from ①

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.

CodeKoreanColorHEXDescription
NORMAL정상Green#3d8b40No alarms
WARN주의Orange#eb7f0aOne or more warning alarms
ERROR위험Red#d9534fOne or more critical alarms
UNKNOWN미상Light gray#cccNo 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.

CodeKoreanColorDescription
NORMAL연결됨GreenAll children are OK
WARN연결지연OrangeOne or more children are WARN
ERROR연결이상RedOne or more children are ERROR
DISCONNECTED연결끊김Dark red (#4a0e0e)One or more children are DISCONNECTED
UNKNOWN미관측Light grayNo evaluation data among the children

Determination logic (highest → lowest priority): DISCONNECTEDERRORWARNNORMALUNKNOWN.


System Health Status

Overall Platform health. Determined by diagnostic log counts.

CodeKoreanColorDescription
NORMAL정상GreenNo diagnostic logs
INFO정보BlueOnly informational diagnostics raised
WARN경고OrangeWarning diagnostics raised
ERROR위험RedCritical 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 StateMeaningEmits
HEALTHYNormal load(one line logged on recovery)
DEGRADEDLevel 1 threshold exceeded for 30 seconds or moreOne diagnostic log line (WARN)
CRITICALLevel 2 threshold exceeded for 30 seconds or moreOne diagnostic log line (ERROR)

Health Check Status (Infrastructure Components)

Shown in the "Infrastructure" section of the Dashboard health rail.

Result Codes

CodeKoreanMeaning
NORMAL정상Component operating normally
ABNORMAL비정상Component fault detected
UNKNOWN알수없음No health check result received

Health Check Targets (per dashboard health rail labels)

LabelRole
인-메모리 캐시Operational data cache
웹소켓Real-time push channel
MQTTMQTT message channel
KAFKAKAFKA 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).

CodeKoreanColorHEXDescription
RUN가동Green#15803DRunning normal production
IDLE유휴Orange#D97706Waiting (material shortage, awaiting order, etc.)
FAULT고장Red#B91C1CDown due to equipment failure/fault
STOP정지Dark gray#374151Intentional stop by an operator
SETUP셋업Blue#1D4ED8Preparation/setup (die change, warm-up)
PLANNED_STOP계획정지Blue#1D4ED8Planned stop (lunch, scheduled inspection, holiday)
PLANNED_START계획시작Blue#1D4ED8Planned start of operation
DOWN비가동Gray#4B5563Non-operating state
UNKNOWN알수없음Gray#888State unknown

Operating / Non-operating Classification

ClassIncluded Codes
OperatingRUN, SETUP (production preparation), PLANNED_START
Non-operatingIDLE, 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 screen shows two more

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.

CodeKoreanColorHEXDescription
WAIT대기Gray#888Awaiting work order execution (default state right after creation)
START진행중Green#15803DWork order in progress
PAUSED일시정지Orange#D97706Work temporarily suspended (can be resumed)
END완료Dark gray#374151Work completed normally
ABORTED중단Dark red#7f1d1dWork 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
TransitionAutomation Node
WAITSTARTflow_start_work_order
STARTPAUSEDflow_pause_work_order
PAUSEDSTARTflow_resume_work_order
START/PAUSEDENDflow_end_work_order
START/PAUSEDABORTEDflow_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.

CodeKoreanColorHEXDescription
UPCOMING예정Gray#888Future schedule
PROGRESS진행중Green#15803DShift currently in progress
DONE완료Dark gray#374151Ended shift

Tag Alarm Band Codes

Codes indicating which alarm band range a tag is in.

Numeric

CodeKoreanMeaning
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

CodeKoreanDescription
BOOL_TRUEWhen 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.).

EventWhen It Occurs
ENTITY_CREATEDImmediately after an entity is created
ENTITY_UPDATEDImmediately after entity metadata is modified
ENTITY_DELETEDImmediately after an entity is deleted

The flow_on_entity_event trigger in Flow receives these events.

Asset-Level Events

EventOccurs On
ASSET_DATAAsset telemetry ingress
ASSET_EVENTAsset domain event
ASSET_ALARMAsset alarm raised
ASSET_COMMANDAsset command issued
ASSET_AGGREGATIONAsset aggregation (e.g., 6-hour average)
ASSET_CONTEXTAsset context
ASSET_HEALTH_STATUSAsset health periodic evaluation result
ASSET_CONNECTION_STATUSAsset connection periodic evaluation result

Flow Node Relations

Relation labels shown on the wires between nodes on the Flow screen. All are uppercase.

CodeMeaning
SUCCESSProcessing completed normally
FAILUREProcessing failed (usually branches to an error handler)
TRUECondition filter true
FALSECondition filter false
MATCHMatching branch of a Switch node
NO_MATCHNon-match on a Switch node
DEFAULTNo case matched on a Switch node
THROTTLEDBlocked by a Throttle node
EXHAUSTEDRetry maximum attempts exceeded
SKIPPEDTrigger pattern did not match (not counted toward executions)

Common Color Palette

Basic Three-Level Status Colors

StatusColor NameHEX
NormalGreen#5eb561
WarningOrange#eb7f0a
Critical/DangerRed#d9534f
Inactive/UnknownGray#888
Very critical (disconnected)Dark red#4a0e0e / #7f1d1d

Equipment Status Colors (OEE)

StatusColor NameHEX
RunningGreen#15803D
IdleOrange#D97706
FaultRed#B91C1C
StoppedDark gray#374151
Setup/PlannedBlue#1D4ED8
Non-operatingGray#4B5563
UnknownGray#888

Alarm Priority Colors (Separate Palette)

PriorityHEX
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.