Ariba Procurement Content Deployment Description 14s Procurement

Ariba Procurement Content TM
Revision Date: October 2016
Deployment Description
This document describes the Deployment Services for the
following Ariba Solution
Solution: Ariba Procurement ContentTM

Package: N/A
© 2001 - 2016 Ariba, Inc. All Rights Reserved.

The contents of this document are confidential and proprietary information of Ariba, Inc. Distribution without express permission from Ariba is
prohibited.
0
I. DEFINTI ONS
· “Solution” – the electronic functionality accessible via the internet, any related incidental software components, and any related
subscription-based services, provided by Ariba to customers as a named package on a subscription basis and described in the portion
of the Documentation corresponding to such named package. Solutions are sometimes also referred to as “Cloud Services” or the
“Service” in Ariba contracts and Documentation. As used in this Deployment Description, “Solution” refers specifically to the Ariba
Procurement ContentTM Solution, (“APC”)
· “Deployment Description” – Document that describes the Deployment Services which Ariba provides to Customer in conjunction
with the Solution, to assist Customer in configuring the Solution and making the Solution accessible to Customer’s users. This
document is a Deployment Description.
· “UI” – User Interface
· “CIF” – Catalog Interchange Format
· “cXML” – Commerce XML
· “EDI” – Electronic Data Interchange
· “Site” – the Solution website accessible by and configured for Customer
Capitalized terms used in this Deployment Description that are not defined above are defined in the Ariba Subscription Agreement or
Order Form between Ariba and Customer, or represent the name of Solution features.
II. INTRODUC TION
The Deployment Description is meant to provide a high level overview of the Deployment Services provided with this Solution.
II I. ARIBA DEPL OYM ENT SCOP E OF S ERVICES
Ariba will provide the services as described below (“Deployment Services”). The Deployment Services described in this document are a standard
offering included in the one-time (non-recurring) fee for Deployment Services related to the Solution for the configuration of a single
production Site and a single test Site. Deployment Services may not be provided in countries in which the Solution is not compliant with all
applicable local laws and/or in which support is not available. Any change in the specific scope of Deployment Services must be mutually agreed
upon by the parties in writing and may be subject to additional fees.
PHASE 1: SOLUTION PLANNING
Ariba Activities:
1) Send Customer the URL to their Solution Environment
2) Establish project infrastructure
3) Confirm deployment scope and approach
4) Define solution set-up
Ariba Deliverables:
1) Account Map defined between Ariba and Customer including escalation paths, roles/responsibilities, and sponsorship.
2) Project plan established including solution scope, geographic scope, and goals and objectives.
3) Test Data Ready for loading into the system
PHASE 2: FUNCTIONAL CONFIGURATION

prohibited.
1
Ariba Activities:
1) Conduct three (3) day on-site Configuration Workshop
2) Present configuration recommendations and/or finalize configuration workshops on major areas of product functionality
3) Assist Customer in learning how to configure approval rules
4) Configure parameters
5) Build customizations per Order Form scope
6) Support resolution of issues with initial data loads
Ariba Deliverables:
1) APC Test Site enabled with active user
2) Functional Configuration document complete with Customer Site configuration details
PHASE 3: SOLUTION CONFIRMATION
Ariba Activities:
1) Assist in coordination and facilitation of a Solution Confirmation workshop. The Solution confirmation workshop is intended to assist the
Customer and core team with moving from functional configuration to the Test phase with a designed and built test system.
Ariba Deliverables:
1) Provide best practices with regard to execution Solution Confirmation workshop
2) Assist in identifying key decision and scenarios
3) Support question and answer for core team in preparation for Solution Confirmation workshop
4) Support core team’s facilitation of Solution Confirmation workshop
PHASE 4: TESTING
Ariba Activities:
1) Provide detailed guidance and best practices for Customer's use case scenarios and test plan
2) Log cases and enhancement requests with Ariba Support, as needed
3) Provide status updates on any Ariba product issues, as needed
Ariba Deliverables:
1) Draft of sample test plan and use case scenarios
2) Up-to-date issue log
3) Updated functional configuration document, if applicable
PHASE 5: GO LIVE
Ariba Activities:
1) Brand and configure production Site
2) Assist with resolution of data load and production testing issues
Ariba Deliverables:
1) Production Site available

