GCS_TO 1_PWS 03-03-2021.pdf

UNCLASSIFIED

GCS-PWS-TO#1

Performance Work Statement (PWS)

For

Geospatial-Intelligence (GEOINT) Core Services

(GCS) Program

Indefinite Delivery Indefinite Quantity (IDIQ)

Task Order #1

3 March 2021

Contents 1 (U) Introduction to GCS Capabilities

2 (U) Objectives and Scope

2.1 (U) Operations and Sustainment of the GCS Software Baseline

2.1.1 (U) MapStack

2.1.1.1 (U) MoW Map Manager

2.1.2 (U) Google Earth (GE)

2.1.3 (U) IC GIS Portal

2.1.4 (U) Queries, Utilities & Tools

2.1.5 (U) GCS Geospatial Content

2.1.6 (U) Enterprise Geospatial Information System (eGIS) (Arnold only)

2.1.7 (U) Enterprise File Delivery (EFD) System

2.1.8 (U) Advanced Data Ingest and Management (ADIM)

2.1.9 (U) GEOINT Delivery P latform (GDP)

2.1.10 (U) Website Hosting

3 (U) RDT&E - Incorporate New Features/Functionality into GCS Software Baseline

3.1 (U) Prototypes

4 (U) GCS General Requirements

4.1 (U) Business Analytics/Metrics

4.2 (U) Strategic Roadmap

4.3 (U) Enterprise Engineering and Integration Considerations

4.3.1 (U) Application Layer

4.3.2 (U) Infrastructure Layer

4.3.2.1 (U) Cloud Migration

4.3.3 (U) Service Design/Development/Delivery

4.3.4 (U) Deployment, Test, Certification and Accreditation

4.3.5 (U) Tier I – III 24 - Hour Operations Support

4.4 (U) Agile Development (RDT&E or Adaptive Maintenance)

4.4.1 (U) Engineering Assessments

4.4.2 (U) IC GIS Portal Development

4.4.3 (U) Queries, Utilities & Tools

4.4.4 (U) Additional Mission Services

4.4.5 (U) Rapid Content Exposure & Sustainment / Backlog Work-Off/Crisis Support (BWOCS) ... 28

4.5 (U) Systems Operations and Sustainment

4.5.1 (U) GCS General Systems O&S

4.5.2 (U) MapStack

4.5.2.1 (U) MapManager

4.5.3 (U) Google Earth (GE)

4.5.4 (U) IC GIS Portal

4.5.5 (U) Queries, Utilities & Tools

4.5.6 (U) Enterprise Geospatial Information System (eGIS) Arnold

4.5.7 (U) Enterprise File Delivery (EFD)

4.5.8 (U) Geospatial Delivery Platform (GDP)

4.5.9 (U) Advanced Data Ingest and Management (ADIM)

4.5.9.1 (U) FGDRT Specific Sustainment Activities

4.5.10 (U) GCS Geospatial Content Sustainment

4.5.11 (U) Website Hosting & Sustainment

4.6 (U) Exercise Support

4.7 (U) Surge Tasks (TBD)

4.8 (U) Operating Constraints (Non-Functional Requirements)

4.9 (U) Customer/User Engagement

4.10 (U) Administrative Requirements

4.10.1 (U) Contractor Key Personnel

4.10.2 (U) Travel

4.10.3 (U) Other Direct Costs

4.10.4 (U) Period of Performance

4.10.5 (U) Place of Performance:

4.10.6 (U) Contract Transition-In and Exit

4.10.7 (U) Classified Work Performance Security Requirements

4.10.7.1 (U) Off-Site Technical & Software Development Utilizing Uncleared Personnel

4.10.7.1.1 (U) Unclassified Work Performance Security Requirements

4.10.7.2 (U) Information Handling

4.10.7.3 (U) For Official Use Only (FOUO) Information

4.10.7.4 (U) International Transfer in Arms Regulation

4.10.7.5 (U) Physical Security

4.10.7.6 (U) Release/Removal of Documentation

4.10.7.7 (U) Automated Information Management System Security

5 (U) Deliverables

5.1 (U) Agile Development Management Plan (CDRL A001)

5.2 (U) Systems Operations/Engineering and Management Plan (CDRL A002)

5.3 (U) Program Management Reviews (CDRL A003)

5.4 (U) Quality Control Plan (CDRL A004)

5.5 (U) Software Code and Software Code Documentation (CDRL A005)

5.6 (U) Test Procedures and Test Results (CDRL A006)

5.7 (U) Readiness Review Documentation (CDRL A007)

5.8 (U) Customer/User Engagement, After-Action-Reports (AARs) and Meeting Minutes (CDRL A008)

5.9 (U) Service Level Agreements & Operational Support Agreements (CDRL A009)

5.10 (U) RFC Change Pages & RFC Change Database (CDRL A010)

5.11 (U) Configuration Management Plan (CDRL A011)

5.12 (U) Weekly Activity Report/Weekly Items of Interest (IoI) (CDRL A012)

5.13 (U) Transition Plan (CDRL A013)

5.14 (U) Surge Task After-Action Report (STAAR) (CDRL A014)

5.15 (U) Metrics Reporting (CDRL A015)

5.16 (U) Strategic Roadmap (CDRL A016)

5.17 (U) Systems Requirements Document (SRD) (CDRL A017)

5.18 (U) Contractor Security P lan (CDRL A018)

6 (U) Performance Requirements Summary (PRS)

6.1 (U) Quality Assurance Surveillance Plan (QASP)

7 (U) Definitions

8 (U) Acronyms

9 (U) Applicable Documents

9.1 (U) Applicable Orders & Directives

