Now recruiting capture teams worldwide. Get paid to record first-person video of real work.

Apply to capture

Hard task

Stereo Busbar and Limit Block Assembly Data

Placing a busbar and a limit block, driving a screw sequence and removing the block is one catalog row on the site, "Busbar + limit-block + screws", rated Hard and listed on the Precision Assembly Bench (electronics). This page covers that one row on the stereo and container side: what the catalog states, what a calibrated stereo pair would add as a separate choice, how MCAP fits and what the site does not state. We run custom precision assembly data collection fast and on demand against a written skill spec, with the row status stated exactly as the catalog lists it.
Catalog row
Busbar + limit-block + screws, in Precision Assembly Bench (electronics)
Skill and status
Hard; Available on request
Catalog capture
Multiview rig + handheld grippers
Container
MCAP (.mcap), open source; stereo agreed in the skill spec

Requirements

What does a busbar and limit block capture need that a general bench clip does not?

01

One catalog row, stated exactly

Busbar + limit-block + screws: "Place a busbar and limit block, drive the screw sequence, then remove the block." The row is rated Hard, lists a multiview rig with handheld grippers and is Available on request.

02

A sequence in view from start to finish

The row has three parts: placing, driving the screw sequence and removing the block. 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 part hides.

03

Stereo and MCAP as separate, spec-level choices

A calibrated stereo pair and an MCAP container are agreed in the skill spec. The row does not state either, and this page does not claim them.

04

Limits stated plainly

No busbar, limit block, screw, driver or panel type, no screw count or order and no torque value is stated for the row. Those are written into the spec, and this page gives no instructions.

Definition

What is stereo busbar and limit block assembly data?

Stereo busbar and limit block assembly data is first-person video of a person doing the work named in one catalog row: placing a busbar and a limit block, driving the screw sequence and removing the block. It is recorded from the contributor’s own point of view with two calibrated cameras, and with synchronized sensor streams alongside, so the frames show what the hands are doing with the parts rather than a distant view of a bench. Searchers also phrase it as stereo busbar assembly video, limit block and screw sequence robot data, a precision assembly dataset or custom precision assembly data collection at scale. 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 assembles a busbar. Stereo describes the capture and MCAP describes the container. They are separate choices, and neither is stated on the row itself.

Catalog row

Which catalog row covers busbar and limit block assembly, and what does it say?

One row counts. "Busbar + limit-block + screws" sits in the Precision Assembly Bench (electronics) environment, in the Manufacturing & Workshops sector, whose example line reads "Assembly bench: PCB/electronics, fasteners, fixtures, solder/crimp tools, small parts". The row reads: "Place a busbar and limit block, drive the screw sequence, then remove the block." It is rated Hard, its capture is Multiview rig + handheld grippers and its status is Available on request. The example line is shared by every row in that environment, so it is quoted here as context rather than assigned to this task.

Available on request means the work is scoped and recruited to spec when a buyer asks. It does not mean a stock of busbar footage exists, and this page claims no volume, hours or delivered clips for the row. The first table below reproduces the row, with neighbouring bench rows as context only.

What the row does not say

What does the busbar row leave unstated?

The row says what is done, not what it is done with. It names a busbar, a limit block and screws, and nothing about their type. It gives no screw count, fastening order or tolerance, and states no torque value. Whether the sequence is a fixed pattern or varies between attempts is not stated. A buyer who needs a particular count, order, placement-only run or removal step as an accept criterion writes it into the skill spec, and a Spec Pilot proves it before you scale.

Neighbouring rows

Which nearby precision assembly rows share the bench?

The Precision Assembly Bench lists 15 rows, all Available on request, each with a multiview rig and handheld grippers. The ratings are two Easy, ten Medium and three Hard, and the busbar row is one of the three Hard rows, alongside crimping a terminal and through-hole soldering.

