Perspectives on Enterprise Planning
Best Practices

The Impact of Forecasting Improvement on Return on Shareholder Value
John T. Mentzer; Journal of Business Forecasting

Improving Salesforce Forecasting
Mark A. Moon and John T. Mentzer; Journal of Business Forecasting

Benchmarking Sales Forecasting Management
John T. Mentzer, Carol C. Bienstock, and Kenneth B. Kahn; Business Horizons


Conferences & Events

Forecasting and Consensus Planning in a Rapidly Changing Environment - Webinar with Christine Pfefferle, Director of Global Demand and Order Management at Tellabs,
June 15, 2005


Sales and Forecasting Management Forum Executive Roundtable,
September 7-9, 2005

The Non-Technical Manager's Guide to Successful System Implementation

By Bichalu Narasimmaraj, Senior Software Engineer at Steelwedge Software
In the post bubble economy companies expect all departments, especially IT, to do more for less. With reduced budgets and manpower, IT has been squeezed between a rock and a hard place. When systems fail, either because they lack a champion or support from the users, they fall in the lap of a reluctant IT Department, which ends up maintaining the decrepit systems that they do not want to support in the first place. The end result is frustrated users and finger pointing. And, IT is often blamed for the inefficiencies and failures of other departments.

This article examines some common pain points of deploying and maintaining an Enterprise system, and provides the non-technical manager with a set of key questions for uncovering potential hick-ups in implementing (or evaluating) a new system.

Hardware

Even though IT usually excels in adding hardware to their environment it is nearly always time consuming-- getting a specification for the hardware from the Enterprise System vendor, internal authorization and placing orders, implementation and integration. There will be at least few rounds of consulting/working with the Enterprise system vendor and the hardware vendors. Although somewhat more expensive at first glance, custom ordered hardware is easier and faster to install than hardware assembled with parts from several vendors.

The storage needs of the Enterprise System also need to be worked out with the vendor and setup properly to get the maximum through put performance. Having an inadequate or unreliable storage system may put the project implementation schedule in jeopardy.

Network requirements also need to be assessed, but this is not usually a bottleneck with the advent of gigabit networks. Another consideration that is usually missed in the requirements phase is the potential upgrades of hardware to the user desktops which may be necessitated because of the Enterprise System’s user interface requirements. Usually processing power (CPU) or the memory (DRAM) need to be upgraded to meet the needs.

Manager's Questions:
  • What hardware does the vendor recommend?
  • Do we support this? (If not, what alternate solutions can be deployed?)
  • What storage system is recommended? What is the through-put?
  • What network requirements does the vendor recommend? Does it scale with upgrades?
Infrastructure/Base Software

The infrastructure software required by the Enterprise System involves an Operating System, Applications/Web Server, Database Server (RDBMS), Web Browser and Office Automation Tools. The following software characteristics are desirable:
  • The fewer software licenses required the better since the software purchase and maintenance drains IT resources.
  • The software is the de facto industry standard in its class or it is widely used by users around the globe.
  • The software is well supported by the ISV/VAR and maintained.
  • The software is easily upgradeable without much downtime of the server.
Even though frequent software revisions are appreciated, a more stable and reliable software is favored by users, unless there are several required features in the upgrade.

Manager's Questions:
  • What infrastructure software does the vendor recommend?
  • Do we support these?
  • If not, can the application work with our standard infrastructure?
Project Implementation

Project implementation involves several critical phases-- Planning, Design, Build and Test, Integrated Test and Go-live. Each step needs to be executed within the required schedule. Some missteps can be taken in to account and maneuvered in the implementation schedule, but a protracted implementation will give rise to cynicism and loss of confidence among potential users.

Although most of the key requirements are identified and included in the project timeline, there will always be some that are included in the schedule in the last phases. This requires that the implementation is repeated accurately and reliably. Even though faster implementation is desirable, users will rather wait for a system without many defects than a buggy software implementation.

Manager's Questions:
  • What are the key implementation risks?
  • Is the build process repeatable?
  • How soon after project kick-off will we see the first build? What will it contain?
  • Who owns the build process?
Data Identification, Preparation and Integration

One of the most important jobs for IT is to keep and maintain the data on which the business users depend. Even though IT is not typically the owner of the data, most of the time they are responsible for it.

