Connected ITSM: a service desk linked to CMDB, devices and incidents, extended across business functions
Updated on
Connected ITSM brings IT service management beyond the ticket. The service desk connects to CMDB, remote device monitoring and management, and incident response, while the same service practices extend to HR, facilities, legal and finance through ESM. Loonar implements this joined-up workflow with AI-assisted triage and responses, aligned with ITIL 4.
In short
- Connected services and assets.
- Incidents with context.
- ESM across functions.
How do you know you need connected ITSM?
Missing device context
Technicians receive tickets without device configuration or asset history. They collect data from separate consoles and repeat questions, while support records fail to capture the actions performed during remote investigation.
Outdated CMDB
CMDB records are outdated or missing, with unreliable asset and service relationships. Changes affect functions absent from planning, and sources and owners are not defined to validate actual operational impact.
Disconnected incidents
Major incidents remain in technical channels without ticket, problem or change links. Support loses context, teams duplicate records and preventive decisions stay scattered after recovery, complicating accountable follow-up across functions.
Scattered requests
HR, facilities and legal use email and spreadsheets without catalogs or SLAs. Approvals disappear and leaders cannot compare demand, capacity and service quality through consistent definitions across the business functions.
How does it work?
Portal and catalog
Bring IT and business functions into a shared portal and catalog with appropriate SLAs and approvals. Separate audiences and permissions so ESM expands without exposing sensitive departmental information.
CMDB and ITAM
Feed CMDB and ITAM through automatic discovery and device inventory. Define reconciliation, ownership and updates to maintain verifiable asset and service relationships, with clear handling of data exceptions.
Integrated RMM
Connect RMM to tickets: eligible alerts create records, and technicians access devices and run scripts from the ticket with suitable permissions and evidence for each authorized action.
Incidents and changes
Link incidents, problems and changes to on-call and engineering. CMDB relationships support impact analysis and preserve connections between recovery, investigated causes and the changes required in ongoing operations.
AI and knowledge
Apply AI agents to triage, responses, deflection and article generation. Approved knowledge, review and human handoffs maintain accountability for the information and actions used within service delivery workflows.
Dashboards and automation
Track SLAs, demand, cost per ticket and satisfaction using shared definitions. No-code automation organizes routing and approvals with reviewed rules and explicit handling of the exceptions teams encounter.
How does Loonar deliver?
ITIL 4 discovery
Loonar assesses processes, tools and ownership using ITIL 4. Identify support and operations gaps, available sources and an initial scope the team can sustain through its daily work.
Catalogs and workflows
Design catalogs, workflows, SLAs and approvals with owners. Validate permissions, escalation and exceptions so published services represent commitments each function can meet within its actual daily operating context.
CMDB and integrations
Implement CMDB and integrations with RMM, monitoring, on-call and identity directories. Test discovery, reconciliation and synchronization to preserve context when systems are unavailable or return inconsistent operational information.
Assisted migration
Loonar plans migration with trial loads, validation and fallback options. Coordinate channels and queues to preserve support, with acceptance criteria and assistance throughout the transition to the new environment.
Function-by-function expansion
Expand ESM function by function across HR, facilities, legal and finance within scope. Each owner validates catalogs, access, approvals and indicators before taking responsibility for the operational workflow.
Training and operations
Train agents, administrators and service owners with real scenarios. Assist early operations and review alerts, automations and procedures using evidence, keeping responsibilities clear after the implementation and launch.
Which technologies does Loonar use to deliver it?
Atlassian
Jira Service Management and Assets as service desk and CMDB for IT and beyond.
Explore the Loonar + Atlassian alliance
NinjaOne
RMM integrated with the service desk: alerts become tickets and technicians act on devices.
Explore the Loonar + NinjaOne alliance
PagerDuty
Critical incidents linked to the service desk, with on-call and crisis communication.
Explore the Loonar + PagerDuty alliance
What results do we measure?
- First-contact resolution
- SLA compliance
- Incident MTTR
- Automatically updated CMDB records
- Deflection rate
- User satisfaction
Traditional ITSM, connected ITSM or ESM?
| Aspect | Traditional ITSM | Connected ITSM | ESM |
|---|---|---|---|
| Scope | IT | IT and operations | Cross-functional |
| Data | Tickets | CMDB, RMM, incidents | Department catalogs |
| Owners | Service desk | IT, engineering | Business functions |
| Examples | Access | Contextual alerts | Onboarding, contracts |
Where do we apply it?
Financial services
The organization links requests, services and assets to assess changes and respond with context. Support follows recovery while technical teams preserve linked evidence. Department catalogs apply their own permissions, preventing exposure of personal or contractual information as service management expands.
Manufacturing
Distributed devices require coordination across support, infrastructure and engineering. Eligible alerts create inventory-linked tickets, and owners check dependencies before changes. Facilities organizes requests and approvals while respecting production constraints and preserving a record of the actions performed on managed assets.
SaaS
Support, operations and engineering link tickets and incidents without duplicate investigations. CMDB reveals affected services and related changes. Reviewed knowledge guides responses and self-service, while dashboards distinguish demand, recovery and satisfaction to prioritize improvements using evidence shared across the teams.
Frequently asked questions
What is the difference between ITSM and ESM?
ITSM organizes IT services through incident, request, problem and change practices. ESM applies service management across functions such as HR, facilities, legal and finance. Departments need not share identical processes or records. Loonar designs appropriate catalogs, permissions and ownership while preserving context and collaboration within the shared service delivery operating environment.
Why connect the service desk to RMM?
Integration brings inventory, device health and remote actions into tickets. Eligible alerts create records and technicians run authorized procedures with context. Define creation, synchronization and closure rules to prevent duplicates. Respect permissions, applicable consent and activity records, keeping device access governed throughout remote support instead of assuming integration alone provides security.
How do we keep a CMDB current?
Combine automatic discovery, inventory and authorized sources with accountable quality owners. Define identifiers, reconciliation, relationships and updates for the environment. Automated collection cannot guarantee correct links: review exceptions and compare records with real services. Start with verifiable scope and purpose so CMDB information supports the decisions teams make during daily operations.
Can we migrate without stopping support?
Plan trial loads, data validation and coordinated channel transitions to preserve support. The approach depends on existing tools, integrations and requirements; do not promise an universally impact-free migration. Loonar agrees acceptance, communication, fallback and assisted operations before transition so teams can validate the environment and assume responsibility for the ongoing service.
Is connected ITSM aligned with ITIL 4?
Yes. ITIL 4 can guide a design adapted to organizational needs. The purpose is connecting service and value, not imposing rigid ceremonies. Catalogs, incidents, problems, changes and continual improvement receive useful ownership. Loonar assesses maturity and priorities to select a scope teams can operate and evolve rather than implementing everything simultaneously.
Shall we design the next version of your operation?
Tell us the challenge. One conversation with a specialist gives you a clear path, even if it isn't time to buy yet.