Manufacturing analytics and reporting See where the shift lost its time, and what it cost.
Fabrico reports are built from what your lines already record: machine signals, operator stop reasons and maintenance tasks. They show OEE, stops and output against target by hour, shift, day, week or month, next to MTTR, MTBF and task costs, with every loss priced in money.
- Real-time dashboards
- Losses priced in money
- Export to Excel

Trusted by FMCG, food and industrial manufacturing groups
The Monday review, answered before the meeting
It is 07:30 on Monday. Line 2 had a bad week, and the plant manager has ten minutes before the production meeting. She opens OEE by line for the week: line 2 is down, and the availability bar is the one pulling it down. The downtime distribution shows how much time went to changeovers, and the top stoppages report shows a jam as the most frequent unplanned stop. Fabrico prices both losses from the selling price and gross margin of the product that was running.
She exports the table to Excel for head office and walks into the meeting with two losses to discuss, not a debate about whose numbers are right.
Ask a question, open the report
Most reporting starts with a question someone asks in a meeting. This table maps the usual questions to the Fabrico report that answers them.
| The question | The report in Fabrico, and how it splits |
|---|---|
| Why was OEE low on the night shift? | OEE with its availability, performance and quality bars (by machine, line or shift) |
| Did we hit the plan? | Production achievement, and gross production against target (by hour, shift or day) |
| Which stops hurt us most? | Top 20 stoppages: downtime, frequency, share and average duration (per line and period) |
| Where did the time go? | Downtime distribution: planned, unplanned, changeover and unclassified (per line and period) |
| What did those losses cost? | Losses priced from your selling price and gross margin (by shift, line or plant) |
| Which machines lose the most time to downtime? | Top machines by downtime (for the period you pick) |
| How fast do we repair, and how often do we fail? | MTTR and MTBF (per period and site) |
| What did the repairs cost? | Task costs: spare parts, labour and downtime (by task or machine) |
| Is preventive work keeping up? | Scheduled against completed, and the annual preventive plan (by category) |
| How does this plant compare with the others? | Group analytics (site by site) |
Who reads which report, and when
- Shift supervisor, during the shift: output against target hour by hour, to catch a drop while the shift can still recover it.
- Production manager, each morning: OEE by line and shift, and the top stoppages of the day before.
- Maintenance manager, each week: MTTR, MTBF, task costs, task distribution and preventive work done against plan.
- Plant manager or finance, each month: what losses cost, and how each site compares.
OEE by line and shift, sample dataReports Fabrico produces today
Production and OEE
OEE and its three factors, production achievement, TEEP, equipment utilisation, waste and rework, and OEE and TEEP over time. These reports split by hour, shift, day, week or month, and the dashboards show real-time data.
Stops and downtime
Top planned and unplanned reasons, the top 20 stoppages table and the time allocation of each line. For the weekly routine, see our guide to the downtime report.
Maintenance
Repair history, task costs, downtime with MTTR and MTBF, task distribution, work hours per machine and per-employee productivity. These come from the CMMS built into OEE software, in the same system.
Several sites
Group analytics compares OEE and maintenance figures across plants. See multi-site management.

Losses with a price on them
A stop measured in minutes is easy to argue about. A stop measured in money is not. The financial impact module needs two inputs per product: the selling price and the gross margin. From those, Fabrico prices each lost unit as revenue at risk and lost profit.
That is what turns a top stoppages list into a priority list. Read more on the cost of downtime per minute.
Fabrico chart, sample dataFrom machine signal to report, in five steps
- Fabrico connects to machine signals, adds IoT sensors where a machine has none, or counts output with the camera add-on, on request. Lines with no sensors run in manual mode.
- Operators give the stop reasons from the plant's own list, so stops do not stay unclassified.
- Technicians close maintenance tasks with parts and hours, which feed MTTR, MTBF and task costs.
- You enter the selling price and gross margin per product, and losses get a price.
- You open the report, pick the period and the split, and export it to Excel if someone needs a file.
Spreadsheet reporting vs Fabrico reports
| Topic | End-of-shift sheet or spreadsheet | Fabrico reports |
|---|---|---|
| Where the numbers come from | Typed in by hand after the shift | Machine signals, cameras or manual mode, plus the reasons operators give |
| When you can see them | After someone builds the file | Real-time dashboards |
| Stops nobody explained | Missing, or filed as "other" | Shown as unclassified time until someone gives a reason |
| What a loss cost | A separate calculation, if anyone does it | Priced from your selling price and gross margin |
| Maintenance figures | A second file from a second tool | MTTR, MTBF and task costs on the same machines |
For the broader buying question, read manufacturing analytics software: what to look for, or how light MES compares with Power BI for OEE reporting.
What the reports need, and their limits
| The reports need | They do not |
|---|---|
| Machine signals, a camera count or manual mode on each line | Show OEE per SKU: OEE is by machine, line and shift |
| Stop reasons from operators | Inspect quality: quality inspection is not part of Fabrico |
| An ideal count per product and line, for performance | Give each user a personal dashboard: dashboards are customised for your company |
| Selling price and gross margin per product, for money | Plan or schedule production: that is not part of Fabrico today |
| Maintenance tasks closed in Fabrico, for MTTR and MTBF | Include a custom report builder in the base: it comes with the Fabrico Copilot add-on |
The base underneath is OEE software and light MES. Signals come through machine monitoring software and stops through downtime tracking software.
Common questions about Fabrico analytics
Do the analytics dashboards show real-time data?
Yes. The dashboards show real-time data based on your search criteria.
What can I report on?
OEE, production achievement, TEEP and equipment utilisation, top stoppages and downtime distribution, and waste and rework, by hour, shift, day, week or month. Also losses in money, and maintenance figures such as MTTR, MTBF and task costs.
Can I export reports to Excel?
Yes. Fabrico analytics include an export to Excel.
Can each user build their own dashboard?
No. Dashboards are customised for your company, not per user. A custom report builder is available with the Fabrico Copilot add-on.
Does Fabrico show OEE per product?
No. Fabrico reports OEE by machine, line and shift, not per SKU.
Can reports show what a loss cost?
Yes. Fabrico prices losses from the selling price and gross margin you enter per product.
Can head office see every plant in one report?
Yes. Group analytics compares OEE and maintenance figures across plants, site by site.
Book a demo to see the reports on sample data, and how a stop turns into a cost in money.