The Enterprise System owners need to identify the sources of the business data in the IT Systems. Since the data may be residing in disparate systems, it needs to be extracted from the sources or host systems, transformed and loaded in to a target system. This process is called (need to spell out name e.g. Enterprise Transfer Locator (ETL.) The data then need to be imported in to the Enterprise System. This process is tedious so exceptions and errors during the ETL/Import process need to be minimal in order to be useful in the Enterprise System. The error or exception conditions need to be identified and logged, so that IT or the System Administration user can go through them and correct the problems in the data.

In order to reflect the changing business conditions, this process needs to be repeated on a recurring basis either daily, weekly or monthly. Hence it is better that these processes are automated with no manual intervention by IT personnel.

Manager's Questions:
  • Where does source data come from?
  • How are they transferred into the new system? At what intervals?
  • Where and how are exceptions trapped and handled? How are exceptions reported?
Security

Security has become more important due to proliferation of the business sensitive data being maintained by IT. The users need to be authenticated and authorized to access the data. This involves maintaining users, groups and user passwords in a directory server. There are several directory servers available in the market, The industry standard directory servers are:
  • LDAP Server (several vendors)
  • Active Directory Server (Microsoft)
The directory servers maintain users and groups for the whole enterprise so the Enterprise System will be able to integrate with the company directory services. The integration may require creating additional groups or directory attributes to the users/groups. Stand-alone or embedded directory servers for the use the Enterprise System are not recommended because this will involve maintaining separate users/groups in addition to the company wide directory services.

Any data which need to be sent or received outside the firewall by the Enterprise System should be encrypted with a strong encryption/decryption protocol. The system should also allow virus propagation by the use of email/SMTP protocol.

Manager's Questions:
  • What directory servers does the vendor support? Do they support ours?
  • Does the system work outside the firewall? If so, is the system properly encrypted?
  • Does the system offer off-line capabilities? If so, how does it sync with the online system?
Deployment

The Enterprise system vendor should be involved actively when deploying the system in the IT infrastructure. This can be accomplished either by manually installing the system or using the industry standard install software with use of configurations options at the right places. It is always better to deploy the system in a development environment and take it for test ride before deploying it in production systems. Key business users should test out the system to debug configuration and other mistakes. During the development testing phase, training of the key and administration users should take place in order to build internal support for the use of the Enterprise System.

Manager's Questions:
  • What is the deployment plan?
  • How do we migrate the system into production?
  • What is the training plan?
Going Live

Once the system has been debugged in a development environment, the system can then be installed and configured in the production system. The owner of the system in consultation with the users needs to decide the date on which the system will be used for real. Sometimes the system will be used in a testing mode in the production system for sometime if there is some internal resistance or apprehension about the new system. Obviously, no new surprises from the operation of the system are expected.

Manager's Questions:
  • How do we go live? Is it a “big bang” or a planned phase-in?
Support/Problem Resolution/Patch management

If surprises do appear, the vendor should be able to fix them as soon as possible. This will quell any doubts about the system/vendors capability to solve the problems. But in order for the vendor to solve the problems in a production system, the following steps are necessary:
  • Diagnostic information: The diagnostic information provides the clues to the problem at hand. It can be collected from logs of the system or from attaching a debugger and stepping through the problem code area. Sometimes all that is needed is simple explanation of the problem.
  • Analysis/Diagnosis: Analysis of a problem often involves going through the system log and finding the problem code or data.
  • Fix: Fix involves correcting a problem so that the system behaves as functionally defined or agreed.
  • Patch: Replacing the problem code or data with the corrected code or data involves usually stopping the system and copying some code or data files. Sometimes the patch can be applied without shutting down.
  • Faster response: Obviously the quicker the response from the vendor will allow the users to keep using the system without a functionality or a wrong behavior. Sometimes the patch may take longer than expected depending on the complexity of the software.
Manager's Questions:
  • How do we deploy patches and upgrades?
  • How is this process managed?
Upgrading the System

When the vendor releases a newer version of the software, it should be provided with upgrade software tools that make sure the old version of the software is replaced with the new version without losing the data and configurations of the current system. The smaller the downtime of the system, the better it is. It is better to backup the data and the old software before applying the new version.

Manager's Questions:
  • How do we ensure that no data is lost when we upgrade?
  • What is the expected downtime during an upgrade?
  • Do we have all the necessary tools for upgrading?
IT Personnel Technical Knowledge Requirements

The technical skills of the IT personnel need to be current with respect to the infrastructure software used by the system. If the software necessitates training, then it is a drain in the IT budget and time. The vendor also needs to train the IT personnel in administering and maintaining the system. Usually the training is free or the price is negotiated in the purchase contract. The amount of time spent by the IT on maintaining the system is also important.

Manager's Questions:
  • What additional skills does our IT organization need to support this system?
  • How much time is spent by for maintaining the system?
Clearly, the above pain-points and related questions are no guarantee that a new system will be successful. But success is in large part dependent on early identification and proactive management. The above pointers is a start to that end.. Good luck!

About the Author

Bichalu Narasimmaraj is a Senior Software Engineer at Steelwedge Software. Prior to Steelwedge he had been with Enterprise Software companies Panscopic Corp, Actuate Inc, Scopus Technology and Informix Inc in senior level engineering positions. He is certified in Production and Inventory Management(CPIM) from APICS. He holds a Masters Degree from Indian Institute of Technology, Madras, India.




3825 Hopyard, Suite 155, Pleasanton, CA 94588
Perspectives on Enterprise Planning is an electronic newsletter highlighting issues and trends in forecasting and planning at high-tech and industrial manufacturers. You are welcome to forward this newsletter to other business partners and associates with an interest in demand management. Published by STEELWEDGE, Inc., the leading innovator in the field of Enterprise Demand Management. For more information about STEELWEDGE, go to http://www.steelwedge.com/.
Copyright 2005 STEELWEDGE, Inc. All rights reserved.
 
Contact us