EVN0042430_DAS_Appendix_A___Exhibits_1-2_FINAL_26.10.01.docx

Appendix A Detailed Scope of Work and Technical Specifications Project Phases

This section provides the overall Scope of Work and Technical Specification requirements of this Solicitation, in addition to the Successful Proposer/Operator's responsibilities for operating the Existing DAS (Distributed Antenna System) network and implementing the installation and continued operation of the New DAS (the “New DAS”). Capitalized terms used but not otherwise defined herein shall have the meanings ascribed to them in the License.

Appendix A describes the deliverables for the DAS network system's design, implementation, ongoing operation, and maintenance. This section collaborates with the following Section II System Specifications.

I. SCOPE

1. GENERAL

The Successful Proposer/Operator shall:

1.1 Maintain and operate the Existing DAS network from the Commencement Date until the transition to the New DAS is completed and approved by the Miami-Dade Aviation Department (MDAD).

1.2 Decommission and remove all Existing DAS network components, other than fiber optic cabling or any other components approved by MDAD to remain in place until after the MDAD representative has signed off on the New DAS System Acceptance Test (SAT) criteria.

1.3 Provide a fully functional turnkey service to design, procure, install, commission, operate, and maintain a neutral host converged wireless New DAS solution at MIA that provides indoor and outdoor wireless coverage using a combination of cellular DAS technologies that meets the requirements specified in this document. Services shall include the necessary elements for a complete and fully functioning converged New DAS network, including repairs, replacements, and required upgrades and updates throughout the term of any resultant Agreement.

1.4 Design should provide for future implementation of CBRS solutions at MDAD’s sole option. This includes the option to passively (or actively) combine CBRS into the antenna coaxial cabling. This includes provisioning passive infrastructure (e.g., antenna coaxial cabling, combiners, couplers) capable of supporting CBRS with minimal additional losses. The design shall support the future implementation of CBRS solutions at the sole discretion of MDAD. The system shall allow CBRS to be passively or actively combined into the antenna coaxial cabling. The contractor shall provide passive infrastructure, including antenna coaxial cabling, combiners, and couplers, that is capable of supporting CBRS with minimal additional losses. All passive infrastructure shall be engineered to accommodate the additional signal losses associated with CBRS combining within the New DAS design. CBRS is currently operated by MDAD on separate infrastructure, but may be integrated into the New DAS at any time during the agreement term. CBRS is currently operated by MDAD via separate infrastructure, but may be integrated into the New DAS at any time during the agreement term.

1.5 In the event MDAD elects to integrate CBRS solutions into the New DAS, General Authorized Access (GAA) or Priority Access License (PAL) spectrum shall be utilized. CBRS deployments may initially use LTE and transition to 5G NR (or 5G SA) or the best available technology at the time of integration, as determined by MDAD.

1.6 Any CBRS (GAA or PAL) use is restricted at MIA without prior written approval from MDAD, and the deployment of which may require a fee to MIA.

1.7 All mobile network operators (MNOs) on the DAS shall fully support CBRS Neutral-Host Network Multi-Operator Core Network (MOCN) or Multi-Operator Radio Access Network (MORAN) for 4G or 5G as a potential DAS alternative. MNOs shall provide MOCN/MORAN capability to enable MIA to shift public cellular traffic to a Private Wireless Network (PWN) MOCN/MORAN network if MDAD elects, ensuring coverage in areas not served by the DAS. MIA reserves the right to move public cellular traffic onto the PWN MOCN/MORAN network if it wishes. MNOs shall provide this MOCN/MORAN capability to ensure that MIA has a solution to provide public cellular coverage in areas that the MNO chooses not to cover by the DAS. This is critical for MIA to provide a safe environment for the public and employees.

1.8 Ensure a seamless transition from the Existing DAS from the Effective Date to the date the New DAS is completed and fully operational (“Transition Period”), with zero service interruptions for passengers, employees, and airport operations. The Existing DAS infrastructure will become the property of MDAD upon termination of the existing DAS agreement. MDAD authorizes the Successful Proposer/Operator to use the existing infrastructure in the design and installation of the New DAS, as approved by MDAD.

1.9 Contract, onboard, integrate, and provision all major commercial WSPs, including AT&T, FirstNet, T-Mobile, and Verizon (each a “WSP”, and collectively “WSPs”), into the New DAS system to provide enhanced Cellular Service for all customers at the Airport. The Operator shall be able to onboard all major WSPs listed above on the New DAS system to deliver service improvements for all Airport passengers on day one of the neutral host New DAS solution going live.

1.10 Complete the implementation of the New DAS system and integrate other WSPs into the New DAS on time once approved agreements are in place.

1.11 Begin New DAS design work immediately upon award with a go-live date on or before a mutually agreed timeline, not to exceed 18 months from Contract award, to ensure that the Airport’s passengers, employees, and facilities have the optimal wireless connectivity experience utilizing the system, as defined in the System Specifications (“System Specifications”) below. The Successful Proposer/Operator shall submit a detailed project schedule within 30 calendar days of award, outlining design, procurement, installation, and commissioning milestones.

1.12 Be the single agent wholly responsible and accountable for all Work and Services to be performed under this Project by it and its authorized Subcontractors, and other third parties, excluding that which is specifically identified as the responsibility of MDAD.

1.13 Conduct operations in a professional, business-like manner to minimize disruption to other Airport tenants or patrons, adhering to MDAD security and operational protocols.

