SOW -GARDEM C2-SpISR 12 MAR 25.docx

AIR FORCE RESEARCH LABORATORY

ROME RESEARCH SITE

ROME, NEW YORK

STATEMENT OF WORK (SOW)

FOR

GARDEM 2

COMMAND & CONTROL - SPACE INTELLIGENCE, SURVEILLANCE & RECONNAISANCE (C2-SpISR)

12 MAR 2025

(Solicitation No. RFI-RIKF-B004)

TABLE OF CONTENTS

4.0 TECHNICAL REQUIREMENTS. The Contractor shall accomplish the following:

4.1 The work will be performed in support of operational systems to include, but not limited to, the following GARDEM software baselines:

· C2Core Cyber

· C2Core Net Ops

· C2Core Air

· National Tactical Data Manager (NTDM)

· Advanced Collection Requirements Engine (ACRE)

· Knowledge-as-a-Service (KaaS)

· Master Air Attack Planning Tool Kit (MAAPTK)

· Integrated Solutions to Situational Awareness (ISSA) suite of tools

· Astrodynamics libraries

· United States Space Force (USSF), Schriever AFB, CO

· Air Force National Tactical Integration Colorado (AF-NTI CO) Buckley SFB, CO

4.2.2.3.1 Provide engineered solutions to mission partner interoperability via Office of the Undersecretary of Defense, Acquisition & Sustainment (OUSD A&S) Defense Exportability Features (DEF) program.

4.2.2.4.2.1 Interface and analyze National Technical Means (NTM) data and protocols to and from tactical data links (TDLs) as part of the service-based ISR mission planning applications

4.2.2.4.5.1 Interface and integrate with relevant PACFLT strike group systems to include but not limited to I-COP (Intelligence Carry On Program), C-COP (Cryptologic Carry On Program) and DCGS-N (Distributed Common Ground Station – Navy).

4.2.2.4.6 Enhance and develop the modernization of Joint Interface Control Officer (JICO) tool sets including but not limited to the C2Core NetOps application, generation of OPTASK LINKs (OTLs) for TDLs, network plans and COMMs for exercises and operational needs. Extend, expand and supplement the legacy Joint Interface Control Officer (JICO) tool sets capabilities with latest technologies and micro-services including but not limited to the C2Core NetOps application, generation of OPTASK LINKs (OTLs) for TDLs, network plans and COMMs for exercises and operational needs.

4.2.2.8.1 Novel approaches for correlating Publicly Available Information (PAI) data with traditional Intelligence sources (GEOINT, SIGINT, IMINT). This includes but not limited to novel techniques in machine learning applied to text analytics, imagery and video analysis, and target tracking.

· Verification of vendor licenses

· Recommendation for changes/upgrades

· Traffic/Load analyses in support of enhanced network component allocation/design

· DoDAF views to include, but not limited to, Operational View (OV), System Views (SV), and Capability Views (CV)

· Network /communications configuration, systems test/validation, data base administration, workstation configuration (to include hardware/software version control)

· Demonstrate reuse and modularity of software components to DoD test organizations

· Application software modifications and enhancements

· Coordination with development team on deliverables to include, but not limited to:

· Software Design Description (SDD)

· System Requirements Specification (SRS)

· Interface Control Document (ICD)

4.3.6.1.1 Provide GARDEM 2 on-site engineering support to the following locations:

· United States Space Force (USSF), Schriever AFB, CO

· Air Force National Tactical Integration Colorado (AF-NTI CO) Buckley SFB, CO

4.4 Work Plans.

4.4.1 Perform the work required under this order in accordance with any detailed performance information provided by the Government during performance in the form of a Work Plan. “Detailed performance information” is information provided to the Contractor that fills in details of the work to be performed, identifies areas of inquiry to be emphasized or de-emphasized, or otherwise serves to accomplish the Statement of Work (SOW). Detailed performance information will be issued to the Contractor in writing by the AFRL COR with a copy provided to the Contracting Officer. Work Plans shall not constitute assignment of new work, shall not change the terms or conditions of this order, and shall not constitute a basis for any increase in the amount of fixed fee or extension to the Contract Line-Item Number (CLIN) period of performance.

