Connection Management

Table of Contents

• Overview
• Screen Configuration — 3 Sub-menus
• Protocol Screen (/connect/index)
  • Data Source Categories
  • OPC List Screen (/connect/opc/index)
  • Add New Connection — Input Items and Protocols
• Status Screen (/connect/status)
  • Top Tools
  • Left — Statistics Charts and History
  • Right — Data Source Card Grid
• Data Source Detail Screen (/connect/view)
  • Left ① Connection Basic Information + Expand
  • Left ② Connection Statistics (Latency/Status 5 Types)
  • Right ① Connection Status Timeline + LIVE Dot
  • Right ② 24-Hour Point Reception Chart
  • Right ③ Connected Tag List
• Edge Screen (/edge/index)
  • List Table (8 Columns)
  • Edge Help Box
• Edge Detail Screen (/edge/view)
  • Top Page Header and Refresh
  • Left — Basic Info, Host, Network, Security 4 Panels
  • Right ① System Resource Gauge + App Restart
  • Right ② PLC / Collection Statistics (8-slot stat-box)
  • Right ③ OPC Status + 5 Summary Chips + Start/Stop Collection
  • Right ④ Docker Containers (Remote Deploy, Start, Stop, Log, Delete)
  • Safe Procedures for System Reboot and App Restart
• Usage Scenarios
• Frequently Asked Questions
• Related Screens

---

Overview

The Connectivity group registers and inspects connections to collect data from external systems (field PLCs, OPC servers, files, external DBs, MQTT/Kafka topics, etc.). The menu consists of the following three sub-screens.

Sub-menu	Internal URL	Purpose
Protocol	/connect/index	Register new connections — entry point for adding by data source type
Connection Status	/connect/status	Monitor communication status, latency, and verification failures of active connections
Edge	/edge/index	System status and PLC collection statistics of field Edge devices

---

Screen Configuration — 3 Sub-menus

Screen	Primary User	Summary
Protocol	System Administrator	Add new data sources (Edge/OPC/PLC/Modbus/External DB/File·API)
Connection Status	Operator	Connection normal/latency/anomaly trends and 24-hour disconnection, latency, and verification failure history
Edge	Operator	Edge OS status (CPU/Memory/Disk/Network) + PLC collection statistics

Names of the Five Connection Statuses

The connection status names used in this document and on the screens are Connected, Connection Latency, Connection Anomaly, Disconnected, and Unobserved. The code values are OK, WARN, ERROR, DISCONNECTED, and UNKNOWN respectively, and the definitions are located in Status Code Definitions.

Some older screens, such as the asset tree legend, may list OK as "Normal Connection" — these refer to the same status.

---

Protocol Screen (/connect/index)

A guidance box is displayed at the top.

🌐 Connections for Industrial Protocols and Other Data Sources [Recommended] Integrates perfectly with the PlantPulse Edge gateway without additional configuration. You can collect data by connecting to widely used industrial OPC, PLC, Modbus protocols, and databases. Additionally, you can collect from MQTT, STOMP, KAFKA, and HTTP via the provided client API. (OPC connects automatically; others use the Edge gateway or collector corresponding to the protocol.)

Number	Position	Function
①	Top	Guidance Box — Text as written above
②	First Section	Edge Gateway / File / API [84] — Bracketed number is the number of currently registered connections
③	Section Right	View List — Navigates to the connection list screen for that category
④	Card Bottom	Connect — Opens the registration form for that type
⑤		OPC [37] — The only category the Platform connects to directly
⑥		PLC [135] — Manufacturer-specific protocols
⑦		Modbus [6]
⑧	Last	Database [0] — Displays [0] if nothing is registered

Data Source Categories

The page is divided into large sections by category, and each section displays icon cards for data source types (including "Connect" links) in a grid.

Section	Displayed Cards	Add Link
Edge Gateway / File / API [N]	Edge Gateway, MQTT, REST API, Excel, CSV (5 types)	/connect/file/add
OPC [N]	OPC Standard Data Sources (Automatic Connection)	/connect/opc/index List
PLC [N]	PLC Communication (Manufacturer-specific protocols)	/connect/plc/index List
Modbus [N]	Modbus TCP/RTU	/connect/modbus/index List
Database [N]	External DB Polling	/connect/database/index List

The [N] next to each section label indicates the number of currently registered connections. The "View List" link on the right navigates to the category-specific list screen.

OPC List Screen (/connect/opc/index)

Access this screen via "View List" in the OPC row of the data source category or through the side menu. It provides a comprehensive overview of the operating status of all registered OPC server connections in a 12-column table.

Column	Width	Display
No.	60px	Row number
Connection ID	100px	OPC domain badge
OPC Name	250px	Display name
Status	70px	Full-color gradient status dot (Normal/Latency/Anomaly/Disconnected/Unknown)
Protocol Type	60px	Dark Badge — protocol-badge-opc-ua (Navy) / protocol-badge-opc-da (Purple). Black background + white text for immediate distinction from other column badges
Program ID | IP	Auto	ProgID or IP address of the OPC server
Start	60px	▶ Start Collection / ◼ Stop (displayed based on current status)
Collection Start Time	120px	Time when collection started (scan_start_time)
Connected Tag Count	70px	Number of tags mapped to that OPC
Total / Received Points	80px	Cumulative / Daily received point count
Error	60px	Cumulative error count (highlighted in red)
Action	80px	🔧 Edit / 🗑 Delete (operable only by roles with change permissions)

