Skip to content

Sub-Domain Blueprint: Operations Services

Domain: Operations (maintenance, security, personnel, services) Logical Sub-Domain: Services (Support Functions) Physical Packages: @sd/mod-operations/procurement, @sd/mod-operations/hospitality, @sd/mod-operations/telemetry Related Documents: Data Definition Context: This document defines the Supply Chain, Guest Experience, and IoT Data layers. Status: Stable (v2.5)

1. Mandate

This Sub-Domain groups the supporting pillars of Operations: 1. Procurement: Managing Vendors, Contracts, and Spending (PO/RFPs). 2. Hospitality: Managing Amenities and Concierge Requests. 3. Telemetry: Ingesting real-time sensor data from the physical plant.

2. Capabilities

Capability Description Component
Vendor Management Tracking Compliance (Insurance) and Performance Ratings. ProcurementService.registerVendor
Purchasing (P2P) Purchase Order lifecycle (Draft -> Approved -> Fulfilled). createPurchaseOrder
RFP Governance Linking High-Value Bids to Board Voting Proposals. selectWinningBid
Amenity Booking Reserving shared spaces (Tennis, Spa). AmenityBooking
IoT Ingestion Normalizing sensor streams (temperature, flow). TelemetryReading

3. Process Models

A. The Purchase Cycle (RFP to PO)

Happy Path: Gym Renovation.

sequenceDiagram
    participant Admin
    participant Service as ProcurementService
    participant Board as Governance
    participant Vendor

    Admin->>Service: createRFP("Gym Reno", budget=$50k)
    Vendor->>Service: submitBid($45k)

    Admin->>Service: selectWinningBid(vendorIs="BestBuild")
    Service->>Board: createProposal("Approve Gym Reno")

    Note over Board: Vote Passed

    Admin->>Service: createPurchaseOrder(vendor="BestBuild", amount=$45k)
    Service-->>Vendor: PO Issued (Net30)

B. Guest Request

Happy Path: Towels needed.

sequenceDiagram
    participant Guest
    participant Service as HospitalityService
    participant Staff

    Guest->>Service: createRequest(type="housekeeping", item="Towels")
    Service->>Staff: dispatch(request)
    Staff->>Service: resolve()

4. State Machines

Purchase Order Status

stateDiagram-v2
    [*] --> Draft
    Draft --> Submitted: Review
    Submitted --> Approved: Budget Check
    Approved --> Fulfilled: Goods Recv
    Fulfilled --> [*]: Billed to Finance

5. Interface Definitions

ProcurementService

  • createPurchaseOrder(po): Promise<PO>
  • submitBid(bid): Promise<Bid>
  • checkVendorCompliance(id): Promise<bool>

HospitalityService

  • bookAmenity(booking): Promise<Booking>

6. Changelog

Date Author Description Reference
2026-01-24 Antigravity Initial creation Implementation Plan