1.14 MDAD shall have no obligation to accept or pay the Successful Proposer/Operator for the sale and provision of additional services not included in the Scope of Work/Services/Technical Specifications unless specifically authorized by MDAD, which is approved and executed in writing by MDAD and the Successful Proposer/Operator.

2. QUALITY ASSURANCE

The Successful Proposer/Operator shall:

2.1 Ensure that all work performed meets the requirements and specifications in the New DAS Agreement, this RFP, and applicable governing standards, including but not limited to 3GPP, CTIA, FCC, NFPA, and IFC standards, as relevant to the New DAS.

2.2 Hold a Project kick-off meeting with MDAD’s Project Manager within fourteen (14) calendar days of the resultant Contract’s Effective Date and provide a preliminary Project schedule identifying primary design, construction, and Wireless Service Provider (WSP) integration activities. Submit a final detailed Project schedule with all tasks and milestones for all phases of the Project within thirty (30) calendar days of the Effective Date, including timelines for RF design, equipment procurement, installation, commissioning, and System Acceptance Testing (SAT).

2.3 Ensure the firm designing and implementing the converged network is certified by the respective DAS and Citizens Broadband Radio Service (CBRS) manufacturers to implement a multi-band, multi-operator New DAS. The design and installation team will proficiently understand and shall demonstrate expertise in the current RF spectrum allocation, WSP technologies, and installation considerations for RF systems, including 4G LTE, 5G NR, and CBRS.

2.4 Ensure all installation personnel are properly trained and experienced in conduit, fiber, and coaxial cable installation techniques, with certifications from recognized industry bodies (e.g., BICSI, FOA) or equivalent, as approved by MDAD. The Successful Proposer/Operator shall submit training records and certifications for key personnel as part of the Project documentation.

2.5 Fiber Installation and Warranty:

2.5.1 MDAD prefers the Successful Proposer/Operator utilize industry standards and MDAD’s standard SC-UPC (Subscriber Connector - Ultra Physical Contact) fiber connectors and avoid fusion splicing.

2.5.2 The Successful Proposer/Operator must use a Corning Optical Communications certified contractor to retain the existing warranty or recertify the Existing DAS fiber plant if (a) it chooses to fusion splice Existing DAS provided fiber, or (b) it chooses to change the connectors on Existing DAS fiber to a type other than SC-UPC.

2.5.3 For new fiber installations, the Successful Proposer/Operator shall use a Corning Preferred Installers (NPI) member or approved equivalent, and ensure the provision of a standard twenty-five (25) year warranty from Corning. The Successful Proposer/Operator must also provide fiber test results in as part of the Project.

2.5.4 The warranty shall commence on the System Acceptance Test (SAT) date and remain in effect for twenty-five (25) years.

2.5.5 The Successful Proposer/Operator shall repair, adjust, or replace any defective fiber equipment, materials, or components at no cost to MDAD during the Agreement term, providing test results (e.g., OTDR, power loss) in Excel format as part of Project closeout documentation.

2.5.6 All third-party warranties, including Corning’s, shall be transferred to MDAD upon Project completion. The Successful Proposer/Operator shall provide all third-party warranties to MDAD.

2.6 All equipment shall be rated for continuous operation under the ambient environmental temperature, humidity, and vibration conditions encountered at the installation locations. Such locations may include environmentally controlled indoor areas (e.g., terminals) and uncontrolled outdoor areas (e.g., parking lots, curbside), with equipment rated for temperatures from -20°C to 50°C and humidity up to 95% non-condensing.

2.7 Ensure all electrically powered equipment is Underwriters Laboratories (UL) or equivalent internationally recognized safety standard approved, with certification documentation provided to MDAD PM.

2.8 All installations shall comply with Parts 15, 22, and 90, Federal Communications Commission (FCC) rules, pertaining to radiation limits and frequency usage both indoors and outdoors, as well as any additional FCC regulations applicable to CBRS and 5G NR deployments.

2.9 Due to the rapid advancement and obsolescence of technology, any product purchased or supplied shall be the newest “version” or “release” of that product certified to work as part of the converged network. This includes all equipment, hardware, software, and firmware, with documentation verifying certification and compatibility provided to MDAD.

Certify the system by providing a Certificate of Commissioning after completion of system implementation. The Certificate of Commissioning document shall certify that the installed system, including cabling, complies with all the requirements of this RFP, the New DAS Agreement, and applicable industry standards (e.g., TIA-568, 3GPP). The Certificate shall include test results verifying compliance with System Acceptance Test (SAT) and Coverage Acceptance Test (CAT) metrics.

2.10 Conduct an RF Site Survey, as necessary, to establish a baseline RF environment within the coverage areas in scope as part of the RF design process. The survey shall include measurements of existing signal levels (e.g., RSRP, SINR) for all WSPs and potential interference sources, with a report submitted to MDAD within 60 calendar days of Contract award.

3. DESIGN AND PRE-INSTALLATION

The Successful Proposer/Operator shall:

3.1 Submit a detailed Project Management Plan within 30 calendar days of the Contract Effective Date. The Project Management Plan shall contain the following at a minimum:

3.1.1 Detailed Project schedule with planned and actual dates for all phases, including design, procurement, installation, WSP integration, commissioning, and testing.

3.1.2 Major milestones, including RF design approval, installation design approval, permitting, equipment delivery, system commissioning, and System Acceptance Test (SAT).

3.1.3 Risk mitigation strategies, identifying potential risks (e.g., WSP delays, permitting issues, fiber shortages) and corresponding contingency plans.

