Planning Ahead for IT Upgrades Key for Reducing Stress

IT upgrades need not be an overwhelming or chaos-inducing process as long as you plan ahead for them, according to industry experts. Two of the methods they discussed were prototyping and a service-based qualification approach to network services.

Companies often fail to develop prototypes of IT systems due to the mistaken notion that the process is expensive, time-consuming and unnecessary, and the result will be "thrown away," said Dawn Marruchella, principal engineer, Emerson Process Management. In reality, she said, "we've seen again and again that prototyping reduces surprises." Specifically, prototyping makes it possible to:

Incorporate your guiding principles into the foundations of the new or upgraded IT system. "A prototype allows you to demonstrate, argue about and agree on the fundamental philosophy for the project," said Marruchella; Ensure a consistent look and feel to the new system; Introduce the new system to the manufacturing, operations, process and maintenance departments; and "Demonstrate methods for software testing, operator training and process simulation."

The first step is deciding which functions should be prototyped, said Marruchella who was speaking in March at the Interphex conference in New York. Select an area (probably not the most complicated or the simplest) whose functional requirements are defined and where technical resources are available, she said. But pick one whose scope isn't going to be eliminated from the entire project. She gave as examples such "core functions" as handshaking, messaging, specific data requirements and interfaces with external systems.

Prototype developers should not overlook the graphic user interface, Marruchella said. "This is what the operator sees; make sure it is easy and pleasant to use." Equipment modules must also be considered, she added: "Are these just for batch operations, or will [individual] operators use them as well?" Developers must also take into account disaster recovery scenarios, protocols on equipment allocation, and documentation requirements, even though the latter are completed only after the prototype is ready.

When the prototype is done, meet with automation-specific stakeholders first, and then with others who will be affected, Marruchella said. "If there is feedback, include it before you take it to management." Far from throwing the prototype away, developers should keep a copy "so you always have it to go back to as you go through the project," said Marruchella.

Like prototyping, a service-based approach to network qualification requires as the first step that those responsible decide specifically what will be the focus of attention. A step-by-step approach to validating the entire network "is impossible because the network is already up and people are using it," noted Nagesh Nama, president of ValiMation. Instead, he said, the IT manager should "break the network down into services, launch a focused qualification effort for each service, and treat each service as an independent entity that is qualified with the network design objectives in mind." These objectives should include availability, scalability, manageability, security, agility and performance, he said. It is vital to ensure that the network uses standardized components.

Best Practice in Service Qualifications

Best practice does not require that each service be requalified all the time, Nama said. Moreover, it is pointless to try to mount a qualification effort "so complex you won't be able to complete it." On the other hand, he noted, for disaster recovery it is advisable to test backup systems periodically to make sure they will actually work in the aftermath of a real emergency. "If it worked a year ago, it won't necessarily work now. [Storage media] may not have been stored properly or may have become corrupt, so it must be tested on an ongoing basis." Physical security and fire prevention should not be neglected either, he said.

The two basic choices for network qualification are a "retrospective model" or an "accretive model," Nama said. The latter approach more closely approximates Marruchella's emphasis on prototyping. "Build a prototype of your network -- a mini-network that kind of represents your production network. Then qualify each service on it," said Nama. He added that this approach dovetails with IT best practices as developed by Microsoft, Hewlett Packard and other IT giants.

In the end, the most important aspect of network qualification is data protection, Nama said. IT managers must know how critical data are stored, backed up and transported through the network. Data protection is a component of good manufacturing practices and regulatory compliance, as well as business success. -- Martin Gidron (mailto:mgidron@fdanews.com)