There are many variations of batch processing software on the market, all of them more
or less complying with the ISA S88 batch process model. The following best practices are
suggested for batch processing software:
1. Select a batch processing system with an open architecture that is compliant with ISA S88
and can be easily interfaced with the process control system from any vendor.
2. The batch process software model should be able to run concurrent batches with
different recipes.
3. Create a flexible batch process integration model in the software, giving it the most
flexibility for common resources used in the plant (for example, a valve matrix for material
transfer, common equipment like blenders, etc.) so that many batches with different recipes
can be run concurrently with less equipment downtime.
4. The batch process model should easily interface with the process control system. The
process control logic should be designed to be intelligent enough to make these dynamic
flexibility decisions.
5. The batch software should be able to archive and send reporting data for batch reporting
as well as MES modules for analysis and interface with the enterprise system.
6. The batch software should have a material tracking module, preferably to get the material
information and trace it.
7. The batch software should have a user-friendly client with an SFC run-time display for
recipe monitoring as well as features to take individual operations and phases in control.
8. The batch processing software suite should be complemented and supported with an
electronic workflow management system to automate SOPs as well as manual actions to
record authentications and comply with 21 CFR Part 11.
Liked this article? Download the entire playbook here.