3.1.4 Roles, responsibilities, and level of commitment of Key Personnel (e.g. Program/Project Manager, Lead RF Engineer(s), Systems Engineer(s), Lead Technicians), referred to herein as “Key Personnel”), including organizational charts and contact information.

3.2 Submit a System Commissioning Plan within 60 calendar days of the Contract Effective Date that describes the following at a minimum:

3.2.1 Minimum requirements for each WSP to connect to the New DAS, including backhaul specifications, frequency bands, and interface protocols.

3.2.2 Process for onboarding and connecting each WSP, including coordination with WSP technical teams, equipment integration, and testing procedures. How each WSP will be onboarded and connected to the DAS.

3.2.3 How the entire New DAS will transition into production and ongoing operations.

3.2.4 Procedure for activating New DAS headend equipment, including power-up, configuration, and integration with WSP base stations. How the New DAS headend equipment will be turned up.

3.2.5 Setup process for remote management and monitoring, including Network Operations Center (NOC) integration and alarm configuration.

3.2.6 Detailed steps for each WSP to ‘go-live’ on the system, including validation testing and WSP sign-off.

3.3 Provide all necessary personnel, mobilization equipment, software, hardware, firmware, consumables, and transportation to complete the Scope of Work as stated herein, ensuring compliance with MDAD security and safety protocols

3.4 Submit all deliverables in this section for MDAD’s Project Manager’s review and approval before implementation of the system. MDAD reserves the right to require revisions or changes at any point in the process before providing approval. All submissions shall be in electronic format (e.g., PDF, AutoCAD) with hard copies provided upon MDAD request.

3.5 Within fourteen (14) calendar days of the Effective Date, begin scheduling bi-weekly (approximately two times per month, every two weeks) Project status meetings with MDAD’s Project Manager.

3.6 Daily Progress Reports (“Daily Progress Reports”) are required and will detail work that was performed, and the location of work performed at the end of each workday. Daily Progress Reports shall include:

a. Work performed that day, including specific locations and tasks completed.

b. Planned work for the next day(s), including locations and tasks.

c. Any potential work stoppages, delays, schedule changes, or other Project-related issues impacting progress, with proposed resolutions. Detail any potential work stoppages, delays, schedule changes, and any other Project related information for MDAD to assess the status of the Project adequately.

d. All work-related injuries, safety incidents, or potential safety issues, with mitigation measures. Detail all work-related injuries or potential safety issues.

e. A running percentage of completion compared to the overall Project schedule. Daily Progress Reports will be sent to MDAD’s Project Manager and the other Carrier PMs WSP Project Managers in electronic format (e.g., PDF) by 8:00 AM Eastern the following workday.

3.7 Perform the system design as follows:

3.7.1 Benchmarking

Submit walk-test routes to MDAD’s Project Manager for approval within 45 calendar days of the Effective Date of the agreement. Walk-test routes will be submitted to MDAD PM for approval. Walk-test routes will include coverage and non-coverage areas. Outdoor walk-test perimeter routes for each building are in scope (with MDAD and Security personnel as needed). Walk-test routes will have arrows on each proposed pathway and be overlaid on MDAD-provided floor plans. Walk-test routes will be granular and as detailed as possible. The same walk-test routes shall be used throughout the Project and after the New DAS is commissioned during routing routine system performance testing, including System Acceptance Test (SAT) and Coverage Acceptance Test (CAT).

3.7.2 RF Design

RF design will use an industry-standard software-based design and simulation/prediction tool. Examples of such devices include iBwave, RanPlan, Wireless Valley, etc. A propagation model shall be done for each of the desired RF bands and associated wireless technologies within that band. The model will show predicted coverage on MDAD-provided floor plans for all coverage areas. The RF design will be done in two (2) stages as follows:

3.7.2.1 Initial RF Design

Initial RF design shall include coverage plots, carrier counts per technology per band per sector, power levels per RF carrier, and composite power levels feeding the New DAS headend. The design shall include an RF link budget (uplink and downlink) for each zone or coverage area, detailing signal strength (e.g., RSRP) and quality (e.g., SINR) metrics. The Successful Proposer/Operator shall include the total number of sectors per coverage area per WSP per technology. The Successful Proposer/Operator shall submit the initial RF design to the MDAD’s Project Manager for approval after obtaining WSP approval, with WSP approval documentation (e.g., email confirmation) included.

3.7.2.2 Final RF Design

The Successful Proposer/Operator shall obtain approval from MDAD’s Project Manager on the initial RF design before submitting the final RF design. All WSPs shall approve the final RF design before submission to the MDAD’s Project Manager. To certify acceptance, an email from the other WSP Project managers stating that the design for the Project meets their design requirements will be submitted to the MDAD PM, including the WSP Project managers’ formal contact information. The final RF design shall include the final RF configuration of the New DAS with coverage and quality prediction plots for all WSPs, including heatmap coverage plots showing signal strength (e.g., RSRP ≥ -85 dBm) and quality metrics (e.g., SINR ≥ 15 dB) for each frequency band, overlaid on MDAD-provided floor plans, with bleed-out analysis. The Successful Proposer/Operator shall submit the total number of sectors per coverage area per WSP per technology.

3.7.3 Installation Design

The installation design shall include construction design with architectural/engineering and electrical drawings submitted to the MDAD’s Project Manager for review and final approval. It shall consist of both the New DAS headend and downstream equipment. Any architectural and engineering drawings shall be submitted to the MDAD’s Project Manager at the following intervals as part of the overall design and construction process:

a. 60% progress/review set

b. 90% progress/review set.

c. Addenda and corrections (as necessary during construction).

