Assembling plants

A plant is a plant.json: a list of items (components placed in space) and lines (pipe joining one item's port to another's). <Plant> renders it, and deck-twin validate validates it.

{
  "name": "HP separation",
  "items": [
    { "tag": "DECK-1", "component": "deck-module", "position": [0, 0, 0], "props": { "length": 30, "width": 20 } },
    { "tag": "V-100", "component": "horizontal-separator", "position": [-6, 0, -3], "props": { "service": "3-phase", "pressure": 40 } },
    { "tag": "P-101A", "component": "centrifugal-pump", "position": [6, 0, 4], "rotation": 180 }
  ],
  "lines": [
    {
      "tag": "6\"-PO-1001-D6A-N",
      "from": "V-100.liquid",
      "to": "P-101A.suction",
      "service": "oil",
      "inline": [{ "component": "gate-valve", "at": 0.25 }, { "component": "y-strainer", "at": 0.75 }]
    }
  ]
}

This is the only plant format the registry and the CLI use. It is built from registry components, so an agent should take names, props and port ids from the CLI, never from memory. The JSON Schema at /r/plant.schema.json carries the full list of component names, and deck-twin validate is the final gate.

Coordinates

Items

Lines

Line numbers are data

When a line's tag follows SIZE"-SERVICE-SEQ-CLASS-INSULATION, the assembler reads it. For 8"-PG-2101-D6A-N:

Explicit fields on the line override the tag. Sizes also work as 1-1/2" or DN200. Mismatches between the tag and the nozzle are reported. Service codes and the class-digit convention are in assembly/linetag.ts; edit them to match your project's line-numbering procedure.

The router leaves each flange straight along the port's axis for 0.6 m. It then climbs or drops to the run elevation, runs along X then Z (or Z then X), and drops into the other flange. Each corner gets a B16.9 long-radius elbow. Each end gets a gasket, a mating weld-neck flange and studs, sized to that end's nozzle. When the two ends differ in size, a B16.9 concentric reducer goes in before the far end. Inline items cut the pipe, with a flange pair on each side; wafer bodies (butterfly, dual-plate check) are clamped by through-bolts.

Rendering

import { Plant, type ComponentMap } from './components/deck-twin/assembly/plant'
import * as horizontalSeparator from './components/deck-twin/vessels/horizontal-separator'
import * as centrifugalPump from './components/deck-twin/rotating/centrifugal-pump'
import * as gateValve from './components/deck-twin/valves/gate-valve'
import spec from './plant.json'

const components: ComponentMap = {
  'horizontal-separator': horizontalSeparator,
  'centrifugal-pump': centrifugalPump,
  'gate-valve': gateValve,
}

<Plant spec={spec} components={components} labels onReport={(issues) => console.table(issues)} />

npx deck-twin assemble plant.json writes this file for you, as src/PlantScene.tsx, with every import in place.

Offshore: show the sea

Add "sea": { "level": -14, "depth": 50 } to the plant. <Plant> draws the animated ocean component at mean sea level, with foam rings where the jacket legs cross the surface, and a seabed depth metres below it. The water is slightly transparent, so the jacket shows through it. For a jacket at y = 0, level is minus its airGap.

Pass night to <Plant> for darker water. Add the sky component for a matching day or night sky, lights and haze. The sea is visual only: it is not part of the checks. See the offshore water injection example, which has a Studio / Day / Night switch.

Checks

onReport receives these issues:

The playground shows the same report for any pasted plant.json.

Layout rules of thumb

• Clearance. Leave at least 1 m between equipment for access, and 1.5–3 m in front of pumps and exchangers for maintenance (tube-bundle pulls need the bundle length clear).
• Flow direction. Wells and inlet sit upstream (west), then separation, then treatment and export (east). Put utilities and power at one end, and accommodation away from hydrocarbons.
• Pumps. Put them close to and below their suction vessel, so the suction line is short and drains towards the pump.
• Pipe racks. Run them along the module's long axis at 4–6 m. Route long lines over the rack with via, and set supports: false.
• Decks. A typical deck stack is a cellar deck at y = 0, the production deck at y = 8–10, and the weather deck 8–10 m above that. Put deck-module items at those heights, and put the equipment on each deck at the same y.
• Cranes. Pedestal cranes go at deck edges and corners, with the laydown area within the boom radius.

See Examples for complete plants.