← Back to portfolioElectrical Engineering · Pilot Builds

Turning a Valid Wiring Design Into a Practical Solution

Improving routing and termination on Trident and SF6 pilot builds to make the physical implementation cleaner, more practical, and easier to service.

TridentSF6Electrical SchematicsWiringTroubleshootingFAT
SCHEMATIC → PHYSICAL BUILD
T1
T2
T3
T4
Alternative routing & termination
2product families: Trident & SF6
Acceptedby Design Engineering
FATrevised products passed validation
Ongoingregular NSR issue identification
01 · Challenge

Correct on paper can still be difficult in the real product.

During Trident and SF6 pilot builds, I identified wiring arrangements that were technically possible but created practical problems in the physical panel.

Poor routingWire paths were less direct than necessary.
Crossed componentsRouting across components increased physical complexity.
Field serviceabilityThe arrangement could make troubleshooting and repair harder.
ManufacturabilityThe pilot build exposed issues not obvious from the schematic alone.
02 · Engineering Analysis

Look beyond the schematic to the real product.

Reviewrequirements
→
Visualizephysical panel
→
Identifyrouting conflict
→
Proposealternative
→
ReviewDesign Engineering
→
Validatebuild & FAT

My contribution

I identified the routing and serviceability issue during pilot-build work, evaluated a more practical arrangement, and proposed different routing and termination. Design Engineering reviewed and accepted the proposal.

03 · Improvement

Different routing. Different termination. Simpler implementation.

The revised approach avoided unnecessary crossing of components and better considered assembly, troubleshooting, and future field service.

Before

Technically valid

Poor routing, crossed components, and more difficult field repair.

→
After

Practical & serviceable

Alternative routing and termination better aligned with the physical product.

FATfinal validation
→
Validation

Accepted, implemented, and tested

Design Engineering accepted the change. The revised products were subsequently built and passed Factory Acceptance Testing (FAT).

Cleaner routingImproved serviceabilityPractical terminationValidated build
04 · Continuous Improvement

Not a one-time observation

Finding design, documentation, and manufacturing issues is part of my regular work. Problems discovered during builds are documented through the NSR process on a daily or weekly basis as needed for review and resolution.

Scope note

This case study intentionally omits proprietary drawings, customer information, internal specifications, and confidential technical details.

Engineering Lesson

Correct on paper is not always optimal in practice.

Pilot builds reveal how a design interacts with physical space, manufacturing constraints, and service requirements.

My Approach

Think about the lifecycle.

I consider not only assembly, but whether the product will be understandable and practical to troubleshoot later.

Collaboration

Improvement requires engineering review.

The solution came from identifying the issue, developing an alternative, and working with Design Engineering to validate it.

Project Sequoia Principle

A good engineering solution should work beyond the drawing.

Manufacturability, troubleshooting, serviceability, and validation all matter. The goal is not simply to make the design work—it is to make the system practical.

Explore More Projects