Coordination and synchronization for the Base / Wing of the future.

Yes. Everything needed to operate — the personnel and coordinator apps, the deterministic scheduling solver, the relational database and event bus — lives inside your intranet enclave. If the outside link is cut, bookings, dispatch, cascade re-planning and custody all keep running. There is zero external dependency to operate.

The only optional external component is the predictive layer, and closing its gateway pauses predictions — nothing else.

No identity data leaves the enclave — ever. If you enable the optional ML layer, only de-identified data passes out through a one-way gateway that strips identity, and only predictions come back in. Your security officer controls that gate; close it and the system continues operating on the base / wing exactly as before.

Sovereign by design · One-way gate · Gateway under your control

Fieldmarch is built for exactly that path: it deploys as an embedded package inside your enclave, requires no internet reach-back to operate, and receives updates as signed packages you bring across on your own terms. We work with your security authority through your accreditation process and provide the architecture documentation, data-flow diagrams and hardening evidence it requires.

Accreditation is your authority's decision on your network — we don't claim it for you; we come prepared to earn it.

The org chart you already have. Five permission levels (A1–A5) map to your rank structure — from request-only privates, through unit transport Sergeants with endorsement power, to base / wing-wide P0 authority at Colonel and Captain (Navy) level. The system strengthens the NCO backbone rather than bypassing it.

It's configuration, not code: the orderly room maintains the rank-to-level table, a delegation letter changes access the same day, and appointment overrides (such as duty officer P0) are time-boxed and logged.

No — it fills the layer none of them cover: the minute-to-minute coordination of requests, assets, crews and custody at base / wing level. Institutional systems of record stay authoritative for what they own; Fieldmarch generates the structured, timestamped coordination data they have never had, and exports it in formats your existing reporting can consume.

Never. The P0–P3 priority model is enforced by the solver: a P0 emergency preempts, and everything affected is re-planned in under 3 seconds — automatically, with every displaced tasking rescheduled rather than dropped. A P0 medevac never waits for a P3 mail run, and P2 taskings auto-escalate to P1 if unactioned two hours before start.

Training is structured for a posting-cycle world: role-based courses for coordinators, unit Sergeants, personnel and trades; train-the-trainer so the base / wing owns its knowledge rather than renting it from us; bilingual materials (EN/FR) with rank-appropriate quick cards; and refresher cycles deliberately aligned to posting season. Knowledge survives the people who first learned it.

Support tooling runs on your intranet — diagnostics and ticketing operate inside the enclave, so no data leaves to get help. Response tiers are guaranteed in the same P0–P3 language your operations already use, and updates arrive as signed packages for your enclave. You get a named account team led by Walter: your first call stays your first call.

One base / wing, Transport module, the Base / Wing Transport Office and two units — with success criteria written together before anything switches on: booking time, utilization, custody compliance. Your numbers, not ours.

If the pilot does not hit the agreed criteria, you walk away with the data anyway. Either outcome produces decision evidence — which is why the pilot is the fastest honest answer to every question on this page.

Pricing is scoped per base / wing at the briefing, because it depends on base / wing size, modules and training footprint — and because the offer is priced and structured around adoption, not licences. Software, training and support come as one accountable package: procurement risk is adoption risk, and a system nobody uses synchronizes nothing.