4 Effective Ways on Achieving Successful Skid Integration in Batching Operations

Four major guidelines for having a successful skid integration when it comes to batching operations 

The integration of the kid equipment in OEM in the overall batch management system will be requiring a clear and specified level of coordination. This coordination should come between the salve and master (DCS or SCADA) systems. The simplistic command set the slave system that does not give the provision for visual representation of the whole system. Once everything is working perfectly fine, a simple command from the master to the slave system is already sufficient to make everything work. However, there is an exemption to this rule. Once the exception condition is bound to happen, it is going to be very hard to determine or troubleshoot without the need to go out to the equipment’s HMI. This is the local human-machine interface to identify the issue. 

With this in mind, this kind of interference can increase the batch cycle time, can lessen the equipment utilization and it can decrease the overall efficiency of the operations. The only solution to this dilemma is to combine a slave OEM system inside the overall master processing system by following these four simple guidelines: 

Distribute the operating modes 

Standard operating states should be followed 

Identify the status feedback definition 

Have communications standardized 

The only thing that can solve this problem is to have tow different pieces of the equipment synchronized by identifying the agreed methodological set of interactions. The flexible batch solution should have an isolation happening between different set of functions. 

1. Distribute the operating modes 

The different operating modes of the remote equipment is a little bit complicated because the boundaries are not well defined. Should an operator implement changes to the local equipment once the controlled variables have been given instructions remotely coming from an overall recipe? Is the recipe will go to the “hold” state when a specified operating status is bound to change? These are the sample few questions that has to be considered when remote systems are to be integrated. The operating philosophy and interface should over rule. This happens between the master and the salve system and should be identified to continually give a uniformed interface between two different systems. 

2. Standard operating states should be followed 

Standard operating states should be followed to enable a mechanism to handle the hardest part of a batch. With this in mind, this is the exception condition. This is identified as a mechanism behavior that exists in the outside of the usual normal or desired behavior of the system process. The critical elements of the batch production includes the handling, processing, and recovering from these types of systematic operations.