All your questions about ROBIN, in one place.

Static schedulingSchedulingDetermination of the order and timing of each operation on each resource, subject to capacity, skills, and deadline constraints.See in the glossary → freezes a sequence at a given moment, often in the morning: it becomes obsolete at the first disruptionDisruptionAn unplanned event that invalidates the schedule: machine breakdown, absence, missing part, non-conformity, additional work discovered during inspection.See in the glossary →. Dynamic scheduling recalculates the sequence at every shop-floor event, within the same constraints, without redoing everything by hand.

MRPMRPMaterial Requirements PlanningNet requirements calculation: determines what to procure and what to release, based on orders and bills of materials. Operates on the assumption of infinite capacity.See in the glossary → calculates requirements at infinite capacity: it says what to produce and by when, without knowing whether the shop floor can deliver. ROBIN is an APSAPSAdvanced Planning & SchedulingAdvanced planning and scheduling software that calculates an optimised sequence under constraints (capacity, skills, materials). The software category to which ROBIN belongs.See in the glossary → that schedules at finite capacity — it sequences every operation on every resource, taking into account real-world availability, routings, and shop floor constraints. The ERPERPEnterprise Resource PlanningIntegrated management software (SAP, Sage X3, Oracle…). It handles orders, stock, bills of materials, and work orders, but schedules by the week, not by the hour.See in the glossary → remains the system of record; ROBIN takes over for detailed scheduling.

It is an electronic label attached to WIPWIPParts, batches or equipment committed to production and not yet completed. The French term for WIP.See in the glossary →WIPWork In ProgressWork in progress: everything engaged on the shop floor but not yet complete. High WIP ties up working capital and extends lead times.See in the glossary →, a container or a pallet, which displays up-to-date information (reference, batch, work order, priority, next step) without being reprinted, and which is geolocated in real timeReal timeData updated continuously from the shop floor, with no re-entry or consolidation delay.See in the glossary →. It replaces the paper label and the jobJobIn MRO, the full set of operations carried out on a given piece of equipment, from its entry to its exit. Equivalent to a single project.See in the glossary → traveller.

A barcode is preferred when the information is stable and WIP volumes are very high; a connected electronic label makes sense when priorities change often, when searching for WIP costs time, or when the goal is a paperless shop floor.

It is the ability to know, at any moment and without going to the shop floor, which parts are in production, at which stage, on which machine, for how long, and where they are physically located. It relies on two building blocks: progress tracking and real-time geolocation of WIP.

The service level — or OTDOTDOn-Time DeliveryOn-time delivery rate: the proportion of orders delivered by the date promised to the customer. The benchmark indicator for industrial performance.See in the glossary →, On-Time Delivery — is the percentage of orders delivered within contractual lead times. It is the indicator that measures how well customer commitments are met, and in many specialist industries, an element of the commercial value proposition, not merely an internal KPIKPIKey Performance IndicatorKey performance indicator tracked by management (TAT, OTD, OEE, service level…).See in the glossary →.

Touch time is the time actually worked on the equipment. TATTATTurnaround TimeTotal cycle time for a job, from equipment intake to return to the client. The central MROMROMaintenance, Repair & OverhaulMaintenance, repair and overhaul of aeronautical equipment. Unlike serial production, the scope of work is only known after inspection.See in the glossary → indicator: it determines both invoicing and client satisfaction.See in the glossary → is the total lead time. The gap between the two is waiting — and that is where most of the opportunity lies. Measuring them separately is the first step of any TAT-reduction project.

TAT (Turn-Around Time) is the total time between receiving equipment for overhaul and returning it to the customer. It covers everything: assessment, waiting for parts, work, testing, quality control, and dispatch. It is the primary contractual commitment of an MRO workshop to its airline customers.

With infinite capacity, the tool schedules work orders on the assumption that resources will keep up. With finite capacity, it refuses to schedule more than machines, furnaces, and operators can absorb — and flags the gap. That is what turns a schedule into a decision-making tool.

