Three catalog rows, stated exactly
Wire an outlet, Outlet & Fixture Wiring, and Strip and wire electrical outlets using wire strippers and a voltage tester. All three are rated Hard, and the first table below quotes them without change.
Now recruiting capture teams worldwide. Get paid to record first-person video of real work.
Apply to captureHard task
Requirements
Wire an outlet, Outlet & Fixture Wiring, and Strip and wire electrical outlets using wire strippers and a voltage tester. All three are rated Hard, and the first table below quotes them without change.
Hand pose, contact events and per-frame instance masks are recorded on one clock, with a visibility flag on each joint for fingers that a wire or a device hides.
Stripping wires and landing them on terminals are written as separate steps, and where each starts and ends is agreed before capture so each step can become its own labeled segment.
Consent, anonymization and the license are stated below. This page makes no electrical-safety or compliance claim and gives no instructions.
Definition
Egocentric outlet wiring data is first-person video of a person doing the work named in the catalog’s outlet rows: stripping wires and landing them on the terminals of an outlet. It is recorded from the contributor’s own point of view with synchronized sensor streams alongside, so the frames show what the hands are doing to the wire and the terminal rather than a distant view of someone standing near a job. Searchers also phrase it as first-person wire stripping and terminal landing video, an electrical outlet robot dataset or custom trades data collection. The data is the same, collected as a custom collection scoped to your task.
On this site the data is human capture: a paid, consented contributor performs the task from a written skill spec. It is not robot or teleoperation data, and the page makes no claim that any robot has been trained on it or that any robot wires an outlet. The page is narrower than the egocentric electrical work page, which covers five electrical rows, and it is the first-person counterpart of the stereo outlet wiring page, which covers the one bench row on the stereo and MCAP side.
Catalog rows
Three rows state outlet wiring, in two environments. In Trades Workshop Bench, "Wire an outlet" reads: "Strip wires and land on terminals." It is rated Hard, its capture is Multiview rig + handheld grippers and its status is Available on request. In Trade Service Calls (Plumbing / HVAC / Electrical), "Outlet & Fixture Wiring" reads: "Strip wires, connect outlets and fixtures and test with a voltage tester with power off." The second, "Strip and wire electrical outlets using wire strippers and a voltage tester", reads: "Strip and connect wires to the outlet terminals and verify with a voltage tester." Both are rated Hard, listed as Phone (head-mounted) / multiview rig and Ready to deploy.
Available on request means the work is scoped and recruited to spec when a buyer asks. Ready to deploy is the catalog’s own status word for the two trade service rows. Neither is a statement that a stock of outlet wiring footage exists, and this page claims no volume, hours or delivered clips for any row. The rows name wires, terminals, outlets, fixtures, wire strippers, a voltage tester and power off. They name no voltage, no wire gauge, no code, no tool or device model, so if your program needs any of them, it is written into the skill spec rather than assumed.
Why it is hard
The site’s answer is the Skill column. The catalog rates all three rows Hard, and that is all "Hard" means here. This page imports no outside rubric and states no failure rate, tolerance or claim about how skilled any worker is. What the row text says is that the task is a sequence: stripping wires, landing or connecting them at outlet terminals, and in the trade service rows testing with a voltage tester with power off. The part that matters is a wire end meeting a terminal, and the site publishes no step list, limit or outcome definition for it.
The site’s electrical copy adds one thing that bears on capture: the part that matters is often the part a hand is covering. That is why hand pose carries a per-joint visibility flag for hidden fingers, why contact events mark when a hand meets an item and why masks are recorded per frame. The challenge table below maps each difficulty to the stream or label the site already states, and says Not stated where nothing is.
Capture
The catalog lists two capture modes across the three rows. The two Trade Service Calls rows list Phone (head-mounted) / multiview rig. That is a first-person view of real work, with a multiview rig adding synchronized third-person angles when the spec asks for them. The bench row lists Multiview rig + handheld grippers, which the site describes as a staged working set recorded by a multiview rig while the operator performs the task with handheld grippers, so demonstrations map onto a robot end effector.
The site also describes the wider egocentric rig: ten synchronized streams (4K head camera, two wrist cameras, depth, IMU, 3D hand and body pose, instance segmentation and action labels), hardware-triggered onto one PTP clock domain and aligned under 2 ms. Which tier applies to an outlet wiring program, and whether a head-mounted view is added to the bench row’s gripper setup, is not stated and is confirmed in the skill spec. This page does not describe any of the rows as stereo capture. Stereo is a separate offer, agreed in a spec and confirmed on a Spec Pilot.
Episodes
Each attempt is delivered as one episode. The standard episode carries action segments, 3D hand pose for both hands with a per-joint visibility flag, contact events that mark when a hand meets an item, an objects list, and per-frame instance masks stored at the depth resolution of 848×480. Hand pose is 21 joints per hand, 3D, in metres in the head-camera frame. For these rows an episode might cover one outlet or a run of several; where each episode starts and ends is written into the spec, because the site sets no episode length.
Action segments divide an episode into start- and end-timestamped spans, each carrying start_ns, end_ns, verb and noun, so stripping and landing can each be their own labeled span. Which verbs and nouns are used is set in the skill spec. The site lists no label for the outcome of a step, such as whether a wire sits on a terminal, no connection or termination label, and no voltage, current or test-result stream. The voltage tester in two rows describes the task the contributor performs, not a delivered measurement, so ask for any such label in the spec.
Neighbouring pages
Two pages sit closest, and neither is egocentric outlet wiring as its main topic. The stereo outlet wiring page covers the one Trades Workshop Bench row, Wire an outlet, on the stereo and MCAP side. The egocentric electrical work page covers five electrical rows across four environments, so outlet wiring is part of a wider set there, alongside electrical installation on a construction site and an electrical repair call in a client’s home.
This page takes the three outlet-wiring rows as one first-person topic, because the hub’s Hard-row table lists them separately and each row now links here. Its distinct content is the pairing of the two trade service rows, which name a voltage tester, with the bench row, which names only terminals. The comparison table below sets each page against this one.
Why it matters
The GR00T N1 paper, linked in the sources, structures its training corpora as a data pyramid. In its words: "large quantities of web data and human videos lay the base of the pyramid; synthetic data generated with physics simulations and/or augmented by off-the-shelf neural models form the middle layer, and real-world data collected on the physical robot hardware complete the top." In that framing, first-person human video of outlet wiring would belong to the human-video base. Human capture does not replace robot data, and this page does not claim that it does.
The same paper says of the human video datasets it used: "These do not include explicit action labels but contain extensive sequences of human-object interactions." That is a statement about those datasets, not about this one. A Firsthand episode carries labeled action segments, 3D hand pose and contact events, so the structure of the step is explicit in the data. No model named on this page was trained on Firsthand data, and this page claims no result from any training run.
Delivery and license
Delivery is in the format your stack already reads: RLDS, LeRobot, WebDataset, HDF5, zarr or Rerun .rrd, or raw streams with metadata, with readable converter source alongside. The official sources describe three of these in their own terms. The RLDS repository describes an ecosystem of tools to store, retrieve and manipulate episodic data, including for learning from demonstrations and imitation learning. The LeRobot repository describes its dataset format as synchronized MP4 videos or images for vision plus Parquet files for state and action data. The WebDataset repository describes tar files in which files that belong together share the same basename and make up a training sample.
The license is perpetual, irrevocable and worldwide, buyer-owned and non-exclusive by default, with exclusivity available as a separate term. The executed agreement controls. MCAP delivery is a separate offer described on the egocentric stereo MCAP page, and nothing on this page promises an MCAP file for these rows.
Validation
Validation runs against signed accept criteria written into the spec before capture, and a reject log ships with each batch. Episodes are machine-checked against stated reject criteria, such as a sync breach, calibration drift beyond tolerance, the manipulated object out of frame for more than 15 percent of the episode, more than 35 percent of depth pixels in the manipulation region invalid or an undocumented bystander, and a human reviewer then checks each one. Only footage that clears the criteria is billed as a validated hour.
For these rows, the spec has to say which item counts as the manipulated object at each step and where the manipulation region is, because the wire, the terminal and the outlet are different items at different moments. What counts as a finished step is also written down, since the site states no outcome definition. Rejected items are recaptured at our cost, and the site states no accuracy figure for step labels, so what counts as a pass for a step boundary is set in the accept criteria.
Capture and privacy
Every contributor signs a written release, and each delivered episode links to it through consent artefact IDs. At ingest, automated detection finds faces, plates and screens and blurs them irreversibly, and speech is scrubbed of names, addresses and card numbers. A human reviewer confirms that no un-consented person is identifiable in any frame, footage with bystanders who cannot be de-identified is discarded, and the anonymization record ships with the data. Firsthand does not capture at a customer’s own facility, and which setting a program uses is agreed in the skill spec before capture begins.
This page makes no electrical-safety, licensing, qualification or compliance claim, because the site makes none for these rows, and it gives no instructions for any step. One row says "with power off"; the other rows do not state the power state, and this page says no more than the rows do. None of this is legal advice.
Speed and scale
From signed spec to first validated batch, the published timeline is a median of 48 hours where coverage is deep and three to four weeks where it is thin and contributors need to be recruited first. The site does not state which range applies to the outlet rows, so it is confirmed when the spec is quoted rather than assumed. After a first batch, on-demand top-ups run against the same accept criteria, so you can add variation without rewriting the spec.
Outlet wiring is custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. The site states no provider count, hours or throughput for these rows, and none of its off-the-shelf dataset descriptions names outlet wiring, so treat it as a custom collection.
Not stated
It states no voltage, no wire gauge, no code, no tool or device model and no outlet or fixture type, because the rows name none and the spec is where they are agreed. It states no number of sites, contributors, episodes or hours, no cycle times and no throughput. It states no connection, termination or test-result label, no force or tactile stream and no safety or compliance claim.
It also states no result from training any model on this data. If your program needs any of these, the way to get them is to write them into the skill spec and the accept criteria, where they are quoted and then checked on the Spec Pilot.
Getting started
Describe the sequence your policy needs, where each step starts and ends, what you expect to see as the wire, the terminal and the outlet, what counts as a finished step and the variation your pipeline is missing. Then name the streams you want, which row wording you are working from and the angles you want beyond the head-mounted view. That becomes a written skill spec, quoted for reach, timeline and price before any capture begins.
Most programs begin with a Spec Pilot, a small, fast first batch that proves the spec and the accept criteria on real footage before volume scales. Collections are billed per validated hour. Counts of sites, episodes and hours are set in the skill spec. Our skill spec guide, linked below, walks through how to write one.
Capture setup
| Part | As stated on this site |
|---|---|
| Capture mode (Trade Service Calls rows) | Phone (head-mounted) / multiview rig, as the catalog lists it |
| Capture mode (Wire an outlet) | Multiview rig + handheld grippers, as the catalog lists it |
| What the bench mode means | A staged working set recorded by a multiview rig while the operator performs the task with handheld grippers, so demonstrations map onto a robot end effector |
| Multiview rig | Adds synchronized third-person angles when the spec asks for them |
| Streams | Ten: 4K head camera, two wrist cameras, depth, IMU, 3D hand and body pose, instance segmentation, action labels |
| Sync | Hardware-triggered onto one PTP clock domain; aligned under 2 ms |
| Calibration | Re-solved twice per session; an episode is accepted only if RMS reprojection stays under 0.28 px |
| Hand pose | 21 joints per hand, 3D, in metres in the head-camera frame; per-joint visibility flag |
| Stereo | Not stated for these rows; a separate offer, agreed in the skill spec and confirmed on a Spec Pilot |
| Which tier applies to a given program | Not stated; confirmed in the skill spec |
Every collection runs through the same seven-stage end-to-end custom collection pipeline.
Live catalog rows
| Task | Description | Environment | Skill | Capture | Status |
|---|---|---|---|---|---|
| Wire an outlet | Strip wires and land on terminals. | Trades Workshop Bench | Hard | Multiview rig + handheld grippers | Available on request |
| Outlet & Fixture Wiring | Strip wires, connect outlets and fixtures and test with a voltage tester with power off. | Trade Service Calls (Plumbing / HVAC / Electrical) | Hard | Phone (head-mounted) / multiview rig | Ready to deploy |
| Strip and wire electrical outlets using wire strippers and a voltage tester | Strip and connect wires to the outlet terminals and verify with a voltage tester. | Trade Service Calls (Plumbing / HVAC / Electrical) | Hard | Phone (head-mounted) / multiview rig | Ready to deploy |
Neighbouring pages
| Page | Main topic | Where the outlet wiring rows appear |
|---|---|---|
| This page | The three outlet wiring rows, egocentric | The whole page |
| Stereo outlet wiring data | The Wire an outlet bench row, with stereo and MCAP as spec-level choices | The bench row is the whole page; the two trade service rows are named as neighbours |
| Egocentric electrical work video data | Five electrical rows across four environments, egocentric | Three of five rows |
| Egocentric wire crimping data | The Medium-rated crimping row on the same bench | Not covered |
| Egocentric cable routing and wiring data | Routing, clipping, patching and outlet wiring across benches, racks and venues | Among the wiring rows |
| Hard-task data collection | The hub of rows the catalog rates Hard | All three rows are in the Hard-row table and link here |
Capture challenges
| Bench challenge | What goes wrong | Stated stream or label |
|---|---|---|
| Hands cover the wire or terminal | Fingers hide the part that matters | 3D hand pose with per-joint visibility flags; per-frame instance masks; a wrist view alongside the head camera; reject if the object is out of frame for more than 15% of an episode |
| Hand meets wire or device | The hand and the item touch in quick succession | Contact events mark when a hand meets an item; no finer contact label is stated |
| Stripping and landing as separate steps | It is unclear where one step ends and the next begins | Action segments, one per step as written in the spec; no accuracy figure for step labels is stated |
| Wire seated on the terminal | Whether a wire has landed is a visual state | Not stated: no connection, termination or seating label is listed |
| Testing with a voltage tester | A test is something the contributor does, not a value in the data | Not stated: no voltage, current or test-result stream is listed |
| Glare and shiny surfaces | Depth readings degrade on a reflective surface | The site states that depth degrades on wet and reflective surfaces and that a confidence map is delivered to mask low-confidence regions; reject if more than 35% of depth pixels in the manipulation region are invalid |
| Motion blur and occlusion | Fast reaches between wire, tool and terminal | Global-shutter head camera avoids rolling-shutter skew; visibility flag for hidden joints |
| Grip and handling force | How hard a wire or device is held | Not stated: no force, torque or tactile stream is listed |
Delivered vs not stated
| Item | Status | Detail |
|---|---|---|
| Action segments | Delivered | start_ns, end_ns, verb, noun, one per step |
| 3D hand pose | Delivered | 21 joints per hand; per-joint visibility flag for occluded fingers |
| Contact events | Delivered | The moment a hand meets an item |
| Per-frame instance masks | Delivered | Stored at 848×480 |
| Consent and anonymization records | Delivered | Consent artefact IDs per episode; anonymization record shipped with the data |
| Formats | Delivered | RLDS, LeRobot, WebDataset, HDF5, zarr, Rerun .rrd or raw streams with metadata |
| Voltages, wire gauges, codes, tool and device models | Not stated | Agreed in the skill spec |
| Connection, termination or test-result labels | Not stated | No such label is listed |
| Cycle times and throughput | Not stated | No such figure is listed |
| Number of sites, episodes and hours | Not stated | Set per program in the skill spec |
| Force or tactile readings | Not stated | Not among the listed streams |
| Safety, qualification or compliance claims | Not stated | This page makes none |
Example footage
One real clip already published on this site, shown as a format and rig example: ten seconds of first-person home cooking with faces blurred. It does not show outlet wiring or any electrical work.
No outlet wiring clip is published on the site, so this is the nearest first-person clip, labelled as a format example. Request a sample to see delivered files. See sample data outputs, request an egocentric data sample.
FAQ
Sources
Tell us the sequence, where each step starts and ends, what you expect to see as the wire, the terminal and the outlet, which row wording you are working from, and the angles you want beyond the head-mounted view. We will quote reach, timeline and price against a written spec.