Prepared for MOFA
Statement of Work
SCCM 2012 Deployment
Prepared for
MOFA
Wednesday, 4 April 2012
Prepared by
Aydin Demir
Senior Consultant
Prior to the parties indicating final agreement by signing a Work Order, the information contained in this document represents the current view of Microsoft on the issues discussed as of the date of publication and is subject to change. Furthermore, prior to the signing of the Work Order, this document should not be interpreted as an invitation to contract or a commitment on the part of Microsoft. After the Work Order has been signed, changes to this document will be managed through the Change Management Process described in this document.
IF THIS DOCUMENT IS INCORPORATED BY REFERENCE INTO A WORK ORDER, ALL WARRANTIES APPLICABLE TO THE WORK ORDER APPLY TO THIS DOCUMENT. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.
The descriptions of other companies’ products in this document, if any, are provided solely as a convenience to aid understanding and should not be considered authoritative or an endorsement by Microsoft. For authoritative descriptions of any non-Microsoft products described herein, please consult the products’ respective manufacturers. © 2011 Microsoft. All rights reserved. Any use or distribution of these materials without the express authorization of Microsoft is strictly prohibited.
Microsoft and Windows are either registered trademarks or trademarks of Microsoft in the United States and/or other countries.
Page ii
Statement of Work, SCCM 2012 Deployment,Prepared by Aydin Demir
"MOFA - SCCM Deployment SOW Ver 3.0" last modified on 4 Apr. 12, Rev 3
Prepared for MOFA
Page iv
Statement of Work, SCCM 2012 DeploymentPrepared by Aydin Demir
"MOFA - SCCM Deployment SOW Ver 3.0" last modified on 4 Apr. 12, Rev 3
Prepared for MOFA
Table of Contents
Introduction 1
1 Project Objectives and Scope 2
1.1 Objectives 2
1.2 Areas Within Scope 3
1.2.1 General Project Scope 5
1.2.2 Software Products / Technologies 6
1.2.3 Environments 6
1.2.4 Training and Knowledge Transfer 6
1.2.5 Testing 7
1.3 Areas Out of Scope 8
2 Project Approach, Timeline and Service Deliverables 9
2.1 Approach 9
2.2 Timeline Error! Bookmark not defined.
2.3 Key Service Deliverables and Acceptance Process 14
2.3.1 Project Service Deliverables 14
2.3.2 Service Deliverable Acceptance Process 15
2.4 Project Governance Approach 17
2.4.1 Part-Time Project Management 17
2.4.2 Communication Plan 17
2.4.3 Issue/Risk Management Procedure 18
2.4.4 Change Management Process 18
2.4.5 Executive Steering Committee 19
2.4.6 Escalation Process 19
2.5 Project Completion 20
3 Project Organization and Staffing 21
3.1 Project Organization Structure 21
3.2 Project Roles and Responsibilities 22
4 General Customer Responsibilities and Project Assumptions 24
4.1 General Customer Responsibilities 24
4.2 Project Assumptions 25
Tables
Table 1: Project Details 3
Table 2: Solution Scope 5
Table 3: Solution Software Required 6
Table 4: Required Environments 6
Table 5: Test types Table 7
Table 6: Defect priorities 7
Table 7: Areas Out of Scope 8
Table 8: Microsoft Activities: System Center Stabilizing and Deployment Phases 12
Table 9: Key Customer Activities 12
Table 10: Key Work Products and Deliverables (Microsoft) 13
Table 11: Key Work Products and Deliverables (Customer) 13
Table 12: Key Phase Assumptions 14
Table 13: Engagement deliverables 14
Table 14: Project Management Activities 17
Table 15: Customer roles and responsibilities 22
Table 16: Microsoft roles and responsibilities 22
Page iv
Statement of Work, SCCM 2012 DeploymentPrepared by Aydin Demir
"MOFA - SCCM Deployment SOW Ver 3.0" last modified on 4 Apr. 12, Rev 3
Prepared for MOFA
Introduction
This Statement of Work (SOW) and any exhibits, appendices, schedules, and attachments to it are made pursuant to the Work Order No. “ “ , the terms of which are incorporated herein by reference, by and between Ministry of Foreign Affairs (“MOFA”) (“Customer”, “you”, “your”) and Microsoft Corporation (“Microsoft”, “us”, “we”, “our) or Microsoft’s affiliate, and sets forth the services to be performed by us related to System Center Configuration Manager 2012. Deployment (“project”). This SOW, together with the Work Order, represents the complete baseline for scope, services, Service Deliverables, and acceptance applicable to this project. All changes to this document will be managed in accordance with the Change Management Process defined below. Any terms not otherwise defined herein will assume the meanings set forth in the Work Order.
This SOW and the associated Work Order expire 30 days after their publication date, unless they have been formally extended in writing by Microsoft.
MOFA requested Microsoft to complete System Center Configuration Manager 2012 design and deployment phases into LAN and internet Networks. This document will provide required details for the work to be delivered.
1 Project Objectives and Scope
1.1 Objectives
The objective of this project is to design and deploy System Center Configuration Manager 2012 to Ministry of Foreign Affairs (MOFA) LAN and internet networks.
Microsoft will deliver green-field deployment of System Center Configuration Manager 2012 to Ministry of Foreign Affairs (MOFA). MOFA has provided the following information regarding current network of internet and LAN:
Internet Network
· Approximately 1050 users, and somewhere around 1150 computers, but it is expected that 900 of them are active
· Single location in Riyadh HQ
LAN Network
· Servers 234
· Desktops 2342 in total including sites (embassies and consulate offices are not included)
Sites:
· MoFA HQ office 1500 - 100
· Dammam site 30 - 50
· Jeddah site 150 - 200
· Makkah site 30 - 50
· Riyadh Diplomatic Quarter site 100 - 150
· IT New Building site 100 - 150
Mostly, client computers are Windows XP SP3 or later, and some of them Vista and Windows 7. Microsoft will include all clients which are in local domain; however, Microsoft will commit on only 1,000 computers in each network. Client computers within the network of the remote embassies will be delivered as a separate scope.
Table 1: Project Details
Project/Work stream / Description /System Center Configuration Manager - SCCM / System Center Configuration Manager (SCCM) will be designed to support servers and client computer for:
▪ Software and Hardware Inventory
▪ Software deployment and patch management;
▪ Designing one 32bit Windows 7 image, deploying on 5 Pilot PCs and address 5 types of different client PC scenario.
▪ Asset and inventory reporting
▪ Desired configuration management
▪ Office 2010 and IE 8/9 Deployment
1.2 Areas Within Scope
Microsoft will provide the following services:
Microsoft will deliver System Center Configuration Manager 2012 deployment to LAN networks by deploying a single primary server including Windows 7 deployment, reporting and software update functionality.
Microsoft will work with MOFA IT Department in Riyadh to deploy identified scope below. All activates will be limited to Windows platform servers and Clients.
SCCM infrastructure will provide the following functionalities:
· Software and Hardware Inventory: By collecting hardware and software inventory data with Microsoft® System Center Configuration Manager 2012, you can build a rich database containing detailed information about the computers in your organization.
· Software deployment and patch management: Configuration Manager 2012. Software Update Management simplifies the complex task of delivering and managing updates to IT systems across the enterprise. IT administrators can deliver updates of Microsoft products, third-party applications, hardware drivers, and system BIOS to a variety of devices, including desktops, laptops, servers, and mobile devices. Internet Based Client Management (IBCM) enables geographically dispersed users that rarely connect to the corporate network to receive software updates securely over the Internet. Automated vulnerability assessment discovers need for patches, and provides updates and reports on recommended actions.
· Automated operating system deployment (Windows 7): Configuration Manager 2012 helps you maximize your cost savings from energy-saving desktops and laptops. New tools to monitor, create, and enforce client power management policies enable administrators to reduce power consumption and reap the resulting financial and environmental rewards.
· Asset and inventory reporting: Configuration Manager 2012 gives you better control over your IT infrastructure and assets. Its asset intelligence technologies that provide administrators with continuous visibility into what hardware assets and software licenses you have, who is using them, and where they are located. Asset Intelligence translates inventory data into information, providing rich reports that help administrators optimize software and hardware usage.
· Desired configuration management: With Configuration Manager 2012. Desired Configuration Management, you can ensure that IT systems comply with desired configuration states to improve availability, security, and performance network-wide. Desired configuration management allows you to assess the compliance of computers against a set of established configurations, such as whether the correct Microsoft Windows operating system versions are installed and configured appropriately or whether prohibited applications are installed. Additionally, you can check for compliance with software updates and security settings.
· Office 2010 and IE 8/9 Deployment: Configuration Manager 2012. Software Distribution simplifies the complex task of distributing applications and updates to desktops, servers, laptops, and mobile devices across enterprise networks. By automating software distribution, Configuration Manager helps to eliminate the inefficient and error-prone process of manually installing applications and software updates
· Mobile Devices: You can deploy the System Center 2012 Configuration Manager client on supported mobile operating systems when the mobile device and site system roles use PKI certificates. When the mobile devices run Windows CE, you must install the mobile device certificate independently from Configuration Manager and then install the client by using a package and program. However, for supported mobile device operating systems, System Center 2012 Configuration Manager can automatically deploy the certificate and install the client. These mobile devices are enrolled by Configuration Manager.
When the Configuration Manager client is installed on mobile devices, you can manage them by using the following features:
· Hardware inventory
· Software installation
· Settings
When you cannot install the System Center 2012 Configuration Manager client on mobile devices, you can use the System Center 2012 Configuration Manager Exchange Server connector to find and manage mobile devices that connect to Microsoft Exchange Server. Because the Configuration Manager client is not installed, management is limited. For example, you cannot deploy applications to these mobile devices. However, you can retrieve some inventory information, define settings and access rules, and issue wipe commands for these mobile devices in System Center 2012 Configuration Manager.
· The Application Catalog and Software Center: The Configuration Manager Application Catalog is a website where users can browse for and request software. To use the Application Catalog, you must install the Application Catalog web service point and the Application Catalog website point for the site.
Software Center is an application that is installed when the Configuration Manager client is installed on computers. Users run this application from the Start menu to request software and manage the software that is deployed to them by using Configuration Manager. Software Center lets users do the following:
· Browse for and install software from the Application Catalog.
· View their software request history.
· Configure when Configuration Manager can install software on their devices.
· Configure access settings for remote control, if an administrative user enabled remote control.
Data collection and capacity will be stored locally and nothing will be shared external parties. Data will be collected in encrypted format.
As part of project scope, default reports will be imported and Microsoft will provide Knowledge Transfer sessions (limited to 12 hours) to use SCCM.
1.2.1 General Project Scope
Table 2: Solution Scope
Solution Component / In Scope Feature / Description/Considerations / Scope Assumptions /Deployment of SCOM Components / o 1 Central Primary Server for internet network
o 1 Central Server for LAN Network
o 5 Distribution points for LAN network (if required) / Required hardware should be ready in deployment phase
Agent Deployment / o Total of 1,000 Agents Deployment (domain joined Windows clients) for internet network and 1,000 agents for LAN network
o Total of 250 Agents Deployment for domain joined Servers / Agents should be up and running
Required ports should be opened for enabling communications.
MOFA will deploy the remaining clients.
Management Packs Deployment, Customization and Configuration / o Software and Hardware Inventory
o Software deployment and patch management;
o Deploying Windows 7 image 32bit and 64bit and deploying on 5 Pilot PCs separately on Internet and LAN network
o Asset and inventory reporting
o Base functionality of Desired configuration management design and deployment
o Office 2010 and IE 8/9 Deployment
Reporting / o Deploy default Reports / Report customizations are not included
Knowledge Transfer Sessions that includes: / o General SCCM Administration Tasks / MOFA project team members should have understanding of All required operational tasks
1.2.2 Software Products / Technologies
Microsoft requires the following software and application media during the project.
Table 3: Solution Software Required
Operating Systems / Core Apps / Databases / Development Languages / Provided by /Windows Server 2008 R2 Enterprise or Standard Edition / SCCM 2012 / Microsoft SQL Server 2008 R2 / English / Customer
1.2.3 Environments
Table 4: Required Environments
Environment / Location / Responsibility / Ready by /Development / Customer Site in Riyadh / Customer / Within 3 weeks of start date
Test / Customer Site in Riyadh / Customer / Within 3 weeks of start date
UAT / Customer Site in Riyadh / Customer / 4 weeks prior to UAT start date
Pre-Production / Customer Site in Riyadh / Customer / 4 weeks prior to UAT start date
Production / Customer Site in Riyadh / Customer / 4 weeks prior to UAT start date
1.2.4 Training and Knowledge Transfer
Microsoft will provide 12 hours of Knowledge Transfer during the project at the customer site in Riyadh. Microsoft recommends official training for complete understanding of Configuration Manager Architecture and features.
1.2.5 Testing
The following testing will be performed as part of this Statement of Work.
Table 5: Test types Table
Test Type / Description / Responsible / Provides Test Data/Cases / Guidance & Support / Environment /Unit Testing / Documenting and executing unit test cases are the responsibility of the developers. Test cases are based upon the Microsoft Functional Specification document. / Microsoft / Microsoft / Customer / Development
System Testing / System Testing focuses on the functionality meeting the design. Test cases are based upon the Microsoft Functional Specification document. Testing duration is time boxed to 5 days. / Microsoft / Customer / Customer / Development
User Acceptance Testing (UAT) / User functionality of key real world scenarios. Test cases are based upon the Microsoft Functional Specification document.Testing duration is time boxed to 3 days. / Customer / Customer / Microsoft / Test
As defects are identified during testing, the Defect Priority will be jointly agreed upon by the Customer and Microsoft. The Microsoft team will triage the defect and fix all in scope P1 and P2 defects. Defect priorities are shown in the following table.