SAP Activate Methodology For SAP Ariba

Sequence Number Title
1 Prepare
1.1 Realm Enablement

1.1.1 Review System Provisioning Process
1.2 Customer Team Self-Enablement

1.2.1 Provide Customer with Links to Learning
Materials
1.2.2 Review Ariba Learning Materials
1.3 Project Initiation and Governance
1.3.1 Conduct Handover Meeting with Sales

1.3.2 Create Project Charter and Scope Statement
1.3.3 Establish Project Governance
1.3.4 Define Project Communications and Reporting
1.3.5 Create Pre-Planning Presentation
1.3.6 Conduct Engagement Review (if applicable)

1.4 Project Plans, Schedule, and Budget
1.4.1 Create Project Schedule and Budget
1.5 End User Learning Strategy
1.5.1 Develop End User Learning Strategy
1.6 Project Standards and Infrastructure
1.6.1 Define Project Standards
1.6.2 Setup Project Team Logistics and Infrastructure
1.7 Project Kick-Off and On-Boarding
1.7.1 On-board Project Team
1.7.2 Conduct Kickoff Workshop

1.8 Phase Closure
1.8.1 Conduct Project Quality Gate
1.8.2 Obtain Customer Sign-Off for Phase Completion
1.9 Architecture Review
1.9.1 Populate Architecture Review Pre-review

Questionnaire
1.9.2 Contact Customer Regarding the Architecture

Review
1.9.3 Deliver Architecture Review Questionnaire to

Customer Team
1.9.4 Respond to Architecture Review Pre-Readiness

Questionnaire
1.9.5 Update the Architecture Review PowerPoint

Deck Template with the Customer-Specific
Details
1.9.6 Internal Review of the Architecture Review
Customer Session Deck
1.9.7 Conduct the Architecture Review Session with

the Customer
1.9.8 Architecture Review Session Follow-up
1.9.9 Review Final Deck with Customer
1.9.10 Customer Approves the Architecture Review

Customer Session Deck
1.9.11 Inform Customer of Next Steps Following the

Completion of the Architecture Review Process
1.9.12 Inform Customer of Next Steps Following the

Completion of the Architecture Review Process
1.9.13 Archive Architecture Review Material in the

Global Project Repository
1.10 Data Strategy
1.10.1 Schedule L1 Data Strategy Discussion

1.10.2 Prep for L1 Data Strategy Discussion
1.10.3 Facilitate L1 Data Strategy Discussion
1.10.4 Schedule L2 Data Strategy Discussion
1.10.5 Incorporate Customer Feedback and Prepare for

L2 Discussions
1.10.6 Facilitate L2 Data Strategy, Risk & Service Level

Discussion
1.10.7 Document and Archive Output
2 Explore
2.1 Execution/Monitoring of Project
2.1.1 Direct and Manage Project Execution

2.1.2 Update Project Management Documents
2.1.3 Manage Project Issues, Risks, and Changes
2.1.4 Communicate Project Status and Progress
2.2 Solution Planning
2.3 Solution Definition

2.3.1 Define Configuration Values
2.4 User Access and Security
2.4.1 Map Authorization Roles to Users

2.5 Integration Prerequisites Confirmation
2.5.1 Apply Integrated System Prerequisites
2.5.2 Confirm Integration Prerequisites

2.5.3 Set Up Network Connectivity and Security
2.5.4 Confirm Integration Fields and Create
Adaptation Specifications
2.6 Phase Closure and Sign-Off Phase Deliverables
3 Realize

3.1.3 Plan and Execute Agile Sprints
3.2 Solution Configuration
3.2.1 Enablement Workbook

3.2.2 Custom Header Fields
3.2.3 Contract Repository Configuration
3.2.4 Contract Process Configuration
3.2.5 Main Agreement

3.2.6 Clause Library
3.2.7 Electronic Signature Integration
3.3 Forms Adaptation Preparation

3.3.1 Mockup Standard Forms with Changes
3.4 Reports
3.4.1 Enable Customer on Standard SAP Reports
3.5 Configuration Freeze

3.5.1 Request Configuration Freeze
3.6 Site Administration Demo
3.6.1 Conduct Admin Demo for Site Admin Users
3.7 Solution Walkthrough

3.7.1 Conduct Solution Walkthrough
3.8 Internal Testing of the Test Site
3.8.1 Complete Internal Testing on Test Site

3.9 Solution Test Preparation
3.9.1 Scenario #1 - n - Prepare Test Cases
3.10 Integration Setup in the Q-Landscape
3.10.1 Create Integration Mappings and Transformation

3.10.2 Perform Integration Set Up on the Cloud System
3.10.3 Execute Initial Integrated Data Load
3.11 Learning Content
3.11.1 Develop Learning Content
3.11.2 Train the Trainer
3.12 Data Load
3.12.1 Execute and Validate Data Load

3.12.2 Support Data Load Issue Resolution
3.12.3 Conduct Final Data Quality Assessment
3.13 Solution Test Execution
3.13.1 Scenario #1 - n - Execute Test Case

3.13.2 Scenario #1 - n - Resolve Test Incidents
3.14 System User Roles and Authorization
Administration
3.14.1 Set Up Administrative Procedures for Roles and
Authorizations
3.15 Cutover Plan
3.15.1 Prepare Cutover Plan
3.16 Integration Setup on the Production System

3.16.1 Apply All Integration Prerequisites
3.16.2 Set Up Network Security and Connectivity
3.16.3 Perform Integration Setup
3.17 Phase Closure and Sign-Off Phase Deliverables
4 Deploy

4.2 End User Learning
4.2.1 Pilot Learning
4.2.2 Deploy Learning
4.2.3 Evaluate
4.3 Production Cutover
4.3.1 Moving Configurations from Test to Production

4.3.2 Production Site Testing
4.4 Delivery to Support Handover
4.4.1 Conduct the Handover to Support Meeting
4.5 Production Support After Go Live

4.5.1 Provide Post Go Live Support
4.6 Project Closure and Sign-Off Project Deliverables
4.6.2 Obtain Sign-off for Project Closure and Results

