20221121_U_Stardust-Base-PWS_v0.6.pdf

UNCLASSIFIED

National Geospatial-Intelligence Agency

Performance Work Statement for

Stardust Base Requirements

Foundation GEOINT Integrated Program Office Earth Modeling Project

Version 0.6 November 21, 2022

Change Table Date Affects Description Author Version

11/21/22 All Initial RFI Draft OCS 0.6

Table of Contents

1.0 Background and Purpose

2.0 Objectives

3.0 Global Tasks

3.1 Program Management

3.2 Development, Test & Acceptance, and Transition to Operations

3.3 Reachback Support

3.4 Transition In/Out Support

4.0 Functional Area 1: Platform Services

4.1 Cloud Architecture and Engineering

4.2 DevSecOps Engineering and Configuration

4.3 Cloud Optimization, Tooling, and Migration

5.0 Functional Area 2: Application Services

5.1 Content Services

5.2 Development Services

5.3 Geosciences

5.4 Elevation

5.5 Global Navigation

5.6 Precise Imagery

5.7 Geodetic Surveys

6.0 Contract Administration & Details

6.1 Deliverables, Required Events, and Quality Assurance Surveillance Matrix

6.2 Period & Place of Performance

6.3 Key Personnel

6.4 Security

1.0 Background and Purpose

The National Geospatial-Intelligence Agency (NGA) employs Integrated Program Offices

(IPOs) to design, build, test, deploy, and sustain capabilities for systems supporting NGA’s mission and operations. The Foundation GEOINT IPO (IPF) is partnered with the Foundation GEOINT Group (NGA/SF) within NGA’s Source Operations and Management Directorate (Source). NGA/SF is responsible for providing foundational content and services associated with a variety of NGA’s mandated missions, including Safety of Navigation and military planning/operations support.

Within NGA/SF, the Office of Geomatics (NGA/SFN) is specifically tasked with developing and maintaining standards/capabilities/services for the following:

• The World Geodetic System 1984 (WGS 84), which underpins most global Positioning, Navigation, and Timing (PNT). WGS 84 consists of a Terrestrial Reference Frame (TRF), Earth Gravitational Model (EGM), and World Magnetic Model (WMM).

• Digital Elevation Models (DEMs), point clouds, and other 2D, 2.5D, or 3D content types utilized in mission planning, space awareness, and targeting applications.

• The Global Positioning Satellite (GPS) system and Global Navigational Satellite System

(GNSS) data provisioning, analysis, and modeling such as Earth Orientation Parameters (EOP) and Precision Timing.

• Precise Imagery including the Controlled Imagery Baseline (CIB), Digital Point Positioning Database (DPPDB), orthorectification, geopositioning services, and accuracy assessments.

• Geodetic Surveys supporting the establishment and maintenance of ground control points along with their positional, gravimetric, and magnetic attributes.

• Other geosciences including, but not limited to, coordinate/datum conversions and subsurface/tectonics modeling.

Geomatics mission systems were historically purpose-built, and the IPF/Earth Modeling project was established to assist in sustaining and/or modernizing legacy capabilities. Earth Modeling has ongoing efforts to refactor, (re)configure, optimize, virtualize, cloud-enable, and/or cloud-migrate these systems. The desired end-state architecture will have all these systems migrated to modern, cloud-based provisioning environments while using DevSecOps approaches, service-oriented architectures, modern code management tools, and current programming languages.

The Earth Modeling project utilizes the NGA strategy to prioritize and measure the progress of its activities.

As part of the NGA Director’s Moonshot initiative, the agency is modernizing against its Mission Imperatives including Assured Positioning, Navigation, Timing, and Targeting (APNT&T). This imperative has been decomposed into four critical capabilities:

• Safety of Navigation, primarily in the Aeronautical and Maritime domains;

• 3D GEOINT, which is an evolution merging 2D imagery, 2.5D rasterized elevation models, and other data such as point clouds into derived products consumed natively in 3D environments;

• Target Coordinate Mensuration (TCM), which relies on Elevation (DEMs), Precise

Imagery, and geopositioning data; and,

