At an ICC, in order to see a particular unit's search/track sector on scope, which S/I is used in conjunction with Sector Bounds to perform track management?

• A. Sector Bounds S/I
• B. Track/Management S/I
• C. Unit/Range S/I
• D. Source/Address S/I

Answer: (D)

The key idea here is how track information is routed to the correct unit’s display. Sector Bounds defines the angular limits of what you want to monitor on the scope, but to show a specific unit’s search/track sector, the system must know where that data originates—i.e., which unit it belongs to. Attaching the Source/Address S/I provides that routing by identifying the data’s origin, so track management can map the sector to the correct unit and display it in the appropriate scope. Without this source/address linkage, the sector might be defined, but there’s no reliable way to tie it to the right unit’s view.

Sector Bounds alone would set the display area but not identify ownership. Track management S/I handles how tracks are created and maintained, not which unit’s sector is shown. Unit/Range S/I could indicate an identity and distance, but the essential link to the correct display path comes from the Source/Address S/I, which names and routes the data to the right unit’s scope.