Skip to content
QUNIAOPX
PREDICTIVE OPERATIONS FOR DATA CENTERS

SEE AHEAD.
ACT WITH
CONFIDENCE.

Anticipate the next load.
Make evidence-led decisions.

Understand what comes next across power, cooling and compute.
Connect response evaluation, safety checks and outcome verification.

Explore the platform ↓
QUNIA / OPX engine · LPM core technology
QUNIA / CONNECTED INTELLIGENCE01 — 04
From energy flows to the next operating stateSignals from power, cooling, compute and energy storage connect around three-dimensional server racks. Concept visualization, not live data. POWERPower demandCOOLINGThermal balanceCOMPUTEWorkload dynamicsESS / GRIDEnergy headroom QUNIA
READ THE FLOW. SEE WHAT’S NEXT.

Connected signals. Earlier insight.

Concept visualization
ONE PLATFORM. FOUR CONNECTED DOMAINS.
POWERCOOLINGCOMPUTEESS & GRID

See what comes next.
See it together.

Peak demand. Cooling headroom. GPU workloads.
Bring separate signals into one decision.

A change in one part of a data center changes operating conditions elsewhere. OPX is designed to forecast these connected states, compare response impacts and review what happens after execution.

CURRENT OPERATIONS

Operating from the current state

Check the status of individual systems
Respond after an alarm
Evaluate performance through retrospective reporting

WITH QUNIA

Preparing for the next state

Forecast connected conditions in advance
Compare scenarios to inform the response
Continuously compare forecasts with actual outcomes

From forecast to verification.
One operating workflow.

Explore the OPX workflow through its product screens.
Select a screen to learn more.

OPX / Overview
OPX Overview product concept screen
OVERVIEW

Today's conditions. Tomorrow's risks. One view.

See operating metrics, predicted peaks and pending decisions in one place, with connected conditions across power, cooling, compute and storage.

Product concept UI. Figures and facility names are illustrative and do not represent actual customer results or validated performance.

The same rise in demand.
A different basis for action.

Once you know the current readings,
what changes when you can also see future risk and the evidence behind a response?

Shared scenario

More batch jobs are driving up electricity demand. Storage is available, but a reserve must be maintained and jobs must finish on time.

Example: current-state operations

Check the readings.
Gather the context separately.

What is available
Current power demand, temperature, storage charge and active alarms
What still needs checking
How long load will rise, which jobs can move and whether enough charge will remain after discharge
Evaluating a response
The operator gathers system data and job schedules to compare options
After the action
Collect operating logs and measurements to assess the result
“We know the current state. We still need the evidence for the next decision.”
The workflow QUNIA aims to connect

Assess future risk and response constraints
in the same context.

What the design aims to show
The timing and range of the predicted peak, contributing variables and data freshness
What to check together
Projected load, remaining storage charge, job deadlines and headroom for each response
Evaluating a response
Review response options and constraint evidence side by side, then select and approve
After the action
Compare the forecast captured at approval with actual observations
“Understand why a response may be feasible—and what needs checking first.”

This example illustrates workflow differences. Forecasting and optimization capabilities vary by existing system configuration. QUNIA's deployment scope is defined through site integration and validation.

DECISION / RESPONSE COMPARISON

The conditions that change matter as much as the expected benefit.

Response optionIntended effectConditions that also changeEvidence needed for the decision
Discharge energy storageReduce grid demand during the peak windowLower remaining charge and additional recharge demand laterAvailable capacity, discharge limits, minimum charge and recharge plan
Reschedule batch jobsShift some load to another time windowCompletion time and load in later periodsFlexible jobs, completion deadlines and available resources
Combine both responsesShare the adjustment between storage and workloadsSeveral sets of constraints change at onceCombined simulation, individual constraints and recovery options

Illustrative review criteria, not calculated results or a ranking of recommendations.

BEFORE APPROVAL

Approval takes more
than a button.

Make the evidence clear before approval,
and evaluate outcomes against the same criteria afterward.

  1. Forecast evidenceData timestamp and gaps, prediction interval and assumptions
  2. Site constraintsLimits and their sources, projected post-action values and remaining headroom
  3. Execution conditionsEquipment and workloads in scope, permissions, timing, stop and recovery conditions
  4. Outcome verificationThe forecast at approval, actual observations, deviations and execution history

Decide how to respond
before the peak arrives.

