Orbital Compute Unit
An Orbital Compute Unit (OCU) is a standardized measure of how much useful computation a satellite can deliver per orbit, accounting for power constraints, eclipse fractions, thermal limits, and ground contact availability.Why OCUs exist — Satellite compute capacity is not a fixed number. It varies with orbit geometry, season, battery age, and thermal state. OCUs normalize this into a single comparable metric so you can plan workloads without modeling the physics yourself.
Bus Profiles
OCU computation starts with a bus profile — a standardized description of the satellite’s compute, power, and thermal capabilities. CAE includes 6 built-in bus classes.Auto-Detection with inferBusClass
If you don’t specify a bus class, CAE infers it from the satellite’s NORAD ID using orbital parameters and known catalog metadata:- Altitude and inclination narrow the platform category
- Radar cross-section (when available) estimates physical size
- Catalog metadata matches against known spacecraft databases
OCU Computation
The OCU model combines bus capabilities with orbital geometry to produce a per-orbit capacity estimate.Sunlit and Eclipse Hours
From the satellite’s current TLE, CAE propagates the orbit and computes:Confidence Model
OCU values carry a confidence score reflecting the quality of the input data:
Confidence is reported as a value between 0 and 1. Values above 0.8 are considered high-confidence.
Cost Model
Each OCU carries an estimated cost based on the bus class and orbital parameters:Limiting Resource
The OCU computation identifies which resource constrains capacity:power (eclipse battery budget), thermal (heat dissipation during sunlit compute), storage (on-board buffer for multi-pass transfers), contact (ground pass availability for data delivery).
negotiateOCU Algorithm
ThenegotiateOCU function runs a 4-phase algorithm to determine achievable OCU for a specific workload:
The negotiation accounts for workload-specific factors like checkpoint overhead, FEC requirements, and quality tier selection.
API Usage
Negotiate OCU for a Workload
Response
Get Bus Class Summary
Retrieve the reference profile for a bus class without specifying a satellite:Response
Negotiate and Summary Parameters
Console Integration
The Console displays an OCU Capacity card in the sidebar of the asset detail page:- OCU/orbit and OCU/day values with confidence indicator
- Bus class label (with “inferred” badge when auto-detected)
- Limiting resource bar chart showing utilization per resource
- Sunlit/eclipse breakdown as a ring chart
- Cost estimate per orbit
Hazard Prediction
Predictive checkpointing around orbital hazards
CAE Overview
Constraint-Aware Execution fundamentals

