Sea_Task_Order_Rev1_20240829.docx

UNCLASSIFIED

UNCLASSIFIED

PERFORMANCE WORK STATEMENT (PWS)

For

Foundation Sustainment Support, Software and Integration (FS3i) Sea Task Order Aug 29, 2024 Version 1.0

Table of Contents

1 (U) Purpose

(U) The contract is required comply, adhere, and execute all requirements and services outlined in this Task Order (TO) Performance Work Statement (PWS).

(U) This PWS defines expectations and requirements needed to sustain the Foundation GEOINT (FG) Integrated Program Office (IPF) Foundation Sustainment Services and integration (FS3i) for the Maritime Safety of Navigation.

(U) This PWS also establishes the acquisition framework for delivering required services for the NGA Source Operations & Management Directorate's Foundation GEOINT Group (SF), Maritime Safety of Navigation, and its mission partners.

(U) The main objective is for the contractor to design and execute an agile support construct to provide the optimal Maritime 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 Maritime Safety Office produces timely, relevant, validated, and accessible worldwide Maritime foundational Geospatial Intelligence, on-line and on-demand, to meet Safety of Navigation at Sea requirements, joint military operations support, international obligations, and other contingency requirements, for the Department of Defense, other US Government Agencies, and our Allied Partner nations. Through formal agreements and partnerships with hydrographic data providers, both domestic and foreign, the Office collects, catalogues, analyzes, and exploits source information to create and update a large suite of navigational products in digital and printed form.

(U) This TO is designed to satisfy the IT mission requirements located in the Maritime and Science Program Epics Production Content Management Ver 1.0, and all future versions and revisions authorized by SF.

(U) The Integrated Program Office will identify and prioritize which systems will be included within this TO.

3 (U) Scope

(U) The FS3i Sea TO will align with the Work Breakdown Structure (WBS) of the FS3i Base IDIQ PWS.

· (U) It is required to provide services for WBS 1.0 Program Management, WBS 2.0 Software Development, WBS 3.0 Integration, WBS 4.0 Software (SW) Maintenance, WBS 5.0 Operations Support Sustainment, WBS 6.0 Foundation GEOINT Information Technology Procurement, and WBS 7.0 Foundation GEOINT COTS Software Procurement.

(U) It is required to comply with, adhere to, and execute all requirements and services outlined in this Task Order PWS.

(U) It is required to update the Agile Development Management Plan.

4 (U) Current Environment and Constraints

(U) It is required to follow the guidance and procedures outlined in the IPF Capability Delivery Standard Operating Procedure (SOP) outlined in the FS3i Base PWS IDIQ.

(U) It is required to work and obtain a waiver with IPF Engineering regarding exceptions or changes to any IPF/NGA standards.

(U) It is required to establish productive teaming arrangements and efficient working relationships with other Sea 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) It is required to 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 onboarded and properly postured for operational readiness within the NGA infrastructure.

5 (U) Tasks

(U) It is required to adhere to all WBS requirements identified in this PWS. Modifications (MOD) to this PWS will be provided for additional Maritime IT capabilities when required and approved by SFH.

(U) It is required to use AGILE methodology to provide sustainment services for the following Source Maritime Capabilities (refer to Appendix L for a description of each capability) as listed below:

· Bathymetric Production System (BPS)

· WBS 1.0: Program Management

· WBS 5.0: Operations Support

· CARIS ENC Desktop (CDE) UPE

· WBS 1.0: Program Management

· WBS 5.0: Operations Support

· Digital Nautical Charts (DNC)

· WBS 1.0: Program Management

· WBS 5.0: Operations Support

· Electronic Navigational Chart S57 (ENC S57) & Chart on Demand (COD)

· WBS 1.0: Program Management

· WBS 5.0: Operations Support

· Enterprise Engine - Notice to Mariners (E2-NTM)

· WBS 1.0: Program Management

· WBS 4.0: Software Maintenance

· WBS 5.0: Operations Support

· ePublisher

· WBS 1.0: Program Management

· WBS 5.0: Operations Support

· Geospatial Hub - Maritime (GHUB) as a Service (GMaaS)

· WBS 1.0: Program Management

· WBS 5.0: Operations Support

· List of Lights (LoL)

· WBS 1.0: Program Management

· WBS 5.0: Operations Support