Use the ↻ icon button to the right of the table header to refresh. A help box at the bottom of the screen provides OPC connection recommendations (e.g., 1,000 tags or fewer per connection).

Add New Connection (/connect/{opc,plc,modbus,messaging,database,api}/add)

Clicking the Connect link on each card opens the registration form.

Six types use the «same form»

The registration forms for OPC, PLC, Modbus, Messaging, Database, and API are identical in terms of input items (all six screens share a single _connection-form-body.jsp in the product). Only the title, icon, save address, and the selectable protocol list (specific to that source type) differ.

Detailed settings per protocol — polling interval, authentication, topics, file paths, register addresses — are not in this form. This form is only for registering «which equipment is located where». Actual collection settings are configured in the Edge gateway or collector responsible for that protocol (protocols collected directly by the Platform are API and POSTGRESQL).

Input Items (Common)

Input	Required	Rule	Description
Site Name	✅	Select from list	Site to which this connection belongs
Connection ID	✅	Starts with OPC_, Uppercase, Numbers, _	Cannot be modified after registration (read-only in edit mode)
Source Type	—	Read-only	Determined by the selected protocol (OPC / PLC / MODBUS / DATABASE / MESSAGING / API / SYSTEM)
Connection Name	✅		Human-readable name
Protocol	✅	Select from list	Actual protocol — see table below
Edge	—	Read-only	Edge collecting this connection. If the protocol is collected directly by the Platform, it displays 「Platform collects directly」
Source IP	—	Max 255 chars, IP or Hostname	Address of the actual source (PLC, Device, OPC UA Server, DB, Broker)
Source Port	—	0 ~ 65535	Port of the actual source
Description	✅		Notes

Connection ID must start with OPC_

There is only one validation formula: ^OPC_[A-Z0-9_]+$. PLC_001, EDGE_00303, and DB_ERP will not be saved. The Edge self-monitoring connection is OPC_SYSTEM_<edge_id> and is declared directly by the Edge via synchronization — it is not created on this screen.

Input is automatically converted to uppercase, and disallowed characters are removed instantly.

Protocols and addresses for Edge-collected connections cannot be modified on screen

The Protocol, Source IP, and Source Port for connections collected by an Edge (where the Edge field is populated) are driven solely by Edge synchronization. They are read-only on the screen. If a protocol is collected by an Edge but the Edge is not yet recorded, an 「Edge Unconfirmed」 badge appears — this will be populated during the next Edge synchronization.

Protocols — Selectable Values (47 types)

The list is read from the mm_opc_protocol table, not hardcoded on the screen. The master version of that table is the Protocol Catalog in plantpulse-event (CI verifies the two). The following is the list based on the catalog. Source Type and Collection Entity (Edge / Platform) are determined by the protocol.

OPC (1)

Value	Description	Collection
OPCUA	OPC UA	Edge

PLC (33)

Value	Description	Collection
AB-ETH	Allen-Bradley AB-Ethernet (CSP/PCCC, PLC-5/SLC-500)	Edge
ADS	Beckhoff TwinCAT/ADS	Edge
BACNET	BACnet/IP (HVAC/building automation)	Edge
CANOPEN	CANopen (motion)	Edge
CCLINK_IE	Mitsubishi CC-Link IE Field	Edge
DALI	DALI (lighting)	Edge
DELTAV	Emerson DeltaV (DCS)	Edge
DNP3	DNP3 (power/utility)	Edge
EIP	Allen-Bradley EtherNet/IP	Edge
FATEK	FATEK FBs	Edge
FINS	OMRON FINS	Edge
FOCAS	Fanuc FOCAS (CNC)	Edge
GE	GE SRTP / PACSystems	Edge
HART	HART-IP (4-20mA + digital)	Edge
IEC104	IEC 60870-5-104 telecontrol	Edge
IEC61162_450	IEC 61162-450 shipboard ethernet (NMEA over UDP)	Edge
IEC61850	IEC 61850 MMS (substation)	Edge
IO_LINK	IO-Link (sensor master)	Edge
KEYENCE_KV	Keyence KV series PLC	Edge
KNXNET	KNXnet/IP (lighting/shading)	Edge
LOGIX	Allen-Bradley ControlLogix/CompactLogix	Edge
LS	LS ELECTRIC XGI/XBC/XBM	Edge
MBUS	M-Bus (metering)	Edge
MELSEC	Mitsubishi MELSEC	Edge
MEWTOCOL	Panasonic MEWTOCOL	Edge
MOTOR_SENSE	Motor Sense	Edge
MTCONNECT	MTConnect machine tool data	Edge
NMEA	NMEA 0183/2000 (marine)	Edge
OP	Atlas Copco Open Protocol (tightening)	Edge
PROFINET	Siemens PROFINET IO	Edge
S7	Siemens S7	Edge
SECSGEM	SECS/GEM (semiconductor fab)	Edge
SNMP	SNMP network device polling	Edge

