Ex10 2 Traffic - jjmcd/ARPSC GitHub Wiki
Introduction
In order to engage all the affiliated nets, and to also encourage the DECs to develop relationships with their local VHF net, traffic will be routed through all the nets.
At the beginning of the exercise, the SEOC will transmit queries to each District through HF nets. These messages will flow through NTS to each District. The nature of the query will require that the District query each of it’s counties. The result will then be pushed back through NTS ultimately arrivng at the SEOC via an HF net.
Traffic Flow
Four HF nets will meet in sequence receiving traffic from the SEOC. Each of these nets will include representatives from a VHF net. These reps will then take the traffic to the VHF net for delivery to the District. After composing a response, the District will deliver it’s answer to that same VHF net, who in turn will send a representative to one of two HF nets meeting with the SEOC later in the morning.
Figure 1. Traffic Flow Diagram
Net Schedule
Each HF net has a specific time slot with the SEOC. It is presumed that the VHF net will meet following the HF meeting at the beginning of the exercise, and before the HF net at the end of the exercise.
| MITN | MACS | Wolverine | UP | GLETN | QMN | MVTN | SEMTN | TMMTN | NLEUP | |
|---|---|---|---|---|---|---|---|---|---|---|
| 8:00 | Rcv D5,6,7 tfc from SEOC | |||||||||
| 8:30 | RcvD1,D2 tfc from SEOC | Dlv D5,6,7 tfc | ||||||||
| 9:00 | Rcv D3 tfc from SEOC | Dlv D1,2 tfc | ||||||||
| 9:30 | Rcv D8 tfc from SEOC | Dlv D3 tfc | ||||||||
| 10:00 | Dlv D8 tfc | |||||||||
| 10:30 | ||||||||||
| 11:00 | D5,6,7 tfc to GLETN | |||||||||
| 11:30 | D5,6,7 tfc to SEOC | D1,D2 tfc to QMN | D3 tfc to QMN | D8 tfc to QMN | ||||||
| 12:00 | D1,2,3,8 tfc to SEOC |
Next Ex10-2 NTS Net Interfaces
Previous Ex10-2 NTS
Back to Ex10-2
Back to 2010 SET