Common use of Possible Additions and Variations to Core Requirements Clause in Contracts

Possible Additions and Variations to Core Requirements. This section covers the possible future requirements for the NDR. It is expected that any tender should reflect understanding and demonstrate wherever appropriate how any proposed solutions may fulfil these requirements in the future: Ref Requirement type Requirements Outline P01 Data Extract (Subscription basis) The Energy Industry may be approved to use the NDR data in the future for marketing purposes e.g. target landlords for energy improvement products. This is not currently allowed for in the Regulations. This data must be aggregated over a number of buildings to protect privacy and could be provided on a subscription basis. An aggregate data extract facility should therefore be available to supply this data to them. This data may be sold on a cost or licence basis therefore any subscription costs should also be collected and recorded for internal reporting purposes. P02 Bulk Data Extraction With all long-term data storage capabilities there are many scenarios where the data may need to be bulk extracted from the repository for transferring to another repository. For example: • The technical platform becomes obsolete – for example due to changing business requirements – and a non-transparent upgrade path requires the existing NDR data to be extracted and transferred into the new NDR. • Continual non-conformance to the Service Level Agreement results in the contract being terminated and awarded to another supplier. The new NDR Operator may choose a different Operational Platform that requires the NDR data to be extracted and transferred during hand-over period. • Other government departments or agencies may be granted access to the data for specific purposes and need to perform bulk extracts of data from the NDR for populating another repository. As part of any solution the NDR Operator will need to demonstrate: • The data can be extracted from the NDR in a platform neutral format – ideally by reconstructing the original messages – in order to migrate the data to another Non Domestic Report Register possibly on a different operational platform. • Any proprietary or licensable software required for this extraction is identified with the expected cost of any licensing payment. Wherever possible at least one viable alternative should also be identified. • The solution allows for selective extraction of data – e.g. All Energy Performance Reports registered between two dates – so that staged transference can occur during any handover period. The data to be included in the handover includes the contents of the: • Energy Documents and Model Data • Property & Address details dataset • User Registration and Authentication dataset • Accreditation Scheme dataset P03 EA lodgement The EA may be permitted to lodge Energy Documents and the Model Data directly into the NDR, this is a possible future requirement beyond October 2008. Schedule 3 IMPLEMENTATION‌

Possible Additions and Variations to Core Requirements. This section covers the possible future requirements for the NDR. It is expected that any tender should reflect understanding and demonstrate wherever appropriate how any proposed solutions may fulfil these requirements in the future: Ref Requirement type Requirements Outline P01 Data Extract (Subscription basis) The Energy Industry may be approved to use the NDR data in the future for marketing purposes e.g. target landlords for energy improvement products. This is not currently allowed for in the Regulations. This data must be aggregated over a number of buildings to protect privacy and could be provided on a subscription basis. An aggregate data extract facility should therefore be available to supply this data to them. This data may be sold on a cost or licence basis therefore any subscription costs should also be collected and recorded for internal reporting purposes. P02 Bulk Data Extraction With all long-term data storage capabilities there are many scenarios where the data may need to be bulk extracted from the repository for transferring to another repository. For example: • The technical platform becomes obsolete – for example due to changing business requirements – and a non-transparent upgrade path requires the existing NDR data to be extracted and transferred into the new NDR. • Continual non-conformance to the Service Level Agreement results in the contract being terminated and awarded to another supplier. The new NDR Operator may choose a different Operational Platform that requires the NDR data to be extracted and transferred during hand-over period. • Other government departments or agencies may be granted access to the data for specific purposes and need to perform bulk extracts of data from the NDR for populating another repository. As part of any solution the NDR Operator will need to demonstrate: • The data can be extracted from the NDR in a platform neutral format – ideally by reconstructing the original messages – in order to migrate the data to another Non Domestic Report Register possibly on a different operational platform. • Any proprietary or licensable software required for this extraction is identified with the expected cost of any licensing payment. Wherever possible at least one viable alternative should also be identified. • The solution allows for selective extraction of data – e.g. All Energy Performance Reports registered between two dates – so that staged transference can occur during any handover period. The data to be included in the handover includes the contents of the: • Energy Documents and Model Data • Property & Address details dataset • User Registration and Authentication dataset • Accreditation Scheme dataset P03 EA lodgement The EA may be permitted to lodge Energy Documents and the Model Data directly into the NDR, this is a possible future requirement beyond October 2008. Schedule 3 IMPLEMENTATION‌.