Skip to content
合機 (Hé Jī)TAIWAN SYSTEMS INTEGRATION

FOR US TEAMS VISITING TAIWAN / PRE-FORUM MATCHING

Bring the requirement.
Define the build.

A practical starting point for UAV, robotics and hardware teams: connect an integration review with Taiwan precision manufacturing, then agree a work package that can be inspected and accepted.

Participation and supply-chain eligibility are assessed per project. A presentation is not an approved supplier status, purchase order or signed MOU.

AI-generated concept of drawings, a controller, machined parts, carbon fibre and a civilian aircraft airframe on one engineering workbench
AI-generated engineering concept. Actual manufacturing photographs, historical cases and their sources appear below.
01 / REQUIREMENTA specific problem to solve
02 / ENGINEERINGInterfaces and responsibilities
03 / MANUFACTURINGMaterials and inspection
04 / ACCEPTANCEAn output you can review

PRIORITY / PROPOSED PRE-FORUM WORK PACKAGES

Two specific reasons
to meet.

Focus on subsystem integration, sensing applications and rapid prototyping. These proposals connect source evidence to a first deliverable; neither company has confirmed this scope or its interest.

Start with one interface or one prototype gap. A small, agreed output gives both teams something concrete to inspect.

AI-generated aquatic sensing concept with a generic surface vehicle, sensor, mount and cable
AI-generated concept for discussing a work package. This is not a Jaia product photograph or a completed joint prototype.

PRIORITY 1 / AQUATIC SENSING

Jaia Robotics · sensor and module integration

One sensor, its mechanical interface and a traceable data handoff within the buyer’s existing architecture.

Bring to the review
The sensor and platform models, available interfaces, environmental conditions and sample data.
Define the first output
A mounting and interface review, data handoff format, and a test plan with acceptance criteria.
Review stages, tests and acceptance →
Read the historical water-quality case →
AI-generated smart-vent engineering concept with a grille, fan, control board and mounting fixture
AI-generated concept for electromechanical prototyping. This is not a Zensys product photograph or a validated ventilation system.

PRIORITY 2 / ELECTROMECHANICAL PROTOTYPING

Zensys · next smart-vent prototype

Define the gap after the existing prototype: housing, mounting, fan/drive interface or coordinated-control verification.

Bring to the review
Current drawings and prototype records, the change required, fan/control interfaces and the intended test conditions.
Define the first output
A revision scope, manufacturability questions and a test plan for the selected mechanical or control change.
Review stages, tests and acceptance →
Inspect the machining reference →

Other forum briefs need narrower qualification: precision housings/fixtures may be relevant to smart eyewear or surgical instruments, but optical, medical and product-level integration evidence has not been established.

What is evidenced today?

C2 / command and control

Ground-station and Topology materials exist. Current command interfaces, versions and operator permissions need confirmation.

Inspect the relevant record →

Mission computer

Owen’s supplied CV names Jetson Orin Nano, Linux ARM64 and ROS 2 project experience. A released configuration, software versions and measured workload remain unverified.

Inspect the relevant record →

Edge AI

The supplied CVs describe YOLO-based inspection and onboard-vision projects. Model versions, licences, datasets and reproducible performance evidence are still required for a new delivery.

Inspect the relevant record →

Drone detection

Currently a topic in the technical guide. No dedicated detection product or sensor acceptance evidence is established here.

Inspect the relevant record →
01 / A SPECIFIC REASON TO MEET

Close the gap between a concept and an agreed engineering task.

You have a drawing.

Discuss a bracket, housing, fixture or precision component. Start with manufacturability, material, tolerance, inspection and quantity.

Explore machining evidence →

You have a system question.

Define payload interfaces, power and thermal limits, data handling or a ground-test requirement. Assign the relevant engineering owner before committing to implementation.

Review integration scope and gaps →

Best fit: a defined civil or industrial requirement with a decision owner and acceptance criteria. Requests for an immediately flight-qualified aircraft, guaranteed procurement eligibility or an undocumented API require additional qualification before any delivery commitment.

02 / DISTINCT ROLES, ONE DEFINED WORK PACKAGE

Know who is responsible.

Integration review

合機 (Hé Jī) core team ↗

Evelyn Liu, Ethan Huang, Owen Liao, Julian Tsai and Yi-Sheng Sun. The original four-person succession direction and Sun’s flight-control, guidance-development, software and technical-instruction capabilities are owner-confirmed. Four English profiles document supplied CVs; Sun’s public biography, English name, technical positioning and portrait use are approved. Supporting project evidence and formal credential details remain to be verified. Project scope, availability and technical ownership are agreed for each enquiry.

