FDM_Draft_PWSv2.docx

UNCLASSIFIED

PERFORMANCE WORK STATEMENT (PWS)

For

Foundation Dissemination Modernization (FDM)

7 June 2024

Table of Contents Contents

(U) Purpose

(U) The National Geospatial-Intelligence Agency (NGA) is both a Combat Support Agency (CSA) of the DoD and a member of the United States Intelligence Community (IC). NGA provides critical support to the national decision-making process and the operational readiness of America’s military forces. As a member of the IC, the NGA mission is to provide timely, relevant, and accurate GEOINT in support of National Security objectives. NGA is responsible for GEOINT dissemination. To remain operationally effective within a fluid, unconventional domain, NGA Source (S) and its mission partners in Dissemination of Mapping, Charting and Geodesy (MC&G) must advance in its capability to capture and share its NGA Source products at the speed of our customer’s need. The GEOINT user community requires the capability to easily and efficiently discover and access Foundation GEOINT (FG) Contents per security domain.

(U) Two of the Source offices supported will be the GEOINT Information Group (ST) and Foundation GEOINT Group (SF).

(U) The mission of ST is to support critical missions by digitalizing and managing global GEOINT; leading and defining the modernization of Source content dissemination. Their functions include, but are not limited to:

· Improve access and integrity of authoritative GEOINT information to support customer requirements.

· Provision GEOINT products and services required for mission planning, safety of navigation, geodetic accuracy and targeting support in connected, semi-connected, and disconnected environments.

· Expose historical imagery across multiple security domains.

(U) The mission of SF is to provide timely and accurate data, products, applications, and services that are dynamically updated, easily discoverable and consumable, and delivered at the point of warfighter and analyst need. The Foundation GEOINT Group provides data, products, and services describing the earth’s physical and cultural characteristics. Foundation GEOINT includes topography, elevations, precise imagery, geodesy, GeoNames and boundaries, human geography, and aeronautical and maritime safety of navigation. The collection, analysis, and interpretation of data support intelligence, defense, civil, and commercial needs.

(U) The purpose of this Performance Work Statement (PWS) is to define the expectations and requirements needed to conduct modernization and development in an effort to ingest, condition, catalog, and disseminate Foundation GEOINT products to users worldwide. NGA strives to improve overall quality, responsiveness, and performance of the user experience and to meet MC&G ingest, catalog, releasability and product dissemination demand.

(U) Background

(U) Foundation GEOINT Dissemination is made up of multiple sub-systems and services that are supported within the Legacy Gateway and the modernized Source Content Dissemination Services (SCDS). The Government’s current overall capabilities for dissemination support multiple functional areas:

· Data Ingest and Management

· Condition and Catalog

· Disclosure and Release

· Dissemination Services

· User Interface

(U) Legacy Gateway software code is 25+ years old with substantial technical debt. The current system contains numerous manual processes that are labor intensive that requires modernization to automate and reduce the time associated to complete certain functions. Components on-premise include, but are not limited to:

· Data Ingest, Validation, and Management

· Geospatial Web Services (GWS)

· Enterprise File Delivery (EFD)

· Business Websites and Applications

· Geospatial Tile Generation

· Business Websites and Applications

(U) While the Gateway resides on-premise, the future architecture shall be cloud native. The Source Content Dissemination Services (SCDS) shall be modular and modernized to be technologically relevant. Components within Geometric and Geospatial Product Modernization (GGPM) Cloud include, but are not limited to:

· Source Content Dissemination Services (SCDS)

· Foundation GEOINT Discovery and Release Tool (FGDRT)

· User Interface (maiNGAte)

· Business Websites and Application Programming Interfaces (APIs).

(U) SCDS has already reached Initial Operational Capability (IOC) and provides ingest, maintenance, and dissemination services needed to support the Source Foundation Catalog (SFC) and similar cloud functionality critical to system operation.

(U) Foundation GEOINT Discovery and Releasability Tool (FGDRT) has reached IOC and provides the business workflow to adjudicate and release NGA GEOINT data, to and from foreign partners of NGA, and enables the dissemination of NGA standard geospatial products by capturing disclosure and release (D&R) decisions through the dissemination services. FGDRT is integrated with GGPM so that data obtained from SCDS has the proper release and disclosure information. Operationalizing FGDRT is highly dependent on SCDS architecture, resolution of the Open Data Store (ODS) data access and data flow blocker, and sufficient/consistent metadata to enable adjudication of release decisions.

(U) NGA’s modernized SCDS architecture allows for an easy to use, unified point of access for NGA customers (domestic and foreign) to discover and retrieve Source Foundation products. FGDRT allows for the disclosure and release of geospatially enabled objects to identity-based access users. FGDRT is a cloud based, data-type agnostic GEOINT requirements adjudication application that is architecturally integrated as a “system of systems” within the SCDS. Unified access to Source Foundation products through SCDS will replace numerous customer-specific access points that created situations in which some users knew where to find some products, while others did not. It will also result in simplification of dissemination processes for product development communities.