The Successful Proposer/Operator shall submit 100% construction set drawings, stamped by a State of Florida licensed PE, to MDAD’s Project Manager. These drawings must be approved before obtaining necessary permits and beginning installation.

The drawings shall include power, HVAC, fire suppression, and structural details for the headend and downstream equipment.

The installation design shall be based on the RF design. Both the RF and installation design shall be approved by MDAD’s Project Manager after approval by each WSP. The Successful Proposer/Operator will obtain necessary approvals from MDAD’s Project Manager for the aesthetics relative to antennas, ensuring compliance with MDAD’s architectural standards

3.8 The RF Design, Installation Design, and necessary permitting required by the Successful Proposer/Operator shall be completed within six (6) months of the Contract Effective Date to ensure sufficient time for system implementation.

3.9 The RF design shall show the predicted RF coverage in the desired area for the said metrics in the form of heatmap coverage plots showing various levels of signal strength and quality metrics, as applicable, overlaid on the floor plan for each frequency band. Bleed out will be included in the delivered plots.

3.10 The design shall also indicate the uplink and downlink RF Link Budget from end to end for each zone or coverage area, compliant with 3GPP standards

3.11 The New DAS design shall incorporate current industry technology trends and, where possible, consolidate both the New DAS headend equipment and the WSP equipment footprint. The Successful Proposer/Operator is encouraged to consider design approaches such as digital baseband headend connection to DAS, end-to-end digital design, or Open RAN (ORAN), etc., if feasible, to minimize or eliminate the need for traditional WSP base station equipment and downstream New DAS infrastructure, which poses significant space, HVAC, power, and fiber capacity demands.

3.12 Installation design shall include the fiber required to support the final system design for all WSPs; this will include the backhaul fiber between the New DAS headend room, terminal IT core rooms, and between core rooms and downstream IDF/TRR/IT (Intermediate Distribution Frame/Test Readiness Review Telecommunications Room/Information Technology) rooms. The fiber design shall specify single-mode fiber with at least 25% excess capacity (e.g., 12 unused fibers per location) and SC-UPC connectors, compliant with TIA-568 standards.

3.13 MDAD does not guarantee that the Existing DAS fiber will be sufficient for the New DAS scope of work herein. Additionally, MDAD makes no assurances or guarantees on the performance and the state of the existing DAS available fiber. If any existing fiber fails, it will be replaced or repaired at the sole cost of the Successful Proposer/Operator. It is the Successful Proposer/Operator’s responsibility to procure and install any additional fiber necessary to meet all requirements in the Scope of Work. The ownership of any fiber or coaxial cable installed by the Successful Proposer/Operator shall transfer to MDAD after the Agreement expires. Additional fiber may be available at cost from the Airport via MIA Tenant Technology Services (“TTS”). The Successful Proposer/Operator is responsible for providing any fiber from the IDF/TRR/IT rooms to any edge (radio) devices in the field. All new fiber installations shall include test results (e.g., OTDR, power loss) submitted to MDAD in Excel format.

3.14 Utilize the industry-standard AutoCAD program to perform the system installation design, including all cable, fiber, and equipment layouts. Both preliminary and final installation designs shall be completed using the AutoCAD program, clearly depicting component names, routing paths, cable lengths, fiber runs, equipment placement, jumpers, etc., and other relevant components. Such information will be presented in separate layers on the AutoCAD drawings to ensure clarity and traceability. The MDAD Project Manager shall approve before installation. All AutoCAD documents shall also be submitted in PDF and native AutoCAD (.dwg) formats.

3.15 Be responsible for the storage of all purchased equipment and materials. The Successful Proposer/Operator shall also store equipment and materials during the daily installation phase, ensuring secure, climate-controlled storage compliant with manufacturer specifications.

3.16 Provide all necessary protection to safeguard any work from damaging its operation or the operations of others, including temporary barriers, signage, and coordination with MDAD to minimize disruptions to airport operations

3.17 Provide all the drawings, permits, and licenses necessary to implement the system, including the PEs stamped and any other PE-stamped drawings required for the design and installation of the system. Obtain written permission from MDAD’s Project Manager before proceeding with any work that requires cutting into or through any part of the building structures, such as, but not limited to, girders, beams, concrete, carpeted or tiled floors, roof partitions, or ceilings, anywhere the fireproofing or moisture proofing could be impaired, or any areas where the area surrounding the building where such actions could potentially impact the facility, supporting infrastructure or entrance facilities. The Successful Proposer/Operator shall be responsible for completing any necessary repairs to building structures, facilities, or surrounding areas affected by the New DAS installation, at no cost to MDAD.

3.18 Once the final installation design is approved, the Successful Proposer/Operator shall submit the New DAS equipment product cut sheets to MDAD’s Project Manager to provide familiarity with the installed solution, including manufacturer specifications, certifications, and environmental ratings.

3.19 Design, build, and furnish the New DAS headend room with power, HVAC, fire suppression, and any other improvements necessary to support the New DAS headend and WSP headend equipment. The Successful Proposer/Operator shall submit detailed engineering/electrical drawings for review and approval by MDAD’s Project Manager before commencing construction within the network headend room, compliant with NFPA and local building codes.

3.20 Provide any improvements, including but not limited to providing adequate power needed in IT rooms used for housing network equipment, ensuring compliance with TIA-942 standards for telecommunications infrastructure.

3.21 Once the final installation design is approved, the Successful Proposer/Operator will submit the New DAS equipment product cut sheets to the MDAD PM.

4. INSTALLATION

