Alibaba Cloud Automotive China Translated from Chinese

Geely Auto

IT Operations Automation

Geely's user-data systems were becoming too complex for manual operations after multi-cloud growth, cross-site deployments, and the addition of Zeekr into the group. Topology was opaque, logs and metrics stayed siloed, alert storms produced hundreds of signals per incident, and mean-time-to-recovery frequently stretched into hours instead of the desired minutes.

incident storms can produce hundreds of alerts at once
manages hundreds of systems across clouds and sites
target service objective is 1 minute to detect, 5 minutes to locate, and 30 minutes to recover
traditional recovery often took 1 to 2 hours

Reported impact

Business outcome

Geely is replacing the old monitor-alarm-ticket chain with a data-driven operations loop that can model dependencies, diagnose incidents faster, and codify operational know-how for reuse. Teams now treat AI operations as a strategic platform capability rather than only a help-desk assistant.

  • Customer Experience
  • Productivity Improvement
  • Risk Reduction

Solution

Geely built an agentic-operations system on Alibaba Cloud around a four-layer model of data, modeling, diagnosis, and knowledge capture. Cloud Monitor 2.0 unifies metrics, logs, traces, events, and change records from scattered environments so operations intelligence starts from one data base instead of many fragmented sources. UModel then creates an operations digital twin by associating cloud resources, service topology, and Geely's internal business models in one context, which lets the intelligent agent follow impact paths and reason about likely root causes. On top of that model, STAROps automates evidence collection, filters large numbers of low-value alerts in seconds, and returns diagnosis paths or recovery ideas. Geely is also turning operational experience into reusable Skills, Runbooks, and healing commands so incident response becomes an asset the AI system can reuse instead of a one-time human effort.

Data flow

Observability and change data from Geely's systems is unified in Cloud Monitor 2.0, associated into a digital twin through UModel, and then analyzed by STAROps for evidence gathering, alert filtering, diagnosis, and runbook-based healing suggestions. The outputs are fed back into operations teams and reusable skills for future incidents.

Solution architecture

3 components · 2 layers
  1. Orchestration
    • UModel Builds the digital-twin model that links topology, resources, and business context for diagnosis.
    • STAROps Runs agentic diagnosis, alert-noise reduction, and reusable operational skills.
  2. Governance
    • Cloud Monitor 2.0 Provides the unified observability data base for AI-assisted operations analysis.

Architecture clues

  • Geely separates the AIOps stack into data, modeling, diagnosis, and knowledge-accumulation layers instead of relying on one monolithic assistant.
  • Runbooks and healing commands are being promoted into reusable skills so future incidents can be automated more directly.
  • UModel lets enterprise-specific topology and business models join cloud observability data in one diagnosis context.

Evidence from the source

Geely said topology had become a black box, data stayed isolated across logs, traces, and metrics, and alert storms could generate hundreds of alarms while recovery still took one or two hours. (original: 拓扑全是黑盒;各系统的日志、链路、指标各自为政... 监控屏瞬间涌出几百条告警... 平均恢复动辄一两个小时。)
Geely wants the new architecture to support a golden SLA of 1 minute to detect, 5 minutes to locate, and 30 minutes to recover. (original: 传统应对方案很难支撑“1 分钟发现、5 分钟定位、30 分钟恢复”的黄金 SLA。)
Its solution is a four-layer intelligent-operations system of data, modeling, diagnosis, and knowledge capture built on Cloud Monitor 2.0, UModel, and STAROps. (original: 吉利基于阿里云可观测构建“数据—建模—诊断—沉淀”四层智能运维体系... 基于阿里云云监控 2.0... 通过 UModel 自动为云上资源建模... 围绕告警/异常自动收集证据。)
Transparency Evidence & methodology 95/100 reference value · 88% 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 value95/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 impact25/25
    2 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence88%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence15/20
    3 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • 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. Alibaba Cloud

    吉利汽车基于STAROps 构建全域智能运维体系,从报警风暴到主动免疫_汽车_阿里云客户案例

    First-party
    https://www.aliyun.com/customer-stories/automotive-2026-geely
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • Published on source page Jun 10, 2026 · Alibaba Cloud · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.