(U) The User Interface currently developed to be SCDS’s front end is maiNGAte, a capability developed under an agreement with the Naval Research Lab (NRL). The maiNGAte is a web-based, dynamically updated landing page that enables users to search, discover, access and order Source Foundation GEOINT products/data from both Government and Commercial. The maiNGAte is going through Test Readiness Reviews (TRR) / Operational Readiness Reviews (ORR) and expected to reach IOC in Q3FY24. This will be the Source platform that consolidates the search, discovery, ordering and dissemination functions of multiple Web sites and portals for Source Foundation products, data and imagery.

(U) SCDS requires integration with other systems such as ODS and Map of the World (MoW).

(U) The terms product-centric and data-centric are used differently between the dissemination environment and the production environment.

· Product-Centric: Within the production environment, product-centric describes the process of maintaining products. Within the dissemination environment, the term product-centric describes the set of services to access the Foundation GEOINT file-based content products and publications, regardless of what production environment the files were created in.

· Data-Centric: Within the production environment, data-centric describes the process of maintaining data within a data management system. Within the dissemination environment, the term data-centric describes the set of services to access the Foundation GEOINT data hosted within a database (e.g., raw FG data).

(U) Current Environment and Constraints

(U) The contractor shall adhere, leverage, and integrate with existing NGA Enterprise services such as the GGPM environment, NGA Confluence, NGA JIRA, NGA Security Pipeline, service desk, and Service Plus.

(U) To-Be High level SCDS Architecture

(U) Multiple micro-services make up SCDS. They are modular and integrated together to complete the dissemination of FG Products to end users.

(U) Scope

(U) The main objective of this requirement is for the contractor to modernize a system to provide the optimal user experience and become a trusted Information Technology (IT) and Source mission partner essential for the daily dissemination of MC&G products. SCDS shall be modular and modernized to be technologically relevant. SCDS will provide an easy-to-use, unified point of access for NGA customers (domestic and foreign) to discover and retrieve Source Foundation products.

· Data Ingest and Management

· Condition and Catalog

· Disclosure and Release

· Dissemination Services

· User Interface

(U) The contractor shall design, implement and continually refine a combination of Program Management process-driven initiatives in order to improve overall quality, responsiveness, and performance of the user experience and to meet MC&G ingest, catalog, releasability and product dissemination demand.

(U) Performance Requirements

(U) The contractor shall provide technical assessments, research, development, testing, integration, operation sustainment, and other required activities that leverage Commercial Off-the-Shelf (COTS), Government Off-the-Shelf (GOTS), Free and Open Source Software (FOSS), NGA’s DevOps toolkit and other technology required to modernize, operate and sustain NGA mission-related efforts.

(U) The contractor shall provide technical expertise to accomplish the capabilities described in this PWS. The Dissemination offering encompasses multiple GEOINT content functions and capabilities which require modernization. The Contractor shall expand the SCDS capacity to ingest, condition, provision, discover, retrieve and deliver additional Source Foundation products, or entirely new product lines from wider NGA

(U) Research, Development, Testing, and Evaluation (RDT&E)

(U) The RDT&E scope includes two service categories: Legacy System Modernization and New Feature Development. Legacy System Modernization consists of:

· Reviewing and assessing the status of the system's configuration control, documentation, system architecture/design/code structure, and tools and processes

· Identifying deficiencies, weaknesses and gaps to end state goals

· Providing recommendations to address deficiencies and weakness, and how best to achieve the desired end state goals

· Developing, testing, and delivering Government approved modernizations New Feature Development may apply to Legacy Systems and new systems delivered by other NGA Organizations that have achieved Minimum Viable Product that require improvements and enhancements, which consists of:

· Services to develop and produce new software code to provide capabilities that satisfy new or existing requirements.

· Working closely with Government Subject Matter Experts (SME) to review and manage Program/Project Epics and User Stories in the Program Backlog

· Documenting and estimating the Features to implement the highest priority User Stories

· Designing, developing, testing, and delivering Government approved features

(U) The contractor shall integrate new/existing Dissemination Capabilities/services/micro-services from development and Integration efforts through the NGA CORE DevOps pipeline into operations.

(U) Operations and Sustainment (O&S)

(U) The Contractor shall perform Operations and Sustainment. The Contractor shall perform Operations as defined below:

· Operations: Execution of support to meet the performance and other defined requirements of the system, application, data repository or service in an efficient manner.

(U) The Contractor shall perform all elements of Sustainment as defined below:

· Software Development: software development services to modify the performance of existing Foundation GEOINT baseline capabilities and services.

