One calendar for every machine.
Every autonomous capture on the portfolio — docked flights, robot shifts, inspection rounds — sits on one calendar under one set of rules. Every 6 h on a live corridor job, twice a day on a high-rise, Tuesday nights on a fit-out.
What it does
A capture cadence is a commitment, not a preference: a corridor job every 6 h, a tower flown at 06:00 and 15:00, a fit-out floor walked on Tuesday nights. Set it once per site and the fleet holds it — 12 million missions on the platform have run off this calendar.
Conflicts resolve before they cost a pass. A flight booked over a pour, two robots routed through the same stair core, a pad closed for a crane climb: the calendar reads the lookahead and the airspace notices, moves what it can move, and escalates the rest to a person by name with a deadline against it.
How it works
- 01
Set the cadence per site
Choose what flies or walks, how often, and in which window. Live earthworks usually runs every 6 h; a fit-out floor runs weekly. Cadence is a site setting, not a decision somebody makes again each morning.
- 02
Check it against the job
The calendar reads the 3-week lookahead, the pour and crane plan and the airspace notices, then flags any mission that would run into them days before the day arrives.
- 03
Publish and hold it
Every mission publishes to the flight log with its window, its machine and its outcome. Anything that does not fly escalates to a named human within 15 min — never to a queue nobody owns.
Spec
- CADENCE
- EVERY 6 H → WEEKLY
- SCOPE
- PORTFOLIO · ALL MACHINES
- CONFLICTS
- READ FROM LOOKAHEAD
- ESCALATION
- NAMED HUMAN · 15 MIN
12M
Missions run off this calendar