comsec1 said:
would'nt this system have to be spec'd out and put out to bid. how could motorola "offer" a system like that.
hav'nt the techs warned the towns about trunked radio systems. trunked radio systems and public safty do not mix well.
Whoa!
I would hope a professional would prepare a standards-based specification. You don't buy these things off the shelf. I also hope that no company ever feels like it has an 'in the bag' deal. With the advent of the P25 standard, there are a number of manufacturers that can build elements of a system up to the entire system, itself. There's a new one starting up in the US - EADS (they're big elsewhere around the world - no, I don't work for them).
As for the second part of that statement, I'd have to disagree. That may have been the case in 1984 when trunking meant one site with five channels and a PrivacyPlus, GE-STAR or LTR controller, but the technology has evolved tremendously further where that opinion requires serious reevaluation today.
Anyway, the teeter-tottering condition of individual radio systems I've been reading about here seems to be probably the biggest reason why I wouldn't take any advice from the local technicians. If they can't keep those in order, what valid voice do they have in critiquing technology they've never seen?
trunked radio systems are designed with spectrum efficency as the number one priority and not system reliablity. and in todays times interoperabilty is all but lost when you go to a "system" no matter who the manufactor is.
Again, we go back to my statement of having a professional design the system versus a committee meeting at a diner. Survivability in a public safety communications system is an engineered expectation and should not be left to happenstance.
When the designer calls for a standards-based solution that meets EIA/ TIA 102 BACC (the Inter-RF Subsystem Interface), dissimilar equipment behaves in a predictable manner because it follows the protocols defined within the standards. I've seen a P25 environment where a Motorola infrastructure worked with E.F. Johnson and M/A-Com portables. That's not really interoperability, though. Interoperability can be seamless roaming for certain talkgroups from network to network. Despite the hoopla, OPERABILITY trumps interoperability. Who gives a damn if everybody in the world can jump in if it doesn't work in a quiescent environment to begin with?
factor in the cost of maintaining a trunked system and the towns will certainly not go for it.
The fact is that EVERYONE now pays for maintaining their own conventional radio system. When the resources are aggregated and developed over the desired coverage area, you will find the sum of individual systems may be astronomical. THIS is what prevents most systems from achieving redundancy or divergency. Some entities will have requirements for additional coverage or additional capacity. On a trunked system, a new user is assigned a talkgroup and a priority, then the radios are programmed and they are up. Resources added don't benefit only one user, but the entire population as would be calculated in Erlang-B distribution.
At my job, I have 14 conventional VHF base stations, some simplex, some repeaterized, at each of five sites to service two agencies. A third agency would need to find their own COMPATIBLE frequency (impossible here for VHF), add a base at each site and possibly an antenna and feedline, and would be the sole beneficiary. With 14 base stations (that I pay maintenance for, btw), I serve only two agencies. IF I were to replace those with 8 trunked repeaters, I can service not only those two agencies, but EVERY SINGLE AGENCY in my county (which is not Bergen). And, I could so that more economically than I could service only those two agencies. If I was the administrator of the prospective system, I could defray those costs amongst all of the interested participants, guarantee a level of service and provide the 'if it doesn't work it's my problem, not yours' for less than their current costs, because of the aggregation and defrayal.
Finally, everyone with an investment in two way radio that does not have a system that conforms to 1 voice path/ 1 - 9.6k data path in a 12.5 channelspace has significant expense coming with compulsory narrowbanding in 2013.
and than thers the question of who is going to manage the system and decide who gets what features. when every town demands to have phone interconnect for all users whos going to tell then they can't.
In today's world of connectivity, with many devices doing wireless telephone so much better than semi-duplex interconnect, it's foolish to even enable an ersatz feature like interconnect. Forget it was ever a feature of trunking. Anyone who makes a 'buy or no-buy' decision on whether their patrol radios can make phone calls is an idi..., um, out of touch (or has been reading too many Morgan O'Brien position papers). I can say that the last thing I need when I'm on a roof working in a tactical situation is receiving a call from someone who is not immediately related to the mission at hand. We all need to zone in on that little thought the next time someone says some nationwide carrier will look after public safety's interests.
and the biggest problem with trunked systems is that when the stuff hits the fan and everytown responds to a staging area and the system loading crashes the system as anyone who works on a trunk system will tell you will happen how will all the "busys" be explained to all the towns who are paying to be on the system.
just some thoughts.
I actually agree with you on that! A complex system needs to be a living system that has to have priority assignment, zoned features which may partition an operational area, a strong committment to training and discipline (yes, I was born and raised in Bergen County, I can hear you lauging all the way out here, yet there has to be someone with a white shirt and gold regalia in the county who can and will hold the line when he or she has to), using transmission trunking (no hang-timer) versus message trunking, those effects are minimized. And, with aggregation of resource, you make sure surge moments are incorporated in the system archetecture. This is all about engineering.
You're welcome.