· Integration: integrate solutions delivered by the individual system development teams into the Foundation GEOINT enterprise production environment. These may include both GOTS and COTS capabilities / services.

· Software Maintenance: Corrective, Adaptive, Preventative, and Perfective maintenance in support of FG capabilities in operations.

· Operations Support: services supporting the FG operational baselines and daily-production activities to include acquisition of all needed licenses.

(U) The Contractor shall provide operations support to SCDS operational capabilities, monitor required operational resources including databases, interfaces, and operational status during designated operations hours. Once an outage or degradation is observed, the Contractor shall take all steps required to identify the cause, make notifications, and fix or submit the proper trouble tickets as required.

(U) The Contractor, per Government direction, shall deliver a report that covers SCDS sub-system gaps, manpower, monitoring requirements, software baselines, IT requirements, and Reliability, Availability and Maintainability discovered during system assessments. The contractor shall conduct assessments after an outage, a degradation is observed, or as requested by the Government.

(U) The Contractor, per Government direction, shall deliver an Operations Support Plan (OSP) (CDRL A020) that addresses all the requirements supported under SCDS. The Contractor shall use the DoD Product Support Manager Guidebook 2019 as a guide to draft the OSP. The Contractor shall update the OSP after additional sub-systems are added SCDS.

(U) The Contractor shall use the NGA CORE DevSecOps pipeline to deploy SCDS capabilities as applicable 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 or services developed elsewhere.

1.1 (U) Data Ingest and Management Data ingest consists of both COTS and GOTS software and manipulation of metadata on all applicable security domains (JWICS, SIPRNet, NIPRNet). Data Ingest and Management functions shall include but not be limited to: currency and accuracy of NGA data and product metadata across all domains, maintain databases with product metadata, data quality assurance, accommodate ingest for military specification-based products, emerging data types and sensors (i.e. LiDAR), and collaboration with Analysis and Source as needed.

· (U) Data ingest/validation and maintenance for Source Foundation products (70+ different product types).

· (U) Custom tailored scripts to create/retrieve/update/delete metadata within the database tables for adaptive maintenance and/or fix-actions.

· (U) Resolve product/data issues with missing, incomplete, or conflicting data and metadata tags.

· (U) Manage database schemas, views, triggers, and stored procedures.

· (U) Develop/maintain spatial components to all applicable Source Foundation GEOINT products added into the databases.

· (U) Develop/maintain Country/State boundaries to all applicable Source Foundation GEOINT products added into the databases.

· (U) Periodically monitor databases for any Source Foundation GEOINT product holding or edition discrepancies. Example: Maps and Charts found in the DLA catalog, but not in the SFC and should be, or edition mismatches between DLA, GeoSqrl and SCDS databases. Includes visualization of the holdings in a comparative fashion in a tabular and geospatial footprint view.

(U) Digital Delivery

(U) Create an inventory and checksums of uploaded files and saves a manifest that is uploaded with the data. A Digital Delivery Uploader script that automates the process of creating a manifest of files in a local directory and then completes a sync of the local directory with an optional specified Simple Storage Service (S3) bucket. Based on the required standardized directory structure expectations, the uploader dynamically creates proper S3 objects for Content ID and Managing Authority. This script tool provides a default User Interface for enhanced interaction or can be run via command line. Ingest capabilities must have the ability to run virus scanning/quarantining of infected files.

(U) Secure the digital data supply chain for deliveries from Data Providers to NGA and then up through NGA security domains.

· (U) Data Ingest

· (U) Data Conditioning

· (U) Data Assurance

· (U) Consumer Integration

· (U) Provider Integration

· (U) GeoServer

· (U) Mag-loader

(U) Document Upload Microservice A document upload microservice that uploads either one or more files into a pre-configured S3 location and requires GEOAxIS for authentication in order to upload documents. This includes the coordination/integrations necessary with dirty buckets.

This microservice must be integrated with FGDRT to upload international agreements and supporting document for Exceptions to Policy and Foreign Military sales cases. It shall be part of FGDRT Records Management capabilities

(U) Ingest Validation Microservice Validates manifests when they arrive in queue. Missing checksums cause processing to stop until Visibility/Timeout expires. Validates Data Access Data Integrity.

(U) Ingest and Management Modernization The Contractor will integrate, test, and deploy services to support data ingest and management.

1.2 (U) Condition and Catalog

(U) Automated metadata extraction, product conditioning, classification and tagging of ingested data. To be maintained throughout the lifecycle, and performer adaptive maintenance, as needed.

· (U) Metadata extraction

· (U) Product conditioning

· (U) Appending metadata to data

· (U) Datum conditioning (includes country codes, mapper, products, etc.)

· (U) Geospatial conditioning

· (U) Releasability handling (via FGDRT)

· (U) Content Catalogue storage

