Deployment hubs
Scale by connecting verified units—not by hiding one larger box.
A hub coordinates multiple named trains or process cells through engineered shared infrastructure. Capacity, isolation, access, utilities and common-mode risks remain part of the site basis.
Why hubs matter
Add capacity in controlled increments.
Hub architecture can support phased capacity, shared services and different qualified chemistry configurations while preserving named train boundaries.
Scaling by connection
Add verified trains only after shared and per-train duties are capacity-checked.
Relocation logic
Transportable elements may be relocated where lifting, cleaning, logistics and the receiving site are engineered.
Different chemistries
Named trains can carry different released configurations without treating shared headers as universal.
Serviceability
Access, isolation, spares and lifecycle work are explicit design functions—not afterthoughts.
Number-up topology
Per-train functions above. Shared functions only after verification.
The hub route retains feed identity, train identity, controlled separation and named product/residual receivers.
Hub maturity
The evidence gate grows with the node.
| Stage | Process capacity | Shared services | Site integration | Evidence gate |
|---|---|---|---|---|
| Initial deployment | Named validated train(s) | Limited sharing | Defined utility and site interfaces | G2–G4 |
| Expanded node | Additional verified trains | Shared services where capacity exists | Common-mode review | G1 / G2 update |
| Hub | Multiple coordinated trains / cells | Engineered shared infrastructure | Full isolation, access and emergency basis | Named site acceptance |
| Hub form | Best fit | Primary design question |
|---|---|---|
| Single node | One source and one or more verified trains | Which services can safely be shared? |
| Linear expansion | Phased trains along a service corridor | How are isolation and future tie-ins controlled? |
| Cluster | Multiple process families at one site | How are chemistry, residual and utility interfaces segregated? |
| Regional network | Several sites with shared support | Which functions remain local and which can be coordinated remotely? |
Configure a node
Navigator can estimate the first module count and budget basis.
The result is a preliminary screening output. Site integration, shared services and final capacity remain outside the €1 million-per-module starting assumption.
