A graceful restart is designed to minimize the impact on active subscribers by allowing the system, where possible, to complete in-progress procedures or facilitate handovers of active sessions to neighboring cells before the restart actually takes effect, reducing the number of abruptly dropped connections. An immediate, or forced, restart proceeds without this consideration, restarting the unit right away regardless of any active sessions, which will be dropped as a result. NOC engineers may choose between these options depending on the urgency of the situation: a graceful restart is generally preferred for planned maintenance activities to minimize subscriber impact, while an immediate restart might be necessary in scenarios where a unit is unresponsive or where the urgency of resolving a critical fault outweighs the brief additional impact of dropped sessions. Neither option permanently disables the unit, and graceful restarts can be initiated remotely - they do not require physical power-cycling on site.

Remote piloting describes a collaborative working model in which a NOC engineer, using centralized O and M tools such as NetAct and element managers, actively supports a field engineer performing physical work at a site. The NOC engineer's responsibilities typically include preparing the network element for the activity (such as locking affected cells), providing real-time guidance based on system status and diagnostic data, performing remote verification steps (such as confirming a replaced module is detected and operating correctly), and executing any remote configuration steps the new hardware requires. This combination of remote expertise and on-site physical capability allows complex maintenance to be carried out efficiently without requiring every engineer involved to have both deep RAN engineering and bring physically present. It is an active, collaborative role - not a passive one - and it relates only to the technical task at hand, not to logistics such as travel arrangements.

Commissioning brings a newly installed AirScale BTS under NetAct management, loads the correct software and configuration, and activates its cells. The definitive operational confirmation that commissioning is complete and the site is ready for live service is that the relevant cells show an unlocked (administratively enabled) state combined with an operational 'in service'/available status in NetAct, and there are no outstanding blocking faults or critical alarms preventing service. This combination of administrative and operational state, together with a clean alarm list, is what NOC engineers check before confirming a site is live. Appearing on a mapping tool, having fiber physically installed by the transport provider, or having power equipment installed are all useful prerequisite facts about the site's physical readiness, but none of them confirm that the RAN equipment itself has successfully completed commissioning and is carrying traffic.

Accessibility KPIs measure a UE's ability to successfully access network services when requested. RRC (Radio Resource Control) Connection Setup Success Rate is a foundational accessibility metric in 4G/5G, representing the percentage of RRC connection setup attempts - the first step a UE takes to establish a radio connection with the gNB - that complete successfully. A high accessibility value indicates subscribers can reliably initiate sessions when they attempt to. This differs from Retainability, which measures whether already-established connections remain stable until normally released; Mobility, which assesses handover performance as UEs move between cells; and Integrity, which assesses the quality and throughput of an established connection. Because RRC setup is the entry point to accessing the network, its success rate falls within Accessibility, a category NOC engineers monitor closely to detect access-related problems caused by congestion, misconfiguration, or hardware faults preventing initial connections.

Verifying that a software package is compatible with a base station's specific hardware variants, installed modules, and current configuration before activation helps avoid activation failures or operational issues that can arise when a software load does not properly support the hardware it is being applied to, or when configuration elements are incompatible with structural changes introduced in the new software. While an automatic fallback mechanism may eventually recover the unit to its previous working state if activation fails, relying on fallback as the primary safeguard introduces avoidable service disruption and consumes a maintenance window without achieving the intended upgrade. Compatibility considerations are relevant across all supported technologies within Nokia's Single RAN portfolio, not just legacy systems, and compatibility checks are a software lifecycle planning activity - they do not update physical inventory records or remove the need for post-activation health monitoring, which remains essential regardless of how thorough the pre-activation checks were.