During the Deploy (or adaptation) phase, the implementation team installs iHRIS and customizes it to meet the system requirements. It is unlikely that iHRIS as installed will fulfill the requirements decided upon by the SLG. iHRIS has been designed to be easily customized by modifying fields, forms, and modules, or even programming new modules, if necessary.
While iHRIS is being installed, customized, and tested, consult the system requirements frequently. Often the unexpected occurs, and changes must be made to the requirements. It is important to document these changes by updating the requirements and noting what updates have been made.
The deliverable of this stage is production code, a version of iHRIS that fulfills the SLG’s requirements and is ready to use. The production code should be deployed on a dedicated server that has proper backups, uninterruptible power supply (UPS), and line conditioners installed. Do not edit any of the source code on the production server; instead pull in committed, tested code from the source code repository.
In addition to production code, you should maintain development code, a version of iHRIS that will continue to be customized as new needs emerge. The development code typically exists in two places: on the software developer’s computer or laptop, from which the developer commits changes to the source code repository; and on a testing server, where the committed code can be reviewed to ensure that the requested functionality is met.
Don’t neglect the SLG during this phase. Set a regular meeting schedule to establish roles and responsibilities and address issues that will arise. Since this group will oversee iHRIS throughout its operation—not only during the implementation phase, but well beyond—now is a good time to put in place standard operating procedures to ensure efficient operation of the SLG.
Objectives and Deliverables
Document any standard operating procedures that exist or have been decided on by the SLG.
Monitor whether customizations to iHRIS conform to the system requirements. Test the software with users or stakeholders to determine if the customizations meet expectations. If a change to the requirements is needed, log the change and the reason for it.
Software & Systems
Download, install, set up, and customize the iHRIS software.
Data Quality & Standards
Customize fields, forms, and modules in iHRIS according to the agreed-upon data standards.
Data Sharing & Interoperability
If existing data are available in electronic format, you may choose to import the data into iHRIS during this phase. Before importing, convert data to standardized data lists [ref to Tool1-D]. Otherwise, collect and enter initial data during the Pilot phase, after ensuring that data collection tools report according to the standardized data lists. See iHRIS Technical Documentation for instructions on how to import and store data in iHRIS.
Data Use & Reporting
Customize reports based on the reporting requirements. Produce sample reports for testing. Engage with the SLG early on the report templates. See iHRIS Technical Documentation for instructions on how to customize reports.
Training & Support
Develop and implement a program for training ICT staff on administering iHRIS. Plan for how ongoing support of iHRIS will be provided, including needed skills updates.
By the end of this phase, you should have two code branches of iHRIS: a production branch and a development branch. We recommend that you publish the code on Launchpad, the hosting site for all of the iHRIS code branches. See iHRIS documentation [above] for instructions on how to manage a site on Launchpad.
Key questions to answer before continuing:
- Does iHRIS meet the system requirements?
- Have all operability, customization, and systematic issues been identified and corrected?
- If there were changes to the requirements, have they been approved by the stakeholders?