Jump to content

Permits on towers?


Recommended Posts

So I have been curious that with all the holdup on the LTE deployment apparently from what I've read on other forums it seems to be caused by either birds or permits on towers. Why would you need a permit to work on a tower? AT&T, Verizon, and T-mobile all got their towers upgraded quick without permit holdups, so what's the deal with Sprint?

Link to comment
Share on other sites

So I have been curious that with all the holdup on the LTE deployment apparently from what I've read on other forums it seems to be caused by either birds or permits on towers. Why would you need a permit to work on a tower? AT&T, Verizon, and T-mobile all got their towers upgraded quick without permit holdups, so what's the deal with Sprint?

Really now? Verizon has had problems with permits, and some of their permits in Vegas took 3 years to be approved. AT&T has had similar delays in Vegas. T-Mobile is having delays too. Hmm.... I think you've been suffering from mis-information.

 

 

Sent from Josh's iPhone 5S using Tapatalk 2

  • Like 2
Link to comment
Share on other sites

This has been discussed ad nauseaum around our forums.  We aren't going to have a new thread on this, especially with how it is being started.  The OP needs to read around the site first.

 

Robert

Link to comment
Share on other sites

I'll take the bait incase others see this post.

 

Permits are almost always required in order for tower work to begin. Permits are required for everything above a certain valuation ($5,000/10,000+ etc) and tower work is typically in the thousands of dollars of range for valuations. In addition to valuation, material changes that also costs a certain amount of money and / or fundamentally changes a structure (cell towers / office cell sites / etc) also requires a permit.

 

A permit, depending on area, has certain requirements that must be met in order to be issued. If one proceeds to work without a permit issued you will get fined Nx the cost for a regular one, stop work, and apply for one and then pay for it again.

 

This is a typical building permit application for Sprint AFTER negotiations with the site owner and local entities including zoning. 

 

4XQh7XQ.png

 

Note the time of application to time of issuance. 

 

Some areas take more time such as Berkeley or Hawaii which takes well over 9 - 12 months (year(s) sometimes) but typically 3-6 months is how long it takes for an average urban area to get a permit issued. Others, such as county or rural areas can just be done in a day (walk in) or a few weeks which incidentally are where a lot of upgraded Sprint sites and LTE is available at. Can't have LTE if you can't upgrade the equipment which you cannot do if you don't have permission from the.... you guessed it.. government. 

 

In addition, the manner of just exactly what the applicant wants to do also impacts how fast a permit gets issued. Sprint is completely tearing everything out. All old electrical wiring, coax cables, old cabinets, and old antennas are going to be removed and replaced by new antennas, radio heads, cabinets, hybridflex wiring, and electrical equipment. Due to this multiple government departments are going to need to review the permits and do inspections to make sure you don't burn a tower down or topple a tower due to wind load or improperly engineered designs. 

 

As can see in the permit above you have things like Life Safety, Electrical, Fire, Planning, and Structural reviews. Fail any one of those reviews and you have to resubmit and wait for them to review it again. It is an extremely time consuming to do.

 

On the other hand what ATT, Tmobile, or Verizon does is far simpler. ATT and Verizon nowadays are mostly adding a remote radio head to existing antenna setups to enable AWS or other LTE bands. This does not require much in the way of any engineering as it does not fundamentally alter the setup of a tower. In addition to that they also do not rip out everything on the ground in the leased areas like cabinets and electrical wiring which is another headache. 

 

Tmobile Ericsson is also similar in that all they need to do is replace antennas with new Ericsson AIR's or RRUs. They also go through a semi lengthy review process but the fact that they do not touch ground equipment at all makes their permitting go through far quicker.  Nokia Solutions & Networks may also face similar time frames as Sprint in their vendor regions but the fact that they already have upgraded backhaul in place makes it appear that they're deploying faster than Sprint as Sprint may be upgrading at the same pace but 1/2 to 2/3rds of their sites are still waiting on backhaul from a LEC in order to fire up LTE. 

 

Lots of variables. 

  • Like 13
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • My hope is they can spot something in the data that was exported. I am going after all 4 carriers on a multitude of phones and Android versions. My S24 did work.  I have not checked another S24 or S22.  S21s failed which are on Android 14 as well. It should be noted I did not reboot after updates and some of the data was captured on the prior update. Data from some new Boost Mobile Dish (Echostar) sites in the Wheeling area did make it in. Was hoping for more SA data from the duo. Many of the phones are just LTE.
    • I was traveling for a couple of days.   Sunday evening, I upload from 3 phones.  A S-22 and two Moto 5G phones.  Everything looked ok.    How do we explain that?   One person has issues and another person does not.  All my phones have the latest update.
    • Uploaded data without issues on Friday. Now with the latest update I am getting "Cluster #1 skipped: invalid file format detected. File exported for inspection." Doing same with all other clusters. Did this on 4 phones in a row.  Seems to work on s24 ultra just fine. On s21 ultra it says "web data upload failed. No data to send" although 8800 records were displayed. Now gives same error as above. I have not sent the data from 3 other phones.  All should have latest update.
    • After several months of testing, an update to SignalCheck Pro is rolling out on Google Play. It may take up to 48 hours to become available for download. Notable changes include: Added option to display site notes for NSA 5G-NR cells. Enabling this new option (Preferences > Display Settings > Show NSA 5G-NR Site Notes) will cause the app to make an "educated guess" as to what the most appropriate site note is linked to the connected NSA 5G cell, using the PCI and the device location. If it finds an existing entry that is likely to be relevant, it will display the note along with the distance from where the strongest signal from that cell was logged. While connected to NSA 5G, these notes cannot be edited; a valid NCI is required to add/edit notes and that information is not available on NSA connections.   Added option to log cells with missing/invalid PLMN (such as NSA 5G-NR cells). Users asked for the ability to log data for NSA 5G, so a new option (Preferences > Logger Settings > Log Cells with Missing PLMN) will permit this.   Added option to display LTE info above 5G-NR info. Enabling this new option (Preferences > Display Settings > Show LTE Cells Above 5G-NR Cells) shows the same information that is currently displayed, but moves the LTE information above the 5G-NR information. Other changes: Code optimizations and enhancements. Improved Android 15 compatibility. Overhauled Purchases module. Resolved force closes impacting some GSM/LTE connections. Resolved issue with improper 5G-NR PLMN display when NR/LTE PLMNs did not match. Resolved issue with improper PLMN display with single-digit MNCs. Resolved issue with incorrect 5G-NR bands displayed on some devices due to Android bug. Resolved issue with incorrect number of neighbor cells displayed when some cells were unknown. Resolved issue with missing 5G-NR data when sector display is enabled. Resolved issue with saving 5G-NR site notes when NR/LTE PLMNs did not match. Resolved issue with settings to log missing GCI/NCI/TAC/PLMN being ignored. Resolved issues with web data export function. Updated internal libraries. Updated provider database. Updated target API to Android 15. I appreciate all of your support, and a big thank you to the members of the Beta Crew that help with testing and feedback!
    • Oct security update is out.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...