Alibaba Cloud Commercial and Professional Services Global Translated from Chinese

ShineWing (信永中和)

Enterprise Knowledge Search · IT Operations Automation

ShineWing needed to move beyond isolated assistants and build a secure enterprise AI layer for document-heavy professional services. It had to coordinate multiple agents, unify AI assets, connect internal systems safely, and control cost and auditability across a growing multi-model estate.

completed final joint integration and launch in 1 week
has more than 12,000 employees
operates 110 offices in 23 countries and regions

Reported impact

Business outcome

ShineWing established a controlled enterprise AI foundation that gives employees a common AI service entrance, reduces the friction of finding internal information and invoking workflows, and lets the firm extend AI from information lookup into multi-step task execution. The project also proved the platform could be integrated and launched in a one-week final sprint.

  • Compliance
  • Productivity Improvement
  • Speed to Market

Solution

ShineWing built an internal multi-agent AI operating layer on Alibaba Cloud so employees could move from simple information lookup to governed task execution across audit, tax, consulting, and administrative workflows. AgentTeams acts as the orchestration plane: it exposes a unified entry point, recognizes user intent, routes requests to specialized agents for policy Q&A, OA integration, information retrieval, and document processing, and can decompose more complex tasks across several agents. Around that runtime, the firm centralized management of models, MCP servers, skills, and agent templates so permissions and reuse are handled consistently instead of in isolated projects. AI Gateway fronts the model layer with authentication, traffic control, failover between models, token accounting, and content-safety inspection, while end-to-end observability records agent runs, model usage, and abnormal behavior for audit and governance. The result is a secure enterprise AI base rather than a collection of disconnected assistants.

Data flow

Employee requests enter a unified AI interface, where AgentTeams classifies the task and routes it to the right specialized agent or coordinates several agents together. Those agents call internal systems through MCP Server and use models protected by AI Gateway, while usage, exceptions, and token consumption are logged for governance and cost analysis.

Solution architecture

3 components · 2 layers
  1. Orchestration
    • AgentTeams Coordinates specialized agents and provides the unified employee entry point for AI services.
    • MCP Server Turns internal systems into standardized capabilities that agents can invoke securely.
  2. Governance
    • AI Gateway Provides model access control, routing, failover, token accounting, and safety checks.

Architecture clues

  • AI Gateway is used for both model failover and token-level cost observation, not just basic proxying.
  • The agent layer is tied directly into professional-services systems such as OA and knowledge bases.
  • The platform treats agents, models, MCP services, and templates as centrally governed AI assets rather than per-team experiments.

Evidence from the source

In the final stage, both teams completed system integration, testing, tuning, and launch within one week. (original: 在项目最终关键阶段仅用一周时间完成系统联调、测试优化并正式上线。)
ShineWing said enterprise AI was moving from a single assistant to complex scenarios that required agent collaboration, unified asset management, and secure integration with OA and knowledge systems. (original: 多智能体协同难... AI 资产管理散... 需要将 AI 能力与内部 OA、知识库等核心业务系统安全连接。)
The company built multiple specialized agents for policy Q&A, OA integration, information lookup, and document processing, and AgentTeams can dispatch them or split complex tasks across several agents. (original: 构建了制度问答、OA 集成、信息查询、文档处理等多类专业 Agent。通过平台统一入口识别员工需求,自动调度相应的专业 Agent,或拆解复杂任务实现多 Agent 协同工作。)
Transparency Evidence & methodology 90/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 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 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

    信永中和基于阿里云AgentTeams与AI网关,一周快速上线多智能体AI平台_金融_阿里云客户案例

    First-party
    https://www.aliyun.com/customer-stories/financial-services-2026-shinewing
    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 Aug 6, 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.