-
Notifications
You must be signed in to change notification settings - Fork 27
WMABS HW 001 Hardware Installation Specification
HARDWARE AND INSTALLATION SPECIFICATION
────────────────────────────────────────
WMABS-HW-001
Hardware Bill of Materials, Installation Procedures, and Field Operations Guide
For the Wi-Fi Mesh Access and Backhaul Subsystem Territorial Deployment Programme
────────────────────────────────────────
Document ID: WMABS-HW-001
Version: 0.1 (Draft)
Date: 2026-02-09
Classification: Internal / Restricted
Parent Spec: WMABS-SP-001 v0.1
Companion: WMABS-DP-001 v0.1
Status: DRAFT
CONFIDENTIAL --- FOR AUTHORISED DISTRIBUTION ONLY
Document Control
Revision History
Version Date Author Description
0.1 2026-02-09 H. Martin Initial draft --- hardware BOM, installation procedures, field operations
Review and Approval
Role Name Date Signature
Hardware
Engineering Lead
RF Engineering
Lead
Regulatory
Compliance
Field Operations
Manager
Supply Chain
Manager
Related Documents
Document ID Title Status
WMABS-SP-001 System Requirements Specification Draft v0.1
WMABS-DP-001 Territorial Rollout Plan Draft v0.1
WMABS-IF-001 Node Management Interface Planned Specification
WMABS-TP-001 Test Plan and Verification Planned Procedures
WMABS-RP-001 Regulatory Profile Registry Planned
Conventions
This document uses the keywords SHALL, SHALL NOT, SHOULD, SHOULD NOT, MAY, and MUST as defined in IETF RFC 2119. All normative requirements carry a traceable identifier in the format [XX-NNN]. Requirements prefixed HW- relate to hardware, IN- to installation, SW- to software provisioning, SP- to spares and logistics, and MN- to maintenance.
Table of Contents
This document defines the hardware bill of materials (BOM), physical installation requirements, software provisioning procedures, spares strategy, and field maintenance operations required to deploy the Wi-Fi Mesh Access and Backhaul Subsystem (WMABS) in a defined territory.
It is intended for use by hardware engineers, field installation teams, procurement officers, and operations managers responsible for the physical deployment and ongoing support of WMABS infrastructure.
This specification covers:
-
Phase A (Baseline) --- indoor and outdoor deployments using internal omnidirectional antennas at standard EIRP levels
-
Phase B (Extended Outdoor) --- optional long-range extension using external directional or sectoral antennas, subject to per-country regulatory approval
-
Gateway node hardware augmentation for upstream backhaul connectivity
-
Installation accessories, mounting hardware, cabling, and weatherproofing for both indoor and outdoor environments
-
Software provisioning procedures performed at install time
-
Spares inventory, logistics considerations, and field maintenance operations
This document does not cover application-layer software, captive portal configuration, network management platform architecture, or end-user device requirements. These are addressed in the companion documents listed in the Document Control section.
All hardware specified in this document SHALL be compliant with the regulatory constraints defined in the active Regulatory Profile for the deployment territory (see WMABS-SP-001 Section 5.2). Hardware SHALL carry the applicable regional certification marks (e.g., CE, FCC ID, IC, TELEC) before deployment.
This section defines the component-level hardware requirements for WMABS nodes. All requirements are normative unless explicitly marked as recommended or informative.
Each WMABS node SHALL include the subsystems described in the following sections.
[HW-001] The node SHALL incorporate an ARM64 or x86_64 system-on-chip (SoC) capable of sustained aggregate packet forwarding at 1 Gbps or greater, concurrent with cryptographic operations (AES-CCMP-128 minimum).
[HW-002] The SoC SHOULD include hardware cryptographic acceleration (e.g., ARM Crypto Extensions, AES-NI) to offload WPA3 SAE handshake and 802.11i key derivation from the main CPU.
[HW-003] Each node SHALL provide a minimum of 2 GB RAM. 4 GB is RECOMMENDED for nodes expected to handle more than 50 concurrent client associations.
[HW-004] Each node SHALL provide a minimum of 16 GB persistent storage (eMMC 5.1 or SSD). Storage SHALL support a minimum of 3,000 program/erase (P/E) cycles to ensure a service life of at least five years under expected write patterns.
The following table summarises the compute platform requirements:
Component Minimum Recommended Requirement
CPU Architecture ARM64 or x86_64 ARM64 HW-001 (Cortex-A53+)
Forwarding 1 Gbps aggregate 1.5 Gbps aggregate HW-001 Throughput
Crypto N/A (recommended) HW AES-NI / CE HW-002 Acceleration
RAM 2 GB DDR4 4 GB DDR4 HW-003
Storage 16 GB eMMC 5.1 32 GB eMMC / SSD HW-004
[HW-005] Each node SHALL include at least one IEEE 802.11ax-compliant radio capable of simultaneous dual-band operation in the 2.4 GHz (2.400--2.4835 GHz) and 5 GHz (5.150--5.850 GHz) bands.
[HW-006] The radio SHALL support a minimum of 2 spatial streams (2×2 MIMO) per band.
[HW-007] Internal omnidirectional antennas SHALL be used for all Phase A deployments. Antenna gain SHALL NOT exceed the value specified in the active regulatory profile.
[HW-008] Radio firmware SHALL support Dynamic Frequency Selection (DFS) including Channel Availability Check (CAC), in-service radar monitoring, and automatic channel evacuation.
[HW-009] Radio firmware SHALL support Transmit Power Control (TPC) as required by the active regulatory profile.
Recommended (non-normative): Tri-radio hardware --- two radios for client access (2.4 GHz + 5 GHz) and one dedicated 5 GHz radio for mesh backhaul --- is strongly recommended for deployments where the mesh hop count exceeds two hops. This configuration eliminates the throughput halving effect of shared-radio mesh designs and is referred to as dedicated backhaul mode in WMABS-SP-001 Section 8.3.
[HW-010] Each node SHALL provide at least one Gigabit Ethernet port (10/100/1000BASE-T, RJ-45) for upstream connectivity or PoE power input.
[HW-011] Nodes MAY include a second Ethernet port for dedicated wired backhaul, management access, or daisy-chain connectivity to adjacent nodes.
[HW-012] All Ethernet ports SHALL support auto-negotiation and auto-MDI/MDI-X.
[HW-013] Each node SHALL support AC mains power via a regional-plug AC adapter (100--240 V AC, 50/60 Hz, universal input).
[HW-014] Each node SHOULD support Power over Ethernet (PoE) as an alternative or primary power source. IEEE 802.3af (15.4 W) is the minimum; IEEE 802.3at (30 W) is RECOMMENDED for tri-radio nodes.
[HW-015] Total node power consumption SHALL NOT exceed 15 W for dual-radio configurations or 25 W for tri-radio configurations under sustained full-load conditions.
[HW-016] The power supply (AC adapter or PoE source) SHALL include over-voltage, over-current, and short-circuit protection.
[HW-017] Nodes SHOULD include a Trusted Platform Module (TPM 2.0) or equivalent hardware secure element for node identity attestation, private key storage, and measured boot.
[HW-018] If no hardware secure element is present, node identity keys SHALL be stored in an encrypted partition with access restricted to the WMABS control plane process.
[HW-019] Nodes SHALL use a compact form-factor enclosure suitable for wall, ceiling, or shelf mounting in indoor environments.
[HW-020] Passive cooling (fanless, convection-based) is RECOMMENDED for indoor nodes to minimise acoustic noise and reduce mechanical failure points.
[HW-021] Indoor nodes SHALL operate reliably within an ambient temperature range of 0 °C to +40 °C and a relative humidity range of 5% to 95% (non-condensing).
Gateway nodes are a functional subset of WMABS nodes that provide upstream connectivity from the mesh to a non-mesh network. In addition to all baseline node requirements, gateway nodes SHALL meet the following:
[HW-022] Gateway nodes SHALL include or connect to a reliable upstream backhaul interface. Acceptable backhaul technologies include fibre/DSL modem (Ethernet handoff), LTE/5G cellular router (Ethernet handoff), satellite modem (Ethernet handoff), or direct Ethernet connection to an existing LAN.
[HW-023] Gateway nodes SHOULD provide increased persistent storage (≥ 32 GB) to accommodate local telemetry buffering, log retention, and firmware staging.
[HW-024] Gateway nodes at critical locations SHOULD include an uninterruptible power supply (UPS) capable of sustaining the node and backhaul equipment for a minimum of 30 minutes during a mains power outage.
[HW-025] The UPS, if present, SHALL signal the node when battery capacity drops below 20%, enabling a graceful shutdown sequence.
The following accessories SHALL be available for each indoor node installation:
Item Specification Requirement
Mounting bracket Wall or ceiling mount; VESA [IN-001]
75/100 compatible or
vendor-specific
Ethernet cable Cat 5e or Cat 6, shielded [IN-002]
(STP) recommended; length per
site survey
PoE injector / switch IEEE 802.3af/at compliant; if [IN-003]
PoE is the primary power
source
Cable management Surface-mount conduit, cable [IN-004]
clips, or in-wall raceway as
required
Cable labels Durable adhesive labels; node [IN-005] ID and port function
Anti-tamper screws Security screws for mounting [IN-006]
bracket in public or
semi-public spaces
For outdoor deployment with internal antennas only. All items are subject to the outdoor-permitted classification in the active regulatory profile.
Item Specification Requirement
Outdoor enclosure IP54 minimum, IP65 preferred; [IN-007]
UV-stabilised polymer or
powder-coated aluminium
Weatherproof Ethernet IP68-rated cable gland for [IN-008] gland RJ-45 pass-through
Outdoor Ethernet cable UV-resistant, [IN-009]
direct-burial-rated Cat 5e or
Cat 6; gel-filled or PE jacket
Pole/wall mount kit Stainless steel banding or [IN-010] U-bolt for pole mount; masonry anchors for wall mount
Grounding point Bonding lug and grounding [IN-011]
conductor (≥ 10 AWG copper) as
required by local electrical
code
Drip loop Service loop in cable entry to [IN-012]
prevent water ingress along
cable jacket
Silicone sealant Outdoor-grade; for secondary [IN-013] sealing of cable penetrations
Phase B hardware SHALL NOT be procured or deployed unless explicitly approved for the target territory by the regulatory compliance authority and documented in the Phase B decision record (see WMABS-DP-001 Section 10).
[HW-026] External antennas for Phase B deployments SHALL be type-approved or certified for the deployment jurisdiction. Antenna types MAY include directional panel antennas (typically 12--18 dBi), sectoral antennas (typically 90°--120° beamwidth, 10--16 dBi), and Yagi or parabolic antennas for point-to-point links (typically 15--23 dBi).
[HW-027] RF coaxial cables SHALL be low-loss type (e.g., LMR-400 equivalent or better) to minimise cable attenuation between the radio and external antenna.
[HW-028] All RF connectors SHALL use weatherproof N-type or SMA connectors with appropriate sealing boots for outdoor installations.
[HW-029] Surge protectors (gas-discharge or quarter-wave type) SHALL be installed on each RF cable run between the antenna and the node to protect against lightning-induced transients.
The following table provides reference cable-loss values for RF planning:
Cable Type Loss at 2.4 Loss at 5 GHz Typical Use GHz
LMR-200 equiv. ≈ 0.55 dB/m ≈ 0.85 dB/m Short runs (< 3 m)
LMR-400 equiv. ≈ 0.22 dB/m ≈ 0.36 dB/m Standard runs (3--15 m)
LMR-600 equiv. ≈ 0.14 dB/m ≈ 0.25 dB/m Long runs (> 15 m)
Note: Cable losses are approximate and vary by manufacturer. Actual datasheets SHALL be used for link-budget calculations.
[HW-030] Mast or pole structures SHALL be rated for the wind loading of the installed antenna(s) plus a safety margin of at least 50% above the regional design wind speed.
[HW-031] Rooftop installations SHALL use non-penetrating mounts (ballast trays) where the building structure does not permit roof penetrations. Where penetrating mounts are used, waterproof flashing SHALL be installed.
[HW-032] Lightning arrestors SHALL be installed on all mast-mounted antenna systems. The arrestor SHALL be bonded to the building's grounding system via a dedicated down-conductor (≥ 6 AWG copper or equivalent).
[HW-033] Ground rods SHALL be installed where no building grounding system is available. Minimum ground rod specification: 1.5 m copper-clad steel, driven to full depth, with resistance to ground ≤ 25 Ω.
[HW-034] Outdoor enclosures for Phase B nodes SHALL meet a minimum ingress protection rating of IP65 (dust-tight, protected against water jets).
[HW-035] Enclosures SHALL support an operating temperature range of −20 °C to +55 °C. Active cooling (fans or thermoelectric) is permitted only if passive cooling cannot maintain internal temperatures within the SoC's safe operating range.
[HW-036] Phase B nodes with dedicated backhaul radios and external antennas MAY require PoE+ (IEEE 802.3at, 30 W) or higher-power PoE (IEEE 802.3bt, 60--90 W) to support the increased power draw.
[HW-037] Extended PoE runs exceeding 100 m SHALL use PoE extenders or midspan injectors placed at intervals not exceeding 100 m.
[IN-014] A site survey SHALL be completed and documented for every installation location before hardware is deployed.
The site survey SHALL assess and record the following:
Survey Item Assessment Criteria Impact on Design
Power availability AC mains socket within 5 m of AC adapter vs. proposed node location; voltage PoE selection and frequency confirmed
Mounting options Wall substrate (plasterboard, Bracket type and masonry, metal stud); ceiling fastener type (drop, solid); height selection constraints
Ethernet / backhaul Existing Ethernet infrastructure; Gateway placement
cable run distance; and backhaul type
fibre/DSL/cellular availability
for gateways
RF environment Existing Wi-Fi networks (channel Channel plan and
and RSSI scan); DFS radar node density
exposure; building materials
(attenuation estimate)
Indoor/outdoor Regulatory classification of the Enclosure rating class installation location under local and EIRP limit RLAN rules
Safety and access Working-at-height requirements; Installation confined space; public access method and PPE restrictions
The following steps SHALL be performed for each indoor Phase A node installation:
-
Select and prepare the approved mounting location as determined by the site survey.
-
Attach the wall or ceiling mounting bracket using appropriate fasteners for the substrate material. Verify the bracket is level and secure.
-
Connect the AC power adapter or PoE Ethernet cable to the node.
-
If the node is a gateway or has a wired uplink, connect the Ethernet cable to the upstream switch or modem.
-
Verify internal antenna orientation: the node SHALL be mounted with the antenna plane parallel to the primary coverage area (typically horizontal for ceiling mounts, vertical for wall mounts).
-
Power on the node and wait for the boot sequence to complete (indicated by status LED).
-
Enrol the node into the centralised management system using the procedure defined in Section 6.
-
Apply the territory-specific regulatory profile.
-
Verify RF operation: confirm the node is transmitting on the assigned channel, at the correct EIRP, and has established mesh peering with adjacent nodes.
-
Label all cables with the node ID and port function.
-
Record the installation in the site deployment log, including: node serial number, MAC address, GPS coordinates (or room/floor reference), mounting type, power source, backhaul connection, and installer name/date.
Outdoor Phase A installations follow the indoor procedure above with the following additional steps:
-
Confirm that outdoor operation is permitted by the active regulatory profile for the deployment band and location.
-
Install the node inside the outdoor-rated enclosure. Verify all cable glands are properly tightened and sealed.
-
Form a drip loop on all cables entering the enclosure to prevent water tracking.
-
Connect the grounding conductor from the enclosure grounding point to the building grounding system or a dedicated ground rod.
-
Verify that the enclosure is securely mounted and that all mounting hardware is stainless steel or otherwise corrosion-resistant.
-
Proceed with steps 6--11 of the indoor procedure.
Phase B installations require all Phase A outdoor steps plus the following mandatory additions:
-
Verify that written regulatory approval for the specific antenna type, gain, and mounting height exists for the deployment jurisdiction. A copy of the approval SHALL be retained in the site deployment log.
-
Calculate the combined EIRP: transmitter output power (dBm) minus cable and connector losses (dB) plus antenna gain (dBi). Confirm the result does not exceed the maximum EIRP specified in the active regulatory profile.
-
Install lightning arrestors on each RF cable run. Bond the arrestor to the grounding system.
-
Mount and align directional antennas: verify line-of-sight to the target node using visual inspection and, where available, GPS/compass tools. Record the azimuth and elevation angles.
-
Lock the transmit power in the node configuration to the approved value. Automatic power-up beyond this limit SHALL be disabled.
-
Perform a link stability test: maintain the link for a minimum of 60 minutes and record RSSI, MCS index, packet error rate, and throughput.
-
Record all Phase B-specific parameters in the site deployment log: antenna model, antenna gain (dBi), cable type and length, calculated EIRP, mounting height (AGL), azimuth/elevation, and link test results.
Each node installation SHALL include the following software provisioning steps. These steps occur after physical installation is complete and the node has booted successfully.
[SW-001] The node SHALL perform a secure boot or image verification sequence on every power-on. Firmware images SHALL be cryptographically signed and verified against a trusted root of trust stored in the TPM or secure element.
[SW-002] If image verification fails, the node SHALL refuse to boot the compromised image and SHALL attempt to load a known-good fallback image from a secondary partition.
[SW-003] Each node SHALL be assigned a unique node identity during initial provisioning. The identity SHALL be bound to the node's hardware (TPM-backed or MAC-address-derived) and SHALL persist across firmware updates and reboots.
[SW-004] The node identity SHALL be registered in the management system's inventory database, along with the node's serial number, hardware revision, and firmware version.
[SW-005] The country-specific regulatory profile SHALL be loaded and activated before the node is permitted to transmit. No RF transmission SHALL occur until the profile is validated and enforced.
[SW-006] The applied profile SHALL be logged, including the profile ID, version, country code, and application timestamp.
[SW-007] Initial channel assignment SHALL follow the territory channel-reuse plan defined during Phase 2 planning (WMABS-DP-001 Section 6.1.2).
[SW-008] Transmit power SHALL be set to the level specified in the channel plan, which SHALL NOT exceed the EIRP limit in the active regulatory profile.
[SW-009] Telemetry collection SHALL be activated at the default interval (60 seconds) and validated by confirming at least one successful telemetry report is received by the management system.
[SW-010] The node SHALL be enrolled into the remote management system and SHALL confirm bidirectional communication (management commands and telemetry reporting) before the installation is marked as complete.
[SP-001] A minimum spare inventory SHALL be maintained for each deployed territory. The following table defines recommended stocking levels:
Item Recommended Rationale Stock
WMABS nodes (complete 5--10% of Hot-swap replacement to units) deployed fleet minimise downtime; pre-provisioned with base firmware
AC power adapters 5% of deployed Most common single-point fleet failure mode in field deployments
PoE injectors 3--5% of Replacement for failed PoE-powered injectors or surge-damaged fleet units
Mounting brackets and 10% of deployed Covers damage during fasteners fleet installation or relocation
Ethernet cables (indoor) 10 units per 50 Various lengths; Cat 5e/6 STP nodes
Ethernet cables 5 units per 20 UV-resistant; pre-terminated (outdoor) outdoor nodes or with field-fit connectors
Outdoor enclosures 2--3 per Replacement for territory weather-damaged enclosures
Surge protectors (RF) 2 per Phase B Replacement after lightning territory strike events
[SP-002] All deployed hardware SHALL carry the applicable regional certification marks for the deployment country (e.g., CE marking for EU/EEA, FCC ID for United States, IC for Canada, TELEC for Japan).
[SP-003] Import and customs classification codes (HS codes) SHALL be determined prior to international shipments. WMABS nodes typically fall under HS heading 8517 (apparatus for the transmission or reception of data).
[SP-004] Power adapter plugs SHALL be localised for the deployment country. Universal-input adapters (100--240 V) with interchangeable plug heads are RECOMMENDED to simplify multi-territory logistics.
[SP-005] Shipping packaging SHALL provide adequate drop and vibration protection (ISTA 2A or equivalent) and SHALL include anti-static bags for electronic assemblies.
[MN-001] Nodes SHALL be designed for tool-less or minimal-tool replacement. The target mean time to replace (MTTR) for an indoor node, from arrival on site to operational status, SHALL NOT exceed 30 minutes.
[MN-002] Replacement nodes SHALL be pre-provisioned with the base firmware image and the territory regulatory profile before dispatch to the field.
[MN-003] Upon replacement, the failed node's identity SHALL be revoked in the management system and the replacement node's identity SHALL be registered.
[MN-004] All firmware updates MUST be deployable remotely via the management system, without requiring physical access to the node.
[MN-005] Firmware updates SHALL use a staged rollout strategy: update a small percentage of nodes (e.g., 5--10%) and monitor for anomalies for at least 24 hours before proceeding to the full fleet.
[MN-006] The firmware update mechanism SHALL support automatic rollback to the previous firmware version if the update fails to boot or fails a post-update health check.
[MN-007] Outdoor installations SHALL be visually inspected at least once per year. The inspection SHALL check for enclosure damage, cable degradation (UV damage, rodent gnaw), connector corrosion, mounting hardware integrity, and grounding continuity.
[MN-008] Phase B installations with external antennas SHALL be re-inspected after any severe weather event (sustained winds > 100 km/h, heavy icing, or confirmed lightning strike within 500 m of the site).
[MN-009] DFS event logs SHALL be reviewed quarterly. Territories with more than 10 DFS channel evacuations per month per node should consider channel-plan adjustments or node relocation.
[MN-010] When a node is permanently removed from service, all node identity credentials SHALL be revoked, persistent storage SHALL be securely erased (ATA Secure Erase or equivalent), and the node SHALL be removed from the management system inventory.
[MN-011] Decommissioned hardware SHALL be disposed of in accordance with applicable e-waste regulations (e.g., EU WEEE Directive 2012/19/EU or local equivalent).
A territory SHALL be declared hardware-ready for deployment only when all of the following criteria are satisfied:
# Criterion Evidence Status
1 Approved node model is selected and Purchase order □ Not started procurement is confirmed
2 Node hardware carries valid regional Cert. □ Not started
certification marks (CE, FCC, IC, documents
etc.) for the target jurisdiction
3 Regulatory-compliant antennas are Antenna □ Not started
identified (Phase A: internal; Phase datasheets
B: approved external models)
4 Indoor and outdoor installation kits Kit inventory □ Not started are standardised and stocked
5 Power supply assumptions are Power audit □ Not started
validated (AC/PoE, voltage, plug
type) for the target country
6 Backhaul equipment for gateway nodes Backhaul test □ Not started is selected and tested report
7 Spares inventory is procured and Inventory □ Not started
warehoused in-territory or within manifest
5-day shipping reach
8 Local installation team is briefed Training □ Not started
on installation procedures, safety records
requirements, and regulatory
constraints
9 Site surveys are completed for all Survey reports □ Not started Phase 1 pilot locations
10 Phase B hardware decision is Decision □ Not started
explicitly accepted or rejected with record
documented rationale
The hardware readiness declaration SHALL be co-signed by the Hardware Engineering Lead and the Field Operations Manager before Phase 1 installation begins.
Annex A Phase B Link Budget Calculation Template (Informative)
The following template SHALL be completed for each Phase B point-to-point or point-to-multipoint link. All values are in dBm or dB unless otherwise noted.
Parameter Symbol Value Unit
Transmitter output power P_tx dBm
Tx cable loss L_cable_tx dB
Tx connector losses (total) L_conn_tx dB
Tx antenna gain G_ant_tx dBi
Effective EIRP EIRP dBm
Regulatory EIRP limit EIRP_max dBm
Free-space path loss FSPL dB
Additional losses (rain, L_misc dB foliage, diffraction)
Rx antenna gain G_ant_rx dBi
Rx cable loss L_cable_rx dB
Rx connector losses (total) L_conn_rx dB
Received signal level RSL dBm
Receiver sensitivity (at S_rx dBm target MCS)
Fade margin FM = RSL − S_rx dB
The EIRP SHALL NOT exceed the regulatory limit (EIRP ≤ EIRP_max). A minimum fade margin of 10 dB is RECOMMENDED for reliable link operation.
FSPL formula (free space): FSPL (dB) = 20 × log₁₀(d) + 20 × log₁₀(f) + 32.44, where d = distance in km, f = frequency in MHz.
Annex B Requirement Traceability Index (Informative)
This annex provides a summary index of all normative requirements defined in this specification.
ID Section Level Summary
HW-001 2.1.1 SHALL SoC: sustained 1 Gbps forwarding with crypto
HW-005 2.1.2 SHALL Dual-band 802.11ax radio, simultaneous 2.4/5 GHz
HW-010 2.1.3 SHALL Minimum 1x Gigabit Ethernet port
HW-013 2.1.4 SHALL AC mains power, universal input 100--240 V
HW-017 2.1.5 SHOULD TPM 2.0 or secure element for node identity
HW-022 2.2 SHALL Gateway: reliable upstream backhaul interface
HW-026 4.1 SHALL Phase B: type-approved external antennas
IN-014 5.1 SHALL Mandatory site survey before deployment
SW-001 6.1 SHALL Secure boot with signed firmware verification
SW-005 6.3 SHALL Regulatory profile loaded before any RF transmission
SP-001 7.1 SHALL Minimum spare inventory per territory
MN-001 8.1 SHALL Tool-less replacement, MTTR ≤ 30 min
MN-004 8.2 MUST Remote firmware update capability
MN-010 8.4 SHALL Credential revocation and secure erase on decommission
Note: This table is a representative subset. The complete requirement register SHALL be maintained in the project requirements management tool.