Overall Menu Structure and Operational Flowchart
Table of Contents
- Overview
- Overall Menu Map
- Role by Menu Group
- Operational Start Flow
- Data Collection and Model Flow
- Alarm Response Flow
- Automation and Standard Integration Flow
- System Management Flow
- Initial Entry Menu by Scenario
- Related Screens
Overview
This page provides a single-view summary of the overall menu structure of the PlantPulse console and the operational flowcharts frequently used by operators. While specific buttons and screen elements are detailed in Console Navigation and Common Screens, this document focuses on "which menu to use and in what order."
The current left menu consists of the following 13 groups based on the integrated server-web menu. The menus visible to a user vary by role — Permissions and Menu Exposure.
개요 → 연결 → 공장 모델 → 설비 → 생산 → 정비 → ISO
→ 데이터 → 알람 → 시각화 → 자동화 → 표준 → 시스템
Overall Menu Map
Role by Menu Group
| Group | Key Question | Representative Screen |
|---|---|---|
| Overview | Are the factory and platform operating normally? | Dashboard, Daily Statistics |
| Connectivity | Is data flowing from the field to the server? | Connection Management, Edge |
| Factory Model | Are the site, line, equipment, and tag models registered correctly? | Factory Model |
| Production | Do customers, products, processes, work schedules, and work orders align with operational standards? | Production Management, Process Diagram |
| Equipment | Which equipment is problematic and what is the related data? | Equipment Management, Data Inquiry |
| ISO | What is the performance from an OEE/RAM/EMS perspective? | ISO Data and Analysis |
| Data | What are the raw values and trends of the tag data? | Data Point, Object |
| Alarm | Which alarm occurred when, where, and why, and is it manageable for the operator? | Alarm |
| Visualization | How will field screens be viewed via drawings and widgets? | Canvas |
| Automation | Should events be processed automatically or integrated with external systems? | Flow, CEP, EQL |
| Standard | How is it connected to the standard namespace, OPC-UA, and AAS? | UNS, Standards and External Tools |
| System | Is the platform's own status, security, and configuration normal? | System, Security Management, Diagnostic |
Operational Start Flow
Data Collection and Model Flow
When adding a new site or line, the model and connection must be reviewed together. Registering only the model leaves the dashboard numbers empty, and registering only the connection makes it difficult for operators to interpret which equipment or tag the data belongs to.
| Step | Check Point |
|---|---|
| Model Registration | Whether Site, Zone, Line, Equipment, and Tag IDs follow the standard |
| Protocol Registration | Whether the connection between the site and data sources (OPC/PLC/DB/API) is correct |
| Connection Status Check | Whether the status falls under Normal, Delay, Anomaly, Disconnected, or Unconnected |
| Data Verification | Whether tag values are actually recorded in streams and trends |
| Dashboard Reflection | Whether the site map, connection rate, and today's collection volume change as expected |
Alarm Response Flow
| Symptom | Next Screen |
|---|---|
| Continuous alarms from a specific tag | Trend in Data Point, Alarm Analysis |
| Alarms concentrated by equipment unit | Equipment Management, Timeline Comparison |
| Alarms occurring simultaneously with communication loss | Connection Status, Edge |
| Too many alarms / Chattering | Alarm Performance |
| Alarm not sounding when it should | Hidden · Suppressed · Excluded from Service |
| Condition formula itself needs changing | Advanced Alarm, EQL Help |
Automation and Standard Integration Flow
Automation is the area where you define "where to receive an event, what conditions to filter by, and where to send it." If topic names are confusing, check the path in UNS first, and configure the actual processing graph in Flow.
System Management Flow
| Inspection Target | Screen to View First |
|---|---|
| WebSocket LIVE stopped | System > Monitoring, Diagnostic |
| Server logs required | System > Log |
| Configuration value check | System > Environment Info, Configuration |
| Account/Token issue | Security Management |
| Cluster node problem | System, Cluster |
Initial Entry Menu by Scenario
| Task | First Entry Menu | Next Menu |
|---|---|---|
| Shift start inspection | Overview > Dashboard | Statistics, Connection Status, Alarm |
| New equipment/tag registration | Factory Model > Model/Asset/Tag | Connectivity > Protocol |
| Data not arriving | Connectivity > Connection Status | Edge, Data > Stream |
| Tag raw value check | Data > Trend | Data Export, Snapshot |
| Specific equipment status check | Equipment > Equipment List | Timeline Comparison, Alarm |
| Alarm cause analysis | Alarm > Alarm | Alarm Search, Alarm Analysis |
| Alarm burden assessment | Alarm > Alarm Performance | Advanced Alarm |
| OEE/RAM/EMS analysis | ISO > ISO Analysis | ISO Data, Production > Work Order |
| Field monitoring screen creation | Visualization > Canvas | Factory Model, Data |
| Event automatic processing | Automation > Flow | EQL Query, Flow Execution History |
| Topic path verification | Standard > UNS | Automation > Flow |
| System failure check | System > Monitoring | Diagnostic, Log, Cluster |
Related Screens
- Console Navigation and Common Screens — Top bar, left menu, domain search
- Dashboard — Operation start screen
- Connection Management — Data ingestion and Edge status
- Factory Model — Site, equipment, and tag models
- Process Diagram — Mapping equipment and process flow and dependencies
- Alarm — Alarm response and analysis
- Flow — Automation graphs
- UNS — Standard namespace and topics
- System — Platform operational status