Worked examples

Three cooling decisions, traced through the evidence.

Each example follows one maintenance question from the input observations through the dependency, the checks, a worked engineering scenario, the unresolved evidence and the next site decision. Nothing here is a customer result.

Illustrative examples with authored inputs. Not based on a customer installation or measured facility performance.

Example system. An illustrative primary chilled-water loop with three pumps. The sample report is a separate illustrative assessment; its observations are not the records for these scenarios. Units. Flow L/s, header pressure kPa, vibration mm/s RMS, temperature C, power kW. Timestamps UTC. Boundary. The authorised site team keeps isolation, switching and permit authority.

How to read a run.

Input observations lead to a dependency question, then to checks, a run result, the evidence still missing and a practical next site decision. A run can end in further checks, a dependency review or a reduced observation with follow-up. It never ends in an isolation approval.

Example 01: pump deterioration and proposed isolation. Increased demand, 104 L/s.

Illustrative exampleWorked engineering scenario

Pump deterioration before a proposed isolation at increased demand.

P-01 shows a rising drive-end vibration signal. The maintenance proposal is to isolate P-01 for a bearing inspection and leave P-02 in duty. Cooling demand has moved from 88 to 104 L/s in the same window.

The maintenance questionCan P-01 be isolated for a bearing inspection while P-02 carries the loop at 104 L/s under the conditions recorded in this window?
Asset focusP-01, with P-02 as the remaining path
Window2 Jun 2026 08:00 to 10 Jun 2026 17:00 UTC
Binding dependencyCommon suction and discharge headers; SC-01 sequence; ELEC-01 feed
Input classAuthored example readings, not site measurements
Example one: P-01 proposed isolation and P-02 remaining path Cooling loop with two chillers, three parallel pumps and isolation valves V-01 to V-06, supply and return headers, three CRAH units with branch valves BV-01 to BV-03, rack zones A and B, and shared controls SC-01 and feed ELEC-01. P-01 and P-02 are highlighted. V-01 and V-02 are marked as the proposed P-01 isolation valves. A measurement marker sits on the P-02 discharge. FOCUS: PROPOSED P-01 ISOLATION P-02 101 L/s at 232 kPa single point, 10 Jun 14:00 SC-01: one lead/lag selector and one DP control output ELEC-01: shared feed covers P-02 and P-03 unverified valve position
Trace: the proposed P-01 isolation, the P-02 point used for the remaining-path reading, and the SC-01 and ELEC-01 paths that one pump cannot avoid sharing. Schematic, not an engineering design.
Supply Return Controls dependency Electrical dependency Isolation or branch valve System boundary

Scenario result

Further checks required

P-02 was recorded at 101 L/s and 232 kPa; loop demand is 104 L/s. The operating points are not matched, and valve, sequence and electrical checks remain open.

Observed change
P-01 vibration 3.4 mm/s RMS; bearing housing 4 C above its own baseline; no BMS alarm.
Demand basis
104 L/s loop flow for the proposed one-pump duty. Recorded window: 88 to 104 L/s at 214 to 206 kPa header differential pressure; the P-02 point has a different pressure basis.
Remaining-path reading
P-02 measured 101 L/s at 232 kPa. Authored example input, one point.
Operating-point comparison
The operating points are not matched. Reconcile measurement locations, pressure basis, valve positions, pump performance and control state before assessing remaining-path capability; these readings do not establish a capacity shortfall or surplus.
Checks recorded
0 of 5. Valve, sequence and electrical evidence all remain part of the decision.
Site authority
Isolation remains with the authorised site team under its permit and change control.

Checks before a decision

  • C1 open: Measure P-02 flow and head at 104 L/s with a temporary point on the same basis as the P-01 observations.
  • C2 open: Verify V-01 and V-02 positions, tightness and the bypass path with the site engineer.
  • C3 open: Confirm the SC-01 lead/lag sequence and the differential-pressure set point for one-pump duty.
  • C4 open: Confirm the ELEC-01 feed and transfer path for P-02 and P-03.
  • C5 open: Walk the isolation, abort and restoration procedure with the authorised person.
Next site decisionHold the isolation request until C1 to C5 are complete and reviewed, including the electrical feed check (C4) and the permit, abort and restoration walk (C5), and until the site has reviewed the result. The site may continue condition monitoring and plan a bearing inspection under its own permit in the meantime.

