Project-Fit Blueprint

Client: <Insert client name>

Project: <Insert project name>

TABLE OF CONTENTS

1. INTRODUCTION 3
1.1. Document Purpose 3
1.2. Complimentary Documents 3

2. PROJECT OVERVIEW 4
2.1. Background 4
2.2. Current Situation 4
2.3. Business Justification 4
2.4. Project Objectives 4
2.5. Project Approach 5
2.6. Task Management Tool 5

3. ASSIGNED RESOURCES 5

4. PROGRAM GOVERNANCE 7

5. ROADMAP & PRODUCTS 7

2
 5.1. Roadmap 7
5.2. Products 8
5.3. Transactional Relationship 10
5.4. Data Center(s) 10

6. PHASE OVERVIEW 10
6.1. Phase 1 10

7. USE CASES 11

8. FUNCTIONAL REQUIREMENTS 14

9. APPLICATION OF CONSENT RECOMMENDED PRACTICES 14

8. KEY MILESTONES 14

9. SAP CUSTOMER DATA CLOUD WORK PACKAGES 15

9.1. Project Exclusions 15
9.2. Risks 16
9.3. Project Controls 16
9.4. Scope Change and Project Tolerance 16

10. CLIENT SIGN OFF 16

1. INTRODUCTION

1.1. Document Purpose

This Project-fit Blueprint is created specifically for <Client Name> (hereinafter referred to as “Client”) and intends
to align all resources on high-level information for <Project Name>. Information in this document includes but is
not limited to project scope, resources and schedules.

1.2. Complimentary Documents

To complement this Project-fit Blueprint, the below Client-specific documents are also available:

The Technical Design Document provides details on the recommended architecture, configuration and
development design strategy. It is intended for technical resources.

Technical Design Document <hyperlink>

3
The Config & Data Mapping Tracker includes recommended configurations, implementation policies and data
field mapping for the migration exercise.

Config & Data Mapping Sheet <hyperlink>

The Project-fit Blueprint is intended to be a static document. As such, amendments to the scope and plan which
did not impact the scheduled hours will be recorded in the Change Control Document.

Change Control Document <hyperlink>

Amendments which alter the allocated hours requires a Change Order. Contact your Implementation Consult for
Change Orders.

2. PROJECT OVERVIEW

2.1. Background
Give context on the client and why this project is happening.

2.2. Current Situation

Describe what functionality their site currently has.

2.3. Business Justification

Provide a clear concise description of the issue(s) that need(s) to be addressed by SAP Customer Data Cloud

2.4. Project Objectives

What is this project looking to accomplish? What defines the project as successful?

4
 2.5. Project Approach

Waterfall, Iterative, etc?

2.6. Task Management Tool

What task management tool will Client and SAP Customer Data Cloud use (i.e. TeamWork)

3. ASSIGNED RESOURCES

The following are resources which are directly assigned to plan, consult or build on the project.

Organization Name Role Responsibilities

SAP Customer EX: John Doe Implementation Consultant Primary contact, managing
Data Cloud resources, project plans, strategy
and the over all implementation

5
SAP Customer Technical Consultant Dedicated technical resource,
Data Cloud consulting on technical strategy and
implementation

EX: Client Org

EX: Client Org

6
 4. PROGRAM GOVERNANCE

In the event of an escalation, contact the following individuals

Organization Name Role Responsibilities

SAP Customer EX: John Doe Account Manager All escalated issues
Data Cloud

EX: Client Org Deviation from scope

EX: Client Org Approvals

EX: Client Org Scheduling changes

7
 5. ROADMAP & PRODUCTS

5.1. Roadmap

Features will be implemented in a phased approach as outlined below.

Example:

5.2. Products

The following highlights the standard product capabilities, by phase. Click the product name for a full description
of the standard product. Specific implementation decisions and guidance are recorded in the Technical Design
Document.

Phase/s Identity Products and Services

User Migration
SAP Customer Data Cloud performs an import of Client’s existing database and will consult on
1,3 the schema design. To achieve this import, Client must export data from the current database,
and provide SAP Customer Data Cloud with necessary information such as password hashing,
test users, etc.

Consent Management
1,2,3 Manage user consent for ToS, PP, and other custom consent. Allow for initial consent, re-
consent, version management, user transparency and control.

Lite Registration
1,2,3 Store user emails without passwords for use-cases like newsletter subscriptions and
sweepstakes.

8
 Registration-as-a-Service (RaaS)