· Littoral Planning Charts (LPC)

· WBS 1.0: Program Management

· WBS 5.0: Operations Support

· Maritime Source Processing System (MSPS)

· WBS 1.0: Program Management

· WBS 4.0: Software Maintenance

· WBS 5.0: Operations Support

· Mobile Offshore Drilling Units (MODU)

· WBS 1.0: Program Management

· WBS 5.0: Operations Support

· Navigation Safety System (NSS)

· WBS 1.0: Program Management

· WBS 4.0: Software Maintenance

· WBS 5.0: Operations Support

· Navigational Safety System (N2)

· WBS 1.0: Program Management

· WBS 2.0: Software Development

· WBS 3.0: Integration

· WBS 4.0: Software Maintenance

· WBS 5.0: Operations Support

· Performance Measurements and Business Intelligence (PMBI) and Performance Reporting Subsystem (PRS)

· WBS 1.0: Program Management

· WBS 5.0: Operations Support

· Radio Navigational Aids (RNA)

· WBS 1.0: Program Management

· WBS 5.0: Operations Support

· Source Maritime Processing System (SMAPS)

· WBS 1.0: Program Management

· WBS 4.0: Software Maintenance

· WBS 5.0: Operations Support

· Submarine Electronic Navigational Chart (SMENC)

· WBS 1.0: Program Management

· WBS 5.0: Operations Support

· Tactical Ocean Data (TOD)

· WBS 1.0: Program Management

· WBS 5.0: Operations Support

· World Port Index (WPI)

· WBS 1.0: Program Management

· WBS 5.0: Operations Support

6 (U) Services

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

(U) Program Management Services – WBS 1.0

(U) It is required to meet the Program Management Service requirements listed in the table below and the associated appendices.

(U) This table is Unclassified.

It is required to arrange and host a task order kick-off meeting within 15 business days of award.

The contractor Kick-off meeting presentation includes the following content:

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

· Additional topics proposed by the Government and Contractor.

It is required to provide a monthly PMR for the IPF / SFH office.

It is required to hold TEMs, facilitate capturing requirements, and be responsive in delivering proposals in support of the most efficient RFP process.

It is required to host a Design Review and Presentation (DRP) with key stakeholders.

· Technical Program Manager

· Deputy Program Manager

· Integration Engineering Lead

· Operation and Sustainment Lead

· Cyber Security Lead

· Software Maintenance lead for Task Appendix E contains job descriptions and job qualifications for the key personnel.

It is required to adhere to the Classified Work performance security requirements in accordance with section 7.7.1 of the FS3i Base IDIQ PWS.

It is required to adhere to the Unclassified Work performance security requirements in accordance with section 7.7.2 of the FS3i Base IDIQ PWS.

Table 6.1 (U) List of Program Management Services

(U) Software Development – WBS 2.0

(U) It is required to develop/enhance new/existing Sea capabilities/services/micro-services for integration efforts into/Release Trains through the DevOps pipeline into operations.

(U) It is required to deliver an overarching Agile Development Management Plan that describes development, deliverables guidelines and templates, as well as integration roles / responsibilities, and a checklist that ensures successful integration of newly developed software or software fixes for the Sea operational capabilities.

(U) It is required to meet the Software Development Service requirements listed in the table below and the associated Appendices.

(U) This table is Unclassified.

It is required to provide Configuration Management services, including SW/HW in accordance with section 6.3 of the FS3i Base IDIQ PWS.

It is required to adhere to the DevSecOps Management services in accordance with section 6.11 of the FS3i Base IDIQ PWS.

It is required to provision and maintain environments on each security domains and environments for development efforts as defined by the Government.

It is required to lead and provide expertise during development, testing and integration of new or changed software for Sea operational capabilities.

It is required to perform the required development tasks for integration as outlined in the deployment instructions as defined in IPF Capability Delivery SOP.

It is required to ensure development activities meet program and product owner requirements.

It is required to provide updates into the configuration management system about the hardware and software changes to the operational baseline.

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

It is required to produce a Development 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.

It is required to participate in preparation and delivery of the services and provide status tracking.

It is required to participate in tracking the project status, open incidents, and other anomalies.

It is required to adhere to the Engineering Services requirements in accordance with section 6.38 of the FS3i Base IDIQ PWS.

It is required to capture appropriate design elements as described in Appendix C.

