Book a demo
Zozio
Book a demo

Product

Industries

Roles

Use cases

Media

About

Product · Integrations

Connect ROBIN to the rest of your information system.

ERP, MES, CMMS and collaboration tool connectors, an open REST API, and a visual workflow engine. An open, governed ecosystem that automates everything from a Teams notification to an action on a shop-floor sensor.

  • SAP · Sage
  • MES / CMMS
  • Microsoft Teams
  • REST API & webhooks
  • IoT actions
Take controlPlatform overview
ROBIN workflow builder — visual trigger / conditions / actions editor

The ecosystem

It builds on your systems, and takes over where they fall short.

Robin aggregates your resource data in real time — machines, operators, tools, containers, materials — to schedule in the real world, not in a perfect factory.

Machine / station

Workstations, machines, ovens & booths

ConnectsRobin plugs into it.

Natively coversRobin takes over.

Typical constraints

  • Availability: maintenance downtime, breakdowns, shifts
  • Capacity: one part at a time or per batch
  • Setup / changeover time to minimise
  • Mandatory cycles: autoclave, oven, paint booth

Autoclave / oven — batching

Compatible parts (same programme, same temperature) are grouped into a fixed-duration cycle. Poorly scheduled = half-empty cycles = lost capacity.

Data sources · France / Europe

Siemens OpcenterAstrée AquiwebCarl SourceDIMO Maint

Data sources · Aerospace MRO (worldwide)

IBM MaximoIFSiBASEt SoluminaExcel

ROBIN coverage

ROBIN

Operator & skill

Skills, authorisations, availability

ConnectsRobin plugs into it.

Natively coversRobin takes over.

Typical constraints

  • Availability: attendance, shift management
  • Skills & authorisation
  • Training schedule management
  • Management of multi-skilling and the floating team
  • Co-activity: some tasks require 2 people

Part-145 approval

An expired NDT certification blocks assignment. Robin blocks it, and identifies the senior operator who can train (dual resource).

Data sources · France / Europe

MercateamAG5KelioMicrosoft Entra ID

Data sources · Aerospace MRO (worldwide)

AMOSTRAXAG5Excel

ROBIN coverage

ROBIN

Tool / tooling

Tooling, equipment, service life

ConnectsRobin plugs into it.

Natively coversRobin takes over.

Typical constraints

  • Availability: often a single unit (bottleneck)
  • Calibration valid if inspection equipment
  • Location / FOD in MRO
  • Lifespan / remaining wear
  • Tool ↔ operation compatibility

Single item + FOD

A tool shared between WOs becomes a hidden bottleneck; a tool that cannot be found prohibits return to service (Foreign Object Damage).

Data sources · France / Europe

TDM SystemsZOLLERNexess

Data sources · Aerospace MRO (worldwide)

NexessCribMasterPower Aero

ROBIN coverage

ROBIN

Container

Cradles, bins, supports

ConnectsRobin plugs into it.

Natively coversRobin takes over.

Typical constraints

  • Availability in quantity (cradles, bins)
  • Type ↔ part compatibility
  • Mandatory packaging (protection, ESD)
  • Real-time location (RFID / RTLS)

Dedicated engine cradle

Not enough carriers = the part cannot move on; some parts cannot wait outside a container (ESD).

Data sources · France / Europe

Paragon IDTraxensCHEPReflex WMS

Data sources · Aerospace MRO (worldwide)

NexessCHEPExcel

ROBIN coverage

ROBIN

Material / stock

Parts, components, stock, material

ConnectsRobin plugs into it.

CompleteRobin enriches.

Typical constraints

  • Component availability to start
  • Waiting for supply (lead time)
  • Quality status: batch on hold / quarantine
  • Shelf life / expiry date (adhesives, seals, chemicals)
  • Batch / serial traceability

Batch in quarantine

A quality-blocked batch prohibits launch; adhesives and seals have a shelf-life limit (DLU) that spoils the material.

Data sources · France / Europe

SAPSage X3CegidReflex

Data sources · Aerospace MRO (worldwide)

AMOSTRAXIFSSAP

Data sources · France / Europe

SAPSage X3CegidReflex

Data sources · Aerospace MRO (worldwide)

AMOSTRAXIFSSAP

