Numbers that disagree
Different functions report different figures because each built its own extract years ago.
Industry
Manufacturing
Plant floor data joined to ERP, so OEE, scrap and predictive maintenance read from the same source.
Two worlds that never met
Plant floor systems and ERP were installed decades apart by different teams for different reasons. Both are working correctly. Neither knows about the other, so OEE on the shop screen disagrees with the figure in the monthly pack.
How we work here
We model the line data and the ERP data into one layer so scrap, downtime and throughput all read from the same source. Historians, PLC tags and MES exports are handled as ordinary sources with tests, not as special cases.
Near-real-time where it changes a decision on the shift, batch everywhere else.
What tends to pay first
Downtime reason codes joined to production volume. It is unglamorous, it is usually sitting in a system nobody queries, and it tells maintenance where to spend next quarter.
Predictive maintenance comes after that, once the history is trustworthy enough to train on.
Challenges
What we hear from data teams here
Models nobody can explain
A model works, but the documentation needed for review was never written down.
Slow regulatory reporting
Each submission is a manual effort because lineage lives in people, not in the platform.
Regulation
What applies, and what we do about it
| Regulation | What it asks for | What we build |
|---|---|---|
| GDPR | Lawful basis, minimisation and subject rights | Classification at ingestion, retention rules in code, subject access queries that run in minutes |
| EU AI Act | Risk tiering, documentation and human oversight | Risk assessment at design time, model cards, and a logged override path for every decision |
| Sector rules | Accurate, complete and timely reporting | End-to-end lineage from source system to reported figure, with quality tests at each hop |
Use cases
Where the return usually shows up first
Faster reporting cycle
Automated reconciliation and a defined metric layer. Typically cuts the cycle by half.
Predictive models
Documented models with challenger comparison and drift monitoring in production.
Anomaly detection
Near-real-time scoring with a review queue and a feedback loop into retraining.
Customer and demand insight
Behaviour modelled across products rather than one product line at a time.
Audit readiness
Submission packs generated from the warehouse with lineage attached.
Platform cost control
Query cost attributed per team, with budgets and alerting.
Data sources
Systems we usually find on day one
Core systems
Transactions, records, master data
CRM
Customers, interactions, cases
Operational telemetry
Events, sensors, logs
Finance
Postings, hierarchies, currency
Questions
Questions from manufacturing
Still unsure? Call (216) 123 45678 and ask for whoever is on the desk.
Ask a questionYes. We work in your tenancy under your access controls, with named individuals vetted to your standard. We do not move data out for convenience.
Our governance team writes documentation to the standard second-line review expects, and has sat on the other side of those reviews.
Delivery teams can be restricted to a region, and all storage and compute stay in the region you specify. We publish our subprocessors.
Tell us which number you cannot trust
Send one paragraph about the report that always starts an argument. A data lead, not a salesperson, replies within one business day.