G-Cloud Service Description. Atos: Cloud Professional Services: Requirements Specification

Transcription

1 G-Cloud Service Description Atos: Cloud Professional Services: Requirements Specification

2 Atos, the Atos logo, Atos Consulting, Atos Worldline, Atos Sphere, Atos Cloud, Atos Healthcare (in the UK) and Atos WorldGrid are registered trademarks of Atos SA. June Atos Page ii

3 Contents 1. Introduction G-Cloud Description (used on Portal) Cloud Professional Services Project Lifecycle Atos SI Requirements & Specification Service Requirements Management for Cloud - Approach Transition to Cloud 4 2. Pricing Termination terms 5 3. Service levels 6 4. Service constraints and additional requirements 7 5. On-boarding and Off-boarding 8 6. Backup/Restore and Disaster Recovery 9 7. Service management Technical requirements Information assurance Data restoration / service migration Consumer responsibilities Training Training Services for Cloud 15 Training Material Development Methodology Ordering and invoicing process Financial recompense 18 Appendix A - xxxxxxx A-1 Page iii

4 1. Introduction 1.1 G-Cloud Description (used on Portal) Atos Requirements & Specification Service includes; Business & Systems Analysis, Feasibility Study and Package Evaluation/Selection. Supported by: Methodologies: PRINCE2, MSP, Agile, Waterfall, BPM, TOGAF, ITIL Cloud Proof of Concept & Pilot G-Cloud offers. Supported by: Atos CLAS Consultants Atos Business Analysts Atos Systems Analysts Atos Data Analysts Delivery locations : At Customer Site At Onshore factory At Offshore factory Cloud Professional Services Project Lifecycle Atos has provided a suite of services that enable the organisation to make the best of GCloud across the IT department and throughout the whole project lifecycle. This document covers the service: Atos SI Requirements & Specification Service indicated in the diagram below Page 1

5 1.2 Atos SI Requirements & Specification Service Requirements Management for Cloud - Approach The Atos approach to Requirements Management supports collaborative working that takes the business centric approach to engage stakeholders and establishes an assured foundation for system delivery. The Atos Requirements Management service provides: Assured foundation for the software delivery lifecycle. Globally operated service based on CMMi (RD and REQM) standard processes with defined roles and responsibilities, supported by predefined product deliverables, stage gate checkpoints and a central Requirements Management tool. Forward and backwards traceability is built in from requirement capture through to delivery. Atos Requirements Management approach is based on CMMi (RD and REQM) standard processes with defined roles and responsibilities, supported by predefined product deliverables, stage gate checkpoints and a central Requirements Management tool. Forward and backwards Traceability is built in from requirement capture through to delivery. Requirements Management is carried out in three phases these are: Business Architecture Definition Requirements Development Software Architecture & detailed functional design These three phases are supported by Requirement Traceability, Management and Configuration Control tools and processes Requirements definition and management The process enables: any issues, risks or assumptions regarding the scope to be reviewed and resolved; a contractual basis for delivery; the foundation for acceptance criteria; the Software Architecture and Detailed Functional Design step of the selected lifecycle to be conducted by providing a baselined starting point. Plan and tailor the requirements management process The goal is to avoid majority of rework cost. Atos recommend that: There is adequate stakeholder and end user representation and involvement from all areas of the business within scope All requirements are defined to an agreed minimum level of detail and are subject to both peer and external reviews to confirm that they are within scope, address the business problem and are fit-for-purpose Verification and reviews are held at the earliest point that a coherent set of requirements is defined. Page 2

6 Tailoring is used on cloud projects to ensure that the basic goal of the process is still achieved and the requirement types and product content delivered. Understand the problem and define the strategy The goal is to ensure there is a joint agreement and understanding between the Project Sponsor and the project delivery team regarding the problem that is to be addressed, scope, constraints, the acceptance criteria for the solution and the process for information gathering. This step also confirms that there is buy-in and active support for the project. Capture and define requirements The goal is to ensure that all constraints, interfaces, functional and nonfunctional needs are captured and defined at the required level of detail. The Requirements Analyst groups requirements under types and subtypes to allow the RM tool to be used to capture all information required in the product. They will engage the relevant stakeholders according to the RACI needs of the product deliverable. Verify requirements The goal is to confirm the accuracy and completeness of the requirements captured. Formal verification activities lead to formal base-lining of the requirements. The Requirements Analyst will keep a trail showing how comments have been resolved and relationship between requirement version status and verification; they will also update the requirement with the verified description. Approve and baseline requirements Approval and base lining verifies that the requirements captured, defined and verified meet the agreed goal of defining the capability to which a solution must conform at a level of detail and completeness that enables compliance to be demonstrated. The requirements are placed in a base lined status after which formal change control processes are invoked. Apportion for phased delivery The goal is to define and agree how the requirements are to be packaged up for delivery to the customer. Working with our client, the Requirements Analyst will establish the business critical or high benefit requirements & those which are of lower urgency or criticality. Manage requirements The goal is to ensure that all requirements can be traced back to source and forwards to further elaborate the requirement, test conditions and forward to delivery. This process ensures that all changes to requirements are assessed to confirm scope, understanding and feasibility of change and those changes can be traced to the requirements that are impacted by the change. Page 3

