IT service management
ITSM that reaches into SAP
From incident to go-live as one flow.
The challenge
An ITSM process is only as good as its handovers
Incidents, changes and requests start at the service desk. Development and SAP then continue in other systems.
These handovers are exactly where follow-up questions, duplicate entry and gaps in information appear.
Tickets passed on by hand
Items move to the next system by email or copy, and the context gets lost.
No feedback from SAP
The service desk does not learn when the SAP change has gone live.
Service quality hard to measure
Without an end-to-end flow, reliable metrics are missing.
The approach
Look at the whole route, not just the workflow
Cross ALM combines process consulting, the ITSM platform and the SAP connection. The service process is viewed from the first report to go-live:
Incident at the service deskAnalysisChange or development taskSAP changeTransportGo-liveStatus back to the service desk
The SAP connection is handled by CC4 and CC5, so the item stays one item across every system.
Services
ITSM processes that flow end to end
Incident management
Capture and classify incidents and hand them to development or SAP when needed, without losing sight of them.
Request management
Standardise recurring requests, define responsibilities and automate the steps where a rule pays off.
Problem management
Trace recurring incidents to their root cause and link that cause to ongoing work.
Change and release
Assess and approve changes, bundle them into releases and connect them with SAP transports.
Service catalogue and knowledge
Organise services clearly and store knowledge from resolved items where people can find it.
Enterprise service management
The same principles for HR, finance and facilities.
Choosing the platform
Jira Service Management or ServiceNow?
There is no general answer. Cross ALM works in both worlds and assesses the question for your case, including:
Platform strategySize of the service organisationProcess complexityNeeds beyond ITCloseness to developmentSAP connectionAudit obligationsLicence and operating modelExisting skills
SAP Cloud ALM provides the SAP-specific operations context. In many landscapes, the ITSM process still runs on a service platform. The task is to connect both rather than rebuild one in the other.
From client projects
Service processes in practice

Public sector
4 weeks
to integrate Jira into SAP Solution Manager processes

Manufacturing
4,000 users
in IT service management and enterprise service management
Your contact
Personal support for your ITSM project

Marco Gubala
Chief Operating Officer and Head of Service Delivery
Steers IT operations and delivery and leads end-to-end ITSM transformations.
Currently: expanding the Atlassian partnership and advising on architecture and processes when moving from SAP Solution Manager to platforms such as Jira Service Management.
In the first conversation you clarify
- where your process loses time today
- which handovers are done by hand
- which platform fits
- what the SAP connection must deliver
Direct contact
Prefer to write or call right away?
Email: solutions@crossalm.com
Phone: +49 30 398 36 112
Approach
Three steps to an end-to-end process
1 · Capture
Record the current process and the points that cost time, together with the service staff.
2 · Define and set up
Decide target process, roles, platform and connections, then configure and automate.
3 · Accept and refine
Test with the business, enable teams and review the metrics together after launch.
FAQ
What to know about IT service management
Does Cross ALM advise on Jira Service Management and ServiceNow?
Yes. Cross ALM is an Atlassian Gold Solution Partner and a ServiceNow partner, and assesses the platform choice for your case.
Does SAP Cloud ALM replace our ITSM tool?
In many landscapes it does not. SAP Cloud ALM provides the SAP operations context, while the service process stays in Jira Service Management or ServiceNow. The connection is what matters.
How does status from SAP get back to the service desk?
Through the Cross ALM connectors: CC4 links Solution Manager with Jira or ServiceNow, and CC5 brings SAP transports into Jira.
Where is the best place to start?
With the process that causes the most follow-up questions today. Often that is the route from incident to SAP change.
From the end of SolMan in 2027 to an agentic tool chain for SAP landscapes
How SAP teams plan the move and connect SAP, Jira and ServiceNow into one tool chain.
Contact
Let’s talk about your project
Tell us briefly what it is about, and you will hear from us personally.

What happens when you get in touch:
- A consultant gets back to you and clarifies your requirements
- Together with you, we analyse your processes and systems
- You receive a proposal for the next steps
You are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationPrefer to get in touch directly? Email solutions@crossalm.com or call +49 30 398 36 112.