"Screw-fasten housing" and "Torque to spec" are context only. They are described as "Fasten a housing with a driver to torque." and "Torque bolts with a torque wrench.", both rated Medium and Available on request. They are single-purpose fastening rows. The busbar row is the one that combines placing, a screw sequence and removing a block. If your project needs several bench tasks, the precision assembly bench page treats all 15 rows; this page takes the busbar row on its own.

Why it is hard

Why is busbar and screw-sequence work listed as Hard?

The site’s answer is the Skill column. The catalog rates the row 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 site does say is in the row text and in its screwdriving copy. The row is three things in sequence: placing a busbar and limit block, driving "the screw sequence", and removing the block. The site’s screwdriving page adds that the catalog rates the busbar screw sequence Hard because of the sequencing and the stakes of the fastener.

Two things follow for capture, both already addressed on the site. Fingers cover the small items they are placing, and the items cover the surface they go onto, which is why hand pose carries a per-joint visibility flag for hidden fingers. And a sequence only makes sense when every step is visible and labeled, so where each step starts and ends is written into the spec. The challenge table below maps each difficulty to the stream or label the site already states, and says Not stated where nothing is.

Capture

Is the Busbar + limit-block + screws row captured in stereo?

The catalog lists one capture mode for the row: Multiview rig + handheld grippers. The site describes it 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 row does not state stereo capture, and this page does not describe it as stereo or as head-mounted phone capture. Stereo reaches this row only through the site’s general stereo offer: a capture choice agreed in the skill spec and confirmed on a Spec Pilot.

The site describes two stereo setups and does not say which one a busbar order would use. The off-the-shelf stereo head rig, dataset 06, is dual fisheye cameras at 1080p per eye with a 62 mm baseline, per-unit calibration, a 9-axis IMU and hand-tracking output, shipped as MCAP. The hard-environments stack is a global-shutter 4K/60 head camera, two 1080p/60 wrist cameras, a depth sensor at 848×480 and 30 fps and 200 Hz 6-DoF IMUs. Which of these apply to a staged gripper setup, and how hand pose is recorded when the operator holds a gripper, is Not stated. Confirm both in the skill spec.

What stereo adds

What would a stereo pair add to a busbar and screw sequence?

The site states that a stereo pair at human-eye spacing makes depth recoverable from every frame pair, and that a calibrated pair measures disparity between two views at a fixed, known baseline rather than guessing depth from a single frame. For a busbar and limit block, that puts the parts and the work surface in the same capture as the hands. The site gives no depth accuracy figure for these tasks and no seated-state label, so what a buyer does with that depth is their pipeline’s question.

The site also states that small fasteners can fall below a depth sensor’s reliable floor, that hand pose stays valid at that range and that metric depth on sub-centimetre parts is flagged rather than interpolated. No depth floor is stated for this row, so ask for it to be confirmed in the spec. Calibration is re-solved at the start and end of every session under a 0.28 px RMS reprojection gate, and streams are hardware-triggered onto one clock with a 2.0 ms cross-stream ceiling.

Episodes

What does each busbar and limit block episode contain?

Each attempt is delivered as one episode, and this row needs a decision up front about what one attempt is: the whole three-part sequence, or a single phase such as placement only. The site sets no episode length, so the spec does. 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.

Action segments divide an episode into spans, each carrying start_ns, end_ns, verb and noun, from a taxonomy of 97 verbs and 512 nouns, annotated to the frame and human-reviewed. A spec that says only "assemble the busbar" gives one long segment; one that names the phases gives a sequence you can slice, for example one span per screw driven if the spec defines it so. The site lists no label for the outcome of a step, such as a seated state, a screw order or a completion, and force, tactile and torque readings are not among the standard streams, so ask for any such label in the spec.

The GR00T N1 paper says its human video datasets do not include explicit action labels, and that hand-held robot grippers speed up collection but leave a mismatch with the downstream robot. Firsthand captures people, not robots, so using the episodes for a specific robot means your own retargeting step.

Neighbouring pages

How does this page differ from the egocentric busbar page and the fastening pages?