It is required to draft an Integration Design Review Presentation (IDRP) 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 informed decisions in systems architecture as needed before building proceeds.

It is required to provide the necessary engineering expertise and resources to plan, execute, and implement Sea technical requirements and activities covered by this PWS consistent with the NGA System Engineering Plan (SEP) and industry best practices.

It is required to provide development and engineering capabilities to integrate developed capabilities 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 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 associated with 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. Provide post release metric collection for analysis of 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 operation/production.

Table 6.2 (U) List of requirements for Software Development Services

(U) Integration Services – WBS 3.0

(U) It is required to integrate new/existing Sea capabilities/services/micro-services from development and integration efforts/Release Trains through the DevOps pipeline into operations. Note: 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.

(U) It is required to integrate Government-Off-The-Shelf (GOTS), COTS, Free and Open Source Software (FOSS), microcode, and software developed by development teams into the Sea 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 database software

5. Security

(U) It is required to 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 Sea 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) It is required to meet Integration Service requirements listed in the table below and the associated appendices.

(U) This table is Unclassified.

It is required to provide Configuration Management services, including SW/HW in accordance with section 6.3 of the FS3i Base IDIQ PWS.

It is required to collaborate with the Operations Support contractor and provide updates to the Configuration Management Plan.

It is required to provide release management services in accordance with section 6.5 of the FS3i Base IDIQ PWS.

It is required to develop, coordinate, and maintain the Release Plan to include any Government required NTO testing, enterprise test events, deployments, scans, external demos, quality standards and security approval.

It is required to 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.

It is required to collaborate with the Operations Support contractor and provide input into the Release Plan. The Release Plan is updated after each Release Planning Event (RPE).

It is required to coordinate release planning events with the Government and Contractor stakeholders.

It is required to deliver an Integration Management Plan that includes and Integration Readiness Review Checklist (IRRC), It is required to support readiness reviews. The final data-deliverable Integration Package and the Subsystem Integration Plan (SIP) to include criteria for passing the operational readiness review.

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.

The Subsystem Integration Plan (SIP) is comprised of a Work Breakdown Structure (WBS) with associated cost (that aligns with the Capability Integration Schedule and a Requirements Traceability Matrix (RTM) that corresponds to the Risk/Issues/Opportunity Register (RIOR).

It is required to organize and facilitate a government Integration Readiness Review and invite all relevant attendees.

It is required to 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).

It is required to provide the outline of BPR / LSS accomplishments for each Program Management Review (PMR) meetings.

It is required to 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.

It is required to adhere to the DevSecOps Management services in accordance with section 6.11 of the FS3i Base IDIQ PWS.

It is required to provision and maintain environments on each security domains for development efforts as defined by the Government.

It is required to lead and provide expertise during testing and deployment of GOTS, COTS, FOSS, and new or changed software to the Sea operational baseline.

It is required to perform integration services on all security domains as required.

It is required to execute all integration tasking required for delivery of new/updated Sea software baselines from one environment to the next to expose the capabilities/services to the users for testing and deployment into operations.

It is required to perform the required integration tasks for development as outlined in the deployment instructions as defined in IPF Capability Delivery SOP.

It is required to participate in analysis of system performance metrics and provide recommendations to gain efficiencies where applicable.

It is required to ensure integration activities meet program and product owner requirements.

It is required to provide updates into the configuration management system about the hardware and software changes to the operational baseline because of the contractor’s actions.

It is required to update the Version Description Document for the integrated portion of the whole.

It is required to develop an Integrated Test Program and associated plans, events, procedures, and checklists scaled appropriate to the baseline. Deliver an integration Test Readiness Review checklist.

It is required to develop scenarios and checklist in support of Government-managed Independent Verification and Validation (IV&V) events.

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

It is required to 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.

It is required to use the Government directed Knowledge Management process in accordance with section 6.15 of the FS3i Base IDIQ PWS.

It is required to provide input and track DRs, and Root cause in the Knowledge Management system.

It is required to 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 appropriate documents, service tickets, help desk inquiries, technical library documentations, and causes of major operational outages.

It is required to adhere, follow, leverage, or integrate all baselines with NGA Enterprise Service plus.

Per the Government direction, it is required to perform Root Cause/Trend Analysis.

It is required to provide the Performance Metrics as they are listed in Appendix B of this task order.