Modbus (3)

Value	Description	Collection
MODBUS	Modbus TCP	Edge
MODBUSUDP	Modbus UDP	Edge
MODBUS_RTU	Modbus RTU (serial)	Edge

Database (1)

Value	Description	Collection
POSTGRESQL	PostgreSQL	Platform

Messaging (7)

Value	Description	Collection
COAP	CoAP (RFC 7252)	Edge
HTTP	HTTP push	Edge
KAFKA	Apache Kafka	Edge
MQTT_CLIENT	MQTT client	Edge
ROS2	ROS 2 (robot middleware)	Edge
SPARKPLUG_B	Sparkplug B (MQTT)	Edge
WEBSOCKET	WebSocket client	Edge

API (1)

Value	Description	Collection
API	PlantPulse REST API	Platform

System (1)

Value	Description	Collection
EDGE	PlantPulse Edge Gateway (self-monitor)	Edge

If you encounter a protocol not in the list

New protocols must first be registered in the protocol catalog of plantpulse-event, and the same code must be added to the platform seed (mm_opc_protocol) — CI verifies that the two match. However, appearing in the list does not guarantee collection — a driver capable of speaking that protocol must exist in the Edge gateway. First check the support status in the Edge Protocol Guide.

After Saving — Connected Tag List

A Connected Tag List panel is always located below the form. However, the list is only populated in edit mode — it is normal for it to be empty in the new registration screen.

Column	Display
Selection · Tag ID · Tag Name · Data Type · Unit · Description · Action	Tags mapped to this connection

Panel header tools — Select All, Delete Selected, Add Virtual Tag, Refresh. The [Virtual Tag] button registers a virtual tag for this connection — a tag that calculates values based on other tags.

Registration alone only captures the metadata. Check the Status Screen to verify if actual data is arriving — once collection starts, a "Connected" badge will appear on the card.

---

Status Screen (/connect/status)

Monitor the status of all active data source connections from a single screen.

Top Tools

📡 연결 상태  [총 N 개의 데이터소스 연결]                  [사이트 ▼] [검색] [↻]

Control	Width	Description
Site Selector (site_id)	200px	List of registered sites (사이트명 [설명]). One is always selected
Search	Red + 🔍	Updates cards after applying site filter
Refresh	Red + ↻	Refreshes the screen

Left — Statistics Charts and History

Five charts and three history panels are arranged vertically in the left col-lg-2 area.

1) Connection Status Distribution (connection_stat_chart, 200px)

Displays the distribution of the five status levels (Connected, Connection Latency, Connection Anomaly, Disconnected, Unobserved) for all currently registered connections as a donut chart.

2) Communication Connection Status Trend [Today] (connection_trend_chart, 150px)

Trend of the number of connections by status per time slot (last 24 hours).

Color	Meaning	Threshold
🟢 Green	Connected	Data received within 10 min
🟠 Orange	Connection Latency	No data received for 10 min or more
🔴 Red	Connection Anomaly	No data received for 1 hour or more
🟥 Dark Red	Disconnected	No data received for 24 hours or more
⬜ Grey	Unobserved	No data reception history

ℹ️ Hovering over the information icon in the header displays these five levels as a tooltip.

3) Communication Latency Status Trend [Today] (latency_trend_chart, 150px)

Color	Meaning	Threshold (Max latency in interval)
🟢 Green	Normal	Under 10s
🟠 Orange	Latency	10s ~ 60s
🔴 Red	Critical Latency	60s or more

The ⓘ tooltip for this chart shows different numbers

The tooltip says "Average latency under 1s / 1~10s / 10s or more", but the bar calculation is based on the maximum latency (max_latency) of 10s and 60s for that time interval. Use the table above when reading the bars.

This is why a connection with an average latency of 3s appears green in this chart. The average-based 1s/10s thresholds are separate criteria used for determining asset Health Status — both criteria are listed side-by-side in Status Code Definitions.

4) Point Verification Failure Trend [Today] (point_fail_trend_chart, 150px)

Aggregates the number of received data points that failed type, range, or validity verification on an hourly basis.

5) Recent Disconnections [Last 24 Hours] (connection_status_history, 200px scroll)

History of data sources that were disconnected over the last 24 hours. Listed in reverse chronological order — data source ID, disconnection time, and last normal time.

6) Recent Reception Latency [Last 24 Hours] (connection_latency_history, 200px scroll)

History of data sources that experienced response latency over the last 24 hours.

7) Recent Point Verification Failures [Last 24 Hours] (point_validation_status_history, 400px scroll)

History of points that failed verification over the last 24 hours.

Right — Data Source Card Grid

Data source cards are displayed in a grid by category in the right col-lg-10 area.

Card Categories (Top to Bottom)

Section Header	Display
Edge Gateway / File / API [N]	FILE type data sources (Edge GW, Files, APIs, etc.)
PLC [N]	PLC data sources
(Others: OPC, Modbus, External DB, etc.)	By registered data source type

Card Configuration (opc_obj)

┌─────────────────────┐
│ [SUB_TYPE]           │ ← 작은 글씨
│  OPC_ID              │ ← ID
│  ────────────────    │
│  현재 상태값(_mm)     │ ← 매분 갱신 상태 표시
└─────────────────────┘

