Verizon Cell Site Infrastructure Database: Managing Power, HVAC, Generator, and FCC Compliance in Memento

A Site Record That Goes Deeper Than the OSS

The OSS knows the SiteID. It knows the network topology, the cell sector configuration, the alarm state. What it does not always know — or at least does not put in front of a field tech who is standing at the gate at 2 AM during a power event — is the GateCombo, the generator's remaining hours, the name and phone number of the biologist who approved tower access and whose approval you need to enter during nesting season, and the last date someone checked the fuel level.

The vzsite2 template is the field intelligence layer that sits alongside the network management system. It is not a replacement for OSS. It is the operational knowledge that network operations actually runs on — the same knowledge that lives in the senior tech's head and needs to survive a staff transition.

Power Plant to DC Load: The Energy Record

DCPlantLoadAmps and DCPlantLoadVolts, each with a corresponding update date and updated-by field, create a timestamped energy audit that the OSS does not maintain. A site where the DC plant load amps were measured eighteen months ago has an outdated energy baseline. When an LTE small cell or 5G NR radio is added to the site, the new load needs to be measured and recorded — and the update date field confirms whether that has happened.

GenStatus as a text field captures whether the generator is operational, on maintenance hold, or removed. GenRemainingHours as an integer is the fuel runtime remaining under current load — the number that determines whether the site survives a grid outage of two hours versus twelve. GenThresholdLimit and GenThresholdType define the NOC alarm points, and GenThresholdIncEm records whether the threshold triggers an escalation to emergency protocols.

Generator fuel tracking runs through FuelCompany, FuelAccount, LastFueledDate, and FuelMonInstalled (the date the fuel monitoring system was installed). A site where the last fueled date is sixty days ago, the monitoring system was installed three years ago, and the remaining hours estimate is based on a load that predates a hardware expansion is a site where the fuel estimate cannot be trusted without a physical check.

Biological Access Restrictions as a Regulatory Record

RstrBiologistName, RSTRBirdType, and the access restriction fields (RstrTowerAccess, RstrGroundAccess, RstrComments) are the environmental compliance layer that most site databases treat as an afterthought. They are not an afterthought at sites where the tower or the surrounding land has active bird nesting restrictions, raptor habitat concerns, or state-level endangered species protocols.

A site with Restriction data that says tower access is prohibited from February through July — the nesting window for a specific raptor species — and that the biologist who issued the restriction needs to be contacted before any tower climb, has two field operations implications. First, scheduled PM work must be completed before February or deferred until August. Second, any emergency tower work during the restricted period requires a documented contact attempt with the biologist, which the RstrBiologistName field makes possible. Without that name in the site record, the contact attempt cannot be documented because nobody knows who to call.

FCC Fields, ASR Numbers, and Tower Lighting

ASRNum (Antenna Structure Registration number) and CallSign are the FCC regulatory identifiers that determine airspace notification requirements. A tower over 200 feet AGL requires an ASR registration and, depending on proximity to airports, specific lighting — TwrLightTypefcc (FCC-mandated light type) versus TwrLightTypeVol (voluntary lighting) — controlled by a TwrLightContMfr/Model combination that the PM team needs to know for controller servicing.

TwrLEDMainStrobe, TwrLEDSideLights, and TWRLEDMainStrobe as boolean fields capture the LED conversion status — relevant because LED tower lighting systems have different power consumption profiles, different maintenance schedules, and different FAA-approved flash patterns than the legacy incandescent/medium intensity systems they replace.

AirportCodePublic and AirportCodePrivate handle the dual airport proximity scenario where a tower is within the notification zone of both a commercial airport and a private airfield — a situation that is more common in suburban expansion areas where private landing strips precede commercial development.

The Contact Tree That Gets You to the Right Person at 2 AM

SiteTech, TechMgr, and TechDir — three tiers of technical contact, each with name, phone, alt phone, and email — is the escalation path that exists in every telecom organization but almost never in the site record. The SiteTech is the person you call first. TechMgr is the next level if the issue exceeds tech authority. TechDir is the executive escalation for a major outage at a high-value site.

FireDeptPhone, PolicePhone, and FireDeptName are the emergency services contact fields that a tech arriving at a site with a generator fire or a security incident needs immediately, without searching county websites in the dark.

CLLI (Common Language Location Identifier), DOMIPADDR (domain IP address), EMISID, NetworkID, and NSSSiteID variants provide the cross-system identifiers that connect the mobile site record to the billing system, the NOC, the EMIS environmental reporting system, and the NSS network element.