Analysis of the Mesh Topology in ISA100.11a D2.
Before a network can be used it must be formed. As part of this formation, devices must be provisioned with a network ID and a join key. The network ID is used to associate a device with a network and the join key is used to protect the device as well as the network during the join operation. Provisioning devices can be done by the manufacturer, in the maintenance shop, or in the field. In the D2 draft neither the requirements for nor the actual physical interface for provisioning has been specified.10/07/2008
The ISA100.11a D2 draft is a major step forward over D1. The D2 document is the first draft that attempts to be a full specification of the network and application protocols for process monitoring and control devices. However, it is incomplete.
The editors have done a substantial amount of work in generating the newest version of the specification. A large number of comments were reviewed, accepted, accepted in principal or otherwise incorporated into the document. In addition, new technical material was developed to fill in the technical omissions that existed in the old document. As a result, the D2 draft requires a thorough review.
In reviewing the document the first goal is to determine if the technical details meet the overall goals stablished for the standard. This paper considers the primary goal of a standard: the interoperability and interchangeability of products (Section 6.2). The intent of this paper is to provide the reader with objective information about the draft to enable them to determine if these goals are met and to assist them in providing comments to the ISA100 committee.09/25/2008
The white paper describes the hardware and software elements of a video process monitoring system, how it uses the plants industrial network to transmit video to the control system and how the video images appear on HMI screens.09/10/2008
Control editor Walt Boyes speaks to the TÜV Safety Symposium in Cologne. Read a transcript of his speech, "Warum Ist Sicherheit So Schwer?/Why Is Safety so HARD?09/02/2008
Business drivers to improve performance, such as supply chain performance and operational effectiveness, require that integration of Enterprise Resource Planning (ERP) and shop-floor systems is considered. Many manufacturing companies have implemented the SAP R/3 ERP system, supporting core business processes including financials, sales, distribution and so on. The manufacturing processes may be controlled by a combination of automatic control equipment and human operators. SAP R/3 supports production planning functionality in its PP (standard production planning) module and sub-modules PP-PI (production planning for the process industries), PP-REP (repetitive manufacturing) and PP-Kanban. These modules support the exchange of data with external systems. However, the technology issues associated with such data exchange are part of a broader set of challenges that an integration project must address if the intended business benefits are to be obtained. This paper examines a business-driven approach to integration and explores recent project experience integrating shop-floor systems with the PP and PP-PI modules.08/28/2008
One of the current problems of batch automation specialists, especially in the pharmaceutical industry, is the integration of PLC-controlled units (package units, e.g. centrifuges, dryers) into DCS-like control systems maintaining homogenous structure. On the basis of IEC 61512-1:1997 standard Workgroup 2 of Hungarian Batch Forum prepared a draft Proposal for users and manufacturers of package units that suggests different methods for the integration of package units. The paper discusses the integration from a system-architecture point of view while the communication problems of control equipment are not considered.08/28/2008
In the recent years, batch process optimization has made significant advances. The efforts that went into the development of ISA-S88/IEC 61512 batch control standard has helped us in this direction. However, in todays highly competitive environment, optimization of individual manufacturing plants is not enough. In order to maximize the return on investments, control engineers must turn their attentions to site and company wide optimization along with the optimization of the supply chains. Typically, batch processes use many different raw materials to produce various products and grades of products. Market demands require frequent changes in product mix under short notice. Thus, batch processes offers greater opportunities than typical continuous processes for the optimization of raw material and intermediate supplies, production scheduling, and upstream and downstream transportations. For the last five years, the ISA-SP95 committee has been developing the standards for integration of control systems with business systems. This effort is significantly helping site and company wide optimization of manufacturing processes. Additionally, the recent developments in Internet and intranet technologies are increasing the feasibility of supply chain optimization. Today, the challenge for control engineers is to broaden their focus from narrow control issues to wider aspects of enterprise-wide optimization.08/28/2008
Successful Contract Pharmaceutical Manufacturing in a GMP regulated environment is heavily dependent on the flexibility and utilisation of the available processing plant and its guaranteed performance. However, changing plant configuration and revalidation is time consuming and therefore costly. This paper presents a case study of the implementation of an S88.01 based control system, as part of a strategy to change an existing process building with single product manufacturing capability, to a multipurpose plant and contrasts it with an earlier retrofit implementation to a similar plant for multi-product use. The paper reviews some important considerations in the equipment model design including the design approach for the control system architecture and methodologies employed for software coding of generic phases, which have been found to yield real economic benefits and ensure the achievement of the required plant flexibility. It also reviews the benefits to the design and validation process from following a structured 'GAMP3' approach. Some of the measurable economic benefits achieved will be shown to include reduced project implementation time, life cycle cost savings through reduced manpower effort during the engineering and validation stages and production capacity increase.08/28/2008
Does your plant suffer from high software maintenance costs, inflexible batch production, safety and environmental regulatory pressures? The Ineos Acrylics Plant at Darwen in the UK was experiencing these problems which are experienced with many legacy batch control systems in the modern chemicals market. The problems can be overcome with an S88 compliant system and approach but the right structure is essential. Reviewing the problems and plans to replace the system it was clear that a simple migration of the existing system would achieve little and that a complete re-structuring based on S88 was required. It was anticipated that this would give economic benefits of reduced software maintenance costs, increased production flexibility, reduced environmental/safety risks, all of which were achieved and more besides. This paper describes the process, problems and achievements of the project.08/28/2008
The World Batch Forum was originally formed to support the S88 Batch Control standard. All forums since have related in some way to the published part of the standard (S88.01) or to other, generally related, work. The second planned part of the standard is now ready for release. This paper attempts to put that event in perspective in the context of the current status of an on-going effort.08/28/2008
In the early days of batch automation there was usually a central computer that controlled everything. This computer ran recipes, executed sequential logic, did data acquisition of process variables and also performed direct digital control (DDC) of analog and discrete devices. Since one computer did every thing from sequencing to DDC it was only natural to imbed the shutdown and safety logic into the batch sequential code that was running normal operations. And since one huge monolithic program ran the entire process, the safety logic was always running. In modern S88 (IEC61512) based modular batch automation systems the monolithic code has been replaced by smaller reusable phases controlled by a batch manager that runs recipes. Many who have grown up with DDC imbed safety logic inside the phases. This approach requires an active equipment phase at all times to keep safety logic available at all times. There is a problem with this approach. Phases are transient by nature. They have a beginning and an end. You cannot guarantee that there will always be an active equipment phase. Although there may be some holding logic associated only with a specific phase, often this logic is generic and should be moved up to the unit level. This paper looks at methods available to the user for safety and exception recovery logic in current modular batch systems. Included are case studies of five separate batch projects where recognizing exception conditions and executing safety shutdown logic was essential.08/28/2008
From which supplier ingredient lots did we compose this batch? Which batches did this pallet feed? Which batches ran after it? Whats the effect of this badly performing unit on previous operations? Whats the correlation between ? These are not easy questions, too often left without an answer. In many cases we have to rely on a combination of the operators memory, some paper log sheets and a variety of electronic data sources. With the introduction of the ISA S88.01 standard in 1995 and the work of the SP95 committee, process industries finally receives a structured framework that extends its advantages beyond the pure process control aspects. By applying the standard, we have a basis for building in traceability as an intrinsic function of the production control system. We will focus on topics like material flow control, the process inventory, integrating quality control and non-conformity checking in the batch recipe and building product genealogy. During the presentation we will explain the methodology behind this and how leading enterprises have already successfully applied it.08/28/2008
All of the components, and the zones in which they reside, that comprise the scope and magnitude of batch manufacturing have always been a challenge to fully comprehend at a single instant. When attempting to automate these components one must understand the unique requirements of the zone in which the component resides, as well as the touch points and interactions between the different S88.01 models. The approaches used to modularize and automate these touch points and interactions have a great impact upon the usability of the automation. The concepts of Unit Modes, Equipment Module and Phase residency are key to a usable automated batch manufacturing application. This paper explores the zones of batch manufacturing and an approach to automate the touch points and interactions of the S88.01 models that provides a very usable application.08/28/2008
Alarm and event analysis has long been used for improving process operation. However since alarms are usually generated and displayed based on physical equipment, alarm analysis has been difficult to perform on a batch basis. In this paper, we focus on the interrelation of alarm/message notification and operator reaction in a batch process and analyze them systematically according to S88.01 Models and Terminology. Balance patterns of alarm/message notification and operator reactions are visually analyzed. Batch based analysis is done by grouping and filtering alarm and event data by master recipe, procedural hierarchy, and batch unit. This makes it easy to find and improve spurious alarms and inefficient operator habits. In a brief experience in a pharmaceutical plant, spurious alarms have been reduced by approximately 30% and smoother operation procedures have been implemented.08/28/2008
Batch Best Practices and Strategic Automation Helping Smaller Companies to Better Business Performance
With the introduction of S88.01, the impending introduction of S88.00.02 and the drive to automate batch production from the transmitter to the corporate offices, the time has never been better for the small to medium size batch processing companies to benefit from the best practices of the best-in-class companies. This paper discusses and gives examples of an approach which aims to match the automation requirements of a batch site with its business drivers. The procedure starts with a comparative analysis of the batch best practices of a site with those of best-in-class sites, in areas such as technology and the application of standards. It also compares the often overlooked, but very important "soft items" such as skills and management practices. A differential analysis then shows the areas where most focus will bring the best results. Finally a strategic automation plan is developed, with the involvement of the site, to deliver the best balance of technology, organization and skills for the most effective business performance.08/28/2008
ABB Automation has adopted elements of object-oriented analysis and design in their batch control projects in order to take advantage of the reuse potential inherent in the ISA S88.01 model. Here are some architectural and process tradeoffs that anyone should consider before doing their first project: 1) Define modules at a level of granularity that optimizes reuse without obscuring the process. 2) Be prepared to manage significantly smaller and more numerous modules as compared with traditional procedural decomposition. 3) Give careful attention to module interfaces and communications between modules. 4) Begin with solution patterns that have proven to work in the real world. 5) Think beyond code reuse to design and test documentation reuse for quicker payback. The goals of this paper are: 1) provide a common perspective and terminology for discussions on application reuse, 2) discuss examples of object-oriented analysis and design in batch control and 3) show how most batch control products can be made to support this model, even if they do not utilize object-oriented application languages.08/28/2008
This paper reviews the information requirements throughout the development lifecycle across different sectors of the batch industries. It then discusses the challenges facing software seeking to enable smarter working through this lifecycle. Aspects considered include the creation, analysis, manipulation and retrieval of process information in ways that enable more effective decision support, eliminate transcription and work cooperatively allowing users to choose the right tool at the right time. Some of the issues addressed are: Uncertainty and data quality/rigor Risk vs. consequences including the business context Resource constraints addressing what should we do next? Multi-disciplinary synergies and frictions (especially chemist & chemical engineer) Supporting/competing standards where does ISA/S88 fit? The differing needs of simulation, design and recipe execution systems Benefits from an effective IT environment are discussed covering both tactical (direct cost and time savings) and strategic (picking the winners, time to market, more efficient, robust and flexible processes) benefits. The paper draws conclusions regarding the classes of software needed, the essential nature of fully supporting information sharing, the impact of existing and developing standards, the current state of the art available and some ideas on how the future might look.08/28/2008
The integration of scheduling and control systems invariably involves custom programming or the use of proprietary formats to enable the transfer of production schedules. Currently there are two ISA standards committees developing standard schedule formats. The ISA SP88 committee's S88.02 draft 14 presents a batch schedule object model and a set of relational database tables for the exchange of schedule data. At the time this paper was written the ISA SP95 committee was finishing work on the S95.01 Enterprise/Control Integration standard1. S95.01 defines a production schedule object model. The SP95 committee is continuing work on this model as part of the S95.02 development effort. The committee is expected to develop attributes for the objects. This paper analyzes the two committee's work and proposes a mapping between the different sets of work. The mapping shows how the S88.02 schedule object model and exchange tables can fit into the S95.01 production schedule model and the on-going S95.02 work.08/28/2008
During the last several years, the ISA Batch Standard (S88.01) has become a commonly understood way of communicating batch system requirements. Traditional batch manufacturing industries such as Food and Beverage, Consumer Products and Pharmaceuticals have realized the benefits of this model. However, non-traditional batch manufacturing applications such as Pulp and Paper, Steel and Plastics can also realize significant productivity benefits by applying the S88.01 model. This paper examines some of these "non-traditional" batch manufacturing applications and outlines the benefits that S88.01 can provide. It also provides a discussion of the usefulness of batch standard terminology for these nontraditional applications. In some instances, the use of actual terminology provides real benefit to the manufacturing process; in others, the application of the standard in principle only is the most appropriate and beneficial.08/28/2008
The ISA S88.01 Standard for Batch Control, Part 1: Models and Terminology has had a significant impact on the implementation of industrial control systems since its inception in the early 1990s. One need only examine all the batch management products available in todays marketplace to recognize the affect S88 has had in standardizing the look and feel of batch applications. While the terms and structures used to describe batch applications are now generally well understood, many users still struggle with the complexities associated with actually building batch control systems. This paper addresses one approach to the how of implementing S88. It presents a proven software development methodology that takes the beast out of batch, and allows users to realize many additional benefits by applying the S88 Standard.08/28/2008