Demonstration corpus

Expert workflows, captured inside the software they happen in.

Every sample is a real modelling session — not a screenshot library. Clicks, the named UI element under each click, the alternatives that were available and rejected, window geometry, narration and per-step file state, all on one clock.

Preparing an imported bumper for surfacing Live capture · CATIA V5 102 actions · 192 recorded alternatives · 357s
42Workflows
13Packages
12Disciplines
2Live trajectories

Production capacity

1,250+Domain experts and instructors
90,000+Engineers trained, last five years
3,600+Hours of content produced
80+Technical deliveries per month

Demonstration data is bounded by how many experts you can put in front of the software, not by how much compute you have. This is the network that records it — practising engineers across mechanical, electrical, embedded and digital domains, already delivering technical programmes every month.

Who we work with

The companies whose work this is

Engineering software vendors on one side, the firms that use their tools all day on the other. The partnerships are why the sessions span thirteen packages; the industry relationships are why the workflows are the ones that actually get done.

Software vendors

11

Partnerships with the companies that build the tools — licences, curriculum input from their own subject-matter experts, and joint delivery.

Dassault Systèmes
MathWorks
Altair
Ansys
MSC Software
Bentley
PTC
Cadence
LDRA
Convergent Science
LSTC

OEM and Tier-1

13

Vehicle makers and their first-tier suppliers.

Daimler
Maruti Suzuki
Honda
Mahindra
MG Motor
Škoda
Bajaj
Motherson
Sona Comstar
SEG Automotive
Spark Minda
Sansera
Greaves

ER&D, engineering services and GCCs

15

The captive centres and services firms where most production CAD work actually happens.

Continental
Magna
Valeo
Faurecia
Hella
Stellantis
Aptiv
Veoneer
Tata Elxsi
Cyient
KPIT
Quest Global
Onward Technologies
Accenture
Infosys

Enterprise and institutions

7
Hitachi
Honeywell
Dell
Afcons
Quess
mjunction
Wadhwani Foundation

What sits behind each card

The image is the artefact. The value is the trace that produced it — recorded by a desktop agent that reads the application's own accessibility tree rather than guessing from pixels.

Action
Click, double-click, drag, scroll and keystroke, timestamped on a single monotonic clock.
Element
The control actually hit — name, role, automationId and bounds, read from UI Automation.
Action space
Sibling controls that were available and not chosen, disabled ones included. The rejected options are the training signal.
Context
Window title and geometry, display bounds, normalised in-window coordinates, and a crop of the region before and after the click.
Intent
Spoken narration on the same clock, plus step marks and typed notes the demonstrator adds while working.
Artefact
The working folder committed at every step, so each action pairs with the file state it produced.
ESC / click to close