OE/04 · Space and closed-loop life support
ORBIS
Margin to a life-critical bound, in a loop with nowhere to vent and no resupply.
What it estimates
The reading you have is not the thing that fails. Scrubbing capacity is, and nothing in the cabin reports it.
Cabin carbon dioxide stays flat while the scrubber works harder to hold it there. The effort is invisible and only the result shows. The engine estimates the effort, so lost margin appears while there is still margin left to spend.
Runs on your instruments
No new hardware, no install, no change to how the plant is operated. If it needed you to add sensors, the model would not be doing its job.
Read only
It estimates and forecasts. It connects to no control loop and changes no set point, which is why evaluating it puts nothing at risk.
Every number carries a band
Each state comes with its uncertainty and each forecast with its probability. A number with no band is not a measurement.
Your data stays yours
Evaluation files are deleted afterwards, and nothing becomes anyone else's training set without an agreement that says so.
Where it runs
Space and closed-loop life support.
Partial pressures and the hours of margin to a life-critical bound, in a loop with no resupply and no exit.
Configurations you can run right now
Each of these is set up in the live demo. Pick the instruments you actually have, set what is on the line, and run it.
Fields this covers
- Bioregenerative life support (BLSS)
- Environmental control and life support (ECLSS)
- Habitat atmosphere management
- Carbon dioxide scrubbing and revitalisation
- Submarine and hyperbaric atmospheres
- Analogue habitat operations
The method
Three steps. Only the first one changes.
Reconstruct the biology
Write down how the system actually behaves: what reacts with what, how fast, what moves where, what the organisms take up and how the population shifts. This is the only step that changes between an oyster hatchery and a space habitat, and it is where most of our work goes.
Decipher backwards
The estimator runs that model against the sensors already on site and works out the things nothing measures directly, with an honest error bar, every cycle.
Forecast forward
Take that state and run it forward under whatever you are planning to do next. This is where the warning hours come from. You get a forecast with a confidence attached to it, not a red light.
Steps two and three are identical across every Orbital Ecology product. Step one is the process model written for this domain, and it is where the domain work lives.
The record
What has been tested here.
| Status | What was tested | Result |
|---|---|---|
| Complete | SIMOC habitat simulator, 60 runs, 7 configurations, Biosphere 2 and Mars models | 98 percent of breaches identified pre-event. Median lead 11 h, max 168. False alarm 11 percent. |
Every completed result is reproducible against a published benchmark or a held-out operating record. The full record for all four products is on the home page.
The rest
One engine, four front doors.
Evaluation
Send one export. We will tell you what it was trying to say.
Send us an export you already keep. We run it blind, with the outcome window hidden from us, then tell you how many hours of warning you would have had, and how often we would have cried wolf.
- No connection to any live system. No change to any control loop.
- No fee, and the file is deleted afterwards.
- You keep the full workings, including where we would have missed.
Validated against the reference models these fields use, and backtested on real commercial operating history. The engine only reads. It estimates and forecasts, and changes nothing in your plant.