Capability Standard¶

Why This Exists¶

This standard defines what a Business Capability is and how every capability must be documented, owned, governed, and connected to the Algosure Blueprint.

Business Capabilities are the primary unit of design because they describe what the Digital Procurement Company must be able to do. They are more stable than implementations because business needs such as compliance assessment, bid response management, supplier evaluation, executive approval, and organizational memory persist even when software screens, APIs, workflow engines, and AI models change.

Owner¶

The owner is the Chief Product Officer and Enterprise Architect.

Each individual capability must have one owning Practice and one accountable Digital Professional.

Business Value¶

The standard creates business value by making capabilities comparable, governable, reusable, measurable, and implementable across product, architecture, workflows, data, AI, and customer experience.

Definition¶

A Business Capability is a stable business ability that the Algosure Digital Procurement Company must perform to create customer value.

A capability is not:

A feature.
A screen.
An API.
A workflow step.
A prompt.
A database table.
A vendor tool.

Those may implement or support a capability, but they are not the capability.

Why Capabilities Are More Stable Than Implementations¶

Capabilities describe enduring business abilities. Implementations describe current mechanisms.

Capability	Implementation examples that may change
Compliance eligibility assessment	Rule engine, AI reasoning flow, checklist UI, API, manual review workflow.
Bid response coordination	Kanban board, proposal studio, workflow queue, document generator, notification system.
Supplier profile management	Marketplace UI, supplier API, CRM sync, spreadsheet import, data service.

The capability remains stable while implementations evolve.

Required Capability Structure¶

Every capability must include:

Section	Required content
Capability ID	Controlled identifier using approved prefix.
Capability name	Business-readable name.
Definition	What the capability enables.
Owning Practice	The Practice accountable for the capability.
Accountable Digital Professional	The Digital Professional responsible for operating or coordinating it.
Business outcome	Customer value created.
SOPs	Procedures that govern execution.
Business Rules	Decision rules, thresholds, constraints, and policy logic.
APIs	System interfaces required or exposed.
Events	Business events triggered or consumed.
Data	Evidence, state, records, and memory used or created.
UX	Customer experience surface or headquarters area.
KPIs	Measures of performance and value.
Maturity	Current and target maturity levels.
Dependencies	Upstream and downstream dependencies.
Governance	Review cadence, approval status, and decision records.

Capability ID Format¶

Capability IDs use the format:

PREFIX-NNN

Examples:

PROC-001
COMP-004
BID-012
ORG-003

Approved Capability Prefixes¶

Prefix	Domain
`PROC`	Procurement Intelligence and procurement work orchestration.
`COMP`	Compliance.
`BID`	Bid Management.
`CONT`	Contract Delivery.
`MARK`	Supplier Marketplace.
`FUND`	Funding.
`LEARN`	Learning and Procurement Academy.
`ANLY`	Analytics and Business Intelligence.
`EXEC`	Executive Office and leadership workflow.
`ORG`	Organizational Memory and operating-system capabilities.
`ID`	Identity, access, tenant, and customer organizational identity capabilities.

Capability Mapping¶

flowchart LR
    Practice[Practice]
    Capability[Business Capability]
    Professional[Digital Professional]
    SOP[SOP]
    Rules[Business Rules]
    Workflow[Executable Workflow]
    Data[Data]
    KPI[KPI]
    Outcome[Business Outcome]

    Practice --> Capability
    Capability --> Professional
    Capability --> SOP
    Capability --> Rules
    SOP --> Workflow
    Rules --> Workflow
    Workflow --> Data
    Data --> KPI
    KPI --> Outcome

Standard Rule¶

No capability should be accepted into the catalogue unless it has a clear owner, business outcome, domain prefix, and relationship to the Algosure Blueprint.