Industrialization
Phase 02The order is placed, and the product is industrialized once: the structured package becomes a versioned production blueprint — stations, tooling, parameters, quality gates — validated in simulation before anything physical is set up. At the higher tiers, the blueprint is the asset that makes production portable.
Order → package → blueprint v1
What was quoted is what is ordered: a production tier and a quality contract. Which floor actually runs the work is decided later, by routing. That separation is deliberate — it is what keeps the capacity configurable.
This is where the full package is required — the sound BOM, the drawings for the things that need them, and the suggested assembly, detailed below. The thesis calls the BOM a strategic routing document: it determines not only what a product costs, but where it should be produced, which components dominate shipping cost, which suppliers must be close, and which production tier is economically justified.
Design-for-manufacturing analysis, tolerance stack-up, station design, fixture design, work instructions, quality gates — compiled into a versioned blueprint and run against a certified hub's reference model first, catching collisions, takt-time gaps, and missing tooling while they are still cheap to fix. Like software: written once, reviewed, validated, then released.
Three things, each shown by example
Everything downstream — the blueprint, the routing, the quality system — reads this package. The examples below follow one fictional product through all three parts.
A sound structure is required, because every downstream decision reads it: levels and subassemblies that reflect how the product actually comes apart; part numbers and revisions for every line; quantities, materials, and finishes; make-or-buy flags; approved alternates; and long-lead or critical components marked as such.
| Level | PN · Rev | Description | Qty | Material / finish | Source | Flags |
|---|---|---|---|---|---|---|
| 0 | EX-100 · C | Handheld inspection unit | 1 | — | assemble | — |
| 1 | EX-110 · B | Housing, machined | 1 | AL 6061 · anodized | make | drawing required |
| 2 | EX-111 · B | Seal, molded | 1 | Silicone | buy | alternate approved |
| 1 | EX-120 · D | Sensor module | 1 | — | buy | critical · long-lead |
| 1 | EX-130 · A | PCBA, main | 1 | FR-4 | buy | test spec required |
| 1 | EX-140 · A | Harness | 1 | — | make | — |
| 1 | EX-150 · B | Fastener kit | 1 | A2 stainless | buy | — |
Levels show how the product comes apart · every line carries a part number and revision · the flags column is what routing and industrialization read first.
Not every part needs a drawing pack, but specific things do: 2D drawings with tolerances for critical features, 3D models where geometry drives fixturing and robot access, interface and test specifications, and the quality requirements that will become inspection points.
The rule: a drawing where a feature is critical, a model where geometry drives tooling, a spec where a boundary must hold — and nothing where nothing is at stake.
The customer submits a proposed way to assemble the product: a sequence, an exploded view, whatever captures their intent. It is deliberately suggestive, never binding. The customer knows their product best; Moduloa's job is to know production. The suggestion enters as input, and industrialization turns it into a validated production flow — reviewed, risk-assessed, and released under change control. If the suggestion were binding, the blueprint and its validation discipline would collapse.
Suggestive, not binding — industrialization may reorder steps, split stations, or change fixturing. In the EX-100's case, validation kept the proposed order for v1 — and the first revision later moved seal seating from the bench into a cell. The validated flow that comes back is the blueprint, and it is under change control.
The blueprint — Layer 02 made real
The thesis treats the factory like software under version control: a proposed flow is a branch, the engineering change proposal is the pull request, engineering review is the code review, simulation is the CI pipeline, and release to the floor is the merge. The blueprint is what moves through that pipeline.
What has to be proven
Encoding process knowledge into a portable blueprint is the model's hardest claim — real factories hold tacit knowledge that resists being written down, and physical rollback is harder than software rollback. Whether a validated blueprint truly runs at a second certified hub without re-engineering is exactly what the register tracks: P-10 (validated production blueprints move between certified factories; portable production is commercially real). See the register →