Provision of Services for the Development/customisation and deployment of DHIS2 for the Rapid Health Facility Assessment (RHFA) in Papua New Guinea

New clarification added: QUESTION:Could you please provide an indication of the expected number of RHFA digital forms/modules to be configured? If exact numbers are not yet finalised, an estimated range would be helpful, for example:1–5 forms6–10 forms Could you provide an indication of the expected data structure per form, such as:approximate number of data elements per form (e.g. <50, 50–150, 150+) number of sections or subsections within each form If available, could you also share sample RHFA tools (Excel, paper forms, or draft templates)? Could you clarify the expected workflow and approval structure for RHFA submissions?If detailed workflows are not yet finalised, an indicative range would be helpful, for example:- simple data entry only (no approval workflow)single-level approval (e.g. district validation)multi-level approval (e.g. district → provincial → national) Additionally, is it expected that all forms follow the same workflow, or will only selected modules require approvals? Could you confirm the expected approach for dashboard configuration:- a single standardised set of dashboards with filters for national, provincial, and district views; or- separate dashboards configured for each province or user group?If separate dashboards are required, an approximate number (e.g. 1–5, 6–20, 20+) would be helpful.ANSWER:The RHFA has six sections. The first 5 sections are short, the 6th section allows for multiple functional areas depending on the facility type.  The RHFA tools will be shared after the contract is awarded. There are five forms (corresponding to five HF levels[L]). There are six sections on each form. Sections A, B, C, D & E are standard across all forms and captures basic details of the health facilties. Section F asks the same questions, but the number of questions depends on the prescribed functional areas for that level. All forms follow the same workflow (in digital sense that is data entry only, of course validation rules at the time of data entry should be part of the data entry feature for all digital forms/modeules). For the dashboard query, one of the tecnical requirement in the TOR specifies role-based access so this will depend on the specific developer's appraoch to how they want to design the dashboard to meet this requirement. It creating orgnainaitonal unit (OU) access together with the different roles and then assigning users to roles and OUs, then it might be one dashboard with controlled and restricted access to visuals on that one dashboard. But this depends on how the developer/bidder/vendor's approach to address this requirement..

New amendment added #2: Tender Amendment No. 2 is issued to upload the pre-bid meeting slides and minutes.

New clarification added: QUESTION:Can UNOPS provide further details regarding the expected level of post-deployment support during the 12-month contract period, including any anticipated service level requirements or response time expectations? Additionally, can UNOPS confirm whether all custom developments, configurations, metadata, documentation, and source code created under this assignment will become the property of NDoH/UNOPS upon project completion?ANSWER:The vendor is expected to provide technical support, troubleshooting, bug fixing, minor configuration adjustments and advisory support throughout the support period. As indicated in Appendix 1, reported bugs and system issues should generally be addressed within 2–3 working days, depending on severity and complexity. Vendors may propose additional Service Level Agreement (SLA) arrangements as part of their proposal. This can be provided as remote support.All data, custom developments, configurations, metadata, documentation and source code produced under this assignment will become the property of UNOPS and NDoH upon completion of the contract and must be transferred as part of the handover process.

New clarification added: QUESTION:Can UNOPS confirm the anticipated number of participants for:Training of Trainers (ToT)System Administrator TrainingEnd User TrainingANSWER:For planning purposes, bidders should assume approximately 10–15 participants for the Training of Trainers programme and system administration training.The in-country end-user training activity is expected to involve approximately 100 participants from the provincial level. But this training will cover more than just the deployment of the tool, and will be coordianted by UNOPS - with 1-2 sessions for the supplier to lead.Final participant numbers will be confirmed during implementation.

New clarification added: QUESTION:Is the project expected to support an initial pilot implementation followed by phased rollout, or should the proposed solution support nationwide deployment from initial production release?ANSWER:The deployment is to be phased region by region (across 4 regions of PNG). The first region will be treated as the pilot. The vendor can advise on how best to approach the development of the solution, but all regions will use the same collection tools and dashboard / reporting formats for simplicity. There is not much time between the completion of the first region (the pilot) and the second region - implementation for the second region must be ready to deploy shortly after the completion of the pilot.

