xGRIDx

Facility Room / Port Twin

One terminal. Ship to refinery, run as one machine.

This is a working concept twin of a representative Gulf Coast marine terminal, modeled the way xGRIDx models any facility: whole, in the open, with every system on one record. A container ship discharges to railcars and a truck that gates out. A products tanker offloads through the tank farm and down the pipeline to a connected refinery. Drones patrol the fence line and the stacks. A command center turns systems on and off and watches the pressures move. And the twin keeps score: every move metered, every idle minute priced, every optimization applied live.

Concept demonstration · Representative terminal · Simulated data Containers · Products · Rail · Truck · Pipeline Drones · Command center · Live optimization
The Port Twin: a container ship at berth with cranes, railcars, a tank farm and a refinery in one model

One continuous operation, live in the model: ship to crane to rail and truck, tanker to tank farm to refinery, drones overhead. Drag to orbit. Tap any component for its record.

Drone hangar

Drone hangar / Designed aircraft, flying the twin

Build it in the studio. Fly it here.

Every aircraft in this hangar is a design record from the Drone Designer, the first bench of the xGRIDx Machine Design Studio. Spawn a design and it joins the patrol as itself: its own frame, its own rotor count, and scan callouts that come from its own payload. A methane build reports methane, a thermal build reports heat, an inventory build counts the yard. The numbers on its card are the designer's estimates, carried into the twin unchanged.

Studio presets

Loading the studio presets…

Your designs

Import a design record

On patrol from the hangar

No designed aircraft flying yet. Spawn one above and it joins the watch.

Command center / The whole model, one panel

Run the terminal from here. The model answers.

Every switch below drives the twin above. Stop the transfer pumps and watch the line pressure fall off. Park the cranes and the move rate dies with them. This is what a watch floor sees when the facility and its record are the same thing.

Line pressure812 kPa
Product temp34.2 °C
Transfer flow1,180 m³/h
TK-104 level61.4 %
TANKER ARM PUMPS TANKS REFINERY SIMULATED FLOW PATH · LIVE STATE

Metering / The twin keeps score

Every move counted. Every idle minute priced.

The same state that animates the model meters it. Berth, cranes, yard, gate and line are read continuously, and the twin works the deltas: where time pools, where energy leaks, what a fix is worth before anyone spends on it. All values simulated, in time-lapse.

Berth occupancy92%Both berths working
Crane rate0Moves per hour, both cranes
Avg dwell41 minContainer, gate to rail
Throughput0Moves this watch
Energy / move38.5kWh per container move

Optimization / Findings, priced before you act

Finding 01

Crane 2 waits on the rail cut

Re-sequencing Crane 2 to finish Bay 4 before the rail cut closes removes a standing wait in every cycle. The twin applies it to the live model: cycle speed up, dwell down 6 minutes, $11 per move.

Finding 02

Gate arrivals bunch at the hour

Appointment smoothing spreads drayage arrivals across the watch. Queue at the OCR portals clears, turn time falls from 38 to 24 minutes, worth $7 per move in the model.

Finding 03

Transfer pumps run flat out against a throttled line

The VFD trim the twin recommends holds line pressure at setpoint instead of fighting the control valve: energy per move down 5.2 kWh, $4 per move, no throughput cost.

Watching

TK-104 ullage on the current receipt

At the present transfer rate the tank reaches its high-level watch band inside this watch. The twin has already flagged the switch to TK-105 in the staff app below. No action needed here; that is the point of a watch.

Economics / What the score is worth

Costs walk down. Margin walks up. Same model.

Cost per move$186Simulated · falls as findings are applied
Margin index21.4%Simulated operating margin on the move
Value of applied findings$0Per year at 1.2M moves · illustrative, from the deltas above

These are demonstration numbers from a simulated terminal, shown so the shape of the accounting is visible: the twin does not report savings after the fact, it prices a change before the change is made, then keeps the receipt.

xGRIDx Field
Meridian Terminal · Watch B · Simulated feed
Twin

Watch started. Both berths working, UAV patrol airborne.

✓Verify railcar seals, cut 1–3
✓Tank TK-104 gauge cross-check
Switch receipts to TK-105 at high band
Walk Berth 2 arm envelope before 14:00

The staff app: the twin in a pocket. Tasks, seals, levels and alerts, signed at the event.

The watch / People run this

The model is tireless. The team is the point.

A twin earns its keep in moments like this one: the watch that cleared a vessel early, beat the tide window, and knew it before the radios did. Planners, crane operators, marine coordinators, inspectors and the twin operators who keep the record honest: men and women who run terminals, backed by a model that never sleeps and never guesses quietly.

The terminal operations team celebrating a cleared vessel in the command center, the twin on the wall behind them
Watch operatorsMarine coordinators Crane + rail plannersInspectorsTwin operators

The offer / Port terminals, twinned whole

Your terminal, modeled the way this one is. Then run from it.

xGRIDx builds the twin from capture and records, connects the systems that already meter your berths, cranes, gates and lines, and keeps the model current under a Managed Operations watch. A pilot is one berth and one tank farm, six to twelve weeks, one link your whole team can open. This page is a concept demonstration with simulated data; a pilot twin is built from your facility and your numbers.