It is required to participate in preparation and delivery of the services and status tracking.

It is required to participate in tracking the status of projects, open incidents, and other anomalies.

It is required to adhere to the Metric Collection and Analysis requirements in accordance with section 6.27 of the FS3i Base IDIQ PWS.

It is required to provide the capability to collect cost, operational and performance metrics for subsystems, subsystem components, and Cloud infrastructure.

It is required to collect Sprint / Scrum metrics in accordance with the metrics stated in the IPF Capability Delivery SOP[footnoteRef:2]. [2: (U) Foundation GEOINT Capability Delivery Standard Operating Procedure (SOP)

It is required to provide the capability to manage collected metrics and provide analysis reports using existing tools, and dashboards.

It is required to tailor the Government ITDR process for all supported subsystems and environments.

It is required to provide the capability to seamlessly integrate databases into subsystems or systems as required by the Government.

It is required to plan, implement, test, and deploy databases in the testing and development environments for all security domains in the Cloud or On-premises

It is required to provide the capability to seamlessly integrate FG capabilities, GOTS, COTS, FOSS, and software to the Government designated Cloud environments.

It is required to adhere to the Engineering Services requirements in accordance with section 6.38 of the FS3i Base IDIQ PWS.

It is required to capture relevent design elements as described in Appendix C. It is required to draft an Integration Design Review Presentation (IDRP) 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.

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

It is required to provide 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.

It is required to 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 Sea subsystem.

It is required to support Transition-In service in accordance with section 6.41 of the FS3i Base IDIQ PWS.

It is required to present a PowerPoint version of the Transition-In Plan 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 existing external contracts. As part of the transition kickoff meeting.

It is required to support the government’s task order transition readiness review checklist execution.

It is required to provide weekly (or more often as needed) transition update teleconferences meetings from Key Personnel to IPF Sustainment Program Office.

It is required to arrange and facilitate a government transition readiness review with the incumbent and the government within 30 days of contract award.

It is required to present an updated transition checklist for the team to review. The objective is to obtain government authority to assume full responsibility for the Sea Task Order operations.

Upon Government request, It is required to execute a Transition-Out Plan to turn over the responsibility for all integration activities for the Sea subsystems and services.

It is required to be given 30 days to produce the transition-out plan and 60-days to transition the responsibilities.

Table 6.3 (U) List of requirements for Integration Services

(U) Software Maintenance Services – WBS 4.0

(U) It is required to meet the Software Maintenance Service requirements listed in the table below and the associated appendices.

(U) It is required to provide software maintenance support for Sea capabilities and their respective operational baselines. This includes maintaining the baseline code and enabling the code to deliver the mission requirements at the optimum level of operational performance while meeting or exceeding the availability requirements.

(U) All development of new capabilities performed by another contract external to the Government managed environments and will be delivered periodically to the recipient of this Task Order for software maintenance and operations support. In addition to the periodic delivery, the development contract is expected to deliver a new release in accordance with the deployment cadence as designated by the Government.

(U) This table is Unclassified.

It is required to update any existing Test Programs, associated plans, events, procedures, and checklists to include the appropriate Sea testing requirements.

It is required to produce and present a Test Plan at the Test Readiness Review.

It is required to deliver an updated test plan to support each test event.

It is required to support the Government-managed Independent Verification and Validation (IV&V) test scenarios.

It is required to produce a 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.

Additional SMAPS requirements in Appendix G.

Additional E2-NtM requirements in Appendix I.

Additional SMAPS requirements in Appendix H.

Additional MSPS requirements in Appendix H.

Additional E2-NtM requirements in Appendix I.

Additional NSS/N2 requirements in Appendix J.

It is required to apply security patches to prevent a security breach.

Per Government direction, it is required to draft a Design Review Presentation (DRP) and host the applicable number of design review sessions with the Government and contractor stakeholders (i.e., operations support and development contractors, and any other contractor that supports the Sea Program Office) for review and approval.

It is required to apply appropriate upgrades to Sea systems to prevent an outage, or performance and functionality degradation.

Additional NSS/N2 requirements in Appendix J.

It is required to recommend replacements for old and outdated software.

Per Government direction, it is required to draft a Design Review Presentation (DRP) and host the applicable number of design review sessions with the Government and contractor stakeholders (i.e., operations support and development contractors, and any other contractor that supports Sea Program Office) for review and approval.

Additional MSPS requirements in Appendix H.

Additional E2-NtM requirements in Appendix I.

Additional NSS/N2 requirements in Appendix J.

Additional NSS/N2 requirements in Appendix J.

It is required to use the Government provided JIRA and Confluence.

The contractor’s test scenarios trace to all system and application requirements.

Table 6.4 (U) Software Maintenance requirements

(U) Operations Support Services – WBS 5.0

(U) It is required to provide operations support to Sea Capabilities, monitor required operational resources including databases, interfaces, and operational status during designated operations hours. Once an outage or degradation is observed, take all steps required to identify the cause, make notifications, and fix it or submit the proper trouble tickets as required. Through user engagement, optimize the user dashboard.

(U) It is required to funnel relevant dashboard information to one dashboard on the TOP SECRET network.

(U) The contractor, per Government direction, is required to deliver a report that covers Sea TO sub-system gaps, manpower, monitoring requirements, software baselines, IT requirements, and Reliability, Availability and Maintainability (RAM) discovered during the Product Support Strategy Survey and Assessment (PSA).

(U) The contractor, per Government direction, is required to deliver an Operations Support Plan (OSP) that addresses all the requirements discovered during the Product Support Strategy Survey and Assessment (PSA).

(U) It is required to use the DoD Product Support Manager Guidebook as a guide to draft the OSP. It is required to update the OSP after additional sub-systems are added to the task order.

(U) It is required to use the DevSecOps pipeline to deploy Sea Capabilities from DEV/TEST into operations after the Certification to Field is approved. This may include, at the direction of the Government, technical insertions of FG Capabilities/services developed elsewhere.

(U) It is required to continuously to optimize the cost of using cloud while improving the user experience

(U) It is required to meet the Operations Support Service requirements listed in the table below and the associated appendices.

(U) This table is Unclassified.

It is required to provide a plan and technical approach for optimizing service performance under the contractor’s care. The plan is required to address, at the minimum, the contractor’s approach for:

1. Performance monitoring and data collection processes for on premises and the cloud resources:

2. Identifying performance monitoring data collected and their data definitions and usage.

3. Refining and optimizing collection and processing of performance monitoring data.

4. Real time end-to-end software performance monitoring.

5. Seamlessly navigating the entire software service stack (on premises, Cloud, application code, containers, databases, infrastructure, network links etc.,) for:

5.a Visibility into the heath of entire software stack.

5.b Identification of performance bottlenecks.

5.c Generating alerts, alarms, and warnings.

5.d Tracking software performance to identify performance improvements, degradations, and any changes in the performance baseline because of a major release or changes to the operational baseline.

Measuring and tracking user experience and the user journey through the entire software service stack.

It is required to provide performance and cost optimizations for Sea systems.

It is required to provide Software Library Management services in accordance with section 6.2 of the FS3i Base IDIQ PWS.

It is required to maintain and provide updates to the master Software Library for the installed FG baselines.

It is required to maintain and manage a configuration control program for the Sea operational baselines, and the multiple baselines that may lead to an operational baseline such as those developed for sub-systems being integrated into FS3i.

It is required to update the configuration management plan to include Sea systems.

It is required to provide a Version Description Document/Software Version Description Document for relevent Sea capabilities.

It is required to provide the capability to model a collection of related Cloud resources, provision them quickly and consistently, and manage them throughout their lifecycles, by treating infrastructure as code.

Additional E2-NtM requirements in Appendix J.

It is required to provide release management services in accordance with section 6.5 of the FS3i Base IDIQ PWS.

It is required to develop, coordinate, and maintain the release schedule to include any Government required NTO testing, stakeholder engagement, enterprise test events, deployments, scans, quality standards, security approval.

It is required to deliver the updated Deployment Chart in Excel spreadsheet 5 days after the RPE event.

It is required to deliver the actual plan for the release (Release Schedule) 5 days before the release of capability into operations It is required to deliver the Release Schedule to PMO in a Government designated media (i.e., JIRA, SharePoint, and Confluence).

It is required to collaborate with the Government and contractor stakeholders (PMO, operations support, development contractor, etc.) and update the Release Schedule based on their inputs.

It is required to provide Release Deployment and Verification and Validation (IV&V) Workflows.

It is required to update the configuration management system by the information from the release.

It is required to provide RM metrics and explanations for any anomaly (i.e., software issues, the version of a component in test and production were not compatible). These include but are not limited to:

· Number of break fix done before the release

· Number of break fix during executing testing scenarios.

· Number of outages caused by a release within two weeks of the release

· Number of Incidents caused by a release within two weeks of the release

· Number of releases delivered on time for QA / Test

· Number of releases delivered on time for Production

· Number of releases successfully deployed to production on schedule and without a glitch

· Down time due deploying code to production

· Number of emergency release

· Customer and stakeholder’s satisfaction

It is required to coordinate and manage backlog grooming sessions with the Government and contractor stakeholders to support updating and prioritized backlog for relevant Sea capabilities and services in operations.

It is required to facilitate Government Readiness Review sessions with the Government and contractor stakeholders.

It is required to provide Test Readiness Reviews (TRR) check list for the developed software that is ready to be tested for deployment.

It is required to provide an Operational Readiness Review (ORR) check list for developed software that is ready to be deployed.

It is required to execute and complete two Continual Service Improvements (CSI) / Business Process Reengineering (BPR) services per contract year in accordance with section 6.8 of the FS3i Base IDIQ PWS). The results is required to initiate a VECP.

