Home / Customers & Partners

Customers & Partners

Trusted by

From leading manufacturers to top university labs, ALiGN stands with the people deepest inside the scenario.

They're running production on ALiGN

Leading lighthouse enterprises · a number of ecosystem partners.

Yanfeng International
Shanghai Electric
AVIC
Chinese Academy of Sciences
China Aerospace
Partners
Partners
Apeloa
Yanmade
Yanfeng International
Shanghai Electric
AVIC
Chinese Academy of Sciences
China Aerospace
Partners
Partners
Apeloa
Yanmade

Three industries, three lighthouses

From automotive parts to energy equipment to pharmaceutical CDMO — one operation layer, different business languages.

Yanfeng International Intelligent Design Platform
Automotive Parts · Equipment Manufacturing

A Global Automotive Parts Giant × ALiGN Intelligent Design Platform

Using large models, knowledge graphs and multi-agent technology to break down data barriers across design, manufacturing and quality inspection.

Background

Massive data accumulation, scattered expertise, complex processes, diverse tools and systems, volatile markets and faster product iteration — all routine for this manufacturing giant. The company set out to build a systematic AI capability and one unified AI enablement platform.

Challenges

  • Intelligent interaction and tool integration:Build a unified human–machine entry point that supports multi-turn natural language dialogue and language switching.
  • Knowledge services and KBE integration:Aggregate heterogeneous knowledge from multiple sources into an ontology-based knowledge hub.
  • Data management and intelligent analysis:Consolidate on-premise and online BOM data, with fully private deployment and permission control.

Solutions

  • Intelligent conversation layer:A unified interaction entry point that fuses knowledge retrieval with business execution, supporting cross-language interaction compliant with KBE coding standards.
  • Cross-platform collaboration layer:Connects business applications horizontally across domains, integrates infrastructure and data resources vertically, and establishes cross-functional collaboration.
  • Data management layer:With BOM information as the data thread, AI empowers every link — R&D, manufacturing, sales and service.

Results

Intelligent scenarios and applications including AI4CAD and AI4CAE have gone live, establishing a paradigm that fuses AI technology with deep domain work and delivering core capabilities such as a knowledge hub driven by intelligent technology, KBE integration and BOM comparison. InLower design cost, higher production efficiency, better verification quality, new business valueAll four dimensions delivered significant results, giving the industry a lighthouse case and a reference approach for AI-empowered manufacturing.

4
Categories of Core Functions Consolidated Into One Entry
100%
Private Deployment · Data Never Leaves the Plant
Cross-System AI Q&A Platform for Steam Turbines
Energy Equipment · Intelligent Design

A Power Equipment Giant × ALiGN Cross-System AI Q&A Platform

Using knowledge graph and data platform technology, build a visual association network spanning the full lifecycle of a turbine blade — from islands of information to a continent of data.

Background

During its digital transformation, the company faced severe information silos: design, manufacturing and quality inspection each ran on separate systems with inconsistent formats and rigid barriers. Cross-department work required many conversations and many system switches — slow, laborious, and decisions were made on incomplete evidence.

Challenges

  • Data barriers make collaboration hard:R&D parameters, digital models and drawings rarely reach process engineering, so data consistency across domains cannot be guaranteed.
  • Process knowledge is hard to reuse:Blade process design relies on individual experience with no systematic capture — hard to search, hard to reuse.
  • Advanced technology is hard to absorb:Inefficient process practices block new technologies and new processes, and hold back the growth of process engineers.

Solutions

  • Intelligent application layer:Built on large models, agents and MCP to enable intelligent generation, recommendation and prediction — powering blade information retrieval, process route generation, UID generation and out-of-tolerance risk detection.
  • Knowledge base layer:Using RAG and knowledge graphs, build an AI knowledge base where a graph database and a vector store work together, achieving full-scope semantic fusion and unified storage.
  • Cross-system fusion layer:Design large-model-based cross-system interface protocols and presentation components to integrate data and functionality across heterogeneous systems.

Results

Build a visual association network spanning the full lifecycle of turbine blades, connect seamlessly with multiple heterogeneous systems, and remove business data barriers entirely — one search reaches through the whole chain across departments. The platform supports real-time multi-user retrieval, and an innovative timeline surfaces key events along the blade lifecycle, giving strong support to intelligent scheduling.

99.9%
First-Pass Yield
30–50%
Higher Blade R&D Efficiency
20%
Shorter Production Cycle
40%
Less Duplicated R&D Work
Pharma CDMO Intelligent Quotation Case
Pharma CDMO · Intelligent Quotation

A Leading Pharma CDMO × ALiGN Intelligent Quotation

Turn an experience-dependent quotation process into one that is computable, traceable and optimizable.

Background

Quotation in pharma CDMO spans requirement parsing, route selection, cost accounting and commercial strategy, with information scattered across departments and historical documents. It leans on veteran experience, responds slowly and lacks a consistent basis.

Solutions

  • Requirement parsing:Structure the customer's RFQ documents into computable requirement elements.
  • Route recommendation:Recommend feasible synthesis routes from historical projects and the process knowledge base.
  • Cost accounting:Link material, labour-hour and capacity data to generate a cost range quickly.
  • Strategy optimization:Give quotation recommendations against margin targets and the competitive landscape.
4
Requirements → Route → Cost → Strategy
AI
Experience Turned Into Reusable Assets

Six Scenarios Already Running

From materials and drawings to changes and reuse — AI does not just answer questions, it completes the business action. Click any scenario to see how it executes.

