Compliance Business Objects¶
Why This Exists¶
This document defines the business objects owned or referenced by the Compliance Domain.
These objects form the language used to describe procurement readiness, compliance evidence, verification, expiry, readiness scoring, and compliance risk.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Compliance owns the canonical definitions in this document.
Business Value¶
Clear compliance objects allow Algosure to assess readiness, track document validity, reduce disqualification risk, and support tender-specific compliance work with traceable evidence.
Business Object Catalogue¶
| Business object | Purpose | Ownership | Procurement relevance |
|---|---|---|---|
| Compliance Profile | Organization-specific compliance state. | Compliance Domain. | Provides readiness context for opportunities and proposals. |
| Compliance Requirement | Requirement that must be satisfied generally or for a tender. | Compliance Domain. | Defines what evidence or status is required. |
| Tender Compliance Requirement | Requirement extracted or defined for a specific tender. | Compliance Domain, references Opportunity. | Drives tender-specific readiness. |
| Compliance Document | Document used as compliance evidence. | Compliance Domain. | Supports eligibility, submission, and verification. |
| Compliance Evidence | Evidence item satisfying a requirement. | Compliance Domain. | Links documents and facts to requirements. |
| Verification Record | Record of verification process and outcome. | Compliance Domain. | Establishes trusted or rejected status. |
| Expiry Monitor | Monitoring object for expiry dates and renewal windows. | Compliance Domain. | Prevents expired evidence in submissions. |
| Procurement Readiness Score | Score representing readiness for procurement participation. | Compliance Domain. | Summarizes readiness and gaps. |
| Compliance Risk | Risk caused by missing, expired, weak, conflicting, or unverified evidence. | Compliance Domain. | Supports prioritization and executive decisions. |
| Compliance Gap | Missing or insufficient requirement coverage. | Compliance Domain. | Drives corrective tasks. |
| Compliance Suggestion | AI or human suggestion to improve compliance state. | Compliance owns acceptance; Intelligence may propose. | Improves readiness without bypassing ownership. |
| SARS Compliance Context | Tax compliance-related evidence and status. | Compliance Domain, references Organization tax data. | Public procurement eligibility. |
| CIPC Evidence | Company registration and director-related evidence. | Compliance Domain for evidence state; Organization owns company identity. | Legal status and company proof. |
| CSD Status | Central Supplier Database-related status or evidence. | Compliance Domain. | Supplier eligibility in public procurement. |
| CIDB Evidence | Construction grading or related evidence. | Compliance Domain. | Construction tender eligibility. |
| COIDA Evidence | Compensation-related evidence where required. | Compliance Domain. | Labour and safety-related compliance. |
| B-BBEE Evidence | B-BBEE certificate or affidavit and level. | Compliance Domain. | Preferential procurement scoring and eligibility. |
Ownership Rule¶
Organization owns company identity. Compliance owns compliance state, evidence status, expiry, verification, readiness score, and compliance risk.
Intelligence may recommend changes, but approved Compliance commands are required before compliance facts change.