Human activity data / Nordic–Baltic focus

Human activity data, collected to your specification.

Scope human demonstrations of industrial tasks for robotics and physical AI. You define the task and what the recordings need to show. We assess feasibility, site access and timing before any commitment.

Define the task → assess feasibility → agree a pilot. A scoped delivery can include accepted video, metadata and optional annotations.

Illustrative workshop scene: gloved technician working on a metal valve assemblyIllustrative scene / Industrial maintenance / Not dataset footage
Buyer-directed collectionYour task. Your specification. A scoped recording program.
Industrial environmentsManufacturing, technology, mining and technical service.
Nordic–Baltic focusLocal conditions considered. Availability confirmed per project.
01 / Where the work happens

Industry is in
the details.

The part being aligned. The connector being inserted. The tool selected before the next step. Define the interaction your model needs to observe.

02 / The Northern context

Specific environments.
Different demands.

Gloved hands. Precision parts. Workshop tools. Seasonal light. The environment changes the task.

Explore the regional focus ↗
  1. 01
    Advanced industrial workflows

    Assembly, maintenance and technical service tasks where sequence, tool choice and object state matter.

  2. 02
    Workwear & physical constraints

    Specify gloves, PPE, restricted reach and approved working postures rather than treating every demonstration as interchangeable.

  3. 03
    Seasonal & environmental variation

    Where relevant, scope daylight, cold conditions, wet surfaces and indoor–outdoor transitions. Conditions are recorded, not assumed.

  4. 04
    Local context, explicitly defined

    Equipment, instructions, labels and spoken language can be part of the brief. Availability is assessed before a program is confirmed.

03 / Build around an actual task

What would you
ask us to capture?

Explore illustrative collection briefs. These define possible recording requirements; they are not samples from an existing dataset.

Illustrative specification. Capture setup, annotations and access are subject to feasibility and pilot review.
04 / From requirements to recording

A collection program.
Built to your brief.

Begin with a defined learning objective and a small pilot. Agree the acceptance criteria before expanding the recording scope.

01 / Scope

Define the task.

Actions, objects, environment, target market, variations and intended use. Specify what success and failure should look like.

02 / Pilot

Validate the setup.

Assess permissions, participant suitability, camera visibility, annotation needs and measurable acceptance criteria.

03 / Collect

Capture & review.

Record the agreed tasks. Review clips against the protocol, document decisions and manage permitted re-recordings.

04 / Deliver

Package the data.

Supply accepted footage with agreed metadata, review records, annotations and licensing documentation.

See the complete collection process ↗

05 / Regional focus

Baltic and Nordic
target markets.

We assess project requests for six Baltic and Nordic target markets. Site access, participants, language requirements and equipment are assessed for each brief.

EstoniaLatviaLithuaniaSwedenNorwayDenmark
Explore countries & industrial context ↗Finland and Iceland: potential expansion markets. Country highlights do not represent established collection capacity.
Northern Europe map: Estonia, Latvia, Lithuania, Sweden, Norway and Denmark highlighted in orange; Finland and Iceland shown as potential expansion
06 / What the buyer receives

More useful than
a folder of footage.

Agree the schema and evidence needed to evaluate a batch. The deliverable is defined in the proposal, including what is not captured or measured.

Video, context and a review trail.

Accepted recordings can be paired with task IDs, recording conditions, camera information and review outcomes. Optional annotation layers are scoped against your requirements.

Human RGB video does not automatically include 3D pose, depth, force or executable robot trajectories. Sensor streams and derived labels require a suitable rig and separate validation.

Task boundariesObject labelsOutcome & retry tagsAgreed file schema

Technical scoping for AI teams ↗

collection-example/  # illustrative
  footage/           # accepted video files
  metadata/          # clip and capture records
  annotations/       # if commissioned
  review/            # QA decisions and reasons
  documentation/     # datasheet and agreed rights
  manifest.json      # agreed file index
07 / Quality, rights & permissions

Define the standard.
Document the result.

The buyer brief sets the acceptance bar. Permissions and privacy requirements are addressed before recording, not added after collection.

Capture

Visible interactions

Framing, focus, lighting, continuity and hand–object visibility checked against agreed rules.

Review

Clear decisions

Accepted, rejected and re-recording decisions tied to the collection specification.

Permissions

Authorized recording

Participant, workplace and intended-use permissions defined for the project.

Privacy

Defined boundaries

Confidential information, bystanders, screens, retention and delivery access scoped in advance.

Review the quality & permissions framework ↗

For businesses

Your workplace.
Your expertise.

Explore a recording project built around authorized tasks, agreed confidentiality boundaries and compensation defined in advance.

For businesses
For contributors

Your skills
have value.

Register interest in demonstrating tasks you know. Suitable assignments depend on location, skills and approved projects.

For contributors
08 / Before you commission

The practical questions.

A clear starting point for your first collection brief.

Can we request a specific industrial task?

Yes. Describe the actions, equipment, environment and variations you need. We assess feasibility, permissions and participant suitability before confirming scope. Specialist or restricted settings may require a separate site arrangement.

Do you already operate in every highlighted country?

No established country-wide capacity is claimed. The map shows target markets. Recording locations, contributors, equipment and delivery timing are confirmed project by project.

Can human video be used directly as robot action data?

Not automatically. Human video may support learning or evaluation depending on your pipeline, but it does not itself provide calibrated robot actions, force or tactile measurements. Required sensors, labels and any transformation pipeline must be scoped and validated separately.

Are there public dataset samples here?

The task briefs and photography on this site are illustrative. There are no captured dataset samples published here yet. A representative pilot should be agreed before a larger collection commitment.

How are price and timing determined?

By task complexity, specialist recruitment, site access, equipment, accepted recording hours, annotation and review requirements. A proposal is scoped after requirements are assessed; there is no fixed price or guaranteed turnaround published here.

Start with the task

What does your AI
need to learn?

Request a collection brief