Steering a pharmaceutical company’s cloud procurement integration.

Client context

The business context.

A pharmaceutical company was replacing its procurement application with a cloud solution. The change covered sourcing, contracts, supplier information and ordering, alongside electronic purchase-order and invoice integration.

Delivery was phased. The program had to coordinate the first set of modules while developing the integration and data requirements for subsequent work. Clear scope boundaries were needed to manage these parallel activities.

The work

How the engagement was delivered.

• Steer phased delivery and scope decisions

  Coordinated the initial procurement-module integration and the requirements work for the next phase. Kept the distinction between implemented scope and subsequent requirements clear across business and delivery teams.

• Resolve integration and data dependencies

  Steered the purchase-order and invoice integration work around Ariba Network. Connected interface requirements with data-management decisions and the delivery teams responsible for the surrounding systems.

What changed

Successful go-live of the implemented procurement modules.

The implemented modules went live successfully. The program also established requirements and analysis for subsequent integration and data work. Reduced maintenance and procurement costs were objectives of the cloud transition, rather than quantified outcomes of this case.