Efficient Value Stream in the Construction of Huoshenshan and Leishenshan Hospitals: A DevOps Case Study

The DevOps case study "Huoshenshan and Leishenshan" examines how multiple activities—foundation work, power grid, communications, medical systems, and IT equipment—were coordinated through parallel and serial value streams to achieve rapid hospital construction.

Timeline Overview (Day 1‑Day 10)

Day 1 (Jan 24): Design work begins, power cabinet installation, fiber and 5G base station deployment, medical system tasks assigned, IT equipment donation plan confirmed.

Day 2 (Jan 25): Ground leveling completed, power supplied early, 5G base station commissioned, medical system development starts, IT equipment prepared for shipment.

Day 3 (Jan 26): Design completed, full construction starts, transformer relocation, communication equipment shipped, medical team arrives for on‑site debugging, IT equipment shipped.

Day 4 (Jan 27): First container houses hoisted, cable laying follows construction progress, network cable re‑routed from underground to perimeter.

Day 5 (Jan 28): Steel structure of double‑storey ward erected, interior power and water lines installed, communication equipment and IT devices arrive on site.

Day 6 (Jan 29): 20% of container houses installed, simultaneous work on HVAC, electrical, and IT hardware assembly, power testing, port planning, pre‑configuration.

Day 7 (Jan 30): More container houses installed, interior work continues, communication equipment begins three‑day on‑site debugging.

Day 8 (Jan 31): Concrete work finished, full interior power, IT equipment deployed and business‑level testing performed.

Day 9 (Feb 1): All container houses completed, road and medical infrastructure advanced, medical system development and debugging near completion.

Day 10 (Feb 2): Project completed, all systems debugged and handed over.

Key Highlights of the Value Stream

Multiple parallel and serial value streams: Tasks without strict dependencies were started early (e.g., land leveling before final designs, pre‑emptive power supply).

Extremely efficient processing time for each step: Leading industry firms handled each activity, ensuring technical excellence and business familiarity, resulting in near‑optimal cycle times.

Very short lead time from task initiation to completion: Waiting or idle time was virtually eliminated, with task start and finish occurring almost back‑to‑back.

High proportion of value‑added activities, minimal non‑value‑added work: Hour‑based progress monitoring and rapid communication kept waste to a minimum.

This article is the second part of a four‑part series on the DevOps case study; readers are encouraged to follow the public account for the remaining chapters.