9.2 (U) Applicable Standards

Figures Figure 2-1 Available Domains .............................................................. Error! Bookmark not defined.

Figure 2-2 MapStack Technology Stack Figure 2-3 MapStack Map Manager Architecture

Figure 2-4 GDP High Level Implementation Architecture Figure 2-5 eGIS Physical High Level Architecture Figure 2-6 eGIS Logical High Level Architecture Figure 2-7 High Level EFD Architecture

Tables Table 2-1 eGIS Domains Table 2-2 EFD Customer Footprint

Table 2-3 ADIM Usage Table 2-4 FGDRT Usage Table 2-5 Data Usage Table 4-1 Period of Performance

Table 5-1 Table of Deliverables Table 6-1 Performance Requirements Summary Table 9-1 Applicable Orders & Directives Table 9-2 Applicable Standards

1 (U) Introduction to GCS Capabilities

(U) Technology has been and will continue to be increasingly fundamental for NGA to achieve its strategic goals. Geospatial-Intelligence (GEOINT) is evolving at a rapid pace and not limited to providing imagery and geospatial awareness to the Intelligence Community (IC). GEOINT is the nexus of data fusion, responsible for the interpretation and visualization of highly disparate, differentiated data streams through transforming the NGA legacy application monolith to a transformational user experience with Application

Programming Interface (API) enabled applications and a service-centric framework. The GEOINT Core Services (GCS) program has been designated as an IC Services Provider and Services of Common Concerns (SOCCs). GCS will be the follow-on to GEOINT Visualization Services (GVS) and include approximately 80% of the NGA Product Dissemination (NPD) Program capabilities.

(U) The existing major core capabilities and services sustained by GCS today are: MapStack, MapManager, Google Earth Globe, Queries, Utilities & Tools, IC GIS Portal, BaseMaps & Content

Sustainment, GEOINT Delivery Platform (GDP), Enterprise File Delivery System (EFD), Data Ingest & Management (ADIM), Enterprise Geospatial Information System (eGIS) (Arnold), Geospatial Content User Registry, approximately 120 web pages, and presence on multiple cloud based architectures (currently on JWICS, SIPRNET, NIPRNET & Stone Ghost). GCS will also encompass Core API development, integration, operations and maintenance to ease integration of new capabilities provided by the IC.

(U) Additionally, NGA maintains an unclassified development environment that allows unclassified developers to produce software, helping to minimize developmental costs associated with companies attempting to replicate NGA’s enterprise development environment. NGA will provide access to the unclassified and classified development environments. This prevents unnecessary duplication of the NGA enterprise environment, software, and development tools. Furthermore, NGA maintains mandatory use of GitHub and GitLab repositories of all NGA code. GCS aligns with the current NGA Technical Strategy and NGA’s 2025 Strategy.

(U) Background – Previous to GCS, the program of record was GVS and NPD. On 14 October 2009, the DoD issued a memorandum, signed by the Assistant Secretary of Defense for Networks and Information Integration/DoD Chief Information Officer (ASD (NII)/DOD CIO), designating the NGA

GEOINT Visualization Services (GVS) Program as the “Shared Enterprise Service for Geospatial visualization for the IC.” This memorandum tasks NGA to continue to work with the Defense Information Systems Agency (DISA) to expand the full portfolio of GVS capabilities on the Worldwide Web (WWW), both User-authenticated instance as well as open/non-authenticated instance, unclassified and sensitive

Internet Protocol (IP) Router Network (NIPRNET), Secret Internet Protocol Router Network (SIPRNet) and Joint Worldwide Intelligence Communications System (JWICS) domains. GVS was first deployed in 2006. GVS’s mission is to provide user-facing core services that facilitate access to GEOINT data and products in an on-line, on-demand, and geospatially relevant environment to the IC, Department of

Defense (DoD), Department of Homeland Security (DHS), and other Federal Government agencies and across the entire National System for Geospatial Intelligence (NSG) and Allied System for Geospatial Intelligence (ASG). GVS Program provides an on-demand environment of capabilities that empowers users to discover, visualize, collaborate, share, and download NGA content and data to meet GEOINT mission requirements, as well as additional utilities and technologies that aid in visualization. The GVS enterprise is deployed across NIPRNet, SIPRNet, JWICS, Stone Ghost, and several external domains.

http://home.gvs.nga.smil.mil/home/ http://home.gvs.nga.ic.gov/home/

(U) The NPD Program began in December 2017. The NPD program provides intelligence products, geospatially orientated products and digital data and information to customers via electronic means. It is comprised of an infrastructure used to host mission segments, mission data, mission software, web services, web sites and APIs. Primary customers include the IC, DoD and inward-facing (corporate) entities. NPD capabilities and team members are split approximately 60% NCW and 40% NCE.

(U) The scope of the current NPD contract encompasses operations and sustainment within six functional areas: Intelligence Product Dissemination, NGA corporate web activities, Intelligence Product Creation, Geospatial Web Services, eGIS, and Data Ingest & Management (currently being modernized and will be named ADIM).

(U) Today there are more than ~3,535,000 daily users across the NSG. In abiding with the Government’s

“Cloud First” mandate, the GCS Program has been transitioning to a cloud architecture over the past ~5+ years. On JWICS, SIPRNET, and NIPRNET, the GCS program is currently fully-operational on Amazon Web Service’s (AWS) Commercial Cloud Service (C2S). The majority of all capabilities going through modernization efforts within NPD will be in the cloud prior to transition to the GCS Program.

