Production Core

NorthStar Motors · Windsor Assembly Plant, Ontario

Shift —
Docs API Flows
connecting

Production lines

OEE = availability × performance × quality

Shift trend

detail & rolled-up shifts

Live event feed

0 events

    Andon board & stoppages

    Feeder buffers

    Maintenance in progress

     

    Preventive maintenance due

    cycles since last service vs the MTBF-derived interval

    Station grid — click a station to control it

    running idle starved blocked down stopped maintenance locked

    Work in progress

    vehicles on the floor right now

    Defect Pareto

    by code, this shift

    Open defects

    Recall analysis

    which vehicles contain a suspect supplier lot, and where are they now

    A supplier reports a bad batch. The question is not “did we use it” but which vehicles have it, and can we still stop them. Pick a lot below; the query runs against an index, so it answers across the whole build history in milliseconds.

    Vehicle genealogy

    the as-built record, sealed at release

    What this is

    A working Manufacturing Execution System for a vehicle assembly plant, built on Node-RED. Seven production lines and 43 stations — body shop, paint, door line, wheel & tire, sub-assembly, main assembly and end-of-line quality — with real domain rules behind them.

    What it actually enforces

    • Routing. A vehicle cannot skip a station. Attempts are rejected, not logged.
    • Quality gates. A unit carrying an open critical defect does not move, and cannot be released.
    • Genealogy. Every part is recorded with its supplier lot at the point of use. The record is append-only and sealed at release.
    • Single consumption. A serialised sub-assembly can be fitted to exactly one vehicle, ever.
    • VINs. Real ISO 3779 identifiers with valid check digits — they decode in any off-the-shelf VIN decoder.

    Where to look

    Node-RED flows → 13 tabs, 204 nodes, 7 custom nodes. Generated from a declarative plant spec. REST API (Swagger) → 83 operations. Try POST /trace/recall first. Line board → An HTML page served by the Node-RED flows themselves. Architecture notes → Why the domain is a library and the flows are the orchestration.

    Standards it follows

    ISA-95 / IEC 62264 plant hierarchy · ISO 22400-2 OEE and KPI definitions · ISO 3779 VIN structure · Six Big Losses downtime classification.