YUAN JIEYUAN JIE
AUTOMATED MATERIAL CONTROL SYSTEM

Every wafer,
on time.

YUAN JIE MCS (Material Control System) automates and governs every transport between OHT, AGV, stocker and tool on your floor. Millisecond dispatch decisions, standard SECS/GEM integration and a fully traceable transport history — so the line never stops waiting for a vehicle.

Read the architecture
Linux
Windows Server compatible
99.98%
Dispatch service uptime
< 80 ms
Per-job dispatch decision
DEPLOYED ACROSS THESE LINE TYPES
300mm Wafer Fab200mm Wafer FabAdvanced Packaging & Test
THE PROBLEM

The line rarely stops
because of the tool.

In most plants transport is reactive: the tool calls for material, a human dispatches, vehicles queue. By the time transport becomes the bottleneck, the capacity is already lost.

01
Transport orders live in five systems
MES, stocker controllers and AGV dispatch each keep their own truth. When something stalls, nobody can say where the carrier actually is.
02
Empty travel inflates cycle time
Fixed-route dispatch congests itself at peak. Empty OHT mileage routinely runs above thirty percent.
03
Recovery depends on who is on shift
A single track stall is cleared vehicle by vehicle. Mean time to recovery is hard to hold under ten minutes.
THE PRODUCT

One system for every movement on the floor.

Real-time dispatch engine
Scores congestion, priority and battery state continuously; picks the next vehicle in milliseconds.
DISPATCH
Route optimisation
Recomputes track paths on the fly, avoiding maintenance segments and peak crossings.
ROUTING
Standard equipment layer
SECS/GEM, OPC UA and custom TCP behind one consistent equipment abstraction.
INTEGRATION
Live transport monitor
Every vehicle, carrier and stocker slot on a single screen, built for the war-room display.
MONITOR
Automatic recovery
Stalled, timed-out and offline vehicles are isolated and their jobs re-dispatched.
RECOVERY
Transport analytics
Every move is traceable, with KPI and audit reporting out of the box.
ANALYTICS
THE ARCHITECTURE

The layer between MES and the floor.

MCS takes transport demand from MES above and drives OHT, AGV and stockers below. Equipment differences collapse into one abstraction, so changing vehicle vendor or tool model never reaches your upper systems.

SECS/GEMCORBAMQTTTIBCO RVSQL Server · Oracle
Dual-active controllers with zero-downtime failover
Multi-site deployment across buildings and floors
Full audit trail retained for every transport order
MES / ERPWork orders · demand
YUAN JIE MCSDispatch · schedule · history
OHT · AGV · STOCKERTransport equipment
EQUIPMENTTools · load ports
SPECIFICATION

Specification and deployment.

The full specification sheet and readiness checklist are available after a demo.

Operating system
Windows Server 2019+ · RHEL 8+ · CentOS Stream 9+
Database
Microsoft SQL Server · Oracle · PostgreSQL
Protocols
SECS/GEM (HSMS) · CORBA · MQTT · TIBCO RV
Single-site load
400 transport vehicles · 12,000 stocker slots
Languages
English · 繁體中文 · 简体中文
FROM LAYOUT TO LIVE

A rollout built around production.

Start with the traffic your floor already has. Each stage produces a practical decision point before the next one begins.

01
Map the flow
Review routes, fleet rules and the hand-offs between MES, stocker and equipment.
02
Simulate the change
Replay representative transport demand on your layout to surface conflicts before cutover.
03
Commission with confidence
Bring areas online in agreed phases, with a rollback path and an audit trail from day one.
COMMON STARTING POINTS

Meet the problem where it is.

Peak-hour congestion
Prioritise urgent lots while actively spreading traffic away from crowded crossings.
FLOW CONTROL
Mixed vehicle fleets
Bring OHT, AGV and stocker behaviour into one dispatch policy without changing upper systems.
ONE CONTROL LAYER
Traceability gaps
Give operations and engineering a shared transport record for every carrier and exception.
SHARED CONTEXT

Questions teams ask before a site survey.

What should we prepare for a first session?

A current layout, a typical day of transport orders and a high-level equipment list are enough to start the conversation.

Can MCS be introduced in phases?

Yes. The rollout can be scoped by building, line or equipment group so teams can validate each phase before expanding.

Does the system require replacing existing controllers?

No. MCS is designed to sit between MES and floor equipment, preserving the controllers and protocols already in use.

GET STARTED

See a dispatch run
before you talk rollout.

We simulate a day of transport volume on your actual layout and hand back a bottleneck analysis. Around 45 minutes.