Motorsport Cockpit HMI RFQ: Separate Overlay, Driver Controls and Safety Hardware

A motorsport cockpit HMI should not be quoted from one dashboard photograph. Before asking for price, separate the printed display overlay, the driver-operated input panel and the vehicle-level safety hardware into controlled packages. For the overlay or membrane interface, freeze the visible windows, legends, mounting datums, key zones, backlight states, circuit tail and connector. Keep steering, fire suppression, restraint, emergency isolation, controller logic and safety validation under the vehicle integrator. This boundary lets a component supplier quote the right article, gives the buyer a useful first-sample plan, and prevents a low-volume spare from changing a function that the vehicle program has already validated.

A current customer-racing launch makes the sourcing boundary visible

Porsche Motorsport North America announced the 911 Challenge on August 26, 2026. The company describes in-cabin controls based on road-car design, a focus on ease of operation, and a mix of production technology with motorsport safety equipment. It also positions lower running and spare-parts costs as part of the program.

That launch is useful procurement context, not a design specification for another vehicle. It shows why a cockpit bill of materials needs clear boundaries when familiar driver controls, competition hardware, service spares and low-volume production meet. It does not show that a printed overlay or membrane switch controls safety functions, and it is not evidence of any Baoshengda involvement.

For a buyer sourcing a custom front interface, the practical question is narrower: what can be reproduced as a controlled HMI component, what must remain a separately sourced switch or controller, and what evidence will prove that a replacement part matches the approved cockpit?

Split the RFQ into three packages before discussing price

A single photo may show one cockpit, but it usually hides several supply scopes. Start the RFQ with three packages and assign an owner to each one.

Do not ask the front-panel supplier to infer these layers from color, symbol shape or location. A red legend does not prove a safety function. A large key does not prove an emergency circuit. A display window does not define the active display area or its optical acceptance criteria.

Build a function-boundary ledger from the driver task

A useful ledger starts with the driver or service task, not with the artwork file. For every visible item, record the intended user, operating state, input type, feedback and system owner.

For example, a pit-service page key might be a momentary membrane input that is enabled only when the vehicle is stationary. A warning telltale might be printed as a dead-front icon but illuminated by electronics behind the overlay. A physical rotary selector might pass through a cutout and mount to a rigid structure behind the panel. These three features can appear side by side while belonging to different suppliers and different validation plans.

The ledger should answer:

• Who can operate the function: driver, technician or both?
• In which states is the function enabled, ignored or locked out?
• Is the visible item a printed legend, a momentary key, a cutout for separate hardware or a status window?
• What feedback confirms the action: tactile snap, indicator light, display change or controller response?
• Which organization owns the logic and the safety case?
• Does the spare part replace only the front component, or does it change a validated assembly?

This is also the point to remove functions that have not been released. Quoting an unfinished key map may produce a sample quickly, but every late function change can alter artwork, circuit routing, pin count, connector choice and test coverage.

Freeze the overlay drawing as an interface, not as decoration

The printed overlay is not just a graphic skin. On an instrument or control panel, it locates display windows, telltales, apertures, fasteners and tactile zones relative to the housing. A quote-ready drawing should therefore identify more than colors and a perimeter.

Specify the primary mounting datum and the secondary datum that prevents rotation. Dimension window edges and active display clearance from those datums, not from a screenshot. Mark through-holes, shaft openings and bezel keep-outs. Define which printed areas must be opaque, translucent or dead-front. State whether legends are judged unlit, lit or in both conditions. If the part uses adhesive, show the adhesive-free zones around windows, apertures and any area that must move.

For low-volume motorsport spares, revision control matters as much as first manufacture. Put the artwork revision, mechanical revision and electrical revision in separate fields. A visual legend change should not silently authorize a connector or circuit change. A later display module should not inherit an old window location because the file name looked familiar.

The complete automotive overlay samples in the cover image illustrate this component boundary. They show full perimeters, central display windows, gauge artwork and mounting apertures. They do not show a race-car installation, switch circuit, tail, connector, control unit or verified safety function.

Define the input panel only after the fixed hardware is known

If the cockpit also needs a membrane input panel, place it around the hardware that cannot move. Steering-column clearance, rotary-switch bodies, display bezel, harness route, fasteners and structural support should be fixed before key shapes are finalized.

Then define each physical key with a function ID rather than relying on its printed label. The function ID should connect the artwork, circuit net, connector pin and controller state matrix. Record whether the key is momentary, whether simultaneous presses are permitted, what feedback is required and what happens when the signal is open, shorted or held.

