Common use of The Contractor’s Solution Clause in Contracts

The Contractor’s Solution. the technical proposal from the Contractor which sets out an overview of the proposed solution supported by the necessary detail of the Contractor’s response to the Authority’s Requirements 1) Two new wizard screens shall be created to allow users to be mapped to one of the new organisation groups 2) Changes shall be implemented to the User Details and User Summary screens to show the new organisational drop downs 3) Amendments to the LSC Security Database shall be made to support the 2 new organisational groups 4) Changes shall be made to extract the new organisation master data from PIMS/CPDS The changes shall be tested according to the Test Plan and Test Approach as per section 1.2. The changes shall be implemented as a maintenance release in accordance with the Release Plan as per section 1.2 The Contractor shall produce or update the following deliverables: Work Package The Functional Specification The Test Approach The Test Plan Detail Design SIT Scripts SIT Report OAT Plan OAT Report Release Plan The Application Overview Document (AOD) Post Implementation Support End of Project Report It is important to recognise that these changes will need to be co-ordinated with other LASS changes and which may have an impact on the overall timelines proposed as per section 3.3. A maximum period of 4 weeks is included for PIS at which point a decision will be made by the Authority and Capgemini to either exit PIS or back out the system and continue UAT or Operational testing. Dependencies: SFA to populate new agency structure in PIMs. Details of structure will need to be available by 15/05/2012 New structure will need to be implemented in PIMs by 22/05/2012 Capgemini will import new PIMS structures into the test environments Assumptions: Authorisation from the Agency to commence will be given by 21/05/2012

The Contractor’s Solution. the technical proposal from the Contractor which sets out an overview of the proposed solution supported by the necessary detail of the Contractor’s response to the Authority’s Requirements 1) Two Requirements Approach Deploy new wizard screens shall be created Blue Coat proxy and AV solution in parallel to allow users existing Blue Coats Move NCS web application on to the new devices Deploy Blue Coat Enterprise Reporter and configure logging from new and existing appliances Enterprise Reporter Capgemini will supply a virtual machine to install the Bluecoat Reporter appliance. The specification is 2 processor and 8GB of RAM. Disk space requirement is still to be mapped finalised, but it is proposed that initially 100GB is made available. Capgemini will install the Bluecoat Reporter and assign an IP address and temporary password for BT. BT will supply the IP address including VLAN ID for the engineer to one assign. Deliverables The table below identifies at a management summary level the list of products to be provided as part of this solution: ID Title Description 1 Technical Infrastructure Design - TID Standard Product. The existing NCS TID document will be extended. 2 Test Approach This will be a short document to summarise the verification approach to be followed. 3 Test Report This will be a short document to document the results of the verification tests. The main tasks and an indicative outline time schedule are shown below. There are 3 Bank Holidays during this period. The new organisation groups 2) Changes shall Blue Coat devices will be implemented issued with temporary IP addresses and smoke tests will be run against the NCS site through them. These will include testing the core site functionality. The site will also be placed under some light load so as to identify potential throughput issues. Another set of smoke tests will be run once the cutover to the User Details live IP addresses has been made. This FSC will be delivered within the established Learner Advancement Portfolio (LAP), of which Blue Coat installation will be a part, managed by IM Services. The reporting arrangements will be via the Capgemini Project Manager for NCS Release 3.1 and User Summary screens to show the new organisational drop downs 3) Amendments arrangements for Release 3 and Release 3.1 In addition the Capgemini NCS Lead architect will face off to the LSC Security Database shall IM Services Lead Architect and his team. The quotation provided within this FSC is valid for 22 days from date of Capgemini signature and is dependent upon FSC 2225 for Release 3.1 being signed and commencing on the same date as this FSC commences. Should this not be made the case, any additional resources required to support the 2 new organisational groups 4) Changes shall be made to extract the new organisation master data from PIMS/CPDS The changes shall be tested according to the Test Plan and Test Approach as per section 1.2. The changes shall be implemented as a maintenance release in accordance with the Release Plan as per section 1.2 The Contractor shall produce or update the following deliverables: Work Package The Functional Specification The Test Approach The Test Plan Detail Design SIT Scripts SIT Report OAT Plan OAT Report Release Plan The Application Overview Document (AOD) Post Implementation Support End of Project Report It is important to recognise that these changes will need to be co-ordinated with other LASS changes and which may have an impact on the overall timelines proposed as per section 3.3. A maximum period of 4 weeks is included for PIS at which point a decision this FSC, will be made by the Authority and Capgemini subject to either exit PIS or back out the system and continue UAT or Operational testing. Dependencies: SFA to populate new agency structure in PIMs. Details of structure will need to be available by 15/05/2012 New structure will need to be implemented in PIMs by 22/05/2012 Capgemini will import new PIMS structures into the test environments Assumptions: Authorisation from the Agency to commence will be given by 21/05/2012appropriate Change Control.