Automotive service

Automotive Service Robotics Training Data

Torque, fluid, trim and diagnostic work captured egocentrically in working service bays, with constrained reach and frequent occlusion by the vehicle itself, against a spec you write.
Streams
Ten, synced under 2 ms
First batch
Median 48 h
Billing
Per validated hour
License
Buyer-owned
An automotive service bay with a car on a two-post hoist and a rolling tool chest
Head- and wrist-mounted capture holds the torque, fluid, and trim motion in frame even as the vehicle itself occludes the view.

Requirements

What does automotive service robotics data need?

01

Captured in a working bay, not a mock-up

A working service bay has real clutter, mixed and low light under the vehicle, and genuine failure cases like a cross-thread or a dropped fastener, none of which a staged bay reproduces.

02

A named service-task skill list

Torque-to-spec wheel work, fluid drain and fill, trim and clip removal, diagnostic connector seat and read, and filter swap in a constrained cavity each need their own coverage, not one generic "automotive" label.

03

Depth and hand pose through occlusion

The vehicle itself frequently occludes the view, and under-vehicle work happens in tight, low-light cavities. Depth and 3D hand pose need to hold through reach, grasp, and fit at that range, aligned to video on one hardware clock.

04

Plate and VIN blurring without exception

A service bay reliably contains license plates and VIN plates in frame. These are detected and irreversibly blurred at ingest on every clip, with no exception.

Why it matters

What automotive service tasks do robots need training data for?

A robot that torques a wheel, drains fluid, removes trim, or reads a diagnostic connector needs to learn the same reach and grasp geometry a technician uses from that viewpoint, not a description of the task or a fixed-camera view of someone else doing it.

That means synchronized egocentric video, depth, 3D hand pose, and frame-accurate action segments, captured against a named list of service-bay skills rather than pulled from incidental garage footage never meant for manipulation training.

Task coverage

What should an automotive service robotics dataset capture?

A custom automotive collection is scoped to the service-bay skills your policy needs: torque wrench to spec on a wheel, fluid drain and fill, trim and clip removal without damage, diagnostic connector seat and read, and filter swap in a constrained cavity.

You describe which of these tasks (and which bay setups — lift bay, tyre bay, engine bay work, under-vehicle on lift) your policy needs, and the collection is scoped to that list rather than a generic automotive category.

Capture setup

Why egocentric stereo video for service-bay tasks?

A head- and wrist-mounted camera keeps the torque, fluid, and trim motion in frame from the viewpoint a service policy will actually see from, even as the vehicle itself occludes parts of the scene from any fixed camera.

Depth, hand pose, and action segments are aligned to video on one hardware clock, so a policy fusing vision with depth or hand pose is training on streams that share the same timeline. Under-vehicle work is IR-hostile — painted and oily surfaces both absorb a depth projector pattern — so those episodes are flagged for depth quality rather than silently interpolated.

Process

How is custom automotive data collected, from skill spec to pilot to scale?

You describe the service tasks and bay setups your policy needs. We turn it into a written spec covering tasks, environments, capture tier, annotation depth, and accept criteria, then quote reach, timeline, and price against that document before any capture begins.

A Spec Pilot is a small, fast first batch that proves the spec and accept criteria before you scale volume on demand, running through the same seven-stage end-to-end pipeline as every Firsthand program: contributor recruiting, capture, per-batch QA, anonymization, and licensed delivery.

Delivery

What labels and formats are delivered?

Each episode ships with 3D hand pose tracked through reach, grasp, and fit; instance segmentation; action segments; and grasp and contact events, alongside the synchronized video and depth streams, with depth-quality flags on episodes where under-vehicle conditions degrade the signal.

Delivery formats are RLDS, LeRobot, and WebDataset, plus HDF5, zarr, and Rerun .rrd, with readable converter source so you can retarget the schema to your own loader.

Rights

How are consent, privacy and license plates handled?

Every custom collection ships under a perpetual, buyer-owned commercial license, and exclusivity is available so the data is never resold. Each episode links to a signed contributor release through a documented consent chain.

Because a service bay reliably contains license plates and VIN plates in frame, these are detected and irreversibly blurred at ingest without exception, and a reviewer confirms the result before anything ships. The anonymization record is delivered with the data.

Related programs

How does this relate to industrial and assembly pretraining data?

Industrial robot pretraining data spans many sites, stations, and tools to give a foundation model a general prior before it is aligned to any one deployment; a custom automotive collection is the narrower, task-specific counterpart once that base layer exists.

