Design Review Service for SAP Commerce Cloud
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
Scope Document for 50158487 custom field package for Design Review Service for SAP Commerce Cloud
- SCOPE OF SERVICES
Customer is undertaking activities utilizing SAP Software. Customer is the owner of the project and has overall responsibility for the project and the process, scope, costs, resources, and targeted solutions.
SAP will provide the following services to assist Customer with the assessment of the potential use of SAP Commerce Cloud as specified herein: design review service for SAP Commerce Cloud Solution (“Service(s”).
-
- 1 Scope
-
-
The SAP consultant(s) assigned to the Services will execute one design review for SAP Commerce Cloud solution. The objective is to analyze and validate the proposed solution design of SAP Solution across key implementation disciplines, and document specific findings with actionable recommendations.
The following scope items form the scope of the Services to be provided by SAP and covers the following applications only:
-
1. SAP Commerce Cloud
- Data model for Customer, Product and Pricing
- Integrations to back-end systems – Master data and Orders
- Catalog designs for Product and Content
- SAP Commerce Cloud Profiles
- Order Management
- Solr Index design
- Up to five (5) third party integrations
-
- 1.1 Functional Scope Details
To enable SAP to perform the Services, the Customer must provide the following information prior to the start of the Services:
- SAP Commerce Cloud functional and non-functional specifications documents
- Role, profile, and security design document
- SAP Commerce Cloud detailed technical design documents
- Key design decision logs
- Architecture documentation including application, logical, physical, and integration design documents
-
- APPROACH AND RACI
The Service will follow a 4-phase approach. The table below shows the phases and corresponding activities.
- Responsible (R): Charged with performing the activities. A mutually agreed project plan may define further details at the work unit level.
- Accountable (A): The Customer has overall accountability for its implementation and all the activities identified below. Hence, Accountable (A) does not appear for the activities below.
- Consulted (C): Provides input on how to perform the activity and supports the execution of the activity.
- Informed (I): Provided with information.
- Consulted (C): Provides input on how to perform the activity and supports the execution of the activity.
- Informed (I): Provided with information.
-
|
Activity
|
SAP
|
Customer
|
|
Prepare Phase
|
|
|
|
Carry out preparatory steps as needed to perform the Services
|
C
|
R
|
|
Prepare SAP’s schedule
|
R
|
I
|
|
Prepare a recommended Services structure including key roles and templates
|
R
|
C
|
|
Confirm Services structure
|
C
|
R
|
|
Prepare the kick-off workshop including presentation, schedule and list of participants
|
R
|
C
|
|
Confirm, in writing, completion of pre-requisites (see section 1.2)
|
C
|
R
|
|
Hold Kick-Off: Communicate the background of the Services, roles and responsibilities, schedule, expectation and approach
|
C
|
R
|
|
Explore Phase
|
|
|
|
Conduct an initial call with the Customer team to understand their current solution and landscape setup
|
R
|
C
|
|
Review and analyze the proposed solution design
|
R
|
C
|
|
Conduct initial review of provided documents
|
R
|
I
|
|
Schedule Q&A sessions with Customer to provide additional information or insight, at SAP’s discretion.
|
R
|
I
|
|
Review and analyse business processes and needs to the solution design
|
R
|
I
|
|
Assess design of solution against SAP Best Practices
|
R
|
I
|
|
Realize Phase
|
|
|
|
Identify solution design risks and provide recommendations to improve solution design
|
R
|
C
|
|
Prepare final assessment report
|
R
|
I
|
|
Schedule one preliminary observation debrief discussion with the Customer Subject Matter Expert’s and Project Sponsor
|
R
|
C
|
|
Provide assessment report to Customer
|
R
|
C
|
- SCHEDULE
The period during which the Services shall be provided shall be mutually agreed between the parties. The estimated duration for the Services is 3 consecutive weeks.
- ORGANIZATION
- 4.1 SAP Team
The key SAP roles are as follows:
|
SAP Team
|
Level of Involvement
|
|
Project Manager
|
Single resource. Part-time. Offsite.
|
|
SAP Commerce Cloud Architect
|
Single resource. Part-time. Offsite.
|
|
SAP Commerce Cloud Functional Consultant
|
Single resource. Part-time. Offsite.
|
|
SAP Commerce Cloud Technical Consultant
|
Single resource. Part-time. Offsite.
|
- 4.2 Customer Team
The Customer team will include the following roles. Customer team is assumed to be available to complete Customer activities.
|
Customer Team
|
Description
|
Level of Involvement
|
|
Project Sponsor
|
Decision maker on scope, priorities, budget and changes issues. Active advocate for the project.
|
Single resource. Part-time.
|
|
Project Manager
|
Single point of contact for management of resources, resolving issues, project plan, project status and decision-making process through the steering committee.
|
Single resource. Part-time.
|
|
Business Lead (Decision Maker)
|
Owns business processes, approves the solution and is the key liaison between the project and the business.
|
Single resource.
|
|
Business / Subject Matter Experts
|
The subject matter expert represents the business. Provides information on business processes from the point of view of the business users.
|
Multiple resources. Part-time.
|
|
Technical Lead / Data Lead / Architect
|
Responsible for architecture, data and technical implementation decisions on the project
|
Multiple resources. Part-time.
|
|
Technical / Integration / Development Subject Matter Experts
|
Subject matter expert on relevant technical implementation details (integrations, catalog design, continuous integration...)
|
Multiple resources, as needed.
|
- SAP DELIVERABLES
5.1 SAP Deliverables
The following table lists the SAP Deliverables.
|
Deliverable
|
Deliverable Description
|
Completion Criteria
|
Deliverable Procedure
|
|
Kick-off Workshop Materials
|
Documents defining the Services delivery approach, objectives, roles, and schedule.
|
Handover of the workshop materials.
|
Approval upon completion
|
|
Assessment Report
|
Documentation of the key findings and recommendations of the Services including an executive summary.
|
Handover of final assessment report.
|
Approval upon completion
|
- 5.2 Deliverable Procedure
Approval upon completion: SAP Deliverables shall be deemed completed and approved by Customer when the above completion criteria have been met.
- CUSTOMER RESPONSIBILITIES
Customer has the following responsibilities. If Customer does not fully meet or fulfil any of the specified responsibilities or requirements in this Agreement, this shall result in a delay of the provision of the Services or an increase of the fees.
6.1 Service-specific Customer responsibilities
- Customer shall provide SAP documentation that contains necessary information to conduct the Services.
- All prerequisite documentation identified, in section 1.2 above, must be provided in English.
- Customer shall provide any necessary project documentation per section 1.2 above, list of pain points, 5 business days prior to the start of the Service.
- Customer shall provide a walk through of their SAP Commerce Cloud implementation, the context, and scope.
Participation of the Customer support/project team members not limited to, and leaders in all stages of the Service
6.2 General Customer responsibilities
- Customer shall ensure that Customer team members are knowledgeable about the scope as defined in section 1 and define their training approach and schedule. Customer shall ensure that key users are available for all workshops and activities as needed.
- Minimize the change in personnel throughout the duration of the Services.
- If third-parties on Customer side are involved: Customer shall manage any Customer’s third-party contractors and be responsibility for the acts, omissions and defects of such third-party that Customer contracts or instructs to perform Customer’s duties.
- Supply SAP with the names and contact information of key Customer and third-party resources.
- Customer shall carry out organizational change management activities, training and knowledge transition activities which include, but are not limited to the following: communication plan, organizational transition plan, business readiness for go live, design and roll-out of end-user training, coordination with remote sites, and project communication to the company.
- Customer shall ensure that a consistent, stable, and fast SAP remote support connection/service connection is available between SAP and the Customer at the required times.
- Customer shall provide SAP with the necessary authorizations for remote access to Customer’s systems.
- Customer shall allow the use of SAP laptops and mobile devices on Customer’s network to SAP’s network via SAP’s Virtual Private Network (VPN) protocols; otherwise, Customer shall provide PCs and/or laptops with the Microsoft Office Suite and e-mail capability for the SAP team. Laptops and/or PCs provided by Customer must have the latest virus protection software.
- Customer shall provide technical advice regarding any third-party systems to which the team will have access.
- Customer shall sign-off Deliverables in accordance with section 5.
- Customer shall comply with all current governmental and regulatory requirements, including but not limited to GDPR.
7. ASSUMPTIONS
The following assumptions apply
7.1 Services Specific Assumptions
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:
- Q&A sessions will be initiated by SAP only during the design review service for SAP Commerce Cloud. These sessions are intended for the Customer to provide answers to SAP.
- The design review service for SAP Commerce Cloud is not intended to be a substitute or replacement for detailed requirements gathering, review, and solution engineering and design modification.
- Customer shall provide business process/subject matter experts to provide walkthrough and be available for ad-hoc questions/follow-ups during the course of the Services.
7.2 General Assumptions
- SAP may require up to 2 weeks to assemble a team. SAP reserves the right not to start the Services until SAP has assembled a team.
- Services are delivered remotely.
- The project language and corresponding documentation is English. The Servicesdocumentation and related Tools shall be delivered in English only.
- Services are based on a predefined scope and delivery approach. In performing the Services, SAP may utilize accelerators such as SAP Best Practices.
- SAP may use certain software and tools (all referred to as Tools herein) for its work, for which the rights are not already regulated through a software license agreement. All title to and rights in Tools, including without limitation copyright and rights of authorship, remain with SAP or SAP SE. These Tools may be copied to Customer’s system and Customer is granted non-exclusive rights to use Tools for the term of and solely for the purposes related to the Services. No other use, including the creation of further copies or use on another system, is permitted. Tools and all permitted copies of Tools must be deleted at the end of the Service. If at SAP’s sole discretion Tools are left on the system for documentation purposes, Customer is not permitted to use Tools for any other remaining purpose except documentation. Such Tools are on an as-is basis with no warranty. SAP will not support or enhance the Tools beyond what is provided during the term of the Services.
- All supporting documentation will be developed using personal computers/laptops using Microsoft Office applications (Word, Excel, MS Project, PowerPoint) or other mutually agreed documentation tools.
8. EXCLUSIONS
The following assumptions apply
8.1 General Exclusions
- Deliverables not explicitly described in this Scope Document.
- Procurement of software licenses (SAP and non-SAP licenses).
- Developments that modify the standard SAP Software source code including, but not limited to,to existing user exits.
- WRICEF development objects (Workflows, Reports, Interfaces, Conversions, Enhancements and Forms).
- Programs or content to migrate data. Data cleansing of migrated data from Customer systems.
- Upgrade to the SAP solution components, operating systems or database systems.
- Any testing activities.
- Any work in quality assurance or production environments.
- Customer specific catalogues (aka entitlements, product inclusions and product exclusions)
- A detailed mitigation plan addressing the identified risks and issues.
- No code or system changes will take place during this design review assessment, such as changes to configuration – only recommendations will be given.
- UX/UI reviews.
- Implementation or execution of any type of actions to mitigate the identified risks and issues.
- Pre-Go-Live check to ensure solution is “Production Ready”
- Addressing or resolving any OSS messages.
- Taking over any responsibility regarding the management of the project.
- Organization Change Management activities, knowledge transfer and end-user or SAP Commerce Cloud administrative trainings.
- Data cleansing or data cleanup.
- Any work to be performed on Customer’s legacy systems.
- Performance related issues will not be addressed or resolved.
9. DEFINITIONS
The following assumptions apply
- “SAP Best Practices” means SAP’s predefined business processes, configuration content and documentation for SAP Software. SAP Best Practices may be used as the basis for SAP implementation activities.
- “WRICEF” means
- Workflows: a workflow is a sequence of connected steps triggered by an event to automate a process such as a document approval. Examples include SAP Business Workflows.
- Reports: technical objects designed to deliver business figures or reports with no change to application data.
- Interfaces: technical objects to transfer information from one system to another, usually referring to objects that are not part of the SAP licensed Software. Examples of technology include SAP Process Orchestration and Intermediate Documents (IDocs).
- Conversions: technical objects used to migrate data to SAP systems during the Service. Examples of technology include data migration programs, SAP Data Services and Legacy System Migration Workbench (LSMW).
- Enhancements: changes and additions to SAP functionality using development objects specifically provided for Customer changes. Examples include the use of user exits and business add-ins .
- Forms: printed or electronic forms containing formatted information from SAP applications. Examples of technology include SAPscripts, Smart Forms and SAP Interactive Forms by Adobe.“GDPR”: means the General Data Protection Regulation under Law No. 2016/679 (EU).
