Menu
MES Selection Guide: 12 Questions for Smarter Production and Maintenance

MES Selection Guide: 12 Questions for Smarter Production and Maintenance

MES selection checklist for plant managers comparing production monitoring tools to platforms that execute maintenance, using Fabrico MES and OEE with.
MES Selection Guide: 12 Questions for Smarter Production and Maintenance

Most MES and OEE tools look similar in demos. They show utilization, scrap and a neat OEE dashboard. The real difference appears when something goes wrong on the line: a jam, a chronic microstop, a slow ramp-up after changeover, a quality drift. Some tools only tell you that you lost time. Others help you fix the problem and prevent it from coming back.

Fabrico captures production and downtime data directly from machines, calculates OEE and losses in real time, and, with built-in maintenance workflows, turns every loss into production and maintenance actions that teams can actually execute.

Request a demo

Before the 12 questions: Are you buying OEE or an MES platform?

Many teams start with OEE and production monitoring, then realize later that the root causes are maintenance or reliability issues that sit outside the OEE tool. Before diving into the checklist, clarify what you need:

  • A production monitoring solution that tracks uptime, speed and scrap and shows OEE
  • Or a platform that combines MES and OEE with maintenance execution, so you can act on the losses in one place

For a deeper comparison of these categories, see OEE vs MES: what belongs where.

Fabrico is designed as a cloud-based MES and OEE platform with a CMMS built into the same environment. Production and maintenance share one version of events: every downtime, slow cycle or defect can trigger actions for maintenance, production or both.

Question 1: How does the MES capture production and downtime data?

The way your MES collects data will define the reliability of every OEE number and loss report you see. Ask:

  • Can it read signals directly from PLCs and machines, or do operators type in most events?
  • How are microstops, short idles and speed losses captured and categorized?
  • What happens when connectivity is down? Does it buffer locally and sync later?

Fabrico connects to machines, captures cycle counts, states and alarms, and combines them with minimal operator input for reasons and context. The goal is to reduce manual typing while keeping the human context that pure machine data cannot provide.

Question 2: Does it calculate OEE in real time and expose the real losses?

OEE that updates at the end of a shift is a report, not a control. For day-to-day decision making you need:

  • Real-time OEE and its components: Availability, Performance and Quality
  • Clear separation of planned and unplanned downtime
  • Visibility of loss buckets like changeovers, minor stops, speed loss and rework

Fabrico continuously calculates OEE and loss categories while the line is running. Teams immediately see if a change or intervention is improving or worsening the situation, rather than waiting for next-day reports.

Question 3: Can every loss become an action for production and maintenance?

This is the first big divider between a monitoring tool and a platform that also executes maintenance. Ask the vendor:

  • When a recurring loss is identified, what can we do with it inside the MES?
  • Can we create and track actions for operators, supervisors and maintenance, all tied to the original event?
  • Can we see whether those actions reduced the specific loss category over time?

In Fabrico, every loss can generate tasks or maintenance requests without leaving the platform. A repeated microstop can trigger a standard work update for operators, a lubrication task for maintenance and a follow-up review, all connected to the specific machine and loss pattern.

Request a demo

Question 4: How deeply is maintenance management built into the platform?

Many MES and OEE tools add simple ticketing or basic work requests. That is not the same as having maintenance management as a core part of the platform. Explore:

  • Can we manage preventive, predictive and corrective maintenance in the same environment as production data?
  • Are work orders, parts, checklists and schedules part of the platform, or bolted on as an integration?
  • Do maintenance teams see live machine states and histories when planning interventions?

Fabrico includes full maintenance management workflows inside the same MES and OEE environment. Work orders, task lists and asset histories sit directly on top of machine data, so planners and technicians act with full context.

If you are refining your maintenance requirements, this checklist may help: CMMS requirements checklist for manufacturing.

Question 5: Are maintenance and production looking at the same truth?

One of the main frustrations in plants is that production and maintenance work from different tools and different numbers. To avoid this:

  • Check if downtime codes, events and comments are shared between operations and maintenance
  • Ask if a technician can see OEE history and loss trends directly for each asset
  • Verify that maintenance actions appear in production views, so teams understand why a machine is down and for how long

In Fabrico there is a single event stream. An unplanned stop is logged once, enriched with cause and commentary, and then used by both operations and maintenance. When a technician finishes a corrective job, that action is visible in the production timeline and analytics.

Question 6: How are root cause analysis and continuous improvement supported?

A good MES should support structured problem solving, not just data browsing. Consider:

  • Does the platform help identify the top losses by equipment, shift, product, crew or reason code?
  • Can you group events into incidents for deeper analysis?
  • Are there tools or workflows to run RCAs and track the resulting actions over time?

Fabrico highlights chronic losses and recurring patterns so teams can focus on the few issues that matter. Improvement actions can be created, assigned and followed through, always linked back to the data that justified them in the first place.

