NPOESS Data Quality Monitoring (DQM) Interface Functionality at DoD Centrals Jim Vermeulen 28 May 2008

Background:  Contract Source Selection included DQM at all 4 centrals (2003) NGST proposed removing the DQM from all centrals except NESDIS in 2005 as part of a cost reduction action.  The removal of these DQM's was initially non concurred by the DOD centrals  Prolonged series of contentious meetings the visibility of which extended to the highest levels of leadership in both the IPO and NGST/Raytheon.  The issue could not be resolved until IPO/NGST agreed to retain all DQM functionality at the DoD sites which will allow each DoD central the option of procuring and operating its own DQM if it so chooses and re-visit the issue in the NPOESS era.

DQM Requirements Calibrate and Validate Data The IDPS shall be capable of displaying Data Quality Notifications (DQN) - Monitoring The IDPS shall display, to a Data Quality Engineer (DQE) missing values of a sensor parameter for DQE selected geographic area – Anomaly Resolution The IDPS shall provide the capability for a DQE to generate and display standard deviations and data trending The IDPS shall alert the IDP operator when data thresholds and parameters have been exceeded - Alerting The IDPS shall be capable of monitoring data quality notification parameters and compare them to configurable thresholds defined in Data Quality Threshold Tables (Data Tuning)

Issues with no DQM at DOD NGST maintains argument that the data is the same at all 4 Centrals DOD Centrals claim how can it be the same data when different files are read/written utilized and manipulated through out the various IDPS system processing chains How can DOD centrals proactively monitor for anomalous data coming out of the DOD IDPS? How can DOD applications be tuned specifically for DOD applications?

Documenting DQM at DOD Concern regarding the existence of DQM interfaces at all Centrals –Baseline includes DQM/DQE at NESDIS only, but architecture should also include capability to connect additional DQMs with no design modifications

Documentation Status DQM interface functionality exists at all Centrals –Regardless of presence of DQM/DQE Functionality is documented in Class I documents controlled by contractor/IPO Program-level boards –System and Segment level specifications –NPOESS Common Interfaces and Services ICD, Volume 1: External - D –NPOESS to Department of Defense ICD - D34466 –NPOESS Site Communications ICD Volume III – Central Site Interfaces - D NPOESS contractor generated an estimate for adding a DQM at a DoD Central (AFWA) –No interface design changes are required

Risks at DOD Centrals with no DQM DOD Centrals have to approve NPOESS Program Documentation ECRs in 2008 before IDPS installs. Architecture can change due to DOD IA constraints Inability to pro-actively monitor IDPS data at DOD Inability to tune IDPS data to DOD applications

DQM at AFWA ROM Contractor provided ROM costs for DQM at AFWA as requested in RCA-008 –No interface design changes are required Tasks to deploy DQM at DoD Central: –HW & COTS products necessary to duplicate the NESDIS DQM capability. Life cycle sustainment of HW & COTS products and DQM SW –HW, COTS, DQM SW functionality installation –System testing, verification –Documentation updates: requirements, ICDs, security documentation ROM contained costing for two hardware configurations for EMD and option CLIN (through FY24) –Alternate A - Operational and I&T Domain Standup ~$3M –Alternate B - Operational Domain Standup ~$1.8M

Summary NPOESS acknowledges desire for DQM capability Ongoing Anomaly Resolution Study – DOD Centrals want to know how anomalous data activity will be resolved NPOESS architecture readily accepts DQM deployment to DoD Centrals ROM costs for DQM deployment at AFWA are similar to DQM deployment costs for the Navy NPOESS Customer Forum Action Item – What are the costs of DQM that are not built into IDPS functionality?

Recommendations Continue to monitor results of Anomaly Data Resolution Study via NPOESS User Conclave and Customer Forum - FNMOC – Jim Vermeulen - AFWA – Capt. David McDonald, Bruce Thomas, Tom Kopp - NAVO – Bob Coulter - NESDIS – Geoff Goodrum, Gene Legg Inform Joint Action Requirements Group (JARG) of status Inform Super Users Action Group (SUAG) members of status Possible joint letter of concern from COPC to SUAG

NPP Data Acquisition at FNMOC/NAVO Requirements sent to AFWA/NESDIS March 2008 via CNMOC Working with Navy SPAWAR PMW120 on bandwidth and landing zone technologies and design issues Working with AFWA experience from NPOESS Early Interface software (size of granules with and without geo- location) Continued planning with AFWA’s Captain David McDonald with support from Aerospace’s Bruce Thomas Continued planning with NESDIS’s Geoffrey Goodrum and Jim Silva