Huawei’s Enterprise Architecture: The 4A Framework in Action

Core Framework: The 4A “One Body Four Faces” Architecture

Huawei defines enterprise architecture as the bridge from strategy to execution, centering on business goals and coordinating four architecture domains to form a closed‑loop system.

1. Business Architecture (BA): Top‑down design from customer value

Value‑stream mapping: Define enterprise‑level value streams (e.g., lead‑to‑cash LTC, IPD product development, issue‑to‑resolution ITR) from the customer perspective to drive business design and break departmental silos.

Business capability decomposition: Break value streams into layered capability inventories; for example, “Warehouse Distribution Management” is refined into 41 second‑level capabilities with clear ownership and maturity requirements.

Process implementation: Build an end‑to‑end process hierarchy L1–L5 (L1 strategic, L5 operational) and solidify rules with PDCA.

Business object identification: Clarify core entities and collaboration relationships in each process to feed the data architecture.

Risk control: Insert eight categories of risk‑control points such as role separation, embedding compliance into processes.

2. Information Architecture (IA): A shared data foundation

Principle of “single source, single hole”: Resolve data inconsistency and silo issues at the source.

Five‑layer data asset catalog: L1 thematic domain grouping → L2 thematic domain → L3 business object → L4 logical entity → L5 attribute, establishing unified data semantics.

Master data governance: Maintain core master data (customers, products, organizations, suppliers) in one place and share it across the entire chain.

Lake‑warehouse integration: Provide a unified storage, tiered authorization, and multi‑use data base that supports operational analysis and business innovation.

3. Application Architecture (AA): Service‑oriented platform + lightweight front‑ends

Top‑down decomposition: From enterprise value streams to application domains, groups, and functional modules, defining system boundaries to avoid duplicate construction.

Bottom‑up aggregation: Consolidate common business capabilities into reusable services (126 public services) and build middle‑platforms for procurement, sales, finance, etc., enabling rapid front‑end consumption.

Metadata‑driven multi‑tenant architecture: Adapt the unified base to varied business needs of carriers, enterprises, and consumers.

4. Technical Architecture (TA): Autonomous, controllable infrastructure

“Three horizontals, two verticals” framework: Infrastructure layer, digital platform layer, public service layer (horizontals) plus security assurance and operation‑maintenance systems (verticals).

Full‑stack self‑control: Build the core stack on self‑developed Euler OS, GaussDB, and TaiShan servers, eliminating overseas technology dependence.

Cloud‑native + cloud‑edge collaboration: Support global elastic deployment, handle traffic spikes during major promotions, and meet localized operational requirements.

6R methodology for cloud migration: Standardize technology selection and control fragmentation risks.

Governance System: Three‑Level Hierarchical Governance

Huawei’s architecture is divided into enterprise, domain, and solution layers, balancing global consistency with business flexibility.

Enterprise layer: Sets group‑level architecture principles, standards, and blueprints, overseeing cross‑domain capabilities and bearing overall responsibility.

Domain layer: Aligns with specific business areas such as finance, supply chain, R&D, refining domain‑level designs and implementation plans.

Solution layer: Translates domain architectures into executable solutions for concrete projects, ensuring compliance with architectural requirements.

Three supporting governance actions:

Legislation: Define architecture principles, norms, and standards as the company’s “architecture constitution.”

Process embedding: Integrate architecture review into core processes like IPD, placing control before project design rather than after.

Compliance audit: Conduct regular audits with checklists and technical red‑lines to guarantee faithful implementation.

Typical Implementation: MetaERP Self‑Developed Replacement

Guided by the 4A methodology, Huawei rebuilt the entire stack—from business and data to applications and technology—replacing the legacy Oracle/SAP suite.

Results: core business processing efficiency increased by 40%, system response time reduced by 50%, and the new platform supports multi‑currency, multi‑tax, and multi‑compliance scenarios worldwide.

The case validates an architecture‑driven reconstruction path: first clarify business logic and data standards, then implement systems, rather than letting existing systems dictate business processes.

Core Characteristics of Huawei’s Practice

Business‑driven, not IT‑driven: Architecture initiatives are owned by business units, with IT serving only as technical support.

Deep coupling of process and architecture: Architecture rollout proceeds in sync with process‑oriented organizational construction, aligning responsibilities, organization, and performance.

Autonomous control and simultaneous stack replacement: Architecture upgrades achieve domestic technology substitution, eliminating legacy debt and “bottleneck” issues.

Layered adaptation for massive scale: The three‑level governance balances group‑wide control with business‑unit agility, fitting diversified, global operations.