[CRTech] Christian Radio Tech [MSG 83305]
[Thread Prev] [-- Thread Index --] [Thread Next] [Date Prev] [-- Date Index --] [Date Next]
Re: Operation Logs
To: CRTech <crtech@crtech.org>
Subject: Re: Operation Logs
From: Tom Van Gorkom <tomvangorkom@gmail.com>
Date: Sat, 7 Jul 2018 16:29:47 -0500
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=8daOunor/Akh0ZiZ0ZzSzVln5R6zLSf2BHFUf2yltmw=; b=ECkOtk+M2jp2Z2myVYCRcCO2xk4bcAdAw7Fkxe70yRs3K9dypc5QPl2hFe/roD4CPt ICdYf0TiPtRTQJawFYYXIsR0yo4PrcS7yo8abXPsJX5+NRDLF6KtYQ9f4DRN9B94Mx51 2/A030krzHRgP1rYrCiII4sFDPPJOtpYTwt+P+ZqsA6PHGSYAEW8VYMV/JONh7Qu5R96 b557jeklTBTnVm79LKl2XvViSFDVeypvb0Nr4eXNDgdFDmfosG+GZxKj4s74GZNfWEtt WHn3wez3y5U18copiO6F3dSofuVI08TO5NpZNvhzWqpBUFNQQKWSVm7FzP0lLcjCii12 H3fg==
In-reply-to: <CAPQBvqpfP0LSQk6AWs_KyAL6C0nYJDNBf1_+JxSmHwkzpTm82A@mail.gmail.com>
References: <CAB42DVo4ft8u2Ci9qQss0LU9h5Z-DGOUiecUHZ=KAWr6VkAh7w@mail.gmail.com> <CAPQBvqriS4H72irV18yf7bK84YakU4A4=PkWaVh-Z-BJBsnKmw@mail.gmail.com> <BYAPR08MB4424704841BECC47F4F22F7BB5460@BYAPR08MB4424.namprd08.prod.outlook.com> <CAB42DVrpe3S_72Doev1iiVjiQAE3O56DVNixcWbenka-XkuQcg@mail.gmail.com> <CAPQBvqpfP0LSQk6AWs_KyAL6C0nYJDNBf1_+JxSmHwkzpTm82A@mail.gmail.com>
OK, thanks.I appreciate your input.

Tom Van Gorkom
Radio Esperanza Engineering, KRIO AM/FM, KOIR FM
Office: 956-380-8150  
Cell: 865-803-7427

Rio Grande Bible Institute
4300 S US Hwy 281
Edinburg, TX 78539

On Sat, Jul 7, 2018 at 4:27 PM, Mark Croom <markc@newmail.kinshipradio.org> wrote:
Most stations that I inspect log readings once a day, if at all.

I consider that adequate as long as they are staying on top of any issues.

Since a properly configured remote monitor and control system will notify them if the station is out of compliance, that should be adequate. Not ideal, but adequate.

In your case, Tom, you might consider a single page weekly log where you take, say, the 9AM reading (and maybe the 10PM if you are a DA2), and transfer those to a single sheet that is your official log. Attach the EAS printout to that if you are printing those, and call it good. Sign off on that transferred data and let the originals go. Maybe there too many towers in the array to make that practical but most stations I have been in are under four towers and can make it work on one sheet a week.

Keep it practical, while staying on top of your stuff. You don't have to keep all 17 pages a week of automated printouts. I view that as YOUR information you are able to keep or destroy at will, as long as you have some record that your station has been operating within licensed parameters, and are able to show me that you stay on top of it. Remember you're only required to have a minimum of items in the station's official log, and transmitter readings are not really required. EAS tests and tower light anomalies are the only things absolutely required (bare minimum) to be on there, plus your weekly review. I like to see at least one set of transmitter readings a day but I can't really ding anybody who doesn't, if they can show me they have a way to stay on top of things.

Many of the stations I inspect are printing the weekly Sage log and just signing off on that. If there is a problem with either a missing EAS test of a tower lighting anomaly, they just write it in on there, initial it, and then sign and date the finished product.

Many ways of accomplishing the same thing.