The Successful Proposer/Operator shall:

4.1 Complete all system implementation.

4.2 Begin installation only after approval of the Final RF Design and 100% Installation Design by MDAD’s Project Manager, with written confirmation provided.

4.3 Install fiber to meet the requirements in the Scope of Work and System Specifications contained herein, ensuring compliance with TIA-568 standards and MDAD’s preference for SC-UPC connectors.

4.4 Provide, install, terminate, and connect all required fiber, in addition to that provided by the Airport, to deliver a turnkey New DAS system that meets all requirements specified in the Scope of Work, including submission of fiber test results (e.g., OTDR, power loss) in Excel format as part of Project closeout documentation.

4.5 Ensure that all work performed under this Scope of Work is accomplished in accordance with the applicable standards included herein, including but not limited to TIA-568, TIA-942, 3GPP, FCC, NFPA, and local building codes.

4.6 Follow manufacturer’s installation guidelines and any additional guidelines specific to the system per any MDAD-provided specifications outlined in this RFP and related Exhibits 1 and 2.

4.7 Install all equipment and materials neatly and professionally, following accepted industry practices, by competent technicians, with certifications (e.g., BICSI, FOA) or equivalent, as approved by MDAD. The Successful Proposer/Operator shall submit technician certifications as part of the project documentation.

4.8 MDAD’s personnel will inspect sample installations to determine conformance to the Airport standards and requirements outlined in this RFP. Such approval shall be limited in scope to the specific equipment/subsystem’s physical structure and shall not be construed to imply any form of acceptance of a system or subsystem.

4.9 Place equipment/materials in approved locations only. Any deviation from these locations must be approved in writing by MDAD’s Project Manager, with a revised installation design submitted for review.

4.10 Ensure coaxial cable conforms to the product manufacturer’s installation guidelines. Special care shall be taken to avoid exceeding the specified bending radius during installation, with bend radii compliant with TIA-568-C.3 standards

4.11 Install network components, including all hardware, cables, connectors, etc., and related infrastructure, as required to comply with the manufacturer’s instructions, with recognized EIA/TIA (Electronic Industries Alliance/Telecommunications Industry Association) standards (e.g., TIA-568, TIA-942), and other relevant industry standards, including 3GPP and CTIA, and the final design drawings and specifications.

4.12 Cables shall be routed appropriately, supported, secured to MDAD-approved mounting surfaces, and labeled in accordance with TIA-606-C standards and MDAD’s existing labeling schema. No handwritten labeling is allowed. All assigned strands shall be marked accordingly in conjunction with the existing label schema, and their details provided to MDAD’s Aviation Technology Department in a cable management log. The Operator may install the final leg of coax connections from the radio/remote unit to the antenna in the ceiling without a conduit. Such connections shall not exceed 20-foot-long jumpers at any location. Such cable jumpers will still need to be supported by adequate means as permitted by Airport standards above the ceiling, using approved cable hangers or trays.

4.13 Perform tests for faults for Voltage Standing Wave Ratio (“VSWR”), continuity, shorts, reversals, and ground, where applicable, on completed RF coaxial cable sections before connecting to mainline equipment in IDF/TRR/IT rooms; this shall include a sweep test of all coaxial cable after the cable is installed. All coaxial cables installed shall pass tolerance limits based on the final RF design and link budget, with test results submitted to MDAD in Excel format.

4.14 Consolidate New DAS equipment installation in the Airport’s IT rooms within a rack or cabinet as much as possible to maximize the limited space available and remove all unused equipment. MDAD IT will assign space allocation for the New DAS equipment, and the successful Proposer/Operator should submit a detailed equipment layout to MDAD for approval before installation.

4.15 Perform all network fiber patching to retain the existing DAS fiber infrastructure warranty. All fiber splicing, if required, shall be performed by a Corning Optical Communications certified contractor to maintain warranty compliance. The Successful Proposer/Operator may utilize one of the Airport’s existing fiber installers authorized to work at the Airport, with certification documentation provided to MDAD.

4.16 Ensure no installation of any device or equipment with less than 24” clearance from conveyor carriers (belts, trays, etc.); this shall apply to all coaxial and other cables, conduits, antennas, remote units, radios, related components, etc.

4.17 Install coaxial cable and coax jumpers in a manner to keep their length to a minimum between the fixed equipment on both ends, while also ensuring the coaxial cable in the ceilings has sufficient ‘slack loop’ to allow for relocation of remote units/radios or antennas in the future around that location, with a minimum slack loop of 10 feet.

4.18 Where possible, install all remote New DAS components in consolidated clusters above ceilings to minimize spreading them around throughout the coverage area. Likewise, install all antennas in consolidated clusters while following RF interference requirements to minimize spreading them throughout the coverage area, ensuring compliance with the approved RF design.

4.19 The subcontractor may utilize current roof penetrations or punches upon written approval by MDAD’s Project Manager. If, for any reason, the existing roof penetrations cannot be used, then the contractor must provide these penetrations at their own expense. MDAD’s Project Manager must approve these penetrations in writing before any work commences on the Project.

4.20 Ensure it does not damage existing fiber, cable, or other equipment from any installation work performed directly by the Successful Proposer/Operator or by one of its contractors or subcontractors. When installing new fiber or cable in the Airport’s existing pathways or conduit, special care must be taken. The Successful Proposer/Operator shall be responsible for fixing, restoring, or remediating any issues or damage it causes to existing Airport, tenant systems, or infrastructure while performing work under the Agreement, at no cost to MDAD.

