Ministry Of Health and Child Care (MoHCC) has centralized data management system (GxAlert) for managing data coming from GeneXpert machines. There is another system (Central Data Repository) which manages data from all other platforms. The current setup calls for users to access two independent systems. To close this gap, MOHCC would like to implement an integration layer that is able to communicate seamlessly with different test platform applications (including GeneXpert GxAlert) and push data to the Central Data Repository.

Purposes:

Objectives

Under this consultancy contract, the engaged consultant will be expected to:

1. Prepare (in consultation with MOHCC) a detailed work plan with a training timetable and curriculum, milestones to be achieved and expected outputs for the technical development.
2. To develop an integration layer (API) to facilitate integration of POC data from external systems into the national central data repository. For illustrative purposes, the consultant will integrate data from one external system called GxAlert to the Central Data Repository
3. Develop a UI to monitor API activity including showing integration statistics

Scope of Work

1. Stable and working dashboard meeting the functional requirements outlined above
2. Documentation – Technical and User manuals
3. Activity reports and relevant annexes

Expectations and Features

1. Study and understand the current database structure
2. Develop open ended API for pushing data into the central data repository. This data can be in the form of csv files, excel, json, sql databases and other formats
3. Develop a web based UI for monitoring API activity
4. The system shall be able to show integration statistics

D.   Expected Outputs and Deliverables

1. Accept multiple formats of data and push into central data repository
2. Read and translate data from the source data system into the API
3. Flag API data with a data_source_identifier
4. Syncing should be configurable (stop, start, restart, pause, resume, suspend, etc)
5. Change source/destination IPs and access credentials on the API.

The POC API will be tested through 3 main stages:

i. Study and Implementation Stage

ii. System Stabilization and User Acceptance Test stage

iii. Support and Maintenance Stage

a) Study and Implementation Stage:

1. The consultant will study the service process and any existing system architecture.
2. The consultant will come up with System Requirement Specification (SRS) to develop a good system after consulting with the users/stakeholders. Once the system is developed users will be trained to use and then the system will be piloted.
3. Justified recommendations will be incorporated into the system and then final testing will be carried out before implementation of the system and other relevant solutions.

b) System Stabilization and User Acceptance Test stage.

The individual shall complete the following activities for the period of scheduled months after the delivery sign-off:

1. Dedicated On-site support to the NMRL development team still on board.
2. Preparation of UAT environments.
3. Incorporate all minor and major changes such as changes in database objects and relationships among the objects, system workflows, core modules if required, and other necessary and critical changes which impact the overall working functionalities of the respective line agencies system.
4. Trainings and workshops wherever necessary as desired by the Ministry.

c) Support and Maintenance Stage.

The Consultant shall develop all documentation to allow client to perform all maintenance activities related to the following:

1. Trouble-shooting at both Applications level and User level.
2. Assist the ICT focal person of the agency in operation of the Systems.
3. Solution up-gradation such as installation of patches, fixing bugs, minor changes, higher versions of the applications, etc.
4. Prompt attention to the issues raised by users/stakeholder

d) User Roles

Detailed scope of work to be covered as part of this TOR Document:

1. Study the existing procedure of the various stages of work of different departments at  the Ministry and document it with workflow diagrams and get acceptance of the client.
2. Apply process re-engineering wherever possible and propose TO-BE workflow diagrams. Obtain a user acceptance on the TO-BE workflow diagrams from the client.
3. Prepare Software Requirement Specifications (SRS) or Functional Specifications (FS) document and Software Design document (SDD) for the web-based API system and submit the same along with workflow diagrams.
4. On acceptance of the SRS/FS, design and develop a wire-frame prototype (HTML, CSS based) that is in line with the requirements indicated so that client gets the feel of the system that is being developed and provide necessary feedback on the frontend aspects.
5. On acceptance of the non-functional prototype by NMRL, design and develop an appropriate software package that is in line with the requirements indicated.

e) System Development and Deployment

