Server room — insurance pack
One-page evidence bundle for an SMB property claim
When equipment in a server room is damaged by a heat or water event, the property insurer wants evidence the environment was within tolerance at the time, or at least that the operator attempted to maintain it. OpenSense's server-room vertical generates this evidence automatically.
This page describes what is in the bundle, how to ask for it, and how to use it in a claim.
What's in the bundle
A single PDF, generated by template = server_room_uptime, that
includes:
- Cover page. Site name, address, period covered, signature blocks for operator and (optional) loss adjuster.
- Uptime summary table. For each monitored channel: % of time in operating range, total minutes in alarm, count of distinct alarm events.
- Per-channel timeline. Stacked chart showing OK / WARN / ALARM bands over the period; the "site uptime" series at the bottom is the AND of every channel.
- Excursion log. Every alarm event during the period with: opened-at, value, closed-at, value, acknowledgement note.
- Sensor health. Uptime per device (% of expected samples received), data-gap timeline.
- Calibration record. Last calibration event per probe.
- Configuration snapshot. Operating ranges, grace periods, and silence-window history during the period — so the adjuster can confirm the alarms were not over-silenced.
How to render it
Manually for a specific event:
POST /v1/reports
{
"site_id": "site_4f3c",
"template": "server_room_uptime",
"period": {
"from": "2026-04-01T00:00:00+02:00",
"to": "2026-04-30T23:59:59+02:00"
},
"language": "en",
"options": {
"include_insurance_cover": true,
"claim_reference": "AXA-2026-04-XXXXX"
}
}
include_insurance_cover adds an extra first page with the
customer's policy number, building address, and a free-text
"incident summary" the operator fills in before sending.
How it is used in a claim
In our customer base so far, two patterns:
Pattern 1 — confirm spec compliance, claim equipment
The AC failed at 03:00 Sunday. By 09:00 Monday the racks reached 35 °C, two switches cooked. The insurer paid for the switches; the PDF showed the environment had been within ASHRAE TC 9.9 spec for the prior 11 months, an OpenSense alarm fired at 03:14 Sunday morning, an SMS escalation pinged on-call at 03:25, the operator escalated to the AC vendor, the AC vendor responded by 08:00 Monday. The PDF made the operator's diligence visible; the claim went through quickly.
Pattern 2 — water event, exonerate cooling
A water-cooling line burst on the floor above; water reached two racks. The flood sensor fired at 02:00. The PDF showed temperature and humidity were nominal before the water event — establishing that the cause was external (the upstairs leak), not internal cooling failure. The insurer pursued the upstairs tenant's insurance rather than denying the claim.
What it does not do
- It does not claim for you. OpenSense is evidence; the claim is between you and your insurer.
- It is not a fire / smoke detector. We have no smoke sensor integration today. For a fire claim, your fire-alarm provider is the relevant evidence source.
- It is not a video record. If the insurer wants security footage, OpenSense does not have it.
Pre-incident hygiene
For the PDF to be useful, certain things must be in order before the incident:
- The site's vertical is
server-room(or it has the right channels configured manually). - Alarms are not over-silenced. A site with a 24×7 silence window on the temperature alarm makes the PDF useless.
- Acknowledgement notes are written for past events. A clean log with no notes looks like the system is unread.
- The insurer's policy number is pre-entered on the site (so the cover page renders correctly).
Set up these things during onboarding (see onboarding checklist). It takes 10 minutes; the value is real only when you need it.
A note for MSPs
If you run a server-room monitoring service for SMB customers, the PDF is also the deliverable for your quarterly customer audit: "here is the evidence that I kept your closet in spec".
Bundle it with your invoice. Customer renewal rates we see go up.