Simultaneous multichannel output needs arbitration rules
Aliases: arbitration · scheduling · cross-modal priority
What it is
When several channels need to output at once, rules must decide who goes first, who waits, and who is dropped. Arbitration spans channels rather than ordering within one: visual, auditory, and haptic events compete for the user's attention. Without rules, each channel emits on its own and the user faces several streams at once.
Why it happens
Cross-channel arbitration is necessary because attention is a single limited resource. Even though sight, hearing, and touch are separate channels, the amount a user can handle at one moment is bounded, so concurrent output must be scheduled. The rules' output is not only order but whether to degrade, merge, or drop. Effectiveness depends on allocating attention by consequence rather than by a channel's technical capability or default priority. Unlike within-channel arbitration, cross-channel arbitration must also judge whether an event deserves more than one channel at all.
Studying it
Build concurrent multichannel scenarios and measure critical-event response: fire cross-channel events together and record detection, response time, and losses for critical ones, comparing conditions with and without arbitration. Variables include event count, channel pairing, and the distribution of consequence levels. Include the proportion of avoidable losses—critical events missed because other channels held attention.
Where it stops holding
With few events and fixed pairings, arbitration returns little and a simple convention suffices. Under low user load with ample attention, concurrent output may cause no obvious problem, so high-load laboratory conclusions must be extrapolated with care. If the pieces belong to one event complementarily, arbitration should not separate them; they belong together as a whole.
Applying it
- Define cross-channel arbitration rules covering order, degradation, and drop conditions.
- Allocate attention by consequence rather than by default channel priority.
- Treat complementary parts of one event as a whole so arbitration does not split them.
- Verification: under concurrent multichannel conditions, measure critical-event detection and loss, and tabulate the share of avoidable losses.
Related
- Within the group: D5.06.2 The same event should not be fully repeated on every channel · D5.06.3 Priority follows consequence level, not channel capability
- Adjacent: D2.10.1 Simultaneous alarms need arbitrated ordering, not overlapping playback · D5.01.3 Choosing complementarity or redundancy depends on environmental uncertainty
- Search terms:
cross-channel arbitration·attention scheduling·event dropping
Cards in the same group
- D5.06.2The same event should not be fully repeated on every channel
- D5.06.3Priority follows consequence level, not channel capability
- D5.06.4Arbitration must handle queueing and dropping among simultaneous events
- D5.06.5Interruptive arbitration cuts off feedback; queued arbitration lets it finish first
- D5.06.6Cross-application arbitration usually belongs to the system layer
- D5.06.7Users should be able to override the default arbitration for a situation