7 1.2.2 Transition to Cloud Atos have a fully proven Transition to Support Methodology to allow us to seamlessly transition from the existing support arrangements with minimum disruption to client s systems and users. This support methodology is known as CSDM (Continuous Service Delivery Model) and is based on the principles of ITIL (IT Infrastructure Library), the industry standard for delivery of IT Service management. The Transition Methodology shares our approach to Project and Programme management and includes: Transition initiation Transition monitoring and control Transition reporting Transition risk and issue management Transition change control Transition lessons learnt To maintain good practice and common approach Atos Transition Practitioners use the same tools, follow the same work flow, and use the same templates and processes. However, for transition to a Cloud environment we also have the ability to fit with our client s methods and tools rather than expect them to adopt our approach. Page 4

8 2. Pricing This section describes the pricing, including unit prices, volume discounts (if any), data extraction etc.) PLEASE NOTE: Units of purchase stated are by day at the SFIA rate card, typically grade 5-6 (ONSHORE Solution Development and Implementation) for Requirements Analysts and Senior Requirements Analysts. However in some instances this could be varied. Please contact us to agree the exact requirement scope and number of days. PLEASE NOTE: Units of purchase stated are by day at the Application SFIA rate card, typically grade 5-6 (ONSHORE Service Management) for Transition and Senior Transition Managers. However in some instances this could be varied. Please contact us to agree the exact requirement scope and number of days 2.1 Termination terms This section details any terms which will be applicable in event of termination of service, either by consumers (i.e. consumption of the service), or by the Supplier (in event of the removal of the G-Cloud Service). Please refer directly to Atos standard Terms and conditions. Page 5

9 3. Service levels This section describes the Service Levels applicable (e.g. performance, availability, support hours, severity definitions etc.) Please refer directly to Atos standard Terms and conditions. However in some instances this could be varied. Please contact us to agree the exact requirement scope. Page 6

10 4. Service constraints and additional requirements This section identifies any constrains placed upon the service, such as maintenance windows, level of customisation permitted, schedule for deprecation of functionality/features etc. Plus where any additional service requirements would be stated i.e service wraps/ additional hardware purchase not covered within this offering direct Not Applicable Page 7

11 5. On-boarding and Off-boarding This section describes the scope service for on-boarding and off-boarding services provided, describing the processes involved and respective responsibilities. Not Applicable Page 8

12 6. Backup/Restore and Disaster Recovery This section details the level of backup/restore and disaster recovery that will be provided. Not Applicable Page 9

13 7. Service management This section describes the service management wrapper which is provided with the service offering. i.e user support desks, incident mgt etc Not Applicable Page 10

14 8. Technical requirements This section describes any service dependencies and detailed technical interfaces, e.g. client side requirements, bandwidth/latency requirements etc. Not Applicable Page 11

15 9. Information assurance This section details the Impact Level (IL) at which the G-Cloud Service is accredited to hold and process information. Not Applicable as this is not a software or hardware offer. Page 12

16 10. Data restoration / service migration Not Applicable as this is not a software or hardware offer. Page 13

17 11. Consumer responsibilities This section defines any responsibilities which will apply to the consumer of the service. Not Applicable Page 14

18 12. Training This section defines any Training services offered in association with or as part of the service offering Training Services for Cloud Atos Training Services are designed with your business goals in mind. We work closely with our customers from the outset of a training requirement to understand the reasons for the training and the expected business benefits. Understanding your organisation, your strategies, objectives and goals is critical to the overall success of the training solution This enables us to design and implement focused learning solutions that take into account your culture, business environment and the impact of the changes Effective training is an integral part of the overall solution and without it the anticipated return on investment is unlikely to be realised Our approach ensures our solution builds awareness, knowledge and understanding. This improves ownership and commitment, increasing the user s confidence in and enthusiasm for the new working practices Our solutions have to be fit for purpose, and we adopt an innovative and flexible approach to deliver training programmes to address your requirements Typically the Training Service may cover the following training activities:- Training Needs Analysis Design and Development of training material including on-line training materials such as e-learning programmes Training Delivery Training Support Services such as floor walking, and one-to-one training Training Administration Training Communication Programmes Training Management Evaluation of training Training Material Development Methodology The Atos Training Development Methodology is a collaborative approach to developing training materials. This methodology has proved to be successful in developing training courses, and materials for a wide variety of customers. The Atos Training Development Methodology covers the following activities: Scope Definition Content Development Preparation of Materials Development of Training Courses Sign off at each stage Page 15

19 PLEASE NOTE: Units of purchase stated are by day at the Application SFIA rate card, typically grade 4-5 (ONSHORE Client Interface) for Trainers and Lead Trainers. However in some instances this could be varied. Please contact us to agree the exact requirement scope and number of days. Page 16

20 13. Ordering and invoicing process This section describes the ordering and invoicing processes for customers wishing to take up the service offering. To order this service please visit our website contact the named individual associated with this offering to discuss your specific requirements further. Page 17

21 14. Financial recompense This section defines any financial recompense model which will be applied for not meeting service levels. Not Applicable Page 18

22 Appendix A - xxxxxxx xxxxxx Page A-1 December 2011