FA466126Q0074 Dorm Wifi Questions and Answers.pdf

Questions Project: Dormitory Managed Wireless & Internet Services

Target Installation: Dyess AFB, TX

Category 1: Site Locations, Addresses, and Physical Infrastructure

Physical Addresses and Demarcation Points

1. Please provide the physical addresses for each of the 12 dormitory buildings, specifically identifying the main building containing the primary telecommunications demarcation point (demarc drop) for the ISP data circuit.

Government Answer:

The addresses for the 12 dormitory buildings are listed in Appendix 1 of the Statement of Work (SoW). The buildings are: 6112, 6113, 6114, 6125, 6126, 6127, 6136, 6137, 6138, 7219, 7220, and 7221.

Demarcation Point:

There are no documents on the demarcation point for the ISP data circuit.

Each building might be currently serviced individually rather than from a centralized point.

2. If no commercial carrier demarcation points currently exist in these buildings, please confirm that the contractor is responsible for coordinating and establishing the carrier connection from the service provider into the dormitory environment.

Government Answer:

Confirmed. The SoW requires the contractor to provide, deliver, and manage a comprehensive end-to-end solution.

Site Drawings, CAD Files, and Underground Pathway Documentation

Reference: SOW §§ 2.1, 3.1–3.5, 6.10.1

3. Please provide any available site drawings, utility maps, or as-built documentation showing existing direct-buried fiber, telecommunications cabling, underground conduits, handholes, maintenance holes, and building entrance facilities.

Government Answer:

Site drawings and building floor plans are part of the RFQ package, Attachment 4 (Dormitory Floorplans). The contractor is responsible for coordinating with Base Civil Engineers (CE) for digging permits and is responsible for any necessary environmental permits, as stated in SoW §§

6.10 and 6.10.1.

4. Can the Government share building floor plans with scale, dimensions, and square footage?

Government Answer:

Yes, DOD SAFE link is provided with detail drawing:

https://safe.apps.mil/pickup.php?claimID=EVgUqHFiiuRa3LYf&recipCode=mU4l4s

Passcode: 5YTDvQ0pVjpAYxM0

Valid for 5 days

5. Specifically, will CAD drawings be provided to enable precise predictive RF Wi-Fi design modeling?

Government Answer:

Yes, DOD SAFE link is provided with detail drawing:

https://safe.apps.mil/pickup.php?claimID=EVgUqHFiiuRa3LYf&recipCode=mU4l4s

Passcode: 5YTDvQ0pVjpAYxM0

Valid for 5 days.

6. Are the buildings currently interconnected via fiber? If so, are there any spare Government-owned fiber strands available for contractor use?

Government Answer:

No https://safe.apps.mil/pickup.php?claimID=EVgUqHFiiuRa3LYf&recipCode=mU4l4s https://safe.apps.mil/pickup.php?claimID=EVgUqHFiiuRa3LYf&recipCode=mU4l4s

7. If not to question 6, will the contractor be required to run new inter-building fiber-optic cable?

Government Answer:

If the contractor’s proposal requires that inter-building fiber be installed, the contractor will be responsible for completing this.

8. What are the physical distances between the 12 dormitory buildings?

Government Answer:

Distances vary between each building. Estimated range between a facility is ~75’ – 100’. Each northside trio of buildings are distanced ~500’ – 700’ apart.

The largest being the direct distance from the northside campus (bldg. 6125) to southside campus (bldg. 7219) ~2,500’.

Telecommunications Rooms (MDF/IDF) Inventory, Sharing, and Conditions

Reference: SOW §§ 2.4, 3.3–3.5

To ensure proper design of the switching and UPS plant, please provide an inventory of the existing telecommunications closets (MDFs/IDFs) for each of the 12 dormitory buildings, including:

9. Physical space (rack space, wall space, and grounding).

Government Answer:

There are no existing telecommunication closets (MDFs/IDFs)

10. Available electrical service, UPS capacity, and environmental controls (HVAC).