Several pages touch the same work, and only one other takes the busbar row as its main topic. The egocentric busbar page covers the same single row from the first-person side: the catalog row, labels, privacy and delivery. This page covers it on the stereo and MCAP side, and neither page claims stereo is part of the row itself.

The stereo screwdriving and fastening page covers the Drive screws with driver row, rated Medium, and the stereo torque and bolt fastening page covers two Medium fastening rows. The stereo wire crimping and harness page covers Crimp connector, which is Hard, and Route + clip harness. None of them has the busbar row as its main topic. The comparison table below sets each page against this one, and the egocentric stereo MCAP page is the format page for the container in general.

MCAP

What is MCAP, and what can a busbar assembly delivery put in it?

MCAP is an open source container file format for multimodal log data, supporting multiple channels of timestamped pre-serialized data. It is serialization-agnostic, so messages can be Protobuf, DDS (CDR), ROS, JSON and more. Its design is row-oriented and append-only, it stores schemas alongside the data, and it offers an optional index plus optional LZ4 or Zstandard chunk compression and optional CRC checksums. Those facts come from mcap.dev and the foxglove/mcap repository, both linked below. Firsthand is not affiliated with Foxglove or the MCAP maintainers.

Firsthand offers MCAP delivery, and dataset 06 is stated as shipping as MCAP. For this row the site states a stereo pair, depth with confidence maps, hand pose, IMU, contact events, action segments and calibration elsewhere. It does not state which of those are channels in an MCAP file, how they are named, what encoding they use or at what rate. No topic name, message schema or rate is stated on this page, and none should be assumed. Name the streams that matter in the skill spec and confirm them on a Spec Pilot batch. The stream map below sets each stream beside what the site states about it.

Delivery and license

Which other formats and which license apply?

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, and MCAP can ship alone or beside any of them. The episodes follow the same episode schema as every other Firsthand collection, so a loader that reads another Firsthand dataset reads this one without changes. Which container suits a lab depends on its reader and its training loop, and the site does not rank them.

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. Official documentation for MCAP, RLDS, LeRobot and WebDataset is linked in the sources below.

Validation

How is the data validated and accepted?

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 cross-stream sync error above a 2.0 ms ceiling, the manipulated object out of frame for more than 15 percent of the episode, or more than 35 percent of depth pixels in the manipulation region invalid, and a human reviewer then checks each one. Only footage that clears the criteria is billed as a validated hour. These are reject thresholds, not a stated pass rate.

For this row, the spec has to say which item counts as the manipulated object at each step and where the manipulation region is, because the busbar, the limit block and the screws are different items at different moments. What counts as a finished sequence is also written down, since the site states no outcome definition. Rejected items are recaptured at our cost.

Capture and privacy

How are contributors and their work protected?

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.

Printed text or markings on a panel or part are not a listed blur category, so this page does not claim they are blurred. This page makes no safety or compliance claim, because the site makes none for this row, and it gives no instructions for any step. None of this is legal advice.

Speed and scale

How fast and at what scale can a custom busbar assembly dataset be collected?

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 row is Available on request, so the range that applies 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.

Busbar and limit block assembly 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 this row, and none of its off-the-shelf dataset descriptions names it, so treat it as a custom collection. Only dataset 06, the stereo head rig, is stated as shipping as MCAP, and a lab can use that stock footage to check the rig and the format before commissioning the task.

Getting started

How do you start a pilot?

Describe the sequence your policy needs: what is placed, what is fastened and what is removed, how many screws and in what order, where each step starts and ends and what counts as a finished sequence. Then name the streams you want, whether stereo is part of the capture, and whether MCAP is the only delivery or sits beside RLDS, LeRobot or WebDataset. 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, and rejected episodes and recaptures are never billed. Counts of sites, episodes and hours are set in the skill spec. Our skill spec guide walks through how to write one.

At a glance

What you get.

