Scope Document: 50139298 – Implementation of SuccessFactors Recruiting Posting

Scope Document for SAP Implementation for SAP Cloud Service

The SAP Service Description for SAP Implementation – SAP Cloud Service Recruiting Posting (hereinafter: Service
Description) as to be found at: http://www.sap.com/servicedescriptions.

This Scope Document specifies the Services to be performed.

1 Scope of Services ............................................................................................................................2

1.1 Solution Scope - Recruiting Posting Factory Implementation Solution......................................2
1.1.1 Additional Scope & Assumption for Medium Complexity ............................................................2
1.1.2 Additional Scope & Assumption for High Complexity .................................................................3
1.2 Integration Scope......................................................................................................................3
1.3 Workflows, Reports, Interfaces, Conversions, Extensions, and Forms (WRICF) ........................3
1.4 Pre-requisites ...........................................................................................................................4
1.5 Geographic and Organization Scope.........................................................................................4
1.6 Data Migration Scope ...............................................................................................................4
1.7 SAP Cloud Services..................................................................................................................4
1.8 Third Party Software .................................................................................................................4
2 Project Approach ..............................................................................................................................4
3 Customer Responsibilities ................................................................................................................7
4 Project Schedule ..............................................................................................................................7
5 Project Organization .........................................................................................................................7
5.1 SAP Team ................................................................................................................................7
5.2 Customer Team ........................................................................................................................7
5.3 Project Governance ..................................................................................................................8
5.4 Escalation and Issue Management............................................................................................8
6 SAP Deliverables and Acceptance....................................................................................................8
6.1 Deliverables ..............................................................................................................................8
6.2 Acceptance Process .................................................................................................................9
7 Assumptions and Exclusions ............................................................................................................9
7.1 Assumptions .............................................................................................................................9
7.2 Exclusions ..............................................................................................................................10

Confidential
Scope Document Template – SAP Implementation for SAP Cloud Service ENGLISH v.12-2015 1
1 Scope of Services
SAP will provide Services to assist Customer with the implementation of the Customer’s Project.
1.1 Solution Scope - Recruiting Posting Factory Implementation Solution
The scope for Recruiting Posting Factory solution has been defined in two different complexities: Medium and High
The following HR Core functionalities listed in the table for will be available for the respective complexity level. However,
based on the complexity determined the additional scope mentioned in the additional scope section will be added to HR
Core scope. The “User-Defined Option” column in the following table states the design parameters or configuration
selections available to the licensee

HR Core Scope
Product Module / Scope Scope Details Customer Defined
Item Options
Recruiting Posting RP / Medium • Configure up to 25 unique • Job boards
Complexity job boards • University
• Configure up to 300 boards
Standard university boards • Users
Timeline: 15 • Configure up to 50 unique • ATS
Weeks users • Product demos
• ATS Integration
• Project Management (32
Hours)
• Customer Responsibility for
all Vendor Management
• Single Entity
• Multiple, standard demo of
module including full Q&A
Recruiting Posting RP / High • Configure up to 25 unique • Job boards
Complexity job boards • University
• Configure up to 300 boards
Standard university boards • Users
Timeline: 19 • Configure up to 50 unique • ATS
Weeks users • Product demos
• ATS Integration
• Project Management (100
hours)
• SAP responsible for vendor
management
• Single Entity
• Multiple, standard demo of
module including full Q&A

1.1.1Additional Scope & Assumption for Medium Complexity

SuccessFactors will configure the following Recruiting Posting components in English:

• Configure up to 25 unique job boards determined by customer.

• Configure up to 300 university boards determined by customer.
• Configure up to 50 unique users determined by customer.
• Integration to Applicant Tracking System; SuccessFactors Recruiting Management.
• 32 hours of Project Management and functional consulting to create & review timeline,
create & review workbook, maintain budget, execute change orders, manage technical
resources, product demos and ongoing assistance in collecting data from vendors.
• One (1) business unit will be configured as determined by the customer.

Confidential
Scope Document Template – SAP Implementation for SAP Cloud Service ENGLISH v.12-2015 2
 • Two (2) product demos performed with customer including full Question & Answer
