Sada 365

Office 365 Migration
with SADA Systems

for City of Albany
1 | SADA Systems CONFIDENTIAL AND PROPRIETARY INFORMATION OF SADA SYSTEMS, INC.

Statement of Work for
City of Albany, CA
Presented on August 27th, 2015
Proprietary Notice
This report contains confidential information of SADA Systems, Inc. which is provided for
the purpose of permitting the recipient to evaluate the proposal submitted herewith. In
consideration of receipt of this document, the recipient agrees to maintain such
information in confidence and to not reproduce or otherwise disclose this information to
any person outside the group directly responsible for evaluation of its contents, except
that there is no obligation to maintain the confidentiality of any information which was
known to the recipient prior to receipt of such information from SADA Systems, or
becomes publicly known through no fault of recipient, or is received without obligation
of confidentiality from a third party owing no obligation of confidentiality to SADA
Systems.

Table of Contents
1 Introduction ...............................................................................................6
2 Project Objectives .....................................................................................6
2.1 Prerequisites ..................................................................................................................................... 6
3 Authorized Contact(s) ..............................................................................7

4 Current Environment ...............................................................................7
5 Scope of Work ......................................................................................... 10
5.1 Office 365 ........................................................................................................................................ 10
5.2 SADA Services ................................................................................................................................ 11
6 Project Approach .................................................................................... 12

6.1 Phase I Planning and Envisioning........................................................................................ 12
6.1.1 Project Spin Up ...................................................................................................................... 13
6.1.2 Project Initiation & Entry Criteria .................................................................................... 13
6.1.3 Project Kick-Off Meeting ................................................................................................... 13
6.1.4 Discovery ................................................................................................................................. 14
6.1.5 Envisioning Workshops ...................................................................................................... 14
6.2 Phase II Build and Stabilize .................................................................................................... 15
6.2.1 Microsoft Online Portal ...................................................................................................... 15
6.2.2 Permissions Assessment .................................................................................................... 16
6.2.3 Directory Synchronization ................................................................................................. 16
6.2.8 Configure EOP Message Hygiene ................................................................................... 16
6.3 Phase III Deploy ......................................................................................................................... 17
6.3.1 Migrate Mail Data................................................................................................................. 17
6.3.1.2 Migrate Data via Migration Tool ............................................................................. 17
6.3.2 MX Cutover ............................................................................................................................. 18

6.3.3 Post Transition Support (Optional) ................................................................................ 18
6.3.4 Decommission Exchange 2010 (Optional) .................................................................. 18
6.3.5 Project Spin Down ................................................................................................................ 19
6.3.6 Office 365 Policy Consulting ......................................................................................... 19
6.3.6.1 Mobile Device Configuration (excluding BBCS) ..................................................... 19
6.3.6.2 Desktop Readiness ............................................................................................................ 19
6.3.6.3 MRM (Message Records Management) Modeling ............................................... 20
6.3.6.4 eDiscovery ........................................................................................................................... 20
6.3.6.5 DLP (Data Loss Prevention) Pilot .................................................................................. 20
6.3.6.6 Azure RMS (Azure Rights Management Services) ................................................. 21
7 Change Management & Training ........................................................ 21

7.1 IT Change Management & Training ...................................................................................... 21
7.1.1 Change Management ......................................................................................................... 21
7.1.2 Administrative Training ...................................................................................................... 22
7.2 End User Change Management & Training ........................................................................ 22
7.2.1 Training .................................................................................................................................... 22
7.2.1.1 Webinars: ......................................................................................................................... 23
7.2.1.2 Additional Considerations: ........................................................................................ 23
8 Project Management.............................................................................. 23
8.1 Key Service Deliverables and Acceptance Process ........................................................... 23
8.1.1 Service Deliverable Acceptance Process ...................................................................... 23
8.1.2 Project Completion .............................................................................................................. 24
8.2 Project Governance Approach ................................................................................................. 24
8.2.1 Communication Plan ........................................................................................................... 24
8.2.2 Issue/Risk Management Procedure ............................................................................... 25

8.2.3 Change Management Process ......................................................................................... 25
8.2.4 Escalation Process ................................................................................................................ 26
9 Project Requirements & Responsibilities .......................................... 26

9.1 Project Requirements .................................................................................................................. 27
9.1.1 Server Requirements ........................................................................................................... 27
9.1.1.1 Directory Synchronization (DirSync) Server ........................................................ 27
9.1.2 Access Requirements .......................................................................................................... 27
9.2 City of Albany Responsibilities................................................................................................. 28
9.2.1 SADAs Assumptions ........................................................................................................... 28
9.2.2 Out of Scope .......................................................................................................................... 29
10 Professional Services & License Fees ...................................................... 30

10.1 Travel Time and Expenses ........................................................................................................... 31
10.2 Payment Terms................................................................................................................................ 31
10.3 Expiration........................................................................................................................................... 32
11 Conclusion.................................................................................................... 33
12 Appendix......................................................................................................... 34
12.1 Appendix A: Change Request Form ................................................................................................ 34
12.2 Appendix B: Testing Success Criteria .............................................................................................. 35
12.5 Appendix C: Case Study Release Form ........................................................................................... 36

1 Introduction
SADA Systems, Inc. (SADA) is pleased to provide this Statement of Work (SOW) to City of
Albany as a document of intent and scope designed to bring clarity to all parties involved.
There is currently an initiative within City of Albany to transition to Office 365 in order to
gain the flexibility and reliability of moving to Microsofts cloud platform. In moving to
Office 365, City of Albany will not only get the reliability and mobility of Microsofts top
products, but will also gain fiscal control of IT expenditures by converting messaging and
collaboration expenses from capital expenditures to operating expenditures.
This SOW will provide the basis for City of Albany to establish a clean path to the new
messaging platform, and the necessary project resources and experience to execute and
fulfill the plan successfully. In addition, SADA will work with City of Albany to develop
project-related communications plans and content, as well as provide post-project
change management considerations.
2 Project Objectives
The primary objective of this engagement is to integrate Office 365 with City of Albanys
current IT environment and migrate data to the new platform. To facilitate this project,
SADA will perform discovery and Active Directory remediation and then move mail data
to the cloud through a 3rd party migration tool. SADA will provide guidance and support
for updating Albanys Outlook clients and work for a successful and seamless transition.
2.1 Prerequisites
Prior to starting this project the prerequisites include elements common to most service-
oriented delivery engagements as well as some that speak to this projects unique
needs/objectives. Identifying critical functionalities processes, and/or operational needs
are also a critical requirement in order for City of Albany to determine the success of the
partnership.
Some of the prerequisites are:
A signed Master Professional Services Agreement

Understanding of the responsibilities surrounding both SADA and City of Albany.

