DRAFT_SOO_GeoSES_3April2025_for SAM.gov.docx

STATEMENT OF OBJECTIVES (SOO)

FOR

GEOPHYSICAL SIGNAL EXPLOITATION SYSTEM (GeoSES)

3 APRIL 2025

CONTROLLED UNCLASSIFIED INFORMATION

CONTROLLED UNCLASSIFIED INFORMATION

table of Contents

PURPOSE

The purpose of this draft Statement of Objectives (SOO) is to identify Air Force Technical Application Center (AFTAC) needs as they relate to transforming and modernizing the United States National Data Center (US NDC) core capabilities to deliver the Geophysical Signal Exploitation System (GSES).

This SOO generation is based on the topic of Enterprise Wide Integration and Architecture Modernization which corresponds to AFTAC’s Commercial Solutions Opening (CSO) number FA7022-25-SC001, Topic AFTAC-006, Enterprise-Wide Integration and Architecture Modernization.

This SOO identifies technical and program objectives designed to assist the contractor in developing a detailed Statement of Work (SOW) and cost proposal in accordance with the associated request.

This is a non-personal services contract. The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. The contractor shall manage its employees and guard against any actions that are of the nature of personal services or give the perception of personal services. The contractor shall notify the Contracting Officer (CO) immediately if they perceive any actions constitute personal services. These services shall not be used to perform any Inherently Governmental Functions

MISSION/BACKGROUND

AFTAC provides the U.S Department of Defense (DoD) time dominant scientific and technical information for decision advantage supporting international nuclear treaty compliance and strategic, operational, and tactical warfighters. Its mission is to detect nuclear explosions anywhere on earth, the atmosphere, or in space. AFTAC monitors for, collects, analyzes, characterizes, and exploits space, missile, atmospheric, subsurface, and hydrological events to identify violations to several nuclear and non-nuclear treaties worldwide. AFTAC operates the US NDC, which is the US arm of the International Monitoring System (IMS) supporting the Comprehensive Test Ban Treaty Organization (CTBTO). The US NDC and the IMS support international efforts to limit nuclear testing and proliferation worldwide. AFTAC provides national authorities quality technical measurements to monitor nuclear treaty compliance and develops advanced proliferation monitoring technologies to preserve our nation’s security. AFTAC also performs research and development of new proliferation detection technologies to enhance or assist treaty verification to limit the proliferation of weapons of mass destruction.

The US NDC software baseline dates to the 1990s. It comprises over 3,000,000 lines of code (logical SLOC), written in over a dozen programming languages (including: C, C++, csh, Fortran, Java, Python, Perl, Scheme, SQL). The current architecture, characterized by its monolithic nature and tightly coupled components, presents significant challenges to maintainability. This legacy software, developed prior to the adoption of modern architectural and security practices, is incompatible with cloud-ready environments in its current form.

SCOPE

The scope of this SOO, and resulting statement of work (SOW), will drive AFTAC's objectives for the replacement of US NDC mission system - modernizing and transforming its core capabilities to deliver the Geophysical Signal Exploitation System (GeoSES). The program aims to preserve mission-proven science and algorithms for signal detection, feature extraction, event building, and discrimination while maximizing the use of prior code investments. To achieve these goals, AFTAC seeks to transform the existing monolithic software architecture into a more modular, service-oriented framework, enabling agile and cost-effective interoperability with new technologies and software platforms. This transformation effort includes migrating code to modern, supportable programming languages, frameworks, and tools that offer enhanced performance, security, and developer productivity. Where practical, AFTAC may leverage cloud services to further enhance scalability, reliability, and cost-efficiency.

ORDERING PERIOD

The Government anticipates a five-year ordering period for Research, Development, Test and Evaluation (RDT&E) associated with the resulting SOW and IDIQ contract.

PERFORMANCE OBJECTIVES Comment by MORAN, LILEANA A CIV USAF ACC AFTAC/AMIC Det 2 OL: This section is work-in-progress. Industry is encourage to submit their own innovative solution.

Program Management The resulting SOW shall require assignment of Program Management (PM) personnel. The PM is responsible for the overall administrative, technical, cost, quality and schedule performance of the project. The Government anticipates Quarterly Program Management Reviews (PMR) and Cross Functional Team (CFT) meetings. The contractor shall provide all labor, facilities, and non-Government Furnished Equipment (non-GFE) to successfully complete all tasks that support the management of contract and task order activities.

