Authority’s Requirements. FUNCTIONAL
Authority’s Requirements. CONSTRUCTION (ATTACHMENT – C1)
Authority’s Requirements. 1.13the Schedules other than Schedule 1 (Authority’s Requirements), Schedule 2 (Contractor’s Proposals) and Schedule 6 (Payment Mechanism); and
Authority’s Requirements. Part 1 Facilities RequirementsOutput Specification SCHEDULE 1 AUTHORITY'S REQUIREMENTS Part 2 Initial Services Output Specification Part 3 Services Specification SCHEDULE 2 CONTRACTOR'S PROPOSALS Part 1 Construction Proposals [TO BE PROVIDED BY THE PREFERRED BIDDER] SCHEDULE 2 CONTRACTOR'S PROPOSALS Part 2 Service Delivery Proposals [TO BE PROVIDED BY THE PREFERRED BIDDER] SCHEDULE 2 CONTRACTOR'S PROPOSALS Part 3 Construction Programme and Phases [TO BE PROVIDED BY THE PREFERRED BIDDER] Part 4 Sub-Contractors [TO BE PROVIDED BY THE PREFERRED BIDDER] SCHEDULE 3 CHANGE IN LAW - CONTRACTOR'S SHARE SOFT SERVICES INTERFACE PROTOCOL Cumulative Capital Expenditure Contractor's Share £0 - £[a] (inclusive) 100% £[a+1] - £[b] (inclusive) 80% £[b+1] - £[c] (inclusive) 60% £[c+1] - £[d] (inclusive) 40% £[d+1] - £[e] (inclusive) 20% £[e+1] - £[f] (inclusive) 10% £ >£[f] 0% SCHEDULE 4 SCHOOLS School (including address) Services StartPlanned ICT Handover Date Planned Services Availability Date [Planned Post Completion Works Acceptance Date]187188 Initial Amount Periodic Rate188189 SCHEDULE 5 COMPLETION REQUIREMENTS Part 1 Services AvailabilityICT Handover Requirements Services AvailabilityICT Handover Requirements shall mean that: the Works (excluding the Post Completion Works) have been provided in accordance with the Facilities RequirementsOutput Specification and the Construction Proposals, and any relevant planning approvalsGood Industry Practice, Guidance, all Necessary Consents, all applicable Authorities’ Policies and Legislation; the Works (excluding the Post Completion Works) have been designed, constructed, remodelled or refurbished in the forms and materials described and as approved in any planning approvals and the Facilities RequirementsOutput Specification and Construction Proposals; each Area (excluding any Areas that are the subject of Post Completion Works) has been completed, finished and laid out in accordance with the standards and provisions set out in the Area Data Sheets that form part of the Facilities RequirementsOutput Specification; the Buildings have been located on each Site, together with external hard and soft play and landscaped areas (excluding any Areas that are the subject of Post Completion Works), and with the sports and recreational facilities as shown in the Facilities RequirementsOutput Specification and the Construction Proposals and as approved in any planning approvals; external fencing, gates, security equipment, vehicular and...
Authority’s Requirements. This FSC covers effort to enable Capgemini to initiate the service. Ongoing service charges are covered separately under CCN058. Both FSC and CCN need to be signed in order to proceed. Xerox software will be hosted on virtual server infrastructure in the LIVE environment. The software will be integrated with Service Desk for automated alerting, remote monitoring and management. It will be configured to communicate with the Xerox service (via internet) and all agreed devices on the LIVE estate. Testing will verify build of server, network connectivity and the ability to monitor agreed Xerox print devices in the Xerox software GUI. Provision of a service based on the following service description: T1 and T4 Service Desk support for scoped Xerox devices including FTF utilising Xerox diagnostic software Interface to Xerox T2 support for technical problems and fault escalation User communication upon printer faults via email (printer up/down comms to site distribution lists using email templates) Escalation service to IM Services for Xerox faults exceeding SLA Provide consumable swap out service through ICM (Phoenix) Provide Incident/Request monthly reporting via JSRF Capgemini will work with Xerox to ensure all agreed Xerox print devices are asset tagged. The corresponding tag number will be added to HIMSys. General Assumptions: The Xerox software will be “Xerox Device Agent for Smart eSolutions v3.6”. A.K.A. XDA v3.6 This quote is based on the implementation and support of 3 models: Xerox 4127 Production System copier/printer Xerox ColorQube 9302 Xerox WorkCentre 7525 IM Services will fully own comms for the project and ongoing printing information cascades (BAU). IM Services will fully own the relationship with Xerox. IM Services will ensure that Xerox make available named contacts to coordinate project work and transition of the service. All project work is expected to be carried out Mon to Fri, 8am to 6pm. Any work that is required outside these times will incur additional charges. IM Services will work with Capgemini to develop a non-functional requirement specification for the project. Implementation Assumptions: Any remediation beyond changes identified in this FSC to the infrastructure required to enable this software to function are not included in this FSC. No packaging or automated delivery of XDA software is required. There will be no need for Global Crossing to perform any actions to allow the necessary data routing between subnets. BT will only n...
Authority’s Requirements. Introduction The TS2000 Oracle HR interface project was halted during 2011 and various deliverables had been produced up to that point. In order to complete the project Capgemini will review those deliverables and produce the additional ones listed below in order to obtain approval to implement the interface into the LIVE environment. Capgemini will liaise with the 3rd party vendor Xxxxxxx Xxxxx Ltd (CHL) to understand how the interface is designed and how they intend to integrate with the Oracle HR database provided by the Oracle on Demand service. Capgemini will then provide suitable development and test environments that will enable the required level of testing to be done prior to LIVE implementation. Requirements and Design Capgemini will review the existing requirements and design documentation and update where necessary prior to obtaining approval at the Capgemini and Agency design approval boards. The HLSD will incorporate the Technical Infrastructure Design (TID) and an SIA will be produced. It is understood that access to the new TS2000 application is required for users working remotely via VPN. The BRS will be updated to include this requirement and the work to enable connectivity via the VPN will be included in the project scope. Environment build and software deployment Based on the design, Capgemini will build the required development and test environments to enable the appropriate level of testing to be carried out. All environments will be built on the Windows Server 2008 R2 and SQL Server 2008 R2 platform. A development environment will be built and access will be provided for the CHL developer from the Capgemini Aston office. Upon receipt of the new TS2000 software from CHL it will be deployed into the development environment by Capgemini working alongside CHL. A subset of the HR data from the Oracle on Demand database will also be deployed into the development environment. The SIT and UAT environments will be built based on the development environment. A controlled deployment will then take place into the SIT/UAT environment prior to testing. The VOTE environment will be built to enable OAT to take place. Testing Capgemini will review the existing Test Approach and update where necessary prior to obtaining approval from the Agency. Test plans and test scripts for SIT and OAT will be produced and incorporated in the Test Approach document in order to reduce the number of documents that require sign-off. The UAT plan and scripts will be pr...
Authority’s Requirements. Scope definition The scope of this work is for the development, test and implementation into live on the Authority’s estate of the Provider Access solution as defined in: Provider Access Technical Detailed Solution Design (DSD) (See section 4.0 Associated Documents ref 3) Provider Access Business Detailed Solution Design (DSD) (See section 4.0 Associated Documents ref 4) The software will be tested during development sprints and System Integration Testing (SIT) for compliance to the DSDs (See section 4.0 Associated Documents ref 3 and 4) and tested during UAT and OAT for compliance to the BRS (See section 4.0 Associated Documents ref 1) in accordance with the Testing Approach document (See section 4.0 Associated Documents ref 6) and put live in accordance with the STaR process. The Contractor will attend weekly checkpoint meetings and monthly steering boards which will be arranged by the Authority. Contractor will also produce a weekly highlight report, which will follow the account standard. PIS In light of the impact on Providers and the high visibility of the Provider Access project a phased roll out is planned at the end of the release 1 build. This FSC is based on the rollout taking the form of a single release of the R1 solution and lasting for a period of six weeks . PIS support is planned for this six week period plus a further two weeks. No further releases are included in this FSC. Performance Analysis A Performance Analysis activity will provide an indication of performance for NFRs in line with the performance analysis approach described in the Test Approach (See Section 4.0 Associated Documents ref 6) and as described in the Performance Analysis Report Product Description (See Section 4.0 Associated Documents ref 5). Authority Associated Projects In addition to this FSC, other Authority projects are also necessary to be completed in order for this FSC to be completed, as clarified in authority obligations. Deliverables The project will deliver the contractual deliverables listed in section 1.2 in accordance with the Product Descriptions (See section 4.0 Associated Documents ref 5) however in order to comply with the Service Gateway and STaR processes the project will also create the following supporting deliverables. These supporting deliverables do not form contractual deliverables under this FSC that require Authority approval, however they will be produced as part of the Service Gateway process.Item Product 1 Service Transition & Review (ST...
Authority’s Requirements. If required under the terms of the AASC Contract the Landlord shall enter into a Sub- Contractor’s Agreement with the Authority and the Tenant in the Authority’s then current form
Authority’s Requirements. This is a change request to the Two Factor Authentication Project - The technical solution to achieve the change will involve the following steps - Add AVG to the UAG list of Anti Virus checked for on connection to the UAG Portal - this will be done by modifying UAG scripts and configuration as needed. This should be carried out in DTE first before applying the changes to LIVE. Test the current version of Free AVG with the above implementation and validate if this works correctly as intended by the request. Regression Testing on rest of the UAG functionality needs to be carried out in DTE. Note that it is expected that the Version of the AVG Software may not be recognised (e.g. version 2011) which will lead to a limitation in checks that can be performed. So the Client validation rules will only check that (i) the AVG Software is running and (ii) latest signatures no older than 14days are installed. This change will be implemented using the built-in UAG default definition of AVG, without using any custom code or any additional configuration required on top of including the AVG. As a result of this Change Request, the following documents will also need updating - Modify the TFA Test Plans, Update the TFA TID and associated Architectural documentation with the addition of AVG