An internal commitment of City of Albanys resources, equivalent to SADAs own resource outlay,
devoted entirely to project success.
Assign SADA as Partner for Record (POR) for a period of 3 years.
Specific prerequisites such as environment needs, test accounts, network access for
testing are detailed further, herein.
3 Authorized Contact(s)
SADA will assign a project manager upon proposal execution, and SADA will communicate
that persons name and information to City of Albanys authorized contact person. If City
of Albanys contact person is someone other than the individual who signs this SOW on
its behalf, City of Albany must supply the name of that contact person below.
Primary Contact
Name: Victor Mba
Email: vmba@albanyca.org
City of Albanys contact person is authorized to approve materials and services provided
by SADA, and SADA may rely on the decisions and approvals made by the contact person
(except that SADA understands that City of Albany may require a different person to sign
any Change Orders amending this SOW). City of Albanys contact person will manage all
communications with SADA, and when services are performed remotely, at City of
Albanys location (or another location designated by City of Albany); they will be present
or otherwise available.
4 Current Environment
Based on initial conversations with City of Albany, the section outlines SADAs current
understanding of the City of Albanys environment. This information is subject to change
and/or update as a result of an assessment, systems discovery, and documentation and/or
planning efforts that will take place during onboarding. Nevertheless, this Statement of
Work is based on the accuracy of the following information and, therefore, discrepancies
between the information below and the actual environment may result in additional
scope, cost and time.

Integration and Migration
Questionnaire
Question Answer
How many total users do you have? 140
What locations do you have and how many users per 5 locations
location?
What is your Active Directory Forest Name Albanyca.org
What is your Forest Status (i.e. Single Forest, multiple single

forests )
What is your Active Directory Functional Level Domain :2008;

Forest:2003
How many Domain Controllers do you have 4
What are the SMTP Domains used and do all of them need Albanyca.org
to be present in the cloud? ; yes
What is the email Messaging Platform? Is it Distributed or Exchange 2010;

local? Local
If Exchange is used, is RPC over HTTPS configured?
How many mailboxes do you have? 186

(active+inactive)
What is the total mail data size? 209GB
What is the current message receive size restrictions? 10MB
What is the current message send size restrictions? 10MB

Do you use Public Folders? If so, how? Yes; Shared Calendar
Do any users access email via thin clients or terminal no

services only?
Is there an existing archive solution in place? What is it? Local outlook archiving utility(used by a
few users)
If there is an archiving solution, how much data exists in

the archive?
What AntiSpam solution is used? Mcafee Virus Enterprise on exchange
server; and
barracuda spam
filter
Please list out any mail enabled applications exist within Kyocera scan tool; wsus; barracuda
the environment. A mail enabled application is any backup; apc ups;
application that uses exchange to send email on the
applications behalf. For example, a scanners that can scan
to email or any type of ticketing system that sends emails.
Are there any external mail relays in place? Any external No, Internal smarthost with Barracuda
Routing? spam filter
Do you take backups of your environment? If yes, please Daily Barracuda backup
detail the specifics.
Do you have a Data Loss Prevention application? no
Do you have a collaboration platform? If so, what is it?
Do you have an instant messaging platform? If so, what is no

it?
What do you use for web conferencing? Skype
What phone system do you use? Please provide a detailed Mitel voip with
response on the type as well as any type of UM or UC Mavericks
functionality leveraged. Networks. No UM
functionality in
Exchange
What type of operating system do end users have? Win7 x64 + x86

How do you manage all of the Workstations? Dell Kace 1000
What mail client to workstations have? outlook
What mobility platform do endusers leverage? If BES is BYOD with MS

used, are any of the complex features utilized? Exchange
Activesync
How is your network configured? Do you have an MPLS? Mpls via

TelePacific
What is your internet bandwidth? 30mbps

(Cityhall to internet); 15mbps , 6mbps,
1.5 Mbps to remote
sites
5 Scope of Work
5.1 Office 365
The proposed platform is Microsofts Office 365, which is a multi-tenant hosted messaging
and collaboration platform, and represents a suite of the following services: Exchange
Online, SharePoint Online, Lync Online, and Office Professional Plus. The SOW herein may
represent deployment of the entire suite of Office 365 services, or individual services. Since
the solution is hosted by Microsoft it is subject to Microsofts product roadmap and
product lifecyclecustomers cannot determine the roadmap. Since Office 365 is hosted
by Microsoft and is a multi-tenant environment, customizations of the services are not
possible.
For more information on Office 365 and a complete service description, please visit:
http://technet.microsoft.com/en-us/library/jj819274.aspx

5.2 SADA Services
Over the course of this project, SADA will leverage our long standing expertise with on-
premises Active Directory environments, Exchange environments, and the Office 365
platform to successfully complete the business objectives as defined in section 2, Project
Objectives. SADAs technical expertise is balanced by business acumen and the pragmatic
application of well-designed project management teams. We leverage tools and skills to
deliver exceptional service quality to our clients. By using designated project teams, and
platform specific tactical teams, SADA strives to maximize efficiency in order to ensure
project success.
Phase Purpose Phase Activities
I Planning and Envisioning Project spin up and hand off

Complete Entry Criteria
Architecture Planning Project kick-off
Validate all findings during discovery
Discovery & Logistics Ensure Active Directory health
Define/refine schedule and plan for
project
II Envisioning Workshops AD Remediation review

Identity Envisioning
Architecture & Design Desktop Readiness Discussion/Pro-Plus
Sessions Deployment (1 session included) +
architecture docs
Networking requirements sessions
SMTP Relay Envisioning
EOP and mail flow Envisioning
DNS Consulting (as applicable)
Mail flow and routing envisioning
Migration Experience Discussion (1
session included) + architecture docs

III Build and Stabilize General Office 365 Platform Setup
Configure MSOP Domains
Configuration- Office 365 Installation and configuration of Azure
Active
Preparation & Staging Directory Synchronization (AAD
Sync) Tool and quality assurance (Single
Client Deployment Forest)
Test and validate Active Directory
Integration
Provision user licenses in O365
Install Desktop Sign in Assistant (Clients
Responsibility)
Prepare workstations (Clients
responsibility)
Provide guidance on workstation and
browser preparedness and requirements
IV Full Production Rollout Validate all requirements in place for full
production rollout and implement
V Training + Adoption
Adoption Management IT & End User Management
Administrative Training
6 Project Approach
6.1 Phase I Planning and Envisioning
The Planning and Envisioning Phase unifies our respective project teams behind a
common vision and allows the SADA project team to prepare the functional specifications,
work through the design process, prepare work plans, and determine the schedules for
the various deliverables. This is one of the most fundamental requirements for project
success, as the engagement management team and project team must have a clear vision
of what they want to accomplish.

6.1.1 Project Spin Up
Upon execution of this Statement of Work, SADA will meet internally to; (a) assemble the
SADA Project Team, (b) provide knowledge transfer around the scope, timelines,
deliverables and assumptions pertaining to the upcoming engagement, (c) to draft an
initial project plan and timelines and, (d) to draft the Entry Criteria suited to City of
Albanys unique deployment scenario. Please note that the initial project plan necessarily
represents a rough order of magnitude that will undergo planned revisions throughout
the course of the project but which is, nevertheless, informed by historical data from
SADAs 200+ Office365 deployments. It is also important to note that SADA does not
typically provide clients with the Entry Criteria until, (i) the SOW has been executed and,
(ii) a SADA Project Manager has had an opportunity to review these items with you.
6.1.2 Project Initiation & Entry Criteria