Catalog row: Busbar + limit-block + screws
"Place a busbar and limit block, drive the screw sequence, then remove the block."; Hard; Precision Assembly Bench (electronics); Available on request
Sector and environment examples
Manufacturing & Workshops; "Assembly bench: PCB/electronics, fasteners, fixtures, solder/crimp tools, small parts"
Catalog capture setup
Multiview rig + handheld grippers: 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
Stereo on this row
Not stated. Reaches the row only through the general stereo offer, agreed in the skill spec and confirmed on a Spec Pilot
Stereo head rig (dataset 06)
Dual fisheye, 1080p per eye, 62 mm baseline, per-unit calibration, 9-axis IMU, hand-tracking output; shipped as MCAP
Streams and sync
Ten streams, hardware-triggered onto one clock; 2.0 ms cross-stream ceiling
Hand pose
21 joints per hand with a per-joint visibility flag
Busbar, limit block, screw, driver and panel types; screw count and order; torque value
Not stated; agreed in the skill spec
MCAP topics, schemas and rates
Not stated; agreed in the skill spec
Delivered hours
None claimed on this page
License
Perpetual, irrevocable, buyer-owned, non-exclusive by default

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.

Live catalog rows

Which catalog row covers busbar and limit block assembly, and which rows sit beside it?

The busbar row as the catalog states it, with neighbouring bench rows as context only, reproduced without change. No delivered hours are claimed.
Task (as listed)Description (as listed)EnvironmentSkillCapture setupStatusRole on this page
Busbar + limit-block + screwsPlace a busbar and limit block, drive the screw sequence, then remove the block.Precision Assembly Bench (electronics)HardMultiview rig + handheld grippersAvailable on requestThe row this page covers
Screw-fasten housingFasten a housing with a driver to torque.Precision Assembly Bench (electronics)MediumMultiview rig + handheld grippersAvailable on requestNearby context only
Torque to specTorque bolts with a torque wrench.Precision Assembly Bench (electronics)MediumMultiview rig + handheld grippersAvailable on requestNearby context only
Crimp connectorCrimp a terminal onto a wire.Precision Assembly Bench (electronics)HardMultiview rig + handheld grippersAvailable on requestNearby context only

Comparison

How does this page compare with the egocentric sibling and the closest stereo assembly pages?

Each page described only as the site states it. No delivered hours are claimed for any of them.
PageMain subjectBusbar row on that pageHow this page differs
This pageThe "Busbar + limit-block + screws" row, with stereo and MCAP as spec-level choicesThe main topicStereo and container side of the single busbar row
Egocentric busbar and limit block assembly dataThe same single row, first-person sideThe main topicCovers the row from the egocentric side; this page covers stereo and MCAP
Stereo screwdriving and fastening dataThe Drive screws with driver row, Medium, Available on requestNot named on that pageA single driving row; the busbar row adds placing, a sequence and removal
Stereo torque and bolt fastening dataTwo rows: Torque to spec and Screw-fasten housing, Medium, Available on requestNot one of its two rowsTorque and housing fastening rather than a placed busbar
Stereo wire crimping and harness assembly dataTwo rows: Crimp connector (Hard) and Route + clip harness (Medium)Not one of its two rowsCrimping and harness work rather than a busbar sequence
Egocentric precision assembly bench dataAll 15 bench rows, all Available on requestOne of 15 rows; one of the three Hard rowsCovers the whole bench
Egocentric stereo data in MCAPThe MCAP delivery format for stereo capture in generalNot covered; format pageApplies the format to one row
Hard-task data collectionThe hub of rows the catalog rates HardThe row is in the Hard-row table and links hereOne row out of the hub

Capture setup

What is the capture setup for the busbar row?