4.21 At the end of the Agreement, all installed components, systems, and software that are part of the Existing DAS, except WSP-owned equipment, shall become property of the Airport. Agreements with the WSPs shall be transferable to the Airport upon the termination of the Agreement between the Successful Proposer/Operator and the Airport.

4.22 Ensure all installation work complies with MDAD safety protocols, including but not limited to personal protective equipment (PPE) requirements, escorted access in secure areas, and coordination with MDAD to avoid disruptions to airport operations. The Successful Proposer/Operator shall submit a safety plan within 30 calendar days of the Contract Effective, detailing compliance measures and emergency procedures.

4.23 Provide as-built documentation within 30 calendar days of installation completion, including updated AutoCAD drawings (.dwg and PDF formats), cable management logs, test results, and equipment inventories, submitted to MDAD’s Project Manager for approval.

5. SYSTEM ACCEPTANCE

5.1 Acceptance of the system shall take place after:

5.1.1 Inspection and approval by the MDAD’s Project Manager of all installation work to verify that all work meets applicable building codes, ANSI/TIA/EIA telecommunication standards, and the MDAD Design Guide Manual

5.1.2 MDAD’s Project Manager’s approval of selected acceptance testing by the Successful Proposer/Operator once approved by each WSP, as defined in Section 5.2 herein. For the sake of clarity, the MDAD PM shall provide final approval for both the System Acceptance Test and the Coverage Acceptance Test noted below.

5.1.3 All test equipment will have a current/non-expired calibration sticker from a NIST-certified calibration lab. A spreadsheet of all equipment and calibration dates/expiration dates will accompany all test reports submitted to the MDAD PM.

5.2 Acceptance testing for the implemented system shall include the following:

5.2.1 System Acceptance Test (“SAT”) - This test aims to ensure that system specifications and technical requirements have been met. The test will verify system design, architecture, management, monitoring, and security features; confirm that the DAS hardware, software, and network integration meet the technical specifications and carrier requirements of the RFP; and ensure all system components (e.g., headend equipment, remote units, antennas, cabling) are installed, configured, and operational.

5.2.1.1 Test Scope:

a. Hardware Verification: Confirm all DAS components (e.g., base transceiver stations (BTS), remote units, antennas, fiber/coaxial cabling) are installed as per the approved design and vendor specifications.

b. WSP Integration: Verify connectivity and signal handoff with each WSP’s network (AT&T, Verizon, T-Mobile, etc.) via their respective BTS interfaces.

c. Network Interfaces: Test internal and external network interfaces, including backhaul connectivity (fiber/ethernet) to WSP networks.

d. Power and Backup Systems: Validate power supply, UPS, and battery backup functionality per design (e.g., minimum 4-hour backup for critical areas).

e. Alarms and Monitoring: Confirm remote monitoring systems (e.g., SNMP, NOC Integration) are operational and report faults correctly.

f. Regulatory Compliance: Ensure compliance with FCC, FAA, and local airport regulations for RF emissions and safety

5.2.1.2 Test Procedures:

a. Functional Testing: Conduct end-to-end tests to verify signal flow from carrier WSP BTS to New DAS antennas for each frequency band.

b. Power Level Testing: Measure transmit and receive power levels at each remote unit using spectrum analyzers to ensure they meet carrier-specific requirements (e.g., within +/-2 dB of design).

c. Signal Quality: Test for signal-to-noise ratio (“SNR”) and bit error rate (“BER”) to confirm compliance with each carrier’s standards.

d. Failover Testing: Simulate power or network failures to verify backup systems and redundancy.

e. Interference Check: Use spectrum analyzers to detect and mitigate interference from external sources or co-located systems.

5.2.1.3 Metrics for Pass/Fail:

a. All hardware components must be 100% operational.

b. Signal power levels must meet WSP specific thresholds (e.g., -85 dBm to -65 dBm for received signal strength RSS).

c. Backhaul latency <50 ms for 4G and < 30 ms for 5G.

d. No unresolved alarms.

e. Compliance with 3GPP and CTIA standards for cellular performance.

5.2.1.4 Reporting Requirements:

a. SAT Test Plan: Successful Proposer/Operator must submit a detailed test plan 30 calendar days before testing, outlining procedures, equipment, and WSP coordination.

b. Test Results Report: Provide a comprehensive report including:

i. Inventory of tested components (e.g., serial numbers, locations).

ii. RF power measurements for each antenna node and frequency band.

iii. SNR, BER, and latency measurements per WSP.

iv. Alarm logs and resolution status.

v. Certification of compliance with WSP and regulatory standards.

c. As-Built Documentation: Updated system diagrams, cable routes, and equipment configurations.

d. WSP Sign off: Written approval from each WSP confirming successful integration, performance compliance, and completion of all required acceptance activities, as outlined in Exhibit 1 - WSP Written Approval and Acceptance Process.

5.2.1.5 The SAT shall include identifying expected signal levels (RF and optical) at each active and passive component and defining allowed variation from expected levels. Performance of the SAT shall consist of documentation of actual signal strength measurements and identifying variance from predicted levels, as shown in the design.

5.2.1.6 The Successful Proposer/Operator shall test all cables using appropriate cable testing devices. Where applicable, coaxial cables shall be tested for VSWR, continuity, shorts, reversals, and grounds, including a sweep test of all coaxial cables after the cable is installed. All fiber shall be tested from end to end for total loss and optical link budget.

5.2.2 Coverage Acceptance Test (“CAT”) – The CAT ensures that the New DAS provides adequate cellular coverage and that capacity throughout the designated coverage areas for all WSPs are successful. The CAT is focused on RF performance and user experience.