Prior to scheduling a Project Kickoff call or engineering resources, City of Albany must
fulfill all Entry Criteria as outlined by SADA. Both the Entry Criteria and the initial project
plan will be reviewed with City of Albany in a Project Initiation Call to better ensure that
there is no confusion around the items SADA will require in order to productively begin
the first phases of the project (i.e. the Planning & Envisioning phase). Once these Entry
Criteria have been fulfilled, SADA will then proceed to schedule a formal project kickoff
call with our respective teams. Please note that delays in completing these items will
represent a corresponding delay to initial project timelines.
6.1.3 Project Kick-Off Meeting

All of SADAs client engagements formally begin with a project kick-off meeting consisting
of the SADA Project Manager and Technical Lead assigned to the project. City of Albany
should ensure that its core project team includes, but is not limited to:
Stakeholders
Project Managers
Technical Personnel
The purpose of this largely non-technical kick-off meeting is to establish a mutual

understanding of the project from its initiation. The meeting generally requires 60-
minutes and consists of the following agenda:

Team introduction, SADA & City of Albany
Role & responsibilities definition
Level set on project objectives, deliverables and timelines
Establish communication standards and rhythms, weekly status calls, etc.
Clearly stated next steps/milestones.
6.1.4 Discovery
SADA will perform discovery of client's existing infrastructure, and gather all information
needed to plan for a successful migration. This phase is designed to collect, verify &
validate the environment specific factors and considerations that are required to complete
this project. This will include the following:
Assessment of the general server environment assessment of Active Directory health.

Validate the Microsoft Online Portal is configured properly.
Assessment of the existing mail environment(s) including number of users, distribution
lists, mail-enabled objects, mailbox sizes and public folder usage and complexity
Discovery of any mail logging or archiving currently in place
Discovery of any server-resident 3rd party Microsoft Exchange Server dependencies
Discovery of existing methods of connecting to Exchange from the client-side,
including email software and hand-held synchronization clients
Discovery of any existing cloud-based services used such as inbound or outbound mail
filtering
Run standard network and AD tests to check AD's health and proper configuration
Run Microsofts Office 365 Readiness Tool
Activities such as data entry, data validation, meetings, conference calls, and a variety of
other administrative or technical remediation activities are not uncommon.
6.1.5 Envisioning Workshops

Most (but not all) of the technical deliverables included within this Scope of Work will
require a Technical Envisioning Workshop to be conducted in the Planning Phase. The
intent of these workshops is to; (a) provide a general overview of the technology and its
functionality and, (b) provide City of Albanys project team with the deployment pre-
requisites for which they will be responsible. Upon completion of each Envisioning

Workshop, SADA will provide a customized Action Plan for the deployment of that
technology for your internal reference and / or change control processes.
AD Remediation review
Active Directory and Exchange Remediation review
Identity Envisioning
Desktop Readiness Discussion and Consulting for Office Deployment 2 Sessions
Networking requirements sessions (2 session included) + architecture docs
SMTP Relay, EOP, Mailflow and Routing and Networking requirements (1 session)
DNS Consulting (as applicable)
Migration Experience Discussion (1 session included) + architecture docs
Office Pro-Plus Deployment Envisioning and Consultancy
Desktop Readiness Discussion (1 session included) + architecture docs
6.2 Phase II Build and Stabilize

During the Build and Stabilize Phase, the team builds and tests all aspects of the solution
included within the scope of the engagement. This phase, and each of its deliverables,
ends when the team validates that the core and defining features of the solution are
functioning properly. Although the solution may continue to evolve, it does so only to
address break/fix situations while the solution is stabilized and readied for deployment.
Testing during this phase emphasizes usage and operation under realistic environmental
conditions. The team focuses on resolving and triaging (prioritizing) issues and bugs, and
preparing the solution for deployment.
6.2.1 Microsoft Online Portal

SADA will configure the necessary administrative activities within the Microsoft Online
Portal (MOP) to facilitate the success of this project. Specifically, all available services will
be activated unless otherwise directed, and ownership & domain validation will occur at
this stage, effectively beginning City of Albanys Microsoft Online Services subscription.
City of Albany may expect involvement during this process including, but not limited to
data entry, data validation, meetings, conference calls, and a variety of other
administrative or technical remediation activities.

6.2.2 Permissions Assessment
SADA will conduct a full permission and mail forwarder survey, parse the data and present
the findings with a strategy to best re-assign permissions and current mail forwarders in
Exchange Online to City of Albany. No permissions are carried over and thus SADA will
document and reassign the following items:
Full Mailbox
Send On behalf
Send As for users
Send as for Distribution groups
Receive As
Mail Forwarding
6.2.3 Directory Synchronization

SADA will deploy and configure the Microsoft Azure Active Directory tool which provides
a method to synchronize a single Active Directory Forest with the Microsoft Online
Services platform. This service is persistent and will remain in production through the life
of the organization and serves to replicate basic changes made in AD to objects in
Exchange Online. AD objects synced are: users, distribution lists, and mail-enabled security
groups. The service also provides password synchronization between user accounts in
Active Directory and Office 365.
City of Albany will be required to provide an adequate environment for the DirSync Service
to reside. City of Albany is expected to be involved prior to this effort to Active Directory
information is accurate and validated. These activities may include, but are not limited to
data entry, data validation, meetings, conference calls, and a variety of other
administrative or technical remediation.
Criteria for a successful implementation of Directory Synchronization are outlined in
Appendix B.
6.2.8 Configure EOP Message Hygiene

Users of Office 365 will essentially leverage Microsofts Exchange Online Protection in
order to receive Anti-Spam and Anti-Virus filtering for all mail; SADA will examine the
existing message hygiene within the current mail filtering platform and apply the same
hygiene to EOP. In order to accomplish this task SADA requires an excel spreadsheet with
the current whitelist and blacklist from the current AS/AV solution.

6.3 Phase III Deploy
Once all the activities carried out in the Build and Stabilize phase are complete and all
systems are tested and ready for production, SADA and Microsoft will then move into the
Deploy Phase. During the Deploy Phase the migration of users to Office 365 will occur.
6.3.1 Migrate Mail Data

SADA and City of Albany will work together to organize all users into migration batches.
Best practice stipulates that batches should be organized by department in order to
ensure team members are migrated at the same time. It is also recommended that
Administrators are migrated with their managers.
6.3.1.2 Migrate Data via Migration Tool