RaaS is a complete set of tools for integrating end-to-end registration.
Core workflows that are available as standard within the UI Builder are:
● Registration: new users can register on to the Website or Mobile Apps
1,2,3 ● Login: existing users can login to their account using known credentials
● Link Accounts: users can link accounts between a social and email profile, if the user
tries to register with one, and SAP Customer Data Cloud identifies that the email
already exists in the other.
● Reset Password: when forgotten, users can create a new password

Site Grouping or Single Sign-on

1,2,3
Allows for multiple sites to have shared configurations or user sessions.

Federation
Federation uses the SAML protocol to allow users seamless access across your business’
1,2,3
touch-points without having to re-enter or create new usernames and passwords, regardless
of whether these touch-points are managed by third parties or do not share a database.

IdentitySync
1,2,3 As a one-time or recurring job, IdentitySync allows data to transfer between two platforms in
bulk

Profile Management
1 Collects and manages your entire customer base in a secure, cloud-hosted repository.

Identity Access
1 Easily manage high volumes of user records and get a complete view of any customer within
your database from a user-friendly dashboard.

Identity Compliance
1 Eliminate the complexities of managing various data laws and social network policies through
features such as automatic account deletion and user data controls.

Analytics
1 Access more than 20 key reports, including new users, demographics and referred traffic, to
better understand your audience and measure on-site behaviors.

Customer Insights
1 Visualize the first-party demographic data of any user who connects with your brand, including
his or her age, gender, relationship status, location and more.

Customer Insights Plus

1 Gain a deeper understanding of your customers with the ability to view their Facebook Likes,
favorite brands, media preferences and more.

User Migration
SAP Customer Data Cloud performs an import of Client’s existing database and will consult on
1,3 the schema design. To achieve this import, Client must export data from the current database,
and provide SAP Customer Data Cloud with necessary information such as password hashing,
test users, etc.

9
Phase/s Identity Products and Services

Social Share Bar

1,2,3
Allow users to share content from your site and into their social stream.

Comments or Ratings & Review Import

SAP Customer Data Cloud performs an import of Client’s existing comments/reviews and will
1,2,3
consult on the schema design. To achieve this import, Client must export data from the
current database, and provide SAP Customer Data Cloud with any necessary information.

Comments
RaaS is a complete set of tools for integrating end-to-end registration.
Core workflows that are available as standard within the UI Builder are:
● Registration - a new user can register on to the Website or Mobile Apps
1,2,3 ● Login - existing users can login to their account using known credentials
● Link Accounts - users can link accounts between a social and email profile, if the user
tries to register with one, and SAP Customer Data Cloud identifies that the email
already exists in the other.
● Reset Password - when forgotten, users can create a new password

Ratings & Review

1,2,3 Allow users to rate and comment on products within your site, with an option to share to their
social stream.

5.3. Transactional Relationship

☐ B2C
☐ B2B
☐ B2B2C
☐ B2B2 employee

5.4. Data Center(s)

☐ North America
☐ EU
☐ AU
☐ Russia
☐ China

10
 6. PHASE OVERVIEW

6.1. Phase 1

The remainder of this document focuses on <Phase 1,2,3,>

While all technical details are documented in the Technical Design Document <hyperlink> the following is an overview for this
phase.

Option: replace this section by adding content to the Config and Data Mapping Sheet.

Work Description

Data Imports Include # of records and sources

IdentitySync List the names and descriptions of each integration

Consult on Schema Design Ex: Design consulting for Profile, Preferences and Subscription schemas

Consult on Best Practices Consult on best designs for

7. USE CASES

The Use Case should define what needs to happen upon a particular action in order for that action to be completed
successfully. The use case should outline all that is needed for a particular process to succeed and also outlines all the
participants involved in it.

Use Case Name Provide name for Use Case

Summary Provide a general overview/summary of the Use Case along with the goal to be achieved
Assumptions Any assumptions that are implicit in the definition of the Use Case
Participants The person(s) who will perform each of the steps described in this use case
Preconditions These are the conditions that need to be met to ensure that the use case can be fulfilled.
If these conditions are not met then the case cannot run its course. For example:

● The website needs to be accessible by the customer

● Age requirement-verification of 18+

Description/ Steps and interactions between participants and system that are necessary to achieve
Steps goal

1.
2.
3.
4.
Exceptions Provide description of what happens when a failure occurs in the flow.

11
Recommended Provide diagram that defines everything involved in the Use Case.
Flows
Note: The below recommended flow examples may not be final

Example #1: Full Registration Flow

Gray: Client-hosted content

Blue: SAP Customer Data Cloud-hosted screens

Example #2: Lite Registration

Green: Social provider-hosted screen

