GovChime
Notice ID: f381e1a14e4640b09f2374bd9b4cbab0Solicitation

Moody, AFB Base Telecommunications Systems

Archived on June 15, 2024. Original response deadline: . Full description on SAM.gov.

Overview

Response deadline
1:00 PM UTC−04:00
Posted
May 15, 2024
Notice type
Solicitation
Set-aside
Small Business Set Aside - Total
NAICS
541513: Computer Facilities Management Services
Agency
Department of WarDepartment of the Air Force

Notice details

Office
FA4830 23 CONS CC
Place of performance
Moody AFB, 31699
Last updated
Sep 25, 2026

Identifiers

Solicitation number
FA483024R0004
Notice ID
f381e1a14e4640b09f2374bd9b4cbab0

Description

Amendment 0004 of FA483024R0004 - (15 May 2024) BASE TELECOMMUNICATIONS SYSTEM (BTS) SERVICES CONTRACT, will include the following changes: 1. Revised Solicitation SF1449 to extend the proposal due to 31 May 2024 1:00 PM est. *This is the final amendment to extend the proposal deadline. And as a reminder, please acknowledge all amendments by signing the SF 1449.* ---------------------------------------------------------------------------------------------------------------- Amendment 0003 of FA483024R0004 - (03 May 2024) BASE TELECOMMUNICATIONS SYSTEM (BTS) SERVICES CONTRACT, will include the following changes: 1. Revised Solicitation SF1449 to extend the proposal due to 16 May 2024 1:00 PM est. ---------------------------------------------------------------------------------------------------------------- Amendment 0002 of FA483024R0004 - (30 April 2024) BASE TELECOMMUNICATIONS SYSTEM (BTS) SERVICES CONTRACT, will include the following changes: Addition of Revised Attachment 1 Performance Work Statement 29 April 2024 Addition of Revised Attachment 7 PP Information Addition of Attachment 9 Workload Estimates Addition of Attachment 10 Q - A Addition of Attachment 11 Wage Determination (Construction) Technical Volume Limitation increased to 85 pages; Technical Subfactor 3: Candidate Qualification Documentation page limitation increased to 35 pages (*Changes will be highlighted in yellow*) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Amendment 0001 of FA483024R0004 - (29 April 2024) BASE TELECOMMUNICATIONS SYSTEM (BTS) SERVICES CONTRACT, will include the following changes: - Revised Questions and Answers date: 1. Answers for questions submitted by Offerors will be posted on 30 April 2024 at 4:00 PM, EST - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This solicitation is issued by the 23rd Contracting Squadron for a non-personal services necessary to ensure that Telecommunication Services are performed at Moody Air Force Base in a manner that will ensure the Base Telecommunications System is available 24-hours per day, 7-days per week. The BTS consists of the outside plant (OSP), inside plant (ISP), voice services and the supporting network infrastructure to install, configure and maintain equipment described in this PWS. The Contractor shall operate and maintain all BTS equipment and systems in accordance with (IAW) the Original Equipment Manufacturers' (OEM) technical manuals and specifications, Department of Defense (DoD), and United States Air Force (AF) policies and regulations, as well as all applicable federal, state, and local laws and regulations. This will be a 100% Small Business Set-aside procurement limited to qualified/eligible firms in the Small Business Development Program. The applicable North American Industry Classification System (NAICS) code for this acquisition is 541513 (Service) with a small business size standard of $37 Million. The Federal Supply Classification code is DG01 and the Government intends to award one contract under this program. Period of Performance and Magnitude: Performance is to begin 01 Oct 2024 with a twelve (12) month base and four (4) twelve (12) month options. All work shall be in strict compliance with the specification of the contract and the Performance Work Statement. The Government intends to conduct a site visit for this proposal. The exact date of the site visit will be identified in the solicitation. PAPER COPIES OF THIS SOLICITATION WILL NOT BE AVAILABLE. All prospective offerors are responsible for visiting SAM.gov web page frequently and obtain the solicitation, any amendments, and/or other information pertaining to this solicitation. No telephone calls or written requests for this solicitation package will be accepted. Any prospective contractor must be registered in the SAM.gov database to be eligible for award. Registration requires applicants to have a Unique Entity ID (UEI) from SAM.gov. Registration may take up to several weeks to process. Recommend registering immediately to be eligible for timely award. All prospective offerors must go to http://www.sam.gov/ to add or update its Representations and Certifications record.

Full description on SAM.gov

Award Overview

