Good questions, I'll try to answer them to the best of my (limited) knowlegde:
Failsoft means the site is operating without connection to the system controller. i.e. if the link between the headend and the site breaks, the site goes into failsoft mode. Which means that it will not check the validity of LIDs against the controller, it cant do advanced features like data, status messages and profile. It essentially turns the site into a non-networked 'island'.
Site neighbors are controlled by the system controller. The site announces who its neighbors are so the radio knows who to scan for when the signal gets low on the current site. It's a handy way for radios to update their roaming list without having to program a new personality. Each site does not actually talk to each other, in the case of RACOM, every site is by itself they just happen to be linked together to share LIDs, GIDs and roaming.
Most towers are linked via a dedicated T1 fiber line. In some cases 2, going opposite directions for redundancy. Some newer sites or sites close together have a microwave link between them then piggybacks over the fiber to the headend. (which in the case of RACOM is in Marshalltown)
In a system like this, all traffic (voice, data) from a site is sent to the headend FIRST, is relayed to all sites that have a user logged in on them on that GID and is sent back to the originating site for transmission. Allowing RACOM to control all aspects of how traffic is handled.
And the rebanding does effect RACOM. According to
TA800.org, The entire band over 861 MHz is being allocated to ESMR (Nextel Sprint) while the band from 851-854 is exclusive for NPSPAC, 854-860 is Public Safety, Business and Industrial and low-power SMR. If you look at the RRDB, RACOM is almost exclusively in the 860-865 range.
How all this ties together (in my head) would play out like this:
Set up sites on the new frequencies (temporary or permanent at the same site) with site numbers different than the normal ones. (i.e. 22, 23, 24 etc)
Start to announce these higher site numbers in the neighbor plan being sent to all the radios.
ProFile or manually reprogram the radios with the existing sites, AND the new sites with all the same GIDs they use now.
Test and get the new sites networked in and bring them online.
Fire up the new sites and shut down the old ones, the radios will automatically switch to the closest site in their roam list (which now has the rebanded sites in the list) and auto-affiliate.
Shut down the old site and either re-configure it to replace the temporary site, or take it down completely and use it at the next site to be rebanded.
At least thats how I see it going down to minimize down-time.
Thats what makes me wonder why Des Moines and Ames are both announcing a new site 22 in the neighbor list, when that site does not exist (or i cant hear it).
I really hope that clears something up for someone somewhere! Sorry for the VERY ling-winded post.
KCØGIK