Membrane switch stack
Overlay, spacer, circuit and adhesive supplied as one tested interface.
One reviewed front-panel interface
An integrated HMI assembly brings the visible overlay, switching circuit, lighting, connector and selected mechanical layers into one defined supply item. The objective is to reduce interface risk between separate parts, not to make unverified claims about the complete customer's equipment.
Engineering variables
Overlay, spacer, circuit and adhesive supplied as one tested interface.
Window printing, optical gaps and display relationship are reviewed in the assembly.
A rigid panel, PCB or other support may be included where drawings and responsibilities are clear.
Tail, connector, pinout and functional test define the connection to the customer's electronics.
Decision matrix
An integrated HMI assembly reduces supplier handoffs only when the delivered configuration and every mechanical, optical, electrical and user-facing interface are defined. A useful RFQ separates HYR assembly verification from the OEM's software, enclosure and complete-equipment validation responsibilities.
| Decision factor | OEM input | Engineering review output |
|---|---|---|
| User task and operating context | Describe the intended users, operating task, sequence, viewing and reach conditions, gloves or tools, expected feedback, foreseeable misuse and the environment in which the complete equipment will be used. | Return the component-level questions affecting key layout, legends, feedback, lighting and service access. HYR input does not replace the OEM's human-factors, safety or complete-system validation. |
| Assembly configuration and ownership | Identify every included and excluded item, controlled drawing and BOM revision, customer-furnished part, approved source, design owner, procurement owner and party responsible for each interface decision. | Return one proposed supply boundary and configuration identity, including assumptions, customer-furnished material controls and open responsibilities. Fewer suppliers do not remove interface ownership. |
| Mechanical stack and mounting | Provide the enclosure and carrier geometry, datum scheme, stack envelope, support and fasteners, adhesive surfaces, display location, tolerances, assembly sequence, service model and exposure conditions. | Return a controlled stack and mounting interface with tolerance, support, sealing and assembly questions tied to the actual enclosure. The HMI drawing does not approve an unknown mating structure. |
| Graphics, window and lighting | Provide controlled artwork, colour and finish references, display active area, window intent, optical gap, indicator map, lighting states, ambient viewing conditions and powered visual acceptance needs. | Return a coordinated overlay, window and lighting definition plus the representative powered sample needed for approval. Separate unpowered parts cannot validate the final visual state. |
| Electrical and system handoff | Define the schematic or interface definition, pinout, connector and mating part, signal and load conditions, grounding or shielding, component ownership, controller or software assumptions and the functional test available at the assembly boundary. | Return the proposed electrical handoff, test access and excluded system behaviours. Passing an assembly continuity or functional check does not validate customer firmware, control logic or complete-equipment performance. |
| Integration, release and change control | Define representative specimens, assembly-level verification, equipment-level validation, acceptance criteria, approval owners, retained baseline, packaging and the notification and requalification rules for later material, source, drawing or process changes. | Return an integration and release plan linking interface documents, samples, results and revisions. Approval applies to the identified configuration; a change is assessed at every affected interface before repeat production. |
NASA interface-management guidance, ISO 9241-210 and ISO 10007 address interface control, human-centred design activities and configuration management at different levels. They do not transfer complete-equipment design, usability, safety, regulatory or validation responsibility to an HYR component supplier, and they do not certify a proposed HMI assembly.
Before the RFQ
Start with the evidence you have now. Open items stay visible for engineering follow-up instead of becoming silent quotation assumptions.
Those files can start the review, but a comparable quotation needs one controlled assembly drawing and BOM, the included and excluded items, design and supply owners, customer-furnished parts, interface data and the acceptance checks for the delivered configuration. Missing decisions remain visible assumptions instead of becoming an implied integration scope.
No. An integrated supply item can reduce handoffs, but it does not transfer the OEM's responsibility for user tasks and human factors, safety, enclosure performance, software or control logic, EMC, regulatory work or complete-system validation. HYR responsibility stays tied to the identified assembly configuration and the tests explicitly included in the reviewed scope.
Evaluate it with the representative enclosure and electronics. Confirm mechanical fit and stack, overlay and key alignment, display windows and powered lighting states, key response, connector and pinout, assembly-level functional checks, plus sealing or service access where included. Record the drawing, BOM, software context, test conditions and approval decision used for that sample.
A useful fit when
Limits to resolve
Prepare the RFQ
You can submit what is available now. Unknown items remain visible for human follow-up rather than being guessed.
Complete front-panel assembly drawing
BOM and ownership of supplied parts
Electrical interface and functional test
Packaging and traceability requirements
Evidence boundary
Assembly claims are limited to the accepted drawing, BOM and inspection plan; parent-company resources are attributed to their actual operating entity.
Technical reference basis
These publisher resources support the decision framework. They do not prove that HYR uses a named grade, holds a listed certification or has approved a project construction.
Primary government guidance on interface management, product integration, verification and validation; it is not an HMI product standard or evidence that HYR performs NASA system-engineering approval.
Primary standards-body scope for human-centred design activities across interactive-system life cycles; it does not establish the usability, safety or regulatory compliance of an HYR component or finished customer equipment.
Primary standards-body guidance for configuration management from concept through disposal; it does not certify HYR, a configuration-management system or a proposed HMI assembly.