prohibited.
2
PHASE 6: TRANSITION AND WRAP UP
Ariba Activities:
1) Finalize and post all deployment documentation
2) Conduct Customer Support transition meeting
Ariba Deliverables:
1) Open Issue and Enhancement Request List
IV. DEPLO YME NT S ERVIC ES TIMELIN E
· ‘Go Live’ is defined as the date on which live transactions are entered into the production Site
· The APC deployment will be delivered per the standard phases and standard deployment timeline, as outlined below.
· The maximum services term for the APC deployment is sixteen (16) calendar weeks as described in the standard deployment
timeline, as outlined below. The deployment timeline includes fourteen (14) weeks to ‘Go Live’ and two (2) weeks of post
deployment support.
· The APC Deployment Services term is the lesser of the maximum service term or APC ‘Go Live’.
· The Customer Support Transition meeting must occur prior to ‘Go Live’.
· Customer ‘Go Live’ must be supported by the Ariba deployment team.
· The Ariba deployment team will support Customer for two (2) weeks after ‘Go Live’ (up to a maximum of sixteen(16) total weeks
unless extended by a project change request)
· At two (2) weeks after ‘Go Live’, the Ariba deployment team will formally exit the deployment. From this time, the Customer will be
supported by Ariba Customer Support.
· If Customer ‘Go Live’ is not achieved within the fourteen (14) week services timeline, a deployment extension must be mutually
agreed upon by the parties in a signed writing. Ariba’s standard project change request procedures may be used to document these
changes.
· Ariba offers additional services beyond the scope as described in this Document and in the contract between Ariba and Customer,
including, for example, expanded implementation to additional regions, departments or business units, a project extension must be
mutually agreed upon by the parties in a signed writing and additional fees may apply.
· Customer acknowledges that if Customer chooses to delay the deployment timeline in order to wait for a service pack release, that
delay will be addressed through a project change request and result in an increase in the deployment services timeline.
V. SERVICE S PAR AMETERS
The Deployment Services described in this document are a standard offering included in the one-time (non-recurring) fee for Deployment
Services related to the Solution provided the following parameters are met:
· Scope of Deployment Services is limited to the activities and tasks outlined in the Document during the initial subscription term
· For information regarding the catalog services to be delivered as part of this package, please review the Catalog Solution
Documentation.
· Scope of Deployment Services is limited to a single punch in integration from one (1) single instance of Customer ERP system
· The following Ariba services are outside the scope of Deployment Services and are offered separately for an additional fee via a
SOW: consulting program management, consulting technical support, change management services, Ariba training services, and
supplier strategy.
· Support for supplier transactions on the AN, and EDI and cXML supplier transactions are outside the scope of Deployment Services.
Please reference the Supplier Enablement Document for details on those services.
· Scope of Deployment Services does not include deployment of Single Sign On or Corporate Authentication in the Customer’s
Solution Site. If Single Sign On or Corporate Authentication is elected by the Customer, it is assumed that all infrastructure is in place,
the Customer is currently using Single Sign On or Corporate Authentication., and the Customer is able to provide the configuration
details needed to enable this for the Solution.
· Stress and performance testing are not in the scope of the APC Deployment Services.
· Any work efforts and/or solutions that are not specified within the Deployment Services described above are out scope; such
services could be included for an additional fee in a change request signed by the parties
· Program management activities for deployment of multiple Ariba solutions are not in the scope of APC Deployment Services.

