GEARS:
The Machine Awakens
A story-driven, cinematic onboarding experience that turns the GEARS (SEA) ZEN workflow into a mission — guided by ATLAS, the facility's holographic master engineer.
00 Program Overview
The premise, the goals, and how a dry click-through becomes a piece of cinema your operators actually want to finish.
The Premise
The learner is a newly-assigned Operator arriving at the GEARS facility — a vast, humming machine that converts experiment requests into real silicon on the shopfloor. The machine has been running on "the old ways" and is sputtering. ATLAS, the facility AI, needs a new operator to bring each subsystem back online. Every session powers up one more part of the great machine; by the finale, GEARS roars back to life — and so does the learner's competence.
Learning philosophy
Narrative ↔ Practice
Every concept beat is immediately followed by a hands-on beat. Story earns attention; practice earns competence.
Progressive load
Simple, low-stakes wins early (login) build toward multi-step judgment calls (request + approval + run).
Cinematic momentum
Motion-graphic interstitials reset attention and reward progress, so no session feels like "more forms."
Program at a glance
| # | Segment | Mode | Runtime | Outcome |
|---|---|---|---|---|
| S0 | Opening Sequence | Cinematic + flythrough | 4–5 min | Motivation + mental map of the whole journey |
| I-A | Interstitial: "Power to the Gate" | Motion graphic | 20 s | Bridge into Login |
| S1 | User Login | Guided do-while-I-explain | 8–10 min | Operator can log in (Email / OneUID) |
| I-B | Interstitial: "Who Goes There?" | Motion graphic | 20 s | Bridge into Access |
| S2 | User Access Management | Concept + storytelling | 8–10 min | Understands roles & requests access |
| I-C | Interstitial: "The Blueprint" | Motion graphic | 25 s | Bridge into Create Request |
| S3 | Create Request | Hands-on practical | 12–14 min | Builds a complete ZEN request |
| I-D | Interstitial: "The Council" | Motion graphic | 20 s | Bridge into Approval |
| S4 | Review & Approval | Concept + light practice | 6–8 min | Understands review gates |
| I-E | Interstitial: "Ignition" | Motion graphic | 25 s | Bridge into Run |
| S5 | Process Request (Run) | Hands-on practical | 8–10 min | Drives experiment to Close |
| ★ | Finale & Graduation | Cinematic payoff | 2–3 min | Mastery confirmation + live-site handoff |
Audience & outcomes
- ✓ Primary: New GEARS (SEA) users in Singapore & Malaysia who need both the "why" and the "how."
- ✓ Terminal objective: Independently complete the GEARS journey — login → access → request → approval → run — on the live system.
- ✓ Confidence objective: Reduce first-request errors (invalid shipping address, wrong priority, missing special instructions) to near zero.
◆ World & Character Bible
A consistent universe is what makes five sessions feel like one film. Here's the canon every asset must honor.
Meet ATLAS — your guide
Role: Holographic master engineer & facility AI. Voice: Authoritative, calm, dry wit — think a veteran flight director crossed with a wise mentor. Commands respect without shouting. Visual: A luminous figure of brushed-steel and cyan light, occasionally rendered as a constellation of rotating gears. Materializes from the machinery itself.
Tone rules
- ✓Confident, never condescending. ATLAS respects the operator.
- ✓One light joke per session max — always at the old process' expense, never the learner's.
- ✓Urgency with safety: "The machine waits for no one — but it also never punishes a careful operator."
The machine metaphor
- ⚙Login = the Gate powering on.
- ⚙Access = your clearance keys glowing to life.
- ⚙Create Request = forging a work-order crystal.
- ⚙Approval = the Council of Gears voting.
- ⚙Run = ignition on the shopfloor.
Visual & color language (sci-fi)
| Token | Use | Feeling |
|---|---|---|
| Cyan #33D6FF | ATLAS, active systems, "go," interactive holograms | Intelligence, life, online |
| Amber #FFB13D | Warnings, "watch-outs," mandatory fields | Caution, importance |
| Green #39E6A4 | Success, approvals, completion | Achievement |
| Violet #9A7BFF | Narrative/interstitial space, "between" moments | Story, transition |
| Void #0A0E17 | Backdrop, deep-facility darkness | Cinematic depth |
Typography: Display = a wide techno sans (e.g., Eurostile / Orbitron feel) for titles; Body = Inter for legibility; Data/UI = monospace. Texture: volumetric light shafts, fine grid floors, particle dust, subtle lens bloom. Avoid clutter — negative space is part of the awe.
◆ Interactive Journey Flowchart
The complete journey from Customer Request to Closed experiment. In the 3D build, each node is a floating gear-station the operator can gaze/click to enter. Click a node below to jump to its session.
Legend: cyan = active path · amber = run states · green = completion. The "Rework" loop returns a task to the operator — reality, not failure.
S0 Opening Sequence — "The Machine Awakens"
Format: Cinematic cold-open + interactive flythrough of the journey flowchart. Runtime 4–5 min.
Learning objectives
- ✓Care about GEARS: see why the workflow matters and what it replaces.
- ✓Hold a mental map of the full journey (the five stations) before any detail.
- ✓Recognize ATLAS as the trusted guide for the rest of the program.
Motion-graphic storyboard
Narration script (excerpt)
- Style: volumetric sci-fi; cyan key light, violet rim; particulate dust; lens bloom on ignitions.
- Camera: slow dolly-in (Shots 1–3), sweeping fly-through (Shot 5), settle to UI (Shot 6).
- Duration: 4:30 total; cut on SFX beats.
- Score: sub-bass drone → rising synth arpeggio as gears chain.
- SFX: metallic engage, electrical hum, comedic printer jam (Shot 4).
- VO: ATLAS — warm, resonant, unhurried; light reverb (large space).
- Captions: burned-in + toggle track for all VO.
- Audio description: alt track narrating visual-only beats (gear chains, ATLAS materializing).
- Comfort: reduced-motion variant with slower dolly + no bloom flashes for VR comfort.
Drag-to-rotate the 3D flowchart and tap each of the five stations to hear its one-line purpose. Gate unlocks Session 1.
From overview → Login
Camera rushes down a light-conduit toward a sealed blast door labeled THE GATE. ATLAS: "First, prove you belong here. Every operator passes through the Gate." SFX: charging hum → heavy lock disengage. Violet narrative space dissolves into the live login UI.
S1 User Login — "The Gate"
Format: Guided "do-while-I-explain." ATLAS narrates as the operator performs each action live. Runtime 8–10 min.
Learning objectives
- ✓Identify the four login options and choose the correct one (Email or OneUID for HP users).
- ✓Complete an Email login with HP credentials.
- ✓Understand that first-time users get an account created automatically.
Narrative bridge & teaching script
Step-by-step walkthrough (with checkpoints)
| Step | Operator action | ATLAS coaching | Checkpoint |
|---|---|---|---|
| 1 | Observe the 4 tabs | "Email & OneUID are yours." | Tap the two valid tabs to highlight |
| 2 | Select Email tab | "This door, today." | Tab glows cyan ✓ |
| 3 | Enter HP email | "Identity first." | Field validates format |
| 4 | Enter NT password | "Then your key." | Masked entry accepted |
| 5 | Click Log in | "Push through." | Transition to register/landing |
| 6 | New user: click Submit | "It builds your record." | Account-created confirmation |
| 7 | Arrive at Landing | "You're inside." | Email visible top-right ✓ |
- Use: brief (3–4s) "energy weld" animation when each field is completed correctly.
- Gate door: opens a crack on successful login; full open on landing.
- Per field: soft confirming "tick."
- Login success: mechanical lock + warm chord.
- Error: low double-buzz, non-punishing.
- All coaching VO captioned; field labels readable by screen reader.
- Color-independent success cues (icon + sound, not color alone).
- Keyboard / controller path mirrors gaze interaction.
Learner completes a full Email login unaided on a second pass. Optional branch: try the OneUID door and explain when you'd use SSO.
Video demonstration
15-second screen-capture loop of a clean Email login, picture-in-picture with ATLAS, available as "Show me again."
From Login → Access
Past the Gate, a corridor of dormant keyholes lights as the operator passes. One key — labeled CUSTOMER — glows; others stay dark. ATLAS: "Inside, not all doors open to all hands. Let's see which keys are yours." SFX: tumblers turning.
S2 User Access Management — "The Keys"
Format: Conceptual explanation woven into story. The operator learns the role system, then requests a key. Runtime 8–10 min.
Learning objectives
- ✓Explain the three roles — Customer, Manager, Task Owner — and what each can do.
- ✓Locate your own roles via the user menu → View User.
- ✓Submit a role-change request and set the expectation that admin approval is required.
Story-led explanation
Concept panel — roles & rights
| Role | Can do | Story name |
|---|---|---|
| Customer | Create requests, add details, send for review | The Forge-hand (default key) |
| Manager | Review & approve/reject requests | The Council voice |
| Task Owner | Accept tasks, run experiments, update status | The Fire-bringer |
Guided micro-practice
- 1Open the account menu (arrow by your email) → View User.
- 2Read your Roles row aloud with ATLAS (it's Customer).
- 3Click ChangeRole, tick Manager or TaskOwner-RequestSEA, then Save.
- Roles visualized as glowing keys; selected key floats & rotates.
- On Save: key flies down a conduit toward a distant "Admin" vault, then a "pending" pulse returns.
- Key select: crystalline chime.
- Request sent: whoosh + soft "pending" heartbeat to convey waiting.
- Role meanings given in text + VO, not only via the key visual.
- "Pending approval" state announced to screen readers.
Drag each task ("approve a request," "run the experiment," "create a request") onto the correct role. Reinforces who-does-what before the heavy practical.
From Access → Create Request
The operator steps onto a luminous forge platform; a holographic blueprint of a work-order "crystal" rotates above an anvil of light. ATLAS: "Now the real craft. We forge a request — and a careless forge ruins good silicon." SFX: forge hum, blueprint draw-on.
S3 Create Request — "The Forge"
Format: Hands-on practical, the program's centerpiece. The operator forges a complete ZEN request with ATLAS guarding the watch-outs. Runtime 12–14 min.
Learning objectives
- ✓Create a request under RequestSEA with correct Build Site, Work Area and Standard Priority.
- ✓Add SKU details (Product Family, Quantity, Special Instruction) — Template not required for ZEN.
- ✓Avoid the three classic errors: invalid shipping address, wrong priority, missing special instructions.
Motion-graphic storyboard (forge sequence)
Hands-on walkthrough
| Step | Action | ATLAS watch-out |
|---|---|---|
| 1 | Top menu → Request | — |
| 2 | Confirm site = RequestSEA → Create Request | "SEA = Singapore & Malaysia." |
| 3 | Build Site = Singapore; Work Area = matching container | "Match container to product line." |
| 4 | Priority = Standard Priority | "Only Standard for ZEN." |
| 5 | Desired Completion Date | "Standard lead time — shorter may be rejected." |
| 6 | Save → Summary; review 4 sections | "Request · Details · Templates · Attachments." |
| 7 | Add Details: Product Family, Quantity, Special Instruction | "Special Instruction is mandatory for non-standard — once, applies to all SKUs." |
| 8 | Save detail (Template not required) | "No template for ZEN." |
| 9 | Verify ship/deliver address | "Valid address only — or pens are disposed." |
- Each completed field = a "rivet" weld; crystal grows more solid as the form fills.
- Error states crack the crystal briefly, then heal on correction (forgiving).
- Rivet weld per field; forge "temper" sound on Save.
- Address alarm: distinct red klaxon (used only here for weight).
- Mandatory fields flagged by icon + label text, not color alone.
- The address warning is also delivered as text + VO + haptic (controller rumble) for emphasis.
Build a complete request unaided. Auto-graded checks: RequestSEA ✓, Standard Priority ✓, valid address ✓, Special Instruction present for non-standard ✓. Three-error guardrail must be clear to pass.
From Create → Approval
The finished crystal floats up a shaft into a ring of glowing gear-elders — the Council. ATLAS: "Your work now faces the Council. They weigh it. All must agree before fire is granted." SFX: low chamber tone, deliberation hum.
S4 Review & Approval — "The Council"
Format: Concept + light practice. Mostly the Customer's send-for-review action and understanding the gate. Runtime 6–8 min.
Learning objectives
- ✓Send a completed request for review and recognize default vs additional reviewers.
- ✓Explain the approval gate: every reviewer must approve; on approval the Task Owner is notified.
- ✓Understand reject/rework as normal, not failure.
Narrative + walkthrough
- 1From the summary, click Send Review to Managers.
- 2Confirm the Default Reviewer; add additional reviewers if needed; Save (email sent).
- 3Concept: reviewer Approves / Rejects / Comments; all must approve to proceed.
- Council gears each light green as approvals land; a single dim gear = pending.
- Unanimous = the ring spins up and opens a path downward to Ignition.
- Each approval: ascending chime; unanimous: resolving chord + gate-open.
- Approval tally (e.g., "2 of 3 approved") spoken + shown as text.
Given a scenario with 3 reviewers and 2 approvals, answer: can it proceed? (No.) Reinforces the unanimity rule.
From Approval → Run
The approved order drops to the shopfloor; turbines spin, the floor floods with amber working-light. ATLAS: "Approved. Now we make it real. To the floor, Operator — this is where ideas burn into being." SFX: turbine spin-up, heat shimmer.
S5 Process Request (Run) — "The Ignition"
Format: Hands-on practical. The Task Owner drives the experiment Queue → Active → Close. Runtime 8–10 min.
Learning objectives
- ✓Accept a task with an estimated completion date (→ Queue).
- ✓Drive status: Start Traveler → Active → Close; use Hold/Rework when needed.
- ✓Know that Phase 1 status updates are manual (Phase 2 will automate via shopfloor).
Hands-on walkthrough
| Step | Action | State |
|---|---|---|
| 1 | Task tab → review task → Accept (set est. completion date) | Pending → Queue |
| 2 | When ready on shopfloor → Start Traveler | Queue → Traveler Started |
| 3 | Update to Active while running | Active (Hold available) |
| 4 | On completion → Close | Closed ★ |
- Floor turbines accelerate with each state; "Active" = full amber glow + sparks.
- "Close" = triumphant cool-down to green, machine settles into a steady idle.
- Spin-up on Start Traveler; steady industrial hum on Active; satisfying power-down + success sting on Close.
- Phase-1 "manual update" caveat shown as a persistent text note + VO.
- Each state change announced for screen readers.
Take a task from Accept to Close unaided. Branch challenge: trigger a Hold then resume, and explain when Rework is the right call.
★ Finale & Graduation — "The Machine Lives"
Cinematic payoff + handoff to the real system. Runtime 2–3 min.
Graduation deliverables
- ★Completion badge: "GEARS Operator — ZEN Certified," with the five stations lit.
- ★One-page quick-reference card (PDF) of the watch-outs (priority, address, special instructions, manual status).
- →Live handoff button: launches the real GEARS site so the operator's first real request happens while the story is fresh.
- Grand reveal fly-out; reduced-motion alt = gentle cross-fade to badge screen.
◆ Motion & Visual Style Bible
| Element | Spec |
|---|---|
| Aesthetic | Cinematic sci-fi: deep void backdrops, volumetric cyan/violet light, fine grid floors, particulate dust, restrained lens bloom. |
| Gears as language | Gears are the recurring motif — meshing = systems connecting; a lone spinning gear = "thinking/pending"; a chain igniting = progress. |
| Transitions | Narrative space = violet; live UI = cyan. Always travel through a light-conduit between them so context never jump-cuts. |
| Duration discipline | Interstitials 20–25s; cold open ≤4:30; no idle shot >6s without motion or VO. |
| Restraint | Red klaxon reserved for the shipping-address alarm only — scarcity = impact. |
◆ Sound Design Bible
| Layer | Spec |
|---|---|
| ATLAS VO | Warm, resonant, unhurried; subtle large-space reverb; consistent take/level across all sessions. |
| Score | Sub-bass drone foundation; rising synth arpeggios for progress; resolving chords for success. Per-session leitmotif variation. |
| UI SFX | Field tick (confirm), weld (commit), chime (select), whoosh (send), klaxon (address error only), power-down sting (Close). |
| Spatial (3D) | Diegetic audio anchored to stations; ATLAS voice slightly head-locked for intimacy; turbines positional on the shopfloor. |
| Mix | VO always +6 dB over score; duck music under coaching; loudness normalized for headset comfort. |
◆ Accessibility Specification
- ✓Captions: all VO and dialogue; toggleable + high-contrast option; positioned for HMD readability.
- ✓Audio descriptions: alternate track narrating visual-only beats (gear chains, ATLAS materializing, forge welds).
- ✓Color independence: every status conveyed by icon + text + sound, never color alone.
- ✓Reduced motion / comfort: slower cameras, no bloom flashes, optional teleport vs smooth locomotion; vignette on movement.
- ✓Input parity: gaze, controller, voice, and keyboard all complete every task; generous dwell times.
- ✓Pacing control: pause, replay ("Show me again"), and self-paced checkpoints throughout.
- ✓Language: plain-English VO; on-screen glossary for GEARS terms (RequestSEA, Traveler, SKU).
◆ 3D / HoloLens Implementation Notes
| Topic | Guidance |
|---|---|
| Engine | Unity + MRTK3 (or equivalent) for HoloLens 2; design for mixed-reality (world-anchored stations) with a 2D fallback for desktop/web. |
| Layout | Five stations placed around the room as world-locked holograms; the journey flowchart is a tabletop hologram in the hub. |
| Live UI in MR | The GEARS look-alike panels float as interactive slates; gaze+pinch to act. Keep text ≥ comfortable angular size. |
| Performance | Budget for 60fps on-device: instanced gears, baked light where possible, particle caps; LOD the facility backdrop. |
| Comfort & safety | No forced fast camera moves on-headset (those are for the 2D cinematic); seated & standing modes; clear exit/pause gesture. |
| Authoring once | Keep content data-driven (the session/step JSON) so the same script powers MR, desktop, and web builds. |
◆ Production Asset Checklist
Motion / video
- ▢Cold open (4:30) + 5 interstitials (20–25s)
- ▢Forge sequence (S3) + Ignition sequence (S5)
- ▢"Show me again" demo loops ×5
- ▢Finale reveal + badge animation
Audio
- ▢ATLAS VO script record (all sessions, one talent)
- ▢Score stems + per-session leitmotifs
- ▢SFX library (welds, chimes, klaxon, turbines)
- ▢Audio-description alt track
Interactive
- ▢GEARS look-alike UI slates (login → run)
- ▢Interactive journey flowchart (3D + 2D)
- ▢6 checkpoints incl. auto-graded S3 forge
- ▢Session/step content JSON (single source)
Support docs
- ▢Captions + transcripts (all locales)
- ▢Quick-reference watch-outs card (PDF)
- ▢Facilitator / admin guide
- ▢Glossary of GEARS terms
Tip: the interactive GEARS look-alike simulator already built (GEARS-ZEN-Interactive-Walkthrough.html) can serve as the S1–S5 "live UI slate" inside this program.