Common use of SERVICE PROVIDER’S SOLUTION Clause in Contracts

SERVICE PROVIDER’S SOLUTION. 6.1 The report produced, and the designs, solutions and proposals developed, by the Service Provider prior to the Effective Date are attached hereto as Schedule 28 (Service Provider’s Solution) (the "Service Provider’s Solution"). 6.2 The Service Provider acknowledges and agrees that: 6.2.1 the Service Provider has full knowledge and understanding of the Requirements and warrants on a continuous basis throughout the Term that: (A) the Service Provider's Solution (as may be varied pursuant to the Change Control Request Procedure from time to time): (1) is Fit for Purpose for the provision of the Services required under this Agreement; (2) meets the Requirements; and (3) meets the TfL Objectives; and (B) the Requirements set out sufficient functional requirements to enable the Service Provider to deliver an IT platform from which to operate the Services in accordance with this Agreement. 6.2.2 the Service Provider’s Solution and any other ideas, methods, concepts or theories (including without limitation any "proof of concept" synopsis, milestone or feasibility demonstration in connection with the Services) will be verifiable, verified, demonstrable, demonstrated and capable of use and used for the purposes of this Agreement; 6.2.3 the Hardware, Software and Systems (including without limitation any relevant Assets) provided or used in connection with the BOps or Business Operations Systems will be completely separate and distinct from any Hardware, Software and Systems provided or used in connection with the EOps or Enforcement Operations Systems, save for the Service Systems Interfaces between BOps, or Business Operations Systems, on the one hand, and EOps, or Enforcement Operations Systems, on the other hand, and save as set out in Appendix DbA (Shared Systems) to Module Db of Schedule 28 (Service Provider's Solution) and shall ensure that all Documentation reflects this.

SERVICE PROVIDER’S SOLUTION. 6.1 The report produced, and the designs, solutions and proposals developed, by the Service Provider prior to the Effective Date are attached hereto as Schedule 28 (Service Provider’s Solution) (the "Service Provider’s Solution"). 6.2 The Service Provider acknowledges and agrees that: 6.2.1 the Service Provider has full knowledge and understanding of the Requirements and warrants on a continuous basis throughout the Term that: (A) the Service Provider's Solution (as may be varied pursuant to the Change Control Request Procedure from time to time): (1) is Fit for Purpose for the provision of the Services required under this Agreement; (2) meets the Requirements; and (3) meets the TfL Objectives; and (B) the Requirements set out sufficient functional requirements to enable the Service Provider to deliver an IT platform from which to operate the Services in accordance with this Agreement. 6.2.2 the Service Provider’s Solution and any other ideas, methods, concepts or theories (including without limitation any "proof of concept" synopsis, milestone or feasibility demonstration in connection with the Services) will be verifiable, verified, demonstrable, demonstrated and capable of use and used for the purposes of this Agreement; 6.2.3 the Hardware, Software and Systems (including without limitation any relevant Assets) provided or used in connection with the BOps or Business Operations Systems will be completely separate and distinct from any Hardware, Software and Systems provided or used in connection with the EOps or Enforcement Operations Systems, save for the Service Systems Interfaces between BOps, or Business Operations Systems, on the one hand, and EOps, or Enforcement Operations Systems, on the other hand, and save as set out in Appendix DbA DbB (Shared Systems) to Module Db of Schedule 28 (Service Provider's Solution) and shall ensure that all Documentation reflects this.