IT Operations Starter

Entity summary

Name	data_object	Description
Asset Contracts	asset_contracts	Lease, maintenance, support, or warranty contracts governing an asset or pool of assets, indexed on the asset side.
Hardware Assets	hardware_assets	Physical IT assets such as laptops, servers, network gear, and peripherals, with serial number, asset tag, current user or location, and lifecycle state.
Incidents	service_incidents	Unplanned service interruptions or quality reductions, with severity, priority, category, assignee, and affected components.
SaaS Applications	saas_applications	SaaS applications in the company portfolio, with vendor, category, criticality, owner, and whether each is sanctioned or shadow IT.
SaaS Subscriptions	saas_subscriptions	Contractual subscriptions for SaaS apps: plan tier, seat count, recurring cost, billing cadence, renewal date, and owner.
Service Requests	service_requests	Planned, catalog-driven requests for access, hardware, software, or information, distinct from reactive incidents.
Software Licenses	software_licenses	License entitlements granting the right to use a software title, with vendor, purchased count, license model, term, and renewal date.
Users	users	Platform users referenced as assignees, authors, approvers, and creators across records.

flowchart TD
  classDef embedded_master fill:#fff4cc,stroke:#c79100,color:#5b4500;
  classDef consumer fill:#e8def8,stroke:#7b1fa2,color:#3a155d;
  asset_contracts["Asset Contracts"]
  saas_subscriptions["SaaS Subscriptions"]
  service_incidents["Incidents"]
  service_requests["Service Requests"]
  hardware_assets["Hardware Assets"]
  saas_applications["SaaS Applications"]
  software_licenses["Software Licenses"]
  users["Users"]
  users -->|"assigned hardware"| hardware_assets
  users -->|"custodian of assets"| hardware_assets
  asset_contracts -->|"covers"| saas_applications
  users -->|"owned contracts"| asset_contracts
  users -->|"owned licenses"| software_licenses
  users -->|"requests"| service_requests
  users -->|"fulfills"| service_requests
  service_requests -->|"routes_to"| service_incidents
  service_requests -->|"triggers"| service_incidents
  users -->|"assigned incidents"| service_incidents
  users -->|"reported incidents"| service_incidents
  users -->|"assigned requests"| service_requests
  users -->|"submitted requests"| service_requests
  saas_applications -->|"has"| saas_subscriptions
  users -->|"owns"| saas_applications
  users -->|"manages"| saas_subscriptions
  saas_applications -->|"raises_incident"| service_incidents
  class asset_contracts embedded_master;
  class saas_subscriptions embedded_master;
  class service_incidents embedded_master;
  class service_requests embedded_master;
  class hardware_assets embedded_master;
  class saas_applications embedded_master;
  class software_licenses embedded_master;
  class users consumer;
  style service_incidents stroke-dasharray:5 5;
  style service_requests stroke-dasharray:5 5;
  style hardware_assets stroke-dasharray:5 5;
  style saas_applications stroke-dasharray:5 5;
  style software_licenses stroke-dasharray:5 5;

Additional Requirements Specification

Cost fields on the embedded shells. For the standalone renewal-and-cost view to resolve, two embedded masters each need a flat cost figure plus a currency code:

• asset_contracts: a flat renewal_cost (or annual_value) numeric field.
• saas_subscriptions: a flat annual_spend (or MRR/ARR) numeric field.

Coexistence: these flat fields are a standalone-only denormalization. They are not needed when the full asset-management and SaaS-management modules are already installed (those carry cost on their own spend entities); when such a full module is added later, the flat field must be deduplicated and reconciled against the canonical source so cost is not double-counted.