The capture setup as stated on this site. Counts of sites, contributors, episodes and hours are set in the skill spec.
PartAs stated on this site
Capture mode (Busbar + limit-block + screws)Multiview rig + handheld grippers, as the catalog lists it
What that meansA 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
Stereo head rig (dataset 06)Dual fisheye, 1080p per eye, 62 mm baseline, per-unit calibration, 9-axis IMU, hand-tracking output; shipped as MCAP
Hard-environments stack4K/60 global-shutter head camera, 120° lens; two 1080p/60 wrist cameras; depth 848×480 at 30 fps; 200 Hz 6-DoF IMU
SyncHardware-triggered onto one clock; 2.0 ms cross-stream ceiling
CalibrationRe-solved at the start and end of every session; 0.28 px RMS gate
Hand pose21 joints per hand, 3D, in metres in the head-camera frame; per-joint visibility flag
Stereo on this rowNot stated; a separate offer, agreed in the skill spec and confirmed on a Spec Pilot
Which streams apply to the gripper setupNot stated; confirmed in the skill spec

Capture challenges

Bench challenge × what goes wrong × stated stream or label

Each capture challenge mapped to a stream or label this site already states. Where nothing is stated, the row says so.
Bench challengeWhat goes wrongStated stream or label
Hands cover the partsFingers hide the busbar, block or screw being worked3D 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 partThe hand and the item touch in quick successionContact events mark when a hand meets an item; no finer contact label is stated
Small fasteners at close rangeDepth sensors have a reliable floor and sub-centimetre parts can fall below itThe site states hand pose stays valid at that range and that metric depth on sub-centimetre parts is flagged rather than interpolated; reject if more than 35% of depth pixels in the manipulation region are invalid
Placing, driving and removing as separate stepsIt is unclear where one step ends and the next beginsAction segments, one per step as written in the spec; no accuracy figure for step labels is stated
Order of the screw sequenceThe row says "the screw sequence", but no count or order is statedNot stated: the count and order are written into the spec; a segment per screw only if the spec defines it
Block seated or removedWhether a block or busbar is in place is a visual stateNot stated: no seated-state or completion label is listed
Fastening forceHow hard a screw is drivenNot stated: no force, torque or tactile stream is listed

Stream map

Streams for busbar assembly and what the site states about an MCAP file

Left to right: the stream or item, what the site states about it, and what the site states about it in MCAP. “Not stated” means the site does not say.
Stream or itemWhat the site statesIn an MCAP delivery, as the site states it
Stereo pairDual fisheye, 1080p per eye, 62 mm baseline (dataset 06); for this row, agreed in the skill specDataset 06 is stated as shipped as MCAP; channel layout not stated
Depth with confidence mapsRecovered from the calibrated stereo pair; confidence map masks low-confidence regionsNot stated
Hand pose21 joints per hand with a per-joint visibility flagChannel layout and joint order not stated
Wrist viewsWrist camera available alongside the head cameraNot stated
IMU9-axis (dataset 06); 6-DoF at 200 Hz (hard-environments stack)Channel layout and rate not stated
Contact events, action segmentsListed in the site’s episode schema; action segments carry start_ns, end_ns, verb and nounNot stated
CalibrationMeasured every session and shipped with the episodePlacement in the file not stated
Topic names, schemas, encoding, ratesNot statedAgreed in the skill spec

Spec checklist

What goes in the skill spec for a busbar and limit block collection?

Decisions the site leaves to the written spec.
Spec itemQuestion to settleHow it is settled
ScopeThe whole three-part sequence, or one phase of itWritten in the spec; proven on a Spec Pilot
ItemsWhat is placed, what is fastened and what is removedNamed in the spec
SequenceHow many screws and in what orderWritten in the spec
Step boundariesWhere each action segment starts and endsVerb and noun per step
Stereo and streamsWhether a stereo pair is part of the capture, and which streams are deliveredAgreed in the spec; confirmed on a Spec Pilot
Accept criteriaWhat counts as finished, and what is a rejectWritten before capture; QA checks against it
Delivery formatMCAP alone or beside another format; topics, schemas and rates if MCAPMCAP, RLDS, LeRobot, WebDataset, HDF5, zarr or Rerun .rrd, or raw streams; MCAP details agreed in the spec
Privacy and licenseHandling of anyone, screens and markings in frame; ownershipBlurring as stated above; perpetual, buyer-owned, non-exclusive by default

