Menu
Book a demo
Light MES · Manufacturing performance platform

Chemical manufacturing software

Chemical manufacturing software for batch reactors and filling lines

Fabrico records when a reactor train, continuous unit or filling line runs and stops, from a machine signal, and the operator adds the cause. Cleaning, waits and slow running land in OEE by line and shift.

  • Machine signal or Fabrico IoT sensor
  • Process control stays in your DCS
  • ISO/IEC 27001
One line's OEE. Real Fabrico screen, sample data.One line's OEE. Real Fabrico screen, sample data.

Trusted by manufacturing groups

ABBSchaefflerHitachi Energykdc/oneLufthansa TechnikAkzoNobelFicosota
Fabrico · Light MES

Two hours lost between batches, and a batch record that says nothing

A resin plant runs a 6,000 litre reactor on the night shift. At 22:10 the next batch cannot be charged: a drum of additive is still in the warehouse, 40 minutes. At 03:30 the reactor is empty and clean, but the only operator is at the filler, so the next charge waits 35 minutes. The clean before the next product runs 50 minutes over.

The batch is on spec, and its record says nothing about those two hours. In Fabrico's OEE and light MES software, the reactor train is a line with the reactor as its core machine. When the reactor's signal shows it idle, the line is down, and the operator picks the cause on a tablet: "Waiting: raw material", "Waiting: operator". The clean runs as a changeover against its expected duration, so the overrun is on record too.

The stops on a line. Real Fabrico screen, sample data.The stops on a line. Real Fabrico screen, sample data.

One batch, five phases: where the cycle loses time

A batch reactor rarely breaks down. It loses time in the phases around the reaction. Fabrico records run and stop time from the reactor's signal and the cause the operator picks; the phase sequence itself stays with your DCS or batch control. One cycle, as an example:

PhaseWhere the time goesHow Fabrico records it
ChargeRaw material not staged, no operator freeWhen the reactor sits idle, a waiting cause such as "Waiting: raw material"
ReactA trip on a temperature or pressure alarmAn unplanned stop with its cause, when the trip stops the reactor
HoldThe batch waits for the lab to release itWhen the reactor sits idle, its own cause, such as "Waiting: lab release"
TransferThe receiving tank or filler is not free; a pump or filter blocksWhen the reactor sits idle, a cause such as "Waiting: tank free" or a pump fault
CleanThe clean overruns, or a full clean is done where a flush would doA changeover to the next product, with its variant, against its expected duration

Between batches: cleaning

Planned: shutdown

Breakdown: pump seal

Example causes, not a screen capture

From reactor to drum filler: what it records in each area

Continuous units: slow running and grade changes

A continuous unit rarely stops outright. After a disturbance it runs below its rated rate. Where its output is counted against an ideal rate, that shows as delayed time, a loss in Performance. A grade change can be logged as a changeover, and off-spec transition material entered as waste or rework lowers Quality.

Mixing and blending: the order of products

In coatings and adhesives, light to dark may need a quick flush, dark to light a full clean. The changeover matrix holds an expected duration for a product pair or category, so a long clean is judged against the right time.

Filling and packing: short stops at the filler

Drum, IBC and pail lines lose time in short stops: a cap that will not seat, a missing pallet. You set a micro-stop threshold of up to 10 minutes. When the filler is the line's core machine, stops under it count as delay, and longer ones are logged as stops for the operator to classify. The shift lead can get a line-down notification.

What the batch record misses, and what Fabrico adds

Batch record or shift logFabrico
Reactor idle between batchesRarely written downStop time from the signal, with a cause
Off-spec or reworked materialIn the batch record, not in OEEWaste or rework, in Quality
Whether the batch was made rightThe batch record's jobStays with the batch record; Fabrico records the time around it

Who on a chemical site uses it, shift by shift

RoleWhenWhat they do
Reactor or line operatorDuring the shiftPicks stop causes, starts changeovers, enters waste or rework
Shift leadDuring the shiftWatches a TV status screen, gets line-down notifications
Plant managerDaily meetingReads OEE by line and shift and the top 10 stop reasons

Connecting a reactor train or a filling line

  1. Set up each reactor train, continuous unit and filling line as a line, with a core machine as its signal source, such as the bottleneck.
  2. Connect the core machine to its machine signal, fit a Fabrico IoT sensor where an older mixer or filler has none, or use manual mode. On request, the camera add-on counts output where a machine has no usable signal.
  3. Add your products with an ideal count per line, and set planned time per shift.
  4. Build the stop reasons and the changeover matrix, with variants and expected durations.
  5. When the line goes down, the operator adds the cause in two steps: the machine, then the reason.
  6. OEE, downtime by cause and changeover time update by line and shift.
The stop list with its causes. Real Fabrico screen, sample data.The stop list with its causes. Real Fabrico screen, sample data.

Requirements, and the jobs that stay with your DCS and ERP

It needsStays with your other systems
A machine signal, a Fabrico IoT sensor or manual entry for each lineProcess control stays with your DCS or SCADA; Fabrico reads machine data to measure OEE and downtime
Products with an ideal count per lineBatch records and recipes stay in the systems that hold them today
Planned time for each lineFabrico supplies the measured run rate and stop history per line; the batch plan itself is made in your ERP, APS or planning spreadsheet
A tablet, phone or PC with a browser at the lineYour ERP keeps its role; a connection to SAP or another ERP can be scoped per customer

Idle reactor hours are capacity a site already owns

A reactor that waits two hours between batches is capacity the site has paid for and not used. In Europe, Cefic's 2025 Facts and Figures puts the European chemical industry at a turnover of €635 billion, 1.2 million jobs and around 31,000 companies, with capacity utilisation 9.5% below its 2014 to 2019 level. In the US, chemical manufacturing employed 906.9 thousand people in October 2026, a preliminary figure (BLS, NAICS 325).

When utilisation is low, fixed costs sit on fewer batches, so the hours lost around a batch are worth knowing by cause.

Line time first, maintenance built into the same platform

A pump seal failure logged as a stop can become a maintenance task with the machine and reason filled in. OSHA's process safety standard, 29 CFR 1910.119, lists pressure vessels, relief systems and pumps among equipment to inspect and test. Checks your own procedures define, such as relief valve tests, can sit in the annual preventive maintenance plan.

Chemical plant questions, answered

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.

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.

Does Fabrico control the process or replace our SCADA?

Process control stays with your DCS or SCADA. Fabrico reads machine data to measure OEE and downtime.

Can we track a unit that has no usable signal?

Yes. Fit a Fabrico IoT sensor, or run the line in manual mode: the operator starts and stops production, registers stops and enters the items produced, with quick buttons for the 5 most-used stop reasons of the last 7 days.

Is Fabrico an EHS or quality system?

EHS and quality inspection stay in your EHS and quality systems. Fabrico is OEE and light MES software: it connects to machine signals and Fabrico IoT sensors, and a connection to SAP or another ERP can be scoped per customer.

How is cleaning between batches counted?

As a changeover against its expected duration, which counts as time lost in Availability. If a plant logs a clean as a planned stop instead, that reason can be kept out of Availability, and the time still shows in total downtime.

Book a demo to see a clean between two products count down against its expected duration, an idle line get its cause, and OEE split by shift.

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 and Cookies Declaration