Precision manufacturing

Jing Mao / BYTE TCM ↗

First manufacturing cooperation entry. Published capabilities cover CNC machining, tooling and measurement. A part-specific review establishes equipment fit, capacity, price and inspection requirements.

Technical-support planning

Chiu-Feng Lin / Uni-Co Tech ↗

Public company information supports discussion of simulation and systems integration. Inclusion here does not allocate its personnel, laboratories or institutional resources to your project.

The network coordinates a discussion. The legal supplier, contracting entity, signatories and engineering leads are named in the agreed work package.

03 / CLAIM → SOURCE → NEXT CHECK

Evidence you can inspect before the meeting.

Historical original-supplier water-quality monitoring reference, retained from the original case
Historical original-supplier water-quality monitoring reference · Read the original case and limits →
Machined component published on BYTE's aerospace capability page
Original manufacturer photograph · BYTE aerospace reference. Component programme and customer are not disclosed. This is not a Zensys component.
Manufacturer-published production and inspection reference
Original BYTE production reference · Source page

Manufacturing and measurement

Official pages describe machining and measurement support. Photographs show published manufacturing references; they do not establish a new part's tolerance, yield or delivery time.

Inspect production evidence →

Aerospace quality-system experience

The retained AFNOR AS9100:D certificate covers 15 March 2020 to 14 March 2023. That copy has expired. Current renewal, holder and applicable scope must be verified before qualification.

View the certificate and limits →

Supply and material experience

The coordinator confirms ongoing supply relationships and semiconductor precision-consumable experience. Carbon-fibre machining is company-published. Neither establishes a named ASML contract or flight qualification.

Customer-reference boundaries → · Carbon-fibre scope →

Evidence labels: manufacturer statements are P2; coordinator-confirmed relationships are attributed separately; proposed fit is engineering judgement (I); missing configuration and performance evidence remain unknown (U). Source register reviewed 20 October 2026.

04 / START SMALL ENOUGH TO VERIFY

Choose one first work package.

A component or fixture review

You provide: drawing revision, material, critical dimensions, quantity, target date and acceptance requirements.

Proposed output: documented manufacturability questions, inspection approach, and a scoped quotation if the requirement is accepted.

Acceptance: both parties agree the drawing, exclusions and inspection criteria. Manufacturing starts only under a separate accepted scope.

An integration or ground-test definition

You provide: platform and payload models, interfaces, power, data restrictions, existing equipment and the failure condition to investigate.

Proposed output: interface boundaries, version list, test cases, evidence filenames, responsible roles and unresolved dependencies.

Acceptance: requirements map to executable tests. A written test plan is not a passed hardware or flight test.

Budget, lead time, staffing, equipment, API access, licences and data/IP rights remain to be agreed. No fixed prototype delivery date is promised by this page.

05 / PREPARE BEFORE THE FORUM

Make the meeting lead to a concrete decision.

  1. Share a capability and requirement brief.

    Use a non-confidential summary first. Identify the demand owner, intended result and constraints.

  2. Seek an interest assessment and introduction.

    Under the supplied organiser process, capability material may be passed to the US co-organising team for assessment and matching. No submission or introduction is claimed here.

  3. Agree scope before discussing a signature.

    Confirm legal parties, technical owners, deliverables, acceptance, costs, IP/data rights, disclosure rules and follow-up actions.

  4. Consider an event MOU if the match succeeds.

    A signing opportunity remains conditional on counterpart agreement and the organiser's arrangements. It does not automatically create a purchase order, funding award or delivery commitment.

Forum information → · Supporting BYTE capability brief → · Source register and supplied-document references →

06 / NEXT STEP

Bring one requirement to the table.

Request a pre-forum discussion or a scoped capability review. Mark unknown equipment, dates or conditions as “not yet determined”.

Manufacturing business contact:
Wayne Chiu · ckchiu@bytetcm.com

Technical owner: designated after scope review. The form is received by BE PASSIVE for coordination; no automatic external forwarding takes place.

Explore products and original evidence →

Current contact: hjuav@icloud.com. Website enquiries are received by the BE PASSIVE coordination desk; email receipt is untested. No automatic email or supplier commitment. Supply, technical ownership and pricing are agreed per project.

English presentation · 20 October 2026 · 合機 (Hé Jī). Supporting source pages retain their original evidence and may include other languages.