Attachment No. 1- GARDEM 2 PM Apps SOW 26 MAR 2025.docx

AIR FORCE RESEARCH LABORATORY (AFRL)

ROME RESEARCH SITE (RRS)

ROME, NEW YORK

DRAFT STATEMENT OF WORK (SOW)

FOR

GLOBAL APPLICATION RESEARCH, DEVELOPMENT, ENGINEERING & MAINTENANCE (GARDEM) 2 PLATFORM AND MISSION APPLICATIONS (P&M APPS) RESEARCH, DEVELOPMENT, ENHANCEMENT AND SUSTAINMENT

26 MARCH 2025

(Reference No. RFI-RIKF-B005)

TABLE OF CONTENTS

4.1.2 Visualization across the enterprise by leveraging the DaaS Platform. Visualizations will include, but are not limited to:

· A workflow tracking and monitoring dashboard (user interface) with data analytics

· A health and status of resource visualization for understanding the status of all collection assets across all Intelligence Sources (INTs) Comment by GAITHER, WHITNEY W CIV USAF AFMC AFRL/RIKF: Spell out acronym.

· Visualization of all data object, object details, object relationships and object status in user-interactive; list, geospatial, temporal, relationship/network, and metrics-based graphics

· Visualization of command direction and guidance as it relates to the prioritization of Request for Information (RFI), Collection, Exploitation, and Production requirements Comment by GAITHER, WHITNEY W CIV USAF AFMC AFRL/RIKF: Spell out acronym.

· Providing awareness of command desired reporting and products via dynamically driven dashboard visualizations

· Visualize and assess intelligence data objects and their associations to determine whether final products meet original requirements. This includes comments associated with the objects through collaboration tools

4.1.2.1 Include development of functionality by scaling existing RFI, Intelligence, Surveillance, and Reconnaissance (ISR), Configuration Management (CM), and Mission Management (MM) systems for enterprise use by integrating them with common DaaS platform and eliminating system stovepipes in the existing CM/MM process.

4.1.2.2 Provide end-to-end traceability and management of Commander's Critical Information Requirements (CCIRs), Essential Elements of Information (EEI), etc.

4.1.3 Provide an Open System Architecture (OSA) based design to yield benefits in the form of a modular, interoperable system allowing components to be added, modified, replaced, removed, and supported by different vendors throughout the life cycle. Comment by GAITHER, WHITNEY W CIV USAF AFMC AFRL/RIKF: Remove “and/or”

4.1.4 Leverage and integrate existing enterprise capabilities, to include but not limited to PACOM JIOC-IT C2 Intel Dashboard, C4I Learning Environment (C4ILE), DLE Dev tools and Reference Implementation, and legacy collection and mission management programs.

4.1.5 Provide a Data as a Service platform to include novel and automated approaches for data access, integration, curation, and query/search

4.1.6 Develop methods for securely extending and integrating capabilities that use Data as a Service to include application hosting and job scheduling functionality

4.2 Operations & Maintenance - System Engineering and Baseline Enhancements: Manage and maintain the operational enterprise platform and mission applications software baselines that support numerous missions within the Intelligence, Air, Space, and Cyber domains. Support will consist of field support, training, requirements collection and analysis, and reviewing, recommending changes to and revising intelligence and operations Standard Operating Procedures (SOPs) and Tactics, Techniques, and Procedures (TTPs). Support will include coordination with on-site teams and other component and application developers to identify requirements for enhancements, executing the design and development of the enhancements, and successfully integrating, testing, and deploying software baselines. Software enhancements shall enable incremental system improvement, functionality, and stability through upgrades of security patches, individual hardware and software modules with newer modular components without redesign of entire system or large portions thereof. The work will be performed in support of operational systems to include, but not limited to, the following GARDEM 2 platforms: Comment by OGUNDADEGBE, ERICA L CIV USAF AFMC AFRL/RIKF: If this is an actual requirement of O&M and R&D we need within 4.0 Comment by GEORGE, DANIEL J CIV USAF AFMC AFRL/RIKA: COTR moved

· Trusted Resources for Tactical & Lean Enterprises (TRESTLE)

· Combined Information Data Network Exchange (CIDNE)

· WebTAS Enterprise

· Command, Control, Communications, and Battle Management (C3BM) Advanced Battle Management System (ABMS)

· C3BM Architecture and Systems Engineering (ASE) Support will be deployed at but not limited to the following locations and additional locations as world events dictate:

· Program Executive Office (PEO)/C3BM, Hanscom AFB, Massachusetts

· PEO/C3BM, Joint Base Anacostia-Bolling, Washington DC

· PEO/C3BM, Nellis AFB, Nevada

· PEO/C3BM, Robins AFB, Georgia

4.2.1 Enhancement Development System Engineering: system engineering includes but is not limited to system installations (para 4.2.4), testing (para 4.15), documentation (para 4.7), PR/CR management (para 4.4), systems engineering (para 4.6), Configuration Management (4.9), Authorization and Assessment (A&A) (para 4.15.2), interface management (para 4.5), and integration.

4.2.2 Provide a modular open standards approach to enhancing/modifying applications and architecture changes.