It is the proactive distribution of work across operators and workstations so as to avoid overload peaks and troughs, taking into account actual skills, absences, shifts, and leave. LevellingLevellingDistribution of workload over time to avoid peaks and troughs on a resource.See in the glossary → requires finite-capacity thinking: overloads are detected at scheduling time, not discovered mid-month.

Tracking follows a state and a progression: at which step, in which status, since when. Track & trace adds traceabilityTraceabilityAbility to reconstruct the complete history of a part: who, when, where, with what, and under which control.See in the glossary →, meaning the complete, auditable history of the item. Geolocation gives its physical position in real time.

A work order can be declared "awaiting inspectionInspectionPost-disassembly inspection phase that reveals the actual condition of the equipment and determines the real work content of the job.See in the glossary →" (tracking) and have been sitting for three days in a forgotten buffer zone (geolocation): that is why a shop-floor project often needs all three.

It receives real-time data — people, parts, processes, available resources — and automatically recalculates priorities. No meetings, no Excel. See the original page

An ERP manages requirements, stock, and invoicing at a daily or weekly granularityGranularityThe level of detail in the temporal or organisational breakdown of the schedule: by week, day, hour, or operation.See in the glossary →. It does not sequence operations across resources at an hourly level, nor does it recalculate when a diagnosis overruns. That is the role of an APS, which connects to the ERP rather than replacing it.

No. Your ERP remains the system of record for work orders, routings and bills of materials: it was designed for management, not for detailed scheduling. ROBIN connects to it through standard connectors (SAP, Sage and others) and takes over what it cannot do: dynamic finite-capacity scheduling and real-time shop-floor data (tracking, geolocation, actual progress).

The same goes for an existing MRO system: ROBIN pulls its work orders, routings and standard hours, and adds the layer it lacks. Your ERP investment is preserved.

Excel can display a schedule, not recalculate it under constraints at every event. It knows neither the real capacity of your resources, nor sequence constraints, nor what is happening on the shop floor right now: the plan is right when printed and wrong an hour later. It relies on manual entry, concentrates errors and exists in only one up-to-date version, held by one person.

ROBIN takes the same data, adds the real constraints and shop-floor data (progress, WIP geolocation), and recalculates automatically at every event. Without that shop-floor data, a new planning tool would just be Excel with a different interface.

Yes. Replenishment dates are used as earliest eligibility dates: an operation cannot be scheduled before its material is available. When a supplier date slips, ROBIN recalculates and flags the impact on the affected delivery dates.

It depends on what you need.

ROBIN can connect to your existing CMMSCMMSComputerised Maintenance Management SystemMaintenance management software: preventive plans, corrective interventions, machine history, spare parts.See in the glossary →, or replace it: preventive and corrective maintenance, history per piece of equipment, spare parts and reliability indicators. Plus real-time tracking of your tooling if needed, and its scheduling directly in the production plan.

ROBIN also specialises in aerospace maintenance and repair: technician qualifications, regulatory traceability and management of urgent maintenance.

It depends on what your MESMESManufacturing Execution SystemManufacturing execution system: work order tracking at the workstation, reporting, real-time traceability. Sits between the ERP and the machine.See in the glossary → covers. ROBIN can connect to your existing MES, or take over work order management if you don't have one: releasing and tracking work orders, progress reporting by operators, time spent and operation traceability. Plus dynamic finite-capacity scheduling and real-time location of WIP.

Through a documented, versioned RESTRESTREpresentational State TransferStandard web APIAPIApplication Programming InterfaceAn interface that enables two software systems to exchange data automatically, without manual re-entry.See in the glossary → style, used to connect ROBIN to other software within the information system.See in the glossary → API with scope-based access tokens. Standard connectors exist for SAP, Sage and the leading MES and CMMS platforms. The ERP remains the reference for work orders, routings and material requirements; ROBIN takes over detailed scheduling and real-time operations. It co-pilots, it does not replace.

Yes. The schedule accounts for real-world capacities: machines, qualified operators, tooling, containers, and available materials. An operation is never assigned to an unavailable resource.