prohibited.
3
· This Document outlines the standard services scope and assumptions for Deployment Services. During the deployment, Ariba and/or
the Customer may identify the need to custom scope the deployment if any of the core assumptions in this Document do not apply.
The custom scope for services are offered separately for an additional fee via a SOW.
· These services are provided one-time only during the initial Services Term specified in the “Deployment Services Timeline” and do
not apply to the remainder of the Subscription Term or any subsequent renewal term.
VI. RESOURC ES
RESOURCES - ARIBA
· Ariba will provide a Deployment Team Project Lead (“Project Lead”) and Deployment Team Technical Lead (“Technical Lead”) to
assist Customer with Deployment Service under this Document.
· The Project Lead and Technical Lead are allocated to the deployment on a part time basis- to a maximum of twenty (20) hours per
week.
· All deployment activities assigned to the Project Lead and Technical Lead will be conducted during normal business hours.
· Customer is responsible for all travel expenses related to the on-Site Configuration Workshop meeting. Travel expenses will be billed
as incurred.
· The Project Lead and Technical Lead will support all other deployment activities remotely.
· All Deployment Services and documents will be delivered in English.
· The Ariba deployment team will be responsible for logging ‘Service Requests’ (“SRs”) and ‘Enhancement Requests’ (“ERs”) on behalf
of the Customer during the deployment. The Ariba deployment team will provide status updates on SRs and ERs are they become
available. Resolution of SRs and ERs will follow the standard Customer Support Services processes.
RESOURCES - CUSTOMER
· Customer shall staff the following deployment roles as detailed in Table 1. Ariba assumes that assigned resources have correct skills
and knowledge to complete all listed responsibilities.
· Customer shall staff the deployment roles per the allocations detailed in Figure 1. This is a minimum recommended allocation.
· Solution Planning scheduling is dependent on the Customer deployment team resources being identified and allocated to the
deployment as detailed in Table 1 and Figure 1.
· If the Customer resources are not able to complete the responsibilities as detailed in Table 1 and the deployment plan either due to
skill, knowledge or time limitations, deployment delays may occur. Any extension to deployment services term due to Customer
resource limitations may result in a project change request and additional fees.
VII. CUSTOM ER’S ROL ESAND RESPONSIBILITES
Table 1 Customer commits to provide the following resources:
Customer Role Customer Responsibilities
Project Sponsor · Assign a Project Manager

· Help define overall deployment vision
· Provide guidance for high-level issue resolution
· Provide senior leadership communication in support of the deployment
· Monitor status reports and timelines
· Help to drive change management for higher adoption
Project · Point of contact for overall deployment
Manager · Secure appropriate resources and confirm availability
· Arrange participation of all required resources
· Manage deployment timeline and schedule adherence
· Provide business and technical guidance
· Facilitate configuration workshops
· Participate in deployment status meetings
· Provide timely resolution of any escalated issues

prohibited.
4
· Manage communication plan development and deployment-wide communications to key stakeholders

· Provide/coordinate signoff on all deliverables
· Participate in all transition and wrap-up discussions
· Coordinate stakeholders as needed
Functional Lead · Identify, escalate, resolve deployment issues
· Participate in configuration workshops
· Develop test cases and test scripts for testing
· Plan, manage, and conduct system testing
· Plan, manage, and conduct user acceptance testing
· Develop cutover plan and manage cutover execution
Technical Team · Technical contact for all Ariba interaction/coordination
· Participate in configuration workshops
· Oversight of interface/integration development and testing
· Build punch in integration
· Configure single sign on/ corporate authentication, if applicable
· Oversee unit testing, integration testing and issue resolution
· Participate in integration testing and UAT as needed
· Issue investigation and resolution
· Secure additional technical resources as necessary
· Conduct cutover activities
Training Lead · Overall responsibility for coordinating all training activity for end-users
· Manage training needs are addressed/issues escalated appropriately
· Develop training approach
· Develop training documentation
· Plan and manage training delivery
· Confirm training plan is in sync with overall deployment plan
·
System · Customer technical expert on Ariba platform
Administrator · Submit and track technical issues
· Main contact to Ariba support after deployment
Process Experts · Provide input to Configuration workshops
/ Pilot Users · Provide input to test case development
· Support Master Data Mapping and Extract
· Participate in UAT
· Support supplier and catalog enablement activities
· Receive training
· Support/conduct cutover activities
· There will be a single primary point of contact from the Customer for Project Management activities (“Customer Project Manager”)
· There will be a single primary point of contact from the Customer for functional activities (“Customer Functional Lead”)
· Customer will make decisions by the specified deadlines throughout the execution of the deployment.
· Required Customer resources will be available for the Customer Introduction and Customer on-site configuration workshop
meetings per the timings recommended by Ariba. Ariba reserves the right to delay either meeting if required Customer resources
are not available to attend.
· If required Customer resources are unavailable per the outlined commitments above, Ariba reserves the right to suspend of services
until the resources are confirmed. This will be done to preserve the Customer’s services timeline and make best use of that time.
· Customer acknowledges that it will be responsible for any delays relating to any deficiencies in the Customer responsibilities. Any
delays to Go Live resulting from such deficiencies in Customer responsibility will result in a deployment extension that must be
mutually agreed upon by the parties in a signed writing.
VII I. CUSTOM ER AC TIVI TI ES A ND D ELIVERA BLES
Customer activities and deliverables as detailed below will be completed per the standard deployment plan.
PHASE 0: PRE-DEPLOYMENT
1) Complete roles and responsibilities template with team member names and contact information

