Optimus Academy — Humanoid Robotics Training Facility
02 · Tesla Fremont · Optimus Program · Jan – Aug 2026

Optimus Academy Factory Layout

Layout
foundational AutoCAD system
Field
validated tagging convention
Demo
contractor-ready guide package
Controls
integration documentation support
AutoCADFactory LayoutEquipment Tracking Demo PlanningControls SupportHandoff Systems

NDA-safe summary: This case study removes internal names, station identifiers, direct quotes, exact layout images, and proprietary installation details. It focuses on the engineering system I built: layout, identification, tracking, field adoption, and handoff.

In parallel with Model 3 BIW work, I supported an internal Optimus training-facility project by building the layout and equipment-control system needed to move from a legacy manufacturing area toward a reusable robotics training environment.

The main challenge was not just drawing a floor plan. The project needed a common language across CAD layouts, equipment trackers, field labels, contractor demo guides, and future install documentation so teams could find the right assets under time pressure.

I built the first usable AutoCAD layout foundation on a compressed schedule, learning the required workflows as I went and then revising the layout through stakeholder feedback.

I proposed and implemented a unified tagging convention for Optimus-bound equipment so demo crews, engineers, and trackers all referred to the same assets in the same way. The system linked physical labels to CAD layouts and spreadsheet trackers.

Engineering problem
Two overlapping field activities created a race condition: equipment needed for the future facility had to be separated from assets scheduled for removal.
My solution
A common ID system tying together layouts, trackers, labels, field guides, and future install documentation.

I created station-level guide layouts intended to be used directly by demo teams and contractors. The standard was not whether the drawings looked polished; it was whether someone could find equipment in the field without me there.

I supported a senior controls engineer on integration documentation for repurposed conveyor and controls assets. My role was to own the structural sections I could complete independently and learn the electrical/control logic well enough to support the formal deliverable.

This project changed how I think about documentation. A planning artifact is only useful if another team can use it under field conditions without the author standing next to them. I structured the Optimus work so each artifact pointed to the next one: layout, ID system, tracker, field guide, install handoff.

What made it usable
Consistent asset IDs, public-to-the-team definitions, field-ready layouts, and a written guide explaining the convention before confusion could happen.
What made it durable
The system did not depend on memory. It connected the physical label, CAD reference, spreadsheet tracker, and future install documentation.
01
Layout
AutoCAD plan becomes the spatial source of truth.
02
Identification
Station-based IDs give every future-use asset a common name.
03
Field Guides
Contractor-ready pages translate the plan into demo execution.
04
Install Handoff
Trackers and documentation preserve decisions for the next phase.
A good naming system prevents physical mistakes
When assets are being moved, removed, or saved, ambiguity becomes expensive. The ID convention worked because it connected the digital plan to the physical floor.
Handoff quality is measured when you are not there
The demo guides were successful because teams could use them directly. That became my standard for future handoff packages: understandable without the author standing next to the user.
Field walks catch what trackers miss
The tracker creates intent, but the floor confirms reality. Walking the area during demo made it possible to catch missing critical hardware while it could still be recovered.
Modular Camera System All projects EOAT Automation Cell