It is required to provide the outline of BPR / CSI accomplishments for each Program Management Review (PMR) meetings.

It is required to provide an actionable recommendation to reduce the cost of using Cloud services while delivering Sea mission requirements.

It is required to provide an actionable recommendation to improve delivery of services to Sea stakeholders and users while meeting Sea systems mission requirements.

It is required to provide VECP services in accordance with section 6.9 of the FS3i Base IDIQ PWS.

It is required to develop and implement cost saving initiatives, processes, and procedures during execution of this PWS tasks throughout the course of contract performance that are intended to result in realized cost efficiencies.

It is required to provide DevSecOps Management services in accordance with section 6.11 of the FS3i Base IDIQ PWS.

It is required to use the DevSecOps pipeline to deploy Sea capabilities from DEV / TEST environment into operations.

It is required to provide skills, expertise, and adequate resources to provision, maintain, and operationalize the Cloud environments including Sand Box, Development, Testing, and Operational environments for all security domains.

It is required to provide the skills, expertise, and adequate resources needed to meet mission requirements for testing, and deployment of new or changed systems that may include code, software, GOTS, COTS, and FOSS, to the operational baseline.

It is required to meet all security requirements for environments, COTS, GOTS, FOSS, software, code. This may include but is not limited to:

· Applying security patches.