prohibited.
5
2) Provide Customer Site enablement details
3) Collect and understand procurement business processes to expedite decision making
PHASE 1: SOLUTION PLANNING
1) Deployment plan approved and communicated to team members
2) Provide and approve the communication plan
3) Arrange participation of all required resources per the deployment plan
4) Manage deployment timeline and schedule adherence
5) Provide necessary resources and inputs into the creation of the overall scope as well as supplier flight and category plans
6) Provide documented current state business processes
7) Provide timely resolution of any escalated issues
8) Provide/coordinate signoff on all deliverables
PHASE 2: FUNCTIONAL CONFIGURATION
1) Participation in configuration workshops by all required participants
2) Internal meetings to vet out and drive functional decisions that relate to the build and test of your solution
3) Provide required master data files in specified Ariba format
4) Load Master Data into APC test Site
5) Validate accuracy of master data in APC test Site
6) Remote Authentication configuration (optional)
7) Detailed requirements for all customizations
8) Customization unit testing
9) Configuration Phase sign-off
10) Approval of project exit criteria
PHASE 3: SOLUTION CONFIRMATION
1) Confirmation that all required attendees will participate per the recommended agenda
2) Logistics for meeting (room, internet access, etc.)
3) Content prepared for solution confirmation workshop
4) Facilitation of solution confirmation workshop
PHASE 4: TESTING
1) Integration Test and User Acceptance Test (“UAT”) Plans

prohibited.
6
2) Integration and UAT test use cases and scripts
3) Planning, scheduling and executing all Integration and UAT testing scenarios
4) Tracking of integration test and UAT execution
5) Test Phase sign-off
PHASE 5: GO LIVE
1) Cutover plan
2) Load Master Data in APC production Site
3) Validate catalogs and master data load into production Site
4) Integration of Customer procurement system with production Site
5) Execution of cutover plan
6) Production Site testing
7) Attend Customer Support transition meeting
PHASE 6: TRANSITION AND WRAP UP
1) Attend Customer Support transition meeting
2) Deployment exit C criteria sign-off
3) Log issues with Customer Support
IX. ASSUMPTIO NS
PROJECT ASSUMPTIONS
· The Deployment Services described in this Document are a standard offering and are included in the subscription to the Solution at
no additional cost, provided that the following parameters are met:
o Customer shall use best efforts to provide accurate and final configuration and customization decisions. Re-work related
to revisions of business process, configurations and/or customizations may result in deployment delays. These delays will
be addressed through a project change request.
o Customer has two (2) business days to provide response on deliverables submitted for its review. If detailed feedback is
not received within two (2) business days, the deliverable will be assumed completed.
o Customer acknowledges that changes in the assumptions in this Document may affect Ariba’s ability to provide the
Deployment Services.
GENERAL ASSUMPTIONS
· For clarity, any version of this or any other Deployment Description attached to the Order Form represents the version of such
Deployment Description that is current as of the Order Form effective date, and for purposes of the Consulting Service warranty

prohibited.
7
applicable to the Deployment Services purchased by Customer, the then-current version of the Deployment Description shall apply unless
explicitly stated otherwise in the Order Form.
· Prior to commencement of the project, Customer will have prepared and installed all prerequisite database software, personal computer
hardware and software, server hardware and software, communications equipment, operating systems and intranet proxy infrastructure.
· Customer will be responsible for establishing and maintaining Customer’s telecommunications links (if deemed necessary) as well as local
area networks, and the security of its network and related systems. Ariba assumes the hardware and third party software not licensed
from Ariba will function according to our expectations and will not present quality, capacity, timing, or performance problems that would
adversely impact the project's overall progress. Ariba will not be responsible for the performance, reliability, availability or security of the
Internet or any third party system or hardware which is not within the scope of the Ariba responsibilities or the control of Ariba.
· If Customer includes any Ariba Confidential Information and/or Cloud Materials in any Customer-created usage manuals, guides or
handbooks (collectively “Customer Materials”) such Customer Materials shall be restricted to Customer’s internal use only and subject to
the terms of the Agreement between Customer and Ariba (and/or its Affiliates as applicable) governing Customer’s access to and use of
the Cloud Services. Further, in addition to preserving and maintaining all copyright and trademark notices, the following designation
must be placed on every page of each such Customer Material: “This document contains proprietary and confidential information of
Ariba, Inc. and/or its Affiliates.
· Customer is responsible for all travel expenses related to the onsite Deployment Kick-Off meeting and any other portion of the
Deployment Services performed onsite at Customer location that are mutually agreed upon in advance. Travel expenses (if any) will be
billed as incurred.

