CBL-GNSS_As-Is_and_Aspirational_Endstate.pdf
PDF 402 KB Posted
- Attached to
- FS3i-RFI
- Solicitation number
- FS3i-TBD
About this file
This document is a government file related to a federal contract opportunity. The file provides an overview of the GNSS (Global Navigation Satellite System) Content & Workflow program within the National Geospatial-Intelligence Agency (NGA). The key objectives are to obtain PNT (Positioning, Navigation, and Timing) content from a robust selection of sources to provide highly reliable PNT data to customers, and to expand the GNSS data collection sites to include SLR (Satellite Laser Ranging) and VLBI (Very Long Baseline Interferometry) in addition to GNSS to enable NGA to independently produce the WGS-84 reference frame. The program plan outlines milestones for GNSS site expansion, PNT data resiliency and diversity, and space product production through FY 2028. The related federal contract opportunity is an RFI (Request for Information) seeking information on how a contractor could provide sustainment, support, software, and integration services for the current Foundation Geospatial-Intelligence (FG) system baseline and future integrated capabilities.
View the file
Other files
Show all 25
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
UNCLASSIFIED
PE2 - GNSS Content & Workflow
1. End State Visual Graphic
(U) At a high level, the mission workflow for PNT data is:
(U) The “system of models” in the center is a variety of NGA and mission partner systems. GNSS contributes to this workflow at the point noted on the upper left side – it is one of the “coordinate sources”, namely being the provider of AFSPACECOM GPS high accuracy
PNT and satellite ephemeris information. Multiple critical GEOINT mission workflows rely on this data source.
(U) The system architecture view is available on COE.
2. Lean Business Case
Epic Name: (U) GNSS – Content &
Workflow
Funnel Entry
Date:
Epic Owner: Trevor
Garner
Epic Description: Value Proposition (what you’re building) (U) The NGA Precise
Navigation and Timing (PNT) mission area provided high accuracy navigational ephemeris data to NGA and external customers for a variety of missions. PNT data is essential for creating geographically precise GEOINT products, geolocating artifacts within GEOINT products, and for a number of NGA military support missions. Furthermore, the NGA network augments the core AFSPACECOM-owned GNSS (GPS) ground control network by providing additional sources of information from the on-orbit assets.
For NSG Analysts and DoD mission partners
Who require PNT data and products
Our implementation
Is a automated and streamlined content processing flow, and incorporation of new data sources
That provides highly reliable PNT data
Unlike the current solution
Our Solution provides dramatically increased distributed locations
Business Outcome Hypothesis: (U) Obtaining PNT content from a robust selection of sources so that customers are able to obtain high precision navigation and timing data to meet production needs.
Leading Indicators: (U) Ground stations and data throughput
In Scope: (U) See Scope below Out of Scope: (U) none
Nonfunctional Requirements: (U) (U) OCI-cleared staff to support the PMO, CIO-T
IPO and organization staff for Enterprise Requirements, Architecture, Budget, Contracting / Acquisition, and Legal support. Enterprise / Common Services for Identity
Management & Authentication, Search & Discovery, System Administration / O&S
Support, Cloud Infrastructure Provider, Enterprise Management / Help Desk·
Minimum Viable Product (MVPf) Functions
IPFGEOINT-6176 - (U) SE1.PE2 GNSS Content & Workflow Backlog
Key Summary Description
Date
Planned
Start
Date
Planned
Finish
Linked
Issues
IPFGEOINT-6175
(U) SE1.PE2
MVPf 6:
Cloud
Environment
Cloud-migrated solution providing continuity and high availability production environment.
Sep 30, Sep 29, IPFGEOINT-
IPFGEOINT-6174
(U) SE1.PE2
MVPf 5:
Monitor
VLBA Sites
Autonomously and continuously monitor TBD
VLBA sites
(100%)
Sep 30, Sep 29, IPFGEOINT-
IPFGEOINT-6173
(U) SE1.PE2
MVPf 4:
Monitor VLBI
Sources
Autonomously and continuously monitor on at least
TBD (25% of the
VLBI Sites) VLBI data sources.
Sep 30, Sep 29, IPFGEOINT-
IPFGEOINT-6172
(U) SE1.PE2
MVPf 3:
Monitor SLR
Sources
Autonomously and continuously monitor on at least
TBD (25% of the
SLR Sites) SLR data sources.
Sep 30, Sep 29, IPFGEOINT-
IPFGEOINT-6171
(U) SE1.PE2
MVPf 2:
Monitor
Tectonic
Plates
Autonomously and continuously monitor on each tectonic plate globally (GNSS data source geographic diversity).
Sep 30, Sep 29, IPFGEOINT-
IPFGEOINT-6170
(U) SE1.PE2
MVPf 1:
Autonomously and continuously
Sep 30, Sep 29, IPFGEOINT-https://usms.nga.mil/jira/browse/IPOF-6176?src=confmacro
Monitor
GNSS
Sources monitor at least 50
GNSS data sources.
6 issues
Sponsors: (U) IPF
Users and Markets Affected: Beneficiaries (U) All GNSS customers
Impact on Products, Programs and Services/ Buy-In
• (U) Requires continued SME support from NGA/SF for software development and data processing insight.
• (U) Requires AFSPACECOM as the mission partner and space constellation operator to provide an operational GPS constellation
• (U) Leverages international navigation satellite systems for augmenting data where appropriate.
• (U) Leverages worldwide navigation satellite expertise and science development to augment
NGA’s contributions for US systems.
Impact on Sales, Distribution, Deployment/ Deployment
(U) GNSS is a key contributor to the overall national navigation satellite capability operated by
AFSPACECOM. The AFSPACECOM mission partner has significant dependencies on NGA delivering its part of the overall enterprise solution. Additionally, multiple product productions rely on precise navigation and timing to generate highly precise GEOINT.
Analysis Summary:
(U) TEMs with the GNSS PMOs / mission owners, and materials from the D/NGA’s Mission Imperative effort.
Go / No-Go:
(Go, or No-Go recommendation) (U) Go
Estimated Story Points (MVP)/Man Months
(U) TBD
Estimated Monetary Cost (MVP):
See CAPE Cost Estimate
Type of Return:
(U) Continued availability of high accuracy PNT content to enable the production of GEOINT, and continued operation of the national GPS navigation system.
Anticipated Business impact Mission
Achievement:
(U) Deliver mission capability for all PNT consumers, both NGA and external.
In-house or Outsourced Development: (Adapt, Adopt, Buy, Build)
(U) Combination of in-house and outsourced. The AFSPACECOM GPS program is the key external source in that GPS mission data and science originate from there. Additionally, international PNT efforts – both government systems and academia – are leveraged to augment the body of knowledge and to advance the science. NGA/SF is the internal NGA provider of
PNT science SME.
Estimated Development Timeline
(U) See program plan below
Start Date:
(U) 1 Oct
Completion date:
(U) 30 Sep 2027
Incremental Implementation Strategy:
(U) See program plan
Sequencing and Dependencies + Key Partners:
(U) GNSS is primarily driven by the AFSPACECOM GPS program. The NGA’s GNSS technical baseline must always conform to and integrate with the overall GPS constellation enterprise solution. This does at times limit what NGA can do with respect to changes / modifications, and also drives requirements to NGA that come from satellite block updates to
GPS as new satellites are built and launched.
Milestones or Checkpoints:
(U) See program plan
Attachments:
(U) Detailed PNT Assurance Program Plan (Excel file)
Other Notes and Comments:
(U) TBD
Scope:
Team Labor
Category Domain Service Configuration summary
NSWC
Software
Development
Unclass &
Secret
EPOCHA
development & updating
EPOCHA updating and development, adapative maintenance (NSWC interagency agreement)
NSWC
Software
Development
Unclass &
Secret
EPOCHA
development & updating
EPOCHA new development
(NSWC interagency agreement) -- SF Funded
NSWC
Software
Development
Unclass &
Secret
EPOCHA
development & updating
EPOCHA new development
(NSWC) -- IPF Funded
ARL
Software
Development
UC2S
&SC2S
Adaptive Maint -
ARL or Cloud
City or combo
1 -New scripts to acquire
SINEX input data from
NASA web portal, 2- Configuration
Management toolset to manage SFNG generated scripts, 3- New software to convert all MSN data into SINEX format automatically, 4- Establish SOPs for software use & quality control metrics
5- New software and scripts for computing stations velocities from Grape positions, configure new VM to support Grape production including installing the
Grape software
6- Platform, infrastructure and communications to support web service for generating MS coordinates and velocities and outputting these data in the ICD-GPS-
211 and ICD-GPS-811 formats. Can work in either
NGA cloud or data centers.
7 - Porting GSWeb into all
NGA's cloud infrastructure.
GSWeb should serve as a common platform for SFNG analysts and external customers. As such, a security apparatus is needed to assign selective permissions to users.
ASP O&S
(SCS / FS2)
Software
Maintenance
Unclassified
& Secret
Application adaptive maintenance on data center provisioning
(currently SCS)
Application maintenance on data center provisioned instances. Currently on SCS as a task order, with a labor rate mix. Priced as an entity for a range of support functions.
Common
GEOMATICS
VPC ("Cloud
City")
Software
Development
Team
UC2S,
SC2S
Data conditioning, usability, application integration to
Amazon cloud environment, and cloud functionality adaptation
Cloud City / ODS support for tailored data conditioning, data ingest, storage, content curation, and metadata tagging services
SF
SLR
Stabalization Unclassified
SLR
Stabalization -- 4 associated subtasks
Provide support to international SLR to sustain operations (FY22) and SLR data processing software development (FY23). This effort is a focused, 2-year funding action and does not extend out, nor does it have a follow-on funding requirement tail.
JPL / NRL
(Research)
Software
Development
Unclassified
& Secret
JPL & NRL
software development
Refactor and prepare
CATREF / PUGS LITE for deployment to cloud
JPL / NRL
(Research)
Software
Development
Unclassified
& Secret
Integrate software to production
Deploy PUGS LITE to NGA
Cloud
JPL / NRL
(Research)
Software
Development
Unclassified
& Secret
Integrate software to production
PUGS LITE maintenance @
25% of deployment estimate
JPL / NRL
(Research)
Software
Development
Unclassified
& Secret
JPL & NRL
software development
Refactor GIPSY software
JPL / NRL
(Research)
Software
Development
Unclassified
& Secret
Integrate software to production
Deploy modified GIPSY to cloud (FY24)
JPL / NRL
(Research)
Software
Development
Unclassified
& Secret
Integrate software to production
GIPSY maintenance @ 25% of deployment estimate
Team Labor
Category Domain Service Configuration summary
GNSS
Ground
Station
Operations &
Sustainment Unclassified
GNSS Ground
Station O&S
O&S of GNSS ground stations at
~100K / site
GNSS
Ground
Station
Equipment Unclassified
GNSS Ground
Station
Equipment
Recap
GPS-related equipment recap at
GNSS ground stations
MSN
Software
Development Unclassified
MSN at ARL
(currently 6 task orders by SF w/2 year PoP)
Mission Station Network operations, performance, monitoring and enhancement
HRTR enhancement & real-time validation
ITEMS
Transport
DISA
transport buy Transport lines:
sites to NGA
Existing comm lines at ~$50K / line
ITEMS
Transport
DISA
transport buy
MI Expansion:
Transport lines:
sites to NGA
New transport lines to expansion sites, at $150K for first year +
$150K upper each year cumulative afterwards
GNSS
Ground
Station
Equipment Unclassified
MI Expansion:
GNSS Ground
Station purchase equipment costs.
Purchase of new station GPS-related equipment at a rate of
$600K per new site block each year.
GNSS
Ground
Station
Operations &
Sustainment Unclassified
MI Expansion:
GNSS Ground
Station
O&S costs.
O&S of new station equipment. $350K first year for new site establishment & setup, then +$350K per year additional for an equal year--by-year buildout rate on new sites.
GNSS
Ground
Station
Software
Development MI Expansion:
MSN at ARL
1 additional STE dedicated to new station integration into MSN software
3. Roadmap
(U) Gap Statement
(U) Statement Title
(U) Autonomously and continuously monitor the GPS Satellite System / WGS-84 Reference
Frame Collection Sites
(U) Description: WGS-84 Reference Frame Collection Sites
(U) The WGS-84 Reference Frame Collection Sites capability expands the current level of reference framing from our current GNSS limited set of sites of 16 NGA referenced sites and 30
ITRF GNSS Stations. There are approximately 1,500 GNSS sites, 50-80 Satellite Laser Ranging
(SLR) sites, 32 Very Long Baseline Interferometry (VLBI) sites, and an unknown number of
French Doppler Satellite DORIS capable sites. Below in Table 1: Satellite Geodesy techniques
Impact on Reference Frame Calculations, is shown the capabilities for each type of geodetic technique and the impacts to the Reference Frame Calculations.
(U) A reference frame is made up of 4 components, an origin, an axis, a scale and reference points.
1. Origin – simply the point in space from which everything is measured. ZERO
2. Axis - for each spatial dimension, a line for each direction, usually 3 lines, x, y and z.
3. Scale – units of length or distances within the reference frame
4. Reference Points – real world points that uniquely fix the coordinate system
1. NGA uses 16 GNSS Monitoring Stations
Figure 1 Reference Frame
(U) Expanding the GNSS base and incorporating the SLR and VLBI satellite data will enable
NGA and DoD to become independent of the ITRF reference frame services, by being able to produce our own scale and origin calculations for the WGS-84 Reference Frame service.
Table 1: Satellite Geodesy techniques Impact on Reference Frame Calculations
Technique Axis Orientation Scale Origin
Satellite Laser Ranging (SLR) (sites today 50-80) X X X
Very Long Baseline Interferometry (VLBI) (32) X X
Global Navigation Satellite Systems (GNSS) (1,500)
(Currently only 16 sites used by NGA)
X
Satellite Doppler (DORIS) (French Systems) X
(U) In the below Figure 2: Comparison of the ITRF and WGS Reference Frame Data Sets, is a view of the data sources across the globe. The right side, GPS control segment are the NGA utilized data sets. The left side are the complete set of all reference frame data sets utilized by the
ITRF, inclusive of the French DORIS data set.
Figure 2: Comparison of the ITRF and WGS Reference Frame Data Sets
(U) Rationale for the Gap
(U) Current Rationale
(U) NGA is required to independently produce a reference frame capable of supporting the DoD.
Our current process relies heavily on the ITRF reference frame for its basic underpinnings.
(U) Recommend Rationale
(U) The WGS 84 Reference Frame (RF) is the official DoD terrestrial reference frame. All DoD maps and charts should be in the WGS 84 frame, and all DoD positioning and navigation are required to be in the WGS 84 frame. As such, the Global Positioning System (GPS) operates in the WGS 84 frame as do all GPS users.
(U) Current US policy is to keep the WGS 84 frame in alignment with the International
Terrestrial Reference Frame (ITRF), the international scientific reference frame. To meet this requirement, NGA aligns the WGS 84 RF to the ITRF rather than creating the RF from raw data.
(U) Without these expanded WGS-84 Reference Frame Collection Sites, DoD navigation, and charts, are fundamentally dependent upon an international scientific product.
(U) Who the Gap Benefits
(U) The ability of the agency to provide an independent WGS-84 Reference Frame to the DoD, commands, and the NSG.
(U) Rationale for Measures
(U) Original Statement
(U) NGA is required to independently produce a reference frame capable of support the DOD.
Our current process relies heavily on the ITRF Reference frame for its basic underpinnings.
(U) Recommended Statement
(U) NGA is required to independently produce a reference frame capable of supporting the
DOD, which means that NGA must be able to collect and process the components for a reference frame: the origin, the axis, the scale and the reference points. To accomplish this NGA needs to increase the number of collection sites and the type of collection sites, to include the additional
GNSS sites, SLR and VLBI sites. The addition of the SLR and VLBI sites will enable the reference frame for scale, and origin, which were vacant in NGAs current collection processes. A minimal set of these sites established the threshold level for the measures. The objective measure is to increase the resiliency and resolution of the quality of the product.
(U) Measures
(U) Current Measures
(U) Threshold: Autonomously and continuously monitor all GNSS data sources
(U) Objective: Autonomously and continuously monitor all WGS-84 data sources (GNSS, SLR, VLBI and Doppler-DORIS)
(U) Recommended Measures
(U) Threshold:
1. (U) Autonomously and continuously monitor at least 50 GNSS data sources
2. (U) Autonomously and continuously monitor on each tectonic plate globally
• (U) Autonomously and continuously monitor on at least TBD (25% of the SLR Sites)
SLR data sources
1. (U) Autonomously and continuously monitor on at least TBD (25% of the VLBI
Sites) VLBI data sources
(U) Objective:
1. (U) Autonomously and continuously monitor (all OR TBD) WGS-84 data sources
(GNSS, SLR, VLBI)
More details are contained in the attached plan (NOTE: this cover GGEPS and GSS topics in addition to GNSS).
GNSS Program Plan
Milestone FY Work Description
SOC
RPM
(U) GNSS Site
Expansion
(U)
23-
(U) Expand the site inventory per the description section of the program epic. Upper limits for need are: 50-80 satellite laser ranging sites (SLR), 32 very long baseline interferometry
(VLBI), and upwards of 1500 global navigation satellite system sites, both US and foreign. Currently on 16 US GNSS sites are in the content baseline.
(U) PNT Data
Resiliency and
Diversity
(U)
23-
(U) Ingest of all L-Band FGNSS data, data from monitor station expansion, and HRTR designed to ingest 256 channels
(U) Space
Product
Production
(U)
23-
(U) Extend GEOINT foundation products above 50,000 MSL based on validated priorities and requirements. Store, curate and disseminate the products.
4. Stakeholders
File details come from the government source that posted it. Updated .