(U) During Fiscal Year (FY) 2021, the GCS Program will transition Map of the World (MoW) to MapStack to be more in line with Program offerings to the NSG and non DoD agencies that receive content, services, and support from NGA. More importantly, the GCS program will focus on three capability lines: MapStack, Google Earth, and IC GIS Portal.

(U) Furthermore, other functional capabilities are being consolidated and transitioned into the GCS Programs Baseline. Those are: Naval Research Lab (NRL) Tile Server, NGA’s ADIM, EFD System, NGA’s GDP, eGIS (Arnold only), and some Server Services for minor web hosting activities. All of these capabilities at this point have been located in NCW.

2 (U) Objectives and Scope

(U) Objectives - The Contractor shall provide technical assessment, operations, sustainment, and other required activities that leverage Commercial Off-the-Shelf (COTS), Government Off-the-Shelf (GOTS), Free and Open Source (FOSS), NGA’s DevSecOps environment and other technology required to operate and sustain NGA mission-related efforts. To the extent possible the Contractor shall utilize and leverage the current NGA enterprise solution for metrics to gather and obtain relevant user and functionality information to support affective Program Management Office (PMO) decision making.

(U) Scope - The scope of this effort consists of Operations and Sustainment (O&S) of the GCS software baseline, as well as modifications, adaptations, prototyping, and integrating new technologies and capabilities. The Contractor will support NGA’s GCS Program in the development, sustainment, architecting, engineering, and program management of capabilities identified and in accordance with (IAW) the Joint Architecture Reference Model (JARM) Technical Service Categories (TSCs).

(U) The Contractor will inherit more than 1.3M Equivalent Lines of Code (ELOC) spanning multiple core applications, program interfaces, and network domains. The GCS software baseline is currently stored in

NGA GitLab repository. The Contractor shall produce at least 1,000 story points per Planning Increment (PI), and have 2 week sprint cycles on average for the GCS baseline O&S/Research, Development, Test, & Evaluation (RDT&E), assuming one story point is equivalent to approximately four engineering, design, development, or direct coding hours. Additionally, another 400 - 600 story points of agile development is required to integrate surge task and RFC requirements annually for the agency and community. This coding and design is necessary based on known future development work, existing backlog, and current sustainment efforts. Because surge task requirements are integrated with existing baseline agile development activities, the actual number of story point execution may be higher. Some sprint cycles will focus more heavily on development efforts, and some will focus more heavily on sustainment efforts, depending on prioritization during Release Planning Events (RPEs). Additionally, the Contractor will be responsible for several non-agile activities (teams), to include:

a. Operational support/help desk during operating hours (detailed in PWS Section 4.3.5) and call-back support during non-operating hours;

b. Provide content optimization activities on globe updates and portable globe development;

c. Provide customer/user engagement personnel to interface with primary user groups on a daily / weekly basis in the National Capital Region, with monthly engagements throughout the Continental United States (CONUS), and quarterly engagements Outside CONUS (OCONUS).

The Contractor will meet the requirements outlined in the compliance documents located in Section 9 of this PWS.

(U) The Contractor shall build, manage, and maintain database tables, associated views, schemas and stored procedures in Oracle, PostgreSQL, ArcSDE, and PostGIS

(U) The Contractor shall employ AWS micro-service architecture, nestjs backend, and database schemas and structures modification.

(U) The Contractor shall perform administration of Apache web server, JBoss software, disk usage, memory usage, and server availability.

a. (U) The Contractor shall maintain the primary functions of GDP’s backend; which include:

makeTarZip, Product Footprint, OCG Compliant Web Services, Download Services, Report Services, Oracle Spatial GDP Product Tables, Imagery and Basemap Tiles, and Data Bundling Capabilities.

2.1 (U) Operations and Sustainment of the GCS Software Baseline

(U) The Contractor shall provide a comprehensive enterprise solution to sustain, modify, improve, and expand on the legacy software baseline. This effort involves maintaining the existing GCS software baseline. The Enterprise GCS software baseline, including deployed user operations, will be sustained and adapted through agile software development methodologies. This objective includes: operations and sustainment of the code, discrepancy reporting (DR) work-off, adherence to and implementation of the GCS development roadmap resolution of the GCS backlog, and software (SW) performance assessments and improvements. Furthermore, the Contractor will identify technology opportunities and overlaps to address requirements and redundancies for data-centric capabilities with technology solutions. The GCS

Figure 2-1 Available Domains

Baseline and Domain locations can be found in the document titled, “GCS_Baseline_Capabilities_Table_(U-F).xlsx” within Appendix A of the PWS.

(U) The following sections describe each GCS Baseline capability:

2.1.1 (U) MapStack

(U) MapStack is a grouping of unique capabilities to provide the user with a variety of capabilities at the Application Layer, Service Layer, Data Layer, and Infrastructure Layer (See illustration in figure 2-2 below). MapStack capabilities are generated from other system requirements and user feedback prioritized and aligned with NGA technical and strategic objectives in mind then developed during a Program Increment (PI) followed by fielding over a relatively short period. The benefits of NGA’s approach to MapStack was a component-based approach to agile software development that has allowed multiple technologies (Openlayers, Cesium, MapLarge, ESRI) to come together and provide visualizat ion “building blocks” used to build other programs such as Exploit. This is the “path forward” for the GCS program strategy and is what has been implemented successfully thus far.

(U) MapStack is an online geospatial environment that provides GEOINT-related and multi-source content for the IC and DoD community to meet their mission needs. It serves two critical functions for the IC:

a. Content Service: Provides integrated, authoritative geospatial content.

b. Geospatial Environment: Integrates data from multiple sources, providing easy and instant access to all information available.

