For batch chemical plants

A batch fails at 2am.By 2:10 you know why.By 2:20 every order it touches is re-planned.

Unified AI reads your DCS, historian, batch records, ERP, CRM and demand channels. When a batch goes off-spec, it finds the cause first, then every job the failure touches, and puts the re-plan in front of the person who owns the call. It writes to nothing.

See it on your worst week

A 30-minute walkthrough built on your plant's own scenarios.

How one plant cut cycle time 25.8%
Plant view · night shiftReactor train A
Timeline: batch R-3 goes off-spec at 02:00, the root cause is found by 02:10, a re-plan of every order it touches is ready by 02:2002:00Batch R-3 off-spec02:10Root cause found02:20Re-plan ready
Root cause · 02:10Strong

Heating step overshot by 6°C for 14 min on R-3. Matches 3 earlier deviations on this product.

Jobs touched

  • ORD-4471movedThu · R-1
  • ORD-4473movedThu · R-1
  • ORD-4480movedFri · R-2
  • ORD-4462Wed · R-3
  • DEL-2210movedFri · export
  • ORD-4488Mon · R-2
RecommendationLikely

Move ORD-4471 and ORD-4473 to R-2, Friday campaign. Hold the ORD-4480 raw-material draw.

Reason (kept with the decision)
Decided by Shift planner, night

Illustrative product surface.

~10 min
to root cause, from hours
25.8%
shorter cycle time, audited
$5.1M/yr
created on one customer’s P&L
3 months
to full rate on 2 new products. The plant’s norm was 12.

All figures from one $200M specialty chemicals company. One plant, not a typical result.

Every plant has a control system. None has an operating system.

  • Off-spec batch.Which orders slip?
  • Supplier slips.Which batches wait?
  • Order doubles.Which campaign moves?
  • Reactor down.Which products re-sequence?
  • Interlock trips.Operator error, or process problem?
  • Operator retires.Which settings leave with them?

A DCS runs one reactor. A historian remembers one tag. An ERP holds one order book. Nothing has ever run them together, so when something changes, the job falls to a meeting. Six departments, four days, and an answer that describes a plant that has already moved on.

An operating system for the plant does what the meeting does, in minutes: finds why, works out what still holds, re-plans every job the change touches, and hands the decision to its owner.

One off-spec batch fans out to the batches, orders, deliveries and raw material it touches, then collapses into one re-plan decisionBatchesOrdersDeliveriesRaw materialOff-spec batch02:00, reactor R-3
RecommendationLikely

Re-sequence R-1 to run ORD-4473 first; pull 400 kg RM-118 forward; move DEL-2210 to Saturday's container.

Reason (kept with the decision)
Decided by Plant planner

One decision. Every job it touches, already re-planned.

Reads your DCS, historian, batch records and ERP. Writes to none of them.

  1. 1Something changes: a batch goes off-spec, a delivery slips, an order doubles.
  2. 2It finds the cause, against every batch and every system before it.
  3. 3It finds what the change touches and re-plans every affected batch, order and delivery.
  4. 4A named person accepts or rejects, with a reason, and the reason is kept.
RecommendationLikely

Hold batch 2248-85 at the heating step; re-sequence ORD-4471 to R-2.

R-2 is free from 06:00 and the order ships Friday.
Decided by Production manager, B shift
Data flows one way: from the DCS, historian, batch records, QMS, ERP and CRM into Unified AI, then to the person who decides. There is no write path back.DCSHistorianBatch recordsQMSERPCRMUnified AIread-onlyre-plan · recommendPlant plannerdecidesno write pathnothing is written to controls, batches or orders

40°C, not 45°C. The whole difference sat in one operator's hands.

For years one operator ran batches faster than every other shift and nobody knew why. In week four the system found it: heat terminated at 40°C, not the 45°C in the procedure. It is now the standard.

At the same plant it found a manual step that appeared in no procedure, that the product manager did not know existed, and that the plant depended on.

Every finding a person accepts or rejects is kept against that plant, product and stage. When the operator retires, the reason stays.

RecommendationStrong

Terminate heating at 40°C on this product. Matches the fastest 31 batches; no quality deviation recorded.

Accepted. SOP revised; C shift briefed.
Decided by Process engineer
Illustrative reactor temperature over one hour. One trace stops heating at 40 °C after 30 minutes; the procedure trace continues to 45 °C at about 53 minutes. The gap is time recovered per batch.20°C30°C40°C50°C015304560 mintime recovered per batch40°C · 30 min45°C · 53 minIllustrative trace
  • Best operator, heat stopped at 40°C
  • Procedure, heat stopped at 45°C
Illustrative scale-up ramps. Two new products reach full production rate at month 3. The plant's previous norm, shown as a dashed reference, reached full rate at month 12.0%50%100%036912 monthslab target bandfull rateplant norm, 12 monthsfull rate at 3 monthsIllustrative
  • Product A
  • Product B
  • Plant's previous ramp

2 new products at full rate in 3 months. The plant's norm was 12.

Scale-up is where specialty chemicals loses the most money and the most time. Every trial batch is judged against lab targets by hand, first-campaign settings are guessed from the last product, and the ramp runs for months while the plant learns what the lab already knew.

Unified AI evaluates every trial batch against the lab target band, recommends first-campaign parameters from the plant's own history, and flags ramp deviations as they start rather than at the batch review.

At one $200M specialty chemicals company, two products reached full rate in 3 months, with no additional capex. The plant's previous norm was 12.

9 months in, one plant plans its month off our numbers, not its own engineering standards.

  1. Starting point. A $200M specialty chemicals company, multi-plant, multi-product, multi-reactor, running a DCS with 1-minute data and no spare engineer.
  2. First deviation. Root cause in about 10 minutes, against hours of reconstruction across logsheets, trends and QC results.
  3. Cycle time. 25.8% shorter on the product line studied, audited.
  4. Scale-up. 2 new products at full rate in 3 months, with no additional capex. The plant’s norm was 12.
  5. Planning now. 9 months in, monthly production is planned off the system’s measured cycle times and yields rather than the plant’s own engineering standards.
One month, one product lineeach block is one batch
Engineering standard
Measured, 25.8% shorter
batches the month gains at the measured cycle timeIllustrative

The monthly plan now starts from the measured cycle time, not the standard the plant wrote years ago.

Process, scale-up, maintenance, quality, inventory, planning. One system, not six.

A batch train from raw material silo to reactor, heat exchanger, dryer, packaging and dispatch, with the six areas numbered where they apply: 1 Process engineering, 2 Scale-up, 3 Maintenance and utilities, 4 Quality, 5 Inventory, 6 Planning123456
  1. 1

    Process engineering finds the deviation, ranks the root causes and shows where cycle time goes.

  2. 2

    Scale-up checks every trial batch against lab targets and recommends first-campaign settings.

  3. 3

    Maintenance and utilities flag failure precursors and rank work orders by batch impact.

  4. 4

    Quality assembles out-of-spec data against process conditions and pre-screens batch records.

  5. 5

    Inventory recommends reorders and prices every expedite against the orders it saves.

  6. 6

    Planning re-sequences campaigns to cut changeovers and shows what a rush order really costs.

Bring us your worst week.

Pick the deviation, the slipped delivery or the rush order that cost you most this quarter. We will show what the plant would have known, and when.