• WGS 84 and associated modeling/geosciences.

Geomatics mission system modernization related to APNT&T will also meet the dual need of preparing the NGA/SFN workforce to transition to the Next NGA West (N2W) campus, currently estimated to occur during Fiscal Year 2026. Lastly, NGA is establishing a Foundation GEOINT Statement of Capabilities (SOC) which details specific Required Performance Metrics

(RPMs) for these modernization efforts. The FG SOC Increment 1 will approve development efforts, goals, and related RPMs for delivery during and/or beyond the Fiscal Years 2025-2027 timeframe.

The purpose of the Stardust program is to provide Earth Modeling capabilities development and integration aligned to APNT&T, N2W transition, and the forthcoming FG SOC Increment 1. In summary, Stardust will result in the modernization of Geomatics IT systems and infrastructure within the desired end-state. As part of this modernization, the program will provide assessment, engineering, and micro-services development to optimize both the systems and the intended cloud environment. Additionally, Stardust will transition and continue feature development of Minimum Viable Products (MVPs) delivered by the NGA Research Directorate’s (NGA/R) Geophysics Pod in support of NGA/SFN.

2.0 Objectives

The Stardust PWS provides services for the for research, development, test, evaluation, integration, and enhancement of Earth Modeling software and content. All performance under Stardust will capabilities development from among the services cataloged in Sections 3-5 of this document.

In addition to the Stardust global tasks delineated in Section 3, this PWS will provide services to IPF/Earth Modeling and NGA/SFN in these Functional Areas (FAs):

• Functional Area 1 - Platform Services: engineering, configuration, tooling, micro-services, and cloud-migration assessments to assist Earth Modeling entities transition to a cloud-ready or -native state of operations

• Functional Area 2 - Applications Services: design, development, testing, integration, and deployment of applications which fulfill the Geomatics mission space

3.0 Global Tasks

This section of the base Stardust requirement details those non-functional requirements and services to be provided by all contractors receiving an award under this program.

3.1 Program Management

Stardust contractors shall assist in the monitoring and reporting of cost, schedule, and performance for all activities decomposed from Earth Modeling Epics and Minimum Viable Products. Vendors will collaborate with the IPF/Earth Modeling project office to ensure prompt invoicing, onboarding/offboarding of cleared personnel, and delivery of CDRLs specified in each award. At a minimum, all Stardust contractors shall deliver the following:

• Monthly Financial Reports detailing data points such as awarded value, funded value, year-to-date totals, and estimate at completion.

• Monthly Technical Reports that breakdown progress against Earth Modeling products and milestones such as MVP, Authority to Operate (ATO), Full Operational Capability (FOC), and associated support activities.

3.2 Development, Test & Acceptance, and Transition to Operations Hybrid Methodology. A cross-component collaboration within NGA resulted in the “Cloud

City” project, which employs a hybrid of the Scaled Agile Framework for the Enterprise (SAFe), SCRUM, and Spiral development paradigms. Stardust contractors shall leverage their internal software development practices while integrating into Cloud City activities, such as quarterly Planning Events and backlog grooming.

Engineering and Technical Documentation. The Stardust program shall adhere to the NGA IT

Acquisition Design Elements (ADE). The NGA IT ADE in turn stipulates usage of the IC Program Architecture Guide (PAG), v2.0, for systems modeling. Stardust contractors should be prepared to deliver architectural views and viewpoints conforming to those required for non-

Major Systems Acquisitions (non-MSAs). See Appendix A for associated non-functional requirements.

Other documentation required for Certification to Field (CTF), Authority to Proceed (ATP), and

ATO shall be maintained at all times. Related documentation will include, but is not limited to, configuration control baselines, security test results, and Software Approval Process (SWAP) documentation for open source code libraries.

Minimum Viable Product. NGA employs Product Managers (PdMs) within its Operating Model.

Stardust developers will support PdMs in delivering on their roadmaps, against Minimum Viable Product (MVP) functional requirements and specifications, while retaining flexibility to engage emerging user needs or National System for Geospatial-Intelligence (NSG) priorities. Stardust teams shall utilize Government Furnished Information (GFI) which define MVPs and additional features/functionality leading up to FOC. Stardust teams shall contribute to the delivery of MVP artifacts that may include, but are not limited to:

