So, if they plan to test the system outside of the existing system, then we should be seeing a whole new system complete with control channels and a new sys ID. Let us know when this happens!
- Status
MetroSafe is not operating yet. I was down in Louisville Friday and nearby Saturday. I checked with my BC396 Control Channel mode and received absolutely nothing.
I did pick up and interesting system, no groups or talking but with a sys Id of 01A6h on a frequency of 860.4625
I did pick up and interesting system, no groups or talking but with a sys Id of 01A6h on a frequency of 860.4625
:lol: :lol: :roll: :roll:
jcpd9720
Member
Hello, Lee here, or if you call 911, "911, communications specialist II Cravens, where is your emergency?"
We are all moved in at 'long term temporary' MetroSafe (as my father in law/fire chief "OFD8001" would put it). Right now, for those of you who are interested in day to day operations, we are almost still 3 seperate entities. The members of the old JCPD are Metrosafe Suburban division. We still answer all the 911 calls from the old county area. As well as dispatch suburban police (F1 and F2), dispatch the Suburban Fire Districts (JCFD 1-2-3-4-Dispatch-and mutual aid), and dispatch Suburban L.M.E.M.S. (Med 2-4-6-10). The old LPD members are Metrosafe Urban division. They answer the 911 calls from the old city area, if it is a police run, they put it in the computer, if it is a fire or ems call they still transfer the call to LFD (yes LFD is in the same room and they still have to route the call). They also dispatch the Urban police (Channels 1 and 2). The LFD members are still LFD, they are not MetroSafe employees, but we are working on that! They recieve the fire and EMS calls for the old city area, and dispatch them (LFR 1-2-3-4 and Med 1-3-5-9).
As is, the operations are moving rather smoothly, but we have had some trouble with the Motorola equipment. Luckily the Motorola people are still there every day, and they have an answer, "It is all HP's fault". The computers that are used for the radios occasionally crash, when they do, it results in a stuck mic. Doesn't seem like much, right? It seems to be happening on the police channels only though. When I am at work, those channels are hopping. The mic stays stuck until the computer is re-booted, logged in, and the program is restarted.
We also operate two seperate CAD systems. The whole suburban side, as well as LFD are on the Positron system, and Urban police are on VisionCAD. As someone who is cross-trained on both systems, I'd have to say that I like the Vision system more. It is a lot more user friendly, and has options that Positron just can't touch. When an officer calls out on a traffic stop, and he gives the lic plate number, the dispatcher puts it in the run. The computer automatically runs the tag through LINK and NCIC, as well as checks it in the LMPD records system. This gives the dispatcher automatic results as to if the vehicle is stolen, dramatically increasing officer safety. With the positron system, we can barely get the computer to recognize interstates.
I am done with the nagging about the down sides to things, if anyone has any questions that I may be able to answer, feel free to ask, I will answer them, or find the answer.
P.S. I have no clue about the 800 Mhz systems of the present, or for the future. Sorry I can't answer those, I am almost completely lost in that area, and it gives me a headache!
We are all moved in at 'long term temporary' MetroSafe (as my father in law/fire chief "OFD8001" would put it). Right now, for those of you who are interested in day to day operations, we are almost still 3 seperate entities. The members of the old JCPD are Metrosafe Suburban division. We still answer all the 911 calls from the old county area. As well as dispatch suburban police (F1 and F2), dispatch the Suburban Fire Districts (JCFD 1-2-3-4-Dispatch-and mutual aid), and dispatch Suburban L.M.E.M.S. (Med 2-4-6-10). The old LPD members are Metrosafe Urban division. They answer the 911 calls from the old city area, if it is a police run, they put it in the computer, if it is a fire or ems call they still transfer the call to LFD (yes LFD is in the same room and they still have to route the call). They also dispatch the Urban police (Channels 1 and 2). The LFD members are still LFD, they are not MetroSafe employees, but we are working on that! They recieve the fire and EMS calls for the old city area, and dispatch them (LFR 1-2-3-4 and Med 1-3-5-9).
As is, the operations are moving rather smoothly, but we have had some trouble with the Motorola equipment. Luckily the Motorola people are still there every day, and they have an answer, "It is all HP's fault". The computers that are used for the radios occasionally crash, when they do, it results in a stuck mic. Doesn't seem like much, right? It seems to be happening on the police channels only though. When I am at work, those channels are hopping. The mic stays stuck until the computer is re-booted, logged in, and the program is restarted.
We also operate two seperate CAD systems. The whole suburban side, as well as LFD are on the Positron system, and Urban police are on VisionCAD. As someone who is cross-trained on both systems, I'd have to say that I like the Vision system more. It is a lot more user friendly, and has options that Positron just can't touch. When an officer calls out on a traffic stop, and he gives the lic plate number, the dispatcher puts it in the run. The computer automatically runs the tag through LINK and NCIC, as well as checks it in the LMPD records system. This gives the dispatcher automatic results as to if the vehicle is stolen, dramatically increasing officer safety. With the positron system, we can barely get the computer to recognize interstates.
I am done with the nagging about the down sides to things, if anyone has any questions that I may be able to answer, feel free to ask, I will answer them, or find the answer.
P.S. I have no clue about the 800 Mhz systems of the present, or for the future. Sorry I can't answer those, I am almost completely lost in that area, and it gives me a headache!
MetroSafe Update
The phase 1 of MetroSafe is completed or nearly so.
Work continues to be done on drafting the specifications/request for proposal on the voice radio system (the 800 MHZ digital trunking deal), which is phase 2. It still has a target date of mid 2007 for completion.
As part of the phase 1 deal, there are 3 sites up and running using 800 digital trunking, using a few of the frequencies for the old/current 800 system. They are being simulcast.
The only traffic on the system is testing at this point.
The phase 1 of MetroSafe is completed or nearly so.
Work continues to be done on drafting the specifications/request for proposal on the voice radio system (the 800 MHZ digital trunking deal), which is phase 2. It still has a target date of mid 2007 for completion.
As part of the phase 1 deal, there are 3 sites up and running using 800 digital trunking, using a few of the frequencies for the old/current 800 system. They are being simulcast.
The only traffic on the system is testing at this point.
Last edited:
jcpd9720
Member
The current 800 Mhz talkgroups are also really good to listen to if you enjoy hearing radio techs talk back and forth on non-private really expensive Nextel phones!
Vague and not compatible
Bolivian Scathology.
Less than 2 weeks ago the issue of ensuring compatibility was discussed at a MetroSafe radio committee meeting. That committee is drafting the RFP for the voice radio system, which is Phase II of the MetroSafe Radio deal. It was emphasized that the new system should be compatible with and inter-connectable to, other systems in our state as they come on line. I know because I was the guy saying it.
For what it's worth, Phase I of MetroSafe is in operation. The entire goal of phase I was interoperability. We can talk will all surrounding counties both in Kentucky and Indiana. We can also talk to the Kentucky State Police. The problem is that it's through a lot of bridging and isn't the easiest to set up. When the new 800 system goes in, the task will be simpler.
If the state government folks have a vision for a larger system, they are doing a real good job of keeping it to themselves.
My opinion is that the denial was strictly political.
Bolivian Scathology.
Less than 2 weeks ago the issue of ensuring compatibility was discussed at a MetroSafe radio committee meeting. That committee is drafting the RFP for the voice radio system, which is Phase II of the MetroSafe Radio deal. It was emphasized that the new system should be compatible with and inter-connectable to, other systems in our state as they come on line. I know because I was the guy saying it.
For what it's worth, Phase I of MetroSafe is in operation. The entire goal of phase I was interoperability. We can talk will all surrounding counties both in Kentucky and Indiana. We can also talk to the Kentucky State Police. The problem is that it's through a lot of bridging and isn't the easiest to set up. When the new 800 system goes in, the task will be simpler.
If the state government folks have a vision for a larger system, they are doing a real good job of keeping it to themselves.
My opinion is that the denial was strictly political.
pblumer
Member
newsalan said:
here I go with a stupid question
What state system is that???
Does KY have a statewide system I know Indiana does or is about to have SAFE-T in Floyd Co but could they use 155.3700 for interop between counties???
jcpd9720
Member
ofd8001 said:
Hey chief, it really isn't that hard to do. I am the go-to guy on 3-11 shift when it comes to setting up a bridge in a quick manner. Have you checked out the Moto-bridge yet, I mean really played with it? Come down one night, call me first to make sure I am there, and I will show you how everything works. (isn't it great that one of our fire chiefs is interested enough to hang out with the little guys in communications?!?)
mastr
Member
- Joined
- May 7, 2005
- Messages
- 496
"If the state government folks have a vision for a larger system, they are doing a real good job of keeping it to themselves."...
The two state mutual aid frequencies have been well known to most "radio people" since about 1980. They are- hang on to your hats, here is the big secret- 453.300mhz and 155.475mhz. They are listed right here on RR and many other places..
The two state mutual aid frequencies have been well known to most "radio people" since about 1980. They are- hang on to your hats, here is the big secret- 453.300mhz and 155.475mhz. They are listed right here on RR and many other places..
Kentucky Mutual Aid channels
Unfortunately Kentucky has not gone the way of Indiana, Illinois and Ohio to develop a statewide strategy for one big happy radio system with users of all disciplines. It would be nice if they did. They had some discussions on a state 800 system, but elected to continue the use of UHF channels for the state police, the biggest entity for state communications. They went from analog to digital and came up with a good system, but only for KSP use.
453.300 and 155.475 ain't exactly interagency, interoperability channels. They are both law enforcement only. So that leaves us fire folks as well as EMS and other responders out.
453.300 is what the state police called their "state" channel. Few state agencies were allowed on the KSP radio net, such as state fire marshal folks (I was one for 12 years) and used this channel as opposed to the regular "post" channels. Unfortunately the state channel wasn't monitored much and you had to call several times before being answered. Lately the vehicle enforcement folks have began to use this channel.
155.475 is the national law enforcement interoperability channel. It is not used much in Kentucky. I don't know of the first dispatch agency who monitors this channel.
A couple of months ago, the Indiana State Police was chasing some person and went through about 3 counties in Kentucky. It was interesting listening, but each agency involved in the pursuit remained on their respective channels, and I never heard a word on 155.475. And, as you can imagine, information took too long to pass between agencies to be useful.
So these may be interoperability channels, if only in theory, but certainly not in practice.
Back to my original point: Kentucky has not done a lot of open discussion on the subject of statewide interoperability plans. They should.
Unfortunately Kentucky has not gone the way of Indiana, Illinois and Ohio to develop a statewide strategy for one big happy radio system with users of all disciplines. It would be nice if they did. They had some discussions on a state 800 system, but elected to continue the use of UHF channels for the state police, the biggest entity for state communications. They went from analog to digital and came up with a good system, but only for KSP use.
453.300 and 155.475 ain't exactly interagency, interoperability channels. They are both law enforcement only. So that leaves us fire folks as well as EMS and other responders out.
453.300 is what the state police called their "state" channel. Few state agencies were allowed on the KSP radio net, such as state fire marshal folks (I was one for 12 years) and used this channel as opposed to the regular "post" channels. Unfortunately the state channel wasn't monitored much and you had to call several times before being answered. Lately the vehicle enforcement folks have began to use this channel.
155.475 is the national law enforcement interoperability channel. It is not used much in Kentucky. I don't know of the first dispatch agency who monitors this channel.
A couple of months ago, the Indiana State Police was chasing some person and went through about 3 counties in Kentucky. It was interesting listening, but each agency involved in the pursuit remained on their respective channels, and I never heard a word on 155.475. And, as you can imagine, information took too long to pass between agencies to be useful.
So these may be interoperability channels, if only in theory, but certainly not in practice.
Back to my original point: Kentucky has not done a lot of open discussion on the subject of statewide interoperability plans. They should.
Last edited:
mastr
Member
- Joined
- May 7, 2005
- Messages
- 496
I'm of the opinion that the best interoperability tool is a well trained, attentive, (appropriately compensated) dispatch staff, but there are few examples of that in this area. If dispatch is on the ball, there will be little need for direct inter-disciplinary communications from police to fire etc. Accordingly, each service can use its own simplex mutual aid freq. for co-ordination on site. Any agency that seriously wants interoperability can afford analog VHF simplex, and a few minutes of training on where the MA channel is on the radio dial. There are literally thousands of serviceable VHF radios in use by police, fire , EMS and EMA personnel in Kentucky. it is a safe bet that most (if not all) of the vehicles involved in your cited IN/KY pursuit had some VHF capability, perhaps even on 155.475, but little/no training in place on how to use it.
Unfortunately, that angle doesn't sell radios very well, no does it offer an excuse to apply for state/federal money to replace systems that are outgrown, worn out or simply no longer supported by the vendor. "Buying a new radio system for interoperability" plays better on TV than does" replacing a system that we bought not too long ago from the lowest bidder, which we have now overloaded with too many users."
As far as a state wide plan, the Commonwealth Office of Technology (COT) has hosted meetings all over the state, wherein the initial plans and proposed standards for interoperable systems have been explained. In that KSP established frequencies for "mutual aid" years ago, it follows that LE will get the first slice of the pie. After all you have to start somewhere, and it is a given that dispatchers are going to remain over worked and under paid.
Unfortunately, that angle doesn't sell radios very well, no does it offer an excuse to apply for state/federal money to replace systems that are outgrown, worn out or simply no longer supported by the vendor. "Buying a new radio system for interoperability" plays better on TV than does" replacing a system that we bought not too long ago from the lowest bidder, which we have now overloaded with too many users."
As far as a state wide plan, the Commonwealth Office of Technology (COT) has hosted meetings all over the state, wherein the initial plans and proposed standards for interoperable systems have been explained. In that KSP established frequencies for "mutual aid" years ago, it follows that LE will get the first slice of the pie. After all you have to start somewhere, and it is a given that dispatchers are going to remain over worked and under paid.
mastr said:
Your exactly right..I know exactly the chase you are refering to because I listened from start to finish as it went out of IN and through KY. It was initiated by the Aurora Police Dept. The ISP was not involved. Every cruiser in the state of Indiana has 155.475 in Indiana it is called I.L.E.E.N, however Fire/EMS do not have this channel.
newsalan said:
Interesting, I wasn't aware of that. I know they don't have them in my area..But that's all about to change with SAFE-T.
pblumer
Member
Wow that is pretty interesting. I have heard some BOLs on 155.370 between Vanderburgh and Henderson Cos here. I would hope that New Albany and Louisville have some sort of Interop going seeing that a car chase could start out in one place and end in the other. Also is it possible for MetroSafe and Safe-T to be interoperable with each other???? So ISP could have a patch TG with LPD and Jefferson CO Sheriff and vice versa.
Patrick
Patrick
- Status
Similar threads
