Alibaba Cloud Automotive China Translated from Chinese

Xpeng Motors (小鹏汽车)

Enterprise Knowledge Search · IT Operations Automation

Xpeng needed one secure AI platform for employees instead of a growing collection of disconnected tools. Internal knowledge was sprawling across many departments, employees wanted generative AI for writing, reporting, and design tasks, and the company had to keep sensitive information inside strict access and compliance boundaries.

covers 44 service-desk knowledge domains
launched within 100 days
supports 85 chatbots

Reported impact

Business outcome

Xpeng gave employees a unified AI service entrance instead of fragmented tools. The platform accelerates internal information access, automates office work, supports multimodal creation and training, and provides managers with new data-driven insight while keeping sensitive knowledge under governed routing and safety controls.

  • Compliance
  • Customer Experience
  • Productivity Improvement
  • Speed to Market

Solution

Xpeng built a company-wide digital employee platform on Alibaba Cloud to unify knowledge search, content generation, workflow assistance, and management insight under one governed AI layer. The platform blends RAG over FAQs, internal documents, external knowledge, and open search with knowledge-graph enrichment and multi-path retrieval so employees can get concise answers without manually navigating many systems. At the model layer, Xpeng uses a hybrid architecture that routes sensitive or high-permission requests to privately deployed models on PAI while AI Gateway can burst overflow traffic to Bailian during peaks and apply policy across both environments. AI safety guardrails add HTTPS transport, content filtering, and intent classification so internal questions that touch private knowledge stay within the private domain. On top of that base, digital employees cover help-desk Q&A, chatbots, document generation, multimodal creation, training, task handling, and management analytics.

Data flow

Employee questions, search requests, and generation tasks enter the digital employee layer, which retrieves context from internal and external knowledge sources through RAG and knowledge-graph enrichment. API Gateway then routes the request either to private models on PAI or to Bailian burst capacity, while AI safety controls filter content and restrict sensitive data to the private environment before answers or generated assets are returned.

Solution architecture

4 components · 3 layers
  1. Compute
    • Platform for AI (PAI) Hosts private model deployments for sensitive internal tasks and enterprise knowledge requests.
  2. Orchestration
    • Bailian Supplies public-cloud model capacity and downstream AI application support during burst demand.
    • API Gateway Routes model traffic across private and public environments and enforces unified access policy.
  3. Governance
    • AI Safety Guardrails Filters unsafe content and enforces intent-based controls for sensitive requests.

Architecture clues

  • Intent classification is used to keep sensitive internal requests inside private model infrastructure.
  • The platform uses multi-path retrieval and knowledge-graph enrichment rather than a single retrieval source.
  • Traffic is split between private PAI models and public Bailian capacity through one gateway layer.

Evidence from the source

The company uses RAG governance, knowledge graphs, and multi-path concurrent retrieval for knowledge search, while AI Gateway coordinates private PAI models with Bailian burst capacity. (original: 实施精细化的 RAG 治理策略,并结合知识图谱构建实现语义关联与结构化表达... 结合 AI 网关的智能路由与流量调度能力,实现 PAI 平台上私有化部署的模型与公有云百炼模型的无缝协同。)
The digital employee platform launched within 100 days and already covers 44 service-desk Q&A domains and 85 chatbots. (original: 该项目实现百日内完成系统上线... 覆盖 44 个服务台问答、85 个聊天机器人。)
Xpeng said employees needed AI for internal process handling, design-image generation, creative material generation, rapid reporting, and secure knowledge access. (original: 员工对 AI 工具的需求快速增长... 如基于文本生成设计图稿、活动创意素材自动生成、快速数据报表分析与可视化... 内部知识体系持续快速膨胀。)
Transparency Evidence & methodology 86/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 value86/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 specificity16/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 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

    小鹏汽车数字员工解决方案

    First-party
    https://www.aliyun.com/customer-stories/automotive-2025-xiaopeng
    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 Oct 31, 2025 · Alibaba Cloud · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.