Analytics Relationships

Why This Exists

This document explains how Analytics relates to other Algosure domains.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Relationship clarity allows Analytics to provide enterprise insight without duplicating or mutating source domain facts.

Relationship Diagram

flowchart TD
    Organization[Organization]
    Compliance[Compliance]
    Opportunity[Opportunity]
    Bid[Bid]
    Contract[Contract]
    Supplier[Supplier]
    Marketplace[Marketplace]
    Funding[Funding]
    Learning[Learning]
    Notification[Notification]
    Billing[Billing]
    Intelligence[Intelligence]
    Analytics[Analytics]
    Executive[Executive Office]

    Organization -->|profile context| Analytics
    Compliance -->|readiness, risk, expiry events| Analytics
    Opportunity -->|pipeline and matching events| Analytics
    Bid -->|tasks, approvals, outcomes| Analytics
    Contract -->|delivery, invoices, payments, milestones| Analytics
    Supplier -->|ratings, reviews, quote performance| Analytics
    Marketplace -->|listing and request metrics| Analytics
    Funding -->|applications, risk, repayment metrics| Analytics
    Learning -->|progress, maturity, certificates| Analytics
    Notification -->|delivery, read, escalation metrics| Analytics
    Billing -->|subscription and revenue references| Analytics
    Intelligence -->|explanations and recommendations| Analytics
    Analytics -->|dashboards and CEO briefings| Executive

Relationship Catalogue

Domain	Relationship	Data ownership rule
Organization	Provides context for segmentation and organization-level reporting.	Organization owns profile. Analytics owns reporting view.
Compliance	Provides readiness, verification, expiry, and risk events.	Compliance owns compliance facts. Analytics owns trends.
Opportunity	Provides tender discovery, matching, saved, and recommendation events.	Opportunity owns opportunity facts. Analytics owns pipeline views.
Bid	Provides bid tasks, approval, submission, outcome, and loss feedback events.	Bid owns bid facts. Analytics owns performance summaries.
Contract	Provides award, delivery, milestone, invoice, payment, and closeout events.	Contract owns contract facts. Analytics owns contract performance views.
Supplier	Provides supplier performance, quote, rating, and review events.	Supplier owns supplier facts. Analytics owns performance analysis.
Marketplace	Provides search, listing, request, and workflow usage events.	Marketplace owns marketplace workflows. Analytics owns usage views.
Funding	Provides funding application, readiness, cash-flow risk, and repayment events.	Funding owns funding facts. Analytics owns funding analytics.
Learning	Provides progress, maturity, recommendation, and certificate events.	Learning owns learning state. Analytics owns learning analytics.
Notification	Provides delivery, read, acknowledgement, and escalation metrics.	Notification owns delivery state. Analytics owns engagement analysis.
Billing	Provides subscription and payment references.	Billing owns billing facts. Analytics owns reporting summaries.
Intelligence	Provides explanations and recommendations.	Intelligence owns reasoning outputs. Analytics owns insight records.

Source Ownership Rule

Analytics may store denormalized reporting models and snapshots for performance and historical comparison. Those models must include lineage and must not become the mutation path for source domain records.