Capabilities

CapabilitiesFE-CAP-001 · Rev. A

What we take responsibility for.

These are not services on a menu. They are the disciplines we practice, and each one is backed by documented work in the project index. When we take on a car, we take responsibility for how these systems behave together.

The difference

We build our own tools.

Most shops buy their capability off the shelf and are limited by what the shelf offers. We develop ours. When the tool we need does not exist, we write it. When a toolchain is stuck in one language, we port it. When a new technology like AI can sharpen the work, we put it on the pit wall before the rest of this industry has finished arguing about it.

That is not recklessness. It is discipline: everything we deploy is validated against physical measurement, labels its own uncertainty, and keeps a human crew in the loop. The result is a small company with capabilities that usually require a factory program.

In-house softwareDeveloped with AI-assisted engineering

SW-01Race strategy toolchainPython port of our MATLAB strategy suite plus a live race engine: telemetry ingest, fuel and stint modeling, pit-wall dashboards. FE-592 →Race proven

SW-02Harness design suitePlans a professional motorsport wiring harness from scratch and generates the schematics, with an LLM-connected device library for connector, pinout, and device data.Operational

SW-03Vehicle health analyzerWhole-session MoTeC analysis that returns a READY, CAUTION, or STOP verdict: oil-pressure margin against an RPM-based curve, thermal and voltage persistence checks, lambda versus aim under load, boost tracking, and per-cylinder knock margins, with shift and transient masking to suppress false alarms. Originally our MATLAB tool, now ported to Python.Race proven

Fig. 01#501 harness construction. Mil-Spec, concentrically twisted, in-house.

C-01

Electrical architecture

We design the electrical system as a system: power distribution strategy, CAN network design, sensor selection, and serviceability. Harnesses are built in-house to Mil-Spec or Club Spec standards depending on the program and budget.

Evidence: #501, complete architecture →

C-02

Engine management & calibration

Standalone ECU selection, installation, and calibration. We build air-mass and torque models, run steady-state dyno development, and refine drivability until the result meets an OEM standard, not just a peak number.

Evidence: S54 E30, 100+ hour calibration →

C-03

Mechanical design

CAD in SolidWorks, packaging studies, prototyping, and fabrication. When a component does not exist or does not fit, we engineer it for the vehicle rather than forcing an adaptation.

Evidence: S54 E30, pedal assembly redesign →

C-04

Vehicle integration

Complete-vehicle programs where electronics, powertrain, chassis, and driver interface are developed together. This is the discipline that separates a collection of parts from a finished car.

Evidence: S54 E30, complete vehicle →

C-05

Testing & data

Instrumented development at the track. Data acquisition, driver feedback, and measured change. We test one variable at a time and keep the results.

Evidence: #11, endurance development →

C-06

Race support

Race preparation and trackside engineering for endurance and sprint competition, from fuel systems to lighting to failure analysis between sessions.

Evidence: #11, NASA WERC program →

C-07

Strategy & simulation

We build our own software. Our endurance race strategy model began as in-house MATLAB code, was rebuilt in Python with AI-assisted development, and ran live during competition, computing fuel windows and stint strategy in real time. We put modern tools, including AI, to work anywhere they sharpen the engineering.

Evidence: FE-592, 6 Hours of Utah live deployment →

C-08

Model-based design & simulation

Simulink, Simscape, and Stateflow, applied with OEM methodology: MIL, SIL, PIL, HIL. Our DRS control strategy was designed as a five-state machine, simulated against the SolidWorks wing geometry in a multibody model with aero loads and a revolute joint for the DRS element, and validated with the driver in the loop. Simulation is complete, and the strategy is ready to deploy to MoTeC hardware through the MATLAB-enabled development license.

Evidence: Presented at UNLV · KTM GTX program

Top-level Simulink model of the DRS control strategy

Fig. C08-aDRS control strategy, top-level Simulink model.

Stateflow chart: Closed, Opening, Open, Closing, Fault

Simscape multibody model of the DRS wing

Fig. C08-b, cFive-state deployment logic in Stateflow. Simscape multibody wing: SolidWorks geometry, revolute DRS joint, aero loads.

Inside C-07As deployed at the 6 Hours of Utah

T-01Legacy toolchain migrationA six-file MATLAB strategy application ported to Python, logic preserved exactly and validated the same day.

T-02Telemetry pipelines250 MB MoTeC exports, 188 channels at 100 Hz, parsed in minutes and tolerant of corrupt data.

T-03Live data systemsCAN telemetry over WebSocket and live timing APIs, consumed through adaptive parsers that survive schema changes.

T-04Modeling & optimizationPer-driver pace and fuel models, stint optimization across pit loss and driver order, caution sensitivity quantified.

T-05Measurement validationA 21 percent fuel-scale error found and fixed by cross-checking the stream against the logger and physical fuel.

T-06Real-time interfacesPit-wall dashboards and a living strategy sheet, served on site, honest about live versus estimated data.

T-07AI-augmented operationsCloud engineering sessions on continuous watch cycles, corrections through a command channel, crew in the loop.

Driver development coaching and arrive-and-drive rental remain available alongside the engineering programs. Ask us.

Inquiries

Tell us what the car needs to do. We will tell you what it takes.

Document

Capabilities

Doc. no.

FE-CAP-001

Rev.

A

Issued

08.2026

Location

Las Vegas, NV