1. Finalization of Software Requirement Specifications and SRS sign-off based on the Acceptance.
2. Architecture Design for the solution including the Security level Designs.
3. Application development of all the system enhancement requirements.
4. Technical testing of all the components.
5. Submit the test cases and test plans to the NMRL.
6. Trial Run of the enhanced API system.
7. All the Requirement, Design, Configurations and Development methodologies have to be well documented and handed over to NMRL
8. Well commented source codes, database scripts, test scripts, etc. to be handed over to NMRL.
9. The framework for system development should not be obsolete but it should be current and progressive.

f) Training and Capacity Building

1. Full involvement of ICT officials from NMRL to ensure proper transfer of Knowledge in terms of development know-how and sustainability of IT Systems developed as a part of this assignment. (For lifecycle of project)
2. Prepare all the System User Manuals (Both technical and normal user manual) and hand over to NMRL.

g) System Stabilization and UAT

1. Support in terms of System stabilization and making Systems acceptable by the NMRL per agreed period from Project delivery sign-off.
2. Conduct major addition or updating of the system wherever required.
3. Meet all requirement through UAT preparation and UAT sign-off.

1) Modules of system

The system shall have one common page to login for the users listed in the table above.

Only authorized information or data or functions of the system will be accessible.

User registration:

1. The users shall be registered with following information for registration but not limited to:
2. First Name, Last Name, Department/Ministry, email-ID, Contact No, username and password

2) Development Methodology

The vendor should strictly follow a recognized development methodology during the project.

1. The vendor shall carry out assessment on existing list of services and technologies to optimally allocate or determine the product backlogs. It shall also consist of TO-BE workflow.
2. The product backlog must consist of related services or processes of different services to efficiently carry out process re-engineering where possible.
3. The vendor shall carry out user requirement of each process backlog separately and get SRS sign off to initiate the implementation of the first sprint.
4. The vendor shall also get sign off on each test case and present each sprint integrated with GitHub staging environment. This will help in better user acceptance of the system.

Some of the guidelines that need to be followed during the development methodology are:

1. The vendor should identify and provide an account for the project manager in the development management tool (recommended GitHub, Trello)
2. The consultant shall indicate the sprint duration and present periodic reviews.

3) Platform and Technology

1. Development Language: The system development is recommended to be implemented using Open Source Languages framework based on Java, Angular, Liquibase, AMQ services etc.
2. The application is recommended to be implemented using MVC (Model View Controller) based web frameworks since they adequately address protocols and standards including application security and manageability.
3. If the developer has alternative development language proposal, developer may provide the details on the proposed language.
4. Database System: The database for the application are recommended to be implemented using Open Source Database such as MySQL, PostgreSQL, etc.

4) General features:

The proposed System should comply/adhere to following technical requirements/functionalities, but not limited to:

1. Implement data validation for both client and server (e.g.: AJAX technologies, JavaScript, etc.)
2. Don't Repeat Yourself (DRY) principle in coding is recommended

Implement Search, Save, Create, Read, Update, Delete (SCRUD) user operations

1. Adopt Role-Based Access Control (RBAC) to authorize users’ access to system resources based on roles
2. Maintain consistent aesthetics and UI of the software
3. System should be scalable and upgradeable as and when the number of users and content increases
4. Maintain and ensure that the system supports concurrent users;

5) Training (Knowledge Transfer)

The consultant will be responsible for the knowledge transfer on the API through use of adequate documentation and training.

6) Quality of Work

The individual shall ensure quality while implementing the system at all times.

7) Timely Completion

The entire work of software development and testing should be completed within agreed period from the date of award of work.

8) Timelines for the deliverables/outputs

The work will be performed over a period of 20 working days spread over 3-4months.

Expected Deliverables from the Bidder

The lists of deliverables from the selected consultant are as follows:

a) Design

1. High Level Software Design Document including Software Architecture Design,
2. Logical and Physical Database Design (E-R Diagrams) etc.
3. Security Level Design document.

b) Application Developments

