J-05 FS3i_ Air_PWS v4.1_01022026.docx

PERFORMANCE WORK STATEMENT (PWS)

For Foundation Sustainment Support, Software and Integration (FS3i)

Solicitation Number HM047625R0016 Air Task Order

July XX, 2025

Version 4.1

UNCLASSIFIED

UNCLASSIFIED

FS3i Air Domain PWS Version Change Tracker

Table of Contents

1 (U) Purpose

(U) The contractor shall comply, adhere, and execute all requirements and services outlined in this Task Order (TO) Performance Work Statement (PWS). This PWS defines expectations and requirements needed to sustain the Foundation GEOINT (FG) Mapping, Charting, and Geodesy Technologies Program Office (IPF) Foundation Sustainment Support, Software and Integration (FS3i) for the Aeronautical Navigation Office (SFA).

(U) This PWS also establishes the acquisition framework for delivering required services for the NGA Source Operations & Management Directorate's Foundation GEOINT Group (SF), Aeronautical (Aero) Safety of Navigation (SoN), and its mission partners. The main objective is for the contractor to design and execute an agile support construct to provide the optimal Aero SoN user experience and become a trusted Information Technology (IT) SF mission partner essential for the daily production of FG data.

2 (U) Background

(U) The SFA produces timely, relevant, validated, and accessible worldwide aeronautical foundational Geospatial Intelligence, online and on-demand, to meet Aero SoN, AFD and VO requirements, and other contingency requirements, for the Department of Defense, Other US Government Agencies and our Allied Partner nations. The process to do such is largely human-centric, labor-intensive, time-consuming, and involves a thorough examination and validation of thousands of source materials received from over 190 nations across the globe, in search of changes to current data holdings. This review is conducted on a 28-day cycle to collect, store, maintain and produce worldwide data. The 28-day cycle is based on standards defined by the International Civil Aviation Organization (ICAO), containing information essential to air navigation.

(U) This TO is designed to satisfy the IT mission requirements located in the Solution Epic Source Content Management Intelligence Capability Baseline Description (ICBD) and Air Solution and Program Epics Production Content Management V1.0, 30 Nov 20 and all future versions and revisions authorized by the Office of SFA.

3 (U) Scope

(U) The FS3i Air TO shall align with the Work Breakdown Structure (WBS) in Appendix B of the FS3i IDIQ PWS. The contractor shall provide services for, WBS 2.0 Integration, WBS 3.0 Software Maintenance, and WBS 4.0 Operations Support. Program Management is embedded within each service category and is not a separate category to itself. The WBS aligns to the service categories as follows:

(U) The top-level work breakdown structure for the FS3i Air TO is depicted in Figure 3.1

Program Management 4.0 Operations Support 3.0 Software Maintenance 2.0 Integration FS3i Contract

(U) The contractor shall adhere to each capability in Section 12 of this PWS for detailed Agile Requirements.

(U) The contract shall comply with, adhere to, and execute all requirements and services outlined in this Task Order PWS.

4 (U) Current Environment and Constraints

(U) The contractor shall follow the guidance and procedures outlined in the IPF Capability Delivery Standard Operating Procedure (SOP) outlined in Section 4 of the FS3i IDIQ PWS.

(U) The contractor shall establish productive teaming arrangements and efficient working relationships with other Aeronautical critical partners, including Government offices, research laboratories, data providers, non-FS3I industry vendors such as SW code providers for development and maintenance, and NGA Development corps.

(U) The contractor shall follow the IPF Software Solution Stack Standards.

(U) The contractor shall adhere, leverage, integrate, coordinate, and deliver all capabilities with NGA enterprise IT offices, such as Enterprise IT Services (TE) Enterprise Operations (TO), Adopt & Deliver Directorate (TI) ensuring all capabilities are properly on boarded and properly postured for operational readiness within the NGA infrastructure.

5 (U) Tasks

(U) The contractor shall adhere to all WBS requirements identified in this PWS. Modifications to this PWS and associated engineering change proposals (ECPs) will be provided for additional Aeronautical IT capabilities when required and approved by SFA.

