Most people use the word recipe loosely to mean everything needed to make a product. ISA-88 is more precise: a recipe is made of several distinct parts, and the formula is only one of them. The formula holds the values, the amounts, temperatures, times, and yields, that tune the recipe for a particular product or batch size. It deliberately does not contain the ordered logic that says what to do first, which lives in the procedure. This page separates the formula from the procedure, the header, and the equipment requirements, and shows how formula values flow down into phase parameters at run time.
recipe formula in one line: In ISA-88 the recipe formula is the collection of process inputs, process parameters, and process outputs, that is, the numeric and enumerated values that parameterize a recipe, without any of the ordering logic. The order of operations lives separately in the procedure, and administrative information lives in the header, so the formula is strictly the values, not the sequence.
ISA-88 breaks a recipe into distinct categories of content so that each can be authored, reviewed, and reused independently. The header carries administrative information such as the recipe name, version, author, approval status, and effective dates. The equipment requirements state what kind of equipment the recipe needs, expressed as capabilities and constraints rather than specific tagged units. The procedure defines the ordered strategy for making the product, the sequence of unit procedures, operations, and phases. Other content such as formula, and optionally other information like comments or references, rounds out the definition.
The formula is the category that answers the question of how much and how hot and how long. It is divided into three parts. Process inputs are the materials and energy consumed, such as the quantity of a raw material to charge. Process parameters are the values that govern how the process runs, such as a mixing temperature, an agitation speed, or a hold time. Process outputs are what the recipe is expected to produce, such as the target quantity and quality of product, and by-products or waste.
Keeping these categories separate is the whole point. The procedure describes the strategy once, and the formula supplies the numbers that make that same strategy produce a specific grade, color, or batch size. Two products that share a manufacturing strategy can share one procedure and differ only in their formulas, which is a major reduction in the amount of logic that has to be written and validated.
The cleanest way to hold the distinction is this: the formula is what, the procedure is when and in what order. A charge of 500 kilograms of solvent and a hold at 65 degrees for 30 minutes are formula values. The rule that says charge the solvent, then heat, then hold, then cool is procedure. The same procedure can run with many different formulas, and the same formula would be meaningless without a procedure to consume it.
This separation is why ISA-88 recipes scale and generalize so well. A base procedure captures the manufacturing know-how, the correct sequence and interlocks, once and correctly. Formulas then adapt that procedure to each product variant without touching the logic. Because the risky, complex part, the ordering and safety logic, is written once, changes to a product often mean editing only formula values, a far lower-risk activity than rewriting sequence logic.
It also clarifies who owns what. Process and product engineers who understand the chemistry and the target grades work primarily in the formula, adjusting values to hit a spec. Automation and controls engineers who understand the equipment and sequencing work primarily in the procedure. The formula-versus-procedure boundary lines up with a natural division of expertise, which is part of why the standard has held up across so many industries.
Formula values do not act on equipment directly. They flow down into the procedure as phase parameters. A phase such as heat carries parameters like target temperature and ramp rate, and the formula supplies the actual numbers for those parameters when the recipe is instantiated as a batch. In a general or site recipe those values may be nominal, and they get refined into a specific, executable master or control recipe that the batch engine runs on real units.
Scaling is a common formula operation. A recipe written for a nominal batch size can be scaled up or down by a factor, and the batch engine multiplies the scalable formula inputs, such as material charges, by that factor while leaving non-scalable parameters, such as a fixed reaction temperature, unchanged. Marking which formula values scale and which do not is part of authoring a good recipe, because scaling the wrong value quietly ruins the product.
For SCADA and remote monitoring, the value of this structure is traceability. When the batch engine records the exact formula values used for a given batch, every setpoint and charge is captured against that specific run. A cloud SCADA platform such as Merobix can surface those as-run formula values alongside the live process data, so an operator or a remote supervisor can confirm that the batch ran on the intended formula and later reviewers can compare the planned values against what the equipment actually delivered.
The formula is the set of values, process inputs, parameters, and outputs, that parameterize the recipe, such as charge amounts, temperatures, and times. The procedure is the ordered logic that says what to do and in what sequence. The formula answers what and how much; the procedure answers when and in what order. They are separate categories of recipe content in ISA-88.
They are the three parts of an ISA-88 formula. Process inputs are materials and energy consumed, such as a raw-material charge. Process parameters govern how the process runs, such as a temperature, agitation speed, or hold time. Process outputs are what the recipe should produce, including the target product quantity and quality plus any by-products or waste.
A recipe can be scaled by a factor, and the batch engine multiplies the scalable formula values, typically material charges, by that factor. Non-scalable values, such as a fixed reaction temperature or a fixed hold time, stay constant. Which values scale and which do not is defined when the recipe is authored, because scaling the wrong parameter can spoil the batch.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.