Quality & Metrology

Inspection equipment & metrology

ConnectsRobin plugs into it.

Natively coversRobin takes over.

Typical constraints

  • Valid calibration (calibration due date)
  • Availability: MMT / shared bench
  • Mandatory checkpoints (FAI, inspection)
  • Mandatory delays between operations

Shared CMM + calibration

The resource must be calibrated (valid due date) and available: a CMM shared between operations creates a queue.

Data sources · France / Europe

HexagonZeissBeamexQualios

Data sources · Aerospace MRO (worldwide)

BeamexFlukeNet-InspectGAGEtrak

ROBIN coverage

ROBIN

WIP tracking

Location, progress & part status

Natively coversRobin takes over.

Natively coversRobin takes over.

What Robin tracks in real time

  • Order types: production, repair, logistics, maintenance, shipping
  • Real-time physical location (zone, workstation, stock, queue)
  • Real-time operations visibility — the end of the "black box"
  • Waiting time per step → bottlenecks & “lost” parts
  • Automated status: in progress / waiting / quality hold / ready ...

The only one to geolocate your WIP

You cannot schedule what you cannot see. By tracking WIP in real time — as automatically as possible — Robin detects bottlenecks and lost parts instantly, and realigns the schedule with reality. That is the condition for a schedule that holds.

ROBIN coverage

ROBIN

ROBIN coverage

ROBIN

Workflow builder · No code

Creating an automation takes a few minutes, without writing a single line of code.

The ROBIN workflow builder works like a visual editor: you choose a trigger, add conditions and chain actions together. A methods manager or a scheduler creates and edits their own automations, without going through the IT department or a custom development.

  • 01

    Choose the trigger

    You select the starting event from a list: routing time overrun, order creation in the ERP, a WO entering a zone, a button press at the workstation, or a fixed time.

  • 02

    Set the conditions

    You add filters using drop-down menus — shop floor, criticality, customer, resource, threshold in minutes. No formula to write.

  • 03

    Chain the actions

    You drag in the actions to run: notify Teams, write to the ERP, reschedule, light up a tag's LED, update an electronic label.

  • 04

    Test, then publish

    The workflow first runs on test data. Once validated, it is published and versioned, and every run remains available for review.

  • 05

    Monitor and govern usage

    A monitoring dashboard shows runs, failures and the volume triggered per workflow. Safeguards cap the number of actions per hour, require human approval for sensitive actions (rescheduling, ERP write-back) and automatically shut down a runaway workflow.

ROBIN workflow builder — visual trigger / conditions / actions editor

The workflow engine

One trigger, conditions, actions.

Every shop-floor event can trigger a sequence of actions in ROBIN as well as in your other tools. Workflows are built visually, tested on test data and versioned before going into production.

  • Trigger

    A WO exceeds its routing time

    Field event, status change, indicator threshold, order creation in the ERP, a button call at the workstation, or simply a schedule.

  • Condition

    If the deviation exceeds 45 minutes and the WO is a priority

    Filters on ROBIN data and on fields coming from the ERP: criticality, customer, shop floor, resource, delivery commitment.

  • Actions

    Actions

    • Notify the shop-floor supervisor in Microsoft Teams
    • Light up the LED on the relevant part's tag
    • Trigger a rescheduling and publish the sequence
    • Write the event to the ERP and to the history

The building blocks combine freely: a single trigger can feed several branches, one action can trigger another, and every run stays traced. The number of possible scenarios is not limited by the product, but by what your shop floor needs to automate.

The connector catalogue

Ready-to-use connectors for industry.

