Task family

Egocentric Food and Beverage Manufacturing Video Data

Inspecting and pulling defective products, running a filling line, sealing and labelling packs and washing down equipment, captured first-person in food and beverage plants against a spec you write, for food manufacturing robot training data and fast, on-demand custom collection.
Plant tasks
Eight catalog rows
Status
All Ready to deploy
Billing
Per validated hour
License
Buyer-owned

Requirements

What does food and beverage manufacturing data need?

01

A named plant task list

Inspection, line operation, packaging and sealing, and sanitation are different sequences, so a spec names each one and the plant setting it covers.

02

Both hands and the product in frame

A head-mounted view keeps both hands, the product and the machine panel or belt in view while items are checked, fed, sealed or pulled.

03

Hand pose through every handling step

3D hand pose with per-joint visibility carries how the fingers hold, turn, place and release each item and how they operate a panel.

04

Step boundaries on the same clock

Frame-accurate action segments mark where inspecting ends, where line feeding starts and where sealing and labelling begin, aligned to video and depth.

05

Rights you can ship on

A perpetual, buyer-owned commercial license backed by a documented consent chain.

Why it matters

What is egocentric food and beverage manufacturing data, and why does it need its own page?

Egocentric food and beverage manufacturing video data is real-world, first-person video of work in a plant that makes packaged food or drink. It is recorded from the worker viewpoint, with depth, 3D hand pose, contact events and frame-accurate action segments aligned on one hardware clock. The tasks it covers are the ones the site states in its task catalog, under the Food & Beverage Manufacturing Plant environment: inspecting and removing defective products, operating and monitoring a filling line, packaging, sealing and labelling, running a production line, foreign-object inspection and sanitation washdown.

The produce packing page covers fruit sorting and packing on a farm, and the print and packaging page covers print and packaging work. Neither is about a manufacturing plant that fills, seals and labels food and drink. This page covers the plant sequence, from a product arriving on the line to a sealed, labelled pack and a washed-down production area.

Setting

Which plant tasks can be captured?

The site states plant work in one catalog environment, Food & Beverage Manufacturing Plant, under the Food & Beverage sector. Its examples line reads "Packaged food factory, bottling plant, meat processing facility, ready-meal production line." Eight task rows sit under it, four rated Easy and four rated Medium, and every one lists a head-mounted phone or multiview rig as the capture mode.

All eight rows carry the status Ready to deploy. The site defines that status as contributors and site access set up, with capture starting once a spec is signed. This page uses all eight rows and lists them in the table below as the catalog states them.

Inspection

How are the inspection rows described?

Two rows are about looking at product and removing what should not go forward. The first reads "Inspect and remove defective products using an inspection light and gloves," described as holding products under the inspection light, spotting defects and pulling them from the line. The second is QA / Foreign-Object Inspection, described as inspecting items on the belt for foreign objects and defects and removing anything suspect.

Both are rated Easy. What counts as a defect or foreign object, and the product inspected, are Not stated and are set in the written spec. The gloves in the first row are part of the task and do not imply tactile data.

Line operation

How are the filling line and production line rows described?

Operate and monitor a filling line using control panels and gauges is described as starting the filling line, reading gauges, adjusting settings on the panel and clearing minor jams. Production Line Operation is described as feeding product onto the line, monitoring the machines and packing finished goods at the end. Both are rated Medium.

These are the rows where the hands work a control panel as well as the product. Machine names, line speeds and panel layouts are Not stated.

Packaging

How are the packaging, sealing and labelling rows described?

Packaging & Sealing is described as filling packages, running them through the sealer and applying labels before casing. A second row, "Seal and label packaged goods using a heat sealer and label applicator," is described as feeding packs into the heat sealer, checking the seal and running them through the label applicator. Both are rated Easy.

Between them they cover the end of the line: fill, seal, check the seal, label and case. The site does not state pack formats, pack counts or label contents. It also does not describe a seal check as a recorded quality label, so no seal-quality outcome is claimed here.

Sanitation

How are the sanitation and washdown rows described?

Sanitation Washdown is described as rinsing equipment with hoses, applying foam sanitizer, scrubbing and rinsing down the production area. The longer row, "Wash down and sanitize production equipment using hoses and foam sanitizer," is described as disassembling guards, hosing down equipment, foaming, scrubbing and rinsing to a sanitary finish. Both are rated Medium.