The mounted stack also affects feel. A loose sample can pass electrical continuity while failing after installation because the housing flexes, the adhesive bridges a recess, a fastener distorts the panel or the tail is forced into a tight exit. Include the housing support surface, gasket or adhesive thickness, tail exit angle, minimum bend area and connector retention in the sample package.

For backlit controls, approve at least two states. An unlit review checks print density, symbol readability and surface appearance. A lit review checks leakage between legends, bright spots, dim zones and whether the intended telltale remains distinct from nearby graphics. The vehicle team still owns when an indicator turns on and what that state means.

Plan the spare before approving the first article

A low-volume part can remain in service longer than the file trail that created it. The RFQ should therefore define the spare strategy before the first sample is signed off.

Choose which items form the controlled master set: released artwork, dimensioned drawing, approved color reference, circuit netlist, tail and connector specification, mounted sample, inspection report and approved physical sample. Record substitutions that require written approval, including film, adhesive, dome, LED, connector and surface finish changes.

Also define interchangeability. A service spare should fit the same datums, clear the same bezel, connect to the same harness and produce the same released inputs. If a new revision intentionally breaks interchangeability, mark it as a new assembly rather than treating it as a cosmetic update. This protects purchasing teams from ordering a visually similar part that cannot replace the approved one.

A useful first-article report can show measured window location, mounting-hole position, perimeter, key-zone registration, tail position, connector orientation, circuit continuity and visible print defects. It should not claim vehicle-level compliance from component measurements.

Approve samples through four different gates

One final appearance check is too late to discover a boundary error. Use four gates with a clear stop decision after each one.

1. **Artwork and datum gate:** approve released legends, windows, apertures, mounting references and revision identifiers before tooling or print setup.

2. **Loose component gate:** inspect the full perimeter, print, windows, apertures, key feel, tail, connector and circuit continuity without the housing masking a defect.

3. **Mounted interface gate:** install the part in the representative bezel or housing and check window registration, surface support, edge lift, key force, tail strain, connector access and light leakage.

4. **Integrated system gate:** the vehicle integrator verifies controller response, enable states, diagnostics, failure behavior, driver reach, service procedure and all safety requirements.

A component supplier can support the evidence at the first three gates within the quoted scope. Passing them does not replace the fourth gate. The buyer should state who signs each gate and what happens to the part revision after a rejection.

Keep the supplier boundary explicit

A front-interface supplier can review and quote printed overlays, membrane-switch stacks, tactile zones, display windows, dead-front legends, light-blocking details, flexible circuits, tails, connectors, adhesive patterns and component inspection evidence when adequate inputs are supplied.

The component supplier does not select the vehicle's safety architecture, assign emergency functions, design the steering or fire system, write controller software, validate interlocks, perform the vehicle hazard analysis, certify a motorsport vehicle or approve compliance with sporting and road regulations. Those decisions remain with the vehicle integrator and its qualified engineering owners.

The current Porsche announcement likewise should not be used as proof that a specific overlay, keypad or supplier is suitable for another cockpit. It is a timely example of a customer-racing program combining familiar controls, competition hardware and spare-cost objectives. The RFQ still needs its own released function boundary and evidence.

Send a cockpit HMI RFQ that can be checked line by line

Before requesting quotation, send a controlled package rather than a photo-only inquiry:

• application description, driver and service user roles, and expected sample and annual quantities;
• interface boundary showing overlay, input panel, separate hardware, controller and safety owners;
• released artwork with colors, opaque, translucent and dead-front regions;
• mechanical drawing with primary and secondary datums, perimeter, windows, active areas, apertures, mounting holes and bezel section;
• key-function IDs, enabled-state matrix, tactile requirements and expected feedback;
• circuit or netlist, tail exit and keep-out zones, connector part, pin assignment and mating direction;
• backlight and telltale states, light-blocking expectations and unlit/lit review conditions;
• film, surface, adhesive, gasket and operating-environment requirements that are already known;
• first-article measurement plan, mounted sample fixture and integrated validation owner;
• spare-part master set, interchangeability rule, change-control process and target revision.

Use the automotive HMI component route to review relevant front-interface scope. If the package is ready, request a cockpit HMI quotation review with the drawing, function-boundary ledger and first-article evidence plan. The result should be a component quote with visible limits, not an implied vehicle-level safety approval.