A named teardown sequence
Unscrewing, prying open, removing a board, removing a battery and sorting materials are different steps, so a spec names each one and the order it should run in.
Task family
Requirements
Unscrewing, prying open, removing a board, removing a battery and sorting materials are different steps, so a spec names each one and the order it should run in.
A head-mounted view keeps both hands, the device being opened and the part being lifted out in view through the whole sequence.
3D hand pose with per-joint visibility carries the finger detail of gripping a casing, working a tool into a seam and easing a part free.
Frame-accurate action segments mark where unscrewing ends, where opening becomes removal and where sorting begins, aligned to video and depth.
A perpetual, buyer-owned commercial license backed by a documented consent chain.
Definition
Egocentric e-waste disassembly data is real-world, first-person video of a person taking electronic devices apart for recycling. The site states the task as one catalog row, E-waste disassembly and sorting, which reads "Unscrew and pry open devices, remove boards and batteries and sort materials into bins." It is recorded from the worker viewpoint, with depth, 3D hand pose, contact events and frame-accurate action segments aligned on one hardware clock, against a written spec.
People search for this under several names: e-waste disassembly robot training data, an electronics dismantling video dataset, egocentric teardown data or custom recycling task data collection. They describe the same thing, a record of how a person opens a device and separates what is inside it, seen from the person own point of view, with both hands and the work in frame.
Teardown is not the same as repair or assembly. A repair starts from a fault and ends with a test. An assembly follows a known build order and ends with a finished unit. A disassembly row in this catalog starts with a closed device and ends with materials sorted into bins. The neighbouring pages on this site cover repair, assembly, screwdriving and trash handling, and they are linked at the end of this page.
This page states only what the site already states. Where a detail is not in the catalog or the delivery terms, it is marked Not stated and left for the written spec.
Setting
The catalog states one e-waste task. It sits in an environment named Electronics Manufacturing & E-Waste, in the Manufacturing & Workshops sector, and it is rated Medium and listed as Available on request. The environment examples read "Circuit board assembly, device manufacturing, component soldering, e-waste disassembly and sorting," so the disassembly row is listed beside three assembly and soldering rows rather than on its own.
The verbs in the row are the verbs a spec can build on: unscrew, pry open, remove boards, remove batteries and sort materials into bins. A buyer who needs only one stage, for example opening casings or taking out boards, can ask for that stage in the spec, and one who needs the full sequence can ask for all of it. The catalog does not split the row into stages, so any split is a spec choice and not a stated task list.
The site does not state which devices are taken apart, how many devices a session covers, which tools are used, which materials are sorted or what the bins hold. Those are Not stated and are set in the written spec before capture begins.
A separate Recycling & Waste-Transfer Facility environment is listed with the examples "Sorting lines, baling, material recovery." It is rated Easy and Ready to deploy and is described as a target environment for commercial egocentric collection. The catalog lists no disassembly task under it, so this page treats it as a neighbouring environment and not as a source of teardown tasks.
Streams and labels
Each episode follows the Firsthand episode schema: ten streams synced under 2 ms, with head and wrist RGB, depth, 3D hand pose with per-joint visibility, contact events on grasp and release, and frame-accurate action segments. For teardown, hand pose tracks the fingers on a casing, a screw and a lifted part, contact events mark when fingers meet a tool or a component, and action segments mark each step of the sequence.
The site also states 200 Hz 6-DoF IMUs on the Firsthand capture rig. Which sensors a given e-waste collection uses depends on the capture mode in the spec, since the catalog lists this row under a head-mounted phone or a multiview rig, so confirm the stream list in the spec before you plan a training pipeline around a specific sensor.
Object labels use the terms your spec sets. Device types and models, tools, material categories, the contents of each bin, force or tactile data, and a disassembly-outcome or task-completion label are Not stated. If your policy needs a label such as "board removed" or "bin correct," define it in the spec and the accept criteria. This page makes no head or camera pose, mapping or SLAM claim as a deliverable.
Delivery
Delivery formats are RLDS, LeRobot and WebDataset, plus HDF5, zarr and Rerun .rrd. The format table below sets each against what its official documentation states. Teardown episodes use the same schema as every other Firsthand collection, so a loader that reads another Firsthand dataset reads this one without changes.
Every batch is validated against signed accept criteria before it ships, with a reject log, and delivery is rolling, per validated batch. Rejected items are recaptured at our cost. Billing is per validated hour, and every collection ships under a perpetual, buyer-owned commercial license.
The site does not state a number of episodes, a batch size or a total hour count for this task, so those are quoted against your spec and not assumed here.
Why it matters
Taking a device apart is contact-heavy hand work. A person works a tool into a seam, feels a clip give, steadies the casing with the other hand, lifts a board out without dragging the parts around it and decides which bin a piece belongs in. A policy that is meant to learn this sequence needs to see how the hands move and when they touch the work, not only the finished state of the device.
First-person video suits that need because the camera sits where the worker eyes sit, so the opening seam, the tool tip and both hands stay in view. 3D hand pose and contact events add the finger-level detail that plain video leaves implicit, and action segments mark where each step starts and stops so a model can learn the order as well as the motion.
This page quotes no robot result, no recovery rate, no throughput figure and no benchmark. It also does not claim that any model has been trained on this data. The site states a catalog task and a capture and delivery method, and the value to a given policy is something a pilot can test against your own accept criteria.
The site lists no refurbishment row. Refurbishment, reuse and resale are therefore outside what this page states, and a buyer who wants them covered describes the work in the spec.
Setting and privacy
For the capture mode this row uses, the site says a head-mounted phone records the first-person view of real work on site, and a multiview rig adds synchronized third-person angles when the spec asks for them. That describes work on site and not a staged set. The staged-set wording on the site belongs to a different capture mode that uses handheld grippers, which this row does not list.
The site does not state whose site that is, how many sites a collection uses, or which regions or cities are covered for this task. Elsewhere it states that Firsthand does not capture at a customer own facility, so this page makes no claim of capture there. Environment, access and schedule are agreed in the spec.
Every episode links to a signed contributor release through a documented consent chain, and the consent record is part of the delivery. Faces, plates and screens are detected and irreversibly blurred at ingest, and a reviewer confirms the result before anything ships. The anonymization record is delivered with the data.
That is the whole of the privacy wording the site states. It does not state a rule for data stored on a device, so none is claimed here, and raise it in the spec if it matters to you. This page also makes no safety, hazardous-material, battery-safety, environmental, certification or compliance claim.
Fast · on demand
The catalog lists the e-waste row as Available on request. The site defines that status as scoped and recruited to spec when a buyer asks for it, so this is not a row where recording is already running. Its timeline is quoted against your spec before any capture begins.
The site publishes two per-batch speed figures. Where coverage is already deep, the first validated batch lands in a median of 48 hours from signed spec. Thin environments typically take three to four weeks, because vetting operators there is the bottleneck, and we quote that up front. The site does not state which of the two applies to e-waste disassembly, so the quote says.
On-demand top-ups run against the same spec and accept criteria after each training run. The site does not state a batch size or a later-batch turnaround for this task, so those are quoted against your spec.
The spec
You describe the devices, the sequence and the sorting your policy needs. We turn that into a written spec covering tasks, environments, capture tier, annotation depth and accept criteria, then quote reach, timeline and price before any capture begins.
A Spec Pilot, a small and fast first batch, can prove the spec and accept criteria before you scale. Billing is per validated hour, a reject log ships with every batch, rejected items are recaptured at our cost, and every collection ships under a perpetual, buyer-owned commercial license.
Useful things to settle in the spec are the stages you want covered, the device categories, the tools you expect to see, the bins and what each one holds, any label you want for step success, and the formats you want delivered. Each of those is Not stated by the site today, which is why the spec is where they are written down.
At a glance
Every collection runs through the same seven-stage end-to-end custom collection pipeline. End-to-end custom data collection is a managed service that takes an AI data need from problem to owned dataset in a single accountable pipeline.
What the site states
| Where it appears | What the site states | Used on this page as |
|---|---|---|
| Task catalog, Electronics Manufacturing & E-Waste environment | One row, E-waste disassembly and sorting, rated Medium and Available on request, with the capture mode Phone (head-mounted) / multiview rig | The stated e-waste disassembly task |
| Environment examples line | "Circuit board assembly, device manufacturing, component soldering, e-waste disassembly and sorting" | Context: the row sits among assembly and soldering rows |
| Task catalog, Recycling & Waste-Transfer Facility environment | Examples "Sorting lines, baling, material recovery"; one environment row, rated Easy and Ready to deploy, described as a target environment for commercial egocentric collection | A neighbouring environment; no disassembly task is named |
| Capture mode description | A head-mounted phone records the first-person view of real work on site; a multiview rig adds synchronized third-person angles when the spec asks for them | How capture is described, as real work on site |
Catalog rows
| Task family | Catalog task and description | Skill | Status |
|---|---|---|---|
| Target task, disassembly | E-waste disassembly and sorting: unscrew and pry open devices, remove boards and batteries and sort materials into bins | Medium | Available on request |
| Neighbour, assembly | Circuit board assembly: place components on the board, seat connectors and secure parts before soldering | Medium | Available on request |
| Neighbour, soldering | Component soldering: solder components to the board with an iron and solder wire, trim leads and inspect joints | Hard | Available on request |
| Neighbour, assembly | Device manufacturing: assemble device housings, fit boards and cables, fasten screws and test the unit | Medium | Available on request |
Streams and labels
| Item | Status on this site | Why it matters for e-waste disassembly |
|---|---|---|
| Head and wrist RGB, depth | Stated; ten streams synced under 2 ms | Keeps the device, tool and hands on one timeline |
| 3D hand pose, per-joint visibility | Stated | Carries the finger detail of gripping, prying and lifting |
| Contact events on grasp and release | Stated | Marks when fingers meet a tool, a casing or a component |
| Action segments | Stated; frame-accurate | Separates unscrewing, opening, removal and sorting |
| 200 Hz 6-DoF IMUs | Stated for the Firsthand capture rig; whether a phone or multiview collection includes them is set in the spec | Motion signal for pipelines that use it |
| Device types and models, tools, materials | Not stated; the row names devices, boards, batteries and materials only | Defined in the spec |
| Number of devices, episodes or hours | Not stated | Quoted against the spec |
| Task durations, throughput, force or tactile data | Not stated | Defined in the spec if needed |
| Disassembly-outcome or success label | Not stated | Defined in the spec if needed |
| Number of sites, regions or cities | Not stated | Agreed in the spec |
Formats
| Format | What the official documentation states | Used for here |
|---|---|---|
| RLDS | A dataset is retrieved as a tf.data.Dataset of episodes, and each episode contains a dataset of steps (RLDS repository README) | Episode-based training loaders |
| LeRobot | LeRobotDataset v3.0 is a standardized format for robot learning data, including multi-camera video, with many episodes stored per Parquet or MP4 file (LeRobot documentation) | LeRobot dataset format and tooling |
| WebDataset | Tar files in which files that belong together share a basename, with shards numbered like something-000000.tar (WebDataset README) | Sharded streaming for large training runs |
| HDF5 and zarr | Stated by Firsthand only | Array storage for custom pipelines |
| Rerun .rrd | Stated by Firsthand only | Multi-stream synchronized playback for review |
FAQ
Sources
Tell us the devices, the teardown sequence and the sorting your policy needs to handle. We will quote reach, timeline, and price against a written spec before any capture begins.