Statement of Requirement Sample Clauses

Statement of Requirement list all of the Authority’s Requirements, specifications or agreed features of the Future Service to be performed.
Statement of Requirement. CTLBC/1627
Statement of Requirement list all of the Authority’s Requirements, specifications or agreed features of the Future Service to be performed. The Authority has been aware that several projects are at varying stages of advancement and development in their plans to consume the IdAMS (Identity and Access Management System) service. The scope of this FSC is to carry out an Initiation Phase to capture the IdAMS requirements for the following 5 projects: Provider Access (Utilise existing requirements and validate) DCFT LRSr10 NCS - Learner Portal EFA - IM Portal Each of the projects should have a predefined set of requirements for authentication which these projects are looking to IdAMS to provide. IdAMS is currently functioning but without any further work it will be unable to meet the requirements of the projects stated above. To address the risk of five individual projects all attempting to make changes to one system the Authority will be establishing a single delivery vehicle for all of these work streams, or sets of IDAMS requirements. The scope of the Initiation Phase is: Capture the IdAMS requirements for the applications in scope Functional Non Functional Where applicable, documenting how IdAMS is currently consumed by the application/s Capture the current status and functionality of the IdAMS solution Provide recommendations on any changes required to the current IdAMS solution, to meet the consuming systems requirements Document the current environments in place (DTE, VOTE & LIVE) and provide details of any environmental changes required
Statement of Requirement. CTLBC/2128
Statement of Requirement list all of the Authority’s Requirements, specifications or agreed features of the Future Service to be performed. 1.1.1 The National Apprenticeship Service (NAS) are seeking to make the following changes to their Apprenticeship vacancies system to align with restructuring and policy changes being introduced. The critical success factor for this project is the delivery to the expectations of the business before the end of January 2012. This FSC will cover the Elaboration phase of the project. A key factor is the completion of the Deliverables identified in Section 1.2 – sign-off of these is the mechanism by which Stage 2: System change depends. 1.1.2 Changes to the system required for January are described below. Geography changes There have been changes to the geography structure which affect the ability to access, allocate and record data in the system as it stands today due to the introduction of divisions and the change to regions and area’s The Apprenticeship vacancies system is moving to be a centrally co-ordinated function, but with geographically based management. This will require the system to show Divisional and area geography for NAS users. Due to the physical geographical location of NAS Apprenticeship vacancies teams, there will be a need for teams, wherever they are based to be able to also view and manage the Apprenticeship vacancies system not only for their Division and Area, but to also support and undertake work within the system for other Divisions and Areas. Impact of Minimum Contract Value (MCL) To understand and accurately reflect the changes to how Providers will be contracted with and manage vacancies as a result of the introduction of Minimum Contract Value. This is where Providers will only hold contracts to deliver provision if they have a contract value over a certain amount. The system will need to show both the vacancies managed by the main contractor, but also the relationship hierarchy with vacancies managed by a sub-contractor. There will be instances where for some provision, a Provider is a main contractor but for other provision they need to be linked to another provider as they are a sub-contractor or part of a consortium arrangement. In addition Apprenticeship vacancies takes a feed of Provider information from PIMS and will therefore also need to align with the changes to PIMS following MCL changes Hierarchy Roles in LASS Create new SFA hierarchy roles in LASS for Av to use. e. g. Av:SFA Regional:User Approver, Av:S...
Statement of Requirement list all of the Authority’s Requirements, specifications or agreed features of the Future Service to be performed. To initiate the Centralised Contract Management (CCM) 2013/14 Release project. The Authority and the Education Funding Agency have a number of requirements for the provision of contracts for the academic year 2013/14. The key requirements identified in the supporting business case are: reflect policy changes made by BIS and the Skills Funding Agency including the following; reflect requirements to introduce provision for 24+ loans. 24+ Advanced Learning Loans (ALL) is driven out of the government papers: “Skills for Sustainable Growth” and “Investing in Skills for Sustainable Growth” (November 2010). support delivery of funding simplification for the Skills Funding Agency. Simplification is critical to enabling an autonomous and responsive system and it recognises that colleges and training organisations are in the best place to identify, interpret and then respond to learners’ needs within their available resources. reflect policy changes made by DfE and the Education Funding Agency including but not limited to the changes required to support academies and direct school grants. For the Authority the project will consider the following: Funding Stream Configuration - 2013/14 rollover (includes funding simplification) 24+ loans (incl. Loans Bursary) CCM Contract Process Improvement Support of NFF Programmes/Deliverable selection/catalogue Changes indentified for future releases in 13/14 that may require consideration/set-up in Release 1. ( For example, Funding Claims, performance management, ILR changes, ESF ) For the Education Funding Agency the project will consider the following: 2013/14 Roll Forward Process streamlining / automation General During the initiation we will assess the anticipated current and future contract volumes for both agencies and provide a recommendations paper for consideration, outlining the findings. Consider the options for upgrades to the core projects to deliver general improvements to the project retain the product within the existing support agreement an upgrade plan for achieving this avoiding disruption to dates along the critical business cycle. Access the ‘quick-wins’ that can be delivered as part of the service enablement work It is expected that as an output of the initiation and elaboration phase a document will be produced detailing a proposal for delivery. Only 1 (draft) version of the proposal is requir...
Statement of Requirement list all of the Authority’s Requirements, specifications or agreed features of the Future Service to be performed. As per attached Proposal: The replacement of the existing WiFi infrastructure at the National Office in Coventry. The expectation is that the requirement will be placed (via the EcoSystem) with Selection Services. The existing service is unable to support the volume of users and the subsequent demand for services. The access points are of an older generation which are no longer able to support the technological advances and demand for resources made by modern client and hand held technology. In short, the existing WiFi infrastructure should be considered ‘end of life’ and no longer fit for purpose.
Statement of Requirement list all of the Authority’s Requirements, specifications or agreed features of the Future Service to be performed. The current FREE AVG Anti-Virus programme should be added to the list of AV software that is deemed valid by the soon to be deployed UAG Portal. This addition should be effective by UAG Go Live.
Statement of Requirement list all of the Authority’s Requirements, specifications or agreed features of the Future Service to be performed. The Authority requires the Contractor to provide a proposal for the delivery of Match and Claim 2012/13 Rollover project in accordance with the deliverables from the Initiation and construction phase FSC2187 and associated Contract Change Notes. The scope of this release will consider the following priority areas in order to support business continuity for the 2012/13 academic year: Article 16 Auditor recommendations 12/13 ILR Specification changes CODA changes as a result of the introduction of the new Skills Funding Agency organisation structure Upgrade Match and Claim components to use .NET v4 The Contractor shall aim to: start deployment on 20/09/2012, and have systems ready on 25/09/2012. The scope of this FSC includes the production of the standard control documents listed in Section 1.2 – Deliverables, and the development, testing and deployment of “Match and Claim” components into LIVE. Post Implementation Support is also to be delivered.
Statement of Requirement list all of the Authority’s Requirements, specifications or agreed features of the Future Service to be performed. The Authority wishes to migrate their ~800 BlackBerry users from the current Contractor provided BlackBerry Enterprise Server to a fully managed Vodafone BlackBerry service. This FSC is designed to fund the activities necessary to migrate the users, decommission the current BlackBerry Enterprise Servers, remove/decommission all redundant associated technology, services, processes, procedures and documentation. In addition, assist with the configuration and setup of a dedicated link to Vodafone for the ongoing provision of the Vodafone fully managed service. The Assumption around future support model should be that the Authority will act as ‘prime’ contact for any incidents/problems raised and will manage these through to resolution. The Contractors responsibilities will be to respond to any Exchange related incidents raised by the Authority. In order to ascertain costs it is anticipated that the Contractor will need to work with the Authority and Vodafone to define specific requirements. The Authority contacts will be Removed as Reserved Information The Vodafone contact will be Removed as Reserved Information. See contact details below.