Pilot plants are where good ideas mature into profitable products. However, too often, pilot plant automation is treated as “temporary,” built quickly to get product out the door, with the assumption that manufacturing automation will be redesigned later. In reality, pilot plants frequently run longer than planned, support multiple products, and eventually become the blueprint for full-scale manufacturing.

This is where ISA-88 (ANSI/ISA-88 / IEC 61512) becomes not just relevant, but essential

When applied correctly, S-88 provides a structured, scalable automation architecture that allows a pilot plant to evolve into manufacturing with minimal rework—both in control logic and in operator workflows. More importantly, it enables process knowledge to be captured once and reused across equipment sizes, configurations, and facilities.

One of the most powerful aspects of S-88 is its formal separation of:

• Process Model – what needs to happen
• Equipment Model – where it happens
• Procedural Control – how it is executed

In pilot environments, it is tempting to hard-code sequences directly into PLC logic tied to specific valves, pumps, and vessels. That approach works—until the same process must run on a different skid, a larger vessel, or a parallel unit in manufacturing. By designing a proper S-88 batch model early—defining operations, and phases independent of equipment—you ensure that the process intent is preserved regardless of scale. The pilot plant stops being a one-off system and becomes the first implementation of a scalable manufacturing platform.^[1]

Recipes are where pilot automation most often breaks down during scale-up. In non-S-88 systems, recipes are tightly coupled to unit sizes, fixed quantities, and specific I/O. Scaling becomes a copy-paste exercise that introduces risk and inconsistency. An S-88-based recipe strategy avoids this by leveraging:

• Master Recipes that define process logic
• Site and Control Recipes that bind execution to specific equipment
• Formulas that parameterize quantities, timing, and conditions

Using the formulas concept, a single master recipe can be made generic across:

• Different vessel volumes
• Multiple unit classes
• Pilot batches, engineering runs, and full-scale production environments

Instead of rewriting recipes, scale-up becomes an exercise in configuration—adjusting parameters, constraints, and equipment capabilities while preserving the validated process logic.^[2]

A common failure mode in pilot automation is a mismatch between recipe expectations and control code structure. S-88 avoids this by prescribing a modular equipment hierarchy:

• Equipment Modules (EMs) represent functional groupings (e.g., “Charge Solvent,” “Heat Reactor”)
• Control Modules (CMs) encapsulate the lowest-level control elements (valves, motors, PID loops)

When EMs and CMs are designed explicitly to support recipe-driven execution, several benefits emerge:

• Phases map cleanly to equipment functionality
• Reuse becomes practical instead of theoretical
• Testing and validation effort is dramatically reduced
• Operators experience consistent behavior across units and scales

In pilot plants, this modularity is especially valuable because equipment configurations change frequently. A well-designed EM/CM layer absorbs those changes without forcing recipe or sequence rewrites.

Organizations that treat pilot plants as disposable prototypes often pay for it later—through rushed redesigns, extended commissioning timelines, and hard-to-validate manufacturing systems.

By contrast, pilot plants designed around ISA-88:

• Capture process knowledge in a structured, reusable form
• Enable early operator and process validation
• Reduce manufacturing automation risk
• Shorten time from pilot success to commercial production

In many cases, the pilot system becomes the template for manufacturing—sometimes even reused directly with minimal modification.

When applied correctly in pilot plants—through proper batch modeling, scalable recipe design, formula-driven flexibility, and disciplined equipment module architecture, it transforms pilot automation from a short-term necessity into a long-term asset. The result is not just smoother scale-up, but a more flexible, understandable, and maintainable automation system.

Contact our experts at Stellaro Technologies to learn how we can help you design and commission a flexible Batch system built to scale from R&D to Manufacturing.