Notification Business Objects

Why This Exists

This document defines the core business objects owned or referenced by the Notification Domain.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Clear business objects make notification workflows stable across channels, domains, and future integrations.

Business Object Catalogue

Object	Purpose	Ownership	Procurement relevance
Notification Request	A request to notify one or more recipients about an event or action.	Notification	Converts domain signals into communication workflow.
Notification	The communication item created from a request.	Notification	Represents the message to be delivered and tracked.
Recipient	The user, team, role, or organization contact intended to receive a notification.	Notification references Identity or Organization.	Ensures the right person is informed.
Notification Channel	A route for delivery such as in-app, push, email, SMS, WhatsApp, or future calendar integration.	Notification	Enables channel-specific delivery control.
Notification Preference	Recipient or organization preference for type, channel, timing, and frequency.	Notification	Reduces noise while preserving critical alerts.
Notification Template	Approved message structure for a notification type and channel.	Notification	Ensures consistent, professional communication.
Reminder	A scheduled notification linked to a future action or deadline.	Notification	Prevents missed tender, bid, compliance, contract, payment, or learning actions.
Escalation	A policy-driven follow-up when a critical notification is not acted on.	Notification	Protects high-risk procurement actions.
Delivery Attempt	A single attempt to send a notification on a channel.	Notification	Supports delivery tracking and retry logic.
Delivery Status	Current delivery state for a notification.	Notification	Shows whether communication was sent, failed, delivered, or blocked.
Read Status	Whether a recipient has seen or acknowledged a notification.	Notification	Supports accountability and escalation.
Notification Priority	Urgency and importance classification.	Notification	Helps route critical messages before routine updates.
Notification Schedule	Timing plan for immediate, delayed, repeated, or deadline-relative delivery.	Notification	Supports reminders and quiet hours.
Communication History	Auditable record of notifications sent, received, read, failed, or escalated.	Notification	Provides traceability for procurement operations.

Notification Type Catalogue

Type	Typical source domain	Example
Tender Deadline	Opportunity	Tender closes in 48 hours.
Expiring Document	Compliance	Tax clearance expires soon.
Recommended Tender	Opportunity	New tender matches services and regions.
Compliance Issue	Compliance	Required document missing for target tender.
Team Approval	Bid	Bid submission approval required.
Award Notification	Bid or Contract	Tender award captured or contract created.
Payment Reminder	Contract or Billing	Invoice or subscription payment due.
Briefing Reminder	Opportunity	Compulsory briefing starts tomorrow.
Bid Task Reminder	Bid	Pricing workbook due today.
Contract Milestone Reminder	Contract	Delivery milestone due next week.
Learning Reminder	Learning	Recommended lesson not completed.
Subscription Payment Notification	Billing	Subscription renewal failed or is due.

Object Relationship

flowchart TD
    Request[Notification Request]
    Notification[Notification]
    Template[Template]
    Preference[Preference]
    Schedule[Schedule]
    Channel[Channel]
    Attempt[Delivery Attempt]
    Read[Read Status]
    Escalation[Escalation]
    History[Communication History]

    Request --> Notification
    Notification --> Template
    Notification --> Preference
    Notification --> Schedule
    Schedule --> Channel
    Channel --> Attempt
    Attempt --> History
    Notification --> Read
    Read --> Escalation
    Escalation --> History