Request a demo

Question 7: Can the MES schedule and protect capacity around maintenance?

Maintenance is often treated as an interruption instead of a contributor to throughput. When evaluating MES solutions, ask:

  • Can we see production schedules and maintenance plans together, so we balance OEE and asset health?
  • Can we block or reserve time for essential work directly in the production schedule?
  • Does the platform help avoid last-minute surprises by surfacing upcoming work that will impact capacity?

With Fabrico, production and maintenance planning share one schedule view. Maintenance can schedule preventive work in low-demand windows, and planners can immediately see the impact on available time and OEE projections.

Question 8: How configurable are reason codes, workflows and user roles?

Plants differ by process, culture and maturity. You need flexibility without chaos. Validate:

  • Are downtime and scrap reason trees configurable, including per-line or per-site variants?
  • Can you define workflows for approvals, escalations and notifications that match your organization?
  • Are roles and permissions granular enough for operators, supervisors, engineers and technicians?

Fabrico provides configurable reason structures, workflows and roles while still maintaining standardization across sites. Corporate teams can define core templates, and plants can refine them within defined boundaries.

Question 9: Does the platform support operators, not just managers?

Adoption in the plant stands or falls with the operators. If the system interrupts their work or feels like extra admin, it will quickly degrade. Ask vendors:

  • How many clicks does it take for an operator to log a stop reason or call maintenance?
  • Can operators see the impact of their actions on today’s targets, OEE and losses?
  • Is the interface clear on touch screens, with simple workflows for start, stop, scrap and checks?

Fabrico is designed for operators first: quick reason selection, one-tap maintenance calls, and simple views of performance versus target. When operators can see their impact in real time, data quality and engagement improve.

Request a demo

Question 10: How easy is it to implement and scale across lines and plants?

An MES that works well on one pilot line but cannot scale is a risky investment. Evaluate:

  • What is the deployment model: purely cloud, hybrid or on-premise components?
  • How are new lines, machines and users added? Is it configuration or custom project work?
  • Are templates available for different equipment types and processes to speed up rollouts?

Fabrico is cloud based and template driven. Once you configure a line, you can replicate structures across similar assets and sites and adjust only where needed, which helps achieve consistent practices without heavy local projects.

Question 11: What analytics and integrations are available for your ecosystem?

MES does not live alone. It should feed and be fed by ERP, planning, quality and corporate BI. Make sure:

  • Standard APIs are available for common integrations, such as ERP, data lakes and reporting tools
  • You can export event-level data, not only aggregated reports
  • Dashboards can be adapted to different audiences, from operators to executive leadership

Fabrico offers open interfaces so production and maintenance data can flow into your existing analytics stack. Event level histories enable deeper reliability and process analysis, not just high level KPIs.

Question 12: How will the vendor support continuous improvement over time?

MES and OEE projects are not one-off installs. They evolve as your plants and processes change. Clarify:

  • What onboarding and training are offered for both operations and maintenance teams?
  • How are new features delivered and communicated?
  • Does the vendor work with you to refine loss structures, workflows and maintenance strategies based on real-world use?

Fabrico works with manufacturers to refine configurations as they learn from their own data. Plants typically start with core OEE and downtime capture, then bring more maintenance processes and continuous improvement practices into the platform as adoption grows.

Request a demo

Putting it together: a practical MES selection checklist

When you compare vendors, use these 12 questions as a simple scoring sheet:

  1. Data capture: Direct from machines, with context and resilience
  2. Real-time OEE: Clear loss breakdown in real time
  3. Actionability: Every loss can become a tracked action
  4. Maintenance depth: Maintenance management built into the platform, not just tickets
  5. Shared truth: Common data and history for production and maintenance
  6. RCA support: Tools and workflows for problem solving and improvement
  7. Capacity and maintenance planning: Unified view of schedules and impact
  8. Configurability: Reason codes, workflows and roles tailored to your plants
  9. Operator usability: Fast, simple, plant ready interfaces
  10. Scalability: Templates and cloud capabilities across lines and sites
  11. Analytics and integrations: Open data and flexible dashboards
  12. Ongoing support: Partnership for continuous improvement, not just installation

Fabrico has been designed around these principles as a cloud-based MES and OEE platform with maintenance management built in. It captures production and downtime directly from machines, shows OEE and losses in real time, and turns those losses into coordinated actions for production and maintenance teams.

If you would like to explore how this approach could fit your plants, you can Request a demo or Contact us.

Related articles

Latest from our blog

Încă te întrebi?
Verificați singuri!
Încă te întrebi?

Programați o întâlnire individuală cu experții noștri sau înscrieți-vă direct în planul nostru gratuit.
Nu este nevoie de card de credit!

By clicking the Accept button, you are giving your consent to the use of cookies when accessing this website and utilizing our services. To learn more about how cookies are used and managed, please refer to our Privacy Policy și Cookies Declaration