sessions.
• Customer does not need prior knowledge about the Recruiting Posting module.
• Customer manages vendor communication and collection of data from vendors with
support from SAP including iterative review of required information and a feedback loop
including next steps when needed to help in collecting information from vendors.
1.1.2Additional Scope & Assumption for High Complexity
SuccessFactors will configure the following Recruiting Posting components in English:

• Configure up to 25 unique job boards determined by customer.

• Configure up to 300 university boards determined by customer.
• Configure up to 50 unique users determined by customer.
• Integration to Applicant Tracking System; SuccessFactors Recruiting Management.
• 100 hours of Project Management and functional consulting to create & review timeline,
create & review workbook, maintain budget, execute change orders, manage technical
resources, product demos and ongoing assistance in collecting data from vendors.
• One (1) business unit will be configured as determined by the customer.
• Three (3) product demos performed with customer including full Question & Answer
sessions.
• Customer does not need prior knowledge about the Recruiting Posting module.
• SAP manages vendor communication and collection of data from vendors on behalf of the
customer. SAP will require written authorization from customer allowing Professional
Services to serve as their representative with vendors.

1.2 Integration Scope

The following SAP standard integration points between SAP systems are part of the scope.

SAP Standard Source Target System Details Solution Scope from Section
Integration Point System 1.1

Requisition Data SuccessFactors SuccessFactors Includes all data elements in SFSF Recruiting Posting
RCM RP Recruiting Management using
SuccessFactors Recruiting
Management standard xml file
format. Customer is
responsible for the
transformation and data
mapping routine for import
into their application.

1.3 Reports and Training

For the standard product, reports will be selected by the customer at time of launch and will be delivered via email to
parties designated by the customer. All training will be provided via selected scope. Therefore, following delivery, they
will not be subject to services, defect resolution, maintenance or upgrades or in any other way be within scope of SAP
Services objects delivered as part of the Customer’s project. Following delivery, all further enhancements, maintenance
and general requests will not be part of the original implementation and will require additional contracted services.

1.4 Pre-requisites

Customer will have the following Software fully functional before the start of the Project:
Confidential
Scope Document Template – SAP Implementation for SAP Cloud Service ENGLISH v.12-2015 3
 Product Product Version / Support Component Description
Package

Recruiting Management n/a n/a Job

1.5 Geographic and Organization Scope

Geographic and Organization Scope In Scope

Number of Customer legal entities 1

Languages English

1.6 SAP Cloud Services

Development, Quality Assurance, and Production Environment based on customer license.

Customer will go live at the then current product version of the SAP Cloud Service.

Product The functionality and configuration Module

settings are based upon the following
version:

SuccessFactors Recruiting Posting Latest Multi-Posting

1.7 Third Party Software

Customer will ensure authorized access to the following third party software before the start of the Project:

Product Product Version / Support Package Component

Vendor Job Boards Latest n/a

2 Project Approach
The main project activities are detailed below with the assumed lead and support responsibility indicated.
Customer acknowledges and agrees that failure on the part of Customer to meet or fulfil any of the specified Customer
responsibilities or requirements in this document might result in a delay in the project and/or a Change Request for
additional SAP resources, an increase in project fees and/or a change in the schedule.
The project follows the applicable parts of the SAP Activate methodology with the following responsibility matrix of tasks
per phase. The Customer has the overall accountability for the whole project and all its elements.
• Responsible (R): Charged with performing the activities. The project plan may define additional detailed responsibility
at the work unit level.
• Accountable (A): The Customer has overall accountability for the whole Project and all the tasks identified below.
Hence, Accountable (A) does not appear for the tasks below.
• Consulted (C): Provides input on how to produce the activity and actively supports the execution of the activity.
• Informed (I): Provided with information.

Medium Complexity

Confidential
Scope Document Template – SAP Implementation for SAP Cloud Service ENGLISH v.12-2015 4
 Task SAP Customer

Cross Phase Tasks

Maintain and update relevant project management documents, e.g. project charter, project plans,
R R
risk and issue logs and status reports

Organizational change management activities, training and knowledge transition activities.

Organizational change management includes, but is not limited to the following: communication
I R
plan, organizational transition plan, business readiness for go live, design and rollout of end-user
training, coordination with remote sites, and project communication to the company.

Resolve questions or issues raised to Customer from the project team (either SAP or Customer
I R
resources) within 16 business hours of notification OR promptly as not to effect the Project schedule.

Prepare Phase

