In our last few articles, we’ve been writing a lot about the need for center-orchestrated Procurement due to the current global trade environment. As a result of this, a number of policies, processes, and platforms will need to change for a modern global Procurement organization in order for it to be efficient, effective, and even endorsed.

While the core platform requirements don’t change, the unique requirements for the platform are different. When you only have to serve yourself, whatever works for you is good enough. But when you have to serve a diverse base of global users, who have to adhere to a diverse spectrum of global requirement, what works for you is sometimes completely irrelevant.

Then there’s also the fact that center-orchestrated procurement, by definition, requires:

• orchestration — if the platform can’t orchestrate data streams, workflows, and users, it’s not sufficient
• common data model — every platform must support the common data model in the central data store to allow for easy data integration and cross organization analytics
• centralized supplier onboarding — there needs to be a central supplier master and management platform
• “excellence” — if the platform can’t encode and distribute best practices across the global organization, it’s not the right platform
• standards — efficiency comes from standardization to the extent possible, if the platform doesn’t support that, it’s no good
• supply chain awareness — it needs to integrate with the logistics, supply chain, and PLM systems in order to allow for organizational aware sourcing and procurement
• knowledge management — it should capture all of the knowledge needed to run the orchestrated workflows effectively
• global risk management — all of the risks must be identified, tracked, mitigated and managed centrally

Breaking this down, you can see that before any sourcing or procurement platform, it needs to support:

• real orchestration support — it needs a fully defined API that allows all data to be pushed in or pulled out, functions to be executed, and workflows to be configured; it can be a standard REST API or MCP, but it has to be orcehstratable
• centralized common data model and data federation platform — that can support all sourcing and procurement data collected and generated by all systems with the ability to define the external system mappings as appropriate; this doesn’t mean the organization dumps everything into a lake / warehouse / lakehouse, but builds the foundation for federated data analysis as the best analytics platforms can pull in the data needed on demand when they have a common data model to work off of (pre-defined mappings from the global organizational systems, and a designation as to which system is “master” for any specific piece of data — which means the data model specifies, for each datum, the master system)
• centralized supplier onboarding — the central supplier master should support global supplier onboarding; if it can’t be localized as needed (language, accessibility, etc.), then it needs to support fine-grained orchestration that will allow a local platform to mimic the global requirements and feed all of the data into the central system
• excellence — any platform used for centralized operations need to support the creation of specialized workflows for each region, location, and project; moreover, the specialized workflows need to inherit the global requirements while supporting the regional and local overrides with minimal effort; nothing should have to be defined twice and no unnecessary work duplicated
• standards — the platform needs to support multiple authentication, security, and privacy standards and implementations to meet global requirements; remember, different countries will require different security protocols, login protocols, privacy requirements, government platform integrations, etc. — the global platforms you select must support switching them in and out as needed by the locale
• supply chain awareness — the platform needs to understand your supply chain data model and be capable of integrating with your supply chain platforms to integrate the required data to make supply chain aware decisions
• knowledge management — the platforms must capture more than process, they must capture the decision making frameworks used to select and execute the processes and do the required analytics; for the categories, they must cover the strategy; for the suppliers, the soft evaluation criteria based on the objective and subjective rankings; for Procurement process selection — catalog vs. RFQ vs. tail-spend provider — the logic used; etc.
• global risk management — a solution for identifying, tracking, and monitoring changes in global risk criteria and alerts and pushing out relevant information to the appropriate regions and locations through the tools the end users actually use (using the built-in orchestration capabilities)

In other words, the platform has to be a lot more adaptive, layered, and customizable than most platforms in use today.