(U) Source Foundation Catalog (SFC)

· (U) The SFC will be an automated database that enables the storage of product metadata. Catalog of all ingested products, allowing external programs (ie GSR, The Globe, etc) to integrate foundational metadata to facilitate automated flows and integration with NGA. In coordination with FGDRT, the Contractor shall create an automated database for sharing content with international partners and non-USG entities such as commercial vendors and academia.

(U) GEOINT Delivery Platform (GDP)

· (U) An application providing a dissemination platform for Foundation GEOINT Products. This application catalogs NGA products and allows users to find and download NGA's digital holdings. Map of the World and other interfaces leverage GDP’s OGC RESTful data services.

(U) Condition and Catalog Modernization

(U) The Contractor will integrate, test, and deploy services to support Conditioning and Cataloging.

1.3 (U) Disclosure and Release

(U) Development and enhancement of the operational components that facilitate and enable NGA to perform its mission essential function of exchanging GEOINT with International Partners through formal agreement, foreign military sales and exceptions to policy. FGDRT allows for the disclosure and release of geospatially enabled objects to identity-based access users. FGDRT is an Enterprise level, cloud based, data-type agnostic GEOINT requirements adjudication application that is architecturally integrated as a “system of systems” within the SCDS. FGDRT supports the traditional distribution of Maps/Charts through the Defense Logistics Agency (DLA) and enables digital distribution of GEOINT to partners through other systems. Operational functions include, but not limited to:

· (U) GEOINT Store (Exception and Foreign Military Sales (FMS))

· (U) Discovery and selection of GEOINT products/data

· (U) Discovery and selection of customers (international partners)

· (U) Summary and submission page/features

· (U) International Agreement

· (U) Input of basic agreement information

· (U) Discovery and selection of GEOINT products/data

· (U) Discovery and selection of customers (international partners)

· (U) Summary and submission page/features

· (U) Commercial GEOINT

· (U) Discovery and selection of GEOINT products/data

· (U) Discovery and selection of customers (international partners)

· (U) Summary and submissions page/features

· (U) Administrator Dashboard

· (U) Administrator & Approver Roles

· (U) User Dashboards

· (U) International Officer Role

· (U) FMS Officer Role

· (U) Requestor (Domestic & Foreign) Roles

· (U) Obligation Search (Business Rule Query)

· (U) Discovery and selection of GEOINT products/data

· (U) Discovery and selection of customers (international partners)

· (U) Summary matrix

· (U) Country Page

· (U) Collects customer information

· (U) Current obligations from exceptions, FMS, and international agreements

· (U) General Country information

· (U) Uploaded Documents/Artifacts associated with Country

· (U) Coalition and Exercise Creation

· (U) Discovery and selection of customers (international partners) (feature used in multiple elements)

· (U) Edition Comparator Tool (compares old/new editions for filter matches and alerts administrators)

· (U) Document Upload and Storage via Dedicated AWS S3 Containers

· (U) FGDRT dedicated content IDs for artifact storage

· (U) Administrator Tools

· (U) Multiple admin components for system maintenance

· (U) Metric reports

· (U) Enables FGDRT to generate various user “roles”

· (U) User Account Management

· (U) GEOAxIS integrated access to support role generation within FGDRT

· (U) Role specific rights/navigation (dashboard and rights are unique to each role)

· (U) SMTP Email Capabilities

· (U) System generated email notifications and coordination capability

· (U) Inter-system “messaging”

· (U) Coordination Capability to capture multiple inputs from relevant stakeholders on a D&R decision (includes already integrated email notification capability)

(U) Expurgation

(U) Support the NGA International Affairs (I) Foreign Military Sales (FMS) and Foreign Partners requests for allowable NGA Source Foundation GEOINT content.

· Correlate NGA Gateway, DLA holdings, and NGA GeoSqrl databases to provide comprehensive Expurgation for International Affairs when supplying content to Foreign Military Sales (FMS) and Foreign user requests.

· Capture product content at time of Expurgation for future retrieval.

· Provide spatially depicted product coverage through GIS viewer manipulation and capture for FMS and Foreign user requests as needed for NGA International Affairs.

· Includes, but not limited to Compressed Arc Digitized Raster Graphics (CADRG), Enhanced Compressed Raster Graphics (ECRG) and other “digital” layered formats and products.

(U) The FGDRT has already declared IOC and is already in limited operations with International Affairs. IOC means the backend architecture is built, which it currently is, and data is able to flow through the cloud infrastructure, which it is.

(U) Disclosure and Release Modernization

(U) The Contractor will integrate, test, and deploy services to support disclosure and release.

1.4 (U) Dissemination Services

(U) Delivery of microservices to enable Foundation GEOINT products to be disseminated to customers worldwide. Microservices include, but are not limited to, the ability to do bundling and bundler clean up functions within SCDS.