Project Preparation

Kick-off (Sales to PSE transition) R A

Initiation - Including Project Team Orientation, resourcing, customer meetings, co-ordination R I

Start System Provisioning

Provisioning Access Request (Include System Landscape) R A

Customer Instance Setup

Conduct System Admin and Setup and instance setup R I

Preliminary testing of the instance for functionalities provided by the SAP Best Practices (RDS)
R I
solution

Factory Lead Tasks

Factory Lead Tasks A I

Project Communication

Support (Ongoing communication and status) A I

Explore Phase

Customer Workshop

Workshop demonstration (RP topics with reporting & Configuration Workbook walkthrough) R A

Perform a fit-gap analysis based on customer's requirements R A

Document configuration changes in the Configuration Workbook R C

Review of Workbook with Customer R R

Solution Configuration - Phase 1

Design and implementation approach R I

Create and implement job & university boards R I

Configure users R I

Testing of phase R I

Confidential
Scope Document Template – SAP Implementation for SAP Cloud Service ENGLISH v.12-2015 5
 Task SAP Customer

Customer review of phase R R

Customer feedback A R

Realize Phase

Solution Configuration - Phase 2

Design and implementation approach R I

Create and implement job & university boards R I

Configure users R I

Testing of phase R I

Customer review of phase R R

Customer feedback A R

Solution Configuration - Phase 3

Design and implementation approach R I

Create and implement job & university boards R I

Configure users R I

Testing of phase R I

Customer review of phase R R

Customer feedback A R

Solution Execution Testing

UAT Support C R

Deploy Phase

Production Cutover / Switch to Production - Go Live in Production

Deploy instance to live status R A

Production instance testing and resolution R R

Delivery to Support Handover

Hyper Care Support - 2 weeks C A

Go Live Support

Provide go-live and post go-live support. I R

Hand Over Deliverables

Hand over the Deliverables to the Customer Project Manager. R A

The project language is English and all documentation will be prepared in English. Project meetings will be held in
English and Change Requests and minutes will be prepared in English.

Confidential
Scope Document Template – SAP Implementation for SAP Cloud Service ENGLISH v.12-2015 6
High Complexity

Task SAP Customer

Cross Phase Tasks

Maintain and update relevant project management documents, e.g. project charter, project plans,
R R
risk and issue logs and status reports

Organizational change management activities, training and knowledge transition activities.

Organizational change management includes, but is not limited to the following: communication
I R
plan, organizational transition plan, business readiness for go live, design and rollout of end -user
training, coordination with remote sites, and project communication to the company.

Resolve questions or issues raised to Customer from the project team (either SAP or Customer
I R
resources) within 16 business hours of notification OR promptly as not to effect the Project schedule.

Prepare Phase

Project Preparation

Kick-off (Sales to PSE transition) R A

Initiation - Including Project Team Orientation, resourcing, customer meetings, co-ordination R I

Start System Provisioning

Provisioning Access Request (Include System Landscape) R A

Customer Instance Setup

Conduct System Admin and Setup and instance setup R I

Preliminary testing of the instance for functionalities provided by the SAP Best Practices (RDS)
R I
solution

Factory Lead Tasks

Factory Lead Tasks A I

Project Communication

Support (Ongoing communication and status) A I

Explore Phase

Customer Workshop

Workshop demonstration (RP topics with reporting & Configuration Workbook walkthrough) R A

Perform a fit-gap analysis based on customer's requirements R A

Document configuration changes in the Configuration Workbook R C

Review of Workbook with Customer R R

Vendor Asset Collection (Vendor Management) R C

Solution Configuration - Phase 1

Design and implementation approach R I

Confidential
Scope Document Template – SAP Implementation for SAP Cloud Service ENGLISH v.12-2015 7
 Task SAP Customer

Create and implement job & university boards R I

Configure users R I

Testing of phase R I

Customer review of phase R R

Customer feedback A R

Realize Phase

Solution Configuration - Phase 2

Design and implementation approach R I

Create and implement job & university boards R I

Configure users R I

Testing of phase R I

Customer review of phase R R

Customer feedback A R

Solution Configuration - Phase 3

Design and implementation approach R I

Create and implement job & university boards R I

Configure users R I

Testing of phase R I

Customer review of phase R R

Customer feedback A R

