Anonymous

Logging Procedures for Subnet Control Operators: Difference between revisions

From WikiNET
m
Took out extra space
(Replaced two external links with internal links)
m (Took out extra space)
Line 1: Line 1:
The primary purpose for logging is to keep track of the activities of your station to allow you to operate more efficiently and accurately.  A secondary purpose is to record information that may be used later to identify opportunities for improving procedures. In some cases, logs may be gathered and compared in order to understand how messages moved from originating stations to their final destination by one or more “hops”. Similarly, logs can be used to understand how replies were routed during a deployment.
The primary purpose for logging is to keep track of the activities of your station to allow you to operate more efficiently and accurately.  A secondary purpose is to record information that may be used later to identify opportunities for improving procedures. In some cases, logs may be gathered and compared in order to understand how messages moved from originating stations to their final destination by one or more “hops”. Similarly, logs can be used to understand how replies were routed during a deployment.


Because your role as a subnet controller (SNC) includes a variety of procedures, no one form efficiently covers everything you should log.  I recommend you spread logging across the following four forms.  
Because your role as a subnet controller (SNC) includes a variety of procedures, no one form efficiently covers everything you should log. I recommend you spread logging across the following four forms.  


* [https://drive.google.com/file/d/1_ryKuDUKzB1gc6DLsuMdG__a4nTuEYn1/view?usp=drive_link ICS 214 – Unit Log]
* [https://drive.google.com/file/d/1_ryKuDUKzB1gc6DLsuMdG__a4nTuEYn1/view?usp=drive_link ICS 214 – Unit Log]