• Mission Model Canvas;

• Lightweight Business Case;

• User Stories;

• Vision Storyboards;

• Design Sprint Prototypes (e.g., mock-ups, models, wireframes); and/or

• Customer-Validated MVP Decision Document with acceptance criteria.

GEOINT Content Standards. Where a capability delivered under Stardust involves the production of GEOINT content (data, products, and services), the contractor shall support NGA Image Quality and Utility (NIQU) testing of the content, applicable algorithms, metadata, and data formats. Other standards compliance testing may be required by NGA/SFN or other offices.

Standards requirements may include, but are not limited to:

• Delivery of engineering and technical documentation (e.g., Integrated Dictionary, AV-2 or data implementation profiles) prior to the onset of testing;

• Buildout of reference libraries with content templates and training data;

• Delivery of test product samples for quality assessments;

• Technical Debt incurred, similar to Deficiency Reports (DRs), to resolve issues identified by the NIQU, SFN, or other NGA organizations; and

• Preparation and maintenance of configuration baseline and change management materials.

Deployment. The MVP is considered a “70% solution” at this phase in the product roadmap.

Stardust development teams shall support the PdM, security personnel, sustainment providers, and other contributing partners in deploying the capabilities through the DevSecOps pipeline into the intended operational environment. Stardust contractors should assume that additional features or tasks will be required from the Epic or product roadmap to reach FOC.

Transition to Operations. Following successful deployment of any new MVPs, Stardust developers shall assist the PdM in transition to operations. Depending on the maturity of the product, these activities may include, but are not limited to:

• Development of environment-specific features and stories;

• Training materials;

• Demonstrations, briefs, and/or other user engagement;

• User feedback and validation (“built the right thing”);

• Technical Documentation and Source Code delivery;

• Interface management; and/or

• Platform integration.

3.3 Reachback Support

The IPF Integration & Operations Project manages the FG Sustainment Services (FS2) program which, among other service categories, provides software maintenance and operations support across multiple systems and environments. As such, purely operations and sustainment (O&S) functions are out of scope to Stardust.

However, Stardust development teams shall be prepared to provide reachback support to correct DRs and other Tier III/IV issues that cannot be resolved by FS2 sustainers. Additionally, Stardust teams will perform adaptive and perfective maintenance in response to changing operational environment configurations, and/or emerging customer needs post-MVP/FOC.

3.4 Transition In/Out Support

Stardust contractors shall implement the processes and knowledge management frameworks necessary to support the transition of entities/systems/capabilities from legacy Earth Modeling contracts to Stardust. Similarly, Stardust developers shall support incoming vendors for any follow-on programs/contracts. The goal in any transition in/out scenario would be the successful turnover of engineering/technical documentation, personnel onboarded, accounts created, and other activities for the initiation of systems development within 60 days of the start of a Base Period of Performance. Example tasks include, but are not limited to:

• Providing a Transition-In Plan within 30 Days of a Stardust award.

• Providing a Transition-Out Plan within 60 Days prior to the expiration of a Stardust award.

• Maintaining up-to-date program and/or product management plan(s), including details for in-progress and upcoming activities or events.

• Maintaining program, engineering, and technical documentation in a centralized, accessible location.

• At the Government’s discretion, participating in transition planning events.

4.0 Functional Area 1: Platform Services

In collaboration with the GEOINT Services Office (NGA/TEG) and the GEOINT Conveyance Office (NGA/ST), IPF/Earth Modeling and NGA/SFN have delivered a target environment for migration of all cloud-ready Geomatics mission systems. The Geomatics Virtual Private Cloud

(VPC) leverages NGA/TEG’s Common Operating Release Environment (CORE) for DevSecOps tooling and Continuous Integration/Continuous Delivery (CI/CD) pipeline.

NGA/ST’s Source Content Dissemination Services (SCDS), also known as Geospatial Product Modernization (GPM), provide common platform services for Foundation GEOINT producers and developers. The Geomatics VPC combined with SCDS/GPM, collectively “GGPM,” provides the intended development, testing, and operations environments for most capabilities to be delivered under Stardust.

