Project homeWiki source code of TDP4 — Split Role for Robot Control and Data Analysis
Version 1.2 by Tjalling Haije on 2026/03/23 10:37
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.2 | 1 | | |**TDP4 Split Role for Robot Control and Data Analysis** |
| 2 | |**Visual**|[[image:1774262232105-659.png]] | ||
| 3 | |**Description**|Separate **Pilot** (control) and **Analyst** (sensing) to reduce overload and improve detection. Every team that has a pilot for a drone or a robot also needs an analyst that can deal with the information and communicate it to the right stakeholders. | ||
| 4 | |**Intent**|Improve safety and sensor interpretation quality. | ||
| 5 | |**Context**|Tight maneuvering; many sensors and datapoints; limited bandwidth. | ||
| 6 | |**Problem**|One person can’t fly precisely and – at the same time- interpret everything while staying safe in a worksite environment. | ||
| 7 | |**Solution**|((( | ||
| 8 | **Pilot:** vehicle state, collision safety, framing on request. | ||
| |
1.1 | 9 | |
| |
1.2 | 10 | **Analyst:** interpretation, communication |
| |
1.1 | 11 | |
| |
1.2 | 12 | **Squad leader or BoO dispatcher: **communication, decision making. |
| 13 | ))) | ||
| 14 | |**Roles**|Pilot; Analyst; Team Lead | ||
| 15 | |**Taks balance (Human vs Machine)**|((( | ||
| 16 | **Human (Pilot/Analyst):** manual flight/framing; analytic judgements; confirmations; task prioritization. | ||
| |
1.1 | 17 | |
| |
1.2 | 18 | **Machine:** stabilization, obstacle warnings, SLAM/map updates, detection proposals with confidence. |
| 19 | ))) | ||
| 20 | |**Consequence**|Better flight safety and detection; requires two people and disciplined comms. | ||
| 21 | |**Related TDPs/IDPs**|TDP1; IDP1. |