Capability
What the enterprise is able to do.
A companion proposition
When enterprise capabilities become increasingly invocable.
Enterprise as a Service is a proposition about access, not an assertion that an enterprise becomes a marketplace. When a business request can be matched to an approved capability, the path to an outcome can become more direct—provided its conditions remain visible and governable.
Business request“Resolve this credit exception.”
MatchAuthoriseCoordinate
Approved capabilityCredit exception handling
Reviewable outcomeDecision, action & record
Business intentApproved capabilityGoverned accessReviewable outcome
The proposition
Make the capability easier to reach.
Do not remove the conditions around it.
Enterprise as Software concerns how operational models become increasingly executable. Enterprise as a Service concerns how the capabilities within those models can be invoked in response to a real business need.
The distinction matters. A capability is not merely an endpoint. It carries a scope, an access path, policy constraints, responsibility, and a record of what happened.
Capability and access
Separate what an enterprise can do from how it is allowed to be used.
Service-oriented architecture provides a useful lineage: a service is a mechanism for accessing capability through a prescribed interface and specified policies. Enterprise as a Service extends that idea into an AI-native operating context.
Service boundary
The prescribed access path, interface, and scope.
Authority
Who or what may use it in the current conditions.
Evidence
What remains available after work is completed.
The governed access path
From a request to a reviewable enterprise outcome.
AI can make discovery and coordination more dynamic. It does not eliminate the need to establish authority, accountabilities, control boundaries, or retained evidence before consequential work is performed.
- 01Operating step
State the intent
A business request names the outcome that is needed.
- 02Operating step
Match the capability
A suitable enterprise capability is identified in context.
- 03Authorisation gate
Set the conditions
Policy, authority, risk, and human responsibility determine whether and how it may be used.
- 04Operating step
Coordinate the work
People, AI, decisions, and systems participate in the approved operating path.
- 05Evidence state
Retain the context
The request, conditions, actions, and outcome remain available for review.
Provable. Intelligent. Executable.PIE’s role
PIE coordinates the conditions that make enterprise capability invocation governable.
PIE does not claim to turn every enterprise function into an instant service. It provides the operating environment for connecting intent, capabilities, intelligent reasoning, decisions, people, systems, authority, and evidence when an approved path is designed.
IntentAuthorityExecutionEvidence
Explore the PIE platform Appropriate boundary
A useful proposition is not a universal claim.
Enterprise as a Service is a way to reason about more direct, governed access to selected capabilities. It is not a claim that every process should be automated, every decision should be delegated, or every capability should be exposed.
Human responsibility, policy, risk, and organisational context remain part of the operating model.
References
OASIS SOA Reference Model
Needs, capabilities, prescribed interfaces, constraints, and policies provide an architecture lineage for the access proposition.
Read sourceNIST AI RMF Core
Govern, map, measure, and manage are used as context for treating governance as cross-cutting throughout an AI lifecycle.
Read sourceThe TOGAF® Standard
An established enterprise architecture methodology and framework of The Open Group; referenced without affiliation or endorsement.
Read source