SADA will leverage a migration tool in order to transfer mail data to Microsoft's Exchange
Online platform. The transfer rates will vary based on availability of disk IO as well as
bandwidth. The tool will leverage an admin exchange account to migrate the contents of
each mailboxes to the online platform. It should be noted that bandwidth, network
interruptions, and Microsofts and the migration tools ingestion rates are factors outside
of our control. The process will follow the following steps:
Verify, installation and/or configuration of all appropriate component
dependencies
Mailbox provisioning
Once mailboxes provisioning phase completed users can login to
their cloud mailboxes. However, in order to receive new emails in
cloud mailboxes client is responsible for populating forwarding
addresses on the source mailboxes, thus forwarding copies of new
emails to cloud platform. The client has the option to redirect new
emails to cloud platform if desired without keeping copies in the
source mailboxes.
Migration of mailboxes
Systematically migrate data to Office 365
The client has the option of staggering mailboxes transfers to
address bandwidth and ingest rate factors by way of submitting
batches of users.

Transfers occur sequentially and will be executed over a pre-
determined period of time.
Migration timeline objectives and available bandwidth should be
considered when scheduling.
Simultaneous migrations can be run in some cases, thus achieving
higher migration rates.
Mailboxes should not be disconnected/deleted in the source system
until migration is fully completed and MX records pointing to online
platform.
NOTE: Corporate network performance on the days immediately following the

final migration may still be impacted by the bandwidth demands of email clients,
and should be considered carefully and communicated to the users accordingly.
It is also required to schedule Exchange backups not to overlap with migration.
6.3.2 MX Cutover
Once all of the data is completely migrated, SADA Systems will change the DNS records
to point mail flow to the new Online Services mail platform. During this phase of the
project timeliness is essence; for this reason SADA requires access to the DNS records at
the start of the project to ensure our ability to change them at the proper time.
6.3.3 Post Transition Support (Optional)

SADA excels in service delivery. Our comprehensive incident, problem and project
management platform ensures that all reported issues are captured and remediated over
the course of the project. SADA generally goes above and beyond to make its resources
available to clients, further insuring project success. General support as it relates to this
SOW will be provided throughout the length of this project, and can include administrative
technical support and training, and the option of ongoing Service Desk and end-user
support. Specifically, the equivalent of 2 FTEs will be resourced and reserved the day
immediately following the project date(s), further insuring the transition is managed
smoothly and completely.
6.3.4 Decommission Exchange 2010 (Optional)

Once all mailboxes have been migrated to the cloud and legacy Exchange servers are no
longer needed, SADA will begin the process of properly removing all Exchange 2010
servers from City of Albanys environment.

SADA will first ensure that all mailbox, Offline address book, and public folder databases
have been moved to either the on-premises Exchange 2010 infrastructure or Office 365.
Once all instances have been removed, SADA will remove the stores associated to the
mailbox and public folders. SADA will then ensure that mail flow is configured to route
to the Exchange 2013 hybrid server.
SADA will then proceed with the removal of the Recipient Update Service and finally
uninstall Exchange 2010 from City of Albanys environment.
6.3.5 Project Spin Down

At the completion of the project, a meeting will be held with SADA to verify that all of City
of Albanys business and technical requirements have been satisfied. This call will also
establish any final action items, change orders, the transfer of knowledge and/or other
project completion activities, as deemed appropriate and within scope. Additionally, a
project feedback form will be supplied to City of Albany for their completion.
6.3.6 Office 365 Policy Consulting

Migrating to Office 365 requires some configuration within the Office 365 platform in
order to adhere to City of Albanys specific business requirements. SADA will configure
the following items within Office 365:
6.3.6.1 Mobile Device Configuration (excluding BBCS)

SADA will work with City of Albany to configure mobile device policy within Office 365.
6.3.6.2 Desktop Readiness

SADA will work with City of Albany to provide consulting around the readiness of end-
users machines for Exchange Online, OneDrive for Business, and Office Pro Plus. In
addition to working through the various workstation requirements, SADA will work with
City of Albany to determine the best method for updating workstations and provide
communication change management for the end-users.
It should be noted that SADA will not touch end-users machines, but will provide the
consultancy for desktop readiness.

6.3.6.3 MRM (Message Records Management) Modeling
SADA will work with appropriate City of Albany stakeholders to construct an enterprise-
wide MRM policy using the Retention Policy and Retention Tags feature of Office 365.
The modelling process will consist of a design session between SADA and City of Albany,
implementation of said design, and informal knowledge transfer throughout the
deployment of this deliverable.
Any modifications to any Retention Policies or Retention tags after the initial
implementation of MRM based on the design session will be pursuant to the Change
Order process outlined in this SOW.
MRM doesnt guarantee retention of every message. For example, a user can delete or
remove a message from their mailbox before the message reaches its retention age;
MRM isn't designed to prevent users from deleting their own messages.
6.3.6.4 eDiscovery
SADA will provide additional consultation and support around eDiscovery workloads in
addition to what SADA already provided in the pilot phase of the Office 365
implementation covered in a previous SOW. Consultation and support is not to exceed
10 hours.
6.3.6.5 DLP (Data Loss Prevention) Pilot

SADA will work with City of Albany to pilot the DLP features of Office 365. The pilot will
consist of three (3) use-case scenarios that City of Albany will provide to SADA for
implementation. The successful implementation of these three 3) use cases scenarios will
serve as the only mutually agreed success criteria for the pilot. An example of a use-
case scenario is the enterprise blocking any e-mails destined for external recipients that
contain credit card or Social Security numbers. SADA will also provide knowledge
transfer and consultancy around other DLP related feature such as DLP incident
reporting and DLP administration.
SADA will use only DLP templates that are natively provided by Office 365 and will make
any modification to these templates to fulfill pilot requirements at its discretion.
Construction of custom DLP policy templates is expressly out of scope and its inclusion
after the execution of this agreement will be pursuant to the Change Order process
outlined in this SOW.

6.3.6.6 Azure RMS (Azure Rights Management Services)
SADA will enable the Azure RMS in City of Albanys Office 365 tenancy and provide
Office and Exchange Online RMS integration. SADA will enable Microsoft Office
Professional Plus 2013 and Microsoft Office 2010 users to be able to protect content
using predefined policies provided by the service within your organization. Office
applications that include these capabilities are Word, Excel, PowerPoint, Outlook, and
InfoPath. SADA will enable users of Microsoft Exchange Online to protect and consume
email messages in Outlook Web Access (OWA) and consume protected messages via
Exchange Active Sync for devices that have implemented IRM support including
Windows Phone. SADA will enable additional features, such as Outlook protection rules
as well as transport rules for protection and decryption, to ensure content is not
inadvertently leaked outside of the organizational boundary and edit the content of the
message to include disclaimers, solely at its discretion.
7 Change Management & Training

Change Management is practiced throughout the entirety of the project and is comprised
of Change Management for City of Albanys IT organization as well as Communication
Management for the end user community.
7.1 IT Change Management & Training

7.1.1 Change Management
Migrating your messaging environment to Office 365 will introduce change to your users,
IT Administrators and the organizations operations. The level of change will vary
depending of service subscription, and will change as additional services are adopted. A
critical success factor of the migration to Office 365 will be the identification of changes
to existing Processes, Operations, and Users in order to develop an action / mitigation
plan. SADA will provide City of Albany with a written Change Management and
Communication plan that delivers a guideline overview and strategy for anticipated
changes related to the migration and post-migration process.
This change management plan will include:
Table of On-Premises changes that will occur as a result of a Cloud Migration

