<Logo> Xforce Normal

Service Design and Transition Review Record

Organization: Document No:
Department: Revision:
Section: Sheet: 1 of 7

Table of Contents

1. Overview............................................................................................................................................. 3
1.1 Purpose....................................................................................................................................................3
1.2 Scope......................................................................................................................................................... 3
2. Service Design and Transition Review Record -....................................................................4
2.1 Project team –....................................................................................................................................... 4
2.2 Exec Summary –...................................................................................................................................4
2.3 Introduction –.......................................................................................................................................4
2.4 Service Design.......................................................................................................................................5
2.5 Service Transition...............................................................................................................................5
2.6 Action Items –.......................................................................................................................................6
3. Key Contacts and Escalations....................................................................................................... 6
 Service Design and Transition Review Record

Document Control
Document Version History

This table shows a record of significant changes to the document.

Version Date Author Description of Change

0.1 26-Oct-2022 Phil Friedman Creation of document

Approvals

This table shows the approvals on this document for circulation, use and withdrawal

Version Date Approver Title/Authority Approval Remarks

1.0 28-Oct-2022 Ivona Warszawa IT Director N/A

Glossary

Term Description
SLA Service Level Agreement

OLA Operational Level Agreement

SDTRR Service Design and Transition Review Record

OS Operating System (Windows / iOS)

POC Proof of Concept

SME Subject Matter Expert

Document No: BR/03-1 Sheet: 2 of 7

Revision No: 0.1 Issue Date: 26-Oct-22
 Service Design and Transition Review Record

1. Overview

1.1 Purpose

This document is intended for use by the IT department to record the new
service design and its transition review.

1.2 Scope

The new service offering is of a cyber security tool that will be installed on all the
organizations’ computers, with the purpose of stopping any malicious attacks
from any external website that the employees will access. This tool will be
installed on both Mac and Window computers.

Document No: BR/03-1 Sheet: 3 of 7

Revision No: 0.1 Issue Date: 26-Oct-22
 Service Design and Transition Review Record

2. Service Design and Transition Review Record -

2.1 Project team –

a. Lead: Toni Johnson

b. Architect: Manny Rodriguez
c. Product Manager: Cynthia Levin
d. R&D team lead: Sharon Cornwall
2.2 Exec Summary –

The project is progressing according to plan, despite some unexpected issues.

We’re using 3 out of the planned 10 contingency buffer days to resolve them.
The issues are –

# Issue Status Owner Due Date Comments

Blocker: Not all the In Progress Slava 08-Nov- We’re updating all the OS to
employees are using the Ainbinder 2022 Win10
1
same Windows OS
version

Blocker: The laptops of In Progress Ron Wang 28-Oct- A patch is being created to
employees using a 2022 update the tools’ security
2 cellular modem can’t policy requirements
configure the required
security policy of the tool

Delay: Not all of the beta In Progress Mellissa 07-Nov- No impact on the timeline,
testers have submitted Green 2022 the due date was pushed by
3
their logs for analysis by 3 workdays
the IT team

2.3 Introduction –

In the past 8 months the IT cyber security team have noticed increased attempts
of malicious attacks coming from external websites that the organizations’
employees are using in their day-to-day functions.

Following a POC by 3 industry lead companies, one tool was chosen to be

implemented in our organization with the goal of detecting and stopping these
attacks. The high-level timeline for the completion of this implementation is –

Document No: BR/03-1 Sheet: 4 of 7

Revision No: 0.1 Issue Date: 26-Oct-22
 Service Design and Transition Review Record

# Milestone Due Date Status Comments

1 Complete Beta testing 29-Nov-2022 On track N/A

2 Complete training for all the 16-Dec-2022 Not started Will be done in 4 cycles
employees
3 Product roll-out completion 30-Jan-2022 Not started Will be done gradually over a 2-
week period

2.4 Service Design

This section should include the architect’s input: Architecture diagram and technical
explanations of the product.

OLA’s – 1

# Objective Measurement Last measured RYG Comments

1 Latency < 0.1 millisecond 24-Oct-2022 G Was less than 0.05 millisecond

2 Malicious attack >99.999% 17-Oct-2022 Y 99.91% of the malicious attacks

detection were detected

3 Coverage 100% 17-Oct-2022 G All the employees that are

participating in the POC are
covered by the new tool

2.5 Service Transition

This section contains a checklist of all the required steps for this new service to
transition into the Production environment.

# Step Owner Due Date Dependency Comments

1 Beta testing Program 24-Nov-2022 None The bugs will be tracked in

results analyzed, Manager the JIRA dashboard
and bugs resolved

2 Risk Matrix Program 20-Dec-2022 None Gate: All the risks need to be
created and Manager mitigated or accepted
mitigated

1
Since this is an internal project OLA’s are used and not SLA’s (which should be used for an external project)

Document No: BR/03-1 Sheet: 5 of 7

Revision No: 0.1 Issue Date: 26-Oct-22
 Service Design and Transition Review Record

3 End to end testing QA team lead 17-Jan-2023 Step #1 Allow a 2-week period for
completed bug resolution

4 Activation plan Program Lead 02-Feb-2023 Step #2 and None

completed #3

5 Stakeholder sign- Program Lead 09-Feb-2023 Step #4 Will require a technical and
off business review

6 Documentation Documentation 22-Feb-2023 Step #5 None

completion SME

Document No: BR/03-1 Sheet: 6 of 7

Revision No: 0.1 Issue Date: 26-Oct-22
 Service Design and Transition Review Record

2.6 Action Items –

# Action Item Owner Due Date Status Comments

1 Create JIRA tickets Michael Wald 24-Nov-2022 On track None

and dashboard for
the Beta bugs

2 Schedule a bi- Toni Johnson 25-Oct-2022 Done The meetings will focus on
weekly risk update mitigation plan and progress
meeting

3 Review and Toni Johnson 30-Nov-2022 On track Template creation has

approve the started
activation plan
template

4 Recognize the Toni Johnson 02-Dec-2022 Not started

major
stakeholders

3. Key Contacts and Escalations

Phone Title/ Phone Title/

# Key Contacts Number/ Depart Escalate to Number/ Departme
Email Id. ment Email Id. nt
grand@exa Cyber rmarcotte
mple.com security @example
1 Guy Rand Ruth Marcotte VP / IT
team .com
lead

Document No: BR/03-1 Sheet: 7 of 7

Revision No: 0.1 Issue Date: 26-Oct-22