/
Modular Implementation plan for HIB

Modular Implementation plan for HIB

Status

Draft plan

Phase

Title

Objective

Key Actions & Guidelines

 

0

Pre-Implementation Check

Ensure technical readiness before user transition.

  • Verify MSSQL data mapping between legacy and modular systems.

  • Complete data migration verification.

  • Technical team evaluates and optimizes system scalability.

Completion

1

Dual Deployment

Introduce the modular version to the live environment safely.

  • Deploy the modular version alongside the legacy system.

 

  • Allow both systems to run side-by-side to monitor live environment stability without disrupting daily operations.

Complete

(waiting update from HIB)

2

User Acceptance Testing (UAT)

Validate usability, workflow efficiency, and accuracy.

  • Appoint designated users from provincial and district levels.

 

  • Test real-world scenarios and identify UI/UX friction points.

 

  • Gather structured feedback on the modular workflow.

UAT at HIB
UAT at provincial / district level

3

Resolution & Training

Address UAT feedback and prepare users for the transition.

  • Bug Fixing: Resolve all technical issues, mapping errors, and workflow bugs identified during UAT.

 

  • Training: Organize comprehensive training sessions focusing on the new interface and workflow changes.

Complete

4

Regional Pilot

Test operational parity in a controlled, live environment.

  • Initiate a phase-wise pilot, starting with one designated region.

 

  • Parallel Running: Utilize both legacy (for basic operations) and modular systems to ensure both function properly simultaneously.

 

  • Expand the pilot to subsequent regions one by one upon successful acceptance.

Complete

5

Legacy Phase-Out & Full Rollout

Fully transition all operations to the modular system.

  • Trigger this phase only when every targeted region has successfully completed its pilot.

 

  • Decommission and phase out the legacy system.

 

  • Transition all daily operations exclusively to the OpenIMIS modular version.

Complete

UAT Feedback Checklist for Provincial & District Users

This checklist is designed to help appointed users systematically test the OpenIMIS modular version during Phase 2.

1. System Access & Navigation

  • [ ] Can you log in successfully using your existing credentials?

  • [ ] Are your assigned provincial/district roles and permissions accurately reflected?

  • [ ] Is the main dashboard easy to navigate compared to the legacy system?

  • [ ] Can you easily locate the primary modules you use daily?

2. Core Operational Workflows

  • [ ] Data Entry: Can you successfully register or update a record without errors?

  • [ ] Data Retrieval: When searching for an existing record, does the modular system pull the exact same MSSQL data as the legacy system?

  • [ ] Process Execution: Can you complete a standard daily task (e.g., submitting a claim, verifying a beneficiary) from start to finish?

  • [ ] Reporting: Do the generated reports match the outputs from the legacy system?

3. Performance & Stability

  • [ ] Does the system load pages and records at an acceptable speed?

  • [ ] Did you experience any crashes, freezing, or unexpected error messages?

  • [ ] Note specific actions that caused any lag or errors

4. Overall User Experience (UX)

  • [ ] Is the terminology used in the modular system clear and consistent with your workflow?

  • [ ] Are required fields and error messages clearly highlighted?

  • [ ] Rate the overall usability of the modular system compared to the legacy system? (1-Poor to 5-Excellent)