Planning Cuts Automation Project Risk

System integrators share tips on how avoiding surprises helps them succeed. Clear communications and documentation top the list. Tools follow for project management.

09/01/2009


Risk reduction is often cited as one of the primary benefits of hiring a system integrator for an automation project. After all, experienced practitioners in any technical discipline are generally more successful than enthusiastic amateurs, and system integrators are the subject matter experts when it comes to designing and installing industrial automation systems. But even the most talented system integrators can't make an automation system work properly without knowing what it's supposed to do.

 

"Identifying and recording the end user's requirements is the single largest factor in defining a project's success," says Dean Streck, chief operating officer of VI Engineering. "We tell our people who are doing project-based work every day that they must clearly define what they are going to do — in writing — before starting and also document how they are going to prove that they have met those requirements."

 

V-model project development methodology was originally formulated by the Good Automated Manufacturing Practice (GAMP) Forum and has been incorporated into the Best Practices of the Control System Integrator Assoication. Left half of the V shows the planning required for each testing step shown on the right half of the V.

V-model project development methodology was originally formulated by the Good Automated Manufacturing Practice (GAMP) Forum and has been incorporated into the Best Practices of the Control System Integrator Association. Left half of the V shows the planning required for each testing step shown on the right half of the V.

Brent Stromwall, vice president of Polytron agrees. "A clearly stated project and communications plan are essential to ensuring that the integrator and the client's stakeholders agree what 'success' and 'done' look like."

 

After all, says Jerry Armstrong, applications engineer at Walco, "there is nothing that will deflate a customer's confidence faster than an after-the-order-is-given statement such as, 'I didn't know that was part of your requirements.' The salesman or application engineer that is responsible for quoting the job must spend an adequate amount of time with the customer and the equipment to find out exactly what it is that the customer wants, and have a good idea of how how it is to be accomplished. This doesn't mean he needs to go into minute details such as the color of pushbuttons, but all major factors and the extent of the project must be defined."

 

Armstrong adds, "Having done our homework correctly, there will be fewer surprises when it comes to physically implementing the system."

 

Don Ulrich, president of Stone Technologies, agrees that making a plan and assessing the risks are key to the success of any automation project. "We tell clients up front how we're going to do the project in infinite detail. That becomes the basis for the contractual details and setting expectations. We then go through a complete risk analysis — schedule risks, technology risks, resource risks, even the risk of clients not providing the information we need in a timely manner.

 

"As we go through the project and have reviews, we revisit the risk question because new risks pop up that we didn't think of initially. The risks we can foresee we address aggressively. It's the risks that we assume aren't a big deal that cause us the most trouble."

 

System integrators can reduce their own risk by deciding which automation projects to accept based on how much they knkow about the prospective clients and the required technology. If both are well-known, the project should go well. If both are unfamiliar, the integrator

System integrators can reduce their own risk by deciding which automation projects to accept based on how much they knkow about the prospective clients and the required technology. If both are well-known, the project should go well. If both are unfamiliar, the integrator's risk is highest. If one or the other is unknown, it's time to expand into the unfamiliar territory.

Joel Langill, senior consultant and staff engineer at ENGlobal Automation, agrees. "These risks can be technology risks such as what would be involved when implementing a new system or a new release of software. Or they can be risks to the client's operations, such as how they will successfully migrate their operator stations from an older to a newer technology, and at the same time move to a consolidated control building."

 

He adds, "Any risks unique to the project should be documented and discussed. Once these risks are understood, specific activities should be amended to the test procedures to demonstrate success and essentially mitigate these risks before the project shifts to the field."

 

And when it comes to planning those tests, Langill prefers to start from the end. He develops the final testing, site commissioning and site cutover plans up front, then designs the rest of the project with those tests in mind.

 

"One of the most common mistakes in projects that are large, complex or that involve integration with numerous automation components is that the final tests are not developed until just before it's time to run them," Langhill notes. "This often results in a test plan that either fails to test all aspects of the automation solution or masks known problems, leaving them to be found during costly site activities."

 

Dan Purvis, senior systems engineer and general manager for the Houston office of Optimation, describes how his company creates their test plans from the project's design documents using the V-model diagram shown in the "Project development methodology" figure. Not surprisingly, the process starts with the end users' requirements. The three phases of the testing process follow from the three documents shown in the figure.

 

