Organization Business Objects¶
Why This Exists¶
This document defines the main business objects owned or referenced by the Organization Domain.
Business objects are the language Algosure uses to describe the customer's business. They must be stable, business-readable, and aligned with Domain-Driven Design.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
The Organization Domain owns the canonical definitions in this document.
Business Value¶
Clear business objects allow Algosure to build compliance, opportunity matching, proposal generation, supplier recommendations, funding support, learning, analytics, and AI reasoning on a reliable business foundation.
Business Object Catalogue¶
| Business object | Purpose | Ownership | Lifecycle relevance | Relationship to procurement |
|---|---|---|---|---|
| Organization | Root customer business entity. | Organization Domain. | Exists from registration through archive or retention. | Defines the party participating in procurement work. |
| Organization Profile | Descriptive, legal, operational, and market-facing profile. | Organization Domain. | Created after registration and improved continuously. | Supplies profile evidence for proposals, compliance, and matching. |
| Organization Owner | Business owner or primary accountable party for the organization. | Organization Domain, referenced by Identity. | Required for activation and governance. | Defines accountable customer leadership. |
| Organization User | User associated with the organization. | Organization Domain for organization association; Identity owns credentials. | Added, activated, suspended, removed. | Supports collaboration, approvals, and learning. |
| Director | Legal or governance director. | Organization Domain. | Added, updated, removed, verified. | Used in compliance checks, declarations, and company credibility. |
| Contact | Business contact for procurement operations. | Organization Domain. | Added and maintained across lifecycle. | Used for proposals, contracts, notifications, and supplier interactions. |
| Address | Physical, postal, or operational location. | Organization Domain. | Maintained as organization footprint changes. | Supports geographic eligibility and service coverage. |
| Branch | Operating branch or location unit. | Organization Domain. | Added as organization structure expands. | Supports regional capability and delivery evidence. |
| Department | Internal department or function. | Organization Domain. | Added for larger organizations. | Supports role-based work and internal responsibility. |
| Employee | Employee or staff member relevant to procurement capability. | Organization Domain, may reference Identity if platform user. | Added and maintained as capability evidence. | Supports capacity, capability, and proposal evidence. |
| Service | Service offered by the organization. | Organization Domain. | Added, updated, retired. | Used for opportunity matching and proposal content. |
| Product | Product offered by the organization. | Organization Domain. | Added, updated, retired. | Used for supplier marketplace and opportunity matching. |
| Capability | Business ability the organization can perform. | Organization Domain for organization capability evidence; Business Capability Catalogue owns architecture standard. | Added, verified, improved, retired. | Used for matching, compliance, proposals, and AI reasoning. |
| Equipment | Equipment owned or available to the organization. | Organization Domain. | Registered, verified, retired. | Supports capability evidence and contract readiness. |
| Fleet Asset | Vehicle or fleet asset relevant to operations. | Organization Domain. | Registered, maintained, retired. | Supports delivery capacity and eligibility. |
| Past Project | Completed work used as experience evidence. | Organization Domain. | Added, verified, referenced, archived. | Supports bid credibility and compliance evidence. |
| Client Reference | Reference from a past or current client. | Organization Domain. | Added, verified, refreshed. | Supports proposal quality and trust. |
| Certification | Formal certification held by the organization. | Organization Domain. | Added, verified, expired, renewed. | Supports eligibility and compliance. |
| Licence | Formal licence or permit held by the organization. | Organization Domain. | Added, verified, expired, renewed. | Supports regulated procurement participation. |
| Financial Profile | Financial indicators and preferences relevant to procurement. | Organization Domain, Funding may reference. | Created and updated as customer matures. | Supports funding fit and tender readiness. |
| Procurement Preference | Customer goals, sectors, regions, opportunity types, and exclusions. | Organization Domain. | Updated continuously. | Drives opportunity matching and AI recommendations. |
| Organization Intelligence Graph | Connected graph of organization facts and relationships. | Organization Domain. | Enriched over time. | Enables AI reasoning, matching, and memory. |
| Organizational Memory | Durable organization-specific knowledge boundary. | Organization Domain. | Grows continuously. | Powers learning and contextual AI procurement support. |
Object Ownership Rule¶
Other domains may reference these objects by ID or read model. They must not redefine or own the canonical Organization business objects.
Procurement Relevance¶
Every object should either:
- Establish customer identity.
- Provide evidence of capability.
- Support procurement eligibility.
- Improve proposal quality.
- Support contract delivery.
- Improve matching and recommendations.
- Strengthen Organizational Memory.
Objects that do none of these require governance review before inclusion.