On Sat, Jul 7, 2018 at 3:29 PM, Tom Van Gorkom <tomvangorkom@gmail.com> wrote:
Perhaps I should take samples less often so the reports aren't so long. With my AM directional array, for my own tracking I have been sampling all key data every 4 hrs. The weekly report is 17 pages long if all is normal or mostly normal. It's helpful for me but a lot of paper to file. The weekly FM sites are 3-4 pages each. Perhaps a sample every 12 hours would be better. How often do others sample their operating data?

Tom Van Gorkom
Radio Esperanza Engineering, KRIO AM/FM, KOIR FM
Office: 956-380-8150  
Cell: 865-803-7427

Rio Grande Bible Institute
4300 S US Hwy 281
Edinburg, TX 78539

On Sat, Jul 7, 2018 at 3:19 PM, Mike Shane <mshane@salemomaha.com> wrote:

Would it be correct, then, to print the log, review it, sign and date it, then scan it back into electronic form?  It would then have the required signature and date of review.  Still wastes a piece of paper but doesn’t create a paper mess.


Just asking; I use paper.


Mike Shane

Salem Media Group Omaha


From: Mark Croom [mailto:markc@newmail.kinshipradio.org]
Sent: Saturday, July 07, 2018 1:51 PM
To: CRTech
Subject: Re: [CRTech] Operation Logs


In my role as ABIP inspector in South Dakota, I tell my Chief Operator clients that *if* they can show me that they are truly reviewing and approving the logs weekly, they can keep them in any accessible format they want. The trick is that the logs are still required to have a date and signature when reviewed.


Nobody who was claiming to store records electronically was actually reviewing the logs (this requirement is unchanged over many long decades).


So I always recommend they keep a weekly printed log with their signature and date (as those are required to prove the review occurred), on file and retained for two years.


For reference, the rule segment in question is 73.1870(c)(3):


(3) Review of the station records at least once each week to determine if required entries are being made correctly. Additionally, verification must be made that the station has been operated as required by the rules or the station authorization. Upon completion of the review, the chief operator or his designee must date and sign the log, initiate any corrective action which may be necessary, and advise the station licensee of any condition which is repetitive. 


I think the best way to fulfil this requirement is to use a printed log which you review weekly. For most stations, one page per week is adequate. Most of my South Dakota stations print the weekly log from their EAS box, and attach that to any other log form they use. As long as it's reviewed weekly, the review is DATED, and issues are noted and taken care of I am fine with that. Obviously the are required to be legible so that's important to me as well but I don't try to tell anybody what their log should look like as long as the required information is present, and the review is being done and recorded.


That's my nickels' worth of contribution to your consideration.


On Fri, Jul 6, 2018 at 4:26 PM, Tom Van Gorkom <tomvangorkom@gmail.com> wrote:

I'm wondering what other stations are doing with their operation logs.... more specifically, do you still print, sign, and put them in a paper file in case the FCC wants to inspect them or do you keep them on a computer somewhere handy?


We use Davicom site monitors and I set them up to email me the custom logs every week but I am tired of printing and filing them - seems like a waste and I recall that the FCC doesn't give a lot of specifics as to the format or storage. You thoughts and practices?


Tom Van Gorkom

Mark W. Croom
Riverfront Communications, LLC
Yankton, SD

References: Operation Logs
(Tom Van Gorkom <tomvangorkom@gmail.com>, 6 Jul 2018 21:26:34 -0000)
Re: Operation Logs
(Mark Croom <markc@newmail.kinshipradio.org>, 7 Jul 2018 18:50:42 -0000)
RE: Operation Logs
(Mike Shane <mshane@salemomaha.com>, 7 Jul 2018 20:19:26 -0000)
Re: Operation Logs
(Tom Van Gorkom <tomvangorkom@gmail.com>, 7 Jul 2018 20:29:54 -0000)
Re: Operation Logs
(Mark Croom <markc@newmail.kinshipradio.org>, 7 Jul 2018 21:27:11 -0000)
Prev by date: Re: Operation Logs
(Mark Croom, 7 Jul 2018 21:27:11 -0000)
Next by date: Re: Operation Logs
(Mark Croom, 7 Jul 2018 21:30:14 -0000)
Prev by thread: Re: Operation Logs
(Mark Croom, 7 Jul 2018 21:27:11 -0000)
Next by thread: Re: Operation Logs
(Mark Croom, 7 Jul 2018 21:30:14 -0000)