A useful monitoring review begins with the conditions your team needs to investigate and the decisions it needs to make. Bring one recent operating problem, the equipment involved and the records available at the time. Those details give a supplier something specific to assess and give your team a way to judge the proposed coverage.
Describe the decision and the equipment
Write the requirement as an operating task. For example: “When this server reports a sustained temperature change, the on-call engineer needs enough context to decide whether to inspect the machine or ask facilities to inspect its surroundings.” This is an illustrative requirement; the duration, limits and response need to be set for the actual equipment.
List the host, rack position, relevant cooling equipment and people responsible for each. Identify the decision the engineer can make and the additional evidence needed before authorizing work. Separate an initial investigation from any maintenance or control action that requires another person’s approval.
Keep the scope small enough to examine. A specific row, equipment type or recurring investigation gives the review a concrete starting point.
Inventory the observations already available
For each condition, record its source: an operating-system interface, device management tool, existing building system, physical instrument or manual inspection. Include the reported field, unit, equipment identifier, sampling interval and permissions needed to read it. Ask for an example record with sensitive details removed.
Check what the value actually represents. A processor temperature, a rack inlet measurement and a room sensor describe different locations. Record those locations explicitly. If a measurement cannot be obtained on the installed model or with the permitted account, mark it unavailable and assign someone to investigate the gap.
Also record how missing, stale and failed readings appear. A reviewer needs to distinguish an unchanged measurement from a collector that stopped reporting.
Specify the physical measurements still needed
A measurement requirement should name the quantity, location, expected range and accuracy needed for the decision. For energy monitoring, the U.S. Department of Energy’s design guide recommends establishing benchmarking goals before selecting measured values. It also calls for specifying instrument accuracy and calibration status. That helps prevent a team from selecting instruments before deciding what the resulting measurements must establish.
Ask the facilities team to document installation restrictions, permitted access and existing instrumentation. Include conditions that may limit a proposed sensor location. A supplier should explain how the proposed measurement relates to the operating question and identify any additional investigation needed before installation.
Keep an explicit list of unanswered questions. A statement such as “the current record contains no pump-seal measurement” is a useful gap to investigate; it does not establish which sensing method will work.
Agree on the record and the response
Use the following questions in the review. Each should produce a recorded answer or a named follow-up owner.
- Which equipment identifier and physical location will accompany each observation?
- Which timestamp describes the event, and which describes collection? How will clock uncertainty be shown?
- How long must records remain available for the investigations the team actually performs?
- Who can read the records, change collection settings and approve access?
- Who receives a finding, what initial check do they perform, and where do they record the outcome?
- What happens during a collection interruption, including how missing coverage is reported?
Apply these questions to the example incident. Walk through the available records with the person who would receive the finding. Note any step that still depends on an undocumented spreadsheet, inaccessible system or unidentified equipment.
Use a representative installation to check coverage
Before accepting a monitoring proposal, agree on a limited evaluation using representative equipment and authorized access. List the observations expected, their source fields and the evidence needed to show they arrive with the correct identity and time. Include a permitted way to check how unavailable data is reported. Record coverage gaps and decide who will resolve each one.
Valen Systems has built machine-level software for Arcturus and is developing sensors for conditions the computer cannot report, starting with power delivery and pump-seal condition where non-invasive monitoring is practical. Arcturus’s machine observation coverage depends on the equipment and available permissions. A review should establish that coverage for your installation and identify physical measurements that still need investigation.
Bring your equipment list, one operating example and any existing measurement records to a monitoring discussion. We can use those materials to examine your requirements and the scope of a suitable evaluation.
Sources
- U.S. Department of Energy — Best Practices Guide for Energy-Efficient Data Center DesignPublication date not stated. Retrieved October 17, 2026.
- Arcturus DCIMPublication date not stated. Retrieved October 17, 2026.