Science_Task_Order_20240917.docx

PERFORMANCE WORK STATEMENT

(DRAFT)

For

Foundation Sustainment Support, Software and Integration (FS3i) Contract Number: xxxx Science Task Order

17 Sep 2024 Version 1

FS3i Science Task Order Perfromance Work Statement (PWS) Version Change Tracker

Table of Contents

Purpose The contract will comply, adhere, and execute all requirements and Information Technology (IT) services outlined in this Task Order (TO), Performance Work Statement (PWS).

This PWS details the services, expectations, and requirements needed to sustain the IT capabilities of the NGA, Foundation GEOINT (FG) Integrated Program Office (IPF) and provide daily operational, mission support for the six divisions of the Office of Geomatics (SFN) within the Source Operations & Management Directorate's Foundation GEOINT Group (SF).

The main objective of this TO is to alignin acquisition, sustainment, and operational efforts, and deliver required, flexible, optimal, and affordable SFN IT capability support outcomes.

To be successful, the contractor must become a trusted IT services mission partner and an essential part of SFN’s daily operations, which is crucial to the NGA and SFN Assured Postioning, Navigation, Timing, and Targeting (APNT&T) mission, the Safety of Navigation missions, the data production missions, and the IC and DoD National Security missions, humantitarian and disaster relief efforts, and civilian organizations around the world.

Background The Office of Geomatics (SFN) enables Geospatial Intelligence (GEOINT) accuracy through functional management of geodetic, geophysical, and photogrammetric sciences and content. SFN through six divisions: Geosciences (SFNA), Elevation (SFNE), GNSS (SFNG), Integration (SFNI), Precise Imagery (SFNP), and Surveys (SFNS) for the collection of sciences, technology and tradecraft measuring and modeling the Globe to provide three-dimensional accuracy of every point in, on, or above the Earth.

The SFN and its 6 divisions currently rely on approximately 150 different IT baselines, each comprised of different types of hardware and software architectures, in order to do it’s daily mission. Each of these IT capabilities require some level of IT sustainment service support, where “sustainment” is defined as “keeping the product relevant to the user.”

This TO is intended to satisfy all sustainment and operational support services, required for all SFN IT capabilities, supporting all 6 divisions of SFN.

This TO is also intended to satisfy all of the IT sustainment requirements as defined within the Office of Geomatics, Intelligence Community Baseline Description (ICBD) Science, Solution and Program Epics, including all future versions and revisions authorized by SFN.

The NGA Integrated Program Office, Source Foundation (IPF), Science, project management office (PMO) will identify, prioritize, and task which IT capabilities and sustainment services will be included within the scope of this FS3i, Science TO, PWS, see this FS3i Science PWS paragragh 5.0 Tasks for specifics.

Scope The FS3i Science TO will align with the Work Breakdown Structure (WBS) of the FS3i Base IDIQ Statement of Work (PWS) and requires WBS 1.0 Program Management, WBS 2.0 Software Development, WBS 3.0 Integration, WBS 4.0 Software Maintenance, and WBS 5.0 Operations Support sustainment services. WBS 6.0 Foundation GEOINT IT Procurement and WBS 7.0 Foundation GEOINT COTS Softare Procurement services are required to support SFN IT capability sustainment, but will be satisfied under a separate FS3i Task Order dedicated to consolidate Procurement support for the entire SF and IPF.

Current Environment and Constraints The contractor will follow the guidance and procedures outlined in the IPF Capability Delivery Standard Operating Procedure (SOP) outlined in the FS3i Base PWS IDIQ Section 4. See Section 12 for a complete listing of applicable contractual compliance documents.

The contractor will establish and maintain productive teaming arrangements and efficient working relationships with other Geomatics 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.

The contractor will adhere, leverage, integrate, coordinate, and deliver all capabilities with NGA enterprise IT offices, such as Enterpise 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.

Tasks The contractor will adhere to all WBS requirements identified in this PWS. Modifications (MOD)s to this PWS and associated addendums will be provided, if needed, for additional Geomatics IT capabilities, when required and approved by the IPF Science PMO.