Solution Execution Testing

UAT Support C R

Deploy Phase

Production Cutover / Switch to Production - Go Live in Production

Deploy instance to live status R A

Production instance testing and resolution R R

Delivery to Support Handover

Hyper Care Support - 2 weeks C A

Go Live Support

Provide go-live and post go-live support. I R

Hand Over Deliverables

Confidential
Scope Document Template – SAP Implementation for SAP Cloud Service ENGLISH v.12-2015 8
 Task SAP Customer

Hand over the Deliverables to the Customer Project Manager. R A

The project language is English and all documentation will be prepared in English. Project meetings will be held in
English and Change Requests and minutes will be prepared in English.

3 Customer Responsibilities
In addition to the Customer responsibilities as set forth in the Service Description, the Customer is in particular
responsible for the following during the Project:
1. Finalizing the configuration workbook
2. Vendor management (if medium complexity)
3. Phase approval and sign-off
4. Production site deliverable review and sign-off
4 Project Schedule
The current estimated schedule for the Service is as follows.

Estimated Schedule for Phase Estimated Duration (Weeks) Planned Start Date

Prepare 4

Explore 5.5

Realize 3

Deploy 1

5 Project Organization
5.1 SAP Team

The key SAP project roles are as follows.

SAP Team Level of Involvement

Senior Business Process Consultant Single resource. Part-time. Offsite.

Technology Consultants Multiple resources. Part-time. Offsite

5.2 Customer Team

The Customer Project team will be as follows:

Customer Project Responsibility / Description Level of Involvement

Team

Project Manager Selects and allocates the appropriate subject matter experts Full-time
for the key user roles on the project
Ensures that the resources will be available for the agreed
upon duration and percentages of time
Ensures Key and End User enablement
Manages the change management and risk management
processes
Ensures the project activities especially data migration and
testing remain on track as per the agreed upon plan

Confidential
Scope Document Template – SAP Implementation for SAP Cloud Service ENGLISH v.12-2015 9
 Manages the relationship with all third party resources.
Provides status reporting

Technical Consultant Reviews configuration workbook for technical feasibility. Part-time

Configures module per best practices.
Reports issues and status to Project Manager.
Tests module for compliance with implementation design.

Business Key Users Functional area subject matter experts Multiple, Part-time
Undertake the set-up, implementation and migration tasks to
support the business areas in scope.
Review workflow and integration scenarios.

5.3 Project Governance

Customer and SAP agree that it is necessary to have a project governance structure and processes in place to support
execution of the Service.

Customer and SAP will work cooperatively during the Prepare phase to establish the Program Governance model. To
facilitate communication between SAP and Customer, an SAP and Customer status meeting to clarify open issues and
questions will occur weekly.

5.4 Escalation and Issue Management

In the event that any issues are not resolved by the project team the Customer and SAP shall be entitled to escalate such
issue in accordance with the table below:

SAP Representative Customer Time goal (not binding) for each level to resolve the issue
Representative before escalation to the next level.

1. SAP Project Manager Customer Project 1 Business Day

Manager

2. SAP Director of Delivery Customer Executive 2 Business Days

Management Sponsor

6 SAP Deliverables and Acceptance

6.1 Deliverables
The following table lists the SAP Deliverables.

Deliverable Description
Phase Deliverable Completion Criteria
[omit if not needed]

Explore Configuration Workbook Document detailing the list of Configuration workbook is delivered to Customer.
additional configurations
identified during the
validation workshops.

Explore Phase 1 of RP module First phase of functioning RP Phase 1 is delivered to the customer and customer
deliverable instance for customer review. feedback is documented.

Realize Phase 2 of RP module Second phase of functioning Phase 2 is delivered to the customer and customer
deliverable RP instance for customer feedback is documented.
review.

Confidential
Scope Document Template – SAP Implementation for SAP Cloud Service ENGLISH v.12-2015 10
 Deliverable Description
Phase Deliverable Completion Criteria
[omit if not needed]

Realize Final phase of RP module Final phase of functioning RP Final phase delivered to the customer and customer
deliverable instance for customer acceptance is completed including customer sign-off.
acceptance and sign-off.

Deploy RP production instance Production instance is Production instance is delivered to the customer and
deliverable delivered to customer during customer acceptance is completed.
go-live process.

7 Assumptions and Exclusions

