CONOPS A product of CONOPS
On-premises deployment

One Windows Server, one SQL Server 2022 instance, your building.

CONOPS | MOS (Manufacturing Operating System) on-premises runs the standalone build as a boot-start service behind IIS, with the application and warehouse databases next to your ERP. Nothing leaves the network except Graph and SMTP calls to your own tenant.

Footprint · On-premises
ComponentWhereNotes
Web service Windows Server Standalone build, boot-start service
Reverse proxy IIS on the same server HTTPS, your certificate
Application DB SQL Server 2022 Row-Level Security, temporal tables
Warehouse DBs Same SQL instance Linked servers to each ERP
Nightly load SQL Agent job Change-only, read-only
Identity Your Entra ID (hybrid) Or scoped otherwise
The whole footprint fits on one server plus your SQL Server instance.
IT runbook outline

Five steps your administrator runs, with us on the call

  1. Service install

    Unpack the standalone build, register the boot-start service under the service account, set the configuration file.

  2. Reverse proxy

    Create the IIS site with your TLS certificate, URL rewrite to the service port, request limits.

  3. Redirect URI

    Add the HTTPS host name to the Entra ID app registration; confirm sign-in on the .us endpoint.

  4. Defender exclusion

    Exclude the service's working directory from real-time scanning so startup and uploads are not throttled.

  5. Smoke test

    Sign in, submit a kiosk record, run one workflow step, confirm the nightly load's verify report.

Identity
Still your Entra ID, hybrid-joined, unless the engagement scopes a different provider. Six roles, permission grid, site-scoped and corporate read-only access all work the same as in the cloud option.
File storage
SharePoint Online in your tenant by default. For air-gapped sites, an on-premises file-share option is scoped as a service; it is not a standard feature today.
Update procedure
Ordered SQL scripts from the migration manifest, run by your DBA in SSMS or by us under escort, each followed by its verify report. Then one web deploy and a service restart. The data is never overwritten by a deploy.
Provisioning checklist

What your IT provides before week one

Server
Windows Server (2019 or later), 4 vCPU and 16 GB as a starting point, on the plant network or a DMZ your users can reach.
SQL Server
SQL Server 2022 instance with capacity for the application database and one warehouse database per ERP; SQL Agent enabled.
ERP access
Linked-server credentials with read access to each site's ERP database (Infor VISUAL, Infor SyteLine, others by scoping).
Certificate and DNS
An internal host name and a TLS certificate your clients trust.
Service account
A domain account for the service and the SQL Agent job, with the rights we list in the runbook.
Outbound rules
HTTPS to graph.microsoft.us and SMTP to Exchange Online in your tenant; nothing else.
Next step

Request an on-premises readiness review.

We walk the runbook with your administrator and DBA, confirm ERP reachability, and return a written provisioning list for your change board.