5.1 (U) The contractor shall provide AGILE sustainment services for the Aeronautical Production System (APS). Refer to the APS Addendum (Attachment #1) for a description of the APS capability.

(U) The contractor shall:

5.1.1 (U) Provide Software Maintenance (O&M) Services for APS. (WBS 3.0)

5.1.2 (U) Provide Operation Support (O&M) Services for APS. (WBS 4.0)

5.2 (U) The contractor shall provide AGILE sustainment services for the Web Digital Vertical Obstruction File (WebDVOF) to include hosted in NGA OpenShift environment. Refer to the WebDVOF Addendum (Attachment #2) for a description of the WebDVOF capability.

(U) The contractor shall:

5.2.1 (U) Provide Integration Support Service (RDT&E) for WebDVOF (WBS 2.0)

5.2.3 (U) Provide Operation Support Service (O&M) for WebDVOF (WBS 4.0)

5.3 (U) The contractor shall provide AGILE sustainment services for the Geospatial Terminals Operation Program (GTO). Refer to the GTO Addendum (Attachment #3) for a description of the GTO capability.

(U) The contractor shall:

5.3.1 (U) Provide Operation Support Service (O&M) for GTO (WBS 4.0)

5.4 (U) The contractor shall provide AGILE sustainment services for Data Abstract Requirements Management System (DARMS).

5.4.1 (U) Provide Integration Support Service (RDT&E) for TERPS (WBS 2.0)

5.4.3 (U) Provide Operations Support Service (O&M) for TERPS (WBS 4.0)

5.5 (U) The contractor shall provide AGILE sustainment services for AIP Source Extraction Tool (ASET).

5.5.1 (U) Provide Integration Support Service (RDT&E) for ASET (WBS 2.0)

5.5.3 (U) Provide Operations Support Service (O&M) for ASET (WBS 4.0)

6 (U) Services

(U) The following WBS items are common services for all Aero SoN capabilities under this TO. Additional details are provided in each service description in the tables below.

6.1 (U) Integration Services – WBS 2.0

(U) The contractor shall integrate new/existing Air Domain capabilities/services/micro-services from development and integration efforts/Release Trains through the DevOps pipeline into operations. Note: Developer/Sustainer Release Train may be Government and/or third-party contractor. Already developed, operational, or commercially available hardware or software capabilities may be integrated into existing environments/architectures.

(U) The contractor shall integrate Government-Off-The-Shelf (GOTS), COTS, Free and Open Source Software (FOSS), microcode, and software developed by development teams into the AERO operational capabilities. An example of activities includes but are not limited to integrating software, GOTS, COTS, and FOSS into the following services and capabilities:

1. NGA Enterprise IT Services

2. IT platform infrastructure

3. System and subsystem software

4. Application and data software

5. Security

(U) The contractor shall deliver an overarching Integration Management Plan that describes development, deliverables guidelines and templates, as well as integration roles / responsibilities, and a checklist that ensure successful integration of newly developed software or software fixes into the AERO operational capabilities.

(U) One or more of the above factors inform the estimated effort needed to integrate a capability into the operational capability.

(U) See the Deployment chart for more information about capabilities that are currently in the integration phase on this Task Order.

(U) The contractor shall meet the Integration Service requirements listed in section 12 documentation and the table below.

(U) This table is Unclassified.

The contractor shall collaborate with the Operations Support contractor and provide updates to the Configuration Management Plan (A013 - Configuration Management Plan).

CDRL A039 - Automation Deployment Instructions.

The contractor shall develop an Integrated Test Program and associated plans, events, procedures, and checklists scaled appropriate to the line.

The contractor shall develop scenarios and checklist in support of Government-managed Independent Verification and Validation (IV&V) events.

The contractor’s scenarios shall track traceability from high-level requirements (from its origins), through its development and specification, to its subsequent testing scenarios, and through all periods of on-going refinement and iteration in any of these phases.

The contractor shall produce an Integration Test Report that includes traceability of software functions to the requirements, number of passed and failed, and a brief description of reasons for the failures.

The contractor shall provide input and track DRs, and Root cause in the Knowledge Management system.

The contractor shall build out and establish a knowledge management program within 90 calendar days. The system shall be based on best practices to meet the Government and stakeholders needs and must be implemented for all lines in a centralized location. It shall capture, document, and trace to all service tickets, help desk inquiries, all technical library documentation, all issues, all analysis, all trouble shooting, and all causes of operational outages.

The contractor shall adhere, follow, leverage, or integrate all lines with NGA Enterprise Service plus.

SOW.

When required, the contractor shall perform Root Cause/Trend Analysis.

2.24 Discrepancy Report (DR) Investigation The contractor shall adhere to the Discrepancy Report (DR) Investigation requirements in accordance with section 6.24 of the FS3i IDIQ PWS.

The contractor shall provide a System Performance Optimization Technical Report (SPOTR) for systems under the contractor’s care. The SPOTR shall produce reports to include performance monitoring and data collection report for on premises and the Cloud resources, cost and usage data, and end-to-end software performance including ETL elapsed time and AWS resource utilization (i.e., EC2, RDS, EBS, etc.).

A037 – System Performance Optimization Technical Report (SPOTR) The contractor shall provide the Performance Metrics as they are listed in Appendix A of this task order.

2.26

The contractor shall participate in preparation and delivery of the services and status tracking.

The contractor shall participate in tracking the status of projects, open incidents, and other anomalies.

The contractor shall provide the capability to collect cost, operational and performance metrics for subsystems, subsystem components, and Cloud infrastructure.

The contractor shall collect Sprint/Scrum metrics in accordance with the metrics stated in the IPF Capability Delivery SOP1.

The contractor shall provide the capability to manage collected metrics and provide analysis reports using existing tools, and dashboards.

The contractor shall tailor the Government ITDR process for all supported subsystems and environments.

CDRL A018 - Information Technology Disaster Recovery (ITDR)

The contractor shall provide the capability to seamlessly integrate database into subsystems or systems as required by the Government.

The contractor shall plan, implement, test, and deploy database in the testing and development environments for all security domains in the Cloud or On-premises

1 (U) Foundation GEOINT Capability Delivery Standard Operating Procedure (SOP)

CDRL A009 Cloud Migration Plan The contractor shall provide the capability to seamlessly integrate FG capabilities, GOTS, COTS, FOSS, and software to the Government designated Cloud environments.

The contractor shall capture all design elements as described in Appendix C. The contractor shall draft an Integration Design Review Presentation (IDRP) (CDRL A032) and host the applicable number of design review sessions with the Government and contractor stakeholders for review and approval. This step will facilitate architecture and design trade-offs that enable the government to make critical investment decisions in systems architecture as needed before building proceeds.

The contractor shall provide the necessary engineering expertise and resources to plan, execute studies, and implement AERO technical requirements and activities covered by this PWS consistent with the NGA System Engineering Plan (SEP) and industry best practices.

The contractor shall provide integration engineering capabilities to integrate FG capabilities, COTS, GOTS, FOSS, and software into the operational line. This includes at the minimum:

1. Solution design.

2. Design review with the Government and contractor stakeholders.

3. Development of solution.

4. Leading the reviews and demonstrations of the integrated solutions.

5. Acceptance testing, a government managed verification, and validation of the integrated solution.

6. Development and delivery of architectural and system engineering artifacts for the integrated solution.

7. Collaboration of the contractor with the Government and contractor stakeholders for packaging and releasing the integrated solution into the operational line.

8. Application Program Interface (API) management

9. Providing the capability for post release metric collection for analysis of executions, functionality, and performance of the newly or changed released capabilities into the operational line.

10. Where applicable, assessing user experience after a new integrated solution is in the production.

Lessons Learned in optimizing the development, integration, and delivery of the integrated solution.

Support The contractor shall provide Technical Writing and Documentation Support services in accordance with section 6.39 of the FS3i IDIQ PWS.

The contractor shall include and register the appropriate engineering and architectural artifacts in a Technical Library as they are listed in Appendix C of this Task Order for each Air subsystem.

The contractor shall present a PowerPoint version of the Transition-In Plan (CDRL A006) at the contract kick-off meeting that details the 30 day schedule, process of capturing and transitioning all necessary Government Furnished Equipment (GFE) and Government Furnished Information (GFI), account creation, personnel onboarding, documentation, security (physical, personnel, cyber, information), software keys, system administration account access, risks, action items, government coordination, and equipment relating to transitioning of operations and maintenance support from the FS2 contract. As part of the transition kickoff meeting, the contractor shall support the government’s task order transition readiness review checklist execution.

The contractor shall provide weekly (or more often as needed) transition update teleconferences meetings from Key Personnel to IPF Sustainment Program Office.

The contractor shall arrange and facilitate a government transition readiness review with the incumbent and the government within 30 days of contract award. The contractor shall present an updated transition checklist for the team to review. The objective is to obtain government authority to assume full responsibility for the Air Task Order operations.

Upon Government request, the contractor shall execute a Transition-Out Plan (CDRL A012) to turn over the responsibility for all integration activities for the AERO subsystems and services.

The contractor shall be given 30 days to produce the transition-out plan and 60-days to transition the responsibilities.

6.2 (U) Software Maintenance – WBS 3.0

(U) The contractor shall meet the Software Maintenance Service requirements in section 12 documentation and requirements listed below.

(U) This table is Unclassified in its entirety.

The contractor shall provide Demo Support every six months.

The contractor shall identify, isolate, and rectify a fault or problem to restore a system or application to an operational state.

The contractor shall ensure resolution of Priority 1 and 2 INC and PBIs, Discrepancy Reports (DR), Information Assurance Vulnerability Assessments (IAVA) and Requests for Change (RFC) per NGA timelines for operational tickets.

Atlassian Confluence or Jira site.

Table 6.3: (U) List of requirements for Software Maintenance

6.3 (U) Operations Support Services – WBS 4.0

(U) The contractor shall provide operations support to all capabilities listed in section 5. This support includes all requirements outlined in the table below.

(U) The table below is UNCLASSIFIED in its entirety.

Technical Report as required every agile cycle in accordance with FS3i IDIQ PWS section 6.1. (CDRL A037)

The contractor shall update the Software Library itself, license management report, and library curation CONOPS

(U) The contractor shall deliver all gold copy source code into the GFE-provided code repository and SVDD. (CDRL A011& A038)

A013)

All line deployments (HW, COTS, GOTS code, Custom Code) shall be deployed using the automated deployment tool.

The contractor shall deliver the Release plan 5 days after each RPE. Plan is delivered in JIRA, and a .pdf copy to PMO.

The contractor shall maintain and update the FS3I Release Plan (CDRL A021).

Backlog grooming The contractor shall manage and coordinate backlog grooming sessions with the Government and contractor stakeholders to support updating and prioritized backlog for all Aero SoN capabilities and services in operations covered under this task order.

The contractor shall provide skills, expertise, and adequate resources to meet mission requirement for testing, and deployment of new or changed software to the operational line and to provision, maintain, and operationalize Aero SoN Cloud environments for all security domains.

The contractor shall provide Resolution entry / Root cause analysis and solution completed in the Knowledge management system within one business day after system restoration.

The contractor shall adhere, follow, leverage, or integrate all operational lines with NGA Enterprise Service plus.

Support The contractor shall meet the requirements stated in FS3i IDIQ PWS section 6.21.

Support The contractor shall meet the requirements stated in FS3i IDIQ PWS section 6.22.

The contractor shall track incidents (INCs), problem investigations (PBIs) and Discrepancy Reports (DRs) that affect the VC test and operational lines.

When required, the contractor shall perform Root Cause/Trend Analysis.

The contractor shall operate and maintain the Aero SoN capabilities and services at a user operational availability rate of 99.9% for deployed services.

The contractor shall provide the Performance Metrics as they are listed in Appendix A of this task order.

The contractor shall provide operations support services to monitor, maintain, and administer the Aero SoN systems development, test, and operational environments to include, but are not limited to, the software line, data configurations and other Cloud services during operating hours as described in Section 10.

The contractor shall report on operational status of subsystems under contractor’s care to include availability and quality of data and services required to make the Aero SoN capabilities/services to meet the mission requirements.

The contractor shall collect Sprint / Scrum metrics in accordance with the metrics stated in the IPF Capability Delivery SOP.

The contractor shall provide the capability to collect and report operational, diagnostics, performance, and cost related Metrics.

The contractor shall provide recommendations for threshold values applicable for generating alerts, alarms, and warnings.

The contractor shall provide the capability to provision Sand Box, Maintenance, Test, and Operational environments in the Cloud for all security domains upon requests from the Government.

4.32

The contractor shall tailor the Government ITDR process for all supported subsystems and environments.

(CDRL A018) ITDR

The contractor shall continuously evaluate the AWS services for use in the operational environments and make recommendations about use of applicable AWS services.

The contractor shall provide the capability for management and sustainment of container technologies that are or will be deployed in the Cloud environments. CDRL (A009) Cloud Migration Plan The contractor shall develop processes and methodology to monitor and optimize the cost of using Cloud services in Development, Test, and Operational environments for all security domains.

The contractor shall produce monthly analysis report outlining cloud costs by environment and by line CDRL (A037) System Performance Optimization Technical Report.

The contractor shall provide the necessary engineering expertise and resources to plan, execute studies, manage, and implement Aero SoN technical requirements and activities covered by this PWS consistent with the NGA System Engineering Plan (SEP) and industry best practices. This includes:

· Acceptance testing, a government managed verification, and validation of the integrated solution.

· Development, maintenance, and delivery of architectural and system engineering artifacts.

· API management and post release metric collections.

· Post release analysis of execution, functionality, and performance of the changed released capability or a change of the operational line.

· Where applicable, assessing user experience after a changed capability is in the production.

Lessons Learned in continual service improvement processes.

The Contractor shall present a PowerPoint version of the Task Order Kickoff (CDRL A025) and the Transition-In Plan (CDRL A006) at the Task Order kick-off meeting that details the schedule, process of capturing and transitioning all necessary GFE and GFI, account creation, personnel onboarding, documentation, security (physical, personnel, cyber, information), software keys, system administration account access, risks, action items, government coordination, and equipment relating to transitioning of operations and maintenance support from the FGS-IOS contract.

The contractor shall provide weekly (or more often as needed) transition update teleconference meetings from Key Personnel to IPF Sustainment Program Office.

The objective is to obtain government authority to assume full responsibility for the Aero SoN Task Order operations.

Upon Government request, the contractor shall plan and execute a Transition-Out plan (CDRL A012) to turn over responsibility for all O&M activities for the Aero SoN subsystems services.

The contractor shall be given 30 days to produce the transition-out plan and 60-days to transition responsibilities.

Table 6-4: (U) List of requirements for Operations Support services.

7 (U) Travel

(U) The contractor shall adhere to travel requirements in accordance with section 8.1 of the FS3i IDIQ PWS.

8 (U) Period and Place of Performance (PoP)

(U) The period of performance shall be a nine (9) month period with four (4) one-year options periods from date of task order award.

(U) The contractor shall provide key personnel for Places of Performance located at the NGA West Campus (2nd Street-within the SFA footprint, St. Louis, MO) and at the Contractor Facility.

(U) The primary place of performance shall be at the contractor’s facilities. The contractor shall provide secure and unclassified video-teleconferencing capability (VTC) facilities, communications infrastructure, NGA connectivity, and NGA workstations, including security to support the goals of the contract and that are cleared in accordance with the National Industrial

Security Program. Primary place of performance, including NGA connectivity and workstations, must be available at task order award.

(U) Temporary access to Government owned and operated equipment (e.g., NGANet or Desk Top Environment (DTE) workstations) will be made available onsite on an as-needed basis to fulfill contractual obligations (e.g., onsite workstation access to perform operational system upgrades). Temporary access will be granted at NGA facilities in the Washington, DC and St. Louis, MO area.

(U) Work at the Contractor site can be unclassified. If classified work is to be conducted at a Contractor site, the Sensitive Compartmented Information Facility (SCIF) must be approved by the CO and Security. Contractor must have existing NGANet connectivity with the appropriate workstations to accomplish all work outlined within this PWS at time of award.

9 (U) Quality Assurance Surveillance Plan

(U) The Quality Assurance Surveillance Plan (QASP) is primarily focused on how the Government will ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the rating standard. The Government will provide the QASP as an attachment to the task order.

(U) The contractor shall ensure the quality of services performed under this task order meet or exceed the performance metrics summary provided in Appendix A: Performance Metrics of this PWS. The contractor shall immediately notify the COR of problems or situations that could negatively impact compliance with the provisions of the task order and the plan the contractor shall implement to resolve problems. The designated COR/ACORs will participate in the administration of this task order by evaluating contractor performance, inspecting, and accepting services for the Government, and providing a report of inspection as well as contractor performance assessments to the CO.

(U) The Contractor Program Manager shall meet twice per task order period with the CO, GPMO, and/or COR and other government-designated personnel as deemed necessary to discuss performance evaluation(s). These will be in-depth reviews with the contractor, including appropriate self-assessments by the contractor; however, if the need arises, the contractor will meet with the GPMO and/or COR as often as required or per either party’s request.

(U) The GPMO and COR along with the contractor should jointly formulate tactical and long-term courses of action. Decisions regarding changes to metrics, thresholds, or service levels should be clearly documented. If a change is required to the existing QASP, it will be incorporated as a contract modification by the CO.

(U) The Contractor shall implement and perform a Quality Control function to ensure that all activities performed, and products delivered meet or exceed the standards in the QASP. The Quality Control function shall be documented in a Quality Control Plan (QCP) (CDRL-A015).

10 (U) Operational Hours

(U) Regular Hours: Onsite and offsite personnel shall be required to perform work during regular NGA duty hours (0500-1700 NCW local time).

(U) Non-regular hours: Provide call back operational and technical support outside of normal business hours (0500-2100 NCW local time) of operation including federal holidays. System outages and Priority 1 Discrepancy Reports require response time within one hour.

(U) Personnel are expected to be available via telephone 365 days per year (366 in leap years) providing Tier 2 and Tier 3 support through a combination of on-site and off-site support, except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings or similar Government-directed facility closings. Modification of normal hours of operation will be at the discretion of the Contracting Officer.

11 (U) Government Furnished Equipment

(U) No Government Furnished Equipment will be located at the contractor’s facility.

(U) Upon change the contractor shall adhere to the Government Furnished/Contractor Acquired Property Management requirements in accordance with section 7.4 of the FS3i IDIQ PWS.

(U) The contractor shall account for and maintain all the Government-provided materials, property, and equipment IAW FAR Clause 52.245-1, Government Furnished Property (CDRL A007).

(U) The contractor shall manage the Aero SoN operational configuration line and Government furnished equipment, property, and information (GFx) for all government and contractor provided hardware, software licenses, maintenance agreements, and information. The Contractor shall be responsible for asset reporting of GFx items via NGA’s Total Asset Management processes.

(U) The Contractor shall manage all GFx and is responsible for:

· Procuring material (if needed and approved by the CO/COR)

· Supporting the Government Program Management Office (GPMO) for tracking of Government Furnished Items (equipment, licenses, information, etc.) and hardware assets, software licenses and maintenance agreements

· Supporting NGA enterprise asset tracking activities for Government Furnished Equipment (GFE) and operational environment material including Total Asset Management (TAM) – related reporting requirements (procured or managed by this contract)

· Providing listings of all software license needs (type and quantity) to the Government NLT 90 days in advance of the need date (unless approved as an exception by the GPMO) for maintenance under Enterprise License Agreements (ELAs)

· Providing listings of all needed Government Furnished Information (GFI) to the Government no later than 30 days in advance

· Provide an inventory of all GFE and Software Licenses within 30 days of contract start with monthly updates thereafter

(U) It is the Government’s intent that all current software lines, development, integration and operations environments, backlogs, contract deliverables and supporting reference documentation for these Aero SoN capabilities will be provided as Government furnished materials (GFx) during the transition.

(U) As directed by the Government, all government furnished information released to the contractor or created in the performance of this contract will be destroyed by the contractor or returned to the NGA upon termination of the contract; or when no longer required in the performance of the contract.

12 (U) Applicable Documents The following is a list of documents the contractor shall reference for Aeronautical (Air) system information and governance details. This list is not exhaustive. As system and/or governance documents change, it is understood that the government Task Order Program Manager will provide the Contractor with updates.

· Foundation Sustainment Support, Software and Integration (FS3i) IDIQ PWS

· IPF Capability Delivery SOP

· IPF Software Solution Stack Standards

· NGA Software Way

· NGA Technology Strategy APR_20-512

· FS3i Aeronautical Safety of Navigation Quality Assurance Surveillance Plan

· Aeronautical Production System (APS) Documents:

· APS Addendum

· APS Concept of Operations (CONOPS)

· Web Digital Vertical Obstruction File (WebDVOF)

· WebDVOF Addendum

· Geospatial Terminal Operations (GTO)

· ACE-GTO Addendum

· Data Abstract Requirements Management System (DARMS)

· AIP Source Extraction Tool (ASET)

(U) APPENDIX A: Performance Metrics PERFORMANCE METRICS – This Table is UNCLASSIFIED

Integration

Configuration Management System (CMS) must be updated/accurate every 30 days

environments/services compliant with NGA monitoring directives.

days of discovery.

DevSecOps tools as outlined in the SOP document.

during the operating hours.

degradation.

disaster. Meet 100% of NGA ITDR policy/requirements.

Software Maintenance

WBS 3.16-3.19

Detect priority 1 issues within 1 hours of onset during operating hours.

WBS 3.16-3.19

Detect priority 2 issues within 3 hours of onset during operating hours.

WBS 3.16-3.19

Operational Priority 1 Discrepancy Report (DR) Investigation corrected within 24 hours or have a workaround in place.

WBS 3.16-3.19

Operational Priority 2 DR’s corrected within 72 hours.

WBS 3.16-3.19

Root Cause Analysis and corrective actions reported to PMO within 5 calendar days of DR closure.

WBS 3.16-3.19

Restore Maintenance/Test Environment within 4 hours of an outage during the operating hours.

WBS 3.16-3.19

Provide status updates twice daily during business hours for any outages or degradations.

Operations Support

months before the expiration dates.

within 1 week of a change to a CI and 95% within 2 weeks.

outlined in the SOP document2

hours of onset, during the operating hours.

corrected within 24 hours or have a workaround in place.

days of discovery.

Provide operational status for 99% operational subsystems, updated hourly during business hours.

deployed services.)

within 4 hours of an outage during the operating hours.

during business hours for any outages or degradations.

20 min after identification of an outage or degradation.

requirements for ITDR.

30 days

(U) APPENDIX B: CDRLs

(U) The CDRLs listed in the table below are FS3i Program Level CDRLs aligned with the FS3i IDIQ.

(U) This table is Unclassified

Data Item Description

Award Subsequent Versions

Upon Award Update Program Management Plan to reflect Aero

Contract Funds Status

Update monthly

Report

7.6

#2.41

Government

Calendar days As directed by the Government

Cloud Migration Plan

Calendar Days As directed by the Government

Software Code and Software Code Documentation

A011

CFA

days of request by the Government

2.42, 4.42 As directed by Government As directed by the Government

Configuration Management Plan

Calendar Days As directed by the Government

Risk Management Plan

Calendar Days As directed by the Government

Quality Control Plan

Calendar Days As directed by the Government

Information Technology Disaster Recovery Plan

(ITDR)

A018

CFA

TO PWS, WBS # 2.32, 4.32

Award +60 Calendar Days

Update yearly for each operational capability

Decommissioning Plan(s)

A020

CFA

Release Plan

A021 Update JIRA and a PDF copy to PM

days after first RPE 5 calendar days after each RPE

Program Management Review

A023

CFA

prior to each review

Task Order Kickoff Presentation

A025

Power Point

TO PWS WBS# 4.41

At the Kick-off meeting 15 calendar days after future subsystem is added to the Task-Order

Operations Support Plan (OSP)

A030

CFA

Base PWS, Para 6.11, 6.25, 6.31 As directed by the government

As directed by the government

Risk / Issue / Opportunity Register (RIOR)

A036

CFA

FS3i IDIQ PWS, Para 6.5, 6.8-6.9, 6.11, 6.36-6.38

Award +30 Calendar Days 30 calendar days after new subsystems are added to contract

System Performance Optimization Technical Report

A037

CFA

Stakeholder Communication Plan (SCP)

A047

CFA

Task-order

(U) Appendix C: Technical Library Contents List

(U) Interface Control Document (ICD):

a. Write up with the appropriate DoDAF viewpoints for before and after ICD design and implementation.

b. At the minimum, produce an SV-1 architectural viewpoint for before and after views.

c. Versioning, document change table and impacted components.

C.2 (U) Interface Descriptions: (System, Subsystem, Services, and Components) C.3 (U) Subsystem Integration Plan (SIP):

d. Work Breakdown Structure (WBS)

e. Integration Schedule that traces to the WBS elements and costs

f. Requirements Traceability Matrix (RTM)

g. Risk/Issues/Opportunity Register (RIOR)

h. Infrastructure and Cloud configuration plan

i. Subs-system monitoring plan C.4 (U) Integration Package

j. Integration Readiness Review

k. Integration Readiness Review checklist C.5 (U) Design Elements

l. Solution design

m. Traceability to the requirements

n. Design alternative analysis

o. System Engineering artifacts

p. API Management

q. Microservices

r. Subsystem monitoring design

s. Infrastructure design including Cloud for all security domains.

t. Alternative analysis, list of viable solutions and their Pros and Cons C.6 (U) Requirements / Capabilities:

u.…