HSCN CN-SP Service Management Requirement Feedback Template

HSCN CN-SP Service Management Requirement Feedback Template v0.1 16/05/2016

HSCN
Directorate / Programme / HSCN / Project / HSCN
Document Reference
Project Manager / Status / Draft
Owner / Ian Cooke / Version / 0.1
Author / Various / Version issue date / 16/05/2016

HSCN CN-SP Service Management Requirement Feedback Template v0.1 16/05/2016

Document Management

Revision History

Document Control:

The controlled copy of this document is maintained in the HSCIC corporate network. Any copies of this document held outside of that area, in whatever format (e.g. paper, email attachment), are considered to have passed out of control and should be checked for currency and validity.

Version / Date / Summary of Changes
0.1 / 16/05/2016 / Initial draft

Reviewers

This document must be reviewed by the following people:

Reviewer name / Title / Responsibility / Date / Version
Ian Cooke / Joint Chair Service Management work-stream for the HSCN / Innopsis engagement (HSCIC) / 16/05/16 / 0.1
Mike Thomas / Joint Chair Service Management work-stream for the HSCN / Innopsis engagement (Innopsis) / 16/05/16 / 0.1

Approved by

This document must be approved by the following people:

Name / Signature / Title / Date / Version

Chris Brown Transition Programme Manager (HSCIC)

Contents

1Introduction

1.1Purpose of this document

1.2The use of the content of this document

2Feedback on the Agreement

2.1Supplier details

2.2Unacceptable aspects of the service management requirements to the HSCN Obligation Framework

2.3Changes that may impact HSCN Consumer charges

2.4Requirements requiring clarification

1Introduction

1.1Purpose of this document

The purpose of this document is to provide a structured template in which suppliers can provide feedback on the draft service management requirements and associated addendum to the HSCN Obligation Framework.

1.2The use of the content of this document

The Authority will consider the information provided by suppliers in this template and will, at the Authority’s sole discretion, amend the service management requirements and associated addendum to the HSCN Obligation Framework to take into account the feedback received.
Following consideration of the feedback, the Authority will inform suppliers of any amendments made to the service management requirements and associated addendum to the HSCN Obligation Framework as a result of this feedback and any further consultation required in order to based-line the same.

1.3Providing feedback using this document

Please return your completed feedback using this template to the following email addresses including “CN-SP SM Requirements Feedback” in the subject field.

-Cc’d to:



HSCN CN-SP Service Management Requirement Feedback Template v0.1 16/05/2016

2Feedback on the Agreement

All references in this document to the service management requirements to the HSCN Obligation Framework include the associated addendum.

2.1Supplier details

Please complete the table below with the details requested.

Organisation name:
The name of the person completing this document:
Therole of the person completing this document:
Are you intending to provide HSCN services as an AC-SP? / Yes / No (delete as appropriate)
Are you intending to provide HSCN services as a DLN-SP? / Yes / No (delete as appropriate)

2.2Unacceptable aspects of the service management requirements to the HSCN Obligation Framework

Suppliers are requested to complete an entry in the table below for any aspects of the service management requirements to the HSCN Obligation Framework that they find unacceptable. In this context “unacceptable” means your organisation would not be prepared to provide HSCN services unless the issue was resolved.
All columns in the table are mandatory and should be completed as follows:

(i)Requirement reference: For example, “requirement SMSDA1” or “addendum section 3.3.1.1 Service level metrics”;

(ii)Issue: A description of the issue you have with the requirement and the reason why it is unacceptable;

(iii)Alternative Proposal: A description of your alternative proposal which if adopted would mean that the issue no longer represents an unacceptable aspect of the requirements.

Requirement reference / Issue, including reason for unacceptability / Alternative Proposal

2.3Changes that may impact HSCN Consumer charges

Suppliers are requested to complete an entry in the table below for each aspect of the service management requirements to the HSCN Obligation Framework where the supplier judges that the requirement would increase the charges to HSCN Consumers for the HSCN services they may supply.
All columns in the table are mandatory and should be completed as follows:

(i)Requirement reference: For example, “requirement SMSDA1” or “addendum section 3.3.1.1 Service level metrics”;

(ii)Description of impact on HSCN Consumer charges: A description of the aspect of the requirements where the supplier judges that the requirement is increasing the charges for the HSCN services they may supply and the rationale for that increase;

(iii)HSCN Consumer charges impact: An estimate of the percentage increase in the HSCN Consumer charges as a result of this requirement;

(iv)Alternative Proposal: A description of any alternative proposal you have that would achieve a similar outcome for the Authority at a reduced impact on the HSCN Consumer charges and the rationale for that reduction;

(v)Alternative HSCN Consumer charges impact: An estimate of the percentage increase in the HSCN Consumer charges if your alternative proposal is adopter rather than the proposed requirement.

Requirement reference / Description of impact on HSCN Consumer charges / HSCN Consumer charges impact / Alternative Proposal / Alternative HSCN Consumer charges impact

2.4Requirements requiring clarification

Suppliers are requested to complete an entry in the table below for any aspects of the requirements they find unclear.
All columns in the table are mandatory and should be completed as follows:

(i)Requirement reference: For example, “requirement SMSDA1” or “addendum section 3.3.1.1 Service level metrics”;

(i)Potential ambiguity: A description of the potential ambiguity.

Requirement reference / Potential ambiguity