Identification of program (task level) status through monthly funds and man-hour expenditure reports that include a summary chart as well as separate financial report documents. Identification of overall (contract level) status reports which contain depict schedule, a plan of actions and milestones (POAM), status of all tasks order requirements that have been completed that month, outstanding actions, future actions that will take place, and a summary addressing potential risks and areas of concern. The resulting SOW will describe documentation, reporting and briefing requirements for contract and task order events.

The Government anticipates a frequency of contractor PM meetings with government program office personnel (minimum 2 per month). The contractor shall support quarterly Program Management Reviews (PMRs) and present accurate status in accordance with the terms of the resulting SOW. The Contractor shall provide minutes of all scheduled meetings.

Assessment and Planning The resulting SOW shall describe:

Independent Assessment: The methodology to conduct a comprehensive assessment of the current US NDC software evaluating its architecture, functionality, performance, and security.

Architectural Alternatives: Explore and analyze alternative software architectures to identify the most cost-effective approach for achieving modernization objectives.

Program Plan: Develop a detailed program plan and schedule for the execution of the chosen modernization approach, outlining key milestones, deliverables, and resource allocation.

Software Modernization The resulting SOW shall describe:

Agile Development: Software modernization activities using agile software development methodologies to ensure iterative development, continuous testing, and flexibility in responding to evolving requirements.

Documentation: Develop comprehensive software specifications and Interface Control Documents (ICDs) to clearly define system requirements and interfaces.

Software Re-architecting: Re-architect the software as necessary to meet technical objectives, ensuring alignment with modern software development principles and best practices. Prioritize open standards and technologies to minimize vendor lock-in and ensure long-term system flexibility. Design the architecture to be scalable, enabling future expansion in terms of sensor channels, analyst workstations, and processing algorithms.

Integration: Integrate existing modernized components seamlessly into the modernized architecture.

Code Conversion: Convert and refactor existing software code to meet technical objectives and ensure optimal performance within the modernized environment. Implement necessary code modifications to comply with applicable cybersecurity requirements, not limited to "Zero Trust" principles.

Functional Parity: Retain all functional and performance capabilities available in the legacy system while addressing known gaps and deficiencies identified in the System Requirements Document (SRD).

Documentation Updates: Modify existing documentation or create new software design documentation as needed to support ongoing software maintenance and enhancement activities.

Testing: Develop comprehensive test procedures, including automated tests where feasible, to verify system compliance with requirements.

Operational Transition and Sustainability The resulting SOW shall describe:

Concurrent Operation: Ensure the modernized system supports the concurrent operation of both the legacy components and new capabilities during the transition periods of parallel operations.

Risk Management and Continuous Improvement The resulting SOW shall describe:

Risk Assessment: Conduct periodic risk assessments throughout the modernization process to identify potential challenges and develop mitigation strategies.

Capability Gap Closure: Prioritize modernization efforts that address identified gaps between required and actual system capabilities, striving to deliver a system that fully meets current and future operational needs.

GOVERNMENT FURNISHED SUPPLIES AND SERVICES

Services: The Government shall provide access to necessary software, equipment and/or information as necessary to execute the tasks within the contract. Examples include but are not limited to software tools and packages, hardware, existing APIs, Interface Control Documentation, etc. Government procedures will be used for control of all assets, equipment and information.

Facilities: The Government will provide access to government furnished property. Computer connectivity will be limited to direct support of specific tasks performed on Patrick Space Force Base, FL. Government procedures will be used for control and disposal of assets, equipment, parts, and materials.

Utilities: The Government will provide access to all power and communication utilities on government facilities necessary to enable task execution.

Equipment: The Government shall provide equipment to include software and hardware used to perform the required tasks in the government facility. Other equipment shall include security and communication hardware used to fulfill contract requirements.

Materials: The Government will provide all compliance documents necessary for the completion of the contract.

CONTRACTOR FURNISHED EQUIPMENT

The resulting task order SOW shall describe equipment the contractor intends to use during the performance of any task order under the resulting IDIQ contract.

SPECIAL REQUIREMENTS/INSTRUCTIONS

