Heat Networks Zoning (HNZ) Digital Beta

Description

Summary of work We require a service design, development and content editing team to deliver a digital service that meets the needs of users though beta and go live, enabling our users to define heat network zones within their local area and understand how these zones impact them. Where the supplied staff will work No specific location (for example they can work remotely) Why the work is being done In 2021 DESNZ consulted on proposals which envisage central and local government working together with industry and local stakeholders to identify and designate planning areas within which heat networks are the lowest cost, low carbon solution for decarbonising heating. A nationwide methodology is being developed by the Heat Network Zoning team for identifying and designating Heat Network zones. A HN model has been developed to identify zone boundaries, with a supporting database of building supply and demand. A discovery and alpha phase for a supporting digital service was undertaken in 2023. We are seeking a partner supplier for the Beta phase of this digital project to create a step change in how Government publishes information on HN zoning. The supplier will develop and test a content management system, supporting web content, and integrated map visualisation tool to present data about heat network zones in a visual manner to enable users to undertake their statutory duties and to identify suitable areas for HN development. The developer will also be mindful of emerging needs from the policy development and where necessary undertake related discovery and/or alpha work to capture these requirements and incorporate these additional functions into the overall iterative Beta build. The business problem Our delivery partner will undertake the development of a digital service through beta and go live to: 1. Provide information and guidance to stakeholders such as zone rules and procurement opportunities in a form that is tailored to the target audience. 2. Inform stakeholders about the rules surrounding a national methodology to identify zone boundaries. 3. Visualise geo-packages using ESRI experience builder representing zones and showing indicative HN routing. 4. Display and collect supporting data about zones populating a database of building supply/demand opportunities The team must have UX, geospatial visualisation, data architecture, user testing and content design expertise to build our digital service, working in an agile way, identifying any additional emerging requirements from our policy and delivery workstreams and incorporate these into the iterative development of the Beta products. The service must comply with Cyber Essentials, the GDPR, and the WCAG (2.1 to AA) requirements and also align to the Government technology code of practice, standards and guidance. A service assessment may be required depending on emerging project needs. As part of the project, internal HN Zoning website administrators and content managers will need to be skilled up, so that the HN team can manage service after the supplier’s involvement has finished. The people who will use the product or service User type: Department for Energy Security and Net Zero, the zoning policy owner Definition: Communicate details of HN Zones to external stakeholders. Use this service to provide supporting information and guidance. Be confident that the service is future proofed such that additional administrative digital services and data management can be incorporated. Know how effective the digital service is so if it is not meeting objectives changes can be made. User type: The Department for Levelling Up, Communities & Housing Definition: Needs to know where HN zones are, and what planning changes are being made due to the zoning policy to enable effective and joined planning. User type: The HN Market Regulator (Ofgem) Definition: Needs up to date information on zoning rules and locations to assess whether legislative requirements are met. User type: National Underground Asset Register Definition: Needs to know where new heat networks are and how to contact them. User type: Zoning co-ordinators (Local Authorities - LA's) Definition: Need to have up-to-date information about zoning rules and requirements and be able to identify local HN zones. User type: HN specialist consultants/developers/operators Definition: Need to identify HN zones to carry out business development activities. User type: Building owners within a HN zone Definition: Need to know whether they are covered by this policy so they can plan a HN connection Any pre-market engagement done The Zoning policy has been consulted upon with the full consultation and market response here: [https://www.gov.uk/government/consultations/proposals-for-heat-network-zoning] The policy and model that has been developed for the national methodology was tested with 28 Local Authorities and nine specialist engineering Consultancies with more information available here: [https://www.gov.uk/government/publications/heat-networks-zoning-pilot]. Work done so far A Discovery and Alpha with detailed user research was undertaken to inform the Beta stage by TPX Impact, however additional requirements are expected to emerge that will need to be investigated and if appropriate incorporated into the build. Outputs from the Discovery and Alpha will be made available to those respondents that progress to the second stage. The delivery partner for discovery and alpha have signed a conflict-of-interest declaration confirming that ethical walls are in place between the technical solution team and the bid team so that no unfair advantage can be gained. Key milestones in the development of the Heat Network Zoning Digital Service include; completion of Discovery and Alpha stages of the HN zoning digital service. The supporting documentation will be made available to those providers that make it through to the second stage of the tender process, this includes the: - Discovery report - Alpha summary slide pack - Alpha technical options report Which phase the project is in Beta Existing team The supplier will work with a team of three who will undertake programme and commercial management and provide input into the Beta. This will include a service owner, internal programme manager and commercial manager. There will also be input from the wider Heat Network team from a policy and technical perspective. Address where the work will be done Majority of work will be conducted remotely, but we expect the supplier's core team to be available up to once a month for face-to-face activity at the DESNZ offices (3-8 Whitehall Place, London, SW1A 2EG). Travel expenses will not be reimbursed. Working arrangements The DESNZ team (1 service manager, 1 product manager, 1 commercial manager for Beta) will be available to support the selected delivery partner 5 days per week (Monday to Friday) and expect this commitment from the delivery partner. Delivery will be governed by standard agile delivery techniques. These could be either a Kanban or a scrum approach (depending on the work) but the standard agile ceremonies appropriate to those will be undertaken. We expect these to be led by the external Delivery Manager, who will work collaboratively with our Programme Manager and Service Owner to prioritise backlogs in refinement sessions. Security and vetting requirements Baseline Personnel Security Standard (BPSS) More information about the Security requirements: The level of clearance for this requirement is an Enhanced DBS and BPSS, suppliers who do not currently have this will not be excluded from the process however will be expected have upon contract start. Latest start date 5 February 2024 Expected contract length Contract length: 2 years 0 months 0 days Special terms and conditions special term or condition: The Buyer will have the right to terminate this Call-Off Contract for convenience for a period of twenty (20) calendar days following the Buyer confirming and accepting the completion of all acceptance criteria for Beta by giving thirty (30) calendar days written notice to the Supplier. Standard exit provisions will apply. Budget Indicative maximum: £3605000 Indicative minimum: £2300000 Further information: The indicative minimum budget is the approved budget available up to the point of Beta 'go live'. There is an approval gate prior to 'go live', which would then look to release further budget. Contracted out service or supply of resource? Contracted out service: the off-payroll rules do not apply Terms and acronyms Term or acronym: BPSS Definition: Baseline Personnel Security Standard Term or acronym: CDDO Definition: Central Digital and Data Office Term or acronym: DESNZ or Contracting Authority Definition: Department for Energy Security and Net Zero Term or acronym: ESRI Definition: Geographic Information Systems (GIS) Mapping Software Term or acronym: GDPR Definition: General Data Protection Regulations Term or acronym: HN Definition: Heat Network Term or acronym: LA Definition: Local Authority Term or acronym: UX Definition: User Experience Term or acronym: WCAG Definition: Web Content Accessibility Guidelines Questions and Clarifications 1. " Question 4 - Could you clarify your definition of identifying wider services? Does this mean identifying wider services (e.g. new sustainability requirements) whilst completing an existing project and then incorporating these requirements into the project? Question 10 - What is the level of access to end-user (and all other) stakeholders for the purposes of determining the most relevant and effective research methods?" The heat network zoning policy is in the process of development and implementation and the operational delivery process design is ongoing. It is therefore anticipated that additional service elements will be needed to deliver effective administration of the HN Zoning policy. Should you proceed to the second stage of the tender this requirement to meet emerging needs will need to be reflected in the size of team, programming and delivery cost profile proposed making sure you reflect the intensity of delivery expected in your bid. Last Updated : <strong>01/12/2023</strong> 2. Question 5: Does this question mean the following: 1. "Explain how you would create a service vision and why you would do it this way?" 2. "Explain how you would design the service and why you would do it this way? 3. "Explain how you would design the service using Service Design principles?" 4. "Explain how KPIs would be selected/agreed?" 5. "Explain which KPIs would be selected/agreed?" 6. "Explain how agreed KPIs would be met by the service design? Question 5: 1. Can you please clarify what service you intend to offer? 2. What is your understanding of service design in this context? Question 5: Does this question mean the following: 1. "Explain how you would create a service vision and why you would do it this way?" Answer: YES 2. "Explain how you would design the service and why you would do it this way? Answer: YES 3. "Explain how you would design the service using Service Design principles?" Answer: YES 4. "Explain how KPIs would be selected/agreed?" 5. "Explain which KPIs would be selected/agreed?" Answer: Instead of breaking out your 4 and 5 think collectively - Explain how you would work with us to select & agree KPIs 6. "Explain how agreed KPIs would be met by the service design? Answer: Explain how you would demonstrate to us that agreed KPIs were meeting the needs of the service design Question 5: 1. Can you please clarify what service you intend to offer? Answer: In the 'problem to be solved' section, points 1-4 inclusive highlight the service we intend to offer. 2. What is your understanding of service design in this context? Answer: Meeting the service needs identified during discovery & alpha and then ensuring that the iterative development continues to identify scope and include within the build, as appropriate, any emerging requirements. Last Updated : <strong>01/12/2023</strong> 3. If shortlisted we have between the 15th December and 9th January to develop a response, however this period lands within the middle of the Christmas holiday, would you consider extending the tender submission date to the later half of January, ideally 26th? We have been mindful of the Christmas break in our timings, ensuring there is a full week both before and after the holiday period, 18th to 22nd December inclusive (5 full working days) and 2nd to 8th January (5 full working days). Unfortunately, in view of the required start date for the project, it is not possible to accommodate an extension. Last Updated : <strong>01/12/2023</strong> 4. Question 10 - What is the level of access to end-user (and all other) stakeholders for the purposes of determining the most relevant and effective research methods? This separate clarification question answers part 2 of the clarification posed in the first response (Question 4 answered previously, this response answers the clarification around Question 10). We would potentially want to engage a large number of local authorities, HN consultants and HN operation organisations and building owner representatives in the closed beta especially as we move to the middle of next year and would want a significant subset of those beta users to be engaged in user research at some level. These would need to be given access through a log in portal as the materials will need formal approval before they can be made publicly available through an open beta. Last Updated : <strong>01/12/2023</strong>