Home / Projects

Process blending control retrofit - an outline.

Illustrative example of the kinds of controls work we take on. The project described here is an archetype, not a portfolio — specific client work is discussed under NDA.

This is an outline, not a delivered case study. It describes the shape of a typical engagement of this kind: the questions we ask up front, the work involved, and how the cutover tends to be sequenced. Actual scope, schedule, and outcomes vary by site.

Example screen

What the operator sees on the mix screen.

The recipe library on the left, the live mix in detail on the right. Both live in the same HMI, on the same screen, so the operator can queue and start mixes without digging through menus.

The HMI screens below are conceptual mockups for illustrative purposes only. They are not real-life screenshots from a live customer system or deployed plant HMI.

RUNNING ▶ MIX LIST 18 RECIPES · 3 ACTIVE
SELECTED · MIX #1
FINE MIX SANDY
MIX%ACT
1. FINE MIX100+
2. UC2 FOB 25% RAP100+
3. TEST MIX DNV100+
4. UC4 10% RAP100+
11. CLASS 1 20% RAP100+
12. 12.5 SUPERPAVE100+
13. 19MM SUPERPAVE100+
MIX RUNTIME CONTROL · 120 TPH TARGET
START MIX PAUSE STOP MIX ABORT
MIX PLANNER · L2
RUNNING ▶ FINE MIX SANDY MIX #1 · TARGET 120 TPH
TARGET
120t/h
ACTUAL
0.0t/h
AGG
100%
ASP
6.70%
MIX TEMP TC
352°F
MIX TEMP IR
351°F
ASP TEMP IR
322°F
TONS RUN
20.9t
AGGREGATE%t/h
5mm Clear10.011.20
Paving Sand48.053.74
7.9mm−42.047.02
ASPHALT · PG64-226.708.04
Recipe active · Operator L2 REV SAVE EDIT %
Typical situation

An aging plant, a glitchy computer, and a busy paving season ahead.

Continuous drum plants with legacy control systems are often partly serviceable and partly at risk: some field hardware may still have useful life, while the PLC, HMI, or support computer may be hard to maintain. Another paving season is just around the corner, and the owner needs a clear view of what can be kept and what should be modernized.

The constraint tends to be the same: a winter shutdown window and a non-negotiable paving start date in the spring.

What the work typically involves

One control platform, one HMI, one alarm philosophy.

  • A PLC platform selected with the client, which may be a new controller or integration with suitable existing I/O
  • Remote I/O or field-device integration sized around the plant's existing wiring and hardware condition
  • Operator HMI station with dual monitor set up
  • Asphalt-oriented custom 3D graphics HMI built from our reusable components — mix, overview, materials, totals, calibration
  • Alarm rationalization aligned with ISA-18.2
  • An on-prem SQL Express historian, with optional cloud KPI feed
  • VPN-based remote support arranged in place of exposed RDP
  • Operator training
How a cutover is usually sequenced

From shutdown to first paving truck.

The exact length depends on the plant. The phases below are usually present in some form.

Phase 1 · Strip & pre-wire

Hardware is removed only where needed; new panels, controllers, or remote I/O are mounted where required, and serviceable field wiring is carried forward.

Phase 2 · Loop checks & safety

Every I/O point is exercised. Drive, motor interlocks and safety systemstested. All with a qualified technician on site.

Phase · Calibration

Calibration of all ingredient channels is completed. Single or multi-point calibrations available.

Phase 4 · Dry-run mix

A small number of mix designs produced to storage silos. Totals reconciled against the truck scale before any customer trucks are loaded.

Phase 5 · Operator dry-run

Operators run the full HMI through a typical paving morning — start-up, mix change, silo drop — before the first paving day.

Phase 6 · Hand-off & first paving day

We aim to be on site for the first customer truck, with remote support arrangements after that.

Common project specs

  • PLC: Siemens, Rockwell, or other suitable platform
  • I/O: existing or new I/O sized to the plant
  • HMI: FactoryTalk Optix
  • Network: PROFINET, PROFIBUS, EtherNet/IP
  • Historian: SQL Express, ODBC-Compliant
  • Cloud: AWS, AZURE optional

Questions we usually ask up front

  • What is the current PLC and HMI, and roughly how old?
  • How long is the shutdown window?
  • What is the non-negotiable start date?
  • What dispatch / ticketing system is in use?
  • Are the field wiring drawings up to date?
  • What does the operator group look like on day one?

Planning something similar?

If a drum plant retrofit is on the radar, a short conversation about the shutdown window and current PLC platform is usually a good place to start.

Get in touch