What do we do with obsolete sites in a TRS?

[nd5y]

I don't remember seeing discussions about this before.
What is the procedure for handling trunked systems that are migrating from one type of system to another? (Type II to P25, EDACS to P25, LTR to DMR, etc.)

For example these two EDACS systems American Electric Power / West Texas Utilities Trunking System, Various, Texas - Scanner Frequencies, and American Electric Power (AEP) Trunking System, Various, Oklahoma - Scanner Frequencies are being converted to P25 and becoming part of American Electric Power P25 Trunking System, various, Multi-State - Scanner Frequencies.

So now the database is full of sites listed on the EDACS systems pages that no longer exist because they have switched to P25.
As I discover new P25 sites coming online I submit them. That's not a problem.
What about the many database listings for the now obsolete EDACS sites that no longer exist?
What do we (members) need to submit when we can confirm that an old site is gone and no longer has a control channel on the air?

 

[GTR8000]

Database Administrator Handbook Live Version - The RadioReference Wiki

wiki.radioreference.com

That is the current policy for dealing with system migrations. It makes life a little easier for the dbadmins if you submit to both systems. One submission to the new system to have the site added, another to the old system regarding the shutdown of the corresponding site. Submission tickets are assigned to a specific entity in the database, which is why it's less than ideal to submit for multiple entities in a single ticket.

 

[nd5y]

Submission tickets are assigned to a specific entity in the database, which is why it's less than ideal to submit for multiple entities in a single ticket.

What is a specific entry? The site or each channel?
If a site has 20 channels do you have to make 20 submissions?

 

[GTR8000]

Entity, not entry.

I'm talking about one trunked system per submission, or one county for conventional submissions. Some people have a bad habit of lumping multiple entities into a single submission.

If two sites and four talkgroups need to be added to one system, then one submission is fine. But in your example of dealing with two trunked systems, then one submission to each, as I pointed out in my previous post.

 

[nd5y]

Ok now I understand.

 

[west-pac]

I don't remember seeing discussions about this before.
What is the procedure for handling trunked systems that are migrating from one type of system to another? (Type II to P25, EDACS to P25, LTR to DMR, etc.)

For example these two EDACS systems American Electric Power / West Texas Utilities Trunking System, Various, Texas - Scanner Frequencies, and American Electric Power (AEP) Trunking System, Various, Oklahoma - Scanner Frequencies are being converted to P25 and becoming part of American Electric Power P25 Trunking System, various, Multi-State - Scanner Frequencies.

So now the database is full of sites listed on the EDACS systems pages that no longer exist because they have switched to P25.
As I discover new P25 sites coming online I submit them. That's not a problem.
What about the many database listings for the now obsolete EDACS sites that no longer exist?
What do we (members) need to submit when we can confirm that an old site is gone and no longer has a control channel on the air?

FWIW, When AEP added P25 sites in Indiana, they left the existing EDACS system in place and online. I would definitely make sure any EDACS sites are actually offline before assuming they're offline because of a new P25 site that came online.

... and maybe that's a good way to keep the old system data until the full transition is complete,...by adding "(offline)" to the old system site number/descriptions.

 

[GlobalNorth]

FWIW, When AEP added P25 sites in Indiana, they left the existing EDACS system in place and online. I would definitely make sure any EDACS sites are actually offline before assuming they're offline because of a new P25 site that came online.

... and maybe that's a good way to keep the old system data until the full transition is complete,...by adding "(offline)" to the old system site number/descriptions.

When systems change or evolve to new technologies [conventional to DMR repeater, for example], the old system is marked as "deprecated" under the DB tag column for a time.

 

[nd5y]

FWIW, When AEP added P25 sites in Indiana, they left the existing EDACS system in place and online.

They aren't doing that here. Whenever I found a new P25 CC the EDACS CC at the same site was gone.

 

[wa8pyr]

FWIW, When AEP added P25 sites in Indiana, they left the existing EDACS system in place and online. I would definitely make sure any EDACS sites are actually offline before assuming they're offline because of a new P25 site that came online.

... and maybe that's a good way to keep the old system data until the full transition is complete,...by adding "(offline)" to the old system site number/descriptions.

That's the way they mostly did it in Ohio as well; several channels were removed from an EDACS site and added to the corresponding P25 site until P25 was debugged and all the locals were ready to move. At that point the EDACS site was decommissioned and the remaining frequencies were moved.