October 4 Implementation Chronicles Update
This week we learn what the definition of “done” is when referring to portions of an integration project. According to blogger John Sever, Cascade Controls has developed specific terminology surrounding the completeness of project assignments to avoid communication errors. Meanwhile, the Baton Rouge wastewater SCADA project is getting back on track as discussions relating to Phase I rebids get underway and agreements are established pertaining to the use of Ethernet as the preferred communication architecture for the project.
Wastewater SCADA project
Last week, chance meetings with maintenance personnel reviewing the
Phase II drawings indicated that there were numerous scope and technical
issues to be resolved. Left unaddressed, QDS could find itself in a
position that, no matter how well it performed on the contract, the city
would be unhappy.
To address this problem, QDS helped the city develop a punch list of concerns.
Discussion of the rebid of Phase I and this list became the agenda for QDS’s
meeting with city maintenance personnel and the primary engineering consultant.
During this meeting, it was agreed that employing standard Ethernet communications is the preferred architecture. The primary consultant expressed a strong
preference for RTU and local HMI units to be selected from among the major PLC
manufacturers, for reasons of reliability and support. Blogger Stan Prutz says that, in his experience, a large installed base is the most important barometer of future hardware support.
Biopharmaceutical filtration automation project
The microfiltration (MF) system PLC control code—IO, control modules, interlocks, and equipment modules—is “code complete.” If you’re not familiar with this term, it is because Cascade Controls has developed its own terminology to describe different levels of completion. Too often when someone says they are 'done,' there is still more work to do. To avoid this type of communication error, Cascade Controls developed and defined its own terms for qualifying degrees of done-ness. These are borrowed terms that have been defined to match normal project execution methodology.
Once Beta Testing is complete and the code is known to pass all test procedures, it is made available for formal testing either by the customer or under supervision by the customer. This stage is called by different names based upon the customer's nomenclature including Factory Acceptance Test (FAT), Customer Acceptance Test (CAT), or Development Test (DT).