Print Glossary FAQs
Case Studies Resources

send to a friend

GEMI Contact Info:

1155 15th Street, NW
Suite 500
Washington, DC 20005
Phone: 202-296-7449
Fax: 202-296-7442

About GEMI

Printer Friendly Page          
Pilot Implementation


Pilot Implementation refers to field-testing a HSE-MIS application (either off-the-shelf or custom developed) prior to broader implementation. Pilot projects can help staff at all levels identify flaws, potential problems, and areas requiring modification early in the process. Any resources required for Pilot Implementation are generally deemed well-spent since rectifying problems at a later stage can be much more costly. In addition, Pilot Implementation provides another way to secure user buy-in.

 Key Concepts  
  • Limit the scope of the Pilot Implementation, but ensure that the scope is representative of the larger scale implementation. 
  • Pilot Implementation is a good time to test historical data loading in accordance with the HSE-MIS Plan.  
  • Consistent data generation and entry will help ensure meaningful reports, trends, and metrics, allowing information to be compared and providing the ability to determine best practices.   
 Practical Advice  
  • Use real data to the fullest extent possible in the Pilot Implementation phase. This ensures that users are focusing on the application itself and not on the validity of test data.
  • Consider a phased approach to implementation. This is not the final step in meeting the objectives. The initial roll-out of the application may be most successful if it is limited in scope.  
  • Be prepared to address user concerns about additional requirements or modifications that are not in the HSE-MIS Plan. Manage these within the change management process.
  • Consider the formation of implementation teams that develop data generation and entry protocols for each site/facility to use. The protocols should establish how much flexibility will be allowed and enforced when data is generated or entered. For example, system generates "incident" vs. "injury," "spill" vs. "release," or a user enters "fifty" vs. "50". This is very important. 
  • Use trainers experienced with software roll-outs. These people will be better equipped to deal with user concerns.

  • Provide a balanced and tailored approach to Training before and during Pilot Implementation.

  Case Studies  


About Contact Us Site Map Credits Disclaimer
All contents © GEMI Inc., All Rights Reserved.