4.4.2 Each Work Plan will include, as applicable, the following information:

· Detailed performance information for work to be performed, cross referenced to the applicable CLIN and paragraphs of the SOW.

· Government estimates of the number hours and duration of effort likely to be required to successfully pursue the detailed objectives provided.

· Breakdown of estimated costs including labor categories (include work location(s)), rates, man hours, fee, Other Direct Costs (ODCs), travel (including origin and destination, number of trips, number of personnel, duration, and purpose).

· Areas of inquiry previously detailed that the Government wishes to emphasize or de-emphasize either because of achievements to date, or because of changes in program priorities.

· Funding Summary: Financial data, Period of Performance, Appropriation Category.

· Executive Technical Summary of work effort.

· Descriptive Summary including government technical and programmatic points of contact. Entities responsible for each distinct work effort, including government stakeholders and Point of Contact information; including COR and Alternate COR, AFRL Technical Lead, Government Capability Customer, and Prime Contractor Program Manager.

· Required Base Support.

· Technical and non-technical dependencies.

· Technical and non-technical assumptions.

· Deliverables and updates

· Program, project name and overview.

· Technical Approach.

· Staffing plan including equivalent heads by labor categories, durations, subcontractors, and management percentage.

· Engineering description and break down of key tasks required to meet technical requirements and objectives including technical effort, design, and developmental detail integration methodology.

· Required GFI, GFE, GFP needs.

· Estimated contractor acquired property (CAP).

· Identify Risks and mitigation plans impacting cost, schedule, or performance.

· Identified Opportunities to save cost, schedule, or to improve performance.

· New hardware and software requirements, reuse identification, number of system components affected, software modules and the percentage of each module involved, estimated lines of code, documentation affected, and estimated pages of updated documentation.

· Methodologies applied including software design and integration methodology, support methodology, etc.

· Use cases, where applicable.

0. Detailed schedule to include milestones.

0. Security requirement needs considering personnel, systems, Industrial Security and DD254s, to include Special Access Program/Special Access Required (SAP/SAR).

4.4.3 Provide Government fiscal year in which issued, and a unique identifying number consecutively issued within each fiscal year (e.g., Work Plan No. 2025-01, Work Plan No. 2025-02).

4.4.4 Upon receipt of a Work Plan (WP) from the Government, perform an analysis and provide implementation strategies to define possible and recommended approaches, potential resolutions, effort required, characterizations of various approaches, relationships to other ongoing effort, advantages and disadvantages of approaches, schedule, risks, and cost of alternative courses of action. Present results to the Government via a Work Plan for review, discussion, disposition, coordination, and approval. If identified in the Work Plan, include in each Work Plan testable performance requirements, deliverable items, delivery schedule, and cost. The Government will analyze this Work Plan to ensure the Contractor’s approach is commensurate with the SOW, the Work Plan, and estimated hours. Approval will be provided by COR signature on the Work Plan. (See CDRL, A025, B024, C024, D024, E024 and F024)

4.4.4.1 Provide to the Government the status of the effort to achieve the objective within budget, performance, and schedule. Participate in meetings to inform the Government as to progress and/or need for approval to change the hours, budget, scope, schedule, or deliverables required as the situation may warrant. Submit updates to Work Plans as requested by the Government due to scheduling, requirements, or other changes.

· Category 1: Prevents the accomplishment of an essential capability or jeopardizes safety, security, or other requirement designated "critical".

· Category 2: Adversely affects the accomplishment of an essential capability and no work around solution is known or adversely affects technical, cost, or schedule risks to the project or to life cycle support of the system, and no work-around solution is known.

· Category 3: Adversely affects the accomplishment of an essential capability but a work-around solution is known or adversely affects technical, cost, or schedule risks to the project or to life cycle support of the system, but a work-around solution is known.

· Category 4: Results in user/operator inconvenience or annoyance but does not affect a required operational or mission-essential capability or result in inconvenience or annoyance for development or maintenance personnel but does not prevent the accomplishment of the responsibilities of those personnel.

· Category 5: Any other effect with less impact.

4.5.6 Each PR/CR shall include the following:

· Description on system problem or enhancement to include title, date, overview of functional requirement, use case, priority and impact

· Customer Point of Contact (POC) to include name, organization, phone number and e-mail address

· US Government customer’s signature

· Total cost estimate to include the labor hours, travel, direct and indirect costs required to design, implement, test, document, and deliver to the Government

· Project schedule to include milestones like design, code, test and delivery phases

· Documentation affected

· PR/CR Software Requirement Specification that shall include the following:

· PR/CR purpose, scope, perspective, functions, user classes and characteristics

· Operating environment parameters and descriptions

· Assumptions and dependencies

· Software modules affected

· Specific requirements to include mock-ups and field tables

4.5.10 Upon Government PMO approval of the PR/CR work plan, design, integrate, test, and deliver site specific software with appropriate system and technical documentation.

4.6.1.1 For any items purchased as contractor-acquired property during the reporting period, please document the following information within the status report: Item Name, Description, Quantity, Unit of Measure, Serial Number, Manufacturer CAGE Code, Mfr Part Number, Mfr Model Number, Date of Acquisition, and Unit Acquisition Cost. This information may be included as an Excel spreadsheet attachment to the status report. (See CDRLs, A001, B001, C001, D001. E001 and F001)

· Standard Operation Procedures (SOP)/Working Procedures

· Collection, Collaboration, and Dissemination Process Documentation

· Training/Familiarization Materials

· Software Design Description (SDD)

· System Requirements Specification (SRS)

· Interface Control Document (ICD)

· Tactics, Techniques, and Procedures (TTPs)

· Roles and Responsibilities of Agile Product Teams

4.6.11.1 Inform the Government of any meeting with the Government or other contractor(s). Identify the organization(s) attending the meeting, the topic/agenda of the meeting, time, and location. (See CDRLs A004, A005, A006, B003, B004, B005, C003, C004, C005, D003, D004, D005, E003, E004, E005, F003, F004 and F005)

4.6.12 Develop, maintain, and provide continuity documentation for all out-plant positions. Document all information needed for continuity of operations in an out-plant position. The continuity documentation shall include: (See CDRLs, A033, B032, C032, D032, E032, and F032)

· Stakeholders, their roles and contact information

· Technical efforts in progress

· Recurring meeting times, locations, dial-in phone numbers and points of contact

· Recurring daily responsibilities

· Frequently used Uniform Resource Locator (URL) links

· Acronym glossary

4.6.13 Within 30 days of award hold a kickoff meeting.

4.8 COTS/GOTS Software: As upgrades to COTS/GOTS software are released by vendors/Government agents, such upgrades must be assessed for impact to the environment in which they operate. Changes shall first be approved through the CM process established prior to adding to the baseline. Upon Government approval, apply the upgrades to the baseline. (See CDRLs, A023, A024, B022, B023)