Guidelines for user account management (e.g. onboarding and off boarding)
PowerShell cmdlet reference guide

Service descriptions and brief overview of Office365 feature set to be used as product
introductions for (new) IT Admins
General Admin-level troubleshooting guides for DirSync, AD FS 3.0, MS Online Portal,
and
EOP
Network Diagrams of post-migration environment
Strategies for obtaining and expediting Microsoft Support
Tier 1 Troubleshooting guide
Migration Experience Document
7.1.2 Administrative Training

As the project progresses SADA will join City of Albanys project team members to
facilitate administrative training sessions on the various aspects of Office 365. This
training is comprised of:
4 Webinar style training sessions

10 hours of training based on your requirement
No days of onsite training time
7.2 End User Change Management & Training

Introduction of Office 365 represents an element of change management that
administrators and end users will need to understand in terms of account changes, user
administration and other such tasks. SADA offers both remote and on-site training plans
that are customizable. These sessions are held by a member of our technical project team
or by our professional trainer based on specific training requirements.
7.2.1 Training
SADA will work with City of Albanys training team to develop a customized training plan
for the pilot users as well as City of Albany training team. City of Albany has expressed a
deep desire to intricately plan every aspect of this rollout of Office 365 especially as it
relates to end user experience. This transition will fundamentally change the way that City
of Albany users are used to interacting with their email and SADA has developed the
following plan in order to best prepare the training team and pilot team. The training is
comprised of:

1 Webinar Style End User Trainings
Adoption Management
7.2.1.1 Webinars:
All webinars have a minimum of five (5) participants and a maximum of 100 participants.
All webinar sessions shall be conducted between the hours of 7 a.m. and 7 p.m. (Pacific),
Monday through Friday (with the exception of national holidays). Sessions scheduled
outside of this time period will be subject to additional fees.
7.2.1.2 Additional Considerations:
All training must be completed within four (4) weeks of the final Go Live date.
All sessions are conducted in English only.
8 Project Management
All projects are handled by our dedicated Project Management Office (PMO). Our Project
Management Organization inherits over 55 years of collective experience overseeing
extremely dynamic, sophisticated and complex software, platform and infrastructure
projects. City of Albany will gain full access to this team, which is supported by a full time
Business Analyst, and will have a dedicated Project Manager at its disposal.
8.1 Key Service Deliverables and Acceptance Process

8.1.1 Service Deliverable Acceptance Process
At specified milestones throughout the project, we will submit completed project Service
Deliverables for your review and approval. Within 5 business days from the date of
submittal, you must either:
Accept the Service Deliverable by signing, dating, and returning the Service Deliverable
Acceptance Form, or
Provide a written notice rejecting the Service Deliverable, including a single and
complete list describing every reason for your rejection.
Service Deliverables shall be deemed accepted unless you provide a written rejection
notice as described above. Your use or partial use of a Service Deliverable will constitute
acceptance of that Service Deliverable.

SADA will correct problems with a Service Deliverable that are identified in the written
rejection notice, as described above, and within the scope of the Service Deliverable, after
which the Service Deliverable will be deemed accepted. Problems that are outside the
scope of a Service Deliverable, and feedback provided after a Service Deliverable has been
deemed accepted will be addressed as a potential change of scope pursuant to the
Change Management process outlined in this SOW.
8.1.2 Project Completion

The project will be considered complete when any of the following conditions is met:
All of the service deliverables identified within this SOW and any Change Requests
accepted pursuant to the Change Management Process defined in this document,
delivered and accepted or deemed accepted; or
The fee provisions of the Work Order have been met; or
This SOW is terminated pursuant to the provisions of the agreement
8.2 Project Governance Approach

The SADA Engagement Manager will work in conjunction with your Project Manager and
Project Sponsor to facilitate the project governance activities outlined in this approach.
8.2.1 Communication Plan

The following will be used to provide formal communication during the course of the
project:
The Engagement Manager, working in conjunction with the Customer Project

Manager, will document a Communication Plan as part of the Master Project
Management Plan
The SADA Engagement Manager, working in conjunction with the Customer Project
Manager, will compile weekly status reports for distribution to both Customer and
SADA management
Weekly status meetings will be held to review the projects overall status, the
acceptance of deliverables, the project schedule, and open issues noted in the status
report
The SADA Engagement Manager will send bi-weekly executive status reports to the
Project Executive Sponsor on project progress on assigned tasks and deliverables

8.2.2 Issue/Risk Management Procedure
The following general procedure will be used to manage active project issues and risks
during the project:
Identify: Identify and document project issues (current problems) and risks (potential
events that impact the project)
Analyze & Prioritize: Assess the impact and determine the highest priority risks and
issues that will be managed actively
Plan & Schedule: Decide how high-priority risks are to be managed and assign
responsibility for risk management and issue resolution
Track & Report: Monitor and report the status of risks and issues and communicate
issue resolutions
Control: Review the effectiveness of the risk and issue management actions
Active issues and risks will be monitored and reassessed on a weekly basis. Mutually
agreed upon issue escalation and risk management processes will be defined at the outset
of the project.
8.2.3 Change Management Process

During the project, either party may request, in writing, additions, deletions, or
modifications to the services described in this SOW (change request).
For all change requests, regardless of origin, City of Albany shall submit to SADAs Change
Request Form (Appendix A), which shall describe the proposed change(s) to the project,
including the impact of the change(s) on the project scope, schedule, fees, and expenses.
For all change requests which Customer originates, SADA shall have a minimum of 5
business days from receipt of the change request to research and document the proposed
change, and prepare the Change Request Form.
Customer shall have 5 business days from your receipt of a completed Change Request
Form to accept the proposed change(s) by signing and returning the Change Request
Form. If Customer does not sign and return the Change Request Form within the time
period prescribed above, the change request will be deemed rejected and SADA will not
perform the proposed change(s).
No change to this project shall be made unless it is requested and accepted in accordance
with the process described in this section. SADA shall have no obligation to perform or

commence work in connection with any proposed change until a Change Request Form
is approved and signed by the designated Project Managers from both parties.
8.2.4 Escalation Process

The SADA Engagement Manager will work closely with the Customer Project Manager,
Sponsor, and other designees to manage Project issues, risks, and Change Requests. The
standard escalation process for review and approval, and/or dispute resolution is as
follows:
Project Team member (SADA or Customer)

Project Manager (Customer)
SADA Engagement Manager / Project Sponsor
9 Project Requirements & Responsibilities

The success and timely completion of your project requires a number interdependent
activities to be carried out by both SADA and your Project Team. Therefore, it should be
expected that your active participation will required throughout the entire course of the
engagement and will require (minimally) a commensurate allocation of time and resources
to those that SADA will be providing.
While Office 365 Projects typically involve infrastructure deployments and unique
integrations, these projects are not intended to be lengthy in duration. The SADA Project
Team responsible for the deployment of your project infrastructure has been made
available for 90 calendar days following your Project Kickoff Call. Infrastructure
deployments lasting longer than 90 calendar days because of failure to provide SADA with
necessary deliverables will require a valid change order with possible impacts to cost,
timeline and resource allocation.
Failure to complete all of the necessary tasks and responsibilities within the mutually
agreed upon timelines (as articulated in your Project Plan) may result in one or more of
the following:
Delayed delivery of project milestones