Government Answer:

Electrical and HVAC controls should be adequate for the project needs. There is no existing Government-provided Uninterruptible Power Supply (UPS).

11. Existing switch inventory, port densities, and current riser cabling diagrams (fiber type, strand counts, termination types).

Government Answer:

None available. The 7th Communications Squadron (7 CS) has stipulated that their existing active network switches, port inventories, and fiber optic riser cabling cannot be utilized for this commercial resident network.

12. Will the contractor's Dorm Internet Services network share physical IT/telecommunications rooms with other operational networks in these buildings?

Government Answer:

Yes. The contractor’s Dorm Internet Services network will share physical space within the facilities. All dormitory buildings feature an electrical/telecommunications room on each floor, with the first-floor room serving as the primary location for network and headend equipment. The second and third-floor electrical rooms are available as optional distribution areas should the contractor require physical separation or additional pathing.

Existing Environment & Infrastructure Context:

• Incumbent Providers: Currently, Boingo and Optimum service these dormitories. Boingo operates using its own proprietary, dedicated physical equipment and infrastructure footprint. Optimum operates by utilizing the facility's existing coaxial cabling.

• SOW Alignment (Section 1.1): As stated in SOW Section 1.1, the Government is seeking an end-to-end solution that leverages the existing, government-owned coaxial cable infrastructure to the greatest extent practicable.

13. Please confirm whether the contractor is permitted to install new racks, switches, fiber backbones, Category 6A cabling, and UPS units within these rooms as required by the proposed design.

Government Answer:

Confirmed, the contractor is permitted to install the necessary equipment in the electrical rooms. The contractor may make changes to facilities with CE approval.

14. If this space and inventory information is currently unavailable, please confirm that the contractor should determine all required infrastructure quantities as part of their proposed design.

Government Answer:

Confirmed

Coaxial Infrastructure Status, Coexistence, and Assumptions

Reference: SOW §§ 1.1, 2.1, 3.1–3.3

15. Please provide any existing coaxial topology, cable certification records, signal levels, faceplate counts, and distribution-hub locations.

Government Answer:

This information is not available. Per SoW § 3.2, offerors may propose to use the existing infrastructure "as-is" and are responsible for validating its suitability.

16. Is any of this coaxial infrastructure currently in use for active television or private internet services that must continue to operate concurrently with the new network?

Government Answer:

Yes. The government-owned coaxial cable infrastructure is currently in active use.

Active Service Context:

• Optimum currently utilizes this coaxial infrastructure to deliver private internet services to dormitory residents.

• Boingo also provides active services within the dormitories, but does so utilizing its own dedicated, proprietary equipment and infrastructure footprint rather than the government-owned coax.

17. Please confirm that coaxial reuse is an optional, stated objective rather than a mandatory architecture.

Government Answer:

Confirmed. The SoW (§ 1.1) seeks a solution that leverages existing coax "to the greatest extent practicable." SoW § 3.2 allows offerors to propose upgrading it or installing completely new infrastructure.

18. May an offeror propose a new Category 6A structured-cabling plant if coaxial validation fails, without being scored as non-compliant?

Yes

19. If detailed coax records are not available, please confirm that offerors may identify and list stated assumptions regarding the condition and layout of the coaxial infrastructure for pricing purposes, subject to post-award validation.

Government Answer:

Per SoW § 3.2, if an offeror's proposal includes using the existing GFP, the offeror is responsible for validating its suitability

20. If the coax fails suitability validation post-award, will replacement cabling, pathways, penetrations, and firestopping be handled as a differing-site-condition or compensable change?

Government Answer:

Per SoW § 3.2, if an offeror's proposal includes using the existing GFP, the offeror is responsible for validating its suitability

Category 2: Wireless RF Design and Performance Criteria

Access Point (AP) Density, Clustering, and Mounting Specifications

Reference: SOW §§ 1.1, 2.1, 2.5

