| Number | Part | Stage | Qty | Due | Material |
|---|---|---|---|---|---|
| WO-2026-118 | BSH-3810 | Inspection | 250 | Oct 21 | 1 lot on hold |
| WO-2026-121 | FLG-2205 | Machining | 80 | Oct 24 | Issued |
| WO-2026-124 | SLV-0940 | Released | 1,200 | Oct 30 | Short 40 kg |
| WO-2026-126 | BSH-4410 | Planned | 60 | Nov 4 | Unknown |
| WO-2026-109 | FLG-2201 | Shipped | 300 | Oct 14 | Issued |
An NCR waits months for a supplier's corrective action that nobody asked for. Parts get made to last month's drawing. Both end up as audit findings, because the next step depended on someone remembering it. Datum gives each step to a named person, reminds them until it's done, and keeps the record for the auditor.
The procedure isn't wrong. The forms were made to be filled in and signed by hand, so every next step depends on someone remembering to do it.
The NCR can't close until the supplier sends back a root cause and corrective action. Nobody sends the request, so the NCR sits in a pile until a registrar's audit finds it.
The NCR shows as waiting on the supplier. Purchasing is reminded to send the request, and reminded again until the supplier's response is attached. Quality can see every NCR that's waiting, and who it's waiting on.
A drawing is revised, but QC and purchasing still have the old revision. Parts get made to an obsolete drawing, or to the new one with no record of the change.
When the new revision is released, everyone who works from that drawing is told. The old revision is marked obsolete, so open jobs, inspection plans and purchase orders point at the new one, and the change is on record.
We set Datum up from your own procedures and forms. NCRs, drawing changes, calibration, purchase orders and work orders all run the same way.
Each step of the procedure is assigned to a person, who gets reminders until it's done. If it still sits, their manager hears about it.
The quality manager gets the NCR the moment it's raised.
A record that's waiting on someone outside the company, like a supplier, says so, and the person who has to chase it is reminded.
"Waiting on supplier corrective action, 12 days."
When a drawing or procedure is revised, everyone who works from it is told, and the old revision is marked obsolete.
Rev C drops off every open job when rev D is released.
Each entry and sign-off is kept with who did it and when, and nothing is overwritten. It's ready for the auditor without a scramble.
"Who approved this, and when?" takes one click.
Sales order SO-2026-0388 for 250 flanged bushings, from the customer's PO to the shipment. Click any step to see what the person does and what Datum does for them. The numbers under each step are the ISO 9001 clauses it keeps records for.
Pick a module. Each demo plays once when it comes into view; press Replay to watch again, or use its slider and buttons to step through it yourself. The demos share one set of sample records, so the same parts, lots and people appear across them.
Every order moves through one pipeline from quote to invoice. Revenue, on-time delivery and the orders at risk update week by week, so a late shipment shows up before the customer calls.
Every line of the customer’s PO is checked against what you can actually deliver: drawing revision, quantity, date, material, certificates, inspection, price.
Sales, quality and planning each sign their part. Anything that doesn’t match goes back to the customer and the agreed change is logged on the order. Only then is it released to planning, with the certificate list already attached.
Purchase orders move from draft to received on one board. Late orders, missing certificates, and each supplier’s on-time rate, rejects and lead time update from the records, not from memory.
On-time rate comes from receiving dates and rejects from receiving NCRs, so the scorecard is never typed in.
The system flags; a person decides. Putting a supplier on watch, asking for a corrective action or removing approval is a named decision on the record. A part can’t be ordered from a supplier that isn’t approved for it.
Launches and process changes as timelines tied to the real records: drawings, first articles, change requests. When a step slips, the plan shows it and the linked records explain why.
The system doesn’t certify anyone. Certification comes from a registrar’s audit of how your whole quality system is run. What the system does is keep the records each clause asks for, at the step where the work happens, so the evidence is there when the auditor asks. Clause numbers refer to ISO 9001:2026, published September 2026.
A sales order becomes a work order, material, machining, a dimensional report, inspection and a shipment. Each step adds its record to the same package. Click any step to see what it records.
The short lot shows on the work order list, the purchase order is raised and approved from it, and the row clears when the stock is issued.
Every lot has a location, a status and a history. Reorder points suggest the purchase order before the shelf runs out. A quarantined lot can’t be issued until quality releases it, and every count adjustment carries a reason and a name.
Someone is left off the copy line, the answer sits in a reply nobody opened, and two days later the question goes round again.
In Datum North the request, the approver and the reason stay on the record. Emails and Teams messages still go out, but they only say which record to open.
ISO 9001 asks you to follow your own procedures and keep the evidence that you did. This is where Datum keeps that evidence, as part of the normal work.
| Clause | What the standard asks for | Where Datum keeps the evidence |
|---|---|---|
| 8.2Requirements for products | You confirm you can meet an order before you accept it. | Contract review, signed by quality, production and commercial |
| 8.4Externally provided products | You control your suppliers and what they send you. | Approved supplier list; certificates required at receiving |
| 7.5Documented information | People work to current, approved documents. | Document and change control; old revisions marked obsolete |
| 8.5.6Control of changes | Changes are reviewed and approved before they're used. | Change requests with impact review and approval |
| 8.5.1Control of production | Work is done to the right instructions with the right equipment. | Work orders with the current drawing and routing |
| 7.1.5Measuring resources | Gauges are calibrated, and you can show it. | Calibration register; gauge status checked when readings are entered |
| 8.7Nonconforming outputs | Bad product is identified and kept from use. | NCRs with holds, dispositions and sign-offs |
| 10.2Corrective action | You find and fix the cause of repeat problems. | Corrective actions linked to the NCRs behind them |
| 8.6Release of products | Product is checked before it ships. | Inspection reports and a signed release |
| 8.5.2Traceability | You can trace a part back to its material and records. | Lot links from purchase order to shipment |
Datum keeps the records. Certification still comes from a registrar's audit of your whole quality system, including internal audit, management review and training, which no software does for you. Check clause numbers against the edition you're certified to.
A customer or an auditor asks how you know a shipment was good. Open the shipment and follow the links back. Click any record in the chain.
Sample data. Each link was made at the step where the work happened.
Most shops start with the problem that hurts most, often NCRs or drawing changes. It isn't a big ERP project. It's built around how your shop already works, priced in fixed phases, and each phase links into the same records.
Raise the NCR, place the hold, and every step after is added with a time and a name. Try to change an earlier entry and the record refuses. A corrective action raised from it stays linked until its effectiveness check is done.
A repeat NCR is flagged, never acted on by the software. A person decides whether it calls for a corrective action (CAR) or a change request. Either can also be raised directly, from an audit finding or a customer request. Supplier rejects count toward the supplier’s record as they happen.
The change request names what it touches. Quality, production and purchasing review the impact, the approver decides, and the drawing revision is released. The old revision goes obsolete, affected work orders are flagged, and shop copies are acknowledged by name.
Every change request starts with a person’s decision: after a repeat NCR, or directly from design, sales or a customer request. The dashboard shows where each one stands and what raised it.
Review, approve and publish a revision. The old one is marked obsolete, and everyone who needs it acknowledges the change by name. Acknowledgements count toward training records.
Open NCRs, shipment holds, changes waiting on a decision and unsigned certificates, counted from the records themselves, never typed in.
Drag the week slider to see how the numbers move, or press Play.
X̄-R charts are built from instrument files as they’re saved, with run rules that flag drift while parts are still in spec.
Capability is computed from the same data using within-subgroup sigma (R̄/d₂). Cp says whether the spread fits the tolerance. Cpk says whether it fits where the process is actually centred.
A process can have a good Cp and still make scrap if it sits off-centre, and the curves show why. Pick a process to compare.
Drop files in, set the order, get one PDF with a cover sheet and bookmarks.
Reads the sales order, lists every document each line needs, collects what exists and flags what's missing.
Enter readings once. Each is judged against its tolerance and the report is generated in your controlled format, ready to sign.
Reports and certificate packages are generated from data already entered, so nobody retypes, renames or hunts for the current version. Generated is not signed: a person signs every report.
Draw the process as boxes and arrows, name an owner for each step, and publish it as a controlled revision. The record routes follow the published map.
By hand or by email, an NCR waits on whoever holds it next. In a binder, a shared folder or a SharePoint library, it is still just a file in a folder. E-signature tools don’t change that: someone still has to send it, chase it and file it.
Datum North makes the NCR a live record. It is drafted, routed, approved and signed in one system, with reminders and escalation built in. Each NCR links to its part, lot and supplier, so supplier performance builds itself from the records, not from a spreadsheet.
Pick a record type, or let it cycle. Each step has an owner, a due date and a reminder, and the route itself is set to your procedure.
The same route breaks for corrective actions, open audit actions, change requests, drawing revisions, work orders, purchase and sales orders, and calibration. Unsigned records and skipped steps are what auditors find, and enough of them put an ISO 9001 or AS9100 certificate at risk.
Chasing signatures and retyping numbers is time a skilled person isn't spending on the part, the root cause or the next improvement.
A manual step is retired only when its replacement is measurably faster. That's company policy, not a slogan.
Start there. One module as a pilot, at a fixed price, signed off before anything else begins. The rest plugs into the same records when you’re ready.