TAIWAN SYSTEMS INTEGRATION02 / ELECTROMECHANICAL PROTOTYPING · PRE-FORUM DISCUSSION
A proposed mechanical prototype and controls-interface review for the next smart-vent iteration.
Engineering proposal (I) · Counterpart interest unconfirmed · Hardware tests not executed
The forum brief seeks rapid prototyping for a smart vent with reversible electric fans and coordinated control before the following January CES [F1, p. 2].
Begin with one approved vent module: housing, fan mounting and test fixture, plus a review of the provided controller interface. Keep airflow performance and coordinated control as measured acceptance items, not assumed capabilities.
Zensys announced a working residential prototype on 23 August 2026 [Z1]. Confirm the gap between that prototype and the forum request before estimating scope. UAV motor catalogues do not establish suitability for a reversible ventilation fan.
Read Zensys’s official reference ↗THE FIRST CONVERSATION
Is the requested work a new housing, fan/drive revision, control improvement or preparation for manufacturing? Confirm the frozen prototype revision, demonstration date, shipping deadline and who owns the controls.
A scoped feasibility review, followed by a separately agreed prototype quotation. Minimum order, sample count, fees, lead time, subcontracting and IP terms remain unknown.
Quote dependencies: approved inputs, access, named assignees, equipment, material availability and acceptance limits. The website does not reserve capacity.
P2 · Manufacturing reference; no claim that this is a ventilation component.
P2 · Equipment/process evidence; actual gauges and sample report needed.
P2 · Reference only; ventilation suitability unverified.
Current AS9100 renewal is unverified. The retained certificate copy expired on 14 March 2023. Brand, assembly location, test results and procurement eligibility must be assessed separately.
| Proposed role | Responsibility | Current status |
|---|---|---|
| Buyer design owner | Approves requirements, interface, drawings and final acceptance. | Named assignee, availability and authority not yet confirmed. |
| Project coordinator | Tracks scope, English technical communication, quote inputs and decisions. | Named assignee, availability and authority not yet confirmed. |
| Integration / controls engineer | Owns the permitted electrical/software interface and test configuration. | Named assignee, availability and authority not yet confirmed. |
| Mechanical / manufacturing engineer | Owns DFM, process selection, material and inspection plan. | Named assignee, availability and authority not yet confirmed. |
| Validation / configuration engineer | Owns measurements, calibration references, evidence and issue tracking. | Named assignee, availability and authority not yet confirmed. |
The four delivery roles are a planning model for the current delivery team; assignments, equipment and capacity have not been verified. Historical original-supplier work is not automatically attributed to that team.
Alliance identity: Zensys — unknown; 合機 (Hé Jī) succession/core team and Jing Mao manufacturing coordination — user-confirmed. This work package: research proposal, no confirmed engagement. Legal supplier, subcontractors and acceptance signatory remain to be designated.
NOT EXECUTED / PROPOSED TEST PLAN
Numeric limits are agreed with the buyer before testing. An unspecified limit blocks acceptance. Each run must record hardware, firmware, OS, software/model, test configuration, environment, workload and operator; mark irrelevant fields N/A with a reason.
| Stage | Entry condition | Method | Pass / exit condition | Evidence files |
|---|---|---|---|---|
| Desktop / DFM | Buyer freezes drawings and identifies design and controls owners. | Review assembly, mounting, tolerances, fan clearance and safe access. Record each open drawing question. | Every critical interface has an approved drawing or blocking issue; no unresolved safety prerequisite to bench work. | dfm-review.csv; approved-drawing-index |
| Offline / command contract | Protocol or mock contract approved; no powered fan connected. | Replay direction/start/stop and duplicate/stale commands against the agreed state table. | Expected states match the approved table; forbidden transitions and stale commands are rejected visibly. | command-table.csv; replay-log |
| Bench / single module | Guarded rig, fan/drive, calibrated instruments and test limits approved. | Measure airflow/pressure operating points, noise at stated distance/background, power and temperature. Exercise the specified safe reversal sequence. | Every result is within buyer-approved limits, with setup and uncertainty recorded. No generic motor benchmark substituted. | measurement.csv; setup-photos; calibration-register |
| Bench / coordinated modules | Buyer specifies unit count, control revision, network and allowed timing error. | Issue coordinated commands; disconnect one unit, restore it and compare timestamps/status across all units. | Timing, safe failure and recovery meet signed limits. Single-unit success does not establish fleet behaviour. | coordination-log; fault-log; acceptance-signoff |
All stages are currently unexecuted. Simulation/replay verifies only the named software behaviour. Bench, environmental and field results remain separate. Stop if a prerequisite, permit, safe test arrangement or accountable operator is missing.
Record voltage, continuous/peak power, mass, cooling, mounting, connector pinout, protocol, units, frequency, time source, latency, memory/storage, offline/loss-of-link behaviour, authentication, permissions, update/rollback, logs, HBOM/SBOM and code/model/data licences. Confirm who can read, store, receive, update or control data; offline operation; and where post-processing happens.
Unknown / blocking: Latest prototype revision; fan/drive availability; airflow, pressure, noise and thermal targets; coordinated-control protocol; required sample count; calibrated test rig; named technical owner; budget and delivery date. No CES deadline or capacity is promised.
These are working templates created for this proposal, not completed measurement records or inspection reports.
Last checked: 20 October 2026. P1 = original organizer document; P2 = company-authored material; I = engineering proposal; U = unknown.
Proposed next sequence: confirm demand → exchange permitted scope information → nominate technical owners → review a small work package → agree schedule, quote and acceptance. An MOU discussion is conditional on mutual interest and organizer process.
Start with non-confidential inputs. “Not yet determined” is acceptable for open items.
Page context: zensys-vent-prototype · Revision 1.0 · F1 p. 2 / F2 pp. 4, 10, 12. This page address and the prefilled subject travel with the enquiry.
BE PASSIVE receives the enquiry. It is not automatically sent to Zensys, an organizer or a supplier. Receipt by the coordination desk does not establish acceptance of the work package.
Review the other proposed work package →