Robometic
Scope an assessmentEnquire

Service detail

See the evidence behind a maintenance decision.

A condition change is the start of the question, not the answer. Connect it to operating load, cooling dependencies, constraints and the checks required before the site acts.

Scope an assessment Try the scenario lab

Evidence chain

From operating evidence to engineering review.

The assessment moves from operating context to a reviewable question. Each step records what is known, what is missing and who must decide. A gap stays visible in the pack instead of becoming an assumption.

Illustrative evidence chain for a cooling maintenance decision Six linked evidence steps: operating context, condition observation, baseline comparison, dependency check, unknowns recorded, and a review question. Lower callouts show the shared dependency, the logged gap and the authorised site decision. ILLUSTRATIVE EVIDENCE CHAIN NOT A CAPACITY OR APPROVAL RESULT 01 Operating context Load, state and the site record. What was running? What changed? 02 Observation Condition evidence from the equipment. What is the signal? What is missing? 03 Baseline Compare with the equipment's own past. Same basis? Same conditions? 04 Dependency check Headers, pumps, controls and power. What else moves? Who shares it? 05 Unknowns Valve positions, records, authority. Recorded, not estimated away. 06 Review question A bounded question for the site team. Who decides? What is next? SHARED DEPENDENCY SC-01 controls and ELEC-01 feed can affect several cooling paths. LOGGED GAP The pack states what the site cannot answer from current data. AUTHORISED Site team decides.
Illustrative structure. The chain does not establish capacity, redundancy, a failure probability or an approved isolation.
Closer motion study. Authored from the same illustrative cooling model. The animation illustrates path and dependency only. It is not a live reading, a design drawing or a simulation result.
  • 01Evidence goes in as it is found, including the gaps.
  • 02Dependencies are checked before any consequence is described.
  • 03The authorised site team receives the question and the limits.

01 / Assessment

Observe the equipment in its operating context.

A reading without context is a number. The assessment relates condition observations to the load, the operating state, the maintenance history and the cooling path the equipment supports.

Condition

What the equipment is doing now and how that compares with its own baseline. Existing records first; targeted observation where a defined gap remains.

Dependencies

Which loads depend on the equipment, which paths and controls are shared, and what else changes when the proposed work takes it out of service.

Operating evidence

Current load, operating states, constraints and the site's own records. Missing evidence is recorded, not filled with an assumption.

The flagship question. Can this cooling equipment be taken out of service under today's operating conditions? The answer is assembled from condition, dependencies, remaining capacity, load, constraints, required checks and authorisation.

02 / Watch

Keep the evidence current after the assessment.

Critical Cooling Watch is a continuation for selected equipment. It reviews condition changes against the equipment's own pattern and the operating state, then routes a notice to the site with the evidence attached.

A notice is not an alarm and not a diagnosis. It is a prompt to look, with the evidence and the checks that may be useful. The site team decides what it means.

Human-reviewed evidence. Site-controlled action.

Condition notices are reviewed before reaching the site. Each notice identifies the observed change, its operating context, possible explanations and the checks to consider. The site decides what action, if any, is appropriate.

Equipment that suits it

Selected pumps, motors, fans and other suitable equipment where a condition-change question is worth watching. Not every component in the cooling chain.

What it does not do

It does not replace BMS alarms or protection, and it does not turn vibration data into a diagnosis of a chiller, a CDU or a whole cooling chain.

03 / Verification

Did the maintenance change what it set out to change?

Pre/post verification compares the same points on the same operating basis. It is evidence about the intervention, not a grade of the whole cooling system.

Before the work

The condition evidence, operating state and measurement basis are recorded. Open questions are listed so the post-work review knows what to look for.

After the work

The same points are compared under comparable conditions. The result can show improvement, no change or a remaining concern. Each is a useful outcome.

A verified change in one measurement does not establish the capacity of the remaining cooling path. That question needs its own evidence and engineering review.

04 / Site ownership

The site team still owns the work.

Operator rounds, BMS alarms, protection settings, permit-to-work and change control remain with the site. Robometic provides evidence and a review pack. It does not take control or authorise the intervention.

How the work is done Read the sample report

Where the evidence stops.

Capacity and operating load
The assessment can describe observed conditions and the questions that remain. It does not convert them into a remaining-capacity number or a redundancy rating.
Equipment condition and reliability
Condition evidence can support a maintenance decision. It does not produce a quantitative probability of failure.
Maintenance authorisation
Isolation is authorised by the site under its own procedures. The assessment can set out dependencies, constraints and checks. It cannot approve the work.
BMS alarms and protection
Those systems remain in service. The assessment is an advisory evidence layer alongside them.
Redundancy classification
The work does not confer or imply a certification, a Tier classification or a redundancy rating.