5.1 The contractor provides AGILE sustainment services for TerraSAR-X add-on for Digital Elevation Measurement (TanDEM X). Refer to Appendix F for a list of the TanDEM X components.

The contractor provides:

5.1.1 WBS 1.0: Program Management

5.1.2 WBS 3.0: Integration

5.1.3 WBS 5.0: Operations Support

5.2 The contractor provides AGILE sustainment services for the Geodetic Survey System (GSS). Refer to Appendix F for a list of the components.

The contractor provides:

5.2.1 WBS 1.0: Program Management

5.2.2 WBS 3.0: Integration

5.2.3 WBS 5.0: Operations Support

5.3 The contractor provides AGILE sustainment services for the Geomatics Unclassified Production Environments (UPEs) capabilities associated with GGEPS, GGPM, GNSS and PIPS. Refer to Appendix F for a list of the components.

The contractor provides:

5.3.1 WBS 1.0: Program Management

5.3.1 WBS 3.0: Integration Support

5.3.2 WBS 5.0: Operations Support

5.4 The contractor provides agile sustainment services for Global Navigation Satellite System (GNSS). Refer to Appendix F for a list of the components.

The contractor provides:

5.4.1 WBS 1.0: Program Management

5.4.2 WBS 3.0: Integration Services

5.4.3 WBS 5.0: Operations Support

5.5 The contractor provides AGILE sustainment services for Geophysics Enhanced Production System (GGEPS). Refer to Appendix F for a list of the components.

The contractor provides:

5.5.1 WBS 1.0: Program Management

5.5.2 WBS 3.0: Integration Services

5.5.2 WBS 5.0: Operations Support

5.6 The contractor provides AGILE integration, deployment and sustainment services, cybersecurity support and virtual infrastructure management for each of the Geomatics and Geospatial Product Modernization (GGPM) security environments. Refer to Appendix F for a list of the components.

The contractor provides:

5.6.1 WBS 1.0: Program Management

5.6.2 WBS 2.0: Software Development

5.6.2 WBS 3.0 Integration Service

5.6.4 WBS 4.0 Software Maintenance

5.6.2 WBS 5.0: Operations Support

5.7 The contractor provides AGILE sustainment services for Terrain Contour Mapping (TERCOM) workstations. Refer to Appendix F for a list of the components.

The contractor provides:

5.7.1 WBS 1.0: Program Management

5.7.2 WBS 5.0: Operations Support

5.8 The contractor provides AGILE sustainment services for Precise Imagery Production System (PIPS) modernization. Refer to Appendix F for a list of the components.

The contractor provides:

5.8.1 WBS 1.0: Program Management

5.8.4 WBS 4.0: Software Maintenance

5.8.5 WBS 5.0: Operations support

IT Sustainment Services The following WBS items are common IT sustainment service requirementas for all Geomatics IT capabilities under this TO, and each are further decomposed with additional details for each IT sustainment service description in the tables below.

1.1 Program Management Services

The contractor provides Program Management Service support to all capabilities listed in this TO. This support includes all requirements outlined in the table 6-1 below and associated addendums in section 12.

The Contractor will arrange and host a task order kick-off meeting within 15 business days of award.

The contractor kick off meeting presentation will include the following content: (CDRL A025)

· Review contract and program administration, deliverables, risks, and transition schedule

· Additional topics proposed by the Government and Contractor.

The Contractor provides a monthly EM TO PMR for the IPF / SFN office.

The contractor will hold TEMs, facilitate capturing requirements, and be responsive in delivering proposals in support of the most efficient RFP process.

The contractor will host reviews and update the required CDRLs NLT 30 days after award for the following:

· Program Management Plan (A001)

· Contract Funds Status Report (A002)

· Risk Management Plan (A014)

· Program Management Review (A023)

· Risk / Issue / Opportunity Register (A036)

· Stakeholder Communication Plan (A047)

The contractor will use each addendum to obtain job descriptions, qualifications, and requirements for all personnel.

Key personnel will be levegered from TO1 for this TO, however, we do anticipate dedicated personnel for this TO in the future.

