A procurement platform answers questions about procurement. The questions the business actually asks span everything else too.
A renewable energy producer in the Philippines runs procurement on Coupa with SAP as its finance system, supported by Valtatech under application managed services.
A procurement platform reports well on procurement. It reports badly on anything needing procurement data to sit alongside operational, financial and asset data — which is most of what an energy producer actually asks. Capital projects, plant maintenance and outage planning all involve spend, and none of them are answered from inside a procurement tool.
The data existed. It was locked in an application built to transact rather than to analyse.
Valtatech delivered a data warehouse integration, extracting Coupa objects into the producer's warehouse where they can be joined to the rest of the business.
Scope was defined object by object in an integration requirements document rather than as a blanket instruction to sync everything. Approvals, contracts, invoices and integration history were among the objects brought across, each with its own mapping.
Delivery ran in sprints, each with its own signed-off go-live rather than one date at the end. A tranche of objects was in production and being queried while the next was still being built — which is what stops a data project from spending eighteen months producing nothing anyone can use.
Valtatech is software vendor agnostic. The technology named here is what this client selected; we start from requirements, operating model and existing systems. See how we approach integration →
Integration work is usually described in terms of systems connected. The more useful measure is which questions become answerable that were not before.
Talk to us about what this would look like in your business.
Start a conversation