21. Does the Government mandate a specific per-room AP deployment (e.g., one AP per room), or is the contractor free to engineer the optimal AP count and placement using predictive RF modeling to meet the performance floor?

Government Answer: The contractor is free to engineer the optimal solution to meet the requirements in the SoW.

22. Where a cluster of three dormitory buildings shares a common area, please confirm that if the predictive wireless design demonstrates that residents in all three dormitories can receive the required coverage, capacity, and performance from a single access point, this approach will be acceptable.

Government Answer: This approach is acceptable provided the contractor's solution meets the minimum requirements outlined in SoW § 2.1 for all rooms and common areas.

23. Are there specific mounting or hardware preferences for indoor APs (ceiling grid, hard ceiling, wall) and outdoor APs (wall, pole, roof, external vs. integrated antennas), or may the contractor propose the best technical solution based on site conditions?

Government Answer: The contractor may propose the best technical solution

RF Acceptance and Performance Evaluation Criteria

Reference: SOW §§ 1.1, 2.1, 2.5

24. Will the Government establish measurable wireless RF acceptance criteria (e.g., RSSI, signal-to-noise ratio, channel utilization, co-channel interference, roaming, latency, packet loss, and minimum sustained data rate under load) to evaluate proposals on engineered performance, rather than evaluating designs purely on device/AP counts?

Government Answer: The primary performance criteria are the speed requirements (100 Mbps/20 Mbps) detailed in SoW § 2.1. The contractor must conduct system-level performance tests to verify compliance (SoW § 2.5).

User Density, Devices, and Common Area Requirements

Reference: SOW §§ 1.1, 2.1, 2.2; Appendix 1; Attachment 4

25. Per-Room Bandwidth Clarification: The SOW requires a minimum service level of 100 Mbps download / 20 Mbps upload per individual room. Please confirm whether this means each room must simply be capable of achieving 100/20 Mbps when tested, or whether 100/20 Mbps of dedicated/simultaneously available bandwidth must be reserved for every room.

Government Answer:

The internet service capability shall meet or exceed a minimum service level of 100 Mbps download and 20 Mbps upload per individual room (SoW § 2.1).

26. Please provide the expected typical and maximum resident occupancy per room, as well as the expected number of simultaneous devices per resident or room.

Government Answer:

The project encompasses approximately 750 individual rooms. No more than one member per room. The number of devices is unknown.

27. Please identify the 36 common areas by building, floor, or designation, and clarify if any are shared or outdoors.

Common areas are located at the center of each floor in all facilities.

28. For common areas supporting a minimum of 10 simultaneous users, is the 100/20 Mbps performance floor required per user, or is the requirement that all 10 users maintain usable, un-degraded connectivity collectively?

Government Answer:

The service must support simultaneous connectivity for a minimum of 10 users per area without service degradation (SoW § 2.1). The 100/20 Mbps requirement is specified for individual rooms

Category 3: Network Architecture and Hardware Configuration

Core Architecture: Enterprise WLAN vs. Legacy Coax

Reference: SOW §§ 1.1, 2.1

29. Is the Government’s intent a single, centrally managed and secured enterprise wireless service (unified policy, identity, filtering, and bandwidth control across all facilities) or a distributed, per-room gateway/modem model delivered over the legacy coax plant?

Government Answer:

The SoW seeks a "comprehensive solution" (SoW § 2.1). The contractor is responsible for proposing the architecture.

Wired Ethernet Ports and Media Conversion

Reference: SOW §§ 2.1, 3.1-3.5

30. Is there any requirement for physical wired Ethernet ports within the dormitory rooms or buildings?

Government Answer:

No, this is not a stated requirement.

31. Will the Government confirm it does not intend to require per-endpoint media conversion (e.g., coax-to-Ethernet, MoCA, or DOCSIS), which would place unmanaged devices outside the centralized security, management, and PoE boundary?

Government Answer:

The Government does not specify the method of delivery, only the performance requirements.