Acceptance
4.6.3 Send Customer Satisfaction Survey Request
(VOC - Voice of the Customer) to Customer
5 Run
Description
The purpose of this phase is to provide the initial planning and preparation for the project. In this phase, the project is star
optimally.
The purpose of this deliverable is to understand the provisioning process and to prepare for the receipt of the initial
After the Client signs a contract for their new SAP Ariba solution(s), their realm will be enabled with all applicable solution(
actual realm set up. Once the Client has been notified and provided access to their new site, SAP Ariba will be able recogni
Delivery Manager for staffing: Send request for Realm enablement to Customer Support: Commercial Integration Cre
Preparation Activities (Including Feature Toggle): Delivery Realm Enablement Coordinator Notify Client that Realm is Ena
The purpose of this deliverable is for the customer to learn different elements of the SAP Ariba system using self-paced ena
Solution specific training is typically included for one Client user in accordance with the Deployment Description document
Live Classroom. Special Note: Please note that this team can assist the customer with the registration in the virtual classroo
The purpose of this task is to review the training material provided by SAP Ariba.
The purpose of this deliverable is to formally recognize that a new project exists and to initiate the work on the project. Du
– such as clients, customers, and SAP management – around a project and its scope, provide upd
initiation activities the project manager conducts a handover from pre-project phase, creates a project charter document,
management process for the project. This ensures alignment between the SAP System Integrator, the customer's proj
operational requirements.
The purpose of this task is to efficiently transition the project from the sales team to the delivery team. During this task, th
transfer key information from the pre-project phase (discover or sales) into the project. The customer and partners are not
scheduled within one week of contract signing Solution Consultant completes updated Sales Handoff Document te
Services Sales, VE/NE, CEE (or RVP), Project Manager/Delivery Leads Optional Attendees: SAP Commercial Team M
2nd Call - Engagement Review Call schedules after above and within two weeks of deal close VE
Business Case/Flight Plan elements based upon sales process; CEE is responsible for completion with the Customer
realization Covers integration and r1v1 flight-panning also Attendees: Account Executiv
Customer Engagement Executive (CEE) Delivery Executive (DE) or Project Advisor (PA) Procure
Delivery Team Manager(s)' Catalog Enablement and/or assigned resource Network or Supplier Enableme
Team Manager(s) or representative (optional) Value Enablement Engineer (if applicable, not usually for Strate
Scope of Work as well as the Sales to Delivery Hand Off document, which is completed by the Sales team, should be sent to
document should be reviewed in advance of the Sales to the Delivery meeting. Realm Enablement Document also required
Delivery meeting, the Delivery Team Manager will be able to ask clarifying questions regarding scope, schedule, and/or clie
Business drivers Customer goals Success metrics for the project Solution scope Customer expectations Critical
staffing, and delivery process (if applicable) Standard Expected Deliverables (Varies based upon applicability) Signed SOW
Recording Business Case and Flight Plan Realm Enablement Form Partner Contact info and plan (if applicable)
The purpose of this task is to create a project charter and scope statement. The project charter is developed by reviewing d
the customer to facilitate an understanding of the project’s goals, business case, external assumptions, and constra
all possible benefits, and quantifies benefits in financial terms. This information and supporting documents align key stakeh
approved scope statement that is documented and communicated to the project team, enabling integrated change c
project summary of the business case and objectives Project Goals and Objectives: Describes what the project is s
found in the business case Project Scope: Focuses on the solutions that will be delivered according to the contract/
List of documents by phase that need to be developed by the Ariba team, in conjunction with the customer and pa
the SOW Project Success Factors and Risks:    Spells out those items that need to be present during the c
the business case that the customer is expecting Project Timeline: Estimated high-level project plan based upon t
starting point, which will include a GANTT chart Meeting Schedule: Describes which types of recurring meetings
scheduling and facilitating Roles and Responsibilities: Describes in detail each position on both the customer and A
should include a person’s name and the RACI contained in the SOW will provide this information Governance Mod
will work and communicate with one another and frequency of these interactions Management Processes: Describ
properly addressed at the appropriate level within each organization and should also provide an overview of the change co
Management Methodology: Describes the SAP Activate methodology that will be used for project management
and managing changes to configurations / customizations created or maintained by the members of the project. This proce
a common process for resolving requested changes and reported problems, and reduce the uncertainty around the existen
customization. Status Reporting and Issue Management: Describes what types of status reporting are required,
format should be used, who should be included on the distribution and where it will be stored Project Assumptions:&nb
information contained in the Charter Sign-off: Review and signature by the customer’s Project Sponsor o
scope and associated project-related assumptions and constraints. The project scope statement evolves through the initiati
project. This information and supporting documents align key stakeholders around what the project is going to deliver. If yo
project manager is not authorized to apply organizational resources to project activities. Also, the scope of the project will
Statement document, assess whether the customer has existing: Organizational policies and procedures Standard pr
instructions Guidelines and criteria for tailoring the organization’s set of standard processes to satisfy the specific
policies and security requirements Procedures for issue and defect management, including controls, identification and re
which the company modifies, approves, and validates official company standards, policies, plans, and procedures as well as
definition and impact, and probability and impact matrix Source Documents Order Form and Statement of Work Custom
from Value Realization Notes from conversations with customer project sponsors and/or project manager Pre-pla
The purpose of this task is to establish project governance. Project governance is a management framework setup for the p
establishes a policy for the project team, project stakeholders, executives, and system integrator that clearly specifies roles
a decision-making framework that is robust and logical in order to ensure the decisions are made timely and on an appropr
The purpose of this task is to define project communications and reporting.  The project manager defin
identifying who needs to see what information, when, and how, in addition to the intent of each message. Information may
subject matter experts, clients, contractors, and other internal or external personnel. Defining the communications strategy
objectives/scope, project schedules, work plans, project status reports, cost information, and so on). One of the key eleme
the regular status reports that the project manager and project teams provide to the key stakeholders. SAP Activate metho
the regular reporting.
The purpose of this task is to create and present a both internal and external customer facing pre-planning presenta
allow proper planning. The decks are meant to both align our internal teams and then to align with customer. Internal Pre-P
project and have at least a 30-day plan. Responsible Parties: Project Manager and/or Project Advisor/Delivery Executive
later than the week before the project manager and/or Project Advisor/Delivery Executive arrive on site for planning with t
Delivery Lead, Project Advisor/Delivery Executive, SSEM, CEX, Project Manager, deployment team Customer Planning Meeti
align on scope, timeline, resources and to assure to the Customer that we are ready for this project. To set up the pr
Advisor/Delivery Executive Applicability: Any full suite project or large project with multiple resources Timing: The initia
Varies based upon customer needs and availability Customer Planning Meeting Attendees: Project Manager, Project Ad
The purpose of this task is to complete an additional deeper dive than the Sales Handoff Meeting for any Procureme
agenda is very similar to that of the Handoff Call, with the same attendee list: Account Executive(s) (optional) So
Delivery Executive (DE) or Project Advisor (PA) Procurement Delivery Team Manager and/or assigned resources Str
resource Network or Supplier Enablement Manager(s) and Catalog Enablement and/or assigned resource Technic
applicable, not usually for Strategic Sourcing) The Agenda is a deeper dive into the scope: Business Case and Flight Plan
Enablement scope and buget Time/ability to meet deadlines
The purpose of this task is to guide you through project plans, schedule, and budget. The planning activities during the ear
WBS, definition of the project schedule and budget development. The project management plan development is critical for
of project management necessary for size and complexity of the project. The project management plan is a comprehensive
budget, issues, risk, project changes, etc. The management plans cover all PMI PMBOK knowledge areas as appropriate. On
the definition of requirements, the project manager and planning team define and sequence required tasks. With depende
estimated duration to create an initial draft of the project schedule. As requirements are identified, the project schedule an
The purpose of this task is to create a project schedule and budget. The detailed project schedule defin
the project, and the individual phases of the project. The work breakdown structure (WBS) serves as the foundation
minimum, the project schedule should include: Deliverables and tasks for the current phase Estimated effort (work) an
and finish dates for each task,based on dependencies Task constraints (such as must-start-on date and must-finish-on dat
Transport freeze periods related to software updates The project manager further elaborates this schedule during subsequ
planning approach. The project manager is responsible for creating a project budget that outlines all the costs associated w
and facilities. The project budget is a living document that the project manager maintains. At this stage, the project manag
plan that is developed as part of the Project Management Plans task.
The purpose of this deliverable is to develop and implement a learning strategy utilizing SAP Best Practices learning method
it is clearly defined and communicated to all.
The purpose of this task is to develop and implement a learning strategy utilizing SAP Best Practice learning methodology. T
learning and knowledge communities. The Learning Strategy will provide a common understanding of the business value o
The purpose of this deliverable is to provide consistent means of executing and governing project work in an efficient and e
communicate standards related to project execution. Where and when applicable, the current customer processes and pro
most suitable standards for the project.
Project standards provide a consistent means of executing and governing project work in an efficient and effective manner.
related to project execution. Project standards are elaborated throughout the Prepare phase (some may be fine-tuned in a
must be defined, approved,and communicated to the project team. Communication of project standards should be include
nature of project standards, changes must be managed in accordance with the integrated change control procedure.&nbsp
The purpose of this task is to setup a physical project team environment and ensure that the project team members
systems. This activity also involves the setup of project team work stations/computers and/or mobile devices (as necessary
setup of the following (the questions in each area are geared to help provide guidance): Project Experience: Is there a re
licenses required? Are the software licenses purchased? Was the software installed for the project team members?
located in different geographical sites? Is there any computer lab required for the project? Physical Project Environment
conference rooms planned for the project team? Has multimedia equipment been planned for all conference rooms (e.g.
team members in different geographical sites? Is there a working area assigned to the project members? IT Infrastructu
been tested? Do the Project Team Members have the necessary printer drivers installed? Has IT access been granted for
collaboration space like SAP Jam MS-Office Project team specific applications like modeling tool, test management
(communication, confidentiality, back-up, etc.)? Has the project policy been communicated? Physical Security: Has all
communicated (e.g. security, safety, emergency exits and etc.)? Telephone/ Voice Mail: Is there a telephone number is
the voice mail? Is there a central phone book for the project team members? Project Team Member Equipment
team members? Are office supplies available to the project member? Are the required software licenses purchased (if
The purpose of this deliverable is to kick-off the project and ensure that all needed information is shared with the project t
kickoff meeting is to ensure that everybody involved in the project understands the goals and objectives of the project, as w
a successful project execution.
The purpose of this task is to prepare the on-boarding package for external consultants and new project team memb
contains the essential information that each new team member needs to understand, which is the purpose of the pr
typically contains the following information: Project objectives, scope, and goals including SAP solutions being implemen
stakeholders Organizational chart for the project- showing both internal and external resources Overview of the existi
location, and other project guidelines as needed.
The purpose of this task is to schedule and prepare the project kick-off meeting. The kick-off meeting includes discussion o
schedule, scope, communication standards, change request process, and decision making process. The kick-off meeting is a
Some resources may attend the kick-off meeting remotely; in such cases, it is important to ensure good audio and vi
session. Use the attached accelerator as a template to prepare kickoff meeting materials specific to your project.
The purpose of the phase closure and sign-off deliverable is to: Ensure that all required deliverables from this phase and t
Identify lessons learned during the phase to prepare for formal phase closure Capture customer feedback and po
The purpose of this task is to conduct regular quality checks at defined or critical stages of the project lifecycle to assess th
SAP Ariba Project Manager and the customer Project Manager (system integrator PM will be involved in these activities as
defined in the Quality Management Plan that is defined during the Prepare phase (and agreed/signed-off by the customer)
deliverables and actions of the gate have been completed in compliance with recommended practices and to the customer
communicate the process and build quality directly into the project Provide a tool to effectively manage project
gate will be performed using the quality gate checklist. The execution of the quality gate includes the review of the project
the quality gates based on the defined completion criteria.The main purpose of managing the quality gates is to ensure qua
Manager and the SAP Ariba Project Manager are accountable for execution and completion of Quality Gate Process,
the quality gate scorecard. During the assessment meeting, the participants include the customer Project Manager, SAP Ar
applicable, and representation from others on Q-Gate invitation (Partner Project Manager, GD Project Manager, Proj
Leads communicate the status of key deliverables. The SAP Ariba Project Manager and the customer Project Manager revie
expectations and satisfaction results are gathered. Key stakeholders sign-off the Quality Gate Scorecard with potential follo
of the Q-Gate the transition to next phase is confirmed, follow-up action items may be defined. In case the Q-Gate is not pa
follow-up.
The purpose of this task is to conduct a formal closure of the project phase and sign-off the deliverables completed during
deliverables from this phase and the project are complete and accurate, and close any outstanding issues Identify
customer feedback and potential customer references When sign-off is obtained, the project can proceed to the
The purpose of this deliverable is to explore and learn about the customer’s existing technologies or systems, consid
the intended use of the systems as an integrated unit. Collectively, this is the “architecture”. SAP Ariba will an
present unique challenges and, if so, plans will be proposed in response to the identified problems or challenges. The findin
scope, Summary of technology landscape, Key deployment items, and Open Items. The architecture and analysis w
with the information that is presented. The objectives are to: Ensure customer satisfaction with the delivery of SAP Arib
solutions. The primary activities completed during the Architectural Review are: Discover technology gaps or compatibil
consequences would be of greater severity, and develop mitigation plans. Determine the best choices for integration t
build upon what has been communicated and understood during the Sales to Delivery handoff process. Clarify p
primary participants for the deliverable are listed below but may change per task: Technology Services Lead Architecture
(Included if customer has hired an implementation partner or an implementation partner has purchased an SAP) Ariba soft
The purpose of this task is to prepopulate the Architecture Review documents to include information previously communic
will populate the Architecture Review with information obtained during the Sales to Delivery handoff and pre-planning me
Readiness Questionnaire. Pre-populate Architecture Review Pre-Readiness Questionnaire.
The purpose of this task is to familiarize the customer with the Architecture Review process and to schedule the first Archit
customer to discuss the purpose and importance of scheduling the Architecture Review session. Major Process Elements:
meeting. Customer contact information can be obtained during the Sales to Delivery handoff or from the pre-planning
Architecture Review. Review the Architecture Review Pre-Readiness Questionnaire, prepopulated with known custo
session. Agree upon date for the review session. Determine who will send out the meeting invitation.
The purpose of this task is to provide the customer with the pre-populated Architecture Review Pre-Readiness Questionna
Architecture Review Pre-Readiness Questionnaire. The questionnaire has been populated based on discussion from the Sal
Elements: Technical Services Lead should provide the customer with the pre-populated Architecture Review Pre-Readin
The purpose of this task is for the customer to review the pre-populated Architecture Review Pre-Readiness Questionnaire
the customer should review the pre-populated Architecture Pre-Readiness Review Questionnaire as provided by the Techn
Customer reviews Architecture Review Pre-Readiness Questionnaire. Customer updates Architecture Review Pre-Read
provides revised Architecture Review Pre-Readiness Questionnaire to SAP Ariba. Technology Services Lead reviews custo
The purpose of this task is for the Technology Services Lead to use the customer responses to the Architecture Review Pre-
(Architecture Review Customer Session Deck). During this task, the Technology Services Lead and technical support team m
Architecture Review Customer Session Deck. Major Process Elements: Review customer feedback on the Architecture R
Architecture Review Customer Session Deck for the customer. Customizing the session PowerPoint involves utilizing the
template.
The purpose of this task is to align the team on the populated Architecture Review Customer Session Deck and to prepare f
Technology Services Lead will review the Architecture Review Customer Session Deck with the supporting architects. The in
and supporting architects should also jointly rehearse the Architecture Review session. Major Process Elements: Techno
project. During this call the Architecture Review Customer Session Deck should be reviewed to ensure all architects are in
Members should consult the Architecture Review Solution Compatibility Matrix to see if there are any compatibility concer
architects should also conduct a joint rehearsal of the Architecture Review session that will eventually be presented to the
The purpose of this task is for the Technology Services Lead to lead the customer through the Architecture Review session
deployment project that would otherwise be discovered later when the consequences would be of greater severity, and de
approach. During this task, the Technology Services Lead will run the Architecture Review session. The previously d
Major Process Elements: Schedule a call with the customer for the purposes of the Architecture Review. Technology
Services Lead will present the Architecture Review Customer Session Deck that has been customized for the customer base
during the Architecture Review discussion.
The purpose of this task is for the Technology Services Lead and Architecture Support Team Members to work through any
Services Lead and Team Members will update the Architecture Review Customer Session Deck with what was learned from
and revise Architecture Review Customer Session Deck based on customer learnings from the Architecture Review session.
can’t be closed, document the plan for how or when the items will be closed (as well as add these items to the RAID
solution outside of Architecture Review Engage the Sales or Commercial Team Bringing open items to clo
teams (P&I, solution experts, etc.)
The purpose of this task is to review the updated Architecture Review Customer Session Deck with the customer to ensure
the customer to walk them through the updated deck. Major Process Elements: Technology Services Lead provides upda
reviews updated deck with customer. Technology Services Lead to note any concerns that come up during the discussio
alignment with the content in the deck and addresses any concerns.
The purpose of this task is to obtain written signoff (via email) that the customer is comfortable with the revised Archi8tect
and the Customer are in alignment on the Architecture Review and will help to prevent unnecessary challenges to the scop
Technology Services Lead will work with the customer to confirm that outstanding concerns were addressed and to obtain
customer sign-off via email.
The purpose of this task is to inform customer of next steps following the completion of the Architecture Review process. T
Lead and architecture support team members advise the customer on what to expect next now that the Architecture Revie
schedule a call with the customer to set expectations for the post Architecture Review period.
The purpose of this task is to inform customer of next steps following the completion of the Architecture Review process. T
Lead and architecture support team members advise the customer on what to expect next now that the Architecture Revie
a call with the customer to set expectations for the post Architecture Review period.
The purpose of this task is to ensure Architecture Review materials are properly stored in the Global Project Repository. Du
materials including the completed questionnaire and PowerPoint deck to the record for this project in the global project re
completed questionnaire and PowerPoint deck to the record for this project in the global project repository.
Purpose The purpose of this deliverable is to guide the Customer through the expectations and understanding of the share
landscape and intended information flow Current versus future state Document any high level changes to intende
program specific master data strategy Identify risks relating to shared master data Review purchased service level sup
be captured and documented using the templates associated with each phase. These outcomes will be completed based o
compiled and ultimately shared with the Customer and SAP Ariba teams via a Data Strategy Scorecard. Objectives The obje
utilized across all platforms. Manage Customer expectations on shared master data usage. Ensure Customer has an u
necessary services to support deployments. Ensure that Customer expectations are properly set before program kickoff a
during the Data Strategy are: Presentation of L1 data strategy session. This strategy session is conducted w
overview of the end to end solution and the master data elements that are shared across those solutions. Pre
the Customer team members who will support the workstream deployments, with the intent being to share a deeper level
Customer has purchased. Primary Participants The primary participants for the deliverable are listed below but may
Coordinator, if assigned Technology Services Lead Functional Lead Customer Partner (Included if customer has h
Ariba software subscription for resale to a customer)
The purpose of this task is to schedule the L1 data strategy review call in order to begin the process of presenting high leve
Technology Services Lead will contact the Customer to discuss the purpose and importance of scheduling the L1 dat
following sending the welcome kit to schedule the L1 data strategy call. During the call Review the purpose a
participants to include in the L1 data strategy call. Agree upon date for the session. Send out the meeting req
The purpose of this task is for the Ariba Technology Services Lead to fully prepare to deliver the L1 data strategy review ses
task, the Technology Services Lead refamiliarizes him or herself with the L1 data strategy documentation and prepare to de
refamiliarize him or herself with the L1 data strategy documentation (Data Strategy Shared Master Data Flow Diagram
The Technology Services Lead should review the Sales to Delivery handoff documentation and the Customer’s contr
The purpose of this task is for the Technology Services Lead to deliver the L1 Data Strategy documentation to the Cu
across all platforms and provide pre-work for Customer. During this task, the Technology Services Lead should facilitate the
Master Data Overview. Major Process Elements: Technology Services Lead reviews the high level shared master data flow
success. Technology Services Lead reviews the high level shared master data elements, where they are loaded and how th
Integrated Realms within the Shared Master Data Overview document. Technology Services Lead reviews the Master Da
Customer will provide feedback throughout the L1 discussion.
The purpose of this task is for the Technology Services Lead to schedule the L2 data strategy call to set proper shared maste
delays and escalations as possible. During this task, the Technology Services Lead will contact the Customer to discuss the p
Elements: Contact the Customer following the L1 data strategy call to schedule the L2 data strategy call. During the c
Determine Customer participants to include in the L2 data strategy call. Agree upon date for the session.
The purpose of this task is to incorporate Customer feedback from the L1 data strategy session, outputs from Program Plan
Services lead will incorporate Customer feedback from the L1 data strategy session, outputs from Program Planning and Ar
conversations. Major Process Elements: The Technology Services Lead should review feedback and discussions from the L
L2 data strategy documentation. The Technology Services Lead should work with the Delivery Executive/Project Manag
understand any impacts as they relate to data strategy. The Technology Services Lead should work with the team assig
relate to the L2 data strategy discussions. The Technology Services Lead should review the Customer’s specific
possibility of missing services, the Technology Services Lead should identify an SSEM to attend and support the L2 Data Str
The purpose of this task is for the Technology Services Lead to facilitate the L2 data strategy call to set proper shared maste
many project delays and escalations as possible. During this task, the Technology Services Lead should facilitate the L2 Data
Elements: The Technology Services Lead will conduct a review of master data element issues as they pertain to the solu
cleanup activities for the Customer to consider prior to the program kickoff. The Technical Services Lead will set cor
will review risk associated with the master data elements. The Technology Services Lead will review with the Customer an
SSEM risks of not having services they have not purchased.
The purpose of this task is for the Technology Services Lead to compile all information from the L1 & L2 data strategy
the program deployments. During this task, the Technology Services Lead compiles all information from the L1 & L2 d
designated project folder and sends the Data Strategy Scorecard to the Customer team. Major Process Elements: The Tec
information: Record of meeting dates and statuses Customer audience Identified risks and poten
information from L1 and L2 data strategy discussions Overall status (red/yellow/green) The Technology
team folder. The Technology Services Lead will send the Data Strategy Scorecard to the Customer and the Delivery Executiv
The purpose of this phase is to perform a fit/gap analysis to validate the solution functionality included in the project scope
configuration values are added to the backlog for use in the next phase.
The purpose of this deliverable is to guide you through the execution and monitoring of the project. During the executing/m
measures project performance to identify variances from the plan. Executing manages the scope of the work to be done, w
quality results, controls progress against the plan, controls changes throughout the project, assesses and responds to risks,
Prepare phase for each of the PM knowledge areas guide the team's approach to management, execution, monitorin
each activity is engaged, supported by the team's monitoring/controlling plans. The project manager is responsible fo
applied at the appropriate level of control.
The purpose of this task is to direct and manage project execution. In directing and managing project execution, the projec
plan to accomplish the work defined in the project scope statement. In executing the project work, the project team
objectives Expend effort and funds to accomplish project objectives Staff, train, and manage the project team membe
the planned methods and standards Create, control, verify, and validate project deliverables Manage the scope of
issues to closure Adapt approved changes into the scope, plans, and project environment Establish and manage inte
performance In monitoring/controlling work results, the project team performs the following types of activities: Compa
determine whether corrective or preventive actions are necessary Monitor and control project risks Provide metrics
of approved changes Take corrective action as needed Management plans developed during the Prepare phase guide the
activities. See “Prepare Project Management Plan” task in the Prepare phase for details. The project m
appropriate level of control.
The purpose of this task is to ensure that the project manager keeps the key project management documents up-to-date. T
appropriate updates to the management plans, scope document and business case to reflect the detailed scope informatio
comprehensive body of project documents that include the project schedule, budget/cost information, monitoring/control
Knowledge (PMBOK), and other information as appropriate. The project management plan document developed for each o
management practices.
The purpose of this task is to manage project issues, risks, and changes. A consistent, comprehensive approach to m
Effective issue management involves the appropriate level of management making decisions on issues and tracking progres
Identified issues are maintained in one, central environment.
The purpose of this task is to communicate project status and progress. Throughout the project, a number of project perfo
the project communication plan. The project manager and project team are responsible for clearly communicating the pro
and budget both internally within SAP and externally with the customer and partner (if applicable). The project teams typic
with the team lead. It is recommended that this report is kept very lightweight and provided to the team lead via e-mail or
status reports are prepared by the team leads and are delivered to the project manager as an input for the project status re
Manager or provided in a predefined format. Project status report , using the project status report template. The project
information like issues list, risk list, etc. Executive status report is typically prepared on monthly or quarterly cadence and
information from the weekly project status report, expands on the value and benefits of the program and includes discussi
throughout the project, as more is known, the project communication matrix should be reviewed and updated. The comm
(including status reporting). It captures the analysis completed as part of communications planning and serves as a tool to
for those projects with a Project Advisor/Delivery is responsible for communicating to internal SAP management routinely.
recurring calls where all the key internal stakeholders (core and extended team members) are invited to hear a high-level o
opportunity to ask questions of the on-site team and make sure that there is alignment across the organization so that a un
Day 7 to Day 13 but can differ based upon participant constraints Meeting continues through all phases of the project t
Director (GAD) Client Partner (CP) Account Executive (AE, both SAP and Ariba) Services Sales Engage
Ariba) or Project Advisor (PA) Customer Engagement Executive or Director (CEX) Prepare a PMO Review
Schedules and conducts the meeting Completes PMO Project Review Deck Reviews deck with PA or DE (a
The purpose of this deliverable (Solution Planning) is to focus deployment configurations on customer goals and to proactiv
applicable to standard deployments that do not have consulting services.
The purpose of this deliverable is to capture the process variations that need to be configured into the system (Design Mat
The purpose of this task is to document the configuration values determined during the Fit-to-Standard workshops.
are explored. The customer is responsible for providing the values that are appropriate to their business processes. The val
process is as follows: Hold Solution Planning Session with Client Client Walks through their Process During Solution Pla
Session Client Finishes Documenting Process in Design Matrix
The purpose of this deliverable is to ensure proper set up of a Roles and Authorizations procedure and approach for the pr
number of User and Team Member licenses a Client has on their Order Form. User Licenses will be monitored by the Client
overages.
The purpose of this task is to review the available authorization roles and related settings and map them to the business us
The purpose of this deliverable is assurance that the systems being integrated to are compatible with the cloud system, set
fields (if required).
The purpose of this deliverable is assurance that the systems being integrated to are compatible with the cloud system, set
prerequisites for extension fields (if required).
The purpose of this task is to review system prerequisites for the systems, security and infrastructure and assure that system
The purpose of this task is to set-up network connectivity and security for the quality system.
The purpose of this task is to confirm the fields to be integrated. The customer provides data mappings and value lists alon
The purpose of this deliverable is to formally close the phase and conduct deliverable sign-off. During this time, the
project are complete and accurate, and close any outstanding issue Conduct formal Project Quality Gate and ide
Customer References
each quality gate will be performed using the quality gate checklist. The execution of the quality gate includes the review o
sign-off of the quality gates based on the defined completion criteria. The main purpose of managing the quality gates is to
customer Project Manager and the SAP Ariba Project Manager are accountable for execution and completion of Quality Ga
attendees and plan the quality gate scorecard. During the assessment meeting, the participants include the customer Proje
Advisor, as applicable, and representation from others on Q-Gate invitation (Partner Project Manager, GD Project Manager,
Team Leads communicate the status of key deliverables. The SAP Ariba Project Manager and the customer Project Man
Customer expectations and satisfaction results are gathered. Key stakeholders sign-off on the Quality Gate Scorecard w
Upon completion of the Q-Gate, the transition to next phase is confirmed; follow-up action items may be defined.
items must be defined for follow-up.
The purpose of this task is to conduct formal closure of the project phase and sign-off the deliverables completed during th
deliverables from this phase and the project are complete and accurate, and close any outstanding issues Identify
customer feedback and potential customer references    When sign-off is obtained, the project can proceed to
The purpose of this phase is to use a series of iterations to incrementally build and test an integrated business and system e
the previous phase. During this phase, data is loaded, adoption activities occur, and operations are planned. Realize Activiti
development environment using incremental build in time-boxed iterations Conduct overall end-to-end testing
Prepare for data migration and data archiving Conduct performance testing Conduct project team
Track and report on value delivery During Realize phase, the project team uses a series of iterations to incrementally config
conversion programs. The project team actively works with business representatives to ensure good fit of the built solution
to the business users to accelerate time to value and provide early access to finalized functionality. Each release is thorough
documents the configuration decisions and solution in the appropriate configuration template (e.g. agile backlog documen
including interfaces, integration points, data conversion programs, reports, and any required enhancements in the appropr
design matrix). Once these activities are complete for a particular release and the team has obtained business approval, th
environment.
The purpose of this deliverable is to guide you through the execution and monitoring of the project. During the exec
work and measures project performance to identify variances from the plan. Executing manages the scope of the work to b
quality results, controls progress against the plan, controls changes throughout the project, assesses and responds to risks,
developed during the Prepare phase for each of the PM knowledge areas guides the team's approach to managemen
to be considered when each activity is engaged and supported by the team's monitoring/controlling plans. The projec
the planning phase are applied at the appropriate level of control.
plan to accomplish the work defined in the project scope statement. In executing the project work, the project team will pe
Expend effort and funds to accomplish project objectives Staff, train, and manage the project team members assign
planned methods and standards Create, control, verify, and validate project deliverables Manage the scope of the
to closure Adapt approved changes into the scope, plans, and project environment Establish and manage internal
determine whether corrective or preventive actions are necessary Monitor and control project risks Provide metrics to s
approved changes Take corrective action as needed Management plans developed during the Prepare phase guide the
The purpose of this task is to ensure that the project manager keeps the key project management documents up-to-date. T
appropriate updates to the management plans, scope document and business case to reflect the detailed scope informatio
comprehensive body of project documents that include the project schedule, budget/cost information, monitoring/control
Knowledge (PMBOK), and other information as appropriate. The project management plan document developed for each o
management practices.
The purpose of this task is plan and execute agile sprints. The project team runs the Realize phase in sequence of sprints, in
incrementally and iteratively build the solution capabilities captured in the backlog, test them, and review their completion
sprint, the project team conducts following activities: Sprint Planning Meeting: At the beginning of the sprint, the project te
the highest priority items from the backlog and conducts detailed planning for the execution activities in the sprint. Each b
These tasks may be configuration, coding, unit testing, data preparation, documentation and others. These tasks are then c
backlog item. As a result of this planning, the team has clarity on what needs to be completed for each backlog item includ
work. Sprint Execution Activities: During the sprint the team members execute the tasks that have been planned and the te
showing the status of each backlog item and each task. Teams are encouraged to use boards on the wall and use the post-i
down chart that is used to track the progress of completing the individual tasks and backlog items. The team reviews the p
daily stand-up meeting the team members review the (a) progress they have made since last meeting; (b) plans for activitie
from completing the tasks they are working on. The daily stand-up meeting is not a project status meeting, but rather a ses
Towards the end of the sprint, the team conducts the sprint demo meeting during which the team demonstrates to the bus
team seeks acceptance of the completed features. During this meeting the business owner may request additional items to
that the team previews the functionality with process owners prior to this meeting. Many projects had great experience wi
business users and decisions makers (instead of the project team members). Sprint Retrospective: SCRUM Master organize
shortly after the sprint demo meeting. Purpose of the meeting is to continuously improve the Scrum process using lessons
What went well during the sprint? What do we want to preserve? What can be improved for the next sprint and ho
the next sprint. This way, the agile process gets improved in an incremental way and remains responsive to the changing en
The purpose of this task is to manage project issues, risks, and changes. A consistent, comprehensive approach to managin
and budget. The project teams typically prepare: Team member status update produced typically weekly and shared with
the team lead via e-mail or in a team meeting Team status reports on regular cadence, typically weekly. The team status
input for the project status report. The team status report may be reviewed in regular team review with Project Manager o
template. The project status report is created weekly, based on the input from individual teams and additional information
quarterly cadence and is provided to the project executive steering group. Generally, this report re-uses the key informatio
and includes discussion of the decisions that are needed from the executive steering group. Additionally, throughout t
updated. The communication matrix documents the project team’s approach to communication (including status re
as a tool to guide the project team throughout the project.
The purpose of this deliverable is to configure the Quality system using the consolidated Configuration Backlog created from
sprints (1 – 2 week duration), configured, tested, and demonstrated; adjustments are made as necessary. At the end
made for global configuration, configuration dependencies, and configuration that can be executed in parallel. Note
Configure Your Solution in the " SAP S/4HANA Cloud Tutorials " accelerator. The path is SAP S/4HANA Cloud Tu
with Manage Your Solution > Using Configure Your Solution.
The Enablement Workbook is used to collect Client master data that will be used to build the foundation of the site. This da
organizations/users, commodity codes, departments, site parameters, etc. A standard Enablement Workbook template (loc
deployed. If the Client is already Live on another SAP Ariba solution, current master data can be used to populate the Enab
workbook based upon the solutions being deployed. If the Client is Live on another SAP Ariba solution, Configuration Lead
information into the Enablement Workbook. The SAP Ariba will provide a quick introduction to the solution. The Configurati
each piece of data being requested, and demonstrating how master data will be used within the site where applicable. Onc
data. The Configuration Lead will respond to Client questions as necessary. Steps: Optional: SAP Ariba Extracts Data from
Enablement Workbook with Client SAP Ariba and Client Work Through Questions and Feedback on Workbook Client C
and Errors Optional: if Gaps or Errors: SAP Ariba Prepares Error Report and Sends to Client Optional: if Gaps or Errors
Each SAP Ariba solution comes with a standard set of header fields, which are used to collect metadata for searching and re
deployments (see Deployment Description); also, Client’s may purchase additional header fields in bundles of five. T
a high-level demonstration of project creation as well as reporting and searching functionality. While reporting will be revie
visualize how their data will be collected and made available in Analysis. As part of the same meeting, the Configuration Le
with the Client. This review will include a review of included standard header fields and permissible modifications, available
After the client has completed the custom header field data collection template, the Configuration Lead will review the tem
Error Report. The Configuration Lead will review the issues with the Client for resolution. After the client has corrected any
fields as outlined in the Custom Header Field Data Collection Template. The SAP Ariba will then review the as-built fields w
Lead will incorporate Client feedback as necessary. All modifications to fields will be documented in the Custom Header Fie
Contract Project Creation Functions Client Completes the Data Collection File SAP Ariba Reviews File and Documents
Sends to Client Optional: if Gaps or Errors: SAP Ariba Works with Client to Correct Errors SAP Ariba Builds Fields in
Requested Changes to Header Fields
The purpose of this task allows clients to use SAP Ariba’s repository functionality to bulk load legacy contract
centralized storage and access for their documents, efficient searching and reporting functionality, and the ability to manag
will typically load up to 250 contract workspaces with two documents each during deployment; however, additional reposi
completion of master data load and custom header field configuration. After these key activities are completed, the Config
Reviewing this document early will allow the Client to begin gathering their data and documents in parallel to other Contra
template and provided documents for the sample load, Configuration Lead will review the completed repository template f
Configuration Lead will review the issues with the Client for resolution. After any errors have been resolved, Configuration L
sample load with the Client, and determine if any adjustments must be made for the full load. After the Client completes th
completed repository template for errors. These errors will be documented in the Configuration Error Report, and the Confi
been resolved, Configuration Lead will load the full load to the Client’s Production Site as part of the migration to Pr
as part of their Production Site testing. Steps: Intro to Contract Repository File Master Data Loaded and C
Template with Client Client Can Begin to Gather Documentation for Standard Fields and Scan to PDF Files &n
(15-20 Contracts) and Related Documents SAP Ariba Reviews Sample Load Files/Related Documents and Documen
Report and Sends to Client Optional: if Gaps or Errors: SAP Ariba and Client Review and Address Gaps in a Meeting
Load in Test with Client Contract Repository File Client Completes and Provides Dat
Files/Related Documents and Documents Gaps and Errors Optional: if Gaps or Errors: SAP Ariba Prepares Error Repo
Address Gaps SAP Ariba Loads Repository Files in Production
The purpose of this task is to manage the processes of configuration for the SAP Ariba solution and identify any and all mod
two distinct types of process templates – Contract Requests and Contract Workspaces. Configuration of the Contrac
template is included with a standard deployment in accordance with the Deployment Description document; however, add
in the design matrix, Configuration Lead will build out the Contract Workspace process template, including any team memb
the Client to identify any required modifications. The process template will also be updated after the completion of main a
be documented in the design matrix and provided to Configuration Lead, who will implement the changes. Steps: SAP Ari
Contract Process in Test Site SAP Ariba Delivers in-depth Demo of Contract Process in Test Site to Client SAP Ariba M
Client via Demo (highlight the updates)
The purpose of this task is for contract authoring in SAP Ariba to be implemented through the use of assembl
are specially configured so that SAP Ariba recognizes the sections and clauses that make up the contract, and this special se
Clients will be able to modify their base contract language by substituting and adding clauses directly in the user interface.
configuration of one main agreement template is within the scope of a standard deployment in accordance with the Deplo
purchased. While the Main Agreement is configured within the contracting process template (see Contract Process Configu
soon as the kick off meeting. The Client should have their contract identified, but they may need a longer lead time to obta
their contract document to be configured as the Main Agreement, the Configuration Lead will review the structure and form
configuration. After any required modifications to structure and formatting have been completed by the Client, Configurati
SAP Ariba will provide a demonstration of the as-built Main Agreement to the Client in order to determine any necessary m
Lead. Updates to the contracting process template may also be required as a result of Main Agreement configuration. Thes
Configuration Lead (see Contract Process Configuration). Special Note – If a Client is implementing DocuSign integra
Main Agreement SAP Ariba Reviews the Main Agreement with the Client Including Format and Structure SAP Ariba P
Main Agreement with Client via in-depth Demo Optional: if Client Requested Changes: SAP Ariba Makes Adjustments Be
The purpose of the Clause Library task is to support an integral part of contract authoring. It is u
to the Main Agreement. While Clients are identifying their Main Agreement, they should also be considering their addition
department. Twenty (20) preferred clauses and an additional 20 alternate/fallback clauses are included within the scope of
however, additional clauses can be purchased. The SAP Ariba will demonstrate Clause Library functionality in conjunction w
also review the Clause Library template and provide further instruction on how the Client should complete the template an
Configuration Lead will review the template for any errors or missing information, which will be recorded in the Configurati
resolution. Once the Client has resolved any issues, Configuration Lead will complete Clause Library configurations, which i
Agreement, and setting up additional preferred/alternate/fallback clauses. It may also include the set up of clause level app
determine any necessary modifications. These modifications will be documented within the Clause Library Template by the
Clause Library with the Client, Provides Demo, and Reviews Data Collection File Client Completes Data Collection File
Optional: if Gaps or Errors: SAP Ariba Prepares Error Report and Sends to Client Optional: if Gaps or Errors: SAP Ariba W
Ariba Reviews Clause Library with Client via in-depth Demo
The purpose of this task is to allow SAP Ariba Contracts the ability to integrate with EchoSign or DocuSign to allow fo
service that the Client can configure; additional services for electronic signature may be purchased and would be indicated
a separate agreement with EchoSign or DocuSign prior to enabling the features in SAP Ariba. If the Client has only purchase
implement electronic signature, the Configuration Lead will provide the Client with the SAP Ariba Contract Management Ad
Configuration Lead may also add a signature task to the Client’s process template as part of the process template de
integration, the Configuration Lead will also configure the parameters that are not customer facing. If the Client has purcha
functionality with the Client and determine the best functional fit for signature task work flow as part of the process design
necessary parameters for electronic signature based upon the type of electronic signature being implemented (DocuSign o
provide a demonstration of the signature task workflow to the customer, and advise the customer on requirements for sign
The purpose of the deliverable is to define and enhance the required forms.
D-Forms are highly customizable, data entry tools that are internal to SAP Ariba (cannot be directly exported or printed). Th
included with each solution deployment in accordance with the Deployment Description document; however, additional fo
deployment, they will no longer be able to have that form configured by Customer Support post-deployment. The SAP Arib
can be found in Form Templates area of the Upstream Production Realm (Manage > Templates > Form Templates) in
strategic discussion to determine if the Client has an applicable use case for including a dform in their process. If the Client
number of pre-fabricated form templates that are housed within the “Strategic Sourcing” production realm i
the Client’s test site for further customization if desired. If the Client does not want to use one of the sample forms,
saved within the Client’s folder. If the Client decides to configure a form in the future, the Client should work with th
a use case for the form in their process, the Configuration Lead will review the Form Data Collection Template (available in
layout options. After the Client has completed the template, the Configuration Lead will review the template for any errors
Configuration Lead will review the issues with the Client for resolution. After the Client has corrected any errors, the Config
then review the as-built form template with Client to identify any modifications to field configuration or layout. The Configu
documented in the Form Data Collection Template. Steps: SAP Ariba Provides Demo of Example D-Form Templates and R
SAP Ariba Reviews File and Documents Gaps in Data and Errors Optional: if Gaps or Errors: SAP Ariba Prepares Error Repo
Errors SAP Ariba Builds D-Forms in Test Site SAP Ariba Reviews Field with the Client via Demo SAP Ariba Makes Any
The purpose of this deliverable is to educate the customer project team on the standard reports available in the SAP system
Each SAP Ariba solution may include a number of prepackaged reports that can be used by clients with the applicable repo
information into a report or reporting on items not covered by a prepackaged report. One custom report is included with s
additional custom reports may be purchased. The SAP Ariba will provide an in depth demonstration of SAP Ariba Analysis, i
creating custom analytical reports. During this demonstration, the SAP Ariba will work collaboratively with the Client team
SAP Ariba functionality to adequately convey their reporting requirements; the SAP Ariba should provide recommendation
support Client objectives with the solution (average duration/cycle time reduction, clause library usage, etc.). For additiona
Creation work instruction (available in Knowledge).
The purpose of this deliverable is to freeze the configuration prior to the start of testing.
The purpose of this task is once the site configuration phase is complete and the Client is ready to begin testing, a configura
configuration changes that will violate the integrity of testing as well as delay the overall project schedule. Once the Client
confirmation of the configuration freeze from the client prior to the start of testing. This confirmation can be in the form of
configuration freeze with the Client to ensure that all parties are prepared for testing. A copy of the written confirmation of
folder in SAP Ariba Project Documents (SAP Docs). Steps: Deployment Lead Requests Confirmation of Configuration Free
The purpose of this deliverable is to provide the Site Admin Users with an Admin Demo.
The purpose of this task is the deployment of the first stage of development for a client’s SAP Ariba solution.
maintain and modify key elements within their site. A number of administrative demonstrations will be provided by SAP Ar
These demonstrations may vary by solution. The Configuration Lead will provide the following administrative demonstratio
accounts and permissions Modifying enumerations (pick list values) General template administration The following a
Discovery (*Deployment Lead to facilitate – contact SAP Ariba Discovery Buyer Adoption Team to actually provide d
Events Sourcing Event Template Administration The following additional demonstrations will be provided for Contract M
Managing the clause library Loading legacy contracts The following additional demonstrations will be provided for
maintaining the Supplier Profile Questionnaire Additional demonstrations may be given throughout deployment to demon
The purpose of this deliverable is to demonstrate the configured solution to the customer project team for solution accept
The purpose of this task is to demonstrate the configured solution to the customer project stakeholders and gain first appro
beginning of a more comprehensive testing stream. Procedure: Schedule the walk through meeting. Decide on the sc
processes at a minimum. Select data for use in the scenarios. It is best to connect the scenarios into a complete story wi
not completed, a conceptual walk-through can be created to explain how the process will work. Demonstrate the scenario
demonstrates how the solution will fulfill the business requirements. Some slides maybe necessary to help explain difficult
Obtain acceptance to proceed into testing.
Once the configuration freeze has been confirmed by the Client, internal testing of the Test Site can commence. The purpo
working properly prior to client testing. The Configuration Lead will complete all internal testing prior to client testing. Thes
master data, and verifying and testing client configurations such as custom header fields, process flows (including condition
configurations should be reviewed against the current data collection templates, and any discrepancies should be reviewed
Complete Internal Testing on Test Site Configurations (SAP Ariba) Customize Client Test Script and Send to Client (SAP A
The purpose of this deliverable is to complete the Internal Testing on the test Site and customize the Client Test Script.
The purpose of this deliverable is to execute the necessary preparation steps to be able to execute customer testing on the
provide a high level test script for each applicable solution to guide client testing. The client can propose additional test cas
not core SAP Ariba functionality. The Configuration Lead will customize the solution specific test script (where applicable) t
the Client did not complete as part of deployment. Once the Configuration Lead has completed their customization of the t
Test Site.
The purpose of this task is to define the test cases, test scripts, and supporting test data to be used for customer solution te
adjustments.
The purpose of this deliverable is to setup the integration in the quality system. Some integrations have prerequisites that n
Cloud Integration Automation Service, requirements documented in the Setup guide are included in the service.
The purpose of this task is to create integration mappings and define transformations.
The purpose of this task is to set up integration on the cloud system.
The purpose of this task is to execute the initial integrated data load into the cloud system.
The purpose of this deliverable is to develop the learning material for SAP customers to learn about the products and busin
provisioning trainers to be equipped to lead training sessions for the end-user.
The purpose of this task is to create learning content to encourage effective user adoption. The learning content bein
experience design should consider the type of material that is required. They will also reflect the business&#3
experience i.e. how and when employees will consume learning content. Learning experience design and development wo
The purpose of this task is to enable your trainers with the knowledge and expertise to deliver effective instructor-led learn
they are teaching. This is done through a combination of knowledge transfer and soft skills training, plus digital learning fac
The purpose of this deliverable is to develop, implement, and test the data processes. This activity consists of iterative testi
legacy data required to support the various test cycles and ultimately the production cutover. The test cycles enable the da
cutover sequencing plan, and exercise data reconciliation and validation processes required to support the production cuto
The purpose of this task is to execute and validate the manual data load and overall load process for testing.
The purpose of this task to support with issue identification by the customer during the data load process.
The purpose of this task is to provide one final assessment at the end of the Realize phase to report on the quality of the co
The purpose of this deliverable is to perform the customer solution and business process testing according to the defined p
steps will be different for each solution, but generally include reviewing and verifying master data, and verifying and testing
tasks and approval flows), and solution specific customizations. The test site configurations should be reviewed against the
Configuration Lead and Deployment Lead Manager for resolution. Steps: Complete Test Site Testing and Document Issues
Test Site Testing and Document Issues Confirm via Email that Test Site Configurations have been Validated
The purpose of this task is to test the solution and business processes according to the previously defined plan. During the
The purpose of this task is to resolve any incidents identified during testing. It is crucial that the issues are re-tested by user
The purpose of this deliverable is to establish an effective operation processes for security.
The purpose of this task is to set-up, document and execute the administrative procedure for roles and authorizations.
The purpose of this deliverable is to document the strategy, scope, and timelines for moving from the "as-is" so
go-live.
The purpose of this task is to document the strategy, scope and timelines for moving from the as-is solution to the to-be so
activities such as the transfer of data from the legacy systems to the SAP Ariba production system, setting up and initializing
new system, setting up and verifying interface connections, importing transports and all manual configurations.
The purpose of this deliverable is to setup the Integration in Production system. This can optionally be included in the cuto
The purpose of this task is to apply all integration prerequisites to all integrated systems.
The purpose of this task is to set up network security and connectivity to all integrated systems.
The purpose of this task is to configure integration between the cloud system and related systems.
The purpose of this deliverable is to formally close the phase and conduct deliverable sign-off. During this time, the p
are complete and accurate, and close any outstanding issue Conduct formal Project Quality Gate and Identify lessons l
References
each quality gate will be performed using the quality gate checklist. The execution of the quality gate includes the review o
sign-off of the quality gates based on the defined completion criteria. The main purpose of managing the quality gates is to
customer Project Manager and the SAP Ariba Project Manager are accountable for execution and completion of Quality Ga
attendees and plan the quality gate scorecard. During the assessment meeting, the participants include the customer Proje
Advisor, as applicable, and representation from others on Q-Gate invitation (Partner Project Manager, GD Project Manager,
Team Leads communicate the status of key deliverables. The SAP Ariba Project Manager and the customer Project Man
Customer expectations and satisfaction results are gathered. Key stakeholders sign-off on the Quality Gate Scorecard w
Upon completion of the Q-Gate, the transition to next phase is confirmed; follow-up action items may be defined.
items must be defined for follow-up.
The purpose of this task is to conduct formal closure of the project phase and sign-off the deliverables completed during th
this phase and the project are complete and accurate, and close any outstanding issues Identify lessons learned during
potential customer references When sign-off is obtained, the project can proceed to the next phase. Use the attached sig
The purpose of this phase is to setup the production system, confirm customer organization readiness, and to switch busin
Finalize the solution and its supporting tools and processes for production go-live Resolve all crucial open is
Proceed with cut-over activities, including data migration Execute transition and cutover plans inc
end user training Identify and document all issues encountered in the transition to the new solution Mo
or an "extra-care" center of excellence for support that provides: Production support proce
support System enhancements Track and report on value delivery
The purpose of this task is the execution/monitoring of the project. During the executing/monitoring of the project, the tea
to identify variances from the plan. Executing manages the scope of the work to be done, while monitoring monitors the e
against the plan, controls changes throughout the project, assesses and responds to risks, and communicates project statu
for each of the PM knowledge areas guide the team's approach to management, execution, monitoring, and control o
engaged, supported by the team's monitoring/controlling plans. The project manager is responsible for ensuring that
The purpose of updating the project management documents task is to ensure that the project manager keeps the key pro
schedule, refinement of the project budget, and appropriate updates to the management plans, scope document and busi
management documents is a comprehensive body of project documents that include the project schedule, budget/cost inf
Management Body of Knowledge (PMBOK), and other information as appropriate. The project management plan documen
application of project management practices.
The purpose of this task is to manage project issues, risks, and changes. A consistent, comprehensive approach to managin
and budget. The project teams typically prepare: Team member status update produced typically weekly and shared with
the team lead via e-mail or in a team meeting Team status reports on regular cadence, typically weekly. The team status
input for the project status report. The team status report may be reviewed in regular team review with Project Manager o
template. The project status report is created weekly, based on the input from individual teams and additional information
quarterly cadence and is provided to the project executive steering group. Generally, this report re-uses the key informatio
and includes discussion of the decisions that are needed from the executive steering group. Additionally, throughout t
updated. The communication matrix documents the project team’s approach to communication (including status re
as a tool to guide the project team throughout the project.
plan to accomplish the work defined in the project scope statement. In executing the project work, the project team
objectives Expend effort and funds to accomplish project objectives Staff, train, and manage the project team membe
the planned methods and standards Create, control, verify, and validate project deliverables Manage the scope of
issues to closure Adapt approved changes into the scope, plans, and project environment Establish and manage inte
determine whether corrective or preventive actions are necessary Monitor and control project risks Provide metrics
of approved changes Take corrective action as needed Management plans developed during the Prepare phase guide the
recommended practices Assuring project planning Validating open risks and issues, and measuring customer satisfa
quality gate checklist with defined expectations to the maturity of particular project deliverables/aspects. Note: new
Manager to the different project types.
The purpose of this task is to complete the final checks to ensure effective learning deployment. As part of the traditional a
courses. This is a ‘dry run’ giving a final opportunity for final testing of the learning materials in the delivery m
trainers are knowledgeable and can deliver in an engaging manner in the ‘live’ courses. Piloting of the trainin
hugely beneficial.
The purpose of this task is to execute the learning plan to optimize user adoption. It is recommended to use a blended app
Micro Learning Social and collaborative learning eLearning Classroom or virtual instructor led delivery On
The purpose of this task is to assess user engagement levels and knowledge retention of the learning content. Evaluation is
and lessons learned along the way help to evolve the learning experience. Useful techniques to receive feedback include:
evaluation sheets, plus key business sponsors and SMEs attending a course and providing feedback Evaluate and track co
The purpose of this task is to migrate the master data and configurations for all applicable solutions from Test to Production
Production Site Customize Test Script for Prod Site Testing and Send to Client Complete Production Site Testing and D
Accurate: Complete Production Site Testing Again and Document Results Provide Final Validation of Production Site
The purpose of this task is at the conclusion of Test Site testing, the Client will return their completed test script indicating
configurations from the Test Site to the Production Site. Once this approval is obtained, the migration of master data and co
Lead will obtain written confirmation of the successful completion of Test Site testing and approval to move configurations
Deployment Lead in the applicable client folder in SAP Ariba Project Documents (SAP Docs). After this approval has been re
as described in the Moving Strategic Sourcing Data and Configurations to Production Work Instruction (available in Knowled
Configuration Lead, and presented to the Deployment Lead for review at the completion of the migration. Special Note: Fo
migration to Production would also include the full repository load. Refer to Contract Repository Files Configuration for add
After migration of data and configurations from the Test Site to the Production Site has been completed, SAP Ariba internal
configurations were migrated successfully. After the SAP Ariba review has been completed, the Client will complete their se
Solution is Live.
The purpose of this deliverable is to transfer from a project support environment to a production support environment. Inf
support the client post-deployment: Customer Management (Customer Engagement Executive), Customer Support, and th
included on transition communication to determine if any further expansion was discussed, but their participation on calls
The purpose of this task is for support services to introduce themselves and take ownership of the support and monitoring
customer knows who will be supporting the system from SAP and the proper methods of engaging with them when concer
meeting prior to go-live.
The purpose of this deliverable is to confirm that the resources and processes are in place to support the ongoing solution
The purpose of this task is to implement ongoing production support to the SAP Ariba users and to monitor and opti
The purpose of this deliverable is to formally close the project and conduct deliverable sign-off. During this time, the projec
accurate, and close any outstanding issues Conduct formal Project Quality Gate Identify lessons learned during the
completed with recommended practices, assuring project planning, validating open risks and issues, and measuring custom
using the quality gate checklist with defined expectations to the maturity of particular project deliverables/aspects.
Project Manager to the different project types.
The purpose of this task is to formally close the project by obtaining customer signatures on dedicated deliverables/docum
The purpose of this task is to capture the customer’s feedback about their experiences with and expectations for SA
constantly innovative to capture the changing requirements of the customers with time, and consequently, provide the cus
https://app.smartsheet.com/b/form?EQBCT=4069c947664f45db9cf4c704a84a6543
The purpose of this phase is to further optimize and automate the operability of the solution. Operability is the abili
availability and required performance levels to support the execution of the enterprise’s business operations.
Access Level Workstream Predecessors Assigned
Public
Public Technical Architecture & Infrastructure Start

Public Application: Customer Team EnablementStart

Public Application: Customer Team EnablementStart
Public Application: Customer Team Enablement1.2.1 , ` Start

Public Project Management Start


Public Application: Solution Adoption Start

Technical Architecture & Infrastructure Start
Public Technical Architecture & Infrastructure 1.9.2
SAP EmployeeTechnical Architecture & Infrastructure 1.9.4 , ` 1.9.3

SAP Partner Technical Architecture & Infrastructure 1.9.5 , ` 1.9.4 , ` 1.9.3
Public Technical Architecture & Infrastructure 1.9.6 , ` 1.9.5 , ` 1.9.4 , ` 1.9.3

Public

Public Application: Design & Configuration Start


Public Application: Integration Start


Public







Public Application: Testing Start


Public System & Data Migration Start

SAP Partner System & Data Migration Start
SAP Partner System & Data Migration Start

Public Transition to Operations Start

Public


System & Data Migration Start

System & Data Migration Start
Public
Tags Accelerators Assigned Role Id
Ariba: Contract Management

Ariba: Contract Management ARI.024,ARI.025 6
Project Management
Project Management ARI.023 6
Project Management S4H_161,S4H_163,S4H_162 6

Project Management
Project Management ARI.013,ARI.014,ARI.015,ARI.016 1

Project Management PM.194,ARI.003,ARI.004,ARI.008,A1
Project Management ARI.008,ARI.017,AG.03 1
Project Management PM.98,PM.99,ARI.005 1
Project Management 5
Project Management
Project Management AG.17 1
Project Management
Project Management
Project Management
Project Management ARI.008,ARI.001 1

Project Management PM.94
Project Management ARI.002,ARI.012,PM_209 3
Project Management PM.94 2
Supply Chain,Supplier Management,

ARI.070

ARI.065 16

ARI.068 16
Supply Chain,Supplier Management,Strategic Sourcing,Procurement,P16

ARI.066,ARI.067,ARI.071 16
ARI.069 16
Deployment Description,Supply Chain,Supplier Management,Strategic15
Supply Chain,Supplier Management,Strategic Sourcing,Procurement,PM

5

ARI.061,ARI.062,ARI.060 16
ARI.061,ARI.062 16

ARI.061,ARI.062 16
PM Staffed,DE Staffed,Deployment Description 16
PM Staffed,DE Staffed,DeploymentARI.063 16
Project Management
Project Management ARI.010,ARI.007,ARI.019 1
Ariba: Contract Management ARI.043

Ariba: Contract Management ARI.026 6
Ariba: Contract Management 8


Project Management PM.94

Project Management

Project Management AG.17,ARI.022,AG.16 1
Ariba: Contract Management ARI.027,ARI.044,ARI.045,ARI.046,A6

Ariba: Contract Management ARI.028,ARI.029,ARI.048 6
Ariba: Contract Management ARI.028,ARI.049,ARI.030,ARI.031,A6

Ariba: Contract Management ARI.028,ARI.036,ARI.054 9

Ariba: Contract Management ARI.028,ARI.037,ARI.055,ARI.056 6








Project Management
Project Management

Ariba: Contract Management ARI.059,ARI.042
13
Project Management
Project Management GL.27,PM.94 1

Role Type
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
Accountable
WBS Role ID Description Service Provider or Customer Job Profile IPP Object ID
1 Service Provider Project Manager 30000006
2 Service Provider Project Management Specialist 30000278
3 Service Provider Business Process Architect 30000540
7 Service Provider Education Senior Consultant 30001880
8 Service Provider Senior Technology Consultant 30000262
9 Service Provider Senior Technology Architect 30000243
10 Service Provider Business Process Consultant 30000257
11 Service Provider Senior Technology Architect 30000243
12 Service Provider Senior Business Process Consultant30000258
13 Service Provider Customer Business Lead
14 Service Provider Technology Architect 30000541
15 Customer Project Coordinator
16 Customer Technology Services Lead
17 Customer Project Lead
Career Level Deployment mode Solution Group Consulting Solution Profile IPP Sol. Pro. ID
Senior Nearshore
Specialist Local
Specialist Local
Senior Local
Senior Local
Senior Nearshore
Senior Local
Senior Nearshore
Senior Offshore
Specialist Offshore
Senior Nearshore
Senior Nearshore
Local
Specialist Local
Associate
Consulting Industry Focus IPP Ind. F. ID Service Element Price Rate
SDC: Project Management Support (S3) S3
General: Project Management (G2) G2
General: Design Services (G2) G2
SDC: Project Management Support (S3) S3
SDC: Execution Services (S3) S3
SDC: Execution Support Services (S4) S4
SDC: Execution Support Services (S4) S4
General: Strategy, Architecture and Expert Services (G1)G1
TOTAL
Effort(Onsite) Effort(Remote) Effort(SAP) Effort(Customer) Last Changed At
0.000 0.000 0.000 0.000 16.08.2017 15.50.03
0.000 0.000 0.000 0.000 16.08.2017 15.50.03
0.000 0.000 0.000 0.000 16.08.2017 15.50.03
0.000 0.000 0.000 0.000 16.08.2017 15.50.03
0.000 0.000 0.000 0.000 25.09.2017 17.40.04
0.000 0.000 0.000 0.000 20.12.2017 20.46.04
0.000 0.000 0.000 0.000 27.12.2017 15.25.35
0.000 0.000 0.000 0.000 27.12.2017 23.31.42
0.000 0.000 0.000 0.000 28.12.2017 17.20.32
0.000 0.000 0.000 0.000 28.12.2017 21.39.38
0.000 0.000 0.000 0.000 29.12.2017 00.25.52
0.000 0.000 0.000 0.000 29.12.2017 00.25.52
0.000 0.000 0.000 0.000 17.01.2018 20.47.34
0.00 0.00 0.00 0.00 26.06.2018 17.19.56
0.000 0.000 0.000 0.000 27.06.2018 16.57.04
0.000 0.000 0.000 0.000 27.06.2018 16.57.04
0.000 0.000 0.000 0.000 28.06.2018 02.14.38
0.000 0.000 0.000 0.000
WBS Accelerator ID Title
AG.03 Agile Project Team Roles and
Responsibilities
AG.16 Backlog including Delta Requirements
and Gaps.xlsx
AG.17 Agile Release Planning

ARI.001 Project Kick-off Template
ARI.002 Project Setup Checklist Sample
ARI.003 Project Charter Template
ARI.004 Scope Statement Template
ARI.005 Communication Plan Overview Template
ARI.006 Internal Pre-Planning Presentation
ARI.007 Meeting Notes Accelerator
ARI.008 Governance Accelerator
ARI.009 CAT Time and Expense Tracking
ARI.010 Project Status Report
ARI.011 Open Issues List Template
ARI.012 Quality Built In New Q-Gate Checklist
ARI.013 Ariba Sales to ACO Handoff Document
ARI.014 Business Case Flight Plan Handoff
ARI.015 Ariba Sales Handoff Provisioning Staffing

Updates
ARI.016 Ariba Site Enablement Document Master
ARI.017 Project Roles & Responsibilities
ARI.018 VOC Process Flow Chart

ARI.019 PMO Project Review
ARI.020 Change Request Log
ARI.021 Change Request Form.docx
ARI.022 Agile Change Control Process
ARI.023 Strategic Sourcing - SAP Ariba Education

Services.pptx
ARI.024 Strategic Sourcing - Best Practice
Contracts Process - Procurement.zip
ARI.025 Strategic Sourcing - Best Practice
Contracts Process - Sales.zip
ARI.026 Strategic Sourcing - Contracting Process
Design Matrix - All Types.xls
ARI.027 Strategic Sourcing - Enablement

Workbook.xls
ARI.028 Strategic Sourcing - Configuration Error

Report.xls
ARI.029 Strategic Sourcing - Custom Header Field

Data Collection Template.xlsx
ARI.030 Strategic Sourcing - (Procurement)

Contract Repository Template.xls
ARI.031 Strategic Sourcing - (Sales) Contract

Repository Template.xls
ARI.032 Strategic Sourcing - Contract Repository

Check In Tool.xls
ARI.033 Strategic Sourcing - Contract Repository

Load Work Instructions for Clients.docx
ARI.034 Strategic Sourcing - Contracting Process

Design Matrix - All Types.xls
ARI.035 Strategic Sourcing - Introduction to
Contract Authoring Best Practices.pptx
ARI.036 Strategic Sourcing - Clause Library

Template.xlsx
ARI.037 Strategic Sourcing - Form Data Collection

Template.xlsx
ARI.038 Global Delivery - Working with SAP Ariba

Analysis and Reporting.zip
ARI.039 Strategic Sourcing - Internal Testing

Checklist.xls
ARI.040 Strategic Sourcing - All Solutions Test

Script.xlsx
ARI.041 Strategic Sourcing - Move to Production

Checklist.xls
ARI.042 Strategic Sourcing - Deployment

Summary and Internal Transition
Checklist.xls
ARI.043 Strategic Sourcing - Solution Planning
Work Instructions.docx
ARI.044 Strategic Sourcing - Flex Master Data
Presentation.pptx
ARI.045 Strategic Sourcing - Customizing

Reviewing and Loading the Enablement
Workbook.docx
ARI.046 Strategic Sourcing - Enablement

Workbook - Review and Loading
Reference Guide.xlsx
ARI.047 Client Automation Technical White

Paper.pdf
ARI.048 Strategic Sourcing - Customization User
Interface Field Creation.docx
ARI.049 Strategic Sourcing - Working with

Contract Repository Loads
(INTERNAL).docx
ARI.050 Strategic Sourcing - Legacy Contract

Repository Load Instructions.ppt
ARI.051 Strategic Sourcing - Creating Process

Templates Work Instruction.docx
ARI.052 Strategic Sourcing - Electronic Signature

Work Instructions.docx
ARI.053 Strategic Sourcing - Authoring Main

Agreements.docx
ARI.054 Strategic Sourcing - Creating a Clause

Library
ARI.055 Strategic Sourcing - Understanding Ariba

Forms.pptx
ARI.056 Strategic Sourcing - Creating Form

Templates Work Instruction.docx
ARI.057 Strategic Sourcing - Internal Testing Work

Instructions.docx
ARI.058 Strategic Sourcing - Moving Data &

Configurations from TEST to PROD.docx
ARI.059 Strategic Sourcing - Deployment Wrap Up

Instructions.docx
ARI.060 Data Strategy L1 Meeting Agenda
ARI.061 Data Strategy Shared Master Data Flow

Diagram
ARI.062 Data Strategy Shared Master Data
Overview
ARI.063 Data Strategy L2 Shared Master Data
Source Details
ARI.064 Architecture Review Operating Model
ARI.065 Architecture Review Pre-Readiness

Questionnaire
ARI.066 Sample Architecture Diagram and

Realm/Account Strategy
ARI.067 Architecture Review Customer Session

Deck
ARI.068 Architecture Review Sample Customer

Email
ARI.069 Architecture Review Solution

Compatibility Matrix
ARI.070 Architecture Review Operating

Model.docx
ARI.071 Architecture Review Middleware

Strategy.pptx
BOM.131 Project schedule XML
GL.27 Project Closeout Report Presentation

Template
PM.13 Project Kick-off Template
PM.15 Project Charter Template
PM.18 Scope Statement Template
PM.194 Business Case Template

PM.205 Project RDS Quality Gate Scorecard
Template
PM.21 Communication Plan Overview Template
PM.94 Phase Sign-Off Template
PM.98 OCM Stakeholder Identification Guide
PM.99 OCM Stakeholder Identification Template

PM_209 QGateChecklist Template Introduction
R.168 MS Project Cutover Schedule Sample

S4H_138 Data Quality Assessment Whitepaper
S4H_161 SAP S/4HANA Overview Learning Room
S4H_162 SAP S/4HANA Cloud Implementation

Learning Room
S4H_163 Activate Learning Room for SAP S/4HANA
S4H_206 Getting Started with the SAP S4HANA
Cloud System.docx
Description
Presentation explaining Agile project team roles and responsibilities. Focusing on new roles and
responsibilities introduced by Agile approach.
The purpose of this accelerator is to capture the Delta Requirements and Gaps during the Scope
Validation workshops in the Explore phase. It will also act as a template of the Project and Sprint
Backlog for Agile Project.
Presentation explaining approach to release and sprint planning in Agile project.

A template for the presentation that is used in the kick-off workshop to align on activities and
responsibilities, and present the scope of the project.
A sample check list which is a combination of an action list and also a tool to verify that necessary
steps have been completed to ensure the success of the project.
A document that clearly and explicitly defines the objectives of the proposed project, analyzes all
possible benefits, and quantifies benefits in financial terms.
A document template that facilitates an initial understanding of the project scope and associated
project-related assumptions and constraints.
A template used to provide an overview of the communication plan of the project.
Pre-Planning Presentation
Meeting Notes Accelerator
Governance Accelerator
CAT Time and Expense Tracking
Template used for project status reporting.
Template list used for collection and tracking of issues in the project.
Quality Built In New Q-Gate Checklist - External
Ariba Sales to ACO Handoff Document
Business Case Flight Plan Handoff v5 (003)
Ariba Sales Handoff Provisioning Staffing Updates
Ariba Site Enablement Document Master Q2 2017 v17
Project Roles & Responsibilities
VOC Process Flow Chart

PMO Project Review
ARI.020_PMAR_44_Change
ARI.021_PMAR.306_Change Request Form.docx
ARI.022_PMAR.307_Agile Change Control Process.pptx
This document is an overview of SAP Ariba Education Services.
This is the ZIP file used to load into a customer's test site during the realm enablement process.
The Contracting Process Design Matrix collects all relevant information required to build the
Contracting processes within the site.
This document is used to collect master data as part of Strategic Sourcing Shared Services team
deployments for Sourcing, Contracts, SIPM and SLP.
This template will be used by Strategic Sourcing Configuration Leads to document errors in customer
data collection templates for resolution.
This is a template to collect requirements of customers in terms of standard and custom header
fields during deployment of Sourcing, Contracts, SIPM and/or SQM.
The Contract Repository template is used to collect header field information that will be input into
SAP Ariba Contracts for bulk-loaded Contracts. Descriptions of each field within the template are
provided within the template.
The Contract Repository template is used to collect header field information that will be input into
SAP Ariba Contracts for bulk-loaded Contracts. Descriptions of each field within the template are
provided within the template below.
Contract Repository Check-In tool is used by Strategic Sourcing Deployment and Configuration Leads
to check the completed Contract Repository template submitted by client against the Enablement
Workbook for accurate data, or data gaps. This tool accelerates loading of contracts during the
deployment of SAP Ariba Contracts solution.
This document provides detailed instructions, including screen shots, on how clients can complete
the repository template, prepare their load files, and load legacy contracts in SAP Ariba Contracts.
The Contracting Process Design Matrix collects all relevant information required to build the
Contracting processes within the site.
This presentation includes topics like introduction and value proposition for authoring, best practice
use cases, customer case studies, and important items to consider. It also covers what to do once
your client decides to pursue contract authoring including pre-kick off preparations, main agreement
analysis of structure and format, section global contract, document properties, etc.
This template is used to collect requirements associated with the Clause Library from the client
during an upstream Contract Management Professional deployments.
This data collection template is used by the Strategic Sourcing shared services deployment team to
gather client requirements for dforms.
This document describes how to work with prepackaged, custom and multi-fact reports in SAP Ariba
Analysis as well as reporting related permissions. It also discusses talking points and questions for
talking to clients about reporting.
This checklist will be completed by Configuration Leads/Deployment Lead to document internal

testing for Strategic Sourcing team deployments.
Customer test script for all Strategic Sourcing solutions including: Sourcing, Savings Tracker,
Contracts, SIPM (classic), SIPM (new architecture), SLP.
This checklist is used in conjunction with the Moving configurations from test to production work
instruction during an Ariba Strategic Sourcing shared service team deployments.
This document provides an overview of the customer specific configurations that were completed
during the deployment.
This presentation is to be used to facilitate Flex Master Data discussions with customers during
Strategic Sourcing deployments. It contains an overview of Flex Master Data, its structure, usage
examples, and reporting limitations.
The purpose of this document is to provide instructions on customizing an enablement workbook

based upon the specific solutions being deployed; reviewing a completed workbook for errors an
documenting those errors in the error report; and loading enablement workbook data to a
customer’s site as part of deployment.

This document provides guidance on trouble shooting and reviewing the enablement workbook
prior to loading as well as a guide for how information from the enablement workbook should be
loaded/updated via Service Manager.
This document describes the deployment and set up of the Ariba Client Automation control. Users of
Ariba Upstream Platform applications, particularly of Ariba Contract Management and Ariba Analysis
can use this white paper to understand the Ariba Client Automation control and set it up for use
with these products.
This document is to guide you through how to access and use the Customization User Interface to
build custom header fields and modify standard fields where allowed. There is also important
information on how to push your customizations from TEST into PRODUCTION.
This document provides an overview of all aspects related to repository loads during an SAP Ariba
Contracts deployment including reviewing the template with clients, using the checkin tool,
uploading contracts, demoing to clients, etc.
This presentation can be used with or provided to clients for assistance with loading legacy contracts
during an SAP Ariba Contracts deployment.
This document provides a comprehensive overview of how to build Strategic Sourcing process
templates, including conditions and team member rules.
This document details how DocuSign and EchoSign can be configured for SAP Ariba Contracts clients
as part of deployment.
This document provides a comprehensive overview of how to analyze and configure a main
agreement in SAP Ariba Contracts.
This document provides instruction on reviewing the clause library template, pushing clauses from
the main agreement into the clause library, building the clause library, and loading clauses.
This presentation can be used to help explain Ariba Forms to clients as part of Strategic Sourcing
Shared Services team deployments.
This document describes how to create custom dform templates and tasks associated with the
dform. Dforms are typically configured as part of strategic sourcing team deployments.
This work instruction explains the methods and resouces to be used by SAP Ariba Configuration
Leads and Deployment Leads while completing 1) internal unit testing after each configuration has
been completed, and 2) internal testing in Test and Production environments prior to customer
testing.
This document provides instructions on how to move data and configurations associated with all
Strategic Sourcing Deployment Team solutions from Test to Production as part of deployment.
This docuement describes the steps to prepare for the Deployment Wrap Up and Go Live for
Strategic Sourcing Shared Services team deployments.
Agenda template to be sent when scheduling the L1 data strategy workstream.
Data flow of end to end full suite ideal state.
Review of master data shared across all solutions.
Field level review of shared master data elements.

Internal document to instruct the Customer Value Organization (CVO) delivery teams on what they
must do to support/complete the Architecture Review process
This template is used to document the customer's ERP, backend systems, middleware, 3rd
party systems, and other areas that may impact the project. It is to be pre-populated by Ariba
based on the Sales-To-Delivery Handoff session, subsequently supplemented by the customer, and
eventually will be the document we used to obtain signoff on Architecture scope.
Visio set of sample diagrams that can be used to facilitate discussions around Data
Strategy/Rationalization, Realm Strategy, Integrations, Automation, and various Ariba Solution
Landscapes.
Presentation template to be customized for the customer and used when conducting the
Architecture Review session.
This email template can be filled out and sent to the customer to inform them of Ariba's intent
to conduct the Arch Review Session, session goals, who should participate, scheduling, and next
steps.
Reference to be used in advance of the Arch Review session to see if there are any compatibility
concerns with the proposed solution footprint.
This is an internal document to instruct the Customer Value Organization (CVO) delivery teams on
what they must do to support/complete the Architecture Review process.
Comparison between middleware strategy with traditional Cloud Integration (CI9 SP2) vs CIG.
A file to exchange data about the project structure into an SAP Solution Manager system (7.2
onward).
A template presentation for the project closeout report.
A template for the presentation that is used in the kick-off workshop to align on activities and
responsibilities, and present the scope of the project.
A document that clearly and explicitly defines the objectives of the proposed project, analyzes all
possible benefits, and quantifies benefits in financial terms.
A document template that facilitates an initial understanding of the project scope and associated
project-related assumptions and constraints.
A template that describes the required components of an implementation business case.
The Project Quality Scorecard for RDS records the results of the Quality Assements for the Phase
Start & Phase Deploy & Run
A template used to provide an overview of the communication plan of the project.
The Phase Acceptance and Closure ensures that the Phase deliverable(s) requirements and
expectations of the deliverable(s) is met, approved and accepted or conditionally accepted.
A guide on how to perform stakeholder identification.
An excel template used for stakeholder identification and project influence valuation.

An external presentation that serves as an introduction to the Quality Gate Checklist Template
Sample of an MS Project Cutover Schedule

Data Quality Assessment Whitepaper
Experience with SAP Learning Hub instant access to a vast learning knowledge-base created by SAP
for business users and IT

SAP S/4HANA Implementation and Configuration Learning Room by SAP Education
SAP Activate Learning Room for SAP S/4HANA by SAP Education

A guide to getting started with the intialS4HANA cloud system without EC integration.
Filename Accelerator Type Access Level
Agile- Reference material SAP Customer
ProjectTeamRolesandResponsibilities.ppt
Template Public
AgileReleasePlanning.ppt Reference material SAP Customer

PMAR.13_Strategic_Sourcing_- Prefilled Template SAP Customer
_Deployment_Kick_Off_Presentation.PPTX
PMAR.01_Deployment Checklist.doc Sample SAP Customer
PMAR.15_Project_Charter_Template.docx Template SAP Customer
Template SAP Customer
PMAR.21_CommunicationPlan.docx Template SAP Customer
ARI.006 Reference material SAP Employee
PMAR.301_Meeting Notes Accelerator.docx Template Public
PMAR.302_Governance Accelerator.pptx Template Public
PMAR_41_Customer_Status_Report_Accele Template SAP Customer

rator.pptx
PMAR_45_RAID_Log.xlsx Template SAP Customer
PMAR_211.xlsb Reference material Public
ARI.013 Template SAP Employee
ARI.014 Template SAP Employee

Template Public
Template Public
Reference material Public
ARI.023.pptx Template SAP Customer
ARI.024.zip Template SAP Customer
ARI.026.xls Template SAP Customer
ARI.029.xlsx Template SAP Customer
ARI.033.docx Template SAP Customer

ARI.035.pptx Template SAP Customer
Reference material SAP Employee

Data Strategy_L1 Meeting Agenda Template Public
Data Strategy L1_Shared Master Data Flow Template Public

Diagram
Data Strategy L1_Shared Master Data Template Public
Overview
Data Strategy L2_Shared Master Data Source Template Public
Details
ArchitectureReview_OperatingModel_Final. Reference material SAP Employee
docx
ArchitectureReview_PreReadinessQuestionn Template Public

aire_Final.docx
ArchitectureReview_SampleArchitectureDia Reference material Public

gramAndRealmAccountStrategyTemplate_Fi
nal.vsdx
ArchitectureReview_CustomerSessionTempl Template Public

ate_Final.pptx
ArchitectureReview_SampleIntroEmailTempl Template SAP Employee

ate_Final.docx
ArchitectureReview_SolutionCompatibilityM Reference material SAP Employee

atrix_Final.xlsx
ARI.070 Architecture Review Operating Reference material SAP Employee

Model.docx
ARI.071 Architecture Review Middleware Reference material Public

Strategy.pptx
Template Public
ProjectCloseoutReportPresentationTemplate Template SAP Customer

.ppt
ProjectKick-offProject.xxX_Template.ppt Template SAP Customer
ProjectCharter_Template.doc Template SAP Customer
ScopeStatement_Template.doc Template SAP Customer
BusinessCase_Template.doc Template SAP Customer

ProjectRDSQualityGateScorecardTemplate Template SAP Customer
CommunicationPlanOverview_Template_20 Template SAP Customer

09.ppt
PhaseSignOff_Template.doc Template SAP Customer
ASAP_Prep_OCM_StakeholderIdentification Reference material SAP Customer

_guide.ppt
ASAP_Prep_OCM_StakeholderIdentification Template SAP Customer
_template.xls
5.6.1SAPMSProjectCutoverSample.mpp Sample SAP Customer

How-to Guide SAP Customer

S4H_206 Getting Started with the SAP How-to Guide Public
S4HANA Cloud System.docx
Workstream
Agile
Agile
Agile
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Project Management
Application: Customer Team Enablement
Technical Architecture & Infrastructure
Application: Design & Configuration

Application: Testing
System & Data Migration
Transition to Operations

Transition to Operations

Project Management
Project Management
Project Management
Project Management
Project Management
Application: Solution Adoption

Project Management
Project Management

Project Management

Training - Training
Training - Training
Training - Training
Source URL
https://support.sap.com/content/dam/SAAP/SAP_Activate/AG_03.pptx
https://support.sap.com/content/dam/SAAP/SAP_Activate/AG_16.xlsx
https://support.sap.com/content/dam/SAAP/SAP_Activate/AG_17.ppt
https://support.sap.com/content/dam/SAAP/SAP_Activate/PMAR.13_Strategic_Sourcing_-
_Deployment_Kick_Off_Presentation.PPTX
https://support.sap.com/content/dam/SAAP/SAP_Activate/PMAR.01%20Deployment
%20Checklist.doc
https://support.sap.com/content/dam/SAAP/SAP_Activate/PMAR.15.docx
https://support.sap.com/content/dam/SAAP/SAP_Activate/PMAR.18.doc
https://support.sap.com/content/dam/SAAP/SAP_Activate/PMAR.21_CommunicationPlan.doc
x
https://documents.wdf.sap.corp/share/proxy/alfresco//api/node/content/workspace/SpacesSt
ore/beeb1b95-837f-4398-b018-c4c9121bf8d2/ARI.006.pptx
https://support.sap.com/content/dam/SAAP/SAP_Activate/PMAR.301_Meeting%20Notes
%20Accelerator.docx
https://support.sap.com/content/dam/SAAP/SAP_Activate/PMAR.302_Governance
%20Accelerator.pptx
ore/08b3a370-a45f-41d7-bdad-2af4ed3eda92/ARI.009.xlsm
https://support.sap.com/content/dam/SAAP/SAP_Activate/PMAR_41_Customer_Status_Repo
rt_Accelerator.pptx
https://support.sap.com/content/dam/SAAP/SAP_Activate/PMAR.45_RAID%20Log.xlsm
https://support.sap.com/content/dam/SAAP/SAP_Activate/PMAR_211.xlsb
ore/8f3a009a-3e3d-4b4b-9206-7125f54f610a/ARI.013.docx
ore/05980db2-b856-492e-9c7a-fe4001db672d/ARI.014.pptx
ore/44ea49cb-d34e-434a-8e80-687f37a16c93/ARI.015.pptx
ore/272d2b58-d84d-4aea-acb5-d271147e63c6/ARI.016.xlsx
ore/145808de-b2e0-48e8-8b0f-72c7ccdc1db2/ARI.017.pptx
ore/70e5a4fd-b2b1-435f-a36a-0077e9377546/ARI.018.pptx
ore/556083a9-6ad1-4c33-8fee-933a08d5b0fc/ARI.019.pptx
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.020_PMAR_44_Change
%20Request%20Log.xls
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.021_PMAR.306_Change
%20Request%20Form.docx
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.022_PMAR.307_Agile
%20Change%20Control%20Process.pptx
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.023.pptx
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.024.zip
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.026.xls
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.029.xlsx
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.033.docx
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.035.pptx
https://documents.wdf.sap.corp/share/proxy/alfresco/api/node/content/workspace/SpacesSt
ore/74e1f41c-67a7-4039-a8f4-24005b12ebb5/ARI.043.docx?a=true
ore/3f44e6c8-de5d-4d48-a3b6-3813877f3a8f/ARI.044.pptx?a=true
ore/70e58a1a-5846-424d-beef-b9d5e75f554d/ARI.045.docx?a=true
ore/7811abb4-5c89-4d35-8c29-5ac0e13b31bf/ARI.046.xlsx?a=true
ore/05ed0a8f-850c-4be6-a71e-ca8a2918c2b0/ARI.047.pdf?a=true
ore/0c526dd2-02c7-4916-a325-469721415e28/ARI.048.docx?a=true
ore/f101e0d7-e706-4bf4-882d-03f9fa780c06/ARI.049.docx?a=true
ore/8ae69f4a-ce84-40f1-820d-2a2647363899/ARI.050.ppt?a=true
ore/801075cd-6b4d-46a1-a3d1-7c3e6ae561bf/ARI.051.docx?a=true
ore/d2aa4b65-119a-4b29-a993-dc8028b07d92/ARI.052.docx?a=true
ore/bcba7d53-0c79-4a60-b699-90582c93dbf3/ARI.053.docx?a=true
ore/f2b73667-0414-426d-9c5c-bdede81aef4d/ARI.054.docx?a=true
ore/8baa8d8b-0268-4fa4-bd53-870aeee343e3/ARI.055.pptx?a=true
ore/33a82690-9a88-4bd4-ae36-7e1c70b79fa4/ARI.056.docx?a=true
ore/6fb17bd5-b71f-40ab-b162-9b76dc04e20b/ARI.057.docx?a=true
ore/330b410c-deab-4e81-8b6e-28d03294a585/ARI.058.docx?a=true
ore/52d4b636-d744-48fa-bd75-7018a0ccafaa/ARI.059.docx?a=true
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.060%20Data%20Strategy
%20L1%20Meeting%20Agenda.docx
%20L1_Shared%20Master%20Data%20Flow%20Diagram.vsdx
%20L1_Shared%20Master%20Data%20Overview.xls
%20L2_Shared%20Master%20Data%20Source%20Details.xlsx
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.064%20ArchitectureReview_O
peratingModel.docx
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.065%20ArchitectureReview_Pr
eReadinessQuestionnaire.docx
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.066%20ArchitectureReview_Sa
mpleArchitectureDiagramAndRealmAccountStrategyTemplate.vsdx
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.067%20ArchitectureReview_C
ustomerSessionTemplate.pptx
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.068%20ArchitectureReview_Sa
mpleIntroEmailTemplate.docx
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.069%20ArchitectureReview_S
olutionCompatibilityMatrix.xlsx
https://documents.wdf.sap.corp/share/page/site/sap-activate/document-details?
nodeRef=workspace://SpacesStore/f0a44f9f-20a8-479d-9869-cb67426c9bc0
https://support.sap.com/content/dam/SAAP/SAP_Activate/ARI.071%20Architecture
%20Review%20Middleware%20Strategy.pptx
https://support.sap.com/content/dam/SAAP/SAP_Activate/SAP%20Activate%20Methodology
%20for%20Ariba%20Project%20Plan.zip
https://support.sap.com/content/dam/SAAP/SAP_Activate/GL_27.ppt
https://support.sap.com/content/dam/SAAP/SAP_Activate/PM_13.pptx
https://support.sap.com/content/dam/SAAP/SAP_Activate/PM_15.doc
https://support.sap.com/content/dam/SAAP/SAP_Activate/PM_205.xlsx
https://support.sap.com/content/dam/SAAP/SAP_Activate/PM_21.ppt
https://support.sap.com/content/dam/SAAP/SAP_Activate/PM_98.ppt
https://support.sap.com/content/dam/SAAP/SAP_Activate/PM_99.xls
https://support.sap.com/content/dam/SAAP/SAP_Activate/PM_209.pptx
https://support.sap.com/content/dam/SAAP/SAP_Activate/R_168.mpp
https://support.sap.com/content/dam/SAAP/SAP_Activate/S4H_138.pdf
https://jam2.sapjam.com/groups/about_page/MDC2ZYZbpZMMK7U0U3VVfK
https://jam2.sapjam.com/groups/about_page/5gwxDPWQPRtOvMO8Xnd32Q
https://jam2.sapjam.com/groups/about_page/fHaQLt0HVw1NHeKIaGu0MG
https://support.sap.com/content/dam/SAAP/SAP_Activate/S4H_206%20Getting%20Started
%20with%20the%20SAP%20S4HANA%20Cloud%20System.docx
Is Accelerator generic File Mime Type
X application/vnd.ms-powerpoint
X application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
application/vnd.ms-powerpoint
application/msword
application/msword
application/msword
application/msword
application/vnd.openxmlformats-officedocument.presentationml.presentation
application/msword
application/vnd.ms-excel.sheet.macroenabled.12
application/vnd.ms-excel.sheet.macroenabled.12
application/vnd.ms-excel.sheet.binary.macroenabled.12
application/vnd.openxmlformats-officedocument.wordprocessingml.documen
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
application/octet-stream
application/x-zip-compressed
application/vnd.ms-excel
text/html
text/html
text/html
text/html
text/html
text/html
text/html
text/html
text/html
text/html
text/html
text/html
text/html
text/html
text/html
text/html
text/html
application/msword
X application/msword
X application/x-zip-compressed
X application/vnd.ms-excel
X application/vnd.ms-project
application/pdf
text/html
text/html
text/html
File Extension Publishing Indicator Last Changed At Tags
PPT X 20.12.2017 22.49.22 Project Management
XLSX 30.03.2018 21.54.33
PPT 16.08.2017 15.50.03 Project Management

PPT 17.08.2017 16.00.48 Ariba: Contract Management,Project Management
DOC 17.08.2017 16.08.46 Ariba: Contract Management,Project Management
DOC 17.08.2017 15.46.56 Project Management
PPTX 26.09.2017 22.42.15 Project Management
DOC 17.08.2017 16.13.46 Ariba: Contract Management,Project Management
XLSM 17.08.2017 16.15.48 Ariba: Contract Management,Project Management
XLSM 17.08.2017 15.54.09 Ariba: Contract Management,Project Management
XLSB 17.08.2017 16.17.14 Ariba: Contract Management,Project Management
DOCX 25.09.2017 21.39.58 Project Management
XLSX 25.09.2017 21.47.47 Project Management

XLXS 22.11.2017 16.59.10 Project Management
PPTX 20.12.2017 21.24.15 Ariba: Contract Management
ZIP 20.12.2017 20.47.58 Ariba: Contract Management
XLS 27.12.2017 23.26.21 Ariba: Contract Management
XLSX 28.12.2017 19.22.26 Ariba: Contract Management
DOCX 28.12.2017 19.38.39 Ariba: Contract Management

PPTX 28.12.2017 19.57.49 Ariba: Contract Management
HTML 27.12.2017 23.24.00 Ariba: Contract Management

DOCX 28.06.2018 02.04.39
VSDX 28.06.2018 02.04.39
XLSX 28.06.2018 02.04.39
XLSX 28.06.2018 02.04.39

DOCX 28.06.2018 21.20.15
DOCX 28.06.2018 02.04.39
VSDX 28.06.2018 02.04.39
PPTX 28.06.2018 02.04.39
DOCX 28.06.2018 02.04.40
XLSX 28.06.2018 02.04.40
DOC 18.07.2018 17.07.30
PPTX 18.07.2018 17.04.40
zip 09.02.2018 17.35.28
DOC X 16.08.2017 15.50.02 Project Management
DOC X 16.08.2017 15.50.02 Project Management

ZIP 16.08.2017 15.50.03 Project Management
PPT X 16.08.2017 15.50.03 Project Management
DOC X 16.08.2017 15.50.03 Ariba: Contract Management,Project Management
XLS X 16.08.2017 15.50.03 Project Management

PPTX 17.08.2017 16.29.18 Ariba: Contract Management,Project Management
MPP X 29.12.2017 16.35.58 Project Management

PDF 29.12.2017 15.56.16 Project Management
html 20.12.2017 21.19.46 Project Management

Management
Management
Management
Management
Management
Management
Management
Management
Management
Management

SAP Activate Methodology For SAP Ariba

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Activate Methodology For SAP Ariba

Uploaded by

Copyright:

Available Formats

Sequence Number Title

1.1 Realm Enablement

1.2 Customer Team Self-Enablement

1.3.1 Conduct Handover Meeting with Sales

1.3.3 Establish Project Governance

1.3.4 Define Project Communications and Reporting

1.3.5 Create Pre-Planning Presentation

1.3.6 Conduct Engagement Review (if applicable)

1.4.1 Create Project Schedule and Budget

1.5 End User Learning Strategy

1.5.1 Develop End User Learning Strategy

1.6 Project Standards and Infrastructure

1.6.1 Define Project Standards

1.6.2 Setup Project Team Logistics and Infrastructure

1.7 Project Kick-Off and On-Boarding

1.7.1 On-board Project Team

1.7.2 Conduct Kickoff Workshop

1.8.1 Conduct Project Quality Gate

1.8.2 Obtain Customer Sign-Off for Phase Completion

1.9 Architecture Review

1.9.1 Populate Architecture Review Pre-review

1.9.2 Contact Customer Regarding the Architecture

1.9.3 Deliver Architecture Review Questionnaire to

1.9.4 Respond to Architecture Review Pre-Readiness

1.9.5 Update the Architecture Review PowerPoint

1.9.7 Conduct the Architecture Review Session with

1.9.8 Architecture Review Session Follow-up

1.9.9 Review Final Deck with Customer

1.9.10 Customer Approves the Architecture Review

1.9.11 Inform Customer of Next Steps Following the

1.9.12 Inform Customer of Next Steps Following the

1.9.13 Archive Architecture Review Material in the

1.10 Data Strategy

1.10.1 Schedule L1 Data Strategy Discussion

1.10.3 Facilitate L1 Data Strategy Discussion

1.10.4 Schedule L2 Data Strategy Discussion

1.10.5 Incorporate Customer Feedback and Prepare for

1.10.6 Facilitate L2 Data Strategy, Risk & Service Level

1.10.7 Document and Archive Output

2.1 Execution/Monitoring of Project

2.1.1 Direct and Manage Project Execution

2.1.3 Manage Project Issues, Risks, and Changes

2.1.4 Communicate Project Status and Progress

2.2 Solution Planning

2.3 Solution Definition

2.4 User Access and Security

2.4.1 Map Authorization Roles to Users

2.5.1 Apply Integrated System Prerequisites

2.5.2 Confirm Integration Prerequisites

2.6.2 Obtain Customer Sign-Off for Phase Completion

3.1 Execution/Monitoring of Project

3.1.1 Direct and Manage Project Execution

3.1.2 Update Project Management Documents

3.1.4 Manage Project Issues, Risks, and Changes

3.1.5 Communicate Project Status and Progress

3.2 Solution Configuration

3.2.1 Enablement Workbook

3.2.3 Contract Repository Configuration

3.2.4 Contract Process Configuration

3.2.5 Main Agreement

3.2.7 Electronic Signature Integration

3.3 Forms Adaptation Preparation

3.5 Configuration Freeze