CONOPS A product of CONOPS
CONOPS · Concept of Operations

Every program has a concept of operations. Your plant should too.

In aerospace and defense, a concept of operations is how you describe the way a system will really be used: who does what, in what order, inside which constraints, and how you will know it is working. CONOPS | MOS (Manufacturing Operating System) brings that discipline to the shop floor. One platform turns your plant's concept of operations into daily execution across every site, deployed in your GCC High cloud or your building.

Built inside an ITAR aerospace manufacturer Nine modules, one database, every site Azure Government or on-premises
The definition

Written from the operator's seat, before anything is built

The concept of operations comes out of defense systems engineering. Before a program office commissions a system, it writes down how the system will be used in the field: the mission, who operates it, the sequence of events on a normal day and on a bad one, the environment it has to survive in, and the measures of effectiveness that decide whether it did its job. The requirements are derived from that document, not the other way round.

It is written in the operator's language rather than the engineer's, and that is the point. A concept of operations is the agreement between the people who will run the thing and the people who will build it, reviewed before anyone cuts metal. When it is missing, every team builds to its own assumption of how the work is supposed to flow, and the gaps show up late, in the field, at the highest cost.

A manufacturing plant is a system too. It has a mission, operators, a sequence of operations, an environment of ERP data and compliance rules, and measures that tell you whether the week went to plan. Almost none of them have written the document.

What a concept of operations contains
Mission
What the system exists to do and for whom.
Roles
Who operates, who approves, who is only informed.
Sequence of operations
The order of events, the hand-offs and the decision points.
Operating environment
The systems, data, networks and rules it has to live inside.
Measures of effectiveness
How you know it is working, and the thresholds that demand action.
Off-nominal modes
What happens when a step fails, stalls or is skipped.
Manufacturing

Your ERP records the transaction. Your concept of operations runs the plant.

Most manufacturers keep a careful ERP and have no written concept of operations. The operating model lives in the heads of a few people, in standing meetings and in the spreadsheets that connect them. When those people are out, the plant runs differently.

Something happensWhat the ERP holdsWhat the concept of operations defines
A request comes off the floorNothing, until it becomes a work orderWho receives it, what the clock is, and who is told when the clock runs out
A new part is introducedA part number and a routingThe gates it must pass, who signs each one, and what is allowed to stop it moving
Engineering changes a drawingThe revised bill of material, once releasedWho reviews in what order, how long each step may take, and where the record of the decision lives
Monday's ship planOrder dates and quantitiesHow the plan is built, when it is reviewed, and who owns each late line
A KPI goes off targetA reportThe threshold, the owner, and the action plan that follows automatically
A second, third and fourth siteMore company codesOne set of roles, sequences and measures, with every site seeing only its own rows

The ERP is the system of record for parts, orders and cost. It was never meant to carry the operating model, and the spreadsheets filling that gap are where the week goes wrong.

Aerospace and defense

In this industry the concept of operations is not optional. It is flowed down to you.

Your customers run on concept-of-operations documents. Their requirements, their audits and their compliance clauses are a program's operating concept arriving at your receiving dock. A supplier with no operating concept of its own answers them one email at a time.

Your customer already has one
Program offices write a concept of operations before a system is fielded. Primes translate it into the requirements, delivery cadence and reporting they flow down to every tier. Your plant is a node in somebody else's operating concept.
Traceability is part of the product
AS9100, first-article inspection and configuration control all assume that every record has an owner, a history and an approval chain you can show an auditor. That is a concept of operations, written down and enforced.
The compliance boundary shapes the operation
ITAR, CMMC 2.0 Level 2 and NIST SP 800-171 decide where technical data may live and who may see it. How work moves through the plant has to be designed inside that boundary, which rules out most general-purpose SaaS.
High mix, low volume, several sites
Hundreds of small jobs, many gates and more than one plant mean the operating model cannot be improvised. Either it is explicit and shared, or it is reinvented at every site and in every meeting.
CONOPS | MOS

The concept of operations, made executable

A document describes how the plant should run. CONOPS | MOS is where it actually runs. Each element of a concept of operations has a place in the platform, on one database, for every site.

Roles and responsibilities
Identity and roles

Entra ID single sign-on, six seeded roles with a permission grid, site-scoped or corporate read-only. Who may do what is configuration, not convention.

The work itself

Every request, ticket, NPI part and change is a typed record with an owner, a clock, a history and the department queue it lives in. Submitted from a browser or a kiosk at the cell.

Sequence of operations

Approval chains and gate reviews become templates: steps, approvers, time limits and escalation, with an append-only ledger of every decision.

Operating cadence

The daily and weekly rhythm is built in: dispatch, the ship plan, meeting packs, and an Intelligence Layer that ranks the risks before the meeting starts.

Measures of effectiveness
KPIs with owners

Targets with thresholds, owners and action plans, read from the ERP warehouse nightly and from the platform's own records. A miss opens a record; it does not wait for a meeting.

Operating environment

Deployed in your Azure Government (GCC High) tenant or on your Windows Server, inside your compliance boundary. The ERP is only ever read; nothing is hosted by CONOPS.

CONOPS | MOS · Site dashboard · Plant 2
Queue · Engineering
27 open
Healthy
SLA breaches today
3
Critical
Ship plan · W42
$1.09M
Warning
Department queue · Engineering
QFI-N-00412 Fixture crack, cell 7 · Shop Floor Ticket SLA 2h left
QFI-N-00409 First article hold, P/N 61-2207 · NPI Breached
QFI-N-00407 Coolant spec change · PLM change In review
Top risks before the weekly meeting2 insights
HIGH

On-time start 76% vs 90%. Material staging is 45% of late starts.

MED

CNC-5 at 118% load in week 44. Overtime or re-route.

The operating concept on one screen: owned queues with clocks, the ship plan against target, and the top risks ranked before the weekly meeting. Rendered stand-in for a product screen.
Operating environment

Same application. Two placements. Your credentials either way.

The environment is part of the operating concept, so you choose it. Only the location of the database, the files and the server changes.

Cloud · Azure Government (GCC High)

Your tenant, your subscription, the .us endpoints.

  • Azure SQL Database in Azure Government, in your subscription
  • SharePoint Online and Entra ID in your GCC High tenant
  • We never hold a tenant for you; all credentials are yours
Cloud deployment

On-Premises · Windows Server + SQL Server 2022

For policies that forbid any cloud database, or isolated plant networks.

  • One Windows Server running the service behind an IIS HTTPS reverse proxy
  • Application and warehouse databases on your SQL Server 2022 instance
  • Updates travel through your change process, never around it
On-premises deployment
The engagement

We write the concept of operations with you, then switch it on

Consulting-led and fixed in scope, run by people who have stood this platform up on a live shop floor. Discovery produces your plant's operating concept; the rest of the engagement makes it run.

  1. 2 weeks

    Discover

    Sites, roles, ERP, record types, approval paper and the spreadsheets you run on today, written up as one operating concept.

  2. 2 to 3 weeks

    Configure

    Sites, departments, workcenters, categories, priorities, SLAs, roles and modules per site, straight from that document.

  3. 2 to 4 weeks

    Integrate

    Linked servers, load definitions, dataset validation and warehouse verify reports per site. The ERP is only read.

  4. 30 days hypercare

    Go live

    Training by role, kiosk setup and daily check-ins for the first month, then support under an SLA.

Next step

See CONOPS | MOS running on your data, in your environment.

A 45-minute discovery call with the people who built it. We cover your sites, your ERP, your approval paper and which deployment fits your compliance posture.