AI-Assisted Machine HMI RFQ: Freeze Manual Control Boundaries Before Quotation

When AI enters machine control or engineering workflows, the physical HMI drawing must still identify which actions remain local, manual and immediately available. Before requesting a quote, freeze each physical key function, the state in which it is accepted, the indication that confirms the state, and the circuit, tail and connector path that delivers it to the controller. A custom industrial automation HMI supplier can build and test the physical interface, but the machine owner must define the automation boundary, permissions, interlocks and safety architecture. Quote the panel only after those ownership lines are visible in the drawing and sample plan.

Current AI activity makes a familiar HMI question more urgent

The International Society of Automation scheduled its September 3, 2026 discussion for automation professionals around AI tools for conventional instrumentation and control processes, neural-network-based control, current use cases and workforce skills. That is useful evidence of current industry attention, not a specification for any particular machine or operator panel.

The ISA page does not define a membrane switch, require a physical keypad or endorse Baoshengda. It also does not decide which action should be automated. The buyer value is in the question the discussion brings forward: when more decisions are assisted or automated, which controls must remain available at the machine, and what evidence allows purchasing to quote that physical interface without guessing about software?

A vague label such as manual, reset, resume or override is not enough. The same word can describe a simple controller input, a mode request, a permission-dependent command or a safety-related function. Those are different responsibilities. If they are not separated before quotation, a supplier may reproduce the visible artwork while the machine team assumes that the sample also proves state logic or safety behavior.

Freeze authority before choosing the key layout

Start with an action-and-owner list, not with colors or button shapes. For every proposed physical key, record the operator intent, the machine state in which the request is valid, the controller input assigned to it, the response owned by software and the person responsible for final validation.

A useful boundary distinguishes at least four conditions:

1. **Local physical input:** the contact closes, opens or changes resistance at the HMI circuit.

2. **Controller recognition:** the assigned input changes at the expected connector pin and controller channel.

3. **Command permission:** application logic accepts, delays or refuses the request in the current mode.

4. **Machine action:** motion, heat, pressure or another output occurs under the equipment owner's approved logic and safeguards.

The membrane-switch supplier can verify the first condition and, with an agreed fixture, help document the interconnect that supports the second. The controller integrator owns recognition and command behavior. The machine builder owns the finished equipment response and its risk controls.

Do not use an ordinary membrane key as implied evidence of a safety function. If an action is safety-related, the system team must define the required architecture, device category, diagnostics, failure response and validation method independently of the graphic panel quotation.

Use a decision table to make quotations comparable

The table prevents one supplier from pricing only a printed face while another includes a complete circuit, tail, connector and mounted review. It also exposes open decisions early. If the owner of a local/automatic transition is unknown, the RFQ is not ready even when the front artwork looks finished.

Connect the visible control to the hidden pin map

The drawing should make every physical key traceable to the controller handoff. Assign a stable function ID to the key, then show its circuit net, common conductor, tail contact, connector position and controller input reference. Use one stated viewing direction for connector pin numbering. Record the contact side and insertion orientation so a replacement drawing cannot be mirrored by accident.

Include the complete tail route, not only its length. Mark the tail exit datum, usable bend region, first-bend keepout, stiffener, connector envelope, strain-relief point and clearance from ribs, fasteners and sharp housing edges. An electrically correct loose sample can become unreliable when the tail is folded beside the stiffener or pulled during assembly.

Indicator windows also need ownership. The HMI supplier can manufacture the clear or translucent window, printed boundary and light-blocking layers specified in the drawing. The equipment team must define what an indicator means, when it illuminates and whether it represents an input request, a controller state or an actual machine condition. Do not ask the overlay artwork to carry a meaning that the controller has not defined.

Approve the sample in the mounted state

Begin with a loose-component inspection. Check the panel perimeter, key positions, windows, print registration, circuit, tail, stiffener and connector. Measure each key at its specified pin pair and confirm that one press changes only the intended circuit. A single successful press is not sufficient; repeat the operation enough times to expose intermittent contact or release behavior.

Then install the panel in the representative enclosure. Use the specified backing support, adhesive landing, gasket or spacer, housing fasteners and tail bend. Confirm that the complete face lies flat, every key can be reached, the indicator windows align, the tail clears the housing and the connector can be mated without pulling the flex.

For the authority check, the controls owner should observe the assigned controller input while the technician presses each local key. This does not require the machine to move. Record whether the expected input changes, whether any second input changes unintentionally and whether the signal returns cleanly at release. Keep this input record separate from the later system test.

Finally, let the equipment owner run the approved state-based test. A physical key may work electrically while a command is correctly refused in an automatic mode. Conversely, a permissive software state cannot repair an intermittent contact. Recording the component, input and machine results in separate columns prevents a good panel from being blamed for application logic and prevents a software response from hiding a poor physical connection.

Keep AI, PLC and safety claims outside the component approval

Baoshengda can review and manufacture the graphic overlay, tactile or non-tactile key stack, membrane circuit, windows, adhesive, flexible tail, stiffener and specified connector. Component evidence can include controlled dimensions, appearance, key registration, continuity, contact behavior, connector orientation and mounted sample observations when the buyer provides an enclosure or representative fixture.

Baoshengda does not choose the AI model, train control algorithms, configure the PLC, define machine modes, approve permissions, validate interlocks, release motion or certify functional safety. It also cannot prove whole-machine reliability, ingress protection or chemical resistance unless the buyer defines the complete assembly, exposure and test method and that work is included in the agreed scope.

This limitation belongs in the quotation and sample report. The ISA discussion shows that AI-assisted automation is receiving current professional attention. It is not evidence that a generated engineering cover, a keypad sample or a continuity report proves automated control performance.

Build the drawing package around decisions, not assumptions

Prepare one controlled package that relates the visible front to the control boundary:

• front artwork with stable function IDs, key zones, windows, active and non-active areas;
• panel outline, mounting datums, housing opening, backing support and adhesive or gasket lands;
• action-and-owner matrix stating local input, accepted controller states and system owner;
• circuit schematic or key-to-net table, common conductors and isolation requirements;
• connector part, contact side, pin numbering view, mating-part ownership and insertion direction;
• tail exit position, route corridor, bend keepout, stiffener, strain relief and service access;
• indication-window function, optical boundary and owner of the displayed state;
• loose and mounted component acceptance methods with pass criteria;
• controller input observation method that does not depend on machine motion;
• system-level test owner for permissions, interlocks, recovery, safety and final release.

Mark every unresolved item as open. Do not convert a worn sample, an old photograph or a software label into an assumed tolerance. If the old panel is the only reference, identify which dimensions were measured, which electrical facts were proven and which geometry still needs equipment-owner approval.

Send an RFQ that closes the quotation boundary

Before using the Request Quote page, send the controlled artwork and mechanical drawing, the key-to-pin map, the full tail and connector definition, the mounted enclosure section and the action-and-owner matrix. Add the planned prototype quantity, production range, revision, service-spare requirement and golden-sample status.

Ask the supplier to state what is included for tooling, artwork, circuit, tail, connector, loose inspection and mounted sample support. Ask the controls owner to state which machine states accept each local request and which results remain outside component approval. When both sides answer against the same evidence package, the quotation compares real scope instead of different assumptions about what AI-assisted control is supposed to do.

The practical goal is not to add more buttons because AI is new, or to remove buttons because automation is fashionable. It is to leave every necessary local action visible, electrically traceable and assigned to the correct validation owner before the first HMI sample is approved.