Independent elevator service company, maintenance and callback history

Summary

Fourteen years of maintenance visits, trouble calls, test records and modernization proposals from one independent US elevator service company with a mixed hydraulic and traction portfolio. Each callback carries the reported symptom, the mechanic's diagnosis, parts and downtime, and every unit keeps one code across the years, so failure histories can be followed unit by unit. Owners, buildings, mechanics and contacts are replaced with placeholders, proposal amounts are removed, and the records end in 2025.

Collected to order. We collect it from US companies for your order. Scope, volume and timing are confirmed in writing before you sign.

Pricing on request

Request scope and pricing

At a glance

  • Planned scope. Volume, sources and timing are confirmed in writing before you sign.
Records
8.6Mwork orders, emails and documents
Size
22.5 GB
Tokens, estimated
2.4B
Years
2012 to 2025
Firms
1
Owner profile
One independent US elevator service and repair company, 150 to 300 staff
Industry
Field services
Data type
Field operations
Headcount
150 to 300 staff
Region
United States
Languages
English
Formats
JSONL, Parquet
Updated

Sources

SystemKindRecords
Salesforce work ordersField operations1.74M work orders
Microsoft 365 mailEmail6.8M messages
Shared drives (test reports, modernization proposals)Shared files96K documents

Good for

  • predicting repeat callbacks from a unit's maintenance and trouble history
  • training diagnostic assistants on symptom, diagnosis and repair sequences
  • evaluating long-horizon reasoning over one asset's ten-year record
  • drafting modernization scopes from test results and failure history

Fields

FieldTypeDescription
wo_idstringUnique work order id
unit_idstringPlaceholder for the elevator or escalator, stable across all years
unit_typeenumhydraulic, traction_geared, traction_gearless, mrl or escalator
wo_typeenummaintenance, callback, entrapment, test_cat1, test_cat5 or repair
opened_attimestampWhen the call or visit was opened
closed_attimestampWhen the mechanic closed it
reported_symptomstringWhat the caller or building reported
diagnosisstringMechanic's finding and fix as written
parts_usedarray<string>Generic part descriptions
downtime_minutesintMinutes the unit was out of service

Example record

{
  "wo_id": "EV1-WO-1288310",
  "unit_id": "[UNIT_6612]",
  "unit_type": "hydraulic",
  "wo_type": "callback",
  "opened_at": "2023-08-02T13:05:00-07:00",
  "closed_at": "2023-08-02T16:40:00-07:00",
  "reported_symptom": "Car stops about 2 in below floor 3 and doors open, tenants tripping. Third call this month.",
  "diagnosis": "Oil at 128F after back to back runs, valve drifting when hot. Down leveling tested ok cold. Found oil cooler fan relay stuck open, replaced. Readjusted down leveling speed. Ran 20 cycles, stops within 1/4 in.",
  "parts_used": [
    "Relay 24VDC DPDT",
    "Hydraulic oil 5 gal"
  ],
  "downtime_minutes": 215
}
One record, de-identified. Placeholders such as [PERSON_12] and [COMPANY_4] stay the same across the whole dataset, so threads still read correctly.

Licenses available

  • Exclusive

    One buyer. Nobody else can license it during the exclusive term, usually 2 years.

  • Non-exclusive

    Licensed to more than one buyer.

  • First look

    One buyer gets 2 to 4 weeks to make an offer before anyone else sees the dataset.

What ships with it

  • Datasheet: what it is, what it is good for, verified size, sources, years, format and limits.
  • Provenance file: the owner shown by code, staff notice and consent status, exclusions, mapped to the EU AI Act Article 53 training-data summary and California AB 2013.
  • Manifest with a hash for every file.
  • QC report and de-identification report.
  • Your own copy, with unique canary records.

How it is de-identified

Default exclusions removed, files flattened to text, identifiers found in three layers and replaced with consistent placeholders, and the result measured against a 99% bar for each identifier type in each source.

The full method

Request scope and pricing

We confirm scope, volume and timing in writing before you sign. Samples go out under evaluation terms after a short buyer check, once the first records are in.

Dataset: NK-25832

Organization type
What would you like?
Intended use
License interest

We use these details to reply to you and handle your request. See our Privacy Notice.