Equipment Brand Preference (OEM)

32. Do you have any desirable brand (OEM) or brand preferences (e.g., Cisco, Aruba, Ruckus) for the network, security, and wireless equipment to be deployed?

No.

Network Management Architecture (Cloud vs. On-Premises)

33. Please confirm whether the Government has a preference or requirement for a cloud-managed versus on-premises network management architecture.

Government Answer:

The Government has no stated preference

34. If on-premises network management/controller solutions are proposed, where should the centralized management equipment be physically located? Should it be located within one of the 12 dormitory buildings, or will the Government provide space/connectivity in a separate central facility? If so, please identify the location and network connectivity.

Government Answer:

There is no pre-designated on-premises location for centralized management equipment. Use of the available space in the electrical room is permitted.

Firewall and WAN Capacity Sizing

35. Is there a Government-required minimum firewall/security gateway throughput with all security, UTM, and content-filtering services enabled, or should the contractor size this equipment based on proposed Internet capacity?

The contractor should size the equipment based on the proposed design to meet all performance requirements.

36. Please identify the required aggregate Internet/WAN capacity for each building and/or the overall 12-building campus.

Government Answer:

The contractor is responsible for engineering the solution to meet the per-room and common area requirements outlined in the SoW.

37. If no aggregate bandwidth requirement has been established, please confirm that the contractor is responsible for engineering the oversubscription/concurrency model.

SSID Strategy and Resident Identity/Authentication (AAA)

Reference: SOW §§ 2.1, 2.2

38. Is the Government seeking one SSID with per-user identity and policy enforcement, or multiple/per-room SSIDs (which degrade wireless airtime and performance)?

Government Answer:

The Government prefers a single, unified SSID

39. Please confirm that a minimal-SSID, identity-driven design is acceptable and preferred.

Government Answer:

Confirmed. A minimal-SSID design utilizing a centralized captive portal for terms of service acceptance is highly acceptable to reduce RF overhead. The contractor is free to propose this architecture.

40. Please confirm if a common resident SSID and captive portal/AUP process may be used across affected dormitories without requiring a separate SSID or access point for each building.

41. Is individual resident identity and authentication (AAA)—including credential lifecycles and deprovisioning—a mandatory requirement?

Government Answer:

No, it is not a mandatory requirement. The contractor is not required to manage individual user accounts, credential lifecycles, or deprovisioning

IP Addressing Architecture

Reference: Technical Capability Instructions; SOW §§ 2.1, 2.2

42. The solicitation mentions a "Dedicated IP address management approach."

Please identify whether dedicated or static public IP addresses are required per room/building, or if a centralized, pooled NAT addressing architecture at the security edge is acceptable.

A centralized, pooled NAT architecture is acceptable.

Headless and IoT Device Onboarding

Reference: SOW § 2.2

43. How should headless or non-browser devices (e.g., gaming consoles, smart TVs, streaming media players, printers, thermostats, and IoT devices) that cannot complete captive-portal authentication be onboarded and associated with a resident?

Government Answer:

The contractor should include their proposed method in their solution.

44. Is a MAC-address device registration or captive-portal exception method acceptable, and is there a limit on the number of registered devices permitted per resident?

Yes, that is an acceptable method. Device number limit can be proposed to ensure the system can meet bandwidth requirements. It would be expected that a reasonable amount of devices per resident would be permitted, maybe 5, before limiting the number of devices.

Category 4: Paid vs. Free Service Tiers & Coexistence

Paid Subscription Service Requirements

Reference: SOW §§ 1.1, 2.1, 2.2

45. Is the contractor required to offer a paid subscription option in addition to the Government-funded basic service (100/20 Mbps)?

Government Answer:

No. The contractor is not required to offer a paid subscription option. Service members must retain the ability to elect to pay the full cost of internet service access of their choice. This ability must not be infringed.

46. If required, what additional capabilities are expected (e.g., higher speeds, extra devices, gaming optimization, dedicated public IPs, or relaxed content filtering)?

