Team scope: colleagues develop calibration, motion reconstruction, SOP models and dashboards. Partners provide digital twin presentation and site installation.
01
The problem
Multiple teams supply algorithms, devices and workstation apps. Input formats, interfaces and verification conditions must align.
02
My responsibility
Project lead for technical coordination; hands-on sample capture, interface adaptation and device troubleshooting; coordinate motion data, SOP and dashboard inputs.
03
Implementation
- Organize and participate in calibration/action capture and handover; report re-calibration issues.
- Adapt cross-network interfaces; report dropped frames and invalid motion inputs.
- Diagnose RS-485 wiring, lamp mapping and switching timing; test MQTT, multiple speakers and microphones.
- Collect workstation samples and align SOP inputs, dashboard data and deployment dependencies.
04
Trade-offs
Test inputs, communication and device feedback separately before combining them. Verify scope changes separately from the original plan.
05
Architecture
Detections → MQTT relay → RS-485 lamps → Warning feedback
Motion / Core21 → Cross-network interface → Digital twin (partners); audio linkage pending.
06
Evidence and boundaries
Ongoing: tools and partial integration records exist. Synchronization, calibration, real-time accuracy and full-chain stability need independent checks and field acceptance. Core21 does not establish finger tracking. Voice control and moving projection remain pending or separate changes.
07
Review
Record interfaces, versions and test results after each site change. Keep runnable, connected and accepted states distinct.