4.2.3 Participate in site exercises and wargames and maintain software during special contingency situations as requested by the Government. The exercise or contingency shall be at or near an existing site, overseas, or remote location. Special contingency situations include, war, armed conflict, insurrection, civil or military strife. This support is designated as mission critical.

4.3.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 Contracting Officer Representative (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.3.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-03, Work Plan No. 2025-04).

4.3.4 Upon receipt of a Work Plan 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 CDRLs, A025, B024, C024, D024, E024, and F024)

4.3.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 another 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.4.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

· 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

· List of deliverables include, but are not limited to:

· Software Design Description (SDD)

· Interface Control Document (ICD)

· System Requirements Specification (SRS)

4.6.2 Continuously analyze existing functional capabilities of the software baseline as well as information display requirements identified but not implemented.

4.7.4 Coordinate TO activities that cross stakeholder organizations and for providing representation on integrated project teams to ensure effective cross-organizational support, coordination, and collaboration.

4.7.5 Schedule, coordinate, and host a Project Kick-Off Meeting within fourteen calendar days of task TO award at a location approved by the Government. At a minimum, the attendees shall include key Contractor personnel, representatives from Government identified stakeholders, GPMO and the GARDEM 2 Contracting Officer (CO). The Contractor shall provide the following at the Kick-Off Meeting; (1) Introduction of Contractor team members and capabilities, (2) Overview of the TO scope, schedule, and deliverables Security Overview of the TO scope, schedule, and deliverables, (3) Security requirements/access procedures, (4) Invoice procedures, (5) Points of contact, (6) Additional issues or concerns, (7) AWS cost calculation worksheet, and (7) Draft Program Management Plan.

4.7.6 Develop and administer a Quality Control Plan. Ensure that all assigned products meet their specified design, format, functional and performance requirements. Assure the quality control process is integrated into all activities supported under the contract.

4.7.7 Perform continuous technical management to identify resources required for managing this order, and to resolve technical, system performance, cost, and schedule problems.

· Standard Operation Procedures (SOPs)/Working Procedures

· Collection, Collaboration, and Dissemination Process Documentation

· Training/Familiarization Materials

· System Requirements Specification (SRS)

· Interface Control Document (ICD)

· Tactics, Techniques, and Procedures (TTPs)

· Roles and Responsibilities of Agile Product Teams

· Management Plans

4.7.16 Conduct Engineering Design Reviews and System Requirements Reviews as prescribed by the GPMO.

4.7.17 Provide written notice to the Contracting Officer at least thirty (30) calendar days prior to substituting or removing individuals occupying these key personnel positions: (1) Program Manager, (2) Data Team Lead, (3) Chief Architect, (4) Lead Software Engineer.

4.8.3 Provide and execute a proven agile methodology (such as Secure Agile Framework for Enterprises, Kanban, Sprints, etc.) for analysis, design, development (including use of prototyping and modeling), coding, integration, testing, demonstration, and installation of development software to support operational sites. The development methodology must be grounded in sound development processes and detailed reviews, ensuring justified progression to the next system engineering phases.

4.8.4 All software and documentation, currently baselined, modified or enhanced, shall be compliant with IC and AF community policies and focus on rapid, agile delivery, enterprise infrastructure, and data management. Ensure all baseline changes are tracked and reproducible from inception to completion.

4.9.1 Provide CM/Requirements Management (CM/RM) in accordance with current Institute of Electrical and Electronic Engineers (IEEE) and Electronics Industries Association (EIA) standards as further defined by DoD and AFRL guidance. Implement an integrated process for managing information and products associated with the deployment and acquisition of all deliverable software, hardware, and associated documentation. The CM/RM process shall support the full software lifecycle (i.e., System Requirements Analysis, Design, Software Requirements Analysis, Preliminary Design, Detailed Design, and System Integration and Testing). (See CDRLs, A011, B010, C010, D010, E010, and F010)

4.9.2 Maintain and enhance CM processes for all software activities within GARDEM 2. Establish and maintain development, test, and production baselines in accordance with the Government-approved CM process. Coordinate, evaluate, prioritize, and schedule updates to baselines. Administer software and database baseline media library. (See CDRLs, A011, B010, C010, D010, E010, and F010)

4.9.3 All program documentation should be created and maintained within Government Owned Tool Suite, such as DLE, to include design review minutes, design checklists; code review minutes, code checklists; unit test results, unit test checklist; software release list; final unit test plan with allocated requirements; test drivers/data, source code, script files, task tracking, and preliminary design data. (See CDRLs, A011, B010, C010, D010, E010, and F010)

4.9.4 Review and revise Installation Plans for CM system delivery to support all aspects of the installation to include procedures for verifying that the installation is successful. (See CDRLs, B026, C026, D026, E026, and F026)

4.20.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.20.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. This level accommodates Non-CUI information categorizations based on CNSSI (Committee on National Security Systems) Instruction 1253 up to low confidentiality and moderate integrity (L-M-x).

4.20.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. This level accommodates CUI information categorizations based on CNSSI (Committee on National Security Systems) Instruction 1253 up to moderate confidentiality and moderate integrity (M-M-x).

4.20.4 Work on this effort will require or allow Contractor access to…