The contractor will adhere to the Classified Work performance security requirements per FS3i Base IDIQ PWS section 7.7.1 The contractor will adhere to the Unclassified Work performance security requirements per FS3i Base IDIQ PWS section 7.7.2

Table 6.1: List of Program Management Services

1.2 Software Development Services

The contractor will develop new EM Capabilities/services/micro-services as alternatively the lead developer, or in cooperation within a multi-vendor development effort. Note: Developers/Sustainer Release Trains may be Government and/or other non-FS3i contractors. This task may involve leveraging already developed, operational, or commercially available software capabilities that are adapted to meet Earth Modeling requirements.

The contractor provides updates to the master Software Library for the installed FG baseline in accordance to the CDRL A038 – Software Library Management Report.

The contractor provides Configuration Management services, including SW/HW in accordance with section 6.3 of the FS3i Base IDIQ SOW.

The contractor will collaborate with the Operations Support contractor and provide updates to the Configuration Management Plan as in accordance to the CDRL A013 - Configuration Management Plan.

CDRL A039 - Automation Deployment Instructions.

The contractor provides release management services in accordance with section 6.5 of the FS3i Base IDIQ PWS.

The contractor will develop, coordinate, and maintain the Release Plan to include any Government required NTO testing, enterprise test events, deployments, scans, external demos, quality standards, security approval (CDRL A021).

The contractor will deliver the actual plan for the release (Release Plan) 5 days after the Release Planning Event (RPE). The Plan is delivered in JIRA and .pdf copy to PMO.

The contractor will collaborate with the Operations Support contractor and provide input into the Release Plan in accordance with CDRL A021. The Release Plan is updated after each Release Planning Event (RPE).

The contractor will coordinate release planning events with all Government and Contractor stakeholders.

CDRL A021 – Release Plan CDRL A024 - Deployment Chart

The contractor will deliver an Integration Management Plan (CDRL A031) that includes and Integration Readiness Review Checklist (IRRC), The contractor will support 10 readiness reviews per year. The final data-deliverable Integration Package and the Sub-system Integration Plan (SIP) (in the formats that are described in the Technical Library), to include criteria for passing the operational readiness review.

1. The Integration Package is comprised of all relevant documents described in the Technical Library document list in Appendix C along with a completed Integration Readiness Review checklist as described in the Integration Management Plan (CDRL A031).

2. The Sub-system Integration Plan (SIP) is comprised of a Work Breakdown Structure (WBS) with associated cost (CDRL A035) that aligns with the Capability Integration Schedule (CDRL A034) and a Requirements Traceability Matrix (RTM) (CDRL A033) that corresponds to the Risk/Issues/Opportunity Register (RIOR) (CDRL A036).

The contractor will organize and facilitate a government Integration Readiness Review and invite all relevant attendees to address.

The Contractor will develop and implement cost saving initiatives, processes, and procedures during execution of all this PWS tasks throughout the course of contract performance that are intended to result in realized cost efficiencies. CDRL A022 - Value Engineering Change Proposal (VECP)

CDRL A043 - Request for Change (RFC) Management Impact Assessment.

The contractor will adhere to the DevSecOps Management services in accordance with section 6.11 of the FS3i Base IDIQ PWS.

The contractor will provision and maintain environments on each security domains for development efforts as defined by the Government.

The contractor will lead and provide expertise during testing and deployment of GOTS, COTS, FOSS, and new or changed software to the EM operational baselines.

The contractor will perform integration services on all security domains as required.

The contractor will execute all integration tasking required for delivery of new/updated EM software baselines from one environment to the next to expose the Capabilities/services to the users for testing and deployment into operations.

The contractor will perform the required integration tasks for development as outlined in the deployment instructions as defined in IPF Capability Delivery SOP.

The contractor will participate in analysis of system performance metrics and provide recommendations to gain efficiencies (CDRL A008) where applicable.

The contractor will ensure integration activities meet program and product owner requirements.

The contractor provides updates into the configuration management system about the hardware and software changes to the operational baseline because of the contractor’s actions.

The contractor will update the Version Description Document for the integrated portion of the whole. (CDRL A019).