(U) Deliver capability to sync content across external nodes

(U) Deliver a bi-directional subscription service to NGA products by Country, Area of Responsibility (AOR), Worldwide on the requested security networks (NIPRNet, SIPRNet, JWICS).

(U) Deliver capability to digitally transfer content between NGA and DLA to replace the current physical workflows/processes (Trans Shipper).

(U) SCDS – capabilities already in the operational GGPM environment:

· (U) Data ingest

· (U) Discoverability & Releasability

· (U) Cataloging

· (U) Data dissemination

· (U) Suite of dissemination APIs and specifically tailored APIs for maiNGAte

(U) Deliver a Business Analytics / Business Intelligence capability to capture customer metrics to guide customer segmentation, product and UI design, resource prioritization, and performance management. Ensure that Business Analytics/Business Intelligence (BA/BI) and systems dedicated to support can access, assess and report on SCDS processed requests through SFC storage and API function. Such data access via API and/or database access (SQL, Oracle or other within SCDS)

· Capture customer profile information on what products are being used by who in order to inform production requirements and tailor customer experience

· The collection of all activity is currently logged, but no analytics is currently done with the data. There is no BA/BI gathering at this point.

(U) Dissemination Services Modernization

(U) The Contractor will integrate, test, and deploy services to support dissemination services.

1.5 (U) User Interface

(U) Development and enhancement of the operational components that facilitate and enable a unified user interface for discovery and dissemination of Foundation GEOINT. A unified access to FG products to replace numerous customer specific access points and simplify the dissemination processes, while maintaining the operational environment. The maiNGAte allows for the discovery and access to Foundation GEOINT. The maiNGAte is an Enterprise level, cloud based, data-type agnostic application that is architecturally integrated as a “system of systems” within the GGPM.

(U) Deliver a unified access to FG products to replace numerous customer specific access points, and simplify the dissemination processes for Foundation GEOINT.

(U) Develop capabilities to integrate multiple FG user interfaces (ex: maiNGAte, MCDP, and FGDRT) for customer access to products based on disclosure & release guidelines. Maintain functioning website allowing customers to order FG products.

(U) User Interface Modernization

(U) The Contractor will integrate, test, and deploy services to support User Interface.

1.6 (U) Modernization Backlog

(U) The Contractor will maintain a backlog of efforts to be developed/modernized. Working closely with Government to review and manage Program/Project Epics and User Stories in the Program Backlog, the Contractor will support prioritized efforts at the direction of the Government. Reference Section 5 for current list of backlog efforts.

(U) Development Backlog (Optional) The Contractor will maintain a backlog of capabilities, features, etc. to be developed/modernized. Working closely with Government SMEs to review and groom Program/Project Epics and User Stories in the Program Backlog, the Contractor will support prioritized efforts at the direction of the Government.

(U) Mission Planning System Updater (MPSU)

(U) Allows users that subscribe to specific products to inventory differences between subscription holdings on the gateway vs. the customer’s holdings to update their local system

· Replace MPSU Rest Service

· Replace MPSU Manifest Updater

(U) Mission Planning System Updates (MPSU), a backend series of functions that update NGA product manifests for a select set of aeronautical and supporting product holdings that mission planners use in tools like Falconview or Xplan so the end user does not need to query manually for any delta of new products from their local system to NGA current holdings. Timer beans update all the product holdings every 10 minutes.

(U) Key Word Search

(U) Develop a “key word” search that works with the security of ‘discovery and release’ decisions based on user credentials. Provide geo-referenced and textual search means for discovery by users

(U) Mapping Enterprise Business System (MEBS)

(U) Integration and data flow into the Mapping Enterprise Business System (MEBS). This is different than digitally transferring to DLA.

(U) New FG Product Integrations

(U) Expand SCDS capacity to ingest, condition, provision, discover, retrieve and deliver additional source foundation products, or entirely new product lines from wider NGA

(U) Geospatial Tile Servers

(U) The contractor shall integrate the storage for Tile Servers into the SCDS for all applicable security domains (NIPRNet, SIPRNet, JWICS).

(U) Customer Media

(U) Integration of Custom Media into SCDS. Custom Media will eventually rely on SCDS to find content and use SCDS Bundler Services. The interface in maiNGAte will provide the option to use Custom Media (or force the use if request is too large).

(U) Maritime Content Dissemination Portal (MCDP)

(U) Integration of MCDP with maiNGAte and/or SCDS.

(U) Tile Server

(U) Provides Vector and Raster map tiles in OGC web service formats for many NGA foundation products, including CADRG, CIB, DEM Products, and many others.

(U) Naval Research Lab (NRL) Tile Server, suite of OGC compliant web-services providing both raster and vector tiles composed of NGA Source Foundation GEOINT content for map viewer front-end applications like Map of the World and various non-NGA customer applications.

