Remote Operations Centre · Mission Control

Sensorem Remote Operations Centre

Mission Control

Start a mission below. Completed checklists auto-save to flight logs.

Operations Status ONLINE
UTC --:--:-- LOCAL --:--:--

Weather feed · ROC location

Sensorem ROC

0
Missions Today
0%
Serials Set
0h
Flight Hours Today
Flight Logs—
Registered Drones—
Active Clients—
Pilots On Roster—

Shift handover

Checklist v1

No handover note yet

Ops board (this desk)

In-flight and today's completed missions on this PC. Cross-desk live board needs cloud sync later.

Today's Missions No missions today
    No completed missions today

    Start a new mission to run your pre-flight checklist.

    Mission Setup

    Select Drone *

    Pre-Flight Checklist

    Ready
    In Flight
    00:00:00

    Timer started when pre-flight checklist was submitted. Flight hours are recorded automatically.

    Post-Flight Checklist

    Post-Flight
    Complete

    Mission Complete

    Checklist saved. CSV, PDF, and AVCRM DJI log (.txt) save to your flight logs folder when auto-export is enabled.

    More exports & options

    Edit Completed Mission

    Correction

    Correct mistakes in mission details, flight times, or post-flight checklist. You will be asked for a reason — changes are recorded in an audit note.

    Drone

    Post-Flight Checklist

    Operations

    Pilot currency (30 days)

    Airframe hours (30 days)

    Ops board

    Step 1

    Operator Name

    Shown on exported PDF checklists and CSV records.

    Display

    Layout (tablet & phone)

    Controls dashboard density on iPad and phones. Auto switches to a simplified dashboard on smaller touch screens — no setting required for most pilots.

    Used for dashboard weather (Open‑Meteo). Works offline with last cached result.

    Step 2

    Pilots

    Pilots appear in mission setup with their ARN (Aviation Reference Number).

    Step 3

    Drones

    Set category, dock (1–3), and DJI serial for each aircraft. Serials power AVCRM / Flight Hub 2 matching. Import a CSV export from AVCRM to sync serial numbers.

    Step 4

    Clients & Drone Assignment

    Pilots pick a client at setup — only assigned drones appear. Set each client's timezone for in-flight clocks.

    Step 5

    Sites

    Sites appear in the mission setup dropdown (e.g. Perth ROC).

    Step 6

    One-Tap Launch

    Mission setup shortcuts — auto-fill pilot, site, AVCRM job ref, and default client/drone. Pilots can adjust client and drone before launch; available after the drone's first pre-flight each day.

    Checklist Template

    Add, remove, and edit pre/post-flight sections and items (one per line). Changes apply to new missions only.

    AVCRM flight logs (.txt)

    Exports DJI-style .txt files for AVCRM Manual Import (~2 KB each). Set each drone's DJI serial under Setup → Drones — no template load required.

    AVCRM export ready (built-in template)

    End-of-shift bulk export: use Dashboard → Today's Missions → Export today's AVCRM logs (ZIP).

    PDF Document Text

    Customise headings and wording on exported PDF checklists. Operator name is set under Setup. Saved with backup/restore.

    Config sync (fleet only)

    Share pilots, drones, clients, sites, checklists, and presets with another PC without overwriting mission history. Use full Backup when you need sessions too.

    Checklist version

    Stamped onto each new mission for audit (e.g. after you change checklist items).

    This desk defaults

    Pre-fill new missions on this PC. Optional photo required on Fail items.

    Backup & Restore

    Move all app data to another PC — settings, pilots, drones, clients, checklists, and completed missions. Save settings first, then download. On the new PC, open Settings and upload the backup file.

    Software Update

    Deploy a new app version to this PC after you change code in Cursor. On your dev machine run node scripts/bump-and-build.mjs (or double-click bump-and-build.cmd) — that bumps the patch version and creates releases/roc-update-<version>.json. Copy that file to each ROC desktop and upload here. Pilot data in the browser is not changed. Requires node fh2-proxy.mjs running.

    Checking installed version…

    Flight Logs & Auto-Export

    When a mission completes, CSV, PDF, and AVCRM DJI .txt logs save automatically under flight logs/avcrm-dji/{pilot}/{date}/. Run node fh2-proxy.mjs for the folder next to this app.

    Browser folder not linked

    Local helper: checking…

    Flight Hub 2 Optional

    Link official FH2 flight tasks after missions. Requires fh2-proxy.mjs. Default cloud: es-flight-api-us.djigate.com.

    Matches by aircraft serial and flight time. Links silently if one task is found; asks you to choose if several match.

    Settings Password

    Lock this page so pilots cannot change drones, clients, or checklists. Leave new password blank to keep unchanged.