Held at the Hilton Hotel, London
Slides from the morning session –
Slides from the afternoon session from NHS-Digital
Slides from the afternoon session from Crown Commercial Service
Questions and issues from the 25th July event.
|Migration||Whilst the 6 month migration forecasting approach described works for larger procurements (collabs and APs etc) it isn’t sufficiently flexible to handle the numerous smaller, simple procurements from individual organisations that could be delivered quickly (within a month of procurement in some cases). What can we do to enable suppliers to deliver these sorts of services quickly without being constrained by a forecast locked at 4 months?||NHSD are exploring options of an alternative forecasting model for high volume / low value replacement services which are subject to much shorter lead times. This solution will likely require proactive engagement from Suppliers to provide the necessary visibility. Suppliers should be aware that this obligation relates to volume forecasting not actual migration slots.|
|Migration||More information and guidance is required on IP management. What are our plans to provide this?||The intention is to organise an event (likely Webinar based) with the TACO SMEs to provide an overview of IP transfer process and respond to Supplier questions. This will be open to Stage 1 Compliant Suppliers.
1) NHSD HSCN IP Address Policy has been published on the NHS D website (https://digital.nhs.uk/health-social-care-network/IP-addressing-policy). The HSCN IP Addressing Policy and supporting guidance is included in the CNSP Technical Guidance Pack
2) NHSD has developed a new IPAM system to manage HSCN IP Addressing
3) Access to the NHSD IPAM system for both Consumer and Supplier will be via the NHSD HMS system.
4) Authorisation / Request process defined, including notification to CNSPs of approved transfer/allocation. Chris Brown, NHSD leading on gathering generic emails for notifications.
5) BT TN Transitional Assistance (TACO) process defined for the transfer of IP Address to new CNSP.
|Migration||How do we intend to share postcode and service data?||We will share data relating to individual APs as part of the tender packs issued for each procurement and via a virtual data room as we develop the individual procurement artefacts ahead of each procurement.
|Procurement||What happens if demand anticipated through aggregated procurements doesn’t materialise||We think this is a low risk due to the incentives placed on consumer organisations. Consumers will be obliged via their MoU with NHSD and CCS to order their entire requirement within a short period following award.
NHSD will investigate potential contractual mechanisms to give suppliers some comfort in this area.
If suppliers have particular ideas on how to address this contractually without undermining the procurement award decision process NHSD will take them into consideration.
|Compliance||Can non-HSCN compliant network resellers provision HSCN connectivity?||No. To be able to contract with a consumer for HSCN services the prime contractor (and any subcontractor providing HSCN connectivity) has to be an accredited CNSP.|
|Compliance||What stage of compliance do suppliers need to achieve to partake in the various stages of procurement?||Suppliers need to be stage 1 compliant to be able to bid for an opportunity and stage 2 at the point of award.|
|ANM||Why isn’t ANM connected to the Peering Exchange?||ANM is not connected to the Peering Exchange to:
1) Enable CN-SPs to breakout Internet traffic at the earliest opportunity
2) Minimise dependency on Peering Exchange service
3) Reduce costs to the Peering Exchange service
4) Potential ability to retain ANM service post Peering Exchange service
5) Potential for the ANM service to be extended to locally procured Internet breakout.
|ANM||What are the requirements for back-up internet provision in the event of ANM service outage?||ANM is delivered across two Data Centres in an Active / Active configuration. A single data centre will host one half of the Active / Active solution. CNSPs will connect to both locations (Primary / Standby).
Each active data centre is capable of supporting full throughput and load requirements in the event of a failure of one of the data centres.
In the event of a catastrophic failure of both sites, CNSPs shall route traffic directly to the Internet.
SO7 – The HSCN Supplier shall provide Layer-4 firewalling functionality for an Internet Gateway connection, with firewall rules provided from HSCN Data Security Centre via an automated process. The rule update shall be implemented within 24 hours from the time of publication.
|NAS||Why does NAS require suppliers to provide 2 separate streams of data to both datacentres?||TBC|
|NAS||Although NAS can support Netflow v5, v9 and IPFIX which should suppliers use to interact with it?||TBC