Area	Display
Top	Data source subtype (e.g., FILE, MQTT, REST_API)
Middle	Data source ID — uses ellipsis (...) if truncated
Bottom	Per-minute status display (${opc_id}_mm) — colors mapped to the 5 status levels

Clicking a card navigates to the data source detail screen (/connect/view?opc_id=...) to verify collection history, tag lists, and logs. Hovering displays the card's description as a tooltip.

Empty State Guidance

If no data sources are registered in a category:

No connected agents

---

Data Source Detail Screen (/connect/view)

Access this screen by clicking a data source card on the Status Screen. This view aggregates all operating information for a single OPC/PLC/DB connection.

Page Header

📶 프로토콜 연결 보기                  [📅 날짜 선택 ▼] [날짜 이동 →] [← 목록] [↻]
   {site_name} / {opc_name}

Control	Action
Date Selection	Calendar — view connection status for other dates
Move Date →	Reload for the selected date
← List	Return to the status screen
↻	Refresh screen

Left ① Connection Basic Information + Expand

Two buttons on the right of the panel header:

Button	Action
⌄ Expand (viewOPCDetail())	Toggles display of the site information section
⚙ Connection Settings	Navigates to the edit form for that data source (requires change permissions)

Basic Information (ds-dl)

Item	Display
Connection ID	OPC domain badge
Connection Name	Data source display name
Description	Notes
Registration Date	Registration time (monospace)

Protocol Connection Information (ds-dl)

Item	Display
Connection Type	OPC_UA / OPC_DA / PLC / MODBUS / DB / FILE, etc.
Subtype	Manufacturer and detailed protocol (e.g., SIEMENS_S7, MITSUBISHI_MC)
Agent IP / Port	IP and port of the agent (Edge) (monospace)

Site Information (only when expanded)

Item	Display
Site ID	Site domain badge
Site Name	Site display name

Left ② Connection Statistics (Latency/Status 5 Types)

Today's Max Latency Trend (3 Slots)

Slot	Display
Min	Fastest response latency (ms, comma separated)
Avg	Average response latency
Max	Slowest response latency

A 24-hour latency trend line chart (latency_24hh) is shown below. If unusual spikes are present, verify the specific time on the Status screen.

Connection Anomaly Count

Displays today's cumulative "Connection Anomaly" count in a read-only input field.

Status Statistics 5-Cell Grid

┌─🟢 연결─┐ ┌─🟠 지연─┐ ┌─🔴 이상─┐ ┌─⬛ 끊김─┐ ┌─⚪ 미관측┐
│  12,453│ │    23  │ │    5   │ │    1   │ │    0   │
└────────┘ └────────┘ └────────┘ └────────┘ └────────┘

Each of the five colored cells displays a cumulative count in a large font, accompanied by a small donut chart (connection_priority_count_chart) below.

Right ① Connection Status Timeline + LIVE Dot

Panel header auxiliary text: "Today's Connection/Disconnection Timeline [{status_txt}]". An ⓘ information icon is on the right of the header — displays a guide tooltip on hover.

Left — Current Status Card (live)

A status card (last_connection_status) consisting of a large icon and label.

Icon + Label	Meaning	Dot Toggle
❓ Unobserved (is-mute)	No data reception history	⚪ Grey
🟢 Connected (is-ok)	Data received within 10 min	🟢 LIVE Dot (Pulse)
🟠 Connection Latency (is-warn)	No data received for 10 min to 1 hour	🟠
🔴 Connection Anomaly (is-err)	No data received for 1 to 24 hours	🔴
⬛ Disconnected (is-disc)	No data received for 24 hours or more	⬛

If the 🟢 LIVE dot flashes as a pulse, data is arriving in real-time. Hovering displays the last reception time as a tooltip.

Right — 24-Hour Timeline Bar (opc_connection_timeline)

Displays 24 hours as a horizontal bar, with each time slot colored by one of the five connection statuses. Hovering over the bar displays the status for that time as a tooltip.

Right ② 24-Hour Point Reception Chart

Panel header auxiliary: "Today's 24-hour points received per minute".

A line chart (opc_point_trend_24h) showing the number of points received per minute. A sharp drop compared to normal operating hours indicates a disconnection in data inflow. "Loading..." is displayed in the center during data retrieval.

Right ③ Connected Tag List

A real-time value list (7 columns) of tags mapped to this data source.

Column	Width	Display
Tag ID	80px	Domain badge
Tag Name	350px	Tag display name
Data Type	100px	INT/FLOAT/STRING/BOOL, etc.
Current Value	Auto	Last received value (quality color badge)
Last Update Time	Auto	Reception time
Latency [MS]	Auto	Average response latency
Action	50px	🔍 → Navigates to the Tag Detail screen

The table is updated in real-time via WebSocket. If a value stops blinking, reception for that tag has been disconnected.

---

Edge Screen (/edge/index)

Monitor the system status and PLC collection statistics of Edge devices installed in the field from a single screen. The page subtitle is "Real-time monitoring of Edge connection status and PLC data collection status."