Read changes in power, temperature and workloads together,
and connect response options with the evidence operators need.

01 INPUT

What is happening
right now?

Bring fragmented site signals
into one view.

Power demandZone temperatureWorkloadStorage charge
Existing BMS, DCIM and site systems
02 PREDICT

When and where
will risk increase?

Model the relationships between signals
to predict the next state and its uncertainty.

Peak timingThermal riskOperating headroomPrediction interval
LPM Predict the next state
03 COMPARE

Which response
fits the constraints?

Compare each option's expected effects
against the site's operating constraints.

Discharge energy storageAdjust workload timingReview cooling settings
OPX Compare responses · Check constraints
04 VERIFY

Did the approved action
have the intended effect?

Connect operator approval and execution status
with expected and observed outcomes.

Approval evidenceExecution historyOutcome comparison
QUNIA Operations · Verification
EXAMPLE / PEAK DEMAND RESPONSE

From “demand is rising”
to “consider this response.”

  1. Predict

    Projected demand is approaching the operating limit.

  2. Compare

    Assess storage discharge and workload adjustments together with their effects, charge limits and completion deadlines.

  3. Decide

    The operator reviews the conditions, approves a response and evaluates the changes that follow.

QUNIA connects forecasts, response evidence, operator decisions and outcomesin one workflow.

Explore LPM technology ↗

A conceptual example of the product workflow. Site integration and execution scope depend on the deployment stage and validation results.

Forecast through time.
Understand across space.

Where will risk emerge?
What would a response change?

The digital twin connects rack- and zone-level conditions with power flows. The experience is designed to compare the current state, predicted state and the state after a response.

People retain control.
Evidence stays clear.

Site constraints and approval procedures
sit at the center of the product experience.

01 / GUARDRAILS

Check against site-specific limits

The design incorporates constraints such as SLAs, contracted power, equipment limits and storage requirements into response evaluation.

02 / HUMAN APPROVAL

Expand authority in stages

Observe → Recommend → Supervised → Autonomous. The scope is agreed according to field validation and operating policies.

03 / AUDITABILITY

A record of decisions and outcomes

The experience connects recommendation, approval, execution and verification histories so that the decision process can be traced.

From one site
to an entire portfolio.

Connect the screens used in daily operations
within a shared context.

Built around your infrastructure.
Adapted to your operation.

Understand the systems. Assess the data.
Start with a scope you can validate.

01 / CONNECT

Assess data and operating conditions

Review existing management systems, data history, access permissions, security requirements and site-specific constraints together.

02 / OBSERVE

Start in Observe mode

Explore a read-only deployment that connects data and evaluates forecast quality without sending equipment commands. Agree on the duration and progression criteria for each site.

03 / EXPAND & VERIFY

Expand the operational scope

Use validation results and site policies to agree, step by step, on recommendations, approval-led operations and further integrations.

On-premises · Private environments · Existing system integrationsDeployment configuration and available features are agreed within the PoC scope.

Before you begin,
a few answers.

What is QUNIA?

QUNIA is a platform under development to understand data center energy flows and guide more efficient operations. OPX is its engine; LPM is its core technology.

Do we need to replace our BMS, BEMS or DCIM?

The approach is to add forecasting and decision workflows alongside existing operating systems. Integration feasibility depends on data access, interfaces and security requirements.

Does deployment start with automated control?

The proposed path starts with observation and forecast validation, then expands to recommendations and operator approvals as appropriate for the site. Automated execution requires separately agreed scope and conditions.

Are the savings and forecasts shown on the site actual results?

The screens are product concept designs. Figures and facility names are illustrative. Actual savings and predictive performance must be validated separately using data from the target site.

How is pricing determined?

Pricing depends on the site, connected systems, data scope, operating features and support requirements. We begin by defining the PoC objectives and evaluation criteria together.

Thinking about
the next operating decision.

View all posts ↗
LET’S BUILD THE NEXT OPERATION.

Prepare your site
for what comes next.

Explore the platform again ↑
OPX
OPX product concept screen

Product concept UI · Illustrative data

LET’S TALK OPX

Define the right PoC
for your operation.

Tell us what you would like to discuss and how to reach you. Our team will get back to you.

We collect your name, email, phone number (if provided) and message to answer your inquiry and arrange a meeting, and keep them for one year after the inquiry is resolved. You may decline, but we cannot receive your inquiry without consent.

QUNIA / BLOG