Measure what matters, with KPIs you define. Prove the results.
MACH Reporting & Analytics is where you define your factory, build KPIs, dashboards, reports, and CI projects, and ask Virgil about any of it. Write KPI formulas that fit your operation. Every dashboard, report, alert, and CI project reads them from the same history of what happened on the floor and the schedule, so the numbers can't disagree. MACH gives you a starting set to begin from. Reporting & Analytics, including Virgil, comes with every MACH product.
Your KPIs
Write your own formulas for OEE, scrap, or tons per hour. Change one once and it changes everywhere it appears.
02 · LookDashboards
Charts, KPI cards, and tables for each plant or machine type, with Virgil beside them for the follow-up question.
03 · DeliveredReports & Alerts
The Monday report arrives as a document or an email, and a long stop sends its own alert.
See Reports & Alerts → 04 · ProveCI Projects
Lock a baseline, measure whether the change is meaningful and what it’s worth, and keep watching after the project closes.
See CI Projects →Last updated: October 13, 2026
Can we define our own KPIs? Write the formula once, and it updates everywhere it appears.
The KPI builder lets you define any metric with a flexible formula language, set targets and thresholds, and use it in every dashboard and report. The same formula shows up on a wall display, a kiosk, and the monthly review. MACH ships with sensible defaults, and you can change any of them.
Here's what you're seeing: a KPI built and charted in under a minute. Pick your inputs, write a formula, set a target and color thresholds, and drop it onto a dashboard, whether it's OEE, scrap rate, throughput per hour, or yield by material grade.
- Build KPI formulas from run time, downtime, changeovers, production counts, and order details, with no code.
- Built-in functions handle the math, so you don't have to, whether it's a percentage, a rate per hour, or a gap to target.
- Set a target and a direction (higher is better for OEE, lower is better for scrap), then define color thresholds so dashboards show green, yellow, or red at a glance.
- Choose the context of the KPI, whether it is grounded in shift or order information, and override the target per machine while keeping one formula.
Build your own dashboards. Then ask them questions.
The dashboard builder turns your KPIs and data queries into charts, gauges, KPI cards, and tables on a grid you arrange, organized in folders and reusable as templates. Filter by plant, machine type, shift, and date, and group by month, quarter, or year. Virgil sits beside every dashboard for the follow-up question, and when an answer deserves a chart, it proposes one for you to add.
Here's what you're seeing: drop widgets onto a grid and point each one at a KPI or a data query. Scope a dashboard to the plant level to view KPIs common to all equipment and schedule attainment, or scope to a machine or station type to drill into the details of that asset type. Build a dashboard and clone it, or copy individual widgets to another.
- Ask Virgil about anything on the dashboard. It answers from the same data and shows the query behind every number.
- Organize dashboards in folders by role, machine type, facility, or function, with a navigation tree for the sidebar.
- Dashboards scope to a plant or machine type, so one layout serves many contexts. You control which filter dimensions are available to users.
- Data tables are sortable, filterable, and export to CSV in a click. The data underlying any chart can be exported the same way.
Custom reports that send themselves. Before the Monday meeting starts.
Build a custom report from the same KPI, chart, and table widgets your dashboards use, and MACH sends it on a schedule as a document or an email, one version per plant if you want. Virgil can write the summary paragraph. Alert rules on stops, changeovers, and late orders send their own message the moment they trip.
Report builder
Rows of KPIs, charts, tables, text, and Virgil blocks, with sections that repeat for every plant. The numbers match the dashboard because they come from the same engine.
Scheduled delivery
Send it every Monday at 5am plant time, or whenever an alert rule fires. Pick recipients by person, role, or group, and each one gets only their plants.
Alerts
Get a message when a stop runs long, a stop goes unclassified, a changeover runs over, or an order falls behind, plus many more conditions you can set up.
Continuous improvement that proves itself. With the data you already have.
Most CI projects start with a spreadsheet and end with a debate about whether the numbers are real. A CI project in MACH locks its baseline from machine data the day tracking starts, then measures every period after against it using the same data that drives your dashboards, so everyone in the review is looking at the same auditable numbers.
Before/after verdicts
The change for every goal, and a plain verdict on whether it’s meaningful. Comparison machines take plant-wide drift out of the result.
Sustain tracking
After the project closes, MACH keeps checking and marks each gain holding, slipping, or regressed.
Savings in dollars
Improvements turn into dollars using your own cost assumptions, with the formula and inputs shown. Only meaningful changes count as confirmed savings.
CI projects reuse your existing KPI definitions and catalog, so if your dashboards already track OEE, changeover time, and scrap rate, your projects can target them from day one. When Virgil spots a loss that keeps coming back, it offers to start a project for it. See CI Projects →
Monitor and Schedule data in one view. Merged in real time.
MACH Monitor, Schedule, and Reporting are one system. Data from the floor and the schedule is merged in real time into a single, current history, so everyone works from the same record and nothing has to be pulled or reconciled by hand.
Here's what you're seeing: every job, shift, stop, and schedule result on every machine lands in one place as it happens. That history is what your KPIs compute against and your dashboards draw from.
- See run time, downtime, production counts, rejects, and the order details for every job that ran on every machine.
- Roll it up by shift or by day to see where the time went, what was produced, and who was running.
- Every classified downtime event is stored with its category, reason, and duration, and every scheduled order carries its planned-versus-actual performance.
- History goes back to day one with no retention limit. Filter by plant, machine, shift, operator, or date range.
Define your plants and machines once. Everything else follows.
The factory catalog is where you define your plants, machines, machine types, order schemas, materials, and process routes. Set them up once in Hub and every change reaches Monitor and Schedule automatically.
Here's what you're seeing: how the catalog feeds the rest of the system. Define anything once in Hub and every app that needs it picks it up, with nothing to re-enter or keep in sync.
- Define plants, work centers, machine types, machines, and manual stations in one catalog.
- Machine-type profiles standardize a class of equipment: production units, data points, KPI definitions and performance goals, downtime and reject reason codes, step parameters, and capability specs.
- Capability specs (max width, max thickness, supported materials) flow to Schedule and drive capability-based machine assignment. Browse specs across your machines to see what your equipment can handle.
- Order schemas define the custom fields that travel with an order. A CNC job may carry a CAD file and QC instructions, while a sawing order carries cut length and bundle size. Fields auto-populate from the selected material, and calculated fields fill themselves in, so order entry is fast and consistent. Orders can also be imported directly from your ERP.
- Process routes define the sequence of operations to produce a product. Each route links machine types into multi-step recipes with step parameters, dependencies, and workcenter assignments.
- Material types and specific materials define what you run. Properties like grade, gauge, and density carry through to order fields and KPI calculations. A shared units-of-measure registry with conversions keeps everything consistent across the catalog.
One bad shift doesn't ruin the month. Correct it, and keep the original on record.
Corrections, data invalidation, and period tagging keep your analytical record accurate and in context, and every change is logged.
- Correct production records after the fact. An operator forgot to log off and downtime accumulated overnight? Fix it with a mandatory reason, and the original values are preserved alongside the correction.
- Every edit is logged with who changed what, when, the old and new values, and the reason, in a queryable audit trail.
- Leave a bad record out of the numbers without deleting it, and put it back any time.
- Mark date ranges with context like trial runs, bad material, or equipment testing, so reports reflect what was normal and what wasn't.
- Global downtime and reject reason libraries keep classification consistent, with per-machine-type additions and overrides.
Your data, in the tools you already use. Through a read-only API.
A read-only API exposes the same analytical data your dashboards show. Connect it to your favorite BI tool, data warehouse, or data lake, so MACH data lives alongside the rest of your business.
Here's what you're seeing: the same history that powers your dashboards, available read-only. Pull machine and shift performance, job detail, downtime with reasons, or schedule results into a spreadsheet, a BI tool, or another system.
- Machine and shift performance: run time, downtime, and output for every machine, by day and by shift.
- Downtime: every stop with its duration and reason.
- Schedule performance: what was planned against what actually ran.
- AI assistants: Claude, ChatGPT, or your own agent can call Virgil’s read-only tools over MCP once your admin approves the app, and each person signs in as themselves.
True cost-to-serve. The real number behind every quote.
Your quoting model uses standard costs, and standard costs don't see the actual changeover time between jobs, the scheduling disruption from a late material delivery, or the overtime your floor absorbed when a run took twice as long as the estimate. MACH captures all of that today. When cost-to-serve analytics ship, every order, product, and customer will carry a real production cost. Some manufacturers who run this analysis find their fastest-growing product is their least profitable.
Product-level cost-to-serve
Actual production cost per unit, per product, per customer.
Customer profitability
Which accounts generate margin and which erode it.
Quoting accuracy
Quotes built from real production data, not standard cost assumptions.
Cost-to-serve analytics reads the data Monitor and Schedule capture today, so when it ships, there's nothing new to implement.
We wrote about what this looks like on a real floor: What the job actually cost.
Questions about MACH Reporting & Analytics.
Can we define our own KPIs?
Yes. You define any KPI with your own formula, built from run time, downtime, changeovers, production counts, and order details, set targets and color thresholds, and use it across dashboards and reports. MACH provides suggested KPIs as a starting point, and you can change them or build your own from scratch.
What is MACH Reporting & Analytics?
It's where you define your factory and measure it. Reporting & Analytics holds your plants, machines, materials, and processes, and merges data from MACH Monitor and Schedule in real time into one history. On top of that history you build custom KPIs, dashboards, scheduled reports, alerts, and CI projects, and ask Virgil questions about any of it.
Can we use our own BI tools and data warehouse?
Yes. A read-only API exposes the same analytical data your dashboards use, so you can pull machine-day metrics, shift data, downtime, and schedule performance into your favorite BI tool, data warehouse, or data lake. And because production data flows into MACH automatically from Monitor and Schedule, there is nothing to pipeline first.
Does changing a KPI require coding?
No. KPIs are defined in a visual editor with a formula language, not application code. You write or edit a formula, set its targets and color thresholds, and it takes effect everywhere it's used, across dashboards, reports, and the floor and schedule displays, without a developer or a software release.
Can MACH extend its APIs beyond the standard endpoints?
Yes. If you need data the API doesn't already cover, the MACH team will extend it for you. Reach out and we'll scope what you need.
Is Reporting & Analytics priced separately?
No. Reporting & Analytics, including Virgil, comes with every MACH product: Monitor, Schedule, or Complete.
How are dashboards, reports, alerts, and Virgil different?
Dashboards are the views you open and look at. Reports are built from the same widgets and sent on a schedule as a document or an email. Alerts send a message on their own when a rule trips, like a long stop or a late order. Virgil answers questions beside every dashboard and can also run on a schedule. All four read the same KPIs and the same history, so the numbers match.
Does Reporting & Analytics include AI?
Yes. Virgil, MACH’s read-only AI assistant, comes with every MACH product. It sits beside every dashboard to answer follow-up questions from your own data, can write the summary in a scheduled report, and never changes anything.
Can I connect my own AI model?
Yes. Claude, ChatGPT, or your own agent can call Virgil’s read-only tools over MCP (Model Context Protocol) once your admin approves the app, and each person signs in as themselves.
All of this. Included with every MACH product.
Reporting and analytics comes with MACH Monitor, MACH Schedule, and MACH Complete, built on the data they already capture. It is not priced separately. See the pricing page for product pricing.