No. ROBIN proposes a sequence and quantifies the impact of each option; the decision remains human. The schedulerSchedulerPerson responsible for building and maintaining the shop floor schedule on a daily basis.See in the glossary → can freeze an operation, force a customer priority or compare two scenarios before publishing, and the engine recalculates around those decisions instead of overriding them. The shop floor receives a sequence someone has validated, not an unreviewed automatic output.

No. ROBIN does not assume fixed durations: times are defined per operation-reference pair, and the plan is recalculated with every new piece of information (diagnosis, actual progress measured by tracking, emerging work). Actual times are continuously compared with theoretical ones, and estimates become more reliable with use, with no extra data entry.

Yes. Qualifications are modelled as an assignment constraint: an operation can only be scheduled to a person authorised to carry it out. Absences, leave, and training reduce the available capacity for the tasks concerned, and the plan accounts for this.

Yes. Campaign groupings, sequence-dependent changeover times, mandatory cleans between families, and product compatibilities are all built into the engine. ROBIN finds the sequence that minimises unproductive time whilst respecting these rules.

From the projected loadLoadVolume of work to be carried out on a resource over a given period. Always compared against capacity.See in the glossary → on each resource, compared against its actual capacity over the horizon in question. The bottleneckBottleneckA resource whose capacity limits the throughput of the entire shop floor. Often a furnace, a bench, a single machine, or a rare skill.See in the glossary → is not fixed once and for all: it shifts according to the product mix, and ROBIN recalculates this projection with every reschedulingReschedulingFull recalculation of the schedule after a disruption. With ROBIN, the operation takes a few seconds rather than several hours.See in the glossary →.

Yes. These durations are handled as time constraints between operations, with minimum and maximum bounds. ROBIN respects them during sequencingSequencingThe order in which operations are processed on a given resource. Good sequencing reduces changeover times.See in the glossary → and flags any cases where a waiting period risks exceeding the permitted limit.

Cleaning operations are modelled as sequence constraints: depending on the outgoing and incoming product, ROBIN automatically inserts the required duration and type of cleaning, and finds the sequencing order that minimises their number without ever violating a compatibility rule.

Yes. ROBIN was designed for the job shop: different routings from one work order (WOWOWork OrderDocument that triggers and tracks the manufacture or repair of a batch or part. Contains the routing, quantities, and dates. French equivalent: OF (Ordre de Fabrication).See in the glossary →WOWork OrderThe English equivalent of the WO (work order).See in the glossary →) to the next, machines shared across programmes, variable batch sizes. The engine reasons operation by operation, not line by line — it handles a one-off part and a run of 200 within the same plan.

Yes, and that is precisely the point: these three flows share the same resources, so they must share the same plan. Relative priorities are configured by flow, customer, or programme, and applied consistently at every recalculation.

The portion covering scheduling uncertainty, yes. The portion covering supplier risk, no — and ROBIN makes no such claim. The diagnostic separates the two before any commitment.

The material coverage of each work order is assessed prior to release, based on current stock levels and expected receipts. At-risk WOs are flagged with the time remaining before they reach the workstation.

No. Orders and contracts remain in the ERP. ROBIN provides the required date and the coverage alert; the purchasing decision stays with you.

From the actual sequencing of operations, calculated at finite capacity against your constraints: skills, tooling, and calendars. It reflects the moment when material must be at the workstation — not a standard lead time applied at WO release.

Yes: skills and qualifications, shared tooling and resources, alternative routings, imposed sequencing orders, team calendars, subcontractingSubcontractingOperations entrusted to an external supplier (surface treatment, machining, NDTNDTNon-Destructive TestingA set of techniques for inspecting a part without damaging it (dye penetrant, magnetic particle inspection, ultrasonics, radiography). A mandatory step and frequent bottleneck in MRO routings.See in the glossary →). Introduces transport and waiting delays outside the shop floor's control.See in the glossary →. These are the constraints that make an Excel schedule unworkable on the shop floor.