4.9 Overseas Travel: Comply with all Government foreign travel requirements as specified by this effort. Additional information and/or training maybe required on a country-by-country basis. Foreign travel is subject to the country-specific DoD Foreign Clearance Guide entry and exit procedures (https://apacs.milcloud.mil/fcg/index.html). As part of these procedures, depending on the country of travel, obtaining a Sponsor Company may be required to process a business license or business visas. The Contractor must also enter their employee information into the Aircraft and Personnel Automated Clearance System (APACS) in addition to the Synchronized Predeployment and Operational Tracker (SPOT), if applicable. The Contractor's responsibility to comply with all applicable laws and regulations regarding performance in country exists independent of, and is not established or limited by, the information provided by this requirement.

4.10 Training and Certification: Establish and execute a robust training baseline and continuing education program incorporating the latest required certifications to include but not limited to system administration, database certification, security certification, and operating system certification required at the sites listed in paragraph 4.1.

4.11 Acquire Hardware and Software: At the direction of the Government, acquire approved hardware and software to support the software baselines. Include licensing, maintenance and diagnostics support software. Arrange for delivery and installation of hardware, firmware, software and licenses to Government designated sites. (See CDRLs, A021, A024, B020, B023, C020, C023, D020, D023, E020, E023, F020 and F023)

4.12 Property Management: No known Government Furnished Property (GFP) is anticipated at this time, however if required during performance it will be addressed and the contractor will be responsible for providing “Property Management” to include updating and maintaining the listing/database of GFP to assure the accounting and status of all GFP under the contract.

4.16 System A&A: All software shall conform to the A&A requirements and system security compliance as defined in the Federal Information Security Management Act (FISMA), RMF, Director of National Intelligence (DNI) Intelligence Community Directive (ICD) 503, National Institute of Standards and Technology (NIST) 800-53 for developing, coordinating, reviewing, and approving Information Technology (IT) and National Security System (NSS) Interoperability and Supportability (I&S), Defense Intelligence Agency’s (DIA) DoD Intelligence Information System (DODIIS) Information Integrators Guide (DIIG) for connecting to DoD and Air Force networks to including Non-Secure Internet Protocol Router Network (NIPRNET), Secret Internet Protocol Router Network (SIPRNET), and Joint Worldwide Intelligence Communication System (JWICS). (See CDRLs, A017, A018, A019, A020, B016, B017, B018, B019, C016, C017, C018, C019, D016, D017, D018, D019, E016, E017, E018, E019, F016, F017, F018 and F019)

4.17 Adhere to Cloud Computing Requirements. Reference Section I clause DFARS 252.239-7010.

4.17.1 Work on this effort will require or allow Contractor access to Privacy Information. Content contained within the cloud services is subject to the Privacy Act. As such, the Contractor shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a, and applicable agency rules and regulations.

4.17.2 Work on this effort will require or allow Contractor access to Level 2 Public or Non-Controlled Unclassified Information. Content contained within the cloud services is subject to the Freedom of Information Act (FOIA). As such, the Contractor shall adhere to the FOIA regulations, and applicable agency rules and regulations.

4.17.3 Work on this effort will require or allow Contractor access to Level 4 Controlled Unclassified Information, including “Export Controlled,” and “For Official Use Only” data, and non-National Security Systems (NSSs). Content contained within the cloud services is subject to the Freedom of Information Act (FOIA). As such, the Contractor shall adhere to the FOIA regulations, and applicable agency rules and regulations.

4.17.4 Work on this effort will require or allow Contractor access to Level 5: Higher Sensitivity Controlled Unclassified Information, Mission Critical Information, and NSSs. This CUI requires a higher level of protection as deemed necessary by the information owner, public law, or other Government regulations, such as information related to unclassified NSSs.

4.17.5 Work on this effort will require or allow Contractor access to Level 6: Classified Information up to SECRET which includes information that has been determined to be classified national security information or Restricted Data (RD).

4.17.6 Data Ownership. All Government data, Government-related data, and metadata is and shall remain the exclusive property of the U.S. Government.

4.17.7 Disposition. Provide for the transition of data in commercially available, or open and non-proprietary format (and for permanent records, in accordance with disposition guidance issued by National Archives and Record Administration). The Cloud service provider shall ensure that the Government retains access and download capability of all Government data, and Government-related data, on demand within one week of request, in an open format (e.g., ASCII, CSV, XML). “Open format” means platform independent, machine readable, and made available to the public without restrictions that would impede the re-use of that information.

4.17.8 Support applicable inspection, audit, investigation, or other similar authorized activities specific to the relevant types of Government data and Government-related data, or specific to the type of cloud computing services being acquired. Ensure the CSP is able to supply the agency with audit trails, exception reports and transaction logs, if requested.

4.17.9 Support and cooperate with applicable system-wide search and access capabilities for inspections, audits, investigations, litigation, eDiscovery, records management associated with the agency’s retention schedules, and similar authorized activities.

4.17.10 Coordinate with the COR to respond to any spillage occurring in connection with the cloud computing services being provided under this effort.

4.17.11 Store all Government data within the 50 states, the District of Columbia, or outlying areas of the United States, unless the Government data is physically located on DoD premises, or the Contractor is otherwise authorized in writing by the Contracting Officer.

4.18 Stand Down Support. Provide documentation, training, and assistance for onboarding purposes to site support individuals for continuity of operations as order transitions to new performer. Provide reduced staff as requested by the Government for an option period of no more than three months.

4.19 SOFTWARE AND HARDWARE