Short answer
HVAC service data combines job records (equipment, symptom, readings, parts, outcome) with video of technicians inspecting, measuring and repairing heating and cooling equipment. Contractors may hold records; useful video is mostly commissioned. It supports diagnosis and task understanding, but a humanoid still needs robot or teleoperation data to learn the physical work.
What makes HVAC distinct
HVAC work mixes three kinds of activity that rarely appear together in one trade. There is physical access work: climbing to rooftops, reaching into attics and crawlspaces, removing panels and moving filters, coils and blower assemblies. There is measurement-driven diagnosis: reading pressures, temperatures, airflow and electrical values and comparing them to expectations. And there is seasonal, high-volume routine work: filter changes, cleaning and tune-ups that dominate service calendars.
For a buyer, the measurements matter as much as the video. A technician connecting gauges and reading a result is making decisions from numbers that the camera may not capture. The data that best supports diagnosis reasoning therefore pairs a recording with the logged readings and the decision that followed.
HVAC is one of several facilities trades. For the broader building-service view see facility maintenance tasks; this page stays with heating, cooling and ventilation. The cluster overview is the maintenance, repair and tool-use data hub, and the full section is mapped in the humanoid training data guide.
Task anatomy
A routine service call usually follows a pattern, though details differ by equipment type and region:
- Arrival and check-in, including reviewing the equipment history.
- Visual and operational check: filters, coils, drains, belts, burner or compressor operation.
- Measurement: electrical, temperature, pressure or airflow readings with instruments; see analog gauge and meter reading.
- Diagnosis: comparing readings to expected ranges and fault patterns.
- Repair or adjustment: replacing a part, cleaning, tightening or recharging.
- Verification and closeout: re-measure, document and brief the customer.
Failure modes include misread gauges, wrong part orders, repeat visits for the same fault and unsafe steps skipped. Recording regulated refrigerant or combustion work raises safety and qualification questions that a supplier should be able to answer; this page does not state what any rule requires.
What each type of data covers
| Data | Covers | Does not cover |
|---|---|---|
| Job records | Equipment type, symptom, parts, labor, outcome | Technique, motion |
| Instrument readings | Evidence for diagnosis | Who decided what, unless logged |
| Technician video | Access, tool use, panel removal, reassembly | Forces, torque, robot actions |
| Gauge or display photos | Reading and display recognition | Behavior of the system |
| Preventive maintenance checklists | Routine task coverage | Execution detail |
| Callback labels | Whether the first fix worked | Why not, unless explained |
See work order histories and first-time-fix and callback labels for how records link to outcomes, and preventive maintenance checklists for scheduled work.
The published reference, and its limits
MaintNet provides logbook data from aviation, automotive and facilities domains, together with abbreviation lists, termbanks and pre-processing tools (Akhbardeh et al., 2020). It contains no HVAC service data, and this page does not claim it covers heating or cooling work. Treat it only as a reference for normalizing shorthand and building termbanks. HVAC job notes will carry their own shorthand, equipment model codes and unit abbreviations that a buyer must resolve with the supplier.
Existing versus commissioned
Contractors often hold job records in field-service software, but they seldom record video. Footage that exists may be chest-camera recordings made for training or liability, or customer-facing photos. Commissioned recordings can be designed: technicians perform defined tasks on rooftop units, furnaces or air handlers, wearing cameras, while instrument readings are logged and annotated. This route requires site access, safety planning and consent; see recording in hazardous spaces and the comparison in existing footage versus commissioned recording.
Limits: what this data cannot support
It cannot train control. Lifting a heavy motor, reaching behind a coil, tightening a fitting in a confined cabinet or handling a sheet-metal panel with sharp edges requires closed-loop robot or teleoperation data with joint states, actions and often force sensing. Video and records alone do not provide them.
It cannot show hidden state. Pressure, current and temperature appear only if logged or if gauges are in frame and legible.
It is regionally and seasonally biased. Equipment types and failure modes depend on climate and building stock. A contractor's records may reflect mostly summer cooling failures or winter heating failures.
It rarely shows rare faults. Most calls are routine; difficult diagnoses are underrepresented unless sought deliberately.
Illustrative record and capture design
The following is an illustrative design with synthetic values, not an existing dataset.
# Illustrative only: synthetic values, not a real or available dataset
job:
job_id: job_00512
equipment: {type: rooftop_unit, age_band: "10-15 yrs", site_id: site_021}
symptom: "not cooling"
readings: # logged by technician or instrument
- {name: supply_air_temp, value: "recorded", unit: degF, t: "00:12:30"}
- {name: return_air_temp, value: "recorded", unit: degF, t: "00:12:45"}
diagnosis: "text plus normalized fault code"
parts: [part_class_A]
outcome: fixed_first_visit
video:
cameras: [head_mounted, wrist_or_chest, fixed_overview]
sync_with_readings: shared_clock
safety_notes: "supplier's own procedure, referenced not restated"
consent: technician release; customer premises permission recorded
Quality and acceptance criteria
You decide the thresholds. Useful checks: readings are time-aligned with video; gauges in frame are legible at the capture resolution; each job links to equipment type and outcome; callbacks are linked to the original visit; and shorthand is mapped to a termbank. Hold out sites and equipment types for evaluation, not random clips from one job.
Permissions and provenance
HVAC calls take place in homes and businesses. Records name customers and addresses; video can show interiors, people and security systems, and rooftop recordings can show neighboring property. Ask what notice customers gave, whether the contractor serves commercial clients under confidentiality terms, who owns the records if work was subcontracted for another company and whether technicians were told how recordings might be used. Blurring faces does not by itself settle permission. See worker consent and identifiable people. This is not legal advice.
Questions to ask suppliers
- Which equipment types and building types dominate your jobs?
- Do records capture instrument readings, and in what form?
- Are symptoms, diagnoses and parts structured or free text?
- Is there any existing video, and what was it recorded for?
- Are callbacks linked to original jobs?
- What qualifications do the technicians who might be recorded hold, and how are safety steps handled on camera?
- Do you subcontract for other firms, and who owns those records?
- What notice have customers received about recordings or data use?
- Could technicians narrate diagnostic reasoning during commissioned sessions?
Discuss your requirements
If you need HVAC service records or recordings, describe the equipment types, measurements and permitted uses to SourceX. SourceX looks for US businesses that hold suitable material, checks the data and the supplier's licensing permissions, and coordinates the license and delivery. If no existing asset fits, SourceX can scope a commissioned collection of new recordings. A request does not guarantee a match. Related pages: field service maintenance records and the physical-world collection path.
Describe the workplace demonstration data your robotics project needs
Sources
- MaintNet: A Collaborative Open-Source Library for Predictive Maintenance Language Resources — facilities-domain maintenance language resources, as a text-normalization reference only.