BOTHX Modular Data Center

BOTHX Modular Data Center

Technical FAQ: Configuration, Services & Delivery Conditions

Flagship Offerings:

• Integrated 40ft Container – 80 kW (Air Cooling)
• Integrated 40ft Container – 200 kW (Liquid Cooling)
• Customized Split Containers and Modular Auxiliary Function Combinations

What modules do you provide, and how can they be configured?

We decompose the data center into independently deliverable functional modules, which can be flexibly configured per project into single-container deployments, dual-container split systems, or multi-container scalable solutions.

• IT Container: Racks, enclosed aisle containment, air-cooling terminals (InRow / CRAH), liquid-cooling terminals (CDU / manifold), power distribution and lighting, security and access control, environmental sensors.
• Cooling Source Modules: Chillers / pump skids / plate heat exchangers, dry coolers or cooling towers, make-up water and chemical dosing systems, emergency water tanks (optional).
• Auxiliary Modules (modular options): UPS and batteries, power distribution and transformer interfaces, fire detection and suppression, remote monitoring and cybersecurity, noise reduction and vibration isolation.

What are the application boundaries between air cooling and liquid cooling?

Both solutions follow the same delivery logic. The key differences lie in cooling terminals and thermal management boundaries.

• 40ft 80 kW (Air Cooling): Designed for general-purpose computing and edge nodes. Enclosed aisles with air-cooling terminals as the primary solution, emphasizing rapid delivery, easy maintenance, and repeatable deployment.
• 40ft 200 kW (Liquid Cooling): Designed for high-density AI and HPC workloads. CDU and liquid distribution manifolds as the primary cooling method, with residual air cooling retained for non-liquid-cooled components and emergency backup.
• Unified Cooling Source for Air & Liquid: A common cooling source is provided, with liquid cooling as the primary path and air cooling as supplementary and fallback, reducing system duplication and interface complexity.

Under what conditions do you provide design, detailed engineering, and delivery services?

• Solution Phase (Quotation-Ready): System architecture, capacity and redundancy recommendations, preliminary layout and interface lists, risk register, BOM framework, and budgetary range.
• Detailed Engineering Phase (Production-Ready): Multidisciplinary drawings and calculation reports, finalized equipment lists and technical specifications, I/O lists and Cause & Effect matrices, construction interface drawings.
• Delivery Phase (Acceptance-Ready): FAT / SAT, commissioning and training, O&M manuals and spare parts packages; optional remote monitoring and integration with customer DCIM / NOC systems.

What is the minimum input required to obtain a “quotation-ready solution”?

• The clearer the inputs, the more effectively system boundaries, cost structure, and delivery timelines can be fixed in one iteration, minimizing rework.
• Total IT load (kW), number of racks, and power density distribution (AI/HPC workloads and liquid-cooling ratio).
• Target thermal criteria: supply air / supply & return water temperatures, allowable ΔT, and redundancy targets (N / N+1 / 2N).
• Deployment location (country / city) and constraints: noise limits, footprint and height, corrosion protection, shipping and lifting conditions.
• Power supply conditions: voltage level, single or dual feed, UPS and battery autonomy; customer acceptance and regulatory requirements.

How is monitoring / DCIM implemented? Can it integrate with customer platforms?

• Default Delivery – Lightweight O&M Monitoring (MVP): Local HMI with remote trending, alarms, and reporting; supports offline local operation (optional data backfill).
• Northbound Integration: Modbus TCP / BACnet IP / SNMP / API, with I/O points and naming conventions frozen per project.
• Full-Function DCIM: Asset management, work orders, capacity management, and multi-tenancy can be delivered as a separate expansion project.

Could fire protection or EPO mis-linkage cause unintended downtime? How are boundaries defined?

• Cause & Effect Matrix Frozen During Detailed Engineering: Fan shutdown, valve isolation, agent discharge, system reset, and alarm strategies are clearly defined for alarm, confirmed alarm, and discharge stages.
• EPO Tiering and Authorization: IT power-off and equipment shutdown are handled in layered logic, with clearly defined reset authority and controlled restart procedures to reduce the risk of unintended outages.
• These boundaries are used for design review, FAT/SAT acceptance, and O&M handover, ensuring consistent interpretation.

How do you ensure rapid installation and commissioning? What is required on site?

Standardized Interface Lists (power, network, make-up water, drainage, outdoor interfaces), I/O naming conventions, and FAT/SAT test templates enable repeatable and fast-track delivery.

Once site foundations and grounding, cabling and networking, and external cooling / water connections are completed, the system can enter power-on self-check and commissioning wizard phases (project-dependent).

Note:

The above represents a typical delivery baseline. Final scope, drawings, and BOM shall be frozen based on project-specific inputs, including load profile, location, local regulations, redundancy targets, and noise constraints.