Delivered vs not stated

What is delivered and what is not stated

Delivered items are stated elsewhere on this site. Items marked not stated are not promised on this page.
ItemStatusDetail
Action segmentsDeliveredstart_ns, end_ns, verb, noun, one per step
3D hand poseDelivered21 joints per hand; per-joint visibility flag for occluded fingers
Contact eventsDeliveredThe moment a hand meets an item
Per-frame instance masksDeliveredStored at 848×480
Consent and anonymization recordsDeliveredConsent artefact IDs per episode; anonymization record shipped with the data
FormatsDeliveredMCAP, RLDS, LeRobot, WebDataset, HDF5, zarr, Rerun .rrd or raw streams with metadata
Busbar, limit block, screw, driver and panel typesNot statedAgreed in the skill spec
Screw count, order and torque valueNot statedAgreed in the skill spec
Seated-state, completion or defect labelsNot statedNo such label is listed
MCAP topics, schemas and ratesNot statedAgreed in the skill spec
Cycle times and throughputNot statedNo such figure is listed
Number of sites, episodes and hoursNot statedSet per program in the skill spec

Example footage

What does egocentric stereo footage look like?

One real clip already published on this site. It is a format and rig example: a head-mounted stereo capture with hands in frame. It is not busbar assembly, screwdriving or any task from this page.

egocentric_stereo_sample.mp4 · head-mounted stereo · hands in frame · 1920 × 1080 web preview · rig example, not a busbar clip

No busbar or limit block clip is published on the site, so this is the nearest stereo clip, labelled as a rig example. Request a sample to see delivered files. See stereo sample page, request an egocentric data sample.

FAQ

Stereo busbar assembly video, answered.

What is stereo busbar and limit block assembly data?
First-person video from two calibrated cameras of a paid, consented contributor placing a busbar and limit block, driving the screw sequence and removing the block, captured to a written skill spec, with hand pose and sensor streams alongside.
Which catalog row covers it, and what is its status?
One row in the Precision Assembly Bench (electronics): "Busbar + limit-block + screws" ("Place a busbar and limit block, drive the screw sequence, then remove the block."). It is rated Hard and Available on request. This page claims no volume, hours or delivered clips.
Is the row captured in stereo?
The catalog lists Multiview rig + handheld grippers. Stereo is not stated for the row; it reaches it through the general stereo offer, agreed in the skill spec and confirmed on a Spec Pilot.
Can it be delivered as MCAP, and what is in the file?
Yes. Firsthand offers MCAP delivery, and dataset 06 ships as MCAP. Topic names, message schemas and rates are Not stated on the site and are agreed in the skill spec.
Does the site name busbar, limit block or screw types, counts or torque values?
No. The site states no busbar, limit block, screw, driver or panel type, no screw count or order, no torque value or tolerance, and no seated-state or defect label for this row. Those details are agreed in the skill spec.
How is this different from the egocentric busbar page?
Both cover the same single catalog row. The egocentric page covers the first-person side; this page covers the stereo and MCAP side, where stereo is a spec-level choice rather than part of the row.
Is there an off-the-shelf busbar assembly dataset?
Not stated. This row is a custom collection, at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. Only the stereo head rig, dataset 06, is stated as MCAP.
How fast can a fast, on-demand busbar assembly dataset arrive, and who owns it?
A median of a median of 48 hours from signed spec to first validated batch where coverage is deep, and three to four weeks where it is thin; the row is Available on request, so the range is confirmed when the spec is quoted. The buyer owns the data under a perpetual, non-exclusive commercial license by default.

Sources

Where are MCAP and the delivery formats documented?

Request a custom busbar and limit block assembly dataset.

Tell us what is placed, what is fastened and what is removed, how many screws and in what order, where each step starts and ends, what counts as finished, whether stereo and MCAP are part of the delivery, and the angles you want. We will quote reach, timeline and price against a written spec, with a first validated batch proven on a Spec Pilot.