No prior contract identified

No prior award matched this notice's agency, NAICS, place of performance and PSC within 18 months. It may be a new requirement.

Contacts

Contracting Officer

Primary Contact

Secondary Contact

Documents

No documents available.

Lifecycle

Solicitation:FA483024R0004
  1. Solicitation

Award typically follows within 30–90 days after the response deadline. (estimate)

  1. 6×
    SolicitationCurrentApr 10, 2024

    Moody, AFB Base Telecommunications Systems

    Notice f381e1a14e4640b09f2374bd9b4cbab0 on SAM.gov

Similar Opportunities

Title
Match
Phase
Deadline
***EDIT*** RFI questions and responses provided as an attachment. The Government is conducting market research to identify capable small-business sources with the expertise, capabilities, and relevant experience to provide technical manual development and revision, technical data management, configuration management support, engineering support services, and AC-130J-only provisioning support for Special Operations Forces (SOF) C-130 aircraft (AC, MC, and HC). AC-130J provisioning support includes; identification and recommendation of spare, repairable, and consumable material requirements; and support for provisioning conferences and Government-approved Source, Maintenance, and Recoverability (SMR) code recommendations. The Government is considering an acquisition strategy consisting of a five-year technical data contract, including one 12-month base period and four 12-month option periods. The contractor would provide technical writing and technical data development support for incorporation into subsequent Technical Order (TO) revisions and updates. The contractor would provide configuration management support, including the policies, procedures, techniques, and tools necessary to: • Evaluate proposed changes; • Maintain configuration status accounting; • Track and document changes; and • Incorporate approved changes into TOs in accordance with applicable requirements. The contractor would provide engineering services, as required, to review, compile, and develop authorized source data into technical data suitable for Government review and approval. The contractor would provide AC-130J-only provisioning support to identify and recommend spare, repairable, and consumable material requirements necessary to support system operation and sustainment; recommendation of SMR codes for Government approval, and participation in AC-130J provisioning and configuration guidance conferences. The contractor would furnish all material, support equipment, tools, and services necessary to perform the required technical data development, technical manual revision, configuration management, and engineering support services, except for items expressly identified as Government-furnished. The contractor would be responsible for providing, utilizing and maintaining, all support equipment and/or software required at their facility or a subcontractor’s facility. The Government currently possesses a specification-control drawing for certain components within the anticipated requirement. The drawing is not a manufacturing (“build-to”) drawing. Lockheed Martin possesses the complete technical data package for the applicable part(s), and the Government does not currently have authority to release, purchase, or provide access to the complete package. Respondents are advised that participation in this market research effort does not guarantee participation in any future solicitation or contract award. The Government will not reimburse respondents for costs incurred in preparing or submitting responses to this RFI.
-Market Research10/30/2026
The Government is conducting market research to identify potential sources that have experience with the Lean Depot Management System (LDMS) and the expertise to maintain the infrastructure to support and sustain the LDMS within existing USAF legacy systems. This requirement is specifically for the USAF Small Arms Depot that has a requirement to sustain the LDMS within their unique depot repair operations. The Air Force has not made a commitment to procure any of the items/services discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. Contractors/Institutions responding to this market research are placed on notice that participation in this survey may not ensure participation in future solicitations or contract awards. The Government will not reimburse participants for any expenses associated with their participation in this survey. All submissions become Government property and will not be returned.
-Market Research03/23/2026
Request for Information Multi-X Security (MXS) Platform Operations and Maintenance 15 October 2026 1.0 Description The Air Force Life Cycle Management Center, in support of the Advanced Technology Branch (AFLCMC/HNJT), is seeking information from interested companies with the capability to provide Operations and Maintenance, and continuous modernization of the Multi-X Security (MXS) Platform. 2.0 Background Between 2019 and 2026, the Advanced Technology program office developed the MXS (pronounced “Maxis”) Platform as a modern security model, data model, reference architecture, and reference implementation, based on open standards and protocols to support software development and secure information sharing at multiple security levels. MXS' goal is to enable Protection Level 3 (PL3) software solution development by third-party developers within security-constrained environments, as typically employed by communities working with Special Access Programs (SAPs). 3.0 Description of Requirements 3.1 Scope & Operating Environment: AFLCMC/HNJT requires information on industry capabilities to operate, maintain, and continuously enhance a multi-tenant, cloud-native platform supporting Air Force and mission-partner applications. The platform operates across multiple security enclaves, including Unclassified, Secret//Special Access Required (SAR), Top Secret//SAR, and Top Secret//Sensitive Compartmented Information (SCI)//SAR cloud environments. 3.2 Platform Operations, Maintenance & DevSecOps: Prospective contractors are expected to provide proactive 24/7/365 system availability, platform administration, and lifecycle sustainment across all designated cloud environments. Core focus areas include: 3.2.1 Cloud-Native Infrastructure: Operating and maintaining containerized environments (e.g., Kubernetes), service meshes, Application Programming Interface (API) gateways, and Infrastructure-as-Code (IaC) baselines. 3.2.2 DevSecOps Toolchain: Sustaining an automated continuous integration/continuous delivery (CI/CD) pipeline that enables secure cross-domain software progression. 3.2.3 Telemetry & Resource Monitoring: Providing automated, granular visibility into platform health, microservice performance, compute/storage utilization, and licensing. 3.2.4 Enterprise ICAM & Certificate Services: operate and maintain enterprise identity management infrastructure across multiple tenants. 3.2.5 Managed Database Services, Registered Queries & API Mediation: Provision, sustain, and optimize managed database services across cloud environments, engineer registered and parameterized queries for controlled data access and governance, and diagnose latency or throughput bottlenecks. 3.3 Continuous Platform Evolution: Delivering agile enhancements, feature updates, and technical debt remediation in alignment with government-prioritized backlogs. 3.4 Tenant Enablement & Multi-Tier Support: To support diverse tenant software programs, the platform requires integrated customer enablement services. 3.4.1 Tenant Onboarding and Offboarding: Assisting tenant developer teams with architectural guidance, common control inheritance, and standardized integration toolkits. 3.4.2 Service Desk Operations: Operating a tiered technical service desk (Tier 1–3) providing incident management, troubleshooting, and user assistance across all classification levels. 3.5 Cybersecurity & Continuous Authorization: The platform must maintain a rigorous cybersecurity posture compliant with DoD, Intelligence Community, and SAP directives. 3.5.1 Sustaining existing Risk Management Framework (RMF) Authorizations to Operate (ATOs). 3.5.2 Executing Static Application Security Testing (SAST) and Dynamic Application Security Testing (DAST), container vulnerability assessments, dependency assessments (Software Bill of Materials (SBOM), Vulnerability Exploitability eXchange (VeX), etc.), and rapid vulnerability remediation. 3.5.3 Generating and maintaining RMF bodies of evidence and security documentation to maintain inheritance relationships for hosted software and systems. 3.6 Potential Security, Facility, and Personnel Requirements. The Government is conducting market research regarding the availability, timing, and feasibility of contractor personnel clearances, secure facilities, and cybersecurity qualifications that may be required for a future acquisition. The requirements of any future solicitation, including timing and acceptability of facilities, will be established only in that solicitation. 3.6.1 Personnel Clearances: Contractor personnel must possess active Top Secret clearances and applicable DoD 8140 baseline certifications at the time of contract award, with the ability to obtain SCI and SAP access within 30 days of contract award 3.6.2 Secure Facilities: Within 30 days of contract award, the Contractor shall possess and maintain accredited Sensitive Compartmented Information Facility (SCIFs)/Special Access Program Facility (SAPFs), as required to perform the classified development and operational activities under this contract. Each facility shall maintain current written accreditation by the cognizant accrediting authority and comply with applicable requirements of ICD 705, DoDM 5105.21, Volume 2, and DoDM 5205.07. 4.0 Specific Areas of Interest 4.1 Corporate Overview & Business Classification 4.1.1 Entity Identification: State your company name, Commercial and Government Entity (CAGE) code, and business size/socioeconomic status under the designated North American Industry Classification System (NAICS) code. 4.1.2 Contract Vehicles: List the relevant Government-Wide Acquisition Contracts (GWACs), Multiple Award Schedules (e.g., GSA MAS, NASA SEWP, OASIS+), or agency vehicles your organization currently holds. 4.2 Experience & Technical Approach 4.2.1 Relevant Past Performance: Provide up to three (3) examples (within the past 5 years) demonstrating prime or major subcontractor experience operating multi-tenant cloud platforms of comparable scope, complexity, and classification (including Amazon Web Services (AWS)/Azure Secret, Top Secret, or SAP enclaves). 4.2.2 Platform Management & DevSecOps: Describe your experience managing cloud-native infrastructure (e.g., Kubernetes, service mesh, Infrastructure as Code (IaC)) and sustaining multi-fabric DevSecOps pipelines across air-gapped or cross-domain environments. 4.2.3 Platform Software Development Kits (SDKs) & Toolkits: Summarize your experience developing and sustaining SDKs, shared libraries, and developer modules to accelerate tenant application delivery. 4.2.4 Enterprise Identity, Credential, and Access Management (ICAM) & Certificate Services: Describe your experience deploying and sustaining enterprise and external Certificate Authorities (CAs) across multi-tenant and air-gapped environments, including certificate validation and revocation infrastructure (e.g., Online Certificate Status Protocol (OCSP) responders, Certificate Revocation List (CRL) distribution points). 4.2.5 Managed Database Services, Registered Queries & API Mediation: Describe your experience provisioning, optimizing, and troubleshooting cloud-managed database services, including engineering registered and parameterized queries for controlled access and governance. Detail your experience developing middleware, abstraction layers, or gateway adapters for protocol bridging, query translation, and data transformation across disparate APIs. 4.2.6 Protection Level 3 (PL-3) Multi-Level Access Control & Attribute-Based Authorization: Describe your experience engineering and operating applications within PL3 SAR environments to restrict data access to users' explicit clearance and compartment authorizations. Detail your approach to synchronizing identity attributes from Authoritative Data Sources (ADS) and implementing, enforcing, and auditing Role-Based Access Control (RBAC), Mandatory Access Control (MAC), and Attribute-Based Access Control (ABAC) policies using Policy Enforcement Points (PEPs), Policy Decision Points (PDPs), and fine-grained, object-level filtering and data labeling. 4.3 Tenant Enablement & Multi-Tenant Operations 4.3.1 Onboarding & Isolation: Describe your approach to onboarding diverse tenant applications to a shared cloud environment while maintaining strict logical isolation, zero trust boundaries, and zero service interruption to existing tenants. 4.3.2 Training & Enablement: Outline the standard onboarding artifacts, API documentation, and training support that should be provided to tenant engineering teams. 4.3.3 Tiered Technical Support: Describe your operational model for delivering Tier 1–3 service desk and platform support across both unclassified and classified environments. 4.3.4 Service Level Agreements (SLAs) & Operational Sustainment: Describe your recommended Service Level Agreements (SLAs) for the platform, such as uptime/availability targets, incident response and resolution thresholds by severity, performance baselines, and Recovery Time Objective (RTO)/Recovery Point Objective (RPO) across unclassified and classified environments. Detail your operational support model, monitoring tooling, escalation procedures, and staffing strategy to guarantee and report on compliance with these metrics. 4.4 Cybersecurity & Compliance 4.4.1 Continuous Authorization: Detail your methodology for maintaining RMF accreditation. 4.4.2 Security Test Automation: Summarize your approach to code scanning and test automation to include tools, artifacts, processes, and gating criteria within a DevSecOps pipeline. 4.4.3 Security Standards Compliance: Outline your experience implementing JSIG/CNSSI 1253 Rev 5, DoDM 5205.07, Zero Trust Architecture, or any other applicable DoD/DoW requirements. 4.5 Security Clearances & Facilities 4.5.1 Personnel Clearance Readiness: Describe your labor pipeline and ability to provide qualified, certified personnel with Top Secret clearances with eligibility for access to SCI and SAP, and general timelines. 4.5.2 Secure Facility: Confirm whether your organization currently operates an accredited SCIF/SAPF suitable for classified contract execution or has a facility that could be accredited or modified within 30 days of contract award to meet applicable ICD 705 and SAP security requirements within the required contract performance timeline. 4.6 Cost Models, Funding Intake & Contract Structure 4.6.1 Cost Drivers: Identify primary cost drivers for baseline platform sustainment versus new feature development. 4.6.2 Consumption Metering & Showback: Describe your approach to tracking and reporting tenant consumption (compute, storage, service desk) to support customer-funded usage and line-of-accounting showback/chargeback. 4.6.3 Contract Structure Recommendations: Recommend suitable contract types (e.g., Firm Fixed Price, Time & Materials, hybrid) and incentive structures that balance performance, flexibility, and risk. 4.7 Contemplated Gating Strategy Feedback: The Government is contemplating an administrative Pass/Fail Phase 1 gate evaluated on an Acceptable/Unacceptable basis (e.g., verified prime contractor experience of similar scope, active facility clearance/accreditation, and baseline cyber certifications) prior to technical proposal evaluation. The contemplated gating approach is provided solely to obtain market research feedback. The Government has not established final evaluation factors, minimum qualification requirements, acquisition strategy, contract type, or source-selection methodology. Any future solicitation will independently state all applicable requirements and evaluation criteria. 4.7.1 Impact on Competition: Does the proposed Phase 1 gate unduly restrict your organization’s ability to compete as a prime contractor or participate as part of a joint venture/team? If yes, fully explain. 4.7.2 Recommended Criteria: What objective metrics, scope parameters, or dollar thresholds should define "similar experience" to ensure robust, qualified competition? 5.0 Response Interested vendors are invited to submit an unclassified capability statement demonstrating their ability to satisfy Section 3.0 requirements, along with detailed responses to the questions in Section 4.0. Do not include classified or SAP data in the submission. Submissions must not exceed twelve (12) single-spaced, single-sided pages (8.5 × 11 inch, 12-point font). Please send responses to this RFI electronically to the Contract Specialist within thirty (30) days after publication of this announcement. Questions concerning this RFI should be directed to Capt Matthew Gauert via email at matthew.gauert.2@us.af.mil with the subject line “RFI Response - MXS Platform O&M - [Company Name].” Note: only electronic responses will be considered. Respondent’s information shall contain respondent company name; company address; primary point of contact for information provided; and company website address that provides any additional information about the respondent’s company. Respondents shall clearly identify and mark any proprietary or confidential commercial information contained in their submissions. The Government will protect properly identified information from disclosure to the extent authorized by law and regulation. Information received may be used solely for market research and acquisition-planning purposes. Submission of a response does not grant the Government any license or other rights in a respondent’s proprietary information beyond those necessary to evaluate and use the response for those purposes. 6.0 Summary This RFI does not constitute an Invitation for Bids (IFB), Request for Proposal, Request for Quote (RFQ), nor does this issuance restrict the Government’s acquisition approach. Any information received is considered market research and may be utilized by the Air Force in developing its acquisition strategy. This market research will be used to assess the availability and adequacy of potential sources. The Government will not respond or conduct formal or informal briefings to vendors or respondents to this RFI. The Government does not reimburse respondents for any costs associated with submission of information being requested/received, nor reimburse expenses incurred to interested parties for responses to this RFI. THIS RFI IS ISSUED SOLELY FOR INFORMATION AND PLANNING PURPOSES AND DOES NOT CONSTITUTE A SOLICITATION. THE GOVERNMENT DOES NOT INTEND TO AWARD A CONTRACT ON THE BASIS OF THIS RFI, AND RESPONSES TO THIS NOTICE ARE NOT OFFERS AND CANNOT BE ACCEPTED BY THE GOVERNMENT TO FORM A BINDING CONTRACT. RESPONSES TO THIS RFI WILL NOT BE RETURNED.
-Market Research11/16/2026
This is an RFI ONLY. See Attached SOW
-Market Research10/17/2026
This requirement is for procurement of services including providing personnel, services, and management support for the Mission Planning Software Tool (MPST) software. The service will provide timely remote and periodic on-site support to the 30RS for MPST. The service includes maintaining compatibility with upgrades to the RQ-170 Mission Planning System (MPS) software, hardware, and databases by utilizing improved and/or expanded intelligence products. It will also ensure the software accurately represents new and/or improved aircraft capabilities, correct errors and address limitations encountered during operational use. Provide software and database maintenance and support functions to the 30 RS for the Mission Planning Support Tools (MPST) and Advanced Framework for Simulation, Integration and Modeling (AFSIM). The contractor shall provide software programming support for MPST computer program and its integration with AFSIM. All individuals performing on-site on this PWS must have a current adjudicated background investigation and be eligible for access to Top Secret, SCI, SAP information and associated ACCMs. Contractor personnel shall be conversant in the computer programming skills to fully support MPST, the version of AFSIM used by the RQ-170 simulator, be familiar with RQ-170 aircraft survivability, capabilities, Blue/Gray/Red ground and airborne threat systems, and Suppressor modeling capabilities/architecture/function/programming. Suppressor model may contain Foreign Government Information. The contractor shall provide support in training in the use of the version of AFSIM currently being used by the RQ-170. Actual work performance location is the contractor facility with periodic on-site visits to Creech AFB, NV and other classified locations as determined by the government.
-Combined Synopsis11/20/2026

Additional Details

Solicitation Number

FA483024R0004

Archive Date

Jun 15, 2024

Office Address

MOODY AFB, GA, 31699-1700