Dashboard (Platform Summary / Site Map)
Table of Contents
- Overview
- Screen Layout
- Page Header
- Global Site Map
- Data Pipeline Cards
- Site Scale and Connection Status Summary
- Right Health Rail
- Platform Key Metrics
- Bottom Operations Widgets
- Key Drilldowns
- Response by Abnormal Signal
- Frequently Asked Questions
- Related Screens
Overview
The dashboard is the operations home screen you see first after logging in. It appears in the left menu as OVERVIEW > Dashboard, and its internal URL is /map/index.
This screen gathers the site map, data pipeline, infrastructure health, cluster status, and key KPIs into a single view so operators can quickly answer the following questions:
- Which site or line has produced an abnormal signal?
- Is the collection, ingest, processing, and storage pipeline blocked anywhere?
- Are the cache, WS, MQTT, Kafka, event DB, and time series engine healthy?
- Are today's collection volume, alarms, equipment operating rate, and OEE within normal ranges?
The first screen that older documents called "Summary" is now organized as Dashboard in the current UI. The URL remains
/map/indexas before.
Screen Layout
┌────────────────────────────────────────────────────────────────────┐
│ 상단 바: 메뉴 토글 / 도메인 검색 / LIVE / 알람 / 전체화면 / 설정 / 매뉴얼 / 사용자 │
├────────────────────────────────────────────────────────────────────┤
│ 한국핵심산업 │
│ 플랫폼 요약 - 사이트별 운영·성능 통합 모니터링 │
├──────────────────────────────────────────────────────────┬─────────┤
│ 글로벌 사이트 맵 │ 우측 │
│ ┌ 데이터 파이프라인: 수집 → 수신 → 처리 → 버퍼 → 저장 ┐ │ 헬스 │
│ │ 사이트 마커 / 지도 확대·축소 / 좌표 표시 │ │ 레일 │
│ │ 사이트·구역·라인·설비·태그 카운트 │ │ │
│ │ 연결 상태 칩: 정상·지연·이상·끊김·안됨 │ │ │
│ └────────────────────────────────────────────────────┘ │ │
├────────────────────────────────────────────────────────────────────┤
│ 플랫폼 핵심 지표: 통신 연결률 / 금일 수집 / 금일 알람 / 가동률 / 가용률 / OEE │
├────────────────────────────────────────────────────────────────────┤
│ 하단 위젯: 사이트 목록 / 포인트·알람 / OPC / 설비 / 생산 / 엣지 / 플로우 / 진단 │
└────────────────────────────────────────────────────────────────────┘
| Area | Contents |
|---|---|
| Page header | Company name, "Platform Summary - Integrated Operations and Performance Monitoring by Site" description |
| Global site map | Site locations, marker status, map controls, coordinate display |
| Data pipeline | Throughput and status for the collection, ingest, processing, buffer, and storage stages |
| Site scale summary | Counts of sites, areas, lines, equipment, and tags |
| Connection status summary | Counts for Connected, Connection Delayed, Connection Error, Disconnected, and Not Connected |
| Right health rail | Platform health timeline, system performance, cluster status, infrastructure/engine status |
| Key KPIs | Communication connection rate, today's collection, today's alarms, equipment operating rate, equipment availability, overall OEE |
| Bottom operations widgets | Site list, point and alarm trends, OPC/equipment status, production schedule and work orders, Edge/flow/diagnostics |
Page Header
The current operating organization or site group name is displayed prominently at the top of the body.
| Item | Description |
|---|---|
| Company name | Example: 한국핵심산업 |
| Subtitle | 플랫폼 요약 - 사이트별 운영·성능 통합 모니터링 |
| Real-time notifications | Equipment status changes, diagnostic events, and similar appear as toasts in the upper right |
For how to use global search and notifications at the top, see Console Navigation and Common Screens.
Global Site Map
The map shows registered site locations and their operating status at the same time. Site markers appear as factory icons, and the marker label shows the site ID or short name.
Map Controls
| Action | Method |
|---|---|
| Zoom in/out | + / - buttons on the left of the map, or the mouse wheel |
| Pan | Drag the map |
| Check a site | Click the site marker |
| Check coordinates | Latitude/longitude display at the bottom of the map |
Reading Markers
| Status | Meaning | What to check next |
|---|---|---|
| Normal | The site's main connections and data ingest are normal | Just check KPIs and collection volume |
| Warning | Some connection delays or equipment warnings | Connection Status, Alarms |
| Error | Possible connection errors, critical alarms, or a sharp drop in data | Diagnostics, Edge Gateway |
| Unknown | Coordinates or collection history are missing | Factory Management, Data Points |
Data Pipeline Cards
Above the map, the platform's data processing flow is shown as a set of cards.
수집 ─→ 수신 ─→ 처리 ─→ 버퍼 ─→ 저장
| Stage | Representative metric | Normal interpretation |
|---|---|---|
| Collection | Hz | Whether the field collection loop is alive |
| Ingest | PPS | Points per second received by the server |
| Processing | Worker count | Whether pipeline workers are running normally |
| Buffer | Waiting queue | Whether the queue is backing up |
| Storage | Stored records | Whether time series and event storage keeps accumulating |
The small sparkline at the bottom of each card shows the recent trend. If a value drops to 0 or only the buffer keeps growing, suspect a bottleneck in data ingest or storage.
Site Scale and Connection Status Summary
The lower left of the map summarizes the current model scale and connection status.
Model Scale
| Item | Meaning |
|---|---|
| Sites | Number of registered factories or business sites |
| Areas | Number of operating areas under a site |
| Lines | Number of production lines |
| Equipment | Number of registered equipment |
| Tags | Number of collection, calculation, and status tags |
If the model scale differs from what you expect, check the registration status of sites, assets, and tags in Factory Management.
Connection Status Chips
| Chip | Meaning | Priority |
|---|---|---|
| Connected | Recent data reception is normal | Reference |
| Connection Delayed | Reception delay occurring | Check the trend for the day |
| Connection Error | No reception beyond the threshold time, or errors | Inspect immediately |
| Disconnected | No reception for an extended period | Check the field, Edge, and network |
| Not Connected | No reception history yet | Check registration and commissioning status |
Exact status criteria follow Status Code Definitions.
Right Health Rail
The right rail of the dashboard gives a quick view of the platform's own health. Operators use it to distinguish site issues from system issues.
Platform Health Timeline
| Item | Description |
|---|---|
| Latest time | Time of the last aggregation |
| Color timeline | Normal, warning, and error status by time slot |
| Purpose | Check whether system status wavered during a particular time slot |
If orange or red segments cluster on the timeline, check the Diagnostics logs and System logs for the same time slot.
System Performance
| Gauge | Meaning | Inspection criteria |
|---|---|---|
| CPU load | Server CPU utilization | If it stays above 80% for a long time, identify the load source |
| Memory usage | JVM/system memory utilization | A steady rise indicates memory pressure |
| HDD usage | Data storage utilization | Above 85%, consider cleanup or expansion |
Cluster Status
| Item | Meaning |
|---|---|
| Status | Cluster node roles and whether they are healthy |
| Mode | Operating mode such as single, master, or worker |
| Read/write latency | Storage response latency |
| CPU / Memory / Data | Cluster resource usage |
| Last update | Time the cluster status was aggregated |
Infrastructure and Engine Status
| Area | Items |
|---|---|
| Infrastructure | Cache, WS, MQTT, Kafka, event DB, time series |
| Engine | Real-time metrics for collection, processing, latency, and storage |
If even one infrastructure item is abnormal, the problem is more likely platform-wide than site-specific. Check System and Diagnostics first.
Platform Key Metrics
Six KPI cards needed for operational judgment appear at the bottom of the dashboard.
| KPI | Meaning | What to check after clicking |
|---|---|---|
| Communication connection rate | Normal connections / total connections | Connection Status |
| Today's collection | Number of data points collected today | Data Points, Daily Statistics |
| Today's alarms | Total number of alarms raised today | Alarms |
| Equipment operating rate | Percentage of equipment with normal data ingest | Equipment, Connection Status |
| Equipment availability | Percentage of equipment with normal health diagnostics | Equipment, Diagnostics |
| Overall OEE | Overall equipment effectiveness across all equipment | Production Management, ISO Analysis |
A KPI card is not just a single number. When a value falls outside its usual range, drill into the card's related screen to narrow down which site, line, equipment, or tag is the cause.
Bottom Operations Widgets
Below the map and KPIs, a series of widgets shows the day's operating flow across the entire platform, not just the selected site.
| Widget | Display | Navigation |
|---|---|---|
| Site list | Connection status, health status, site ID/name, 24-hour data trend, today's data and alarms | Click a site name to open the asset tree |
| Data points and alarms | Point reception and alarm trends over the last 24 hours | Trends, Alarms |
| Alarm statistics | Today's alarm total, distribution by priority and ON/OFF | Alarm Visualization Analysis |
| OPC trends | Communication connection status, communication latency status | Connection Status |
| Equipment status | Equipment connection heatmap, equipment health heatmap | Assets, Equipment |
| Production information | Today's shift schedule, today's work orders, OEE trend and comparison | Production Management, ISO Analysis |
| Edge | Edge health by hour, Edge API calls, Edge push reception, Edge status distribution | Edge |
| Flow | Top 5 calls, top 5 errors, hourly execution trend | Flow |
| Diagnostics sidebar | Edge heatmap, flow health heatmap, diagnostic INFO/WARN/ERROR list | Diagnostics, System Logs |
The bottom widgets are useful for narrowing the "scope" of a problem. For example, if today's collection volume has dropped, going from the site list to OPC trends to the equipment heatmap quickly reveals which layer stopped.
Key Drilldowns
| Starting point | Next screen | Purpose |
|---|---|---|
| Map marker | Factory Management, Equipment | Check site, line, and equipment structure |
| Connection status chip | Connection Status | Identify disconnected or delayed data sources |
| Edge anomaly | Edge Gateway | Check Edge device resources and PLC collection status |
| Alarm toast | Alarms | Check the tag, asset, and time of the alarm |
| Diagnostics toast | Diagnostics | Trace the cause of a system event |
| Sharp drop in collection volume | Daily Statistics, Data Points | Compare which site or tag saw reduced data |
| OEE decline | Production Management, ISO Analysis | Break down causes across work orders, availability, performance, and quality |
Response by Abnormal Signal
| Symptom | Check first | Typical action |
|---|---|---|
| Sharp drop in communication connection rate | Connection status chips, Connection Status | Identify the dropped OPC/Edge, check the network and collection processes |
| Today's collection is 0 or sharply reduced | Pipeline collection and ingest cards | Check Edge collection, MQTT/Kafka, and storage in that order |
| Growing buffer backlog | Pipeline buffer card, engine metrics on the right | Check storage latency, external system call latency, and worker count |
| Abnormal infrastructure item | Infrastructure rail on the right | Check cache/WS/MQTT/Kafka/DB status in System |
| Increase in critical alarms | Alarm KPI, alarm toasts | Sort by tag, asset, and priority in Alarms |
| Drop in equipment availability | Equipment availability card | Check equipment health status, diagnostic logs, and recent maintenance history |
| OEE decline | Overall OEE card | Identify which axis — availability, performance, or quality — declined in ISO Analysis |
Frequently Asked Questions
Q. The dashboard numbers appear to be frozen. A. Check whether the LIVE indicator at the top is green. If it is gray or the time is stopped, refresh the browser to reconnect; if it recurs, check Diagnostics.
Q. Site markers do not appear on the map. A. The site must have latitude and longitude registered. Check the site coordinates and model registration status in Factory Management.
Q. The connection rate is low, but Edge looks normal. A. The HTTP status of an Edge device and the reception status of tag data can differ. Check the actual delayed or disconnected targets in Connection Status.
Q. Everything in the right health rail's infrastructure is normal, but one site is abnormal. A. Rather than a platform-wide failure, this is more likely a network, Edge, or OPC/PLC connection problem at that site. Check the site marker and Connection Status first.
Q. An alarm toast disappeared. Can I see it again?
A. In Alarms, narrow the recent time range to 10M or 30M to review it. For a system event, query the same time slot in Diagnostics.
Related Screens
- Console Navigation and Common Screens — Left menu, top search, common patterns
- Daily Statistics — Operating statistics by date and comparative analysis
- Connection Management — Protocols, connection status, Edge gateway
- Alarms — Real-time alarms and history search
- Equipment Management — Equipment list and per-equipment dashboards
- Data Points — Source data lookup by tag
- Diagnostics — System diagnostic events
- System — Infrastructure health, logs, settings, environment information
- Status Code Definitions — Connection, health, alarm, and production status codes