Please provide any required paid service tier performance levels.

Government Answer:

No, it is not a requirement. However, if an offeror proposes the capability for residents to opt-in to paid tier upgrades (e.g., faster speeds), the Government will permit it. The core requirement remains that every resident must receive the baseline 100/20 Mbps filtered service free-of-charge regardless of whether they purchase upgrades. Relaxed content filtering or bypassing the security baseline is not permitted on upgraded tiers.

47. Is the contractor responsible for establishing subscription pricing and directly billing/collecting payments from residents?

Government Answer:

Yes. If the contractor chooses to offer upgrade tiers, they assume 100% responsibility for establishing terms of service, processing payments, billing, and resolving any financial disputes directly with the residents. The Government will not participate in or arbitrate resident billing.

Integration with Existing Services & Infrastructure Sharing

Reference: SOW §§ 2.1, 2.2

48. During the site visit, it was indicated that an existing paid subscription service might remain in place. Please confirm whether the contractor must coexist with the incumbent provider or completely replace them.

Government Answer:

The contractor's network will coexist with any incumbent providers currently operating in the facilities. The Government is providing a free, optional baseline service to residents. The Government will not mandate the removal of existing commercial utility infrastructure, nor will it restrict residents from choosing to purchase private internet services from other on-base providers

49. If there is an existing contract in place for these buildings, could the Government share the network contract name and contract number?

Government Answer:

Existing providers operate under separate utility franchise agreements, right-of-way grants, or AAFES concession contracts. These agreement details are proprietary and are not part of this solicitation.

50. If coexisting with an incumbent, please clarify the demarcation of responsibility between the contractor and the incumbent for ISP circuits, APs, switching infrastructure, authentication, security, billing, and help-desk support.

Government Answer:

The contractor is 100% responsible for their own end-to-end service stack

51. Will the free and paid services utilize the same contractor-provided network infrastructure (segmented logically via separate SSIDs, VLANs, and VRFs), or must they operate on physically separate networks?

Government Answer:

Either approach is acceptable, provided the Government service is strictly protected. The contractor may deliver an upgraded paid service using logical segmentation (separate VLANs/VRFs) on the same physical hardware, OR they may deploy a completely separate physical network stack. Whichever method is chosen, the Government-paid basic service (100/20 Mbps) must remain fully operational and uninterrupted at all times.

Category 5: Cybersecurity, Compliance, and Data Management

Authority to Operate (ATO) and Security Framework

Reference: SOW §§ 4.1–4.3; Combined Synopsis/Solicitation

52. The SOW states the contractor must obtain a formal ATO. Because this system provides resident personal internet access isolated from operational networks, please confirm that a formal ATO is required, and identify the authorizing organization, security framework (e.g., NIST SP 800-37/800-53, CSF, or CMMC level), system categorization, and control baseline.

Government Answer:

The requirement to obtain a formal ATO was rescinded and is no longer a requirement.

53. Must the ATO process be completed entirely within the 120-calendar-day implementation window?

Government Answer:

Not applicable. The ATO requirement has been rescinded.

54. If the service is fully isolated from the base enterprise network (NIPRNet/SIPRNet) and processes no FCI or CUI, will an approved System Security Plan (SSP) and security review satisfy the requirement in lieu of a formal ATO?

Government Answer:

Not applicable. The ATO requirement has been rescinded.

55. Will the Government evaluate an integrated secure-networking architecture (unified firewall/IPS, switching, wireless, and network access control) as a technical discriminator, given that a single consistent security fabric provides one coherent SSP and body of evidence for DFARS 252.204-7012 / NIST 800- 171?

Government Answer:

Yes. While a military ATO is not required, proposals showing a highly secure commercial architecture (such as integrated firewalls to protect residents from external cyber threats) will still be evaluated favorably under the technical evaluation criteria.

Content Filtering Policies

Reference: SOW §§ 2.2, 4.1, 4.2