(U) This capability serves a very wide community of users across the NSG, ASG, and other Federal agencies supporting a range of expertise from a novice with minimal GIS expertise to an expert analyst applying the available content services to execute robust analytics and geospatial discovery in 2D or 3D as required. By improving the community's access to and discovery of authoritative content, the MapStack facilitates improved collaboration among users. As organizations produce, obtain, and store data and intelligence, the MapStack enables others to discover this content, thereby increasing efficiencies in data management and reducing duplicative effort. Additionally, the MapStack API allows analysts and developers to create map applications for their specific purposes and needs while leveraging the Foundation GEOINT and tools available on MapStack.

(U) GCS gains efficiencies through the development and sustainment of multiple capabilities while also promoting reuse and integration. The Unified Architecture provides cost savings in sustainment, accreditation, and user engagement activities. Monthly Operational Releases encompass traditional sustainment activities, user feedback requests, as well as new capabilities based on stakeholder priorities and user feedback while the GCS flexible and modular baseline allows for rapid deployment of one baseline to all GCS systems using automated deployment methods to NGA’s Enterprise Cloud-based

Systems: C2S, Unclassified Commercial Cloud Service (UC2S), and Secret Commercial Cloud Service (SC2S), and External Datacenter Environments (Overseas Data Center (ODC), United States Forces- Korea (USFK), and Stone Ghost). Furthermore, the common AWS unclassified development environment provides collaboration platform with external consumers and facilitates integration by commercial vendors and government organizations (MapLarge, NRL, DIA, etc.).

(U) To nominate new content or services to MapStack, users or organizations can submit a Content Nomination request form for review and approval by the NGA Source Directorate. This process can be initiated from the MapStack Add Content dialog and is described in the MapStack Help documentation.

Questions or feedback on the MapStack application or content are submitted via the Feedback links found throughout the Map of the World (MoW) Application, the GCS webpage, GEOINT Services RocketChat page, Jabber, or via email on all available networks.

2.1.1.1 (U) MoW Map Manager

(U) MoW’s Map Manager Tool is a web-based administration tool (PHP and AngularJS) that allows GCS

Administrators to configure external content sources and environment-specific application settings for the MapStack application. Map Manager provides all the map configurations to MoW via REST web services to ensure loose coupling and allow GCS Administrators to make configuration changes at a faster cadence without requiring a software release deployed into operations. Map Manager also supports versioning and multiple profiles, allowing GCS to test updates before publishing them to operations and to support various configurations for exercises, test events, external consumer integration, and custom MapStack Instances.

Figure 2-1 MapStack Technology Stack

Figure 2-2 MapStack Map Manager Architecture

2.1.2 (U) Google Earth (GE)

(U) NGA’s GCS program provides a customized version of Google Earth, tailored to address community needs for on-demand access to GEOINT data and products on operational networks. The offering includes Google Earth globes for different network environments, integrated globe services accessible within the environment, predefined content layers, and a range of support services for obtaining and rendering other overlays on the globe.

(U) NGA’s Google Earth services are associated with the deployed globe servers used by client applications. GCS provides globes for the following enterprise environments: NIPRNET, SIPRNET, JWICS, JWICS ODC, and Stone Ghost.

(U) GCS also provides three separate globes:

a. World Wide Coverage Globe (WWCG)

b. Afghanistan/Pakistan (AFPK) Globe

c. Natural Vue (NVUE) Globe

(U) Google Earth services are accessed via the Google Earth Enterprise Client. The client is freely available for download and use. GCS currently supports version 7.3.3.7699 of the Google Earth Enterprise Client. Additionally, GCS maintains a robust list of information and known issues for review by the NSG and ASG on the GCS website.

(U) The GCS Google Globe imagery can also be accessed using a map application that supports the Open Geospatial Consortium (OGC) Web Map Service (WMS) format.

2.1.3 (U) IC GIS Portal

(U) The GIS Portal is a collaborative geospatial content management system for the IC and DoD. The GIS

Portal enables the discovery and sharing of geospatial information for the DoD and intelligence communities. Users can create, organize, secure, and manage geographic assets and connect end-users with useful apps, maps, and geographic data. Central to the GIS Portal is integration with NGA's Identity Management Program, GEOAxIS, for enterprise user management permitting community-wide single-sign-on.

(U) User managed groups provide self-managed communities of interest within the GIS Portal, streamlining access to relevant information while also providing integration with GEOAxIS for protecting sensitive data.

(U) Web maps allow users to create geospatial products that can combine ArcGIS and OGC web services from content accessible across the community. Within the geospatial information products, the producer can define both symbology and define the end-user interaction with the geospatial content. The authoring experience also provides a simplified workflow allowing non-traditional GIS users to produce geographic products. Through the collaboration tools of the GIS Portal, multiple users can contribute to a product and build off work templates enabling faster information sharing.

(U) The GIS Portal includes many built-in customizable web mapping applications including, Story Maps, Time Aware apps, and several OpenSource templates that are common across the public internet and classified domains. For users needing to create customized applications, a visual Web AppBuilder is available, which allows for a more tailored web mapping application without the need to write code. Web

AppBuilder and portal based hosting can enable groups to create custom web experiences without incurring any overhead for web-hosting or development environments. Web AppBuilder (Developer Edition) provides an extensible framework for developers to create custom widgets and themes that can then be shared within the GIS Portal infrastructure.

(U) Story Maps are a simple yet powerful way to inform, engage, and collaborate across organizations with any mission narrative you want to tell that involves maps, places, locations, or geography. Story

Maps make it easy for you to harness the power of maps to tell your story. Story Maps are hosted web applications that let authors combine maps with narrative text, images, and multimedia, including video.