prohibited.
8
Figure 1.The deployment services will be made available by Ariba to Customer during the following time frame:

The contents of this document are confidential and proprietary information of Ariba, Inc. Distribution without express permission from Ariba is prohibited.
9
X. BEST P RACTICE CE NTER SERVICES (OP TI ONAL)
Ariba’s Best Practice Center (“BPC”) provides a proactive and structured approach to driving adoption, return on investment, and use of Ariba
Cloud Services. The Best Practice Center gives users access to a combination of process expertise, proven configuration and template
techniques, and coached projects, all based on Ariba’s extensive experience with helping organizations get the most out of its commerce
programs. The Best Practice Center is offered as a fixed fee Consulting Service that can be purchased in blocks of twenty-five (25) hours.
Two (2) identified master users coordinate activities associated with the BPC Services and can request ad-hoc support through a designated
Ariba BPC email address. Only master users can access the BPC directly, but all registered users in an organization might benefit indirectly from
the services and information the master users disseminate. Master users may also designate that other users in their organization can work
with the BPC directly, but all requests must filter through one of the two master users.
BPC services include:
• Support for coaching and best practice sessions highlighting configuration, adoption, usage, and reporting using demonstrations
• Support and guidance on bridging multiple Ariba Cloud Services
• Support for reviews of new feature and functionality releases that might be relevant to an organization’s specific initiatives in order
to maximize the value of their Ariba Cloud Services
Examples of topics that can be covered include:
o Coaching on customized projects based on an organization’s unique needs

o Flexible coaching, guidance and workshops that build the skills of the users in the organization
o Configuration techniques and approaches
o Reporting guidance
Examples of activities out of scope for Ariba in this effort are:
o Configurations / customizations to the Ariba applications

o On-boarding of suppliers to the Ariba Network
o Development of any new internal or external collateral
o Development of specific reports required by Customer
Assumptions:
• Best Practice Center fees are based on the assumptions below, and in reliance on Customer’s fulfillment of its responsibilities as set
forth in this document.
· Ariba will assign to Customer an Ariba representative to serve as the BPC single point of contact after deployment of the Ariba Cloud
Services in Customer’s organization. This individual will be responsible managing the customer’s BPC services.
· Ariba shall deliver all BPC Services remotely.
· Customer may place a BPC activity request through the Customer’s Ariba Account Manager or the general BPC email.
· BPC hours of operation for service requests are 8:00 am to 6:00 pm Eastern Time (North America) and 8:00 am to 6:00 pm Central
European Time, Monday through Friday, excluding Ariba recognized holidays.
· The BPC is available in English only. Other languages may be available for additional fees.
· This document describes all service elements available as part of the BPC offering. Ariba shall provide selected service elements as
appropriate for Customer and the Cloud Services to which Customer subscribes; however, Ariba is not obligated to provide all
service elements.
· The BPC is an as-needed guidance service and is not designed to deliver procurement programs or event projects Ariba reserves the
right to decline any Customer request to the BPC for projects outside a standard offering, and/or to modify Customer’s access to the
BPC to prevent such requests.
· Ariba will monitor the number of BPC hours used by Customer and will notify a Customer if usage exceeds the maximum number of
hours designated above. Ariba reserves the right to decline a Customer’s request or modify access when usage exceeds, or when
requested usage would exceed, maximum permitted hours.
· Customer will make timely decisions throughout the execution of this engagement. Delays in decisions may impact Ariba resources,
deliverables, timelines and fees associated with the engagement. Customer will be responsible for any delays or additional costs
relating to any deficiencies in Customer’s performance of its obligations.
· For a period of one (1) year from the completion of the project, for any Ariba individual engaged on project, Customer shall not
solicit for employment or hire such individual, nor engage such individual as an independent contractor or other non-Ariba
consultant.

