Combat Coder Site Support

Request for Information (RFI)

This RFI seeks information regarding contractor capabilities to provide a dedicated software engineering team for the Combat Coder Program. The objective is to design, engineer, test, integrate, deploy, and sustain software capabilities for the Distributed Common Ground System (DCGS) enterprise, focusing on continuous delivery of secure, high-quality, and mission-effective software to meet evolving ISR requirements.

• Operate within a DevSecOps framework and perform full Software Development Life Cycle (SDLC) support.

• Adhere to Agile methodologies (Scrum, Kanban) with code increments delivered at the end of each sprint.

• Utilize government-provided GitLab repository for all source code, configuration files, and deployment scripts.

• Develop on platforms including Maven Smart Systems, ArcGIS, Dagster, and Apache Airflow.

• Ensure code undergoes peer-reviewed Merge Requests and passes automated pipeline checks (zero new critical/high vulnerabilities, minimum 80% unit test coverage).

• Provide 24/7 software sustainment and incident response for the DCGS production environment.

• All personnel must possess DoD 8570 IAT Level II certification and maintain an active Top Secret/SCI security clearance. No trainee-level personnel.

• Tasks will be directed by individual Task Descriptions (TD) issued under an Indefinite Delivery/Indefinite Quantity (IDIQ) contract.

• This RFI is for informational and planning purposes only and does not constitute a Request for Proposal (RFP).

• Responses to Capability Survey Part I and Part II are due by 4:00 PM EST, July 16, 2026.

• Responses must be sent via email to Samantha Taylor (samantha.taylor.12@us.af.mil) and Mathew McGhee (mathew.mcghee.3@us.af.mil).

• Attachments should not exceed 10MB per email; multiple emails are acceptable.

• Government proposed NAICS Code: 541330.

• Responders must indicate their business size and certifications (Small Business, WOSB, SDB, 8(a), HUBZone, VOSB, SDVOSB, SAM registered).

• Indicate if the company is domestically or foreign owned.

• Company Name, Address, POC, CAGE Code, Phone, Email, Web Page URL.

• Business size and ownership details.

• Verifies capability to perform PWS services.

• Summarizes relevant previous experience.

• Assesses capability to perform all required services.

• Determines if the PWS provides sufficient information for RFP response.

• Inquires about personnel with Top Secret/SCI clearances and facility clearances.

• Assesses understanding of DoD and FIAR regulations.

• Gathers information on Accountable Property System of Record (APSR) experience and preferences.

• Gauges interest in submitting a proposal for a future RFP.

• Focuses on methodologies for cost-sharing in an IDIQ FFP structure with multiple stakeholders.

• Seeks information on managing on/off ramping, fluctuating demand, and cost allocation.

• The Government will not pay for any information or administrative costs incurred in response to this RFI.

• All costs associated with responding are solely at the interested party's expense.

Performance Work Statement (PWS)

To provide a dedicated, contractor-operated software engineering team to design, engineer, test, integrate, deploy, and sustain software capabilities for the Air Force Distributed Common Ground System (DCGS) enterprise. The primary goal is the continuous delivery of secure, high-quality, and mission-effective software that rapidly responds to emerging DCGS enterprise intelligence, surveillance, and reconnaissance (ISR) requirements.

• Agile Methodologies: Utilize iterative Agile methodologies (Scrum, Kanban) and track work in the government-provided JIRA instance. Participate in Agile ceremonies.

• Software Design & Development: Design, develop, and test resilient software applications on authorized government platforms (e.g., Maven Smart Systems, ArcGIS, Dagster, Apache Airflow) using open standards and APIs. Code must be clean, efficient, maintainable, and adhere to secure coding practices (OWASP Top 10).

• DevSecOps & Cybersecurity: Integrate security into all SDLC phases. Maintain source code in government-provided GitLab using a "GitFlow" strategy. Code must pass peer-reviewed Merge Requests and automated pipeline checks, with zero new critical or high vulnerabilities. Maintain a minimum of 80% unit test coverage.

• 24/7 Sustainment & Incident Response: Provide rapid engineering support for the DCGS production environment. Respond to critical, mission-impacting bug reports within 4 business hours, providing a mitigation plan or hotfix within 24 business hours. Ensure documented rollback procedures.

• Deliver tested and integrated software increments at the end of each two-week sprint; achieve at least 80% of committed story points.

• All code must pass security scans with zero new critical or high vulnerabilities.

• Maintain a minimum of 80% unit test coverage for new code.

• Respond to critical operational bug reports within 4 business hours and provide a mitigation plan within 24 business hours.

• 100% compliance with contractor personnel qualifications.

• No more than one rejection of any CDRL deliverable per contract year due to quality or accuracy issues.

• No more than one late submission of deliverables per quarter.

• Period: 12-month base period with four (4) 12-month option periods.

• Place: Primarily at Langley AFB, VA; McConnell AFB, MO; and Beale AFB, CA. Temporary Duty Travel may be required to Hickam AFB, HI; Ramstein AB, GER; and Osan AB, ROK.

• Personnel Qualifications: Staff with highly vetted, experienced, and certified professionals. Minimum requirements include specific years of experience, technical proficiencies, DoD 8570 cybersecurity certifications (IAT Level II minimum), and active Top Secret/SCI clearances.

• Government Property: Contractor must define and manage Government Furnished Property (GFP), Equipment (GFE), and Material (GFM). Government will provide development workstations, access to classified networks, DCGS technical baseline, and development/testing platforms.

• Security: Strict compliance with numerous DoD and Air Force security regulations, including CUI, Covered Defense Information, NISPOM, OPSEC, COMSEC, and personnel security clearances (TS/SCI).

• Mission-Essential Services: Contractor must submit a plan for continuing mission-essential software development, integration, and sustainment activities during a crisis.