Yes, that is in fact the primary use case. For one-off parts, measurement is taken by operation type rather than by part reference, which yields usable standards where traditional time studies never have a sufficient run size.

No. It calculates the variance and proposes a correction; validation remains with the methods office. A workflow can then propagate the validated value to the ERP — never without your approval.

Not necessarily, and this project's experience demonstrates as much. The scope was refocused to deploy manual scheduling across all mini-plants before automating — priority given to adoption and data standards. A sophisticated algorithm on an isolated scope delivers lower service levels than a simple tool used everywhere.

Contractual priorities, AOGs and criticality levels enter the calculation as explicit constraints, alongside resource and material availability. ROBIN does not decide for you: inserting an urgent job is simulated before validation, with the list of orders it pushes back and by how much.

Once the plan is validated, the work queue is reordered at the workstation with the reason shown (customer priority, milestone at risk, reworkReworkRework of a non-conforming part to bring it into conformance. Consumes unplanned capacity.See in the glossary →), and any delay caused elsewhere is recorded with its cause.

About two minutes* for a complete reschedule after a disruption, so trade-offs can be made during the production day rather than the next morning.

*Average observed duration. It varies with the number of work orders to schedule.

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

Rework, also called repair or reintegration depending on the plant, can come from a defect found at quality control, a non-conformity during production or a customer return.

ROBIN treats it as a new operation to schedule, with its priority and the skills it requires. It reinserts it into the sequence and shows its impact on the other parts.

The conflict is resolved locally: only the operations concerned are shifted, the rest of the plan stays as it is.

Requirement dates are recalculated alongside it in under two minutes. Procurement immediately sees which requirements have moved forward and which have been pushed back, along with the variance against the original order.

The downtime is declared, the engine recalculates the schedule around the constraint and proposes a new sequence in about two minutes. Operations that put a customer milestone at risk are flagged, with the quantified impact.

No. Shop-floor declarations, scans, and ERP data are sufficient to get started. Automatic traceability improves data freshness and eliminates manual entry, but it is a complement — not a prerequisite.

Several years for a standard tag, depending on the transmission rate. This rate is configurable per workflow: faster for critical items, slower elsewhere, preserving battery life.

Zone or workstation level with BLEBLEBluetooth Low EnergyLow-power radio technology used for object location beacons. Accuracy at zone level (a few metres).See in the glossary →, and to within tens of centimetres with UWBUWBUltra Wide BandPrecise radio location technology (30 cm to 1 m), used to track WIP down to the nearest workstation.See in the glossary →. The technology choice depends on the granularity needed to manage your flows.

A lightweight infrastructure of beacons and tags, sized to your site layout. Deployment requires no overhaul of your information system and no production stoppage.

Yes. Indoor and outdoor technologies are combined, so a work order, container, tank or tool can be tracked on the shop floor as well as during a road transfer between sites. Position, condition and compliance remain visible at all times.

No. Position and status changes are captured automatically: no scanning, no badging, no end-of-operation entry.

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

Yes. Each part, batch, or container can be tracked individually via geolocation, with a timestamped history of operations and movements. This history is viewable and exportable without manual reconstruction.

Via indoor and outdoor geolocation, with no operator input required. Each container or tooling item carries a tag; ROBIN continuously knows its position, status, and history. Teams stop searching for equipment, and actual availability feeds directly into the scheduling calculation.

Yes, for zones that require it. The Zozio hardware catalogue includes ATEX- and IECEx-certified tags and beacons, suitable for gas and vapour atmospheres — alcohols, solvents, fragrances — as well as the dusty atmospheres of weighing zones. Selection is based on your zoning plan: certified hardware is deployed where the zone demands it, standard hardware elsewhere. Certificates and compliance data sheets are provided in the installation dossier.

ROBIN.Tracking locates WIP via sensors, with no operator input. Every part, bin, or carrier appears on the shop floor plan, along with the time spent at its current position. Shop floor declarations complement progress tracking.

Yes: by workstation, by period, and by reason, based on operations actually carried out. Recurrence identifies the operation or work instruction requiring rework.