New clarification added: QUESTION:Can UNOPS provide an estimate of the anticipated number of users at the national, provincial, district, and facility levels who are expected to access and utilise the RHFA Digital Platform?ANSWER:The exact number of users will be confirmed during implementation. For proposal purposes, bidders should assume national-level users (NDoH branches including HFSB, PMRB and ICT), provincial-level users across 22 provinces, and potentially district-level representatives in 96 districts.

New clarification added: QUESTION:Are there any existing digital assets available to the selected vendor, including digital forms, metadata configurations, organisational hierarchies, GIS datasets, dashboards, indicators, facility master lists, or data models that have already been developed for RHFA or related health programmes?ANSWER:The RHFA assessment tools currently exist in a non-digital format and will be made available to the successful bidder. Existing organisational hierarchies, facility master lists and selected reference datasets may also be made available where relevant. However, bidders should assume that the majority of the RHFA configuration, metadata, forms, workflows, dashboards and reporting structures will need to be developed and configured as part of this assignment.

New clarification added: QUESTION:Can UNOPS provide details of any existing National Health Information Systems, databases, applications, or platforms that the RHFA Digital Platform is expected to integrate with during this project phase?ANSWER:The RHFA Digital Platform is not required to implement full integration with other national systems during the initial development phase. However, the solution should be designed to support future interoperability, particularly with the national eNHIS. Vendors are expected to propose an approach that supports future integration through standard DHIS2 and API-based mechanisms.

New clarification added: QUESTIONS:Does the National Department of Health currently operate an existing DHIS2 environment and, if so, is the RHFA Digital Platform expected to be deployed within that environment or as a standalone DHIS2 instance?Additionally, will hosting infrastructure be provided by UNOPS/NDoH, or is the vendor expected to provide hosting and infrastructure services as part of the proposed solution?Finally, for evaluation purposes, will experience implementing comparable digital information systems, data collection platforms, workflow management systems, and reporting platforms be considered equivalent to DHIS2-specific implementation experience where similar functionality has been successfully delivered?ANSWERS:The RHFA Digital Platform is expected to be implemented as a separate DHIS2 instance during the scope of this assignment. Future interoperability with eNHIS and other national systems should be considered in the solution design, but is not required at this time.As per the ToR, the vendor is expected to provide and manage the hosting infrastructure, including associated hosting costs, during the first year of implementation. There must be a plan, made in collaboration with UNOPS and the National Department of Health (NDoH) to transition the hosting to NDOH after the first year of implementation.Experience implementing DHIS2 solutions is strongly preferred; however, experience delivering comparable digital information systems, data collection platforms, workflow management systems and reporting platforms may also be considered where the bidder can demonstrate equivalent functionality and successful implementation outcomes.

New amendment added #1: Tender Amendment No. 1 is issued to reschedule the online pre-bid meeting as follows:Date: 12 June 2026Time: 13.00 - 14.00 (Port Moresby time)Google Meet joining infoVideo call link: https://meet.google.com/bau-xtmj-svwPlease register for the pre-bid meeting by sending an email to thanaphonet@unops.org and copy arifu@unops.org by 11 June 2026.Kindly note that attending the pre-bid meeting is not mandatory, but is strongly encouraged to avoid the risk of non-compliant proposals.

New clarification added: QUESTION:Can you please clarify which documents are intended for uploading to the following section:A) Appendix 1: Technical RequirementsWhere can I download the following forms for submitting - Are they provided by UNOPS? Or the company shall create this form by itself?B) Form F: Performance Statement FormC) Form E: Resume of Proposed PersonnelD)  Form G: Self Disclosure FormANSWER:All bidding forms, including Forms A-G and Appendix 1, are provided by UNOPS as part of the tender package.Please refer to Section III - Returnable Bidding Forms available at the tender notice link: https://www.ungm.org/Public/Notice/302299Bidders are required to complete and submit the templates provided by UNOPS. The creation of alternative formats or bidder-developed forms is not required and is discouraged.