The numbers your team needs. On a schedule, or the moment it matters.
MACH Reports & Alerts builds production reports from your dashboard charts and KPIs, sends them on a schedule, and alerts the right people when something on the floor or schedule needs them. Someone on your team spends Friday afternoon copying numbers out of three screens into last week's report file, and by Monday the first question in the meeting is whether they're right.
The numbers, before the meeting.
Custom reports from your own KPIs, with Virgil’s takeaways written in and one version for each plant.
See reports ↓ AlertsThe problem, while you can fix it.
A message the moment a stop runs long or an order falls behind, sent to the people who can act on it.
See alerts ↓Last updated: October 13, 2026
Build custom reports the way you'd sketch them. Every chart is a dashboard chart.
Build the report from the KPIs, charts, and tables you already use on your dashboards, and let Virgil write the summary at the top. One report can cover every plant, with a section for each, and the numbers always match the dashboard.
- Heading · {plant} weekly review
- OEE · Scrap · On-time
- Downtime by reason · Summary
- Schedule adherence by machine
- Section per plant
Material feed jams were the largest loss at 11.2 hours, most of it on Press 2 on Tuesday and Wednesday. Scrap rose with them.
Here's what you're seeing: a weekly review laid out on the canvas, drawn with live data as you build it. You set the period and plants once at the top, and every block follows them.
- Set the report's period once: last week, quarter to date, the previous quarter, the last twelve months, or year to date.
- Headings and text can carry the plant and the period, so "Plant 2 weekly review, Sep 28 – Oct 4" writes itself every week.
- Describe a block in plain words, like "top five downtime reasons by plant in hours," and Virgil fills in the setup for you to check before you keep it.
- KPIs and tables arrive in the document as real text and tables you can edit, and charts arrive ready to present.
Connects to: your custom KPIs and dashboard widgets.
Virgil writes the summary. The paragraph someone used to write by hand at the top of every report.
Charts show what moved. Put Virgil anywhere in the report, as a summary at the top or a note beside a chart, and it says which changes matter in a few plain sentences, so the meeting can start with the answer.
Explains what's on the page.
Place it beside a chart or at the top of a section, and it says what stood out in those numbers, like the biggest loss of the week and the machine behind it.
Answers the next question.
Ask it something you'd ask every week, like why Press 2's downtime rose, and each report arrives with the answer, worked out from that week's data.
Scheduled reports, delivered before Monday. Spend the morning fixing problems Virgil has already found.
Every Monday at 5am plant time, or on whatever schedule you set, the report lands in Hub or your team's inbox with Virgil's takeaways already written: what changed since last week and where the losses were. Your supervisors and managers start the week fixing those problems and running the floor, because Virgil did the analysis before they sat down.
The layout you made, refreshed.
The same structure every week, so readers know where to look. Only the numbers and Virgil's notes change.
Virgil writes it from scratch.
Give Virgil a standing question, like which presses slipped on scrap and OEE, and it writes the report fresh each time, with its findings first.
Build it once. Every plant manager gets their own version.
One report covers every plant, and each plant manager gets the version for their floor, so you're not building and maintaining a separate report for each site. Leadership can get a rollup across every plant instead, with Virgil calling out the few things that matter most. Reports can go out by role, like plant manager or maintenance lead, so when someone changes jobs or you add a plant, the right people still get them, with no list to update.
Already sending a report you're happy with? Upload it as a Word, Excel, PowerPoint, or PDF file. Virgil reads it, matches each figure to a MACH data source, and shows you how much of it MACH can build for you, before anyone builds anything.
Production alerts the moment something goes wrong. While there’s still time to fix it.
Set a rule for what matters on your floor, like a stop over 30 minutes or an order falling behind, and MACH sends a short message the moment it happens. Limits can follow each machine’s own normal, so you hear about what’s unusual for that machine, not every routine stop.
Press 2 has been stopped since 9:12 AM. The operator logged material feed jam. Order 41187 (bracket, 2,400 pcs) is waiting on it.
This is the third feed jam on Press 2 this week. The first two cleared in under 15 minutes, and Press 1 and Press 3 haven't had one running the same part.
On the floor.
A stop running long, a changeover going over, the same downtime reason coming back, or several machines down at once, plus many more you can set up.
On the schedule.
An order falling behind, a machine’s day slipping past plan, or a conflict on the board.
Alerts by role and plant. The right person hears about it, with Virgil’s read on what’s happening.
Alerts go out by role and plant, the same way reports do, so the supervisor at Plant 2 hears about Plant 2’s stops and leadership isn’t buried in every one. Turn on Virgil for a rule and its read on the situation comes in the same message, so whoever gets it knows where to start.
- Add a note for the people who receive it, like who to call or what to check first.
- One rule can cover several machine types, so you set it up once.
Questions about Reports & Alerts.
What format do MACH reports arrive in?
A Word document or an email. KPIs and tables arrive as real text and tables you can edit, and charts arrive ready to present.
Do the numbers in a report match the dashboards?
Yes. Every KPI, chart, and table in a report is built and calculated the same way as on your dashboards, using your KPI definitions.
Does a report need AI to run?
No. Reports run on your own data, and Virgil's notes are an option you can add.
Can each plant manager get their own plant's report?
Yes. Set the schedule to send one version per plant, and each plant's version goes to the people at that plant. Leadership can get a rollup across every plant instead.
What can MACH send alerts about?
Stops running long, changeovers going over, the same downtime reason coming back, several machines down at once, orders falling behind, a machine's day slipping past plan, conflicts on the schedule, and more. Each alert goes to the people responsible for that plant.
Do alerts depend on Virgil?
No. An alert rule sends its own message with the facts, like the machine, how long it has been stopped, and the order it's holding up. If you turn on Virgil for a rule, its read on the situation comes in the same message.
Can MACH reproduce the report we already send?
Upload it as a Word, Excel, PowerPoint, or PDF file and Virgil reads it, matches each figure to a MACH data source, and shows you how much of it MACH can build for you. You then build the report from there.
Is Reports & Alerts priced separately?
No. Reports & Alerts is part of Reporting & Analytics, which comes with every MACH product: Monitor, Schedule, or Complete. See pricing.
Bring the report you send today. We'll show you what it looks like when it builds itself.
We start with a Shop Floor Diagnostic. One-hour call to understand your situation, then a written assessment of where the losses are and what closing them would be worth. Where we can't help, we say so. Reports & Alerts comes with every MACH product.
Reports & Alerts is part of Reporting & Analytics, included with every MACH product at no additional charge. See pricing.