TAIWAN SYSTEMS INTEGRATION01 / AQUATIC SENSING · PRE-FORUM DISCUSSION
A proposed sensor, mounting and data-handoff work package for an existing aquatic platform.
Engineering proposal (I) · Counterpart interest unconfirmed · Hardware tests not executed
The forum brief describes a small aquatic vehicle carrying cameras and sensors for aquaculture, fisheries and marine data collection [F1, p. 2].
Start with one buyer-selected sensor, its mounting interface and a traceable data export. Retain the buyer’s vehicle and autonomy architecture. The historical Baihe record provides application context; it does not demonstrate current compatibility or underwater qualification.
Jaia’s official product page describes modular sensors, a hub and its own software based on Goby3 and MOOS-IvP [J1]. ArduPilot-compatible HJUAV equipment is not evidence of a compatible Jaia control replacement.
Read Jaia Robotics’s official reference ↗THE FIRST CONVERSATION
Which sensor, mechanical module or manufacturing operation does Jaia actually want a partner to supply? Identify the exact platform revision and the owner authorised to approve the interface.
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 · HJUAV account; no current raw measurement or calibration supplied.
P2 · Product reference; not Jaia compatibility.
P2 · Process imagery; new-part acceptance remains open.
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: Jaia Robotics — 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 / interface review | Buyer supplies versioned documents and an authorised interface owner. | Trace each required signal from sensor output to host input. Check units, timing, licences and power limits. | Each required field has an agreed value or explicit blocker; both interface owners approve the revision. | interface-contract.csv; questions.csv |
| Offline / sample replay | A permitted sample file and agreed schema exist; no vehicle commands enabled. | Replay the same sample twice; add a duplicate, missing timestamp and out-of-range value. Compare accepted/rejected records. | All deliberately invalid records are flagged; deterministic output; no silent duplicate. This verifies the parser only. | replay-log.jsonl; manifest.csv |
| Ground bench / sensor | Hardware, calibrated reference, safe power supply, owner and thresholds approved. | Compare the sensor with the reference at buyer-agreed points. Interrupt and restore data transfer; reconcile record IDs. | Calibration error, timing and recovery meet signed thresholds; gaps are reported and configurations match. | measurement.csv; calibration-reference; recovery-log |
| Controlled water test | Approved wet-test procedure, equipment, location and responsible operator available. | Test agreed sealing/exposure and repeat acquisition under the specified environment; inspect before/after. | No unrecorded failure; all environmental and data limits in the signed plan met. Passing a bench does not pass this gate. | environment-log; inspection-report; 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: Sensor and vehicle SKU; wet connector; pressure/saltwater scope; software/API access; current equipment; licences; named technical owner; quantity, budget and schedule. No values are inferred from historical flight or water-quality accounts.
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: jaia-sensor-integration · 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 Jaia Robotics, an organizer or a supplier. Receipt by the coordination desk does not establish acceptance of the work package.
Review the other proposed work package →