Planner
Schedule work orders by delivery date, priority, line, and shift, identify overload, idle time, and unestimated tasks.
Focus: delivery / priority / capacity
Production Line MES · Planning and Execution
Production planning and production line task execution
Based on product versions and process snapshots, through work orders, production scheduling, production capacity inspection and supervisor acceptance, orders are converted into work views used by planners, supervisors and operators.
Product and process versionsWork Order LifecycleScheduling and capacityWorkstation queues
From planning to execution
One work order, three types of role views
Planners, supervisors and operators work together according to the status of the same work order, and each view the corresponding tasks and production information.
Workshop Supervisor
Accept work orders, understand line status, work order progress, bottlenecks, and on-site exceptions, coordinate resources to resume production.
Focus: progress / load / exceptionsWorkstation Operator
Pick tasks from current line or workstation queues, follow steps to view instructions, start execution, report work, and submit issues.
Focus: Current process / quantity / guidanceWork order downstream path
From master data preparation to on-site reporting
Define process
Product type, release version, steps, workstation, work instructions, and BOM.
Create work order
Select product version, fill in planned quantity, production line, delivery date, and customer info.
Schedule check
Arrange date, shifts, and priorities, matching with production line and team available capacity.
Accept assignment
Supervisor reviews the work order, allows batch creation, and moves it into the production queue.
Workstation execution
Operator starts steps, checks ESOP, records output and anomalies.
Product / Process
Execute by version and process snapshot
A product version fixes one executable process path, including step sequence, workstations, instructions, checklist, and BOM. When a work order is created, a process snapshot is formed, and later template changes won’t silently rewrite orders in production.
- Product types and released product versions
- Fixed, alternative, or parallel workstation resources
- Standard duration, work instructions, and checklist
Scheduling / Capacity
Unified view of priority and planned load
Supports weekly, daily, hourly and monthly views, and arranges work orders to production lines, shifts and time periods. The planned load is compared with the available working hours of the team, indicating overload, no shifts and unestimated working hours.
- Backlog pool and drag-and-drop adjustments
- Check production line, team, and maintenance downtime load
- Plan changes retain operator, time, and content
On-site execution boundaries
Make workstations handle only the actions they’re supposed to
Execution entry is determined by production organization and permissions, supporting both line collaboration and routing within the line.
Execute collaboratively by production line
Steps without a specified workstation are completed collaboratively by operators with that line’s permission, suitable for line-managed scenarios without distinguishing workstations.
- Line permissions are the basis for accessing tasks
- Batch, steps, and production quantity are recorded uniformly
- On-site status and planned progress are synchronized in real time
Distributed by workstation
Once a step assigns a workstation, the system can filter queues by operator-bound workstations and limit execution, suitable for clear equipment and role responsibility lines.
- Step workstations determine production location
- Operator binding determines executable scope
- Alternative or parallel resource pools support flexible scheduling
Key control points
Plans can be adjusted, production facts cannot be silently overwritten
Produce only after acceptance
Pending work orders must be accepted by a supervisor before any batch can be created; the review cannot be bypassed.
Lock the route after starting work
Once batches or work reports are generated, the production line, workstations, and process snapshots are protected.
Quantity uses the event ledger
Manual Production Reporting, machine counting and correction events are uniformly summarized, and the quantity is checked by event.
Changes go through controlled requests
When changes in quantity, delivery, or other facts are needed, reasons, approvals, and effective records are kept.