• Subscribe
  • Products
  • Factory
  • Process
    1. Factory
    2. Analytics

    Batch Forensics: The Case for Procedural Unit Tags

    Aug. 16, 2021
    Simple to implement, unit tags provide instrumental value that can enhance recipe editing capability and execution.
    Randy Otto, CEO, ECS Solutions
    Randy Otto, CEO, ECS Solutions

    A unit tag is a class-based tag that identifies a characteristic of a unit.

    The values of these tags are usually associated with information captured via the control systems analog and digital input cards, signals like temperature, weight, pressure, level, conductivity, pH, level switch, etc. Other unit tags can contain the status, state, material of construction, or any other user-defined attribute that can enhance the recipe editing capability and execution.

    Figure 1 – Batch Process
    Figure 1 – Batch Process
    In the ISA-95 standard in figure 2, these are defined in levels 1&2, these signals are used to provide basic control, supervisory control, process sensing, process manipulation, etc. 
    Figure 2 – ISA-95 levels representation
    Figure 2 – ISA-95 levels representation
    This information—in addition to being used for basic control—can be exposed to the recipe author as “unit tags". In the procedural model, these can then be used by the recipe author to specify procedural decisions based on process and equipment information. As per the ISA-88 model in figure 3, the procedural model now contains the unit tags, the workflow also lives in level 3 of the ISA-95 layer. 
    Figure 3 – ISA-88 Procedural end Equipment Models
    Figure 3 – ISA-88 Procedural end Equipment Models
    In the following sequential function chart, figure 4, we can see how the recipe author specified the requirements for an operation to manufacture a product. Not just the required steps (add material A, add material B, temperature control and agitation phases) and their set points but also specified the conditions that must exist to complete or to start a step, these conditions are specified in the expressions of the transition conditions (T1, T2, T3, T4, T5). 
    Figure 4 – Sample Operation Level Recipe using unit tags
    Figure 4 – Sample Operation Level Recipe using unit tags

    Material A (1000 Kg) should be added while heating (71°C) while slowly mixing (20%), during the addition transition expressions T5 monitors the unit weight to change the mixing speed from 20% to 75% once the weight in the unit is greater than 500 Kg (Unit Weight – Unit Tag).

    As per transition expression T2, material B (150 Kg) should only be added after material A addition is complete and the content of the unit has reached a temperature greater than 50°C (Unit Tag – Unit Temperature).

    As per transition expression T3, once the material B addition is complete, we need to start a 10-minute fusion timer but, only if the material in the unit has reached a temperature greater than 70°C (Unit Temperature – Unit Tag).

    After the fusion timer is complete the recipe will stop controlling temperature and agitation and then move on to the next operation.

    Other examples of unit tags can be:

    • CIP supply and return conductivity, temperature, flow.
    • Thermal lethality factor (F0).
    • Total volume or weight transferred.
    • Etc.

    Unit tags can be used for equipment selection (unit attribute binding) during control recipe creation such as:

    • Material of construction (plastic, stainless steel, glass lined, etc.),
    • Unit status (To be cleaned, clean, sterile, sterile expired, clean expired, ready, disabled, etc.)

    Unit Tags are very simple to implement during the automation setup process and should expose all pertinent equipment information, since they provide the recipe author the capability to condition the procedural activities based on process conditions as well as equipment status.

    Randy Otto is CEO of ECS Solutions, a certified member of the Control System Integrators Association (CSIA). For more information about ECS Solutions, visit its profile on the CSIA Industrial Automation Exchange.
    About the Author

    Randy Otto | CEO of ECS Solutions

    Randy Otto is the CEO of ECS Solutions and brings more than 25 years of experience in diverse industries, including glass fibers manufacturing and custom assembly machine manufacturing. Before joining ECS, Randy spent 10 years managing the delivery of assembly equipment for Integrated Systems Manufacturing and process control systems for Premier System Integrators. For most of the last 12 years, he has managed business development and sales for ECS. Randy graduated from Purdue University with a degree in electrical engineering technology. He has an MBA from the University of Southern Indiana.

    Companies in this Article

    Continued Reading

    Sponsored Recommendations

    Put the Plant Floor in Your Pocket with Ignition Perspective

    Build mobile-responsive HTML applications that run natively on any screen.

    Ignition: Industrial-Strength System Security and Stability

    Ignition is built on a solid, unified architecture and proven, industrial-grade security technology, which is why industrial organizations all over the world have been trusting...

    Iron Foundry Gains Competitive Edge & Increases Efficiency with Innovative Technology

    With help from Artek, Ferroloy implemented Ignition to digitally transform their disconnected foundry through efficient data collection and analysis while integrating the new ...

    Empowering Data Center Growth: Leveraging Ignition for Scalability and Efficiency

    Data center growth has exploded over the past decade. Initially driven by organizations moving their computer assets to the cloud, this trend has only accelerated. With the rise...

    Sponsored