Machine monitoring for aerospace machining
Aerospace manufacturing software for the shop floor: stops, setups and waits
Fabrico is cloud OEE and light MES software. In an aerospace machine shop it records when each machining center, lathe or grinder runs and stops, from the PLC or a sensor, and the machinist adds the cause.
- Stops on record during a long program
- Setups, FAI waits and breakdowns apart
- Older CNC: IoT sensor or manual mode
One line's OEE. Real Fabrico screen, sample data.Trusted by manufacturing groups
A four-hour program, and the stop nobody saw
A five-axis machining center starts a titanium bracket at 01:30. The program runs 4 hours 40 minutes. At 02:15 it stops on a tool alarm. The night machinist, minding three other machines, reaches it at 03:05.
On a whiteboard, that shift shows one part short and no reason. In Fabrico, the stop is on the line's timeline from the signal, with its start and length. The machinist picks the cause on a tablet, and the morning meeting sees the 50 minutes and why.

Who looks at it, and when in the shift
- Machinist, at the machine: picks the cause of a stop on a tablet or phone.
- Shift lead, during the shift: sees which machines are down, and can get a line-down notification.
- Production or operations manager, at the daily meeting: reads OEE by machine, line and shift, and the top stop causes.
- Maintenance, when a breakdown is logged: opens a task from the stop, with the machine and reason filled in.
- Quality manager, weekly: sees the machine hours spent waiting for inspection.
Where machine time hides in an aerospace shop
| Shop area | What goes unseen | How it shows in Fabrico |
|---|---|---|
| Five-axis and multi-axis machining | Mid-cycle stops inside long programs; setups and probing mixed into run time | Stops from the PLC or a sensor; setups logged as changeovers with an expected duration |
| Older CNC and manual lathes | No usable machine output, so no record at all | A Fabrico IoT sensor, or manual mode where the machinist starts and stops production |
| Composite trim and finishing benches | Work with no counting signal | Manual mode: the operator starts and stops production and enters the parts made |
| Autoclaves and cure ovens | Long cure cycles with stops and waits between loads | Run and stop time from the PLC or a sensor, like any other machine; waiting causes from your list |
| Assembly cells | Waiting for parts, tooling or a buyoff | Waiting causes picked from your own reason list |
| MRO component shops | Machines running one-off repair jobs between waits | The same stop and cause records on those machines |
Four plant situations it makes visible
1. Waiting for first article inspection
The first part off a new program goes to the CMM for first article inspection, and the machine waits. Logged as "Waiting: first article inspection", that time shows per machine and per week.
Setup: fixture change
Waiting: first article inspection
Breakdown: spindle
2. Setups in high-mix, low-volume work
Each new part number means fixtures, tools and offsets. Changeovers are logged from one product to the next, with an expected duration per variant. A negative time remaining means the setup is running late.
3. Short stops to clear chips or check a tool
You set a micro-stop threshold of up to 10 minutes. Shorter stops are not logged as downtime, but they still count as delay, so many small pauses still show in Performance.
4. Breakdowns that keep coming back
A spindle fault logged as a stop can become a maintenance task with the machine and reason filled in. Spindle checks sit in the annual preventive maintenance plan, and MTTR and MTBF show which machines keep failing.
From stop to cause, step by step
- Each machine is connected: its PLC where it has usable output, a Fabrico IoT sensor where it does not, or manual mode where neither works. See machine connectivity.
- You set the basics: planned time, an ideal count per product and line, and your stop reasons, waiting causes included.
- The signal records run and stop time on each machine's timeline.
- The machinist picks the cause in two steps: the machine, then the reason, plus a comment if needed.
- OEE, downtime by cause and changeover time update by machine, line and shift.
- A breakdown can become a maintenance task.

What Fabrico needs, and what stays with your quality system
| It needs | Stays with your other systems |
|---|---|
| A PLC signal, a Fabrico IoT sensor or manual entry for each machine | Inspection and first article inspection stay with your quality team; Fabrico records the time a machine waits for them |
| Products with an ideal count per line | AS9102 forms and quality records stay in your quality system |
| A stop reason list your machinists will actually use | Your quality management system and traceability records keep their role |
| Planned time for each machine | Fabrico supplies the measured run rate and stop history per line; the plan itself is made in your ERP, APS or planning spreadsheet |
| Tablets or phones at the machines, or a browser | Your ERP and MRO system keep their role; Fabrico records what each machine did |
AS9100D, published by SAE International, includes the ISO 9001:2015 requirements and adds aviation, space and defense requirements on top. AS9102C, revised in June 2023, sets the requirements for performing and documenting FAI.
The FAA sets record periods too. A production approval holder keeps its quality records for at least 5 years, and at least 10 years for critical components (14 CFR 21.137). A certificated repair station keeps its records for at least 2 years from the date the article was approved for return to service (14 CFR 145.219).
Fabrico shows the machine time around those records.
Where it sits in OEE and light MES
The stop records on this page are the base of Fabrico's OEE and MES software and its downtime tracking. The maintenance module is built into the same platform, so a stop and its repair are in one place. A group account shows several plants in one view.
It sits between your ERP and the shop floor: Fabrico records what each machine did, and a connection to SAP or another ERP can be scoped per customer.
For the wider topic, read OEE for aerospace manufacturing, OEE software for AS9100 and CNC machine monitoring.
Machine time records: paper or spreadsheet vs Fabrico
| Whiteboard or spreadsheet | Fabrico | |
|---|---|---|
| When a stop is recorded | End of shift, from memory | When the signal drops |
| Cause | Often blank or "other" | Picked at the machine from your list |
| Waiting for first article inspection | Hidden in run time or downtime | Its own cause, per machine |
Questions aerospace buyers ask
Does Fabrico do first article inspection or AS9102 reports?
Quality inspection, first article inspection and AS9102 reports stay in your quality system. Fabrico records the time a machine waits for first article inspection as a stop cause, so you see that wait in machine hours.
Will Fabrico make us AS9100 compliant?
AS9100 compliance comes from your quality management system and your certification audit. Fabrico is OEE and light MES software, and Fabrico as a company is certified by DNV to ISO 9001, ISO/IEC 27001 and ISO/IEC 20000-1.
Does a stop in the middle of a long program get recorded?
Yes, on a connected machine. The stop comes from the PLC or sensor signal, so it is on record when it happens, with its start and length, not at the end of the part. The machinist adds the cause.
What about older CNC machines with no usable output?
A Fabrico IoT sensor can be fitted. Manual mode covers machines with no sensor at all: the machinist starts and stops production and enters the parts made.
Is Fabrico a full MES?
Fabrico is light MES: it covers the monitoring and OEE side of MES, with machine data, downtime, OEE and the maintenance work that follows. For planning, Fabrico supplies the measured run rate and stop history per line; the plan itself is made in your ERP, APS or planning spreadsheet.
How long does a rollout take?
With hardware, installing and connecting the devices takes about 1 month, and the full rollout takes 3 to 4 months.
Do machinists need a PC at the machine?
No. The iOS and Android apps run on a tablet or phone, and the web app in a browser.
Where is Fabrico hosted for EU customers?
EU customers are hosted on AWS in Frankfurt.
Book a demo to see how stops, causes, setups and OEE by shift are recorded on a line, and how a breakdown becomes a maintenance task.