Batboard

i've allways been curious... i operate on a Type II trunking system which does Analog, and recently added few Astro channels. using MCS2000, and XTS2500, both in analog mode.

there is one channel which i am most curious of.. it's called "REGROUP" on our radios.. we've been told that in a large scale even, we should be told to switch to this frequency, and the system will make a temporary talkgroup with the radios sitting on that channel.. that seems a bit bizzare to me. the frequency also hums while the radio is merely tuned to the TG.

anybody with high-end knowledge, please explain this to me.. my sponge of a mind is wanting knowledge.

libuff wrote:...Analog, and recently added few Astro channels. using MCS2000, and XTS2500, both in analog mode....

The MCS2000 is a Analog Only Radio Anyway...........It will never do ASTRO.

DYNAMIC REGROUPING a Technical explanation...

In a trunked radio frequency communications system, a dynamic regrouping scheme includes an effective user interface, automatic support of multi-site systems, the capability to program individual radio transceivers with multiple new groups dynamically, a fast rate of reconfiguration, instantaneous switch over to prevent radios from residing in immature groups, and a satisfactory mode of operation should the site controller (or site controllers in non-fault tolerant systems) fail. Some of the dynamic regrouping features includes unlimited prestored plans and source and destination groups per plan, regrouping at the plan or destination group level, an advanced user interface, automatic support of multiple sites, fast regrouping at the rate of over 30 radios per second while reducing loading on the system control channel, and fast activation/deactivation. Each plan can be immediately activated or deactivated and users are effectively regrouped together. An alternate control channel is used to regroup transceivers to avoid undue main control channel loading and to increase rate of regrouping

libuff wrote:there is one channel which i am most curious of.. it's called "REGROUP" on our radios.. we've been told that in a large scale even, we should be told to switch to this frequency, and the system will make a temporary talkgroup with the radios sitting on that channel.. that seems a bit bizzare to me. the frequency also hums while the radio is merely tuned to the TG.

Normally the regroup assigned channel sits empty in the radio. In the event a console operator wants to create a temporary TG they can specify a group of radio IDs which the system then sends out a command to the radios to tell them to take 'this' TG ID and use it for the regroup channel. You can then use the regroup channel like any other TG. You'll only have one per system.

To go even further you can lock the channel selector to that mode so that the user cannot change out of it.

For example, the San Diego County RCS (Cali.) uses this method for stolen or missing radios. They send a regroup command to the radio and lock the channel to the regroup channel. Then a pre-recorded messages is continually sent over that TG instructing what to do with the radio. The channel is aliased "REWARD". From an admin point of view it's a much better way to do it than inhibiting.

I still must be missing something about this dynamic regroup thing. All I'm getting is that it can become a new talkgroup. So what is the difference between that and just a normal talkgroup that already exists?

"... So what is the difference between that and just a normal talkgroup that already exists?"

Nothing, actually. Radios can be regrouped to a new talkgroup or to a talkgroup that already exists.

Regrouping is a tool. A very versatile tool. Just not everybody realizes the value.

Take a biscuit joiner. A zillion guys off the street could look at one and see no point to it at all. On the other hand, a real woodworker gets it right away.

Show him regrouping and a communications guy "gets it".

Take a couple examples.

Let's say we have an incident. The Incident Manager has some law guys that need to talk to some fire guys. The law radios don't have fire talkgroups. The fire radios don't have law talkgroups. You're the Comm Leader. "Help us out here. Make it happen." What are you going to do? Get out a laptop and start programming radios? No. Use regrouping. Each radio can be given a common talkgroup through regrouping. Each of the users can switch to it to interoperate and they still have all their normal talkgroups available.

Another example. A BIG fire. Mutual aid. Lots of help from neighbors. Their radios are not on the same system. We need to hand out radios that are on our system. We gather up whatever radios can be spared. ANY radios that are on our system; law, fire, public works, meter reader, dog catcher. We regroup all of those radios to a talkgroup being used for the incident. They can be selector locked so they don't accidently get confused or on the wrong channel. Hand it to the guy and tell him: "Just turn it on and talk".

Same deal for a search and rescue operation. All you need to make the radios interoperate is a plan [ICS-205], the ID numbers, and a few moments at a system administrative terminal [consoles don't initiate regrouping]

Regrouping plans can be preconfigured for specific sorts of envisioned emergencies or created ad hoc. It should be part of your TICP. Don't have one? The Feds want you to have one if you want their grant money.

Nice answer.....

Ah, I get it now. It all of a sudden hit me after years of scratching my head. Thanks!

Actually, I didn't much "get it" when I first heard about regrouping, mostly I think because the sales types push it as a solution in their vision of things like "storm plans" .

Most of us in the field solve those issues when we fleetmap a system. You create "common" and "event" talkgroups and put them in all the radios. That takes care of most of the day-to-day interoperability needs.

It's the situations you can't plan for where you need tools like regrouping.

xmo wrote:Actually, I didn't much "get it" when I first heard about regrouping, mostly I think because the sales types push it as a solution in their vision of things like "storm plans" .

Most of us in the field solve those issues when we fleetmap a system. You create "common" and "event" talkgroups and put them in all the radios. That takes care of most of the day-to-day interoperability needs.

It's the situations you can't plan for where you need tools like regrouping.

Agreed, with one caveat: the "special event" talkgroups should be disabled during normal operations, to prevent their becoming chit-chat or "get the coffee" channels.