grabowski
9ed51f4b22
Deploy test site / deploy (push) Successful in 51s
New page docs/factory-console.html (site /demos/factory/): the factory application of digital-factory.md on a simulated plant day, with a switch to the customer portal of the same orders. Factory console (sidebar: Floor, Orders, Quality, Lab, Metal, Ledger): - floor: five presses of the launch fleet (two Newbilt Duplex systems, one Classic) with the mounted order, live good / rejected counters, stamper plays against life, cycle time and steam; KPIs for the day; live optical inspection stream with record keys; alerts (stops, lab holds, stampers near end of life, listening reviews, long gate waits); stations (cutting, galvanics, stamper prep, lab, packing); orders by stage; good records per day - orders list with stage filters and search; order detail with stage track, approvals, metal genealogy and stamper metrology, press run telemetry, compound lot certificate, rejects by reason, audio samples, packing and shipping, and the order's events - press detail with telemetry sparklines; quality (rejects by reason, yield per press, audio comparison); lab (compound lots with results against illustrative limits, one lot on hold with re-dry and retest, regrind batches, hoppers); metal (baths, mounted stampers, metrology, archive); hash-chained event log Customer portal (four demo customers: pressing now, waiting to approve the test pressing, in plating, delivered): progress through every step and the three gates, copies pressed so far with the latest copies and their record keys, approving the test pressing books the press slot (greedy plan of the queue gives the start time and press), and a quality report that fills in step by step: files, lacquers, metal parts with metrology, test pressings, the compound lot's lab results, pressing and inspection, listening checks, packing. Simulation: 60 days warmed up at load (about 0.7 s), then 1x to 3600x. Stages and durations from the production timeline, Newbilt cycle times, two shifts 06:00 to 22:00, unplanned stops, stamper life 1,000 to 2,000 plays, audio sampling first-off plus about 1 in 50 (1 in 25 near end of life), compound lots through the lab gate and release test pressing. All orders, values and IDs are simulated; limits are illustrative. Linked from digital-factory.md (the factory application), traceability.md (customer-facing view), the README and the landing page.
4.1 KiB
4.1 KiB
Process Logging and Traceability
Every step of production is logged continuously, so that every record is traceable end to end for the customer. This is a set requirement, and it is the core specification for the factory software this repository will eventually host.
It is also the part of the plan the industry responds to. At Making Vinyl Europe 2026 most people the team talked to were strongly interested in it, and Sibert's representative named it as a reason to work with a newcomer he would otherwise have advised against building a plant; buildfor.life's development and data work settled the question for him (see the exhibitor briefing).
What a customer can trace
For any order, the customer can follow the full chain:
- Audio intake: file received, checksums, versions, who handled it, approval trail
- Mastering: session log, engineer, settings, customer approvals
- Cutting: lacquer IDs, lathe parameters, stylus used, inspection result
- Galvanics: silvering and plating batch IDs, bath chemistry logs, father/mother/stamper genealogy (which stamper came from which mother from which father), or the external stamper supplier and batch if bridged
- Pressing: press ID, operator, shift, mold and stamper IDs, cycle parameters (temperatures, pressures, cycle times), PVC compound lot and virgin/recycled mix, label lot
- Quality control: test pressing approvals, inspection results, reject counts and reasons (the automated instrument layers feeding this are specified in quality automation)
- Finishing and packaging: trimming, sleeving, carton lot, packaging partner batch
- Fulfillment: warehouse location, shipment or dropshipping consignment, carrier tracking per end customer
Principles
- Log at the source: machine data comes from the machine (the presses and the plating rectifiers expose PLC data; the AD12 supports remote monitoring), not from manual transcription. Manual steps get simple operator check-ins, not paperwork.
- Batch and genealogy first: every physical artifact (lacquer, father, mother, stamper, press run, box) gets an ID, and every ID knows its parents. A customer complaint about one record resolves to a specific stamper, press, shift, and compound lot.
- Environment attached: the whole-factory HVAC monitoring (temperature, humidity, PM per zone) is logged on the same timeline, so any production window can be correlated with plant conditions.
- Immutable and retained: logs are append-only and retained for the life of the customer relationship; stamper genealogy is retained as long as the archive holds the metal parts.
- Customer-facing view: traceability is a product feature, not an internal file. Customers get a per-order view (portal or report) covering the chain above, without exposing other customers' data. The investor demo make a record shows the per-copy version a fan reaches from the code printed on the sleeve, the record passport: stamper, press, cycle time and side, with the stage dates and the inspection result (IDs simulated). The per-order view itself is shown in the factory console and order status demo: the customer follows the order through the gates, sees how many copies are pressed so far and the results of every inspection station, from the lab certificate of the compound lot to the listening checks.
Open design work
- Data model for batch genealogy across all eight steps
- Which PLC/machine interfaces each vendor exposes (ask Newbilt, Pheenix Alpha, and Digital Matrix during procurement, before purchase)
- Retention, backup, and PDPA handling for operator-linked records
- Whether test-pressing approval workflows live in the same system from day one
This system should be specified alongside equipment procurement: machine data access is a purchasing requirement, not an afterthought. The systems that implement this specification (machines, networks, collectors, database, application) are planned in digital-factory.md.