DAS Acceptance Testing: Verify Every Carrier's Service

What Does a DAS Acceptance Plan Cover?

The project scope establishes the required coverage areas, participating operators, service objectives and acceptance criteria. The DAS integrator and RF engineering team develop the measurement methods, walking routes, devices, sampling locations and documentation used to demonstrate compliance. Participating carriers may also have their own commissioning and approval requirements.

A complete acceptance plan typically documents:

• Where: Contracted coverage areas, critical rooms, representative routes and permitted exclusions.
• Who: Each required mobile operator and the status of its participation and activation.
• What: Agreed voice, data, mobility and RF performance objectives for the services in scope.
• How: Test methods, tools, sampling, conditions and pass/fail criteria proposed by qualified engineering personnel and approved as required.
• When: Installation checks, carrier commissioning, owner acceptance and any deferred post-occupancy testing.
• Evidence: Maps, test logs, exceptions, sign-offs and the final handover package.

RF thresholds are not necessarily transferable from one building to another. Appropriate measurements and pass criteria depend on the radio technology, carrier configuration, building use and services being verified. The related DAS RFP Guide explains how acceptance requirements fit into the procurement scope.

Who Signs Off on Installation, Carrier Activation and Final Acceptance?

These are related but distinct milestones. Installation completion confirms that the equipment and distribution infrastructure have been installed and checked against the approved design and construction scope. Carrier commissioning and activation concern the operator-specific signal source, integration, authorization and readiness to provide service. Owner acceptance confirms that the contracted system requirements have been demonstrated and outstanding items addressed or formally documented.

A multi-carrier-capable DAS is not necessarily active for every requested mobile operator on the same day. One carrier's successful testing does not establish commissioning completion for another. The DAS Carrier Activation companion article describes the dependencies that can affect each operator's go-live date.

Project records identify the parties responsible for preparing test evidence and approving each milestone. When the contract permits partial or conditional acceptance, the documentation specifies which carriers, areas and services are available and which obligations remain open.

Commercial cellular acceptance is separate from the testing and approval of a public safety DAS or emergency responder radio communication system. These serve different radio users and are subject to different technical and regulatory requirements.

What Does a Carrier-by-Carrier Acceptance Matrix Show?

A single building-wide pass/fail statement can obscure important differences among operators. Carrier-by-carrier reporting links the evidence for each participating network to its tested areas and required services. The following example illustrates the reporting structure; the carrier labels and statuses are hypothetical, not results from an actual CTS project.

A full acceptance report also contains pass/fail criteria, test dates and conditions, locations, equipment or device details, supporting records, responsible parties and formal approvals. An operator that has not been activated cannot pass live-service acceptance testing. Open items remain visible even if installation is substantially complete.

A single building-wide pass/fail statement can obscure important differences among operators.

Which Building Areas and Movement Routes Need Testing?

Testing areas are derived from approved floor plans and the contracted coverage boundary. Depending on the agreed scope, they can include tenant areas, corridors, conference rooms, lobbies, loading or service areas and parking levels.

Mobility testing evaluates the experience as people move through the building. Calls and mobile applications may need to continue between floors, wings or indoor and outdoor areas. A stationary reading cannot demonstrate continuity along those routes. RF engineers select representative walking paths, transitions and conditions that reflect the contracted service requirements.

Access restrictions can affect the completeness of acceptance results. When a laboratory, clinical space, tenant suite or unfinished area is inaccessible, the documentation identifies the untested area and a return-testing plan. Elevator and moving-equipment tests are coordinated with the facility's safety and access procedures.

What Do Installation Checks and RF Surveys Prove?

Installation records establish whether equipment, cabling, fiber and antennas were installed and checked using procedures appropriate to the selected architecture. Depending on the system, these checks may include cable identification, optical measurements, RF cable and antenna tests, equipment configuration and alarms. Matching report identifiers to the as-built drawings also helps future technicians locate and troubleshoot individual components.

