Insights / 06
Capture is a fleet discipline.
Anyone can fly a drone once. Capture that a turnaround, an inspection program or a custody record can depend on is a system: aircraft, stations, software and rules, designed together. That system is LIIVE SPACE.
Status, stated plainly
LIIVE SPACE is a designed system, and we label it that way everywhere on this site. It exists today as a complete design package: a master operating blueprint, system requirements and an interface control document, a requirements traceability register, and canonical data schemas with an initial API specification. It is the package a serious aerospace or robotics manufacturer can quote and build against. The capture work our twins run on today flows through the shipped reality capture pipeline: terrestrial scanning, photogrammetry and partner capture.
The aircraft family
Three airframes share one operating system. The A1 EVENT is built for venues and media: a ducted design for working around people and productions. The A2 SENTINEL, RESCUE and RESPONSE aircraft carry radiometric thermal and electro-optical payloads, resilient command links, and navigation that holds up when GPS does not: RTK, UWB, visual inertial odometry, LiDAR and radar. The A3 works corridors and industrial sites: rail, emissions and critical infrastructure runs.
NEST: the station is the system
Aircraft are the easy part. The NEST autonomous docking and charging station is what makes a fleet a discipline instead of a hobby: autonomous recovery and mechanical capture, data offload, automated inspection, charging and battery swap, quarantine and lockout states, all run as an explicit state machine. Revision one is deliberately honest about its limits: the NEST inspects and turns aircraft around; it does not claim robotic repair.
COMMAND and the safety case
LIIVE COMMAND integrates the fleet into the systems sites already run: video management, access control, fire systems, CAD and 911, GIS, security tooling and maintenance systems. Missions are requested through schemas (Mission, Evidence, Maintenance) designed so the twin platform and other systems can task capture without ever touching motor control or bypassing the aviation safety layer.
The regulatory homework is in the package: Part 89 Remote ID, operations over people, BVLOS waiver paths, the stadium restriction. Methane work is specified against EPA frameworks, with the honest caveat that drone measurements are not automatically compliance grade.
Field facts
- Status
- Designed: full blueprint, ICD, traceability register, schemas and API spec
- Aircraft
- A1 EVENT (venues), A2 SENTINEL / RESCUE / RESPONSE, A3 corridor and industrial
- NEST
- Docking, charging, inspection, data offload, quarantine and lockout as a state machine
- Rules carried
- Part 89 Remote ID, over-people rules, BVLOS waiver paths, stadium restrictions
Keep reading
Start / One door
Bring us an asset.
A plant, a terminal, a building, a venue. If it exists in the world, it belongs in the system. Tell us what you operate and we will show you the twin.
Start a conversation