IPF/Earth Modeling is also responsible for the Geospatial Repository and Data (GRiD) management system, NGA’s enterprise system for all Elevation-related 2D, 2.5D, and 3D content. GRiD is currently a standalone cloud-native platform and applications storefront separate from GGPM. Any Stardust awards associated with Elevation capabilities should consider the target operations environment to be GRiD, not GGPM.

4.1 Cloud Architecture and Engineering

These include services to analyze and recommend approaches to the Earth Modeling project for the GGPM and/or GRiD platforms. Examples tasks include, but are not limited to:

• Cloud Environment Architectures: developing system-level or overall Earth Modeling architectures enabling optimal integration and delivery of capabilities into production.

• Systems Modernization and Cloud Migration Assessments: developing modernization proposals for legacy Earth Modeling systems, with an emphasis on cloud-ready or -native solutions.

• Delivery Management: Collaboration with applications or platform developers who are onboarding new capabilities, tooling, or micro-services. Contribute to, manage, and maintain an overall Earth Modeling backlog to identify schedule, interface, and other dependencies/risks and work to mitigate across development teams.

• Application Provisioning & Support: For developers deploying new systems or applications to GGPM or GRiD, support application check-in, initial system testing, performance assessments, quality assessments, and provide feedback on additional features or measures needed for successful deployment.

4.2 DevSecOps Engineering and Configuration

Under Stardust, contractors should anticipate active planning and implementation of tasks or processes which optimize the delivery of applications into the GGPM or GRiD environments.

Example tasks include, but are not limited to:

• Configuration Management: Establishing and maintaining VPC configuration baselines, to include the creation/monitoring of infrastructure elements (e.g., virtual machine instances, database instances, storage devices, etc.)

• Persona Management: Baselining of Identity and Access Management (IDAM) roles, rules, and associated features (e.g. identity tokens, group accounts, etc.) in support of the Information Systems Owner (ISO).

• Environment Management: Initial creation of environment management and reporting features, such as notification mail groups, billing reports, performance monitoring reporting, etc.

• Pipeline Management: Documenting roles/responsibilities within the NGA DevSecOps environment (CORE) and updating baseline/configuration document as needed.

• Transition Management: Supporting the transition of ownership for deployed, FOC capabilities to an enterprise integration / operations & sustainment provider, including onboarding and training the enterprise provider to assume ownership.

• Accreditation Management: Completing the necessary security accreditation and certification for the DevSecOps environment. Provide support to other developers deploying to the target environments.

4.3 Cloud Optimization, Tooling, and Migration

Stardust development teams will engage Senior GEOINT Officers (SGOs), SMEs, analysts, and other engineers or developers to assist in migrating legacy Geomatics systems to cloud environments. Additionally, Stardust developers should anticipate the need to build micro-services to assist in the performance of either the applications targeted for cloud transition, or the cloud environment itself. Example tasks include, but are not limited to:

• Code Packaging and Deployment: Develop containerized software packages to deploy from a data center to a cloud environment. Provision the application in the target environment.

• Content Migration: Redeploy/Rehost databases and content from data center locations to cloud-provisioned environments.

• Content Services Optimization: Identify issues, propose fixes, and deploy tools to improve the ingest, conditioning, discoverability, access, and dissemination of Geomatics content at the platform level.

• Application Optimization: Identify gaps in the platform architecture preventing scalable, high-performance operations of applications in GGPM or GRiD, and develop/deploy micro-services enabling integration of legacy.

5.0 Functional Area 2: Application Services

Stardust contractors shall design, build, test, and deliver software code for applications.

Applications development may include integration and/or customization related to COTS, GOTS, and FOSS which otherwise meet the needs of Geomatics Product Managers. Stakeholder needs shall be documented via Product Kick-Offs, and development requirements shall be prioritized & approved during Program Increment (PI) events. These requirements may be refined during Sprint Planning, with the concurrence of the Product Manager.

