1. Home
  2. Industries

Organised by process, not by product.

Two plants making different products often share the same operational problem, while two plants in the same sector rarely do. How a factory makes things decides how it should be digitised.

Why process type matters more than sector

Sector is a label. Process type is a design constraint.

A pharmaceutical packing line and a consumer electronics line are both discrete, high-changeover operations with serialisation requirements, and the systems they need look much alike. A pharmaceutical reactor and a speciality chemical reactor are both batch processes with recipe control and deviation management, and they need something quite different.

Process type

Discrete and assembly

Automotive and components, consumer durables, electronics, industrial equipment, fabrication and packaging.

What defines it

Countable units moving through stations. Cycle time rules, changeovers are frequent and expensive, line balance sets throughput and quality is judged per unit. Traceability runs by serial number or batch through the bill of materials.

Where signal dies

Micro-stops nobody records because each one is short. Changeover time booked as “setup” with no breakdown. Rework that leaves the line and re-enters it without ever appearing in the yield figure.

What we typically build

  • Station-level cycle and micro-stop capture
  • Changeover tracking with reasons
  • Serial and batch genealogy through the BOM
  • In-process quality gates with error-proofing interlocks
  • Line balance and bottleneck analysis
  • Rework and repair loop visibility
Process type

Batch and formulation

Pharmaceuticals, speciality chemicals, paints and coatings, food and beverage, cosmetics and personal care.

What defines it

Recipes, vessels and defined quantities. The batch is the unit of costing, quality, traceability and release. Recipe adherence and parameter control decide the outcome, and deviations need a documented investigation before release.

Where signal dies

Parameters logged on paper at intervals, so an excursion between readings is invisible. Yield reconciled at month end. Deviation investigations that take weeks because the evidence sits in several systems.

What we typically build

  • Electronic batch records with parameter capture
  • Recipe and formulation checks at dispensing
  • Continuous parameter monitoring against limits
  • Deviation and CAPA workflow with evidence attached
  • Yield reconciliation per batch, not per month
  • Cleaning and changeover verification
Process type

Continuous and process

Cement, steel and metals, paper and pulp, glass, textiles, power and utilities.

What defines it

Uninterrupted flow, measured by rate. A stop is expensive, energy is a dominant cost, asset reliability decides output more than labour does, and quality is a property of a stream rather than a unit.

Where signal dies

Large volumes of historian data that nobody analyses. Energy billed monthly and never allocated to production. Condition monitoring on critical assets, reviewed only after a failure.

What we typically build

  • Specific energy consumption per tonne or unit
  • Utility metering allocated to lines
  • Condition monitoring with actionable thresholds
  • Rate, yield and quality stream analytics
  • Shutdown and start-up sequence management
  • Emissions and environmental compliance records
Process type

Regulated and validated

A layer across the other three: pharmaceuticals, medical devices, aerospace, food safety, and any operation subject to customer or regulatory audit.

What defines it

The record is the product. Every entry needs attribution, a timestamp and an audit trail; changes must be traceable; and the systems themselves need qualification. Audit readiness is continuous rather than periodic.

Where signal dies

Compliance evidence assembled in a hurry before an audit rather than produced by normal work. Paper records that satisfy the letter of a requirement while telling nobody anything useful.

What we typically build

  • Attributable, time-stamped electronic records
  • Audit trails on every change, with reasons
  • Electronic signature and approval workflows
  • Training and certification linked to task authorisation
  • Continuous audit-readiness reporting
  • Documentation supporting system qualification
Most plants are more than one type

Most plants combine types. A pharmaceutical site typically runs batch manufacturing feeding a discrete packing hall, under a regulated layer covering both.

That is why we design the operational core first, so that different process worlds can share one definition of a lot, a shift and a deviation.

Start with the audit, not the software.

A fixed-scope diagnosis of where your plant loses information, what it costs you and what to fix first. The roadmap is yours to keep, whoever builds it.