Common use of Statement of Requirement Clause in Contracts

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

Appears in 2 contracts

Sources: Future Services Agreement, Future Services Agreement