Defense
Licensing
The architecture was designed so you do not have to buy a mission system from one vendor. We build individually procurable OMS services for the platforms adopting the Government Reference Architectures. License what you need.
License any combination of capabilities.
Why this model exists
The OMS Standard defines a Service as an architecture element assessed against a prescribed interface and constraints specified by a non-proprietary Service Contract, communicating over publish/subscribe for loose coupling. Non-proprietary contracts at every service boundary are what make it possible to buy one service from one vendor and another from someone else.
The AFMC MOSA Guidebook states that modular technical design and an open systems approach enable competition, provide platform independence, and reduce vendor lock. We build to that.
Free and open
OMS Developer Kit
Free and open source under Apache 2.0. Service templates and libraries for building OMS-conformant services. Permanently free, with no obligation to buy anything.
Licensing model
- Per platform instance, per year. Production licenses are scoped to a platform instance for an annual term.
- Updates and support included. The license covers all updates and support for the life of the term.
No keys. No shutdown.
There are no license keys and no shutdown mechanism. If a license lapses, you keep running the version you have. What lapses is access to updates and support.
Two ways to license
Per instance
For prototypes, test articles, and small deployments. Priced per platform instance per year. Straightforward when you are standing up a handful of aircraft or nodes.
Program-wide
For fielded programs. One license covering unlimited instances of a capability on a single platform type, for a program. Priced as a single annual line rather than by count. Program-wide licensing is scoped to one platform type.
Mission Services
Individually procurable OMS capabilities. License any combination. Quote only: contact us for pricing.
Spatial-Temporal Reasoning Service
Deterministic geometry and time reasoning as a procurable OMS capability.
Weapons Resource Manager
Manages weapons inventory and employment against mission constraints.
ACP Resource Manager
Coordinates Autonomous Collaborative Platform resources for mission planning and execution.
OMS Isolator
Isolation bounds where recertification is required when something changes, which keeps update costs down.
File Coordination Service
Coordinates file transfer and distribution across the mission systems bus.
Tactical Pilot Vehicle Interface
Tactical PVI between aircrew controls and mission systems services.
Reference Implementation
Mission Autonomy Reference Implementation
A reference implementation of the A-GRA L1 interfaces. A-GRA defines L1 interface compliance at the system level, with the Mission Autonomy system treated as a black box at its external boundary, across the C2, Peer, Mission Plan, and Mission Systems interfaces.
Composed of four Mission Autonomy services: Mission Core, Planner Host, Package Coordinator, and Recorder & Debrief.
Built for airframe and autonomy vendors who need to reach a finished product without building the interface layer themselves: license the RI, add your specifics using our free developer kit, and get to a finished product faster.
Support
What's included with a license:
- Updates for the term, including conformance currency as OMS and UCI versions change.
- Incident and troubleshooting response commitments for the life of the license.
- Product Terms & Conditions available on request.
On-site or embedded engineering support is available as an optional add-on, priced separately.
FAQ
What's free?
How is software licensed?
What counts as a platform instance?
What happens if we don't renew?
What's included in support?
Can we license just one service?
How is this different from buying a mission system?
How do we buy?
Do you provide source code?
Request a quote
Quote only. Tell us which capabilities you need and how you plan to deploy them.