Via WIP location tracking and existing declarations: every zone change is timestamped, with time spent on site. No additional input is required from operators.

Less than 3 months from signature to go-live, sensor installation included. Deployment happens in phases, building by building for example, then extends at your teams' pace. A ROBIN.Deploy project manager is on site during commissioning.

Based on time spent in the work zone and operations logged against the asset. These are actual recorded hours, not a calendar-based estimate.

No. You start with the most critical assets or those most frequently searched for — that's where the immediate gains are. The rollout then proceeds at your teams' own pace.

Via a sensor attached to the tool and beacons installed on the shop floor. The position updates automatically, with no scanning or manual entry. Depending on the required accuracy, tracking works at zone level or down to the nearest metre.

The choice depends on the required accuracy and available infrastructure. ROBIN is technology-agnostic and integrates a catalogue of technologies: BLE, UWB, wired or wireless RTLS, GPS for outdoors. On this project, a cable-free BLE infrastructure with autonomous anchors and 4G gateways achieved accuracy of under 15 ft (≈ 4,5 m) across two buildings.

Because a priority that is not visible on the part is not applied. The label displays up-to-date work order data, communicates priority changes decided by scheduling, and remains geolocated in real time. It replaces the paper traveller — with, on the group's North American deployment, a target of 1 day gained per work order.

It eliminates manual entry and therefore lag. When geolocation automatically triggers a stage change, dwell time is measured without human intervention — and the delay alert fires at the right moment. It also allows standard hours to be challenged against actual observed durations, which makes promised dates more reliable.

Yes, provided the right hardware is selected. On this project, the geolocation tags are made of POM, with an IP69K casing, operating range −30 °C to +60 °C, and their chemical compatibility with the site's cleaning products was validated prior to deployment.

It is the condition for lasting adoption. A digital schedule without automatic shop-floor data reverts to a schedule that requires manual entry. Geolocation eliminates re-keying for everything that can be measured: zone entry and exit, dwell time, inventory, availability.

Making wait time visible. Real-time geolocation provides actual dwell time by zone and by test benchTest BenchA workstation equipped to test equipment after reassembly. A scarce resource and frequent bottleneck at the end of the routingRoutingmanufacturingAn ordered sequence of operations required to produce or repair a part, with the associated times, resources, and skills.See in the glossary →.See in the glossary →, automatic WIP inventory, movement spaghetti diagrams, congestion heatmaps — and enables comparison of the declared status in the ERP with the physical reality of the shop floor.

Status and dwell-time tracking, before anything else. It requires no infrastructure and immediately delivers a map of the queues. Geolocation comes next, to eliminate manual data entry for everything that can be deduced from a position, automate stage-change tracking by geofence, and measure actual downtime on the test bench.

To carry the right information on the object, continuously and without paper. It displays the reference, batch, priority and next step; it updates remotely when scheduling recalculates the sequence; it flags urgent jobs, such as an AOGAOGAircraft On GroundAircraft grounded due to a missing part or repair. An absolute emergency: every AOG request takes priority over everything else on the shop floor.See in the glossary → in MRO; it is geolocated in real time, so the object can be found at once; it carries a QR link to the documentation. It replaces the paper job traveller, removes the risk of an outdated version and secures digital sign-off.

Both — but the lasting value lies in optimisation. Locating a piece of equipment saves time immediately — 20 min per day per person in the cosmetics business case. Measuring utilisation rates enables you to guide investment decisions, identify bottlenecks, and plan ahead. And those gains compound.

Average TAT by job type, the number of manual rescheduling actions over a given period, and the late-delivery rate. If all three driftDriftGrowing gap between the planned schedule and shop floor reality. Measured in accumulated days of delay.See in the glossary → together, the problem is the tool, not the teams.

Yes. Positions, statuses, actual durations, and KPI values are continuously logged. Replay a day, a closed work order, or a completed batch, and generate the spaghetti diagram of the actual path to identify back-and-forth movements and waiting times.