The following assumptions and exclusions apply in addition to those set forth in the Service Description. The price in the
Order Form is partly based on these assumptions.
7.1 Assumptions
• If the Project has not started within two (2) months of the Estimated Start Date as set forth in the Order Form, then a
Change Order may be required for work to be carried out on the Project or SAP has the right to terminate the Scope
Document without the Customer being able to claim damages.
• SAP may require up to two (2) weeks to assemble a project team. SAP reserves the right not to start the Project until
SAP has assembled a project team
• No more than one (1) business days of workshops will be undertaken during the Explore phase.
• SAP will execute integration testing for up to two (2) continuous business days which will not exceed three (3) SAP
person days.
• SAP will provide up to one (1) continuous business days of knowledge transfer to project team members to a
maximum of one (1) SAP person days.
• No more than one (1) Customer project team members will attend the knowledge transfer workshop.
• SAP will assist the Customer with User Acceptance Testing for up to two (2) continuous business days which will not
exceed two (2) SAP person days.
• No more than xxx (#) Customer persons will execute User Acceptance Testing.
• SAP will provide up to one (1) continuous business days of go live support to a maximum of one (1) SAP person days,
remotely. Go live support will begin when the technical cutover has been executed by Customer, unless a different
date is agreed upon through the approval of a Change Order. Cutover to Production is expected to be executed by
Customer within three (3) days after knowledge transfer has been completed. Production validation by Customer is
considered part of the period of go live support.
• Prior to Project closure, Customer is not permitted to change any customizing settings since this may interfere with
the implementation of the Project.
• Part time resources over and above those identified in the Customer project team will be used to diversify the
knowledge base and reduce risk. Other business and technical experts from within Customer will participate on an as
needed basis.
• Customer acknowledges that the Services performed may include the export of Customer data. The Customer is
responsible that all Customer data provided to SAP does not contain any sensitive defense information for which the
export of such data would violate the International Traffic in Arms Regulations or any other applicable export control
laws or regulations.
• One (1) job board is the equivalent of one (1) configuration, contract, template, etc.
• One (1) user is the equivalent of one (1) entity or group.
• Each user must post under a single brand/entity unless explicitly named in the statement of work.
• The full scope of the Service is to be deployed during a single user rollout cycle. The scope of the Service will not be
divided into phased functionality deployments or multiple rollout schedules to groups of users.
• The full scope of the server is to be deployed in the Production instance only.
• SAP will have access to Customer telephones with both international and domestic calling access and Customer will
be responsible for any charges associated with such telephone use by SAP related to the project.

Confidential
Scope Document Template – SAP Implementation for SAP Cloud Service ENGLISH v.12-2015 11
• For the high complexity model only, customer will need to provide written authorization for SAP Services to engage
third-party vendors on their behalf.
7.2 Exclusions
Any items or services not defined as in scope for this Service are deemed out of scope, including, but not limited to the
following exclusions:

• Deliverables not explicitly described in this Scope Document.

• Multiple business units or lines of business unless explicitly named in the statement of work.
• An analysis of as-is business processes.
• Programs or content to migrate data.
• Data cleansing or data clean up.
• Coordination of work required from Customer’s third party vendors.
• Formalized training on the SAP Cloud Service for project team members or training for users. This would be included
in a separate Scope Document for Education Services. Knowledge transfer does not replace training.
• Content for end user training.
• The development of new functionality, extensions or co-innovation.
• Verification and validation testing processes that may be required by regulatory, industry or governmental
requirements.
• Implementation of any solution or integration scope not explicitly mentioned in this document.
• Implementation on any additional servers not explicitly mentioned in Section 1.X of this document
• Customer specific authorizations roles and security concepts. SAP will use the standard authorization content
provided with the SAP Cloud Service.
• Custom developments and software developments.
• Any changes required because of pre-existing Customer specific enhancements or developments.
• Any changes required because of quality or values of Customer’s master and transactional data.
• Unit testing in any other environment besides the environment where the initial configuration was completed.
• Testing using more than one application language. Only content in English will be tested.
• Interfaces to third party or to legacy systems not defined.
• Reports that are not in the SAP standard application or modifications to these standard reports.

Confidential
Scope Document Template – SAP Implementation for SAP Cloud Service ENGLISH v.12-2015 12