Agile Automation

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Agile Automation refers to the application of select Agile software development principles, patterns and practices, to the area of industrial automation and process control software development. The term was first coined by HAL Software (Ireland) in 2013.

Traditionally, Industrial Automation Software has been developed using languages that do not fully implement OOP. Software development lifecycle is in line with the Waterfall model, For example the GxP (Good Automated manufacturing practice) V model that is pervasive throughout the pharmaceutical regulated industries. There was a growing belief however, that the model was too rigid, did not allow for sufficient change throughout the software development lifecycle and did not target testing according to risk . The latest version of the GxP model went some way towards testing based on risk assessment.

The latest GxP model advocates testing and documenting according to perceived risk to the end user. (The patient, in the case of the Pharmaceutical industry).

In fact the GAMP5 guide in 2008 explicitly mentioned Agile programming; The approach described in this document is designed to be compatible with a wide range of other models, methods, and schemes, including: Software development methods such as RAD, Agile, RUP, or Extreme programming (GAMP5)[1]

There is debate however over whether Agile methods can truly satisfy regulatory requirements, as outlined in the article on Alternative Software development modals and methods in GxP Environments, by ISAP GMAP D_A_C_H SIG ASDMM. (Pharmaceutical Engineering Jan2012 Vol32 No.1). The Industry has some experience of poorly executed MES Agile software projects and these experiences have tended to reinforce the traditional notion that Waterfall software development lifecycle is the simplest way to enforce Engineering Rigour and budgetary/schedule contraints on a software development team.

Agile Automation software development has the potential to reduce the development lifecycle and at the same time, encompass automated unit testing. Something that the industry is calling for. In addition, the 'don't repeat yourself' aspects of Agile object oriented software development encompassing extension of software classes through interfaces (Software class is open for extension but closed for modification) are very attractive in a regulated industry where software change validation is particularly expensive. Agile software development promotes true object oriented software programming which in turn results in software that is more amenable to change and less likely to break. [2]

The two most widely used strategy design patterns in Pharmaceutical and other Batch Industrial Automation higher level systems (SCADA, Batch and MES ) are ISA S88 & ISA S95. These patterns can be implemented such that the action behaviours (e.g. read / write method or Valve command on/off method) are encapsulated as interfaces using languages such as Microsoft Visual Studio and C#/.NET, or Java/Eclipse environment.[3] Presently, commercial Control System software development is biased towards inheritance and subtyping, and the other OOP tenets (Encapsulation, Polymorphism) are not exposed to the programmer to the same extent. This incomplete OOP implementation increases the amount of design effort required. Even Commercial Proprietary DCS systems such as Emerson DeltaV are biased towards subtyping and inheritance without an easy way to implement a behaviour through an interface or similar construct (There is no way to implement multiple inheritance)

The IEC 61131-3 programming language is the most widely used language for programming PLC & DCS systems. It is not a truly object oriented language, implementing only 1 tenet of OOP (inheritance/subtyping) and not encapsulation or polymorphism. This limits its amenability to automated unit testing and encapsulating of behaviours for class extension.

Generally there is less scope for encapsulating behaviours in most industrial controllers except for platforms that run a more advanced operating system (for example the Beckhoff Twincat platform) that can be programmed via high level IDEs such as visual studio .

There is a replacement standard (IEC 61499)that is more object oriented, but Industry uptake is presently small . There are moves towards IEC61131-3 consolidation, notably through the PLCOpen standard. This approach to developing an abstract XML class can result in a library of tested class modules/types that can subsequently be instanced and imported to target platform.

Interest is growing in model driven architecture (MDA) Agile programming whereby a platform independent model is first developed. As a result of regulatory filing requirements and the need to protect against litigation, the Pharmaceutical industry records and saves data that must be reconstituted for subsequent filing submittal or Batch release (Electronic batch records). A model developed in the pilot lab and used as the guideline for manufacturing scale up, can aid filing submittal.[4][5][6]

References[edit]

  1. ^ http://www.ispe.org
  2. ^ 12JF-Hambloch_GAMP.pdf - Alternative Software development models and methods in GxP environments (reprinted from pharmaceutical engineering)
  3. ^ http://www.isa.org
  4. ^ Bringing new products to market faster - (Adam Fermier, Paul McKenzie, Terry Murphy, Leif Poulsen, Gene Schaefer) ISPE 2012
  5. ^ 'Design and optimisation of a large scale biopharmaceutical facility using process simulation and scheduling tools' Pharmaceutical engineering 2010 Vol 30 No2
  6. ^ agile principles, patterns and practices in c# - Robert C. MArtin