Liquid Cooling Data Centre Operations in Singapore: How to Control Requests, Approvals, and Escalations

Singapore’s new liquid cooling standard is a timely reminder that data centre operations are becoming more complex—not only at the engineering level, but also across everyday coordination and decision-making.

For operators, the practical question is straightforward: can facilities, engineering, sustainability, procurement, vendors, and service teams manage cooling-related work through consistent, visible processes?

A data centre operations workflow in Singapore can help answer that question. By replacing scattered email threads, spreadsheets, and informal escalation channels with structured requests, approvals, routing, and tracking, operators can create a clearer operating model for changing infrastructure requirements.

Why liquid cooling changes the operating model

Singapore’s IMDA announced Singapore Standard SS 726:2026, described as the world’s first standard for liquid cooling in tropical data centres. The standard is intended to support the adoption of liquid cooling technologies in tropical conditions while helping the data centre sector address growing energy demands, including those associated with increasingly compute-intensive artificial intelligence workloads.

The engineering implications are important. But the operational implications are equally relevant.

Liquid cooling may introduce or increase the need to coordinate:

• Cooling system change requests
• Planned maintenance and shutdown approvals
• Equipment and configuration updates
• Vendor access and service activities
• Incident escalation between facilities and IT teams
• Sustainability and energy-efficiency reporting inputs
• Post-incident reviews and corrective actions

These activities often involve different owners, approval levels, service providers, and operating schedules. A request that begins with an engineering team may require facilities approval, procurement input, vendor coordination, risk review, and documented closure.

When the process depends mainly on email, it can be difficult to determine which version of a request is current, who is responsible for the next action, whether an approval has been completed, or what evidence should be retained for future review.

Why this matters in Singapore and Southeast Asia

Singapore remains a significant data centre market and is continuing to manage the relationship between digital infrastructure growth, energy use, water efficiency, and sustainability objectives. In August 2026, EDB and IMDA provisionally allocated 200 megawatts of new capacity to four data centre operators through the second Data Centre Call for Application exercise.

That type of capacity expansion can increase operational complexity. As facilities become larger, more specialised, or more closely integrated with regional service networks, teams need processes that can work across organisational boundaries.

The same consideration applies to operators expanding across Southeast Asia. Regional teams may need to coordinate different sites, vendors, maintenance windows, internal approval structures, and reporting requirements. The specific technical environment may differ by facility, but the process questions are similar:

• How is a request submitted?
• Which information is mandatory before review?
• Who approves a change?
• What happens when an issue crosses team boundaries?
• How are overdue actions escalated?
• Where can managers see current workload and risk?

These are workflow management questions. They do not always require a large, bespoke software programme.

Operational workflows data centre teams should review

A useful review should begin with the processes that create the most coordination risk. For many operators, the following workflows are good starting points.

1. Cooling system change requests

A structured form can capture the affected site, equipment, proposed change, reason, risk considerations, requested timing, and supporting documents. The request can then be routed to the relevant engineering, facilities, and operational owners.

This creates a consistent intake process and reduces the chance that critical context is lost in a long email chain.

2. Maintenance and access approvals

Planned maintenance may involve internal teams, specialist contractors, equipment suppliers, and site access controls. A workflow can route the request for the appropriate approvals, record the maintenance window, assign follow-up actions, and show whether required steps have been completed.

3. Incident escalation

Cooling-related incidents can require rapid coordination between facilities, engineering, service operations, and management. An escalation workflow can capture the initial issue, assign ownership, set priority, notify the next responsible team, and track actions through resolution.

The aim is not to replace technical incident tools where those are already in place. Instead, a workflow management platform can support the business coordination surrounding the incident.

4. Vendor coordination

Data centre operators often depend on external providers for equipment, maintenance, inspections, and specialist support. A vendor request workflow can standardise the information required, route approvals, record commitments, and track completion without relying on a single employee’s inbox.

5. Sustainability reporting inputs

