Tag: data center

HOPE OF THE NEXT

Posted on by lechuck park

Hope to jump

This image visualizes humanity’s endless desire for ‘difference’ as the creative force behind ‘newness.’ The organic human brain fuses with the logical AI circuitry, and from their core, a burst of light emerges. This light symbolizes not just the expansion of knowledge, but the very moment of creation, transforming into unknown worlds and novel concepts.

Data Center Operantions

Posted on by lechuck park

Data center operations are shifting from experience-driven practices toward data-driven and AI-optimized systems.
However, a fundamental challenge persists: the lack of digital credibility.

  • Insufficient data quality: Incomplete monitoring data and unreliable hardware reduce trust.
  • Limited digital expertise of integrators: Many providers focus on traditional design/operations, lacking strong datafication and automation capabilities.
  • Absence of verification frameworks: No standardized process to validate or certify collected data and analytical outputs.

These gaps are amplified by the growing scale and complexity of data centers and the expansion of GPU adoption, making them urgent issues that must be addressed for the next phase of digital operations.

Numbers about power

Posted on by lechuck park

kW (Instantaneous Power) ↔ UPS (Uninterruptible Power Supply)

UPS Core Objective: Instantaneous Power Supply Capability

  • kW represents the power needed “right now at this moment”
  • UPS priority is immediate power supply during outages
  • Like the “speed” concept in the image, UPS focuses on instantaneous power delivery speed
  • Design actual kW capacity considering Power Factor (PF) 0.8-0.95
  • Calculate total load (kW) reflecting safety factor, growth rate, and redundancy

kWh (Energy Capacity) ↔ ESS (Energy Storage System)

ESS Core Objective: Sustained Energy Supply Capability

  • kWh indicates “how long” power can be supplied
  • ESS priority is long-term stable power supply
  • Like the “distance” concept in the image, ESS focuses on power supply duration
  • Required ESS capacity = Total Load (kW) × Desired Runtime (Hours)
  • Design actual storage capacity considering efficiency rate

Complementary Operation Strategy

Phase 1: UPS Immediate Response

  • Power outage → UPS immediately supplies power in kW units
  • Short-term power supply for minutes to tens of minutes

Phase 2: ESS Long-term Support

  • Extended outages → ESS provides sustained power in kWh units
  • Long-term power supply for hours to days

Summary: This structure optimally matches kW (instantaneousness) with UPS strengths and kWh (sustainability) with ESS capabilities. UPS handles immediate power needs while ESS ensures long-duration supply, creating a comprehensive power backup solution.

With Claude

Data Center Mgt. System Req.

Posted on by lechuck park

System Components (Top Level)

Six core components:

  • Facility: Data center physical infrastructure
  • Data List: Data management and cataloging
  • Data Converter: Data format conversion
  • Network: Network infrastructure
  • Server: Server hardware
  • Software (Database): Applications and database systems

Universal Mandatory Requirements

Fundamental requirements applied to ALL components:

  • Stability (24/7 HA): 24/7 High Availability – All systems must operate continuously without interruption
  • Performance: Optimal performance assurance – All components must meet required performance levels

Component-Specific Additional Requirements

1. Data List

  • Sampling Rate, Computing Power, HW/SW Interface

2. Data Converter

  • Data Capacity, Computing Power, Program Logic (control facilities), High Availability

3. Network

  • Private NW, Bandwidth, Architecture (L2/L3, Ring/Star), UTP/Optic, Management Include

4. Server

  • Computing Power, Storage Sizing, High Availability, External (Public Network)

5. Software/Database

  • Data Integrity, Cloud-like High Availability & Scale-out, Monitoring, Event Management, Analysis (AI)

This architecture emphasizes that stability and performance are fundamental prerequisites for data center operations, with each component having its own specific additional requirements built upon these two essential foundation requirements.

With Claude

Temperate Prediction in DC

Posted on by lechuck park

Overall Structure

Top: CFD (Computational Fluid Dynamics) based approach Bottom: ML (Machine Learning) based approach