SADA carefully schedules its resources to complete a pre-defined set of tasks within a
specific timeframe and does so for a number of projects running concurrently. As a
result, SADA cannot guarantee the immediate availability or continuity of resources
when rescheduling tasks that have slipped more than 30 days from the agreed upon

completion date and where such slippage was due to a failure in providing SADA with
project Deliverables.
Failure on the client's part to complete a project Deliverable within 30 calendar days of
the agreed upon completion date will be cause for SADA to invoice the client for that
Deliverable as outlined in Section #N under NET 30 terms.
9.1 Project Requirements

The following items are required by SADA in order to facilitate the project.
9.1.1 Server Requirements
9.1.1.1 Directory Synchronization (DirSync) Server

You will need the following for the DirSync server:
Requirement Recommended Requirement
CPU Speed Dual-core, 1.6 GHz
RAM 4 GB
Disk Space 50 GB
Operating System Windows Server 2008 R2 SP1 (STD or

ENT) at minimum.
9.1.1.2 Disk Space 200 GB
Operating System Windows Server 2012 R2 (STD or ENT)

at minimum.
9.1.2 Access Requirements

Provide SADA with User Credentials to access a Microsoft Online Services
administrator account in Microsoft Online Admin Center, after sign-up has been
completed
Provide SADA a predetermined/designated/approved method of remote unattended
access to all the necessary servers and workstations required to facilitate project
success.
Provide SADA with credentials for an Active Directory service (user) account
which is:

A member of Enterprise Admins, Schema Admins, Domain Admins, and security
groups
A member of Exchange Full Administrator security group or a member of the
local Administrator security group on the non-DC server member server.
Provide SADA with credentials and access information for DNS management of client's
public domain name(s), or contact information for an individual with immediate access
to the aforementioned system access.
9.2 City of Albany Responsibilities

The following subsections are items are the responsibility of City of Albany and required
by SADA to facilitate a successful project:
Fulfillment of all the requirements as listed in the Project Prerequisites section.

All project requirements listed in the Project Requirements section.
Procurement of all necessary subscriptions including Microsoft Online Services
Give SADA the assurance that all software, hardware and/or infrastructure
requirements are met as set forth by Microsoft and/or SADAs own products.
Provide all communications to end users. This includes notification on changes,
migration schedule, and other project pertinent information.
A qualified technical resource, which can also facilitate physical or remote access, who
is capable of fulfilling the requirements of this project and who can also make
decisions to ensure uninterrupted progress of the project.
Software deployments including, but not limited to Microsoft Outlook, Lync Online, or
any other software dependencies or operating systems.
Provision and provide one or more appropriate server resource(s) to all of the servers
listed in the Server requirement section. City of Albany is responsible for provisioning
the server and configuring the OS.
Any subscriptions, hardware, or licenses required to implement Exchange 2010
Server(s) into City of Albanys environment will be procured by City of Albany.
City of Albany will participate in marketing efforts for both SADA and Microsoft to
provide favorable case studies.
9.2.1 SADAs Assumptions

SADA assumes the following within the context of this SOW:
All services will be rendered during the following time periods:

Normal business hours: 9am 6pm, Monday Friday PT.

All times exclude national holidays.
Adequate facilities and resources will be provided by City of Albany for services
rendered by SADA while on-site at any City of Albany location, as needed.
City of Albany will authorize SADA to perform several interviews of stakeholders,
sponsors, team members, technical staff and managers, who will be reasonably
available from time to time for the purpose of information gathering as the project
may demand.
City of Albany will acquire all necessary hardware, software and/or subscriptions
required to complete this project.
Any changes made to technical or business specifications found in this proposal must
be submitted through a valid Change Order, and approved by both City of Albany and
SADA.
If City of Albany wishes to fully integrate their on-premises UM System then they will
take the necessary steps in order to ensure success.
SADA will assist the client with installation of required VPN appliance to ensure correct
configuration
9.2.2 Out of Scope

It is important to note that some of the items not included within the scope of this
Agreement are, nevertheless, critical path items which will be required for successful and
timely completion of this project.
The Following items are out of scope:
Any items not specifically called out in the scope of work are out of scope.
Configuration of SMTP Relay outside of the envisioning session included.
Outlook profile creation or direct assistance on the transfer unless opted for by Albany
Policy Consulting outside of the stated envisioning and training listed above, unless
opted for by Albany.
Deployment of client/desktop software is out of scope unless exceptions are explicitly
stated otherwise in the SOW. This is limited to the included envisioning sessions.
Direct end-user assistance of any type, unless City of Albany otherwise opts to use
SADA's Service Desk services.
The removal, uninstallation, retirement, decommissioning or any of the activities
related with removing any elements of the existing messaging platform.
Migration of PST data, centrally archived data, or encrypted mail.
Archiving for Exchange Online setup is out of scope, with the exception of service
enablement.

Skype for Business configuration is out of scope beyond basic service activation.
Active Directory remediation outside of consultation. SADA will perform discovery and
make recommendations, however Albany will be required to make the actual changes.
Off boarding pilot users from the Office 365 platform.
Remediation of Blackberry devices outside of general consulting.
Configuration of Exchange Online Protection (Pre-configure EOP, mirror current spam
filtering settings on EOP). This should be considered as a part of full migration.
Configuration of UM in Office 365.
Integration with composite applications
Permanent migration of delegations, permissions, and properties is out of scope.
The migration process using rich coexistence will transfer all existing delegate to
Office 365. Though copied, the permissions will only work if the delegator and
delegate are in the same exchange org (e.g. both in Exchange Online, or both on
premises). OWA and Outlook cannot access folders in other mailboxes cross-
premises.
Full access and send as permissions (permissions that an admin would assign)
are NOT migrated. When moving to Office 365 these permissions need to be
migrated manually.
10 Professional Services & License Fees
Description Total
Phase I Logistics & Discovery $3,510.00

Envisioning Workshops + Architecture & Design Sessions $2,730.00
Phase II Build & Stabilize $1,170.00
Phase III and IV Pilot and Full Production Rollout $2,580.00
Phase V Admin / End User Training and Adoption Management $2,830.00
Policy Consulting $1,950.00
Project Management $1,998.00
Migration Wiz Licenses (180) $2,046.00
Note: Subtotal: $18,814.00
Taxes: Included

SADA provides free basic admin
support when licenses are SADA Discount (if
purchased through SADA, and signed by September -$2,500
additional end-user support can be 25th, 2015)
added to scope
Pricing based on:

3-yr License
Commitment
Case Study
Pinpoint Review Grand $16,314.00
Total Services:
Use of Logo
Reference
180 G3 Licenses: $14.50/user/month $31,320.00

