Alibaba Cloud Manufacturing Global Translated from Chinese

Midea Building Technologies (美的楼宇科技)

Data Lake / Data Warehouse Modernization · Real-time Analytics

Midea Building Technologies had a large and fast-growing stream of semi-structured IoT equipment data, but its earlier environment focused on storage and basic use rather than deeper analytical and AI-driven value extraction. The company needed a unified, elastic data platform that could support large-scale processing, real-time and historical data fusion, and AI-assisted analysis for energy management, equipment operations, and maintenance decisions.

aggregated 100-billion-scale data at million-level dimensionality
more than 3x performance advantage over open-source versions
overall cost reduced 30%
overall data-platform performance improved 50%

Reported impact

Business outcome

Midea turned a storage-heavy IoT environment into a governed Data+AI platform that can process large streams of equipment data faster and at lower cost. The new stack improved overall platform performance, reduced total cost, simplified the batch-and-stream pipeline, and gave the data team a more practical foundation for intelligent building operations and analytics.

  • Cost Reduction
  • Productivity Improvement
  • Scalability

Solution

Midea Building Technologies built an IoT lakehouse on Alibaba Cloud around EMR Serverless Spark so building-equipment telemetry could be processed with both analytics and AI logic at production scale. Historical customer and device data is batch-loaded from relational systems into Hudi tables through Spark SQL, while real-time events are streamed through Cloud Kafka and written into the same Hudi tables with Spark Structured Streaming, giving the company one batch-and-stream data base. On top of that pipeline, PySpark jobs use PyArrow UDFs to call Midea's own algorithms and aggregate hundred-billion-scale records across million-dimensional feature spaces. DLF provides unified lakehouse management, and processed indicators are loaded into Serverless StarRocks for dashboards and reporting. The result is a managed Data+AI platform that combines IoT data engineering, lakehouse governance, and AI-assisted decision support in one architecture.

Data flow

Historical data is batch-imported from customer relational databases into Hudi tables with Spark SQL, while real-time IoT events flow through Cloud Kafka into Spark Structured Streaming and land in the same lakehouse tables. EMR Serverless Spark and PySpark UDFs aggregate and score the resulting data, then processed indicators are loaded into Serverless StarRocks for dashboards, reporting, and downstream data-science workflows.

Solution architecture

5 components · 5 layers
  1. Ingest
    • Cloud Kafka Carries real-time IoT events from the device platform into the streaming data pipeline.
  2. Compute
    • EMR Serverless Spark Provides the managed compute layer for batch imports, streaming processing, and AI-oriented feature aggregation.
  3. Storage
    • Hudi Lake Stores unified historical and real-time IoT data in the lakehouse layer.
  4. Serving
    • Serverless StarRocks Serves processed indicators to dashboards and reporting applications for business users.
  5. Governance
    • Data Lake Formation (DLF) Provides centralized management for the lakehouse metadata and governance layer.

Architecture clues

  • Historical and real-time IoT data are written into the same Hudi tables, so Midea runs a true batch-and-stream lakehouse pattern.
  • PyArrow UDFs are used to call Midea's own algorithms from PySpark jobs rather than keeping AI logic outside the data platform.
  • Serverless StarRocks is the serving layer for processed indicators, while DLF governs the lakehouse control plane.

Evidence from the source

After the redesign, platform performance improved 50%, overall cost fell 30%, and EMR Serverless Spark delivered more than 3 times the performance of open-source alternatives. (original: 数据平台整体性能提升 50……综合成本下降 30……相比开源版本 3 倍以上的性能优势。)
Historical data is batch-imported into Hudi with Spark SQL, while real-time IoT data is collected through Cloud Kafka and written into the same Hudi tables with Spark Structured Streaming. (original: 历史存量数据是通过 Spark SQL 以天为单位从不同客户关系数据库批量导入 Hudi Lake 表中;实时数据通过 IoT 平台采集到云 Kafka,经由 Spark Structured Streaming 消费后实时写入到 Hudi Lake 表中。)
Midea said its growing semi-structured IoT device data needed a unified elastic platform with data-science and AI support so the company could move beyond basic storage into intelligent mining. (original: 当前设备数据量庞大且持续增长、数据呈现半结构化特点……迫切需要构建一个统一且通用的 IoT 数据平台……还应具备强大的大规模数据处理能力以及数据科学和 AI 技术支持。)
The company used Serverless Spark PySpark tasks with PyArrow UDFs to call self-developed algorithms and aggregate 100-billion-scale data at million-level dimensionality. (original: 楼宇科技通过 Serverless Spark PySpark 任务,并基于 PyArrow UDF 调用自研算法实现了千亿级别数据在百万级维度的聚合。)
Transparency Evidence & methodology 100/100 reference value · 95% 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 value100/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
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence95%
  • 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 evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency10/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

    美的楼宇科技基于EMR Serverless Spark 构建 LakeHouse 湖仓数据平台

    First-party
    https://www.aliyun.com/customer-stories/manufacturing-2025-mbt-midea
    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 Mar 14, 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.