RF surveys document signal conditions at recorded locations. Engineers may evaluate metrics such as reference signal received power (RSRP), reference signal received quality (RSRQ) and signal-to-interference-plus-noise ratio (SINR), using the technology-specific forms appropriate to LTE and 5G New Radio (NR). A usable report identifies each metric, its units, the measurement equipment, the tested carrier, the location and the agreed criteria. For some 5G measurements, synchronization-signal-based metrics, such as SS-RSRP and SS-SINR, may be relevant.

Successful DAS acceptance requires more than confirming the installation is complete. Testing should verify both RF coverage and actual service performance using connected devices, with additional measurements and troubleshooting when results fall short. Rohde & Schwarz provides further detail on these procedures in its guidance for verifying in-building LTE and 5G deployments.

RF measurements can also help distinguish service delivered by the intended indoor system from a signal originating elsewhere. The RF engineer selects the appropriate method for identifying and correlating the serving network or cell.

How Are Voice, Data and Mobility Services Verified?

Live-service verification is performed separately for each active carrier using compatible test devices with valid subscriptions. The testing plan documents supported technologies, device settings, locations and conditions relevant to interpreting the results.

• Voice: Tests assess call setup, call continuity and the agreed voice experience at representative locations and routes. The applicable service features depend on the carrier and network configuration.
• Data: Tests evaluate the applications or upload/download performance specified for the project. Test records capture endpoints, device details and network conditions because these can influence results.
• Mobility: Testing documents continuity and interruptions along agreed routes. An interruption while moving does not automatically establish a handover fault; engineering analysis identifies the underlying cause.
• Cellular versus Wi-Fi: For cellular-service tests, the device's Wi-Fi and Wi-Fi calling settings are documented to distinguish cellular results from Wi-Fi-based calls. Wi-Fi calling is evaluated separately when included in the project scope.

Where emergency-call functionality is part of the agreed verification, the procedure is coordinated in advance with the carrier and appropriate emergency communications authorities. Routine acceptance testing does not include unannounced calls to emergency services.

Acceptance records distinguish results by carrier and, where relevant, by technology or band. Passing results for one operator, device or air interface do not establish equivalent performance on another.

Does a Successful Walk Test Prove Busy-Hour Capacity?

No. A successful walk test shows performance under the conditions present at the time of testing. It does not, on its own, establish what happens when hundreds of people simultaneously use cellular applications in a conference hall, hospital or event venue.

Where peak occupancy is part of the project requirements, the acceptance approach draws on the assumptions discussed in DAS Capacity Planning. Engineering documentation distinguishes what can be validated before occupancy from what requires controlled-load testing, analysis or operational measurements after the building opens.

Those limitations form part of the acceptance record. A speed test at a quiet time does not guarantee an identical result during busy periods; user experience depends on available carrier radio resources, the DAS distribution system and other network conditions.

How Are Exceptions Closed and the System Handed Over?

Failed, deferred or inaccessible tests are captured in an exceptions register, typically identifying the carrier, location, unmet requirement, finding, corrective-action owner, target date and retest evidence. When corrective work affects a shared component or configuration, the engineering team assesses whether additional areas or carriers require retesting.

The final handover package typically includes:

• Approved scope, required areas and final acceptance criteria.
• As-built drawings and an equipment and signal-source inventory.
• Installation and commissioning records applicable to the architecture.
• Carrier-specific RF survey results, voice and data logs, and tested routes.
• Exceptions, corrective actions, deferred tests and signed approvals.
• Alarm and monitoring setup, escalation contacts, access arrangements and support responsibilities.

The accepted results become the system's initial operating baseline. They provide a reference when tenants reconfigure space, equipment is modified or building occupants report degraded service. Ongoing operations, monitoring, repair and dispatch may be provided through services such as CTS MMRD (Monitoring, Maintenance, Repair and Dispatch).