Number	Position	Function
①	Top Right	Site Selector and Search
②	Top Panel	Edge Reliability Summary — 6 cards (below)
③	Single Card	Large number + label + one-line description
④	List Header	Count and Last Query Time
⑤	Table Header	8 columns
⑥	First Row	Single Edge device
⑦	Throughput Cell	Current speed (mps) · Cumulative points · 24-hour sparkline
⑧	Action Cell	Detail · Refresh · Power · Log · Settings · View Reliability

Edge Reliability Summary — 6 Cards

The panel subtitle is 「Monitor connection, PLC, latency, and resource status at a glance」. The first three count Edge devices, and the last three count PLCs — the units differ, so it is normal for the sum not to align.

Card	Count Target	Description
Total	Edge	Edges subject to monitoring
Connected	Edge	Edges reachable by the Platform
Disconnected	Edge	Edges unreachable by the Platform · Unobserved
PLC Normal	PLC	Number of PLCs with normal connection and collection
PLC Collection Stopped	PLC	Number of PLCs connected but not collecting
PLC Disconnected	PLC	Number of disconnected PLCs — Immediate Action Required

View Reliability — Single Edge Diagnosis

Clicking View Reliability in the Action cell (⑧) opens a drawer from the right. It contains a Reliability grade and a list of Diagnostic Items.

Diagnostic Item	When it appears
Disconnected PLC Count	When one or more PLCs are disconnected — 🔴
(Collection Stopped)	When PLCs are connected but inflow is 0 — 🟡
Unreachable Edge Count	When connection is lost (🔴) or never observed (🟡)
System Error	When the count of errors in the log is greater than 0 — 🟡
System Resource	When any of CPU, Memory, or Disk is 90% or higher — 🟡
No Anomalies	When none of the above are present — 🟢

Reliability «Grade» is determined by the PLC axis only

The grade (healthy / warning / critical) is determined solely by PLC connection and collection.

Disconnections, system errors, and resources exceeding 90% are «only shown» as diagnostic items and do not change the grade. This may result in combinations such as 「Disconnected but reliability is not critical» — this is a design choice to separate axes, not a bug. Read the diagnostic items along with the grade.

「Unobserved」 is not a failure, but a state where the device has never been reported. It is a target to verify if registration was done correctly, rather than for immediate corrective action.

Latency is not in this drawer

A latency diagnostic item existed previously but has been removed. The official source for latency anomalies is the Today's Max Latency Trend in the Data Source Detail Screen.

Top Tools

📡 엣지                                        [사이트 ▼] [검색] [↻]

Control	Width	Description
Site Selector (site_id)	200px	Registered sites. One is always selected
Search	🔍	Applies site filter
Refresh	↻	Immediately re-queries the list

The list is automatically re-queried every 60 seconds. The "every 10 seconds" mentioned in the help box refers to the interval at which the Edge uploads its status to the server, not the screen refresh interval — these are easily confused. Click ↻ to see the most recent values immediately.

List Table (8 Columns)

Related metrics are grouped into a single column. CPU, Memory, and Disk no longer occupy individual columns.

┌────────────────────────── 목록 ──────────────────────────┐
│ 연결 │ EDGE_ID │ 엣지 │ 리소스 │ 네트워크 │ PLC │ 처리량 │ 액션 │
└──────────────────────────────────────────────────────────┘

Column	Width	Display
Connection	60px	Connection status icon badge (🔌 Disconnected / ⚠ Warning)
EDGE_ID	130px	Edge device identifier
Edge	260px	Edge name (+ O/S hostname, version)
Resource	150px	CPU, Memory, and Disk usage in one cell
Network	110px	Status of NET 1, NET 2, WiFi, and VPN in one cell
PLC	80px	Count of Normal Connections / Disconnections
Throughput	110px	Current collection speed (mps) · Σ Cumulative received points + Last 24-hour hourly reception sparkline
Action	110px	View Details, etc.

In the throughput cell sparkline, empty intervals mean «No Observation», not «0 points received». This same explanation appears as a tooltip when hovering over the cell.

Edge Help Box

The following operating guide is displayed at the bottom of the page (4 items).

❓ Edge Help You can check the connection and PLC data collection status of the Edge in the Edge menu.

• For Edges displayed as Disconnected [🔌], you must check the physical environment, network, and Edge O/S.
• For Edges displayed as Warning [⚠], S/W errors exist during collection; connect to the Edge to resolve the issue.
• When CPU/Memory/Disk usage is 80% or higher, check the Edge and clear resources.
• Edge status is updated every 10 seconds.

Operating Procedures (When Anomalies are Found)

1. Edge is 🔌 (Disconnected) → Field inspection (Power, Network, Hardware)
2. CPU/Memory/Disk 80% or higher → Connect to Edge and clear unnecessary processes/logs
3. PLC Disconnected count is not 0 → Inspect PLC cables and settings for that Edge

---

Edge Detail Screen (/edge/view)

The detail screen for a single Edge, accessed by clicking the EDGE_ID or "Action" column in the Edge list. This screen allows for the following:

