Tadano XR Service & Maintenance

Working definition

What we are building toward

An XR service and maintenance training platform for Tadano crawler cranes. The system should help technicians learn, rehearse, and validate maintenance procedures without relocating massive equipment or relying only on static manuals.

What this is not

This is not a crane operator simulator pitch. The proposal thread repeatedly corrected the direction toward service and maintenance, not load-operation training.

Keep every technical sketch, prototype, scope note, and demo idea anchored to maintenance tasks, diagnostic flow, technician knowledge transfer, and service procedure quality.

Current technical assumptions

MVP scope

Start with 3-6 maintenance lessons as a proof of concept.
Use modular lesson structure so future procedures can be added without redesigning the whole platform.
Represent candidate crane systems clearly before promising full-crane coverage.

Candidate procedures

Air filter change.
Engine-tray lowering mechanism.
Additional service/inspection procedures once Tadano supplies curriculum, photos, video, or procedure references.

Hardware direction

Enterprise XR headset framing: Pico, Meta Quest, or Samsung Galaxy XR depending on final positioning.
No real-world control integration is assumed for the baseline concept.
Virtual hands/controllers are acceptable for interaction language.

Technical discovery needed

Confirm exact target crane model(s) and available reference materials.
Get actual maintenance curriculum, procedure outlines, manuals, service video, CAD/model availability, and approval constraints.
Identify which procedure is the best MVP: simple enough to build, valuable enough to sell, and visual enough to demo.
Decide fidelity level for crane systems: visual-only, interactive components, diagnostics, scoring, or full guided workflow.
Define success criteria for guided vs. unguided modes.

Visual/prototype direction

Use realistic technician training scenes, not arcade-style operation visuals.
Show headset/head/hand movement synchronized with the simulator view when creating video or motion concepts.
If a screen is visible behind the trainee, it should match first-person XR perspective and hand/controller state.
Tadano branding should use the correct dark navy/black look, not red.
Avoid overpromising perfect cause-and-effect sync from single-pass AI video; compositing may be more reliable.

Known decisions and constraints

Scope

Maintenance and servicing training is the center of gravity. Operator training language should be removed or heavily subordinated.

MVP

Proposal language supports a 3-6 lesson proof of concept with a modular roadmap.

Modes

Keep training modes simple: guided training and unguided assessment are the clearest baseline.

Data dependency

Technical planning depends on Tadano supplying procedure references, maintenance curriculum, photos, video, or model data.

Suggested next technical workstream

Pick one canonical MVP lesson

Choose the maintenance procedure that will anchor the prototype and proposal math. Ideal candidate: visible, bounded, common, safe to simplify, and easy for Tadano stakeholders to understand.

Write the interaction model

Define technician actions, virtual tools, system states, feedback, hints, error states, and assessment scoring for that single lesson.

Block a throwaway prototype

Create a simple web or Unity-style flow that proves the lesson sequence, not visual polish. Use boxes, labels, and step transitions first.

Map the expansion model

Show how the same lesson architecture supports additional systems, procedures, languages, assessments, analytics, and future device targets.

Open loops from sales channel

Confirm whether the July review/discussion with Andrew Broussard was scheduled.
Confirm whether the Salesforce transcript date field was filled.
Confirm final SharePoint location for the edited creative brief and PDF.
Gather Tadano-approved reference material for the technical team.

Recommended non-sales channel prompt

Use this when starting the technical thread:

We need to scope a technical MVP for Tadano XR service and maintenance training for crawler cranes. Start with one maintenance lesson, likely a simple service procedure, and define the interaction model, asset needs, fidelity assumptions, and prototype path. Do not frame this as operator training.

Source pointers

Local channel context: channels/tadano_proposals/
Most useful context files: MEMORY.md, STATE.md, THREADS.md, DECISIONS.md
Relevant channel source: #tadano_proposals