Taxes Included
Grand Total: Licenses and Services Yr. 1 $47,634.00
10.1 Travel Time and Expenses

Travel time and expenses are all not included in the scope of the service offered in this
agreement. Should travel time be required during the project, travel expenses will be billed
separately.
All services are to be rendered remotely by SADA systems within the scope of this project.
10.2 Payment Terms

SADA requires payment of 50% of the services total upon SOW execution. The remaining
portion of the services total will be invoiced and due immediately upon completion of the
project.

If some, or all, of the funds for the project are provided by Microsoft and/or SADA, and
the specific terms and conditions around the funding are not met by City of Albany, then
the City of Albany is responsible for paying the entire subsidized amount.
The terms and conditions set forth by SADA and/or Microsoft to secure funding supersede
payment/procurement agreements otherwise establish in this or other agreements, and
are available upon request unless otherwise included herein.
10.3 Expiration
This proposal expires within 30 days. Please indicate your acceptance by signing the
below, and faxing it in its entirety to 818-766-0090. City of Albany may also email a signed
and scanned copy to the designated account manager.

11 Conclusion
Any part of this proposal you deem unsatisfactory can be amended to comply with your
requirements. At SADA Systems Inc. we are committed to 100% satisfaction of client
needs, and fostering a good business relationship.
We very much look forward to working with you on this project.
Agreed and signed by City of Albany
____________________________
Authorized Signature
____________________________
Print Name
____________________________
Date
Agreed and signed by SADA
____________________________
Authorized Signature
____________________________
Print Name
____________________________
Date

12 Appendix
12.1 Appendix A: Change Request Form
Date Requested: ________________________
Change Number: _____________________
This Change to the SOW number, dated ________________, between City of Albany (Client) and
SADA Systems (Company) is entered into between the parties and is effective on <date>. This Change
Order is subject to all terms and conditions in the Agreement and SOW. The parties agree as follows:
Description of Change:
Reason for Change:
Impact of Change (complete all that apply):

Current: Proposed:
Cost
Schedule
Resources
Effective Date
This Change Control will be effective on <date>.
CLIENT
Print Name/Title: ____________________________________________________

Signature______________________________ Date________________________
SADA Systems Approval
Print Name/Title_____________________________________________________
Signature______________________________ Date_________________________

12.2 Appendix B: Testing Success Criteria
Testing and Success Criteria
Directory Global Address List is current and up-to-date in the cloud

Synchronization Relevant Properties for a subset of user accounts in Active
Directory appear in Office 365
AD FS 3.0 Users use their existing Active Directory corporate credentials
(User Principal Name and password) to access services in
Office 365 for enterprises
Rich Coexistence Mail routing between on-premises and cloud-based
organizations
Mail routing with a shared domain namespace. For example,
both on-premises and cloud-based organizations use the
@contoso.com SMTP domain.
Free/busy and calendar sharing between on-premises and
cloud-based organizations
The ability to move existing on-premises mailboxes to the
cloud-based organization
Message tracking, MailTips and multi-mailbox search between
on-premises and cloud-based organizations
The ability to off board a mailbox
SMTP Relay Relaying properly works between mail enabled application and
the test cloud user
Pilot Migration Users have access in Cloud to Mail, Calendar, Contacts and
Tasks
(For more details, see Users have Send/Receive As and Full Mailbox permissions
What is Migrated data manually recreated on the Cloud
sheet) Users are able to access Mail items on handhelds (Mail,
Calendar, Contacts and Tasks) Please note that SADA
Systems is unable to support Blackberry devices (unless
otherwise agreed to) as this is a separate hosted service
72 hour term where Post-Migration Support is provided

12.5 Appendix C: Case Study Release Form
Case Study, Press & Analyst Relations Release for Microsoft Online Services
This Case Study, Press and Analyst Relations Release (the Release), is between SADA Systems, Inc.,
a California corporation (SADA Systems) and the company identified below (Company). This
Release is effective on the later of the two signature dates below (the Effective Date). This Release
consists of:
The terms and conditions below; and
Exhibit A Individual Release (applicable to specific quotes or testimonials)
Addresses and contacts for notices

SADA Systems Company
Attention: Attention:
Address: Address:
Phone number: Phone number:
Fax number: Fax number:
E-mail (if applicable): E-mail (if applicable):
Other contact address: Other contact address:
Agreed and accepted

SADA Systems Company
Signature: Signature:
Name: Name:
Title: Title:
Date: Date:
1. Purpose

SADA Systems would like to conduct a case study and other public/analyst relations activities with
Company describing Companys use of Microsoft products, technologies and/or relevant services
provided by SADA Systems. This Release sets forth the activities that Company agrees to take part in.
It also sets forth the parties use rights for any documents or recordings (Materials) resulting from
these activities. This Release applies to the activities listed in Section 2 (Participation) below unless the
parties otherwise agree in writing. Neither SADA Systems nor Microsoft is required to create or use
any Materials in connection with such activities.
2. Participation
Company will take part in the following activities that are listed below:
Marketing and Public Relations
Written case study a document describing Companys experience with and use of
Microsoft technologies and focused on SADAs services.
Customer testimonial a brief statement regarding the Customers experience with
SADAs services on SADAs Office 365 Marketplace services listing.
Media Reference Named o Companys name and/or logo to be used in a press release,
SADA blog, event keynote/presentation, SADA press interviews or similar public
statement, any such uses to be reviewed and approved in advance by Client. o Company
quote/statement to be used in public facing content such as a press release, quote sheet,
SADA blog or similar content. Any use of such quotes or statement to be reviewed and
approved in advance by Client.
o Company case study to be shared with media via participation in an industry or
media event
3. Intellectual property rights
The following terms apply to all Materials created under this Release.
a) SADA Systems may interview and record, by any means chosen by SADA, identified
employees and contractors of Company to gather information for creating the
Materials. Company will obtain the consent of all Companys employees and
contractors whose quotes, names, voice or image appear in the Materials to grant the
rights set forth in this Release.
b) Company hereby grants to SADA Systems the non-exclusive and non-transferable
right and license to may display Companys name, trademarks, service marks, logos,
and other identifying information (collectively, the Marks) in the Materials. The
Marks will shall not be used by SADA Systems for any other
c) Purpose. SADA Systems acknowledges Companys exclusive right, title and interest
in and to the Marks and shall not do anything that impairs the same. SADA Systems
shall not represent that it has any ownership or other rights in the Marks and

