Manufacturing ERP That Works Alongside SAP and Oracle
Manufacturing ERP for the order-to-invoice pipeline — sales orders, production sheets, delivery and invoicing on one traceable chain — designed to run alongside SAP, Oracle or Microsoft Dynamics across the ISA-95 boundary.
A manufacturing ERP built from the shop floor outward
MileSoft ERP runs the order-to-invoice pipeline for manufacturers: a sales order raised against the customer's purchase order becomes a production sheet with quantities and dates, moves through packing and delivery, and closes with an invoice that retrieves its delivery order rather than being retyped. Each document carries the identifier of the one before it, so any invoice can be traced back to the originating purchase order.
The dashboard shows cleared and pending orders at each gate, and those counts conserve — cleared plus pending always equals what the previous gate cleared — so the gate holding the most work, the real constraint, is visible without a capacity study. Order lines keep ordered and released quantity, and required and promise date, side by side, and money is computed exactly rather than in floating point.
It is designed to sit alongside a corporate SAP, Oracle or Microsoft Dynamics system rather than replace it, exchanging item master, purchase and financial postings across the IEC 62264 (ISA-95) boundary. High-resolution production data — fastening events, downtime, material genealogy — stays with MileSoft's torque traceability, andon and material traceability modules.
Manufacturing ERP
The eleven o'clock test for a manufacturing ERP
Change the schedule at 11 a.m. If the floor sees it at tomorrow's stand-up, the system is producing reports, not running production.
Most enterprise systems were built outward-in — general ledger first, a thin manufacturing module last — which is the wrong order for a factory. The result is familiar: a long implementation, a go-live full of workarounds, and a shop floor still running on the spreadsheets the ERP was meant to replace. The distinction is not real time against batch; it is whether the number a decision-maker sees is the number the floor is working from.
Here an order is one object moving through five documents, each carrying the identifier of the one before it, so the pipeline can be walked in both directions:
| Document | What passing the gate asserts | Link carried |
|---|---|---|
| Sales order | The commitment exists, priced, with terms and a promise date | Customer purchase order number and date |
| Production sheet | The commitment has become manufacturable work, with quantities and dates | Sales order number, plus its own production order number |
| Packing / handover | The work is complete and physically consolidated | Production order reference |
| Delivery order | The goods have left under the agreed trade terms | Packing reference and destination |
| Invoice | The commercial claim is raised against the delivery | Delivery order number, retrieved rather than typed |
Order pipeline
A dashboard you can check with one subtraction, and the constraint it reveals
Orders waiting at a gate are inventory, and inventory is conserved.
cleared + pending at each gate = cleared at the gate before it
The first test of any pipeline dashboard. A cascade that does not conserve is counting different populations at different gates, and every conversion figure derived from it is meaningless.
Worked example: the numbers on MileSoft ERP's own dashboard
1,087 orders raised; 931, 771, 520 and 479 cleared at the four gates. 931 + 156 = 1,087; 771 + 160 = 931; 520 + 251 = 771; 479 + 41 = 520 — four independent checks, all exact.
| Gate | Arrived | Cleared | Pending | Loss |
|---|---|---|---|---|
| 1 | 1,087 | 931 | 156 | 14.3% |
| 2 | 931 | 771 | 160 | 17.2% |
| 3 | 771 | 520 | 251 | 32.7% |
| 4 | 520 | 479 | 41 | 7.9% |
| End to end | 1,087 | 479 | 608 | 55.9% |
The constraint is the gate holding the most work — here the third, delivery, with 251 orders, more than the other three combined. It is not where a manufacturer looks: production clears 82.8% of what reaches it, delivery 67.3%. Adding 20% capacity at production would push 34 more orders into a queue already 251 deep, and end-to-end conversion would not move.
Order to cash
From pending orders to days of delay, and where the pipeline actually ends
Customers experience days, not pending counts. Little's Law converts one into the other.
delay at a gate = pending orders ÷ orders cleared per day · pipeline time = queueing delays + service times
Worked example: the same pipeline in days
With the four gates clearing 62, 51, 26 and 48 orders a day and service times of 0.5, 2.0, 0.5 and 0.2 days, queueing delays are 2.5, 3.1, 9.7 and 0.9 days: 16.2 days of waiting plus 3.2 of work, 19.4 days in all. Production has the longest service time — it is the real work — but makes an order wait only 3.1 days. Delivery does almost nothing to an order and makes it wait 9.7, half the pipeline. One is a technical problem; the other is sequencing and capacity.
The dashboard's last gate is the invoice. The business's last gate is cash. With a 105-day average payment term, order-to-cash is 124.4 days, and the 19 operational days the dashboard reports are 16% of it — an improvement programme aimed only at the gates is optimising the smaller half.
Order lines
Two quantities and two dates on every order line
What the customer asked for and what the plant committed to are different facts.
Lines carry ordered and released quantity as separate columns — where they differ, the difference is a deliberate decision such as a minimum batch or a partial release, the economic-order-quantity logic under every production sheet — and required and promise date side by side.
Almost every manufacturer reports on-time delivery against the promise date and scores well, because the plant sets the promise. A plant meeting 98% of its own promises while promising two weeks later than customers asked is failing them with a green dashboard. The gap between required and promise dates, aggregated across orders, is the honest measure — and the order line already holds it.
An order line is not always a quantity of interchangeable items either. In the captured deployment, a uniform manufacturer, an invoice line expands to the named recipients who will wear it, each with a size and quantity — a structural sub-line that survives from order through production sheet to invoice and aggregates correctly at every gate, rather than a free-text field.
Monetary integrity
Why money must never be held in floating point
A rounding difference that appears on one invoice in three hundred makes all of them untrustworthy.
Worked example: 3 units at 53.00 with 5% tax
The line is 159.00, tax 7.95, net 166.95. In binary double precision, 159.00 × 0.05 is not 7.95 but 7.9499999999999992894…, and the net is 166.94999999999998863…. Rounded for display both look correct. Sum a hundred such lines and the accumulated error can exceed half a paisa or cent, so the stored document total and the sum of stored lines differ — exactly when a ledger, an auditor or a tax authority compares them.
The fix is architectural: hold money as exact decimals or integer minor units — 15,900 × 5 ÷ 100 = 795 — and round once at computation against the currency's ISO 4217 exponent. Test any system with one query: sum the stored line amounts of a hundred invoices and compare each to its stored total, exactly rather than to two places.
ERP with SAP and Oracle
Where a manufacturing ERP's boundary belongs
IEC 62264 separates business planning from manufacturing operations for a reason.
IEC 62264, adopted from ANSI/ISA-95, separates level 4 business planning from level 3 manufacturing operations and defines the interface between them. A manufacturing ERP that tries to be a machine-data system fails at both, because it becomes responsible for data it cannot capture at the rate required. MileSoft ERP holds the commercial and planning record — sales orders, production sheets, delivery and invoicing — and sits alongside a corporate SAP, Oracle or Microsoft Dynamics system, exchanging item master, purchase and financial postings across that boundary.
High-resolution production data stays with the level-3 systems built to capture it: torque traceability, andon and material traceability. In MileSoft's published Industry 4.0 case study, a Tier-1 automotive supplier ran all four together across two plants, with a phased rollout of eight weeks at the first plant and six at the second. That rollout figure and the programme's headline outcomes belong to the four-module programme, not to the ERP alone — what the deployment shows is that the boundary is workable.
Evaluating manufacturing ERP
Eight questions to put to any manufacturing ERP
Each is answerable by demonstration — including by us.
| # | Dimension | Ask the vendor to demonstrate |
|---|---|---|
| D1 | Conservation | Do the dashboard's gate counts satisfy cleared plus pending equals the prior gate's cleared? |
| D2 | Identity chain | Open an invoice. Can you reach the originating customer purchase order without a search? |
| D3 | Two quantities | Where ordered and released quantities differ, does the line record both, and why? |
| D4 | Two dates | Can the system report the gap between required and promise dates across all open orders? |
| D5 | Flow time | Convert a pending count into days of delay. Does the system do it, or is it a spreadsheet exercise? |
| D6 | Change propagation | Release an engineering change. Which revision do in-flight orders show? |
| D7 | Exact money | Sum stored line amounts against the stored document total, exactly. Do they match on every invoice? |
| D8 | The eleven o'clock test | Change the schedule now. When does the floor display show it? |
D1 and D7 take minutes and are almost never asked. Both test whether a system's own numbers agree with each other — a lower bar than any feature comparison, and a more informative one.
On evidence: MileSoft's product material states that core modules — production planning, bill of materials, routing and sales orders — typically go live in 12 to 20 weeks, with external integrations adding 4 to 8. That range is vendor-reported with no sample, and the critical path is usually item-master data quality rather than configuration.
Standards referenced: IEC 62264-1, -2 and -3 / ANSI-ISA-95, ISO 22400-1 and -2, ISO 4217, Incoterms 2020, IATF 16949, GS1 General Specifications. For the argument in plain terms see manufacturing ERP; derivations are in the manufacturing ERP method paper.
Software Modules
Complete ERP Software Modules
Screens from the running system — click a module to preview
Dashboard
The main dashboard provides an immediate snapshot of your entire operation. Monitor total orders and drill down into key statuses.
Features
Key Features
Built-in capabilities that set our software apart
Order-to-invoice document chain
sales order, production sheet, packing, delivery order and invoice, each carrying its predecessor's number
Conserved pipeline dashboard
cleared and pending orders per gate that add up, so the constraint is visible
Production sheets
sales orders turned into manufacturable work with quantities and dates
Two quantities and two dates
ordered vs released quantity and required vs promise date on every line
Per-recipient sub-lines
line items that resolve to named recipients with size and quantity
Exact monetary arithmetic
tax, discounts and totals that reconcile exactly from line to document
SAP, Oracle and Dynamics integration
item master, purchase and financial postings across the ISA-95 boundary
Benefits
Key Benefits
What your team gains from adopting our platform
Integrations
Works with the systems you already run
Sits alongside your corporate ERP rather than replacing it, exchanging item master and postings across the ISA-95 boundary.
Testimonials
What Our Clients Say
Trusted by industry leaders across manufacturing, HVAC, and logistics.
"The software features, such as real-time monitoring and alerts, have proved invaluable in optimizing machine operations. MileSoft team's professionalism, technical expertise, and dedication to meeting our requirements have been impressive."
FAQ
Manufacturing ERP That Works Alongside SAP and Oracle — FAQs
Answers to the most common questions about this product. Need more? Book a demo or reach out via Contact.
What makes a manufacturing ERP different from a generic one?
Why do generic ERPs fail on the shop floor?
Can it integrate with SAP or Oracle?
How are engineering change orders handled?
What is a typical implementation timeline?
Explore More
Related Products
Complementary tools teams often pair with this solution
Related Reading
Go deeper
Explore the long-form story behind this product.
The Conserved Pipeline: Stage Gates, Pending Inventory, and Locating the Constraint in an Order-to-Cash System
Architecture, Computational Methods, and Reported Outcomes from MileSoft Manufacturing ERP
Read the paperRead the full Manufacturing ERP That Works Alongside SAP and Oracle deep-dive
Read articleSee how MileSoft delivers in Industry 4.0
Read case studySee your savings in under a minute
Estimate the time and cost this tool could give back — free, instant, no sign-up.
Run the eleven o'clock test with us
Bring a month of order data. We will show whether your gate counts conserve, where orders are really waiting, and how many days of delay that adds.