Opportunity Value Objects¶
Why This Exists¶
This document defines immutable and value-based concepts used by the Opportunity Domain.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Precise value objects improve tender matching, deadline tracking, qualification, recommendations, and risk analysis.
Value Object Catalogue¶
| Value object | Purpose | Validation rules |
|---|---|---|
| TenderOpportunityId | Identifies tender opportunity. | Required, unique, immutable. |
| TenderSourceType | Classifies source. | Controlled values public, private, partner, manual. |
| TenderReferenceNumber | External tender reference. | Preserve source format and source. |
| TenderCategory | Classifies tender. | Controlled taxonomy where available. |
| TenderRegion | Geographic area. | Must distinguish source region from inferred region. |
| TenderDeadlineType | Deadline category. | Submission, briefing, clarification, document purchase, other. |
| TenderDeadlineDate | Deadline date and time. | Must include timezone or source timezone context. |
| MatchScore | Relevance score. | Numeric range with factors and method. |
| QualificationStatus | Qualification outcome. | Qualified, not qualified, needs review, unknown. |
| RecommendationDecision | Bid/no-bid recommendation. | Bid, no-bid, watch, needs review. |
| WinProbabilityEstimate | Estimated probability of winning. | Numeric range with confidence and method. |
| TenderRiskLevel | Risk severity. | Low, medium, high, critical. |
| SavedOpportunityPriority | Customer priority. | Low, medium, high, strategic. |
| WatchlistCriteria | Saved monitoring criteria. | Must be explicit and explainable. |
Deadline Rule¶
Deadlines must preserve source context. If timezone is unknown, it must be marked as unknown instead of assumed.
Recommendation Rule¶
Recommendation decisions are decision-support records. They do not initiate proposal writing by themselves.