xGRIDx
A tank farm from high above at dusk, a drone in the foreground
The Drone Designer bench: a parametric patrol drone on the design turntable
A patrol drone over a tank farm, the ground machines' working world
The Port Twin: a container ship at berth with cranes, a rail spur, container yard and tank farm in one interactive model

Machines / By the numbers

2Live design tools: Designer and Hangar
5Drone applications on the bench
20 inThe manway the railcar robot folds through (published)
0Man entries the railcar robot is designed to need

Every number on this page carries its kind: published, computed, or estimated. Nothing here is a measured result from built hardware, and the one machine that is still a design is labeled a design wherever it appears.

The family

Two of these machines you can use in your browser right now. The third exists as a design capture, dimensioned drawings, a full parts register, and two virtual test suites, and it is presented exactly that way. That honesty is the product: a machine record you can trust is a machine record a facility can plan around.

Air / Instance 01, live

The Drone Designer

Pick the application, the climate band, the wind and sealing targets, the mission range and endurance, and the sensor payload. The bench sizes the frame class, rotor count, propeller class and battery from published component assumptions, rebuilds the airframe on the turntable while you watch, and reprices the physics on the spec card: all-up weight, endurance, mission radius, thrust-to-weight, wind limit, and an estimated unit cost.

What comes out is not a picture. It is a named configuration record, the same record the facility twins consume as a patrol unit. Five applications, seven sensor payloads, four frame classes in quad or hex. Every figure is an estimate and is labeled one on the bench itself.

Live tool: open in your browser
The Drone Designer bench: a parametric patrol drone on the design turntable, its frame, rotors, battery and sensor modules generated from the designer inputs
The Port Twin: a container ship at berth with ship-to-shore cranes, a rail spur, container yard, tank farm and a refinery in one interactive model

The hangar / Port Twin, live

The Port Hangar

The hangar is where designed machines report for duty. Save a configuration on the bench and it spawns in the Port Twin: the same airframe, the same sensor fit, flying patrol over a working terminal model where a container ship discharges to railcars and a truck, a products tanker flows through the tank farm to a connected refinery, and a command center runs the whole operation.

This is the design loop closed in public: design a machine, hand the twin its record, watch it work. The port is a concept demonstration and every value on it is simulated and labeled as such.

Live twin: simulated data, labeled

Ground / Instance 02, design stage

The rail tank car cleaning robot.

Rail tank cars are still cleaned the hard way: a person climbs inside the car. This machine is designed to end that. It folds to pass through the car's own standard 20 inch manway, unfolds inside, and does the shoveling, spraying and scrubbing while the operator stays outside. The car is never cut, never modified: the only interfaces are the manway it was built with and the bottom outlet valve.

Design stage: design capture, drawings, register and simulation onlyNo prototype built

How it is designed to work

Four tension arms with wheels ride the shell in offset rings, extending and retracting to fit the car and to hold the machine wherever the work is. An algorithm sets arm force by task: more grip when the sprayer pushes back, more again when the shovels lean into heavy bottoms.

Two crescent shovels break up the bottoms and windrow them to the center sump and the bottom outlet, while the spray arm washes the same material ahead of the blades with steam, water and a d-limonene class solvent, so the outlet never clogs and one modest vacuum can serve the car. The scrub arm works the wall through a full circle behind them.

It sees without eyes. Optical cameras white out in steam, so awareness is layered: LiDAR for geometry, thermal imaging for the fluidization proof, radar for sludge depth through the fog, and air-purged cameras for the operator when visibility allows.

Safe by architecture. Power and intelligence stay outside on the trailer. Inside the car: fluid motors, a sealed manifold, fail-safe valves, and only low-energy intrinsically safe circuits, with trailer-side gas monitoring on a sample line and an automatic cutoff. That is the design intent, stated as intent.

The strategy is computed per car from the residue's safety data sheet, ambient conditions, the presence of a liner, the tank metal, and the disposal plan: the platform's chemistry recipe engine and steam sizing work, fed live by the machine's own sensors. Best job, least money, fastest, safest, in that order.

