TL-SF100 Ethernet Splitter

1 February 2023

Effective 1 Feb, all state madar analysts (and state directors if they request it) will get an automated copy of the MADAR Alert Daily.  This doesn't have to be printed out, but can be printed or saved for use by the SMA to see what is going on in their states, PLUS nearby states. This is an extremely valuable tool to help with Project MATCH. The data within it includes contact information. And if a particular op is having excessive "hits" (false alarms) this tool will be a big help to us here at MADAR Operations so that we don't have to waste time on state problems. After all, we have over a 150 sites to maintain. States need to let us know if they want to be on this new automatic daily report.

I cannot stress how far we have progressed since the early days when we envied the Air Force, FBI and CIA and their capabilities if they had applied them to UFOs. In the 1980's we entered the computer age with email, web sites and databases. I think we are out-performing them even today. MADAR ops and state analysts, anyone interested in fact, can get intel every week regarding the MADAR project results.  I'm describing them below in the order of the main file which is by report title. There are 13 weekly files. If anything I'm saying here confuses you, when you look at the file folder below it will probably graphically explain everything better. The titles are presented (and spelled) exactly as shown.

1) 2023-JAN-NodeEvalRep - This is the least interesting to the bulk of our readers, but basically a "report card" to ops with problematic devices.

2) ALERT WEEKLY - A list of unprocessed madar anomalies, including false alarms. It is the compilation of the 7 previous MADAR Daily alerts mentioned two paragraphs ago.

3) ActiveNodes - Shows the active nodes, which are the madar sites running, out of the total devices in the field.

4) CorrelationsPerState - This is the report on the number of potential correlations per state with madar sites, to show which states are getting results. This is no reflection on the state operations since a state may have a lot of sites but just not having reported sightings.

5) DAS-Equipped - This link shows the MADAR sites that are equipped with an audible alarm system, to get the reaction teams out looking and taking down additional data, videos, night-vision shots, etc.

6) Daily Offline Report - To help us maintain the system, this list of offline nodes can change every day, but we utilize only one of those dailies here (in the weekly) to show the reader just how many and which nodes are for some reason not running. The op always gets an automated one but this list is for everybody to see, in case there is an unresolved issue, etc.

ere is how we establish the status and success of the program. This database list linked in the weekly is updated each Saturday morning for anyone who made a desktop icon for it.  It shows in date order all the sightings that have potential or actual correlations, if it has been investigated, who investigated, and the disposition. It also shows what type of MADAR anomaly it was, such as "code blue" (alarm and madar/visual) or SCRAM (data instances where the time matches the variation in magnetometer and compass readings).

8) MonthlyAlerts - A compilation of the previous weeklys, this list shows who is having repeated false alarms without taking any action to remedy the situation.

9) MonthlyNMS - here we get into the fun part where we see the culled reports of potential sightings of interest that our MADAR UFO Officer, Jeremy Haslam compiles each month, mostly from NUFORC. I go over these items to see if there might be a potential correlation and then file a CIR or "contact information request" with Christian Stepien of NUFORC so we can get investigators to check these out.

10) NOL60 rep - Then there is the printout which shows any nodes that have been offline for over 60 days. Say need to be Z-d out of the system or Ops might need to be contacted to find out why they are not online. I keep job tickets (work orders) on all MADARs being handled by myself or tech support.

11) NodesByStates - This database printout groups the MADAR sites by state so one can see how many MADAR sites there are in each and who operates them. The absence therefore depicts which states have no MADAR dataProbe presence. 

12) RunRep - This is a database with the MADAR sites in node order, grouped first by nodes actually running at the time of the inventory, then by those NOL, followed by the Z-outs.  It's similar to the ActiveNodes list (item 2) but goes farther to show ALL three classes of nodes. It includes the ones offline and those no longer in the system (Z-outs). The latter are those that were moved to another location with a new data history, and a new node number had to be assigned to it. For example, a recent RunRep showed a total of 153 active nodes, 122 running and 31 NOL. The Z-outs are listed but not counted.

13) STATS/ - This folder is a depository for any report or any statistics such as graphs or reports by our team or others that should be of interest to all of us

Fran Ridge
Newburgh, Indiana