These are the wet, multi-step rows, and they are included because the catalog states them. "Sanitary finish" is catalog wording and not a standard: the site states no food-safety, hygiene or cleaning certification, and none is claimed here. Any acceptance rule for a washdown is written into the spec.

Environments

Where is it captured and how are workers protected?

The catalog places the work in a food or beverage plant, and the environment page states that contributors are recruited to spec in Western program markets, so the footage reflects how this work is done in North American and European businesses. The site names no plant, company, city or region, and it does not state capture at a customer own plant. Access and schedule are agreed in the spec, and the number of plants is Not stated.

The privacy steps the site states are these. 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, a reviewer confirms the result before anything ships, and the anonymization record is delivered with the data. Physical-safety measures, PPE rules and plant access terms are Not stated.

Capture setup

How is plant work captured from a first-person view?

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. All eight plant rows list this single setup. On the rig tier, every stream is aligned to a shared clock and checked at the sync gate before an hour is billed.

Camera count, resolution and frame rate for plant work are Not stated, so session length and volume are quoted against your spec.

Streams and labels

What does each plant episode contain?

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. In a plant, hand pose tracks how the fingers hold and place each item and work a panel, contact events mark when fingers meet a product, a pack or a control, and action segments mark each step.

Object labels use the terms your spec sets. Force or tactile data, and defect, seal or quality-outcome labels, are Not stated for these rows. If your policy needs them, they are defined in the spec. Tactile gloves are a separate capture tier with their own page.

Delivery

How is the data labeled and delivered?

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. Action segments are the step labels, and any further object labels follow the spec.

Every batch is validated against signed accept criteria before it ships, with a reject log, and delivery is rolling, per validated batch. Billing is per validated hour, and rejected items are recaptured at our cost.

Why it is hard

Why are deformable, wet and repetitive products hard for robot learning?

A survey of more than 150 studies states that, compared with rigid objects, deformable object manipulation poses significant challenges for perception, modeling and manipulation, because deformable objects have an infinite-dimensional state space and complex dynamics. The same survey states that data-driven approaches can address some of those challenges. That is the case for demonstrations recorded from the worker viewpoint, where the hands and the product are in view together.

The site does not state which products are deformable, so this page makes no claim about any product. It does state wet washdown rows and belt-side inspection rows. Wet work and item-after-item handling are hard to cover with a few recordings, which is why a spec names the tasks, the products and the number of sequences. Cycle times and repetition rates are Not stated.

Fast · on demand

How fast can a custom food manufacturing dataset be collected?

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 plant work, so the timeline is quoted against your spec.

On-demand top-ups run against the same spec and accept criteria after each training run.

The spec

How do you start a pilot?

You describe the plant tasks, products and sequence 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.

At a glance

What you get.

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

Which catalog rows cover food and beverage manufacturing?

The eight Food & Beverage Manufacturing Plant rows with the catalog description, skill rating and status as listed. Every row lists a head-mounted phone or multiview rig as capture mode.
Task familyCatalog task and descriptionSkillStatus
Inspect and pullInspect and remove defective products using an inspection light and gloves: hold products under the inspection light, spot defects and pull them from the lineEasyReady to deploy
Foreign-object inspectionQA / Foreign-Object Inspection: inspect items on the belt for foreign objects and defects and remove anything suspectEasyReady to deploy
Filling lineOperate and monitor a filling line using control panels and gauges: start the filling line, read gauges, adjust settings on the panel and clear minor jamsMediumReady to deploy
Production lineProduction Line Operation: feed product onto the line, monitor the machines and pack finished goods at the endMediumReady to deploy
Packaging and sealingPackaging & Sealing: fill packages, run them through the sealer and apply labels before casingEasyReady to deploy
Seal and labelSeal and label packaged goods using a heat sealer and label applicator: feed packs into the heat sealer, check the seal and run them through the label applicatorEasyReady to deploy
SanitationSanitation Washdown: rinse equipment with hoses, apply foam sanitizer, scrub and rinse down the production areaMediumReady to deploy
Equipment washdownWash down and sanitize production equipment using hoses and foam sanitizer: disassemble guards, hose down equipment, foam, scrub and rinse to a sanitary finishMediumReady to deploy