acknowledges that its use of the Marks will not create in SADA Systems favor any
right, title or interest in and to the Marks. Company shall have the right to review and
approve SADA Systems use of Companys Marks, before SADA Systems releases
any Materials incorporating such Marks to the public.
d) Company will review the Materials before it approves their release for factual
accuracy and to prevent the inadvertent release of Companys confidential
information. Company will provide its approval or comments to SADA Systems in
writing (e-mail sufficient) within thirty (30) days of Companys receipt of the
proposed Materials.
e) SADA Systems will own the Materials except for any of Companys Trademarks
incorporated therein.
4. Mutual rights and obligations
Each party will have a worldwide right to use, reproduce, publish, distribute, broadcast, publicly
perform or display, translate, and transmit the final, approved Materials. These rights apply to the
Materials in whole or through unedited excerpts, in all forms of media now or hereafter known.
Neither party will change or alter the Materials without the prior written consent of the other party.
Each party will stop distributing, publicly referencing, and/or displaying the Materials upon written
request from the other party.
5. Representation and warranties Company warrants and represents that:
a) It has the requisite corporate or other power and authority to enter into this Release
and carry out the actions contemplated by this Release;
b) It has the exclusive right, title and interest in and to all Marks and has full power and
authority to grant SADA Systems the license described in Section 3(b), which grant
does not require the consent of any other person or entity; and
c) The rights granted in this Release do not violate the rights of any other person or
entity and do not conflict with existing commitments.
6. Limitation of liability
Each party releases the other party and its contractors, agents, affiliates, officers and employees, from
any claims relating to use of the Materials as long as the Materials are used in accordance with the
rights and obligations set forth in this Release.
[Remainder of this page is intentionally left blank]
Individual Release

For good and valuable consideration, the receipt and sufficiency of which is acknowledged, the
undersigned enters this Individual Release (Individual Release). This Individual Release is effective on
[insert date] (the Effective Date).
Agreed and accepted
Individual
Signature:
Name:
Date:
Address:
Phone number:
E-mail (if applicable):

1. Rights of use
I grant to SADA Systems the nonexclusive, worldwide, perpetual right to distribute, reproduce,
publicly perform, display, transmit, broadcast, translate, create derivative works of, or use my name,
biographical information, likeness, image and quotes or testimonials set forth below with respect to
Microsoft Online Services and SADAs services. These rights apply to my quotes or testimonials in
whole or in part and apply to all forms of media now or hereafter known.
[Insert Quote or Testimonial]
[Insert specific solution, project, product, etc.]
2. No fees/waiver
I acknowledge that I will not be paid in connection with this Individual Release or the use of my quotes
or testimonials. In consideration of my personal satisfaction resulting from SADA Systems use of my
quotes or testimonials, I hereby waive all other forms of compensation for granting the above use
rights to SADA Systems.
3. Representations and warranties

I warrant and represent that:
a) I have the legal authority to enter into this Individual Release; and
b) The rights granted herein will not:

(i) Violate any third party right;
(ii) Conflict with any existing contractual or legal commitment on my part; or
(iii) Require SADA Systems to obtain any additional permission from or pay any third
party.
4. Limitation of liability
I hereby release SADA Systems, its affiliates, contractors, agents, officers, employees, from any and all
liability to me relating to this Individual Release.

Sada 365

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Sada 365

Diunggah oleh

Hak Cipta:

Format Tersedia

Office 365 Migration

with SADA Systems

1 | SADA Systems CONFIDENTIAL AND PROPRIETARY INFORMATION OF SADA SYSTEMS, INC.

Presented on August 27th, 2015

2 | SADA Systems CONFIDENTIAL AND PROPRIETARY INFORMATION OF SADA SYSTEMS, INC.

3 Authorized Contact(s) ..............................................................................7

5.2 SADA Services ................................................................................................................................ 11

6 Project Approach .................................................................................... 12

6.1.1 Project Spin Up ...................................................................................................................... 13

6.1.2 Project Initiation & Entry Criteria .................................................................................... 13

6.1.3 Project Kick-Off Meeting ................................................................................................... 13

6.1.4 Discovery ................................................................................................................................. 14

6.1.5 Envisioning Workshops ...................................................................................................... 14

6.2 Phase II Build and Stabilize .................................................................................................... 15

6.2.1 Microsoft Online Portal ...................................................................................................... 15

6.2.2 Permissions Assessment .................................................................................................... 16

6.2.3 Directory Synchronization ................................................................................................. 16

6.2.8 Configure EOP Message Hygiene ................................................................................... 16

6.3 Phase III Deploy ......................................................................................................................... 17

6.3.1 Migrate Mail Data................................................................................................................. 17

6.3.1.2 Migrate Data via Migration Tool ............................................................................. 17

6.3.2 MX Cutover ............................................................................................................................. 18

3 | SADA Systems CONFIDENTIAL AND PROPRIETARY INFORMATION OF SADA SYSTEMS, INC.

6.3.4 Decommission Exchange 2010 (Optional) .................................................................. 18

6.3.5 Project Spin Down ................................................................................................................ 19

6.3.6 Office 365 Policy Consulting ......................................................................................... 19

6.3.6.1 Mobile Device Configuration (excluding BBCS) ..................................................... 19

6.3.6.2 Desktop Readiness ............................................................................................................ 19

6.3.6.3 MRM (Message Records Management) Modeling ............................................... 20

6.3.6.4 eDiscovery ........................................................................................................................... 20

6.3.6.5 DLP (Data Loss Prevention) Pilot .................................................................................. 20

6.3.6.6 Azure RMS (Azure Rights Management Services) ................................................. 21

7 Change Management & Training ........................................................ 21

7.1.1 Change Management ......................................................................................................... 21

7.1.2 Administrative Training ...................................................................................................... 22

7.2 End User Change Management & Training ........................................................................ 22

7.2.1 Training .................................................................................................................................... 22

7.2.1.1 Webinars: ......................................................................................................................... 23

7.2.1.2 Additional Considerations: ........................................................................................ 23

8.1.1 Service Deliverable Acceptance Process ...................................................................... 23

8.1.2 Project Completion .............................................................................................................. 24

8.2 Project Governance Approach ................................................................................................. 24

8.2.1 Communication Plan ........................................................................................................... 24

8.2.2 Issue/Risk Management Procedure ............................................................................... 25

4 | SADA Systems CONFIDENTIAL AND PROPRIETARY INFORMATION OF SADA SYSTEMS, INC.

8.2.4 Escalation Process ................................................................................................................ 26

9 Project Requirements & Responsibilities .......................................... 26

9.1.1 Server Requirements ........................................................................................................... 27

9.1.1.1 Directory Synchronization (DirSync) Server ........................................................ 27

9.1.2 Access Requirements .......................................................................................................... 27

9.2 City of Albany Responsibilities................................................................................................. 28

9.2.1 SADAs Assumptions ........................................................................................................... 28

9.2.2 Out of Scope .......................................................................................................................... 29

10 Professional Services & License Fees ...................................................... 30

10.2 Payment Terms................................................................................................................................ 31

5 | SADA Systems CONFIDENTIAL AND PROPRIETARY INFORMATION OF SADA SYSTEMS, INC.

Some of the prerequisites are:

A signed Master Professional Services Agreement

6 | SADA Systems CONFIDENTIAL AND PROPRIETARY INFORMATION OF SADA SYSTEMS, INC.

7 | SADA Systems CONFIDENTIAL AND PROPRIETARY INFORMATION OF SADA SYSTEMS, INC.

How many total users do you have? 140

What is your Active Directory Forest Name Albanyca.org

What is your Forest Status (i.e. Single Forest, multiple single