CFD Approach (Top)

  • Basic Setup:
    • Spatial Definition & Material Properties: Physical space definition of the data center and material characteristics (servers, walls, air, etc.)
    • Boundary Conditions: Setting boundary conditions (inlet/outlet temperatures, airflow rates, heat sources, etc.)
  • Processing:
    • Configuration + Physical Rules: Application of physical laws (heat transfer equations, fluid dynamics equations, etc.)
    • Heat Flow: Heat flow calculations based on defined conditions
  • Output: Heat + Air Flow Simulation (physics-based heat and airflow simulation)

ML Approach (Bottom)

  • Data Collection:
    • Real-time monitoring through Metrics/Data Sensing
    • Operational data: Power (Kw), CPU (%), Workload, etc.
    • Actual temperature measurements through Temperature Sensing
  • Processing: Pattern learning through Machine Learning algorithms
  • Output: Heat (with Location) Prediction (location-specific heat prediction)

Key Differences

CFD Method: Theoretical calculation through physical laws using physical space definitions, material properties, and boundary conditions as inputs ML Method: Data-driven approach that learns from actual operational data and sensor information for prediction

The key distinction is that CFD performs simulation from predefined physical conditions, while ML learns from actual operational data collected during runtime to make predictions.

With Claude

TCS (Technology Cooling Loop)

Posted on by lechuck park

This image shows a diagram of the TCS (Technology Cooling Loop) system structure.

System Components

The First Loop:

  • Cooling Tower: Dissipates heat to the atmosphere
  • Chiller: Generates chilled water
  • CDU (Coolant Distribution Unit): Distributes coolant throughout the system

The Second Main Loop:

  • Row Manifold: Distributes cooling water to each server rack row
  • Rack Manifold: Individual rack-level cooling water distribution system
  • Server Racks: IT equipment racks that require cooling

System Operation

  1. Primary Loop: The cooling tower releases heat to the outside air, while the chiller produces chilled water that is supplied to the CDU
  2. Secondary Loop: Coolant distributed from the CDU flows through the Row Manifold to each server rack’s Rack Manifold, cooling the servers
  3. Circulation System: The heated coolant returns to the CDU where it is re-cooled through the primary loop

This is an efficient cooling system used in data centers and large-scale IT facilities. It systematically removes heat generated by server equipment to ensure stable operations through a two-loop architecture that separates the heat rejection process from the precision cooling delivery to IT equipment.

With Claude

Data Center Digitalization

Posted on by lechuck park

This image presents a roadmap for “Data Center Digitalization” showing the evolutionary process. Based on your explanation, here’s a more accurate interpretation:

Top 4 Core Concepts (Purpose for All Stages)

  • Check Point: Current state inspection and verification point for each stage
  • Respond to change: Rapid response system to quick changes
  • Target Image: Final target state to be achieved
  • Direction: Overall strategic direction setting

Digital Transformation Evolution Stages

Stage 1: Experience-Based Digital Environment Foundation

  • Easy to Use: Creating user-friendly digital environments through experience
  • Integrate Experience: Integrating existing data center operational experience and know-how into the digital environment
  • Purpose: Utilizing existing operational experience as checkpoints to establish a foundation for responding to changes

Stage 2: DevOps Integrated Environment Configuration

  • DevOps: Development-operations integrated environment supporting Fast Upgrade
  • Building efficient development-operations integrated systems based on existing operational experience and know-how
  • Purpose: Implementing DevOps environment that can rapidly respond to changes based on integrated experience

Stage 3: Evolution to Intelligent Digital Environment

  • Digital Twin & AI Agent(LLM): Accumulated operational experience and know-how evolve into digital twins and AI agents
  • Intelligent automated decision-making through Operation Evolutions
  • Purpose: Establishing intelligent systems toward the target image and confirming operational direction

Stage 4: Complete Automation Environment Achievement

  • Robotics: Unmanned operations through physical automation
  • Digital 99.99% Automation: Nearly complete digital automation environment integrating all experience and know-how
  • Purpose: Achieving the final target image – complete digital environment where all experience is implemented as automation

Final Goal: Simultaneous Development of Stability and Efficiency

WIN-WIN Achievement:

  • Stable: Ensuring high availability and reliability based on accumulated operational experience
  • Efficient: Maximizing operational efficiency utilizing integrated know-how

This diagram presents a strategic roadmap where data centers systematically integrate existing operational experience and know-how into digital environments, evolving step by step while reflecting the top 4 core concepts as purposes for each stage, ultimately achieving both stability and efficiency simultaneously.

With Claude