"On the back end of the V you get a series of items that naturally happen because the hard work of the project has already been accomplished on the front end," says Purvis. The final site acceptance test corresponds to the user requirements, the factory acceptance test corresponds to the functional requirements, and the system documentation corresponds to the design specifications. In between comes the actual implementation of the project — writing, integrating, and testing the software.

 

Purvis adds, "Programmers and operators manuals fall right out from the design and architecture documents in the design phase. The factory acceptance testing (FAT) happens naturally from the FRS (functional requirements specification) and FAT test documents. You run through the FAT and answer the questions. Any nonconformities create punch lists for rework, but the number of surprises is minimized."

 

Stone Technologies' Ulrich cites "no surprises" as Rule #1 for planning and managing a project. After all, he says, integrators can't manage what they don't know. Rule #2 is "I-can-fix-that-later does not constitute a plan." Ulrich says clients much prefer to hear that there's a problem as soon as it comes up, especially if the bad news comes with a new plan to fix the problem.

 

Ray Bachelor, president of system integrator Bachelor Controls, elaborates on the project management issue: "Project management is not just reporting the news. Project managers are supposed to manage the project to ensure that it remains true to the original functional requirements. They should have a realistic schedule to begin with, rather than such an optimistic schedule that slips become inevitable."

 

 

 

ONLINE

 

www.viengineering.com

 

www.polytron.com

 

www.walcokip.com

 

www.stonetek.com

 

www.englobal.com

 

www.opimation.us

 

www.bachelorcontrols.com

 

www.matrixti.com

 

 

 

www.controleng.com

 

 

Author Information

Vance VanDoren is contributing editor for Control Engineering. For a detailed example of how the V diagram might be applied to the development of a specific automation project, view this article online at www.controleng.com/archives .

 



No comments
The Top Plant program honors outstanding manufacturing facilities in North America. View the 2013 Top Plant.
The Product of the Year program recognizes products newly released in the manufacturing industries.
The Engineering Leaders Under 40 program identifies and gives recognition to young engineers who...
The true cost of lubrication: Three keys to consider when evaluating oils; Plant Engineering Lubrication Guide; 11 ways to protect bearing assets; Is lubrication part of your KPIs?
Contract maintenance: 5 ways to keep things humming while keeping an eye on costs; Pneumatic systems; Energy monitoring; The sixth 'S' is safety
Transport your data: Supply chain information critical to operational excellence; High-voltage faults; Portable cooling; Safety automation isn't automatic
Case Study Database

Case Study Database

Get more exposure for your case study by uploading it to the Plant Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.

These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.

Click here to visit the Case Study Database and upload your case study.

Maintaining low data center PUE; Using eco mode in UPS systems; Commissioning electrical and power systems; Exploring dc power distribution alternatives
Synchronizing industrial Ethernet networks; Selecting protocol conversion gateways; Integrating HMIs with PLCs and PACs
Why manufacturers need to see energy in a different light: Current approaches to energy management yield quick savings, but leave plant managers searching for ways of improving on those early gains.

Annual Salary Survey

Participate in the 2013 Salary Survey

In a year when manufacturing continued to lead the economic rebound, it makes sense that plant manager bonuses rebounded. Plant Engineering’s annual Salary Survey shows both wages and bonuses rose in 2012 after a retreat the year before.

Average salary across all job titles for plant floor management rose 3.5% to $95,446, and bonus compensation jumped to $15,162, a 4.2% increase from the 2010 level and double the 2011 total, which showed a sharp drop in bonus.

2012 Salary Survey Analysis

2012 Salary Survey Results

Maintenance and reliability tips and best practices from the maintenance and reliability coaches at Allied Reliability Group.
The One Voice for Manufacturing blog reports on federal public policy issues impacting the manufacturing sector. One Voice is a joint effort by the National Tooling and Machining...
The Society for Maintenance and Reliability Professionals an organization devoted...
Join this ongoing discussion of machine guarding topics, including solutions assessments, regulatory compliance, gap analysis...
IMS Research, recently acquired by IHS Inc., is a leading independent supplier of market research and consultancy to the global electronics industry.
Maintenance is not optional in manufacturing. It’s a profit center, driving productivity and uptime while reducing overall repair costs.
The Lachance on CMMS blog is about current maintenance topics. Blogger Paul Lachance is president and chief technology officer for Smartware Group.