Energy and water-efficiency initiatives typically require information from several functions. A workflow can help request, validate, and consolidate operational inputs before they are used in internal reporting or management reviews.

6. Post-incident reviews

A post-incident process can assign review owners, collect findings, record corrective actions, and monitor due dates. This helps teams move from documenting an event to managing the follow-up work that results from it.

Where no-code workflow management fits

A no-code workflow platform is a business process digitisation tool for creating structured processes without developing a fully custom application for every use case.

For data centre operations, it can provide:

• Request intake: Use forms to collect consistent information at the start of a process.
• Configurable routing: Send requests to the right engineering, facilities, procurement, sustainability, or management owner.
• Approval control: Define approval steps based on request type, site, risk, value, or operational impact.
• Status tracking: Give teams a shared view of open, pending, approved, rejected, and completed work.
• Ownership and escalation: Make the next responsible person clear and flag overdue actions.
• Operational visibility: Help managers identify bottlenecks, recurring request types, and unresolved follow-up work.

This is particularly useful when processes change frequently. As operators learn from new cooling deployments, update internal controls, or introduce additional sites, a no-code approach can make it easier to adjust forms, routing, and approval logic.

How Qingflow may help

Qingflow is a no-code workflow platform and workflow management platform for requests, approvals, forms, routing, tracking, and operational visibility.

It may fit data centre teams that want to digitise coordination processes without starting with a lengthy custom software project. For example, an operator could use Qingflow to create a cooling system change request, route it through defined reviews, assign vendor or facilities actions, and provide managers with a current view of progress.

The value is not simply moving a paper form online. A well-designed workflow should clarify:

1. What information is needed before work begins.
2. Who owns each stage of the process.
3. Which decisions require approval.
4. What happens when a request is incomplete or delayed.
5. How the final outcome and follow-up actions are recorded.

Qingflow can also support a gradual approach. Teams may begin with one high-friction process—such as maintenance approvals or incident follow-up—then expand to related workflows once the operating model is clear.

Buyer checklist: what to evaluate

When assessing workflow software for data centre operations, consider whether it supports:

• No-code configuration that business and operations teams can manage
• Forms with the fields and attachments required for technical requests
• Routing across multiple teams, sites, and approval levels
• Clear ownership, due dates, and escalation rules
• Audit-friendly records of decisions and actions
• Dashboards or reports for operational visibility
• Easy changes as processes, sites, or responsibilities evolve
• Adoption by both technical and non-technical stakeholders
• Integration with existing systems where appropriate, without creating unnecessary complexity

The right choice will depend on each operator’s existing tools, governance model, and process requirements. The important point is to evaluate workflow capability as part of infrastructure operations—not as a separate administrative concern.

Frequently asked questions

What is a data centre operations workflow in Singapore?

It is a structured digital process for managing operational requests, approvals, incidents, maintenance, vendor coordination, and follow-up actions within Singapore-based data centre environments.

Does a workflow platform replace data centre monitoring or incident tools?

Not necessarily. Workflow software can complement technical monitoring and service management tools by managing the human coordination, approvals, ownership, and business follow-up around operational events.

Why use a no-code platform for cooling-related processes?

Cooling-related processes may change as equipment, policies, vendors, and operating practices evolve. No-code configuration can make it easier to update forms, routing, and approvals without commissioning a separate custom development project for every change.

When does Qingflow fit?

Qingflow may fit when teams need a practical way to digitise requests, approvals, routing, tracking, and visibility across facilities, engineering, procurement, sustainability, vendors, and management.

Want to see how this could work for your team? Request a walkthrough of Qingflow and discuss your data centre workflow.

Recent signals and sources

• Singapore launches world’s first liquid cooling standard for data centres in tropical climates — IMDA, 27 August 2026.
• Liquid Cooling in Tropical Data Centres — IMDA, 27 August 2026.
• Four data centre proposals selected as part of second Data Centre Call for Application — IMDA, 21 August 2026.