Input observations

What the site already holds, before any new work. These are the inputs the run compares.

AssetReadingTimestampProvenance
P-01Drive-end vibration rose from 2.1 to 3.4 mm/s RMS over nine days10 Jun 2026 17:00Temporary vibration point, daily sample
P-01Bearing housing 4 C above its own baseline on the last four days10 Jun 2026 17:00Existing RTD via BMS, hourly mean
P-01VFD output 47.2 kW at 104 L/s loop flow; no BMS alarm reached10 Jun 2026 14:00BMS trend export
LoopFlow moved from 88 L/s to 104 L/s; header DP 214 to 206 kPa10 Jun 2026 14:00FT-01 and DP-01, 5-minute means
P-02Full-load performance test dated 14 Nov 2024; no current full-load record10 Jun 2026 09:00Maintenance record review

Evidence provenance

  • BMS trend export: loop flow FT-01, header DP-01, VFD output on P-01.
  • Temporary vibration point on the P-01 drive end, one daily sample.
  • P-01 bearing housing temperature from the existing RTD, hourly mean.
  • Maintenance records: P-02 last full-load performance test dated 14 Nov 2024.
  • Control narrative revision 4 and the BMS point list.

Dependency map

HydraulicP-01, P-02 and P-03 discharge into a common header. A common suction header and the return path are shared.
ControlSC-01 holds the lead/lag selector and the differential-pressure control output for all three pumps.
IsolationV-01 and V-02 are the proposed isolation valves for P-01. Their position and tightness were not verified in this window.
ElectricalP-02 and P-03 share the ELEC-01 feed and transfer path. The path was not assessed.
LoadThe loop serves CRAH-1 to CRAH-3 and rack zones RZ-A and RZ-B. IT load distribution was not verified.

Limits that stay in force

  • The run compares authored example inputs. It is not a capacity rating, a failure probability or a validated simulation.
  • One P-02 flow reading does not establish performance across the demand range or over time.
  • The run does not authorise isolation. Site procedures, alarms and protection remain in service.

P-01 drive-end vibration

Daily sample, 2 to 10 Jun 2026. Event marker at the point where the isolation proposal was raised. Unit: mm/s RMS.

Chart data table, same numbers as the plot
P-01 drive-end vibration, mm/s RMS, UTC
TimestampValueEvent
2 Jun 2026 08:002.1
3 Jun 2026 08:002.3
4 Jun 2026 08:002.5
5 Jun 2026 08:002.6
6 Jun 2026 08:002.8
7 Jun 2026 08:003.0
8 Jun 2026 08:003.1
9 Jun 2026 08:003.3
10 Jun 2026 17:003.4Isolation proposal raised

Loop flow against the demand basis

Five-minute means, 2 to 10 Jun 2026. The last marker is the 104 L/s demand basis used for the proposed isolation. Unit: L/s.

Chart data table, same numbers as the plot
Loop flow at FT-01, L/s, UTC
TimestampValueEvent
2 Jun 2026 08:0088
6 Jun 2026 12:0090
8 Jun 2026 12:0096Demand rising
9 Jun 2026 12:00101
10 Jun 2026 14:00104104 L/s demand basis

Unresolved evidence

  • The remaining flow margin of the P-02 path at 104 L/s is not established.
  • Valve tightness and the actual changeover sequence have not been tested under load.
  • P-02 full-load performance and its maintenance history need review before it is treated as the duty pump.
  • IT load distribution across the CRAH units is not verified.

What the run would change on site

It turns the isolation request into a short, owned check list. C1 and C2 close the first question: whether P-02 can carry the loop and whether the isolation valves actually isolate. C3 and C4 test the two shared paths that the BMS drawing does not show. Until then the request stays open, and condition monitoring continues under the site's own plan.

This is a practical next step. The checks will show what the condition is.

These examples are authored to show the shape and depth of an evidence pack. The readings, records and site names are example inputs. They are not Robometic customers, deployments or measured results, and they do not indicate how a real site would behave. Any assessment is scoped to the site, the system and the question in writing before work starts.

From example to decision

Bring one cooling system and one maintenance question.

We will confirm whether an assessment can answer it, what evidence the site already holds and what the authorised team would receive.