Analysis implementation service for SAP SuccessFactors Workforce Analytics
Terms and Conditions
By clicking "Accept" or “Agree,” you agree to all of the terms and conditions stated in this Agreement. If you do not agree to these terms, do not click "Accept" or “Agree.” By clicking “Accept” or “Agree” you hereby represent and warrant that you have been given the power of attorney by your employer (“Customer”) to carry out this transaction and conclude the respective contracts with SAP on behalf of your employer. If you do not have the appropriate power of attorney, we kindly ask you to not continue with this transaction.
Once completed, this agreement (defined below) is a legally binding agreement for SAP Services between Customer and the SAP affiliate or subsidiary company in the country in which Customer is located and from whom Customer is ordering the Services displayed in the Purchase Review and Order Confirmation (both defined below) (“SAP”).
Please note, that the transaction will only be completed, and the contract formed, when SAP accepts Company’s offer by either SAP sending an order confirmation e-mail to Customer, or the Services have been made available to Customer by SAP. Until then, if any issue arises regarding the processing of the order, SAP reserves the right to cancel the transaction and Customer will be notified accordingly
This order document (Order Form) is governed by and incorporates the following documents in effect as of the effective date. All documents are listed in order of precedence, and collectively referred to as the “Agreement”:
|
Agreement
|
Location
|
|
Order Form (including Scope
Document)
|
This Order Form and Exhibit 1
|
|
Data Processing Agreement for SAP Services (“DPA”)
|
https://www.sap.com/about/trust-center/agreements/onpremise/data-processing-
agreements.html?tag=agreements:data-processingagreements/support-professional-services
|
|
SAP Services General Terms and Conditions (“GTC”) (for country in which Customer is located)
|
https://www.sap.com/about/trust-
center/agreements/services/sap-professionalservices.html?tag=agreements:general-terms-andconditions/services-customer-direct-or-sap-as-prime
|
Customer has had the opportunity to review the Agreement, including without limitation the Scope Document, the GTC, the DPA and terms and conditions mentioned above, prior to accepting this Agreement. For purposes of this Agreement, the following provisions of the GTC shall not apply: Change Request Procedures (generally section 4) and Satisfaction with Personnel (generally section 5).
SAP recommends Customer prints copies of this Order Form, the applicable DPA and GTC for Customer’s own records.
-
SERVICES FEES AND PAYMENTS
The applicable Service fees (“Service Fees”) for the Services are identified in the purchase review displayed on the SAP Store (“Purchase Review”) as well as in the corresponding order confirmation email Customer receives from SAP (“Order Confirmation”). The Service Fees are payable by Customer as follows.
(a) If Customer is registered as an authorized buyer of SAP products, Customer may choose to pay the Service Fees via invoice. SAP will invoice Customer and payment is due 14 days after the invoice date. (b) If Customer is not registered as an authorized buyer, Customer must use a valid credit card to complete this order. Service Fees will be billed to Customer’s credit card upon Order Confirmation.
-
SERVICE LOCATION AND TAXES
Customer acknowledges that the “Ship-to” address entered by Customer in the SAP Store site is the primary location of receipt of the Service(s) (“Service Location”) and should be in the same country in which Customer is located and has its billing address. It is the obligation of the Customer to consider if withholding tax is applicable. In case of any applicable local taxes, these are to be borne by Customer. Applicable taxes have to be declared and paid to the respective tax authority by Customer. Customer’s failure to provide SAP with its VAT and/or GST number may have sales tax implications. Services Fees do not include Taxes.
-
SCHEDULING OF THE SERVICE DELIVERY
Unless otherwise stated in Exhibit 1, SAP shall contact Customer within 5 business days after Order Confirmation to schedule the start of the Service.
EXHIBIT 1: SCOPE DOCUMENT
2. Integration Scope
No integration in scope.
3. Reporting Scope
No reporting in scope
4. Data Migration Scope
No data migration in scope
5. Testing Scope
No testing in scope
6. Third Party Scope
No third-party software in scope
7. Pre-requisites
Customer will have a fully functional WFA instance in production before the start of the Project.
8. Porject 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.
|
Tasks
|
SAP
|
Customer
|
|
Provide required data from EC/HRIS
|
I
|
R
|
|
Provide high-level scope, including data scenarios to support development work
|
C
|
R
|
|
Complete technical implementation details and add to specification
|
R
|
I
|
|
Build new functionality within the WFA framework
|
R
|
I
|
|
Process refresh and publish to preview site
|
R
|
I
|
|
Review and approve publication to production site
|
I
|
R
|
|
Publish to production site and close request
|
R
|
I
|
9. Porject Schedule
Within 48 hours after placing the order for the Custom Analysis Dimension for Workforce Analytics service the Customer will be contacted by SAP to schedule the start of the service.
-
Project Organization
1. SAP Team
The key SAP project roles are as follows.
|
SAP Team
|
Service Elements in Order Form
|
Level of Involvement
|
|
Project Manager
|
Project Management
|
Single resource. Part- Time. Offsite.
|
|
Technical Consultant
|
Execution Services
|
Multiple resources. Part- Time. Offsite.
|
- 2. Customer Team
The Customer Project team will be as follows:
|
Customer Project Team
|
Responsibility / Description
|
Level of Involvement
|
|
Business Key User
|
Approve specification changes, Supply refresh/development data, and approve migration to production site.
|
Part-time
|
- 3. Escalation and Issue Management
An issues management process will be documented and established as part of the overall Project governance. The purpose of this process is to address any and all issues which arise on the Project. Additionally, it will address the prioritization of these issues as well as an effective means for issue escalation and resolution. The details of this process will be established by SAP during the Project Preparation phase, subject to Licensee’s approval. Types of issues that would be addressed through issues escalation process may include:
-
-
-
Situations that require attention and will impact cost, hours, schedule, resources or the success of the Project
-
Concerns that require attention
-
Unresolved action items
-
Change requests
-
Lack of commitment or availability of Project resources
-
Unaccepted deliverables
In the event that any issues are not resolved by the project team the Customer and SAP shall be entitled to escalate such issue.
11. SAP Deliverables
SAP will deliver an updated Workforce Analytics instance based on the scope description in Section 1.1.
12. 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.
-
-
Assumptions
-
SAP may require up to two (2) week to assemble a project team. SAP reserves the right not to start the Project until SAP has assembled a project team.
-
Prior to Project closure, Customer is not permitted to change any configuration 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.
-
The full scope of the Service is to be deployed in between scheduled refresh cycles, where it will not interfere with business as usual data refreshes as per a customer subscription agreement.
-
-
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.
-
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.
-
The development of new functionality, extensions or co-innovation.
-
Implementation of any solution or integration scope not explicitly mentioned in this document.
-
Any changes required because of pre-existing Customer specific enhancements or developments.
-
Interfaces to third party or to legacy systems not defined.
