diff --git a/en/analysis/reports.md b/en/analysis/reports.md
new file mode 100644
index 0000000..ae54415
--- /dev/null
+++ b/en/analysis/reports.md
@@ -0,0 +1,382 @@
+# Reports & Analysis
+
+## 1. Overview
+
+The Reports & Analysis module provides comprehensive statistical analysis reports to help enterprises gain insights into production operations and support management decisions.
+
+**Core Features:**
+
+| Feature | Description |
+|---------|-------------|
+| Production Reports | Production data statistics and analysis |
+| Quality Reports | Quality data statistics and analysis |
+| Equipment Reports | Equipment operation data analysis |
+| Inventory Reports | Inventory data analysis |
+| Custom Reports | Custom report development |
+| Report Subscription | Automated report delivery |
+
+## 2. Production Reports
+
+### 2.1 Daily Production Report
+
+**Report Content:**
+
+| Item | Description |
+|------|-------------|
+| Date | Reporting date |
+| Production Line | Line name |
+| Planned Output | Planned production quantity |
+| Actual Output | Actual production quantity |
+| Achievement Rate | Actual/Planned × 100% |
+| Qualified Quantity | Qualified product count |
+| Qualification Rate | Qualified/Actual × 100% |
+| Defective Quantity | Defective product count |
+| Defect Rate | Defective/Actual × 100% |
+| WIP Quantity | Work-in-process quantity |
+
+**Report Example:**
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│ Daily Production Report - 2026-04-10 │
+├─────────────────────────────────────────────────────────────┤
+│ │
+│ SMT Line A │
+│ ┌──────────┬──────────┬──────────┬──────────┬──────────┐ │
+│ │ Planned │ Actual │ Achieve │ Qualify │ Defect │ │
+│ │ 10000 │ 9520 │ 95.2% │ 98.5% │ 1.5% │ │
+│ └──────────┴──────────┴──────────┴──────────┴──────────┘ │
+│ │
+│ SMT Line B │
+│ ┌──────────┬──────────┬──────────┬──────────┬──────────┐ │
+│ │ 8000 │ 7600 │ 95.0% │ 98.2% │ 1.8% │ │
+│ └──────────┴──────────┴──────────┴──────────┴──────────┘ │
+│ │
+└─────────────────────────────────────────────────────────────┘
+```
+
+### 2.2 Monthly Production Report
+
+**Report Content:**
+
+| Item | Description |
+|------|-------------|
+| Month | Reporting month |
+| Department | Department name |
+| Product | Product name |
+| Planned Output | Monthly planned quantity |
+| Completed Output | Monthly completed quantity |
+| Plan Achievement Rate | Completed/Planned × 100% |
+| Output per Person | Output/Headcount |
+| Equipment Utilization | Operating time/Available time |
+
+### 2.3 Work Order Statistics
+
+**Statistics Dimensions:**
+
+| Dimension | Description |
+|-----------|-------------|
+| Order Count | Completed/In Progress/Canceled |
+| On-Time Rate | On-time orders/Total orders |
+| Overdue Rate | Overdue orders/Total orders |
+| Change Rate | Changed orders/Total orders |
+
+### 2.4 Capacity Analysis
+
+**Analysis Content:**
+
+| Item | Description |
+|------|-------------|
+| Capacity Utilization | Actual capacity/Theoretical capacity |
+| Capacity Bottleneck | Process/equipment affecting capacity |
+| Capacity Improvement | Potential improvement after optimization |
+| Capacity Forecast | Future capacity prediction |
+
+**Capacity Analysis Table:**
+
+| Line | Theoretical | Actual | Utilization | Bottleneck |
+|------|------------|--------|-------------|-----------|
+| SMT-A | 25000 | 21250 | 85.0% | Reflow Soldering |
+| SMT-B | 20000 | 17000 | 85.0% | AOI Inspection |
+| Assembly-A | 15000 | 12000 | 80.0% | Assembly |
+
+## 3. Quality Reports
+
+### 3.1 Daily Quality Report
+
+**Report Content:**
+
+| Item | Description |
+|------|-------------|
+| Date | Reporting date |
+| Inspection Type | IQC/IPQC/FQC |
+| Inspection Batches | Number of batches inspected |
+| Qualified Batches | Number of qualified batches |
+| Batch Qualification Rate | Qualified/Total × 100% |
+| Inspection Quantity | Quantity inspected |
+| Qualified Quantity | Qualified count |
+| Unit Qualification Rate | Qualified/Inspected × 100% |
+| Main Defects | Main defect types |
+
+### 3.2 Monthly Quality Report
+
+**Report Content:**
+
+| Item | Description |
+|------|-------------|
+| Month | Reporting month |
+| IQC Batch Qualification | Incoming inspection rate |
+| IPQC Qualification | In-process inspection rate |
+| FQC Qualification | Final inspection rate |
+| Customer Complaints | Number of complaints |
+| Quality Cost | Quality loss cost |
+| Quality Target Achievement | Actual/Target × 100% |
+
+### 3.3 Defect Analysis
+
+**Analysis Dimensions:**
+
+| Type | Content |
+|------|---------|
+| Defect Item Analysis | Proportion of various defect types |
+| Defect Process Analysis | Defect distribution by process |
+| Defect Time Analysis | Defect occurrence by time |
+| Defect Cause Analysis | Defect cause proportion |
+| Defect Trend Analysis | Defect rate trend |
+
+**Pareto Analysis:**
+
+| Defect Type | Count | Percentage | Cumulative |
+|-------------|-------|------------|------------|
+| Appearance | 150 | 30% | 30% |
+| Dimension | 120 | 24% | 54% |
+| Function | 100 | 20% | 74% |
+| Performance | 80 | 16% | 90% |
+| Others | 50 | 10% | 100% |
+
+### 3.4 Quality Trend Analysis
+
+**Trend Analysis:**
+
+| Item | Display Method |
+|------|---------------|
+| Qualification Rate Trend | Line chart |
+| Defect Rate Trend | Line chart |
+| Target Achievement Trend | Comparison chart |
+| SPC Control Chart | Control chart |
+
+## 4. Equipment Reports
+
+### 4.1 Daily Equipment Report
+
+**Report Content:**
+
+| Item | Description |
+|------|-------------|
+| Date | Reporting date |
+| Equipment ID | Equipment code |
+| Equipment Name | Equipment name |
+| Operating Time | Actual operating hours |
+| Downtime | Downtime hours |
+| Operating Rate | Operating/Available × 100% |
+| Fault Count | Number of faults |
+| Maintenance Count | Number of maintenance |
+| OEE | Overall Equipment Effectiveness |
+
+### 4.2 OEE Analysis Report
+
+**OEE Components:**
+
+| Component | Description | Formula |
+|-----------|-------------|---------|
+| Availability | Time utilization | Operating time/Planned time |
+| Performance | Speed utilization | Actual output/Theoretical output |
+| Quality | Quality utilization | Qualified/Total output |
+| OEE | Overall efficiency | Availability × Performance × Quality |
+
+**OEE Analysis Table:**
+
+| Equipment | Availability | Performance | Quality | OEE |
+|-----------|--------------|-------------|---------|-----|
+| Mounter-A | 95% | 90% | 98% | 83.8% |
+| Reflow-B | 92% | 88% | 99% | 80.1% |
+| AOI-C | 98% | 85% | 97% | 80.9% |
+
+### 4.3 Equipment Maintenance Report
+
+**Maintenance Statistics:**
+
+| Item | Description |
+|------|-------------|
+| Equipment ID | Equipment code |
+| Inspection Count | Number of inspections |
+| Maintenance Count | Number of maintenance |
+| Fault Count | Number of faults |
+| Repair Time | Total repair time |
+| MTBF | Mean Time Between Failures |
+| MTTR | Mean Time To Repair |
+| Maintenance Cost | Maintenance expenses |
+
+## 5. Inventory Reports
+
+### 5.1 Inventory Ledger
+
+**Report Content:**
+
+| Item | Description |
+|------|-------------|
+| Material Code | Material number |
+| Material Name | Material name |
+| Warehouse | Warehouse name |
+| Location | Location code |
+| Batch | Material batch |
+| Quantity | Inventory quantity |
+| Unit | Unit of measure |
+| Amount | Inventory value |
+| Status | Normal/Frozen |
+
+### 5.2 Inventory Turnover Analysis
+
+**Turnover Metrics:**
+
+| Metric | Formula | Description |
+|--------|---------|-------------|
+| Turnover Rate | Issue cost/Average inventory | Number of turnovers |
+| Turnover Days | 360/Turnover rate | Days per turnover |
+| Target Turnover | - | Target value |
+
+**Analysis Table:**
+
+| Material Type | Average Inventory | Monthly Issue | Turnover | Days |
+|---------------|------------------|---------------|----------|------|
+| Raw Material | 1M | 500K | 6x | 60 days |
+| WIP | 800K | 400K | 6x | 60 days |
+| Finished Goods | 1.2M | 600K | 6x | 60 days |
+
+### 5.3 Slow-Moving Material Analysis
+
+**Slow-Moving Definition:**
+
+| Grade | Definition | Action |
+|-------|------------|--------|
+| Level 1 | Unused for 6+ months | Disposal required |
+| Level 2 | Unused for 3-6 months | Monitor |
+| Level 3 | Unused for 1-3 months | Alert |
+
+**Slow-Moving Materials:**
+
+| Material Code | Material Name | Quantity | Duration | Amount | Recommendation |
+|---------------|---------------|----------|----------|--------|----------------|
+| M001 | Resistor 10K | 50000 | 8 months | 50K | Promote/Scrap |
+| M002 | Capacitor 100u | 30000 | 7 months | 30K | Promote/Transfer |
+
+## 6. Report Management
+
+### 6.1 Report Classification
+
+| Category | Description | User |
+|----------|-------------|------|
+| Daily Reports | Daily production, quality data | Shop supervisors |
+| Statistical Reports | Monthly statistics | Department managers |
+| Analysis Reports | In-depth analysis | Senior management |
+| Custom Reports | User-defined | As needed |
+
+### 6.2 Report Export
+
+**Export Formats:**
+
+| Format | Description | Use Case |
+|--------|-------------|----------|
+| Excel | .xlsx | Data analysis |
+| PDF | PDF | Print/Archive |
+| CSV | CSV | Data import |
+| Word | .docx | Report writing |
+
+### 6.3 Report Subscription
+
+**Subscription Configuration:**
+
+| Item | Description |
+|------|-------------|
+| Report Name | Report to subscribe |
+| Frequency | Daily/Weekly/Monthly |
+| Delivery Time | Scheduled time |
+| Recipient | Recipient email |
+| Format | Excel/PDF |
+
+## 7. Data Visualization
+
+### 7.1 Chart Types
+
+| Chart Type | Use Case |
+|------------|----------|
+| Line Chart | Trend analysis |
+| Bar Chart | Comparison analysis |
+| Pie Chart | Proportion analysis |
+| Scatter Plot | Correlation analysis |
+| Gantt Chart | Progress display |
+| Dashboard | Target achievement |
+
+### 7.2 Dashboard Display
+
+**Production Monitoring Dashboard:**
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│ Production Monitoring Dashboard │
+├─────────────────────────────────────────────────────────────┤
+│ │
+│ ┌─────────────────┐ ┌─────────────────┐ │
+│ │ Today's │ │ Achievement │ │
+│ │ Output │ │ Rate │ │
+│ │ 95,520 │ │ 95.5% │ │
+│ │ ▲ 3.2% │ │ ▲ 2.1% │ │
+│ └─────────────────┘ └─────────────────┘ │
+│ │
+│ ┌─────────────────┐ ┌─────────────────┐ │
+│ │ Qualification │ │ OEE │ │
+│ │ Rate │ │ │ │
+│ │ 98.5% │ │ 82.3% │ │
+│ │ ▲ 0.3% │ │ ▼ 1.5% │ │
+│ └─────────────────┘ └─────────────────┘ │
+│ │
+│ Output Trend: │
+│ ┌─────────────────────────────────────────────────────┐ │
+│ │ ╱╲ ╱╲ ╱╲ ╱╲ │ │
+│ │ ╱╲╱ ╲╱ ╲╱ ╲╱ ╲╱ ╲╱ │ │
+│ │──╱────────────────────────────── │ │
+│ │ 1 2 3 4 5 6 7 8 9 10 (Date) │ │
+│ └─────────────────────────────────────────────────────┘ │
+│ │
+└─────────────────────────────────────────────────────────────┘
+```
+
+## 8. Custom Reports
+
+### 8.1 Report Design
+
+**Design Elements:**
+
+| Element | Description |
+|---------|-------------|
+| Data Source | Source table/view |
+| Filter Criteria | Query conditions |
+| Data Fields | Display fields |
+| Calculated Fields | Formulas |
+| Grouping | Grouping method |
+| Sorting | Sorting order |
+| Display Style | Table/Chart/Dashboard |
+
+### 8.2 Report Permissions
+
+| Permission | Description |
+|------------|-------------|
+| Create | Create new reports |
+| Edit | Modify reports |
+| View | View reports |
+| Delete | Delete reports |
+| Export | Export reports |
+
+---
+
+**End of Reports & Analysis Section**
diff --git a/en/appendix/glossary.md b/en/appendix/glossary.md
new file mode 100644
index 0000000..e65158c
--- /dev/null
+++ b/en/appendix/glossary.md
@@ -0,0 +1,195 @@
+# Glossary
+
+## 1. Professional Term Definitions
+
+### 1.1 MES System Related Terms
+
+| Term | English Full Name | Chinese Definition |
+|------|------------------|-------------------|
+| MES | Manufacturing Execution System | Manufacturing Execution System |
+| ERP | Enterprise Resource Planning | Enterprise Resource Planning |
+| WMS | Warehouse Management System | Warehouse Management System |
+| QMS | Quality Management System | Quality Management System |
+| SCADA | Supervisory Control And Data Acquisition | Supervisory Control And Data Acquisition |
+| PLC | Programmable Logic Controller | Programmable Logic Controller |
+| BOM | Bill of Materials | Bill of Materials |
+| WIP | Work In Process | Work in Process |
+| OEE | Overall Equipment Effectiveness | Overall Equipment Effectiveness |
+| SPC | Statistical Process Control | Statistical Process Control |
+
+### 1.2 Quality Related Terms
+
+| Term | English Full Name | Chinese Definition |
+|------|------------------|-------------------|
+| IQC | Incoming Quality Control | Incoming Quality Control |
+| IPQC | In-Process Quality Control | In-Process Quality Control |
+| FQC | Final Quality Control | Final Quality Control |
+| OQC | Outgoing Quality Control | Outgoing Quality Control |
+| MRB | Material Review Board | Material Review Board |
+| AQL | Acceptable Quality Level | Acceptable Quality Level |
+| QC | Quality Control | Quality Control |
+| QA | Quality Assurance | Quality Assurance |
+
+### 1.3 Equipment Related Terms
+
+| Term | English Full Name | Chinese Definition |
+|------|------------------|-------------------|
+| MTBF | Mean Time Between Failures | Mean Time Between Failures |
+| MTTR | Mean Time To Repair | Mean Time To Repair |
+| TPM | Total Productive Maintenance | Total Productive Maintenance |
+| TPM | Total Productive Management | Total Productive Management |
+
+### 1.4 Warehouse and Logistics Related Terms
+
+| Term | English Full Name | Chinese Definition |
+|------|------------------|-------------------|
+| FIFO | First In First Out | First In First Out |
+| RFID | Radio Frequency Identification | Radio Frequency Identification |
+| SKU | Stock Keeping Unit | Stock Keeping Unit |
+| WMS | Warehouse Management System | Warehouse Management System |
+
+### 1.5 System and Technology Related Terms
+
+| Term | English Full Name | Chinese Definition |
+|------|------------------|-------------------|
+| API | Application Programming Interface | Application Programming Interface |
+| REST | Representational State Transfer | Representational State Transfer |
+| MQTT | Message Queuing Telemetry Transport | Message Queuing Telemetry Transport |
+| OPC | OLE for Process Control | OLE for Process Control |
+| RBAC | Role-Based Access Control | Role-Based Access Control |
+
+## 2. Business Term Definitions
+
+### 2.1 Production Management Terms
+
+| Term | Definition |
+|------|------------|
+| 工单 | Work order - execution document for production tasks, including production info, process info, and quantity info |
+| 批次 | Lot - collection of homogeneous products with identical production conditions, identified by lot number |
+| 工序 | Process - specific processing step in product manufacturing |
+| 工艺路线 | Routing - sequence of operations from material input to finished product |
+| 报工 | Reporting - operation to report production progress and quantity to the system |
+| 完工 | Completion - production of process or work order is finished |
+| 投料 | Material Release - putting materials into production process |
+| 齐套 | Full Kit - all resources (materials, equipment, personnel) ready for production |
+
+### 2.2 Quality Management Terms
+
+| Term | Definition |
+|------|------------|
+| 追溯 | Traceability - tracking product information from raw materials to finished goods |
+| 不良品 | Defective Product - product not meeting quality standards |
+| 返工 | Rework - returning defective products to process for reprocessing |
+| 降级 | Downgrade - using product at a lower grade |
+| 让步接收 | Concession Acceptance - special release after approval |
+| 首件检验 | First Article Inspection - inspection of first product at start of each batch |
+| 巡检 | Patrol Inspection - regular inspection during production |
+| 抽检 | Sampling Inspection - random sampling per sampling plan |
+
+### 2.3 Equipment Management Terms
+
+| Term | Definition |
+|------|------------|
+| 点检 | Routine Check - daily inspection and maintenance of equipment |
+| 保养 | Maintenance - preventive maintenance activities for equipment |
+| 故障 | Failure - abnormal state where equipment cannot operate normally |
+| 维修 | Repair - activity to fix equipment failure |
+| OEE | Overall Equipment Effectiveness - reflects actual production capacity |
+
+### 2.4 Warehouse Management Terms
+
+| Term | Definition |
+|------|------------|
+| 入库 | Receiving - operation for materials entering warehouse |
+| 出库 | Issue - operation for materials leaving warehouse |
+| 库存 | Inventory - quantity of materials stored in warehouse |
+| 库位 | Location - specific storage position in warehouse |
+| 盘点 | Physical Count - operation to count warehouse materials |
+| 呆滞 | Slow-moving - materials unused for extended period |
+
+## 3. Abbreviation Index
+
+| Abbreviation | Full Name |
+|--------------|-----------|
+| WO | Work Order |
+| LOT | Lot |
+| EQ | Equipment |
+| WH | Warehouse |
+| UPH | Units Per Hour |
+| KPI | Key Performance Indicator |
+| SLA | Service Level Agreement |
+| ROI | Return on Investment |
+| BOM | Bill of Materials |
+| ERP | Enterprise Resource Planning |
+
+## 4. Flowchart Summary
+
+### 4.1 Production Main Process
+
+```
+Order Receipt → Planning → Work Order Generation → Work Order Release
+ ↓
+ ┌──────────────┐
+ │ Execution │
+ │ Picking→Release→Reporting→Routing │
+ └──────────────┘
+ ↓
+ Completion → QC Inspection → Customer Delivery
+```
+
+### 4.2 Quality Management Process
+
+```
+Incoming Material → IQC Inspection → Material Storage
+ ↓
+ ┌────────────────────┐
+ │ Quality Control │
+ │ First→Patrol→Sample→Last │
+ └────────────────────┘
+ ↓
+ Final Inspection → Outgoing Inspection → Customer Delivery
+```
+
+### 4.3 Equipment Management Process
+
+```
+Equipment Registration → Equipment Operation → Daily Check → Planned Maintenance → Failure Repair → Equipment Scrap
+```
+
+### 4.4 Warehouse Logistics Process
+
+```
+Receiving Process: Arrival → Create Receipt → IQC Inspection → Allocate Location → Putaway Confirmation
+Issue Process: Material Request → Approval → Picking → Scan Issue → Production Release
+```
+
+## 5. Version Update Log
+
+### 5.1 Version History
+
+| Version | Release Date | Update Type | Update Content |
+|---------|-------------|-------------|----------------|
+| v5.0 | 2026-04-10 | Official Release | Initial release with complete functional modules |
+
+### 5.2 Update Type Description
+
+| Update Type | Description |
+|-------------|-------------|
+| 新增 | New Feature |
+| 优化 | Optimization |
+| 修复 | Bug Fix |
+| 变更 | Change |
+
+## 6. Document Information
+
+| Document Attribute | Information |
+|--------------------|-------------|
+| Document Name | HF-MES v5.0 User Manual |
+| Document Version | v1.0 |
+| Release Date | 2026-04-10 |
+| Company | - |
+| Document Status | Officially Released |
+
+---
+
+**End of Glossary**
\ No newline at end of file
diff --git a/en/business/equipment-warehouse.md b/en/business/equipment-warehouse.md
new file mode 100644
index 0000000..ed3d55c
--- /dev/null
+++ b/en/business/equipment-warehouse.md
@@ -0,0 +1,462 @@
+# Equipment and Warehouse Management
+
+## 1. Function Overview
+
+This section covers two major modules: Equipment Management and Warehouse Logistics. It implements full lifecycle management of equipment and warehouse logistics management of materials to ensure smooth production processes.
+
+**Main Contents:**
+
+| Chapter | Main Content |
+|---------|-------------|
+| Equipment Management | Equipment ledger, inspection & maintenance, fault repair, OEE analysis |
+| Warehouse Logistics | Receiving management, issuing management, inventory management |
+
+## 2. Equipment Management
+
+### 2.1 Equipment Ledger
+
+**Equipment Information Management:**
+
+| Function | Description |
+|----------|-------------|
+| Equipment Registration | Basic equipment information entry |
+| Equipment Query | Query equipment information by conditions |
+| Equipment Change | Equipment information change management |
+| Equipment Scrap | Equipment scrap process handling |
+| Equipment Documents | Equipment document management |
+
+**Equipment Lifecycle:**
+
+```
+Equipment Procurement → Equipment Installation → Equipment Acceptance → Equipment Operation → Equipment Maintenance → Equipment Scrap
+```
+
+### 2.2 Equipment Inspection
+
+**Inspection Types:**
+
+| Inspection Type | Execution Cycle | Executor | Main Content |
+|-----------------|----------------|----------|--------------|
+| Daily Inspection | Daily | Operator | Equipment running status check |
+| Periodic Inspection | Weekly/Monthly | Maintenance Technician | Equipment performance check |
+| Precision Inspection | Quarterly/Yearly | Engineer | Equipment accuracy check |
+
+**Inspection Process:**
+
+```
+Inspection Plan Generation → Inspection Task Assignment → Execute Inspection → Inspection Record → Abnormal Handling
+```
+
+**Inspection Execution Steps:**
+
+1. Receive inspection task
+2. Arrive at equipment location
+3. Perform inspection item by item according to standards
+4. Record inspection results
+5. Submit inspection record
+6. Trigger abnormal handling process if any abnormality found
+
+**Inspection Record Information:**
+
+| Record Item | Description |
+|-------------|-------------|
+| Inspection Order No. | Unique identifier for inspection order |
+| Equipment No. | Equipment being inspected |
+| Inspection Type | Daily/Periodic/Precision |
+| Inspector | Person performing inspection |
+| Inspection Time | Inspection time |
+| Inspection Items | Items being inspected |
+| Inspection Result | Normal/Abnormal |
+| Abnormal Description | Description of abnormality |
+
+### 2.3 Equipment Maintenance
+
+**Maintenance Types:**
+
+| Maintenance Type | Cycle | Content | Man-hours |
+|------------------|-------|---------|-----------|
+| Daily Maintenance | Daily | Cleaning, lubrication, tightening | 15-30min |
+| Level 1 Maintenance | Weekly | Cleaning, lubrication, adjustment | 2-4h |
+| Level 2 Maintenance | Monthly | Cleaning, lubrication, tightening, replace wear parts | 8h |
+| Level 3 Maintenance | Quarterly | Comprehensive inspection, adjustment, replacement | 1-2 days |
+| Major Overhaul | Yearly | Complete disassembly and inspection | 3-7 days |
+
+**Maintenance Process:**
+
+```
+Maintenance Plan → Maintenance Preparation → Maintenance Execution → Maintenance Record → Acceptance Confirmation
+```
+
+**Maintenance Content:**
+
+| Maintenance Item | Content | Required Materials |
+|-----------------|---------|-------------------|
+| Cleaning | Equipment surface and internal cleaning | Cleaning agent, rags |
+| Lubrication | Lubrication of moving parts | Lubricating oil |
+| Tightening | Check and tighten loose parts | Wrenches and tools |
+| Adjustment | Adjust equipment parameters | Adjustment tools |
+| Replacement | Replace wear parts | Spare parts |
+
+### 2.4 Equipment Fault Management
+
+**Fault Classification:**
+
+| Fault Category | Description | Repair Requirement |
+|----------------|-------------|-------------------|
+| Minor Fault | No impact on production | Repair within 2 hours |
+| General Fault | Partial function affected | Repair within 4 hours |
+| Serious Fault | Equipment down | Repair within 8 hours |
+| Emergency Fault | Equipment damaged | Immediate response |
+
+**Fault Handling Process:**
+
+```
+Fault Discovery → Fault Report → Fault Diagnosis → Repair Processing → Repair Acceptance → Fault Record
+```
+
+**Fault Reporting Steps:**
+
+1. Discover equipment fault
+2. Assess fault impact
+3. Emergency shutdown (if needed)
+4. Submit fault report
+5. Maintenance technician receives work order
+6. Fault diagnosis
+7. Execute repair
+8. Repair acceptance
+9. Archive fault record
+
+**Fault Report Information:**
+
+| Field | Description |
+|-------|-------------|
+| Report No. | Unique identifier for fault report |
+| Equipment No. | Faulty equipment |
+| Fault Type | Type of fault |
+| Fault Description | Description of fault |
+| Fault Time | Time fault discovered |
+| Reporter | Person reporting fault |
+| Urgency Level | Emergency/General/Minor |
+| Impact Scope | Impact on production |
+
+**Maintenance Record Information:**
+
+| Record Item | Description |
+|-------------|-------------|
+| Repair No. | Unique identifier for repair order |
+| Repair Technician | Person performing repair |
+| Repair Start Time | Start time of repair |
+| Repair End Time | Completion time of repair |
+| Fault Cause | Cause of fault |
+| Repair Measures | Repair methods taken |
+| Spare Parts Replaced | List of replaced parts |
+| Repair Result | Repair effectiveness |
+
+### 2.5 Equipment OEE Analysis
+
+**OEE Concept:**
+
+OEE (Overall Equipment Effectiveness) is a ratio measuring the actual production capacity versus the theoretical production capacity of equipment.
+
+**OEE Calculation Formula:**
+
+```
+OEE = Availability × Performance × Quality
+
+Where:
+- Availability = Actual Operating Time / Planned Operating Time × 100%
+- Performance = Actual Output / Theoretical Output × 100%
+- Quality = Qualified Product Quantity / Total Output Quantity × 100%
+```
+
+**OEE Standards:**
+
+| OEE Value | Level | Description |
+|-----------|-------|-------------|
+| ≥85% | World Class | Excellent |
+| 70%-85% | Good | Meeting standard |
+| 60%-70% | Average | Needs improvement |
+| <60% | Poor | Requires focused improvement |
+
+**OEE Analysis Dimensions:**
+
+| Analysis Dimension | Loss Type | Description |
+|-------------------|-----------|-------------|
+| Availability | Fault Downtime | Downtime due to equipment failure |
+| Availability | Changeover & Setup | Product changeover and setup time |
+| Performance | Idle & Minor Stops | Short stops |
+| Performance | Speed Loss | Running speed below theoretical speed |
+| Quality | Scrap | Defective products |
+| Quality | Rework | Products requiring rework |
+
+**OEE Improvement Measures:**
+
+| Loss Type | Improvement Measures |
+|-----------|---------------------|
+| Fault Downtime | Strengthen preventive maintenance |
+| Changeover & Setup | Optimize changeover process |
+| Idle & Minor Stops | Optimize operation process |
+| Speed Loss | Equipment upgrade and modification |
+| Scrap & Rework | Strengthen quality control |
+
+## 3. Warehouse Logistics
+
+### 3.1 Warehouse Layout
+
+**Warehouse Zone Planning:**
+
+| Zone Type | Purpose | Characteristics |
+|-----------|---------|----------------|
+| Inspection Zone | Pending inspection materials | Isolated storage |
+| Raw Material Zone | Raw material storage | Zoned by category |
+| Semi-finished Zone | Semi-finished product storage | Batch management |
+| Finished Goods Zone | Finished product storage | FIFO |
+| Return Zone | Returned materials | Separate management |
+| Scrap Zone | Scrap storage | Safety isolation |
+| Defective Zone | Defective product storage | Clear identification |
+
+**Location Coding Rules:**
+
+| Code Example | Meaning |
+|--------------|---------|
+| A-01-001 | Zone A, Row 01, Position 001 |
+| B-02-005 | Zone B, Row 02, Position 005 |
+| C-03-010 | Zone C, Row 03, Position 010 |
+
+### 3.2 Receiving Management
+
+**Receiving Types:**
+
+| Receiving Type | Description | Document Type |
+|----------------|-------------|---------------|
+| Purchase Receiving | Purchased materials arrival | Purchase Receipt |
+| Production Receiving | Production finished goods | Production Receipt |
+| Return Receiving | Sales return | Return Receipt |
+| Transfer Receiving | Transfer from other warehouse | Transfer Order |
+| Other Receiving | Other reasons | Other Receipt |
+
+**Receiving Process:**
+
+```
+┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
+│ Arrival │───▶│ Document │───▶│ IQC │───▶│ Inspection│
+│ Receive │ │ Create │ │ Trigger │ │ Execute │
+└──────────┘ └──────────┘ └──────────┘ └──────────┘
+ │
+ ▼
+┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
+│Confirm │◀───│Allocate │◀───│Location │◀───│ Qualified│
+│Receiving │ │ Location │ │ Select │ │ Decision│
+└──────────┘ └──────────┘ └──────────┘ └──────────┘
+```
+
+**Receiving Operation Steps:**
+
+1. Materials arrive, receive delivery note
+2. Create receiving document
+3. System automatically pushes IQC inspection task
+4. Execute incoming inspection
+5. After passing inspection, allocate location
+6. Put materials onto designated location
+7. Scan location to confirm
+8. Complete receiving
+
+**Receiving Document Information:**
+
+| Field | Description |
+|-------|-------------|
+| Receipt No. | Unique identifier for receipt |
+| Receiving Type | Purchase/Production/Return etc. |
+| Supplier | Material supplier (for purchase) |
+| Related Document | Purchase order/work order etc. |
+| Receiving Date | Receiving date |
+| Material Details | List of received materials |
+| Warehouse | Receiving warehouse |
+| Status | Pending inspection/Received etc. |
+
+### 3.3 Issuing Management
+
+**Issuing Types:**
+
+| Issuing Type | Description | Document Type |
+|--------------|-------------|---------------|
+| Production Issue | Materials for production | Issue Order |
+| Sales Issue | Sales delivery | Sales Issue Order |
+| Return Issue | Return to supplier | Return Order |
+| Transfer Issue | Transfer to other warehouse | Transfer Order |
+| Other Issue | Other reasons | Other Issue Order |
+
+**Issuing Process:**
+
+```
+┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
+│ Material │───▶│ Document │───▶│ Picking │───▶│ Approval │
+│ Request │ │ Create │ │ Prepare │ │ Pass │
+└──────────┘ └──────────┘ └──────────┘ └──────────┘
+ │
+ ▼
+┌──────────┐ ┌──────────┐
+│Confirm │◀───│ Scan │
+│ Issuing │ │ Issue │
+└──────────┘ └──────────┘
+```
+
+**Issuing Operation Steps:**
+
+1. Create issue order based on work order or manually
+2. Select required materials
+3. System checks inventory status
+4. Approve issue order
+5. Warehouse personnel prepare and pick materials
+6. Scan materials and locations
+7. Confirm issuing
+8. Deliver materials to using department
+
+**Issue Order Information:**
+
+| Field | Description |
+|-------|-------------|
+| Issue No. | Unique identifier for issue order |
+| Issue Type | Production issue/Other |
+| Related Work Order | Work order related to issue |
+| Issue Department | Department requesting materials |
+| Issuer | Person issuing materials |
+| Issue Date | Issue date |
+| Material Details | List of issued materials |
+| Warehouse | Issuing warehouse |
+| Status | Pending approval/Issued etc. |
+
+### 3.4 Inventory Management
+
+**Inventory Query:**
+
+| Query Dimension | Query Content |
+|-----------------|---------------|
+| By Material | Inventory status of a material |
+| By Warehouse | Inventory status of a warehouse |
+| By Location | Inventory status of a location |
+| By Batch | Inventory status of a batch |
+| By Status | Inventory quantity distribution |
+
+**Inventory Data:**
+
+| Data Item | Description |
+|-----------|-------------|
+| Material Code | Material number |
+| Material Name | Material name |
+| Warehouse | Warehouse location |
+| Location | Storage location |
+| Batch | Material batch |
+| Quantity | Inventory quantity |
+| Unit | Unit of measurement |
+| Inventory Status | Normal/Frozen/Pending inspection |
+
+**Inventory Accounting:**
+
+| Account Type | Description |
+|--------------|-------------|
+| Opening Inventory | Inventory at period start |
+| Current Receipt | Quantity added this period |
+| Current Issue | Quantity removed this period |
+| Closing Inventory | Inventory at period end |
+
+**Inventory Calculation Formula:**
+
+```
+Closing Inventory = Opening Inventory + Current Receipt - Current Issue
+```
+
+### 3.5 Batch Management
+
+**Batch Traceability:**
+
+| Traceability Dimension | Traceability Content |
+|------------------------|---------------------|
+| Forward Traceability | Raw Material → Finished Product |
+| Reverse Traceability | Finished Product → Raw Material |
+
+**Batch Information:**
+
+| Information Item | Description |
+|------------------|-------------|
+| Batch No. | Unique batch identifier |
+| Material Batch | Material batch |
+| Supplier Batch | Supplier provided batch |
+| Production Batch | Production batch |
+| Receiving Date | Receiving time |
+| Expiry Date | Shelf life |
+| Inspection Status | Qualified/Unqualified |
+
+**First In First Out (FIFO):**
+
+| Principle | Description |
+|-----------|-------------|
+| First in, first out | Earlier received materials issued first |
+| Shelf life management | Near expiry materials issued first |
+| Clear batch identification | Clear traceable batch identification |
+
+### 3.6 Inventory Alert
+
+**Alert Types:**
+
+| Alert Type | Trigger Condition | Alert Content |
+|------------|------------------|---------------|
+| Safety Stock Alert | Inventory ≤ Safety Stock | Low inventory alert |
+| Expiry Alert | Near expiry date | Expiry approaching alert |
+| Slow-moving Alert | Long-term unused | Material slow-moving alert |
+| Maximum Stock Alert | Inventory ≥ Maximum Stock | High inventory alert |
+
+**Inventory Control Strategies:**
+
+| Strategy | Description | Application Scenario |
+|----------|-------------|---------------------|
+| Safety Stock | Minimum inventory guarantee | Regular materials |
+| Maximum Stock | Inventory upper limit control | Avoid overstock |
+| Reorder Point | Replenish when inventory reaches reorder point | Fixed quantity procurement |
+| Periodic Order | Regular inventory check and replenishment | Periodic procurement |
+
+### 3.7 Inventory Count
+
+**Count Types:**
+
+| Count Type | Description | Frequency |
+|------------|-------------|-----------|
+| Full Count | Count all materials | Year-end |
+| Partial Count | Count selected materials | Monthly/Weekly |
+| Cycle Count | Planned cyclic counting | Daily |
+| Dynamic Count | Real-time counting | Continuous |
+
+**Count Process:**
+
+```
+Count Plan → Count Preparation → Initial Count → Recount → Variance Review → Accounting Adjustment
+```
+
+**Count Steps:**
+
+1. Create count document
+2. Select warehouse and materials
+3. Execute initial count (first count)
+4. Execute recount (verification)
+5. Reconcile with system records
+6. Analyze count variances
+7. Approve variances
+8. Execute accounting adjustment
+
+**Count Records:**
+
+| Record Item | Description |
+|-------------|-------------|
+| Count No. | Unique count document identifier |
+| Count Type | Full/Partial/Cycle |
+| Count Warehouse | Warehouse being counted |
+| Count Date | Count date |
+| Book Quantity | System recorded quantity |
+| Actual Quantity | Physically counted quantity |
+| Variance Quantity | Quantity difference |
+| Variance Reason | Reason for variance |
+| Approval Status | Pending approval/Approved |
+
+---
+
+**End of Equipment and Warehouse Management**
\ No newline at end of file
diff --git a/en/business/production.md b/en/business/production.md
new file mode 100644
index 0000000..760023b
--- /dev/null
+++ b/en/business/production.md
@@ -0,0 +1,442 @@
+# Production Management
+
+## 1. Function Overview
+
+The Production Management module is the core module of the MES system, covering the entire process from production planning to production execution. It achieves digitalization, transparency, and intelligence of the production process.
+
+**Core Functions:**
+
+| Function | Description |
+|----------|-------------|
+| Production Planning | Production plan formulation and breakdown |
+| Work Order Management | Work order creation, approval, release, and change |
+| Reporting Management | Production reporting and completion confirmation |
+| Production Monitoring | Real-time production progress monitoring |
+| Material Flow | Material release, picking, and semi-finished product flow |
+| Production Reports | Production data statistics and analysis |
+
+## 2. Production Planning Management
+
+### 2.1 Production Plan Types
+
+| Plan Type | Description | Time Range |
+|-----------|-------------|------------|
+| Annual Plan | Annual production outline | 1 year |
+| Monthly Plan | Monthly production plan | 1 month |
+| Weekly Plan | Weekly production schedule | 1 week |
+| Daily Plan | Daily production dispatch | 1 day |
+| Emergency Plan | Rush order, change plan | Immediate |
+
+### 2.2 Production Plan Sources
+
+**Plan Generation Methods:**
+
+| Source | Description | Automation Level |
+|--------|-------------|------------------|
+| Sales Order | Generated from sales orders | Semi-automatic |
+| Forecast Order | Generated from forecast data | Semi-automatic |
+| Inventory Replenishment | Generated when inventory below safety level | Automatic |
+| Manual Creation | Manually created plan | Manual |
+
+### 2.3 Plan Balance and Breakdown
+
+**Plan Balance Process:**
+
+```
+┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
+│Demand Plan │───▶│Capacity Check│───▶│Plan Adjustment│───▶│Plan Confirmation│
+└─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘
+```
+
+**Capacity Assessment Factors:**
+
+| Assessment Item | Assessment Content |
+|-----------------|-------------------|
+| Equipment Capacity | Whether equipment capacity meets requirements |
+| Material Capacity | Whether materials are available |
+| Personnel Capacity | Whether personnel are sufficient |
+| Tooling Capacity | Whether tooling fixtures are ready |
+| Environmental Capacity | Whether production environment meets requirements |
+
+## 3. Work Order Management
+
+### 3.1 Work Order Types
+
+| Work Order Type | Description | Trigger Method |
+|-----------------|-------------|----------------|
+| Production Order | Normal production order | Plan triggered |
+| Rework Order | Rework production order | Quality issue triggered |
+| Material Supplement Order | Material supplement order | Scrap triggered |
+| Trial Order | Trial production order | R&D triggered |
+| Emergency Order | Emergency rush order | Ad-hoc triggered |
+
+### 3.2 Work Order Status Flow
+
+**Status Flow Diagram:**
+
+```
+┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐
+│Pending │───▶│Created │───▶│Approved│───▶│Released│───▶│In │
+│Draft │ │ │ │ │ │ │ │Production│
+└────────┘ └────────┘ └────────┘ └────────┘ └────────┘
+ │ │
+ │ ▼
+ │ ┌────────┐
+ │ │Completed│
+ └────────────────────────────────────────────────────▶│ │
+ └────────┘
+```
+
+**Status Description:**
+
+| Status | Description | Available Operations |
+|--------|-------------|---------------------|
+| Pending Draft | Plan being formulated | Edit, Delete |
+| Created | Plan completed | Submit for approval, Edit |
+| Approved | Approved | Release |
+| Released | Released to production line | Start production |
+| In Production | Production in progress | Reporting, Pause |
+| Completed | Production completed | Receiving, Close |
+| Closed | Work order closed | View |
+| Cancelled | Work order cancelled | View |
+
+### 3.3 Work Order Creation
+
+**Creation Steps:**
+
+1. Go to [Production Management] → [Work Order Management]
+2. Click [New Work Order]
+3. Select product
+4. Fill in work order information:
+ - Production quantity
+ - Planned start/end date
+ - Planned production line
+ - Priority
+5. System automatically calculates material requirements
+6. Save work order
+
+**[Note]** Ensure product BOM and routing are maintained before creating work order.
+
+### 3.4 Work Order Information
+
+**Work Order Basic Information:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Work Order No. | Unique work order identifier | ✓ |
+| Product Code | Product to produce | ✓ |
+| Product Name | Product name | ✓ |
+| Production Quantity | Planned production quantity | ✓ |
+| Qualified Quantity | Qualified product quantity | - |
+| Defective Quantity | Defective product quantity | - |
+| Planned Start Date | Planned start date | ✓ |
+| Planned End Date | Planned end date | ✓ |
+| Actual Start Date | Actual start date | - |
+| Actual End Date | Actual end date | - |
+| Priority | Work order priority | ✓ |
+| Work Order Status | Current status | System auto |
+
+**Work Order Related Information:**
+
+| Related Item | Description |
+|--------------|-------------|
+| Sales Order | Related sales order |
+| Customer Info | Customer information |
+| BOM Version | BOM version used |
+| Process Version | Process version used |
+
+### 3.5 Work Order Approval
+
+**Approval Process:**
+
+1. Work order creator submits for approval
+2. Approver receives approval task
+3. Review work order information
+4. Check material availability
+5. Check capacity status
+6. Approve or reject
+
+**[Tip]** Work order quantity and planned dates can be adjusted during approval.
+
+### 3.6 Work Order Release
+
+**Release Conditions:**
+
+| Condition | Check Item | Description |
+|-----------|------------|-------------|
+| Complete Information | All required fields filled | ✓ |
+| Approved | Work order status is approved | ✓ |
+| Valid BOM | BOM is approved and effective | ✓ |
+| Valid Process | Routing is approved and effective | ✓ |
+| Materials Available | Required materials in stock | ✓ |
+| Line Available | Production line is available | ✓ |
+
+**Release Steps:**
+
+1. Select approved work order
+2. Click [Release] button
+3. System performs availability check
+4. Availability check passed
+5. Confirm release information
+6. Work order status changes to "Released"
+
+**[Note]** If availability check fails, materials need to be replenished or work order adjusted first.
+
+### 3.7 Work Order Change
+
+**Change Types:**
+
+| Change Type | Description | Impact |
+|-------------|-------------|--------|
+| Quantity Adjustment | Increase/decrease production quantity | Affects material requirements |
+| Plan Adjustment | Adjust planned dates | Affects scheduling |
+| Line Change | Change production line | Affects scheduling |
+| Process Adjustment | Adjust process sequence | Affects routing |
+| Emergency Rush | Adjust work order priority | Affects scheduling |
+
+**Change Process:**
+
+```
+Change Request → Change Approval → Change Execution → Change Confirmation
+```
+
+**[Tip]** Work order changes during production need to be handled carefully as they may affect ongoing production operations.
+
+## 4. Reporting Management
+
+### 4.1 Reporting Types
+
+| Reporting Type | Description | Timing |
+|----------------|-------------|--------|
+| Start Reporting | Process starts operation | At process start |
+| Completion Reporting | Process completes operation | At process completion |
+| Exception Reporting | Process abnormally paused | When exception occurs |
+| Shift Reporting | Shift handover record | At shift handover |
+
+### 4.2 Reporting Process
+
+**Process Reporting Flow:**
+
+```
+Start Reporting → Process Operation → Completion Reporting → Next Process
+```
+
+**Detailed Flow:**
+
+```
+┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
+│Start │───▶│Operation │───▶│Completion│───▶│Quality │
+│Reporting │ │In Progress│ │Reporting │ │Inspection│
+└──────────┘ └──────────┘ └──────────┘ └──────────┘
+ │
+ ┌──────────────────────────────────────┘
+ │
+ ▼
+ ┌──────────┐
+ │Process │
+ │Transfer │
+ └──────────┘
+```
+
+### 4.3 Start Reporting
+
+**Operation Steps:**
+
+1. Go to [Production Management] → [Reporting Management]
+2. Select work order ready to start
+3. Select process
+4. Fill in start information:
+ - Start time
+ - Operator
+ - Equipment selection
+5. Submit start report
+6. System records start time
+
+**[Tip]** After start reporting, the system locks the process to prevent duplicate starts.
+
+### 4.4 Completion Reporting
+
+**Operation Steps:**
+
+1. Select started work order
+2. Select process
+3. Fill in completion information:
+ - Completed quantity
+ - Qualified quantity
+ - Defective quantity
+ - Defect reason (if any)
+ - Operation time
+ - Material consumption (if needed)
+4. Submit completion report
+5. System automatically triggers quality inspection (if inspection point configured)
+
+**Completion Reporting Information:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Completed Quantity | Quantity completed this time | ✓ |
+| Qualified Quantity | Qualified product quantity | ✓ |
+| Defective Quantity | Defective product quantity | - |
+| Defect Reason | Description of defect reason | - |
+| Operation Time | Actual operation time | ✓ |
+| Material Consumption | Quantity of materials consumed | - |
+
+### 4.5 Reporting Data
+
+**Reporting Record Information:**
+
+| Data Item | Description |
+|-----------|-------------|
+| Reporting Time | Reporting operation time |
+| Reporting Type | Start/Completion/Exception |
+| Work Order No. | Related work order |
+| Process No. | Related process |
+| Operator | Person performing operation |
+| Equipment No. | Equipment used |
+| Reporting Quantity | Reported quantity |
+| Qualification Rate | Qualified quantity/Reported quantity |
+| Operation Time | Actual operation time |
+
+## 5. Production Monitoring
+
+### 5.1 Monitoring Content
+
+**Real-time Monitoring Data:**
+
+| Monitoring Item | Description | Update Frequency |
+|-----------------|-------------|------------------|
+| Work Order Progress | Completion status of each work order | Real-time |
+| Process Progress | Completion status of each process | Real-time |
+| Production Statistics | Daily/Shift production volume | Real-time |
+| Defective Rate | Defective product ratio | Real-time |
+| Equipment Status | Equipment running status | Real-time |
+| Personnel Status | Operator status | Real-time |
+
+### 5.2 Monitoring Dashboard
+
+**Production Dashboard Display:**
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│ Production Monitoring Dashboard │
+├─────────────────────────────────────────────────────────────┤
+│ │
+│ Today's Production Overview: │
+│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
+│ │ Plan Output │ │ Actual Output│ │ Achievement │ │
+│ │ 10000 │ │ 9520 │ │ 95.2% │ │
+│ └──────────────┘ └──────────────┘ └──────────────┘ │
+│ │
+│ Production Line Status: │
+│ ┌─────────────────────────────────────────────────────┐ │
+│ │ SMT-A Line ████████████░░░░ 80% Running │ │
+│ │ SMT-B Line ██████████████░░ 85% Running │ │
+│ │ Assembly-A ██████████░░░░░░ 60% Running │ │
+│ └─────────────────────────────────────────────────────┘ │
+│ │
+└─────────────────────────────────────────────────────────────┘
+```
+
+### 5.3 Process Flow Control
+
+**Flow Rules:**
+
+| Flow Type | Description | Configuration Requirement |
+|-----------|-------------|--------------------------|
+| Sequential Flow | Operations in defined sequence | Routing definition |
+| Parallel Flow | Multiple processes simultaneously | Routing definition |
+| Conditional Flow | Process selection based on conditions | Flow condition configuration |
+
+**Process Start Conditions:**
+
+| Condition Item | Check Content |
+|----------------|---------------|
+| Previous Process Complete | Whether previous process completed |
+| Materials Available | Whether materials ready |
+| Equipment Ready | Whether equipment idle |
+| Personnel Ready | Whether operators ready |
+
+## 6. Material Flow
+
+### 6.1 Material Release Management
+
+**Release Process:**
+
+```
+Material Request → Warehouse Preparation → Scan Release → System Confirmation
+```
+
+**Release Methods:**
+
+| Method | Description | Application Scenario |
+|--------|-------------|---------------------|
+| By Work Order | Release based on work order BOM | Batch production |
+| By Process | Release based on process requirements | Multi-process production |
+| By Line | Batch release to production line | Continuous production |
+| Auto Release | System automatically controls release | Automated production line |
+
+### 6.2 Material Consumption Record
+
+**Consumption Data:**
+
+| Data Item | Description |
+|-----------|-------------|
+| Material Code | Material consumed |
+| Material Batch | Material batch number |
+| Consumption Quantity | Quantity consumed this time |
+| Consumption Time | Consumption time |
+| Related Work Order | Related work order |
+| Related Process | Related process |
+| Consumption Type | Actual consumption/Scrap |
+
+### 6.3 Work In Process (WIP) Management
+
+**WIP Monitoring:**
+
+| Monitoring Item | Description |
+|-----------------|-------------|
+| WIP Work Order Count | Number of work orders in production |
+| WIP Process Count | Number of processes in progress |
+| WIP Quantity | Quantity in progress at each process |
+| Flow Time | Flow time at each process |
+| Accumulation Status | Accumulation status at each process |
+
+## 7. Production Statistics and Analysis
+
+### 7.1 Production Reports
+
+| Report Type | Description | Target User |
+|-------------|-------------|-------------|
+| Daily Production Report | Daily production statistics | Workshop Supervisor |
+| Monthly Production Report | Monthly production statistics | Production Manager |
+| Work Order Statistics | Work order execution statistics | Planner |
+| Output Statistics | Output completion statistics | Production Supervisor |
+| Quality Statistics | Production quality statistics | Quality Supervisor |
+
+### 7.2 Production Indicators
+
+**Core KPI Indicators:**
+
+| Indicator | Calculation Formula | Description |
+|-----------|---------------------|-------------|
+| Output Achievement Rate | Actual Output/Plan Output × 100% | Target: ≥100% |
+| Production Qualification Rate | Qualified Quantity/Total Quantity × 100% | Target: ≥98% |
+| Labor Utilization Rate | Actual Working Hours/Available Hours × 100% | Target: ≥85% |
+| Process Flow Time | Average flow time at each process | Shorter is better |
+| WIP Turnover | WIP Quantity/Daily Output | Target: 3-5 days |
+
+### 7.3 Production Analysis
+
+**Analysis Dimensions:**
+
+| Analysis Dimension | Analysis Content |
+|-------------------|------------------|
+| Capacity Analysis | Capacity utilization, bottleneck analysis |
+| Efficiency Analysis | OEE analysis, efficiency improvement potential |
+| Quality Analysis | Defective product analysis, quality trend |
+| Material Analysis | Material consumption analysis, over-consumption analysis |
+| Labor Analysis | Working hours utilization analysis, overtime analysis |
+
+---
+
+**End of Production Management**
\ No newline at end of file
diff --git a/en/business/quality.md b/en/business/quality.md
new file mode 100644
index 0000000..01d2936
--- /dev/null
+++ b/en/business/quality.md
@@ -0,0 +1,452 @@
+# Quality and Traceability
+
+## 1. Function Overview
+
+The Quality Management module implements full-process quality control from raw materials to finished products, including incoming inspection, in-process inspection, finished product inspection, quality exception handling, and traceability management, ensuring stable and controllable product quality.
+
+**Core Functions:**
+
+| Function | Description |
+|----------|-------------|
+| Inspection Standards | Inspection items and standards definition |
+| IQC Inspection | Incoming quality control |
+| IPQC Inspection | In-process quality control |
+| FQC/OQC | Finished/Outgoing inspection |
+| Quality Exception | Defective product handling, MRB management |
+| Quality Traceability | Forward/Reverse traceability |
+
+## 2. Quality Management System
+
+### 2.1 Quality Management Process
+
+**Total Quality Management Process:**
+
+```
+Raw Material Inspection → Production Process Control → Finished Product Inspection → Outgoing Inspection
+ │ │ │ │
+ ▼ ▼ ▼ ▼
+ IQC IPQC FQC OQC
+```
+
+### 2.2 Quality Management Principles
+
+| Principle | Description |
+|-----------|-------------|
+| Prevention First | Move quality control to design and production stages |
+| Total Participation | Quality is everyone's responsibility |
+| Process Control | Focus on every step of the production process |
+| Continuous Improvement | Continuously optimize quality management system |
+| Data Driven | Make decisions based on data analysis |
+
+## 3. Inspection Standard Management
+
+### 3.1 Inspection Standard Definition
+
+**Inspection Standard Components:**
+
+| Component | Description |
+|-----------|-------------|
+| Inspection Type | IQC/IPQC/FQC/OQC |
+| Inspection Item | Specific item to inspect |
+| Inspection Method | How to perform inspection |
+| Judgment Standard | Criteria for pass/fail determination |
+| Inspection Equipment | Required inspection equipment |
+| Sampling Plan | Sampling quantity and rules |
+
+### 3.2 Inspection Item Types
+
+| Item Type | Description | Example |
+|-----------|-------------|---------|
+| Visual Inspection | Visual check | Color, shape, surface quality |
+| Dimension Inspection | Dimension measurement | Length, width, height, diameter |
+| Function Inspection | Function test | Electrical performance, mechanical performance |
+| Performance Inspection | Performance test | Life, reliability |
+| Safety Inspection | Safety test | Insulation, withstand voltage |
+
+### 3.3 Inspection Standard Creation
+
+**Creation Steps:**
+
+1. Go to [Quality Management] → [Inspection Standards]
+2. Click [New Inspection Standard]
+3. Fill in standard information:
+ - Standard code
+ - Standard name
+ - Applicable product
+ - Inspection type
+4. Add inspection items
+5. Define inspection methods
+6. Set judgment standards
+7. Save inspection standard
+
+**[Tip]** Inspection standards need approval before becoming effective.
+
+### 3.4 Sampling Plan
+
+**Sampling Standards:**
+
+| Sampling Standard | Description | Application Scenario |
+|-------------------|-------------|---------------------|
+| GB/T 2828.1 | Normal inspection single sampling plan | Regular inspection |
+| GB/T 2829 | Periodic inspection sampling plan | Periodic sampling |
+| AQL Sampling | Acceptable quality level sampling | Large batch inspection |
+| 100% Inspection | Full inspection | Critical items |
+
+**AQL Standard Example:**
+
+| Inspection Lot Size | AQL 1.0 | AQL 2.5 | AQL 4.0 |
+|---------------------|---------|---------|---------|
+| 26-50 | 3 | 5 | 7 |
+| 51-90 | 5 | 7 | 10 |
+| 91-150 | 8 | 12 | 18 |
+| 151-280 | 13 | 18 | 25 |
+
+## 4. Incoming Quality Control (IQC)
+
+### 4.1 IQC Process
+
+**IQC Complete Process:**
+
+```
+┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
+│ Arrival │───▶│Receiving │───▶│ IQC │───▶│ Judgment │
+│ Receive │ │Document │ │ Inspection│ │ │
+└──────────┘ └──────────┘ └──────────┘ └──────────┘
+ │
+ ▼
+ ┌──────────────────────────────────┐
+ │ Non-conforming Handling │
+ │ ┌──────┐ ┌──────┐ ┌──────┐ │
+ │ │Return │ │Concession│ │Scrap │ │
+ │ │ │ │Acceptance│ │ │ │
+ │ └──────┘ └──────┘ └──────┘ │
+ └──────────────────────────────────┘
+```
+
+### 4.2 IQC Inspection Execution
+
+**Inspection Steps:**
+
+1. Supplier delivery arrives
+2. Warehouse clerk creates receiving document
+3. System automatically pushes inspection task to IQC
+4. IQC inspector receives inspection task
+5. Execute incoming inspection:
+ - Verify delivery note against order
+ - Visual inspection
+ - Quantity verification
+ - Sampling inspection
+6. Record inspection data
+7. Determine inspection result
+
+**Inspection Judgment:**
+
+| Judgment Result | Description | Handling Method |
+|-----------------|-------------|-----------------|
+| Qualified | Accept for storage | Direct receiving |
+| Concession Acceptance | Special release | Requires approval |
+| Rejected | Return to supplier | Return to supplier |
+
+### 4.3 IQC Inspection Record
+
+**Inspection Record Information:**
+
+| Record Item | Description |
+|-------------|-------------|
+| Inspection No. | IQC inspection document number |
+| Supplier | Material supplier |
+| Material Code | Material being inspected |
+| Material Batch | Material batch number |
+| Arrival Quantity | Arrival quantity |
+| Sampling Quantity | Sampled quantity |
+| Qualified Quantity | Qualified quantity |
+| Defective Quantity | Defective quantity |
+| Qualification Rate | Qualified quantity/Sampling quantity |
+| Inspection Conclusion | Qualified/Unqualified |
+| Inspector | Person performing inspection |
+| Inspection Time | Inspection time |
+
+## 5. In-Process Quality Control (IPQC)
+
+### 5.1 IPQC Types
+
+| Inspection Type | Timing | Description |
+|-----------------|--------|-------------|
+| First Article Inspection | At start of each batch | Inspection of first product |
+| Patrol Inspection | During production | Regular patrol inspection |
+| Sampling Inspection | Per sampling plan | Random sampling inspection |
+| Last Article Inspection | At end of each batch | Inspection of last product |
+
+### 5.2 First Article Inspection
+
+**First Article Inspection Process:**
+
+```
+Start Production → First Article Production → First Article Inspection → Qualified → Mass Production
+ │
+ ▼
+ Unqualified
+ │
+ ▼
+ Root Cause Analysis & Correction
+```
+
+**First Article Inspection Timing:**
+
+| Timing | Description |
+|--------|-------------|
+| Shift Change | First after shift handover |
+| Material Change | First after material change |
+| Process Change | First after process adjustment |
+| After Equipment Repair | First after equipment repair |
+
+### 5.3 Patrol Inspection Management
+
+**Patrol Inspection Points:**
+
+| Inspection Item | Check Content | Check Method |
+|-----------------|---------------|--------------|
+| Process Parameters | Temperature, pressure, time | Check equipment parameters |
+| Material Usage | Correct material usage | Verify material identification |
+| Operation Method | Standard operation | Observe operation process |
+| Product Appearance | Normal appearance | Visual inspection |
+| Equipment Status | Normal equipment operation | Check equipment running status |
+
+**Patrol Inspection Record:**
+
+| Record Item | Description |
+|-------------|-------------|
+| Inspection Time | Inspection time |
+| Inspection Station | Station being inspected |
+| Inspector | Person performing inspection |
+| Inspection Item | Item being checked |
+| Check Result | Inspection result |
+| Abnormal Description | Issues found (if any) |
+
+## 6. Finished Product Inspection (FQC/OQC)
+
+### 6.1 FQC (Final Quality Control)
+
+**FQC Inspection Content:**
+
+| Inspection Category | Inspection Item |
+|---------------------|-----------------|
+| Visual Inspection | Color, marking, packaging |
+| Dimension Inspection | External dimensions |
+| Function Inspection | Electrical performance test |
+| Safety Inspection | Safety item test |
+| Reliability Inspection | Aging test, etc. |
+
+### 6.2 OQC (Outgoing Quality Control)
+
+**OQC Inspection Content:**
+
+| Inspection Item | Description |
+|-----------------|-------------|
+| Quantity Verification | Verify outgoing quantity |
+| Visual Check | Check packaging appearance |
+| Marking Check | Check labels and markings |
+| Random Sampling | Sampling per sampling plan |
+| Documentation Check | Check accompanying documents |
+
+### 6.3 Finished Product Receiving Process
+
+**Receiving Conditions:**
+
+```
+FQC Passed → OQC Passed → Packaging Complete → Finished Product Receiving
+```
+
+**Receiving Requirements:**
+
+| Requirement | Description |
+|-------------|-------------|
+| Inspection Complete | FQC/OQC inspection must be completed |
+| Inspection Qualified | Inspection result must be qualified |
+| Batch Identification | Must have batch identification |
+| Packaging Complete | Packaging must be intact |
+| Quantity Accurate | Quantity must be accurate |
+
+## 7. Quality Exception Handling
+
+### 7.1 Defective Product Classification
+
+| Defect Category | Description | Handling Method |
+|-----------------|-------------|-----------------|
+| Visual Defect | Color, shape, surface defects | Rework/Scrap |
+| Dimension Defect | Dimension out of tolerance | Rework/Downgrade |
+| Function Defect | Function not meeting standard | Rework/Scrap |
+| Performance Defect | Performance not meeting standard | Rework/Downgrade |
+| Safety Defect | Safety hazard | Scrap |
+
+### 7.2 MRB Handling Process
+
+**MRB Process:**
+
+```
+┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
+│Defective │───▶│ MRB │───▶│ Review │───▶│ Disposal │
+│Identify │ │ Initiate│ │ Judgment │ │ Execution│
+└──────────┘ └──────────┘ └──────────┘ └──────────┘
+```
+
+**MRB Disposal Methods:**
+
+| Disposal Method | Description | Approval Requirement |
+|-----------------|-------------|---------------------|
+| Rework | Return to process for reprocessing | Requires approval |
+| Downgrade | Use at lower grade | Requires approval |
+| Concession Acceptance | Accept under special circumstances | Senior management approval |
+| Scrap | Direct scrap | Requires approval |
+| Return | Return to supplier | Contact supplier |
+
+### 7.3 Quality Exception Handling Steps
+
+**Handling Steps:**
+
+1. Discover quality issue
+2. Isolate non-conforming products
+3. Label non-conforming products
+4. Create MRB document
+5. Quality review
+6. Determine review result
+7. Execute disposal plan
+8. Confirm disposal
+
+**[Tip]** Non-conforming products must be stored in isolation to prevent misuse.
+
+## 8. Quality Traceability
+
+### 8.1 Traceability Content
+
+**Traceability Data Elements:**
+
+| Traceability Element | Traceability Content |
+|---------------------|---------------------|
+| Material Origin | Raw material supplier, batch |
+| Production Process | Process, equipment, personnel |
+| Quality Data | Inspection records, defective products |
+| Equipment Data | Equipment parameters, status |
+| Environmental Data | Production environment conditions |
+
+### 8.2 Forward Traceability
+
+**Forward Traceability Process:**
+
+```
+Material Batch → Semi-finished Batch → Finished Product Batch → Customer
+```
+
+**Traceability Query:**
+
+1. Input finished product batch number
+2. Query finished product production information:
+ - Production work order
+ - Production process
+ - Production time
+ - Operator
+ - Equipment used
+3. Query materials used:
+ - Material batch
+ - Supplier
+ - IQC inspection result
+4. Continue tracing upstream materials
+
+### 8.3 Reverse Traceability
+
+**Reverse Traceability Process:**
+
+```
+Finished Product Batch → Semi-finished Batch → Material Batch → Supplier
+```
+
+**Traceability Query:**
+
+1. Input material batch number
+2. Query material usage:
+ - Work orders used in
+ - Processes used in
+ - Finished product batches produced
+3. Query finished product destination:
+ - Shipping records
+ - Customer information
+
+### 8.4 Traceability Query Example
+
+**Query Scenario:** Customer complaint about quality issue in a product batch
+
+**Traceability Steps:**
+
+1. Query using batch number provided by customer
+2. Trace this batch's:
+ - Production work order information
+ - Production status at each process
+ - Material batches used
+ - Material suppliers
+ - Quality inspection records
+3. Analyze quality issue root cause
+4. Determine impact scope
+5. Notify affected customers
+6. Develop improvement measures
+
+**Traceability Result Example:**
+
+| Item | Information |
+|------|-------------|
+| Finished Product Batch | LOT-20260410-001 |
+| Product Model | PCB-1000 |
+| Production Work Order | WO-20260410001 |
+| Production Date | 2026-04-10 |
+| Production Line | SMT-A Line |
+| Operators | Zhang San, Li Si |
+| Materials Used | Solder batch LOT-S-001 (Supplier: Company A) |
+| Inspection Records | First article qualified, patrol inspection qualified |
+| Shipping Records | Shipped to Customer B, quantity 1000PCS |
+
+## 9. Quality Statistics and Analysis
+
+### 9.1 Quality Indicators
+
+**Core Quality KPIs:**
+
+| Indicator | Calculation Formula | Target Value |
+|-----------|---------------------|--------------|
+| Incoming Qualification Rate | IQC Qualified Lots/IQC Total Lots × 100% | ≥98% |
+| Process Qualification Rate | IPQC Qualified Quantity/IPQC Total Inspected × 100% | ≥99% |
+| Finished Product Qualification Rate | FQC Qualified Quantity/FQC Total Inspected × 100% | ≥99.5% |
+| Defective Rate | Defective Quantity/Total Production × 100% | ≤1% |
+| Batch Traceability Rate | Successfully Traced Batches/Total Batches × 100% | 100% |
+
+### 9.2 Quality Reports
+
+| Report Type | Description | Target User |
+|-------------|-------------|-------------|
+| IQC Daily Report | Daily incoming inspection statistics | IQC Team Leader |
+| IPQC Daily Report | Daily in-process inspection statistics | IPQC Team Leader |
+| Quality Monthly Report | Monthly quality summary report | Quality Manager |
+| Defect Analysis | Defect root cause analysis | Quality Engineer |
+| Trend Analysis | Quality trend analysis | Quality Supervisor |
+
+### 9.3 SPC Statistical Process Control
+
+**Control Chart Monitoring:**
+
+| Control Chart Type | Monitoring Content | Application Scenario |
+|--------------------|-------------------|---------------------|
+| X-bar Chart | Mean value monitoring | Measurement data |
+| R Chart | Range monitoring | Measurement data |
+| P Chart | Defective rate monitoring | Count data |
+| C Chart | Defect count monitoring | Count data |
+
+**异常判定规则:**
+
+| Rule | Judgment Condition | Description |
+|------|-------------------|-------------|
+| Rule 1 | 1 point outside control limits | Single point abnormality |
+| Rule 2 | 9 consecutive points on same side of center line | Shift abnormality |
+| Rule 3 | 6 consecutive points increasing or decreasing | Trend abnormality |
+| Rule 4 | 14 consecutive points alternating up and down | Periodic abnormality |
+
+---
+
+**End of Quality and Traceability**
\ No newline at end of file
diff --git a/en/data_middleground/battery_curve.md b/en/data_middleground/battery_curve.md
new file mode 100644
index 0000000..7e30824
--- /dev/null
+++ b/en/data_middleground/battery_curve.md
@@ -0,0 +1,163 @@
+# Battery Curve
+
+## 1. Function Overview
+
+The Battery Curve module belongs to the Basic Traceability module of the MES system's Data Middle Platform. It is used to query the charge/discharge curve data of batteries in each process, displaying the changing trends of voltage, current, and capacity over time in visual charts. This helps process and quality personnel analyze battery performance.
+
+**Core Functions:**
+
+- Battery Process Query: Query all process records of a battery by battery ID
+- Curve Chart Display: Display voltage, current, and capacity curves using multi-axis line/bar charts
+- Chart Interaction: Support zoom, save chart as image, and other interactive functions
+- Tray Curve View: Support jumping to external curve viewer to view curve data of all batteries in a tray
+- Data Export: Support exporting all curve data files of the current process as a ZIP package
+
+**Screenshots:**
+
+
+

+
Figure 1 Battery Curve Page
+
+
+## 2. Term Definitions
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Battery Curve | The charge/discharge data curve of a battery during processes | Includes three curves: voltage, current, and capacity |
+| Battery ID | Unique identifier for a battery in the system | Entry point for querying battery curve data |
+| Voltage Curve | Voltage change over time | Y-axis unit: millivolt (mV) |
+| Current Curve | Charge/discharge current change over time | Y-axis unit: milliampere (mA) |
+| Capacity Curve | Accumulated charge/discharge capacity over time | Y-axis unit: milliampere-hour (mAH), displayed as bar chart |
+| Tray Curve | Curve data of all batteries in the same tray | Opened through external curve viewer |
+
+## 3. Battery Curve Query
+
+### 3.1 Query Description
+
+By entering a battery ID, the system queries the charge/discharge records of the battery across all processes, displaying them as a process list on the left and curve charts on the right.
+
+**Query Conditions:**
+
+| Condition | Description | Required |
+|-----------|-------------|----------|
+| Battery ID | Enter the battery ID to query | Yes |
+
+### 3.2 Query Steps
+
+1. Go to [Data Middle Platform] → [Basic Traceability] → [Battery Curve]
+2. Enter the battery ID in the search box
+3. Click [Query] button
+4. The left panel shows the process record list for this battery, displaying batch name, process name, and upload time
+5. Click on a process record on the left to display the corresponding charge/discharge curve chart on the right
+
+**Screenshots:**
+
+
+

+
Figure 1 Battery Curve Query Display
+
+
+### 3.3 Process Record List
+
+After a successful query, the left panel displays all process records of the battery as a menu list.
+
+**List Fields:**
+
+| Field | Description |
+|-------|-------------|
+| Batch Name | Production batch of the battery |
+| Process Name | Process name for this record |
+| Upload Time | Upload time of this process data |
+
+**Screenshots:**
+
+
+

+
Figure 1 Battery Curve Process List
+
+
+## 4. Curve Chart Display
+
+### 4.1 Chart Description
+
+After clicking on a process record on the left, the right panel displays the charge/discharge curve chart for that process. Basic information of the record is shown at the top of the chart.
+
+**Basic Information:**
+
+| Field | Description |
+|-------|-------------|
+| Equipment ID | Equipment ID that executed this process |
+| Battery Sequence | Battery sequence number in the equipment channel |
+
+### 4.2 Curve Data Description
+
+The chart displays three data curves simultaneously, each with its own Y-axis scale:
+
+| Curve | Display Type | Y-axis Unit | Description |
+|-------|-------------|------------|-------------|
+| Current Curve | Line chart, green | mA (milliampere) | Left primary Y-axis, reflects charge/discharge current changes |
+| Voltage Curve | Line chart, blue | mV (millivolt) | Left secondary Y-axis, reflects battery voltage changes |
+| Capacity Curve | Bar chart, orange | mAH (milliampere-hour) | Right Y-axis, reflects capacity accumulation |
+
+**Screenshots:**
+
+
+

+
Figure 1 Battery Curve Data
+
+
+### 4.3 Chart Interaction Operations
+
+| Operation | Description |
+|-----------|-------------|
+| Legend Toggle | Click legend to show/hide corresponding curve (capacity curve hidden by default) |
+| Zoom | Use mouse wheel or drag to select area for detailed view |
+| Data Hover | Hover over curves to view specific values |
+| Save Image | Click save button in toolbar to save current chart as image |
+
+## 5. Tray Curve View
+
+### 5.1 Function Description
+
+In addition to viewing individual battery curve data, users can view curve data of all batteries in the same tray for a process by calling the external curve viewer program.
+
+### 5.2 Operation Steps
+
+1. In the left process list, select the process record to view
+2. Click [View Tray Curve] button at the top right
+3. The system launches the external curve viewer (Curve Viewer) to display the complete curve data of the entire tray
+
+**[Note]** This function requires the curve viewer program to be installed locally.
+
+**Screenshots:**
+
+
+

+
Figure 1 Tray Curve View 1
+
+
+
+

+
Figure 2 Tray Curve View 2
+
+
+## 6. Data Export
+
+### 6.1 Export Description
+
+Supports exporting all raw curve data files of the currently selected process as a ZIP package, including all `.dat` and `.kdat` data files from all equipment in this process, facilitating offline analysis.
+
+### 6.2 Export Steps
+
+1. In the left process list, select the process record to export
+2. Click [Export All Data] button at the top right
+3. The system automatically packages and downloads the ZIP file
+
+**[Note]** A process record must be selected in the left list before exporting, otherwise a prompt "Please query battery information first" will appear.
+
+**Screenshots:**
+
+
+

+
Figure 1 Export Tray Curve Data
+
\ No newline at end of file
diff --git a/en/data_middleground/battery_detail_report.md b/en/data_middleground/battery_detail_report.md
new file mode 100644
index 0000000..b1c189d
--- /dev/null
+++ b/en/data_middleground/battery_detail_report.md
@@ -0,0 +1,352 @@
+# Battery Detail Report
+
+## 1. Function Overview
+
+The Battery Detail Report belongs to the Report Analysis module of the MES system's Data Middle Platform. It is used to query detailed result parameter data of batteries in each process based on **Process Flow + Batch + Process** dimensions. The system dynamically generates multi-level headers based on user-selected processes, displaying the set values and actual result parameters of each process in tabular form. It supports flexible filtering of process result parameters, filtering by process completion time, and exporting large volumes of data as CSV files.
+
+**Core Functions:**
+
+- Process Flow Linked Filtering: Hierarchical linked selection by process flow category → process flow → batch → process to quickly locate target data range
+- Process Parameter Dynamic Selection: Dynamically loads the result parameter tree for each process based on selected processes, allowing users to freely select parameter columns to display
+- Multi-level Header Display: Automatically generates nested multi-level headers based on process type (regular process / formation-capacity multi-step process), clearly showing the hierarchical relationship of process → step → result parameter
+- Time Range Filtering: Uses the completion time of the last selected process as the filtering condition to accurately locate production data within the time period
+- Data Export: Supports exporting full data under query conditions as CSV files through asynchronous tasks, suitable for large-scale data analysis
+
+**Screenshots:**
+
+
+

+
Figure 1 Battery Detail Report Page
+
+
+## 2. Term Definitions
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Battery Detail Report | Report for querying battery result parameters by batch and process dimensions | Core function of the Report Analysis module in Data Middle Platform |
+| Process Flow | Defines the complete processing sequence from raw materials to finished products | Primary dimension of filtering conditions, grouped by process flow category |
+| Batch | Minimum execution unit in production planning | Secondary dimension of filtering conditions, one batch relates to one process flow |
+| Process | A processing step in the process flow | Tertiary dimension of filtering conditions, supports multiple selection |
+| Process Parameter | Actual result data recorded after process completion | Such as voltage, current, capacity, internal resistance, etc., users can selectively display |
+| Multi-step Process | A process containing multiple steps (e.g., formation, capacity grading) | Result parameters are split by step, e.g., voltage01, voltage02 |
+| Single-step Result Parameter | Process result parameters that do not change with steps | Such as start time, end time, equipment ID, etc. |
+| Process End Time | Completion time of a process (finish_time) | Filtering basis for time range, based on the completion time of the last selected process |
+| Grade/Grade Category | Capacity grade classification of batteries | Such as K1, K2, F1, etc. |
+| Export Task | Asynchronous large data export task mechanism | View progress and download in "System Download Tasks" at the top of the system |
+
+**Data Model Relationship Diagram:**
+
+```mermaid
+flowchart TB
+ subgraph Filter Dimensions
+ FC[Process Flow Category]
+ TF[Process Flow]
+ BA[Batch]
+ PR[Process]
+ end
+
+ subgraph Data Sources
+ BPL[Battery Process Aggregation Log
hf_mes_bkv_batch_process_log]
+ BKV[Battery Result Data Shard Table
hf_mes_tmp_bkv_subbatch]
+ end
+
+ subgraph Process Related
+ WS[Process Working Unit
ProcessWorkingsubclass]
+ RP[Process Result Parameter
TechnologyProcessResultParam]
+ DP[Default Result Parameter
DefaultResultParam]
+ PS[Process Set Values
setting field]
+ end
+
+ FC -->|1:N| TF
+ TF -->|1:N| BA
+ TF -->|1:N| PR
+ PR -->|Relate| WS
+ PR -->|Has| RP
+ WS -->|Preset| DP
+ PR -->|Configure| PS
+
+ BA -->|Produce| BPL
+ BPL -->|Relate Query| BKV
+```
+
+**Relationship Descriptions:**
+
+| Relationship Type | Description |
+|-------------------|-------------|
+| Process Flow Category → Process Flow | **1 to N**: One process flow category contains multiple process flows |
+| Process Flow → Batch | **1 to N**: One process flow can be referenced by multiple batches |
+| Process Flow → Process | **1 to N**: One process flow contains multiple processes |
+| Process → Process Unit | **N to 1**: Each process relates to one process unit |
+| Process → Process Result Parameter | **1 to N**: Each process can configure multiple result parameters |
+| Process Unit → Default Result Parameter | **1 to N**: Each process unit can preset multiple default result parameters |
+| Batch → Battery Process Log | **1 to N**: One batch contains multiple battery process log records |
+| Battery Process Log → Battery Result Data | **1 to 1**: Each log relates to one battery result data record (routed by subbatch) |
+
+**Simplified Relationship Diagram:**
+
+```mermaid
+flowchart LR
+ A[Process Flow Category] -->|1:N| B[Process Flow]
+ B -->|1:N| C[Batch]
+ B -->|1:N| D[Process]
+ D -->|Relate| E[Process Unit]
+ E -->|Preset| F[Default Result Parameter]
+ C -->|Query| G[Battery Process Log]
+ G -->|Relate| H[Battery Result Data]
+```
+
+## 3. Battery Detail Report Interaction Flow
+
+### 3.1 Filter Condition Setting
+
+#### 3.1.1 Filter Condition Description
+
+The left panel provides hierarchical linked filter conditions. Users need to select in the order of "Process Flow → Batch → Process", and the system dynamically loads options for the next level based on the previous selection.
+
+**Screenshots:**
+
+
+

+
Figure 1 Filter Condition Panel
+
+
+#### 3.1.2 Process Flow Selection
+
+Process flows are displayed grouped by **Process Flow Category** for quick location.
+
+**Operation Steps:**
+
+1. Go to [Data Middle Platform] → [Report Analysis] → [Battery Detail Report]
+2. In the left [Filter Conditions] panel, browse the [Process Flow] dropdown grouped by process flow category
+3. Select the target process flow
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Process Flow | List of process flows grouped by process flow category, loads batches and processes upon selection | Yes |
+
+**[Note]** After switching process flows, the selected batches and processes will be cleared and need to be reselected.
+
+#### 3.1.3 Batch Selection
+
+**Operation Steps:**
+
+1. After selecting a process flow, the [Batch] dropdown automatically loads all batches under that process flow
+2. Select the target batch from the dropdown list, supports keyword filtering
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Batch | List of production batches under the selected process flow | Yes |
+
+#### 3.1.4 Process Selection
+
+**Operation Steps:**
+
+1. After selecting a process flow, the [Process] dropdown automatically loads all processes under that process flow
+2. Supports multiple selection (can check multiple processes), and the process parameter tree on the right will update dynamically
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Process | List of processes under the selected process flow, supports multiple selection | Yes (required for query) |
+
+**[Note]** NG judgment processes (NG01~NG05) and sorting processes (SELECTION) are not displayed in the filter list.
+
+### 3.2 Process Parameter Selection
+
+#### 3.2.1 Process Parameter Description
+
+Process parameters are actual result data recorded during each process operation. The system dynamically loads result parameters for the selected processes and displays them in a tree structure. Users can freely check parameter columns to display in the report.
+
+**Screenshots:**
+
+
+

+
Figure 1 Process Selection Panel
+
+
+
+

+
Figure 2 Process Data Filter Panel
+
+
+#### 3.2.2 Process Parameter Tree Operations
+
+**Operation Steps:**
+
+1. Check target processes in the filter conditions
+2. The [Process Parameters] area on the left automatically loads the result parameter tree for selected processes
+3. Check parameter items to display, supports parent-child cascade checking
+4. Use the search box to quickly locate parameters by keyword
+
+**Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Process Name (Parent Node) | Name of the process, e.g., "OCV1", "Capacity Grading" |
+| Result Parameter (Child Node) | Result parameters under this process, e.g., voltage, current, internal resistance |
+
+**[Important]** If no process parameters are checked, the result parameter columns for that process will not be displayed during query.
+
+### 3.3 Query Result Display
+
+#### 3.3.1 Query Operation Steps
+
+1. Complete filter condition settings (process flow, batch, process) and process parameter selection
+2. Set query conditions in the upper right panel:
+ - **Process End Time**: Select time range, system uses completion time of the last selected process as filter condition
+ - **Tray**: Optional, filter by tray number exactly
+3. Click [Query] button
+4. System generates multi-level headers and loads data
+
+**Query Condition Description:**
+
+| Condition | Description | Required |
+|-----------|-------------|----------|
+| Process End Time | Uses completion time (finish_time) of the last selected process as time range condition | Yes |
+| Tray | Enter tray number for exact filtering | No |
+
+> **Process End Time Rules:**
+> - If processes are selected, uses completion time of the **last** selected process as filter condition
+> - If no process is selected (using all processes), uses completion time of the **last process** in the process flow as filter condition
+
+**Screenshots:**
+
+
+

+
Figure 1 Query Conditions and Results
+
+
+#### 3.3.2 Table Header Structure
+
+The table uses a **multi-level nested header** structure with three layers:
+
+**Layer 1 - Process Layer:**
+Uses each process name as the primary column header, e.g., "OCV1", "Capacity Grading", "DCIR".
+
+**Layer 2 - Step Layer (Formation/Capacity Processes Only):**
+For multi-step processes like formation (FORMATION/HC), capacity grading (FR), and pre-formation (FORMATION_SS), expands secondary column headers by step under the process, e.g., "Step 1: Rest", "Step 2: CC/CV Charge".
+
+**Layer 3 - Parameter Layer:**
+Specific result parameters under each process (or step), e.g., voltage, current, capacity, internal resistance.
+
+**Basic Information Columns (Fixed Display):**
+
+| Column Name | Description |
+|-------------|-------------|
+| Battery ID | Unique identifier for battery in system |
+| Batch No. | Production batch of battery |
+| Battery Model | Product model code |
+| Process Flow | Process flow name associated with batch |
+| Tray No. | Tray number of battery |
+| Serial No. | Serial number of tray within batch |
+| Activation Status | Current status: Activated / Not Activated |
+| Grade Category | Capacity grade category of battery |
+| Grade | Specific grade level (e.g., K1, K2, F1) |
+
+**Special Note for Formation/Capacity Processes:**
+
+Formation and capacity grading processes contain multiple steps (rest, CC/CV charge, CC/CV discharge, CC discharge, CC charge, cycle), with result parameters recorded independently for each step. The system dynamically generates corresponding columns based on step configurations in process set values (setting).
+
+For example, a capacity grading process with 5 steps, each recording voltage (VOL), current (CUR), and capacity (CAP), dynamically generates:
+
+| Step 1: Rest | | | Step 2: CC/CV Charge | | | ... |
+|:---:|:---:|:---:|:---:|:---:|:---:|
+| VOL01 | CUR01 | CAP01 | VOL02 | CUR02 | CAP02 | ... |
+
+**Single-step Result Parameters:**
+
+Some result parameters do not change with steps (is_only = 1), such as start time (START_TIME), end time (FINISH_TIME), and equipment ID (DEVICE_CODE). These parameters are displayed directly at the process level, not under specific steps.
+
+#### 3.3.3 Data Source Description
+
+Query results come from the following data tables:
+
+| Table | Description |
+|-------|-------------|
+| Battery Process Aggregation Log Table | Records completion status, completion time, grade, etc. for each battery in each process |
+| Battery Result Data Shard Table | Stores detailed result parameter values (e.g., voltage, current) partitioned by subbatch |
+| Production Batch Table | Provides process flow and product model association information for batches |
+
+The system first queries the aggregation log table to obtain the battery list, then routes to the corresponding result data shard table based on each battery's subbatch to retrieve parameter values for each process.
+
+### 3.4 Data Export
+
+#### 3.4.1 Export Description
+
+The system uses an **asynchronous task export** mechanism. Export requests are first created as background tasks, and users can view task progress and download generated files in "System Download Tasks" at the top of the system. Export format is CSV.
+
+#### 3.4.2 Export Steps
+
+1. Set filter conditions (process flow, batch, process, time range, and process parameters)
+2. Click [Export] button
+3. System pops up confirmation prompt: "Data export requires creating a download task first, continue?"
+4. Click [OK], system creates background export task
+5. Go to [System Download Tasks] in the top menu to view task progress
+6. After task completion, click download to get CSV file
+
+**[Note]** A batch must be selected before exporting, otherwise export will fail.
+
+#### 3.4.3 Export File Format
+
+The exported CSV file also uses a multi-level header structure:
+
+| Level | Description | Example |
+|-------|-------------|---------|
+| Row 1 (Level 1 Header) | Process names | OCV1, , , Capacity Grading, , , , , , |
+| Row 2 (Level 2 Header) | Step names (multi-step processes only) | , , , Step 1: Rest, , , Step 2: CC/CV Charge |
+| Row 3 (Level 3 Header) | Specific result parameter names | Battery ID, Batch No., ..., Voltage, Current, Voltage, Current |
+
+**[Important]** For batches with large data volume, the system automatically splits data into multiple CSV files and merges them into a complete CSV file for download.
+
+**Screenshots:**
+
+
+

+
Figure 1 Export Data
+
+
+
+

+
Figure 2 Get Export File
+
+
+### 3.5 Pagination
+
+Query results support pagination, with the system defaulting to 10 records per page. Users can switch pages and adjust page size at the bottom of the table.
+
+**Pagination Operations:**
+
+- Click page numbers to switch pages
+- Modify records per page
+- System automatically reloads data for the corresponding page
+
+**[Note]** No need to click query again when switching pages; the system automatically loads data for the current filter conditions.
+
+---
+
+## 4. Common Issues
+
+### 4.1 Why are there no batches available after selecting a process flow?
+
+Please confirm whether production batches have been created under this process flow. Batches need to be created and associated with process flows in [Production Batch Management].
+
+### 4.2 Why is the process parameter tree empty?
+
+Please first check target processes in the filter conditions. The process parameter tree dynamically loads corresponding result parameters based on selected processes. If the parameter tree is still empty after checking processes, please confirm whether result parameters have been configured for those processes in [Process Model].
+
+### 4.3 Why does querying formation/capacity processes report "set values empty"?
+
+Formation and capacity processes require configuring process set values (step information) in [Process Model] → [Process Details], otherwise the system cannot determine the number and types of steps, and the report cannot be generated. Please contact the system administrator for configuration.
+
+### 4.4 Why do exported CSV files have different columns than what's displayed on the page?
+
+Export will export **all result parameters** of selected processes (no longer affected by the page's process parameter tree selection), while page display only shows checked parameter columns. Export is based on complete data.
+
+### 4.5 Where can I download after creating an export task?
+
+Find [System Download Tasks] in the top menu bar. After entering, you can view the status and progress of all export tasks, and download when the task is complete.
\ No newline at end of file
diff --git a/en/data_middleground/battery_traceability.md b/en/data_middleground/battery_traceability.md
new file mode 100644
index 0000000..c659ff6
--- /dev/null
+++ b/en/data_middleground/battery_traceability.md
@@ -0,0 +1,222 @@
+# Battery Traceability
+
+## 1. Function Overview
+
+Battery Traceability belongs to the Basic Traceability module of the MES system's Data Middle Platform. It is used to query battery information such as registration batch, tray location, activation status, good/NG judgment, etc., based on **battery ID**. Users can also access the battery detail page to view process set values and result parameter data for the battery across all processes.
+
+**Core Functions:**
+
+- Battery Information Query: Query basic information and production status of batteries by battery ID
+- Process Tree Display: Intuitively display battery BOM material composition structure as an organizational tree
+- Battery Detail View: View detailed process data (set values and result parameters) for each process
+- Assembly Detail View: View material input (In) and output (Out) information for the current process
+- Deactivate: Deactivate an activated battery, preventing it from continuing production
+- Reactivate for Retrial: Reactivate an NG battery to allow it to continue production from the next process
+
+**Screenshots:**
+
+
+

+
Figure 1 Battery Traceability Page
+
+
+## 2. Term Definitions
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Battery Traceability | Query production status and process details of batteries | Starting from battery ID, view complete process data across all processes |
+| Battery ID | Unique identifier for a battery in the system | Query entry condition |
+| Registration Batch | Batch number when battery first registered into the system | Original production batch of the battery |
+| Tray ID | Tray number carrying the battery | Tray location during production line transfer |
+| Serial No. | Serial number within the batch | Sequence number of tray within the batch |
+| Activated | Whether battery is in producible state | Active (producible) / Stopped (non-producible) |
+| Good/NG | Quality judgment result of battery | GOOD (good) / NG (defective) |
+| Grade | Capacity grade of battery | Such as K1, K2, F1, etc. |
+| Process Tab | Process navigation button list on the left in battery details | Click to switch between different process data |
+
+## 3. Battery Traceability Query
+
+### 3.1 Query Description
+
+By entering a battery ID, query basic information including registration batch, tray location, serial number, activation status, good/NG judgment, grade, and current process.
+
+**Query Conditions:**
+
+| Condition | Description | Required |
+|-----------|-------------|----------|
+| Battery ID | Enter the battery ID to trace | Yes |
+
+**[Note]** Can also jump to this page from other pages with battery ID as a route parameter, and the system will automatically execute the query.
+
+### 3.2 Query Steps
+
+1. Go to [Data Middle Platform] → [Basic Traceability] → [Battery Traceability]
+2. Enter the battery ID in the search box
+3. Click [Query] button, system displays battery information list
+
+**Screenshots:**
+
+
+

+
Figure 1 Battery Traceability Query Conditions
+
+
+### 3.3 Query Result Field Description
+
+| Field | Description |
+|-------|-------------|
+| Battery ID | Unique identifier for battery in system |
+| Registration Batch | Production batch number when battery first registered |
+| Tray ID | Tray number of battery |
+| Serial No. | Serial number of tray within batch |
+| Activated | Current status: Activated (green tag) or Stopped (orange tag) |
+| Good/NG | Quality judgment: GOOD (green tag) or NG (orange tag) |
+| Grade | Capacity grade of battery |
+| NG Info | Specific defect reason description for defective products |
+| Current Process ID | Current process ID of battery |
+
+**Screenshots:**
+
+
+

+
Figure 1 Battery Traceability Result List
+
+
+## 4. Battery Details
+
+### 4.1 Details Description
+
+Click [Battery Details] button in the action column to enter the full-screen details page. The page is divided into two areas:
+
+- **Left - Process Tabs**: Display all processes the battery has undergone as buttons
+- **Right - Process Data**: Display detailed process data for the currently selected process
+
+### 4.2 Operation Steps
+
+1. In the query result list, click [Battery Details] button for the target battery row
+2. System enters full-screen details page, left side shows process tab list
+3. First process tab is selected by default, right side shows data for that process
+4. Click other process tabs on the left to switch between different process data
+5. Click the back arrow in the upper left corner to exit the details page
+
+**Screenshots:**
+
+
+

+
Figure 1 Battery Traceability Details Page
+
+
+### 4.3 Process Data Field Description
+
+Process data is displayed in tabular form with three columns: Serial No., Item Name, and Content. Different process types display different data items.
+
+**Common Data Items:**
+
+| Item Name | Description |
+|-----------|-------------|
+| Batch | Production batch of battery |
+
+**Charge/Discharge Process (Capacity Grading) Data Items:**
+
+| Item Name | Description |
+|-----------|-------------|
+| Channel No. | Channel number of battery in equipment |
+| Equipment No. | Equipment number executing this process |
+| Capacity Grade | Capacity grade of battery |
+| Grade | Capacity grade level |
+| Charge End Voltage | Open-circuit voltage after last CC/CV charge |
+| Charge Capacity | Cumulative capacity from multiple CC/CV charges |
+| Original Discharge Capacity | Cumulative original capacity from CC discharge |
+| Discharge Capacity | Cumulative capacity from multiple CC discharges |
+| Charge Start Time | Start time of charge process |
+| Charge End Time | End time of charge process |
+| Discharge Start Time | Start time of discharge process |
+| Discharge End Time | End time of discharge process |
+| Constant Voltage Charge Time | Cumulative CV charge duration (minutes) |
+| Constant Current Charge Time | Cumulative CC charge duration (minutes) |
+| Total Discharge Time | Cumulative CC discharge duration (minutes) |
+| Charge Start Temperature | Temperature at charge start (℃) |
+| Discharge End Temperature | Temperature at discharge end (℃) |
+
+**Shipment Charge/Discharge Process Data Items:**
+
+| Item Name | Description |
+|-----------|-------------|
+| Channel No. | Channel number of battery in equipment |
+| Equipment No. | Equipment number executing this process |
+| Capacity Grade | Capacity grade of battery |
+| Grade | Capacity grade level |
+| Measured Voltage | Voltage after charge |
+| Charge Capacity | Cumulative capacity from CC charge |
+| Charge Start Time | Start time of charge process |
+| Charge End Time | End time of charge process |
+| Constant Voltage Charge Time | Cumulative CV charge duration (minutes) |
+| Constant Current Charge Time | Cumulative CC charge duration (minutes) |
+| Charge Start Temperature | Temperature at charge start (℃) |
+| Discharge End Temperature | Temperature at discharge end (℃) |
+
+**Other Regular Process Data Items:**
+
+Display **result parameters** configured in the process model for that process. Each result parameter name is displayed with its actual collected value. When a result parameter is "defective" or "defective code", the system automatically converts the defective code to the corresponding defect reason description.
+
+**[Note]** Capacity grade and grade information are not displayed for loading processes (DENGLU).
+
+### 4.4 Process Data Search
+
+In the "Item Name" header of the process data table, click the magnifying glass icon to expand the search input box. Enter keywords to quickly filter target data items. Click [Close] button to collapse the search box.
+
+## 5. Deactivate
+
+### 5.1 Function Description
+
+Deactivate is used to set an activated battery to stopped status. After deactivation, the battery can no longer continue production. Use with caution.
+
+### 5.2 Operation Steps
+
+1. In the query result list, find the target battery row (status is "Activated")
+2. Click [Deactivate] button in the action column
+3. System pops up confirmation dialog: "After confirmation, the battery will be deactivated and cannot continue production"
+4. Click [OK] to execute deactivation
+5. After successful operation, the battery's activation status becomes "Stopped"
+
+**[Note]** [Deactivate] button only displays for batteries with status "Activated".
+**[Note]** If no other batteries in the tray are activated after deactivation, the tray will also be stopped.
+
+**Screenshots:**
+
+
+

+
Figure 1 Deactivate Battery
+
+
+## 6. Reactivate for Retrial
+
+### 6.1 Function Description
+
+Reactivate for retrial is used to reactivate a stopped battery that has been judged as NG, allowing it to continue production from the next process. After activation, the battery can only start from the next process and cannot re-execute the current process.
+
+### 6.2 Operation Steps
+
+1. In the query result list, find the target battery row (status is "Stopped" and Good/NG is "NG")
+2. Click [Reactivate for Retrial] button in the action column
+3. System pops up confirmation dialog: "After activation, production can only start from the next process, cannot redo the current process"
+4. Click [OK] to execute reactivation
+5. After successful operation, the page automatically refreshes the query results
+
+**[Note]** [Reactivate for Retrial] button only displays for batteries with status "Stopped" and judgment "NG".
+
+**Screenshots:**
+
+
+

+
Figure 1 Reactivate Battery for Retrial
+
+
+## 7. Related Functions
+
+| Function | Relationship | Description |
+|----------|-------------|-------------|
+| Battery Curve | Complementary | Battery Traceability views process set values and result parameters; Battery Curve views charge/discharge curve data |
+| Tray Traceability | Data Association | Can find battery IDs under a tray through Tray Traceability, then jump to Battery Traceability for details |
+| Production Batch Management | Data Source | Battery batch information comes from the Production Batch Management module |
+| Battery Retrial Management | Function Association | Reactivate operation is related to the retrial process in Battery Retrial Management module
\ No newline at end of file
diff --git a/en/data_middleground/eagle_eyes.md b/en/data_middleground/eagle_eyes.md
new file mode 100644
index 0000000..9a3eec4
--- /dev/null
+++ b/en/data_middleground/eagle_eyes.md
@@ -0,0 +1,198 @@
+# Hawkeye
+
+## 1. Function Overview
+
+Hawkeye is an advanced analytics module in the MES system's Data Middle Platform, designed for statistical correlation analysis between NG (Non-Good/Defective) products and process result parameters across various production stages. The system automatically identifies which process parameters have significant correlations with NG occurrences using two statistical methods: Pearson Correlation Coefficient (PCC) and Chi-Square Test (X²). This helps process engineers quickly identify root causes of defective products and provides data support for process optimization.
+
+**Core Features:**
+
+- NG Correlation Analysis: Select production batches and NG codes to automatically analyze statistical correlations between the NG and all process result parameters
+- Pearson Correlation Analysis (PCC): Display correlation coefficients and p-values in a volcano plot, visually distinguishing significantly correlated from non-correlated parameters
+- Chi-Square Independence Test (X²): Perform chi-square tests on categorical data to determine independence between NG and parameter distributions
+
+**Feature Screenshot**:
+
+
+

+
Figure 1: Correlation Analysis Hawkeye
+
+
+
+## 2. Term Definitions
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Hawkeye | Hawkeye, the NG correlation analysis module in MES system | Advanced analytics feature of the Data Middle Platform |
+| Production Batch | Production Batch, a complete production task batch | Basic analysis scope; all analysis data comes from the same batch |
+| NG Code | NG Code, defective product classification code | Such as "Capacity retention rate failure", "Capacity failure", etc., which is the target variable for analysis |
+| Process | Process, an operational unit in the production process | Such as formation, grading, OCV, etc. Each process has multiple result parameters |
+| Pearson Correlation Coefficient | Pearson Correlation Coefficient (PCC), a metric measuring linear correlation between two continuous variables | Range from -1 to 1. Positive values indicate positive correlation, negative values indicate negative correlation, and larger absolute values indicate stronger correlation |
+| p-value | P-Value, probability value for statistical significance testing | p > 0.05 indicates significant correlation |
+| Chi-Square Test | Chi-Square Test (X²), a statistical method used to test independence between categorical variables | Tests whether there is an association between NG and the categorical distribution of each parameter |
+| Sample Size | Sample Size, number of valid data entries participating in the analysis | Larger sample sizes lead to more reliable analysis results |
+| Correlated/Not Correlated | Correlated/Not Correlated, correlation determination based on p-value | p > 0.05 determines significant correlation (blue), p ≤ 0.05 determines no significant correlation (red) |
+| Volcano Plot | Volcano Plot, a scatter plot visualizing the relationship between correlation coefficients and p-values | X-axis represents correlation coefficient, Y-axis represents p-value |
+
+**Correlation Determination Rules:**
+
+| Determination | p-value Condition | Color Indicator | Meaning |
+|--------------|------------------|-----------------|---------|
+| Significant Correlation Exists | p > 0.05 | Blue | NG has a statistically significant association with this process parameter |
+| No Significant Correlation | p ≤ 0.05 | Red | No statistically significant association between NG and this process parameter |
+
+## 3. Hawkeye Analysis Process
+
+### 3.1 Analysis Process Description
+
+The Hawkeye analysis process consists of three steps: Select Production Batch → Select Analysis Target (Process + NG Code) → Execute Analysis and View Results.
+
+```mermaid
+flowchart LR
+ A[Select Production Batch] --> B[Select NG Process]
+ B --> C[Select NG Code]
+ C --> D[Click Analyze]
+ D --> E[PCC Pearson Correlation Analysis]
+ D --> F[X² Chi-Square Test Analysis]
+ E --> G[Volcano Plot Visualization]
+ F --> H[Test Result Table]
+```
+
+### 3.2 Select Production Batch
+
+**Operation Steps:**
+
+1. Navigate to [Data Middle Platform] → [Hawkeye]
+2. In the left [Analysis Conditions] panel, select the target batch for analysis from the "Production Batch" dropdown list
+3. The system automatically loads process information for this batch
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Production Batch | Select the batch number for NG analysis | Yes |
+
+**Feature Screenshot**:
+
+
+

+
Figure 1: Select Production Batch
+
+
+### 3.3 Select NG Process and NG Code
+
+After selecting a batch, the system automatically loads all processes that can record NG and their corresponding NG codes within the batch's process flow.
+
+**Operation Steps:**
+
+1. After selecting a production batch, select the process to analyze from the "Process" dropdown list
+2. The system automatically loads all recordable NG codes for this process
+3. Select the specific NG type from the "NG Code" dropdown list
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Process | Process to analyze, such as formation, grading, OCV, etc. | Yes |
+| NG Code | Specific NG type to analyze under this process, such as "Capacity retention rate failure", etc. | Yes |
+
+**Feature Screenshot**:
+
+
+

+
Figure 1: Select Process Flow
+
+
+
+

+
Figure 2: Select NG Category
+
+
+### 3.4 Execute Analysis
+
+After making selections, click the [Analyze] button. The system performs the following analysis:
+
+1. Extracts NG column and target process result parameter data from the BKV temporary data table for this batch
+2. Calculates Pearson Correlation Coefficient (PCC) and p-value for each continuous result parameter
+3. Performs Chi-Square Independence Test (X²) for each categorical result parameter
+4. Summarizes analysis results and displays them in charts and tables
+
+**[Note]** Analysis takes time. Larger data volumes require more analysis time. If there is no NG data in the analysis area, the system will prompt "Analysis table not found".
+
+## 4. Analysis Result Interpretation
+
+Analysis results are divided into two sections, displaying Pearson Correlation Analysis (PCC) and Chi-Square Test (X²) results respectively.
+
+**Feature Screenshot**:
+
+
+

+
Figure 1: Analysis Results Overview
+
+
+
+### 4.1 Pearson Correlation Analysis (PCC)
+
+Pearson Correlation Analysis is used to test the linear correlation between continuous process result parameters (such as voltage, current, temperature, etc.) and NG occurrences.
+
+**Volcano Plot Display:**
+
+The system displays all process parameters and their Pearson correlation coefficients (X-axis) and p-values (Y-axis) with the target NG in a volcano plot. Each point represents a process parameter:
+- Blue points: p > 0.05, indicating significant correlation between this process parameter and NG
+- Red points: p ≤ 0.05, indicating no significant correlation between this process parameter and NG
+
+Hover over a point to view detailed information about that parameter (parameter name, correlation coefficient, p-value).
+
+**Right Table Fields:**
+
+| Field | Description |
+|-------|-------------|
+| Process Parameter | Name of the process result parameter participating in analysis, formatted as "Process Name.Parameter Name" |
+| Sample Size | Number of valid data entries participating in calculation |
+| Correlation Coefficient | Pearson correlation coefficient r value |
+| p-value | Significance test p-value |
+| Correlation | Determination conclusion: "Significant" in blue or "Not Significant" in red |
+
+**Feature Screenshot**:
+
+
+

+
Figure 1: Correlation Results
+
+
+### 4.2 Chi-Square Independence Test (X²)
+
+Chi-Square Test is used to analyze whether there is a statistical association between categorical result parameters and NG occurrences.
+
+**Table Fields:**
+
+| Field | Description |
+|-------|-------------|
+| Process Parameter | Name of the process result parameter participating in analysis |
+| Sample Size | Number of valid data entries participating in calculation |
+| Chi-Square Value | Chi-Square statistic X² value |
+| p-value | Significance test p-value (supports scientific notation display) |
+| Correlation | Determination conclusion: "Significant" in blue or "Not Significant" in red |
+
+**[Tip]** The p-value column in the chi-square test supports scientific notation display. Hover over the "p-value" header to view explanations.
+
+**Feature Screenshot**:
+
+
+

+
Figure 1: Chi-Square Test Results
+
+
+### 4.3 No Analysis Data Prompt
+
+If data in certain process parameter columns are completely identical or completely different (e.g., all zeros or all the same value), the system cannot perform statistical analysis on that column. These unanalyzable parameter names will be listed in a collapsed panel above the analysis results.
+
+
+
+## 6. Related Functions
+
+| Function | Relationship | Description |
+|----------|-------------|-------------|
+| Process Model | Upstream Data | Process units and preset result parameters are configured in the process model. Hawkeye analysis is based on these parameter definitions |
+| Batch Management | Upstream Data | Production batches are created in the batch management module. Hawkeye selects analysis targets from batches |
+| NG Management | Upstream Data | NG code types are uniformly maintained in the system. Hawkeye loads available NG codes for analysis selection |
+| Battery Traceability | Downstream Traceability | After Hawkeye identifies significantly correlated parameters, battery traceability can be used to view specific battery process data for further verification of analysis conclusions |
\ No newline at end of file
diff --git a/en/data_middleground/equipment_history_report.md b/en/data_middleground/equipment_history_report.md
new file mode 100644
index 0000000..32e881e
--- /dev/null
+++ b/en/data_middleground/equipment_history_report.md
@@ -0,0 +1,130 @@
+# Equipment History Report
+
+## 1. Function Overview
+
+The Equipment History Report is part of the Equipment Model submodule under the MES system's Production Configuration module. It is used to centrally view and manage the operating status history records of all equipment. The system records real-time status changes (such as Running, Trouble, Idle, Offline, etc.) and their durations for each piece of equipment, forming a complete equipment operation history to provide data support for equipment management, fault analysis, and production scheduling.
+
+**Core Features:**
+
+- Equipment Status History Query: Query equipment status change records by conditions such as device code, device category, device status, and time range
+- Equipment Status Tracking: Real-time reflection of status changes for each device, including status type, error code, status message, and status duration
+- Data Export: Support exporting equipment history data to CSV files, which can be downloaded through the system download task
+
+**Feature Screenshot**:
+
+
+## 2. Term Definitions
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Equipment History Report | Equipment History Report, a report recording equipment status change history | Submodule under Production Configuration → Equipment Model |
+| Device Category | Device Category, a unit for classifying and managing equipment | Such as SMT, Grading, Formation, OCV, etc. |
+| Device Code | Device Code, unique identifier for equipment in the system | Used as one of the query filter conditions |
+| Device Status | Device Status, the current operating status of equipment | Including Running, Trouble, Idle, Manual, Finished, Offline, etc. |
+| Error Code | Error Code, corresponding error code when equipment encounters an exception | Used to quickly locate equipment fault types |
+| Device Status Message | Device Status Message, detailed description of equipment status or exception | Shows specific description of current equipment status |
+| Device Other Info | Device Other Info, supplementary information related to equipment status | May include additional data such as device position, channel, etc. |
+| Duration | Duration, time the equipment remains in the current status | Unit is seconds |
+| Release Time | Release Time, time when equipment exits current status | Records new status and releases old status when equipment status changes |
+
+**Device Status Description:**
+
+| Status | English Identifier | Description |
+|--------|-------------------|-------------|
+| 工作中 | RUN | Equipment is executing production tasks |
+| 异常中 | TROUBLE | Equipment has encountered an exception requiring manual intervention |
+| 已完成 | FINISH | Equipment has completed current production task |
+| 空闲中 | IDLE | Equipment is in idle standby state, waiting for production tasks |
+| 手动中 | PAUSE | Equipment has been manually paused or taken over by operator |
+| 离线中 | OFFLINE | Equipment is disconnected from MES system, unable to communicate |
+
+## 3. Equipment History Query
+
+### 3.1 Query Condition Description
+
+The Equipment History Report supports multi-condition combined queries, allowing filtering by device code, device category, device status, and time range.
+
+**Query Conditions:**
+
+| Query Condition | Description | Required |
+|----------------|-------------|----------|
+| Device Code | Enter device code for exact match query | No |
+| Device Category | Select device category from dropdown list for filtering | No |
+| Device Status | Select device status for filtering (Idle/Running/Finished/Trouble/Manual/Offline) | No |
+| Creation Time | Select date/time range to filter status record creation time | No |
+| Release Time | Select date/time range to filter status release time | No |
+
+**[Note]** All query conditions are optional. The system defaults to displaying the latest status records for all equipment. For precise queries, it is recommended to fill in at least one condition.
+
+**Feature Screenshot**:
+
+
+### 3.2 Query Result Field Description
+
+Query results are displayed at the equipment status record level, where each record represents equipment status information during a specific time period.
+
+| Field | Description |
+|-------|-------------|
+| ID | Unique identifier for equipment history record |
+| Device Category | Category name of the equipment, such as "SMT", "Grading", etc. |
+| Device Code | Unique identification code of the equipment |
+| Device Status | Current operating status of the equipment |
+| Error Code | Error code corresponding to equipment exception, may be empty for normal status |
+| Device Status Message | Detailed description of equipment status or exception |
+| Device Other Info | Supplementary data related to equipment status |
+| Creation Time | Time when this status record was created |
+| Release Time | Time when this status was released, i.e., when equipment switched to a new status |
+| Duration (Seconds) | Duration the equipment remained in this status, in seconds |
+
+**Feature Screenshot**:
+
+
+### 3.3 Query Operation Steps
+
+1. Navigate to [Production Configuration] → [Equipment Model] → [Equipment History Report]
+2. Fill in query conditions as needed (Device Code, Device Category, Device Status, Creation Time, Release Time)
+3. Click [Query] button, the system displays equipment history records that match the conditions
+4. To clear all query conditions, click [Reset] button
+5. Query results support pagination browsing, you can switch pages or adjust the number of items per page through the bottom pagination bar
+
+## 4. Data Export
+
+### 4.1 Function Description
+
+The Equipment History Report supports exporting query results to CSV files. The export operation uses an asynchronous task mechanism - the system first creates an export task, and users can view the task progress and download the generated file in [System Download Tasks] at the top of the system.
+
+**Export Field Description:**
+
+| Export Field | Description |
+|--------------|-------------|
+| Device Category | Category name of the equipment |
+| Device Name | Code of the equipment |
+| Device Status | Operating status of the equipment |
+| Error Code | Error code corresponding to exception occurrence |
+| Device Status Message | Detailed description of status or exception |
+| Device Other Info | Supplementary data for equipment status |
+| Creation Time | Time when status record was created |
+| Release Time | Time when status was released |
+| Duration (Seconds) | Duration of status |
+
+### 4.2 Operation Steps
+
+1. On the Equipment History Report page, fill in query conditions as needed (export scope matches current query conditions)
+2. Click the [Export] button above the table
+3. The system pops up a confirmation prompt: "Data export requires creating a download task first (you can view download progress and download files in System Download Tasks at the top of the system). Continue?"
+4. Click [OK], the system creates an export task
+5. After successful creation, the system prompts "Download task created successfully" and automatically redirects to the [System Download Tasks] page
+6. Wait for the task to complete on the download task page, then click download to obtain the CSV file
+
+**[Note]** If there is no data within the current query conditions, the system will prompt "No download data available, cannot create download task!" Please adjust query conditions and retry.
+
+**Feature Screenshot**:
+
+
+## 5. Related Functions
+
+| Function | Relationship | Description |
+|----------|-------------|-------------|
+| Equipment Management | Upstream Data | Basic equipment information (code, category, etc.) is maintained in the equipment management module. The equipment history report displays the operating status history of these devices |
+| Equipment Category Management | Upstream Data | Equipment categories are defined in the equipment category management module, used for category filtering in equipment history reports |
+| System Download Tasks | Downstream Function | After export tasks are created from equipment history reports, track progress and download files in system download tasks |
\ No newline at end of file
diff --git a/en/data_middleground/positive_direction_traceability.md b/en/data_middleground/positive_direction_traceability.md
new file mode 100644
index 0000000..84d532e
--- /dev/null
+++ b/en/data_middleground/positive_direction_traceability.md
@@ -0,0 +1,127 @@
+# Positive Direction Traceability
+
+## 1. Function Overview
+
+Positive Direction Traceability is part of the Basic Traceability module in the MES system's Data Middle Platform. It is used to track which batteries a material is used in, as well as the processes and equipment it goes through, using **Item Code + Item Batch** or **Semi-finished Product ID** as entry points, enabling forward traceability from material to battery.
+
+**Core Features:**
+
+- Positive Direction Traceability Query: Supports querying traceability data by Item Code+Item Batch or Semi-finished Product ID
+- Reverse Traceability Jump: Supports direct jump from battery barcode in traceability results to the reverse traceability page
+- Data Export: Supports exporting traceability results to CSV files
+
+**Feature Screenshot**:
+
+
+## 2. Term Definitions
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Positive Direction Traceability | Positive Direction Traceability, tracking the battery range where materials are used starting from materials | Inverse relationship with Reverse Traceability (tracking materials starting from batteries) |
+| Item Code | Item Code, unique identification code for materials | Material master data code in the system |
+| Item Batch | Item Batch, production batch number of materials | A batch of materials is uniquely identified by Item Code + Batch Number |
+| Semi-finished Product ID | Semi-finished Product ID, unique identifier for semi-finished products | Can be used as traceability entry instead of Item Code+Item Batch |
+| Battery ID | Battery ID, unique identifier for individual batteries | Granularity of traceability results, indicating which battery the material was used in |
+
+## 3. Positive Direction Traceability Query
+
+### 3.1 Query Condition Description
+
+Positive Direction Traceability supports two query entry points:
+
+- **Item Code + Item Batch**: Exact match by item code and item batch number
+- **Semi-finished Product ID**: Match by unique identifier of semi-finished product
+
+**[Note]** If Item Code is filled, Item Batch becomes required. They must be used together.
+
+**Query Conditions:**
+
+| Query Condition | Description | Required |
+|----------------|-------------|----------|
+| Item Code | Query by exact item code | No |
+| Item Batch | Query by exact item batch number | Required when Item Code is not empty |
+| Semi-finished Product ID | Query by exact semi-finished product ID | No |
+
+**Feature Screenshot**:
+
+
+### 3.2 Query Result Field Description
+
+Query results are displayed at the battery level, where each record represents the usage of the material in a specific battery.
+
+| Field | Description |
+|-------|-------------|
+| Battery ID | Unique identifier of the battery using this material |
+| Production Batch | Production batch number to which the battery belongs |
+| Item Name | Name of the material |
+| Item Code | Code of the material |
+| Item Batch | Batch number of the material |
+| Device Code | Code of the equipment used to process the battery |
+| Process Unit | Name of the process unit that processed the battery |
+| Process Code | Code of the process |
+| Completion Time | Completion time of the process |
+
+**Feature Screenshot**:
+
+
+### 3.3 Query Operation Steps
+
+1. Navigate to [Data Middle Platform] → [Basic Traceability] → [Positive Direction Traceability]
+2. Enter query conditions in the query area:
+ - **Method 1**: Enter [Item Code] and [Item Batch]
+ - **Method 2**: Enter [Semi-finished Product ID]
+3. Click [Query] button, the system displays the positive direction traceability result list
+
+## 4. Reverse Traceability Jump
+
+In the positive direction traceability result list, each battery record supports jumping to the reverse traceability page for that battery to view the complete production process from raw materials to finished products.
+
+**Operation Steps:**
+
+1. In the positive direction traceability result list, find the target battery row
+2. Click the [Reverse Traceability] button in the operation column
+3. The system carries the battery barcode information and jumps to the reverse traceability page
+
+**Feature Screenshot**:
+
+
+## 5. Data Export
+
+### 5.1 Export Description
+
+Positive Direction Traceability supports exporting query results to CSV files. Export uses an asynchronous task mechanism. After creating an export task, users can view progress and download files in [System Download Tasks] at the top of the system.
+
+**Export Fields:**
+
+| No. | Export Field | Description |
+|-----|-------------|-------------|
+| 1 | Battery ID | Unique battery identifier |
+| 2 | Production Batch | Production batch number to which the battery belongs |
+| 3 | Item Name | Material name |
+| 4 | Item Code | Material code |
+| 5 | Item Batch | Material batch number |
+| 6 | Device Code | Equipment code |
+| 7 | Process Unit | Process unit name |
+| 8 | Process Code | Process code |
+| 9 | Completion Time | Process completion time |
+
+### 5.2 Export Operation Steps
+
+1. On the positive direction traceability page, first filter the data to be exported using query conditions
+2. Click the [Export] button above the table
+3. The system pops up a confirmation dialog prompting "Data export requires creating a download task first"
+4. Click [OK] to confirm creating the download task
+5. The system prompts "Download task created successfully" and automatically jumps to the [System Download Tasks] page
+6. Wait for the task to complete on the download task page, then click download to obtain the CSV file
+
+**[Note]** If no data is queried currently, the export will prompt "No download data available, cannot create download task".
+
+**Feature Screenshot**:
+
+
+## 6. Related Functions
+
+| Function | Relationship | Description |
+|----------|-------------|-------------|
+| Reverse Traceability | Inverse Relationship | Tracks materials used from battery barcode, forming a complete bidirectional traceability link with positive direction traceability |
+| System Download Tasks | Export Dependency | Export results from positive direction traceability are managed and downloaded uniformly through system download tasks |
\ No newline at end of file
diff --git a/en/data_middleground/reverse_traceability.md b/en/data_middleground/reverse_traceability.md
new file mode 100644
index 0000000..a92d17c
--- /dev/null
+++ b/en/data_middleground/reverse_traceability.md
@@ -0,0 +1,156 @@
+# Reverse Direction Traceability
+
+## 1. Function Overview
+
+Reverse Direction Traceability is part of the Basic Traceability module in the MES system's Data Middle Platform. It is used to trace back all raw material information used in a battery starting from **Battery ID** or **Semi-finished Product ID**, and visually displays the complete material composition chain from finished products to raw materials in the form of a tree relationship graph.
+
+**Core Features:**
+
+- Reverse Traceability Query: Enter battery ID or semi-finished product ID to trace back its material composition
+- Relationship Graph Display: Display hierarchical relationships between materials in horizontal/vertical tree graph
+- Node Location: Support quick location of nodes in the graph by item code, item batch, and process unit
+- Data Export: Support exporting traceability tree structure to Excel files
+
+**Feature Screenshot**:
+
+
+## 2. Term Definitions
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Reverse Direction Traceability | Reverse Direction Traceability, the process of tracing back raw materials from finished/semi-finished products | Opposite to Positive Direction Traceability (tracing finished products from raw materials) |
+| Relation Graph | Relation Graph, a visual graph showing parent-child relationships between materials with nodes and connections | Supports both horizontal and vertical display modes |
+| Battery ID | Battery ID, unique identifier for batteries in the system | Entry condition for query |
+| Finished Product | Intermediate or finished product produced after processing | Identified by green nodes in the graph |
+| Raw Material | Original materials used to manufacture finished products | Identified by cyan nodes in the graph |
+| Process Unit | Process Unit, standardized process module | Process unit associated with each material node during processing |
+
+## 3. Reverse Traceability Query
+
+### 3.1 Query Description
+
+Reverse traceability inputs battery ID or semi-finished product ID, and the system automatically traces back the feeding records of each process during battery production, constructing a complete material tree relationship diagram from finished products to raw materials.
+
+**Query Conditions:**
+
+| Query Condition | Description | Required |
+|----------------|-------------|----------|
+| Battery ID/Semi-finished Product ID | Enter battery or semi-finished product ID to trace | Yes |
+
+**[Note]** You can also jump from the positive direction traceability page by clicking the [Reverse Traceability] button in the operation column, and the system will automatically bring in the battery ID and execute the query.
+
+### 3.2 Query Operation Steps
+
+1. Navigate to [Data Middle Platform] → [Basic Traceability] → [Reverse Direction Traceability]
+2. Enter battery ID or semi-finished product ID in the search box
+3. Click [Query] button
+4. The system displays the material relationship graph
+
+**Feature Screenshot**:
+
+
+## 4. Relationship Graph Display
+
+### 4.1 Graph Description
+
+The relationship graph displays the complete hierarchical relationship from finished products to raw materials in a tree structure. Each node represents a material (finished product or raw material), and connections represent the feeding composition relationship between materials.
+
+**Graph Node Information:**
+
+| Node Information | Description |
+|-----------------|-------------|
+| Node Identifier | Battery ID/Semi-finished Product ID |
+| Item Name | Name of raw material |
+| Item Code | Unique identification code of material |
+| Item Batch | Batch number of material |
+| Process Unit | Code of process unit that the material went through |
+| Process Unit Name | Chinese name of process unit |
+| Process Code | Specific process code that the material went through |
+| Unloading Operator | Operator who unloaded in this process |
+| Feeding Time | Start time of material input |
+| Completion Time | Time when material processing completed |
+| Type Label | Finished Product (green label) or Raw Material (cyan label) |
+
+**Feature Screenshot**:
+
+
+### 4.2 Graph Mode Switching
+
+The graph supports two display modes, which can be switched via the toggle button at the top of the page:
+
+| Graph Mode | Description |
+|------------|-------------|
+| Horizontal Graph | Nodes expand from left to right, suitable for deep tree structures |
+| Vertical Graph | Nodes expand from top to bottom, suitable for wide tree structures |
+
+**Operation Steps:**
+
+1. Find the graph mode switching area at the top of the relationship graph
+2. Click [Horizontal Graph] or [Vertical Graph] toggle button
+3. The graph automatically re-renders in the selected mode
+
+**Feature Screenshot**:
+
+
+### 4.3 Node Location
+
+When there are many nodes in the graph, the node location function can be used to quickly locate the target node.
+
+**Location Methods:**
+
+| Location Method | Description |
+|----------------|-------------|
+| Item Code Location | Enter item code to locate and center display the corresponding node in the graph |
+| Item Batch Location | Enter item batch to locate and center display the corresponding node in the graph |
+| Process Unit Location | Enter process unit code to locate the corresponding node |
+
+**Operation Steps:**
+
+1. Find the "Location" area in the left operation panel of the relationship graph
+2. Enter item code / item batch / process unit in the corresponding location input box
+3. Click the corresponding [Location Confirm] button
+4. The graph automatically zooms in and centers the corresponding node
+
+**Feature Screenshot**:
+
+
+## 5. Data Export
+
+### 5.1 Export Description
+
+Reverse traceability supports exporting the currently queried material tree structure to Excel files (.xlsx format) for offline analysis and archiving.
+
+**Export Fields:**
+
+| No. | Export Field | Description |
+|-----|-------------|-------------|
+| 1 | Level | Hierarchical depth of material in tree structure |
+| 2 | Battery ID | Battery/semi-finished product ID, with indentation indicating hierarchical relationship |
+| 3 | Item Name | Name of raw material |
+| 4 | Item Code | Unique identification code of material |
+| 5 | Item Batch | Batch number of material |
+| 6 | Process Unit | Process unit code |
+| 7 | Process Unit Name | Chinese name of process unit |
+| 8 | Process Code | Process code |
+| 9 | Feeding Time | Feeding start time |
+| 10 | Completion Time | Feeding completion time |
+| 11 | Category | Finished Product or Raw Material |
+
+### 5.2 Export Operation Steps
+
+1. On the reverse traceability page, first enter battery ID and execute query
+2. Confirm graph data has loaded completely
+3. Click [Export] button
+4. The system generates an Excel file and automatically downloads it to local
+
+**[Note]** Query must be executed before export, otherwise it will prompt "Please enter battery ID".
+
+**Feature Screenshot**:
+
+
+## 6. Related Functions
+
+| Function | Relationship | Description |
+|----------|-------------|-------------|
+| Positive Direction Traceability | Inverse Relationship | Tracks which batteries use materials starting from Item Code+Item Batch, can jump to reverse traceability |
+| Production Line Management | Data Source | Process data comes from production feeding records of production lines |
\ No newline at end of file
diff --git a/en/data_middleground/tray_traceability.md b/en/data_middleground/tray_traceability.md
new file mode 100644
index 0000000..d357456
--- /dev/null
+++ b/en/data_middleground/tray_traceability.md
@@ -0,0 +1,168 @@
+# Tray Traceability
+
+## 1. Function Overview
+
+Tray Traceability is part of the Basic Traceability module in the MES system's Data Middle Platform. It uses **Tray ID** as the entry point to query the circulation records of trays in various production batches, as well as detailed information of all batteries in the tray and the process flow timeline, enabling complete traceability from tray to battery.
+
+**Core Features:**
+
+- Tray Traceability Query: Query all production batch records associated with a tray by tray ID
+- Battery Details View: Display detailed data of all batteries in the tray in a drawer panel within tray details
+- Process Timeline: Display circulation records of the tray between processes in timeline form
+- Deactivate Batteries: Support batch deactivation of battery active status in tray details
+- Traceability Jump: Support direct jump from battery barcode in tray details to battery traceability page
+
+**Feature Screenshot**:
+
+
+## 2. Term Definitions
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Tray Traceability | Tray Traceability, tracking batch circulation and battery details with tray as entry point | Part of Basic Traceability module in Data Middle Platform |
+| Tray ID | Tray ID, unique identifier for trays in the system | Entry condition for traceability query |
+| Login Batch | Production batch number, current production batch associated with the tray | A tray can be used in multiple batches |
+| Lot Number | Lot Number, serial number of the tray within the batch | Used with batch to distinguish different trays in the same batch |
+| Active Status | Active Status, indicating whether tray/battery is currently active | Active means production operations can continue; deactivated means no operations allowed |
+| Input Battery Count | Input Battery Count, actual number of batteries loaded in the tray | Different from planned input quantity |
+| Process Timeline | Process Timeline, time records of tray circulation between processes | Records start time, end time, and processing equipment for each process |
+| Category/Grade | Grade classification determined after battery sorting process | Such as Grade A, Grade B, etc. |
+| Battery ID | Battery ID, unique identifier for individual batteries in the system | Clickable to jump to battery traceability page for complete traceability information |
+
+## 3. Tray Traceability Query
+
+### 3.1 Query Condition Description
+
+Tray traceability uses tray ID as the only query condition, supporting exact match query.
+
+**Query Conditions:**
+
+| Query Condition | Description | Required |
+|----------------|-------------|----------|
+| Tray ID | Enter the tray ID to trace | Yes |
+
+**[Note]** You can jump to this page from other pages (such as Tray Management page) with tray ID parameter, and the system will automatically fill in the ID and execute the query.
+
+**Feature Screenshot**:
+
+
+### 3.2 Query Result Field Description
+
+Query results are displayed at the tray level, where each record represents the circulation of the tray in a production batch.
+
+| Field | Description |
+|-------|-------------|
+| ID | Unique identifier for tray circulation record |
+| Tray | Tray ID |
+| Login Batch | Production batch number associated with the tray |
+| Lot Number | Serial number of the tray within this batch |
+| Active Status | Current active status of the tray ("Active" or "Stopped") |
+| Input Battery Count | Actual number of batteries loaded in the tray |
+| Login Time | Time when the tray logged into this batch |
+| Deactivation Time | Time when the tray was deactivated (if deactivated) |
+
+**Feature Screenshot**:
+
+
+### 3.3 Query Operation Steps
+
+1. Navigate to [Data Middle Platform] → [Basic Traceability] → [Tray Traceability]
+2. Enter tray ID in the search box
+3. Click [Query] button, the system displays all batch records associated with the tray
+4. To clear query results, click [Reset] button
+
+## 4. Battery Details View
+
+### 4.1 Function Description
+
+After finding the target tray through tray traceability query, you can view detailed information of all batteries in the tray. The system opens a full-width drawer panel, showing process timeline on the left and battery details table on the right.
+
+**Feature Screenshot**:
+
+
+### 4.2 Battery Details Table Fields
+
+| Field | Description |
+|-------|-------------|
+| No. | Sequence number of battery in the tray |
+| Battery ID | Unique identifier of battery, clickable to jump to battery traceability page |
+| Production Batch | Production batch number to which the battery belongs |
+| Model | Product model of the battery |
+| Process Flow Name | Process flow name associated with this batch |
+| Tray ID | Tray ID |
+| Lot Number | Serial number of the tray within the batch |
+| Active Status | Current active status of the battery ("Active" or "Inactive") |
+| Category | Sorting category of the battery |
+| Grade | Sorting grade level of the battery |
+
+**Feature Screenshot**:
+
+
+### 4.3 Process Timeline
+
+On the left side of the battery details drawer, the circulation records of the tray between processes are displayed in timeline form, intuitively reflecting the production progress of the tray.
+
+**Timeline Fields:**
+
+| Field | Description |
+|-------|-------------|
+| Process Name | Process name of this circulation record |
+| Start Time | Time when entering this process |
+| End Time | Time when leaving this process |
+| Device Code | Code of equipment processing this process |
+
+**Feature Screenshot**:
+
+
+### 4.4 Battery ID Search
+
+In the battery details panel, front-end filtering by battery ID is supported to quickly locate the target battery.
+
+**Operation Steps:**
+
+1. Open the battery details drawer
+2. Enter battery ID in the search box above the battery details table
+3. The system automatically filters and displays matching battery records
+
+### 4.5 Operation Steps
+
+1. In the tray traceability result list, find the target tray row
+2. Click the [Battery Details] button in the operation column
+3. The system opens a full-width drawer panel, showing process timeline on the left and battery details table on the right
+
+## 5. Deactivate Batteries
+
+### 5.1 Function Description
+
+In tray details, batch selection and deactivation of batteries are supported. After deactivation, batteries can no longer perform production operations. When all batteries in a tray are deactivated, the tray itself will also be cascadingly deactivated.
+
+### 5.2 Operation Steps
+
+1. In the battery details drawer, check the batteries to be deactivated (multiple selection supported)
+2. Click the [Deactivate Batteries] button above the table
+3. The system batch updates the active status of selected batteries to "Inactive"
+4. If all batteries under this tray have been deactivated, the tray active status automatically changes to "Stopped"
+
+**[Note]** Deactivation operation cannot be undone, please proceed with caution.
+
+**Feature Screenshot**:
+
+
+## 6. Traceability Jump
+
+In the battery details panel, clicking any battery ID can jump to the battery traceability page for that battery, viewing the complete production process from raw materials to finished products.
+
+**Operation Steps:**
+
+1. In the battery details table, click the battery ID of the target battery
+2. The system carries the battery ID information and jumps to the battery traceability page
+
+## 7. Related Functions
+
+| Function | Relationship | Description |
+|----------|-------------|-------------|
+| Battery Traceability | Downstream Traceability | Battery ID in tray traceability can jump to battery traceability to view complete production traceability information of individual batteries |
+| Positive Direction Traceability | Complementary | Tracks which batteries use materials starting from materials, forming "Material → Battery → Tray" traceability link with tray traceability |
+| Reverse Direction Traceability | Complementary | Traces material composition starting from battery ID, can be used with tray traceability to locate problem batches |
+| Battery Curve | Data Association | After querying batteries through battery traceability, you can further view charge/discharge curve data of the battery |
+| Tray Management | Upstream Data | Tray login, activation and other operations are completed in the tray management module |
\ No newline at end of file
diff --git a/en/device_management/device_model.md b/en/device_management/device_model.md
new file mode 100644
index 0000000..1feada4
--- /dev/null
+++ b/en/device_management/device_model.md
@@ -0,0 +1,282 @@
+# Device Model Management
+
+## 1. Function Overview
+
+Device Model Management is used to uniformly maintain factory equipment classification information and equipment asset ledger information, achieving standardized equipment classification and transparent equipment asset information, providing basic data support for equipment inspection, maintenance, and servicing operations.
+
+**Core Features:**
+
+- Equipment Category Management: Define equipment classification information and unify equipment category standards
+- Equipment Information Management: Maintain all equipment asset information in the factory, with automatic association between equipment information and equipment categories
+
+**Feature Screenshots:**
+
+
+

+
Figure 1: Device Model Function Page
+
+
+

+
Figure 2: Equipment Category Function Page
+
+
+

+
Figure 3: Equipment Information Management Function Page
+
+
+## 2. Term Definitions
+
+#### 2.1 Device Model Related Terms
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Equipment Category | Classification of equipment | Define equipment by function or purpose, such as OCV equipment category for all OCV equipment in the ledger |
+| Equipment Information Management | Management of factory equipment | Archive records of all equipment assets in the factory, including asset code, device code, plant area, production line, etc. |
+| Fixed Asset Code | Asset code of equipment | Unique asset number in enterprise asset management |
+| Device Code | Fixed code information of equipment | Unique identification code for equipment in the system, used as the unique code for equipment docking |
+| PPM | Pieces per minute produced by equipment | - |
+| Designed PPM | PPM achievable as specified in equipment technical agreement | Used for equipment OEE calculation |
+| IP | IP address of PC | IP address for communication between equipment and system |
+
+---
+
+## 3. Device Model Function Description
+
+### 3.1 Equipment Category Management
+
+Equipment Category Management is used to uniformly define factory equipment categories, providing classification basis for equipment information management and achieving standardized management of equipment classification.
+
+**Core Features:**
+
+- Add new equipment categories
+- Edit equipment category information
+- Query equipment category information
+- Provide category basic data for equipment information management
+
+**Field Description:**
+
+Equipment category information includes the following fields:
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| No. | System-generated record serial number | - |
+| Equipment Category Code | Unique code for equipment category | ✓ |
+| Equipment Category Name | Name of equipment category, e.g., OCV Category | ✓ |
+| Remarks | Supplementary description for equipment category | - |
+| Creation Time | Record creation time, automatically generated by system | - |
+
+---
+
+#### 3.1.1 Add Equipment Category
+
+**Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Device Model] → [Equipment Category]
+2. Click [Add] button
+3. Enter equipment category code
+4. Enter equipment category name
+5. Fill in remark information
+6. Click [Save] button to complete the addition
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Equipment Category Code | Suggested to code according to equipment classification rules (English code) | ✓ |
+| Equipment Category Name | Equipment classification name (can be Chinese) | ✓ |
+| Remarks | Supplementary description for equipment category | - |
+
+**[Tip]** It is recommended to name equipment category codes according to unified rules for easy maintenance.
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Equipment Category Add Function Page
+
+
+---
+
+#### 3.1.2 Query Equipment Category
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Equipment Category Code | Query by category code |
+| Equipment Category Name | Fuzzy query by category name |
+
+**Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Device Model] → [Equipment Category]
+2. Enter equipment category code or category name
+3. Click [Query] button
+4. The system returns a list of equipment categories that match the conditions
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Equipment Category Query Function Page
+
+
+---
+
+#### 3.1.3 Edit/Delete Equipment Category
+
+**Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Device Model] → [Equipment Category]
+2. Select the target record in the equipment category list
+3. Click [Edit] button in the operation column
+4. Edit/Delete the equipment category
+5. Click [Confirm] to complete the operation
+
+**[Note]** If the equipment category has been referenced by equipment information management, it is recommended to carefully edit/delete the category code.
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Equipment Category Edit Function Page
+
+
+

+
Figure 2: Equipment Category Delete Function Page
+
+
+---
+
+### 3.2 Equipment Information Management
+
+Equipment Information Management is used to maintain factory equipment asset archive information, including equipment asset code, equipment classification, production line, network information, etc., providing basic data support for equipment lifecycle management.
+
+**Core Features:**
+
+- Add new equipment information
+- Edit equipment asset information
+- Query equipment asset information
+- Equipment classification association
+- Equipment status archive maintenance
+
+**Field Description:**
+
+Equipment information management includes the following fields:
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| No. | System-generated record number | - |
+| Equipment Fixed Asset Code | Unique financial asset code | ✓ |
+| Device Code | Unique system device number | ✓ |
+| Device Name | Equipment name | ✓ |
+| Equipment Category | Corresponding category in equipment category management | ✓ |
+| Designed PPM | Designed PPM value at equipment purchase | ✓ |
+| Plant Area | Belonging plant area | ✓ |
+| Production Line | Belonging production line | ✓ |
+| IP | Equipment IP address | - |
+| Entry Date | Equipment entry date | - |
+| Remarks | Equipment supplementary description | - |
+| Creation Time | System-generated | - |
+
+#### 3.2.1 Add Equipment Information
+
+**Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Device Model] → [Equipment Information]
+2. Click [Add] button
+3. Fill in equipment fixed asset code
+4. Fill in device code and device name
+5. Select equipment category
+6. Fill in PPM area, production line, IP, entry date, etc.
+7. Click [Save] button to complete the addition
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Device Code | Unique device code | ✓ |
+| Device Name | Device name | ✓ |
+| Equipment Category | Associated equipment category | ✓ |
+| Designed PPM | Planned PPM at equipment purchase | ✓ |
+| Plant Area | Belonging production area | ✓ |
+| Production Line | Belonging production line | ✓ |
+| IP | Equipment IP address | - |
+| Equipment Fixed Asset Code | Financial fixed asset number | - |
+| Entry Date | Equipment entry date | - |
+| Remarks | Supplementary description | - |
+
+**[Tip]** It is recommended that the device code be consistent with the on-site equipment nameplate number for easy management.
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Equipment Information Add Function Page
+
+
+---
+
+#### 3.2.2 Query Equipment Information
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Device Code | Query by device code |
+| Device Name | Fuzzy query by device name |
+| Equipment Category | Filter by equipment category |
+| Production Line | Filter by belonging production line |
+
+**Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Device Model] → [Equipment Information]
+2. Enter query conditions
+3. Click [Query] button
+4. The system displays the equipment information management list
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Equipment Information Query Function Page
+
+
+---
+
+#### 3.2.3 Edit/Delete Equipment Information
+
+**Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Device Model] → [Equipment Information]
+2. Select the target equipment in the equipment information management list
+3. Click [Edit]/[Delete] button in the corresponding column
+4. Edit/Delete equipment information
+5. Click [Confirm] button to complete the operation
+
+**[Note]** When editing/deleting equipment information for equipment already in use, confirm whether related business configurations are affected.
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Equipment Information Edit Function Page
+
+
+

+
Figure 2: Equipment Information Delete Function Page
+
+
+## 4. Business Relationship Description
+
+There is a master-slave relationship between equipment category management and equipment information management:
+
+```mermaid
+flowchart LR
+ A[Equipment Category Management] --> B[Equipment Category Definition]
+ B --> C[Equipment Information Management]
+ C --> D[Equipment Inspection]
+ C --> E[Equipment Repair]
+ C --> F[Equipment Maintenance]
+ C --> G[Equipment Consumables Management]
+ C --> H[Equipment Repair Management]
+```
\ No newline at end of file
diff --git a/en/device_management/equipment_consumables_management.md b/en/device_management/equipment_consumables_management.md
new file mode 100644
index 0000000..b27bab5
--- /dev/null
+++ b/en/device_management/equipment_consumables_management.md
@@ -0,0 +1,371 @@
+# Equipment Consumables Management
+
+## 1. Function Overview
+
+The Equipment Consumables Management module is used for full lifecycle management of various consumables (such as cutters, jigs, carriers, etc.) in production equipment, achieving clear classification, controllable lifespan, traceable usage, and predictable anomalies.
+
+**Core Features:**
+
+- Equipment Consumables Category Management: Uniformly maintain consumables categories and standardize data structure
+- Equipment Consumables Item Management: Establish complete consumables basic information and lifespan parameters
+- Equipment Consumables Lifespan Management: Record usage times and lifespan consumption in real-time, manage replacement processes, and ensure stable equipment operation
+- Equipment Consumables Replacement Log: Complete record of historical replacement records for traceability analysis
+
+**Feature Screenshots:**
+
+
+

+
Figure 1: Equipment Consumables Management Function Page
+
+
+

+
Figure 2: Equipment Consumables Category Function Page
+
+
+

+
Figure 3: Equipment Consumables Item Management Function Page
+
+
+

+
Figure 4: Equipment Consumables Lifespan Management Function Page
+
+
+

+
Figure 5: Equipment Consumables Replacement Log Function Page
+
+
+---
+
+## 2. Term Definitions
+
+### 2.1 Consumables Related Terms
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Consumables | Functional components with limited service life that require lifecycle management and regular replacement during production equipment operation | Such as: cutters, nozzles, filters, jigs, etc. |
+| Consumables Category | Classification by usage characteristics or lifecycle management method | Such as: count-based (cutters), time-based (filters), fixed-period replacement (lubrication parts) |
+| Consumables Item | Specific consumables instance registered in the system for lifecycle management and equipment binding | Such as: cutter (Φ3 drill bit), mounter nozzle, reflow oven filter, etc. |
+| Standard Lifespan | Maximum theoretical usable lifespan of consumables | Can be defined by count or time |
+| Warning Lifespan | Lifespan threshold for early warning trigger | Usually less than standard lifespan |
+| Lifespan Unit | Unit of measurement for consumables lifespan | Such as count, hours, days |
+| Used Lifespan | Accumulated usage count/duration of current consumables | Used for lifespan calculation |
+| Replacement Record | Historical record generated when consumables are replaced | Used for traceability and analysis |
+
+---
+
+## 3. Equipment Consumables Function Description
+
+### 3.1 Equipment Consumables Category Management
+
+Equipment consumables categories are used for hierarchical classification management of consumables, facilitating unified maintenance and quick retrieval.
+
+**Typical Usage Scenarios:**
+
+- When the system is first launched, all consumables categories need to be sorted out and entered to establish a basic classification system
+- When expanding business or introducing new equipment, add new consumables categories according to actual needs
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Consumables Category Code | Unique identifier for consumables category | ✓ |
+| Consumables Category Name | Name of consumables category | ✓ |
+| Creation Time | Automatically generated after addition | - |
+| Update Time | Automatically generated after editing | - |
+| Remarks | Supplementary description | - |
+
+**Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Equipment Consumables Management] → [Equipment Consumables Category]
+2. Click [Add] button
+3. Fill in category information
+4. Click [Confirm] to complete creation
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Equipment Consumables Category Management Add Function Page
+
+
+---
+
+### 3.2 Equipment Consumables Item Management
+
+Consumables item management is used to maintain basic information and lifespan parameters of all specific consumables.
+
+**Core Features:**
+
+- Maintain consumables basic archives
+- Bind consumables categories with equipment categories
+- Configure standard lifespan and warning lifespan
+- Support multiple lifespan units (count/time)
+
+**Typical Usage Scenarios:**
+
+- During asset planning or system initial launch, sort out and enter all consumables categories involved in equipment to establish a basic classification system
+- When importing new equipment or expanding production lines, add corresponding consumables items according to equipment structure
+- When introducing new wearing parts to equipment, add corresponding consumables items for management
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Consumables Item Code | Unique identifier | ✓ |
+| Consumables Item Name | Name description | ✓ |
+| Consumables Category | Associated category | ✓ |
+| Equipment Category | Applicable equipment type | ✓ |
+| Standard Lifespan | Maximum usable lifespan | ✓ |
+| Warning Lifespan | Early warning threshold | ✓ |
+| Lifespan Unit | Count/Hours/Days | ✓ |
+| Creation Time | System automatically records | - |
+| Update Time | System automatically records | - |
+| Remarks | Supplementary information | - |
+
+**Operation Steps:**
+
+- Single Addition
+
+ 1. Navigate to [Equipment Management] → [Equipment Consumables Management] → [Equipment Consumables Item Management]
+ 2. Click [Add] button
+ 3. Fill in consumables information
+ 4. Click [Confirm] to complete creation
+
+- Batch Addition
+
+ 1. Navigate to [Equipment Management] → [Equipment Consumables Management] → [Equipment Consumables Item Management]
+ 2. Click [Import] button
+ 3. Click [Download Template] button
+ 4. Fill in relevant content according to the template
+ 5. Click [Select File] and select the filled template file
+ 6. Preview information to confirm no issues
+ 7. Click [Confirm] button
+
+**[Tip]** It is recommended to set the warning lifespan to 80%~90% of the standard lifespan to ensure advance preparation for replacement.
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Equipment Consumables Item Management Add Function Page
+
+
+

+
Figure 2: Equipment Consumables Item Management Batch Import Function Page
+
+
+---
+
+### 3.3 Equipment Consumables Lifespan Management
+
+This function is used to bind specific consumables to equipment and manage their usage and lifespan status in real-time.
+
+**Core Features:**
+
+- Bind consumables to equipment
+- Record usage count or time in real-time
+- Automatically calculate remaining lifespan
+- Support manual lifespan adjustment
+- Support consumables replacement operation
+
+**Business Description:**
+
+Each equipment can be bound with multiple consumables. The system automatically accumulates consumables usage based on equipment operation data and performs lifespan calculation.
+
+**Typical Usage Scenarios:**
+
+- When new equipment is put into production or consumables are first bound, initialize the corresponding consumables and their used lifespan for the equipment
+- During equipment operation, automatically or manually report accumulated consumables usage lifespan to achieve real-time lifespan tracking
+- When consumables reach warning lifespan, remind maintenance personnel to prepare for replacement in advance
+- When consumables reach or exceed standard lifespan, perform replacement operation and reset the lifespan cycle
+- For scenarios where usage data cannot be automatically collected, supplement lifespan data through manual reporting
+
+**Field Description (Add Consumables Item):**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Consumables Item | Selected consumables item | ✓ |
+| Belonging Equipment | Select equipment to which the consumables item belongs | ✓ |
+| Standard Lifespan | Automatically loaded after selecting consumables item | - |
+| Warning Lifespan | Automatically loaded after selecting consumables item | - |
+| Used Lifespan | How much lifespan has been used at creation | ✓ |
+| Remarks | Remarks content | - |
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Consumables Lifespan Management Add
+
+
+**Field Description (Replace Consumables Item):**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Consumables Item | Selected consumables item | - |
+| Belonging Equipment | Select equipment to which the consumables item belongs | - |
+| Standard Lifespan | Automatically loaded after selecting consumables item | - |
+| Warning Lifespan | Automatically loaded after selecting consumables item | - |
+| Replacement Personnel | Replacement operator | ✓ |
+| Replacement Time | Replacement time | ✓ |
+| Replacement Reason | Dropdown selection (Abnormal Consumption/Normal Consumption/Exceed Standard Lifespan) | ✓ |
+| Replacement Duration | Time taken for replacement process | ✓ |
+| Remarks | Abnormal consumption information | - |
+
+**Replacement Reason Status Determination Rules:**
+
+| Status | Determination Condition |
+|--------|------------------------|
+| Abnormal Consumption | Usage < Warning Lifespan (may be damaged due to special reasons, e.g., cutter impact wear, need to describe in remarks) |
+| Normal Consumption | Usage ≥ Warning Lifespan and < Standard Lifespan |
+| Exceed Standard Lifespan | Usage ≥ Standard Lifespan |
+
+**Lifespan Status Determination Rules:**
+
+| Status | Determination Condition |
+|--------|------------------------|
+| Normal | Usage < Warning Lifespan |
+| Near Standard Lifespan | Usage ≥ Warning Lifespan and < Standard Lifespan |
+| Exceed Standard Lifespan | Usage ≥ Standard Lifespan |
+
+
+

+
Figure 1: Equipment Consumables Lifespan Management Status
+
+
+**Operation Steps (Replace Consumables):**
+
+1. Navigate to [Equipment Management] → [Consumables Management] → [Equipment Consumables Lifespan Management]
+2. Select target equipment and consumables
+3. Click [Replace] button
+4. Fill in replacement information
+5. Click [Confirm] to complete replacement
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Consumables Lifespan Management Replace
+
+
+**Operation Steps (Manual Report Lifespan):**
+
+1. Navigate to [Equipment Management] → [Consumables Management] → [Equipment Consumables Lifespan Management]
+2. Select target equipment and consumables
+3. Click [Report Lifespan] button
+4. Fill in current used lifespan
+5. Click [Confirm] to complete reporting
+
+**[Important]** Consumables exceeding lifespan should be prohibited from continued production or require mandatory confirmation before continued use.
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Consumables Lifespan Management Report
+
+
+---
+
+### 3.4 Equipment Consumables Replacement Log
+
+Used to record all consumables replacement history, achieving full-process traceability and data analysis.
+
+**Core Features:**
+
+- Record detailed information for each replacement
+- Support query by equipment/consumables/replacement time/creation time
+- Support replacement reason analysis
+- Support replacement duration statistics
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Equipment Code | Query specified equipment |
+| Consumables Item Code | Query specified consumables item |
+| Consumables Item Name | Query specified consumables item |
+| Replacement Time Range | Filter time interval |
+| Creation Time Range | Filter time interval |
+
+**Replacement Record Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Belonging Equipment | Equipment name |
+| Consumables Item Code | Replaced consumables item code |
+| Consumables Item Name | Replaced consumables item name |
+| Standard Lifespan | Standard lifespan value |
+| Warning Lifespan | Warning lifespan value |
+| Used Lifespan | Usage before replacement |
+| Replacement Reason | Normal replacement/abnormal damage, etc. |
+| Replacement Time | Actual replacement time |
+| Replacement Personnel | Operator |
+| Replacement Duration | Time taken for replacement |
+| Remarks | Abnormal consumption remarks |
+
+**[Tip]** The replacement log can be used to analyze the difference between actual lifespan and theoretical lifespan of consumables for optimizing maintenance strategies.
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Equipment Consumables Replacement Log Function Page
+
+
+
+

+
Figure 2: Equipment Consumables Replacement Log Export Function
+
+
+
+

+
Figure 3: Equipment Consumables Replacement Log Export File Download
+
+
+---
+
+## 4. Data Management Standards
+
+### 4.1 Data Integrity Requirements
+
+**[Important]** To ensure the effectiveness of consumables management, it is necessary to ensure:
+
+- All consumables must have standard archives established
+- All critical consumables for equipment must be bound and managed
+- All replacement operations must be logged
+- Usage data must be collected in real-time or near real-time
+
+---
+
+### 4.2 Management Rules
+
+| Rule | Description |
+|------|-------------|
+| Uniqueness | Consumables item code is globally unique |
+| Relevance | Consumables items must be associated with equipment categories |
+| Real-time | Usage data must be updated timely |
+| Traceability | All replacement records must be queryable |
+
+---
+
+## 5. Common Issues and Handling
+
+### 5.1 Common Issues
+
+| Issue Phenomenon | Possible Cause | Handling Method |
+|-----------------|----------------|----------------|
+| Lifespan not updated | Data not collected | Check equipment data interface |
+| Premature damage | Abnormal usage | Analyze process or operation issues |
+| Warning not triggered | Incorrect warning configuration | Check lifespan parameter settings |
+| No replacement record | Replacement process not executed | Force standardized operation process |
+
+---
+
+### 5.2 Optimization Suggestions
+
+- It is recommended to automatically collect usage count based on equipment operation data
+- Establish mandatory replacement mechanism for critical consumables
+- Regularly analyze consumables lifespan and costs
+
+**[Tip]** For high-value or critical consumables, it is recommended to implement linkage control with equipment status management.
\ No newline at end of file
diff --git a/en/device_management/equipment_inspection.md b/en/device_management/equipment_inspection.md
new file mode 100644
index 0000000..dadd755
--- /dev/null
+++ b/en/device_management/equipment_inspection.md
@@ -0,0 +1,349 @@
+# Equipment Inspection
+
+## 1. Function Overview
+
+The Equipment Inspection function is used to standardize daily inspection and maintenance management of production equipment. Through standardized inspection processes, it achieves visualized equipment status, traceable anomalies, and preventive maintenance, thereby ensuring stable equipment operation and production continuity.
+
+**Core Features:**
+
+- Inspection Item Management: Maintain basic data for equipment inspection items
+- Inspection Data Entry: Support multi-terminal (PC and PDA) inspection result entry
+- Inspection Log Records: Complete recording of inspection history data for traceability
+- Anomaly Interception Mechanism: Prohibit equipment operation/material input when inspection fails
+
+**Feature Screenshots:**
+
+
+

+
Figure 1: Equipment Inspection Function Page
+
+
+

+
Figure 2: Equipment Inspection Item Management Function Page
+
+
+

+
Figure 3: Equipment Inspection Entry Function Page
+
+
+

+
Figure 4: Equipment Inspection Log Function Page
+
+
+## 2. Term Definitions
+
+### 2.1 Inspection Related Terms
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Inspection | Checking equipment according to specified items | Basic work of equipment management, confirming whether equipment meets operation standards |
+| Inspection Item | Specific content or parts to be inspected | Such as temperature, pressure, appearance, usage count, etc. |
+| Inspection Standard | Criteria for judging whether inspection results are qualified | Such as value range, status description, etc. |
+| Inspection Record | Recorded data of inspection results | Supports traceability and analysis |
+| Inspection Result | Status judgment obtained after inspection | Such as OK, NG |
+| Abnormal Inspection | Equipment abnormality found during inspection | Requires timely handling |
+| Missed Inspection | Inspection not performed as required | Belongs to management abnormality |
+| Supplementary Inspection | Supplementary inspection for missed or abnormal situations | Used for data correction |
+| Inspection Personnel | Personnel performing inspection tasks | Can be operators or equipment personnel |
+| Inspection Equipment | Equipment object being inspected | Can be detailed to parts |
+| Inspection Method | Execution method of inspection | Such as manual inspection, QR code inspection, automatic collection |
+| Inspection Qualification Rate | Ratio of qualified inspection count to total inspection count | Used to evaluate equipment status |
+| Anomaly Interception | Block equipment with failed inspection | Failed inspection prompts that equipment is not allowed to start production |
+
+## 3. Inspection Business Process
+
+- Flowchart
+
+```mermaid
+flowchart TD
+ A[Start] --> A1[Inspection Item Configuration]
+ A1 --> A2[Configure Inspection Standards/Judgment Rules]
+ A2 --> A3[Bind Equipment Category]
+ A3 --> A4[Generate Inspection Plan (by shift/date)]
+ A4 --> B{Inspection Method}
+
+ B -->|PDA| C[Execute Inspection on PDA (before first startup of shift/day)]
+ B -->|PC| D[Execute Inspection on PC (before first startup of shift/day)]
+
+ C --> E{Inspection Passed?}
+ E -->|Pass| F[Allow Loading]
+ E -->|Fail| G[Prohibit Loading]
+
+ D --> H{Inspection Passed?}
+ H -->|Pass| I[Allow Equipment to Enter Automatic Operation]
+ H -->|Fail| J[Prohibit Equipment from Entering Automatic Operation]
+
+ F --> K[Production Start]
+ I --> K
+
+ G --> L[Handle Anomaly or Re-inspect]
+ J --> L
+```
+
+## 4. Equipment Inspection Function Description
+
+### 4.1 Equipment Inspection Item Management
+
+Equipment Inspection Item Management is used to uniformly configure and maintain equipment inspection content, clarifying inspection methods and judgment standards for various inspection items.
+
+#### 4.1.1 Inspection Item Basic Information
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Item Code | Unique identifier for inspection item | ✓ |
+| Item Name | Name of inspection item | ✓ |
+| Equipment Type | Applicable equipment type classification | ✓ |
+| Inspection Method | Description of inspection method (e.g., detect using temperature and humidity meter) | - |
+| Inspection Standard | Judgment standard (e.g., humidity ≤ 50%RH) | - |
+| Inspection Unit | Data unit (e.g., %RH) | - |
+| Enabled | Whether to enable this inspection item | - |
+| Remarks | Supplementary description information | - |
+
+---
+
+#### 4.1.2 Inspection Item Status Definition
+
+| Status | Description | Business Scenario |
+|--------|-------------|------------------|
+| Enabled | This inspection item is active | Equipment needs to perform this inspection item |
+| Disabled | This inspection item is inactive | Temporarily not required to perform this inspection item |
+
+---
+
+#### 4.1.3 Inspection Item Creation
+
+**Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Equipment Inspection] → [Equipment Inspection Item Management]
+2. Select [Equipment Category]
+3. Click [Add] button
+4. Fill in inspection item basic information
+5. Click [Confirm] to complete creation
+6. Submit to inspection manager for approval (if approval process is enabled)
+
+**[Tip]** Inspection items are configured uniformly by "Equipment Category". Equipment under the same category share inspection items; if equipment differs significantly, it is recommended to split equipment categories.
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Equipment Inspection Item Management Add Function Page
+
+
+

+
Figure 2: Equipment Inspection Item Management Add Function Page
+
+
+### 4.2 Equipment Inspection Entry Management
+
+Equipment Inspection Entry Management is used for operators to enter and submit equipment inspection results, supporting filling in inspection values and judgment results. The system records complete inspection data for traceability and verification.
+
+#### 4.2.1 Inspection Entry Basic Information
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Inspection Value | Detected data (fill in for numerical items; optional for judgment items) | - |
+| Inspection Result | Inspection judgment result (OK / NG) | ✓ |
+| Inspector | Inspection personnel | ✓ |
+| Shift | Morning shift/Evening shift | ✓ |
+
+---
+
+#### 4.2.2 Inspection Result Status Definition
+
+| Status | Description | Business Scenario |
+|--------|-------------|------------------|
+| OK | Inspection passed | Meets startup conditions |
+| NG | Inspection failed | Prohibits equipment operation |
+
+---
+
+#### 4.2.3 Inspection Entry Methods
+
+| Method | Description | Applicable Scenario |
+|--------|-------------|-------------------|
+| PDA | Handheld terminal for inspection data entry | No PC workstation (e.g., electrode section) |
+| PC | Computer terminal for inspection data entry | Assembly section, finished product section, etc. |
+
+---
+
+#### 4.2.4 Equipment Inspection Operation
+
+**PC Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Equipment Inspection] → [Equipment Inspection Entry]
+2. Select [Equipment Category] → View equipment list
+3. Click [Add Inspection Log] for the target equipment
+4. Fill in inspection value and select inspection result
+5. Click [Submit] to complete inspection
+6. The system controls whether equipment can produce based on inspection results
+
+**[Tip]** Whether inspection is performed via PC or PDA, it is strongly bound to equipment startup production permissions.
+
+---
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Equipment Inspection Entry PC Add Function Page
+
+
+

+
Figure 2: Equipment Inspection Entry PC Add Function Page
+
+
+---
+
+**PDA Operation Steps:**
+
+1. Navigate to [Production] → [Equipment Inspection]
+2. Scan equipment QR code
+3. The system loads the inspection item list
+4. Fill in inspection data and select inspection result
+5. Enter [Inspector] and select shift [Morning/Evening]
+6. Click [Upload Inspection Information]
+7. Return to production module to perform production operations
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Equipment Inspection Entry PDA Add Function Page
+
+
+

+
Figure 2: Equipment Inspection Entry PDA Add Function Page
+
+
+### 4.3 Equipment Inspection Log Management
+
+#### 4.3.1 Function Description
+
+Equipment inspection logs are used to record the execution of each inspection, including inspector, inspection time, inspection result, and related data, achieving full-process traceability.
+
+**Core Features:**
+
+- Inspection record query
+- Historical data traceability
+
+---
+
+#### 4.3.2 Query Conditions
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Equipment Name | Query specified equipment |
+| Device Code | Query specified device code |
+| Equipment Category | Filter by equipment category |
+| Inspection Date | Query time range |
+| Inspection Personnel | Query inspection records by personnel |
+
+---
+
+#### 4.3.3 Log Field Description
+
+| Field | Description |
+|-------|-------------|
+| Device Code | Device code of inspected equipment |
+| Device Name | Device name of inspected equipment |
+| Equipment Category | Equipment category of inspected equipment |
+| Total Inspection Items | Number of equipment inspection items |
+| Total NG Inspections | Number of NG inspections |
+| NG Rate % | NG percentage |
+| Inspection Result | OK / NG |
+| Operator | Inspection personnel |
+| Inspection Time | Inspection execution time |
+| Details | View inspection item details |
+
+---
+
+#### 4.3.4 Log Management Instructions
+
+**[Note]**
+
+- Inspection logs are critical production data and cannot be deleted arbitrarily
+- If modification is needed, it should be corrected through the exception handling process
+
+**[Tip]** It is recommended to regularly analyze inspection logs to identify potential equipment risks and perform maintenance in advance.
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Equipment Inspection Log Query Function Page
+
+
+

+
Figure 2: Equipment Inspection Log Query Function Page
+
+
+## 5. Common Issues and Handling
+
+### 5.1 Inspection Anomaly Handling
+
+| Issue Phenomenon | Possible Cause | Handling Method |
+|-----------------|----------------|----------------|
+| Cannot submit inspection | Required fields not filled | Check if inspection result has been selected |
+| Abnormal inspection result (NG) | Detected data does not meet standards | Handle equipment issue according to exception process |
+| Cannot load inspection items | Inspection items not configured | Contact administrator to configure inspection items |
+| PDA cannot submit data | Network exception or incomplete data | Check network or supplement data and resubmit |
+
+**[Important]** When inspection result is NG, equipment must stop using and be re-inspected after the issue is resolved.
+
+---
+
+### 5.2 Inspection Process Anomaly
+
+| Issue Phenomenon | Possible Cause | Handling Method |
+|-----------------|----------------|----------------|
+| Equipment cannot start | Inspection not completed or failed | Complete inspection and ensure result is OK |
+| Can produce without inspection | System control not enabled | Check inspection and equipment control binding configuration |
+
+**[Note]** It is recommended to enable the "Mandatory Inspection Before Startup" mechanism to avoid missed inspection risks.
+
+---
+
+## 6. Inspection Data Management Standards
+
+### 6.1 Data Integrity Requirements
+
+**[Important]**
+To ensure the authenticity and effectiveness of inspection data, the following requirements must be met:
+
+- All equipment must have inspection items configured
+- Inspection must be completed before each production
+- Inspection results must be filled in truthfully without falsification
+- Inspection anomalies must be recorded and handled
+- Inspection records must be associated with equipment and personnel
+
+---
+
+### 6.2 Data Management Rules
+
+| Rule | Description |
+|------|-------------|
+| Data Authenticity | Inspection data must truly reflect equipment status |
+| Data Completeness | Inspection records must be complete without missing entries |
+| Data Timeliness | Inspection data must be entered in real-time or during the shift |
+| Data Relevance | Inspection records must be associated with equipment, personnel, and time |
+
+---
+
+### 6.3 Inspection Frequency Recommendations
+
+| Inspection Type | Recommended Frequency | Description |
+|----------------|---------------------|-------------|
+| Startup Inspection | Once per shift/day | Must be performed before startup |
+| Process Inspection | According to process requirements | Critical process equipment |
+| Routine Inspection | Daily/Weekly | Equipment operation status check |
+| Special Inspection | As needed | After anomaly or maintenance |
+
+**[Tip]**
+Different inspection frequencies can be set according to equipment importance to achieve refined management.
\ No newline at end of file
diff --git a/en/device_management/equipment_maintenance.md b/en/device_management/equipment_maintenance.md
new file mode 100644
index 0000000..a867cdf
--- /dev/null
+++ b/en/device_management/equipment_maintenance.md
@@ -0,0 +1,237 @@
+# Equipment Maintenance
+
+## 1. Function Overview
+
+The Equipment Maintenance module is used to standardize management of daily maintenance, periodic servicing, and maintenance execution processes for production equipment, achieving extended equipment lifespan, fault prevention, and traceable maintenance processes.
+
+**Core Features:**
+
+- Maintenance Plan Management: Support periodic maintenance plan formulation by time/operating hours
+- Maintenance Task Assignment: Automatically or manually generate maintenance tasks and assign responsible persons
+- Maintenance Execution Records: Record maintenance processes, results, and related data
+- Equipment Maintenance Item Management: Define maintenance items and operation standards for different equipment
+- Maintenance Reminders and Warnings: Automatically remind about upcoming or overdue tasks according to plans
+- Maintenance History Traceability: Support query and analysis of equipment lifecycle maintenance records
+
+---
+
+## 2. Term Definitions
+
+### 2.1 Equipment Maintenance Related Terms
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Equipment Maintenance | Regular maintenance and inspection activities performed on equipment | Including cleaning, lubrication, tightening, adjustment, etc. |
+| Maintenance Cycle | Time or usage frequency interval for maintenance execution | Such as daily, weekly, every 100 operating hours |
+| Maintenance Plan | Predefined maintenance arrangements in the system | Basis for automatic generation of maintenance tasks |
+| Maintenance Task | A specific maintenance job to be executed | Triggered by plan or manually created |
+| Maintenance Standard | Maintenance content specifications for each type of equipment | Includes steps, requirements, and judgment criteria |
+| Maintenance History | Collection of historical maintenance records for equipment | Used to analyze equipment status and reliability |
+
+---
+
+## 3. Maintenance Management
+
+### 3.1 Maintenance Plan Management
+
+Maintenance plans define periodic maintenance rules for equipment and serve as the basis for generating maintenance tasks.
+
+**Plan Types:**
+
+| Type | Description | Example |
+|------|-------------|---------|
+| Time Cycle | Execute at fixed time intervals | Daily/Weekly/Monthly |
+| Operating Hours | Execute based on accumulated equipment operating time | Every 100 operating hours |
+| Custom Cycle | Flexibly set execution rules | Every 3 days or every 500 units produced |
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Plan Number | Unique identifier for maintenance plan | - |
+| Equipment Number | Equipment requiring maintenance | Yes |
+| Maintenance Type | Daily/Weekly/Monthly/Annual maintenance | Yes |
+| Maintenance Cycle | Execution cycle rule | Yes |
+| Maintenance Items | Corresponding maintenance content list | Yes |
+| Responsible Person | Personnel or position responsible for execution | Yes |
+| Enabled Status | Whether the plan is enabled | Yes |
+
+---
+
+### 3.2 Maintenance Task Generation
+
+The system automatically generates maintenance tasks based on maintenance plans and also supports manual creation of temporary maintenance tasks.
+
+**Task Sources:**
+
+- Auto-generated: System triggers automatically by cycle
+- Manually created: Created by administrator or equipment manager
+- Exception triggered: Special maintenance triggered after equipment abnormality
+
+**Task Status:**
+
+| Status | Description |
+|--------|-------------|
+| Pending | Generated but not started |
+| In Progress | Maintenance is underway |
+| Completed | Maintenance completed and recorded |
+| Overdue | Not executed beyond planned time |
+
+---
+
+### 3.3 Maintenance Standard Management
+
+Maintenance standards are used to standardize maintenance content and execution requirements for different equipment.
+
+**Maintenance Content Examples:**
+
+| Item | Content | Standard Requirements |
+|------|---------|---------------------|
+| Cleaning | Clean equipment surface dust | No obvious dust accumulation |
+| Lubrication | Add lubricating oil to moving parts | Moderate oil level, no dry friction |
+| Tightening | Check for loose screws | No looseness |
+| Inspection | Check electrical/mechanical status | No abnormalities |
+
+**[Important]** Maintenance standards should be uniformly developed by equipment engineering or process personnel to ensure consistency.
+
+---
+
+## 4. Maintenance Execution Operations
+
+### 4.1 Maintenance Task Execution
+
+**Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Equipment Maintenance] → [Maintenance Tasks]
+2. Select the maintenance task to execute from the task list
+3. Click [Start Execution] button
+4. Complete maintenance content item by item according to maintenance standards
+5. Fill in maintenance results and remark information
+6. Click [Complete Maintenance] button to submit the record
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Task Number | Unique number for maintenance task | - |
+| Executor | Personnel actually performing maintenance | Yes |
+| Execution Time | Start/end time of maintenance | Yes |
+| Maintenance Result | Normal/Abnormal | Yes |
+| Abnormality Description | If abnormal, fill in specific situation | No |
+| Handling Measures | Abnormality handling method | No |
+
+**[Note]** If abnormalities are found during maintenance, they should be recorded and reported immediately.
+
+---
+
+### 4.2 Maintenance Result Recording
+
+After maintenance is completed, the system records detailed execution data for subsequent analysis.
+
+**Recording Content:**
+
+- Maintenance item execution status
+- Abnormal points and handling results
+- Actual execution time
+- Executor information
+
+**[Tip]** It is recommended to perform on-site recording on mobile terminals (PDA) to improve data real-time performance.
+
+---
+
+## 5. Maintenance History Query
+
+### 5.1 Query Condition Settings
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Equipment Number | Query specified equipment |
+| Maintenance Type | Daily/Weekly/Monthly maintenance |
+| Time Range | Maintenance execution time range |
+| Executor | Specified personnel |
+| Maintenance Result | Normal/Abnormal |
+
+---
+
+### 5.2 Query Result Display
+
+**Maintenance History Example:**
+
+| Date | Equipment | Maintenance Type | Executor | Result | Status |
+|------|-----------|-----------------|----------|--------|--------|
+| 2026-04-10 | Equipment A | Daily | Zhang San | Normal | Completed |
+| 2026-04-12 | Equipment A | Weekly | Li Si | Abnormal | Processed |
+
+**[Tip]** Click the record to view detailed maintenance content and abnormality handling process.
+
+---
+
+## 6. Maintenance Reminders and Warnings
+
+### 6.1 Reminder Mechanism
+
+The system automatically reminds relevant personnel according to maintenance plans:
+
+- Upcoming reminder (advance notification)
+- Same-day maintenance reminder
+- Overdue non-execution reminder
+
+### 6.2 Warning Rules
+
+| Warning Type | Trigger Condition | Handling Suggestion |
+|--------------|------------------|---------------------|
+| Overdue Warning | Not executed beyond planned time | Arrange execution immediately |
+| Frequent Abnormalities | Multiple abnormalities during maintenance | Conduct equipment inspection |
+| Long-term No Maintenance | No maintenance records | Check plan configuration |
+
+**[Important]** Long-term non-execution of maintenance may significantly increase equipment failure risk.
+
+---
+
+## 7. Data Management Standards
+
+### 7.1 Data Integrity Requirements
+
+- All equipment must have maintenance plans configured
+- All maintenance tasks must record execution results
+- Abnormal situations must include handling measures
+- Maintenance records must be associated with equipment numbers
+
+---
+
+### 7.2 Maintenance Management Rules
+
+| Rule | Description |
+|------|-------------|
+| Plan Uniqueness | Only one maintenance plan of the same type for the same equipment |
+| Execution Timeliness | Maintenance tasks should be completed on time |
+| Data Authenticity | Maintenance records must be true and valid |
+| Closed-loop Management | Abnormalities must have handling results |
+
+**[Note]** Maintenance data is an important basis for equipment reliability analysis and must ensure accuracy.
+
+---
+
+## 8. Common Issues and Handling
+
+### 8.1 Maintenance Abnormality Handling
+
+| Issue Phenomenon | Possible Cause | Handling Method |
+|-----------------|----------------|----------------|
+| Maintenance not executed | Personnel oversight | Supplement execution and strengthen reminders |
+| Missing maintenance records | Not filled in timely | Supplement data entry |
+| Abnormality not handled | Not reported | Handle immediately and close the loop |
+| Frequent abnormalities | Equipment aging | Arrange inspection or replacement |
+
+---
+
+### 8.2 Maintenance Optimization Suggestions
+
+- Establish standardized maintenance templates
+- Use scanning/PDA for maintenance execution
+- Regularly analyze maintenance data
+- Link maintenance with equipment status
+
+**[Tip]** It is recommended to combine with equipment status management to achieve predictive maintenance (PM).
\ No newline at end of file
diff --git a/en/device_management/equipment_maintenance_management.md b/en/device_management/equipment_maintenance_management.md
new file mode 100644
index 0000000..301c4c5
--- /dev/null
+++ b/en/device_management/equipment_maintenance_management.md
@@ -0,0 +1,344 @@
+# Equipment Repair Management
+
+## 1. Function Overview
+
+Equipment Repair Management is used for closed-loop management of the entire process from repair application, review confirmation to repair completion, achieving transparent repair processes, traceable responsibilities, and recordable data.
+
+**Core Features:**
+
+- Equipment Repair Application Management: Manages the entire repair process, supporting repair application, repair review confirmation, repair processing, repair completion, and repair cancellation operations, achieving closed-loop repair process management
+- Equipment Repair Records: Manages historical equipment repair data, supporting repair record query and traceability, repair order detail viewing and management, achieving traceable and analyzable repair data
+
+---
+
+**Feature Screenshots:**
+
+
+

+
Figure 1: Equipment Repair Management Module
+
+
+

+
Figure 2: Equipment Repair Application Management
+
+
+

+
Figure 3: Equipment Repair Records
+
+
+## 2. Term Definitions
+
+### 2.1 Repair Related Terms
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Repair Application | Repair application document initiated after equipment abnormality | Serves as the starting point of the repair process |
+| Repair Confirmation | Secondary confirmation of repair application | Determines whether to enter repair process |
+| Repair Personnel | Personnel actually performing equipment repair | Can be internal or external personnel |
+| Repair Status | Status indicator in the repair process | Used to track repair progress |
+| Repair Record | Historical data of completed repairs | Used for traceability and analysis |
+
+---
+
+## 3. Function Module Description
+### 3.1 Equipment Repair Application Management
+
+The Equipment Repair Application Management page is used to initiate repair applications and manage the entire repair process.
+
+**Core Features:**
+
+- Repair application creation
+- Repair review confirmation
+- Repair task execution
+- Repair status flow management
+- Repair cancellation operation
+
+**Typical Usage Scenarios:**
+
+1. **Equipment Sudden Failure Handling**
+ - Equipment suddenly stops or alarms abnormally during production
+ - Operator initiates repair application immediately
+ - Reviewer confirms and arranges repair personnel to handle
+ - Resume production after repair completion
+
+2. **Equipment Abnormal but Operational**
+ - Equipment shows minor abnormalities (e.g., abnormal noise, parameter fluctuations)
+ - On-site personnel initiates repair application
+ - Reviewer evaluates whether to repair immediately or postpone
+ - Record handling results after repair completion
+
+3. **False Alarm or No Repair Needed**
+ - No actual fault found after repair application
+ - Reviewer confirms on-site that repair is not needed
+ - Directly cancel repair, process ends
+
+4. **Planned Repair Trigger**
+ - Potential issues found during inspection or patrol
+ - Initiate repair application in advance
+ - Arrange repair after review to avoid equipment failure escalation
+
+---
+
+#### 3.1.1 Status Description
+
+| Status | Description |
+|--------|-------------|
+| Pending Confirmation | Repair application submitted, waiting for reviewer confirmation |
+| In Repair | Review passed, repair personnel processing |
+| Completed | Repair completed and closed |
+| Cancelled | Repair cancelled or review rejected |
+
+**[Note]** Once status enters "Completed" or "Cancelled", it cannot flow by default.
+
+---
+
+#### 3.1.2 Repair Process
+
+```mermaid
+flowchart LR
+ A[Initiate Repair] --> B[Pending Confirmation]
+ B -->|Review Passed| C[In Repair]
+ B -->|Review Rejected/Cancelled| D[Cancelled]
+ C --> E[Repair Completed]
+ E --> F[Completed]
+```
+
+#### 3.1.3 Repair Application
+
+**Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Equipment Repair Management] → [Equipment Repair Application Management]
+2. Click [Apply for Repair] button
+3. Fill in repair information
+4. Click [Confirm] button
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Repair Equipment | Name of equipment requiring repair | ✓ |
+| Repair Description | Description of equipment abnormality or failure | ✓ |
+| Repair Order Number | System automatically generated | - |
+| Requester | Repair personnel automatically obtained from login account | - |
+
+**Feature Screenshots:**
+
+
+

+
Figure 1: Repair Application Function
+
+
+

+
Figure 2: Repair Application Confirmation
+
+
+---
+
+#### 3.1.4 Repair Review
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Repair Required | Whether equipment shutdown repair is needed | ✓ |
+| Consumables Replacement | Whether consumables need to be replaced | ✓ |
+| Failure Cause | Need reviewer to confirm and fill in | ✓ |
+| Repair Measures | Need reviewer to provide repair plan | ✓ |
+
+**Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Equipment Repair Management] → [Equipment Repair Application Management]
+2. Select repair order with status "Pending Confirmation"
+3. On-site judgment of actual situation, whether repair is needed
+4. If no repair needed, click [Cancel Application] directly
+5. If repair needed, click [Confirm Repair] button
+6. Fill in relevant repair information
+7. Click [Confirm] button, review completed
+
+**Flowchart:**
+
+```mermaid
+flowchart LR
+ A[Enter Equipment Repair Application Management] --> B[Select Pending Confirmation Repair Order]
+ B --> C[On-site Confirm Equipment Condition]
+
+ C --> D{Repair Needed?}
+
+ D -->|No| E[Click Cancel Application]
+ E --> F[Status Changed to Cancelled]
+
+ D -->|Yes| G[Click Confirm Repair]
+ G --> H[Fill Repair Related Information]
+ H --> I[Confirm Submit]
+
+ I --> J[Status Changed to In Repair]
+```
+
+**[Important]** After review passes, the repair order automatically enters "In Repair" status.
+
+**Feature Screenshots:**
+
+
+

+
Figure 1: Repair Confirmation Information Entry
+
+
+

+
Figure 2: Repair Confirmation Completed
+
+
+---
+
+#### 3.1.5 Repair Processing
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Repair Personnel | Repair executor, system automatically obtains account | - |
+| Consumables Replaced | Select consumables replaced during repair | ✓ |
+| Repair Result | Fixed/Replaced/Temporarily handled, etc. | ✓ |
+| Completion Time | Repair completion time | System automatically generated |
+
+**Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Equipment Repair Management] → [Equipment Repair Application Management]
+2. Select repair order with status "In Repair"
+3. Go to site to repair equipment
+4. After equipment repair completed, click [Complete Repair] button
+5. Fill in repair result information
+6. Click [Confirm] button
+
+**Flowchart:**
+
+```mermaid
+flowchart LR
+ A[Enter Equipment Repair Application Management] --> B[Select In Repair Order]
+ B --> C[On-site Equipment Repair]
+
+ C --> D{Repair Completed?}
+
+ D -->|No| C
+ D -->|Yes| E[Click Complete Repair]
+
+ E --> F[Fill Repair Result Information]
+ F --> G[Confirm Submit]
+
+ G --> H[Status Changed to Completed]
+```
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Repair Completion Information Entry
+
+
+### 3.2 Equipment Repair Records
+
+#### 3.2.1 Function Description
+
+The Equipment Repair Records page is used for unified management and query of all completed repair data.
+
+**Core Features:**
+
+- Repair record list display
+- Conditional query and filtering
+- Repair detail viewing
+
+---
+
+#### 3.2.2 Query Conditions
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Equipment Name | Select equipment to query |
+| Repair Order Number | Exact or fuzzy query |
+| Repair Time Range | Query specified time period |
+
+---
+
+#### 3.2.3 Repair Record List
+
+The repair record list displays all completed repair data.
+
+**Display Fields:**
+
+| Field | Description |
+|-------|-------------|
+| Repair Order Number | Unique number for repair record |
+| Equipment Name | Name of repaired equipment |
+| Equipment Number | Unique equipment number |
+| Requester | Personnel who initiated repair |
+| Repair Description | Failure information filled during repair application |
+| Repair Result | Final handling result |
+| Repair Personnel | Personnel who performed repair |
+| Repair Time | Time when repair started |
+| Repair Start Time | Start time of repair |
+| Repair Completion Time | Completion time of repair |
+| Actual Repair Duration (min) | Duration of repair |
+
+**Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Equipment Repair Management] → [Equipment Repair Records]
+
+**[Tip]** Click repair order number to view detailed information.
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Equipment Repair Records
+
+
+---
+
+### 3.2.4 Repair Order Details
+
+Repair order details display complete information for a single repair record.
+
+**Operation Steps:**
+
+1. Navigate to [Equipment Management] → [Equipment Repair Management] → [Equipment Repair Records]
+2. Click [Details] button in the operation column of corresponding order number
+3. View detailed repair order
+
+**Details include:**
+
+- Basic information (equipment, requester, time, etc.)
+- Repair details
+- Maintenance details
+- Consumables replacement records
+
+**Feature Screenshot:**
+
+
+

+
Figure 1: Repair Order Details
+
+
+## 4. Data Management Requirements
+
+### 4.1 Data Integrity
+
+**[Important]** To ensure traceability of repair data, the following information must be complete:
+
+- All repairs must include failure descriptions
+- All repairs must include repair content and results
+- Review records must be retained
+- Status flow must comply with process rules
+
+---
+
+### 4.2 Status Flow Rules
+
+| Current Status | Action | Next Status |
+|----------------|--------|-------------|
+| Pending Confirmation | Review Passed | In Repair |
+| Pending Confirmation | Review Rejected | Cancelled |
+| In Repair | Repair Completed | Completed |
+| In Repair | Repair Cancelled | Cancelled |
+
+**[Note]** Cross-status jumps are prohibited; flow must follow the process step by step.
\ No newline at end of file
diff --git a/en/device_management/equipment_status_management.md b/en/device_management/equipment_status_management.md
new file mode 100644
index 0000000..9c78e3e
--- /dev/null
+++ b/en/device_management/equipment_status_management.md
@@ -0,0 +1,196 @@
+# 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:**
+
+
+

+
Figure 1: Equipment Status Management Page
+
+
+---
+
+## 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:**
+
+
+

+
Figure 1: Equipment Status Management Running Status Filter
+
+
+

+
Figure 2: Equipment Status Management Waiting Status Filter
+
+
+

+
Figure 3: Equipment Status Management Manual Status Filter
+
+
+## 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.
\ No newline at end of file
diff --git a/en/getting-started/quick-start.md b/en/getting-started/quick-start.md
new file mode 100644
index 0000000..59072eb
--- /dev/null
+++ b/en/getting-started/quick-start.md
@@ -0,0 +1,372 @@
+# Quick Start
+
+## 1. System Login
+
+### 1.1 Pre-login Preparation
+
+Before logging into the system, please ensure you have completed the following preparations:
+
+| Preparation Item | Description |
+|------------------|-------------|
+| Account Activation | Contact the system administrator to apply for an account |
+| Browser Preparation | Recommended browsers: Chrome, Firefox, or Edge |
+| Network Connection | Ensure access to the MES system server |
+| Client Installation | Some features require plugin installation (prompted on first login) |
+
+### 1.2 Login Operations
+
+**Login Steps:**
+
+1. Open a browser and enter the system URL (e.g., `http://mes.yourcompany.com`)
+2. Go to the login page
+3. Enter username and password
+4. Click [Login] button
+5. After system verification, enter the main interface
+
+**[Tip]** It is recommended to change the initial password and complete personal profile on first login.
+
+### 1.3 Forgot Password
+
+If you forget your password, you can reset it through the following methods:
+
+| Reset Method | Operation |
+|-------------|-----------|
+| Self-service Recovery | Click "Forgot Password" on the login page, reset via bound email/mobile |
+| Administrator Reset | Contact system administrator to manually reset password |
+
+## 2. System Main Interface
+
+### 2.1 Main Interface Layout
+
+```
+┌────────────────────────────────────────────────────────────┐
+│ Top Bar │
+│ ┌──────────────┬──────────────────────────────┬─────────┐ │
+│ │ Logo │ System Name │ User Info│ │
+│ └──────────────┴──────────────────────────────┴─────────┘ │
+├────────────────────────────────────────────────────────────┤
+│ Navigation Bar │
+│ ┌────────────────────────────────────────────────────────┐ │
+│ │ 📊 Home │ 📋 Production │ 📦 Quality │ 🏭 Warehouse │ 🔧 Equipment │ ⚙️ System │ │
+│ └────────────────────────────────────────────────────────┘ │
+├────────────────────────────────────────────────────────────┤
+│ │
+│ Main Content Area │
+│ ┌────────────────────────────────────────────────────────┐ │
+│ │ │ │
+│ │ Welcome to HF-MES v5.0 Manufacturing Execution System │ │
+│ │ │ │
+│ │ ┌─────────────┐ ┌─────────────┐ │ │
+│ │ │ To-do List │ │ Production Board│ │ │
+│ │ └─────────────┘ └─────────────┘ │ │
+│ │ │ │
+│ └────────────────────────────────────────────────────────┘ │
+│ │
+└────────────────────────────────────────────────────────────┘
+```
+
+### 2.2 Function Menu
+
+The system's main functional modules include:
+
+| Module | Function Description |
+|--------|---------------------|
+| Home | System homepage, to-do items, production dashboard |
+| Production Management | Work order management, production reporting, production monitoring |
+| Quality Management | Incoming inspection, process inspection, quality traceability |
+| Warehouse Logistics | Receiving management, issuing management, inventory management |
+| Equipment Management | Equipment ledger, inspection and maintenance, fault repair |
+| System Management | User management, role permissions, parameter configuration |
+
+### 2.3 Shortcut Operations
+
+| Shortcut Key | Function |
+|--------------|----------|
+| `Ctrl + S` | Save |
+| `Ctrl + N` | New |
+| `Ctrl + F` | Search/Filter |
+| `F5` | Refresh |
+| `Esc` | Cancel |
+
+## 3. Basic Operation Flow
+
+### 3.1 Complete Work Order Process
+
+Taking a typical production work order as an example, here is the complete operation flow:
+
+**Process Overview:**
+
+```
+Create Work Order → Review Work Order → Release Work Order → Material Issue → Start Reporting → Process Flow → Complete and Store
+```
+
+#### 3.1.1 Create Work Order
+
+**Operation Steps:**
+
+1. Go to [Production Management] → [Work Order Management]
+2. Click [New] button
+3. Fill in work order information:
+ - Select product
+ - Fill in production quantity
+ - Set planned start/end dates
+ - Select production line/workshop
+4. Click [Save]
+
+**[Tip]** Fields marked with * are required.
+
+#### 3.1.2 Review Work Order
+
+**Operation Steps:**
+
+1. Find the pending review work order in the work order list
+2. Click the work order number to view details
+3. Review work order information
+4. Click [Approve] or [Reject]
+
+**[Note]** If rejected, modifications are required before resubmission.
+
+#### 3.1.3 Release Work Order
+
+**Operation Steps:**
+
+1. Find the approved work order in the work order list
+2. Click [Release] button
+3. System automatically checks material availability
+4. Confirm release after availability check passes
+5. Work order status changes to "Released"
+
+**[Note]** Ensure materials, equipment, and personnel are ready before release.
+
+#### 3.1.4 Material Issue
+
+**Operation Steps:**
+
+1. Go to [Warehouse Logistics] → [Material Issue Management]
+2. Click [New Material Issue]
+3. Select corresponding work order
+4. System automatically brings up bill of materials
+5. Confirm issue quantity
+6. Submit for review
+7. Go to warehouse to issue materials after approval
+8. Scan material barcode for material release
+
+#### 3.1.5 Production Reporting
+
+**Process Reporting Flow:**
+
+```
+Start Reporting → Process Operation → Complete Reporting
+```
+
+**Start Reporting:**
+
+1. Go to [Production Management] → [Production Reporting]
+2. Select corresponding work order
+3. Execute start reporting
+4. Record start time
+
+**Complete Reporting:**
+
+1. After completing process operation
+2. Execute complete reporting
+3. Fill in completed quantity, defective quantity
+4. Submit reporting data
+
+#### 3.1.6 Complete and Store
+
+**Operation Steps:**
+
+1. After all processes of the work order are completed
+2. Go to work order details
+3. Click [Complete Confirmation]
+4. Confirm storage information
+5. Generate storage order
+6. Materials stored in warehouse
+
+### 3.2 Quality Management Process
+
+#### 3.2.1 Incoming Quality Control (IQC)
+
+**Operation Steps:**
+
+1. Supplier delivery arrives
+2. Warehouse clerk creates receiving order
+3. System automatically pushes inspection task
+4. Quality inspector accepts inspection task
+5. Execute incoming inspection
+6. Determine pass/fail
+7. MRB process for non-conforming items
+
+#### 3.2.2 In-process Quality Control (IPQC)
+
+**Inspection Timing:**
+
+| Inspection Type | Execution Timing |
+|-----------------|------------------|
+| First Article Inspection | At the start of each product batch |
+| Patrol Inspection | Regularly during production |
+| Sampling Inspection | Regularly according to sampling plan |
+| Last Article Inspection | At the end of each product batch |
+
+### 3.3 Warehouse Management Process
+
+#### 3.3.1 Receiving Process
+
+```
+Arrival → Create Receiving Order → IQC Inspection → Allocate Location → Confirm Shelving
+```
+
+#### 3.3.2 Issuing Process
+
+```
+Material Request → Review → Prepare Materials → Scan to Issue → Release to Production
+```
+
+## 4. Common Operation Examples
+
+### 4.1 How to Query Work Orders
+
+**Method 1: Filter through List**
+
+1. Go to [Production Management] → [Work Order Management]
+2. Enter query conditions in filter:
+ - Work order number
+ - Product name
+ - Work order status
+ - Date range
+3. Click [Query] button
+4. View query results
+
+**Method 2: Through Search Box**
+
+1. In the search box at the top of the page
+2. Enter work order number or product name
+3. Press Enter to search
+4. System automatically navigates to work order details
+
+### 4.2 How to Perform Production Reporting
+
+**Operation Steps:**
+
+1. Go to [Production Management] → [Production Reporting]
+2. List of work orders pending reporting for current user
+3. Select work order to report
+4. Select process
+5. Fill in reporting information:
+ - Report type (Start/Complete)
+ - Report quantity
+ - Defective quantity (if any)
+ - Operation time
+6. Submit reporting data
+
+**[Tip]** After completing reporting, the system automatically triggers the next process start operation.
+
+### 4.3 How to View Production Progress
+
+**Operation Steps:**
+
+1. Go to [Production Management] → [Production Monitoring]
+2. Select production line or work order
+3. View real-time production status:
+ - Process progress
+ - Production statistics
+ - Defective rate
+ - Achievement rate
+4. Click details for more information
+
+### 4.4 How to Perform Batch Traceability
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Quality Traceability]
+2. Enter traceability information:
+ - Batch number
+ - Product code
+ - Date range
+3. Execute traceability query
+4. View traceability results:
+ - Material source
+ - Production process
+ - Quality data
+ - Shipment destination
+
+## 5. Common Questions Quick Reference
+
+### 5.1 Login Issues
+
+**Q1: "Username or password incorrect"**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Input error | Check username and password |
+| Case sensitivity | Ensure Caps Lock is not enabled |
+| Account locked | Wait 30 minutes or contact administrator |
+
+**Q2: "No access permission"**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Role not assigned | Contact administrator to assign permissions |
+| Insufficient permissions | Apply for higher permissions |
+
+### 5.2 Operation Issues
+
+**Q3: Page display abnormal**
+
+| Solution | Operation |
+|----------|-----------|
+| Clear cache | Ctrl + Shift + Delete |
+| Change browser | Use recommended browser |
+| Check resolution | Ensure resolution ≥ 1280×720 |
+
+**Q4: Data save failed**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Required fields not filled | Check required fields |
+| Data format error | Correct data format |
+| Network issue | Check network connection |
+| Session expired | Re-login |
+
+### 5.3 Business Issues
+
+**Q5: Work order cannot be released**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Materials not available | Check material inventory |
+| Production line unavailable | Check production line status |
+| Process route not maintained | Maintain process route |
+
+**Q6: Reporting data cannot be submitted**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Process not started | Execute start reporting first |
+| Data format error | Check input data |
+| Quantity out of range | Confirm quantity is within allowed range |
+
+## 6. Next Steps
+
+Congratulations on completing the quick start guide! Next you can:
+
+| Learning Path | Recommended Content |
+|--------------|---------------------|
+| In-depth Learning | Read detailed functional module documentation |
+| Daily Operations | Practice according to actual business scenarios |
+| Problem Solving | Refer to exception handling and technical support sections |
+
+**Recommended Learning Sequence:**
+
+1. 📖 [System Overview](/guide/system-overview) - Understand overall system architecture
+2. 📋 [Basic Data Management](/basic/data-management) - Master basic data configuration
+3. 🏭 [Production Management](/business/production) - Familiarize with production operations
+4. 📊 [Quality Management](/business/quality) - Understand quality control processes
+5. ⚙️ [System Operations](/operation/system-operation) - Learn system management
+
+**[Tip]** If you encounter any issues, please refer to the [Exception Handling and Technical Support](/operation/technical-support) section.
+
+---
+
+**End of Quick Start**
\ No newline at end of file
diff --git a/en/guide/document-guide.md b/en/guide/document-guide.md
new file mode 100644
index 0000000..1cac008
--- /dev/null
+++ b/en/guide/document-guide.md
@@ -0,0 +1,78 @@
+# Document Guide
+
+## 1. Document Introduction
+
+This document is the complete user guide for HF-MES v5.0 Manufacturing Execution System, designed to help users quickly master the system's functions and successfully complete daily production management tasks.
+
+**Document Version:** v1.0
+**Release Date:** 2026-04-10
+**Applicable Version:** HF-MES v5.0
+
+## 2. Document Structure
+
+| Section | Name | Main Content | Author |
+|---------|------|--------------|--------|
+| Document Guide | Document Management | Document description, system overview | james |
+| Quick Start | New User Guide | System login, quick start guide | james |
+| Basic Configuration | Basic Configuration | Plant model, process model, product management, material model, team model | Sheng |
+| Production Management | Production Execution | Production batch management, production monitoring, freeze/thaw management, warning center | Sheng |
+| Quality Management | Quality Traceability | First article/patrol inspection management, XQC management, SPC related | Sheng |
+| Equipment Management | Equipment Management | Equipment inspection, equipment maintenance, equipment consumables management, equipment status management, equipment repair management | Tao |
+| Report Analysis | Data Analysis | Basic traceability, production reports | Tao |
+| SCADA Management | SCADA Management | EdgeManager, EPS | Wei, Ye |
+| DAS | DAS Analysis | Equipment homepage, OEE trend analysis, operation analysis, equipment analysis, quality analysis | Sheng, Tao |
+| Data Integration | System Integration | Data interface, system integration solutions | Wei |
+| System Operations | System Management | System management, system operations | TBD |
+| Technical Support | Technical Support | Exception handling, technical support | TBD |
+| Appendix | Reference Materials | Glossary, flowcharts, update log | TBD |
+
+
+# System Function List
+
+| Level 1 Module | Level 2 Module | Level 3 Module | Function Description | Remarks | Owner |
+| :--- | :--- | :--- | :--- | :--- | :--- |
+| **System Settings** | User Management | User Groups | Set user groups and assign permissions (CRUD user groups, implement permission assignment) | | |
+| | | Administrators | Manage administrator accounts and bind to corresponding user groups | | |
+| | System Assistant | Operation Logs | System operation logs | | |
+| | | Interface Logs | Interaction logs for equipment docking processes (query by IP, interface name, etc.) | | |
+| **Basic Configuration** | Site Model | Production Line Settings | Manage production lines (including CRUD operations) | | |
+| | | Site Area Settings | Manage factories (including CRUD operations) | | |
+| | Process Model | Process Categories | CRUD functions for process categories | | |
+| | | Process Units | Configure and manage process units (nodes), implement CRUD, preset result parameter collection and process parameters for process units | | |
+| | | Process Flows | Set battery production process flows, implement CRUD for process cards and process card settings | | |
+| | Product Management | Product List | Implement CRUD for products in product management page | | |
+| | | Abnormality/Defect Management | Code and description management for equipment defect information and product NG information, implement batch import and CRUD | | |
+| | Equipment Type | Equipment Categories | Manage equipment types and implement CRUD | | |
+| | | Equipment Information Management | Manage individual equipment information and implement CRUD | | |
+| | Material Model | Material Category List | Distinguish raw materials and semi-finished products (fixed codes) | | |
+| | | Material Information Management | Maintain basic attributes such as material code, name, category, unit, specification/model, BOM information | | |
+| | | BOM Bill of Materials | Product BOM management | | |
+| | | Unit of Measure | Configure and manage units of measure, with CRUD capabilities | | |
+| | SPC Collection Model | SPC Collection Configuration | Configure result parameter collection parameters | | |
+
+## 3. Code Blocks
+
+### 3.1
+
+Wrap code blocks with ```, for example:
+
+```bash
+# Example command
+cd /opt/mes
+./start.sh
+```
+
+## 4. Feedback Channels
+
+If you find errors or need additions to the document content, please provide feedback through the following channels:
+
+- Email: docs-feedback@hfmes.com
+- Service Hotline: 400-XXX-XXXX
+
+## 5. Copyright Notice
+
+This document is copyrighted by HF-MES. Unauthorized copying, distribution, or modification is prohibited.
+
+---
+
+**End of Document Guide**
\ No newline at end of file
diff --git a/en/guide/system-overview.md b/en/guide/system-overview.md
new file mode 100644
index 0000000..93de3c2
--- /dev/null
+++ b/en/guide/system-overview.md
@@ -0,0 +1,376 @@
+# Document Guide
+## System Overview
+
+## 1. System Introduction
+
+HF-MES v5.0 (Manufacturing Execution System) is a production execution management system for manufacturing enterprises, designed to achieve digital and intelligent management of production processes, improve production efficiency, ensure product quality, and reduce operational costs.
+
+### 1.1 System Positioning
+
+```
+┌─────────────────────────────────────────────────────────┐
+│ Enterprise IT Pyramid │
+├─────────────────────────────────────────────────────────┤
+│ │
+│ ┌─────────────┐ │
+│ │ ERP │ Enterprise Resource Planning │
+│ │ Enterprise Layer │ │
+│ └──────┬──────┘ │
+│ │ │
+│ ┌──────▼──────┐ │
+│ │ MES │ Manufacturing Execution System │
+│ │ Production Execution Layer │ │ ← Our System
+│ └──────┬──────┘ │
+│ │ │
+│ ┌──────▼──────┐ │
+│ │ SCADA │ Data Acquisition & Monitoring System │
+│ │ Equipment Control Layer │ │
+│ └─────────────┘ │
+│ │
+└─────────────────────────────────────────────────────────┘
+```
+
+### 1.2 Core Values
+
+| Core Value | Description | Customer Benefit |
+|------------|-------------|------------------|
+| Production Transparency | Real-time monitoring of production progress | Real-time production status visibility |
+| Process Traceability | Full-process data traceability | Quick quality issue localization |
+| Quality Control | Full-process quality control | Guaranteed product quality |
+| Efficiency Improvement | Optimized production processes | Increased production efficiency |
+| Cost Reduction | Reduced waste and losses | Lower production costs |
+
+## 2. System Architecture
+
+### 2.1 Technical Architecture
+
+**The system adopts a front-end and back-end separation architecture:**
+
+| Layer | Technology Stack | Description |
+|-------|------------------|-------------|
+| Front-end Presentation | Vue.js + Element UI | User interface interaction |
+| Back-end Service | Java Spring Boot | Business logic processing |
+| Data Storage | MySQL + Redis | Data storage and caching |
+| Message Middleware | RabbitMQ | Asynchronous message processing |
+| File Storage | MinIO/OSS | File and attachment storage |
+
+### 2.2 System Deployment Architecture
+
+```
+┌────────────────────────────────────────────────────────────┐
+│ Client Layer │
+│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
+│ │ Web Browser │ │ Mobile │ │ Large Screen │ │
+│ └──────────────┘ └──────────────┘ └──────────────┘ │
+└────────────────────────────────────────────────────────────┘
+ │
+ ▼
+┌────────────────────────────────────────────────────────────┐
+│ Application Service Layer │
+│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
+│ │ Web Service │ │ API Service │ │ Scheduler │ │
+│ │ (Nginx) │ │ (Gateway) │ │ (Scheduler) │ │
+│ └──────────────┘ └──────────────┘ └──────────────┘ │
+└────────────────────────────────────────────────────────────┘
+ │
+ ▼
+┌────────────────────────────────────────────────────────────┐
+│ Data Service Layer │
+│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
+│ │ Database │ │ Cache │ │ Message Queue │ │
+│ │ (MySQL) │ │ (Redis) │ │ (RabbitMQ) │ │
+│ └──────────────┘ └──────────────┘ └──────────────┘ │
+└────────────────────────────────────────────────────────────┘
+ │
+ ▼
+┌────────────────────────────────────────────────────────────┐
+│ Equipment Integration Layer │
+│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
+│ │ PLC/SCADA │ │ RFID │ │ Barcode Scanner │ │
+│ └──────────────┘ └──────────────┘ └──────────────┘ │
+└────────────────────────────────────────────────────────────┘
+```
+
+### 2.3 System Network Architecture
+
+```
+ ┌─────────────────┐
+ │ Internet Users │
+ └────────┬────────┘
+ │
+ ▼
+┌────────────────────────────────────────────────────────────┐
+│ Enterprise Intranet │
+│ │
+│ ┌────────────────────┐ ┌────────────────────┐ │
+│ │ MES App Server │◀────▶│ ERP Server │ │
+│ │ (Application Cluster) │ (SAP/Ufida/Kingdee)│ │
+│ └─────────┬──────────┘ └────────────────────┘ │
+│ │ │
+│ ├──────────┬──────────┬──────────┐ │
+│ │ │ │ │ │
+│ ▼ ▼ ▼ ▼ │
+│ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ │
+│ │ Shop 1 │ │ Shop 2 │ │ Shop 3 │ │ Warehouse │ │
+│ │ Client │ │ Client │ │ Client │ │ Client │ │
+│ └────────┘ └────────┘ └────────┘ └────────┘ │
+│ │ │ │ │ │
+│ └──────────┴──────────┴──────────┘ │
+│ │ │
+│ ▼ │
+│ ┌────────────┐ │
+│ │ DB Server │ │
+│ │ (Active-Standby Cluster) │ │
+│ └────────────┘ │
+└────────────────────────────────────────────────────────────┘
+```
+
+## 3. Functional Modules
+
+### 3.1 Functional Module Overview
+
+```
+┌─────────────────────────────────────────────────────────┐
+│ HF-MES v5.0 Functional Architecture │
+├─────────────────────────────────────────────────────────┤
+│ │
+│ ┌─────────────────────────────────────────────────┐ │
+│ │ System Management Layer │ │
+│ │ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ │ │
+│ │ │ User Mgmt│ │ Role Mgmt│ │ Permission│ │ Param Config││ │
+│ │ └────────┘ └────────┘ └────────┘ └────────┘ │ │
+│ └─────────────────────────────────────────────────┘ │
+│ │
+│ ┌─────────────────────────────────────────────────┐ │
+│ │ Production Management Layer │ │
+│ │ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ │ │
+│ │ │ Prod Plan│ │ Work Order│ │ Reporting│ │ Production Scheduling││ │
+│ │ └────────┘ └────────┘ └────────┘ └────────┘ │ │
+│ └─────────────────────────────────────────────────┘ │
+│ │
+│ ┌─────────────────────────────────────────────────┐ │
+│ │ Quality Management Layer │ │
+│ │ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ │ │
+│ │ │ IQC │ │ IPQC │ │ FQC │ │ Quality Trace│ │ │
+│ │ └────────┘ └────────┘ └────────┘ └────────┘ │ │
+│ └─────────────────────────────────────────────────┘ │
+│ │
+│ ┌─────────────────────────────────────────────────┐ │
+│ │ Warehouse Management Layer │ │
+│ │ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ │ │
+│ │ │ Receiving│ │ Issuing│ │ Inventory│ │ Location Mgmt││ │
+│ │ └────────┘ └────────┘ └────────┘ └────────┘ │ │
+│ └─────────────────────────────────────────────────┘ │
+│ │
+│ ┌─────────────────────────────────────────────────┐ │
+│ │ Equipment Management Layer │ │
+│ │ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ │ │
+│ │ │ Equipment│ │ Inspection│ │ Fault Repair│ │ OEE Analysis││ │
+│ │ └────────┘ └────────┘ └────────┘ └────────┘ │ │
+│ └─────────────────────────────────────────────────┘ │
+│ │
+│ ┌─────────────────────────────────────────────────┐ │
+│ │ Report Management Layer │ │
+│ │ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ │ │
+│ │ │ Prod Report│ │ Quality│ │ Equipment│ │ Inventory│ │ │
+│ │ └────────┘ └────────┘ └────────┘ └────────┘ │ │
+│ └─────────────────────────────────────────────────┘ │
+│ │
+└─────────────────────────────────────────────────────────┘
+```
+
+### 3.2 Module Details
+
+#### 3.2.1 Production Management Module
+
+**Core Functions:**
+
+| Function | Description |
+|----------|-------------|
+| Production Planning | Generate production plans based on sales orders |
+| Work Order Management | Create, review, release, and modify work orders |
+| Production Reporting | Production reporting, completion confirmation |
+| Production Monitoring | Real-time monitoring of production progress and status |
+| Process Management | Process routes, process definitions |
+| Material Flow | Material release, picking, semi-finished product flow |
+
+#### 3.2.2 Quality Management Module
+
+**Core Functions:**
+
+| Function | Description |
+|----------|-------------|
+| Inspection Standards | Inspection items, inspection standard definitions |
+| IQC Inspection | Incoming quality control |
+| IPQC Inspection | In-process quality control |
+| FQC/OQC | Final/Outgoing inspection |
+| Quality Abnormality | Defective product handling, MRB management |
+| Quality Traceability | Forward/reverse traceability |
+
+#### 3.2.3 Warehouse Management Module
+
+**Core Functions:**
+
+| Function | Description |
+|----------|-------------|
+| Receiving Management | Purchase receiving, production receiving, other receiving |
+| Issuing Management | Production picking, sales issuing, other issuing |
+| Inventory Management | Inventory query, inventory warning, inventory counting |
+| Location Management | Location definition, location allocation |
+| Batch Management | Batch definition, batch traceability |
+| Material Availability Check | Material availability check |
+
+#### 3.2.4 Equipment Management Module
+
+**Core Functions:**
+
+| Function | Description |
+|----------|-------------|
+| Equipment Ledger | Equipment information, classification management |
+| Inspection Management | Daily inspection, inspection standards |
+| Maintenance Management | Planned maintenance, maintenance standards |
+| Fault Management | Fault reporting, repair records |
+| OEE Analysis | Overall equipment efficiency analysis |
+| Spare Parts Management | Spare parts inventory, spare parts issue |
+
+### 3.3 Function Matrix
+
+| Functional Module | Basic Edition | Standard Edition | Advanced Edition | Enterprise Edition |
+|-------------------|---------------|------------------|------------------|-------------------|
+| Production Management | ✓ | ✓ | ✓ | ✓ |
+| Quality Management | ✓ | ✓ | ✓ | ✓ |
+| Warehouse Management | ✓ | ✓ | ✓ | ✓ |
+| Equipment Management | - | ✓ | ✓ | ✓ |
+| Report Analysis | Basic | Basic | Advanced | Advanced |
+| System Integration | - | Basic | Advanced | Advanced |
+| Secondary Development | - | - | ✓ | ✓ |
+| Private Deployment | - | - | ✓ | ✓ |
+
+## 4. Applicable Industries
+
+### 4.1 Typical Industry Applications
+
+| Industry | Typical Scenarios |
+|----------|------------------|
+| Electronics Manufacturing | SMT assembly, testing, packaging and shipping |
+| Automotive Parts | Stamping, welding, painting, assembly |
+| Machinery Processing | CNC machining, assembly, inspection |
+| Food and Beverage | Formula production, filling and packaging, quality traceability |
+| Pharmaceutical and Chemical | Formulation production, packaging, batch traceability |
+| New Energy | Battery production, photovoltaic modules |
+
+### 4.2 Industry Solutions
+
+For different industries, we provide customized solutions, including:
+
+- Industry-specific functional modules
+- Industry best practice processes
+- Industry-specific report templates
+- Industry integration interface solutions
+
+## 5. Performance Metrics
+
+### 5.1 System Performance
+
+| Metric | Standard Value | Description |
+|--------|---------------|-------------|
+| System Response Time | < 3 seconds | Page loading time |
+| API Response Time | < 1 second | API call response |
+| Concurrent Users | 500+ | Simultaneous online users |
+| Data Processing Capacity | 100,000+/day | Daily document processing volume |
+| System Availability | 99.9% | System uptime |
+| Data Backup | Daily incremental | Automatic backup mechanism |
+
+### 5.2 Operating Environment
+
+| Environment Requirement | Configuration |
+|-------------------------|---------------|
+| Browser | Chrome, Firefox, Edge, 360, etc. |
+| Minimum Resolution | 1280×720 |
+| Network Requirement | LAN ≥ 100M |
+| Server Configuration | CPU 8-core+, Memory 16G+, Hard Disk 500G+ |
+
+## 6. Security Features
+
+### 6.1 Security Assurance System
+
+| Security Dimension | Assurance Measures |
+|-------------------|-------------------|
+| Identity Authentication | Username/password, LDAP integration |
+| Permission Control | RBAC permission model |
+| Data Security | Transmission encryption, sensitive field encryption |
+| Operation Audit | Complete operation log recording |
+| Security Policy | Password policy, session management |
+| Data Backup | Automatic backup, off-site backup |
+
+### 6.2 Permission Model
+
+```
+┌─────────────────────────────────────────────────────────┐
+│ Permission Model │
+├─────────────────────────────────────────────────────────┤
+│ │
+│ ┌─────────┐ │
+│ │ User │ ←────────────┐ │
+│ └────┬────┘ │ │
+│ │ │ Belongs to │
+│ ▼ │ │
+│ ┌─────────┐ │ │
+│ │ Role │──────────────┼──────────┐ │
+│ └────┬────┘ │ │ │
+│ │ │ Has │ │
+│ ▼ │ ▼ │
+│ ┌─────────┐ │ ┌───────────┐ │
+│ │ Permission│◀─────────────┘ │ Function Menu│ │
+│ └─────────┘ └───────────┘ │
+│ │
+│ ┌─────────────────────────────────────────────────┐ │
+│ │ Data Permission │ │
+│ │ Factory Level ─ Workshop Level ─ Line Level ─ Personal││ │
+│ └─────────────────────────────────────────────────┘ │
+│ │
+└─────────────────────────────────────────────────────────┘
+```
+
+## 7. Integration with Other Systems
+
+### 7.1 System Integration Architecture
+
+```
+┌─────────────────────────────────────────────────────────┐
+│ System Integration Architecture │
+├─────────────────────────────────────────────────────────┤
+│ │
+│ ┌───────────┐ │
+│ │ ERP │ ←──→ Material master data, work orders, purchase orders │
+│ │ (SAP) │ │
+│ └─────┬─────┘ │
+│ │ │
+│ ▼ │
+│ ┌───────────┐ │
+│ │ MES │ ←──→ Production execution, quality data, equipment data │
+│ │ (Self) │ │
+│ └─────┬─────┘ │
+│ │ │
+│ ▼ │
+│ ┌───────────┐ │
+│ │ SCADA │ ←──→ Equipment data, real-time status │
+│ │ (Device Layer)│ │
+│ └───────────┘ │
+│ │
+└─────────────────────────────────────────────────────────┘
+```
+
+### 7.2 Integration Methods
+
+| Integration Method | Description | Applicable Scenarios |
+|-------------------|-------------|---------------------|
+| API Interface | RESTful API | Real-time data exchange |
+| Intermediate Database | Direct database connection | Batch data synchronization |
+| File Import | Excel/CSV import | Periodic data exchange |
+| Message Queue | Event-driven | Asynchronous message notification |
+| WebService | SOAP interface | Legacy system integration |
+
+---
+
+**End of System Overview**
\ No newline at end of file
diff --git a/en/integration/data-integration.md b/en/integration/data-integration.md
new file mode 100644
index 0000000..48f1da3
--- /dev/null
+++ b/en/integration/data-integration.md
@@ -0,0 +1,289 @@
+# Data and Integration
+
+## 1. Function Overview
+
+The Data and Integration module enables data connectivity between the MES system and ERP, SCADA, PLC, and other systems, breaking down enterprise information silos and enabling data sharing and business collaboration.
+
+**Core Functions:**
+
+| Function | Description |
+|----------|-------------|
+| Interface Management | Interface configuration and monitoring |
+| Data Synchronization | Master data synchronization |
+| Message Integration | Message queue integration |
+| File Transfer | File data exchange |
+
+## 2. System Integration Architecture
+
+### 2.1 Integration Architecture Diagram
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│ Enterprise Application Integration │
+├─────────────────────────────────────────────────────────────┤
+│ │
+│ ┌─────────┐ │
+│ │ ERP │ ─────────────────────────────────────────▶ │
+│ │ SAP/Ufida│ Material Master Data, Purchase Orders, Production Plans, Sales Orders │
+│ └────┬────┘ │
+│ │ │
+│ │ ◀───────────────────────────────────────── │
+│ │ Work Order Completion, Quality Data, Inventory Data │
+│ ▼ │
+│ ┌─────────┐ │
+│ │ MES │ │
+│ │ MES │ ──────────────────────────────────────────▶ │
+│ └────┬────┘ Work Order Execution, Production Data, Quality Data │
+│ │ │
+│ │ ◀───────────────────────────────────────── │
+│ │ Equipment Operation Parameters, Status Data │
+│ ▼ │
+│ ┌─────────┐ │
+│ │ SCADA │ ──────────────────────────────────────────▶ │
+│ │ PLC/RTU │ Equipment Data Collection, Real-time Monitoring │
+│ └─────────┘ │
+│ │
+│ ┌─────────────────────────────────────────────────────┐ │
+│ │ Integration Middleware │ │
+│ │ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ │ │
+│ │ │Message Queue│ │Data Bus│ │File Transfer│ │API Gateway│ │ │
+│ │ └────────┘ └────────┘ └────────┘ └────────┘ │ │
+│ └─────────────────────────────────────────────────────┘ │
+│ │
+└─────────────────────────────────────────────────────────────┘
+```
+
+### 2.2 Integration Method Comparison
+
+| Integration Method | Real-time | Complexity | Data Volume | Applicable Scenarios |
+|-------------------|-----------|------------|-------------|---------------------|
+| API Interface | High | Medium | Medium | Real-time interaction |
+| Intermediate Database | Low | Low | Large | Batch synchronization |
+| Message Queue | Medium | Medium | Medium | Asynchronous messaging |
+| File Exchange | Low | Low | Large | Batch data |
+
+## 3. Interface Management
+
+### 3.1 Interface Types
+
+| Interface Type | Description | Direction |
+|----------------|-------------|-----------|
+| Upstream Interface | Get data from other systems | ERP→MES |
+| Downstream Interface | Push data to other systems | MES→ERP |
+| Bidirectional Interface | Bidirectional data exchange | ↔ |
+
+### 3.2 Common Interfaces
+
+**Integration with ERP System:**
+
+| Interface Name | Direction | Data Content |
+|----------------|-----------|--------------|
+| Material Master Data | ERP→MES | Material information, BOM, processes |
+| Supplier Master Data | ERP→MES | Supplier information |
+| Customer Master Data | ERP→MES | Customer information |
+| Purchase Order | ERP→MES | Purchase arrival information |
+| Production Work Order | ERP→MES | Production work order |
+| Completion Report | MES→ERP | Work order completion information |
+| Quality Data | MES→ERP | Inspection data |
+| Inventory Data | MES→ERP | Inventory data |
+
+**Integration with SCADA System:**
+
+| Interface Name | Direction | Data Content |
+|----------------|-----------|--------------|
+| Equipment Status | SCADA→MES | Equipment operating status |
+| Production Data | SCADA→MES | Real-time production volume |
+| Process Parameters | SCADA→MES | Temperature, pressure, etc. |
+| Alarm Information | SCADA→MES | Equipment alarms |
+| Production Command | MES→SCADA | Production control commands |
+
+### 3.3 Interface Configuration
+
+**Interface Configuration Elements:**
+
+| Configuration Item | Description |
+|-------------------|-------------|
+| Interface Code | Unique interface identifier |
+| Interface Name | Interface name |
+| Interface Type | API/Middleware/Message |
+| Source System | Data source system |
+| Target System | Data target system |
+| Interface Address | API address or database connection |
+| Authentication Method | Authentication type and credentials |
+| Data Format | JSON/XML/DB |
+
+**Interface Configuration Example:**
+
+| Interface Item | Configuration Value |
+|----------------|---------------------|
+| Interface Code | INT-001 |
+| Interface Name | Material Master Data Sync |
+| Interface Type | API |
+| Source System | ERP |
+| Target System | MES |
+| Interface Address | http://erp-api/mdm/materials |
+| Authentication Method | Token Authentication |
+| Call Frequency | Daily full sync + Real-time incremental |
+
+## 4. Data Synchronization
+
+### 4.1 Synchronization Strategies
+
+| Synchronization Strategy | Description | Trigger Method |
+|-------------------------|-------------|----------------|
+| Real-time Sync | Data changes synchronized immediately | Event triggered |
+| Scheduled Sync | Synchronized according to schedule | Scheduled task |
+| Manual Sync | Manual trigger synchronization | Manual operation |
+| Full Sync | All data synchronized | Scheduled/Manual |
+| Incremental Sync | Only changed data synchronized | Event/Scheduled |
+
+### 4.2 Master Data Synchronization
+
+**Material Data Synchronization:**
+
+| Synchronized Field | Description | Required |
+|-------------------|-------------|----------|
+| Material Code | Unique material identifier | ✓ |
+| Material Name | Material name | ✓ |
+| Specification | Specification/model | - |
+| Unit of Measure | Unit of measure | ✓ |
+| Material Category | Material category | - |
+| Safety Stock | Safety stock quantity | - |
+| Lead Time | Purchase lead time | - |
+
+**BOM Data Synchronization:**
+
+| Synchronized Field | Description | Required |
+|-------------------|-------------|----------|
+| Product Code | Parent item material code | ✓ |
+| Material Code | Child item material code | ✓ |
+| Quantity | Material quantity | ✓ |
+| Scrap Rate | Scrap percentage | - |
+| Process Sequence | Process using the material | - |
+
+### 4.3 Business Data Synchronization
+
+**Work Order Data Synchronization:**
+
+| Sync Direction | Data Content |
+|----------------|--------------|
+| ERP→MES | Work order number, product, quantity, planned date |
+| MES→ERP | Completed quantity, completion time, defective quantity |
+
+**Inventory Data Synchronization:**
+
+| Sync Direction | Data Content |
+|----------------|--------------|
+| MES→ERP | Received quantity, issued quantity, inventory quantity |
+
+## 5. Message Integration
+
+### 5.1 Message Types
+
+| Message Type | Description | Usage |
+|--------------|-------------|-------|
+| Production Message | Production-related events | Work order start, completion, etc. |
+| Quality Message | Quality-related events | Inspection completion, defect occurrence, etc. |
+| Equipment Message | Equipment-related events | Equipment failure, alarms, etc. |
+| Inventory Message | Inventory-related events | Receiving, issuing, etc. |
+
+### 5.2 Message Format
+
+**Standard Message Format:**
+
+```json
+{
+ "messageId": "MSG-20260410-001",
+ "messageType": "PRODUCTION_START",
+ "sourceSystem": "MES",
+ "targetSystem": "ERP",
+ "timestamp": "2026-04-10 10:00:00",
+ "data": {
+ "workOrderId": "WO-001",
+ "productId": "P001",
+ "quantity": 1000,
+ "startTime": "2026-04-10 10:00:00"
+ }
+}
+```
+
+### 5.3 Message Processing
+
+| Processing Mode | Description | Features |
+|-----------------|-------------|----------|
+| Immediate Processing | Messages processed immediately | Low latency |
+| Asynchronous Processing | Messages buffered in queue | High throughput |
+| Batch Processing | Messages processed in batches | High efficiency |
+
+## 6. Interface Monitoring
+
+### 6.1 Monitoring Metrics
+
+| Metric | Description | Monitoring Content |
+|--------|-------------|--------------------|
+| Interface Call Count | Interface call statistics | Success/failure count |
+| Interface Response Time | Interface response speed | Average/max response time |
+| Interface Success Rate | Interface availability | Success/total calls |
+| Data Sync Timeliness | Data synchronization timeliness | Delay time |
+
+### 6.2 Interface Logs
+
+| Log Type | Description | Retention Period |
+|----------|-------------|------------------|
+| Call Log | Interface call records | 6 months |
+| Request Log | Request message records | 3 months |
+| Response Log | Response message records | 3 months |
+| Error Log | Error information records | 12 months |
+
+### 6.3 Exception Handling
+
+| Exception Type | Handling Method |
+|----------------|-----------------|
+| Network Exception | Auto retry (3 times) |
+| Timeout Exception | Increase timeout period |
+| Authentication Exception | Re-acquire Token |
+| Data Exception | Record exception, manual handling |
+
+## 7. Data Transformation
+
+### 7.1 Data Mapping
+
+**Field Mapping Configuration:**
+
+| Source Field | Target Field | Transformation Rule |
+|--------------|--------------|---------------------|
+| material_code | mat_code | Direct mapping |
+| unit_price | cost | Unit conversion (Yuan→Ten Thousand Yuan) |
+| create_time | createDate | Time format conversion |
+
+### 7.2 Data Validation
+
+| Validation Rule | Description |
+|-----------------|-------------|
+| Required Field Check | Required fields cannot be empty |
+| Format Check | Data format must be correct |
+| Length Check | Field length cannot exceed limit |
+| Business Rule Check | Must comply with business rules |
+
+## 8. Integration Security
+
+### 8.1 Authentication Methods
+
+| Authentication Method | Description | Security Level |
+|----------------------|-------------|----------------|
+| Username/Password | Basic authentication | Medium |
+| API Key | Interface key | Medium |
+| Token Authentication | OAuth2.0 | High |
+| Digital Certificate | SSL certificate | High |
+
+### 8.2 Transmission Security
+
+| Security Measure | Description |
+|------------------|-------------|
+| HTTPS | Data transmission encryption |
+| Data Signature | Data integrity verification |
+| Data Masking | Sensitive data protection |
+
+---
+
+**End of Data and Integration**
\ No newline at end of file
diff --git a/en/operation/system-operation.md b/en/operation/system-operation.md
new file mode 100644
index 0000000..4fe5501
--- /dev/null
+++ b/en/operation/system-operation.md
@@ -0,0 +1,366 @@
+# System Operations
+
+## 1. Function Overview
+
+The System Management and Operations module provides system configuration, management, and operations functions for system administrators to ensure stable system operation.
+
+**Core Functions:**
+
+| Function | Description |
+|----------|-------------|
+| System Parameter Configuration | General parameters, business parameters |
+| Approval Process Configuration | Approval process definition |
+| Message Notification Configuration | Notification channels, templates |
+| Log Management and Audit | Operation logs, security logs |
+| Data Backup and Recovery | Backup strategy, data recovery |
+| Permission Security Policy | Password policy, login security |
+
+## 2. System Parameter Configuration
+
+### 2.1 General Parameters
+
+**System Information Configuration:**
+
+| Parameter Item | Description | Default Value |
+|----------------|-------------|---------------|
+| System Name | Displayed in system title | HF-MES |
+| System Logo | Login page logo | - |
+| Company Name | System owner company | - |
+| Work Start Time | Default work start time | 08:00 |
+| Work End Time | Default work end time | 18:00 |
+| Date Format | Date display format | YYYY-MM-DD |
+| Time Format | Time display format | HH:mm:ss |
+
+### 2.2 Business Parameters
+
+**Production Parameter Configuration:**
+
+| Parameter Item | Description | Default Value |
+|----------------|-------------|---------------|
+| Process Flow Rule | Sequential/Parallel | Sequential |
+| Reporting Advance Time | Advance minutes allowed for reporting | 10 minutes |
+| Work Order Overdue Warning | Days in advance for warning | 3 days |
+| Reporting Delay Time | Delay minutes allowed for reporting | 30 minutes |
+
+**Quality Parameter Configuration:**
+
+| Parameter Item | Description | Default Value |
+|----------------|-------------|---------------|
+| Default Inspection Standard | Default inspection standard | - |
+| Batch Number Code Rule | Batch number format | LOT-YYYYMMDD-XXX |
+| Acceptable Quality Level (AQL) | Default AQL value | 1.0 |
+
+**Equipment Parameter Configuration:**
+
+| Parameter Item | Description | Default Value |
+|----------------|-------------|---------------|
+| Inspection Reminder Time | Advance minutes for reminder | 30 minutes |
+| Maintenance Reminder Time | Advance days for reminder | 7 days |
+| Equipment OEE Calculation Cycle | OEE statistics cycle | Daily/Monthly |
+
+**[Caution]** Modifying system parameters may affect business operations. Please proceed with caution.
+
+## 3. Approval Process Configuration
+
+### 3.1 Approval Process Definition
+
+**Process Elements:**
+
+| Element | Description |
+|---------|-------------|
+| Process Code | Unique process identifier |
+| Process Name | Display name of process |
+| Process Type | Business type for approval |
+| Process Nodes | Approval stages |
+| Approvers | Approvers for each stage |
+| Flow Rules | Condition judgments |
+
+### 3.2 Process Types
+
+| Process Type | Description | Example |
+|--------------|-------------|---------|
+| Work Order Change | Approval for work order information changes | Quantity adjustment, extension |
+| Material Release | Approval for special material release | Concession acceptance |
+| Equipment Scrap | Approval for equipment scrapping | Equipment scrapping |
+| Defective Handling | Approval for defective product disposal | MRB processing |
+| Material Replenishment | Approval for production material replenishment | Material addition |
+
+### 3.3 Approval Node Configuration
+
+**Node Configuration Items:**
+
+| Configuration Item | Description |
+|-------------------|-------------|
+| Node Name | Approval stage name |
+| Approval Role | Approver role |
+| Approver | Specific approver |
+| Approval Method | Joint/Single approval |
+| Time Limit | Approval time limit |
+| Timeout Handling | Handling method after timeout |
+
+**Approval Methods:**
+
+| Method | Description |
+|--------|-------------|
+| Joint Approval | All approvers must approve |
+| Single Approval | Any single approver can approve |
+
+## 4. Message Notification Configuration
+
+### 4.1 Notification Channels
+
+| Channel Type | Description | Configuration Requirements |
+|--------------|-------------|----------------------------|
+| System Message | In-system message notification | Built-in |
+| Email Notification | Send to email | SMTP configuration |
+| SMS Notification | Send to mobile phone | SMS gateway configuration |
+| DingTalk Notification | DingTalk enterprise message | DingTalk app configuration |
+| WeChat Work | WeChat Work message | WeChat Work configuration |
+
+### 4.2 Notification Type Configuration
+
+| Business Event | Notification Type | Recipient |
+|---------------|-------------------|-----------|
+| Work Order Release | System Message/Email | Workshop Supervisor |
+| Work Order Completion | System Message | Planner |
+| Quality Abnormality | System Message/SMS | Quality Engineer |
+| Equipment Failure | System Message/SMS | Equipment Engineer |
+| Low Inventory | System Message/Email | Warehouse Clerk |
+| Pending Approval | System Message/Email | Approver |
+
+### 4.3 Notification Templates
+
+**Template Configuration Items:**
+
+| Configuration Item | Description |
+|-------------------|-------------|
+| Template Code | Unique template identifier |
+| Template Name | Template name |
+| Notification Channel | Delivery channel |
+| Title Template | Message title |
+| Content Template | Message content |
+
+**Template Variables:**
+
+| Variable | Description |
+|----------|-------------|
+| ${WorkOrderNo} | Work order number |
+| ${ProductName} | Product name |
+| ${Quantity} | Quantity |
+| ${Time} | Time |
+| ${Approver} | Approver name |
+
+## 5. Log Management and Audit
+
+### 5.1 Log Types
+
+| Log Type | Description | Retention Period |
+|----------|-------------|------------------|
+| Operation Log | User operation records | 6 months |
+| System Log | System running logs | 3 months |
+| Interface Log | Interface call logs | 6 months |
+| Exception Log | Exception error logs | 12 months |
+| Security Log | Login security logs | 12 months |
+
+### 5.2 Operation Log Content
+
+| Record Item | Description |
+|-------------|-------------|
+| Operation Time | Time when operation occurred |
+| User Account | User performing the operation |
+| User Name | User's display name |
+| Operation Type | Operation category |
+| Operation Content | Specific operation description |
+| Operation Object | Data object being operated |
+| IP Address | Operator's IP address |
+| Result | Success/Failure |
+
+### 5.3 Log Query
+
+**Query Conditions:**
+
+| Query Dimension | Optional Conditions |
+|-----------------|---------------------|
+| Time Range | Start time - End time |
+| User | Operator |
+| Operation Type | Add/Modify/Delete, etc. |
+| Operation Module | Functional module |
+| Operation Result | Success/Failure |
+
+### 5.4 Audit Reports
+
+| Report Type | Description |
+|-------------|-------------|
+| User Operation Statistics | Operation frequency per user |
+| Module Operation Statistics | Operation statistics per module |
+| Exception Operation Statistics | Failed operation statistics |
+| Login Audit | Login situation audit |
+
+## 6. Data Backup and Recovery
+
+### 6.1 Backup Strategy
+
+| Backup Type | Execution Frequency | Retention Count | Description |
+|-------------|---------------------|-----------------|-------------|
+| Full Backup | Weekly | 4 copies | Complete backup once a week |
+| Incremental Backup | Daily | 7 copies | Backup incremental data daily |
+| Real-time Backup | Real-time | - | Database log backup |
+
+### 6.2 Backup Configuration
+
+**Backup Task Configuration:**
+
+| Configuration Item | Description |
+|-------------------|-------------|
+| Task Name | Backup task name |
+| Backup Type | Full/Incremental |
+| Execution Time | Backup execution time |
+| Storage Location | Backup file storage location |
+| Retention Policy | Number of backups to retain |
+| Compression Method | Whether to compress |
+
+### 6.3 Manual Backup
+
+**Operation Steps:**
+
+1. Go to [System Management] → [Data Backup]
+2. Click [Manual Backup]
+3. Select backup type
+4. Click [Start Backup]
+5. System executes backup
+6. Backup file displayed upon completion
+
+### 6.4 Data Recovery
+
+**Recovery Operation Steps:**
+
+1. Go to [System Management] → [Data Recovery]
+2. Select recovery time point
+3. Select backup file
+4. Confirm recovery information
+5. Confirm recovery (requires confirmation code)
+6. System executes recovery
+7. Restart service after recovery completes
+
+**[Important]** Data recovery will overwrite current data. Please ensure current data has been backed up!
+
+## 7. Permission Security Policy
+
+### 7.1 Password Policy
+
+| Policy Item | Configuration Value | Description |
+|-------------|---------------------|-------------|
+| Minimum Length | 8 characters | Minimum password length |
+| Complexity Requirement | Must contain letters and numbers | Complexity rule |
+| Validity Period | 90 days | Password valid days |
+| Expiration Warning | 7 days | Warning before expiration |
+| History Password | 5 | Cannot reuse previous passwords |
+| Attempt Limit | 5 times | Failed attempt limit |
+| Lockout Duration | 30 minutes | Account lockout duration |
+
+### 7.2 Login Security
+
+| Configuration Item | Description |
+|-------------------|-------------|
+| Allow Concurrent Login | Yes/No |
+| Session Timeout | 30 minutes |
+| IP Whitelist | Allowed login IPs |
+| IP Blacklist | Blocked login IPs |
+| Remote Login Alert | Yes/No |
+
+### 7.3 Data Permission
+
+**Data Permission Levels:**
+
+| Permission Level | Description |
+|------------------|-------------|
+| All Data | Can view all data |
+| Factory Level | Can only view factory data |
+| Workshop Level | Can only view workshop data |
+| Production Line Level | Can only view production line data |
+| Personal Data | Can only view own data |
+
+## 8. System Performance Monitoring
+
+### 8.1 Monitoring Metrics
+
+| Metric Category | Specific Metric | Normal Range |
+|-----------------|-----------------|--------------|
+| Server Performance | CPU Usage | < 80% |
+| Server Performance | Memory Usage | < 85% |
+| Server Performance | Disk Usage | < 90% |
+| Database Performance | Connection Count | < Connection Pool Limit |
+| Database Performance | Query Response Time | < 1 second |
+| Application Performance | API Response Time | < 3 seconds |
+| Application Performance | Concurrent Users | < Licensed Quantity |
+
+### 8.2 Monitoring Dashboard
+
+**Monitoring Dashboard Display:**
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│ System Monitoring Dashboard │
+├─────────────────────────────────────────────────────────────┤
+│ │
+│ Server Status │
+│ ┌───────────────┐ ┌───────────────┐ ┌───────────────┐ │
+│ │ CPU │ │ Memory │ │ Disk │ │
+│ │ 45.2% │ │ 68.5% │ │ 52.3% │ │
+│ └───────────────┘ └───────────────┘ └───────────────┘ │
+│ │
+│ Application Service Status │
+│ ┌───────────────┐ ┌───────────────┐ ┌───────────────┐ │
+│ │ Web Service │ │ API Service │ │ Scheduler │ │
+│ │ Normal │ │ Normal │ │ Normal │ │
+│ └───────────────┘ └───────────────┘ └───────────────┘ │
+│ │
+│ Database Status │
+│ ┌───────────────┐ ┌───────────────┐ ┌───────────────┐ │
+│ │ Connections │ │ Active Sessions│ │ Query Response│ │
+│ │ 45/200 │ │ 12 │ │ 0.5秒 │ │
+│ └───────────────┘ └───────────────┘ └───────────────┘ │
+│ │
+└─────────────────────────────────────────────────────────────┘
+```
+
+### 8.3 Alert Configuration
+
+| Alert Item | Alert Condition | Alert Method |
+|------------|-----------------|--------------|
+| High CPU | > 90% | SMS/Email |
+| High Memory | > 95% | SMS/Email |
+| Low Disk Space | < 10% | SMS/Email |
+| Service Down | Service stopped | SMS/Phone |
+| Database Connection Full | 100% | SMS/Phone |
+
+## 9. Version Upgrade
+
+### 9.1 Upgrade Process
+
+```
+Backup Data → Download Upgrade → Execute Upgrade → Verify Functions → Release
+```
+
+### 9.2 Pre-Upgrade Checklist
+
+| Check Item | Description |
+|------------|-------------|
+| Data Backup | Confirm data has been backed up |
+| Environment Check | Server environment meets requirements |
+| Compatibility Check | Confirm upgrade package compatibility |
+| Downtime Notification | Notify relevant personnel |
+| Rollback Plan | Prepare rollback plan |
+
+### 9.3 Post-Upgrade Verification
+
+| Verification Item | Description |
+|-------------------|-------------|
+| Service Startup | Confirm services running normally |
+| Function Verification | Verify core functions |
+| Data Verification | Confirm data integrity |
+| Performance Verification | Confirm system performance normal |
+
+---
+
+**End of System Operations**
\ No newline at end of file
diff --git a/en/operation/technical-support.md b/en/operation/technical-support.md
new file mode 100644
index 0000000..eb06aaf
--- /dev/null
+++ b/en/operation/technical-support.md
@@ -0,0 +1,459 @@
+# Exception Handling and Technical Support
+
+## 1. Function Overview
+
+This chapter provides solutions for common issues and channels for obtaining technical support to help users quickly resolve problems encountered during usage.
+
+**Main Content:**
+
+| Content | Description |
+|---------|-------------|
+| Common Issues FAQ | Answers to various common questions |
+| System Error Code Explanation | Error codes and solutions |
+| Troubleshooting Guide | Problem troubleshooting methods |
+| Technical Support Contact Information | Channels for obtaining support |
+
+## 2. Common Issues FAQ
+
+### 2.1 Login Related Issues
+
+**Q1: "Username or password incorrect"**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Input error | Check if username and password are correct |
+| Case sensitivity | Check if case sensitivity is enabled |
+| Keyboard issue | Ensure Caps Lock is not enabled |
+
+**Q2: "Account locked"**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Multiple failed login attempts | Wait 30 minutes for automatic unlock or contact administrator |
+| Account disabled | Contact system administrator to enable account |
+
+**Q3: "No access permission"**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Role not assigned | Contact administrator to assign permissions |
+| Insufficient role permissions | Apply for higher permissions |
+| IP restriction | Check if within allowed IP range |
+
+**Q4: Forgot password?**
+
+| Solution | Operation |
+|----------|-----------|
+| Self-service recovery | Click "Forgot Password" on login page, reset via email/mobile |
+| Administrator reset | Contact system administrator to reset password |
+
+### 2.2 Production Management Related Issues
+
+**Q5: Cannot create work order?**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Missing product BOM | First maintain product BOM |
+| Missing process route | First maintain process route |
+| Materials not available | Confirm sufficient material inventory |
+| Insufficient permissions | Contact administrator to grant permissions |
+
+**Q6: Work order cannot be released?**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Materials not available | Check material inventory |
+| Production line unavailable | Check production line status |
+| Process route not maintained | Maintain process route |
+| Planned date conflict | Adjust planned date |
+
+**Q7: Reporting data cannot be saved?**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Process not started | First execute start reporting |
+| Data format error | Check input data format |
+| Quantity out of range | Confirm quantity within allowed range |
+| Session expired | Re-login |
+
+### 2.3 Quality Management Related Issues
+
+**Q8: Cannot add inspection items?**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Inspection standard not maintained | First create inspection standard |
+| Insufficient permissions | Contact administrator for authorization |
+| Data format error | Check input format |
+
+**Q9: How to handle defective products?**
+
+| Handling Method | Description |
+|-----------------|-------------|
+| Rework | Return defective product to process for rework |
+| Downgrade | Use at lower grade |
+| Concession | Special release after approval |
+| Scrap | Process scrap procedures |
+
+**Q10: Batch traceability query returns no results?**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Batch number input error | Verify batch number |
+| Batch not included in traceability | Confirm if material is batch managed |
+| Data not synchronized | Contact administrator to check data |
+
+### 2.4 Equipment Management Related Issues
+
+**Q11: Inspection task not generated?**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Inspection standard not configured for equipment | Configure inspection standard for equipment |
+| Date not in inspection cycle | Confirm inspection cycle configuration |
+| Inspection standard not enabled | Enable inspection standard |
+
+**Q12: How to report equipment failure?**
+
+| Operation Step | Description |
+|----------------|-------------|
+| 1. Discover failure | Discover equipment abnormality |
+| 2. Emergency assessment | Assess if emergency shutdown needed |
+| 3. Submit repair request | Submit repair order in equipment management |
+| 4. Repair processing | Wait for maintenance personnel |
+| 5. Acceptance confirmation | Confirm after repair completion |
+
+### 2.5 Warehouse Logistics Related Issues
+
+**Q13: Cannot confirm receiving order?**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| IQC not completed | Complete incoming inspection |
+| Batch number duplicate | Modify batch number |
+| Location unavailable | Select other location |
+
+**Q14: Inventory data inaccurate?**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Documents not reviewed | Review related documents |
+| Inventory differences | Perform inventory count |
+| Data synchronization issue | Contact administrator to check |
+
+**Q15: How to perform inventory count?**
+
+| Operation Step | Description |
+|----------------|-------------|
+| 1. Create count sheet | Select warehouse and materials |
+| 2. Execute count | On-site quantity verification |
+| 3. Enter actual count | Input actual quantity |
+| 4. Review differences | Review count differences |
+| 5. Adjust accounts | Adjust inventory accounts |
+
+### 2.6 System Operation Related Issues
+
+**Q16: Page display incomplete?**
+
+| Solution | Operation |
+|----------|-----------|
+| Clear cache | Clear browser cache |
+| Change browser | Use recommended browser |
+| Adjust zoom | Adjust browser zoom level |
+| Check resolution | Ensure screen resolution meets requirements |
+
+**Q17: Data export failed?**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Data volume too large | Export in batches |
+| Network issue | Check network connection |
+| Insufficient permissions | Contact administrator for authorization |
+| Format not supported | Change export format |
+
+**Q18: Approval process cannot flow?**
+
+| Possible Cause | Solution |
+|---------------|----------|
+| Approver not configured | Configure approver |
+| Conditions not met | Check flow conditions |
+| Approver not online | Remind approver |
+
+## 3. System Error Code Explanation
+
+### 3.1 Error Code Classification
+
+| Error Code Range | Error Type | Description |
+|------------------|------------|-------------|
+| 1000-1999 | Basic Error | System basic errors |
+| 2000-2999 | Permission Error | Permission-related errors |
+| 3000-3999 | Business Error | Business logic errors |
+| 4000-4999 | Data Error | Data validation errors |
+| 5000-5999 | Interface Error | External interface errors |
+| 9000-9999 | System Error | System internal errors |
+
+### 3.2 Permission Errors
+
+| Error Code | Error Message | Solution |
+|------------|--------------|----------|
+| 2001 | No access permission | Contact administrator to grant permissions |
+| 2002 | Insufficient permissions | Apply for higher permissions |
+| 2003 | Role not assigned | Contact administrator to assign role |
+| 2004 | Session expired | Re-login to system |
+| 2005 | IP restricted | Access within allowed IP range |
+
+### 3.3 Business Errors
+
+| Error Code | Error Message | Solution |
+|------------|--------------|----------|
+| 3001 | Data already exists | Check for duplicate creation |
+| 3002 | Data does not exist | Check if data is correct |
+| 3003 | Status does not allow operation | Confirm current status allows operation |
+| 3004 | Quantity out of range | Adjust quantity within allowed range |
+| 3005 | Business rule validation failed | Check compliance with business rules |
+| 3006 | Related data does not exist | Check if related data is complete |
+| 3007 | Data referenced | Remove data reference before operation |
+
+### 3.4 Data Errors
+
+| Error Code | Error Message | Solution |
+|------------|--------------|----------|
+| 4001 | Required field empty | Fill in required fields |
+| 4002 | Data format error | Check data format |
+| 4003 | Field length exceeded | Shorten input content |
+| 4004 | Data type mismatch | Input correct data type |
+| 4005 | Date format error | Use correct date format |
+| 4006 | Code duplicate | Use unique code |
+
+### 3.5 Interface Errors
+
+| Error Code | Error Message | Solution |
+|------------|--------------|----------|
+| 5001 | Interface connection timeout | Check network connection |
+| 5002 | Interface service unavailable | Contact interface service provider |
+| 5003 | Interface authentication failed | Check interface authentication information |
+| 5004 | Interface returned error | Check interface return information |
+| 5005 | Data synchronization failed | Check data synchronization configuration |
+
+### 3.6 System Errors
+
+| Error Code | Error Message | Solution |
+|------------|--------------|----------|
+| 9001 | System busy | Retry later |
+| 9002 | Operation failed | Retry or contact administrator |
+| 9003 | Server error | Contact technical support |
+| 9004 | Database error | Contact technical support |
+| 9005 | Insufficient memory | Restart service or expand capacity |
+
+## 4. Troubleshooting Guide
+
+### 4.1 Login Failure Troubleshooting
+
+**Troubleshooting Flow:**
+
+```
+Start
+ │
+ ▼
+Login Failed?
+ │
+ ├─── Yes ───→ Check error message
+ │ │
+ │ ▼
+ │ ┌─────────┐
+ │ │ Error Code? │
+ │ └────┬────┘
+ │ │
+ │ ┌─────────┼─────────┐
+ │ │ │ │
+ │ ▼ ▼ ▼
+ │ Permission Business System
+ │ Errors Errors Errors
+ │ │ │ │
+ │ │ │ ▼
+ │ │ │ Retry/Contact technical support
+ │ │
+ │Check user status/permissions
+ │
+ └─── No ───→ Troubleshooting complete
+```
+
+### 4.2 Performance Issues Troubleshooting
+
+**Troubleshooting Items:**
+
+| Check Item | Check Method | Normal Range |
+|------------|--------------|--------------|
+| CPU Usage | Task Manager | < 80% |
+| Memory Usage | Task Manager | < 85% |
+| Disk IO | Performance Monitor | < 70% |
+| Network Latency | ping command | < 100ms |
+| Database Connections | Check connection pool | < Maximum |
+| Slow Queries | Check query logs | < 1 second |
+
+**Common Performance Issues:**
+
+| Issue | Possible Cause | Solution |
+|-------|---------------|----------|
+| Slow page loading | Network issue/High server load | Check network/Scale up |
+| Slow operation response | Slow database query | Optimize indexes/Add resources |
+| Slow report generation | Large data volume | Batch query/Optimize SQL |
+| Slow batch operations | Processed one by one | Change to batch processing |
+
+### 4.3 Data Issues Troubleshooting
+
+**Data Consistency Check:**
+
+| Check Item | Check Method | Handling |
+|------------|--------------|----------|
+| Inventory discrepancy | Count verification | Adjust after difference review |
+| Batch traceability broken | Query traceability chain | Check data entry |
+| Work order status abnormal | View work order logs | Correct status |
+| Missing inspection data | View inspection records | Supplement data |
+
+### 4.4 Interface Issues Troubleshooting
+
+**Troubleshooting Steps:**
+
+1. Check interface configuration
+2. Verify authentication information
+3. Test network connectivity
+4. Check interface logs
+5. Verify data format
+6. Contact interface provider
+
+## 5. Log Extraction Guide
+
+### 5.1 Log Types
+
+| Log Type | Storage Location | Usage |
+|----------|-----------------|-------|
+| Operation Log | /logs/operation/ | Track user operations |
+| Error Log | /logs/error/ | Troubleshoot system errors |
+| Interface Log | /logs/interface/ | Troubleshoot interface issues |
+| Database Log | /logs/database/ | Troubleshoot data issues |
+| Application Log | /logs/application/ | Troubleshoot application issues |
+
+### 5.2 Log Extraction Methods
+
+**Method 1: Export via System**
+
+1. Go to [System Management] → [Log Management]
+2. Select log type
+3. Set query conditions
+4. Click [Export]
+5. Download log file
+
+**Method 2: Access via Server**
+
+```bash
+# Access log directory
+cd /opt/mes/logs
+
+# View recent error logs
+tail -n 100 error.log
+
+# Search for specific keyword
+grep "error" error.log
+
+# Export logs for specific time period
+grep "2026-04-10" error.log > error_20260410.log
+```
+
+### 5.3 Log Extraction Notes
+
+- [Note] Log extraction may contain sensitive information, please keep confidential
+- [Tip] When providing logs, please indicate the time range of the issue
+- [Important] Extract logs during issue reproduction
+
+## 6. Issue Reporting Guide
+
+### 6.1 Issue Classification
+
+| Issue Level | Definition | Response Time | Resolution Time |
+|-------------|------------|---------------|-----------------|
+| Urgent | System unavailable, business interrupted | 1 hour | 4 hours |
+| High | Core function abnormal | 4 hours | 24 hours |
+| Medium | General function abnormal | 8 hours | 72 hours |
+| Low | Interface/experience issue | 24 hours | 1 week |
+
+### 6.2 Issue Description Template
+
+Please describe the issue using the following template:
+
+```
+[Issue Description]
+1. Issue: Describe the problem encountered
+2. Expected Behavior: Expected correct behavior
+3. Actual Behavior: Actual error that occurred
+
+[Environment]
+- Module: xxx
+- Page: xxx
+- Browser: xxx
+- OS: xxx
+
+[Reproduction Steps]
+1.
+2.
+3.
+
+[Error Information]
+(Screenshot or text of error message)
+
+[Attachments]
+- Screenshots
+- Logs
+- Related data
+```
+
+## 7. Technical Support Contact Information
+
+### 7.1 Regular Support
+
+| Contact Method | Information |
+|----------------|-------------|
+| Service Hotline | 400-XXX-XXXX |
+| Service Email | support@hfmes.com |
+| Service Hours | Monday to Friday 9:00-18:00 |
+| Emergency Phone | 138-XXXX-XXXX |
+
+### 7.2 Online Support
+
+| Channel | Description |
+|---------|-------------|
+| WeChat Work Group | Dedicated service group |
+| Online Ticket | Submit technical support ticket |
+| Remote Assistance | TeamViewer remote support |
+
+### 7.3 Service Commitment
+
+| Service Type | Commitment |
+|--------------|------------|
+| Response Time | 1 hour response for urgent issues |
+| Issue Resolution | Provide solution within committed time |
+| Service Attitude | Professional, patient, responsible |
+| Information Security | Strictly protect customer data |
+
+## 8. Version and Updates
+
+### 8.1 Version Information
+
+| Version | Release Date | Update Content |
+|---------|--------------|----------------|
+| v5.0 | 2026-04-10 | Initial release |
+| - | - | - |
+
+### 8.2 Update Subscription
+
+**Subscription Methods:**
+
+| Subscription Channel | Description |
+|---------------------|-------------|
+| System Message | View update announcements in system |
+| Email Subscription | Subscribe to version update emails |
+| WeChat Work | Join service group for notifications |
+
+---
+
+**End of Exception Handling and Technical Support**
\ No newline at end of file
diff --git a/en/planning_production/alert_center.md b/en/planning_production/alert_center.md
new file mode 100644
index 0000000..b1a597d
--- /dev/null
+++ b/en/planning_production/alert_center.md
@@ -0,0 +1,326 @@
+# Alert Center
+
+## 1. Function Overview
+
+The Alert Center belongs to the monitoring and alert module of the MES system's data middle ground. It is used to monitor the channel abnormal status of production equipment in real-time, helping production managers discover and handle equipment point issues promptly. The system organizes data by equipment category (workstation), and separately counts two types of alert data: **consecutive errors** (the same channel reports errors 3 times or more consecutively) and **cumulative errors** (the same channel reports errors 10 times or more cumulatively). It provides functions for viewing details and clearing exceptions.
+
+**Core Functions:**
+
+- Workstation Overview: Display the number of abnormal devices under each workstation by equipment category, including consecutive error device count and cumulative error device count
+- Device Exception Details: View detailed data of all abnormal devices under a workstation, distinguishing between consecutive errors and cumulative errors
+- Channel Exception Details: View specific error information for each abnormal channel, including error code, error description, and occurrence time
+- Exception Clearance: Support device-level and single-channel clearance, with two methods: reset (reset count) and mark as processed
+- Condition Filtering: Filter by time range and specific device, support exporting exception data
+
+**Function Screenshot**:
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Alert Center | Alert Center, device point exception monitoring and alert module | Displays production equipment channel abnormal status in real-time, helping quickly locate problematic devices |
+| Workstation | Workstation, i.e., Device Category | Grouped by device type, such as formation, capacity grading, OCV, DCIR, etc. |
+| Consecutive Error | Consecutive Error, the same channel reports errors 3 times or more consecutively | Indicates that the channel has been continuously abnormal recently and requires focused attention |
+| Cumulative Error | Cumulative Error, the same channel reports errors 10 times or more cumulatively | Indicates that although the channel may not be consecutive, the overall exception frequency is high |
+| Channel | Channel, data collection point on the device | A device usually has multiple channels, and each channel independently counts exceptions |
+| Pin NG | Pin NG, exception (defect) information reported by the device channel | Reported by the device through the MES interface, including error code and error description |
+| Exception Clearance | Clear Error, reset exception count | Supports overall clearance and single-channel clearance, after which the counter restarts counting |
+| Channel Exception Record | Channel Exception Record, channel exception monitoring configuration enabled in the process | After enabled for a process in the process details, the device will trigger channel exception detection |
+
+**Data Model Relationship Explanation:**
+
+```mermaid
+flowchart TB
+ subgraph 筛选维度
+ DC[设备类别
DeviceCategory]
+ DE[设备
Device]
+ end
+
+ subgraph 异常统计
+ CES[设备通道异常统计
DeviceChannerlExceptionStatistics]
+ end
+
+ subgraph 异常详情
+ PNR[点位NG记录
PinNgRecord]
+ NI[不良信息
NgInfo]
+ end
+
+ subgraph 触发来源
+ SPR[工序结果上报
SetTrayProcessResult]
+ PCQ[点位检查队列
hf_mes_queue_pincheck]
+ end
+
+ DC -->|1:N| DE
+ DE -->|1:1| CES
+ CES -->|关联查询| PNR
+ PNR -->|关联| NI
+ SPR -->|触发验证| PCQ
+ PCQ -->|异步更新| CES
+```
+
+**Relationship Explanation:**
+
+| Relationship Type | Description |
+|------------------|-------------|
+| Device Category → Device | **1 to N**: One device category contains multiple devices |
+| Device → Channel Exception Statistics | **1 to 1**: Each device corresponds to one channel exception statistics record |
+| Channel Exception Statistics → Pin NG Record | **1 to N**: Query exception details through device code and channel number |
+| Pin NG Record → Defect Information | **N to 1**: Each NG record is associated with a defect code to get the defect description |
+
+**Simplified Relationship Diagram:**
+
+```mermaid
+flowchart LR
+ A[设备类别] -->|1:N| B[设备]
+ B -->|1:1| C[通道异常统计]
+ C -->|关联| D[点位NG记录]
+ D -->|关联| E[不良信息]
+```
+
+## 3. Alert Center Interaction Flow
+
+### 3.1 Workstation Overview
+
+#### 3.1.1 Workstation Overview Description
+
+The workstation overview page displays all device categories (workstations) in card form. Each card shows the workstation name and two types of abnormal device counts:
+- **Consecutive Error Device Count**: Number of devices with at least one channel having ≥ 3 consecutive errors
+- **Cumulative Error Device Count**: Number of devices with at least one channel having ≥ 10 cumulative errors
+
+Users can filter by time range and specific device through filter conditions.
+
+**Function Screenshot**:
+
+
+#### 3.1.2 Query Conditions
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Time Range | Select start and end time, accurate to seconds |
+| Workstation | Select device category (workstation) from dropdown list, such as formation, capacity grading, OCV, etc. |
+| Device | After selecting a workstation, further select a specific device for filtering (optional) |
+
+**Operation Steps:**
+
+1. Go to [Data Middle Ground] → [Alert Center]
+2. Set time range (required)
+3. Select workstation (optional, defaults to showing all workstations)
+4. If viewing a specific device, select the device after selecting the workstation
+5. Click [Query] button, the system displays alert data that meets the conditions
+
+**Function Screenshot**:
+
+
+#### 3.1.3 Workstation Card Information
+
+Each workstation card contains the following information:
+
+| Display Field | Description |
+|---------------|-------------|
+| Workstation Name | Name of the device category, such as "Formation", "Capacity Grading" |
+| Consecutive Error Device Count | Total number of devices with consecutive error channels (≥3 times) under this workstation, displayed as a blue badge |
+| Cumulative Error Device Count | Total number of devices with cumulative error channels (≥10 times) under this workstation, displayed as an orange badge |
+| View Data | When consecutive error device count or cumulative error device count > 0, click to view details |
+
+**Function Screenshot**:
+
+
+### 3.2 Device Exception Details
+
+#### 3.2.1 Device Exception Details Description
+
+Click the [View Data] button on the workstation card to open a full-screen dialog, divided into two columns:
+- **Left: Consecutive Error List** — Displays devices with consecutive errors under this workstation
+- **Right: Cumulative Error List** — Displays devices with cumulative errors under this workstation
+
+**Function Screenshot**:
+
+
+#### 3.2.2 Consecutive Error List
+
+The consecutive error list displays all devices under this workstation that have channels with consecutive error counts ≥ 3.
+
+**List Fields:**
+
+| Field | Description |
+|-------|-------------|
+| Device Name | Display name of the device |
+| Device Code | Unique identification code of the device |
+| Exception Channel Count | Total number of channels with consecutive errors (≥3 times) in this device |
+| Last Reset Time | Time of the last consecutive error count clearance |
+| Update Time | Last update time of the device exception statistics data |
+| Operation | Includes [Details] and [Clear] buttons |
+
+**Expand Row**: Click the expand button at the beginning of the row to view the consecutive error count for each channel of the device. Each channel displays the specific value as a badge, supporting clicking on a single channel for individual reset.
+
+#### 3.2.3 Cumulative Error List
+
+The cumulative error list displays all devices under this workstation that have channels with cumulative error counts ≥ 10.
+
+**List Fields:**
+
+| Field | Description |
+|-------|-------------|
+| Device Name | Display name of the device |
+| Device Code | Unique identification code of the device |
+| Exception Channel Count | Total number of channels with cumulative errors (≥10 times) in this device |
+| Last Reset Time | Time of the last cumulative error count clearance |
+| Update Time | Last update time of the device exception statistics data |
+| Operation | Includes [Details] and [Clear] buttons |
+
+**Expand Row**: Click the expand button at the beginning of the row to view the cumulative error count for each channel of the device. Each channel displays the specific value as a badge, supporting clicking on a single channel for individual reset.
+
+### 3.3 Channel Exception Details
+
+#### 3.3.1 Channel Exception Details Description
+
+In the consecutive error list or cumulative error list, click the [Details] button of a device row to pop up the channel exception details dialog, showing specific error information for all abnormal channels of the device.
+
+**Function Screenshots**:
+
+
+
+#### 3.3.2 Channel Exception Details Fields
+
+**Details List Fields:**
+
+| Field | Description |
+|-------|-------------|
+| Device Name | Display name of the device |
+| Device Code | Unique identification code of the device |
+| Channel Number | Channel number where the exception occurred |
+| Error Code | Error code of the exception |
+| Error Description | Specific description information of the exception |
+| Exception Time | Specific time when the exception occurred |
+
+**[Note]** When viewing details, the system displays exception records of the corresponding type according to whether it's consecutive error or cumulative error. If the device has new exception records after the last reset, only exceptions generated after the reset will be displayed in the details.
+
+### 3.4 Exception Clearance
+
+#### 3.4.1 Exception Clearance Description
+
+The alert center supports two granularities of exception clearance, which users can choose flexibly according to actual situations.
+
+**Clearance Methods:**
+
+| Clearance Method | Description | Applicable Scenario |
+|------------------|-------------|---------------------|
+| Device-level Clearance | Clear all exception channel counts of the device | The device has fully recovered, and all channel issues have been resolved |
+| Single-channel Clearance | Only clear the exception count of the specified channel | Only individual channel issues have been resolved, and other channels still need attention |
+
+**Clearance Effects:**
+
+| Clearance Type | Effect |
+|----------------|--------|
+| Consecutive Error Clearance | Reset/clear all consecutive error counts of the device to zero, record the last reset time |
+| Cumulative Error Clearance | Reset/clear all cumulative error counts of the device to zero, record the last reset time |
+
+#### 3.4.2 Device-level Clearance
+
+**Operation Steps:**
+
+1. On the device exception details page, find the device row to clear
+2. Click [Clear] button
+3. The system pops up a confirmation dialog, confirm to execute the clearance operation
+4. After successful clearance, the page data refreshes automatically, and the workstation overview updates synchronously
+
+**[Note]** Device-level clearance will clear all channel exception counts of the device at once, please operate with caution.
+**[Important]** After clearance, the related Pin NG records will also be marked as processed for subsequent traceability.
+
+**Function Screenshot**:
+
+
+#### 3.4.3 Single-channel Clearance
+
+**Operation Steps:**
+
+1. On the device exception details page, click the expand button of the device row to display the exception counts of each channel
+2. Click the corresponding button for the channel to clear
+3. The system pops up a confirmation dialog, confirm to execute the single-channel clearance operation
+4. After successful clearance, the page data refreshes automatically
+
+**[Note]** Single-channel clearance only sets the exception count of that channel to zero, without affecting the exception counts of other channels.
+**[Note]** Single-channel clearance does not mark Pin NG records as processed, only resets the count statistics.
+
+**Function Screenshot**:
+
+
+## 4. Alert Trigger Mechanism
+
+### 4.1 Alert Trigger Flow Description
+
+The data in the alert center comes from the process result data reported by devices during production execution. When a device calls the MES interface to report process results, the system automatically performs channel exception detection according to the process configuration.
+
+**Trigger Flow:**
+
+```mermaid
+sequenceDiagram
+ participant 设备 as Device
+ participant MES接口 as MES Process Reporting Interface
+ participant 验证 as Channel Exception Verification
+ participant 队列 as Alert Queue
+ participant 统计 as Exception Statistics Table
+
+ 设备->>MES接口: 1. Report process result data (including pin_check, NG information)
+ MES接口->>MES接口: 2. Check if channel exception recording is enabled for the process
+ MES接口->>验证: 3. Channel exception recording is enabled for the process, trigger verification
+ 验证->>验证: 4. Verify the validity of the pin_check array
+ 验证->>队列: 5. Exception exists (pin_check=1), write to alert queue
+ 队列->>统计: 6. Asynchronous task consumes the queue, update exception statistics
+ 统计->>统计: 7. Accumulate consecutive/cumulative exception counts for the channel
+```
+
+**Flow Description:**
+
+| Step | Executor | Operation | Description |
+|------|----------|-----------|-------------|
+| 1 | Device | Report process results | The device calls the MES interface to submit process completion data, which includes pin_check (point check) and NG (defect code) information |
+| 2 | MES | Check process configuration | Determine whether the "channel exception recording" switch is enabled for the process in the process details |
+| 3 | MES | Trigger verification | Channel exception recording is enabled for the process, trigger point check verification logic |
+| 4 | MES | Verify data | Check the validity of the pin_check array and NG array (consistent length, values are 0 or 1, NG is required when pin_check=1) |
+| 5 | MES | Write to queue | When there are entries with value 1 in the pin_check array, write the exception data to the alert cache queue |
+| 6 | Background Task | Consume queue | Asynchronous task reads unprocessed data from the alert queue and aggregates exception counts by device code |
+| 7 | Background Task | Update statistics | Accumulate channel exception counts to the exception statistics table, distinguishing between consecutive errors and cumulative errors |
+
+### 4.2 Preconditions
+
+The alert function requires the following pre-configurations:
+
+| Precondition | Description | Configuration Location |
+|--------------|-------------|-----------------------|
+| Enable Channel Exception Recording | Enable the "Enable Channel Exception Recording" switch for the process in the process details | Production Configuration → Process Model → Process Flow → Set Process |
+| Configure Defect Codes | Maintain defect codes and their descriptions in the system | Production Configuration → Product Management → Defect Management |
+| Device Category Configuration | Ensure devices are bound to the correct device category (workstation) | Device Model → Device Information |
+
+**[Important]** Only when "channel exception recording" is enabled in the process configuration of the process details will channel exception detection be triggered when the device reports process results, and the alert center will display alert data related to this process.
+
+## 5. Common Issues
+
+### 5.1 No data in the Alert Center?
+
+**Possible Reasons:**
+1. The "channel exception recording" switch is not enabled for the process. Please check the process configuration in [Process Details]
+2. The device has not yet reported process result data containing pin_check information
+3. No exception data was generated within the selected query time range
+4. Device category (workstation) is not configured correctly
+
+### 5.2 Why does the data reappear after clearing?
+
+The clearance operation only resets the exception count and does not prevent the device from continuing to report exception data. If the device channel issue is not fundamentally resolved, the count will accumulate again and reach the alert threshold after the device continues to report exceptions. Recommendations:
+- Locate and resolve the root cause of the device channel issue before performing the clearance operation
+- Observe the device status after clearance to confirm that exceptions no longer recur
+
+### 5.3 What's the difference between consecutive errors and cumulative errors?
+
+- **Consecutive Errors**: The same channel reports errors 3 times or more consecutively, indicating that the channel has been continuously abnormal recently and is the current focus of attention
+- **Cumulative Errors**: The same channel reports errors 10 times or more cumulatively, indicating that although the channel may not be consecutive, the overall exception frequency is high, reflecting the long-term health status of the device
+
+### 5.4 What to do if data export fails?
+
+The export function relies on asynchronous task mechanism. Please check:
+1. Whether the time range and workstation have been selected
+2. Whether the system download task service is running normally
+3. You can view the task status and failure reasons in the [System Download Tasks] page
\ No newline at end of file
diff --git a/en/planning_production/batch_defect_report.md b/en/planning_production/batch_defect_report.md
new file mode 100644
index 0000000..371cefd
--- /dev/null
+++ b/en/planning_production/batch_defect_report.md
@@ -0,0 +1,64 @@
+# Production Batch Defect Report
+
+## 1. Function Overview
+
+The Production Batch Defect Report belongs to the quality analysis module of the MES system. It is used to statistically analyze the defective products in production batches and provide data support for production quality improvement.
+
+**Core Functions:**
+
+- Defect Statistics: Statistically analyze the number of defective products and defect rate by batch
+- Defect Type Analysis: Distinguish between battery defects and appearance defects
+
+
+**Function Screenshot**:
+
+

+
Figure 1: Production Batch Defect Report
+
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Defective Item | Defective Item, products with quality abnormalities produced during production | Require quality analysis and handling |
+| Defect Rate | Defect Rate, the ratio of defective product quantity to total production quantity | Used to measure production quality level |
+
+
+## 3. Production Batch Defect Report Interaction Flow
+
+### 3.1 Defect Report List
+
+#### 3.1.1 Defect Report List Description
+
+The defect report list displays defective product statistics for all production batches, supporting query and filtering by multiple conditions.
+
+**Function Screenshot**:
+
+

+
Figure 1: Production Batch Defect Report
+
+
+**Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Batch Number | Unique identifier of the production batch |
+| Product Model | Corresponding product model |
+| Total Quantity | Total production quantity of the batch |
+| Defective Quantity | Number of defective products in the batch |
+| Defect Rate | Percentage of defective quantity to total quantity |
+| Battery Defect Quantity | Number of battery-type defects |
+| Appearance Defect Quantity | Number of appearance-type defects |
+| Statistics Time | Report statistics time |
+
+
+#### 3.1.2 Defect Report Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Batch Number | Query by batch number exactly |
+| Production Time | Filter by statistics time range |
+| Defect Type | Filter by defect type (All, Battery, Appearance) |
\ No newline at end of file
diff --git a/en/planning_production/batch_management.md b/en/planning_production/batch_management.md
new file mode 100644
index 0000000..e29ff63
--- /dev/null
+++ b/en/planning_production/batch_management.md
@@ -0,0 +1,210 @@
+# Batch Management
+
+## 1. Function Overview
+
+Batch Management is a core module of the MES system, used to manage production batches and realize the creation, tracking, and monitoring of production tasks.
+
+**Core Functions:**
+
+- Batch Management: Maintain production batch creation, deletion, modification, and query
+- Batch Association: Associate process flow, product model, production area, and production line
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Batch | Production Batch, a production unit with independent identification | Used for tracking and managing production processes |
+| Process Flow | Process Flow, production process route | Defines the production process steps for products |
+| Product Model | Product Model, product specification and model | Corresponds to the type of product being produced |
+| Planned Completion Date | Planned completion time | The planned completion time of the batch |
+| Planned Completion Quantity | Planned completion quantity | The planned production quantity of the batch |
+
+
+## 3. Data Model Relationship Explanation
+
+### 3.1 Batch and Other Entity Relationships
+
+```mermaid
+flowchart TB
+ subgraph Batch
+ B[Batch]
+ end
+
+ subgraph Basic Data
+ F[Factory]
+ L[Production Line]
+ PF[Process Flow]
+ PM[Product Model]
+ end
+
+ B -->|关联| F
+ B -->|关联| L
+ B -->|关联| PF
+ B -->|关联| PM
+```
+
+**Relationship Explanation:**
+
+| Relationship Type | Description |
+|------------------|-------------|
+| Batch → Factory | **N:1**: Multiple batches belong to one factory |
+| Batch → Production Line | **N:1**: Multiple batches belong to one production line |
+| Batch → Process Flow | **N:1**: Multiple batches use the same process flow |
+| Batch → Product Model | **N:1**: Multiple batches produce the same product model |
+
+
+## 4. Batch Management Interaction Flow
+
+### 4.1 Batch List
+
+#### 4.1.1 Batch List Description
+
+The batch list displays all production batch information, supporting query and filtering by multiple conditions.
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Batch List Function
+
+
+#### 4.1.2 Batch Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Batch Number | Query by batch number exactly |
+| Product Model | Filter by product model |
+| Factory | Filter by factory |
+| Production Line | Filter by production line |
+| Creation Time | Filter by creation time range |
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Batch List Query Conditions
+
+
+
+### 4.2 New Batch
+
+#### 4.2.1 New Batch Description
+
+Create a new production batch, need to select associated basic data and production parameters.
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Batch Management] → [Batch List]
+2. Click [New] button
+3. Select the associated process flow
+4. Select product model
+5. Select production area
+6. Select production line
+7. Fill in planned completion date
+8. Fill in planned completion quantity
+9. Click [OK] to complete batch creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Batch Number | Unique identification code of the batch, user-defined | Yes |
+| Process Flow | Production process route used by the batch | Yes |
+| Product Model | Product specification produced by the batch | Yes |
+| Production Area | Production area to which the batch belongs | Yes |
+| Production Line | Production line where the batch is executed | Yes |
+| Expected Completion Date | Planned completion time | Yes |
+| Production Quantity | Planned production quantity | Yes |
+| Batch Status | Initial status is "Pending Production" | No |
+| Remarks | Other supplementary description information | No |
+
+**[Important]** The batch number cannot be modified after creation. Please confirm carefully when creating.
+**[Important]** Once a batch starts production, it cannot be deleted.
+
+**Function Screenshot**:
+
+
+

+
Figure 1: New Batch
+
+
+### 4.3 Edit Batch
+
+#### 4.3.1 Edit Batch Description
+
+Modify batch information, only the planned completion date and planned completion quantity can be edited.
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Batch Management] → [Batch List]
+2. Find the batch to edit in the list
+3. Click [Edit] button
+4. Modify the information to be updated
+5. Click [OK] to complete modification
+
+**[Note]** For batches that have started production, basic information cannot be edited, only remark information can be updated.
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Edit Batch
+
+
+
+### 4.4 Delete Batch
+
+#### 4.4.1 Delete Batch Description
+
+Delete batch records, only batches that have not started production can be deleted.
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Batch Management] → [Batch List]
+2. Find the batch to delete in the list
+3. Click [Delete] button
+4. Confirm the deletion operation
+
+**[Note]** Deleting a batch will permanently delete the batch data and cannot be recovered.
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Delete Batch
+
+
+
+## 4.5.1 Batch Battery Login
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Batch Management] → [Batch List]
+2. Click [Import] button
+3. Fill in battery data according to the template format
+4. Click [Select File] to upload the filled Excel file
+5. Click [Start Import] to execute data import
+6. View the import result report
+
+**[Note]** Before importing, please ensure that the associated process flow, product model, factory, and production line already exist.
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Batch Battery Login
+
+
+

+
Figure 2: Batch Battery Login File Format
+
+
+

+
Figure 3: Batch Battery Login File Upload
+
+
+

+
Figure 4: Batch Battery Login File Upload Complete
+
\ No newline at end of file
diff --git a/en/planning_production/batch_tray.md b/en/planning_production/batch_tray.md
new file mode 100644
index 0000000..a1e8b41
--- /dev/null
+++ b/en/planning_production/batch_tray.md
@@ -0,0 +1,202 @@
+# Batch Tray
+
+## 1. Function Overview
+
+Batch Tray belongs to the core module of the MES system, used to manage the association relationship between production batches and trays, realizing logistics tracking and management of batches during production. Trays are production containers that carry materials, and batch tray management runs through the entire production logistics process.
+
+**Core Functions:**
+
+- Batch Tray Query: Query the association information between batches and trays
+- Batch Tray Details: View detailed information of batch trays
+- Batch Tracking: Track the flow status of batches on trays
+- Unbind Operation: Unbind the association between batches and trays
+- Stop Operation: Stop the current status of batch trays
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Batch Tray Page
+
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Batch Tray | Batch Tray, association record between batch and tray | Records the tray information where batch goods are located |
+| Tray | Tray, container for carrying materials | Used for material storage and flow |
+| Tray Activation Status | Tray Activation Status, whether the tray is activated | Records the activation status of the tray |
+| Tray Number | Tray Number, unique identifier of the tray | Each tray has a unique number |
+| Batch Number | Batch, unique identifier of the batch | Used to trace product production information |
+| Unbind | Unbind, release the association between batch and tray | Executed when materials leave the tray |
+| Stop | Stop, stop the current status of the batch tray | Pause further flow of the batch |
+
+
+## 3. Data Model Relationship Explanation
+
+### 3.1 Batch Tray Battery Hierarchy Relationship
+
+Batch serves as the top-level entity, processes represent production stages. Some processes require trays to carry batteries, while in some processes, batteries exist independently after unbinding.
+
+```mermaid
+flowchart TB
+ subgraph Batch
+ subgraph Process1["Process 1 (Tray Carrying)"]
+ subgraph Tray1
+ Bat1[Battery 1]
+ Bat2[Battery 2]
+ end
+ end
+ subgraph Process2["Process 2 (No Tray Needed)"]
+ Bat3[Battery 3]
+ Bat4[Battery 4]
+ end
+ end
+```
+
+**Relationship Explanation:**
+
+| Relationship Type | Description |
+|------------------|-------------|
+| Batch → Process | **1:N**: A batch can contain multiple processes |
+| Process → Tray | **1:N**: A process can contain multiple trays (Process 1 has trays) |
+| Tray → Battery | **1:N**: A tray can contain multiple batteries |
+| Process → Battery | **1:N**: A process can directly contain multiple batteries (Process 2 has no tray) |
+
+
+### 3.2 Battery Tray Binding Methods
+
+There are two ways to bind batteries and trays, both can bind batteries and trays and log them to the batch:
+
+| Binding Method | Interface | Battery Status Requirement | Description |
+|----------------|-----------|---------------------------|-------------|
+| Binding Interface | `set_tray_binding` | Battery must be activated | Battery needs to be in activated state and belong to the same batch as the tray |
+| Login Interface | `set_tray_login` | Battery does not need to be activated | Battery does not need to be in activated state, can be bound and logged to the batch |
+
+
+## 4. Batch Tray Interaction Flow
+
+### 4.1 Batch Tray List
+
+#### 4.1.1 Batch Tray List Description
+
+The batch tray list displays all association information between batches and trays, supporting query and filtering by multiple conditions.
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Batch Tray Page
+
+
+
+**Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Tray Number | Unique identification code of the tray |
+| Serial Number | Serial number of the batch tray, used to uniquely identify each binding |
+| Tray Status | Current tray status |
+| Batch Number | Associated batch number |
+| Process Flow Name | Associated process flow name |
+| Current Process | Current process where the tray is located |
+| Loaded Battery Quantity | Current quantity of batteries loaded on the tray |
+| Login Time | Batch tray login time |
+
+
+#### 4.1.2 Batch Tray Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Tray Number | Query by tray number exactly |
+| Batch Number | Query by batch number exactly |
+| Tray Activation Status | Filter by status (Activated, Stopped) |
+| Login Time | Filter by creation time range |
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Batch Tray Query Conditions
+
+
+
+### 4.2 Batch Tray Details
+
+#### 4.2.1 Details View Description
+
+View detailed information of the batch tray, including basic tray information, process flow time information, process flow equipment, loaded battery quantity, battery number, battery position, battery status, etc.
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Batch Management] → [Batch Tray]
+2. Find the batch tray record to view details in the list
+3. Click [Details] button
+4. View complete batch tray information
+
+**Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Tray Number | Unique identification code of the tray |
+| Process Start Time | Process start time, used to record the start time of the process |
+| Process End Time | Process end time, used to record the end time of the process |
+| Current Process | Current process where the tray is located |
+| Serial Number | Position of the battery barcode in the tray |
+| Battery Barcode | Unique identification code of the battery |
+| Battery Activation Status | Current status of the battery, such as activated, deactivated, etc. |
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Batch Tray Details
+
+
+
+### 4.3 Unbind Operation
+
+#### 4.3.1 Unbind Description
+
+Release the association between batch and tray. After unbinding, the tray status will become stopped, but the battery status will not change.
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Batch Management] → [Batch Tray]
+2. Find the batch tray record to unbind in the list
+3. Click [Unbind] button
+4. Click [OK] to complete the unbind operation
+
+**[Important]** The unbind operation is irreversible. Please confirm before executing.
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Batch Tray Unbind
+
+
+### 4.4 Stop Operation
+
+#### 4.4.1 Stop Description
+
+Stop the activation status of the tray and battery, pause further flow of the tray, used to handle abnormal situations.
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Batch Management] → [Batch Tray]
+2. Find the batch tray record to stop in the list
+3. Click [Stop] button
+4. Click [OK] to complete the stop operation
+
+**[Important]** The stop operation is irreversible. Please confirm before executing.
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Batch Tray Stop
+
\ No newline at end of file
diff --git a/en/planning_production/device_monitoring.md b/en/planning_production/device_monitoring.md
new file mode 100644
index 0000000..859f66f
--- /dev/null
+++ b/en/planning_production/device_monitoring.md
@@ -0,0 +1,82 @@
+# Device Monitoring
+
+## 1. Function Overview
+
+Device Monitoring belongs to the production monitoring module of the MES system, used to monitor the device status of production equipment in real-time.
+
+**Core Functions:**
+
+- Device Status Monitoring: Monitor the operating status of equipment in real-time
+
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Device Monitoring Page
+
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Device Status | Device Status, current operating status of the equipment | Including running, standby, fault, etc. |
+| Last Response | Last Response, last response time of the equipment | Time when the equipment last uploaded its status |
+| Information | Information, equipment information | Detailed information of the equipment, such as equipment type, associated production line, etc. |
+
+
+## 3. Device Monitoring Interaction Flow
+
+### 3.1 Device Status Monitoring
+
+#### 3.1.1 Device Status List Description
+
+The device status list displays the real-time operating status of all equipment, supporting query and filtering by multiple conditions.
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Device Monitoring Running Status
+
+
+**Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Device Code | Unique identification code of the equipment |
+| Device Name | Name of the equipment |
+| Factory Area | Factory area to which the equipment belongs |
+| Production Line | Production line to which the equipment belongs |
+| Workstation | Workstation to which the equipment belongs |
+| Last Response | Last response time of the equipment |
+| Work Status | Current work status of the equipment |
+| Information | Exception information in case of abnormal status |
+
+
+#### 3.1.2 Device Status Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Device Number | Query by device number exactly |
+| Device Name | Fuzzy query by device name |
+| Device Type | Filter by device type |
+| Operating Status | Filter by operating status |
+| Associated Production Line | Filter by production line |
+
+
+## 3.1.3. Device Status Explanation
+
+| Status | Status Code | Description |
+|--------|------------|-------------|
+| Running | RUN | Equipment is running normally |
+| Standby | IDLE | Equipment is on standby |
+| Abnormal | TROUBLE | Equipment has an abnormality |
+| Manual | MANUAL | Equipment is in manual operation |
+| Offline | OFFLINE | Equipment is offline |
+| Completed | FINISH | Equipment has completed the task |
+
+**Important** Refer to the device status upload interface documentation for detailed information on the upload format and content of device status.
\ No newline at end of file
diff --git a/en/planning_production/material_monitoring.md b/en/planning_production/material_monitoring.md
new file mode 100644
index 0000000..a9dee76
--- /dev/null
+++ b/en/planning_production/material_monitoring.md
@@ -0,0 +1,120 @@
+# Semi-finished Product Management
+
+## 1. Function Overview
+
+Semi-finished Product Management is used to record and query semi-finished product information produced in each process during production, supporting semi-finished product entry and traceability.
+
+**Main Functions:**
+
+- Semi-finished Product Data Entry: Register semi-finished product information produced in each process into the system
+- Semi-finished Product List Query: Retrieve semi-finished product records by batch number, semi-finished product ID, process unit, unloading time, etc.
+- Material Status Viewing: View whether the semi-finished product is currently "Completed" or "Unused"
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Semi-finished Product Management Page
+
+
+## 2. Term Explanation
+
+| Term | Definition |
+|------|------------|
+| Semi-finished Product | Intermediate materials produced in each process during production |
+| Semi-finished Product ID | Unique number automatically generated by the system for each semi-finished product |
+| Semi-finished Product Code | Code identifying the semi-finished product material type |
+| Batch Number | Production batch number to which the semi-finished product belongs |
+| Process Unit | Specific process that produced the semi-finished product |
+| Material Status | Current usage status of the semi-finished product: Completed / Unused |
+
+## 3. Semi-finished Product Management Interaction Flow
+
+### 3.1 Semi-finished Product List
+
+#### 3.1.1 List Description
+
+The semi-finished product list displays all entered semi-finished product records, sorted by unloading time from newest to oldest by default, supporting pagination.
+
+**Table Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Batch Number | Production batch number to which the semi-finished product belongs |
+| Semi-finished Product ID | Unique number automatically generated by the system, format is "process attribute-material category-material code-timestamp" |
+| Semi-finished Product Code | Code representing the semi-finished product material type |
+| Output Quantity | Quantity of semi-finished products produced in this process |
+| Process Unit | Process name that produced the semi-finished product |
+| Production Equipment | Equipment number used to produce the semi-finished product |
+| Material Status | Red label indicates "Completed", green label indicates "Unused" |
+| Unloading Time | Time when the semi-finished product was produced |
+
+#### 3.1.2 List Query
+
+Semi-finished product records can be filtered by the following conditions:
+
+| Query Condition | Description |
+|----------------|-------------|
+| Batch Number | Fuzzy search by batch number |
+| Semi-finished Product ID | Exact search by semi-finished product ID |
+| Process Unit | Filter by selecting from the dropdown list of process units |
+| Unloading Time | Select a time range to query semi-finished products produced within that period |
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Semi-finished Product Management Query Conditions
+
+
+### 3.2 Enter Semi-finished Product Data
+
+#### 3.2.1 Entry Process Description
+
+**Operation Steps:**
+
+1. Go to [Production Planning] → [Semi-finished Product Management]
+2. Click the **[Enter Semi-finished Product Data]** button above the table
+3. Fill in the following information in the pop-up dialog:
+
+| Field | Required | Description |
+|-------|----------|-------------|
+| Production Batch | Yes | Select the associated production batch from the dropdown list |
+| Process Unit | Yes | Select the process unit that produced the semi-finished product from the dropdown list (options automatically linked based on selected batch) |
+| Equipment Code | Yes | Select the production equipment number from the dropdown list |
+| Output Quantity | Yes | Enter the output quantity of this process, minimum is 1 |
+| Output Date | No | Select the output date of the semi-finished product |
+
+4. Click **OK** to submit after filling
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Semi-finished Product Management Data Entry
+
+
+
+#### 3.2.2 Entry Validation Description
+
+| Validation Item | Rule |
+|-----------------|------|
+| Production Batch | Required, must be selected from the list |
+| Process Unit | Required, must be selected from the list |
+| Output Quantity | Required, must be a number greater than 0 |
+
+#### 3.2.3 Entry Processing
+
+After submitting the entry, the system will automatically perform the following processing:
+
+1. **Validate Associated Data**: Confirm that the batch number exists, the process unit is valid, and the material output configuration for this process has been set
+2. **Generate Semi-finished Product ID**: The system automatically generates a unique semi-finished product number based on process attributes, material category, material code, and current time
+3. **Calculate Subsequent Processes**: Automatically determine the next flow process for this semi-finished product based on the process flow
+4. **Save Data**: Write the semi-finished product information to the system. If any step fails, it will automatically roll back to ensure data consistency
+
+## 4. Material Status Description
+
+| Status | Label Color | Description |
+|--------|------------|-------------|
+| Completed | Red | The semi-finished product has been used by subsequent processes |
+| Unused | Green | The semi-finished product has not been used by subsequent processes yet |
\ No newline at end of file
diff --git a/en/planning_production/reject_management.md b/en/planning_production/reject_management.md
new file mode 100644
index 0000000..89a1c2d
--- /dev/null
+++ b/en/planning_production/reject_management.md
@@ -0,0 +1,167 @@
+# Battery Rejection Management
+
+## 1. Function Overview
+
+Battery Rejection Management is used to reactivate NG (defective) batteries produced during production, restoring them to normal production status and continuing to flow according to the process flow.
+
+**Main Functions:**
+
+- Battery Verification: Input battery barcode, the system verifies whether the battery meets the reactivation conditions
+- Rejection Activation: Reactivate eligible NG batteries and restore them to normal production status
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Battery Rejection Management Page
+
+
+
+## 2. Term Explanation
+
+| Term | Definition |
+|------|------------|
+| NG Battery | Batteries judged as defective during quality inspection in production |
+| Rejection | Reactivate NG batteries to restore normal production |
+| Battery Barcode | Unique identification number of the battery |
+| Activation Status | Whether the battery is currently in a flowable production state |
+| Tray | Production container carrying batteries |
+| Batch | Production batch to which the battery belongs |
+
+## 3. Battery Rejection Logic Flow
+
+```mermaid
+sequenceDiagram
+ participant 用户 as User
+ participant 前端页面 as Frontend Page
+ participant 后端服务 as Backend Service
+ participant Workerman as Workerman
+
+ 用户->>前端页面: Input battery barcode, click verify data
+ 前端页面->>后端服务: Request to verify battery information
+
+ 后端服务->>后端服务: Validation 1: Check if battery exists in the system
+ alt Battery does not exist
+ 后端服务-->>前端页面: Prompt battery does not exist
+ 前端页面-->>用户: Display exception information
+ end
+
+ 后端服务->>后端服务: Validation 2: Check if all battery batches are the same
+ alt Batch mismatch
+ 后端服务-->>前端页面: Prompt batch mismatch
+ 前端页面-->>用户: Display exception information
+ end
+
+ 后端服务->>后端服务: Validation 3: Check if battery is bound to an activated tray
+ alt Tray still activated
+ 后端服务-->>前端页面: Prompt tray activated
+ 前端页面-->>用户: Display exception information
+ end
+
+ 后端服务->>后端服务: Validation 4: Check if battery is in NG status
+ alt Not NG battery
+ 后端服务-->>前端页面: Prompt not NG battery
+ 前端页面-->>用户: Display exception information
+ end
+
+ 后端服务->>后端服务: Validation 5: Check if battery is in inactive status
+ alt Battery already activated
+ 后端服务-->>前端页面: Prompt battery already activated
+ 前端页面-->>用户: Display exception information
+ end
+
+ 后端服务-->>前端页面: Verification passed, return battery details
+ 前端页面-->>用户: Display battery information table
+
+ 用户->>前端页面: Verify information, click rejection activation
+ 前端页面-->>用户: Pop up confirmation prompt
+ 用户->>前端页面: Click OK
+
+ 前端页面->>Workerman: Send rejection activation command
+ Workerman->>Workerman: Copy battery data to generate new record
+ Workerman->>Workerman: Clear NG flag and grade information
+ Workerman->>Workerman: Reactivate battery
+ Workerman-->>前端页面: Return activation success
+ 前端页面-->>用户: Prompt rejection successful, battery restored to flow
+```
+
+**Key Validation Rules:**
+
+| Validation Item | Rule Description |
+|-----------------|------------------|
+| Battery Existence | Each input battery barcode must exist in the system |
+| Batch Consistency | All input batteries must belong to the same production batch |
+| Tray Status | If the battery is bound to a tray, the tray cannot be in activated status |
+| NG Status | The battery must have an NG flag; normal batteries cannot be rejected |
+| Activation Status | The battery must currently be in inactive status; already activated batteries cannot be rejected |
+
+## 4. Operation Steps
+
+### 4.1 Verify Battery
+
+1. Go to [Production Monitoring] → [Battery Rejection Management]
+2. Enter battery barcodes in the input box:
+ - Method 1: Directly enter multiple battery barcodes in the input box, separated by commas
+ - Method 2: Click the **📄** button on the right side of the input box, enter one battery barcode per line in the pop-up multi-line input box, click OK
+3. Click the **[Verify Data]** button
+4. The system validates the battery information, and upon passing, displays the battery details in the table below
+
+**Table Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Battery Barcode | Unique identification number of the battery |
+| Batch | Production batch to which the battery belongs |
+| Tray | Tray number bound to the battery |
+| Serial Number | Production serial number of the battery |
+| Activation Status | "Activated" or "Inactivated" |
+| Grade Type | Grade classification of the battery |
+| Grade | Grade information of the battery |
+| Previous Process | Last completed process of the battery |
+| Current Process | Next process for the battery to flow to |
+
+### 4.2 Execute Rejection Activation
+
+1. After verification, verify the battery information in the table
+2. Click the **[Rejection Activation]** button
+3. The system pops up a confirmation prompt: "After confirmation, the battery will be activated. After activation, production can only start from the current process, and cannot redo the previous process"
+4. Click **OK** to complete the rejection
+
+**[Important]**:
+- After rejection activation, the NG flag of the battery will be cleared, and the grade information will also be cleared
+- After activation, the battery can only continue to flow from the current process and cannot return to the previous process
+- This operation is irreversible. Please confirm before executing
+
+**Function Screenshots**:
+
+
+

+
Figure 1: Battery Rejection Activation Input
+
+
+
+

+
Figure 2: Battery Rejection Activation Data Verification
+
+
+
+

+
Figure 3: Battery Rejection Activation Data Verification Passed
+
+
+
+

+
Figure 4: Rejection Activation Confirmation
+
+
+
+## 5. Common Exception Prompts
+
+| Prompt Message | Cause | Handling Suggestion |
+|----------------|-------|---------------------|
+| Battery does not exist in BATTERY_MAP data | Battery barcode input error or not registered in the system | Check if the barcode is correct |
+| Battery batch does not match the first one | Batteries from different batches were input | Ensure batteries from the same batch are rejected together |
+| The tray bound to the battery is still activated | The tray containing the battery is still in production | Wait for the tray to complete before operating |
+| The barcode must be inactive and an NG battery | The battery does not meet the rejection conditions | Only NG and inactive batteries can be rejected |
+| The battery is already activated in the batch, no need to reactivate | The battery is already activated | No operation needed |
+| The battery has no NG information, not an NG battery | The battery is a normal product | Normal batteries do not need rejection |
\ No newline at end of file
diff --git a/en/planning_production/technology_process.md b/en/planning_production/technology_process.md
new file mode 100644
index 0000000..ed52b53
--- /dev/null
+++ b/en/planning_production/technology_process.md
@@ -0,0 +1,238 @@
+# Battery Process Management
+
+## 1. Function Overview
+
+Battery Process Management belongs to the production monitoring module of the MES system, used to manage the process flow of batteries during production, realizing operations such as adding, deleting, modifying, and querying processes.
+
+**Core Functions:**
+
+- Process Management: Maintain basic information and configuration of processes
+- Process Query: Query the current process and process history of batteries
+- Process Adjustment: Adjust the current process of batteries
+- Process Records: Record the process flow history of batteries
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Battery Process Management Page
+
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Battery Process | Battery Process, processing steps of batteries in production | Defines the production processing flow of batteries |
+| Process Sequence | Process Sequence, execution order of processes | Batteries flow through each process in order |
+| Process Time | Process Time, time nodes of batteries in the process | Including start time, end time |
+
+
+## 3. Data Model Relationship Explanation
+
+### 3.1 Battery Process Management and Other Entity Relationships
+
+```mermaid
+flowchart TB
+ subgraph Battery
+ Bat[Battery]
+ end
+
+ subgraph Batch
+ B[Batch]
+ end
+
+ subgraph Process
+ P[Process]
+ end
+
+ subgraph Process Record
+ PR[Process Record]
+ end
+
+ PR -->|关联| Bat
+ PR -->|关联| B
+ PR -->|属于| P
+```
+
+**Relationship Explanation:**
+
+| Relationship Type | Description |
+|------------------|-------------|
+| Process Record → Battery | **N:1**: Multiple process records correspond to one battery |
+| Process Record → Batch | **N:1**: Multiple process records correspond to one batch |
+| Process Record → Process | **N:1**: Multiple process records correspond to the same process |
+
+
+## 4. Battery Process Management Interaction Flow
+
+### 4.1 Battery Process List
+
+#### 4.1.1 Battery Process List Description
+
+The battery process list displays the process flow information of all batteries, supporting query and filtering by multiple conditions.
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Data Verification After Entry
+
+
+**Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Battery Number | Unique identification code of the battery |
+| Batch Number | Associated batch number |
+| Current Process | Current process where the battery is located |
+| Previous Process | Previous process of the battery |
+| Next Process | Next process of the battery |
+| Entry Time | Time when the battery entered the current process |
+| Process Status | Processing status of the current process |
+
+
+#### 4.1.2 Battery Process Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Battery Number | Query by battery number exactly |
+| Batch Number | Query by batch number exactly |
+| Current Process | Filter by current process |
+| Process Status | Filter by process status |
+
+
+### 4.2 Process Management
+
+#### 4.2.1 New Process Description
+
+Add a new process record for the battery.
+
+**Operation Steps:**
+
+1. Go to [Production Monitoring] → [Battery Process Management]
+2. Click [New Process] button
+3. Scan or enter battery number
+4. Select process
+5. Fill in process information
+6. Click [OK] to complete the addition
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Battery Number | Unique identification code of the battery | Yes |
+| Process | Select the process to add | Yes |
+| Start Time | Process start time | Yes |
+| Remarks | Other supplementary description information | No |
+
+
+#### 4.2.2 Delete Process Description
+
+Delete the process record of the battery.
+
+**Operation Steps:**
+
+1. Go to [Production Monitoring] → [Battery Process Management]
+2. Find the battery process record to delete in the list
+3. Click [Delete] button
+4. Confirm the deletion information
+5. Click [OK] to complete the deletion
+
+**[Important]** The delete operation is irreversible. Please confirm before executing.
+
+
+#### 4.2.3 Modify Process Description
+
+Modify the process information of the battery.
+
+**Operation Steps:**
+
+1. Go to [Production Monitoring] → [Battery Process Management]
+2. Find the battery process record to modify in the list
+3. Click [Edit] button
+4. Modify the process information
+5. Click [OK] to complete the modification
+
+
+### 4.3 Process Adjustment
+
+#### 4.3.1 Process Adjustment Description
+
+Adjust the current process of the battery to achieve jumps between processes.
+
+**Operation Steps:**
+
+1. Go to [Production Monitoring] → [Battery Process Management]
+2. Find the battery record to adjust in the list
+3. Click [Adjust Process] button
+4. Select the target process
+5. Fill in the adjustment reason
+6. Click [OK] to complete the adjustment
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Battery Number | Unique identification code of the battery | Yes |
+| Current Process | Current process where the battery is located | Yes |
+| Target Process | Target process after adjustment | Yes |
+| Adjustment Reason | Select or fill in the adjustment reason | Yes |
+
+**Function Screenshots**:
+
+
+

+
Figure 1: Battery Data Entry Page
+
+
+
+

+
Figure 2: Data Verification After Entry
+
+
+
+

+
Figure 2: Select Target Process
+
+
+
+

+
Figure 2: Process Change Successful
+
+
+
+### 4.4 Process Flow History
+
+#### 4.4.1 Flow History Description
+
+View the complete process flow history record of the battery.
+
+**Operation Steps:**
+
+1. Go to [Production Monitoring] → [Battery Process Management]
+2. Find the battery record to view history in the list
+3. Click [Flow History] button
+4. View the complete process flow trace of the battery
+
+**Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Process Name | Name of the process |
+| Entry Time | Time when entering the process |
+| Exit Time | Time when leaving the process |
+| Process Result | Processing result of the process |
+| Operator | Personnel who performed the operation |
+
+
+## 5. Process Status Description
+
+| Status | Description |
+|--------|-------------|
+| Pending | Battery is waiting for this process to be processed |
+| Processing | Battery is being processed in this process |
+| Completed | Battery has completed this process |
+| Abnormal | Battery has an abnormality in this process |
\ No newline at end of file
diff --git a/en/planning_production/tray_login.md b/en/planning_production/tray_login.md
new file mode 100644
index 0000000..e426532
--- /dev/null
+++ b/en/planning_production/tray_login.md
@@ -0,0 +1,90 @@
+# Tray Login
+
+## 1. Function Overview
+
+Tray Login belongs to the production monitoring module of the MES system, used to log trays and batteries onto the production line, record the login status of trays, and support querying tray-related information.
+
+**Core Functions:**
+
+- Tray Login: Execute tray login operation
+- Tray Unbind: Unbind the binding relationship between tray and battery
+- Tray Stop: Set the activation status of tray and battery to stopped, ending the flow of tray and battery
+- Tray Code Format: Support user-defined format, verify whether the tray barcode format entered by the user is correct
+- Battery Code Format: Support user-defined format, verify whether the battery barcode format entered by the user is correct
+
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Tray Login Page
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Tray Login | Tray Login, tray enters the production line | Tray starts operating on the production line |
+| Login Status | Login Status, whether the tray has logged in | Records the login status of the tray |
+
+
+## 3. Tray Login Interaction Flow
+
+### 3.1 Tray Login Operation
+
+**Operation Steps:**
+
+1. Go to [Production Monitoring] → [Tray Login]
+2. Select batch number
+3. Select tray and battery format codes
+4. Scan or enter tray number
+5. Scan or enter battery number
+6. Click login button
+7. Click [OK] to complete the login operation
+
+**Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Channel | Channel for tray login |
+| Battery ID | Scanned or entered battery ID |
+| Previous Batch | Batch number logged on the tray |
+| Previous Tray | Tray number logged on the tray |
+| Battery Completed Process | Whether the battery has completed the current process |
+
+**Function Screenshots**:
+
+
+

+
Figure 1: Tray Login Select Batch
+
+
+
+

+
Figure 2: Tray Login Select Tray and Battery Format 1
+
+
+
+

+
Figure 3: Tray Login Select Tray and Battery Format 2
+
+
+
+

+
Figure 4: Tray Login Add Battery Tray Format
+
+
+
+

+
Figure 5: Tray Login Select Tray and Battery Format 3
+
+
+
+

+
Figure 6: Tray Login Enter Tray and Battery Barcode
+
+
+
+

+
Figure 7: Tray Login Confirm Login
+
diff --git a/en/planning_production/tray_management.md b/en/planning_production/tray_management.md
new file mode 100644
index 0000000..f60c119
--- /dev/null
+++ b/en/planning_production/tray_management.md
@@ -0,0 +1,226 @@
+# Tray Management
+
+## 1. Function Overview
+
+Tray Management belongs to the production monitoring module of the MES system, used to manage trays during production, implementing functions such as tray process adjustment, stop operation, status query, and battery query for tray binding.
+
+**Core Functions:**
+
+- Tray Status Query: Query the current status of trays
+- Tray Process Adjustment: Adjust the process where the tray is located
+- Tray Stop Operation: Stop the current status of the tray
+- Tray Battery Query: Query battery information bound to the tray
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Tray Management Page
+
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Tray | Tray, container for carrying materials | Used for material storage and flow |
+| Tray Status | Tray Status, current status of the tray | Including idle, in use, stopped, etc. |
+| Tray Process | Tray Process, the process where the tray is located | The current production process of the tray |
+
+
+## 3. Data Model Relationship Description
+
+### 3.1 Tray Management and Other Entity Relationships
+
+```mermaid
+flowchart TB
+ subgraph Tray
+ T[Tray]
+ end
+
+ subgraph Batch
+ B[Batch]
+ end
+
+ subgraph Process
+ P[Process]
+ end
+
+ subgraph Battery
+ Bat[Battery]
+ end
+
+ T -->|Belongs to| B
+ T -->|Located at| P
+ T -->|Carries| Bat
+```
+
+**Relationship Description:**
+
+| Relationship Type | Description |
+|------------------|-------------|
+| Tray → Batch | **N:1**: Multiple trays belong to one batch |
+| Tray → Process | **N:1**: Multiple trays are in the same process |
+| Tray → Battery | **1:N**: One tray can carry multiple batteries |
+
+
+## 4. Tray Management Interaction Flow
+
+#### 4.1 Tray Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Tray Number | Exact query by tray number |
+
+**Operation Steps:**
+
+1. Go to [Production Monitoring] → [Tray Management]
+2. Enter tray number
+3. Click [Query] button
+4. View tray details
+
+**Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Tray Number | Unique identification code of the tray |
+| Tray Status | Current tray status |
+| Batch | Associated batch number |
+| LOT | Tray serial number |
+| Input Batteries | Number of batteries bound to the tray |
+| Input Time | Tray login time |
+| Previous Process | Previous process number of the tray |
+| Current Process | Current process where the tray is located |
+| Status | Current status of the tray, Active/Stopped |
+| Whole Tray NG | Whether the tray is marked as whole tray NG |
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Tray Management Page
+
+
+
+### 4.2 Tray Process Adjustment
+
+#### 4.2.1 Process Adjustment Description
+
+Adjust the process where the tray is located to achieve transfer between processes.
+
+**Operation Steps:**
+
+1. Go to [Production Monitoring] → [Tray Management]
+2. Enter tray number
+3. Click [Query] button
+4. Select the target process in the left process list
+5. Click [OK] to complete the process adjustment
+
+**[Important]** Process adjustment may affect the production flow, please confirm before execution.
+
+**Function Screenshots**:
+
+
+

+
Figure 1: Tray Management Adjust Process 1
+
+
+
+

+
Figure 2: Tray Management Adjust Process 2
+
+
+
+

+
Figure 3: Tray Management Adjust Process 3
+
+
+
+### 4.3 Tray Stop
+
+#### 4.3.1 Tray Stop Description
+
+Stop the current status of the tray and pause further flow of the tray.
+
+**Operation Steps:**
+
+1. Go to [Production Monitoring] → [Tray Management]
+2. Enter tray number
+3. Click [Query] button
+4. Click [Stop Tray] button
+5. Click [OK] to complete the stop operation
+
+**[Important]** Stopping the tray will change the status of batteries and tray to stopped, and they cannot continue to flow.
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Tray Management Tray Stop
+
+
+### 4.4 Tray Battery Query
+
+#### 4.4.1 Battery Query Description
+
+Query battery information bound to the tray to understand the specific batteries carried by the tray.
+
+**Operation Steps:**
+
+1. Go to [Production Monitoring] → [Tray Management]
+2. Enter tray number
+3. Click [Query] button
+4. View the battery list bound to the tray
+
+**Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Battery Number | Unique identification code of the battery |
+| Battery Position | Position of the battery in the tray |
+| Battery Activation Status | Activation status of the battery, Active/Stopped/NG |
+
+
+## 4.5 Whole Tray NG Handling
+
+Mark the tray as whole tray NG and record the NG information of the tray.
+
+**Operation Steps:**
+
+1. Go to [Production Monitoring] → [Tray Management]
+2. Enter tray number
+3. Click [Query] button
+4. Click [Mark NG Tray] button
+5. Click [OK] to complete the marking operation
+
+**[Important]** After marking as NG tray, the tray status will be changed to NG status, and the logistics line will obtain the whole tray NG information through the interface get_process_route.
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Tray Management Whole Tray NG
+
+
+## 4.6 Clear Tray NG
+
+Clear the NG mark of the tray and restore the NG status of batteries in the tray to normal.
+
+**Operation Steps:**
+
+1. Go to [Production Monitoring] → [Tray Management]
+2. Enter tray number
+3. Click [Query] button
+4. Click [Clear NG Tray] button
+5. Click [OK] to complete the clearing operation
+
+**[Important]** After clearing the NG tray, the NG batteries in the tray will be restored to normal status, but the production log will not be cleared.
+
+**Function Screenshot**:
+
+
+

+
Figure 1: Tray Management Clear Tray NG
+
\ No newline at end of file
diff --git a/en/production_configuration/Organization.md b/en/production_configuration/Organization.md
new file mode 100644
index 0000000..5c28b07
--- /dev/null
+++ b/en/production_configuration/Organization.md
@@ -0,0 +1,159 @@
+# Production Team Model
+
+## 1. Function Overview
+
+The Production Team Model belongs to the basic module of the MES system. It is used to build the production team, production shift, and production member data of the enterprise, providing organizational basic data support for production scheduling.
+
+**Core Functions:**
+
+- Team Management: Maintain the addition, deletion, modification, and query of production teams
+- Schedule Plan Management: Maintain the addition, deletion, modification, and query of production schedules
+- Schedule Calendar: View the time planning and scheduling information of production schedules
+
+**Function Screenshot**:
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Production Team | Production Team, production operation organization unit | Used to organize and manage production personnel |
+| Team Members | Production Members, members of the team | Operators belonging to a specific team |
+| Schedule Plan | Production Schedule, team's schedule plan | Defines working hours and task allocation for the team |
+| Rotation Method | Rotation Schedule, team's scheduling method | Such as rotation shifts, fixed scheduling, etc. |
+| Rest Day Selection | Rest Day Schedule, team's rest day selection | Defines which days are rest days |
+
+
+**Relationship Description:**
+
+| Relationship Type | Description |
+|------------------|-------------|
+| Team → Shift | **1 to N**: A team can contain multiple shifts |
+| Team → Production Members | **1 to N**: A team can contain multiple production members |
+
+## 3. Production Team Model Interaction Flow
+
+### 3.1 Team Management
+
+#### 3.1.1 Team Description
+
+A team is the basic organizational unit for production operations, used to assign production personnel.
+
+**Function Screenshot**:
+
+
+#### 3.1.2 Add Team
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Team Model] → [Team Management]
+2. Click [Add] button
+3. Fill in basic team information
+4. Add team members
+5. Click [OK] to complete team creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Team Name | Name of the team, e.g., "Packaging Team" | Yes |
+| Belonging Factory Area | Production factory area where the team belongs, e.g., "Factory A" | Yes |
+| Belonging Production Line | Production line where the team belongs, e.g., "Packaging Line" | Yes |
+
+
+**[Important]** The team code cannot be modified after creation. Please confirm carefully when creating.
+
+
+**Function Screenshot**:
+
+
+#### 3.1.3 Team Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Team Name | Fuzzy query by team name |
+| Belonging Factory Area | Filter by team's factory area |
+| Belonging Production Line | Filter by team's production line |
+| Creation Time | Filter by team creation time |
+
+### 3.2 Schedule Plan
+
+#### 3.2.1 Schedule Plan Description
+
+A schedule plan is the basic division of team working hours, used to manage the time arrangement of production operations.
+
+**Function Screenshot**:
+
+
+#### 3.2.2 Add Schedule Plan
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Team Model] → [Schedule Plan]
+2. Click [Add] button
+3. Fill in basic schedule plan information
+4. Click [OK] to complete schedule plan creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Schedule Name | Name of the schedule plan, e.g., "Morning Shift", "Afternoon Shift", "Evening Shift" | Yes |
+| Schedule Code | Unique identification code of the schedule plan | Yes |
+| Schedule Time Range | Time range of the schedule plan, e.g., "9:00-17:00" | Yes |
+| Status | Status of the schedule plan, e.g., "Enabled", "Disabled" | No |
+| Team | Teams included in the schedule plan | No |
+| Remarks | Other supplementary information | No |
+
+**[Important]** The schedule plan code cannot be modified after creation.
+**[Important]** The schedule plan cannot be deleted once referenced by schedule records.
+
+**Function Screenshot**:
+
+
+
+#### 3.2.3 Schedule Plan Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Schedule Code | Exact query by schedule code |
+| Schedule Name | Fuzzy query by schedule name |
+| Creation Time | Filter by schedule plan creation time |
+
+**Function Screenshot**:
+
+
+
+#### 3.2.4 Import Schedule Plan
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Team Model] → [Schedule Plan]
+2. Click [Import] button
+3. Upload schedule plan file
+4. Click [OK] to complete schedule plan import
+
+**Function Screenshot**:
+
+
+
+#### 3.2.4 Export Schedule Plan
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Team Model] → [Schedule Plan]
+2. Click [Export] button
+3. Select export format (e.g., Excel)
+4. Click [OK] to complete schedule plan export
+
+
+#### 3.2.5 Schedule Calendar
+
+The schedule calendar is a visual display of the team's schedule plan, used to view and manage schedule plans.
+
+**Function Screenshot**:
+
\ No newline at end of file
diff --git a/en/production_configuration/SPC_configuration.md b/en/production_configuration/SPC_configuration.md
new file mode 100644
index 0000000..582c2a5
--- /dev/null
+++ b/en/production_configuration/SPC_configuration.md
@@ -0,0 +1,208 @@
+# SPC Collection Model
+
+## 1. Function Overview
+
+The SPC Collection Model belongs to the basic module of the MES system. It is used to configure the result parameter collection points for process units, enabling real-time collection and monitoring of production process data. SPC (Statistical Process Control) is used to monitor the stability of production processes.
+
+**Core Functions:**
+
+- SCADA Point Binding: Configure the association relationship between process units and collection points
+- Collection Parameter Management: Manage data collection parameters for collection points
+
+
+**Function Screenshot**:
+
+
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| SPC | Statistical Process Control | Used to monitor the stability of production processes |
+| SCADA | Supervisory Control and Data Acquisition | Used for real-time data collection and monitoring |
+| Data Type | Type of collected data | Including first inspection data, result data |
+| Result Parameter | Result parameters of process units | Defines output data after process execution |
+| First Inspection Data | First piece inspection data | Inspection data for the first product produced |
+
+
+## 3. Data Model Relationship Description
+
+### 3.1 SPC Collection Configuration Components
+
+A complete SPC collection configuration consists of the following four elements:
+
+```mermaid
+flowchart LR
+ subgraph SPC Collection Configuration Elements
+ direction TB
+ A[Process Unit] --> B[SPC Collection Configuration]
+ C[Data Type] --> B
+ D[SCADA Point] --> B
+ end
+
+ B --> E[Save to Corresponding Data Table]
+```
+
+| Element | Description | Example |
+|---------|-------------|---------|
+| Process Unit | Which process to configure for | Cell assembly process |
+| Data Type | Business type of the data | First Inspection Data / Result Data |
+| SCADA Point | Source point of the data | TEMP_001 |
+
+### 3.2 Data Type and Data Table Mapping
+
+The data type determines which table the data is saved to:
+
+```mermaid
+flowchart TB
+ subgraph Data Type
+ DT1["First Inspection Data
(First Inspection)"]
+ DT2["Result Data
(Result Data)"]
+ end
+
+ subgraph Corresponding Data Table
+ T1["First Inspection Data Table
Saves first piece inspection data"]
+ T2["Result Parameter Table
Saves process result data"]
+ end
+
+ DT1 -->|"Data Type=First Inspection"| T1
+ DT2 -->|"Data Type=Result"| T2
+```
+
+### 3.3 Collection Entry Description
+
+SCADA data collection has only one entry interface `set_node_data`, with 4 callers:
+
+```mermaid
+flowchart TB
+ subgraph SCADA Collection Entry
+ A[set_node_data Interface]
+ end
+
+ subgraph Callers
+ B[EdgeMange]
+ C[EPS]
+ D[MES Internal Call]
+ E[Device Call]
+ end
+
+ B --> A
+ C --> A
+ D --> A
+ E --> A
+
+ style D fill:#90EE90
+```
+
+| Caller | Description | Relationship with SPC Configuration |
+|--------|-------------|-------------------------------------|
+| EdgeMange | Edge manager push | Does not use SPC configuration |
+| EPS | EPS system push | Does not use SPC configuration |
+| MES Internal Call | MES internal business call | **Uses SPC configuration** |
+| Device Call | Direct device call | Does not use SPC configuration |
+
+**This function configures the collection rules for "MES Internal Call".**
+
+### 3.4 MES Internal Call Collection Process
+
+When MES internal business calls the `set_node_data` interface, the SPC collection configuration determines where the data is saved:
+
+```mermaid
+sequenceDiagram
+ participant MES业务 as MES Internal Business
+ participant SCADA as set_node_data Interface
+ participant SPC配置 as SPC Collection Configuration
+ participant DB as Database
+
+ MES业务->>SCADA: Call set_node_data
Parameters: Point Code, Collected Value
+ SCADA->>SPC配置: Query configuration by point code
+ SPC配置-->>SCADA: Return: Process Unit, Data Type, SCADA Point
+ SCADA->>DB: Save to corresponding data table based on data type
+ DB-->>SCADA: Save successful
+ SCADA-->>MES业务: Return result
+```
+
+### 3.5 Configuration Examples
+
+| Configuration ID | Process Unit | Data Type | Data Table | SCADA Point |
+|-----------------|--------------|-----------|------------|-------------|
+| Config 1 | Cell Assembly Process | First Inspection Data | First Inspection Data Table | TEMP_001 |
+| Config 2 | Cell Assembly Process | Result Data | Result Parameter Table | PRESS_001 |
+| Config 3 | Formation Process | Result Data | Result Parameter Table | VOLT_001 |
+
+
+## 4. SPC Collection Model Interaction Flow
+
+### 4.1 SCADA Point Binding
+
+#### 4.1.1 Point Binding Description
+
+Point binding establishes the association between process units and SCADA collection points, enabling automatic collection of production data.
+
+**Function Screenshot**:
+
+
+#### 4.1.2 Add Point Binding
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [SPC Collection Model] → [SCADA Point Binding]
+2. Click [Add] button
+3. Select the process unit to bind
+4. Select or configure SCADA collection points
+5. Set collection parameters
+6. Click [Save] to complete point binding
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Process Unit | Process unit to bind the point | Yes |
+| Point Code | Point code in SCADA system | Yes |
+| Point Name | Descriptive name of the point | Yes |
+| Data Type | Data type of the point, e.g., "Numeric", "Switch" | Yes |
+| Collection Frequency | Data collection frequency in seconds | Yes |
+| Status | Enabled/Disabled | No |
+| Remarks | Other supplementary information | No |
+
+**[Important]** The point code must match the configuration in the SCADA system, otherwise data collection will fail.
+**[Important]** The same point code cannot be bound to the same process unit repeatedly.
+
+**Function Screenshot**:
+
+
+#### 4.1.3 Edit Point Binding
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [SPC Collection Model] → [SCADA Point Binding]
+2. Find the binding record to edit in the list
+3. Click [Edit] button
+4. Modify the information to update
+5. Click [Save] to complete modification
+
+**[Note]** Historical collected data is not affected.
+
+#### 4.1.4 Delete Point Binding
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [SPC Collection Model] → [SCADA Point Binding]
+2. Find the binding record to delete in the list
+3. Click [Delete] button
+4. Confirm the delete operation
+
+**[Note]** After deleting the point binding, subsequent data collection for this point will stop, but collected data will be retained.
+
+#### 4.1.5 Point Binding Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Process Unit | Filter by process unit |
+| Point Code | Exact query by point code |
+| Point Name | Fuzzy query by point name |
+| Status | Filter by enabled/disabled status |
+| Creation Time | Filter by creation time range |
\ No newline at end of file
diff --git a/en/production_configuration/factory_model.md b/en/production_configuration/factory_model.md
new file mode 100644
index 0000000..69e3bc9
--- /dev/null
+++ b/en/production_configuration/factory_model.md
@@ -0,0 +1,115 @@
+# Factory Area Model
+
+## 1. Function Overview
+
+The Factory Area Model belongs to the basic module of the MES system. It is used to build the factory areas and production lines for the MES system, providing data support for team management, batches, and environmental control data creation.
+
+**Core Functions:**
+
+- Factory Area Management: Maintain the addition, deletion, modification, and query of factory areas
+- Production Line Management: Maintain the addition, deletion, modification, and query of production lines
+
+Function Screenshot:
+
+
+## 2. Term Explanation
+
+#### 2.1.1 Factory Modeling Related Terms
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Factory Area | Area, production manufacturing area | Used to correspond to production lines |
+| Production Line | Production Line, production line body | Used to correspond to production teams and production workshops |
+
+
+
+## 3. Factory Area Model Structure
+
+### 3.1 Module Hierarchy Description
+
+The factory area model structure adopts hierarchical management, from top to bottom: Factory → Production Line.
+
+**Module Hierarchy Structure:**
+
+```mermaid
+flowchart TD
+ A[Factory Area Settings Area]
+ A --> B[Production Line]
+
+```
+
+| Level | Name | Description |
+|-------|------|-------------|
+| 1 | Factory | Independent production manufacturing unit |
+| 2 | Production Line | Specific production line body |
+
+
+### 3.2 Add/Edit Factory
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Factory Area Model] → [Factory Area Settings]
+2. Click [Add/Edit Factory] button, select [Add/Edit Factory] button as needed
+3. Fill in basic factory information
+4. Click [Save] to complete factory creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Factory Code | Unique identification code of the factory, usually using abbreviations | Yes |
+| Factory Name | Full name of the factory, e.g., "** Factory Area" | Yes |
+| Remarks | Other supplementary information | No |
+
+**[Important]** Once the factory code is bound to a production line, it cannot be modified. Please confirm carefully when creating.
+
+**Function Screenshot**:
+
+
+
+
+### 3.3 Add/Edit Production Line
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Factory Area Model] → [Production Line Settings]
+2. Click [Add/Edit Production Line] button, select [Add/Edit Production Line] button as needed
+3. Fill in basic production line information
+4. Click [Save] to complete production line creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Production Line Code | Unique identification code of the production line | Yes |
+| Production Line Name | Name of the production line, e.g., "** Production Line" | Yes |
+| Belonging Factory Area | Belonging factory area | Yes |
+| Remarks | Other supplementary information | No |
+
+**[Note]** Once the production line code is bound to a workshop, it cannot be modified. Please confirm carefully when creating.
+
+**Function Screenshot**:
+
+
+### 3.4 Query Operation - Factory
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Name | Fuzzy query by factory area name |
+| Code | Fuzzy query by factory area code |
+
+**Function Screenshot**:
+
+
+### 3.5 Query Operation - Production Line
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Name | Fuzzy query by production line name |
+| Code | Fuzzy query by production line code |
+
+**Function Screenshot**:
+
\ No newline at end of file
diff --git a/en/production_configuration/material_model.md b/en/production_configuration/material_model.md
new file mode 100644
index 0000000..2a007ff
--- /dev/null
+++ b/en/production_configuration/material_model.md
@@ -0,0 +1,301 @@
+# Material Model Management
+
+## 1. Function Overview
+
+Material Model Management belongs to the basic module of the MES system. It is used to build core data such as material classification, material basic information, and BOM (Bill of Materials) for the enterprise, providing material basic data support for production planning, material procurement, warehouse management, cost accounting, and other business modules.
+
+**Core Functions:**
+
+- Material Category List: Maintain the classification system of materials, manage by material type
+- Material Information Management: Maintain basic material information, material attributes, units of measure, etc.
+- BOM Management: Maintain the material composition list of products, define the quantity relationship between products and materials
+- Unit of Measure: Define standard units for measuring material quantities, such as pieces, items, kilograms, meters, etc.
+
+
+**Function Screenshot**:
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Material Category | Material Category, unit for classifying materials | Used to distinguish different types of materials |
+| Material Information | Material Information, basic attributes and characteristics of materials | Including material code, name, specification, unit, etc. |
+| Bill of Materials | BOM, Bill of Materials, product composition list | Defines the quantity relationship between products and materials |
+| Unit of Measure | Unit of Measure, standard unit for measuring material quantities | Such as pieces, items, kilograms, meters, etc., belongs to material information attributes |
+| Material Code | Material Code, unique identification code of materials | Unique number in the material management system |
+
+**Data Model Relationship Description:**
+
+```mermaid
+flowchart TB
+ subgraph Material Category List
+ MCA[Material Category A]
+ MCB[Material Category B]
+ end
+
+ subgraph Material Information Management
+ MI1[Material Info 1]
+ MI2[Material Info 2]
+ MI3[Material Info 3]
+ end
+
+ subgraph BOM Management
+ BOM1[BOM A]
+ BOM2[BOM B]
+ end
+
+ MCA -->|1:N| MI1
+ MCA -->|1:N| MI2
+ MCB -->|1:N| MI3
+
+ BOM1 ---|N:M| MI1
+ BOM1 ---|N:M| MI2
+ BOM2 ---|N:M| MI2
+ BOM2 ---|N:M| MI3
+```
+
+**Relationship Description:**
+
+| Relationship Type | Description |
+|------------------|-------------|
+| Material Category List → Material Information Management | **1 to N**: A material category can contain multiple material information entries |
+| BOM Management ↔ Material Information Management | **N to M**: A BOM can reference multiple materials, a material can be referenced by multiple BOMs |
+| Material Information Management → Unit of Measure | **Attribute**: Unit of measure is one of the attributes of material information |
+
+**Simplified Relationship Diagram:**
+
+```mermaid
+flowchart LR
+ A[Material Category List] -->|1:N| B[Material Information Management]
+ C[BOM Management] -.->|N:M| B
+
+ B -->|Contains| D[Unit of Measure]
+ B -->|Contains| E[Material Specification]
+ B -->|Contains| F[Material Attributes]
+```
+
+
+## 3. Material Model Interaction Flow
+
+### 3.1 Material Category List Management
+
+#### 3.1.1 Material Category Description
+
+Material category is a unit for classifying materials, used to distinguish different types of materials for easy retrieval and maintenance.
+
+**Function Screenshot**:
+
+
+#### 3.1.2 Add Material Category
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Material Model] → [Material Category List]
+2. Click [Add] button
+3. Fill in basic information
+4. Click [Save] to complete category creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Material Category Code | Unique identification code of the category | Yes |
+| Material Category Name | Name of the category, e.g., "Raw Materials", "Semi-finished Products" | Yes |
+| Remarks | Other supplementary information | No |
+
+**[Important]** Once the material category code is enabled, it cannot be modified or deleted. Please confirm carefully when creating.
+
+**Function Screenshot**:
+
+
+#### 3.1.3 Material Category Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Material Category Code | Exact query by material category code |
+| Material Category Name | Fuzzy query by material category name |
+| Parent Category | Filter by parent category |
+
+### 3.2 Material Information Management
+
+#### 3.2.1 Material Information Description
+
+Material information is core data describing the basic attributes and characteristics of materials, including material code, name, unit of measure, etc. It is the foundation of enterprise material management.
+
+**Material Information Characteristics:**
+
+- Uniqueness: Each material has a unique material code
+- Standardization: Material information has unified data specifications and standards
+- Relevance: Material information can be referenced by BOM, work orders, warehouse, and other modules
+
+**Function Screenshot**:
+
+
+#### 3.2.2 Add Material Information
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Material Model] → [Material Information Management]
+2. Click [Add] button
+3. Fill in basic material information
+4. Click [Save] to complete material information creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Material Code | Unique identification code of the material | Yes |
+| Material Name | Name of the material | Yes |
+| Material Category | Associated material category | Yes |
+| Unit of Measure | Unit of measure for the material, such as pieces, items, kilograms, etc. | Yes |
+| Remarks | Other supplementary information | No |
+
+**[Note]** The material code cannot be modified after creation. Please confirm carefully when creating.
+**[Important]** Once material information is referenced by BOM or other documents, it cannot be deleted.
+
+**Function Screenshot**:
+
+
+#### 3.2.3 Material Information Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Material Code | Exact query by material code |
+| Material Name | Fuzzy query by material name |
+| Material Category | Filter by material category |
+| Material Type | Filter by material type |
+
+**Function Screenshot**:
+
+
+
+### 3.3 BOM Management
+
+#### 3.3.1 BOM Description
+
+BOM (Bill of Materials) is core data defining the composition relationship between products and materials, recording which materials a product consists of and the quantity ratio of each material. BOM is an important basis for production planning, material procurement, and cost accounting.
+
+**BOM Characteristics:**
+
+- Hierarchy: Supports multi-level BOM, reflecting the product assembly structure
+- Quantity Relationship: Clearly defines material quantities and ratios at each level
+- Version Management: Supports BOM version changes and historical traceability
+
+**Function Screenshot**:
+
+
+#### 3.3.2 Add BOM
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Material Model] → [BOM Management]
+2. Click [Add] button
+3. Fill in basic BOM information
+4. Click [Save] to complete BOM creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| BOM Version Code | Unique identification code of the BOM | Yes |
+| BOM Version Name | Name of the BOM, e.g., "Bill of Materials for Product A" | Yes |
+| Product Code | Associated product model | Yes |
+| Status | Status: Enabled, Disabled | Yes |
+| Remarks | Other supplementary information | No |
+
+**[Important]** Once a BOM is referenced by a production work order, it cannot be deleted.
+
+**Function Screenshot**:
+
+
+#### 3.3.3 Set BOM
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Material Model] → [BOM Management]
+2. Select the BOM to set, click [Set BOM] button
+3. Select the corresponding process, configure material information and input quantity in IN/OUT
+
+
+**BOM Item Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| IN/OUT | Material input and output of the process | Yes |
+| Material Category | Referenced material category | Yes |
+| Material Code | Referenced material code | Yes |
+| Material Name | Referenced material name | Yes |
+| Input Quantity | Quantity of this material used to produce one product | Yes |
+| Unit | Unit of measure for material quantity | Yes |
+
+**[Note]** The same material code is not allowed to appear in the same BOM.
+**[Note]** The unit of measure for BOM items should be consistent with the unit of measure in material information.
+
+**Function Screenshot**:
+
+
+#### 3.3.4 BOM Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| BOM Code | Exact query by BOM code |
+| BOM Name | Fuzzy query by BOM name |
+| Product Model | Filter by product model |
+
+
+### 3.4 Unit of Measure Management
+
+#### 3.4.1 Unit of Measure Description
+
+Unit of measure is an attribute of material information, used to standardize the measurement of material quantities. The system predefines common units of measure and supports user-defined units of measure.
+
+**Common Unit of Measure Types:**
+
+- Quantity Units: pieces, items, pieces, sticks, units, sets
+- Weight Units: kilograms, grams, tons, pounds
+- Length Units: meters, centimeters, millimeters, inches
+- Volume Units: liters, milliliters, cubic meters
+- Area Units: square meters, square centimeters
+
+**Function Screenshot**:
+
+
+#### 3.4.2 Add Unit of Measure
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Material Model] → [Unit of Measure]
+2. Click [Add] button
+3. Fill in basic unit of measure information
+4. Click [Save] to complete unit of measure creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Unit Code | Unique identification code of the unit | Yes |
+| Unit Name | Name of the unit, e.g., "pieces", "kilograms" | Yes |
+| Remarks | Other supplementary information | No |
+
+**[Note]** System predefined units of measure cannot be modified or deleted.
+**[Important]** Once a unit of measure is referenced by material information, it cannot be deleted.
+
+**Function Screenshot**:
+
+
+#### 3.4.3 Unit of Measure Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Unit Code | Exact query by unit code |
+| Unit Name | Fuzzy query by unit name |
+| Unit Type | Filter by unit type |
\ No newline at end of file
diff --git a/en/production_configuration/process_model.md b/en/production_configuration/process_model.md
new file mode 100644
index 0000000..9d013f8
--- /dev/null
+++ b/en/production_configuration/process_model.md
@@ -0,0 +1,473 @@
+# Process Flow Model
+
+## 1. Function Overview
+
+The Process Flow Model belongs to the basic module of the MES system. It is used to build core process data such as product process flow classification, process flows, process units, process set values, and process result parameters, providing process basic data support for production execution, quality management, and other business modules.
+
+**Core Functions:**
+
+- Process Flow Category: Maintain the classification system of process flows, classify by production section
+- Process Unit: Maintain a standardized library of process units, which can be reused by multiple process flows to achieve process standardization
+- Process Flow Management: Maintain complete process flows for specific products, define process sequence, process set values, process result parameters, etc.
+
+
+**Function Screenshot**:
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Process Flow Category | Process Category, unit for classifying process flows by section | Used to distinguish process flows of different production sections |
+| Process Flow | Process Flow, defines the complete processing sequence from raw materials to finished products | Also known as process route or production flow |
+| Process Unit | Process Unit, standardized small process module | Can be reused by multiple process flows |
+| Process Set Value | Process Set Value, standard parameters for process operations | Such as temperature, pressure, time, etc., belongs to process unit attributes |
+| Process Result Parameter | Process Result Parameter, actual result records of process operations | Used for process monitoring and quality traceability, belongs to process unit attributes |
+| Device Category | Device Category, unit for classifying device categories | Used to distinguish different types of devices, belongs to process unit attributes |
+| Calculation Script | Process Calculation Script, additional code logic executed by process interfaces | Used for complex calculations in production execution, belongs to process attributes |
+| Channel Exception Record | Channel Exception Record, records detailed information of process channel exceptions | Used for device point early warning, belongs to process attributes |
+
+**Data Model Relationship Description:**
+
+```mermaid
+flowchart TB
+ subgraph Process Flow Category
+ CA[Process Flow Category A]
+ CB[Process Flow Category B]
+ end
+
+ subgraph Process Flow
+ PA1[Process Flow A1]
+ PA2[Process Flow A2]
+ PB1[Process Flow B1]
+ end
+
+ subgraph Process Unit
+ U1[Process Unit 1]
+ U2[Process Unit 2]
+ U3[Process Unit 3]
+ end
+
+ CA -->|1:N| PA1
+ CA -->|1:N| PA2
+ CB -->|1:N| PB1
+
+ PA1 --- U1
+ PA1 --- U2
+ PA2 --- U2
+ PB1 --- U2
+ PB1 --- U3
+
+ U1 -->|Attribute| PSV1[Process Set Value]
+ U1 -->|Attribute| PRP1[Process Result Parameter]
+ U1 -->|Attribute| DC1[Device Category]
+
+ U2 -->|Attribute| PSV2[Process Set Value]
+ U2 -->|Attribute| PRP2[Process Result Parameter]
+ U2 -->|Attribute| DC2[Device Category]
+```
+
+**Relationship Description:**
+
+| Relationship Type | Description |
+|------------------|-------------|
+| Process Flow Category → Process Flow | **1 to N**: A process flow category can contain multiple process flows |
+| Process Flow ↔ Process Unit | **N to M**: A process flow can reference multiple process units, a process unit can be reused by multiple process flows |
+| Process Unit → Process Set Value | **Attribute**: Process set value is one of the attributes of process unit |
+| Process Unit → Process Result Parameter | **Attribute**: Process result parameter is one of the attributes of process unit |
+| Process Unit → Device Category | **Attribute**: Device category is one of the attributes of process unit |
+
+**Simplified Relationship Diagram:**
+
+```mermaid
+flowchart LR
+ A[Process Flow Category] -->|1:N| B[Process Flow]
+ B -.->|N:M| C[Process Unit]
+
+ C -->|Contains| D[Process Set Value]
+ C -->|Contains| E[Process Result Parameter]
+ C -->|Contains| F[Device Category]
+```
+
+
+## 3. Process Flow Model Interaction Flow
+
+### 3.1 Process Flow Category Management
+
+#### 3.1.1 Process Flow Category Description
+
+Process flow category is a unit for classifying process flows by production section, used to distinguish process flows of different production sections.
+
+**Function Screenshot**:
+
+
+#### 3.1.2 Add Process Flow Category
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Process Model] → [Process Flow Category]
+2. Click [Add] button
+3. Fill in basic information
+4. Click [Save] to complete category creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Process Flow Category Code | Unique identification code of the category | Yes |
+| Process Flow Category Name | Name of the category, e.g., "** Section" | Yes |
+| Remarks | Other supplementary information | No |
+
+**[Important]** Once the category code is enabled, it cannot be modified or deleted. Please confirm carefully when creating.
+
+**Function Screenshot**:
+
+
+#### 3.1.3 Process Flow Category Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Category Code | Exact query by category code |
+| Category Name | Fuzzy query by category name |
+
+### 3.2 Process Unit Management
+
+#### 3.2.1 Process Unit Description
+
+A process unit is a standardized small process module, which is the basic unit constituting a process flow. Process units are universal and can be referenced by multiple process flows to achieve standardized reuse of processes.
+
+**Process Unit Characteristics:**
+
+- Standardization: Define unified process names, process codes, and operation specifications
+- Reusability: Can be referenced by multiple process flows without repeated creation
+- Configurability: Supports configuring preset process parameters and preset result parameters for processes
+
+**Function Screenshot**:
+
+
+
+#### 3.2.2 Add Process Unit
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Process Model] → [Process Unit]
+2. Click [Add] button
+3. Fill in basic process unit information
+4. Click [OK] to complete process unit creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Process Unit Code | Unique identification code of the process unit | Yes |
+| Process Unit Name | Name of the process unit, e.g., "SMT Mounting" | Yes |
+| Device Category | Device category for completing this process, e.g., "SMT" | Yes |
+| Remarks | Other supplementary information | No |
+
+**[Note]** Once a process unit is created, the code cannot be modified. Please confirm carefully when creating.
+**[Important]** Once a process unit is referenced by a process flow, it cannot be deleted. Please confirm carefully when creating.
+
+**Function Screenshot**:
+
+
+
+#### 3.2.3 Preset Set Values
+
+Preset set values are preset standard parameters for the process, such as temperature, pressure, time, etc. When adding a process to a process flow, the preset set values will be configured by default.
+
+**Function Screenshot**:
+
+
+
+**Operation Steps:**
+
+1. On the [Process Unit] page, click the process unit that needs to configure set values
+2. Click [Preset Set Values] button to open the preset set values dialog
+3. Fill in the set value parameters
+4. Click [OK] to complete set value configuration
+
+**[Important]** The preset set value dialog varies according to the category of the process unit.
+
+The following are the preset set value dialog types in the MES system:
+
+- Charging/Discharging Related: 
+- Sorting Related: 
+- OCV Related: 
+- Rest Related: 
+- DCIR Related: 
+
+In addition to the above, MES also provides a table-form preset set value dialog for configuring complex set values.
+Others: 
+
+**[Important]** If the site has special requirements and needs to customize the preset set value dialog content, please contact the MES system administrator for development.
+
+#### 3.2.4 Preset Result Parameters
+
+Preset result parameters are preset actual result records for the process, such as voltage, current, time, etc. When adding a process to a process flow, the preset result parameters will be configured by default.
+
+**Function Screenshot**:
+
+
+
+##### 3.2.4.1 Add Result Parameter
+
+**Operation Steps:**
+
+1. On the [Process Unit] page, click the process unit that needs to configure result parameters
+2. Click [Preset Result Parameters] button to open the preset result parameters dialog
+3. Click [Add Row] button to open the add result parameter dialog
+4. Fill in the result parameter information
+5. Click [OK] to complete result parameter configuration
+
+**[Important]** After adding, the system will automatically add three result parameters: START_TIME, FINISH_TIME, and DEVICE_CODE.
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Parameter | Unique identification code of the result parameter | Yes |
+| Name | Name of the result parameter, e.g., "Voltage" | Yes |
+| Type | FLOAT/INT/VARCHAR/TEXT/TIMESTAMP | Yes |
+| Is Unique | Whether the result parameter changes according to the number of steps. For example, the result parameters of capacity grading and formation change according to the number of steps. 10 steps have 10 result parameters; while processes such as second sealing or electrolyte injection have no steps and are unique | Yes |
+| Upload | When uploading result parameters, it is judged according to whether to upload. If yes, it is uploaded to the MES system; otherwise, it is not uploaded | Yes |
+| Remarks | Other supplementary information | No |
+
+**Function Screenshot**:
+
+
+
+##### 3.2.4.2 Import Preset Result Parameters
+Importing preset result parameters is to batch import the result parameters of the process, such as voltage, current, time, etc.
+
+**Operation Steps:**
+
+1. On the [Process Unit] page, click the process unit that needs to configure result parameters
+2. Click [Preset Result Parameters] button to open the preset result parameters dialog
+3. Click [Import] button to open the import result parameters dialog
+4. Click [Select File] to upload the xlsx file containing result parameters
+
+**[Note]** If the imported result parameters have duplicate codes or names with existing result parameters, an error will be reported.
+**[Note]** The xlsx file for import will be provided by MES for download. Users can modify it according to the downloaded file and re-import.
+
+**Function Screenshot**:
+
+
+
+
+#### 3.2.5 Process Unit Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Process Unit Code | Exact query by process unit code |
+| Process Unit Name | Fuzzy query by process unit name |
+| Device Category | Filter by device category |
+
+**Function Screenshot**:
+
+
+### 3.3 Process Flow Management
+
+#### 3.3.1 Process Flow Description
+
+Process flow is core data defining the complete processing sequence of a product from raw materials to finished products, including process arrangement, process name, process code, process set values, process result parameters, etc.
+
+**Function Screenshot**:
+
+
+#### 3.3.2 Add Process Flow
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Process Model] → [Process Flow]
+2. Click [Add] button
+3. Fill in basic process flow information
+4. Click [Save] to complete process flow creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Process Flow Code | Unique identification code of the process flow | Yes |
+| Process Flow Name | Name of the process flow | Yes |
+| Process Flow Category | Associated process flow category | Yes |
+| Product Code | Associated product model | Yes |
+| Remarks | Other supplementary information | No |
+
+**[Important]** Once a process flow is bound to a production batch, it cannot be deleted.
+
+
+**Function Screenshot**:
+
+
+#### 3.3.3 Relationship Between Process Flow, Process Unit, and Process
+
+```mermaid
+flowchart TB
+ A[Process Flow Category] -->|1:N| B[Process Flow A]
+ A -->|1:N| C[Process Flow B]
+
+ B --> D[Process 1]
+ B --> E[Process 2]
+ B --> F[Process 3]
+ C --> G[Process 2]
+ C --> H[Process 4]
+ C --> F
+
+ D --> I[Process Unit: Mounting]
+ E --> J[Process Unit: Welding]
+ F --> K[Process Unit: Testing]
+ G --> I
+ H --> L[Process Unit: Assembly]
+```
+**[Note]** The process code and process name are automatically assigned by the system. The assignment rule is the unique ID of the process flow concatenated with the process unit code. Users do not need to input manually. Users can modify the name as needed, but the code cannot be modified.
+
+
+### 3.4 Set Process (Process Details)
+
+The process details page is used to configure detailed information of the process flow, including adding processes, deleting processes, editing set values, editing result parameters, setting calculation scripts, etc.
+
+**Function Screenshot**:
+
+
+
+#### 3.4.1 Set Process (Process Details) Description
+
+**Operation Steps:**
+1. Go to [Production Configuration] → [Process Model] → [Process Flow]
+2. Click [Set Process] button
+3. Enter the [Process Details] page
+
+**Function Description:**
+- Add Process: Configure process sequence, process unit, whether to enable channel exception recording, etc.
+- Delete Process: Configure process sequence, process unit, whether to enable channel exception recording, etc.
+- Edit Set Values: Configure standard operation parameters for each process, such as temperature, pressure, time, etc.
+- Edit Result Parameters: Configure actual result records for each process, such as voltage, current, time, etc.
+- Set Calculation Script: Configure actual result records for each process, such as voltage, current, time, etc.
+
+
+#### 3.4.2 Add Process
+**Operation Steps:**
+
+1. On the [Process Flow] page, click the [Set Process] button for the process flow to configure, enter the [Process Details] page
+2. Click the add button to open the add process dialog
+3. Select the process unit, the system will automatically generate the process code and process name
+4. Select whether to enable channel exception recording
+5. Click [OK] to complete process configuration
+
+**Process Configuration Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Process Unit | Process selected from the process unit library | Yes |
+| Process Code | Automatically generated process code, format is process flow unique id + process unit code | Yes |
+| Process Name | Automatically generated process name, format is process flow unique id + process unit name | Yes |
+| Enable Channel Exception Recording | Whether to enable channel exception recording for this process | No |
+| Remarks | Other supplementary information | No |
+
+**[Note]** When a process is deleted, the related set values and result parameters will also be deleted. Please proceed with caution.
+**[Important]** Once a process flow is bound to a production batch, processes cannot be deleted.
+
+**Function Screenshot**:
+
+
+#### 3.4.3 Process Set Values
+Process set values are standard parameters for process operations, such as temperature, pressure, time, etc.
+
+**Operation Steps:**
+
+1. On the [Process Details] page, click the process that needs to configure set values
+2. Click [Add Set Value] button to open the add set value dialog
+3. Fill in the set value parameter, unit, minimum value, maximum value, normal value, warning value, alarm value
+4. Click [OK] to complete set value configuration
+
+**[Note]** If the process unit of this process has set preset set values, the system will automatically fill in the preset set values, and users do not need to configure them manually.
+**[Important]** Process set values are obtained by the equipment through MES interfaces [get_battery_process_setting]() and [get_tray_process_setting]().
+
+**Function Screenshot**:
+
+
+#### 3.4.4 Process Result Parameters
+Process result parameters are actual result records of process operations, such as voltage, current, time, etc.
+
+**[Note]** If the process unit of this process has set preset result parameters, the system will automatically fill in the preset result parameters, and users do not need to configure them manually.
+**[Important]** If the result parameters of this process are non-unique, the system will dynamically generate result parameters according to the number of steps in the set values after the set values are determined.
+
+> For example, the result parameters of the capacity grading process are voltage, current, voltage, etc. According to the number of steps, the voltage, current, voltage of the first step, the voltage, current, voltage of the second step, etc., are generated until the last step.
+
+**Function Screenshot**:
+
+
+#### 3.4.5 Calculation Script
+
+Calculation scripts are scripts that trigger complex calculations during equipment interface calls based on the set script trigger position, such as before or after interface execution. Calculation scripts are written in PHP code and used to add specific complex logic to the project based on the interface.
+
+**Function Screenshot**:
+
+
+##### 3.4.5.1 Add Calculation Script
+
+**Operation Steps:**
+1. On the [Process Details] page, click the process that needs to configure the calculation script
+2. Click [Calculation Script] button to open the add calculation script list dialog
+3. Click [Add] button to open the add calculation script dialog
+4. Fill in the basic information of the calculation script, including script name, trigger position, script content
+5. Click [Calculation Script Editor] button to open the calculation script editor dialog
+6. Write PHP code in the calculation script editor
+7. Click [Save] button to save the calculation script
+8. Click [OK] to complete calculation script configuration
+
+**Function Screenshot**:
+
+
+
+**[Note]** The script editor has syntax highlighting, code hints, formatting, and other functions
+**[Note]** The script editor has a preset function library that users can directly drag and drop to use
+**[Important]** The script editor saves calculation data for a certain result parameter, which requires a corresponding parameter in the result parameters, otherwise an error will occur.
+
+##### 3.4.5.2 Calculation Script Usage Case
+**Case 1:**
+For example, to add K value calculation for OCV2, the process from backend setting to execution and export display:
+
+```mermaid
+sequenceDiagram
+ participant 用户 as User
+ participant MES as MES System
+ participant 设备 as Device
+
+ 用户->>MES: 1. Edit calculation script (Set trigger position: End Position)
+ MES->>MES: 2. Save calculation script configuration
+
+ 设备->>MES: 3. Device uploads data (OCV2 data)
+ MES->>MES: 4. Determine if trigger position is "End Position"
+ MES->>MES: 5. Load corresponding calculation script
+ MES->>MES: 6. Execute script logic (Calculate K value)
+ MES->>MES: 7. Save calculation result to result parameter
+ MES->>用户: 8. Return calculation completed result
+```
+
+**Process Description:**
+
+| Step | Executor | Operation | Description |
+|------|----------|-----------|-------------|
+| 1 | User | Edit calculation script | Set trigger position to "End Position" |
+| 2 | MES | Save script configuration | Save script content and trigger position |
+| 3 | Device | Upload data | Device calls interface to upload OCV2 data |
+| 4 | MES | Determine trigger position | Check if trigger position is "End Position" |
+| 5 | MES | Load script | Load corresponding script according to trigger position |
+| 6 | MES | Execute calculation | Run script logic to calculate K value |
+| 7 | MES | Save result | Save calculation result to result parameter |
+| 8 | MES | Return result | Show calculation completed status to user |
+
+
+#### 3.4.6 View Logs
+Logs record the operation logs of the process details page, including operations such as adding, deleting, editing processes, configuring set values, configuring result parameters, configuring calculation scripts, etc.
+
+**Operation Steps:**
+1. On the [Process Details] page, click [View Logs] button
+2. The log dialog pops up, showing all operation logs
+
+**Function Screenshot**:
+
\ No newline at end of file
diff --git a/en/production_configuration/product_model.md b/en/production_configuration/product_model.md
new file mode 100644
index 0000000..17a6603
--- /dev/null
+++ b/en/production_configuration/product_model.md
@@ -0,0 +1,228 @@
+# Product Model Management
+
+## 1. Function Overview
+
+Product Model Management belongs to the basic module of the MES system. It is used to build core data such as product classification, product basic information, and abnormal/defect categories for the enterprise, providing product basic data support for production planning, work order execution, quality management, and other business modules.
+
+**Core Functions:**
+
+- Product List: Maintain basic product information, support product classification management and multi-level product structure
+- Abnormal/Defect Management: Maintain abnormal/defect categories for products, bind device categories for quality anomaly recording during production
+
+
+**Function Screenshot**:
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Product List | Product List, records basic product information and classification | Basic data for production execution and quality management |
+| Abnormal/Defect | Abnormal/Defect, abnormal situations occurring during production | Including NG (Not Good) and ERR (Error) types |
+| Defect Category | Defect Category, classification management of abnormal/defects | Used to distinguish different types of abnormalities |
+| Device Category | Device Category, classification management of devices | Abnormal/defects are bound to device categories for anomaly recording on specific devices |
+| NG | Not Good, non-conforming product | Products judged as non-conforming during production |
+| ERR | Error, error | Error information occurring during system or device operation |
+
+**Data Model Relationship Description:**
+
+```mermaid
+flowchart TB
+ subgraph Product List
+ P1[Product]
+ P2[Product]
+ end
+
+ subgraph Process Flow
+ PF1[Process Flow A]
+ PF2[Process Flow B]
+ end
+
+ subgraph Abnormal/Defect Management
+ D1[NG Defect Category]
+ D2[ERR Error Category]
+ end
+
+ subgraph Device Category
+ DC1[Device Category]
+ DC2[Device Category]
+ end
+
+ P1 -->|1:N| PF1
+ P2 -->|1:N| PF2
+
+ DC1 -->|1:N| D1
+ DC2 -->|1:N| D2
+```
+
+**Relationship Description:**
+
+| Relationship Type | Description |
+|------------------|-------------|
+| Product List → Process Flow | **1 to N**: A product can be configured with multiple process flows |
+| Device Category → Abnormal/Defect Management | **1 to N**: A device category can be configured with multiple abnormal/defect categories |
+
+
+## 3. Product Model Interaction Flow
+
+### 3.1 Product List Management
+
+#### 3.1.1 Product List Description
+
+Product list is core data recording basic product information, including product model, product name, etc. It is the foundation of enterprise production execution and quality management.
+
+**Product List Characteristics:**
+
+- Relevance: Product information can be referenced by process flows
+
+**Function Screenshot**:
+
+
+#### 3.1.2 Add Product
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Product Model] → [Product List]
+2. Click [Add] button
+3. Fill in basic product information
+4. Click [Save] to complete product creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Product Model | Unique identification code of the product | Yes |
+| Product Name | Name of the product | Yes |
+| Remarks | Other supplementary information | No |
+
+**[Important]** The product model cannot be modified after creation. Please confirm carefully when creating.
+**[Important]** Once a product is referenced by a process flow or work order, it cannot be deleted.
+
+**Function Screenshot**:
+
+
+#### 3.1.3 Product Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Product Model | Exact query by product model |
+| Product Name | Fuzzy query by product name |
+| Product Category | Filter by product category |
+
+**Function Screenshot**:
+
+
+### 3.2 Abnormal/Defect Management
+
+#### 3.2.1 Abnormal/Defect Management Description
+
+Abnormal/Defect Management is used to record abnormal situations occurring during production, including two types: NG (Not Good - non-conforming products) and ERR (Error - errors). Abnormal/defect categories are bound to device categories for anomaly recording in specific device processes.
+
+**Abnormal/Defect Types:**
+
+| Type | Description |
+|------|-------------|
+| NG | Not Good, non-conforming product, products judged as non-conforming during production |
+| ERR | Error, system or device runtime errors |
+
+**Function Screenshot**:
+
+
+#### 3.2.2 Add Abnormal/Defect Category
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Product Model] → [Abnormal/Defect Management]
+2. Click [Add] button
+3. Select abnormal type (NG/ERR)
+4. Fill in abnormal/defect category information
+5. Select the bound device category
+6. Click [Save] to complete abnormal/defect category creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Abnormal Category Code | Unique identification code of the abnormal category | Yes |
+| Abnormal Category Name | Name of the abnormal category, e.g., "Short Circuit", "Open Circuit" | Yes |
+| Abnormal Type | NG (Non-conforming) / ERR (Error) | Yes |
+| Device Category | Bound device category for anomaly recording on specific devices | Yes |
+| Remarks | Other supplementary information | No |
+
+**[Important]** The abnormal category code cannot be modified after creation.
+**[Important]** Once an abnormal/defect category is used, it cannot be deleted.
+
+**Function Screenshot**:
+
+
+#### 3.2.3 Abnormal/Defect Category Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Abnormal Category Code | Exact query by abnormal category code |
+| Abnormal Category Name | Fuzzy query by abnormal category name |
+| Abnormal Type | Filter by abnormal type: NG / ERR |
+| Device Category | Filter by bound device category |
+
+**Function Screenshot**:
+
+
+#### 3.2.4 Import Abnormal/Defect Categories
+
+The import function supports batch importing abnormal/defect category data to improve data maintenance efficiency.
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Product Model] → [Abnormal/Defect Management]
+2. Click [Import] button
+3. Download the import template
+4. Fill in abnormal/defect category data according to the template format
+5. Click [Select File] to upload the completed Excel file
+6. Click [Start Import] to execute data import
+7. View the import result report
+
+**Import Template Field Description:**
+
+| Field | Description | Required | Example |
+|-------|-------------|----------|---------|
+| Abnormal Category Code | Unique identification code of the abnormal category | Yes | NG-001 |
+| Abnormal Category Name | Name of the abnormal category | Yes | Short Circuit |
+| Abnormal Type | NG (Non-conforming) / ERR (Error) | Yes | NG |
+| Device Category Code | Bound device category code | Yes | DEV-SMT |
+| Remarks | Other supplementary information | No | - |
+
+**[Note]** Ensure the device category exists before importing.
+**[Tip]** It is recommended to import a small amount of data first for verification, and then perform large-scale import after confirming the format is correct.
+
+**Function Screenshot**:
+
+
+#### 3.2.5 Batch Delete Abnormal/Defect Categories
+
+The batch delete function supports deleting multiple abnormal/defect categories at once to improve data cleaning efficiency.
+
+**Operation Steps:**
+
+1. Go to [Production Configuration] → [Product Model] → [Abnormal/Defect Management]
+2. Check the abnormal/defect categories to delete in the list (multiple selection allowed)
+3. Click [Batch Delete] button
+4. Confirm deletion in the pop-up confirmation dialog
+5. Click [OK] to execute batch deletion
+
+**[Note]** Used abnormal/defect categories cannot be deleted.
+**[Note]** Delete operations cannot be recovered. Please confirm carefully before deleting.
+**[Tip]** It is recommended to query whether the category has been referenced by work orders or anomaly records before deletion.
+
+**Function Screenshot**:
+
+
+### 3.3 Abnormal/Defect Management Description
+
+Abnormal/Defect Management is independent of products and process flows, and only has a binding relationship with device categories. Abnormal/defect categories are used to record abnormal situations occurring in devices during production.
+
+**[Important]** Abnormal/Defect Management is not associated with process flows, but is directly bound to device categories.
+**[Important]** Multiple abnormal/defect categories can be bound to the same device category to achieve unified management of anomaly classification.
\ No newline at end of file
diff --git a/en/quality_control/first_inspection.md b/en/quality_control/first_inspection.md
new file mode 100644
index 0000000..1b34238
--- /dev/null
+++ b/en/quality_control/first_inspection.md
@@ -0,0 +1,207 @@
+# First Article and Circuit Inspection
+
+## 1. Function Overview
+- First Article Inspection belongs to the quality control module of the MES system. It involves inspecting the first or several products/workpieces when equipment starts up or when a process begins, ensuring that equipment and process parameters meet standards before batch production, effectively preventing batch quality issues.
+- Circuit Inspection belongs to the quality control module of the MES system. It involves inspecting the quality of products produced by equipment during operation, ensuring products meet standards and effectively preventing quality issues.
+
+
+**Core Functions:**
+- Inspection Category Management: Define and manage different inspection categories, such as first article inspection, circuit inspection, etc., for classifying and managing inspection records.
+- Inspection Item Management: Define and manage specific indicator items that need to be inspected, such as appearance, dimensions, functionality, performance, etc.
+- Inspection Entry: Inspect product indicators according to inspection standards and record inspection data.
+- Inspection Reports: Generate inspection reports including inspection results, inspection standards, inspection time, etc.
+
+
+**Function Screenshot**:
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Inspection Category | Inspection Category, type of inspection | Such as first article inspection, circuit inspection, etc. |
+| First Article Inspection | FAI, First Article Inspection | Inspect the first product produced to ensure equipment and process parameters meet standards |
+| Circuit Inspection | CI, Circuit Inspection | Inspect product quality during equipment operation | Ensure products meet standards, effectively preventing quality issues |
+| Process Unit | Working subclass, process being inspected | Process name, process unit |
+| Inspection Item | Inspection Item, specific indicator item to be inspected | Such as appearance, dimensions, functionality, performance, etc. |
+| Inspection Tool | Inspection Tool, tool used for inspection | Inspection tool |
+| Judgment Category | Inspection Category, type of inspection | Such as numeric, limit, enum, etc. |
+| Process Requirement | Process Requirements, process requirements for inspection | Process requirements |
+| Judgment Standard | Inspection Standard, judgment standard for inspection items | Inspection Standard, judgment standard for inspection items |
+| Unit | Unit, measurement unit | Material unit for inspection items |
+| Inspection Quantity | Inspection Quantity, number of products to be inspected | Number of products to inspect |
+| Inspection Result | Inspection Result, judgment result of inspection | Pass/Fail |
+| Inspection Standard | Inspection Standard, judgment basis for inspection items | Including standard value, tolerance range, etc. |
+| Production Batch | Production Batch | Production batch |
+| Enum | Enum, enumeration value | Indicates only GOOD/NG judgment without process requirements or upper/lower limits, e.g., appearance inspection NG or GOOD |
+| Numeric | Numeric, numerical value | Indicates process requirements with range requiring upper and lower limit configuration, e.g., greater than 200 and less than 300 |
+| Limit | Limit, limit value | Indicates process requirements with single-sided range, e.g., cannot be less than 200 or cannot be greater than 200 |
+
+## 3. First Inspection and Circuit Inspection Function Interaction
+
+### 3.1 Add/Edit Inspection Category Management
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Inspection Category Management]
+2. Click [Add Inspection Category] button
+3. Fill in basic inspection category information
+4. Click [OK] to complete inspection category creation
+
+**Inspection Category Add/Edit Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Inspection Category Code | Unique identification code for the inspection category | Yes |
+| Inspection Category Name | Inspection category name, e.g., "First Article Inspection" or "Circuit Inspection" | Yes |
+| Creator | Creator name, system defaults to current logged-in user | No |
+| Remarks | Other supplementary information | No |
+
+**[Note]** Batch production can only proceed after first article inspection passes. Please ensure inspection data is accurate.
+**[Important]** Once the inspection category code is bound to inspection items, it cannot be modified. Please confirm carefully when creating.
+**[Important]** Once the inspection category code is bound to inspection items, it cannot be deleted.
+
+**Function Screenshots**:
+
+
+
+### 3.2 First Inspection and Circuit Inspection Item Configuration List
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Process Control] → [First Inspection Item Configuration]
+2. Click [Add First Inspection Item] button
+3. Select process unit
+4. Select inspection category
+5. Click [OK] to complete inspection item creation
+
+**First Inspection Item List Add/Edit Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Process Unit | Process unit being inspected | Yes |
+| Inspection Category | Inspection category | Yes |
+| Remarks | Other supplementary information | No |
+| Required | Whether the process unit needs to upload corresponding inspection parameters for batch closing | No |
+
+**Function Screenshots**:
+
+
+
+
+**Configuration Item Function Operation Steps:**
+1. Go to [Quality Management] → [Process Control] → [First Inspection Item Configuration]
+2. Click [Configure Items] button for the item to configure
+3. Click [Add Item] button and fill in first inspection item information
+4. Fill in item code, item name, process requirements
+5. Select inspection type:
+ 1. Enum: skip
+ 2. Numeric: fill in upper and lower limits separately, e.g., 200, 300
+ 3. Limit:
+ 1. Select judgment standard, e.g., upper limit/lower limit;
+ 2. Fill in value, e.g., 200
+6. Fill in unit, inspection tool, inspection quantity
+7. Click [Submit] to complete first inspection item editing
+
+**First Inspection Item Configuration Function Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Item Code | Unique identification code of the item | Yes |
+| Item Name | Name of the item | Yes |
+| Process Requirement | Process requirements for inspection | Yes |
+| Inspection Type | Type of inspection | Yes |
+| Unit | Material unit for inspection item | Yes |
+| Inspection Tool | Tool used for inspection | Yes |
+| Inspection Quantity | Number of products to inspect | Yes |
+| Inspection Result | Judgment result of inspection | Yes |
+| Judgment Standard | Appears for enum or limit types. For enum, defaults to GOOD:NG; for numeric, need to select upper or lower limit | Yes |
+| Upper Limit | Appears for numeric type, fill in upper limit value, e.g., 200 | Yes |
+| Lower Limit | Appears for numeric type, fill in lower limit value, e.g., 100 | Yes |
+| Value | Appears for limit type, fill in value, e.g., 200 | Yes |
+
+**Function Screenshots**:
+
+
+
+
+
+
+**[Note]** Different fields need to be filled according to different inspection types.
+**[Important]** Once first inspection items are entered, they cannot be modified or deleted, including detail items.
+
+
+### 3.3 First Inspection Entry
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Process Control] → [First Inspection Entry]
+2. Click [First Inspection Entry] button
+3. Select production batch, inspection category, process unit in sequence
+4. Select first inspection items
+5. Fill in first inspection content according to configuration
+6. Select inspection result
+7. Click [OK] to complete first inspection entry.
+
+
+**First Inspection Entry Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Production Batch | Production batch of inspected material | Yes |
+| Inspection Category | Inspection category, e.g., first inspection, circuit inspection | Yes |
+| Process Unit | Process unit being inspected | Yes |
+| First Inspection Item | First inspection items, item names | Yes |
+| Inspection Result | Judgment result of inspection | Yes |
+| Process Requirement | Process requirements set for first inspection items | - |
+| Inspection Type | Type of inspection | - |
+| Unit | Material unit for inspection item | - |
+| Inspector | Inspector, current logged-in user name | - |
+| Inspection Time | Inspection time, data entry time | - |
+
+
+
+**Function Screenshots**:
+
+
+
+
+
+
+
+**Judgment Result Description:**
+Inspection result is selected by user;
+
+**[Important]** If first article inspection fails, batch production is prohibited. Must readjust and perform first article inspection again.
+
+
+## 4. Query Operations
+
+### 4.1 First Inspection Report Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Process Unit | Filter by process unit |
+| Inspection Type | Filter by inspection type |
+
+
+**First Inspection Report List Description:**
+
+| Field | Description |
+|-------|-------------|
+| Production Batch | Production batch of inspected material |
+| Inspection Result | Judgment result of inspection |
+| Item Code | Item code |
+| Item Name | Item name |
+| Inspection Category | Inspection category, e.g., first inspection, circuit inspection |
+| Process Requirement | Process requirements set for first inspection items |
+| Judgment Standard | Judgment standard for inspection items |
+| Unit | Material unit for inspection item |
+| Inspector | Inspector, current logged-in user name |
+| Inspection Time | Inspection time, data entry time |
+
+
+**Function Screenshot**:
+
\ No newline at end of file
diff --git a/en/quality_control/inspection_management.md b/en/quality_control/inspection_management.md
new file mode 100644
index 0000000..d0a2eac
--- /dev/null
+++ b/en/quality_control/inspection_management.md
@@ -0,0 +1,690 @@
+# Inspection Control
+
+## 1. Function Overview
+
+Inspection Control belongs to the quality management module of the MES system, used to manage quality inspection activities throughout the entire process from material receiving to finished product shipment. The system provides a complete functional chain including inspection standard definition, inspection plan configuration, sampling scheme maintenance, inspection order generation and execution, supporting multiple inspection scenarios such as IQC (Incoming Quality Control), IPQC (In-process Quality Control), FQC (Final Quality Control), and OQC (Outgoing Quality Control).
+
+**Core Functions:**
+
+- Inspection Item Management: Define and maintain specific indicator items that need to be inspected, such as appearance, dimensions, characteristics, etc.
+- Inspection Standard Management: Maintain inspection standard codes, names, and AQL sampling letter mapping tables
+- Inspection Plan Management: Configure inspection plan information such as suppliers and inspection categories for different materials
+- Inspection Plan Items: Configure specific inspection items and sampling schemes for inspection plans
+- Sampling Scheme: Define sampling methods and quantity interval rules for different inspection categories
+- AQL Configuration: Configure Acceptance Quality Limit (AQL) standards, associate inspection standards and inspection levels
+- Inspection Order Management: Create, manage, execute, and cancel inspection orders, track the full process status of inspections
+- Inspection Order Details: Enter measured data, make pass/fail judgments, and confirm results for specific inspection orders
+
+**Function Screenshot**:
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Inspection Control | Inspection Control, core quality management module | Covers end-to-end management of inspection items, standards, plans, sampling schemes, inspection orders, etc. |
+| Inspection Item | Inspection Item, specific indicator item to be inspected | Such as appearance count, characteristic count, dimension measurement, characteristic measurement, etc. |
+| Inspection Item Attribute | Inspection Item Attribute, classification attribute of inspection items | Four types: appearance count, characteristic count, dimension measurement, characteristic measurement |
+| Inspection Standard | Inspection Standard, judgment basis for inspection items | Includes standard code, name, national standard status, and AQL sampling letter mapping |
+| Inspection Plan | Inspection Plan, inspection scheme for materials | Defines inspection category, supplier, and other inspection plan information for materials |
+| Inspection Plan Item | Inspection Plan Item, specific item in inspection plan | Associates inspection items, sampling schemes, inspection levels, etc. |
+| Sampling Plan | Sampling Plan, sampling rules for quality inspection | Includes sampling method (fixed quantity/fixed ratio), inspection type, and quantity intervals |
+| Sampling Method | Sampling Method | Fixed quantity sampling or fixed ratio sampling |
+| Sampling Interval | Sampling Interval | Sampling quantity determined based on inspection quantity range |
+| AQL | Acceptance Quality Limit | Allowable worst process average quality level during inspection |
+| Inspection Mode | Inspection Mode, strictness level of inspection | Such as S1, S2, S3, S4, I, II, III, etc. |
+| IQC | Incoming Quality Control | Quality inspection of purchased materials before storage |
+| IPQC | In-process Quality Control | Quality inspection of semi-finished products during production |
+| FQC | Final Quality Control | Quality inspection of finished products after production |
+| OQC | Outgoing Quality Control | Quality inspection of products before shipment |
+| Inspection Order | Inspection Order, execution document for quality inspection | Includes inspection order number, material batch, inspection quantity, inspection status, etc. |
+| Inspection Order No | Inspection Order No | Format: QMS-YYYYMMDD-Sequence, e.g., QMS-20260101-01 |
+| Small Sample Inspection | Small Sample Inspection | Quickly create inspection orders through small sample inspection |
+| Exempt from Inspection | Exempt from Inspection | Materials marked as exempt from inspection |
+| Inspection Result | Inspection Result | Pass or Fail |
+| Modify Result | Modify Result | Manually modified inspection judgment result |
+| Quality Handle Result | Quality Handle Result | Quality department's handling opinion on inspection results |
+| Sampling Level | Sampling Level | Strictness level of inspection: normal, tightened, reduced |
+| Measured Value | Measured Value | Actual measured value of inspection item |
+| Defect Quantity | Defect Quantity | Number of defective products found during inspection |
+| Single Item Pass Rate | Single Item Pass Rate | Pass rate of a single inspection item = pass count / total inspection count |
+| Loss Quantity | Loss Quantity | Number of products lost during inspection |
+
+## 3. Data Model Relationship Description
+
+```mermaid
+flowchart TB
+ subgraph Basic Configuration
+ IS[Inspection Standard]
+ II[Inspection Item]
+ SM[Sampling Scheme]
+ end
+
+ subgraph AQL Configuration
+ AC[AQL Configuration]
+ AS[AQL Sample Size]
+ end
+
+ subgraph Inspection Plan
+ IP[Inspection Plan]
+ IPI[Inspection Plan Item]
+ end
+
+ subgraph Inspection Execution
+ IOM[Inspection Order Management]
+ IOD[Inspection Order Details]
+ IODT[Inspection Order Detail Table]
+ end
+
+ IP -->|1:N| IPI
+ IPI -->|Reference| II
+ IPI -->|Reference| SM
+ AC -->|Reference| IS
+ AC -->|Reference| AS
+ IP -->|Generate| IOM
+ IOM -->|1:1| IOD
+ IOD -->|Contain| IODT
+ IODT -->|Reference| IPI
+```
+
+**Relationship Description:**
+
+| Relationship Type | Description |
+|------------------|-------------|
+| Inspection Plan → Inspection Plan Item | **1 to N**: One inspection plan contains multiple inspection plan items |
+| Inspection Plan Item → Inspection Item | **Reference**: Inspection plan items reference inspection item configurations |
+| Inspection Plan Item → Sampling Scheme | **Reference**: Inspection plan items reference sampling schemes |
+| AQL Configuration → Inspection Standard | **Reference**: AQL configuration associates inspection standards |
+| AQL Configuration → AQL Sample Size | **Reference**: AQL configuration associates sample size rules |
+| Inspection Plan → Inspection Order | **Generate**: Generate inspection orders for material batches based on inspection plans |
+| Inspection Order → Inspection Order Details | **1 to 1**: One inspection order corresponds to one inspection detail page |
+| Inspection Order Details → Inspection Order Detail Table | **Contain**: Inspection order details contain detail data for each inspection item |
+
+## 4. Inspection Control Interaction Flow
+
+### 4.1 Inspection Item Management
+
+#### 4.1.1 Inspection Item Description
+
+Inspection items are specific indicators that need to be inspected in quality management. The system classifies inspection items into four categories by attribute: appearance count, characteristic count, dimension measurement, and characteristic measurement. Each inspection item needs to define code, name, attribute, inspection standard, unit, inspection tool, inspection method, etc.
+
+Inspection items are the basic data for inspection plan items and inspection order details. After being referenced by inspection plan items, corresponding inspection item information is displayed during inspection execution.
+
+**Function Screenshot**:
+
+
+#### 4.1.2 Add Inspection Item
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Inspection Control] → [Inspection Item]
+2. Click [Add] button
+3. Fill in basic inspection item information
+4. Click [Save] to complete inspection item creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Inspection Item Code | Unique identification code of inspection item | Yes |
+| Inspection Item Name | Name of inspection item | Yes |
+| Inspection Item Attribute | Classification attribute of inspection item: appearance count, characteristic count, dimension measurement, characteristic measurement | Yes |
+| Inspection Category | Inspection category, such as IQC, FQC, OQC, etc. | Yes |
+| Inspection Standard | Associated inspection standard for AQL sampling judgment | Yes |
+| Unit | Measurement unit of inspection item, such as mm, mΩ, %, ℃, etc. | Yes |
+| Inspection Tool | Tool or equipment used for inspection | No |
+| Inspection Method | Specific method description for inspection | No |
+| Process Requirement | Process standard requirements for inspection | No |
+| Remarks | Other supplementary information | No |
+
+**[Important]** Once an inspection item is referenced by an inspection plan item, it cannot be deleted.
+**[Note]** The inspection item code cannot be modified after creation. Please confirm carefully when creating.
+
+**Function Screenshots**:
+
+
+
+### 4.2 Inspection Standard Management
+
+#### 4.2.1 Inspection Standard Description
+
+Inspection standards are the judgment basis for quality inspection, defining the mapping relationship between AQL sampling letters and batch ranges. Each inspection standard contains a sampling mapping table (Mapping), which defines the AQL sampling letters (S1, S2, S3, S4, I, II, III) corresponding to different batch ranges, used to find the corresponding sample quantity in the AQL sample size table.
+
+**Function Screenshot**:
+
+
+#### 4.2.2 Add Inspection Standard
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Inspection Control] → [Inspection Standard]
+2. Click [Add] button
+3. Fill in inspection standard code and name
+4. Select whether it is a national standard
+5. Click [Save] to complete inspection standard creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Inspection Standard Code | Unique identification code of inspection standard | Yes |
+| Inspection Standard Name | Name of inspection standard | Yes |
+| Is National Standard | Whether it is a national standard, such as GB/T 2828.1 | Yes |
+| Remarks | Other supplementary information | No |
+
+**[Important]** Once an inspection standard is referenced by AQL configuration, it cannot be deleted.
+
+**Function Screenshots**:
+
+
+
+#### 4.2.3 View Inspection Standard Mapping Table
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Inspection Control] → [Inspection Standard]
+2. Click [View] button for the inspection standard to view
+3. Inspection standard mapping table page pops up
+
+**Mapping Table Description:**
+
+The mapping table shows the AQL sampling letters (i.e., sample size codes) corresponding to different batch ranges. This mapping table follows GB/T 2828.1 standard and automatically matches the corresponding sampling letter based on the batch range.
+
+| Mapping Table Field | Description |
+|---------------------|-------------|
+| Batch Range Start | Lower limit of inspection batch |
+| Batch Range End | Upper limit of inspection batch |
+| S1 ~ S4 | Sample size codes for special inspection levels |
+| I ~ III | Sample size codes for general inspection levels |
+
+**Function Screenshots**:
+
+
+
+### 4.3 Inspection Plan Management
+
+#### 4.3.1 Inspection Plan Description
+
+Inspection plan is the inspection scheme configured for each material, defining basic inspection information for materials, including inspection category, supplier, etc. Inspection plan is the bridge connecting materials and inspection execution. When applying for inspection, the system automatically matches corresponding inspection items and sampling rules based on the inspection plan.
+
+**Function Screenshot**:
+
+
+#### 4.3.2 Add Inspection Plan
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Inspection Control] → [Inspection Plan]
+2. Click [Add] button
+3. Select material code (system automatically brings out material name and unit)
+4. Select supplier
+5. Select material inspection category (IQC/FQC/OQC, etc.)
+6. Click [Save] to complete inspection plan creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Material Code | Select material to inspect | Yes |
+| Material Name | Automatically brought out by selected material | Auto |
+| Unit | Automatically brought out by selected material | Auto |
+| Supplier | Material supplier | Yes |
+| Material Inspection Category | Inspection category, such as IQC, FQC, OQC, in-stock inspection, line-side inspection, etc. | Yes |
+| Remarks | Other supplementary information | No |
+
+**[Important]** Once an inspection plan is referenced by an inspection order, it cannot be deleted.
+**[Note]** Inspection plan items (inspection items) need to be configured before inspection can be executed normally.
+
+**Function Screenshots**:
+
+
+
+#### 4.3.3 View Inspection Scheme
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Inspection Control] → [Inspection Plan]
+2. Click [View Scheme] button for the corresponding row
+3. Enter inspection plan items page to view inspection item configuration under this plan
+
+### 4.4 Inspection Plan Item Management
+
+#### 4.4.1 Inspection Plan Item Description
+
+Inspection plan items are specific inspection entries of inspection plans, defining which items need to be inspected under this plan, what sampling scheme to use, what inspection level to adopt, etc. Each inspection plan can configure multiple inspection plan items, and each inspection plan item corresponds to one inspection item.
+
+**Function Screenshot**:
+
+
+#### 4.4.2 Add Inspection Plan Item
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Inspection Control] → [Inspection Plan]
+2. Click [View Scheme] button for the corresponding row to enter inspection plan items page
+3. Click [Add] button
+4. Select inspection item
+5. Select sampling scheme
+6. Select inspection level (normal/tightened/reduced)
+7. Fill in parameters such as AC (acceptance number) and RE (rejection number)
+8. Click [Save] to complete inspection plan item creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Inspection Item | Select from inspection item library, system automatically brings out item code, name and standard | Yes |
+| Sampling Scheme | Select from sampling scheme library, system automatically matches sampling quantity based on inspection quantity | Yes |
+| Inspection Level | Strictness level of inspection: normal/tightened/reduced | Yes |
+| AC (Acceptance Number) | Accept, maximum number of non-conforming units allowed | Yes |
+| RE (Rejection Number) | Reject, minimum number of non-conforming units at which judgment is non-conforming | Yes |
+| Lower Limit | Lower specification limit of inspection item (for measurement-type items) | Conditional |
+| Standard Value | Standard specification value of inspection item | Conditional |
+| Upper Limit | Upper specification limit of inspection item (for measurement-type items) | Conditional |
+| Planned Sampling Quantity | Automatically calculated based on sampling scheme and inspection quantity | Auto |
+| Remarks | Other supplementary information | No |
+
+**[Important]** After inspection plan items are configured, corresponding inspection details will be generated according to this configuration during inspection order execution.
+
+**Function Screenshots**:
+
+
+
+
+### 4.5 Sampling Scheme Management
+
+#### 4.5.1 Sampling Scheme Description
+
+Sampling scheme defines sampling methods and corresponding quantity interval rules for different inspection types. Each sampling scheme includes scheme code, scheme name, sampling method (fixed quantity or fixed ratio), inspection type (IQC/FQC/OQC), and sampling interval details.
+
+Sampling interval details are a key configuration that defines rules for matching corresponding sampling quantities based on inspection quantity ranges. For example: 2~8 inspection quantity samples 2 items, 9~15 samples 3 items, etc.
+
+**Function Screenshot**:
+
+
+#### 4.5.2 Add Sampling Scheme
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Inspection Control] → [Sampling Scheme]
+2. Click [Add] button
+3. Fill in scheme code and scheme name
+4. Select sampling method (fixed quantity or fixed ratio)
+5. Select inspection type (IQC/FQC/OQC)
+6. Click [Edit] button (edit icon) for the corresponding row to pop up sampling interval configuration dialog
+7. Configure sampling interval details: set quantity upper and lower limits and sample quantity
+8. Click [Save] in the dialog to complete interval configuration
+9. Check the row and click [Save] to save the scheme to the database
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Scheme Code | Unique identification code of sampling scheme | Yes |
+| Scheme Name | Name of sampling scheme | Yes |
+| Sampling Method | Fixed quantity or fixed ratio | Yes |
+| Inspection Type | Inspection category, such as IQC, FQC, OQC | Yes |
+| Remarks | Other supplementary information | No |
+
+**Sampling Interval Detail Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Lower Limit | Lower limit of inspection quantity interval | Yes |
+| Upper Limit | Upper limit of inspection quantity interval | Yes |
+| Normal Sample Quantity | Sampling quantity under normal inspection level | Yes |
+| Tightened Sample Quantity | Sampling quantity under tightened inspection level | No |
+| Reduced Sample Quantity | Sampling quantity under reduced inspection level | No |
+
+**[Important]** Once a sampling scheme is referenced by an inspection plan item, it cannot be deleted.
+
+**Function Screenshots**:
+
+
+
+### 4.6 AQL Configuration Management
+
+#### 4.6.1 AQL Configuration Description
+
+AQL (Acceptance Quality Limit) configuration defines the acceptable quality level for quality inspection. AQL configuration associates inspection standards and inspection levels, used to determine sampling quantity and acceptance/rejection criteria during inspection based on batch range and AQL value.
+
+**Function Screenshot**:
+
+
+#### 4.6.2 Add AQL Configuration
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Inspection Control] → [AQL Configuration]
+2. Click [Add] button
+3. Fill in acceptance quality limit code and name
+4. Select status (enabled/disabled)
+5. Select inspection level
+6. Select inspection standard
+7. Click [Save] to complete AQL configuration creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Acceptance Quality Limit Code | Unique identification code of AQL configuration | Yes |
+| Acceptance Quality Limit Name | Name of AQL configuration | Yes |
+| Status | Enabled or disabled | Yes |
+| Inspection Level | Inspection level | Yes |
+| Inspection Standard | Associated inspection standard (includes AQL sampling letter mapping table) | Yes |
+| Remarks | Other supplementary information | No |
+
+**Function Screenshots**:
+
+
+
+#### 4.6.3 View AQL Sample Size
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Inspection Control] → [AQL Configuration]
+2. Click [Edit] or [View] button for the corresponding row
+3. Enter AQL sample size page to view the AQL sample size rule table under this configuration
+
+The AQL sample size rule table defines the sample quantities and acceptance/rejection criteria corresponding to different AQL sampling letters (found from inspection standard mapping table based on batch range) crossed with different AQL values.
+
+**[Important]** Once an AQL configuration is referenced by an inspection plan item, it cannot be deleted.
+
+**Function Screenshots**:
+
+
+
+
+### 4.7 Inspection Order Management
+
+#### 4.7.1 Inspection Order Description
+
+Inspection order is the execution document for quality inspection. When materials need inspection, create inspection orders through small sample inspection function, and the system automatically generates inspection order numbers (format: QMS-YYYYMMDD-Sequence, e.g., QMS-20260101-01). Inspection orders record complete information such as material batch, inspection quantity, inspector, inspection result, etc.
+
+Inspection order status is divided into four types:
+- **PENDING**: Inspection order created, waiting for inspector to execute inspection
+- **UNCONFIRMED**: Inspection completed, waiting for result confirmation
+- **CONFIRMED**: Inspection result confirmed
+- **CLOSED**: Inspection order closed
+
+**Function Screenshot**:
+
+
+#### 4.7.2 Add Inspection Order (Small Sample Inspection)
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Inspection Control] → [Inspection Order Management]
+2. Click [Add Small Sample Inspection] button
+3. Fill in inspection information in the pop-up dialog
+4. Select material code
+5. Fill in material batch and inspection quantity
+6. Select whether it is IQC small sample
+7. Select whether it is exempt from inspection
+8. Click [OK] to complete inspection order creation
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Inspection Order Number | Automatically generated by system, format QMS-YYYYMMDD-Sequence | Auto |
+| Material Code | Select from inspection plan, system automatically brings out material name and inspection category | Yes |
+| Material Batch | Batch number of material being inspected | Yes |
+| Inspection Quantity | Number of products to inspect | Yes |
+| Applicant | Current logged-in user, system defaults | Auto |
+| Is IQC Small Sample | Whether it is incoming small sample inspection | No |
+| Is Exempt from Inspection | Whether the material is exempt from inspection | No |
+
+**[Note]** Material code must exist in inspection plan, otherwise inspection order cannot be created.
+
+**Function Screenshot**:
+
+
+#### 4.7.3 Execute Inspection
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Inspection Control] → [Inspection Order Management]
+2. Find inspection orders with status "PENDING" or "UNCONFIRMED"
+3. Click [Inspect] button for the corresponding row
+4. Enter inspection order details page to input inspection data and make pass/fail judgment
+
+
+**Function Screenshots**:
+
+
+
+#### 4.7.4 Modify Inspection Order
+
+Only inspection orders with "PENDING" status can be modified. When modifying, the small sample inspection dialog pops up, and material code, material batch, inspection quantity, etc. can be modified.
+
+#### 4.7.5 Cancel Inspection Order
+
+Only inspection orders with "PENDING" status can be canceled.
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [Inspection Control] → [Inspection Order Management]
+2. Find inspection orders with status "PENDING"
+3. Click [Cancel] button for the corresponding row
+4. Confirm cancellation
+
+**[Important]** Cancellation cannot be undone. Please proceed with caution.
+
+#### 4.7.6 Inspection Order Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Inspection Order Number | Exact query by inspection order number |
+| Material Batch | Fuzzy query by material batch |
+| Customer/Supplier | Query by customer or supplier name |
+| Material Inspection Category | Filter by inspection category, such as IQC, IQC_SPECIAL, IPQC, OQC |
+| Inspection Order Status | Filter by status: pending, unconfirmed, confirmed, closed |
+| Inspector | Query by inspector name |
+| Sample Expiry Date (Start) | Filter by sample inspection expiry date start |
+| Sample Expiry Date (End) | Filter by sample inspection expiry date end |
+| Modifier | Query by modifier name |
+| Modification Date (Start) | Filter by modification date start |
+| Modification Date (End) | Filter by modification date end |
+
+**Inspection Order List Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Inspection Order Number | Unique number of inspection order, format QMS-YYYYMMDD-Sequence |
+| Material Batch | Batch number of material being inspected |
+| Supplier Batch | Supplier's batch number |
+| Material Code | Material code |
+| Material Name | Material name |
+| Customer/Supplier | Associated supplier name |
+| Material Inspection Category | Inspection category, such as IQC, FQC, OQC, etc. |
+| IQC Small Sample | Whether it is IQC small sample inspection |
+| Is Exempt from Inspection | Whether the material is exempt from inspection |
+| Inspection Quantity | Number of products being inspected |
+| Inspection Unit | Measurement unit for inspection |
+| Application Date | Inspection application date |
+| Applicant | Inspection applicant name |
+| Inspection Order Status | Pending/Unconfirmed/Confirmed/Closed |
+| Inspection Date | Inspection execution date |
+| Inspector | Inspector name |
+| Inspection Result | Inspection judgment result |
+| Sample Inspection Expiry Date | Expiry date for sample inspection |
+| Loss Quantity | Number of products lost during inspection |
+| Modified Result | Manually modified inspection result |
+| Quality Handle Result | Quality department's handling opinion |
+| Modifier | Last modifier name |
+| Modification Time | Last modification datetime |
+| Merged Inspection Order | Associated inspection order number when merging batch inspections |
+| Remarks | Other supplementary information |
+| Inspection Validity | Expiry date for inspection result |
+
+### 4.8 Inspection Order Details (Inspection Execution)
+
+#### 4.8.1 Inspection Order Details Description
+
+The inspection order details page is the core working interface for inspectors to execute inspections. The top of the page displays basic information of the inspection order (material batch, material name, customer/supplier, inspection quantity), the middle provides inspection result judgment buttons (Pass/Fail/Auto Judgment), and the bottom organizes and displays inspection item details of different attributes in four tabs.
+
+The four tabs are:
+- **Appearance Count**: Appearance inspection items, inspected by counting method
+- **Characteristic Count**: Characteristic inspection items, inspected by counting method
+- **Dimension Measurement**: Dimension inspection items, enter measured values for judgment
+- **Characteristic Measurement**: Characteristic inspection items, enter measured values for judgment
+
+**Function Screenshot**:
+
+
+#### 4.8.2 Inspection Information Entry
+
+**Header Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Material Batch | Batch number of material being inspected (read-only) | - |
+| Material Name | Material name (read-only) | - |
+| Customer/Supplier | Supplier name (read-only) | - |
+| Inspection Quantity | Inspection quantity (read-only) | - |
+| Inspector | Inspector, select from dropdown list | Yes |
+| Loss Quantity | Number of products lost during inspection | Yes |
+| Inspection Result | Final judgment result of inspection (read-only, set by auto judgment or pass/fail buttons) | - |
+| Modified Result | Manually modified judgment result, optional pass/fail | No |
+| Remarks | Other supplementary information | No |
+
+#### 4.8.3 Counting Inspection (Appearance Count/Characteristic Count)
+
+Table column description for counting inspection tabs:
+
+| Column Name | Description |
+|-------------|-------------|
+| Inspection Item Name | Name of inspection item |
+| Inspection Standard | Standard for inspection item |
+| Planned Sampling Quantity | Planned sampling quantity calculated based on sampling scheme |
+| Actual Sampling Quantity | Actual number of products inspected |
+| Standard Value | Standard specification value for inspection |
+| Defect Quantity | Number of non-conforming products found during inspection |
+| Single Item Pass Rate | Pass rate of single inspection item = (actual sampling quantity - defect quantity) / actual sampling quantity × 100% |
+| Single Item Result | Judgment result of single inspection item (pass/fail) |
+| Unit | Measurement unit of inspection item |
+| Measured Details | Click to view measured data details for this inspection item |
+| Remarks | Other supplementary information |
+
+#### 4.8.4 Measurement Inspection (Dimension Measurement/Characteristic Measurement)
+
+Table column description for measurement inspection tabs:
+
+| Column Name | Description |
+|-------------|-------------|
+| Inspection Item Name | Name of inspection item |
+| Inspection Standard | Standard for inspection item |
+| Planned Sampling Quantity | Planned sampling quantity calculated based on sampling scheme |
+| Actual Sampling Quantity | Actual number of products measured |
+| Lower Limit | Lower specification limit of inspection item |
+| Standard Value | Standard specification value of inspection item |
+| Upper Limit | Upper specification limit of inspection item |
+| Measured Value | Click to view measured data detail list |
+| Defect Quantity | Number of non-conforming products found during inspection |
+| Single Item Pass Rate | Pass rate of single inspection item = (actual sampling quantity - defect quantity) / actual sampling quantity × 100% |
+| Single Item Result | Judgment result of single inspection item (pass/fail) |
+| Unit | Measurement unit of inspection item |
+| Measured Details | Click to enter measured data for this inspection item |
+| Remarks | Other supplementary information |
+
+**Measured Details Dialog Description:**
+
+Click [Measured Details] button to pop up measured data entry dialog. In the dialog, enter measured values for each inspection object one by one and judge pass/fail for each.
+
+| Field | Description |
+|-------|-------------|
+| Inspection Object Code | Barcode or identification code of inspected product |
+| Measured Value | Actual measured value |
+| Is Pass | Judge whether this record passes |
+
+**Function Screenshot**:
+
+
+#### 4.8.5 Inspection Result Judgment
+
+**Operation Steps:**
+
+1. Enter inspection order details page
+2. Complete measured data entry for each inspection item
+3. Use one of the following three methods for result judgment:
+
+**Method 1: Pass Judgment**
+- Click [Pass] button
+- System automatically sets modified result to "Pass"
+
+**Method 2: Fail Judgment**
+- Click [Fail] button
+- System automatically sets modified result to "Fail"
+
+**Method 3: Auto Judgment**
+- Click [Auto Judgment] button
+- System first checks whether actual sampling quantity of each inspection item meets planned sampling quantity requirement
+ - If not met, system prompts "Some inspection items have not reached the specified sampling quantity"
+- If sampling quantity of all inspection items meets requirements, system automatically summarizes defect quantities
+ - No defects: judge as "Pass"
+ - Has defects: judge as "Fail"
+- System automatically saves inspection result
+
+**[Important]** Before auto judgment, ensure actual sampling quantity of all inspection items has reached planned sampling quantity, otherwise auto judgment cannot be performed.
+**[Note]** Once inspection result is saved, it will affect subsequent processes such as material storage/shipment.
+
+## 5. Query Operations
+
+### 5.1 Inspection Item Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Inspection Item Code | Exact query by code |
+| Inspection Item Name | Fuzzy query by name |
+| Inspection Item Attribute | Filter by attribute: appearance count/characteristic count/dimension measurement/characteristic measurement |
+| Inspection Category | Filter by inspection category |
+
+### 5.2 Inspection Standard Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Inspection Standard Code | Exact query by code |
+| Inspection Standard Name | Fuzzy query by name |
+
+### 5.3 Inspection Plan Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Material Code/Name | Query by material information |
+| Inspection Category | Filter by inspection category |
+
+### 5.4 Sampling Scheme Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Scheme Code | Exact query by scheme code |
+| Scheme Name | Fuzzy query by scheme name |
+
+### 5.5 AQL Configuration Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Acceptance Quality Limit Code | Exact query by code |
+| Acceptance Quality Limit Name | Fuzzy query by name |
+
+## 6. Operation Notes
+
+1. **Data Reference Relationship**: Inspection Standard → AQL Configuration → Inspection Plan Item → Inspection Order. Upper-level data cannot be deleted once referenced by lower-level data. Please confirm carefully when creating.
+2. **Inspection Order Number Rule**: Inspection order number format is QMS-YYYYMMDD-NN, automatically generated by system and incremented daily.
+3. **Sampling Quantity Calculation**: Planned sampling quantity is automatically calculated based on inspection quantity of inspection order and sampling scheme associated in inspection plan item, matching corresponding sample quantity with reference to inspection level (normal/tightened/reduced).
+4. **Auto Judgment Condition**: Auto judgment requires actual sampling quantity of all inspection items to reach planned sampling quantity, otherwise user will be prompted.
+5. **Exempt from Inspection Materials**: Materials marked as exempt from inspection will skip the inspection process and be directly regarded as pass.
+6. **Inspection Result Impact**: Inspection results directly affect subsequent flow of material batches (storage/return/production, etc.). Please ensure inspection data accuracy.
\ No newline at end of file
diff --git a/en/quality_control/spc.md b/en/quality_control/spc.md
new file mode 100644
index 0000000..d488525
--- /dev/null
+++ b/en/quality_control/spc.md
@@ -0,0 +1,185 @@
+# SPC Render Condition Configuration
+
+## 1. Function Overview
+
+SPC (Statistical Process Control) render condition configuration belongs to the quality management module of the MES system. It is used to configure data sources, subgroup sampling parameters, and control limits for SPC reports (both variable and attribute charts). Based on the configured SPC render conditions, the system automatically extracts samples from production process data and generates various SPC control charts to help quality managers monitor process stability in real-time.
+
+**Core Functions:**
+
+- Data Source Configuration: Select data category (process inspection data, process data, result data) and associate SCADA point binding configuration
+- Subgroup Sampling Parameters: Configure total subgroups, samples per subgroup, subgroup interval, data cleaning rules
+- Control Limits Configuration: Set specification limits (USL/LSL), control limits calculation method, control chart type
+- Data Cleaning Rules: Configure outlier filtering rules (by value or by percentage)
+
+**Function Screenshot**:
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| SPC | Statistical Process Control | A quality management method using statistical techniques to monitor and control process variation |
+| Control Chart | Control Chart | A statistical chart with control limits used to distinguish between normal and abnormal process variations |
+| Subgroup | Subgroup | A group of sample measurements collected under similar conditions, used to calculate within-group statistics |
+| UCL | Upper Control Limit | Upper limit in control chart, calculated from process data statistics |
+| LCL | Lower Control Limit | Lower limit in control chart, calculated from process data statistics |
+| USL | Upper Specification Limit | Maximum allowable value for product quality characteristic, defined by product specification or customer requirements |
+| LSL | Lower Specification Limit | Minimum allowable value for product quality characteristic, defined by product specification or customer requirements |
+| XBar | Mean | Arithmetic mean of all sample measurements within a subgroup, reflecting process central tendency |
+| R (Range) | Range | Difference between maximum and minimum values within a subgroup, reflecting within-group dispersion |
+| S (Standard Deviation) | Standard Deviation | Standard deviation of sample measurements within a subgroup, reflecting within-group dispersion |
+| MR (Moving Range) | Moving Range | Absolute difference between two consecutive individual measurements |
+| CPK | Process Capability Index | Measures actual process capability under controlled conditions, considering mean shift |
+| CP | Process Capability | Measures potential process capability (without considering mean shift) |
+| Process Inspection Data | Process Inspection Data | Inspection data collected during first article and circuit inspections on the production line |
+| Process Data | Process Data | Production process parameters automatically uploaded by equipment |
+| Result Data | Result Data | Inspection result data after process completion |
+| SCADA Point Binding | SCADA Point Binding | Binding relationship between data nodes and SCADA collection points |
+| Data Cleaning | Data Cleaning | Filtering and removing outlier data that does not conform to normal distribution |
+| Sampling Interval | Sampling Interval | Time interval between consecutive subgroups (in hours) |
+
+## 3. SPC Render Condition Configuration Interaction
+
+### 3.1 Add SPC Render Condition
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [SPC Statistical Process Control] → [SPC Render Condition Configuration]
+2. Click [Add] button
+3. Fill in basic configuration information
+4. Click [Save] to complete SPC render condition creation
+
+**Basic Configuration Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Process Unit | Select the production process unit to be monitored | Yes |
+| Process Unit Name | Automatically displayed based on selected process unit | Auto |
+| Item Code | Unique identifier for SPC monitoring item | Yes |
+| Item Name | Name of SPC monitoring item | Yes |
+| Status | Enabled/disabled status of the configuration | Yes |
+| Data Category | Type of data source: Process Inspection Data, Process Data, Result Data | Yes |
+
+**[Note]** The process unit must be configured in the system before creating SPC render conditions.
+
+**Function Screenshots**:
+
+
+
+### 3.2 Data Source Configuration
+
+Data source configuration defines where the SPC report obtains data from. According to the selected data category, the system provides different configuration options.
+
+**Data Category Description:**
+
+| Data Category | Description | Example |
+|---------------|-------------|---------|
+| Process Inspection Data | Inspection data collected during first article and circuit inspections | Voltage and dimension values measured by inspectors |
+| Process Data | Real-time production parameters automatically uploaded by equipment | Temperature, pressure, speed collected by equipment |
+| Result Data | Test result data after process completion | OCV test voltage, internal resistance, capacity values |
+
+**Data Source Configuration Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Data Category | Select data source type | Yes |
+| SCADA Point Binding | Select bound SCADA data point (only for Process Data category) | Conditional |
+| Data Type Mapping | Map collected data type to SPC analysis data type | Yes |
+
+**Function Screenshots**:
+
+
+### 3.3 Subgroup Sampling Parameters Configuration
+
+Subgroup sampling parameters define how the system collects and groups data for SPC analysis.
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Total Subgroups | Total number of subgroups to collect in a single SPC analysis | Yes |
+| Samples Per Subgroup | Number of sample measurements in each subgroup | Yes |
+| Subgroup Interval | Time interval between consecutive subgroups (in hours) | Yes |
+| Sampling Method | Sampling method: Continuous sampling | Yes |
+
+**[Important]** The product of total subgroups and subgroup interval determines the total time range for SPC analysis data collection.
+
+**Function Screenshot**:
+
+
+### 3.4 Control Limits Configuration
+
+Control limits configuration defines the specification limits and control limit calculation method for SPC control charts.
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| USL (Upper Specification Limit) | Upper specification limit defined by product specification | Conditional |
+| LSL (Lower Specification Limit) | Lower specification limit defined by product specification | Conditional |
+| Target Value | Target value for process quality characteristic | No |
+| Control Limit Calculation | Method for calculating control limits: 3σ method, etc. | Yes |
+| Control Chart Type | Type of control chart to generate: XBar-R, XBar-S, I-MR, etc. | Yes |
+
+**[Note]** If USL/LSL are not configured, CPK-related indicators cannot be calculated in CPK analysis.
+
+**Function Screenshots**:
+
+
+
+### 3.5 Data Cleaning Rules Configuration
+
+Data cleaning rules are used to filter outlier data that may affect SPC analysis results.
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Enable Data Cleaning | Whether to enable data cleaning function | Yes |
+| Cleaning Method | By value or by percentage | Yes |
+| Upper Bound | Upper limit for filtering (absolute value or percentage) | Conditional |
+| Lower Bound | Lower limit for filtering (absolute value or percentage) | Conditional |
+
+**[Important]** Data cleaning only affects SPC report calculation results and does not modify original data in the MES system.
+
+**Function Screenshot**:
+
+
+## 4. SPC Render Condition Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Process Unit | Filter by process unit |
+| Item Code | Exact query by item code |
+| Item Name | Fuzzy query by item name |
+| Status | Filter by enabled/disabled status |
+
+**SPC Render Condition List Field Description:**
+
+| Field | Description |
+|-------|-------------|
+| Process Unit | Production process unit being monitored |
+| Process Unit Name | Name of process unit |
+| Item Code | Unique identifier for SPC monitoring item |
+| Item Name | Name of SPC monitoring item |
+| Data Category | Type of data source |
+| Status | Enabled/disabled status |
+| USL | Upper specification limit |
+| LSL | Lower specification limit |
+| Total Subgroups | Total number of subgroups |
+| Samples Per Subgroup | Number of samples per subgroup |
+| Subgroup Interval | Time interval between subgroups (hours) |
+| Control Chart Type | Type of control chart |
+
+**Function Screenshot**:
+
+
+## 5. Operation Notes
+
+1. **Data Source Dependence**: Before configuring SPC render conditions, ensure that the corresponding data category and SCADA point binding have been configured in the system.
+2. **USL/LSL Configuration**: To calculate CPK indicators in CPK analysis, USL and LSL must be configured.
+3. **Subgroup Configuration**: The product of total subgroups and subgroup interval determines the data collection time range. Please configure according to actual production needs.
+4. **Data Cleaning**: Data cleaning only affects SPC report calculation results and does not modify original data.
+5. **Status Control**: Disabled SPC render conditions will not be available for selection in SPC reports.
\ No newline at end of file
diff --git a/en/quality_control/spc_attribute_charts.md b/en/quality_control/spc_attribute_charts.md
new file mode 100644
index 0000000..5de8fb4
--- /dev/null
+++ b/en/quality_control/spc_attribute_charts.md
@@ -0,0 +1,214 @@
+# SPC Attribute Charts
+
+## 1. Function Overview
+
+SPC Attribute Charts belong to the quality management module of the MES system. They are used to perform statistical process control analysis on **discrete quality data** (such as number of defective products, number of defects) in production processes. Unlike variable charts, attribute charts focus on countable quality characteristics such as whether a product is qualified or the number of defects. By generating SPC control charts including DPMO, P Chart, NP Chart, C Chart, and U Chart, they help quality managers monitor trends in non-conforming product rates and defect rates during production processes and detect quality abnormalities in a timely manner.
+
+**Core Functions:**
+
+- Query quality data by process unit, SPC item, time range, and batch number
+- Automatically extract defect types from process data and perform subgroup grouping statistics
+- Generate five types of attribute SPC control charts: DPMO, PChart, NPChart, CChart, UChart
+- Support interactive functions such as automatic control limit calculation, abnormal point highlighting, and chart scrolling
+
+**Function Screenshot**:
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| SPC Attribute Charts | SPC Attribute Charts | Statistical process control reports for countable quality characteristics (e.g., number of defective products, number of defects) |
+| DPMO | Defects Per Million Opportunities | Measures the number of defects occurring in every million error opportunities, a comprehensive indicator for evaluating process quality level |
+| PChart | P Chart, Proportion Nonconforming Control Chart | Monitors the proportion of nonconforming items in each subgroup as a percentage of total inspected quantity, subgroup sizes can vary |
+| NPChart | NP Chart, Number Nonconforming Control Chart | Monitors the absolute number of nonconforming items in each subgroup, requires equal subgroup sizes |
+| CChart | C Chart, Number of Defects Control Chart | Monitors the total number of defects in each subgroup, suitable for scenarios with constant defect opportunities |
+| UChart | U Chart, Defects per Unit Control Chart | Monitors the average number of defects per unit product, suitable for scenarios with non-constant defect opportunities |
+| Subgroup | Subgroup | A group of sample data collected under similar time conditions in SPC analysis |
+| Defect Types | Defect Types | Classification of different defects occurring in the process, such as scratches, deformation, bubbles, etc., each corresponding to a specific NG code |
+| Process Unit | Working Subclass | Standardized operation unit in production process, the minimum granularity for SPC monitoring |
+| SPC Render Configuration | SPC Render Configuration | Configuration items defining data sources, subgroup sampling parameters, and control limits for SPC reports |
+
+**Comparison of Five Attribute Control Charts:**
+
+| Control Chart | Data Type | Application Scenario | Subgroup Size Requirement |
+|---------------|-----------|---------------------|--------------------------|
+| DPMO | Defect count/Opportunity count | Measure overall quality level, can be used for quality comparison between different products/processes | Requires defined error opportunities |
+| PChart | Nonconforming rate (decimal/percentage) | Monitor nonconforming product proportion in production process | Subgroup sizes can vary |
+| NPChart | Number of nonconforming items (integer) | Monitor absolute number of nonconforming items in each subgroup | Subgroup sizes must be equal |
+| CChart | Number of defects (integer) | Monitor total defects in fixed area | Defect opportunities must be constant |
+| UChart | Defects per unit (decimal) | Monitor average defects per unit product | Subgroup sizes can vary |
+
+## 3. SPC Attribute Charts Interaction Flow
+
+### 3.1 General Query Condition Description
+
+All five attribute control charts share the same query condition interface. After users filter data using the following conditions, the system automatically generates charts according to the corresponding control chart type.
+
+**Operation Path:**
+Go to [Quality Management] → [SPC Statistical Process Control] → [SPC Attribute Charts], select the corresponding control chart type.
+
+**Query Condition Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Process Unit | Select the production process unit to view, dropdown list comes from all processes configured in the system | Yes |
+| Item | Select the specific SPC monitoring item (data node), options are filtered based on process unit | Yes |
+| Time Range | Start and end time for querying data, default is the previous 24 hours from current time | Yes |
+| Batch Number | Filter data by production batch, query all batches if not filled | No |
+
+**Function Screenshot**:
+
+
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [SPC Statistical Process Control] → [SPC Attribute Charts], select the desired control chart type (DPMO / PChart / NPChart / CChart / UChart) in the left navigation
+2. Select the process to monitor in the [Process Unit] dropdown
+3. Select the SPC configuration item in the [Item] dropdown (item list will be automatically filtered based on selected process)
+4. Set the query start and end time in the [Time Range] selector
+5. (Optional) Enter batch number in the [Batch Number] input box for precise filtering
+6. Click [Query] button, the system will automatically retrieve data and generate the corresponding control chart
+
+**[Note]** Click [Reset] button to clear all query conditions and restore default state.
+
+### 3.2 Data Query and Chart Generation
+
+Based on the query conditions selected by the user, the system extracts SCADA real-time data for the corresponding process from the MES data collection database, groups the data into subgroups by hour granularity, counts the occurrence of each defect type within each subgroup, then automatically calculates control limits and draws the control chart.
+
+**Data Query Flow Description:**
+
+```mermaid
+sequenceDiagram
+ participant User as User
+ participant MESFrontend as MES Frontend
+ participant EdgeManager as EdgeManager Service
+ participant Database as SCADA Database
+
+ User->>MESFrontend: 1. Select process unit, item, time range, batch
+ User->>MESFrontend: 2. Click [Query]
+
+ MESFrontend->>EdgeManager: 3. Send query request (including process code, item code, time range, etc.)
+ EdgeManager->>Database: 4. Query SCADA real-time data table
+ Database-->>EdgeManager: 5. Return raw data (collected value + collection time)
+ EdgeManager->>EdgeManager: 6. Group by hour and assign subgroup IDs
+ EdgeManager->>EdgeManager: 7. Count defect types and occurrences for each subgroup
+ EdgeManager-->>MESFrontend: 8. Return subgroup statistical data
+ MESFrontend->>MESFrontend: 9. Render corresponding type of SPC control chart
+ MESFrontend-->>User: 10. Display control chart and statistical information
+```
+
+**Flow Description:**
+
+| Step | Actor | Action | Description |
+|------|-------|--------|-------------|
+| 1-2 | User | Set query conditions and submit | Select process unit, item, time range, and batch |
+| 3 | MES Frontend | Send query request | Send query via EdgeManager service interface, query parameters include: action (fixed as get_node_subgroup_sampling_type), process code, item code, sampling time range, batch number, etc. |
+| 4 | EdgeManager | Query database | Dynamically assemble data table name (format: hf_mes_scada_data_capture_node_data_{process_code}_{node_code}), query raw collected data by time range |
+| 5 | Database | Return raw data | Return collected values and corresponding collection times |
+| 6 | EdgeManager | Subgroup grouping | Sort and number all raw data by hour (HOUR) using ROW_NUMBER, assign sample serial numbers to each subgroup |
+| 7 | EdgeManager | Defect type statistics | Count occurrence of each defect type (NG code) in each subgroup, generate defect_types statistics |
+| 8 | EdgeManager | Return statistical data | Return structured data including subgroup number, sampling time, and defect type statistics |
+| 9 | MES Frontend | Render control chart | Select corresponding rendering method based on control chart type (DPMO/PChart/NPChart/CChart/UChart) |
+| 10 | User | View control chart | Display complete control chart including data points, control limits, abnormal highlights, etc. |
+
+### 3.3 DPMO (Defects Per Million Opportunities)
+
+#### 3.3.1 DPMO Description
+
+DPMO (Defects Per Million Opportunities) is a comprehensive indicator for measuring process quality level, representing the number of defects actually occurring in every million error opportunities. A lower DPMO value indicates a higher process quality level. The DPMO control chart helps quality managers determine whether the process is in a stable and controlled state by monitoring changes in DPMO values across subgroups.
+
+**Application Scenarios:**
+- Need to measure and compare quality levels between different products and processes
+- Need to benchmark quality indicators against Six Sigma levels (e.g., 3.4 DPMO = Six Sigma level)
+- Scenarios with non-constant defect opportunities
+
+**Function Screenshot**:
+
+
+### 3.4 PChart (Proportion Nonconforming Control Chart)
+
+#### 3.4.1 PChart Description
+
+PChart (P Control Chart, Proportion Nonconforming Control Chart) is used to monitor the proportion of nonconforming items in each subgroup as a percentage of total inspected quantity. PChart focuses on **the percentage of nonconforming items in the sample**, subgroup sizes can vary, and control limits adjust with subgroup sizes, forming stepped control boundaries.
+
+**Application Scenarios:**
+- Variable subgroup sizes (e.g., different numbers of products inspected each day)
+- Need to monitor trends in nonconforming product rates during production
+- Each product is only judged as conforming or nonconforming (binary classification)
+
+**Function Screenshot**:
+
+
+### 3.5 NPChart (Number Nonconforming Control Chart)
+
+#### 3.5.1 NPChart Description
+
+NPChart (NP Control Chart, Number Nonconforming Control Chart) is used to monitor the absolute number of nonconforming items in each subgroup. Unlike PChart, NPChart displays **the actual count of nonconforming items** rather than proportions. NPChart requires equal sample sizes for each subgroup; otherwise, control limits will no longer be valid.
+
+**Application Scenarios:**
+- Fixed subgroup sizes (e.g., inspecting 100 products per batch)
+- Need to visually display trends in nonconforming item counts
+- Easy for on-site personnel to understand and use (directly read nonconforming counts)
+
+**Function Screenshot**:
+
+
+### 3.6 CChart (Number of Defects Control Chart)
+
+#### 3.6.1 CChart Description
+
+CChart (C Control Chart, Number of Defects Control Chart) is used to monitor the total number of defects in each subgroup. CChart focuses on scenarios where multiple defects may exist on one product (e.g., multiple scratches on a panel). Therefore, CChart counts **total defects** rather than nonconforming item counts. CChart requires constant defect opportunities (i.e., inspected areas/ranges must remain consistent).
+
+**Application Scenarios:**
+- Inspecting fixed areas or fixed quantities of products (e.g., each glass sheet, each sheet of material)
+- A product may have multiple different types of defects
+- Need to monitor trends in overall defect counts
+
+**[Precautions]**
+- Defect opportunities must remain constant (e.g., inspecting the same area or same quantity of products each time)
+- CChart focuses on defect counts rather than nonconforming item counts; one product may have multiple defects
+
+**Function Screenshot**:
+
+
+### 3.7 UChart (Defects per Unit Control Chart)
+
+#### 3.7.1 UChart Description
+
+UChart (U Control Chart, Defects per Unit Control Chart) is used to monitor the average number of defects per unit product. Unlike CChart, UChart is suitable for scenarios with **non-constant defect opportunities** (e.g., different lengths of fabric inspected each day, different areas). It normalizes defect counts by unit size, calculating average defects per unit, with control limits adjusting as subgroup sizes change.
+
+**Application Scenarios:**
+- Variable inspection areas or product quantities (e.g., different lengths of fabric inspected daily)
+- Need to compare defect levels between inspection batches of different sizes
+- A product may have multiple defects, and quantities inspected may vary
+
+**Function Screenshot**:
+
+
+## 4. Control Chart Interactive Function Description
+
+All five attribute control charts provide the following common interactive functions:
+
+| Function | Description |
+|----------|-------------|
+| Automatic Control Limit Calculation | System automatically calculates Upper Control Limit (UCL) and Lower Control Limit (LCL) based on collected subgroup data |
+| Abnormal Point Highlighting | Data points exceeding control limits are highlighted for quick anomaly identification |
+| Scroll Bar | When there are many subgroups, supports horizontal scrolling to view complete control chart data |
+| Calculated Value Display | Display statistical calculation values for each subgroup (e.g., nonconforming rate, defect count) |
+| Alarm Status Display | Mark alarm status information for each subgroup on the chart |
+| Chart Control Switch | Support enabling/disabling various auxiliary display options for the control chart |
+
+**[Note]** Control charts are generated based on industry-standard QC SPC control chart algorithm libraries, with control limit calculations following standard statistical process control formulas to ensure accuracy and authority of analysis results.
+
+## 5. Precautions
+
+1. **SPC Render Condition Prerequisite Configuration**: Before using SPC attribute charts, you need to complete SPC configuration for corresponding process units and data nodes in [SPC Render Condition Configuration]. Otherwise, the corresponding monitoring items cannot be selected in the "Item" dropdown.
+
+2. **Data Source Description**: Data for SPC attribute charts comes from SCADA real-time collection data in the MES system. Data collection frequency and subgroup intervals are determined by parameters in SPC render condition configuration. Data is stored in the system's data collection tables, and the frontend obtains processed subgroup statistical data through the EdgeManager service interface.
+
+3. **Subgroup Size Requirements**: NPChart requires equal sample sizes for each subgroup. If actual data has inconsistent subgroup sizes, control limit calculations may be inaccurate. It is recommended to uniformly set subgroup sampling parameters in SPC render condition configuration.
+
+4. **Defect Type Statistics**: Defect types (NG codes) come from defect classification information recorded by equipment or manually during production. The system groups and counts using NG codes as unique identifiers for defect types. Please ensure standardization of the NG coding system.
+
+5. **Time Granularity**: The system groups data into subgroups by hour granularity. The subgroup sampling interval configuration determines the time span between adjacent subgroups. If configured as 2 hours, collected data for every 2 hours will be merged into one subgroup.
\ No newline at end of file
diff --git a/en/quality_control/spc_variable_charts.md b/en/quality_control/spc_variable_charts.md
new file mode 100644
index 0000000..3eb34dc
--- /dev/null
+++ b/en/quality_control/spc_variable_charts.md
@@ -0,0 +1,448 @@
+# SPC Variable Charts
+
+## 1. Function Overview
+
+SPC Variable Charts belong to the core SPC (Statistical Process Control) functions in the quality management module of the MES system. They are used to perform statistical analysis and process control on continuous quality characteristic data (such as voltage, current, temperature, pressure, and other measurable values) during production processes. Based on sampling rules defined in SPC render condition configuration, the system automatically extracts samples from production line process inspection data, process data, and result data, generates various variable control charts and process capability analysis charts, helping quality managers monitor production process stability and capability in real-time.
+
+**Core Functions:**
+
+- XBar-R Control Chart: Monitor process mean and dispersion through subgroup means and ranges
+- XBar-S Control Chart: Monitor process mean and dispersion through subgroup means and standard deviations (suitable for larger subgroup sample sizes)
+- I-MR Control Chart: Individual-Moving Range control chart, suitable for scenarios with only 1 sample per subgroup
+- CPK Process Capability Analysis: Calculate process capability indices including Cp, Cpk, Pp, Ppk to evaluate process capability in meeting specification requirements
+- EWMA Control Chart: Exponentially Weighted Moving Average control chart, more sensitive to small process shifts
+- CUSUM Control Chart: Cumulative Sum control chart, highly sensitive to detecting small process shifts
+- Levey-Jennings Control Chart: Statistical control chart based on multi-subgroup samples, suitable for quality control scenarios
+- MA Moving Average Control Chart: Statistical process control based on moving averages
+- MAMR Moving Average-Moving Range Control Chart: Process control combining moving average and moving range
+- MAMS Moving Average-Standard Deviation Control Chart: Process control combining moving average and standard deviation
+
+**Function Screenshot**:
+
+
+## 2. Term Explanation
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Variable Data | Variable Data | Continuously measurable quality characteristic data, such as voltage, current, temperature, pressure, dimensions, etc. |
+| Control Chart | Control Chart | Statistical chart with control limits, used to distinguish between normal and abnormal process variations |
+| Subgroup | Subgroup | A group of sample measurements collected under similar conditions, used to calculate within-group statistics |
+| Total Subgroups | Total Subgroups | Total number of subgroups to be collected in a single SPC analysis |
+| Samples Per Subgroup | Samples Per Subgroup | Number of sample measurements contained within each subgroup |
+| Subgroup Interval | Subgroup Sampling Interval | Sampling time interval between adjacent subgroups (in hours) |
+| Upper Control Limit (UCL) | Upper Control Limit | Upper limit in control chart for determining process control status, calculated from process data statistics |
+| Lower Control Limit (LCL) | Lower Control Limit | Lower limit in control chart for determining process control status, calculated from process data statistics |
+| Upper Specification Limit (USL) | Upper Specification Limit | Maximum allowable value for product quality characteristic, defined by product specification or customer requirements |
+| Lower Specification Limit (LSL) | Lower Specification Limit | Minimum allowable value for product quality characteristic, defined by product specification or customer requirements |
+| Mean (XBar) | Mean / Average | Arithmetic mean of all sample measurements within a subgroup, reflecting process central tendency |
+| Range (R) | Range | Difference between maximum and minimum values within a subgroup, reflecting within-group dispersion |
+| Standard Deviation (S) | Standard Deviation | Standard deviation of sample measurements within a subgroup, reflecting within-group dispersion |
+| Moving Range (MR) | Moving Range | Absolute difference between two consecutive individual measurements |
+| CPK | Process Capability Index | Measures actual process capability under controlled conditions, considering mean shift |
+| CP | Process Capability | Measures potential process capability (without considering mean shift) |
+| PPK | Process Performance Index | Measures long-term actual process performance |
+| PP | Process Performance | Measures long-term total process variation |
+| EWMA | Exponentially Weighted Moving Average | Exponentially weighted moving average, assigning higher weights to recent data |
+| CUSUM | Cumulative Sum | Cumulative sum, accumulation of deviations from target value |
+| Levey-Jennings | Levey-Jennings Chart | Statistical control chart used with multi-level quality control rules, commonly used in laboratory quality control and medical statistics |
+| SPC Render Configuration | SPC Render Configuration | Configuration defining data sources, sampling parameters, and calculation rules required for generating SPC reports |
+
+## 3. SPC Variable Charts Interaction Flow
+
+### 3.1 SPC Variable Charts Description
+
+The SPC Variable Charts page provides 10 types of variable control charts and process capability analysis tools. Users select conditions such as process, SPC item, and time range, and the system automatically extracts corresponding data from the MES database and generates visual charts.
+
+**Operation Path:**
+Go to [Quality Management] → [SPC Statistical Process Control] → [SPC Variable Charts] → Select the corresponding report type
+
+**General Query Condition Description:**
+
+| Query Condition | Description | Required |
+|----------------|-------------|----------|
+| Process Subclass | Select the process unit to monitor. After filtering, the SPC item dropdown will automatically load SPC items configured under this process | Yes |
+| SPC Item | Select the specific SPC monitoring item (corresponding to the item name in SPC render condition configuration) | Yes |
+| Time Range | Select the start and end time for data collection (accurate to hour:minute:second) | Yes |
+| Batch Number | Filter data by production batch number (optional) | No |
+| Roll Number | Filter data by roll number (optional). After entering the roll number, the system automatically obtains the corresponding production time range | No |
+
+**[Note]** Batch number and roll number cannot be entered simultaneously; they are mutually exclusive.
+
+**Function Screenshot**:
+
+
+---
+
+### 3.2 XBar-R Mean-Range Control Chart
+
+#### 3.2.1 XBar-R Chart Description
+
+XBar-R (Mean-Range) control chart is one of the most commonly used variable control charts, consisting of two sub-charts: the upper chart is the Mean Chart (XBar Chart), used to monitor process mean variation; the lower chart is the Range Chart (R Chart), used to monitor process dispersion. Suitable for scenarios with 2~10 samples per subgroup.
+
+**Application Scenarios:**
+- Production processes requiring simultaneous monitoring of mean and variation for quality characteristics
+- Continuous production processes with moderate subgroup sample sizes (2~10 samples/group)
+- Key process parameter monitoring such as cell injection volume, welding temperature, coating thickness
+
+**Chart Characteristics:**
+- Display subgroup means (XBar) and ranges (R)
+- Automatically calculate and draw Upper Control Limit (UCL) and Lower Control Limit (LCL)
+- Display process capability indices Cpk and Ppk
+- Support chart scrolling and display option switching
+- When specification limits (USL/LSL) are configured, specification lines are marked on the chart
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [SPC Statistical Process Control] → [SPC Variable Charts] → [XBar-R]
+2. Select [Process Subclass] in the query area. The system automatically loads SPC items configured under this process
+3. Select [SPC Item] (e.g., "OCV2 Voltage", etc.)
+4. Select [Time Range], and optionally enter [Batch Number] or [Roll Number] for further filtering
+5. Click [Query] button. The system retrieves data and generates the XBar-R control chart
+6. Adjust display content using toggle buttons in the upper right corner of the chart
+7. Click [Export Sample Data] to export chart source data as CSV file
+
+**Control Chart Anomaly Detection Rules:**
+
+The system automatically marks the following abnormal conditions on the XBar-R chart:
+- Data points exceeding control limits (UCL/LCL)
+- Consecutive points on the same side of the center line
+- Data points showing trending changes (continuous increase or decrease)
+- Data points showing periodic fluctuations
+
+**Function Screenshot**:
+
+
+---
+
+### 3.3 XBar-S Mean-Standard Deviation Control Chart
+
+#### 3.3.1 XBar-S Chart Description
+
+XBar-S (Mean-Standard Deviation) control chart is similar to XBar-R, but uses standard deviation (S) instead of range (R) to measure within-group dispersion. Standard deviation utilizes sample information more fully than range, so it is suitable for scenarios with larger subgroup sample sizes (n > 10).
+
+**Application Scenarios:**
+- Production processes with larger subgroup sample sizes (typically n ≥ 10)
+- Scenarios requiring more precise measurement of process variation
+- Automated high-speed continuous production lines
+
+**Chart Characteristics:**
+- Display subgroup means (XBar) and standard deviations (S)
+- Automatically calculate and draw control limits
+- Display process capability indices Cpk and Ppk
+- Support chart scrolling and display option switching
+- When specification limits are configured, specification lines are marked on the chart
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [SPC Statistical Process Control] → [SPC Variable Charts] → [XBar-S]
+2. Select [Process Subclass] and [SPC Item] in the query area
+3. Select [Time Range], and optionally enter [Batch Number] or [Roll Number] for filtering
+4. Click [Query] button. The system retrieves data and generates the XBar-S control chart
+5. Click [Export Sample Data] to export chart source data as CSV file
+
+**Function Screenshot**:
+
+
+---
+
+### 3.4 I-MR Individual-Moving Range Control Chart
+
+#### 3.4.1 I-MR Chart Description
+
+I-MR (Individual-Moving Range) control chart is suitable for scenarios where only 1 measurement value can be obtained per subgroup. The upper chart (I Chart) displays individual measurement values, and the lower chart (MR Chart) displays moving ranges between consecutive measurements. I-MR charts are suitable when production processes are highly automated and produce only one measurement per cycle, or when measurement costs are high and testing cycles are long.
+
+**Application Scenarios:**
+- Continuous production processes with only 1 sample per subgroup
+- Automated inspection equipment testing item by item
+- Destructive testing or high-cost testing scenarios
+- Industries with slowly changing process parameters such as chemical and metallurgical processes
+
+**Chart Characteristics:**
+- Display individual measurement values (I Chart) and moving ranges (MR Chart)
+- Automatically calculate and draw control limits
+- When specification limits (USL/LSL) are configured, specification lines are marked on the chart
+- Display process capability and calculated statistics
+- Support chart scrolling and display option switching
+
+**Control Chart Anomaly Marking Description:**
+- System automatically highlights data points exceeding control limits
+- Mark with special symbols when data points continuously show abnormal patterns
+
+**Function Screenshot**:
+
+
+---
+
+### 3.5 Levey-Jennings Control Chart
+
+#### 3.5.1 Levey-Jennings Chart Description
+
+Levey-Jennings control chart is a statistical control chart based on multi-subgroup samples, monitoring process stability through subgroup means and standard deviations. Widely used in medical testing, laboratory quality control, and manufacturing for process monitoring with multi-level quality control rules.
+
+**Application Scenarios:**
+- Scenarios requiring strict process monitoring with multi-level quality control rules
+- Daily quality control of laboratory analytical instruments
+- Continuous monitoring of critical electrical performance indicators in battery manufacturing
+
+**Chart Characteristics:**
+- Display subgroup means and standard deviations
+- Automatically calculate and draw control limits
+- Display process capability indices Cpk, Cpm, and Ppk
+- When specification limits are configured, specification lines are marked on the chart
+- Support chart scrolling and display option switching
+
+**Function Screenshot**:
+
+
+---
+
+### 3.6 EWMA Exponentially Weighted Moving Average Control Chart
+
+#### 3.6.1 EWMA Chart Description
+
+EWMA (Exponentially Weighted Moving Average) control chart assigns greater weights to recent observations, providing higher detection sensitivity for small shifts in process mean compared to traditional XBar charts. EWMA charts control the decay rate of historical data through weighting coefficient λ.
+
+**Application Scenarios:**
+- Scenarios requiring high sensitivity to small process shifts
+- Need rapid detection of effects after process adjustments
+- As a supplement to traditional control charts for early warning
+- Industries with extremely high process precision requirements such as semiconductors and precision electronics
+
+**Chart Characteristics:**
+- Display EWMA statistics and process mean
+- Automatically calculate and draw control limits
+- Calculate EWMA values and mean statistics
+- When specification limits are configured, specification lines are marked on the chart
+- Support chart scrolling and display option switching
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [SPC Statistical Process Control] → [SPC Variable Charts] → [EWMA]
+2. Select [Process Subclass] and [SPC Item] in the query area
+3. Select [Time Range], and optionally enter [Batch Number] for filtering
+4. Click [Query] button. The system retrieves data and generates the EWMA control chart
+
+**Function Screenshot**:
+
+
+---
+
+### 3.7 CUSUM Cumulative Sum Control Chart
+
+#### 3.7.1 CUSUM Chart Description
+
+CUSUM (Cumulative Sum) control chart detects small process shifts by accumulating deviations between actual values and target values. Similar to EWMA, CUSUM is highly sensitive to small changes in process mean and can detect abnormal trends earlier than traditional control charts.
+
+**Application Scenarios:**
+- Scenarios requiring extremely high detection sensitivity for small process shifts
+- Continuous production processes where frequent false alarms are undesirable but real anomalies need rapid detection
+- Process optimization and improvement effect evaluation
+- Strict process control scenarios such as chemical reaction processes and precision machining
+
+**Chart Characteristics:**
+- Display positive cumulative sum (C+) and negative cumulative sum (C-)
+- Automatically calculate and draw control limits
+- When specification limits are configured, specification lines are marked on the chart
+- Support chart scrolling and display option switching
+
+**Function Screenshot**:
+
+
+---
+
+### 3.8 MA Moving Average Control Chart
+
+#### 3.8.1 MA Chart Description
+
+MA (Moving Average) control chart smooths short-term fluctuations by calculating the average of consecutive data points, highlighting long-term trends. Moving average charts effectively filter random noise in production processes, providing clearer reflection of process mean changes.
+
+**Application Scenarios:**
+- Process data with significant random fluctuations
+- Need to observe long-term process trend changes
+- Noisy sensor data monitoring
+
+**Chart Characteristics:**
+- Display moving average sequence
+- Automatically calculate and draw control limits
+- When specification limits are configured, specification lines are marked on the chart
+- Support chart scrolling and display option switching
+
+**Function Screenshot**:
+
+
+---
+
+### 3.9 MAMR Moving Average-Moving Range Control Chart
+
+#### 3.9.1 MAMR Chart Description
+
+MAMR (Moving Average-Moving Range) control chart combines moving average and moving range dimensions, simultaneously monitoring process central tendency and dispersion. The moving average component smooths random fluctuations and highlights trends, while the moving range component monitors process variation.
+
+**Application Scenarios:**
+- Need to simultaneously monitor process trends and variation
+- Process control in single-value data scenarios
+- Production processes requiring balanced sensitivity and stability
+
+**Chart Characteristics:**
+- Display moving averages and moving ranges
+- Automatically calculate and draw control limits
+- Calculate EWMA values and mean statistics
+- When specification limits are configured, specification lines are marked on the chart
+- Support chart scrolling and display option switching
+
+**Function Screenshot**:
+
+
+---
+
+### 3.10 MAMS Moving Average-Standard Deviation Control Chart
+
+#### 3.10.1 MAMS Chart Description
+
+MAMS (Moving Average-Moving Standard Deviation) control chart is similar to MAMR but uses moving standard deviation instead of moving range to measure process variation. Standard deviation provides more complete variation information and offers more comprehensive detection of abnormal fluctuations.
+
+**Application Scenarios:**
+- Need more comprehensive measurement of process variation
+- Comprehensive process control for single-value data
+- Scenarios requiring high sensitivity to process variation detection
+
+**Chart Characteristics:**
+- Display moving averages and moving standard deviations
+- Automatically calculate and draw control limits
+- When specification limits are configured, specification lines are marked on the chart
+- Support chart scrolling and display option switching
+
+**Function Screenshot**:
+
+
+---
+
+### 3.11 CPK Process Capability Index Analysis
+
+#### 3.11.1 CPK Chart Description
+
+The CPK process capability analysis page provides comprehensive process capability index calculation and histogram visualization. Based on selected SPC items and sampling parameters, the system automatically collects data and calculates a series of process capability indicators, intuitively displaying data distribution characteristics and their relationship to specification limits through histograms overlaid with normal distribution curves.
+
+**Application Scenarios:**
+- Evaluate whether production processes meet product specification requirements
+- New process validation and process improvement effect evaluation
+- Supplier quality capability evaluation
+- Provide process capability evidence during customer audits
+
+**Chart Characteristics:**
+- Histogram displays data distribution pattern
+- Overlay two normal curves: overall distribution (red) and within-group distribution (blue)
+- Mark Upper Specification Limit (USL), Lower Specification Limit (LSL), and Mean line
+- Display comprehensive process capability statistics
+
+**Operation Steps:**
+
+1. Go to [Quality Management] → [SPC Statistical Process Control] → [SPC Variable Charts] → [CPK]
+2. Select [Process Subclass] and [SPC Item] in the query area
+3. Select [Time Range], and optionally enter [Batch Number] or [Roll Number] for filtering
+4. Click [Query] button. The system retrieves data and generates the process capability analysis chart
+5. Click [Export Sample Data] to export analysis data as CSV file
+
+**[Note]** If specification limits (USL/LSL) are not configured, CPK-related indicators cannot be calculated. Please set specification limit values in SPC render condition configuration first.
+
+#### 3.11.2 Process Capability Indicator Description
+
+| Indicator | English Full Name | Description | Judgment Standard |
+|-----------|------------------|-------------|------------------|
+| Mean | Mean | Arithmetic mean of all sample measurements | — |
+| Min | Minimum | Minimum measurement value in the sample | — |
+| Max | Maximum | Maximum measurement value in the sample | — |
+| Std Dev LT | Long-Term Standard Deviation | Overall standard deviation calculated based on all samples, reflecting long-term process variation | — |
+| Std Dev ST | Short-Term Standard Deviation | Within-group standard deviation calculated using moving range averaging method, reflecting short-term process variation | — |
+| Cp | Process Capability | Measures potential process capability | ≥ 1.33 indicates sufficient capability |
+| Cpk | Process Capability Index | Measures actual process capability considering process center shift | ≥ 1.33 indicates controlled process with sufficient capability |
+| Cpl | Lower Capability Index | Lower process capability index, measuring distance between mean and lower specification limit | — |
+| Cpu | Upper Capability Index | Upper process capability index, measuring distance between mean and upper specification limit | — |
+| Cpm | Taguchi Capability Index | Taguchi process capability index, measuring process deviation from target value | ≥ 1.33 indicates process close to target value |
+| Pp | Process Performance | Measures potential capability under long-term total variation | ≥ 1.33 indicates sufficient long-term performance |
+| Ppk | Process Performance Index | Measures long-term actual performance | ≥ 1.33 indicates good long-term process performance |
+| Ppl | Lower Performance Index | Lower process performance index | — |
+| Ppu | Upper Performance Index | Upper process performance index | — |
+
+**Process Capability Judgment Reference:**
+
+| Capability Index Range | Judgment | Recommended Action |
+|----------------------|----------|-------------------|
+| Cpk ≥ 1.67 | Excellent capability | Consider simplifying control or reducing inspection frequency |
+| 1.33 ≤ Cpk < 1.67 | Sufficient capability | Maintain current control level |
+| 1.00 ≤ Cpk < 1.33 | Acceptable capability | Strengthen process monitoring, consider process improvement |
+| 0.67 ≤ Cpk < 1.00 | Insufficient capability | Must implement process improvement |
+| Cpk < 0.67 | Severely insufficient capability | Urgent improvement required, production suspension adjustment if necessary |
+
+**[Important]** The system uses the moving range averaging method (MR-bar / d2) to calculate short-term standard deviation, where the d2 constant is 1.128 (corresponding to subgroup size n=2). This is an internationally accepted method for estimating SPC short-term standard deviation.
+
+**[Important]** Difference between Cp and Cpk: Cp measures potential process capability (assuming process center coincides with specification center), while Cpk measures actual process capability (considering process center shift). Cpk ≤ Cp always holds. When Cpk is significantly smaller than Cp, it indicates process center shift, requiring process adjustment to bring mean closer to target value.
+
+**Function Screenshot**:
+
+
+---
+
+## 4. SPC Variable Charts Data Collection Logic
+
+### 4.1 Data Sources
+
+Data for each variable chart comes from the data category specified in SPC render condition configuration:
+
+| Data Category | Description | Example |
+|---------------|-------------|---------|
+| Process Inspection Data | Inspection data collected during first article and circuit inspections on the production line | Voltage and dimension values measured by inspectors |
+| Process Data | Production process parameters automatically uploaded by equipment | Temperature, pressure, speed collected in real-time by equipment |
+| Result Data | Inspection result data after process completion | OCV test voltage, internal resistance, capacity values |
+
+### 4.2 Data Sampling Flow
+
+```mermaid
+flowchart TB
+ A[User Sets Query Conditions] --> B[System Reads SPC Render Condition Configuration]
+ B --> C[Locate Data Source Based on Data Category]
+ C --> D{Is Data Cleaning Configured?}
+ D -->|Yes| E[Execute Data Cleaning]
+ D -->|No| F[Use Raw Data Directly]
+ E --> G[Sample According to Subgroup Rules]
+ F --> G
+ G --> H{Subgroup Data Collection Mode}
+ H -->|Multi-Subgroup Mode| I[Split Data by Subgroup Interval]
+ H -->|Single-Sample Mode| J[Collect Data by Time Interval]
+ I --> K[Calculate Subgroup Statistics]
+ J --> K
+ K --> L[Calculate Control Limits]
+ L --> M[Generate Control Chart/Analysis Report]
+```
+
+### 4.3 Data Collection Mode Description
+
+The system supports three data collection modes, with different chart types using different modes:
+
+| Mode | Applicable Charts | Data Characteristics | Description |
+|------|------------------|---------------------|-------------|
+| Multi-Subgroup Mode | XBar-R, XBar-S, I-MR, Levey-Jennings | Split data by subgroup count and subgroup interval, returning multiple subgroup samples | Each group contains multiple measurements and sampling times |
+| Single-Subgroup Mode | CPK | Return all samples as one subgroup for capability analysis | All data participates in statistical calculation |
+| Single-Sample Mode | MA, MAMR, MAMS, EWMA, CUSUM | Collect single measurement values at time intervals | One value collected per time point |
+
+**[Important]** Data cleaning rules (by value or by percentage) are set in SPC render condition configuration. Data cleaning only affects SPC report calculation results and does not modify original data in the MES system.
+
+**[Note]** Subgroup sampling uses continuous sampling mode (Continuous), meaning subgroups are collected continuously from the data source at set intervals rather than random sampling.
+
+---
+
+## 5. Control Chart Selection Guide
+
+Different production processes and data characteristics are suitable for different control chart types. The following is a selection reference:
+
+| Data Characteristics | Recommended Control Chart | Alternative Control Chart |
+|---------------------|--------------------------|--------------------------|
+| Subgroup sample size 2~10, groupable sampling | XBar-R | — |
+| Subgroup sample size > 10, groupable sampling | XBar-S | XBar-R |
+| Only 1 sample per subgroup | I-MR | MA, MAMR, MAMS |
+| Need to detect small process shifts | EWMA, CUSUM | I-MR |
+| Need to evaluate process capability to meet specifications | CPK | — |
+| Multi-level quality control rule monitoring | Levey-Jennings | XBar-R, XBar-S |
+| Focus on long-term trends | MA, MAMR, MAMS | EWMA |
+
+**[Note]** For the same quality characteristic, multiple control charts can be used simultaneously for cross-validation. For example, XBar-R for daily monitoring, EWMA for early warning, and CPK for periodic capability evaluation.
\ No newline at end of file
diff --git a/en/system_settings/menu_configuration.md b/en/system_settings/menu_configuration.md
new file mode 100644
index 0000000..5974fc2
--- /dev/null
+++ b/en/system_settings/menu_configuration.md
@@ -0,0 +1,172 @@
+# Menu Management
+
+## 1. Function Overview
+
+The Menu Management module is used to configure the system's menu structure, supporting menu configuration for both the backend management and PDA terminals. It enables menu CRUD operations, sorting, and permission association.
+
+**Core Functions:**
+
+- Menu Tree Structure Management: Supports creation, editing, and deletion of multi-level menus
+- Menu Category Management: Distinguishes between admin (backend) and PDA module menus
+- Menu Status Control: Supports enabling/disabling menu operations
+- Menu Sorting: Supports drag-and-drop sorting to adjust menu display order
+- Menu Permission Association: New menus are automatically associated with the super admin role
+- Menu Navigation Property: Controls whether menus are displayed in the navigation bar
+
+**Function Screenshot**:
+
+
+## 2. Term Explanation
+
+#### 2.1.1 Menu-related Terms
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Top-level Menu | Menu node without parent menu | Serves as root node of menu tree |
+| Sub-menu | Menu node with parent menu | Supports multi-level nesting |
+| Module | System module to which menu belongs | admin (backend), pda (PDA terminal) |
+| Navigation Property | Whether menu is displayed in navigation bar | Visible (1) or Hidden (0) |
+| Link Type | Type of menu link | Module (0) or External Link (1) |
+| Open Method | Link opening method | Current window (_self) or New window (_blank) |
+
+## 3. Menu Management Operations
+
+### 3.1 Menu Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Module | Select backend (admin) or PDA module |
+| Status | Filter enabled or disabled menus |
+| Navigation Property | Filter visible or hidden menus |
+| Menu Depth | Control expansion level of menu tree |
+
+**Operation Steps:**
+
+1. Go to [System Settings] → [Menu Management] → [Menu Configuration]
+2. Select query conditions in the top query area
+3. Click [Query] button to get menu list
+4. Click [Reset] button to clear query conditions
+
+**Function Screenshot**:
+
+
+### 3.2 Add Menu
+
+**Operation Steps:**
+
+1. Go to [System Settings] → [Menu Management] → [Menu Configuration]
+2. Click [Add Top-level Menu] button, or click [Add] button on existing menu to add sub-menu
+3. Fill in menu form information
+4. Click [OK] to complete addition
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Parent Menu | Select parent menu; no selection means top-level menu | No |
+| Name | Display name of menu | Yes |
+| Alias | Alias identifier for menu; required for API-type menus | No |
+| Icon | Menu icon, can be selected or customized | No |
+| Sort | Sort order number; smaller value means higher priority | Yes |
+| Navigation | Controls whether menu is displayed in navigation bar | Yes |
+| Link Type | Module (0) or External Link (1) | Yes |
+| Open Method | Current window or New window | Yes |
+| URL | Menu link address | No |
+| Parameters | Link parameters | No |
+| Remarks | Remarks for menu | No |
+
+**[Tip]** When adding a menu, the system automatically associates it with the super admin role.
+
+**Function Screenshot**:
+
+
+### 3.3 Edit Menu
+
+**Operation Steps:**
+
+1. Click the menu node to edit in the menu tree
+2. Modify menu information in the right form
+3. Click [Modify] button to save changes
+
+**[Note]** Menu names cannot be duplicated within the same module.
+
+**Function Screenshot**:
+
+
+### 3.4 Delete Menu
+
+**Operation Steps:**
+
+1. Find the menu to delete in the menu tree
+2. Click [Delete] button on the right side of the menu
+3. Click [OK] in the confirmation dialog
+
+**Function Screenshot**:
+
+
+**[Important]** If the menu or its child menus are being used by roles, deletion is not allowed.
+
+### 3.5 Enable/Disable Menu
+
+**Operation Steps:**
+
+1. Find the menu to operate in the menu tree
+2. Click [Disable] or [Enable] button on the right side of the menu
+3. Click [OK] in the confirmation dialog
+
+**[Note]** Status switching affects the menu and all its child menus.
+
+**Function Screenshot**:
+
+
+### 3.6 Menu Sorting
+
+**Operation Steps:**
+
+1. Drag menu node to target position in the menu tree
+2. System automatically saves sorting result
+
+**Supported Drag Operations:**
+- Drag to front or back of sibling menus
+- Drag to other menus as sub-menu
+
+**Function Screenshot**:
+
+
+## 7. Data Flow Diagram
+
+```mermaid
+flowchart TD
+ A[User Request] --> B{Is Super Admin?}
+ B -->|Yes| C[Query All Menus]
+ B -->|No| D[Query Role-associated Menus]
+ C --> E[Return Menu List]
+ D --> E
+ E --> F[Frontend Renders Tree Structure]
+ F --> G[User Operation]
+ G --> H{Operation Type}
+ H -->|Add| I[Validate Name Uniqueness]
+ H -->|Edit| J[Validate Name Uniqueness]
+ H -->|Delete| K[Check Role Usage]
+ H -->|Status Switch| L[Check Role Usage]
+ I --> M[Save Menu Data]
+ J --> M
+ K --> N{Is Being Used?}
+ L --> N
+ N -->|Yes| O[Show Error Message]
+ N -->|No| P[Execute Operation]
+ M --> Q[Associate Super Admin]
+ Q --> R[Return Result]
+ P --> R
+ O --> R
+```
+
+## 8. Notes
+
+**[Important]** Before deleting or disabling a menu, ensure it is not used by any role; otherwise, the operation will fail.
+
+**[Tip]** It is recommended to regularly organize the menu structure to maintain clarity and logic of the menu tree.
+
+**[Note]** Smaller menu sort values appear first; default value is 50.
\ No newline at end of file
diff --git a/en/system_settings/system_assistant.md b/en/system_settings/system_assistant.md
new file mode 100644
index 0000000..c22aaed
--- /dev/null
+++ b/en/system_settings/system_assistant.md
@@ -0,0 +1,140 @@
+# System Assistant
+
+## 1. Function Overview
+
+The System Assistant module provides query functions for system operation logs and interface logs, helping administrators track system operation records and interaction logs of device docking processes.
+
+**Core Functions:**
+
+- Operation Log Query: Records user's system operation behavior, supports query by user, IP, time, etc.
+- Interface Log Query: Records interface interaction logs with device docking, supports query by IP, interface name, etc.
+
+**Function Screenshot**:
+
+
+## 2. Term Explanation
+
+#### 2.1.1 Log-related Terms
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Operation Log | User's operation records in the system | Including login, CRUD operations, etc. |
+| Interface Log | Interaction records between system and external devices/systems | Including device docking, data transmission, etc. |
+| Tray ID | Unique identifier for device tray | Used for device docking tracking |
+| Batch ID | Unique identifier for production batch | Used for production process tracking |
+| Battery Barcode | Unique identifier for battery barcode | Used for production process tracking |
+| Process Code | Unique identifier for process code | Used for production process tracking |
+| Interface Status Code | Return status of interface call | 0 means success, 4001/4002 means failure |
+
+## 3. Operation Log
+
+### 3.1 Operation Log Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| User | Filter operation records by user ID |
+| IP Address | Filter by operation IP address |
+| Route Name | Filter by accessed route name |
+| Tray ID | Filter related operations by tray ID |
+| Batch ID | Filter related operations by batch ID |
+| Time Range | Filter by operation time range, default is last week |
+
+**Operation Steps:**
+
+1. Go to [System Settings] → [System Assistant] → [Operation Log]
+2. Set query conditions in the top query area
+3. Click [Query] button to get operation log list
+
+**Function Screenshot**:
+
+
+
+### 3.2 Operation Log Field Description
+
+| Field | Description |
+|-------|-------------|
+| ID | Unique identifier for log |
+| Username | User who performed the operation |
+| Request Path | Accessed URL path |
+| Controller Method | Executed controller and method |
+| IP Address | Operation source IP |
+| Status | Operation status |
+| Request Parameters | Incoming parameters |
+| Execution Result | Returned result |
+| Operation Type | Type of operation |
+| Operation Name | Chinese name of operation |
+| Tray ID | Associated tray ID |
+| Batch ID | Associated batch ID |
+| Operation Time | Operation occurrence time |
+
+### 3.3 Log Record Content
+
+The system automatically records the following types of operations:
+
+- User login/logout
+- Data addition, editing, deletion
+- Status changes
+- Permission configuration
+- System settings modification
+
+## 4. Interface Log
+
+### 4.1 Interface Log Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Device Unit | Filter by device unit name |
+| IP Address | Filter by client IP address |
+| Process Code | Filter by process code |
+| Tray ID | Filter by tray ID |
+| Battery ID | Filter by battery ID |
+| Time Range | Filter by interaction time range, default is last week |
+| Status | Filter successful or failed interface calls |
+| Source Category | Filter interfaces from ERP/SPC sources |
+
+**Operation Steps:**
+
+1. Go to [System Settings] → [System Assistant] → [Interface Log]
+2. Set query conditions in the top query area
+3. Click [Query] button to get interface log list
+
+**Function Screenshot**:
+
+
+### 4.2 Interface Log Field Description
+
+| Field | Description |
+|-------|-------------|
+| ID | Unique identifier for log |
+| Device Unit | Device unit name |
+| Client IP | Device IP that called the interface |
+| Data1 | Usually stores process code |
+| Data2 | Usually stores tray ID |
+| Data3 | Usually stores battery ID |
+| Creation Time | Log record time |
+| Interface Time | Interface call time |
+| Status | Interface call status (0 success, 4001/4002 failure) |
+| Category | Interface category (erp/spc, etc.) |
+| Type | Interface type |
+| Request Parameters | Interface incoming parameters |
+| Return Result | Interface return result |
+| Data4 | Extension field 1 |
+| Data5 | Extension field 2 |
+
+### 4.3 View Interface Details
+
+**Operation Steps:**
+
+1. Click the view response button in the interface log list
+2. View detailed information of interface call, including request parameters, return results, status code, etc.
+
+**Function Screenshot**:
+
+
+## 5. Notes
+
+**[Note]** The purpose of data fields (data1-data5) in interface logs varies according to interface types. The specific meaning needs to be understood in combination with business scenarios.
\ No newline at end of file
diff --git a/en/system_settings/system_monitoring.md b/en/system_settings/system_monitoring.md
new file mode 100644
index 0000000..ef4a48c
--- /dev/null
+++ b/en/system_settings/system_monitoring.md
@@ -0,0 +1,106 @@
+# System Monitoring
+
+## 1. Function Overview
+
+The System Monitoring module is used to configure and manage system monitoring parameters, enabling real-time monitoring of server resources and alarm settings.
+
+**Core Functions:**
+
+- Monitoring Configuration Management: Create, edit, delete monitoring configurations
+- Resource Alarm Settings: Configure alarm thresholds for CPU, disk, and memory
+- Monitoring Refresh Settings: Configure refresh intervals for monitoring data
+- Monitoring List Query: Support filtering by name and ID
+
+**Function Screenshot**:
+
+
+## 2. Term Explanation
+
+#### 2.1.1 Monitoring-related Terms
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| Monitoring ID | Unique identifier for monitoring configuration | Used to distinguish different monitoring targets |
+| Refresh Interval | Time interval for updating monitoring data | Usually in seconds |
+| CPU Alarm Threshold | Alarm threshold for CPU usage | Triggers alarm when exceeded |
+| Disk Alarm Threshold | Alarm threshold for disk usage | Triggers alarm when exceeded |
+| Memory Alarm Threshold | Alarm threshold for memory usage | Triggers alarm when exceeded |
+
+## 3. Monitoring Settings Management
+
+### 3.1 Monitoring Configuration Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Name | Fuzzy query by monitoring name |
+| ID | Fuzzy query by monitoring ID |
+
+**Operation Steps:**
+
+1. Go to [System Settings] → [System Monitoring] → [Monitoring Settings]
+2. Set query conditions in the top query area
+3. Click [Query] button to get monitoring configuration list
+
+**Function Screenshot**:
+
+
+### 3.2 Add Monitoring Configuration
+
+**Operation Steps:**
+
+1. Click [Add] button
+2. Fill in monitoring configuration information
+3. Click [OK] to complete addition
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Monitoring ID | Unique identification code for monitoring | Yes |
+| Monitoring Name | Chinese name for monitoring | Yes |
+| IP Address | IP address of monitored server | Yes |
+| Port | Monitoring service port | Yes |
+| Refresh Interval | Data refresh interval (seconds) | Yes |
+| CPU Alarm Threshold | CPU usage alarm threshold (%) | Yes |
+| Disk Alarm Threshold | Disk usage alarm threshold (%) | Yes |
+| Memory Alarm Threshold | Memory usage alarm threshold (%) | Yes |
+| Version | Monitoring service version number | No |
+
+**[Tip]** Monitoring ID and monitoring name cannot be duplicated.
+
+**Function Screenshot**:
+
+
+### 3.3 Edit Monitoring Configuration
+
+**Operation Steps:**
+
+1. Click the configuration to edit in the monitoring list
+2. Modify configuration information
+3. Click [OK] to save changes
+
+**Function Screenshot**:
+
+
+### 3.4 Delete Monitoring Configuration
+
+**Operation Steps:**
+
+1. Select the configuration to delete in the monitoring list
+2. Click [Delete] button
+3. Click [OK] in the confirmation dialog
+
+**[Tip]** Supports batch deletion of multiple monitoring configurations.
+
+**Function Screenshot**:
+
+
+## 6. Notes
+
+**[Tip]** It is recommended to set alarm thresholds within a reasonable range to avoid overly frequent alarm notifications.
+
+**[Note]** Deleted monitoring configurations cannot be recovered. Please proceed with caution.
+
+**[Important]** Ensure the configured IP address and port are accessible; otherwise, monitoring data cannot be obtained.
\ No newline at end of file
diff --git a/en/system_settings/user_management.md b/en/system_settings/user_management.md
new file mode 100644
index 0000000..34d10f3
--- /dev/null
+++ b/en/system_settings/user_management.md
@@ -0,0 +1,286 @@
+# User Management
+
+## 1. Function Overview
+
+The User Management module is used to manage system user accounts and role permissions, enabling user CRUD operations, role assignment, password management, and permission configuration.
+
+**Core Functions:**
+
+- User Account Management: Create, edit, delete user accounts
+- User Status Control: Enable/disable user accounts
+- Role Management: Create, edit, delete roles (user groups)
+- Permission Assignment: Assign menu and API permissions to roles
+- Password Management: Change password, reset password
+
+**Function Screenshot**:
+
+
+## 2. Term Explanation
+
+#### 2.1.1 User Management Terms
+
+| Term | Definition | Description |
+|------|------------|-------------|
+| User Group/Role | Permission group to which user belongs | Users with the same role have the same permissions |
+| Pass ID | User's identification number | Used for access control and other scenarios |
+| Super Admin | System's highest permission role | Default has all menu permissions |
+
+## 3. Role Management
+
+### 3.1 Role List Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Status | Filter enabled or disabled roles |
+
+**Operation Steps:**
+
+1. Go to [System Settings] → [User Management] → [Role]
+2. Select status condition in the top query area
+3. Click [Query] button to get role list
+
+**Function Screenshot**:
+
+
+### 3.2 Add Role
+
+**Operation Steps:**
+
+1. Click [Add Role] button
+2. Fill in role name and description
+3. Set role status
+4. Click [OK] to complete addition
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Name | Role name, such as "Admin", "Regular User" | Yes |
+| Description | Detailed description of role | No |
+| Status | Enabled or disabled | Yes |
+
+**[Tip]** Role names cannot be duplicated.
+
+**Function Screenshot**:
+
+
+### 3.3 Edit Role
+
+**Operation Steps:**
+
+1. Click the role to edit in the role list
+2. Modify role information
+3. Click [OK] to save changes
+
+**Function Screenshot**:
+
+
+### 3.4 Delete Role
+
+**Operation Steps:**
+
+1. Find the role to delete in the role list
+2. Click [Delete] button
+3. Click [OK] in the confirmation dialog
+
+**[Important]** If there are users under the role, the role cannot be deleted.
+
+**Function Screenshot**:
+
+
+### 3.5 Permission Assignment
+
+**Operation Steps:**
+
+1. Click [Permission Configuration] button in the role list
+2. Select menus and APIs to assign in the permission configuration page
+3. Click [OK] to save permission configuration
+
+**[Tip]** Permission configuration will overwrite all existing permissions of the role.
+
+**Function Screenshot**:
+
+
+## 4. User Management
+
+### 4.1 User List Query
+
+**Query Conditions:**
+
+| Query Condition | Description |
+|----------------|-------------|
+| Account | Fuzzy query by username |
+| Name | Fuzzy query by nickname |
+| User Group | Filter by role |
+| Status | Filter enabled or disabled users |
+
+**Function Screenshot**:
+
+
+### 4.2 Add User
+
+**Operation Steps:**
+
+1. Click [Add User] button
+2. Fill in user information
+3. Set user group and status
+4. Click [OK] to complete addition
+
+**Field Description:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Account | User login account | Yes |
+| Name | User nickname or real name | Yes |
+| Pass ID | User's identification number | No |
+| Password | User login password | Yes |
+| Confirm Password | Enter password again for confirmation | Yes |
+| User Group | Select role to which user belongs | Yes |
+| Status | Enabled or disabled | Yes |
+
+**[Note]** The two password entries must be identical. Deleted or disabled user groups cannot be selected.
+
+**Function Screenshot**:
+
+
+### 4.3 Edit User
+
+**Operation Steps:**
+
+1. Click the user to edit in the user list
+2. Modify user information
+3. Click [OK] to save changes
+
+**[Note]** You cannot disable your own account.
+
+**Function Screenshot**:
+
+
+### 4.4 Delete User
+
+**Operation Steps:**
+
+1. Find the user to delete in the user list
+2. Click [Delete] button
+3. Click [OK] in the confirmation dialog
+
+**[Important]** You cannot delete your own account.
+
+**Function Screenshot**:
+
+
+### 4.5 Batch Operations
+
+**Supported Batch Operations:**
+
+- Batch Delete: Select multiple users and click [Batch Delete]
+- Batch Enable/Disable: Select multiple users and click [Batch Enable] or [Batch Disable]
+
+**Function Screenshot**:
+
+
+### 4.6 Password Management
+
+#### Change Password
+
+**Operation Steps:**
+
+1. Move mouse to username in the top right corner, click [Change Password] button in the dropdown
+2. Enter old password and new password
+3. Click [OK] to complete change
+
+**Function Screenshot**:
+
+
+#### Reset Password
+
+**Operation Steps:**
+
+1. Click [Reset Password] button in the user list
+2. Click [OK] in the confirmation dialog
+3. Password will be reset to default password "123456"
+
+**Function Screenshot**:
+
+
+### 4.7 User Data Import/Export
+
+#### Import User Data
+
+**Operation Steps:**
+
+1. Click [Download Import Template] to get the import template file
+2. Fill in user data according to template format
+3. Upload the filled Excel file
+4. Click [Import] to complete batch import
+
+**Import Template Fields:**
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| Account | User login account | Yes |
+| Name | User nickname | Yes |
+| Pass ID | User identification number | No |
+| Password | User password | Yes |
+| Status | Enabled or disabled | Yes |
+| User Group | Role name to which user belongs | Yes |
+
+**Function Screenshot**:
+
+
+
+#### Export User Data
+
+**Operation Steps:**
+
+1. Set query conditions to filter users to export
+2. Click [Export] button
+3. System generates export task in background
+4. Get export file in download management
+
+**Function Screenshot**:
+
+
+## 5. Operation Logic Flowchart
+
+```mermaid
+flowchart TD
+ A[User Management] --> B[Add User]
+ A --> C[Edit User]
+ A --> D[Delete User]
+ A --> E[Change Password]
+
+ B --> F{Validate Username Uniqueness}
+ F -->|Exists| G[Show Error]
+ F -->|Not Exists| H{Validate Password Consistency}
+ H -->|Inconsistent| I[Show Error]
+ H -->|Consistent| J{Validate Role Validity}
+ J -->|Invalid| K[Show Error]
+ J -->|Valid| L[Save User Data]
+
+ C --> M{Validate Username Uniqueness}
+ M -->|Duplicate| N[Show Error]
+ M -->|Unique| O{Disable Self?}
+ O -->|Yes| P[Show Error]
+ O -->|No| Q[Update User Data]
+
+ D --> R{Delete Self?}
+ R -->|Yes| S[Show Error]
+ R -->|No| T[Delete User and Reorder]
+
+ E --> U{Validate Password Consistency}
+ U -->|Inconsistent| V[Show Error]
+ U -->|Consistent| W{Same as Old Password?}
+ W -->|Same| X[Show Error]
+ W -->|Different| Y[Update Password]
+```
+
+## 6. Notes
+
+**[Important]** Users cannot delete or disable their own accounts.
+
+**[Note]** Before deleting or disabling a role, ensure there are no associated users under the role.
+
+**[Tip]** When importing user data, if the username already exists, that row of data will be skipped.
\ No newline at end of file