R&D Data

Material Creation

One sentence from an engineer takes a material from specification to active master data
3
Key User Confirmations
40+
Attribute Fields Auto-Processed
3
Systems Take Over Automatically
+

Customer Pain Points

  • A new material typically takes about two weeks of back-and-forth across systems before it lands
  • The definitions of forty-plus attribute fields are scattered across specifications, rule libraries, historical data and human judgement
  • Whether a similar material can be reused depends mostly on the engineer's search experience
  • Approval and master data wait in series; one delayed node stalls the whole chain

How Users Work

Upload the specification and state your intentConfirm Whether to Reuse a Similar MaterialFill In a Few Key FieldsView Results & Audit Log

AI Execution Chain

Parse the specification → extract key parameters → check for duplicates → auto-fill attributes → create the controlled object → drive approval → push master data → issue the material number
Engineering Change

Engineering Change Closed Loop

See the change impact first, then run the forms, approvals and cross-system sync to the end
1
Initiated in Natural Language
8
Affected Object Analysis
End-to-End
Change Execution Traceability
+

Customer Pain Points

  • Impact scope is judged by experience, easily missing products, orders, suppliers or in-transit batches
  • Change forms demand a long list of fields — reason, objects, impact, risk, approvers and switchover strategy
  • The drawing changed but the BOM did not; the system changed but downstream was never synced — classic execution risk
  • Discussions, approvals, supplier confirmations and implementation results are scattered across systems and email

How Users Work

State the Change IntentLocate Change ObjectsView the Impact ListConfirm the Switchover StrategyAI Drives the Loop

AI Execution Chain

Identify the change type → link materials, drawings and BOM → analyse affected objects → mark the risk level → create the change form → assign approval tasks → generate actions → sync across systems → keep a full audit trail
Supply Chain Collaboration

Drawing Release & Supplier Collaboration

Deliver controlled drawings to suppliers securely and govern the entire collaboration
1
Conversation Entry
3
Collaboration Scenarios
End-to-End
Versioning & Audit
+

Customer Pain Points

  • Release notices are routinely ignored; a completed workflow does not mean the recipient actually read it
  • Distribution forms need manual selection of objects, recipients, approval chasing, then packaging and encryption
  • RFQs pass drawings over email and chat, which leads to wrong versions and missing trails
  • On secured network segments, moving files in and out, confirming versions and controlling permissions all consume people

How Users Work

State the Collaboration IntentAuto-Link Controlled DocumentsCheck External Release ConditionsTrack Downloads & Iterations

AI Execution Chain

Locate the latest version → verify classification and qualifications → generate the distribution form → drive approval → encrypt and package → upload to the collaboration area → notify suppliers → track downloads → manage technical clarification rounds
Development Collaboration

xBOM Skeleton Development Collaboration

Let every discipline work around one product tree, not just hand over a final BOM
xBOM
Collaboration Backbone
7
BOM View Evolution
Multi-Discipline
Process Data Mounted
+

Customer Pain Points

  • BOMs exist to serve manufacturing and delivery; system partitioning, design intent and configuration rules are never captured
  • CAD integration produces a structural list, but systems, subsystems and virtual parts are still built by hand
  • Purchasing, process, quality and certification data are scattered across documents, spreadsheets and meeting notes
  • What gets delivered is a document package, not reusable stage-gate process data

How Users Work

Describe the Project IntentRecommend the xBOM SkeletonMap Electrical/Mechanical DataAssign Discipline TasksRelease by Phase

AI Execution Chain

Match historical architecture → generate the system and subsystem skeleton → map the electrical/mechanical list → create discipline data mounting points → assign role tasks → release by phase
Release Quality

BOM Release & Completeness Check

Check completeness first, then release the BOM downstream safely
7
Gaps Auto-Identified
3
Release Blockers
5
Downstream Consumption Checks
+

Customer Pain Points

  • Approval is complete, yet downstream consumption reveals missing drawing versions and inactive materials
  • Relationships between BOMs, materials, drawings, substitutes and change orders are complex and hard to retrieve in one pass
  • Materials, documents, changes, approvals and master data status are frequently out of sync
  • Once a gap is found, someone still has to judge ownership, send messages, chase feedback and re-check

How Users Work

Specify Release TargetsRun the Completeness CheckGaps Auto-AssignedConfirm, Then Release

AI Execution Chain

Identify the BOM view → expand the structure → bind drawings and documents → verify objects and status → grade the gaps → assign by role → re-check after completion → release and notify downstream → capture the check rules
Design Reuse

Similar Design Reuse & Module Recommendation

Find reusable solutions among historical designs and explain why they are recommended
4
Similar Project Matches
27
Candidate Proven Modules
9
Directly Reusable
+

Customer Pain Points

  • There are many historical projects, but whether one can be reused — and where the similarity lies — is never clear
  • No unified gate decides whether a module can be reused as-is, reused with modification, or must not be reused
  • Only after reuse do interface mismatches, configuration conflicts or recurring quality problems surface
  • The reasoning behind each reuse decision is never captured, so the next one starts from scratch

How Users Work

Enter the New Project RequirementMatch Similar Historical DesignsView Recommended ModulesConfirm and Instantiate

AI Execution Chain

Extract requirements → search similar requirements → map functions → recommend logic modules → shortlist proven modules → verify interfaces and risks → write back reuse relationships

Could your industry be the next lighthouse?

Start with a 90-day closed loop: prove the value first, then talk about scale.

Book a Demo