The Story Map components can integrate media contents that are accessible via Uniform Resource Locator (URL) from any location.

2.1.4 (U) Queries, Utilities & Tools

(U) Queries, Utilities & Tools are capabilities used across the GCS Capabilities Baseline for Google Earth, MapStack, IC GIS Portal, and other visualization clients. Most may be used across all domains and platforms with minor exceptions and domain restrictions. New development and routine maintenance and new code shall not negatively impact the use of any previously developed Queries, Utilities, or Tools and shall not break or degrade an existing capability. A comprehensive listing of these Queries, Utilities, or

Tools may be found in the document titled “GCS-Queries-Utilities-Tools-Table_(U-F).xlsx” and is located within Appendix A of the PWS.

2.1.5 (U) GCS Geospatial Content

(U) The GCS Program maintains and provisions a variety of Geospatial Content for the agency: BaseMaps (x6), Elevation Maps (x5), Globes (x3), Locators (x1), and Vector Overlays (x14) for use with all GCS principal capabilities, MapStack, GE, and IC GIS Portal. A complete listing of the GCS Geospatial

Content maintained by the GCS Program is located in the file titled “GCS_Geospatial-Content_Table_(U- F).xlsx” within Appendix A of the PWS. All Geospatial Content are considered developed, authored, and receive their classification by and through the agency’s Source Directorate. The GCS Program only maintains and provisions this information across the applicable domains for use by the NSG, ASG and other agencies as required.

(U) Any content that does not retain source attribution shall be identified to the Government for concurrence/usage approval. Each month, GCS continues to ingest Controlled Image Base (CIB), RegionOrthos, Active Earthscape (AE) orthos, and elevation updates (when applicable) for the WWCG, the AFPK Globe, Basemaps from the NGA Content Management Office (CMO) and any Government directed content provider. The Contractor shall optimize and publish ~10-12 TB of content/data per month for the WWCG/AFPK Globe and Basemaps. The monthly deliveries for the Globe of ScannedMaps (Enhanced Compressed Raster Graphic (ECRG)/Compressed ARC Digitized Raster Graphics (CADRG)), CIB, Orthos, and Digital Nautical Charts (DNC) vary in size, and elevation datasets will vary by month. Recent metrics reflect Scanned Maps averaged ~45GB, CIB ranged from 50GB-300GB, regional orthos ranged from 5TB-12TB and are provided by the NGA Source Directorate. GCS also includes AE orthos, which varied from 2-20 additional images per calendar year. Basemap deltas vary in size and most range from 500GB to 1TB – including SM, Trans, Elevation, DNC, and Scanned Maps. Work entailed for Basemap cartography has remained constant with Trans mxd, canvas lite, and analytical Basemaps.

Some of this effort requires correcting the mxds for visual optimization. In addition, the Contractor shall visualize and enable interaction with a large and growing number of structured observations, tracks and other point/line/polygon data from historic and ongoing intelligence analysis.

(U) The imagery tiles are added to the skin of the globe, applied to the “Best Imagery” BaseMap for MapStack / MoW, and viewed on the GIS Portal and Google Earth. The Contractor is required to optimize content (in some cases) to ensure a positive user experience across all base maps and operational data/content overlays.

(U) All work is performed utilizing existing capacity as part of each PI using agile development methodology.

(U) The NRL Tile Server: During FY 21, a new capability from NRL called “NRL Tile Server” will be migrating into the family of GCS capabilities and reside in the BaseMaps category of Capabilities. NRL Tile Services is a collaborative initiative between NRL and NGA to provide vector and raster map tiles in OGC web service formats for many NGA foundation products, including CADRG, Controlled Image Base

(CIB), Digital Elevation Model (DEM) products, and many others. This implementation is currently ongoing and is expected to be to be fully integrated into all Security Domains (NIPR, SIPR, and JWICS).

The Government will continue to be the data repository for NGA products, responsible for product feedback, Quality Assurance/Quality Control (QA/QC), and has overall responsibility for running custom scripts to generate Tile Packages for hosting in NRL Tile Server. The Contractor will maintain NRL Tile

Server into the GCS Cloud Account; however, the Government (GCS PMO/Source Foundation (SF)) will continue to send Tile Packages to S3 Storage under the GCS Cloud Account (UC/SC/TC) and maintains overall responsibility for data curation and generation.

(U) NRL Tile Server is a critical GDP interface and dependency. GDP pulls imagery/data from the Tile Server and ArcGIS Oracle spatial database to provide downloadable files through web services.

(U) The GDP backend technology stack includes, but is not limited to: ArcGIS, Oracle Spatial, jQuery, Apache, Java, and Spring

Boot.

(U) The GCS Program provides content to overseas users in the form of “portable” globes. This is generally content that is copied onto a portable hard disk drive, formatted with all necessary drivers/ software to be usable to the particular requestor, and shipped directly to the requestor based on the instructions provided.

Typical end-users are deployed throughout the world and materials/ shipping costs could vary.

The underlying content is typically classified at UNCLASSIFIED//LIMITED DISTRIBUTION.

2.1.6 (U) Enterprise Geospatial Information System (eGIS) (Arnold only)

(U) eGIS systems for GCS are located at Arnold on NIPR, SIPR, and JWICS.

(U) The Contractor functions in support of eGIS shall encompass administering Apache web server, JBoss software, disk usage, memory usage, server availability, and other system administration functions.

(U) The Contractor shall maintain GeoServer and ArcGIS, and be capable of utilizing GeoServer and

ArcGIS Enterprise suite (e.g. ArcGIS Server, Geoevent Server, Data Store, and Portal).