Stardust products and applications delivered under FA2 will be targeted for deployment into the GGPM or GRiD environments, as appropriate. In limited circumstances, Stardust developers may support the (re)configuration, refactoring, and optimization of legacy Geomatics mission systems to improve performance in a data center environment.

Under Stardust, mission-based Earth Modeling stakeholders (e.g., SMEs in NGA/SFN) serving as Product Managers will assist the IPF PMO in determining content, applications, and capability requirements. The services delineated in Sections 5.1 and 5.2 are cross-cutting requirements, while Sections 5.3 through 5.7 detail specific Geomatics customers and the range of requirements that may apply to Stardust.

5.1 Content Services

In addition to the requirements contained within Section 3.2, GEOINT Content Standards, Stardust applications developers shall be prepared to provide additional content services including, but not limited to:

• Content ingest, conditioning, metadata tagging, and provenance;

• Content format transformation, translation, and conversion;

• Content search, filtering, and retrieval;

• Content curation consulting with NGA analysts or data stewards; and,

• Content account creation, management, and maintenance.

5.2 Development Services

Under FA2, Stardust contractors will provide a range of applications development support to NGA/SFN customers. This may include, but is not limited to:

• Software code development;

• Software code refactoring and modernization modern architectures, programming languages, and/or provisioning environments;

• Software library management;

• Software configuration and change management;

• Software test and evaluation support;

• Software provisioning and deployment;

• Software training support;

• Software transition to sustainment support; and,

• Software sunsetting and retirement.

5.3 Geosciences

The Geosciences Division (NGA/SFNA) provides geodetic, geotechnical, and geophysical science content which improves the accuracy of GEOINT products. This includes production of the EGM and WMM to support WGS 84. Examples of geosciences systems and applications which may be supported under Stardust include, but are not limited to:

• Geodesy and Geophysical Enhanced Production System (GGEPS)

• GeoHazards, Indications, and Potentials (GeoHIP)

• Compensation for Active Tectonics (CAT)

5.4 Elevation

The Elevation Division (SFNE) provides foundational expertise for the production, validation, and management of DEMs, point clouds, and other 2D, 2.5D, and 3D content. Presently, GRiD is the primary environment for all Elevation capabilities. However, on any applicable Stardust award, developers may deliver containerized FOSS micro-services to NGA co-production partners enabling the interoperable ingest, production, quality control, and dissemination of Elevation content. Examples of Elevation services supported under Stardust may include, but are not limited to:

• 3D Tiles;

• DEM conversions (e.g., DSM to DTM);

• Imagery conversions (e.g., Imagery to DEM, Point Cloud, or 3D Mesh)

• Point Data Abstraction Library (PDAL);

• Spatio-Temporal Asset Catalog (STAC); and,

• Cloud-Optimized Point Clouds (COPC).

5.5 Global Navigation

The Global Navigation Satellite System (GNSS) Division (NGA/SFNG) ensures that the WGS 84 system is available for navigation and targeting applications, as realized within GPS. The division is also responsible for producing the TRF. Examples of GNSS systems and capabilities which may be supported under Stardust include, but are not limited to:

• GNSS

• Civil Signal Monitoring System (CSMS)

• Precise Unified Geodetic System with Limited International Tactical Exposure (PUGS

LITE)

5.6 Precise Imagery

The Precise Imagery Division (NGA/SFNP) is responsible for a range of products, standards and analysis which improve imagery accuracy and assists in the validation of imagery sources and derived imagery data for different mission applications. The division is also responsible for the production of orthorectified imagery, such as the Controlled Imagery Baseline (CIB), and stereo imagery content, such as the Digital Point Positioning Database (DPPDB). Examples of precise imagery systems and applications which may be supported under Stardust include, but are not limited to:

• Active Earthscape

• Geospatial Data Analysis Tool – Multisensor (GDAT-M)

• CIB/ECIB Data Analysis Tool – Modernized (CDAT-M)

• Precise Imagery Management System (PIMS)

• Geopositioning-as-a-Service (GPaaS)

5.7 Geodetic Surveys

The Geodetic Surveys Division (NGA/SFNS) performs geodetic, geophysical, and geotechnical data collection to develop ground truth data related to WGS 84 production and maintenance.

