MES or batch: What is the best answer?

Should an application use a manufacturing execution system or will batch software suffice? A small set of decision points can determine the most commonly used models for selection or integration of ISA 88 batch execution systems and ISA 95 manufacturing operations management (MOM) systems. Ask these questions to decide. The ISA 95 Technical Report TR95.02 – Integrating ISA 88 and ISA 95 workflows can help.


Figure 1: Orchestrated workflow. Courtesy: BR&L ConsultingMany have manufacturing execution system (MES), a batch management system, or a combination of the two. Deciding what parts of the process are better served by an ISA 88 batch execution system (BES), and which parts are better served by an ISA 95 manufacturing operations management (MOM) system or MES can be a contentious debate. The methodology and decision tree defined here can be used to help determine the appropriate tool and implementation architecture based on the ratio of equipment-based actions to manual-based actions. The methodology is based on work used to develop the draft ISA 95 Technical Report TR95.02 - Integrating ISA 88 and ISA 95 workflows. It addresses the fact that the typical MOM/MES is focused on manual actions, while a BES is focused on equipment control. Two different systems in a complete automation environment can be used together by using the strength of each system. 

New process control

Many companies have islands of automation in their facilities, with some systems using ISA 88 BES, some with paper processes for coordination of automated equipment, some using an ISA 95 MES/MOM system, and often every possible combination. When it comes time to expand a system or add new production lines, the same question always comes up: What system are we going to use to control the new production process?

  • Will it be an MES system because many manual actions must be coordinated?
  • Will it be a BES because a lot of automated equipment must be coordinated?
  • Will it be a combination?
  • What if it must integrate with existing automated equipment?

The usual answers are more likely to be based on local experience, or integrator experience, with the MES options or the BES options, rather than a careful evaluation of advantages and disadvantages. Selecting the best option requires some knowledge of both the MES and BES models. 

Workflow models

Figure 2: Choreographed workflow. Courtesy: BR&L ConsultingThe core model for many MESs and BESs is workflows. The workflows are what provide automated execution support for standard operating procedures (SOP), standard work instructions, and other production procedures. The workflows can be customizable or editable, or can be hard-coded (as is typical in weight and dispense procedures).

There are two basic models for workflows: an orchestrated model and a choreographed model. In the orchestrated model, a coordination workflow contains the logic to sequence lower level workflows. The lower level workflows don't directly interact with each other, but only with the coordinating workflow.

Many business systems follow the orchestrated workflow model because it improves modularity and reusability of services. The orchestrated model also provides a single view into the coordinating workflows, making it easy to see the status of the work and determine the next steps.

While there is a performance penalty from the centralized coordination service, the impact is usually not significant at the relatively slow speed of business processes. The biggest problem with the orchestrated model is that it does not scale well to entire organizations. Orchestrated workflows work best when the job or task has a well-defined scope, such as in the execution of an ISA 88 recipe.

In the choreographed model there is no overall coordinating workflow. Any workflow may trigger the execution of another workflow, and wait for a response or continue asynchronously. The overall workflow process is defined by the collection of rules implemented in the individual workflows. Because there is no single view into the workflows, the choreographed model does not provide a simple way to view the status of the work and determine the next steps.

Figure 3: Recipe orchestrating equipment procedures. Courtesy: BR&L ConsultingChoreographed workflows are used when there is a large scope of work, no single overall triggering condition, or no overall coordination is needed. The choreographed model can handle faster process times and is the model often used in manufacturing applications and in customer-facing Internet applications. Both of these applications must handle thousands of interactions per minute with minimal latency and delays.

MESs typically use the choreographed model. An MES will often handle manual tasks that are triggered by external events or other workflows. An MES workflow will often have significant logic to handle exceptions and errors.

BESs, following the ISA 88 models, use the orchestrated model. Each recipe is an orchestrating workflow, commanding the lower level actions (called equipment phases in the ISA 88 standard) in an orchestrated manner. The lower level procedures are phase logic, usually implemented in equipment modules. This model allows for a single view into the status of a batch and is designed for reusability of the lower level equipment phases in different recipes and across different equipment.

BES recipes are specialized workflows. They follow the orchestrated model, and their primary purpose is the control of equipment. The equipment control can be directly to automated equipment, or as commands to operators to control equipment. Because of the focus on equipment control, batch systems also implement mode and state control of the workflow. Modes allow operators to control the execution of the workflow, allowing it to run in automatic mode, single stepped using a semi-automated mode, or entirely manual with no automatic stepping through the workflow. State control allows for the workflow to be paused, resumed, stopped, and aborted. Not all MESs provide this ability to control their workflow execution through modes and states. 

Workflow on top?

Figure 4: Is there a coordinating workflow? Courtesy: BR&L ConsultingThere is a typical pattern for operational workflows that is based on a simple decision. If the system will receive process orders that will require multiple separate jobs (batches or production runs), or there is work in process (WIP) that is managed at the operations level, then there is typically a workflow system that receives the process orders, supports breaking each process order into jobs, assigns jobs to work centers (process cells, production lines, etc.), and tracks WIP. In this case there is a workflow coordinating activities in work centers. The top level workflow can be configured, or can be dynamically interpreted depending on the tool chosen. In making a decision on the use of an MES or batch system at each work center, one can follow a decision tree to determine the appropriate model to be used. In any complex manufacturing facility, there may be different models for different work centers. For example, there may be a batch model for primary processing, a manual workflow for packaging, and a mixed model for incoming material and material preparation. 

<< First < Previous 1 2 Next > Last >>

Anonymous , 09/30/16 03:41 AM:

Perhaps a bit late to post a comment almost 2 years after publication. However, I think still relevant. In general a great article. However, decision #4 caught my eye, the question if the system has a standard PackML interface. The tree depicts only the route to implement 'custom proxy' model 2 in case no standard PackML is present. The text suggest that usualy model 3 is chosen in such a case. I wonder if you could give some more insight in this part of the tree. Does the tree perhaps lack an additional decision to determine between model 2 or 3?
Anonymous , 09/30/16 03:59 AM:

In addition to my previous comment. Do you have some practical insights as on how to actually measure the percentage of basic equipment executed actions and on how to determine the primary coordination type. (decisions 1 and 2)
The Engineers' Choice Awards highlight some of the best new control, instrumentation and automation products as chosen by...
The System Integrator Giants program lists the top 100 system integrators among companies listed in CFE Media's Global System Integrator Database.
The Engineering Leaders Under 40 program identifies and gives recognition to young engineers who...
This eGuide illustrates solutions, applications and benefits of machine vision systems.
Learn how to increase device reliability in harsh environments and decrease unplanned system downtime.
This eGuide contains a series of articles and videos that considers theoretical and practical; immediate needs and a look into the future.
Make Big Data and Industrial Internet of Things work for you, 2017 Engineers' Choice Finalists, Avoid control design pitfalls, Managing IIoT processes
Engineering Leaders Under 40; System integration improving packaging operation; Process sensing; PID velocity; Cybersecurity and functional safety
Mobile HMI; PID tuning tips; Mechatronics; Intelligent project management; Cybersecurity in Russia; Engineering education; Road to IANA
This article collection contains several articles on the Industrial Internet of Things (IIoT) and how it is transforming manufacturing.

Find and connect with the most suitable service provider for your unique application. Start searching the Global System Integrator Database Now!

SCADA at the junction, Managing risk through maintenance, Moving at the speed of data
Flexible offshore fire protection; Big Data's impact on operations; Bridging the skills gap; Identifying security risks
The digital oilfield: Utilizing Big Data can yield big savings; Virtualization a real solution; Tracking SIS performance
click me