Information Technology All IT products (requirements and solutions), to include software, hardware, processes and security products delivered to AFTAC as a requirement of the resulting contract and/or task order SOW shall adhere to the AFTAC Enterprise Infrastructure Baseline with any deviations approved by the AFTAC Infrastructure Strategy Council before delivery of the IT product. All IT deliveries are expected to integrate and conform to AFTAC’s Enterprise Infrastructure Baseline. Hardware, storage, and database requirements must be identified as soon as possible and presented to the AFTAC Infrastructure Strategy Council for approval.

This program expects the adoption and execution of the Preferred Agile Framework outlined by the Department of the Air Force, ensuring an architectural framework that can be adjusted throughout the period of performance. If feasible, adopting existing applications, components, and platforms is preferred over creating custom solutions.

Software solutions shall adhere to the AFTAC Software Development Strategy Document (SDSD), to include software security and quality considerations. Any deviations shall be presented to the AFTAC Software Strategy Council as soon as they are identified. (Reference Addendum A, “Software Development Strategy Document”).

The resulting SOW shall describe a requirement providing all software developed for AFTAC will first be installed and tested in a development environment such as the Common Development Environment (CDE) at the appropriate classification level. The SOW will describe the contractors CDE. The Contractor shall supply on-site support for installation of software into AFTAC’s Continuous Integration (CI) Pipeline. The contractor shall also provide support to install and configure any middleware necessary to run the delivered software. Some software will remain in the CDE indefinitely. When software is intended for installation in the CDE and the operational environment the Contractor shall provide documentation to support certification and accreditation processes.

Software deliveries shall consist of source code of noncommercial software, all software dependencies, unit tests, related data, and associated license rights that are necessary across the life cycle of that software, including development, testing, operations, and maintenance. This includes all artifacts necessary to reproduce, build, or recompile the software from its source code and required software libraries; to conduct required software testing; and to deploy on relevant system hardware. Binaries or executables without source code, unless identified as Commercial off the Shelf (COTS) with support, are not an acceptable delivery.

All software deliveries are complete after integration into AFTAC’s CI Pipelines, installed and running in the CDE, and contain clean security scans (to include source code scans, third-party dependency scans, and ACAS scans) if intended for the operational environment. Onsite support for installation onto CDE and production/operational networks may be required, as well as assistance with integration and system testing efforts. The final software product is considered completed once it can be run by a government employee on AFTAC systems and it produces the results the software was developed for.

Data deliveries must be coordinated with appropriate Data Stewards or the AFTAC Data Governance Council. Any one-time or infrequent data delivery without any near real-time requirements may be provided via physical media such as DVD or external drives as approved by the AFTAC CISO, as well as enterprise mechanisms such as DoD Secure Access File Exchange (SAFE). Recurring data deliveries or time-sensitive data should be delivered in an automated fashion and must be coordinated with AFTAC's Data Flow team.

Special Training, Certifications and Qualifications Personnel requiring access to a DoD Information System shall receive initial IA awareness orientation as a condition of access and thereafter shall complete annual IA refresher awareness, as required by DoD Directive 8570.01, "Information Assurance Training, Certification, and Workforce Management."

Any contractor requiring access to an AFTAC-managed IT system (on premises or cloud) in order to write or edit software destined for the production system will require IAT Level II certification IAW DoD Directive 8570.01 “Information Assurance Training, Certification, and Workforce Management”. Contractors requiring elevated privileges to an AFTAC-managed IT system (on premises or cloud) will require certifications based on the level of elevated privileges that will be determined on a case-by-case basis but will require a minimum of IAT Level II certification.

Contractor Identification in the Government Workplace When conversing with Government personnel during business meetings, over the telephone or via electronic mail, the contractor shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. The contractor shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation.

Industrial Security DD Form 254. Overarching security requirements and contractor access to classified information will be as specified in the DD Form 254, Department of Defense Security Classification attached to the contract. The contractor shall have a final U.S. Government issued TOP SECRET security clearance and be DCID 6/4 eligible with a current SSBI.

Location(s) of Work The work to be performed under this IDIQ shall be performed at AFTAC HQ (1020 south Patric Drive, Building 10989, Patrick SFB, FL 32925). This requirement shall be defined in individual Task Orders and via the DD Form 254.

