[{"data":1,"prerenderedAt":4},["ShallowReactive",2],{"raw-en-use-cases\u002Fservice-management":3},"---\ntitle: Service Management\ndescription: How IQ:NS supports service management by making operational knowledge and service knowledge management queryable.\nlang: en\nnavigation:\n  section: use-cases\n  label: Service Management\n  order: 80\n---\n\n# IQ:NS for Service Management\n\nService management teams need structured knowledge that spans ITSM, policies, and AI-enabled services. IQ:NS turns service definitions, roles, and operational rules into a shared vocabulary.\n\n## The challenge\n\nService knowledge is often stored in separate systems: service catalogs, runbooks, policies, and control frameworks. That fragmentation makes it hard to answer what a service should do and why.\n\n## What the ontologies provide\n\n- **Service catalog structure** — formal concepts for services, capabilities, and support models\n- **Operational alignment** — map ITSM workflows to controls, obligations, and compliance needs\n- **Agent-ready service knowledge** — enable bots and incident response systems to reason over service semantics\n- **Integrated change context** — link service updates to the same knowledge used by governance and risk teams\n\n## How it fits\n\nIQ:NS complements service management tools with structured knowledge, not process automation. It lets ITSM, SKMS, and operational dashboards all refer to the same semantics.\n\n[Explore the ontologies](https:\u002F\u002Fgithub.com\u002Fiqns-org\u002Fontologies) · [How it works](\u002Fhow-it-works)\n",1776235632404]