(U) The Contractor shall maintain database tables, associated views, indices, triggers and stored procedures and be capable of utilizing Oracle, PostgreSQL, ArcSDE, and PostGIS.

(U) eGIS is geospatial software and infrastructure for users to host and manage geospatial content and publish web services on NGA’s Virtual Hosting Environment (VHE). It provides self-service tools to retrieve, view, interact with, and store modified versions of vector and raster GIS products. eGIS provides an environment to interact with desired GIS products and perform value-added functions on them (i.e., annotation, aggregation, amalgamation, new product development, publication). It also serves as a storage environment for user-created data and products. eGIS provides multi-user enterprise geodatabases and OGC compliant data and web services to mission planners, Combatant Commands (COCOMS), the IC, and NGA applications such as MapStack and the IC GIS Portal. The technology stack for eGIS includes a combination of ESRI and Open Source spatial technologies to serve OGC standards-based web services such as WMS, Web Coverage Service (WCS), Web Feature Service (WFS), Web Processing Service

Figure 2-3 GDP High Level Implementation Architecture

(WPS), and Web Map Tile Service (WMTS). It includes both proprietary and open source GIS technologies to include ArcGIS Server, GeoServer, Oracle, and PostgreSQL. The current eGIS system consists of approximately 12 servers per network (NIPR, SIPR, and JWICS) with both Linux and Windows operating systems (OSs). The database contains about 5TB of data and the mass storage contains approximately 15TB of data. In addition, there is a separate instance on JWICS and SIPR used by the NGA College for training purposes. There are approximately 100 publishers with access to eGIS from Analysis (AO) and SF offices. Figures 2-5 and 2-6 provide a high-level eGIS overview.

Figure 2-4 eGIS Physical High Level Architecture

Platform Site Locations Network / Domain

VHE Arnold Data Center @ NCW NIPRnet @ arn.gov

VHE Arnold Data Center @ NCW SIPRnet @ arn.gov

VHE Arnold Data Center @ NCW JWICS @ arn.gov

VHE Arnold Data Center @ NCW Stone Ghost @ Mercury

Table 2-1 eGIS Domains

Figure 2-5 eGIS Logical High Level Architecture

2.1.7 (U) Enterprise File Delivery (EFD) System

(U) EFD synchronizes foundational GEOINT data holdings between NGA and its customers. EFD provides a subscription service that allows customers to sign up for NGA product holdings based on geographical, temporal, and image type attributes such as type, name, size, or other information. For example, users can subscribe for products by country, area of responsibility (AOR), or file type, name, or size. EFD has job management and scheduling (e.g., content updates get pushed to the customer every two weeks). Users receive automatic updates on products, keeping them in synch with NGA’s current holdings. Users can also choose what frequency they receive data. EFD also allows users to send products and data back to NGA. The EFD capability is free to the NSG community and available on NIPR, SIPR, and JWICS. EFD eliminates the need for costly and time-consuming hard copy replication (hard drives, DVDs) as well as time-consuming downloads over slow networks. The only requirement of customers is that they have a geospatial repository, or map server, set up.

(U) Currently, the EFD capability is migrating to the Cloud on all networks. Figure 2-7 depicts an EFD notional architecture diagram once the cloud migration is completed.

Benefits of EFD are as follows:

a. NGA provided software at no cost to the customer.

b. NGA provides installation and troubleshooting support to the customer site.

c. Eliminates the need for costly and time-consuming hard copy replication (hard drives, DVD’s) as well as time-consuming manual downloads over slow networks.

d. It can be installed on Windows, Linux, and Solaris OSs.

e. EFD delivers mission-critical products to customers 24x7.

f. Customers can prioritize synchronizations according to mission demands.

EFD Functionality is as follows:

a. Uses Transport Layer Security (TLS) encryption standards for secure communication between source and client sites – HTTPS protocol/FIPS 140-2 compliant encryption.

b. Has advanced cron capabilities for job management and scheduling which keeps customers in -synch with NGA’s holdings.

c. Systematically adds/deletes data during synchronization tasks.

d. Software resumes data transfer from systems/network failure.

e. High volume data transfer can set multiple feeds per connection.

f. The software can both consume and supply data. Some customers use it to deliver NGA products to their subordinate organizations.

Figure 2-6 High Level EFD Architecture

Table 2-2 below provides high-level information about EFD’s growing customer footprint and the amount of data and files transferred per month. NGA’s goal is to increase the EFD user base.

Approximate # of customers

Approximate # of data transferred per month

(TB)

Approximate # of files transferred per month

(Millions)

NIPR 5 6 .35

SIPR 35 50 .75

JWICS 10 35 8

Disconnected

Instances

3 N/A N/A

Table 2-2 EFD Customer Footprint

2.1.8 (U) Advanced Data Ingest and Management (ADIM)

(U) ADIM provides NGA foundation GEOINT products and processes from ingest, through releasability disposition, to dissemination. It is the data ingest and Extract Transform Load (ETL) capability for all of

NGA’s foundation GEOINT data. ADIM provides the metadata and storage retrieval catalog for foundation GEOINT data and allows for the digital receipt of foundation GEOINT, a previously manual process. ADIM processes approximately 70 products with approximately 20 data standards. It is anticipated that more products and standards will need to be added over time.

(U) ADIM utilizes Lambda within cloud native services and a micro-service architecture. It simultaneously occupies an Oracle and open source database. The expectation is to phase out the Oracle database by the end of FY 23. The core of ADIM’s architecture is the Cloud Content Catalog and Product Offering (C3PO), which tracks all logistical aspects of foundation GEOINT content from arrival, through the digital delivery process. This accounts for content that is both acquired and/or created in-house. It accounts for content locations in the cloud and in the data center.

