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.
Overview
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.
Foundational Factory Layout
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.
- Converted incomplete legacy information and field observations into a layout system that could support planning, equipment tracking, demo guides, and future installation references.
- Used the layout as the base artifact for downstream project documents so updates could stay connected to one spatial source of truth.
- Iterated the layout through multiple review cycles while preserving the project logic: station identity, equipment ownership, flow, and install-readiness.
Equipment Tagging & Recovery System
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.
- Designed a station-based identification convention that could scale across many pieces of equipment without depending on memory or tribal knowledge.
- Built supporting tracker logic and a written guide so the system could be adopted by others without me interpreting it in person.
- Validated the system during field demo activity when crews were able to locate equipment using the guide package and labels.
- Identified and escalated missing critical controls hardware during a line walk before it could be lost during removal activity.
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.
Contractor-Ready Demo Guide Package
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.
- Built field-reference layouts that showed what equipment belonged to the future training facility and how it should be identified.
- Designed the pages as standalone artifacts with enough context for field use rather than internal-only documentation.
- The guide package was adopted by the demo team and used by contractor crews as a reference during selective demo work.
Controls Integration Support
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.
- Documented mechanical/layout portions of the integration package and helped organize information for install-team use.
- Worked through electrical/control sections with senior-engineer guidance, learning how controls hardware, operator interfaces, safety I/O, PLC cabinets, and power-distribution components fit into the overall equipment package.
- Built confidence contributing to a formal controls-adjacent deliverable without pretending to be the controls owner.
Handoff Package Standard
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.
System Architecture
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.
What This Demonstrates
- Systems thinking: a naming convention can be an engineering control when multiple teams share physical assets.
- Field validation: the guide package worked under real demo conditions, not just in a planning meeting.
- Cross-functional execution: deliverables had to serve managers, demo crews, contractors, manufacturing engineers, and controls stakeholders.
- Ownership under ambiguity: I built the structure first, then used feedback and field results to improve it.
Lessons Learned
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.