Yes, in no-code. You choose the widget (card, table, line chart, gauge, breakdown, counter), the source data and scope, then save the view for your team. TAT by part family, waiting time at a workstation, routing compliance: the indicator is built without any development and without going through our team.

As soon as ERP data and the first field readings come through — typically a few days after connection. Views are then completed progressively as sensors and connected workstations are deployed.

Yes, for day-to-day monitoring. Figures come directly from the shop floor and the scheduler, with no manual re-entry or consolidation. Exports to Excel or Power BIBIBusiness IntelligenceReporting and dashboard tools that leverage company data (Power BI, Tableau, Qlik).See in the glossary → remain available for ad-hoc analysis.

By continuously comparing actual progress against the theoretical routing, and by detecting abnormal inactivity. The alert surfaces visually, without having to search through a report.

OTD (On-Time Delivery), average TAT (Turnaround Time), WIP (work in progress) and service level, along with workstation load and queues. Values update continuously from shop-floor data.

No. During the pilot, both run in parallel: this is what allows definition discrepancies to be verified. Manual reporting stops when your teams find it is saying exactly the same thing — only later.

Yes, provided definitions are shared: ROBIN applies the same TAT and OTD calculation method to every shop floor, line, and workstation on the site. This is often the first benefit observed — a common language between scheduling, production, and quality, even before performance gains are realised.

At the diagnostic stage, using your historical data: average TAT and variance, OTD, WIP, and station utilisation rates. This starting snapshot serves as the reference for all subsequently measured gains. Without a baseline, no gain can be demonstrated.

From production events themselves: shop floor declarations, WIP location by ROBIN.Tracking, ERP and MES data. The indicators are not re-entered — they are derived from the actual flow. That is what makes them available on the same day.

The pilot starts on a defined scope and produces its first variances within a few weeks. A full scope is live in under 3 months.

This depends on the spread of the operation. ROBIN displays the number of occurrences and the standard deviation alongside the mean, so you can judge whether the sample is sufficient before making corrections.

By geo-locating the asset and automatically timestamping its zone entries and exits. ROBIN derives the number of cycles, actual cycle time (min, max, average), total idle time, and real-time availability rate — both by asset count and by capacity. No operator input is required.

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.

Yes. ROBIN.DataFlow streams data continuously to Power BI, Tableau, Snowflake or BigQuery, via REST API, webhooks or a scheduled file drop. ROBIN does not try to replace your BI: it supplies the shop-floor data it was missing.

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.

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

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.

Through shop floor declarations and ROBIN.Tracking, which locates WIP without manual entry. Progress feeds back continuously during production: the schedule is recalculated against shop floor reality, not against what the ERP assumes.

From shop floor declarations and WIP location tracking by ROBIN.Tracking. The start and end of an operation are timestamped with no additional input: the measurement comes from the flow, not a stopwatch.

Through short, on-station sessions, on the actual screens teams will use in practice. Documentation and onboarding guides remain accessible within the tool after go-live.

A methods or scheduling lead for a few hours per week, an IT contact for access and data flows, and shop floor managers available during modelling workshops.

A mixed team: a scheduling engineer for the business rules and a project manager for deployment and on-site adoption. The project is run as an operational project, not an ITITInformation TechnologyEnterprise IT in the broad sense: teams, systems and infrastructure.See in the glossary → project.

From signature to go-live, allow less than three months in most cases, support included, where heavyweight APS projects take 16 to 24 months. A demonstration on your own data can be set up in a few days.

You then start on a critical scope (a workshop, a line, a resource) and extend at your teams' pace. Most of the work goes into structuring routings and resources, not into configuring the software. The timeline is split into phases, with milestones and success criteria defined at the outset.

No. Deployment starts on a pilot scope — a shop floor, a line, a cellCellGrouping of workstations dedicated to a part family or a process step.See in the glossary → — in under 3 months. Excel runs in parallel until confidence in the ROBIN schedule is established, then fades away on its own.

Scoping the data flows and opening access. The business configuration — constraints, priorities, routing rules — is carried out with your production teams, not your developers.