(U) The catalog is replicated using a master-to-master configuration to keep data synchronized with current operations. It utilizes a REST API (C3PO API) for metadata access and transparently filters content for users based on their identity, which is provided by the Enterprise ADIM solution. Metadata comes from content in S3 and from other production databases. Additionally, content is served out through C3PO to meet the needs of OGC standards.

(U) Automated data disclosure is driven by the Release, Redaction, Disclosure, and Dissemination (R2D2) of Foundation GEOINT (FG). Foundation GEOINT Discovery and Releasability Tool (FGDRT) is developing a service enabled FG disclosure and release (D&R) program of record system in the unclassified environment that is architecturally integrated with the Gateway (C3PO), thereby enabling (near) real-time distribution of FG to foreign partners. ADIM’s backend services are currently being modified to ensure that existing service contracts and interfaces are not broken through the use of views to minimize the impact to end users whenever possible. This will be complete and contained in the GCS

Baseline in October 2022.

(U) ADIM is integrated with FGDRT to ensure accurate dissemination of NGA standard geospatial products to foreign partners by capturing disclosure and release decisions in a database record.

Table 2-3 below provides high-level information about projected ADIM usage taken from current NGA

Product Dissemination usage estimate.

Approximate # of customers

Approximate # of data transferred per month

(TB)

Approximate # of files transferred per month

(Millions)

NIPR 3000 630 6

SIPR 1000 310 3

JWICS 2000 500 5

Disconnected

Instances

3 N/A N/A

Table 2-3 ADIM Usage

(U) ADIM provides Data Bundlers, Java Web Backend Services to support foundation data dissemination.

The infrastructure of loading/ingest is drastically different than the NPD one today. Open Data Store (ODS) S3 Dirty/Clean buckets to received data digitally, a collection of micro-services build using lambda and other cloud native services to extract metadata, populate a catalog API (C3PO API) and enhance/modify the metadata and the integration of FGDRT for accurate dissemination.

(U) FGDRT 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 D&R decisions in a database record. Disclosure and release information captured in FGDRT helps provide data to the entire GEOINT enterprise, such as the Defense Logistics Agency (DLA), COCOMS, Foreign Disclosure Offices (FDO) and NGA Support Teams (NSTs). FGDRT has an API with primary data on the unclassified network and accessibility from any SIPRNET/SECNET and JWIC/NGANet network.

FGDRT enables (near) real-time D&R decisions on Foundation GEOINT (FG) automating previously manual activities, taking the time for data release adjudication from weeks to hours. The front end is a web-based requirements and decision capture tool. The backend is cloud native relational data service

(RDS) which stores all D&R decisions on foundational geospatial products and data to the entire GEOINT enterprise. A FGDRT high-level graphical representation is located within Appendix A of the PWS.

(U) FGDRT is built in Lambda with cloud native services and micro-service architecture. The FGDRT API is built using Typescript language hosting in Node.js server-side. The programming language is NestJS API framework and Node.js hosting runtime. The FGDRT user interface (UI) is built using Javascript - hosted in Node.js server-side environment. This primarily runs in the end-user's browser and is based on DevCorps react-template; Javascript programming language, React front-end development framework, and Node.js hosting runtime. The API and front-end is hosted via Docker containers on Kubernetes and other runtimes such as AWS Lambda, multiple supporting libraries, and testing frameworks.

(U) FGDRT is integrated with ADIM so that data obtained from ADIM has the proper release and disclosure information in the form of “obligations,” which, will number in the hundreds of thousands across partitioned tables that connect “products/data” with “customers” (DoDAACs, Country, Country Profile),. Product/Data + Customer(s) = Obligation. This is the heart of FGDRT.

Table 2-4 below provides high-level information about FGDRT usage taken from the 2018 GEOINT Services assessment report.

User Type FY20 Three Year Growth Projection

Total Users 644 >1000

Number of files 500 >1000

Table 2-4 FGDRT Usage

2.1.9 (U) GEOINT Delivery Platform (GDP)

(U) GDP is a service enabled web-based application that provides a catalog of NGA products and allows users to find, view and download NGA's digital holdings through the GCS GDP Data Plug-in API contained in MapStack. GDP displays available digital map product coverage, allows global users to query for products based on certain parameters (i.e. CD name, data load date), estimates download file size, and creates a compressed file for download by preauthorized users across DoD. GDP provides a viewer for most products, and will reformat many product types into an alternate commercial format at user download. Available products are grouped into categories loosely identified by format and file structure.

(U) The Contractor will perform administration of Apache web server, JBoss software, disk usage, memory usage, and server availability.

(U) New items for NGA-produced product series are normally available for download several weeks before being made available on CD/DVD to order through the DLA. GDP is operational on NIPR, SIPR, and JWICS domains and users can download up to 6MB of data at a time.

Approximate number of unique visitors (per month)

Approximate amount of data downloaded per month (GB)

NIPR 1,000 4,500

SIPR 1,500 1,500

JWICS 600 350

Table 2-5 Data Usage

(U) NGA has developed and migrated into operations the GDP Plugin (Frontend Viewer) during FY 21

MoW.

(U) The primary functions of GDP’s backend include:

makeTarZip

Product footprints OCG compliant web services: integrates with ArcGIS Server to provide RESTful interface queries, WMS and WFS Queries, Geotrans, GEONames Query, Airfield Query, World Port Index (WPI) Query, and Assault Zone Query.

Download Service: provides CADRG and other products, CD based downloads, spatial download capabilities, country downloads, and MBR/point/line downloads.