• Verification of registration metadata, host, network, and security keys
• Real-time CPU, Memory, and Disk gauges
• 8 PLC collection statistics metrics
• List of OPC servers connected to the Edge and Start/Stop collection
• List of Docker containers running on the Edge with Start, Stop, Restart, Log, and Delete functions
• Remote deployment of new containers
• Restart of Edge applications and reboot of the Edge host OS

⚠️ All control commands on this screen are executed directly on the field Edge device. For Edges in active service, OPC collection will be interrupted during collection stops, container deletions, or system reboots. Perform these actions only during maintenance windows.

Top Page Header and Refresh

🛜 ${엣지명}                    [← 목록] [⚡ 실시간 새로고침] [↻ 새로고침]
   사이트: ${site_id} · 엣지 ID: ${edge_id} · ${설명}

Control	Action
← List	Return to /edge/index
⚡ Real-time Refresh	Directly calls the Edge equipment to update gauges, OPC lists, and Docker lists with the latest values
↻ Refresh	Refreshes the entire page

Gauge, OPC, and Docker panels do not self-refresh

Only two things on this screen refresh automatically.

Target	Interval	Source
Left info panels, PLC statistics, etc.	30s	Read-model (/edge/{id}/model) stored in the Platform — values uploaded by Edge via ~60s heartbeat
Upgrade availability check	5m	—

System resource gauges, OPC lists, and Docker container lists call the Edge directly only once upon entering the screen. After that, they are only updated when ⚡ Real-time Refresh is clicked. This is designed to avoid polling the equipment every second.

If the screen is left open for a long time, the gauges show values from the time of entry. Always click ⚡ to verify results after taking action in the field.

Connection / Health Timeline Tabs

The statistics area is divided into two tabs.

Tab	Content
Connection Status Timeline (Default)	Reachability over the last 24 hours
Health Status Timeline	PLC connection & collection over the last 24 hours

The Health timeline is drawn when the tab is selected and becomes visible. It is normal for it to be empty before the tab is opened.

Left — Basic Info, Host, Network, Security 4 Panels

Four panels are stacked vertically in the left col-lg-3 area. All are in definition list (label / value) format.

① Basic Information — Including System Reboot Button

Item	Meaning
Edge ID	Domain ID badge (Edge domain color)
Name	edge_name
Site	Site ID (domain badge)
Role	role (or - if none)
Status	status value from the master table
Description	Notes
Registration Date	Date and time when the Edge was first registered
Recent Status	Date and time of the last received heartbeat

A 🔴 red ⏻ power icon button is located on the right of the panel header — clicking this reboots the Edge host OS (refer to Safe Procedures below).

② Host

Item	Meaning
Hostname	Operating system hostname
Version	Edge software build version
Build Date	Date the software was built
CPU Cores	Number of cores
Threads	Number of threads
Temperature	CPU temperature (°C) — 0 if no temperature sensor is present on the board

③ Network

IPs for six interfaces: VPN, NET 1, NET 2, WiFi, Management, and GSM. Displays - if not configured.

Item	Purpose
VPN IP	Edge-side address of the headquarters ↔ field VPN tunnel
NET 1	Primary LAN
NET 2	Secondary LAN
WiFi	Wireless
Management	OOB management network
GSM	LTE/3G backup line

④ Security

Item	Display
API Key	Key used by the Edge to authenticate with the server — masked as first 4 chars + **** + last 4 chars

This is the same key as the Flow REST node X-API-Key — only the masked format is visible on this screen; the actual key value is not displayed.

Right ① System Resource Gauge + App Restart

The panel header contains the ⓘ "CPU · Memory · Disk Usage (Real-time)" label, and an App Restart button on the right.

Status Line (state-row)

A one-line status message is displayed above the gauges.

Display	Meaning
🟢 엣지 LIVE — 정상 응답 중	Edge responds to ping
🔴 엣지 OFFLINE	Edge's /api/v1/monitoring is ping=false
🔴 엣지 UNREACHABLE	HTTP request itself failed (network disconnection)

3 Gauges (140px donuts each)

Gauge	Unit	Color Threshold
CPU Usage	%	< 80 Green · 80~89 Orange · ≥ 90 Red
Memory Usage	%	Same
Disk Usage	%	Same

Values are displayed to one decimal place (e.g., 73.4%).

App Restart Button

Restarts only the Edge application (daemon). Does not affect the host OS.

🔄 Clicking this opens a confirmation dialog → "Restart" → The Edge process restarts itself after about 3 seconds and returns after about 10 seconds. During this time, gauges and statistics temporarily display -.

Right ② PLC / Collection Statistics (8-slot stat-box)

Eight statistics boxes are arranged in a grid.

Box	Unit	Meaning	Highlight
Normal Connection	Count	Number of alive PLC connections	🟢 ok
Disconnected	Count	Number of disconnected PLCs	🔴 err
Read Success	Count	Cumulative counter for successful PLC polling	-
Read Failure	Count	Cumulative counter for failed PLC polling	🔴 err
Transmitted Points	Count	Cumulative number of points sent to the server	-
MPS	Count/Sec	Message processing speed (points per second)	-
Avg Latency	MS	Average response latency of the recent window	-
Max Latency	MS	Maximum response latency of the recent window	-

Counters (Read Success, Read Failure, Transmitted Points) reset to 0 when the Edge process restarts. Interpret these as trends, not absolute values.

