CONOPS A product of CONOPS
ERP integration

Read your ERP nightly. Write to it never.

CONOPS | MOS (Manufacturing Operating System) reads each site's ERP through a linked server into a metadata-driven warehouse. Onboarding a site is configuration, not code: load definitions name the source tables, the change columns and the target datasets.

Warehouse · Load status · Plant 2 (Infor VISUAL)
DatasetRows changedDurationVerify
Backlog 1,204 00:41 Pass
Job orders 3,318 01:12 Pass
Purchase orders 812 00:27 Pass
Shipments 96 00:08 Pass
Labor transactions 9,441 02:03 Pass
BOM structure 0 00:05 No change
The nightly load report your DBA and our integration engineer both read.
Supported today

Two ERPs mapped, others scoped

Infor VISUAL
Mapped and in production. Backlog, job orders, purchase orders, shipments, bookings, BOM structure, part master, customers, cost of sales and labor transactions.
Mapped
Infor SyteLine / CloudSuite Industrial
Mapped. Same dataset coverage from the SyteLine schema, with site and warehouse identifiers carried through.
Mapped
Other ERPs
Epicor, JobBOSS, Plex and others are scoped through a fit assessment: we review the schema access, map the ten datasets and quote the integration phase.
By scoping
How a site is onboarded

Configuration, not code

  1. Linked server

    Your DBA creates a linked server from the warehouse instance to the site's ERP database with a read-only login.

  2. Load definitions

    We register the site and its source schema in the metadata tables: source table, key, change column, target dataset.

  3. Initial load and validation

    A full load, then row counts and totals reconciled against ERP reports your controller already trusts.

  4. Nightly schedule and verify reports

    A SQL Agent job runs change-only loads each night; verify reports confirm counts and flag anomalies.

The ten datasets
  • Backlog
  • Job orders and operations
  • Purchase orders
  • Shipments
  • Bookings
  • BOM structure
  • Part master
  • Customers
  • Cost of sales
  • Labor transactions

Which module reads which dataset is listed on each module page.

Fit assessment

What we check for an ERP we have not mapped

Access
Direct SQL access to the ERP database or a replica; linked-server reachability from where the warehouse will run.
Schema
Where the ten datasets live, how change is detected (timestamps, row versions or audit tables), and site identifiers.
Volumes
Rows per dataset and daily change rates, to size the load window.
Reconciliation
Which ERP reports we validate against for backlog, shipments and cost of sales.
Output
A written scope and a fixed price for the integration phase, usually within two weeks of access.
Next step

Request an ERP fit assessment.

Tell us the ERP and the number of sites. We return a scoped integration phase with a fixed price.