The sponsor is typically the head of manufacturing or the head of operations, with a single point of contact on the Zozio side (ROBIN.Deploy) throughout the project. Senior leadership validates the business case and monitors the KPIs; they do not need to manage the rollout on a day-to-day basis.

The approach is incremental: a pilot scope in under 3 months, value demonstrated, then rollout. Change management is part of ROBIN.Deploy — training, on-site support, and a dedicated project manager until you're self-sufficient. No 2-year tunnel.

You're never on your own. A dedicated project manager structures the deployment, trains your teams, and ensures follow-up until you reach full autonomy. After go-live, you benefit from comprehensive support in your language and continuous updates.

The cockpitCockpitROBIN's operations management module: real-time shop floor view, indicators, alerts, and decision simulation.See in the glossary → displays equally well on a large shop-floor screen, a desktop workstation, or a tablet. Views are designed to be read at a glance.

No, that is the whole point. Location is automatic and progress comes from the declarations that already exist in your tools: no extra form, neither during nor at the end of a shift. The shop-floor screen shows the work queue: what needs doing, in what order, with which tooling. The operator reads it, they do not fill in a spreadsheet.

The screen shows this before you go to fetch it, with its location or reason for unavailability. The scheduler accounts for this and suggests an alternative operation.

No. ROBIN tracks parts, tools, WIP and equipment, not people. Metrics are produced by workstation and by flow, never by individual.

The screen displays a list: what needs doing, in what order, and with which tooling. It takes thirty seconds to grasp. If lengthy training were required, the tool would be poorly designed.

It is our design priority. The interface is built for the shop floor: a workshop map, a work queue, alerts. An operator or team leader sees at a glance what to do, in what order, and where each part is. Getting started takes a few hours, training included, and there is no per-user cost, so the whole shop floor has access. Moving away from Excel becomes an immediate time saver, not a burden.

By scope and by role, with separate API tokens. There is no per-user cost: opening access to an entire shop floor does not affect the budget, so security is never traded off against licences.

