Mako-Cloud Onboarding Project

Mako

Get Started. It's Free
or sign up with your email address
Rocket clouds
Mako-Cloud Onboarding Project by Mind Map: Mako-Cloud Onboarding Project

1. Objectives

1.1. Cloud base

1.1.1. In scope

1.1.1.1. Firewall service

1.1.1.1.1. First line

1.1.1.1.2. Second line

1.1.1.2. Monitoring virtual applicance

1.1.1.3. Internet service

1.1.1.3.1. Internet line with 20 Mbits

1.1.1.3.2. DDoS Protection

1.1.1.3.3. Site to site VPN

1.1.2. Out of scope

1.1.2.1. On-premise Firewall

1.1.2.2. Public DNS

1.1.2.3. Public customer certificate

1.2. IaaS

1.2.1. In scope

1.2.1.1. VM provisioning (7)

1.2.1.2. Configure backup to tape job

1.2.1.3. Coordinate business app re-installation on new VMs (8 hours)

1.2.2. Out of scope

1.2.2.1. OS Licences

1.2.2.2. Deployment of Antivirus

1.2.2.3. Deployment of Monitorinf solution

1.2.2.4. Monthly patching

1.3. Desktop as a Service

1.3.1. In scope

1.3.1.1. Installation of Desktop control layer

1.3.1.2. Integration of the Desktop platform environment with the VMware ESX environment

1.3.1.3. Coordinate business app re-installation on new VMs (8 hours)

1.3.1.4. Natrive print drivers installation

1.3.1.5. Deployment of the 30 VDIs

1.3.2. Out of scope

1.3.2.1. Business applications' cleints

1.3.2.2. Configuration of end-user devices "on premise"

1.4. AD/O365

1.4.1. In scope

1.4.1.1. Deployment of new Active Directory inside SSL Cloud platform

1.4.1.2. Preparation of Office 365 and Exchange Online

1.4.1.3. Azure AD Connect Deployment

1.4.1.4. Active Directory Migration

1.4.1.5. Exchange Online Migration

1.4.1.6. Documentation

1.4.2. Out of scope

1.4.2.1. Any other applications available in Office 365

1.4.2.2. Definition of ACLs, Security group and Distribution lists

1.4.2.3. Decommissioning of old infrastructure

1.4.2.4. All actions not mentioned in the “in scope” section

2. Project Goals

2.1. Cloud Onboarding

3. Project Team

3.1. Customer

3.1.1. IT Team

3.1.1.1. Damien MATTUCCI

3.1.1.1.1. IT Manager

3.1.2. COPIL

3.1.2.1. Alain WAGNER

3.1.2.1.1. Managing Director

3.2. SSL

3.2.1. IT Team

3.2.1.1. Mike DELANNOY

3.2.1.1.1. Project Manager

3.2.1.2. Benoit MORIN

3.2.1.2.1. Network & Security Engineer

3.2.1.3. Sebastiano INGALLO

3.2.1.3.1. EUC Engineer

3.2.1.4. Michael GEYER

3.2.1.4.1. MS Application Engineer

3.2.1.5. Grégory SOTTIAUX

3.2.1.5.1. MS Application Engineer

3.2.1.6. Fabien CLAUSI

3.2.1.6.1. Technical Engineer

3.2.2. COPIL

3.2.2.1. Sebastien ISTACE

3.2.2.1.1. IT Director

3.2.3. Sales

3.2.3.1. Thierry BOUSEFSAF

3.2.3.1.1. Account Manager

3.3. External Supplier

4. Phases

4.1. P1-Initiation

4.1.1. WP1-Assessment

4.1.1.1. Network and Security

4.1.1.2. IaaS

4.1.1.3. EUC

4.1.1.4. O365

4.1.2. WP2-Design

4.1.2.1. Network and Security

4.1.2.2. IaaS

4.1.2.3. EUC

4.1.2.4. O365

4.2. P2-Delivery

4.2.1. WP3-Implementation

4.2.1.1. Network and Security

4.2.1.2. IaaS

4.2.1.3. EUC

4.2.1.4. O365

4.2.2. WP4-Test & Validation

4.2.2.1. Network and Security

4.2.2.2. IaaS

4.2.2.3. EUC

4.2.2.4. O365

4.3. P3-Closure

4.3.1. WP5-Documentation

4.3.1.1. Network and Security

4.3.1.2. IaaS

4.3.1.3. EUC

4.3.1.4. O365

4.3.2. WP6-Knowledge Transfer

4.3.2.1. Network and Security

4.3.2.2. IaaS

4.3.2.3. EUC

4.3.2.4. O365

4.3.3. WP7-Migration

4.3.3.1. Network and Security

4.3.3.2. IaaS

4.3.3.3. EUC

4.3.3.4. O365

5. Communication Plan

5.1. Kick-Off

5.1.1. Method

5.1.1.1. Meeting - OnSite

5.1.2. Audience

5.1.2.1. COPIL + Project Team

5.1.3. Frequency

5.1.3.1. At begining of project

5.2. Team standup

5.2.1. Method

5.2.1.1. Meeting

5.2.2. Frequency

5.2.2.1. Daily

5.2.3. Audience

5.2.3.1. Project Team

5.3. Project Status Report

5.3.1. Method

5.3.1.1. Email

5.3.2. Frequency

5.3.2.1. At milestones

5.3.3. Audience

5.3.3.1. COPIL

5.4. Project Closure

5.4.1. Method

5.4.1.1. Meeting

5.4.2. Frequency

5.4.2.1. At end of project

5.4.3. Audience

5.4.3.1. COPIL + Project Team

5.5. Escalation (Issue, Change, Risk)

5.5.1. Method

5.5.1.1. Email

5.5.2. Frequency

5.5.2.1. When identified

5.5.3. Audience

5.5.3.1. COPIL + Project Manager

6. Risk

6.1. Very High

6.2. High

6.2.1. Telecom lines

6.3. Medium

6.3.1. Thin Clients compatibility

6.4. Low

6.5. Very Low

6.6. Mitigated

6.6.1. OS licences key for IaaS VMs

6.6.2. On premise Firewalls

6.6.3. SSL Certificates