Most private-network diagrams are clean because they omit the building, devices, interference, transport failure and operational ownership. Those omitted details are where the deployment lives.
Decision one: spectrum
CBRS GAA and PAL are not simply free and paid versions of the same design. Protection, interference exposure, SAS behavior, power limits and local occupancy affect availability and capacity. Licensed or shared spectrum must be evaluated against the consequence of interruption—not only acquisition cost.
Decision two: core and failure behavior
Core placement determines what continues when WAN connectivity fails. A local core can preserve local service; a cloud core can simplify lifecycle management. Neither is universally correct. The requirement is what the plant, campus or utility operation must still do during the outage.
Decision three: devices and applications
Band support, SIM/eSIM provisioning, power behavior, mobility, application retry logic and certification timelines often constrain the solution more than RAN capacity. Validate the actual device population early—especially scanners, sensors, routers and industrial endpoints.
Acceptance must reflect design intent
Define numerical coverage, quality, capacity, mobility and application targets before installation. Test independently against the real environment and preserve a day-one baseline. A heatmap without method, device and threshold is presentation—not acceptance evidence.
Operational ownership is architecture
Someone must own spectrum coordination, SIM lifecycle, alarms, software versions, change control and incident escalation. If those responsibilities are undefined, the network is incomplete even when every radio is online.