56. Please identify the specific Federal, DoD, or Air Force content-filtering categories and policies that the contractor must enforce.

Government Answer:

The contractor is required to enforce standard commercial-grade content filtering to block malicious categories (phishing, malware, botnets), illegal acts, and adult/pornographic material.

57. Is standard DNS/category-based filtering sufficient, or does the Government require deep packet SSL decryption/inspection?

Government Answer:

Standard DNS/category-based filtering is completely sufficient.

58. Will Government personnel require administrative access to modify filtering categories or exceptions during the contract period?

Government Answer:

No. The contractor will maintain full administrative control of their filtering engine.

Data Retention and Privacy Requirements

Reference: SOW §§ 4.1, 4.2

59. Please identify what resident or network metadata the contractor is required to collect, retain, and report (e.g., captive-portal acceptance logs, device MACs, IP assignments, connection logs, or security events), along with the required retention periods and reporting frequencies.

Government Answer:

The contractor must collect and securely retain DHCP lease logs, NAT translation tables, and captive portal acceptance timestamps paired with device MAC addresses for a rolling window of 90 days. These logs are required solely to comply with potential law enforcement or subpoena requests and will only be reported or handed over upon formal legal demand.

Compliance Standards (TAA & Section 889) and Existing Infrastructure

Reference: SOW § 4.1; Attachment 6

60. Please confirm that all proposed network infrastructure components (switches, APs, firewalls, gateways, transceivers, and media converters) must be fully Trade Agreements Act (TAA) compliant and Section 889 compliant.

Government Answer:

Confirmed. All active physical infrastructure, devices, firmware, and software utilized in the execution of this contract must be 100% TAA compliant and strictly adhere to Section 889 of the FY19 NDAA (prohibiting the use of covered Chinese telecommunications equipment).

61. Do you have any government Wi-Fi networks currently existing in the same buildings that are not part of this solicitation?

Government Answer:

Yes. Official military enterprise wireless networks (e.g., NIPRNet) managed by the 7th Communications Squadron (7 CS) may be present in administrative offices or common spaces within these buildings. These are physically and logically isolated from the scope of this project.

Category 6: Operations, Maintenance, and Logistics

Managed Service Boundary and Support SLAs

Reference: SOW §§ 2.6–2.8; Combined Synopsis/Solicitation

62. Is contractor support limited to the network infrastructure and internet delivery, or must it include troubleshooting resident-owned personal devices?

Government Answer:

Support is strictly limited to the contractor-provided network, backhaul circuit, and captive portal onboarding. The contractor is not responsible for troubleshooting hardware, operating systems, or driver issues on personal devices, other than verifying network signal delivery.

63. What are the specific criteria that trigger an on-site technician dispatch (truck roll) versus remote remediation?

Government Answer:

A physical dispatch is triggered at the contractor's discretion when remote troubleshooting cannot resolve an incident, or when physical hardware failure (such as a dead Access Point or switch) is verified

64. Is there a required on-site physical response time SLA, separate from the 2-hour initial response and 18-hour restoration targets?

Government Answer:

No. There is no separate physical response SLA. The contractor is free to determine when to dispatch technicians, provided they meet the overall 18-hour service restoration SLA

65. Does the requirement to respond during base alerts and exercises require on-site contractor presence if the network is operating normally?

Government Answer:

No. Normal remote monitoring and help-desk availability are sufficient during base alerts and exercises. An physical presence is only required if an active system outage occurs during those periods.

66. Will the Government require read-only access to the contractor's network monitoring dashboard or ticketing system?

Government Answer:

Yes. The contractor must provide a designated representative with read-only access to a web-based dashboard showing live network up/down status and open support tickets.

67. Please clarify if the service must remain operational following the failure of a single Internet circuit, carrier path, network device, or power source (redundancy requirements), and identify any required monthly or annual service-availability target.

Physical dual-circuit path redundancy is not a mandatory requirement, but the overall architecture must support a 99.9% annual availability target.