1. Well-commented Source Code (Application development) for all systems
2. Test Plans and Test cases (including Unit Test Plan, System/Integration Test Plan, User Acceptance Test Plan, Security Test Plan, Load Test Plan, Regression Test
3. Plan)
4. Unit Testing
5. Load Testing
6. Integration Testing
7. Implementation of Security Policy
8. Testing Documentation (including details of defects/bugs/errors and their resolution)
9. All database scripts.
10. Setup and Release notes for each new release.

c) User Training

1. Training Manuals
2. User Manuals for all the enhanced systems.
3. Systems Administration Manuals – Installation, Maintenance, and MIS reporting for all systems.
4. The Consultant shall provide all other relevant design & documents as may be required to carry out the work as detailed in the scope of work

E.    Institutional Arrangement

1. The IT LIMS Coordinator will review output and confirm acceptance and directly supervise the Contractor, to whom the consultant will be directly responsible to, reporting to, seeking approval/acceptance of output
2. Progress report will be presented at the end of each milestone. There is an option for presenting the report virtually depending on circumstances.
3. The contractor is expected to liaise/interact/collaborate with the LIMS Team during performance of the work for technical guidance

F.    Duration of the Work

1. The work will be performed over a period of 20 working days spread over 3-4 months.
2. MOHCC is expected to review outputs, give comments, and certify approval/acceptance of outputs, etc within 2 weeks. 

G.   Duty Station

1. Training will be conducted at a venue to be determined by MOHCC

Professionalism:

Demonstrates professional competence and mastery of subject matter;

Good research, analytical and problem-solving skills;

Conscientious and efficient in meeting commitments, observing deadlines and achieving results.

Communication:

Excellent and effective written and oral skills; ability to persuade people with varying points of view and to present information in a concise and accurate manner, ability to clearly communicate links between the organizations.

Planning and Organizing:

Proven ability to plan, coordinate and monitor own work and that of others;

Ability to work under pressure and uses time efficiently;

Identifies priority activities and assignments, adjust priorities as required.

Teamwork:

Works collaboratively with colleagues to achieve organizational goals;

Solicits input by valuing ideas and expertise of others and is willing to learn from others

LANGUAGE:

• Fluent in English

1. Scope of Price Proposal and Schedule of Payments

1. Lump Sum Amount is the preferred approach. 
2. The Lump Sum Amount must be “all-inclusive”.

Clearly state that the contract price is fixed

J.     Recommended Presentation of Offer

For purposes of generating Offers whose contents are uniformly presented and to facilitate their comparative analysis, it is best to recommend the preferred contents and presentation of the Offer to be submitted, as well as the format/sequencing of their presentation.  The following documents may be requested:

1. Duly accomplished Letter of Confirmation of Interest and Availability using the template provided by UNDP;
2. Personal CV or P11, indicating all past experience from similar projects, as well as the contact details (email and telephone number) of the Candidate and at least three (3) professional references;
3. Brief description of why the individual considers him/herself as the most suitable for the assignment, and a methodology, if applicable, on how they will approach and complete the assignment. A methodology is recommended for intellectual services, but may be omitted for support services [Note: this is optional for support services];  
4. Financial Proposal that indicates the all-inclusive fixed total contract price, supported by a breakdown of costs, as per template provided.  If an Offeror is employed by an organization/company/institution, and he/she expects his/her employer to charge a management fee in the process of releasing him/her to UNDP under Reimbursable Loan Agreement (RLA), the Offeror must indicate at this point, and ensure that all such costs are duly incorporated in the financial proposal submitted to UNDP. 

K.   Criteria for Selection of the Best Offer

The individuals desirous of quoting for the work should make an expression of interest by submitting the required documents and information listed below

1. The relevant individual should have a degree in Computer Science, Information Systems or any related field
2. Proven Knowledge and the use of the following tools is a must: AMQ, Event Based programing, Database versioning, java, jasper reports, angular JS
3. Knowledge of health information systems is an added advantage
4. At least 6 years working experience
5. Proven systems integration experience (provide references)
6. The successful candidate should be a local