Streams and tasks

How do the stated streams map to plant tasks?

The streams the site states for Firsthand custom collections, set against what each carries in a food or beverage plant episode.
Stream or labelStatus on this siteWhat it carries in a plant episode
Head and wrist RGB, depthStated; ten streams synced under 2 msKeeps the product, the belt or panel and both hands on one timeline
3D hand pose, per-joint visibilityStatedCarries how the fingers hold, turn, place and release each item and work a panel
Contact and grasp eventsStatedMarks when fingers meet a product, a pack, a control or a hose
Action segmentsStated; frame-accurateSeparates inspecting, feeding, filling, sealing, labelling and washing down
Object labelsSet by your specNames the products and steps in the terms your policy uses

What is not stated

Which plant details does the site not state?

Food and beverage manufacturing fields the site does not state, and where each one is settled.
ItemStatus on this siteWhere it is settled
Products, ingredients, product typesNot stated; the examples line names plant settings onlyThe written spec
Machine, equipment or tool modelsNot stated; task rows name tool types onlyThe written spec
Plant types or sizes, regions, number of plantsNot stated beyond the examples line and Western program marketsThe written spec
Line speeds, throughput, cycle times, yieldsNot statedQuoted against your spec
Number of episodes or workersNot statedThe written spec
Food-safety, hygiene or quality-system certificationsNot statedNot claimed on this page
Defect, seal or quality-outcome labelsNot statedThe written spec, if needed
Force or tactile dataNot stated for these rowsThe written spec, if needed
Robot or policy resultsNot statedNot claimed on this page

Formats

Which formats carry food and beverage manufacturing data?

Delivery formats stated on the site, set against what each format official documentation states where the documentation was read.
FormatWhat the official documentation statesUsed for here
RLDSA dataset is retrieved as episodes, and each episode holds a dataset of steps (RLDS repository README)Episode-based training loaders
LeRobotLeRobotDataset 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
WebDatasetTar files in which files that belong together share a basename, split into numbered shards (WebDataset README)Sharded streaming for large training runs
HDF5 and zarrStated by Firsthand onlyArray storage for custom pipelines
Rerun .rrdStated by Firsthand onlyMulti-stream synchronized playback for review

FAQ

Food manufacturing robot training data, answered.

What is egocentric food and beverage manufacturing video data?
Real-world, first-person video of plant work, such as inspecting and pulling defective products, running a filling line, sealing and labelling packs and washing down equipment, captured against a written spec with 3D hand pose, depth and action segments.
Which plant tasks does the site state?
The task catalog lists eight rows under Food & Beverage Manufacturing Plant: defective-product inspection, foreign-object inspection, filling line operation, production line operation, packaging and sealing, seal and label, sanitation washdown and equipment washdown. Four are rated Easy and four Medium, and all are Ready to deploy.
Does the site state products, machines, line speeds or certifications?
No. The examples line names a packaged food factory, bottling plant, meat processing facility and ready-meal production line, but products, machine models, line speeds, cycle times, yields and any food-safety or hygiene certification are Not stated.
Are force data or defect labels included?
Not stated for these rows. They are defined in the written spec if your policy needs them. The site states hand pose, depth, contact events and action segments. The gloves named in the inspection row are part of the task, not a tactile capture.
How is privacy handled?
Faces, plates and screens are detected and irreversibly blurred at ingest, and a reviewer confirms the result. Each episode links to a signed contributor release, and the anonymization record ships with the data. PPE and plant safety rules are Not stated.
How fast can a custom food manufacturing dataset be collected?
Where coverage is deep, the first validated batch lands in a median of 48 hours from signed spec. Thin environments typically take three to four weeks. All eight plant rows are Ready to deploy, and the timeline is quoted against your spec.
How do you start a pilot?
Describe the plant tasks, products and sequence you need. We write a spec, quote against it, and a Spec Pilot proves the accept criteria before you scale.

Sources

Where are the deformable-object claim and delivery formats documented?

Request a custom dataset.

Tell us the plant tasks, products and sequence your policy needs to handle. 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.