Dimensioned design drawing of the rail tank car cleaning robot in its folded configuration: an 18.2 inch maximum folded package, 16 inch sealed body, four folded tension arms with 8 inch wheels, folded scrub arm, sprayer wrist and nozzle bar, and two crescent shovel blades, with the deployment sequence through a 20 inch manway
A drawing, not a photograph. The folded configuration sheet, Rev 0.3, drawn from the fold specification. No machine has been built; this sheet is the design.

The design record, with its kinds labeled

These are the numbers the design currently stands on. Each one names where it came from. When the first car is instrumented, measured values replace the computed ones, and the record will say so.

Spec strip / Railcar cleaning robot, design values

Entry
Standard 20 in manway (published: TrinityRail and ARI manufacturer spec sheets; the federal floor is 18 in under 49 CFR 179.100-12)
Folded package
18.2 in maximum diameter, 74 in long (computed: virtual test suite v0.2, fold test S1)
Body
16 in sealed capsule; manifold, fluid motors and sensors inside; no battery, no computer inside (design specification)
Tension arms
4 arms in offset rings, 8 in wheels, 2.50 x 0.250 in arm tube (computed: structure test S4, safety factor 2.1 on yield)
Shovel blades
Two 22 in crescents, edge curved to the shell radius, 1 in dish (computed: winner of a 144 variant shovel simulation)
Scrub arm
58 in telescoping reach, full circle slew (computed: coverage test S2)
Sensing
Scanning LiDAR, thermal camera, radar sludge depth, air-purged body cameras (design specification)
Steam plant
Sioux SF-50 class, 2.0M BTU, 1,725 lb/hr steam (published: manufacturer figures)
Field spread
One 38 ft aluminum gooseneck trailer between the cars plus one support pickup, about 25,330 lb gross combination weight, crew of 3, 150 ft service runs (computed: minimum spread design, Rev 0.3)
Parts register
174 line items across 14 assemblies, robots, umbilicals, trailer, steam, vacuum, control, safety and both trucks (computed: system bill of materials register)
Cycle estimate
About 184 minutes of robot-active time per car on pre-softened bottoms, one operator, zero man entry (computed: cycle simulation S8; an estimate from a model, not a measurement)
Status
Design stage. No prototype, no production unit, nothing for sale, and no performance figure on this page was measured on a real car.
Dimensioned layout drawing of the minimum field spread: one 38 ft gooseneck trailer parked between two rail tank cars, davits and guide cones on both manways, robots inside the cars, 150 ft service runs, and a support pickup, drawn from the system bill of materials
The outside system, drawn from the same register. One trailer serves two cars at once; the davit and guide cone kit travels car to car on the support pickup. Computed layout, minimum spread Rev 0.3.

What design stage means here

It means the design capture, the dimensioned drawings, the 174 item register, and two rounds of virtual testing exist, and nothing else does. There is no prototype to photograph, so this page shows drawings. There is no CAD release being claimed as built hardware. The honest next steps are the ones the design record itself names: instrument the first car, replace the model's anchored assumptions with measurements, and let the fold, force and thermal numbers earn their way from computed to measured.

The same record discipline that runs the twins runs this machine: every claim carries its kind, and the kind only upgrades on evidence.

The studio / How a machine gets designed here

Bench, simulation, twin. In that order.

1. Design on the bench

Parametric first: dimensions are parameters, not pictures. Change the mission and the machine resizes itself, in the open, with its assumptions showing. The Drone Designer is this step, live.

2. Test in simulation

Virtual test suites run the failure modes before metal does: fold clearance, force balance, thermal soak, coverage, cycle time. The railcar robot has two suites on its record, and they corrected the design twice.

3. Spawn into the twin

The output is a configuration record the facility twin can consume, so the machine joins the fleet it will serve before it exists. Designer to Port Hangar is this step, live.

Keep reading

Start / One door

Bring us a machine problem.

A job your crews should not have to enter, climb, or guess at. Tell us what the work is and we will show you the machine record it starts with.

Start a conversation