Hardware redundancy at the core/distribution layer is highly encouraged to meet the 18-hour restoration target.

Access to Occupied Rooms

Reference: SOW §§ 2.4, 3.3, 6.7

68. Please confirm if the dormitories will remain occupied during installation, and clarify the Government's protocol and notice requirements for coordinating contractor access to individual resident rooms for installation, testing, and validation.

Government Answer:

Confirmed. Dormitories will remain fully occupied. The Government requires a minimum of 48 hours' advance notice to coordinate access. All contractor technicians working inside occupied resident rooms must be physically escorted.

Liability and Maintenance Boundaries

Reference: SOW §§ 2.6.3, 3.1, 3.2

69. The SOW states the contractor is liable for third-party charges to isolate and repair problems. Please clarify that the contractor is only financially responsible for remediating issues occurring within the contractor-maintained systems, and is not financially liable for system damage or repairs caused by outside forces (e.g., building water leaks or facility structural failures).

Government Answer:

Confirmed. The contractor is only financially liable for issues within their own logical and physical network scope of work. The contractor is not responsible for outages or damages caused by base-wide power failures, physical facility damage (such as water leaks), or structural incidents.

Demobilization and Asset Disposition

Reference: SOW §§ 2.4, 3.2, 3.3

70. The SOW states contractor-provided equipment must be removed at contract termination. Please clarify the ownership and disposition of permanent passive infrastructure installed during the contract (e.g., fiber, copper cabling, conduits, patch panels, racks, and wall plates). Which elements must be removed, and which will remain as Government property?

Government Answer:

All passive cabling, conduit, patch panels, and racks permanently installed in wall cavities or ceilings during this project become the property of the Government upon installation and shall not be removed. Active hardware (APs, switches, firewalls) remains contractor property and must be decommissioned at contract termination.

Category 7: Administrative, Timeline, and Pricing Instructions

Base Location Discrepancy

Reference: SOW § 1.1; Attachment 2 (Price Schedule)

71. The pricing spreadsheet references "Dorm Internet Services at Whiteman AFB, MO" in cells A1, A10, A24, and A30, whereas the solicitation and SOW designate Dyess AFB, TX. Please confirm that these are typographical errors and that Dyess AFB is the sole location for this requirement.

Government Answer:

Confirmed. This is a typographical error on the price schedule. The requirement is exclusively for Dyess AFB, TX.

72. Is there an ISP company that is preferred for data Internet services for Dyess AFB, or at least one with an existing presence on the installation?

Government Answer:

No specific Internet Service Provider (ISP) is preferred or mandated by the Government for this effort. Offerors are free to partner with any carrier or provider that can meet the performance, bandwidth, and SLA requirements detailed in the Statement of Work (SoW).

Existing Installation Presence: For situational awareness and coordination purposes, the Government discloses that Boingo and Optimum currently have an active service presence within the Dyess AFB dormitory facilities.

Base Year Performance Dates and Implementation Timeline

Reference: Combined Synopsis/Solicitation; SOW §§ 1.2, 2.7; Attachment 2

73. The solicitation lists the Base Year performance period as September 15, 2026 – September 14, 2027, but the Price Schedule (Attachment 2) lists it as September 1, 2026 – August 31, 2027. Please confirm the correct performance dates.

Government Answer:

The new Price Schedule document will reflect the period of performance start date being 15 Sept 2026 – 14 September 2027

74. Please clarify whether the 120-calendar-day implementation period begins upon Contract Award or upon the issuance of a formal Notice to Proceed (NTP).

Government Answer:

The 120 calendar period upon the issuance of a signed contract award.

75. Will the Government permit phased billing/recurring service charges to begin per building as they are individually accepted, or must billing wait until all 12 buildings are accepted?

Government Answer:

Phased billing would be acceptable. The contractor may commence monthly recurring service charges for an individual building once that specific facility has been completed, tested, and formally signed off by the Government.