Blue: SAP Customer Data Cloud-hosted screens

12
8. FUNCTIONAL REQUIREMENTS

13
The following sections include a set of tables summarizing the requirements that apply for each use case. All the tables
include the following information for each requirement:

● Requirement ID: Unique identifier for the requirement

● Requirement: Description of the requirement.
● Type: Indicates whether the requirement is a reference to a standard (Std) or a new requirement (New).
● Feature: Identifies the functional category which the requirement is linked to.

Requirement Requirement Type Feature Phase Notes

ID
ID001 Ensure data accuracy, Std Registration-as-a- 1
security and privacy with Service
email and CAPTCHA
verification
ID002 The system shall identify Std Lite Registration 1
the
user based on their email
address
ID003 Ability to log consent in the Std Consent 1
SAP Customer Data Cloud
Consent Vault

9. APPLICATION OF CONSENT RECOMMENDED PRACTICES

The below are recommended practices to help safe-guard Client from consent compliance issus. Check off each
item to indicate that the development plan supports these recommendations. Not checking off a practice may
require written acknowledgement of the below decisions.

Planned Recommended Practice Notes

Ensure data accuracy, security and privacy with email and Indicate reasons why it may not be
CAPTCHA verification planned
X SAP Customer Data Cloud serves as the source of truth
Require re-consent for imported users
Only push consented users to marketing applications
Make consent & withdrawal easy for the user
Require re-consent for new PP & ToS
Always authenticate the user
Use real-time imports & ID tracking for proxy consent
Provide lifetime accessibility to legal documents

10. KEY MILESTONES

The following are key milestones which are critical to the project’s success.

Key Milestones Owner Date

14
 Ex: Technical Kick-off EX: SAP Customer Data Cloud

EX: Blueprint Workshop EX: SAP Customer Data Cloud

EX: Identity Strategy Workshop EX: SAP Customer Data Cloud

EX: Project-fit Blueprint and Technical Design EX: SAP Customer Data Cloud
Document Delivered

EX: Start User Migration EX: SAP Customer Data Cloud

11. SAP CUSTOMER DATA CLOUD WORK PACKAGES

Work Packages and Deliverables

Work Package Ex: Project-fit Blueprint and Technical Design Document

Ex: Consult on RaaS, IdentitySync, Consent Management
Ex: Import of users

Description Ex: Creation of integration documents

Ex: Consultation of Client’s UX and technical designs
Ex: Migration of user profile data
Ex: Best practices review

Project hours Ex: Phase 1 is scheduled to utilize 200 of the 750 contracted hours

End deliverable(s) Ex: Project-fit Blueprint and Technical Design Document

11.1. Project Exclusions

● Work not included in the above scope will be considered out of scope of this project.

11.2. Risks

● Client is held responsible for development, as recommended by SAP Customer Data Cloud.
● Delay by Client team will result in the project delivery being delayed.

15
 ● SAP Customer Data Cloud recommends limiting the number of users that can access the RaaS
screensets (in the Development environment) to control deployments and updates to screensets
and policies.
● SAP Customer Data Cloud will be in code freeze state from November - January. No
amendments (i.e. product features) will be deployed to SAP Customer Data Cloud’s production
environment within this period.

11.3. Project Controls

● Any changes to the scope or plan will result in resource adjustment and possible project delay.
● Any changes to the project that affect scope and/or fees must be documented and agreed to in
writing by both Client and SAP Customer Data Cloud before commencing work; if additional
hours are needed beyond the total authorized in this Blueprint, another Work Order or Change
Order will be required.
● Client and SAP Customer Data Cloud must agree to the project schedules (i.e. sprints) and
systems used to track the project. Access to agreed upon platforms must be provided before
development begins.

11.4. Scope Change and Project Tolerance

● Deviation from the agreed scope, may result in the project being put on hold until a change
assessment has been completed. Scope change will be managed through a change request
process whereby the Implementation Consultant will assess the impact of the change, estimate
the cost and timescales required to implement the change and request sign off from the client.
● Agreed timelines and scope rely on the following:
a. Timely supply of any documentation and assets from client or third
parties as agreed in the above document.
b. Timely written feedback and approval of work in progress and final
deliverables according to the agreed project plan.
c. No change to the project scope and deliverables once agreed
d. No change in direction once project deliverables are approved

12. CLIENT SIGN OFF

The undersigned acknowledge they have reviewed the <Project Name> plan and agree with the approach it
presents. Changes to this Project-fit Blueprint will be coordinated with and approved by the undersigned or their
designated representatives.

16
Client

Signature

Full Name

Title

Date

17