The division also supports site surveys utilized for flight safety and systems calibration, among other mission applications. Examples of geodetic survey systems and applications that may be supported under Stardust include, but are not limited to:

• Geodetic Survey System (GSS)

• Multi-Use Geodetic Sensor System (MUGSS)

6.0 Contract Administration & Details

6.1 Deliverables, Required Events, and Quality Assurance Surveillance Matrix The Stardust Contracting Officer’s Representative (COR) shall evaluate performance through the indicated surveillance methods below, to include inspection and acceptance of deliverables and services. While this table refers to overall performance requirements, the Government may require sprint deliveries, in-progress reviews, code commits/releases, or other incremental status indicators based upon the awardee’s technical approach. Additional performance standards or changes to the Quality Assurance Surveillance Plan (QASP) may be applicable to specific

Stardust efforts.

Deliverable/Event Performance Standard Minimum Threshold Frequency Surveillance Method

Program Kick-Off Meeting

Hosted by IPF/Earth Modeling. Contractor-led introductions of key staff with a discussion of program strategy, action items, assumptions, and known risks.

1) Introduces Key Personnel and senior contractor staff

2) Initial POA&M for transition and product kick-offs

5 days after award

Review of materials and attendance at Kick-off

Knowledge Management

Repository

1) Online repository to host programmatic, engineering, and technical documentation

2) Utilized to facilitate

Increment, Sprint, and other planning/review events.

1) Developer Jira/Confluence pages connected to IPF/Earth Modeling Epics

2) Product artifacts per

Section 3.2

30 days after award, updated each Sprint thereafter

1) Review of materials during planning events

2) Periodic inspection

Transition-In Plan Details start-up activities to engage stakeholders and departing contractors to train on existing products/systems and accept related documentation.

Enables product and/or increment planning kick-offs within 60 days of start of Base PoP

30 days after award

Manual review and participation in transition events/meetings

Code Repository 1) Version-controlled NGA GitHub code repository for inspection and Quality Control

2) Code is unobfuscated and commented

0 linting errors and 0 warnings

Prior to completion of each release

Manual review and automated testing in code compilers

Code Testing Developer conducts security testing and delivers reports indicating substantive coverage and results.

80% coverage for functionally relevant code within a relevant environment

Prior to ATP for each release

Manual review of scans (e.g., Fortify), inspection of SWAP approval requests

Product Verification & Validation

Committed code must successfully compile, build, and instantiate in a staging/test environment for stakeholder testing and inspection

1) 0 critical errors in an operationally relevant environment

2) 100% of Stakeholder-identified DRs and bugs resolved

3) 100% of MVP functions, user stories, and use cases validated

Prior to ATO 1) Signed MVP Acceptance Document

2) Signed FOC

Acceptance Document

3) User surveys and feedback

Product/System Design

Documentation

Documents adhere to NGA IT ADE, DoDAF, or other standards and templates, where applicable

1) Required systems/services views per IC PAG 2.0

2) Configuration Control Baseline/SW

Library

3) Product/System

CONOPS

1) Prior to deployment of first release

2) Updated each release thereafter

Manual review and feedback from

IPF/Engineering team

Authority to Operate (ATO) Events

Developer incorporates technical debt, dependencies, and other schedule considerations into Program, Increment, and Sprint backlog planning.

1) Scans, assessments, and other security artifacts responded to within 48 hours

2) DRs resolved within 5 business days

As needed for deployments t

Coordination through NGA/IPF, CORE, or security and onboarding partners

Product Kick-Off

Meeting(s)

Per Section 3.2, developer captures and documents stakeholder needs leading up to the definition of the functional baselines for MVP and FOC.

1) PdM-validated

MVP functions

2) PdM-validated acceptance criteria

Prior to start of first Increment, then for each assigned Epic thereafter

Signed MVP Decision

Document

Program Increment

(PI) Plans

In coordination with

NGA stakeholders, produce a prioritized issue backlog (Epics, Features) for each PI.

1) Participation in/ presentation at Cloud City Planning Events

2) Backlog grooming and prioritization conducted with

