Subnet Control Operator Standard Operating Procedure: Difference between revisions
From Portland NET Wiki
BruceSchafer (talk | contribs) Added sub-precedence to Priority messages |
BruceSchafer (talk | contribs) m Corrected formatting |
||
| Line 13: | Line 13: | ||
* Return to your regional subnet frequency and announce your return. | * Return to your regional subnet frequency and announce your return. | ||
* Handle message traffic based on [[Message Precedence|precedence]]. If you receive a surge of Priority messages use the following sub-precedence: | * Handle message traffic based on [[Message Precedence|precedence]]. If you receive a surge of Priority messages use the following sub-precedence: | ||
# EOC traffic to teams | |||
# Teams' replies to EOC | |||
# Team to Team traffic | |||
# Team to EOC traffic | |||
* Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]]. | * Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]]. | ||
* If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions. | * If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions. | ||
