MSC_eProcurement_Onboarding_Process.pdf

Version 1.0 01.16.23

E-PROCUREMENT ONBOARDING PROCESS

This document sets the general expectations and timeline of the e-procurement integration process. The requirements set out in this document are what is needed for MSC to be able to set-up a system-to-system integration. Without you, the customer’s cooperation, and all the below information, a timely integration will not be possible.

Please be advised, that integration timelines may vary depending on customization needed, testing qualifications, and scope of project.

Minimum Necessary Customer Expectations for Successful Integration:

• Customers are expected to have a dedicated person AND actively participate in a mandatory discovery process through a scheduled teleconference.

• Once technical requirements for all the below segments have been clarified, customers must agree on formalized testing scenarios that will be qualified during the testing and implementation phase of the project. If testing scenarios are not specified, B2B Tech Team will utilize standard scenarios depending on scope of project.

• Customer and MSC will align on tentative date when B2B Tech Team resource will be assigned, and when testing will begin. The B2B Tech Team resource will be responsible for testing document transmission, and catalog capabilities with customer.

• When the B2B Tech Team resources make initial contact, the customer is expected to within 1-2 business days begin testing and have testing/QA ready and available after B2B Tech Team begins testing.

• Customers are expected to complete all formalized testing scenarios, with the agreed upon standards, which were agreed upon during the discovery call. MSC Integration Project Manager will gather all technical details and coordinate the initial discovery call.

• Once formalized testing is completed to both parties’ satisfaction, MSC and customer will agree on production go-live date.

• Recommend that once both parties have moved to production an end-to-end production order be submitted to ensure the implementation has no disparities.

o This is highly suggested not required.

o Any orders submitted in production during this phase can be monitored for cancellation and are for the purpose of ensuring integration readiness.

If you as the customer are not able to meet all the expectations, MSC will work with you to ensure your project is completed, but timelines might be extended, or the project might be put on hold at times if resources are not available to assist in the integration from your side.

MSC Integration/Onboarding Process:

The timeframe below is contingent on if the integration is “standard” or “non-standard” and if you, the MSC Customer meets the expectations laid out above. The criteria of what is “standard” vs. “non-standard” will be discussed on the Discovery Call.

1. Discovery Call Objectives (MSC Integration Project Manager will attempt to coordinate discovery within 1 week of project submission by MSC Sales Team)

• Discuss targeted Go-Live

• MSC Integration Project Manager and customer will:

o Review the platform and solutions including how to shop (i.e., PunchOut/Hosted Catalog) and what transaction documents are needed (PO, Order Confirmation, ASN, Invoice, etc.).

o Review specific rules i.e., tolerances, tax, freight, eVending, etc.

o Explore other requirements needed in the transaction documents that are not standard that need to be considered.

o Discuss formalize testing scenarios

• All customer properties, segments, and divisions that will utilize integration for purchasing must be discussed during onboarding. It is expected that location address, and codes will be provided during this time.

• Customer should provide all technical, financial, and business contacts as applicable.

• If the ERP/platform requires a customer-initiated relationship request, customer to send prior to the start of testing and implementation.

2. Confirmation of Integration Expectations and Details (within 3-4 days after Discovery Call)

• Summary of discovery call sent to all parties by MSC Integration Project Manager o Start date (with time estimate to complete) o Tentative go-live date o High-level summary of all points discussed during call

• Customer should review and approve scope of project as summarized by MSC Integration Project Manager and send back confirmation of their approval.

3. Active Project (6-12 weeks dependent on agreed upon scope)

• B2B Tech Team resource will be assigned and send testing kickoff email.

• Customer will establish catalog if applicable and ensure that QA environment is setup for testing.

• Customer creates test order based on testing scenarios agreed upon.

• B2B Tech Team provides return documents for all test orders sent by customer as applicable.

• Once UAT testing is complete, both parties must confirm that integration activities have been successful, and all parties are ready to move to production.

o Both parties agree upon a production go live date.

o Reconfirm cutover actions if this is a migration from one ERP to another

MSC focuses on the Go Live dates of all our customers, and we are committed to helping everyone achieve specific milestones. If at any time there is a breakdown in communication, a project might be put on hold as we move unto other customers projects based on their Go Live date. When all parties are ready to engage again, any projects on hold will be reprioritized and put back into the queue for resource assignment. New dates will be discussed and approved prior to project moving back to active status.

4. Go-Live (1 day Post UAT Approval)

• B2B Tech Team and customer move integration to production.

• It is highly recommended that a production, end-to-end smoke test be conducted during this time, however, this is not required.

• MSC Integration Project Manager will monitor integration for a minimum of two weeks after live order has been submitted.

• MSC Integration Project Manager and B2B Tech Team will drive fixes expediently as necessary.

We strongly suggest first live order is submitted withing a month of agreed go live date. This ensures expedient service is provided if integration obstacles occur.