PM/PdM

Every 12 weeks

Feedback and/or

Interviews with

NGA/IPF, NGA/SFN,

and other event participants

Sprint Plans In coordination with NGA stakeholders, produce a prioritized task backlog with allocated story points.

1) Re-validated backlog with concurrence from

PdM

At least bi-weekly

Stakeholder surveys and feedback

Monthly Technical

Report

Contractor formatted technical and financial reports which detail schedule and performance progress for each calendar month.

1) Indicates completion status at Task, Feature, and Epic levels

2) Highlights known/emerging risks and issues

By the 15th calendar day of the following month

Manual review and stakeholder feedback

Monthly Financial

Report

Contractor formatted cost report which details

1) Realistic EAC provided for PoP

By the 15th calendar day of the

Inspection prior to review of invoices monthly and YTD actuals.

2) Costs allocated to applicable NGA capital asset(s) following month

Program

Management Reviews

Informs NGA stakeholders on cost, schedule, performance, security, risk, and contract administration factors.

1) Highlights technical accomplishments

2) Provides cost and schedule baseline updates

3) Identifies and proposes mitigation for emerging risks

Quarterly Quarterly quality surveys, annual performance assessment report

(PAR)

Transition-Out Plan Details cross-training and the handoff of system/product documentation during any contractual turnover.

1) Identifies technical debt related to cross-training

2) Identifies location of specific products/documents within the Knowledge

Management Repository

At COR direction, or

60 days before contract expiration

Manual review and participation in transition events/meetings

6.2 Period & Place of Performance

Base Period of Performance of up to 12 months. Awards may include up to four (4) 12-month Option Periods.

The Place of Performance for Stardust will be determined by the requirements in each individual award, as well as the Contractor’s Technical Approach. Use of “build low, move high” principles are encouraged wherever possible. However, a minimum presence or availability at NGA facilities in Springfield, VA or St. Louis, MO will be required to support Kick-Offs, PMRs, and product code staging, testing, and deployment into operations in the Secret (SC) and

Top Secret (TC) cloud domains.

Other Direct Cost (ODC) line items for travel and training are anticipated. Local travel (<50 miles) will not be reimbursed.

6.3 Key Personnel

The following positions are considered Key Personnel on all Stardust awards:

• Technical Lead, who serves as the primary POC for all coordination among the

Contractor, Government Program Manager (PM), COR, Contracting Officer (CO), and Product Manager(s)

• Software Development Lead

• Engineering & Integration Lead

One individual can fill more than one role. Following the award of a Stardust contract, contractors shall provide updated résumés and contact information for all approved Key

Personnel, for the IPF/Earth Modeling office to retain on file.

6.4 Security

Only United States citizens are authorized to perform work on Stardust awards.

The following are Classified Work Performance Requirements on all potential Stardust awards:

• Contractor personnel performing Top Secret/Sensitive Compartmented Information

(TS/SCI) work on Stardust contracts are required to have active TS/SCI clearances for access to NGA facilities, when performing duties within TS/SCI environments, and for access to TS/SCI NGA computer systems. Contractors are subject to a

Counterintelligence Polygraph as requested by the Government. NGA will sponsor TS/SCI security clearances, NGA Badges, Common Access Cards (CAC) and other items (example: parking hangtag) for required contract personnel.

• Contractors must abide by the DD Form 254 - Contract Security Classification

Specification and applicable security policies and regulations.

• Contractor personnel shall follow all applicable NGA, IC, and DoD information security and operational security policies and guidance when accessing and transmitting data over networks during performance of agreement requirements.

• The contractor shall inform the Government when its employees no longer support the contract (see DD254). The Government desires notification prior to the day the individual no longer supports the contract, but requires notification no later than the day support ends. If contractor personnel will no longer be supporting NGA via an NGA contract, any debriefing paperwork, notifications, and/or requests for further direction from the COR or Industrial Security shall be turned into the NGA Workforce Support Center, NGA Site Security Office, or the COR. If contract personnel are unable to turn these items into the