Right ③ OPC Status + 5 Summary Chips + Start/Stop Collection

The panel header says "List of OPC servers connected to the Edge and collection status".

5 Summary Chips (opc-chip-v2)

Each chip consists of an icon, a large number, and a label.

Chip	Icon	Meaning	Color
Registered	☰	Total number of OPC servers mapped to this Edge	Grey
Connected	✓	Number of connection_status = CONNECTED	🟢 Green
Collecting	≋	Normal Connection + scan_status = START	🟢 Green
Stopped	⏸	Number of scan_status = STOP	Grey
Disconnected	🔗∕	Number of connection_status ≠ CONNECTED	🔴 Red

List Table (7 Columns)

Column	Width	Display
OPC ID	160px	🔌 + ID (Click to open /connect/opc/edit/{id} edit screen)
Name	Auto	opc_name
Type	80px	OPC UA / OPC DA badge
Agent IP	140px	OPC Agent IP (monospace)
Connection	90px	🟢 CONNECTED / 🔴 Other — displayed as dot
Collection	90px	🟢 START / 🟡 Other / ⚫ STOP — dot
Control	160px	Action buttons (below)

Control Buttons

Status Condition	Displayed Button	Action
scan_status ≠ START	🟢 ▶ Start Collection	Confirm → POST /edge/{edge_id}/opc/{opc_id}/start → Screen reloads after 2s
scan_status = START	🔴 ◼ Stop Collection	Confirm → POST /edge/{edge_id}/opc/{opc_id}/stop → Screen reloads after 2s
Always Displayed	⚙ Edit OPC	Move to /connect/opc/edit/{opc_id} edit screen

The "Stop Collection" dialog is displayed in warning color (orange) — it actually interrupts the data flow.

Right ④ Docker Containers (Remote Deploy, Start, Stop, Log, Delete)

Refreshes the list of containers running in the Edge host's Docker every 5 seconds.

Panel Header

Button	Action
↻	Immediate refresh
➕ New Deploy	Container deployment dialog (input name, image, port, and environment variables)

List Table (6 Columns)

Column	Width	Display
Name	160px	▢ Cube icon + Container name (Bold)
Image	Auto	Image tag (monospace, e.g., grafana/grafana:latest)
Status	80px	🟢 UP / 🔴 DOWN chip
Recent Status	200px	docker status text (e.g., Up 3 hours)
Port	200px	호스트:컨테이너/프로토콜 comma separated
Control	240px	5 types of action buttons (below)

Control Buttons (Common for all rows)

Button	Color	Action
▶ Start	🟢 Green	POST /app/{name}/start
🔄 Restart	🟡 Orange	POST /app/{name}/restart
◼ Stop	🔴 Red	POST /app/{name}/stop (Warning dialog)
📄 Log	Grey	GET /app/{name}/logs → Displays container standard output in a wide dialog
🗑 Delete	Red Text	DELETE /app/{name} (Danger dialog) — force terminates even if running

New Deployment Dialog

Input	Example
Container Name	grafana
Image	grafana/grafana:latest
Port (host:container, comma separated)	3000:3000
Environment Variable (KEY=VAL, comma separated)	GF_SECURITY_ADMIN_PASSWORD=admin

Deployment is performed by the Docker daemon on the Edge host, which executes image pull + run. Large images may take time; use the list refresh to track progress.

Safe Procedures for System Reboot and App Restart

🔄 App Restart (Edge Application only)

1. Click App Restart at the top right of the System Resource panel.
2. Confirmation dialog → "Restart".
3. The process restarts itself after about 3 seconds.
4. Returns after about 10 seconds — gauges and statistics automatically refill.

Impact: PLC/OPC collection is interrupted for about 10~15 seconds. CEP alarm evaluation continues on the server. Cumulative counters reset to 0.

⏻ System Reboot (Edge Host OS)

Use the 🔴 ⏻ button in the header of the Left ① Basic Information panel.

1. Confirmation dialog is displayed as Danger (Red).
2. There will be no response for about 1 minute; it returns only after the OS has fully booted.
3. All PLC/OPC connections are lost during boot — containers also stop and restart.

Use only in the following cases: ① When memory/disk is 100% full and App Restart does not recover the system. ② When the board itself becomes slow to respond. Generally, try App Restart first.

---

Usage Scenarios

Scenario	Screen	Procedure
Register OPC for new line	Protocol → OPC Card → Connect	Enter Site, OPC ID, Server Address → Save
Bulk check of disconnected links during operation	Status	Left "Recent Disconnections" 24h history → Identify Red/Dark Red cards on the right
Analyze cause of point verification failure	Status	Left "Point Verification Failure Trend" + "Recent Verification Failures" → Asset ID + Time → Compare with trend screen
Check Edge device resources	Edge	Identify devices with CPU/Memory/Disk ≥ 80% → Field cleanup
Identify sites with PLC disconnections	Edge	Sort "PLC Disconnected" column → Inspect Edges in sites with non-zero values
Analyze network latency	Edge	Sort "Max Latency [MS]" → Inspect network for devices ≥ 10s
Restart Grafana/Integration container on Edge	Edge Detail → Docker	Click 🔄 Restart in the container row (no need for full screen refresh)
Temporarily pause field OPC for inspection	Edge Detail → OPC	Click ◼ Stop Collection in the OPC row → After inspection, click ▶ Start Collection
Recover slow Edge response	Edge Detail → System Resource	App Restart (10s impact). If not recovered, ⏻ System Reboot (1min impact)
Remotely deploy new monitoring tool	Edge Detail → Docker → ➕ New Deploy	Enter Image, Port, Env Var and deploy — Image pull is automatic

