3D Life Support Rack Maintenance

Rack Maintenance

Maintenance interval 14 d

Degradation rate 0.06 /d

Crew-hours per visit 2.5 h

Simulation speed 4 d/s

Avg. component health

–

Elapsed time

–

Cumulative crew-hours

–

Near-failure events

–

How it works

Four modules sit on the rack, each wearing continuously since its last service — a smooth exponential decay, not a random breakdown. When the schedule ticks, a service drone travels down the rack and touches each module in turn: on contact the module's panel wipes from grimy back to clean and its wear timer resets to zero. That single trip costs crew-hours whether the modules needed it badly or barely at all.

health(t) = 100 · e^(−rate · Δt)
Δt = time since drone last serviced this module
on schedule tick → drone visits each module → health = 100, crew_hours += cost

Maintenance interval — days between the drone's rounds down the rack. Longer intervals save crew-hours but let panels darken further first.
Degradation rate — how fast grime/wear accumulates; watch the panel colour drift from clean to rust between visits.
Crew-hours per visit — cost paid per module, every round trip, regardless of how worn it was.
Near-failure events — a module's warning beacon turns red whenever its health drops below 25% before the drone reaches it.

Compare against the 2D scheduler: same underlying wear-and-reset math, but here servicing is a physical, sequential act — the drone visits modules one at a time rather than resetting the whole rack instantly, so a long rack or a short interval can leave the drone still finishing one round when the next is already due.

O2 Generator CO2 Scrubber Water Recycler Air Filter Beacon = below 25%

⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.