DRONE COMMAND CENTREFLEET · CREW · COMPLIANCE

Features

Every module an ReOC holder actually runs on.

One platform for the work, the crew, the aircraft and the evidence — instead of a scheduler, a spreadsheet, a logbook app and a folder of PDFs that disagree with each other. Here's what's inside, in the order a job moves through it.

01 · The release gate

Four inputs. One decision. A permanent record.

Crew — RePL and ARN valid, medical and inductions in date, recency met, endorsed for this operation type. Aircraft — serviceable, maintenance not overdue, no open defect, batteries within cycle and health limits. Airspace — the operating area checked against airspace, aerodromes, landing sites and vertical limits at your planned ceiling. Documentation — risk assessment, JSA and pre-flight checklist complete and signed by the people who had to sign them.

Released: the CRP issues a written release naming crew, aircraft, area and conditions. Withheld: the gate names the blocker and who can clear it. Nobody argues about whether the paperwork was done.

Operations page with the release gate
Operations. Sites, depots, the airspace map and the EVLOS, OONP, BVLOS RPA and BVLOS area registers sit on the same page.
02 · Jobs and the schedule

From enquiry to completion without leaving the job record.

A six-step build for every job — details and brief, legality check, job area, risk, JSA, attachments, sign-off — with client-ready and crew-ready job sheet PDFs at the end of it. The pipeline view shows where every job sits; the schedule puts jobs, crew and equipment on one board and flags double-bookings and eligibility conflicts as you drag.

  • Toggleable brief blocks — parking, comms, PPE, meals, contacts
  • Crew accept or decline from their own view; conflicts list who's clashing and why
  • Travel & itinerary tied to the job on Business and Enterprise plans
The Schedule: a week view of jobs by crew and aircraft, with a conflicts list underneath
Schedule · Week. Five jobs across the week, and the conflicts the board found before anyone rang.
03 · Crew, credentials and training

Expiries that chase people instead of surprising them.

Roster, profiles, qualifications and currency in one place: RePL, ARN, endorsements, medicals, inductions, onboarding packs, contractor agreements and NDAs. Pilot logbooks are fed from real flight data, not from memory.

The training engine — courses, records, site inductions and the competency matrix — is in every plan. Add the DCC Training Library to fill it with ReOC-aligned courses, inductions, quizzes and an SOP library, kept current as the Part 101 MOS changes.

Crew competency matrix: four crew members against RePL, fitness/medical, drivers licence and proficiency check, with valid, expiring and expired states
Crew · Competency matrix. Who is signed off for what — the question every CRP gets asked.
04 · Fleet, maintenance and flight logs

Hours and cycles come from the aircraft, not from anyone's recollection.

Aircraft, batteries, payloads and kits with custody, serviceability and a defect trail that survives staff turnover. Check-out and check-in records who holds what; scheduled maintenance, defects and a serviceability board keep a grounded aircraft out of the roster until it's cleared.

DJI flight logs are ingested natively — with cloud back-link — and feed logbooks, airframe hours and battery cycles automatically. KML and PDF export per flight.

Inventory: aircraft and batteries with status, location, health and value
Inventory. Thirty-three items, one in maintenance, seven alerts — and who has each of them.
05 · Safety and analytics

Versioned, matrix-scored, and ready to hand to a regulator.

Risk assessments, SWMS / JSEA, permit-to-work, a JSA per job with a hazard library and controls, and incident and hazard reporting with follow-up. A CASA-aligned SWMS can be drafted from the activity and environment in seconds, for you to review and sign.

Analytics shows utilisation, release outcomes, crew eligibility and fleet hours over time — exportable, so a client or an auditor gets a report rather than a promise.

Analytics: jobs over six months, jobs by status, crew eligibility and release outcomes
Analytics. Release outcomes and crew eligibility as charts, not as a feeling.

And the rest of it.

Airspace mapDraw the operating area, set your ceiling, and see what applies to that volume — controlled, restricted, danger, prohibited and military volumes; aerodromes, HLS, approach and departure splays, 3 NM boundaries; powerline and national park overlays.
Manual Opsevery planController-flown flights live on the board with position, telemetry and video; the flight log writes itself at touchdown. Monitor-only — the pilot holds authority.
Remote Operations Centreadd-onDocks, waylines, missions, a dispatch gate, live video, alarms, handovers, and Tasks & Replay. For ReOC holders on Team and above. Details →
Weather windowLive conditions and the full forecast timeline for the site, reachable from the job — wind, gusts, rain, cloud, temperature and storm overlays. No key or account to configure.
Field appCrews check in, run pre-flight and post-flight checklists and log flights from the phone in their hand. Job pack and brief on the device.
Travel & itineraryBusiness+Flights, cars and beds planned and attached to the job they belong to. Crew see travel alongside their tasking; costs stay with the work.
Advanced-ops registersTeam+BVLOS area and RPA registers, EVLOS and OONP registers — the gate reads them when the operation type calls for them.
API, webhooks, white-labelBusiness+A public API and webhooks for your own integrations; your branding on the app and on exports. SSO and priority support on Enterprise.
Documents & retentionEncrypted document storage under seven-year object-lock. Releases, logs and logbooks are held seven years; training records three. Full export on cancellation.
Client portalplannedA site-scoped role for asset owners whose docks are run by a managed operations partner — request a mission, see the decision, watch the feed, pull reports.

Specialised operations, without a separate system.

Operations beyond standard daytime VLOS carry their own crew, equipment and documentation requirements. The gate knows which apply to the operation type on the job and refuses to release until they're met. Core compliance is in every plan and is never an add-on.

OperationWhat the gate addsWhere it lives
Standard daytime VLOSThe ordinary crew, aircraft, airspace and documentation checks, on every job.Every plan
Night VLOSLighting, crew composition and additional currency requirements enforced per crew member.Every plan
EVLOS Class 1 and 2Observer qualification, comms plan and training records checked before release; the EVLOS register.Team and above
Over or near peopleThe operation type drives the risk assessment; the OONP register and the corresponding controls are required before release.Team and above
BVLOS area and RPAArea and RPA registers, SORA-style assessment inputs, and the dispatch gate's eleven hard checks for remote operations.Team and above · ROC add-on for docks

Same application, three ways to run it.

OptionWhat you getWho it's for
TrialFourteen days of the full platform on the plan you choose, hosted by us. Card required, nothing charged until day 14. Remote Operations runs in simulator.Everyone starts here
Hosted in AustraliaManaged hosting on Australian infrastructure — encrypted document storage, object-lock retention on records that carry an obligation, backups and updates handled for you.Solo, Team, Business, Enterprise
Self-hosted perpetual licenceBuy Business, Scale or Enterprise outright and run it on your own infrastructure. One-time licence with the first year of maintenance included, then 10% a year for updates, compliance content and support. Write-once storage is mandatory and attested by you. Licence pricing →Business and above, where the records must stay on your own infrastructure

See it against one of your own jobs.

A walkthrough is thirty minutes and works best with a real job. Or skip the call and start the trial.