5.2.2.1 Objective:

a. Verify that the DAS delivers consistent, high-quality cellular coverage and capacity across all specified areas (e.g., terminals, concourses, parking garages, baggage claim). Ensure seamless connectivity for voice, text, and data services for all supported WSPs.

b. Test results will be submitted to the MDAD’s Project Manager for review and approval.

5.2.2.2 Test Scope:

a. Coverage Areas: Test all designated areas, including indoor (terminals, offices, restrooms) and outdoor (curbside, parking lots) spaces.

b. WSP Services: Validate performance for all WSP-specific services (2G, 3G, 4G LTE, 5G NR) across supported frequency bands.

c. Capacity Testing: Assess system performance under simulated high-traffic conditions (e.g., peak passenger loads).

d. Handoff Testing: Verify seamless handoffs between New DAS sectors and macro networks at coverage boundaries.

5.2.2.3 Test Procedures:

a. RF Grid Testing: Perform walk tests using RF measurement tools (e.g., iBwave, PCTel scanners) to map signal strength and quality across a grid of the facility (e.g., 10x10 meter grid).

b. Signal Strength Measurement: Measure Received Signal Strength Indicator (RSSI) and Reference Signal Received Power (RSRP) for each carrier and band.

c. Data Throughput Testing: Conduct download/upload speed tests under normal and peak load conditions using WSP-approved tools (e.g., Ookla Speedtest, iPerf).

d. Voice Quality Testing: Measure Mean Opinion Score (MOS) for voice calls (target MOS ≥ 4.0 for clear audio).

e. Capacity Stress Testing: Simulate high user density (e.g., 100 simultaneous users per sector) to confirm no degradation in performance.

f. Handoff Validation: Test mobility scenarios to ensure no dropped calls or data sessions at sector boundaries.

5.2.2.4 Metrics for Pass/Fail:

a. Coverage: Minimum 95% of tested areas must have RSRP ≥ -85 dBm for 4G LTE and ≥ -90 dBm for 5G NR.

b. Signal Quality: Signal-to-Interference-plus-Noise Ratio (“SINR”) ≥ 15 dB in 95% of tested areas.

c. Data Throughput: Minimum 10 Mbps download/5 Mbps upload for 4G; 50 Mbps download/10 Mbps upload for 5G in 95% of areas.

d. Voice Quality: MOS ≥ 4.0 in 95% of tested areas.

e. Handoff Success Rate: ≥ 99% success rate for handoffs between DAS sectors and macro network.

f. Capacity: No more than 5% degradation in throughput under peak load conditions.

5.2.2.5 Reporting Requirements:

a. CAT Test Plan: Submit a detailed plan 30 calendar days prior, including test locations, grid layout, and WSP-specific test parameters.

b. Coverage Maps: Provide heatmaps showing RSSI, RSRP, and SINR across all tested areas for each carrier and band.

c. Test Results Report includes:

i. Detailed measurements (RSSI, RSRP, SINR, throughput, MOS) per grid point.

ii. Pass/fail status for each test point and overall system.

iii. Documentation of any coverage gaps and proposed remediation plans.

d. WSP Validation: Obtain written confirmation from each WSP that coverage meets their standards.

e. Final Report: Summarize findings, including statistical analysis (e.g., percentage of areas meeting metrics) and any deviations from requirements.

5.2.2.6 Additional Testing Guidance:

a. Timeline: Require SAT completion within 30 calendar days of New DAS commissioning and CAT within 60 calendar days, with reports submitted within 7 calendar days of each test.

b. Remediation: If any test fails, the Successful Proposer/Operator must submit a corrective action plan within 5 calendar days and retest within 14 calendar days at no additional cost.

5.2.3 Endurance Test – The objective of the test is to verify that the New DAS operates reliably and maintains performance under the final WSP configuration and capacity loads for 30 consecutive calendar days without significant issues, ensuring readiness for final acceptance by the MDAD Project Manager.

5.2.3.1 Test Scope:

a. The Endurance Test shall commence after successful completion of the System Acceptance Test (SAT) and Coverage Acceptance Test (CAT).

b. The test shall operate the DAS in its final configuration, including all WSPs (e.g., AT&T, Verizon, T-Mobile) and their respective frequency bands (e.g., 700 MHz, AWS, PCS, 5G NR).

c. The New DAS shall be tested under realistic capacity loads simulating peak airport traffic conditions (e.g., 100 simultaneous users per sector or as specified by WSPs).

d. Testing shall include all DAS components (e.g., headend, remote units, antennas, backhaul) and WSP network interfaces.

5.2.3.2 Test Procedures:

a. Continuous Operation: Operate the New DAS 24/7 for 30 consecutive calendar days with continuous monitoring via the Network Operations Center (NOC) or equivalent system.

b. Performance Monitoring: Measure key performance indicators (KPIs) daily, including signal strength (RSRP), signal quality (SINR), data throughput, voice quality (MOS), and system alarms.

c. Capacity Stress Testing: Conduct periodic stress tests (e.g., weekly) during the 30-day period to simulate peak passenger loads, ensuring no degradation in performance.

d. Handoff Validation: Monitor seamless handoffs between New DAS sectors and macro networks during normal operation.

e. Power and Backup Testing: Verify that power systems (e.g., UPS, battery backups) maintain operation during simulated outages.

5.2.3.3 Restart Conditions:

a. Service Outage: Defined as any unplanned interruption of cellular service for any WSP lasting more than 15 minutes in any coverage area, affecting voice, text, or data services.

