Files
HF-MES-manual/en/device_management/equipment_status_management.md

196 lines
9.1 KiB
Markdown
Raw Normal View History

2026-05-12 01:46:34 +08:00
# Equipment Status Management
## 1. Function Overview
The Equipment Status Management function is used for real-time monitoring, recording, and analysis of production site equipment operating status, achieving transparent equipment status, traceable anomalies, and controllable operations.
**Core Features:**
- Real-time Status Monitoring: View current equipment operating status (Running/Standby/Fault/Offline/Completed/Manual)
## 2. Term Definitions
### 2.1 Equipment Status Related Terms
| Term | Definition | Description |
|------|------------|-------------|
| Equipment Status | Equipment operating condition at a specific point in time | Such as running, standby, fault, offline, completed, manual |
| Running Status | Equipment is in normal production or processing | Usually indicates equipment is processing |
| Standby Status | Equipment is powered on but not producing | Can enter production status at any time |
| Fault Status | Equipment cannot run due to abnormality | Requires repair or manual intervention |
| Offline Status | Equipment not connected to system or powered off | System cannot obtain real-time data for more than 15 seconds |
| Completed Status | Equipment is in finished/ended state | Some equipment have completed status (e.g., grading and DCIR equipment). After equipment work ends, it needs to wait for logistics line to pick up or discharge materials. Equipment will be defined as completed status: work completed, waiting for pickup |
| Manual Status | Equipment is in manual mode | When equipment is in first inspection/patrol/equipment adjustment to manual, this status is mostly for equipment debugging |
| Status Switch | Process of change between equipment statuses | Such as running → fault → recovery |
| Status Log | Historical data recording equipment status changes | Includes time, status, duration, etc. |
**Feature Screenshots:**
<div align="center">
<img style="margin-top:18px;" src="/public/image_en/device_management/equipment_status_management/设备状态管理页面截图.png" alt="Equipment Status Management Page Screenshot">
<div style="font-size:12px; font-weight:bold;">Figure 1: Equipment Status Management Page</div>
</div>
---
## 3. Function Modules
### 3.1 Equipment Status Monitoring
Equipment status logs are used to record and display all status change information of equipment during production.
**Typical Application Scenarios:**
- Production managers view equipment operating status in real-time
- Quickly locate fault occurrence time when equipment is abnormal
**Equipment Status Data Flow:**
```mermaid
flowchart LR
A[Equipment Power On] --> B[Standby Status]
%% Normal Production Flow
B --> C[Running Status]
C --> D{Processing Completed?}
D -->|No| C
D -->|Yes| E[Completed Status]
%% Post-completion Flow
E --> F{Materials Picked Up?}
F -->|No| E
F -->|Yes| B
%% Fault Flow
C --> G{Abnormal?}
G -->|Yes| H[Fault Status]
H --> I[Repair Processing]
I --> B
%% Manual Flow (Can be inserted into multiple statuses)
B --> J[Manual Status]
C --> J
E --> J
J --> K[Manual End]
K --> B
```
## 4. Operation Instructions
### 4.1 Equipment Status Monitoring
**Operation Steps:**
1. Navigate to [Equipment Management] → [Equipment Status Management] → [Equipment Status Monitoring]
2. Click status (Running / Standby / Fault / Completed / Manual / Offline)
3. The system displays equipment status records that meet the conditions
**Feature Screenshots:**
<div align="center">
<img style="margin-top:18px;" src="/public/image_en/device_management/equipment_status_management/设备状态管理运行状态筛选截图.png" alt="Equipment Status Management Running Status Filter Screenshot">
<div style="font-size:12px; font-weight:bold;">Figure 1: Equipment Status Management Running Status Filter</div>
</div>
<div align="center">
<img style="margin-top:18px;" src="/public/image_en/device_management/equipment_status_management/设备状态管理待料状态筛选截图.png" alt="Equipment Status Management Waiting Status Filter Screenshot">
<div style="font-size:12px; font-weight:bold;">Figure 2: Equipment Status Management Waiting Status Filter</div>
</div>
<div align="center">
<img style="margin-top:18px;" src="/public/image_en/device_management/equipment_status_management/设备状态管理手动状态筛选截图.png" alt="Equipment Status Management Manual Status Filter Screenshot">
<div style="font-size:12px; font-weight:bold;">Figure 3: Equipment Status Management Manual Status Filter</div>
</div>
## 5. Status Definitions and Rules
### 5.1 Status Priority
To prevent equipment from having multiple statuses simultaneously, the system defines status priorities as follows:
| Priority | Status | Description |
|----------|--------|-------------|
| 1 | Fault Status | Highest priority, equipment abnormal |
| 2 | Manual Status | Manual intervention (adjustment/inspection) |
| 3 | Running Status | Normal production |
| 4 | Completed Status | Processing completed, waiting for pickup |
| 5 | Standby Status | Idle, ready for production |
**[Important]** When multiple statuses are satisfied simultaneously, the system displays the highest priority status.
---
### 5.2 Status Judgment Rules
| Status | Judgment Rule |
|--------|---------------|
| Running Status | Equipment has production task and is processing |
| Standby Status | Equipment is powered on but has no production task |
| Fault Status | Equipment reports error or stops abnormally |
| Completed Status | Processing completed but materials not picked up |
| Manual Status | Manual operation or debugging in progress |
| Offline Status | System cannot obtain equipment communication for more than 15 seconds, defaults to offline |
**[Note]** Status judgment depends on equipment data collection. If data is abnormal, status may be inaccurate.
### 5.3 Abnormal Status Upload Rules
**Note: The following rules depend on equipment and manufacturer. Need to check if the equipment manufacturer has specific definitions. MES single request only collects unique equipment abnormal code and abnormal information. Abnormal level requires corresponding planning from equipment manufacturer.**
During equipment operation, multiple abnormal signals may appear simultaneously (e.g., servo alarm, safety door open, air pressure abnormality). To ensure uniqueness and accuracy of equipment status display, the system must judge according to preset priorities and only display the highest priority abnormal status.
**Judgment Principles:**
- When multiple abnormalities exist simultaneously, only the highest priority abnormality is displayed
- Low priority abnormalities do not take effect until high priority abnormalities are resolved
- After abnormality recovery, the system automatically re-judges the current highest priority status
- Abnormal status takes priority over all normal statuses (running/standby/completed, etc.)
---
**Abnormality Priority Example:**
| Priority | Abnormality Type | Description |
|----------|------------------|-------------|
| 1 | Servo Motor Abnormality | Affects equipment core motion control, requires immediate shutdown |
| 2 | Spindle/Drive Abnormality | Critical execution component abnormality |
| 3 | Air Pressure Abnormality | Affects equipment motion stability |
| 4 | Safety Door Open | Safety protection triggered, requires manual intervention |
| 5 | General Alarm | Non-critical alarm, does not affect core operation |
---
**Judgment Logic Description:**
- When "Servo Motor Abnormality" and "Safety Door Open" exist simultaneously, the system/equipment prioritizes judging "Servo Motor Abnormality"
- After high priority abnormality is resolved, if low priority abnormality still exists, it automatically switches to corresponding abnormal status
- If all abnormalities are resolved, equipment returns to normal status (running/standby, etc.)
---
**[Important]** Abnormality priority needs to be configured according to equipment type. Different equipment (e.g., grading equipment, assembly equipment) may have differences.
**[Note]** If abnormality priority is configured unreasonably, it may lead to misjudgment of actual equipment status on-site. Equipment engineering personnel should participate in defining priorities.
**[Tip]** It is recommended to bind abnormal codes with priorities for unified system maintenance and expansion.
## 6. Data Management Requirements
### 6.1 Data Integrity Requirements
**[Important]** To ensure accuracy of status analysis, the following data must be complete:
- All equipment must be connected to the system
- Status changes must be uploaded in real-time
- Fault status must record causes
- Manual status must record operation scenarios
---
### 6.2 Data Abnormality Handling
| Issue Phenomenon | Possible Cause | Handling Method |
|-----------------|----------------|----------------|
| Status not updated | Equipment not connected to network | Check equipment connection |
| Incorrect status | Data collection abnormal | Check collection program |
| No status records | Status management not enabled | Enable equipment monitoring |
**[Note]** Data abnormalities directly affect equipment analysis results and should be handled promptly.