OpenCore MES Try the demo
The problem

A real flow is never a straight list of steps.

A test segment run at room and again hot, two minutes allowed between the saw and die attach, a lot measured only when none was in the last hour, a split that must follow its parent, a lot moved to the fast route halfway: in most systems each one is a customisation, written by the vendor, proved by nobody.

Solution

Drawn on one canvas, kept to the letter.

Each step says which transactions it offers, on which tools, with which settings. Everything else is refused, in words.

The Flow designer's canvas of a semiconductor assembly and test line: receiving, a decision on the lot's date, the saw, a sampling decision, SPC, die attach, wire bonding, mold, trim, a test segment run at room and again hot, QA, packaging, shipped; two dotted time links between steps
An assembly and test line: decisions, a segment run twice, two time links, on one canvas.
The Flow designer's canvas of a semiconductor assembly and test lineAn assembly and test line: decisions, a segment run twice, two time links, on one canvas.

Steps that offer

Move in, Track in, Track out, Move out: each only where its step allows it, on a tool of that step's process. The wrong tool is refused by name.

Decisions that read the floor

A wire holds on the lot, on today's date, or on a count: how many readings the saw had in the last hour decides whether this lot is measured.

Settings the step owns

Tracked in by itself, moved out by itself, the limits for a reading, a certified operator only: read by the transaction at that step, written nowhere else.

Solution

A segment drawn once, run wherever it is needed.

A test insertion is a route of its own. The main route runs it at room, then hot, passing each run what it is for.

  1. Trim and form

    Moves the lot out by itself; a minute to cool after mold first.

  2. Room test

    The test segment, passed “room”.

  3. Hot test?

    A decision on the product.

  4. Hot test

    The same segment again, passed “hot”; then QA, packaging, shipped.

  • Passed a value each timeThe step's transactions read what the segment was passed and the route's own values, as one scope; a tag records which insertion.
  • Lots that start insideA lot made at a segment's step starts there, the route waiting at its sub flow. A lot split off follows the lot it came from, hot pass included.
  • One fix, every routeA segment changed is one change, followed by every route that runs it; a lot already inside finishes on the version it entered.
  • Ended from aboveThe route's end condition is read on every level: shipped, merged or scrapped, nothing is sent on.
Solution

Time between two steps, kept.

A queue time is a link drawn between two steps: a warning, a maximum, a minimum, and what the route does when it is passed.

  • Opened and closed by the lotFrom leaving the saw to Track in at die attach: two minutes, warned at one.
  • Past the maximum, the route actsIt runs the transaction you chose, as itself: the lot held, Quality told, audited as the route.
  • Refused in wordsTrack in says how long the lot waited and the limit. A waiver you design, such as a field Quality sets, lets it through.
  • No sooner thanA minute to cool after mold before trim tracks in.
  • Seen where it mattersOn the lot's page, how much is left or by how much it is over; on the map, the link in the colour of its state.
A lot's page: its whole way along the main route, from Start through the room test, the hot test decision, QA and packaging to Shipped; the SPC out-of-control plan it set off, closed; its fields read only, changed through transactions
A lot's page: its whole way on the route, and the plan it set off.
A lot's page with its whole way along the main routeA lot's page: its whole way on the route, and the plan it set off.
Solution

A plan for what goes wrong, from the bell.

A reading out of limits, a tool due its maintenance, the third lot of an item within the hour: each sets a plan off.

Set off by a write, a date or a count

A reading written out of limits, a maintenance date arrived, a count of records within the last minutes.

Each step waits for its people

An input screen for Quality, a decision for Engineering, an acknowledgement for Production, a sub flow that hands its finding back: each from the bell.

Ends that act

An end runs a script as the plan: the lot scrapped, the tool back on the line; a lot's route ends with that write.

Drawn: The SPC out-of-control plan

Solution

Lots that join, leave, split, merge, and are held.

The route follows the lot, whatever wrote it: a form, an import, a plan, a transaction.

  • Taken up on a writeA lot imported later, returned, or made at any step is taken up where its step says, inside a segment too.
  • Moved to another routeEngineering sets its route: the main run ends there, the fast route takes the lot up at that step.
  • Holds as recordsA future hold on every lot at mold, applied as each one leaves by the route's every-step transaction; released by Quality from its page.
  • Batches, gatedOne lot scanned tags every waiting lot of its product on the route. One standing where that step does not allow it refuses the run, by name.
Solution

Proved the way a plant uses it.

A semiconductor assembly and test line ships with the code as a model file and runs in the test pipeline: a real browser works every move through the screens, no service called for one.

65 stepsthrough the screens: people from a file, the model executed, lots started, every move a form
3 lots, 2 shiftsa night crew and a day crew, a handover between them, every move stamped with its shift
Every scenario firsteach transaction and route tried in a sandbox before the line went live

On every push, in the test pipeline. How changes go live

Draw yours.

A route, a segment, a time link, a plan: each approved like every other change, and live without a restart.