Every handover is a re-key.
Stores, planning and QA enter the same lot, batch and record into their own systems, and reconcile them later.
ProductsDMP
• Digital Manufacturing Platform
One record, from receipt to release.
ERP, MES and QMS on one database. A decision in one product controls what can happen in the others.
Start with one product. Connect the rest when ready.
The problem
Most plants run three systems.
Batches wait in the gaps.
Purchase, production and quality each keep their own records. Every handover between them is a re-key, a reconciliation or a chase.
A hold does not travel.
QA puts a lot on hold. Stores, planning and dispatch find out by email, if they find out at all.
Three validations, plus the interfaces.
Inspectors walk through three records and the middleware between them. So does every upgrade.
Close the gaps between systems
Five reasons
to run one record.
Five things you only get when purchase, production and quality share one record.
01 / Lot genealogy
Trace any lot, end to end, in one search.
A supplier lot carries its receipt, test, dispensing, batches and dispatches on one record. Recall reach is a view, not a project.
- 01Start from any lot.
Search a supplier lot, batch or dispatch and see the whole path, backward and forward.
- 02See every link.
Receipt from ERP, test from QMS and dispensing from MES, on the same record.
- 03Know the reach.
See the batches, customers and stock a recall touches, before the call ends.
02 / One hold
Hold a lot once. Every team sees it.
When QC holds a lot, stores, planning and sales see it in the same second. No email, no interface, no sync.
- 01Stop the issue.
Stores cannot issue held stock, and its bins are locked.
- 02Flag the plan.
Planned batches that need the lot are flagged in MES before dispensing starts.
- 03Warn sales.
Orders that depend on it are marked at risk, with the reason attached.
03 / Batch costing
Know what a batch really cost.
Prices from purchase meet actual consumption from the floor, so batch costing is a report, not a month-end spreadsheet.
- 01Price from the PO.
Every material is costed at the rate it was bought at.
- 02Quantity from the floor.
Dispensed and reconciled quantities, not the BOM standard.
- 03Variance by batch.
Price and usage variance against plan, batch by batch.
04 / Plant view
See delays where they start.
Sales, purchase, production and quality on one dashboard, so a delay shows up at its cause, not where it lands.
- 01One dashboard.
OTIF, OEE and readiness, read from the same record.
- 02Trace the delay.
Each late batch points to the step and the team holding it.
- 03Act on exceptions.
Overdue work opens with the record attached.
05 / Quality events
All quality events in one place.
Deviations, CAPA and change control from every team land on one list, raised by people or by Factro itself, each linked to the lot, batch or equipment it came from.
- 01Raised where it happens.
A failed result, a short delivery or a missed calibration raises its own event, with the record attached.
- 02One list, one lifecycle.
Deviations, CAPA and change control share one queue, so QA sees what is open, who owns it and what is late.
- 03Linked both ways.
An event shows the lots it holds, and a lot shows its open events, so no release misses an investigation.
Under the hood
Everything DMP runs,
on one database.
Twelve modules across ERP, MES and QMS, on one record.
One platform, not ten systems.
DMP takes the place of around ten separate systems. No integration tax: no interfaces to build, maintain, validate or reconcile.
One record, one audit trail.
Every change in ERP, MES and QMS lands on one append-only audit trail. You validate one system, not three plus the interfaces between them.
One decision holds everywhere.
A QC hold in QMS stops issue in stores and the planned batch in MES at once, because there is nothing to synchronise.
Industry packs
Controls for each regulated category, on the same records and workflows.
Moments that matter
What one record
changes.
Five situations where separate systems stall and one record does not.
01
Sales wants to promise a batch still in QC.
Available-to-promise counts released stock only, so the promise matches what QC has approved.
02
A customer asks where a lot went.
Genealogy runs from supplier lot through every batch to dispatch. From one record, ready before the call ends.
03
Finance asks what a batch really cost.
Purchase prices meet actual floor consumption, so costing is a report, not a month-end spreadsheet.
04
QC fails a test at 4 pm.
Stores, planning and dispatch see the hold the moment the lab records it. Nobody chases anyone’s inbox.
05
An inspector asks for the validation package.
One audit trail and one validation package, instead of three systems and the interfaces between them.
Who it is for
Built for the people who
run the plant.
Each role opens Factro on its own screen, with the evidence it needs to act.
01 / Who it is for
Plant head
See the whole plant in one place.
- 01
OTIF, OEE and readiness in one place
- 02
Batch cost against plan
- 03
Delays traced to where they started
02 / Who it is for
Managing director
Grow without adding systems.
- 01
One subscription for every product and module
- 02
Industry packs and new modules included
- 03
No integration project to fund
03 / Who it is for
QA and regulatory lead
Walk inspectors through one system.
- 01
One append-only audit trail
- 02
One validation package
- 03
Evidence captured with the batch
04 / Who it is for
Supply chain head
Follow every material movement across the operation.
- 01
Receipts and supplier standing
- 02
Released material for planned batches
- 03
Orders at risk when a lot is held
05 / Who it is for
Production head
Connect the floor to the rest of the plant.
- 01
Material readiness on the plan
- 02
Stage progress and quality holds
- 03
Delays visible to every department
06 / Who it is for
Finance controller
Batch cost based on the work that happened.
- 01
Price from purchase, quantity from dispensing
- 02
Yield from reconciliation
- 03
Variance against plan, batch by batch
07 / Who it is for
IT and systems admin
One system to govern and support.
- 01
One access model across the plant
- 02
Controlled integrations and audit history
- 03
One validated record, not three copies
Before you start
Questions
plants ask us.
Start with the operation you have. Agree the controls and connections you need.
Talk to our teamWhat does one record mean in practice?
One database for ERP, MES and QMS. A lot, a batch or a deviation exists once, and every team reads and writes the same record, so a QC hold in QMS blocks issue in stores and flags the planned batch in MES in the same moment.
How is that different from integrating three systems?
An integration copies data between databases, on a schedule or on an event, and every interface is one more thing to build, validate, monitor and repair. With DMP there is nothing to copy, so there is no delay, no reconciliation and no interface for an inspector to question.
Do we have to start with all three products?
No. Start with the product that solves your most expensive problem. When you add the others, they join the same database, with no data to migrate and no interface to build.
How does validation work with one platform?
You validate one system with one audit trail, instead of three systems and the interfaces between them. On the Dedicated tier, the validation pack covers URS, IQ, OQ and PQ with a requirements traceability matrix across ERP, MES and QMS.
We make products in more than one regulated category. Do we need two systems?
No. One site runs one Factro. Industry packs add the controls each category needs on the same record, so a nutraceutical line and a pharmaceutical line share one audit trail.
Does DMP replace SAP?
Only if you want it to. If SAP runs your finance, procurement and reporting, it stays. Factro adds an enforced batch record on the floor and a quality system that holds work until its checks pass, and posts transactions back to SAP.
How is DMP priced?
One subscription covers every product, module and industry pack, including new ones as they ship. You start paying when you start using it, with no purchase obligation before onboarding and assisted operation are complete.
Make it your workflow
Bring your plant.
See it on one record.
Walk through one product from receipt to release with our team. Start with the handovers that slow your batches down.