Report Service: provides download file size estimation, web service based product definitions , exposure and compatibility to external processes and clients, and user customizable product availability reports.

Oracle Spatial GDP Product Tables : provide standard product tables, country, state and AOR based tables for all products, and performs spatial intersections at data load time.

Imagery and Basemap tiles

Data bundling capabilities

2.1.10 (U) Website Hosting

(U) The Web Hosting capability provides infrastructure for websites and applications, which consist of a mix of intranet/corporate and external facing sites across NIPR, SIPR and JWICS. There are approximately 100 websites on NIPR and 160 websites each on SIPR and JWICS. Product and/or application owners external to GeoCapabilities Divison (TEDG) are responsible for updating their content and/or application.

In addition to the 260 websites, the GCS web hosting capability maintains the agency’s GEOINT Foundation information across nine separate.

Most of the aforementioned sites utilize one or more of the following technologies: HTML, JavaScript, PHP, Oracle Database, MySQL, Apache Server, Windows, and/or Linux. A small number of websites leverage Cold Fusion.

The Government does not intend to expand web-hosting capabilities. To the contrary, the number of hosted websites is expected to decrease as product and application owners are encouraged to leverage other means to acquire the infrastructure required to host their applications.

Note: the owners of the hosted websites are responsible for updating their content; GCS provides the infrastructure.

3 (U) RDT&E - Incorporate New Features/Functionality into GCS Software

Baseline

(U) The Contractor shall incorporate new features into the baseline, support customers and systems throughout the NSG, ASG, and other current and future user groups to capitalize on new initiatives to enhance the user experience. Using a cloud-based foundation and following agile software development methodologies (e.g. Scaled Agile Framework (SAFe), etc.), the Contractor shall adapt and extend GCS as necessary to access and leverage data held and served through consolidated data storage and dissemination architectures using a properly implemented API Lifecycle Management strategy to facilitate successful cloud operations and enable consistent integration patterns including consistent interactions with other systems. The Contractor shall, without exception, enable data to be accessed via APIs without manual process intervention. Utilizing MapManager, the MapStack configuration management tool, the Contractor shall optimize the legacy software, a service-centric architecture, and future GCS developments for standards conformance, interoperability, and complimentary functionality with other NSG and ASG service consumers and providers. New features will be incorporated into the GCS software baseline (following each Sprint Cycle and PI). Feedback from GCS consumers and providers will form the basis for developmental direction/inclusion and the Contractor shall be expected to team with technical representatives of other stakeholder programs to optimize GCS capabilities for all users. A listing of key consumers and providers include, but are not limited to:

eXploit Structured Observation Management (SOM) – context cloud-based web application designed to provide users the ability to capture and record observations and objects with searchable metadata and add them to the repository of shared GEOINT databases

FM2i (Full-Motion – Motion Imagery) – NGA’s program responsible for exploiting UAV tracks and their full motion video streams

GEOAxIS – NGA’s identity management service

FGCMS – NGA’s source for foundation GEOINT content

GEOINT Search and Retrieval (GSR)

Analytical Services Contract

NGA Research Directorate initiatives and other emerging technologies

Enterprise Configuration Management (CM)

GIMS (GEOINT Information Management System)

Other Sensor Integration Program Offices

(U) Various NGA Directorate Offices within Analysis and Source Foundation Adaptation emerging data architectures for NGA and the IC, in conjunction with the requirements of this PWS, shall position the

GCS Program to support Core Services and interaction with SOM content and the application of Activity- Based Intelligence (ABI) methodologies. The Contractor shall utilize all needed GEOINT capabilities/functions in seeking innovative methods to further merge existing and emerging geospatial capabilities into a single geospatial immersive environment. The Contractor shall fully enable the program to provide capability and data access, to include data download for NGA’s MapStack, GE, IC GIS Portal, disconnected platforms, and GEOINT management and presentation strategy IAW NGA Tech and 2025 Strategy.

3.1 (U) Prototypes

(U) The Contractor shall develop and provide prototypes as specified by the Government to allow for testing and evaluation by both the Contractor and Government. If a prototype is deemed acceptable, the Government will determine whether to incorporate further requirements into the backlog and deliver the prototype to operations. The Government anticipates approximately two prototype efforts annually.

Prototypes assessed for conformance to GEOINT standards shall be tested to verify their incorporation into the operational baseline(s). All subsystem dependencies that have not been identified to be included in a prototype shall be identified in writing before delivering the prototype. Additionally, a Requirements Traceability Matrix (RTM) shall be delivered with the prototype. The RTM shall include the verification criteria for each requirement established by the Government, in order to provide testing.

(U) The Contractor shall maintain a developmental working environment (e.g., a digital test environment in the Top Secret security domain) allowing NGA stakeholders to determine, evaluate, and test solutions. The environment shall mirror the operational environment and be hosted within the NGA IC Common Operating Environment (COE) and accessible through Desk Top Enterprise (DTE). The Contractor shall maintain all GCS software in this environment. The development environment shall replicate the minimal operational functionality needed to test prototypes, and experimentation features under development.

4 (U) GCS General Requirements

(U) This requirement is for non-personnel services. The Government shall not exercise any supervision or control over the service provider(s) performing the services herein. Such service provider(s) shall be accountable solely to the Contractor who, in turn is responsible to the Government. The Contractor shall provide personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform the services as defined in this PWS, except for those items specified as Government furnished property and services. The Contractor shall perform to the standards in this PWS. IAW FAR 7.503, the Contractor shall not perform any inherently governmental functions.

4.1 (U) Business Analytics/Metrics

(U) The Contractor shall establish a process for gathering and assessing both…