One platform between your people, your ERP and Microsoft 365
CONOPS | MOS (Manufacturing Operating System) is one web application on one database. Nine modules share typed records, sites, roles, workflow templates and a warehouse that reads your ERP nightly and never writes to it.
Three boxes, one direction of trust
Your people sign in through your own Microsoft 365 Government tenant. The platform reads the ERP through a linked server and keeps files and mail inside your tenant.
Your users
- Browser on the plant network or VPN
- Kiosk terminals at the cell
- Entra ID sign-in (login.microsoftonline.us)
- Six roles, site-scoped or corporate read-only
CONOPS | MOS
- One web service (Windows service, standalone build)
- One application database with Row-Level Security by site
- Warehouse databases, metadata-driven loads
- Nine modules, one record model, one workflow engine
Your ERP and Microsoft 365
- Infor VISUAL, Infor SyteLine (others by scoping)
- Linked server, nightly change-only loads
- SharePoint Online attachments via Graph API
- Exchange Online outbox and shared mailbox
The same application runs against Azure SQL in Azure Government or SQL Server 2022 on your premises. Compare the two placements.
Nine modules, one layout to learn
Each module page follows the same structure: the promise, three outcomes, a feature walk-through, the ERP data it reads, who uses it and how it connects to the rest.
| Module | What it does, as built | Buyer it speaks to | Status |
|---|---|---|---|
| Records | Tickets, NPI, savings and change requests as typed records | Engineering managers, quality, shop-floor leads | In production |
| Workflows | Visual approvals with scheduling, escalation and an audit ledger | Engineering, quality, contracts | In production |
| Projects | Milestones, tasks, Gantt and resource calendar across sites | PMO, engineering leads | In production |
| Program Management | Ship Plan, Line of Balance, contract review, past-due burn-down | Program managers, VP Ops, finance | In production |
| Engineering | NPI Tracker, Item Review, orders without BOM | Engineering, NPI leads | Available, enabled per site |
| Operations | Capacity, staffing, KPI dashboard, dispatch and schedule compliance | Plant managers, production control | Available, enabled per site |
| Procurement | PO history, shortages, PPV, outside-service performance | Supply chain, purchasing | Available, enabled per site |
| Finance | AR aging and gross profit, straight from the warehouse | Controllers, CFO | Available, enabled per site |
| CRM | Customer 360, contract registry, scorecards, pipeline, risk | Business development, contracts | Available, enabled per site |
The foundation every module stands on
Configured per site, not customized per customer
What a site needs changes over time. The platform is designed so that change is configuration your administrator makes, not code a vendor ships.
- Record types. Add a category with its own fields, priorities, SLAs and response plan.
- Modules per site. A per-site module switch turns on Engineering, Operations, Procurement, Finance or CRM when that site is ready.
- Workflow templates. Versioned templates with effective dates; auto-launch rules by record category.
- Saved views. Grids remember filters, columns and sort per user, role and site.
- KPI catalogue and targets. Define a measure once; set plan targets by site, workcenter and period.
| Site | Records | Workflows | Projects | Programs | Ops | Finance |
|---|---|---|---|---|---|---|
| Plant 1 | On | On | On | On | On | Off |
| Plant 2 | On | On | On | On | Pilot | Off |
| Plant 3 | On | On | Off | On | Off | Off |
| Corporate | Read | Read | Read | Read | Read | On |
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.