Yes, at any time and without our involvement: full export via API or file, in a usable format. Data portability is written into the contract.

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 (GDPRGDPRGeneral Data Protection RegulationEuropean regulation governing the processing of personal data, including operator activity-tracking data.See in the glossary → 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.

MRO and aerospace production, automotive and transport, electronics, cosmetics and pharma, textiles and luxury, and more broadly manufacturing industries with complex flows. ROBIN reasons at the level of the constraint (machine, operator, tooling), not of a fixed flow type: whatever your production mode, the challenge is to keep up with a shop-floor reality that changes all the time.

Yes. Every operation, every container movement, and every rescheduling action is time-stamped and retained. The history is searchable and exportable, making it possible to reconstruct a batch without manual investigation. ROBIN complements your quality system — it does not replace it.

Yes. Every operation, every part movement and every rescheduling decision is timestamped and traced — the “black box” of the shop floor. The full history remains auditable.

Yes. Deployment starts on a limited scope — one workshop, one flow, one critical resource — and then expands. The complexity of a job shop lies in the variety of routings, not the number of machines.

ROBIN maintains a timestamped log of every operation, every part movement, and every rescheduling event, which can be consulted and exported. This log feeds your audit records; it complements your quality system without replacing it.

No. Non-conformances remain in your quality tools. ROBIN links the rework back to the flow, reschedules it as an operation, and measures its impact on customer milestones.

The history log is timestamped, viewable, and exportable. It documents the actual path and waiting times. It complements your quality file; it does not replace the regulatory records held in your business tools.

Reduction in TAT, improvement in service level and productivity, reduction in WIP, load levelling and real-time visibility on progress. We build the value framework with you, based on our previous clients.

ROBIN simulates the future load on your critical resources before you commit to the ramp-up rate. You can see where the bottleneck will shift, which lever addresses it — hours, subcontracting, investment — and which delivery date each scenario can sustain.

Around 7% reduction observed on jobs managed with ROBIN — on a 10-day TAT, 17 hours saved per job. Not by working faster: by eliminating idle time and organisational errors that no one sees without an end-to-end view.

The pilot covers a defined scope, with a quantified baseline and a control group where possible. The built-in metrics track the variance over time, operation by operation. The reasoning holds up under management accounting scrutiny.

Against your critical KPIs: TAT, OTD, service level, WIP, productivity. The baseline is established at diagnosis, and the metrics embedded in ROBIN track the variance over time. You can also speak directly with our existing clients.

The subscription is annual, calculated per site and according to the modules activated (scheduling, simulation, operations management, geolocation…), with no per-user cost. We start from a pricing grid that is as standard as possible, provide an indicative quote within 5 days, then a business case costed on your data before any commitment.

Three steps, in this order. Measure: track WIP and geolocate its position, automatically timestamping every zone change. Alert: define dwell-time thresholds per stage, in working hours, and alert before they are exceeded. Prioritise: implement a shared priority system and make priority visible on the item — shop floor screen or connected electronic label.

Because flows are not linear: a wide variety of routings, multiple passes on the same resources, and cascading queues. A delay at one workstation propagates in a non-intuitive way. Without real-time visibility into the position and dwell time of WIP, delays are only detected at delivery.

By attacking queues rather than working time. Three levers, in this order: measure the number of days spent in each status and the actual position of WIP; only schedule workable work to avoid clogging the queues; automatically re-sequence at every disruption using a priority score.

Because the condition of the equipment is unknown on intake. Operation time cannot be read from a routing: it is discovered at the technician's assessment. On top of that come waits for parts, supplier warranty and test benches: the initial schedule changes considerably, and without the right tool each reorganisation costs lead time, which adds up to days of TAT. Static scheduling cannot cope with this variability: it takes dynamic scheduling, able to recalculate continuously.

France and Europe account for the majority of our installed base, with deployments in North America. The industries covered are detailed on the sector pages of the site.

Yes, within the scope of published use cases — lead time (TAT), service level, WIP visibility. Each result is tied to a specific scope: use it with its context, not in isolation.

Not systematically. Shareable information — funding rounds, headcount, growth — is communicated on a case-by-case basis by the communications team.

Zozio with a single capital Z, ROBIN in capitals. The registered company name is ZOZIO SAS. Usage guidelines, clear space rules, and vector files are available in the press kit.

Those published on this site and in the press kit, which are the only ones approved for distribution. For a more recent or more precise figure, please ask: we will confirm or correct it before publication.

Zozio is the company, ROBIN is the product. In an article, write “ROBIN, the Zozio platform”. The modules are named ROBIN.Deploy, ROBIN.DataFlow, ROBIN.Tracking, ROBIN.Cockpit and ROBIN.Scheduling.

Only those already cited publicly, notably in our testimonial videos and press coverage. Any other mention must be validated by the relevant client before publication.

Bastien Triclot, co-founder and CEO, on vision and market. Depending on the topic, a scheduling engineer or a deployment manager may contribute on the technical and field side.

The communications team, via the press kit request form above. Please include your media outlet, your topic, and your copy deadline.

We never ask for editorial approval rights. We do, however, offer a factual check of figures and technical terms, should you wish.

Cropping is permitted; distorting or recolouring the logo is not. Product screenshots must not be retouched: they display real shop-floor data.

In the press kit: vector logos on light and dark backgrounds, high-resolution screenshots of scheduling, the Cockpit, and real-time tracking, and royalty-free executive portraits for press use.

Finite capacity scheduling, aeronautical MRO, shop floor data and WIP tracking, the gap between ERP and production reality, moving off Excel planning.

Yes, in French and in English, whether by video call or in person. All talking points are available in both languages.

Requests receive a response within 24 hours and a slot is offered within the week. For a tight deadline, mention it in your message: we will work to your schedule.

Zozio publishes ROBIN, a real-time scheduling and shop floor management platform for manufacturers with complex workflows — aerospace MRO and make-to-order production first and foremost.