The contractor will develop an Integrated Test Program and associated plans, events, procedures, and checklists scaled appropriate to the baseline. Deliver an integration Test Readiness Review checklist (CDRL A027).

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

The contractor’s scenarios will 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 will 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.

CDRL A044 - Integration Test Report

The contractor will use the Government directed Knowledge Management process in accordance with section 6.15 of the FS3i Base IDIQ PWS.

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

The contractor will build out and establish a knowledge management program within 90 calendar days. The system will be based on best practices to meet the Government and stakeholders needs, and must be implemented for all baselines in a centralized location. It will 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 will keep it up-to-date per metric(s) in Appendix D.

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

The contractor provides the Performance Metrics as they are listed in Appendix D of this task order.

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

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

The contractor will adhere to the Metric Collection and Analysis requirements in accordance with section 6.27 of the FS3i Base IDIQ PWS.

The contractor provides the capability to collect cost, operational and performance metrics for sub-systems, sub-system components, and Cloud infrastructure.

The contractor will collect Sprint / Scrum metrics in accordance with the metrics stated in the IPF Capability Delivery SOP[footnoteRef:2]. [2: Foundation GEOINT Capability Delivery Standard Operating Procedure (SOP)

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

in accordance with section 6.31 of the FS3i Base IDIQ PWS.

The contractor will tailor the Government ITDR process for all supported sub-systems and environments.

CDRL A018 - Information Technology Disaster Recovery (ITDR)

The contractor provides the capability to seamlessly integrate databases into sub-systems or systems as required by the Government.

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

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

The contractor will adhere to the Engineering Services requirements in accordance with section 6.38 of the FS3i Base IDIQ PWS.

The contractor will capture all design elements as described in Appendix C. The contractor will 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 provides the necessary engineering expertise and resources to plan, execute studies, and implement EM technical requirements and activities covered by this PWS consistent with the NGA System Engineering Plan (SEP) and industry best practices.

The contractor provides integration engineering Capabilities to integrate FG Capabilities, COTS, GOTS, FOSS, and software into the operational baseline. 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 baseline.

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 baseline.

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.

The contractor will include and register the appropriate engineering and architectural artifacts in Technical Library as they are listed in Appendix C of this Task Order for each sub-system EM.

The contractor will support Transition-In service in accordance with section 6.41 of the FS3i Base IDIQ PWS.

The contractor will present a PowerPoint version (CDRL A025) of the Transition-In Plan (CDRL A006) at the contract kick-off meeting that details the 30-60-90 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 FGS-IOS contract. As part of the transition kickoff meeting, the contractor will support the government’s task order transition readiness review checklist execution (CDRL A006).

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

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

Upon Government request, the contractor will execute a Transition-Out Plan (CDRL A012) to turn over the responsibility for all integration activities for the EM sub-systems and services.

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

Table 6-2.1: List of requirements for Software Development Services

1. Integration Services The contractor will integrate new/existing EM Capabilities/services/micro-services from development and Integration efforts/Release Trains through the DevOps pipeline into operations. Note that Developers/Sustainer Release Trains may be Government and/or other non-FS3i contractors. Already developed, operational, or commercially available hardware or software Capabilities may be integrated into existing environments / architectures.

The contractor will integrate Government-Off-The-Shelf (GOT)s, COTS, Free and Open Source Software (FOSS), microcode, and software developed by development teams into the EM operational baselines. 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 sub-system software

4. Application and database software

5. Security

The contractor will deliver an overarching Integration Management Plan (CDRL A031) 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 EM operational baselines.

The contractor will adhere to the FS3i EM TO Sustainment Services Cost Model (found in RFP Section L-10) that provides system profile information and an estimated effort required to complete an Integration task for a capability. The EM TO Cost Model for the Integration of a capability will be determined based on a combination of factors. The factors are:

a. Complexity of the systems and sub-systems to be Integrated,

b. The number and complexity of requirements involved in the Integrations, and / or

c. System Sizing i.e. number of environments and users.

The Table below is UNCLASSIFIED in its entirety.

The contractor provides updates to the master Software Library for the installed FG baseline in accordance to the CDRL A038 – Software Library Management Report.

The contractor provides Configuration Management services, including SW/HW in accordance with section 6.3 of the FS3i Base IDIQ PWS.

The contractor will collaborate with the Operations Support contractor and provide updates to the Configuration Management Plan as in accordance to the CDRL A013 - Configuration Management Plan.

CDRL A039 - Automation Deployment Instructions.

The contractor provides release management services in accordance with section 6.5 of the FS3i Base IDIQ PWS.

The contractor will develop, coordinate, and maintain the Release Plan to include any Government required NTO testing, enterprise test events, deployments, scans, external demos, quality standards, security approval (CDRL A021).

The contractor will deliver the actual plan for the release (Release Plan) 5 days after the Release Planning Event (RPE). The Plan is delivered in JIRA and .pdf copy to PMO.

The contractor will collaborate with the Operations Support contractor and provide input into the Release Plan in accordance with CDRL A021. The Release Plan is updated after each Release Planning Event (RPE).

The contractor will coordinate release planning events with all Government and Contractor stakeholders.

CDRL A021 – Release Plan CDRL A024 - Deployment Chart

The contractor will deliver an Integration Management Plan (CDRL A031) that includes and Integration Readiness Review Checklist (IRRC), The contractor will support 10 readiness reviews per year. The final data-deliverable Integration Package and the Sub-system Integration Plan (SIP) (in the formats that are described in the Technical Library), to include criteria for passing the operational readiness review.

3. The Integration Package is comprised of all relevant documents described in the Technical Library document list in Appendix C along with a completed Integration Readiness Review checklist as described in the Integration Management Plan (CDRL A031).

4. The Sub-system Integration Plan (SIP) is comprised of a Work Breakdown Structure (WBS) with associated cost (CDRL A035) that aligns with the Capability Integration Schedule (CDRL A034) and a Requirements Traceability Matrix (RTM) (CDRL A033) that corresponds to the Risk/Issues/Opportunity Register (RIOR) (CDRL A036).

The contractor will organize and facilitate a government Integration Readiness Review and invite all relevant attendees to address.

The contractor will execute and complete two Lean Six Sigma (LSS)/ Business Process Reengineering (BPR) services per contract year in accordance with section 6.8 of the FS3i Base IDIQ PWS (2 total between Integrations and Operations Support). The results will initiate a Value Engineering Change Proposal (VECP).

The contractor provides the outline of BPR / LSS accomplishments for each Program Management Review (PMR) meetings.

CDRL A042 - Continual Service Improvement (CSI)/Business Process Reengineering (BPR)

The Contractor will develop and implement cost saving initiatives, processes, and procedures during execution of all this PWS tasks throughout the course of contract performance that are intended to result in realized cost efficiencies. CDRL A022 - Value Engineering Change Proposal (VECP)

CDRL A043 - Request for Change (RFC) Management Impact Assessment.

The contractor will adhere to the DevSecOps Management services in accordance with section 6.11 of the FS3i Base IDIQ PWS.

The contractor will provision and maintain environments on each security domains for development efforts as defined by the Government.

The contractor will lead and provide expertise during testing and deployment of GOTS, COTS, FOSS, and new or changed software to the EM operational baselines.

The contractor will perform integration services on all security domains as required.

The contractor will execute all integration tasking required for delivery of new/updated EM software baselines from one environment to the next to expose the Capabilities/services to the users for testing and deployment into operations.

The contractor will perform the required integration tasks for development as outlined in the deployment instructions as defined in IPF Capability Delivery SOP.

The contractor will participate in analysis of system performance metrics and provide recommendations to gain efficiencies (CDRL A008) where applicable.

The contractor will ensure integration activities meet program and product owner requirements.

The contractor provides updates into the configuration management system about the hardware and software changes to the operational baseline because of the contractor’s actions.

The contractor will update the Version Description Document for the integrated portion of the whole. (CDRL A019).

The contractor will develop an Integrated Test Program and associated plans, events, procedures, and checklists scaled appropriate to the baseline. Deliver an integration Test Readiness Review checklist (CDRL A027).

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

The contractor’s scenarios will 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 will 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.

CDRL A044 - Integration Test Report

The contractor will use the Government directed Knowledge Management process in accordance with section 6.15 of the FS3i Base IDIQ PWS.

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

The contractor will build out and establish a knowledge management program within 90 calendar days. The system will be based on best practices to meet the Government and stakeholders needs, and must be implemented for all baselines in a centralized location. It will 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 will keep it up-to-date per metric(s) in Appendix D.

The contractor will adhere, follow, leverage, or integrate all baselines with NGA Enterprise Service plus.

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

The contractor provides the Performance Metrics as they are listed in Appendix D of this task order.

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

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

The contractor will adhere to the Metric Collection and Analysis requirements in accordance with section 6.27 of the FS3i Base IDIQ PWS.

The contractor provides the capability to collect cost, operational and performance metrics for sub-systems, sub-system components, and Cloud infrastructure.

The contractor will collect Sprint / Scrum metrics in accordance with the metrics stated in the IPF Capability Delivery SOP[footnoteRef:3]. [3: Foundation GEOINT Capability Delivery Standard Operating Procedure (SOP)

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

in accordance with section 6.31 of the FS3i Base IDIQ PWS.

The contractor will tailor the Government ITDR process for all supported sub-systems and environments.

CDRL A018 - Information Technology Disaster Recovery (ITDR)

The contractor provides the capability to seamlessly integrate databases into sub-systems or systems as required by the Government.

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

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

The contractor will adhere to the Engineering Services requirements in accordance with section 6.38 of the FS3i Base IDIQ PWS.

The contractor will capture all design elements as described in Appendix C. The contractor will 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 provides the necessary engineering expertise and resources to plan, execute studies, and implement EM technical requirements and activities covered by this PWS consistent with the NGA System Engineering Plan (SEP) and industry best practices.

The contractor provides integration engineering Capabilities to integrate FG Capabilities, COTS, GOTS, FOSS, and software into the operational baseline. This includes at the minimum:

11. Solution design.

12. Design review with the Government and contractor stakeholders.

13. Development of solution.

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

15. Acceptance testing, a Government managed verification, and validation of the integrated solution.

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

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

18. Application Program Interface (API) management

19. 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 baseline.

20. 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.

The contractor will include and register the appropriate engineering and architectural artifacts in Technical Library as they are listed in Appendix C of this Task Order for each sub-system EM.

The contractor will support Transition-In service in accordance with section 6.41 of the FS3i Base IDIQ PWS.

The contractor will present a PowerPoint version (CDRL A025) of the Transition-In Plan (CDRL A006) at the contract kick-off meeting that details the 30-60-90 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 FGS-IOS contract. As part of the transition kickoff meeting, the contractor will support the government’s task order transition readiness review checklist execution (CDRL A006).

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

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

Upon Government request, the contractor will execute a Transition-Out Plan (CDRL A012) to turn over the responsibility for all integration activities for the EM sub-systems and services.

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

Table 6-3.1: List of requirements for Integration Services

1. Software Maintenance Services The contractor provides Software Maintenance Service for all capabilities listed in Section 5 of this TO as well as the requirements listed in all addendums in section 12.

Tables 6-2 and 6-2.1 represents EM Software Maintenance services supporting the Agency with Safety of Navigation data production and other mission critical activities. The Contractor must provide daily Software Maintenance services for every EM sub-system Capability as listed in Tables 6-3 and 6-3.1 with the contract Capacity provided. Deviations within the priorities of work and/or new priorities of work not listed in the Tables below may be directed by the PM or the COR within the Capacity and scope of the Contract.

This table is Unclassified in its entirety.

The contractor provides Demo Support every six months.

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

The contractor will 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.

The Contractor will use the Government provide JIRA and Confluence

Table 6.4.1: Software Maintenance requirements

1. Operations Support Services The contractor provides Operations Support Service for all capabilities listed in Section 5 of this TO as well as the requirements listed in all addendums in section 12.

Tables 6-3 and 6-3.1 represents EM Operational Capabilities supporting the Agency with Safety of Navigation data production and other mission critical activities.