b. Coverage Degradation: Measured RSRP falls below -85 dBm for 4G LTE or -90 dBm for 5G NR in more than 5% of designated coverage areas for over 1 hour.

c. Signal Quality Failure: SINR drops below 15 dB in more than 5% of coverage areas for over 1 hour.

d. Throughput Failure: Average data throughput falls below 10 Mbps download/5 Mbps upload for 4G or 50 Mbps download/10 Mbps upload for 5G in more than 5% of coverage areas for over 1 hour.

e. Voice Quality Failure: Mean Opinion Score (MOS) for voice calls drops below 4.0 in more than 5% of coverage areas for over 1 hour.

f. System Alarms: Any critical alarm (e.g., hardware failure, backhaul disconnection) that remains unresolved for more than 4 hours.

g. Handoff Failure: Handoff success rate between New DAS sectors or to macro networks falls below 99% for over 1 hour.

h. Power System Failure: Failure of UPS or battery backup to maintain system operation during a simulated power outage.

5.2.3.4 Remediation and Retesting:

a. If a significant problem occurs, the Successful Proposer/Operator shall:

i. Notify the MDAD Project Manager within 4 hours of detecting the issue, including a preliminary root cause analysis.

ii. Submit a detailed Failed Testing Report within 48 hours, including:

a. Description of the issue, affected areas, and duration.

b. Root cause analysis and proposed remediation plan.

c. Timeline for implementing corrections.

iii. Complete remediation within 7 calendar days (or as agreed with MDAD) and restart the 30-day Endurance Test after MDAD approval.

b. Retesting shall follow the same procedures and metrics as the initial test, with updated results submitted to the MDAD Project Manager.

5.2.3.5 Reporting Requirements:

a. Endurance Test Plan: The Successful Proposer/Operator shall submit a detailed test plan 30 calendar days before the start of testing, including:

i. Monitoring tools and methodologies (e.g., NOC software, RF scanners).

ii. Schedule for capacity stress tests.

iii. Coordination plan with WSPs for performance validation.

b. Daily Monitoring Logs: Submit daily KPI reports to the MDAD PM, including RSRP, SINR, throughput, MOS, and alarm status for each WSP.

c. Coverage Data: Provide CW and Live RF Carrier coverage test data as coverage plots with heatmaps, showing RSRP and SINR across all designated areas, updated weekly.

d. Successful Final Endurance Test Report: Submit a comprehensive report within 7 calendar days of test completion, including:

i. Summary of daily KPI measurements, with statistical analysis (e.g., percentage of time/area meeting metrics).

ii. Coverage heatmaps for each WSP and frequency band.

iii. Documentation of any minor issues and their resolutions.

iv. Certification of compliance with WSP and MDAD requirements.

v. Written confirmation from each WSP verifying performance during the test period.

e. All reports shall be submitted in electronic format (e.g., PDF) to the MDAD Project Manager, with hard copies available upon request.

5.2.3.6 WSP Coordination:

a. The Successful Proposer/Operator shall coordinate with all WSPs to incorporate their specific acceptance testing requirements into the Endurance Test scope.

b. Obtain written confirmation from each WSP that the New DAS meets their performance standards at the conclusion of the test.

6. COMMISSIONING

6.1 The New DAS shall be commissioned after successful acceptance as defined in Section 5 herein –completion and acceptance of System Acceptance Testing (SAT) and Coverage Acceptance Testing (CAT) as outlined in Section 5.

6.2 Commissioning will mark the entire system moving from an implementation and test phase to a production/operations phase where it will carry live traffic from WSPs and serve the Airport's passengers, employees, and other customers.

6.3 The Successful Proposer/Operator shall submit a Commissioning Plan for review and approval by MDAD’s Project Manager within 60 calendar days of the Contract’s Effective Date, that describes the following at a minimum, as outlined in Section 3.2 herein, including but not limited to:

6.3.1 Minimum requirements for each WSP to connect to the New DAS.

a. Specify technical requirements for connectivity, including signal strength (e.g., RSRP ≥ -85 dBm), frequency bands (e.g., 600 MHz, C-Band, mmWave), and interface protocols (e.g., CPRI, eCPRI).

b. List required hardware (e.g., baseband units, routers) and software configurations (e.g., firmware versions, network parameters) for WSP integration.

c. Ensure compliance with MDAD’s Telecom Design Guideline Manual (DGM) and industry standards (e.g., 3GPP, TIA-568).

d. Define testing protocols and performance benchmarks (e.g., SINR ≥ 15 dB, throughput ≥ 100 Mbps) for signal quality and system performance, with results submitted to MDAD in Excel format.

6.3.2 How each WSP will be onboarded and connected to the New DAS.

a. Provide a step-by-step onboarding process for each WSP, including equipment installation, backhaul integration, and configuration.

b. Clarify roles and responsibilities of the Successful Proposer/Operator and WSPs, with a RACI (Responsible, Accountable, Consulted, Informed) matrix included.

c. Include a timeline for each onboarding phase, aligned with the Project schedule, targeting completion within 12 months of Contract award.

d. Establish communication protocols for WSP coordination, including weekly status updates and escalation procedures.

e. Submit a checklist of required documentation (e.g., WSP approval emails, test results) and MDAD approvals for each WSP onboarding.

6.3.3 How the entire system will transition from installation to production and ongoing operations.

a. Define the transition phases (e.g., installation completion, testing, go-live, operations handover) and criteria for phase completion.

b. Detail the handover process…