(U) Potential migration/integration moving storage from on-premise databases into SCDS’s architecture leveraging cloud S3 buckets.

(U) Support for Precision Fire Image Generator Online / PSS-SOF DPPDB Chip Tool (tool resides on higher domains)

(U) Enterprise File Delivery

(U) Enterprise File Delivery (EFD) system, an application with client and server-based software that provides the capability for a forward based location to subscribe to an area of interest of standard geospatial product data sets for replication to local data stores. Note: EFD requires an end-user to have an EFD client.

· (U) Inventory maintenance (NGA and customer holdings tracked)

· (U) Download new data, remove expired data

· (U) Data synchronization

· (U) Subscription services (Global, AOR, Country List, Product line)

· (U) Data delivery

· (U) General fault tolerance (retry after failed file delivery)

· (U) Secure file delivery via HTTPS

· (U) Large file transfer (>250GB)

· (U) Multiple file transfer

· (U) Data compression during transfer (TBD)

· (U) Data decompression after transfer

· (U) Data file chunking

· (U) Certificate Authenticated file transfer

· (U) Customer support

· (U) SysAdmins to troubleshoot and handle file transfer issues

· (U) System level logging

· (U) Task logging

· (U) Automated authorization for data release

· (U) Customer on-boarding

· (U) Metrics collection

· (U) Foreign partner support (via FGDRT)

(U) Program Management

1.7 (U) Program Management Services

(U) The Contractor shall adhere to the Program Management Plan (PMP) (CDRL A001). Within the PMP, the Contractor shall include, but not limited to:

· Quality Control Plan

· Staffing Plan

· Risk, Issue, and Opportunity Management Plan

· Stakeholder Communications Plan

(U) The Contractor shall adhere to the Transition-In Plan (CDRL A004) when new systems or capabilities are transitioned over to FDM from another entity (Government or Contractor developed).

Kickoff meeting

(U) The Contractor shall arrange and host a contract kick-off meeting at NGA within 14 calendar days after award. Prior to the kick-off, the Contractor shall review contract and program administration, deliverables, risks, and upcoming transition schedule of events as well as other topics proposed by the Government and Contractor. At the kick-off, the Government and Contractor shall review contract and program administration.

Program Management Review (PMR)

(U) The contractor shall conduct a monthly PMR (CDRL A005). The Program Management Review shall include, but not be limited to:

· Program progress, financial execution including financial performance for each CLIN that includes burned rates and other financial information and projection, staffing profile for the overall program.

· Reports of outages, deployments, risks, issues, mitigation strategies, blockers, showstoppers, and process failures.

· Staffing and Financial Report

· Risk, Issue, and Opportunity Registrar (RIOR) (CDRL A007)

· Schedule/Roadmap Update

· Present the heath and status of Configuration Management at the monthly PMR meeting slides.

· Outstanding Action Items

· Program accomplishments that includes but is not limited to:

· Status of development schedule and major accomplishments

· Status of any cost saving initiatives

Capability Demonstrations

(U) The Contractor shall provide capability demonstrations as requested by the Government. Capability demonstrations and briefings shall:

· Show the latest schedule status in format approved by the PM or COR for the software and technical documentation activities, JIRA tickets worked with status for the sprint, epics or user stories, and SWAP status (when applicable)

· Include any Government required test plans/approach for the release

· Demonstration of JIRA tickets worked

· Action Items

· Identify risk and issues, alternate or contingency plans, and notifications to Government CO, COR, PM and PMO teams

Communications Program

(U) Design and conduct a stakeholder communications program. Deliver a Stakeholder Communications Plan (CDRL A003). Ensure all necessary stakeholders are informed of outages, impacts, schedules, blockers, showstoppers, and process failures. Request Government assistance in solving problems through this communications plan and process. The Contractor shall provide Customer Engagement/Meeting Minutes & Action Items (CDRL A008).

Staffing List

(U) The Contractor shall development and maintain a current Staffing List. (CDRL A006)

Reserved

1.8 (U) Transition-In

(U) Services to transition capabilities from a legacy service provider to the FDM Contractor. The Contractor delivers transition-in plans and associated artifacts that details the process of capturing and transitioning all necessary information, equipment and personnel relating to transitioning of operations and maintenance support from an incumbent service provider to the FDM service provider. The Contractor then executes the transition-in of the capability, in coordination with the legacy service provider, in accordance with the transition plan.

For capabilities transitioning to the FDM Contractor, the Government will provide access to the code baseline and all technical information and documentation necessary for the Contractor to assess the Legacy System. The Government will provide at least one overview briefing to the Contractor and will be available for questions and requests for additional briefings to clarify or expand on specific topics identified by the Contractor.