Kick-off Meeting and Periodic Progress Meetings The contractor shall attend an initial kick-off meeting within 30 days after contract award. The Contracting Officer (CO), PM/ Government Program Manager (GPM), and other Government personnel, as appropriate, will meet periodically with the contractor to review the contractor's performance. At these meetings the CO will apprise the contractor of how the Government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues.

The contractor shall participate in a quarterly engineering, design, and information assurance review called a Technical Interchange Meeting (TIM). The contractor shall provide minutes of these meetings to the Government.

Contractor Travel The contractor may be required to travel to other Government and or industry facilities during the performance of this contract in support of specific tasks to include, but not limited to, participate in meetings, conferences, and test/demonstration events. All travel requirements (including destination, purpose, plans, agenda, itinerary, number and names of personnel, and dates) shall be pre-approved by the GPM. The contractor shall submit a trip report within five business days from completion of travel. The SOW shall describe any anticipated travel requirements. Costs for travel shall be billed on a strictly cost reimbursable basis IAW, the regulatory implementation of Public Law 99-234, FAR subpart 31.205-46 entitled Travel Costs and the limitation of funds specified in this contract. The Government will establish a CLIN for a set NOT-TO-EXCEED amount.

Deliverables The resulting SOW shall include identification of a Contract Data Requirements List (CDRL). The CDRLs listed below are examples of deliverables the government expects to see in the resulting SOW.

First report due 45 calendar days after contract award. Subsequent reports due no later than the 10th business day of each month.

First report due 45 calendar days after contract award. Subsequent reports due no later than the 10th business day of each month.

First report due 45 calendar days after contract award. Subsequent reports due no later than the 10th business day of each month.

Due 30 calendar days prior to end of contract.

Due not later than 5 calendar days of meeting / event.

Working version due every 30 calendar days. Final IMS due not later than 15 calendar days prior to end of contract.

Working version due every 30 calendar days. Final RMP due not later than 15 calendar days prior to end of contract.

As requested.

Shall be provided within the first half of the POP.

Due not later than 10 calendar days of testing new software version.

Notification of software release with SVD due 10 calendar days prior to software release.

First submission date to be defined and determined in Kick-off meeting and/or subsequent technical interchange Meetings. Subsequent deliveries due 30 days prior to any Software delivery.

Due with final delivery of software, CDRL A017, not later than 15 business days prior to end of contract.

As required, concurrent with any software release. Final consolidated manual due 15 calendar days prior to end of contract.

Due not later than 10 calendar days prior to testing any new software / version of software.

Systems Engineering Management Plan (SEM)

Draft shall be provided not later than 90 calendar days from contract award. Final SEM due not later than 15 calendar days prior to end of contract.

As requested and in frequency in accordance with CDRL.

Data Rights The contractor shall provide the government with copies of GOTS system(s) used in execution of this contract and all associated source code(s) developed in association with the resulting contract and associated task orders. The resulting contract will include FAR Clause 52.227-23, Rights to Proposal Data (Technical). The Government requires solutions to allow for open-source release. Comment by MORAN, LILEANA A CIV USAF ACC AFTAC/AMIC Det 2 OL: Additional Data Rights may be pursue by the Government in accordance with the CSO.

Task Order 0001 SOW The Government anticipates the award of an IDIQ contract. Regulations require a simultaneous award of at least one Task Order with the award of any IDIQ contract. This SOO requires preparation and submission of both a contract level SOW and Task Order 0001 specific SOW. Performance objectives 5.1 - 5.5, will be addressed in the Task Order 0001 SOW.

Task Order 0001 Delivery Schedule 45 Days after Task Order Award: Program Delivery Roadmap. Schedule updates to be provided monthly thereafter.

APPENDIX A - ACRONYMS AND ABBREVIATIONS LIST

Acronym/Abbreviation Definition

APPENDIX B - APPLICABLE PUBLICATIONS & INSTRUCTIONS

Compliance with all publications, regulations and operating instructions provided by the Government is required when: They pertain to the procedures for materials expediting herein and where the contractor is authorized by the PWS to accomplish the work specified in the publication, regulation or operating instructions. The publications prescribe USAF policies, use of materials, procedures and processes applicable to the work requirements. The contractor is required to acquire and work on the latest version of the publication.

Chapter SOO Section

Software Development Strategy Document (SDSD) Addendum A