SIGNET: procurement as the first proving ground

Why start with procurement?

Procurement is not one form or one button labelled ‘buy’. It often involves finding potential suppliers, qualifying them, describing a requirement, comparing proposals, negotiating terms, authorising commitments, receiving goods or services, and confirming payment information. Each stage may involve a different team or system.

When those systems lack a common language, work gets repeated. A supplier that has already provided a qualification may need to supply it again. A buyer’s requirement can lose meaning as it moves between applications. An agreement may be disconnected from the order that follows it. A dispute may become harder to resolve because each participant holds a different version of the story.

The Free Commerce manifesto therefore begins with procurement, where fragmentation is hard to ignore and meaningful progress can be demonstrated.

What a shared vocabulary changes

Imagine a buyer needs maintenance services for several offices. It creates a requirement describing the work, the places involved, the timetable and conditions for participation. Several suppliers use different commercial systems, yet can receive and interpret the core request consistently. They return proposals, evidence of qualifications and commercial terms. The buyer evaluates these under its own policies and selects a supplier.

If systems can preserve agreed meaning across those exchanges, the participants spend less effort retyping and translating data. Later interactions – orders, delivery evidence or invoicing – can refer back to earlier commitments without requiring one vendor to control the whole journey.

That is an illustration of what standardisation can enable, not a statement that every step is already supported in a released SIGNET implementation. Check the current specification for actual supported structures and maturity before presenting diagrams as executable interoperability flows.

SIGNET and Concert Foundation

Concert Foundation is the steward of the Free Commerce mission and the open standards it develops. SIGNET is its starting point for governed, intelligent, interoperable procurement. A procurement product, buyer system, supplier platform or agent may implement the standard, but no commercial operator should have a preferential right to do so.

A standard is not itself an operating marketplace. It does not host every participant’s data, approve every supplier, enforce every contract or take responsibility for every transaction. Those responsibilities remain with the relevant parties and implementing systems, within the applicable legal and governance arrangements.

Walk through a sample journey

This is a conceptual teaching sequence, not a normative SIGNET API, schema or a claim of complete lifecycle implementation. The current technical documentation has the precise messages and supported features.

Where intelligent agents fit

Agents could help search, compare or validate information, but should only act within their mandates. A supplier’s agent might answer a qualification request with authorised evidence; a buyer’s agent might rank proposals against stated criteria. A person or authorised process must remain accountable for decisions requiring approval. The standard’s role is to support meaningful governed exchange between independent participants – not to declare one agent provider the winner.

What would count as proof?

An attractive demo is helpful. Stronger evidence would show two independently built systems exchanging information on published terms, preserving meaning and respecting each party’s authority. Confidence grows further when different implementers can repeat the result using public documentation and reproducible tests. Any public claim about deployment, certification or governance should refer to verifiable evidence, not aspiration.

Try it: trace a requirement

Write a maintenance requirement in five fields: buyer need, service scope, timing, supplier evidence and approval constraint. Follow it through qualification, offer, agreement and invoice. At each handoff, circle the data that must keep its meaning. Underline the decisions that must remain local to the buyer or supplier. Note which parts would benefit from shared vocabulary and which are matters of business policy.

Key terms

• Procurement: Organisational process of acquiring goods and services.
• Common vocabulary: Agreed terms and data structures that different participants interpret consistently.
• Governance: Rules, responsibilities and oversight controlling legitimate decisions and changes.
• Conformance: Evidence that an implementation meets specified requirements, not a label to claim without testing.
• Reference implementation: Software demonstrating a possible application of a standard; it need not be the only implementation.

The full course in one paragraph

Commerce should be free to connect, compete, choose and leave. Open standards enable independent systems to cooperate without surrendering their differences. Portable trust lets organisations carry earned evidence with them. Accountable agents can act across boundaries only within delegated authority. SIGNET begins making these ideas practical in procurement – and its success should be judged by genuinely independent participation and demonstrable interoperability.

What next?

Read the full Free Commerce manifesto; explore the current SIGNET specification; examine the public governance record; and contribute an example, question or independent implementation through the project’s established participation channel. No purchase, subscription or special permission should be required to begin learning.