Upon completion of obtaining the Government provided information, the Contractor will be able to review and assess the state of the system with respect to modernization and end-state goals and new features. The Contractor shall develop and deliver an Assessment Plan that defines the approach and schedule to assess the system against modernization and end state goals, and the Legacy or New System against new feature development requirements (CDRL A004).

Transition-In activities are expected to take 30 business days or less to complete. The Contractor shall provide weekly status on the progress of Transition-In activities.

1.9 (U) Transition-Out

(U) Services to transition capabilities out of FDM control to a new Integration / Operations and Sustainment service provider. The Contractor delivers transition-out plans and associated artifacts that details the process of capturing and transitioning all necessary information, equipment and personnel relating to transitioning of operations and maintenance support from FDM to a future service provider. The Contractor then executes the transition-out of the capability, in coordination with the successor service provider, in accordance with the transition plan.

System Transition-out includes services to transition capabilities as directed by NGA. The Contractor shall develop and deliver a transition-out plan (CDRL A010) and associated artifacts that detail the process of capturing and transitioning all necessary information and artifacts required for operations and maintenance support to an existing or new sustainment service provider. The Contractor shall execute the transition-out of the capability, in coordination with the sustainment service provider, in accordance with the Government-approved transition plan. The Government may require the Contractor to train a new contractor including executing dual operations for a specified period.

System Transition-Out will normally include, but not be limited to, the following activities:

· Document all artifacts to include software and supporting documentation (CDRL A009)

· Update any remaining backlog items

· Complete all remaining technical documentation and supporting information required for operations and maintenance

· Work with Government personnel for specific instructions on how the transition out will occur and new points of contacts.

· Transfer all Government Furnished Information/Equipment to the Government

· Perform training when directed by the Government and provide training material (CDRL A016)

1.10 (U) Travel

(U) Travel may be required to various locations within the Continental United States (CONUS) in performance of this contract. The Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Federal Travel Regulation (JFTR), FAR 31.205-46, and the limitation of cost/funds specified in this contract. All travel requires advanced approval in writing by the COR 10 days prior to the requested travel date.

(U) The Contractor will not be reimbursed for any local travel. Local travel is defined in the contract as travel conducted on official business within a 60-mile radius of official duty station.

The contractor must submit monthly invoices for reimbursement citing the appropriate CLIN in accordance with the JTR. Each individual travel instance must be captured. Copies of receipts, travel vouchers, etc. must be attached to the invoice to support charges. Original receipts must be maintained by the contractor and made available to Government auditors upon request.

(U) Contractors are not permitted to charge the Government for business or first-class travel. Maximum use is to be made of the lowest available customary standard coach or equivalent airfare accommodations available during normal business hours. Contractor travel must be in accordance with Government approved lodging and per-diem rates.

1.11 (U) Telework

(U) Unclassified teleworking is a benefit and not a requirement of the contract. Regardless of telework allowability, the Contractor shall be responsible for performing all classified and unclassified requirements of the contract. Unclassified telework is permitted under this contract unless the Contracting Officer (CO) and Government Point-of-Contact (GPOC) determine that the contract requirements, including security, cannot be met through telecommuting.

(U) A Government-approved telework plan must be in place prior to telework that shows direct traceability to the work statements duties and tasking. Any telework that takes place without written approval from the CO or COR will be considered unallowable. All telework plans must be authorized and approved by the COR or CO. The Government shall not reimburse the Contractor for telework costs including, but not limited to: internet service, telephone service, or hardware. All work hours must be billed at the negotiated rate for the position. Premium rates will not be allowed. Telework must be performed on the NGA SBU via PKI credentials. The Contractor must maintain adherence to proper security classification rules and standards while operating in a telework environment.

(U) Contractors (prime and subcontractors) are responsible for predetermining and disclosing their charging practices for telecommuting, applicable cost accounting standards and company policy. Contractors must follow their disclosed charging practices.

Contractor telecommuting policy and labor timekeeping policies and procedures are subject to Government audit.

(U) Telework Location Telework is only allowed within the local commuting area of the locations identified in the contract for each position approved for telework. Teleworking from a different location must be authorized by the CO or COR on a case by case basis if required to meet unique requirements. Contractors must be able to be recalled to the duty site from telework at any time. Contractors going on vacation must disconnect from work and take appropriate leave.

(U) Invoicing and Reporting Telework will be monitored by the COR and GPOC. All telework must be performed in accordance with the Government-approved telework plan. The Contractor must include one (1) consolidated monthly Telework Report in conjunction with the submitted Monthly Program Management Report (PMR) (CDRL 005) deliverable for all of the unclassified telecommuting work activities. All telecommuting hours must be noted and broken out separately in the Contractor’s invoices. The Telecommuting Report must include the following minimum information:

· Contractor Name(s)

· Location of Telework

· Duration of Telework

· Description of Telework performed