NGA Workforce Support Center, NGA Site Security Office, or COR then it is the contractor’s security office’s responsibility to collect the items from the individual. If the contractor debriefs the employee, the contractor shall send a copy of the debriefing statement, plus any Government items (i.e. NGA Badge, CAC, Courier Card, parking hangtags, etc.) within four (4) business days (timeline may be extended with authorized documented exceptions by NGA Security) to an NGA Site Security Office or the NGA Workforce Support Center.

• All classified work performed at a non-NGA facility must be approved by the COR.

• Cleared contractor personnel may be authorized to hand-carry contract-related classified information as authorized by the COR. Contract personnel will obtain NGA courier authorization prior to hand-carry of contract-related classified data. Contract personnel will be limited to hand-carry classified information between the contractor facilities and

NGA facilities only.

• Any classified work performed at collaborator sites must be performed in either an NGA accredited SCIF or an Other Government Agency (OGA) SCIF that has either a Memorandum of Agreement (MOA), Memorandum of Understanding (MOU), Joint Use

Agreement, or Co-Use Agreement with NGA for this contract.

• Contract personnel are forbidden from bringing in prohibited, unauthorized, and/or Portable Electronic Devices (PEDs) items into any NGA installation or any office/working location at which work is performed under this contract. A list of PEDs includes but is not limited to cell phones, cameras, two-way pagers, laptops, recorders (digital, tape, etc.), flash drives, or any other kind of removable media, without prior approval and approval paperwork from NGA. See NGA instructions/regulations/policy for a full list of prohibited and unauthorized items. Security violation repercussions will be determined on the severity of the violation.

The following are Unclassified Work Performance Requirements on all Stardust awards:

• Uncleared Contractor personnel are authorized to work on this contract up to the

Unclassified level, with access to DoD Controlled Unclassified Information (CUI) at the Contractor site without the requirement of a security clearance.

• Any Contractor personnel working with CUI information must receive a favorable

HSPD-12 and/or HSPD-12 Tier 1 adjudication prior to accessing CUI information.

Contractor personnel who require access to CUI for 60 days or less must receive a favorable HSPD-12 adjudication. Contractor personnel who require CUI access for greater than 60 days must receive a favorable HSPD-12 Tier 1 adjudication.

• NGA will sponsor the HSPD-12 and HSPD-12 Tier 1 background investigation for required program personnel.

o NOTE: Contractor personnel submitted for SCI access cannot be submitted for a HSPD-12 or HSPD-12 Tier 1 adjudication while waiting for their SCI approval.

• Contractor personnel shall not release any unclassified information, regardless of medium (e.g. film, tape, document), pertaining to any part of this contract or any program related to this contract, unless the COR has given prior written approval or in performance of a project that has been scoped and negotiated by NGA.

• Contractor personnel visiting NGA facilities and/or sites will receive the appropriate visitor badge and be escorted, as appropriate. The visitor badge will be returned at the end of each visit day. NOTE: NGA reserves the right to refuse access to personnel when necessary.

• Contractor personnel are forbidden from bringing in prohibited, unauthorized, and/or Portable Electronic Devices (PEDs) items into any NGA installation or any secure office/working location covered under this agreement. A list of PEDs includes but is not limited to cell phones, cameras, two-way pagers, laptops, recorders (e.g. digital, tape, etc.), flash drives, or any other kind of removable media, without prior approval and approval paperwork from NGA. See NGA instructions/regulations/policy for a full list of prohibited and unauthorized items. Security violation repercussions will be determined on the severity of the violation.

The following are Information Handling Requirements on all Stardust awards:

• Contractor personnel will comply with the NGA, DoD, and IC policies and regulations

(to include, but not limited to, the Consolidated NGA (CoNGA) Security Classification Guide) to properly mark (to include portion marking) classified and unclassified documentation, media, etc.

• Document markings will be in accordance with the lowest security classification possible to ensure the confidentiality and integrity for the greatest release to partners in accordance with NGA and mission partner marking guides for classified information.

• All Government-furnished information released to the Contractor or created in the performance of this contract will be destroyed or returned by the Contractor to NGA upon contract termination or when no longer required for contract performance. The determination to destroy or return will be at the direction of the NGA CO or COR.