---

Frequently Asked Questions

Q. I registered an OPC data source, but the card is not visible on the [Status] screen. A. Immediately after registration, the card should appear as "Unobserved" (Grey). If not visible, verify that you have selected the site where the OPC is registered in the site selector.

Q. The trend charts in [Status] are empty. A. This happens if there are no data sources in that site or if there has been no data inflow today. If you just registered a data source, wait a moment for the first inflow.

Q. The tooltip for the information icon ℹ on the chart appears cut off. A. Hovering over the information icon displays the 5-level status criteria table. If the screen width is narrow, it may be cut off; widen the screen or refer to the Status Code Definitions screen.

Q. Edge status is not updating. A. There are three different intervals, which can be confusing. ① Edge uploads status to server: 10s, ② List screen re-queries server: 60s, ③ Detail screen saved value refresh: 30s. It is normal for values in the list to appear up to a minute late. If it remains stopped longer than that, the Edge is unable to send a response (Disconnected). Perform a field inspection or check the EDGE application logs in Diagnostics.

Q. The CPU gauge on the detail screen stays at the same value. A. Gauges, OPC lists, and Docker lists do not refresh automatically — they call the Edge once upon entering the screen. Please click ⚡ Real-time Refresh.

Q. The PLC Disconnected column increased to 1; how do I check it? A. Use the action button for that Edge to enter the detail screen, where you can see the status by PLC. Alternatively, identify the red card in the PLC card grid on the Status screen.

Q. There is an Edge with 100% CPU/Memory. A. Connect to the field immediately to clear unnecessary processes. If this recurs, consider upgrading the device specifications or adjusting the collection interval.

Q. Clicking a card leads to a blank screen. A. You are navigating to the data source detail screen (/connect/view), but if there is no incoming data, it may appear blank. Rich information is only displayed for data sources with a history of data inflow.

Q. Is it updated automatically in real-time? A. The per-minute display (_mm) of cards on the [Status] screen is automatically updated. The statistics charts on the left are refreshed at set intervals; to reflect changes immediately, click the ↻ refresh button at the top right.

Q. "Points received count" suddenly becomes 0. A. When the Edge counter restarts, it begins again from 0. To determine if it is a true zero or a counter reset, cross-check the data count by site on the Daily Statistics screen.

Q. I stopped OPC collection in the Edge detail screen (/edge/view), but it returns to START after some time. A. There is no 「Auto Restart」 option. The cause is one of the following:

1. The Edge collector was restarted — If 「Automatically start collection」 (auto_collect) is enabled for the connection, the collector sets that OPC to START at startup. Even if you stop it on the screen, it will return to START on the next restart. This item only operates at the time of startup and does not revive a stopped OPC via a timer — the «after some time» is actually a restart. This is toggled in the checkbox on the Edge Add/Edit Connection screen.
2. A start command was received from outside — Anyone can turn on collection via POST /api/v1/opc/{opcId}/start (nothing happens if it is already START). Suspect integration scripts or upstream systems.

For a permanent stop, either disable 「Automatically start collection」 or deactivate the OPC entirely — stopping it once on the screen is not sufficient.

Q. The Docker container panel is empty. A. ① The Edge may not be in Docker mode — some Edges use direct systemd startup. ② The Docker daemon on the Edge OS may not be responding (in this case, ↻ refresh will still be empty). Perform a field inspection or consider a ⏻ system reboot.

Q. The ▶ Start, 🔄 Restart, and ◼ Stop buttons for containers are all visible. Which one is active? A. All buttons are always clickable — commands are sent regardless of the Docker status. If you click ▶ Start while it is already running, it may be ignored or restarted without an error. Check the status chip (🟢 UP / 🔴 DOWN) and select the intended command.

Q. What is the difference between ⏻ System Reboot and 🔄 App Restart? A. ① App Restart (10s impact) — Restarts only the Edge daemon process; OPC/PLC collection is interrupted for 10s. ② System Reboot (1min impact) — Boots the entire Edge host OS; restarts Docker containers. Always attempt App Restart first.

Q. The API Key is masked; how do I see the actual value? A. Masking is intentionally applied — the plain key is not visible anywhere on the screen. It is the same key as the X-API-Key in the Flow REST node; please keep it in a secure location upon initial issuance. Request a reissue from the operator if lost.

---

Related Screens

• Dashboard — Connection rates on site maps and KPI cards
• Daily Statistics — Comparative analysis by site, OPC, and tag
• Data Point — Verify incoming data via charts
• Factory Management — Registration of sites and asset trees
• Diagnostics — Diagnostic logs for Edge and server modules
• Status Code Definitions — 5-level connection status and color mapping