ITSMJune 27, 2026
Service Request Fulfillment
Service Request Fulfillment gives your workforce a single front door for the everyday things they need from IT: access, equipment, software, and standard changes. Each request follows a defined path through submission, approval, and fulfillment so nothing stalls in someone's inbox. Approval routing and fulfillment tracking make the experience predictable for the requester and measurable for the team. Repeatable requests become catalog-driven, freeing agents to focus on the work that genuinely needs a human.
Use the Service Request Fulfillment semantic blueprint
/semantius-admin use the architect, analyst and modeler skills to update the semantius platform with the model specified in https://www.semantius.com/blueprints/itsm-service-request-semantic-blueprint.mdEntity summary
| Name | data_object | Description |
|---|---|---|
| Service Catalog Items | service_catalog_items |
Definitions of what can be requested: the request form, fulfillment workflow, approvals, service level, and charge-back rules. |
| Service Offerings | service_offerings |
Back-end service definitions covering commitments, supported configurations, and fulfillment, separate from their user-facing catalog items. |
| Service Requests | service_requests |
Planned, catalog-driven requests for access, hardware, software, or information, distinct from reactive incidents. |
| Configuration Items | configuration_items |
Canonical records of IT things under management: servers, containers, applications, services, network devices, databases, and cloud resources. |
| Locations | locations |
Physical or organizational locations referenced across the system, used to place and group other records. |
| Onboarding Tasks | onboarding_tasks |
Discrete to-do items within an onboarding journey, each with an assignee, due date, type, and completion state, some triggering handoffs to other systems. |
| Org Units | org_units |
Nodes in the organizational hierarchy such as divisions, departments, and teams, with manager, cost center alignment, geographic scope, and parent-child links. |
flowchart TD classDef master fill:#d4f4dd,stroke:#27ae60,color:#0b3d20; classDef embedded_master fill:#fff4cc,stroke:#c79100,color:#5b4500; classDef platform_builtin fill:#e0e0e0,stroke:#424242,color:#1a1a1a; locations["Locations"] service_requests["Service Requests"] service_catalog_items["Service Catalog Items"] configuration_items["Configuration Items"] org_units["Org Units"] onboarding_tasks["Onboarding Tasks"] service_offerings["Service Offerings"] users["Users"] service_catalog_items -->|"spawns"| service_requests onboarding_tasks -->|"emits"| service_requests org_units -->|"rolls_up_to"| org_units locations -->|"rolls_up_to"| locations users -->|"owned CIs"| configuration_items users -->|"leads"| org_units users -->|"performs"| onboarding_tasks users -->|"created"| onboarding_tasks users -->|"requests"| service_requests users -->|"fulfills"| service_requests users -->|"assigned requests"| service_requests users -->|"submitted requests"| service_requests users -->|"owned catalog items"| service_catalog_items org_units -->|"has members"| users locations -->|"houses"| users class locations embedded_master; class service_requests master; class service_catalog_items master; class configuration_items embedded_master; class org_units embedded_master; class onboarding_tasks embedded_master; class service_offerings master; class users platform_builtin; style locations stroke-dasharray:5 5; style configuration_items stroke-dasharray:5 5; style org_units stroke-dasharray:5 5;