Assembly task data shares the same bench-side, hand-pose-precision approach used here for wheel, fluid, and trim work ��� both are captured against a written spec at the same depth of annotation, just in different environments.

Capture setup

What does an automotive service custom collection capture?

The capture setup and streams behind a custom automotive service robotics data collection.
Automotive service needWhat Firsthand captures
Torque, fluid, and trim motion in frame despite occlusionHead- and wrist-mounted camera keeping the motion visible through the task cycle
Named skill coverageTorque wrench to spec, fluid drain and fill, trim and clip removal, diagnostic connector seat and read, filter swap in a constrained cavity
Hand-level detail3D hand pose tracked through reach, grasp, and fit
Depth through low light and clutterDepth stream aligned to video and hand pose on one hardware clock, with depth-quality flags on IR-hostile under-vehicle episodes
Action structureInstance segmentation, action segments, grasp and contact events
Plate and VIN handlingLicense plates and VIN plates detected and irreversibly blurred at ingest without exception
QualityMeasured against signed accept criteria; billed per validated hour; reject log with every batch
FormatsRLDS, LeRobot, WebDataset, plus HDF5, zarr, and Rerun .rrd

Every collection runs through the same seven-stage end-to-end custom collection pipeline.

Task coverage

Automotive service task by task

Named service-bay skills and what each one delivers.
Service taskWhat's capturedLabels delivered
Torque wrench to spec on a wheelReach, grasp, and torque application at a wheel studAction segments, 3D hand pose, grasp events
Fluid drain and fillHandling a drain plug or fill cap and pouring fluidAction segments, hand pose, contact events
Trim and clip removal without damageReleasing and lifting trim panels and clipsAction segments, hand pose, instance segmentation
Diagnostic connector seat and readSeating a diagnostic connector and reading its displayAction segments, hand pose, depth
Filter swap in a constrained cavityRemoving and refitting a filter in a tight engine-bay spaceAction segments, hand pose, depth-quality-flagged depth

Related programs

Automotive custom collection vs. industrial and assembly pretraining data

How this task-specific spoke relates to the broader pretraining programs.
Industrial robot pretraining dataCustom assembly task dataAutomotive service robotics data
ScopeMany sites, stations, and tools for a general base layerBench-side fastening, measuring, press-fit and wire workWheel, fluid, trim and diagnostic tasks in a service bay
Typical usePretraining a foundation model before site alignmentHand-pose-precision fastening and fittingFine-tuning or evaluating a service-specific policy
EnvironmentFactories, workshops, and warehouses broadlyBench or fixed workstationWorking automotive service bay
LicensePerpetual, buyer-owned; exclusivity availablePerpetual, buyer-owned; exclusivity availablePerpetual, buyer-owned; exclusivity available

FAQ

Automotive robot training data, answered.

What is automotive service robotics training data?
It is real-world, first-person demonstration data of wheel, fluid, trim and diagnostic tasks in a working service bay, captured against a written spec: egocentric video with depth, hand pose, and action segments. Firsthand handles contributors, capture, QA, consent, and delivery.
How is this different from the existing automotive service bay dataset?
The existing dataset is a fixed, already-captured corpus available now under its published terms. A custom collection is scoped to your written spec — the exact tasks, bay setups, and volume your policy needs — and captured on demand.
Is capture done in a live service bay or a mock-up?
Working service bays — lift bay, tyre bay, engine bay work, and under-vehicle on lift — rather than a staged mock-up.
How are license plates and VINs handled?
License and VIN plates are detected and irreversibly blurred at ingest without exception, and a reviewer confirms the result before anything ships. The anonymization record is delivered with the data.
How does depth hold up on under-vehicle work?
Under-vehicle capture is IR-hostile because painted and oily surfaces absorb a depth projector pattern. Those episodes carry a depth-quality flag rather than being silently interpolated.
How is custom automotive data billed?
Per validated hour, quoted against the written spec before any capture. You pay only for data that clears the accept criteria, and rejected items are recaptured at our cost.
Which delivery formats are supported?
RLDS, LeRobot, and WebDataset, plus HDF5, zarr, and Rerun .rrd. Converter source is readable, so you can retarget the schema to your own loader.
Can we start with a small pilot?
Yes. A Spec Pilot is a small, fast first batch that proves the spec and accept criteria before you scale volume on demand.

Sources

Where are the delivery formats documented?

Request a custom dataset.

Tell us the service-bay tasks your policy needs to perform. We will quote reach, timeline, and price against a written spec, with a first validated batch in a median of 48 hours where coverage is deep.