Contract Delivery Glossary¶
Executive Summary¶
This glossary defines process-specific language for the Contract Delivery process wave.
Why This Exists¶
Contract Delivery involves multiple Domains, Practices, Digital Professionals, approvals, and events. Controlled language prevents ownership confusion and supports AIOS reasoning.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
A shared glossary improves process consistency, onboarding, audit review, and cross-Practice collaboration.
Terms¶
| Term | Definition |
|---|---|
| Contract Delivery | End-to-end process wave from contract award onboarding to contract closeout. |
| Contract Onboarding | Process of converting awarded contract context into a Contract-owned delivery workspace. |
| Contract Kickoff | Process of aligning stakeholders, cadence, responsibilities, and initial delivery expectations. |
| Milestone | Contract-owned delivery checkpoint with date, dependency, status, and expected outcome. |
| Deliverable | Contract-owned output, service, product, evidence, or obligation that must be delivered or accepted. |
| Supplier Coordination | Process of coordinating suppliers or providers needed for contract delivery. |
| Funding Readiness | Assessment of cash-flow exposure, funding need, and funding workflow support for delivery. |
| Contract Risk | Potential issue affecting delivery, milestone, supplier, funding, payment, or contractual outcome. |
| Variation | Proposed change to scope, timeline, price, deliverable, obligation, or delivery baseline. |
| Invoice Tracking | Monitoring of invoices, status, supporting evidence, and readiness for payment follow-up. |
| Payment Tracking | Monitoring of payment due dates, receipts, overdue status, and cash-flow implications. |
| Performance Review | Structured review of delivery, supplier, funding, milestone, payment, and KPI performance. |
| Closeout | Controlled closure of contract obligations, risks, invoices, payments, performance, and handoff to lessons learned. |
| Lessons Learned | Structured capture of delivery outcomes, issues, supplier lessons, funding lessons, and process improvements. |
| Delivery Workspace | Contract-owned operating workspace for managing delivery state. |
| Payment Delay | Payment not received by expected or agreed timing. |
| Closeout Blocker | Unresolved obligation, risk, invoice, payment, supplier issue, or approval preventing closeout. |
Cross-Reference Notes¶
- Contract Domain owns delivery state, milestones, deliverables, risks, variations, invoices, payments, performance, closeout, and lessons learned.
- Supplier Domain owns supplier relationship and supplier performance state.
- Marketplace Domain owns provider discovery and listing workflows.
- Funding Domain owns funding facts, assessments, applications, and readiness workflows.
- AIOS orchestrates process execution but does not own source facts.