ServiceNow Healthcare Erlangen, Germany

Siemens Healthineers

Enterprise Knowledge Search · IT Operations Automation

Siemens Healthineers needed one governed platform for employee and supplier services, because fragmented departmental processes and manual support work made it harder to deliver consistent HR experiences, strengthen contract management, and introduce autonomous AI while staying compliant.

115+ Active HR services available in Enterprise Services portal
74,000 employees in over 70 countries
75% Employee adoption of Enterprise Service portal
850 Knowledge Articles available in eight languages

Reported impact

Business outcome

Siemens Healthineers reached 75% employee adoption of its service portal, exposed 115-plus HR services through one engagement layer, positioned Agent Zero to handle about 9,000 cases per month, and created a compliant-by-design model for AI-assisted HR and procurement workflows.

  • Compliance
  • Customer Experience
  • Productivity Improvement

Solution

Siemens Healthineers is using ServiceNow as an employee and supplier engagement layer built around AI Agents, Employee Center, HR Service Delivery, and Supplier Lifecycle Operations. Employee Center is the front door for more than 115 HR services and 850-plus knowledge articles in eight languages, while HR Service Delivery provides the case-management model for employee support. AI Agents such as Agent Zero and the Payslip Explanation Agent use ticket patterns and knowledge to classify, resolve, or escalate inquiries with context. Supplier Lifecycle Operations extends the same platform principles to the One Supplier Portal, where procurement teams manage supplier documents, contacts, contract insights, and stakeholder coordination in one place. The result is a compliant-by-design AI operating model that links HR, procurement, and governance on one ServiceNow foundation.

Data flow

Employees enter through Employee Center, where AI Agents use case history and knowledge articles to answer questions or open HR Service Delivery cases, then escalate unresolved work to human agents with full context. Procurement and supplier work flows through the same platform into Supplier Lifecycle Operations, where documents, contacts, and contract processes are coordinated with downstream business stakeholders.

Solution architecture

4 components · 3 layers
  1. Compute
    • AI Agents Run Agent Zero and the Payslip Explanation Agent to classify, answer, resolve, or escalate HR inquiries.
  2. Serving
    • Employee Center Acts as the single employee portal for services, knowledge, and lifecycle interactions.
  3. Orchestration
    • HR Service Delivery Manages HR cases, routing, and employee-support workflows behind the portal and AI agents.
    • Supplier Lifecycle Operations Coordinates supplier processes, documents, and stakeholder communication in the One Supplier Portal.

Architecture clues

  • AI governance is built into the operating model to align with the EU AI Act and platform-level visibility into agent usage and execution patterns.
  • Agent Zero is being rolled out in North America first, with humans reviewing AI-resolved cases and two dedicated reviewers initially handling one in ten queries.
  • The platform includes an Alumni Service Center so the same engagement layer stays in place across the employment lifecycle.

Evidence from the source

"Agent Zero is the latest example of this approach in practice-and Siemens Healthineers' first live deployment of agentic AI."
"HR is the primary use case, with over 115 active HR services available to employees via the Employee Service portal."
"The One Supplier Portal gives procurement teams a single place to work with direct and indirect suppliers-managing processes, contacts, documents, tools, and communications all in one spot."
"The aim is for it to autonomously process up to 9,000 HR tickets when it can find the answer or solution right away."
"With more than 850 Knowledge Articles available in eight languages, the portal supports everything from booking a desk, to raising an HR case or interacting with suppliers."
Transparency Evidence & methodology 90/100 reference value · 79% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. ServiceNow

    Siemens Healthineers customer story

    First-party
    https://www.servicenow.com/customers/siemens-healthineers-ai.html
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • Sitemap last modified Jul 30, 2026 · ServiceNow · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
  • Unverified extracted date Jul 30, 2026 · ServiceNow · Unknown Legacy extracted date without source-page confirmation.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.