Operations record
Incidents and operational events captured as they happen: assignments, resources, decisions, timeline. The spine everything else hangs from.
The platform
One operational core. Every module reads and writes the same record.
Operion is not a suite of products that share a login. It is a single operational record, with modules that are views onto it — which is why one capture can serve the operation, the report and the financial file at once.
Modules
Each one is a face of the same record rather than a separate system with its own copy of the truth.
Assets & fleet
Apparatus, vehicles, equipment and consumables with readiness state, maintenance history and custody — attributed to the operations that used them.
Personnel & readiness
Credentials, certifications, currency, scheduling and availability, so the readiness picture is a fact rather than an estimate.
Logistics
Resource ordering, movement and demobilisation tracked against the operation that requested them.
Procurement
Requisitions, contracts and vendors linked to the operational events that justify them, so the paper trail is built rather than assembled.
Cost & audit
Force account labour, equipment hours and contract cost attributed as they are incurred, against the incident, the asset and the funding source.
Reporting
NERIS submissions and required reporting generated from the record officers already complete, instead of re-entered into a second system.
Analytics
Operational and financial questions answered from the record itself — no export, no reconciliation step, no second version of the numbers.
Integrations
Works alongside existing CAD and reporting systems. Operion is the record behind dispatch, not a replacement for it.
What it does not do
Being explicit about the edges is more useful than claiming the whole map.
- It is not a CAD system. Operion takes the incident forward from the moment units are working. Dispatch stays where it is, and Operion integrates with it.
- It is not a rip-and-replace. The systems that already work keep working; Operion is the spine underneath them.
- It does not ask the field to become data entry. If capture costs more attention than the fact is worth in the moment, the design is wrong.
- It does not require a connection to record a fact. Field capture works offline and reconciles on reconnect.
Security and compliance
Procurement in this market starts here, so it is stated plainly — including the parts that are not finished.
SOC 2 Type II, CJIS and FedRAMP are all in progress. None of the three is complete. We will not claim an attestation before it exists, and we would rather lose a deal over that than win one on it. Ask where each stands and we will tell you specifically — what is done, what is left, and what we expect it to take.
- SOC 2 Type II — in progress. Ask for current status and scope.
- CJIS — in progress. Ask for current status and scope.
- FedRAMP — in progress. Operion is not listed on the FedRAMP Marketplace, and we claim no Marketplace designation.
Built in today
- Capture and reconciliation designed to hold an evidentiary chain, not just a database row.
- Operational records retained so that an audit years later reads the same as the day it was written.
- Role and jurisdiction boundaries enforced on the record, not just in the interface.
Bring the operation you actually run.
We will walk the record through one of your scenarios — incident to report to reimbursement file — rather than through a scripted tour.
Request a demonstration