The most requested integrations ship pre-configured. The rest go through the REST API, webhooks or a file drop, with no custom development on your side in most cases.

  • ERP

    The contract stays in the ERP

    Work orders, routings, bills of materials and milestones synchronised both ways, with no re-entry.

    • SAP
    • Sage X3
    • Oracle
    • Microsoft Dynamics
    • Infor
    • Divalto

  • MES / CMMS

    Execution and maintenance

    Production declarations, maintenance orders and machine statuses consolidated with the plan.

    • MES
    • CMMS
    • SCADA / OPC UA
    • Historian

  • Collaboration

    Alerts where the team works

    Notifications, approvals and arbitration requests pushed into the tools already open.

    • Microsoft Teams
    • Outlook
    • Slack
    • SMS
    • Google Workspace

  • Data & BI

    Your analyses, your tools

    Continuous export to the data warehouse and management dashboards.

    • Power BI
    • Tableau
    • Snowflake
    • BigQuery
    • CSV / SFTP

  • Open by default

    REST API, webhooks, files

    Everything the interface does is available through the API. Events go out as webhooks, files through a scheduled drop.

    • REST API
    • Webhooks
    • Event stream
    • EDI / flat files
    • MCP

  • Connected objects

    The shop floor becomes actionable

    ROBIN.Tracking tags and beacons don’t just report information back: they receive orders.

    • BLE / UWB tags
    • Beacons
    • Electronic labels
    • Call buttons
    • Environmental sensors

An actionable shop floor

Your sensors don’t just report back: they receive orders.

An electronic label fitted to the bin shows the current WO and lights up when a condition is triggered. Pick a rule to see what the operator sees.

  • No active condition

    Standard display

    The label shows the WO, the current operation and the workstation. The LED stays off and the battery is preserved.

  • If the WO becomes priority 1

    Blue LED + instruction displayed

    Scheduling moves the WO up the sequence: the LED turns blue and the label shows which part to pick now.

  • If an inspection is required

    Amber LED + destination workstation

    The mandatory checkpoint is reached: the label shows the test bench and the LED turns amber until the pick-up scan.

  • If the routing time is exceeded

    Red LED + buzzer + Teams alert

    The deviation exceeds the threshold: the LED flashes red, the buzzer sounds and the shop floor supervisor receives the notification.

Discover ROBIN.Tracking

The scenarios

Ten examples among endless combinations.

Every shop floor writes its own. These scenarios are configured in minutes, with no development.

Security and governance

Open, yet governed.

An open ecosystem is only valuable if IT keeps control. Explicit rights, managed secrets, traced executions and safeguards on sensitive actions.

  • Authentication and roles

    SAML / OIDC SSO, roles and scopes per shop floor: every workflow runs with explicit rights.

  • Full logging

    Every execution is timestamped, traced and replayable. Who triggered what, when, and with what result.

  • Managed secrets and keys

    Encrypted credentials, API keys with a limited lifespan, isolation per connector.

  • Sandbox and versions

    A workflow is tested on test data, versioned and restorable. Nothing goes into production by accident.

  • Controlled hosting

    European cloud or on-premises deployment depending on your constraints: data stays within your perimeter.

  • Execution safeguards

    Quotas, mandatory human validation on sensitive actions, emergency stop workflow by workflow.

Frequently asked questions

What IT departments and methods teams ask us.

Do you need to know how to code to create a workflow?

No. Workflows are built visually: a trigger, conditions, and actions. Technical teams retain the option to call the REST API or write a custom step when the situation demands it.

Does ROBIN replace our ERP?

No. The ERP remains the contractual reference system: work orders, routings, and bills of materials. ROBIN takes over for detailed scheduling, real-time operations, and automated responses to disruptions.

Can sensors be controlled from a workflow?

Yes. ROBIN.Tracking tags and beacons expose actions: LED activation, buzzer, immediate position request, transmission frequency change, and electronic label update.

What happens if a third-party system is unavailable?

Executions are queued, automatically retried, and flagged if the failure persists. No shop-floor event is lost.

How are access rights managed?

Via SSO and application roles, with a scope defined per site or per shop floor. Sensitive actions may require human approval.

Is there a public API?

Yes. Everything the interface does is accessible via REST API, with outbound webhooks on business events.

They use it

Faustine LiabastreCAP Performance Manager, L'Oréal
Our story with Zozio was born from a need: to geolocate and track our tank fleet. Today, the application covers 4 roles — production assistant, washer, technician, and manufacturer. Zozio means time saved at work and less mental load. It also delivers a general efficiency gain, whether for operators or for Cosmetic Active Production.
L’Oréal Cosmétique Active ProductionAll testimonials

Going further

What we write about integration.

All articles

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.

Take action

Let's connect ROBIN to your IS.

A scoping workshop with your IT department to list the priority flows, access rights and scenarios.

Take controlTalk to an expert