Bid Relationships¶
Why This Exists¶
This document explains how Bid relates to Opportunity, Organization, Compliance, Intelligence, Contract, Notification, and Analytics.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Clear relationships allow bid preparation to use source facts without taking ownership of those facts.
Relationship Diagram¶
flowchart TD
Opportunity[Opportunity]
Bid[Bid]
Organization[Organization]
Compliance[Compliance]
Intelligence[Intelligence]
Contract[Contract]
Notification[Notification]
Analytics[Analytics]
Opportunity --> Bid
Organization --> Bid
Compliance --> Bid
Intelligence --> Bid
Bid --> Contract
Bid --> Notification
Bid --> Analytics
Relationship Map¶
| Domain | Relationship | Ownership boundary |
|---|---|---|
| Opportunity | Provides tender opportunity context and pursue decision. | Opportunity owns tender records and recommendations. |
| Organization | Supplies profile, capabilities, services, products, experience, people, resources. | Organization owns company facts. |
| Compliance | Supplies readiness, evidence, expiry, and compliance status. | Compliance owns compliance facts. |
| Intelligence | Generates drafts, summaries, task suggestions, and recommendations. | Intelligence owns reasoning sessions; Bid owns accepted workspace state. |
| Contract | Receives award handoff only. | Contract owns awarded delivery and obligations. |
| Notification | Sends task, approval, deadline, and submission alerts. | Notification owns delivery records. |
| Analytics | Consumes bid events and outcomes. | Analytics owns projections and dashboards. |
Ownership Rule¶
Bid owns bid preparation state. It references upstream domain facts and records accepted artefacts into the workspace.