upcoming
Predictable MRO Delivery with an Aligned Scheduling and Execution Model
October 14, 2026 - 5:00 PM CEST
English
%201.png)
.png)
Most MRO organizations don't lose TAT to one big failure. They lose it a day at a time: a repair return that slips, a kit that comes up short at the gate, a priority that changes after the plan was built.
The warning signal almost always sits somewhere in an existing system, in a supplier portal, in someone's inbox. It just doesn't reach the person making the decision while the decision can still make a difference.
Here’s what to expect
Pelico and iBase-t are hosting a 30-minute session ahead of MRO Europe on what changes when the plan and the shop floor stop working from different versions of the same repair.
iBase-t's Solumina holds execution truth: work orders, routings, nonconformances, gate actuals. Pelico maps dependencies and coordinates the decisions that data should trigger: what to re-sequence, what to expedite, what to trade off.
Two panelists and a moderator: 25 minutes of discussion + live Q&A.
Chelsea Morgan
VP of Customer Success @ iBase-t
Chelsea brings 20+ years of software engineering and management experience with Six Sigma Black Belt and Lean Kaizen credentials from GE Aerospace. As VP of Customer Success at iBase-t, she provides strategic guidance to help clients successfully implement, support, and maximize the value of Solumina.
Marc Rivière
Head of Industry Aerospace & Defense @ Pelico
Marc is a senior advisor with over 30 years of leadership in Aerospace, Defense and MRO. A former French Air Force officer, serving as Program Director and holding various leadership positions as Head of MRO, followed by leadership roles in Aerospace Consulting and digital transformation.
Who should attend?
VPs and Directors of MRO Operations and Production
Heads of Supply Chain, Planning, Materials and Program Management
IT and OT leaders responsible for MES and MRO execution platforms and their integrations
Agenda
Why the weekly plan decays. Three patterns every MRO shop recognizes: start-stop execution across parallel jobs, external repair loops that go opaque, and shortages discovered at the workstation instead of ahead of the gate.
What each system is actually for. The ERP holds the commitment: what was promised, what it costs, what gets billed. The MES tracks reality: what happened at the station, in what sequence, with what findings. Orchestration drives the next decision: what to do now that the two no longer agree, in the 0 to 90 day window where that decision still matters. Most MRO shops have the first two and resolve the third in a meeting.
What the connection actually requires. What the MES should publish upward, what has to come back, and why this is weeks of integration rather than a data warehouse program.
One repair, run twice. A gearbox return drifts four days. We walk it as it happens today, then again with Solumina and Pelico connected: same four days, different outcome.
How to know which recovery option to choose. Alternate part, rotable, standard exchange, transfer, repair or replace. Each simulated for impact before anything is committed.