leak....Introduction
Project Objectives and Scope
Objectives
The Bank of Tokyo-Mitsubishi UFJ line of business will separate from the bank primary infrastructure. MC S Services will support Bank of Tokyo-Mitsubishi UFJ in the development of a migration infrastructure and process for the directory separation project.
The infrastructure build out consists of two regional datacenters.
Areas within Scope
Microsoft Services will provide The Bank of Tokyo-Mitsubishi UFJ with Envisioning and Scoping Workshops, infrastructure consulting and design services for:
1. Active Directory Assessment of the source and target forests
2. Directory / Mail Migration and Co-existence
3. Directory Migration Strategy and Process
4. Creation of Migration Infrastructure Test Plans
5. Testing of the Migration Infrastructure Processes in the lab.
a. Source Environment Changes
b. Target Environment Changes
c. ADMT Toolset installation and configuration
d. GPO Configuration
e. Password Synchronization
f. Trust Relationships
g. SID History Configuration
h. Network/DNS Resolution
i. User Migration
j. Group Migration
k. Security Translation
l. User Profile Migration
m. Workstation Migration
n. Logon scripts Evaluation
Areas Out of Scope
• Stabilization phase of the of solution proposed
• Deployment phase of the solution proposed
• Application Compatibility Testing
• Meta-directory and GAL Synchronization design
• Development of Logon Scripts
• Migration of applications and file server resources
Anything not excluded in this section and not listed in the above “Areas within Scope” is considered out of scope for this SOW.
Project Approach, Timeline and Service Deliverables
Microsoft Solutions Framework
We will leverage the Microsoft Solutions Framework (MSF) to execute this SOW. MSF represents a proven solution development approach that provides for well-defined phases that take into account development of requirements, architectural design, detailed software design, software development, system testing, and managed release cycles.
MSF organizes the solution approach into five distinct phases during the project lifecycle.
Envisioning: Envisioning involves creating a business vision and defining the scope of work necessary to bring the vision to reality.
During the Envisioning phase MCS will provide an Envisioning conceptual design document that covers the technologies areas listed below:
Active Directory Envision Phase
o Envisioning and Scoping Workshops
o Review Exchange Configuration
o Assess Exchange Requirements for directory co-existence
o Base Environmental Validation
o Active Directory Migration
o Technical QA
Planning: Planning continues through the development of detailed functional requirements, system and application architectures, the user interface prototype and a detailed project plan for the remainder of the project.
During the planning phase, MCS will deliverables covering:
Active Directory Validation/Baseline
o Source Active Directory Environment
o Target Active Directory Environment
o User Principal Analysis
o Group / Group Expansion Analysis
o Trust Relationship Analysis
o Computer Account Analysis
o Security Preparation Analysis for Migration
o Functional Specification
o OU Analysis
o Domain Controller Security and GPO Analysis
o Site & Replication Analysis
o Security Group Analysis
o DC Server Build Analysis
o Application Dependencies
• Migration & Deployment Design
o User/Group Migration
o Workstation Migration
o Member Server Migration
o Infrastructure Server Migration
o Directory Consolidation Plan
o Mail Migration
o Test Plan Documentation
o Login Scripts
o Printer Discovery
Development/Build: The Development phase begins with the first iteration of development and culminates with the “functionality complete” milestone (or Beta release).
Migration Test Plan and Configuration Guide
o Develop a test plan for Active Directory Migration
Migration Infrastructure
User Migration
Group Migration
Workstation Migration
User Profile Migration
Application Dependencies
Mail Profile Generation
Stabilization: The Stabilization phase involves testing and acceptance.
Stabilization Phase activities are out of scope in this statement of work
Deployment: The Deployment phase includes deployment of the core technology and site components, transitioning of the project to operations and support, and obtaining final Customer approval of the project
Deployment Phase activities are out of scope in this statement of work.
Timeline
The project will be divided into phases and milestones as depicted below. This timeline is an estimate only which is based on our current planning assumptions and may change during the course of the project.
Project Phase Timeline
Envision and Assessment 60 Hours
Design 100 Hours
Development/Test 160 Hours
Key Service Deliverables and Acceptance Process
Key Project Service Deliverables
The following is a list of the key project service deliverables that will be delivered within this SOW, which must be formally reviewed and accepted. At the beginning of each phase, Microsoft and Customer will jointly define in writing the Acceptance Criteria for each deliverable.
Project Phase Service Deliverable Name Service Deliverable Description
Envision Directory Services Envision Document Envision document captures Mitsubishi Securities current state of the directory services source, target environment, migration stated goals, envision and conceptual technology architecture of the migration infrastructure to support Mitsubishi directory separation.
Design Migration Infrastructure Design Document Technology Design document provides detail design and architecture for the migration infrastructure technology components in scope used to enable Mitsubishi directory separation requirements as outlined in the Directory Services Envision Document.
Development/Build Migration test plan and configuration guide. This document provides case tests and configuration guide for the directory migration process. This includes conceptual design for the POC/Lab environment, and test cases for users, groups, workstations, profile migrations, source and target environment preparations.
Service Deliverable Acceptance Process
At specified milestones throughout the project, we will deliver completed project service deliverables for review and approval. Service deliverables shall be accepted or rejected within 30 consecutive business days from the time of submittal for acceptance. Service deliverables shall be deemed accepted in the absence of review or response of acceptance within this specified time. The use or partial use of any service deliverable constitutes acceptance of that service deliverable. Feedback supplied after the review period will be evaluated as a potential change of scope and shall follow the Change Management Process outlined in this SOW.
The Service Deliverable Acceptance Process is described below.
Submission of Service deliverables
The Microsoft Project Manager, or his designee, will prepare a Service Deliverable Acceptance Form (see Exhibit section) and forward with the respective service deliverable to the Customer Project Manager, or Customer designee, for consideration.
Assessment of Service Deliverables
The Customer representative will determine whether the service deliverable meets the requirements as defined in this SOW and that the service deliverable is complete. Additional work on, or changes to, an accepted service deliverable that are requested by the Customer will managed through the Change Management Process.
Acceptance / Rejection
After the review, the Customer will either accept the service deliverable (by signing and dating the Service Deliverable Acceptance Form) or will provide a written reason for rejecting it and will return the Service Deliverable Acceptance Form to the Microsoft team. If feedback from multiple Customer representatives is received, then the Customer Project Manager, or Customer designee, will consolidate that feedback before delivering it to the Microsoft team.
Correction of Service Deliverables
Microsoft will correct in-scope problems found with the service deliverable and will address the correction of out-of-scope changes according to the Change Management Process. Microsoft will submit a schedule for making changes to the service deliverable within two (2) business days of receiving a rejected Service Deliverable Acceptance Form. Once Microsoft corrects all previously identified in-scope problems, the service deliverable will be deemed accepted.
Monitoring and Reporting
The Microsoft project team will track service deliverable acceptance. Updates on service deliverable acceptance will be included in the status report and discussed in the status meeting. Service deliverable acceptance issues that cannot be resolved will be elevated to the Project Steering Committee.
Communication Plan
A formal process will be employed to facilitate communication during the project. There will be two key vehicles for providing this communication: a weekly status report and an hourly status meeting every week.
The Microsoft Project Manager, working in conjunction with the Customer Project Manager, will compile status reports with the frequency defined above for distribution to both Customer and Microsoft management.
Meetings will be held with the frequency defined above to review overall status, the project schedule, and open issues noted in the status report.
Issue/Risk Management Procedure
The following general procedure will be used to manage project issues and risks:
Identify and document
Assess impact and prioritize
Assign responsibility
Monitor and report progress
Communicate issue resolution
A mutually agreed upon issue escalation process will be defined at the outset of the project.
Change Management Process
During the project, either party may request in writing additions, deletions, or modifications to the services described in this SOW (“change”). We shall have no obligation to commence work in connection with any change until the estimated fee and schedule impact of the change is agreed upon in a written Change Request Form signed by the designated Project Managers from both parties.
Upon a request for a change, we shall submit the change on our standard change Request Form describing the change, including the estimated impact of the change on the project schedule, fees and expenses. The Change Management Process that will be employed is defined below. Both parties agree to follow this process and to use the Change Request Form.
Identify and document
Assess impact and prioritize
Estimate required effort
Approve / disapprove
Assign responsibility
Monitor and report progress
Communicate change resolution.
Within 5 consecutive business days of receipt of the proposed Change Request Form, you shall either indicate acceptance of the proposed change by signing the Change Request Form or advise us not to perform the change. If you advise us not to perform the change, then we shall proceed only with the original services. In the absence of your acceptance or rejection, we will not perform the proposed change.
Project Completion
The project will be considered complete, when any of the following are met:
1. All of the service deliverables identified within this SOW have been completed, delivered and accepted or deemed accepted, including approved Change Request Forms;
2. The fee provisions of the Work Order have been met; or
3. This agreement is terminated pursuant to the provisions of the agreement.
Project Organization and Staffing
General Customer Responsibilities and Project Assumptions
General Customer Responsibilities
Our delivery of the services are dependent on your involvement in all aspects of the services, your ability to provide accurate and complete information as needed, your timely and effective completion of the responsibilities as identified herein, the accuracy and completeness of the Assumptions, and timely decisions and approvals by your management. In addition to any Customer activities identified in the Approach section, you will perform the tasks, furnish the personnel, provide the resources or undertake the responsibilities specified below.
This Customer representative will:
• Work with the Microsoft Project Manager to deliver the Project on schedule.
• Manage Project plans, schedules, and so on
• Make key day-to-day decisions and provide a single point of contact
• Accept deliverables.
• Provide, as needed, personnel knowledgeable in the current Customer systems.
• Provide business user representatives as required by project plan.
• Provide, unless otherwise agreed to in writing, all test cases, test data, procedures, and personnel needed to conduct the acceptance testing of the solution, including interfaces.
• Provide necessary work site access as well as necessary Customer systems logons and passwords.
• Provide access to other materials and resources as needed, and as advised by us in advance.
• Provide suitable work area spaces with desks, chairs, and telephones, and so on
• Provide LAN connections that enable access to the Internet and e-mail for Microsoft on-site team.
• Assume responsibility for management of all non-Microsoft managed vendors.
• Provide access with proper licenses to all necessary tools and third party products required for Microsoft to complete its assigned tasks.
• Acquire and install the appropriate server capacity to support the development, test and production environments.
• In performing our services under this SOW and the applicable WO, we will rely upon any instructions, authorizations, approvals, or other information provided to us by your project Manager or by any other personnel identified by your Project Manager.
In performing our services under this SOW and the applicable WO, we will rely upon any instructions, authorizations, approvals, or other information provided to us by your project Manager or by any other personnel identified by your Project Manager.
Project Assumptions
The Services, fees and delivery schedule for this project are based upon the following assumptions.
• Customer will provide lab equipment for validating solution in the lab environment.
• Microsoft ADMT 3.1 migration tools will be used for inter-forest directory migration.
• Based on initial requirements, no directory synchronization (Meta directory) is required to support mail migration. Meta-directory design is out of scope for this engagement.
• Existing workstations will be preserved. Workstations will be migrated (joined) to the new infrastructure.
Budget Estimate
MCS will provide Time and Materials consulting services. The estimated costs for this project are below:
Resource Rate/Hour Hours Fees
Active Directory consultant $275.00 320 $88,000.00
Program Manager $275.00 32 $8,800.00
Subtotal fees 352 $96,800.00
Estimated expenses (*) $10,000.00
Total $106,800.00
(*) Mitsubishi Securities will only be invoiced for actual expenses which will be billed at cost
All content on this website is automatically licensed under a Creative Commons Attribution license. You are free to redistribute and/or remix it, but you have to credit the author, or, if the author is unknown ("Anonymous"), place a backlink to the corresponding page on AnonNews and attribute it to "Anonymous".
