Two named mounting tasks
Fastening rail brackets with a driver and clipping cage nuts before mounting a blanking panel are different sequences, so a spec names each one, where it starts and where it ends.
Now recruiting capture teams worldwide. Get paid to record first-person video of real work.
Apply to captureTask family
Requirements
Fastening rail brackets with a driver and clipping cage nuts before mounting a blanking panel are different sequences, so a spec names each one, where it starts and where it ends.
The catalog lists a multiview rig with handheld grippers for both rows, so the spec states which streams that mode carries rather than assuming them.
Where the spec asks for them, contact events and action segments mark when a bracket, a cage nut or a panel meets the rack and where each step ends, aligned to video and depth.
Where hand pose is part of the spec, a per-joint visibility flag records which joints were hidden behind a bracket, a panel or the driver.
A perpetual, buyer-owned commercial license backed by a documented consent chain.
Definition
It is video of the mounting work at a server rack: fastening rail brackets with a driver, and clipping cage nuts and mounting a blanking panel. People reach it through several phrasings: egocentric server rack installation data, first-person rack rail and cage nut video, a blanking panel mounting robot dataset, or custom data center data collection. It is recorded against a written spec, with depth, contact events and frame-accurate action segments aligned on one hardware clock where the spec includes them.
The broad egocentric data center page covers all twelve rows in the environment in a paragraph each. This page narrows to the two rows that mount hardware to the rack itself, so a spec for rail and panel work can be read in one place. The data is human capture by paid, consented contributors, not robot or teleoperation data, so use for a specific robot still needs your own retargeting step.
Catalog rows
Two, both listed under the Data Center & IT Hardware Bench environment in the Office & IT sector, whose examples read "Server rack plus hardware bench: modules, cabling, drivers". "Screw-mount rack rails" is described as "Fasten rail brackets with a driver." and is rated Easy. "Clip cage nuts + panel" is described as "Clip cage nuts and mount a blanking panel." and is rated Medium.
Both are listed as Available on request, with the capture setup "Multiview rig + handheld grippers". Available on request means the work is scoped and recruited to spec when a buyer asks for it, rather than running as an open capture stream today. The site states no delivered hours for either row, so this page claims none.
Difference
The egocentric data center and IT hardware page is the broad page: all twelve rows, from cable dressing to asset tags, with these two rows listed among them. The egocentric server hot-swap and component seating page covers five other rows, and it lists "Clip cage nuts + panel" and "Screw-mount rack rails" as rows it does not cover. The egocentric network patching and fiber transceiver page also lists them as rows outside its scope.
The stereo data center rack and server hardware page treats all twelve rows from the stereo and container side. None of them has rail and panel mounting as its main topic, which is why this page exists. The comparison table below sets the pages side by side.
Rail brackets
One row, "Screw-mount rack rails", and one sentence: "Fasten rail brackets with a driver." It is the only mounting row that names a tool, a driver, and the site states no driver model, bit, torque or fastener type. The row is rated Easy, which is all the site says about its difficulty.
Rail length, bracket type, rack standard, number of brackets per episode and what a correctly fastened bracket looks like are Not stated. A spec that depends on any of them has to name them, and the accept criteria say what counts as a finished step.
Cage nuts and panel
One row, "Clip cage nuts + panel", described as "Clip cage nuts and mount a blanking panel." It is the one Medium row of the two. The description holds two parts in one row, the cage nuts and the panel, so a spec can decide whether an episode covers both parts or one.
Cage nut counts, panel size, the order of the steps, hole patterns and any hand tool used for clipping are Not stated. The catalog does not say whether the two parts are separate steps or one, and it gives no way of labelling or measuring a mounted result.
Why demanding
The catalog describes steps that end in a physical fit to the rack: brackets fastened with a driver, cage nuts clipped and a panel mounted. Lighting, rack density, reach and the height of the work are Not stated. The two rows are rated Easy and Medium, and this page says no more about difficulty than that.
What the site does state is what egocentric video puts into the training distribution: hands entering the frame from below, occlusion during grasp and motion blur during reach. RGB alone leaves a model to infer 3D hand structure it cannot see reliably through occlusion and motion blur, which is why the site delivers hand pose with a visibility flag per joint where a spec includes it. Whether that stream is populated for the staged gripper capture mode is Not stated.
Capture setup
The catalog describes the mode 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 catalog does not list a head-mounted phone or a stereo pair for either row, and this page does not claim either is running on them. The site states no camera count, resolution or frame rate for these rows, so the capture tier is agreed in the spec.
Stereo applies only through the site’s general stereo offer: a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot, and the stereo data center page covers that side. Whether the first-person head-mounted mode listed for other rows is offered for these two is Not stated. The site states no gripper model or jaw type, and the setting is agreed in the spec, since the site lists capture at a customer’s own facility as not offered.
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 and grasp events, and frame-accurate action segments. For mounting work, contact events mark when a bracket, a cage nut or a panel meets the rack, and action segments mark each step as the skill spec defines it.
The site does not state which of those streams the staged gripper mode populates for each row. Object labels use the terms your spec sets. Force or tactile data, and success or quality labels for a fastened bracket, a clipped nut or a seated panel, are Not stated. The streams table below sets each against what the site states.
Gloves
The site offers a tactile glove tier as a pilot-ready option. The glove signal is time-synced to a head-mounted stereo camera by hardware timestamps and an IMU, and each glove is calibrated every session.
The site does not state that the glove tier has been used on either mounting row, and both rows list handheld grippers as their capture mode. Treat force and tactile data as Not stated for these rows unless a spec adds the glove tier and agrees the fit with you.
Setting and privacy
The catalog places the rows in a server rack plus hardware bench environment. The site names no data center, colocation facility, customer or operator, and it does not state capture at a customer’s own site. Environment, access and schedule are agreed in the spec, and the number of sites is Not stated.
Every episode links to a signed contributor release through a documented consent chain. Faces, plates and screens are detected and irreversibly blurred at ingest, a reviewer confirms the result before anything ships, and the anonymization record is delivered with the data. An undocumented bystander is a stated reject criterion. How asset tags, serial numbers, barcodes and cable labels are handled is Not stated, so name them in the spec.
Quality gates
Episodes are machine-checked at ingest against the stated reject criteria, listed in the failure-mode table below, and a human reviewer then checks the result. Two stated rules bite on this work: an episode is rejected when the manipulated object is out of frame for more than 15 percent of it, and when more than 35 percent of depth pixels in the manipulation region are invalid.
What counts as the object, a bracket, a cage nut or a panel, is set in the spec. How often a part leaves the view in a rack, how depth behaves on rack metalwork, and any blur or sharpness rule are Not stated. A rejected item goes to the reject log and is recaptured at our cost.
Delivery
Delivery formats are RLDS, LeRobot and WebDataset, plus HDF5, zarr and Rerun .rrd. Firsthand also offers MCAP delivery; the MCAP hub page covers the container as its own documentation describes it, and which streams would be channels in a file, and what they are named, is Not stated and is agreed in the skill spec.
Every batch is validated against signed accept criteria before it ships, with a reject log, and delivery is rolling, per validated batch. The formats table below sets each format against what its official documentation states.
Scale and speed
None of the site’s off-the-shelf dataset descriptions names rack rail or cage nut mounting, so for this task it is custom collection, not an off-the-shelf purchase. It is custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.
From signed spec to first validated batch, the timeline is a median of 48 hours where coverage is deep and three to four weeks where it is thin and operators need to be recruited and vetted first. Both rows are Available on request, so which range applies is confirmed when the spec is quoted rather than assumed. On-demand top-ups run against the same spec and accept criteria after each training run. Collections are billed per validated hour, and the site publishes no price list, minimum order or batch size for these rows.
Ordering
Describe which of the two rows are in scope, where each task starts and ends, whether an episode covers one part or the whole step, and what counts as finished. Add the setting, the privacy rule for screens and labels, and the variation your pipeline is missing. Then name the streams you want, the capture mode, and the delivery format.
Most programs begin with a Spec Pilot, a small, fast first batch that proves the spec and accept criteria on real footage before you scale. The last table below shows what each spec element decides.
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.
Catalog rows
| Task (as listed) | Description (as listed) | Environment | Skill | Capture setup | Status |
|---|---|---|---|---|---|
| Screw-mount rack rails | Fasten rail brackets with a driver. | Data Center & IT Hardware Bench | Easy | Multiview rig + handheld grippers | Available on request |
| Clip cage nuts + panel | Clip cage nuts and mount a blanking panel. | Data Center & IT Hardware Bench | Medium | Multiview rig + handheld grippers | Available on request |
| Racking a full server, configuring a switch, decommissioning hardware | Not stated as catalog rows | Not stated | Not stated | Not stated | Not stated |
Compared pages
| Page | Main topic | Capture framing | Treatment of the two mounting rows |
|---|---|---|---|
| This page: egocentric rack rail and cage nut mounting data | The two mounting rows only | Multiview rig + handheld grippers, as the catalog lists it | The whole page: scope, limits, streams and ordering |
| Egocentric data center and IT hardware data | All twelve rows in the environment | As the catalog lists it | Two of twelve rows, described in short |
| Egocentric server hot-swap and component seating data | Five rows that swap or seat a part | As the catalog lists it | Not covered; named as rows outside the page |
| Egocentric network patching and fiber transceiver data | Patching and transceiver rows | As the catalog lists it | Not covered; named as rows outside the page |
| Stereo data center rack and server hardware data | All twelve rows, stereo and MCAP side | Stereo pair agreed in the skill spec | Two of twelve rows, with the others |
| Hard task data collection | Every catalog row rated Hard | As each row lists it | Not covered; these rows are rated Easy and Medium |
Stated vs not stated
| Item | What the site states | For a rack mounting order |
|---|---|---|
| Catalog capture setup | A staged working set recorded by a multiview rig while the operator performs the task with handheld grippers | Stated for both rows; no head-mounted phone or stereo pair is listed for them |
| Stereo | A stereo pair is a capture choice agreed in the skill spec through the general stereo offer | Not running on these rows as far as the site states; agreed in the spec |
| Camera count, resolution, frame rate for these rows | Not stated | Capture tier agreed in the spec |
| Gripper model and jaw type | Not stated | Agreed in the spec |
| Hand pose in gripper mode | Not stated | Agreed in the spec and confirmed on a Spec Pilot |
| Driver model, torque, fastener type | A driver is named in one row; the rest is Not stated | Not claimed; set in the spec |
| Rack standard, rail and panel sizes, cage nut counts | Not stated | Not claimed; set in the spec |
| Faces and screens | Detected and irreversibly blurred at ingest; reviewer confirms; footage that cannot be de-identified is discarded | Stated; record ships with the data |
| Asset tags, serial numbers, labels | Not stated | Name them in the spec |
| Row status | Available on request | No volume, hours or delivered footage is claimed on this page |
Streams and tasks
| Stream or label | Status on this site | What it carries in a mounting episode |
|---|---|---|
| Head and wrist RGB, depth | Stated; ten streams synced under 2 ms | Keeps the rack, the part and the hands on one timeline |
| 3D hand pose, per-joint visibility | Stated; two hands of 21 joints, with a visibility flag per joint | Carries how the fingers hold a bracket, nut or panel and which joints were hidden |
| Contact and grasp events | Stated | Marks when a bracket, cage nut or panel meets the rack |
| Action segments | Stated; frame-accurate | Separates the fastening, clipping and mounting steps |
| Per-frame instance masks | Stated; stored at 848×480 | Follows the part set as the object in the spec |
| Object labels | Set by your spec | Names the parts and steps in the terms your policy uses |
| Force or tactile data | Glove tier stated; use on these rows Not stated | Added only if a spec includes the glove tier |
Failure modes and QA
| Failure mode | What the site states | What a buyer sees |
|---|---|---|
| Fingers hidden behind a part or the driver | Per-joint visibility flag on hand pose where a spec includes it | A hidden joint flagged as hidden, not guessed |
| Part out of frame | Episode rejected when the manipulated object is out of frame for more than 15 percent of it | Reject log per batch; what the object is gets set in the spec |
| Invalid depth in the manipulation region | Episode rejected when more than 35 percent of depth pixels are invalid; behaviour on rack hardware Not stated | Reject log per batch |
| Sync breach | Rejected beyond the ceiling for more than three consecutive frames | Reject log per batch |
| Calibration drift | Rejected beyond tolerance | Calibration shipped with the episode |
| Bystander in frame | Undocumented bystander rejected; faces and screens blurred and reviewer-confirmed | Reject log per batch; anonymization record ships with the data |
| Spec mismatch | Rejected for a mismatch against the named skill spec | Reject log per batch |
| Blur or sharpness | Not stated | Set in the spec if your policy needs a rule |
Formats
| Format | What the official documentation states | Used for here |
|---|---|---|
| RLDS | A dataset is retrieved as episodes, and each episode holds 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, split into numbered shards (WebDataset README) | Sharded streaming for large training runs |
| MCAP | An open source container file format for multimodal log data, supporting multiple channels of timestamped pre-serialized data (MCAP site) | Multi-stream files; topics and schemas Not stated, agreed in the spec |
| HDF5 and zarr | Stated by Firsthand only | Array storage for custom pipelines |
| Rerun .rrd | Stated by Firsthand only | Multi-stream synchronized playback for review |
Delivery and licensing
| Item | As stated on this site | Note |
|---|---|---|
| Formats | RLDS, LeRobot, WebDataset, HDF5, zarr, Rerun .rrd, MCAP, or raw streams with metadata | Chosen in the skill spec; converter source ships with the data |
| License | Perpetual, irrevocable, worldwide, buyer-owned, non-exclusive by default | Exclusivity is available as a separate term; the executed agreement controls |
| Billing | Per validated hour | Rejected items are recaptured at our cost |
| Privacy | Faces, plates and screens blurred irreversibly; footage that cannot be de-identified is discarded | Anonymization record delivered with the data |
| Timeline | a median of 48 hours to first validated batch where coverage is deep; three to four weeks where thin | Which applies to these rows is Not stated; quoted against your spec |
| Price, minimum order, batch size | Not published for these rows | Set in your quote |
Skill spec
| Spec element | What it decides | Where it shows up |
|---|---|---|
| Rows in scope | Rail brackets, cage nuts and panel, or both | What the cameras see; set per program |
| Steps and order | What one step is and how steps are named | Episode boundaries and action segments; set per program |
| Episode scope | One part, one row or a longer run | Set per program; the site does not state an episode length |
| Object definition | Whether a bracket, a cage nut, a panel or the driver counts as the object | Contact events and the out-of-frame reject rule; set per program |
| Capture mode and streams | Multiview rig with handheld grippers, any stereo pair, wrist views and hand pose | The channels you can read; confirm on the Spec Pilot |
| People and privacy | What may be in frame and how screens and labels are handled | Settled before capture; faces and screens blurred at ingest |
| Accept criteria | What counts as a finished step and what passes QA | Reject log per batch |
| Delivery format | How the data is packaged | RLDS, LeRobot, WebDataset, HDF5, zarr or MCAP |
| License | Who owns the dataset | Perpetual, irrevocable, buyer-owned, non-exclusive by default |
Example footage
One real clip already published on this site, shown as a format and rig example: a head-mounted stereo capture with hands in frame. It does not show rack rail mounting, cage nuts or a blanking panel, and it is not a multiview-rig or handheld-gripper clip.
No rack mounting clip is published on the site, so this is labelled as a format and rig example. Request a sample to see delivered files. See stereo sample page, request an egocentric data sample.
FAQ
Sources
Tell us which of rail bracket fastening, and cage nut and blanking panel mounting are in scope, where each task starts and ends, the capture mode, the privacy rule for screens and labels, and the streams and format you want. We will quote reach, timeline and price against a written spec.