Pricing Sheet Clarifications and Cost Allocation

Reference: Attachment 2 (Price Schedule); Combined Synopsis/Solicitation

76. CLIN Mapping Typo: The "Base Year" tab note states that "CLIN 0007 equipment installation will only occur on the Base Year," but CLIN 0007 is labeled as monthly service for Building 6136, while CLIN 0013 appears to be the installation CLIN. Please clarify if this is a typographical error.

This discrepancy was an administrative oversight. The forthcoming revised Price Schedule will be amended to include the clarifying provision: 'CLIN 0013 equipment installation is restricted solely to the Base Year.'

77. 6-Month Extension Typo: The total cell on the "6 Month Extension" tab is labeled "Total Option Year 4 Price." Please confirm this is a typographical error.

Government Answer:

That discrepancy was a clerical oversight and will be fully rectified in the forthcoming revised Price Schedule.

78. One-Time vs. Shared Cost Allocations: Please identify where offerors should price shared, one-time project costs (e.g., carrier construction, permitting, and centralized firewalls/licensing) within the building-specific CLIN structure.

Government Answer:

The Government does not have a dedicated, centralized "one-time setup" or "transition" CLIN for shared project initiation costs. Therefore, offerors must price and amortize all shared, one-time project costs (including, but not limited to, carrier construction, permitting, centralized firewalls, and central licensing) using one of the following two compliant methodologies:

Cost will be captured in CLIN 0013.

79. Please confirm that the separate monthly service CLINs for each dormitory building do not require a separate physical Internet circuit or complete network service stack for each building.

Government Answer:

Confirmed. The separate monthly service CLINs established for each dormitory building do not require, nor do they dictate, a separate physical Internet circuit or an independent, complete network service stack for each individual building.

In accordance with Statement of Work (SoW) Section 1.1 and Section 2.1, the Government's objective is to obtain a reliable, high-performing, and cost-effective end-to-end service while leveraging existing infrastructure to the greatest extent practicable. Offerors are fully authorized—and encouraged— to propose an efficient, centralized architecture (e.g., a primary high-capacity internet circuit feeding a central headend/distribution node that distributes connectivity to all 12 buildings).

The separate monthly service CLINs for each dormitory building are structured solely for administrative, location-based cost tracking, and monthly billing purposes. Regardless of the physical network design proposed, the contractor must guarantee that the specified bandwidth, performance metrics, and Service Level Agreements (SLAs) are met uniformly across all rooms and common areas in all 12 buildings.

80. May shared recurring costs (circuits, management platforms, help desk) be distributed across the building-specific monthly service CLINs at the offeror's discretion?

Government Answer:

Yes. Shared recurring costs (including circuits, management platforms, and help desk support) may be distributed across the building-specific monthly service CLINs at the offeror's discretion.

81. How many units, front doors, are in each building?

Government Answer:

Bldg 6112 – 64 rooms (external entry, individual rooms), 3 common areas Bldg 6113 – 74 rooms (external entry, individual rooms), 3 common areas Bldg 6114 – 74 rooms (external entry, individual rooms), 3 common areas Bldg 6125 – 64 rooms (external entry, individual rooms), 3 common areas Bldg 6126 – 57 rooms (Quad style, 2/3/4 rooms with kitchenette), 3 common areas Bldg 6127 – 57 rooms (Quad style, 2/3/4 rooms with kitchenette), 3 common areas Bldg 6136 – 52 rooms (Quad style, 2/3/4 rooms with kitchenette), 3 common areas Bldg 6137 – 52 rooms (Quad style, 2/3/4 rooms with kitchenette), 3 common areas Bldg 6138 – 64 rooms (external entry, individual rooms), 3 common areas Bldg 7219 – 64 rooms (external entry, individual rooms), 3 common areas Bldg 7220 – 64 rooms (external entry, individual rooms), 3 common areas Bldg 7221 – 64 rooms (external entry, individual rooms), 3 common areas