Common use of AS-BUILT PHYSICAL ARCHITECTURE AND CAPACITY PLANNING Clause in Contracts

AS-BUILT PHYSICAL ARCHITECTURE AND CAPACITY PLANNING. 17.1 The Service Provider shall prepare, maintain and keep up to date from time to time (and in any event within ten (10) Working Days of any change) a document detailing the physical architecture of each technical environment used for each Service Element (the "As-Built Physical Architecture"). The As-Built Physical Architecture shall include the following: 17.1.1 where every Service Provider Asset used exclusively in the provision of the Services is physically deployed; and 17.1.2 what function each Asset supports, and shall identify Assets by reference to the Asset Register. 17.2 The Service Provider shall on and at all times following the Operational Commencement Date: 17.2.1 ensure that the Service Systems have at all times sufficient Capacity and process and deal with all Data and other requirements provided to or required of the Service Provider in providing the Services to enable the Services to be supplied in accordance with the Service Levels; and 17.2.2 carry out Capacity Planning to identify potential gaps between the Capacity available and the Capacity required with a view to ensuring that the Service Systems will have Capacity (including but not limited to sufficient processing power, Data storage capacity and network bandwidth) to cope with all foreseeable contingencies and with all anticipated or planned expansion of the Services, including without limitation in connection with the implementation of the Service System(s), any Additional Services and new Services introduced in accordance with the Change Control Request Procedure. 17.3 The Service Provider shall during the Operational Phase prepare and keep updated during the Term Capacity Plans supported by spreadsheets and shall submit a current version of such plans, together with current versions of the Asset Register and As-Built Physical Architecture, to TfL:

AS-BUILT PHYSICAL ARCHITECTURE AND CAPACITY PLANNING. 17.1 20.1 The Service Provider shall prepare, maintain and keep up to date from time to time (and in any event within ten (10) Working Days of any change) a document detailing the physical architecture of each technical environment used for each Service Element (the "“As-Built Physical Architecture"”). The As-Built Physical Architecture shall include the following: 17.1.1 (A) where every TfL Asset is physically deployed; (B) where every Service Provider Asset used exclusively in the provision of the Services is physically deployed; and 17.1.2 (C) what function each Asset supports, and shall identify Assets by reference to the Asset Register. 17.2 20.2 The Service Provider shall on and at all times following the Operational Commencement Date: 17.2.1 (A) ensure that the Service Systems have at all times sufficient Capacity and process and deal with all Data and other requirements provided to or required of the Service Provider in providing the Services to enable the Services to be supplied in accordance with the Service Levels; and 17.2.2 (B) carry out Capacity Planning to identify potential gaps between the Capacity available and the Capacity required with a view to ensuring that the Service Systems will have Capacity (including but not limited to sufficient processing power, Data storage capacity and network bandwidth) to cope with all foreseeable contingencies and with all anticipated or planned expansion of the Services, including without limitation in connection with the implementation of the Service System(s), Release 2 and any Additional Services and new further Services introduced in accordance with agreed through the Change Control Request Procedure. 17.3 20.3 The Service Provider shall during the Operational Phase prepare and keep updated on an ongoing basis during the Term draft Capacity Plans plans supported by spreadsheets (“Draft Capacity Plans”) and shall submit a current version of such plans, together with current versions of the Asset Register and As-Built Physical Architecture, to TfL: (A) every six (6) months; and/or (B) with greater regularity if TfL requests it or if the Service Provider wishes to raise a Capacity Planning issue of concern with TfL; and (C) as part of the Change Control Request Procedure and promptly following the issue of a Change Authorisation where such Change requires an amendment to the Draft Capacity Plan(s); and (D) no later than nine (9) Months prior to the expiry of the Agreement or (if earlier) promptly following the issue of a notice of termination or a Partial Termination Notice. 20.4 The Draft Capacity Plans shall be prepared by the Service Provider in respect of each Asset or logical group of Assets as specified in the As-Built Physical Architecture, and shall include the following: (A) actual utilisation of the Asset; (B) 1, 2, 3, 4 and 5 year Capacity predictions based on observable trends, foreseeable contingencies and anticipated or planned expansion of the Services (including without limitation in connection with the implementation of Release 2 and any Additional Services and further Services agreed through the Change Control Request Procedure); and (C) required or recommended changes to each Asset to enable the Service Provider to achieve the Service Levels. 20.5 TfL: (A) shall, subject to clause 20.10, inform the Service Provider of any likely significant increases in the demand for Capacity of which it is aware during the Operational Phase; and

AS-BUILT PHYSICAL ARCHITECTURE AND CAPACITY PLANNING. 17.1 The Service Provider shall prepare, maintain and keep up to date from time to time (and in any event within ten (10) Working Days of any changeChange) a document detailing the physical architecture of each technical environment used for each Scheme, Service Element and the D&EI Systems (and parts thereof) (the "As-As- Built Physical Architecture"). The As-Built Physical Architecture shall include the following: 17.1.1 where every Service Provider Asset used exclusively in the provision of the Services is physically deployed; and 17.1.2 what function each Asset supports, and shall identify Assets by reference to the Asset Register. 17.2 The Service Provider shall on and at all times following the Operational Commencement Date: 17.2.1 ensure that the Service D&EI Systems have at all times sufficient Capacity and process and deal with all Data and other requirements provided to or required of the Service Provider in providing the Services to enable the Services to be supplied in accordance with the Service Levels; and 17.2.2 carry out Capacity Planning to identify potential gaps between the Capacity available and the Capacity required with a view to ensuring that the Service D&EI Systems will have Capacity (including but not limited to sufficient processing power, Data storage capacity and network bandwidth) to cope with all foreseeable contingencies and with all anticipated or planned expansion of the Services, including without limitation in connection with the implementation of the Service D&EI System(s), ) and any Additional Services and new Services introduced in accordance with the Change Control Request Procedure. 17.3 The Service Provider shall during the Operational Phase prepare and keep updated during the Term Term, Capacity Plans supported by spreadsheets and shall submit a current version of such plansCapacity Plans, together with current versions of the Asset Register and As-Built Physical Architecture, to TfL: