Product · ROBIN.DataFlow
Structure your data to power sound decisions.
The data foundation for your operations: ingestion from ERP, MES and CMMS with no re-keying, native MRO business ontology, shared single source of truth, and real-time feeds to all other modules.
- ERP / MES / CMMS connectors
- MRO ontology
- Single reference base
- Traceability

Chapter 01
Connect the existing IS and structure the business
Production data already exists. It is scattered across the ERP, the MES, the CMMS and local files, in formats that were never designed for scheduling.
ERP / MES / CMMS connectors
Ingestion of existing data without re-keying, whatever your source IS.
MRO business ontology
Data model structured around shop-floor realities: WOs, routings, resources, parts, TAT.

Chapter 02
Make a single source of truth reliable and shared
A schedule is only as good as its input data. Quality is monitored continuously, not just at go-live.
Cleansing & normalisation
Detection of missing, inconsistent or outdated data that skews your decisions.
Single, shared reference base
A common source of truth across scheduling, production and management.

Chapter 03
Keep a history and distribute in real time
Every data point is dated and versioned: the history serves audit as much as learning actual routing times.
History & traceability
Every data point timestamped and versioned — full auditability of a WO's lifecycle.
Real-time feeding
Continuous flow to Cockpit and Scheduling — decisions rely on live data, not overnight exports.

Industries
Every industry has its own flow vocabulary.
Business ontology, reference bases and connectors adapt to your information system and your real-world objects.

Aerospace · MRO
MRO & repair
Routing disruptions, AOG, customer-supplied parts: the flow is recomposed several times a day.

Aerospace · Production
Production & assembly
Rate, assembly stations and shortages across long series and short cycles.

Industry · Multi-industry
Manufacturing industries
Mixed flows, subcontracting and WIP scattered across several buildings.
Frequently asked questions
What teams ask us about ROBIN.DataFlow.
Which ERPs does ROBIN connect to?
ROBIN connects via standard connectors to the leading ERPs on the market, including SAP and Sage, as well as to existing MES and CMMS. The ERP remains the contractual system of record; ROBIN takes over for detailed scheduling and real-time operations.
Do you need perfect data to get started?
No. Your routings, your operation times, even approximate ones, and your resources are enough, with no prior overhaul of your information system: ROBIN connects to the existing ERP, MES and CMMS. The initial diagnosis identifies the data available and the gaps to fill, then ROBIN flags missing, inconsistent or outdated data before it skews a decision. Accuracy improves with use.
What does an MRO ontology offer over a generic model?
It describes the real objects of the shop floor — work order, routing, emerging work, resource, part, TAT — rather than forcing them into a generic model. Scheduling rules can then be expressed in the business vocabulary.
Where is our data hosted, and does it stay confidential?
Your data belongs to you and is never shared. ROBIN is available as SaaS, hosted in the cloud in France, Europe or the United States (GDPR compliant), with a separate environment for each customer. It can also be installed on your own servers if your security policy or a defence context requires it. Zozio is a French software publisher: the hosting choice is contractual.
They use it

Our big focus is data-driven transformation: reducing our carbon footprint, optimising our productivity, and securing business diversification — working on drones right now, for example. One phrase that has really stayed with me, from Yves Dubreuil at Renault: “When the only tool you have is a hammer, you see every problem as a nail.
All testimonialsGoing further
What we write about ROBIN.DataFlow.
Article
Why a native MRO ontology beats a generic model
Routings, emerging work, resources: what a data model designed for MRO changes.
Article
Coexisting with SAP without becoming a SAP module
The ERP holds the contract, execution holds the sequence. Where the line runs, and why it must stay clear.

Case study
Reducing TAT in an MRO shop floor
The data foundation put in place and the gains achieved.
In the platform
One platform, six building blocks.
From deployment to scheduling, each building block feeds the next — a single reference base, a single flight plan.
ROBIN.Deploy
Consulting, diagnostics and deployment
ROBIN.DataFlow
The data foundation for your operations
ROBIN.Tracking
Real time, measured at every step
ROBIN.Cockpit
The whole shop floor, visible live
ROBIN.Scheduling
The flight plan, continuously optimised
Integrations
Connectors, workflows and automation
Take action
See ROBIN.DataFlow on your data.
A demo prepared with a scheduling engineer, on your shop floor.