· Total number of teleworking hours being charged to the contract

· CLIN(s) charged

1.12 IT Accessibility (Section 508)

The Contractor must ensure that all systems, hardware, software, software engineering, and information technology associated with this effort is made in a manner that is accessible for those with disabilities as directed in the NGA Instruction 8400.4 and Section 508 of the Rehabilitation Act of 1973 as amended in 1998 (Section 508). Specifically, all Information and Communications Technology associated with this contract, may use the Web Content Accessibility Guidelines 2.1 to comply with the Section 508 or use alternative designs or technologies which result insubstantially equivalent or greater access to and use of the product for people with disabilities. Furthermore, the Contractor must pursue human centered design and usability guidelines in order to ensure that all services associated with this PWS are accessible by as many users as possible and as a means to drive modernization, innovation, and enhance mission support.

1.13 Other Direct Costs (ODC)

In accordance with existing Government guidelines for expenses, the Contractor may submit charges supporting the delivery of requested services for the accomplishment of contract activities. All Contractor other direct costs must be approved by the Government COR or CO prior to the contractor incurring any expenses; this includes any commercial software licenses to be used, which must be submitted to the CO or the COR for agency approval prior to purchase and installation. Any commercial software license purchased under this contract must be licensed to the Government, and must be registered in the name of the Government. Any additional software required by the contractor must be identified in the invoice Material CLIN that will be prepared and delivered to the Government.

(U) Period and Place of Performance

(U) The period of performance shall be a 12-month base year with four one-year option periods from date of contract award.

(U) The primary place of performance will be the contractor facility(ies), within a 60-mile radius to a SCIF.

· (U) The Contractor will be responsible for ensuring their personnel have access to their identified Sensitive Compartmented Information Facility (SCIF) to address time sensitive tasks.

· (U) The Contractor is responsible for all costs and coordination associated with leveraging non-NGA facilities.

(U) Work at the Contractor site can be unclassified. If classified work is to be conducted at a Contractor site, the SCIF must be approved by the Defense Counterintelligence and Security Agency and NGA Security. Contractor must have NGA Net connectivity with the appropriate workstations to accomplish all work outlined within this PWS at time of award.

(U) Quality Assurance Surveillance

(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. The plan 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 contract.

(U) The Contractor shall immediately notify the COR of problems or situations that could negatively impact compliance with the provisions of the contract and the plan the Contractor shall implement to resolve problems. The designated COR/ACORs will participate in the administration of this contract 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 period of performance with the CO, GPM, 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) If the Contractor is not meeting the minimum requirements, the contractor shall develop and deliver a Corrective Action Report (CAR) (CDRL A011) in the manner and within the time frame specified by the Government, stipulating how and by what date it shall bring performance up to the required levels.

(U) The GPM 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 A002).

(U) Operational Hours

(U) Regular Hours: Personnel will be generally required to perform work during regular NGA duty hours. It is expected that all personnel begin their work day before 0900 local time. Exceptions may be requested for early or late arrival of some smaller set of personnel based on mission need.

(U) Non-regular time: Personnel may be required to work during non-regular duty hours to resolve unexpected outages, planned outages and crises. The Contractor should plan for 10% of the total hours allocated to this contract will be performed outside of regular business hours. Provide call back operational and technical support outside of normal business hours of operation including federal holidays.

(U) Recall: The Contractor shall provide a plan for recall of personnel to support all objective areas during non-duty hours. Recalled personnel shall arrive to the duty location within four hours from notification. Personnel are expected to be available via telephone 365 days per year (366 in leap years) providing support through a combination of on-site and off-site support.

(U) Government Furnished Equipment

(U) The contractor must account for and maintain all the Government-provided materials, property and equipment IAW FAR 52.245-1 (SEP 2021), Government Property and NARI Clause 5X52.45.102-9000 (Nov 2016). The equipment must be documented and tracked via a Government Furnished Property/Material list. The list must include, but is not limited to:

· Contract Number

· Contractor Point of Contact

· Date of Last Physical Inventory

· Inventory with the following:

· Item Name

· Asset Identification Number or Unique Item Identifier

· Item Description

· Manufacturer Name

· Manufacturer Part Number

· Manufacturer Model Number

· Serial Number

· Quantity

· Location

· Type of Government Property – Government Furnished Property (GFP) or Contractor Acquired Property (CAP)

· Current condition of equipment, per the equipment condition status listed below as applicable:

· Condition A – Serviceable Usable without Qualification

· Condition B – Serviceable Usable with Qualification

· Condition D – Serviceable Test/Modification

· Condition F – Unserviceable Reparable

· Condition H - Condemned

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

(U) The Contractor shall manage the SCDS operational configuration baseline 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:

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

· (U) 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

· (U) Supporting NGA enterprise asset tracking activities for…