Common use of Statement of Requirements Clause in Contracts

Statement of Requirements. This document, along with its appendices, is part of Schedule 2 (Statement of Requirements) of the Business Operations Agreement. Schedule 2 provides the requirements for the Business Operations, MIS, Finance, Interoperability, VoSI and General Service Elements. This document should be read in conjunction with other component documents of the Agreement as these play an integral part in understanding the requirements set out in this document. Definitions of terms used in this document are contained in Schedule 1 (Definitions). In meeting the Requirements set out in this Schedule 2: Statement of Requirements (Interoperability) the Service Provider shall at all times ensure that the Requirements are delivered in accordance with Clause 4 (TfL Objectives) of this Agreement. The structure and layout of this document is ordered into sections. Each section has a heading with an introductory statement. This is followed by sub-headings containing requirements. Each requirement has two rows containing the following information (see example of layout of Statement of Requirements): - Requirement number; - Mandatory; and - Requirement detail.

Statement of Requirements. This document, along with its appendices, is part of Schedule schedule 2 (Statement of Requirements) of the Business Enforcement Operations Agreement. Schedule 2 provides the requirements for the Business OperationsNotice Processing, MIS, Finance, Interoperability, VoSI Interoperability and General Service Elements. This document should be read in conjunction with other component documents of the Agreement as these play an integral part in understanding the requirements set out in this document. Definitions of terms used in this document are contained in Schedule 1 (Definitions). In meeting the Requirements set out in this Schedule 2: Statement of Requirements (InteroperabilityEnforcement Operations) the Service Provider shall at all times ensure that the Requirements are delivered in accordance with Clause 4 (TfL Objectives) of this Agreement. The structure and layout of this document is ordered into sections. Each section has a heading with an introductory statement. This is followed by sub-headings containing requirements. Each requirement has two rows containing the following information (see example of layout of Statement of Requirements): - • Requirement number; - Mandatory• Mandatory or Request For Information (RFI); and - • Requirement detail.

Statement of Requirements. STATEMENT OF REQUIREMENTS This document, along with its appendices, is part of Schedule 2 (Statement of Requirements) of the Business Enforcement Operations Agreement. Schedule 2 provides the requirements for the Business Enforcement Operations, MIS, Finance, Interoperability, VoSI Interoperability and General Service Elements. This document should be read in conjunction with other component documents of the Agreement as these play an integral part in understanding the requirements set out in this document. Definitions of terms used in this document are contained in Schedule 1 (Definitions). In meeting the Requirements set out in this Schedule 2: Statement of Requirements (InteroperabilityFinance) the Service Provider shall at all times ensure that the Requirements are delivered in accordance with Clause 4 (TfL Objectives) of this Agreement. The structure and layout of this document is ordered into sections. Each section has a heading with an introductory statement. This is followed by sub-headings containing requirements. Each requirement has two rows containing the following information (see example of layout of Statement of Requirements): - Requirement number; - Mandatory; and - Requirement detail.

Statement of Requirements. This document, along with its appendices, is part of Schedule schedule 2 (Statement of Requirements) of the Business Enforcement Operations Agreement. Schedule 2 provides the requirements for the Business OperationsNotice Processing, MIS, Finance, Interoperability, VoSI Interoperability and General Service Elements. This document should be read in conjunction with other component documents of the Agreement as these play an integral part in understanding the requirements set out in this document. Definitions of terms used in this document are contained in Schedule 1 (Definitions). In meeting the Requirements set out in this Schedule 2: Statement of Requirements (InteroperabilityEnforcement Operations) the Service Provider shall at all times ensure that the Requirements are delivered in accordance with Clause 4 (TfL Objectives) of this Agreement. The structure and layout of this document is ordered into sections. Each section has a heading with an introductory statement. This is followed by sub-headings containing requirements. Each requirement has two rows containing the following information (see example of layout of Statement of Requirements): -  Requirement number; - Mandatory Mandatory or Request For Information (RFI); and -  Requirement detail.

Statement of Requirements. This document, along with its appendices, is part of Schedule 2 (Statement of Requirements) of the Business Operations Agreement. Schedule 2 provides the requirements for the Business Operations, MIS, Finance, Interoperability, VoSI and General Service Elements. This document should be read in conjunction with other component documents of the Agreement as these play an integral part in understanding the requirements set out in this document. Definitions of terms used in this document are contained in Schedule 1 (Definitions). In meeting the Requirements set out in this Schedule 2: Statement of Requirements (InteroperabilityFinance) the Service Provider shall at all times ensure that the Requirements are delivered in accordance with Clause 4 (TfL Objectives) of this Agreement. The structure and layout of this document is ordered into sections. Each section has a heading with an introductory statement. This is followed by sub-headings containing requirements. Each requirement has two rows containing the following information (see example of layout of Statement of Requirements): - Requirement number; - Mandatory; and - Requirement detail.