· Automating day-to-day security tasks, configurations security scans.

· Adhering to all NGA security requirements.

It is required to develop, update, and maintain Release Plan, collaborating with the Government and contractor stakeholders, including development and integration teams and update the Release Plan for each new release.

It is required to execute processes required for delivery of updated Sea software baselines from one environment to the next to expose the capabilities/services to the users for testing and deployment into operations.

It is required to collaborate to refine and perform the required tasks for Operations Support outlined in the deployment instructions as defined in IPF Capability Delivery SOP.

It is required to create and maintain a progress tracker to inform Government of status of each step of testing, deployment, and operational activities.

It is required to provide analysis of operational performance metrics (i.e., network response time) and provide recommendations to gain efficiencies where applicable.

It is required to provide input and track DRs, and Root cause in the Government designated Knowledge Management system (SharePoint, Confluence, JIRA, etc.)

It is required to store all baselines in a centralized location within the Knowledge Management system.

It is required to capture and maintain the current versions of, documents, service tickets, help desk inquiries, technical libraries documentations, analysis and trouble shootings, and causes of operational outages.

It is required to keep it up to date per metric(s) in the Appendix B of this task order.

It is required to have a process to manage the content of the Knowledge management system this include:

· An intuitive organization that facilitates a quick and accurate search results.

· Provide a clutter free knowledge Management experience.

· Provide the capability to archive and delete for the content that are not access for a given period, or a user wants to change the state to archive or delete.

It is required to adhere, follow, leverage, or integrate operational baselines with NGA Enterprise Service plus.

It is required to track incidents (INCs), problem investigations (PBIs) and Discrepancy Reports (DRs) that affect Sea systems development, test, and operational baselines.

When required, it is required to perform Root Cause/Trend Analysis.