prohibited.
10
XI. BUSI NESS COMM ERC E ENA BLEM ENT SERVICES (OP TIONAL)
Ariba Business Commerce Enablement Services may be purchased separately.
o These services address the introduction of the new Ariba Solution into the Customer’s organization and address the management,
planning, business process change, organizational readiness and post deployment adoption and training necessary to fully realize
the Solution’s value proposition.
o These services are recommended to achieve the optimal value in using the Ariba Commerce Solutions.
XII. TRAINING SERVICES (OPTIONAL)
Training and Custom Training Programs may be purchased separately.
· Public and Private Training - Ariba courses are offered globally in both public and private on-site training options. Based on our standard
curriculum, each instructor-led class includes an Ariba Training manual, hands-on training, lecture, and labs.
· A current schedule of courses is available at https://training.sap.com.
· Customized Training – Ariba offers services to assist Customers with a more customized training program to fit their end user needs.
These customized trainings are targeted to end users, key users, and train the trainer programs. Deliverables can consist of courseware,
online or quick reference guides, and will vary based on need and audience.
XIII. NOTES
Items listed as “Optional” or “Add-On” are not included within the Services set forth herein, but rather may be added for an additional fee at
Ariba’s then current rate.

prohibited.
11

Ariba Procurement Content Deployment Description 14s Procurement

Uploaded by

Document Information

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

Ariba Procurement Content Deployment Description 14s Procurement

Uploaded by

Copyright:

Available Formats

Ariba Procurement Content TM

Revision Date: October 2016

Solution: Ariba Procurement ContentTM

© 2001 - 2016 Ariba, Inc. All Rights Reserved.

· “UI” – User Interface

· “CIF” – Catalog Interchange Format

· “cXML” – Commerce XML

· “EDI” – Electronic Data Interchange

· “Site” – the Solution website accessible by and configured for Customer

II. INTRODUC TION

II I. ARIBA DEPL OYM ENT SCOP E OF S ERVICES

PHASE 1: SOLUTION PLANNING

2) Establish project infrastructure

3) Confirm deployment scope and approach

4) Define solution set-up

3) Test Data Ready for loading into the system

PHASE 2: FUNCTIONAL CONFIGURATION

3) Assist Customer in learning how to configure approval rules

5) Build customizations per Order Form scope

6) Support resolution of issues with initial data loads

2) Functional Configuration document complete with Customer Site configuration details

PHASE 3: SOLUTION CONFIRMATION

2) Assist in identifying key decision and scenarios

4) Support core team’s facilitation of Solution Confirmation workshop

2) Log cases and enhancement requests with Ariba Support, as needed

3) Provide status updates on any Ariba product issues, as needed

2) Up-to-date issue log

3) Updated functional configuration document, if applicable

2) Assist with resolution of data load and production testing issues

© 2001 - 2016 Ariba, Inc. All Rights Reserved.

PHASE 6: TRANSITION AND WRAP UP

2) Conduct Customer Support transition meeting

IV. DEPLO YME NT S ERVIC ES TIMELIN E

V. SERVICE S PAR AMETERS

© 2001 - 2016 Ariba, Inc. All Rights Reserved.

VII. CUSTOM ER’S ROL ESAND RESPONSIBILITES

Table 1 Customer commits to provide the following resources:

Customer Role Customer Responsibilities

Project Sponsor · Assign a Project Manager

© 2001 - 2016 Ariba, Inc. All Rights Reserved.

· Manage communication plan development and deployment-wide communications to key stakeholders

VII I. CUSTOM ER AC TIVI TI ES A ND D ELIVERA BLES

© 2001 - 2016 Ariba, Inc. All Rights Reserved.

2) Provide Customer Site enablement details

3) Collect and understand procurement business processes to expedite decision making

PHASE 1: SOLUTION PLANNING

1) Deployment plan approved and communicated to team members

2) Provide and approve the communication plan

3) Arrange participation of all required resources per the deployment plan

4) Manage deployment timeline and schedule adherence

6) Provide documented current state business processes

7) Provide timely resolution of any escalated issues

8) Provide/coordinate signoff on all deliverables

PHASE 2: FUNCTIONAL CONFIGURATION

1) Participation in configuration workshops by all required participants

3) Provide required master data files in specified Ariba format

4) Load Master Data into APC test Site

5) Validate accuracy of master data in APC test Site

6) Remote Authentication configuration (optional)

7) Detailed requirements for all customizations

8) Customization unit testing

9) Configuration Phase sign-off

10) Approval of project exit criteria

PHASE 3: SOLUTION CONFIRMATION