Figure 2 – High level Process for Algorithm Updates

Updates of operational IDPS algorithms need to be rapid, accurate, and compatible with the exigencies of 24/7 operations. As algorithms progress

through the Calibration/Validation program, they mature and become more suitable for end users’ needs, as defined by the product maturity levels

in Figure 1. The program’s approach to incorporate changes must handle algorithms in each stage of the validation regime appropriately, with

processes and controls that balance the speed of updates against operational system considerations (Figures 2 and 3). In addition, to help ensure a

rapid transition of the algorithm code into the operational baseline, JPSS CGS has developed tools and methods to reduce the cycle time from

science algorithm to operational code. These tools (Figure 4) are being made available to any science algorithm developer who feels they may be

beneficial, and will be required for use by GFE algorithm developers.

Government RaytheonJoint

Figure 4 - Algorithm Development Library

The Algorithm Development Library provides a toolkit enabling algorithm developers to work outside of JPSS

CGS-provided hardware, yet allow quick integration of new or modified algorithms into IDPS. This is

accomplished by aligning the algorithm structure with the IDPS architecture approach, and using operational

code-identical interface calls to perform I/O operations on the developer’s native platform.

P

File Based

CMD LineFile Based

CMD Line

I Alg Development

Science

Integration/OPS

ADL Framework

I O DMS Memory

Defined APIsDMS Memory

Defined APIs

Integrated

Algorithm

CAT 1

PRO Common Framework

O P

P

Algorithm changes enter the Change Process through discoveries made by the Government Team or by external entities

which may propose changes to JPSS CGS algorithms. Once proposed, all recommendations are jointly vetted and, if

worthy, approved for incorporation. At this point, the change is verified from a scientific standpoint to ensure that it is both

effective and compatible with other products and processes in the system. After all stakeholders are satisfied of the efficacy

of the change, it is prioritized with other updates, integrated and tested with the complete system, and deployed to

operations.

Algorithm Change

Recommendations

from the Government

Team or External Data

Users

Joint Adjudication of

Recommendations

Government

Approval

Science

Verification of

Change

Change

Control

Boards

Integration and

Testing

Science and

Operational

Verification of

Change

Deploy to JPSS CGS

Operations

Figure 3 – Rapid Algorithm Deployment Timeline

For algorithms in the “beta” maturity category, it is possible to execute the deployment of changes to the

Integration and Test system at a Central in as little as 24 hours. This capability is essential during the Intensive

Cal/Val timeframe, since immediate updates may be necessary to ensure continued production of xDRs for

evaluation. For products at more advanced maturity levels, standard sustainment processes would apply to

ensure all operational necessities are followed.

STAGE NPP SDR NPP EDR

Product Maturity Levels Product Maturity Levels

Preliminary

Comprehensive

Beta

Provisional

Validated/Calibrated

Beta

Provisional

Validated – Stage 1

Validated – Stage 2

Validated – Stage 3

Maturity Levels

Beta

Provisional

Validated – Stage 1

Validated – Stage 2

Validated – Stage 3

Early release,minimally validated, may

contain significant errors

Product quality may not be optimal

Ready for use – small validation range

Ready for use – wide validation range

Ready for use – robust validation

Joint Polar Satellite System Common Ground System (JPSS CGS)

NPOESS Preparatory Project (NPP) Rapid Algorithm Updates

Kerry Grant, JPSS CGS Chief Engineer

Raytheon Intelligence and Information Systems, Aurora CO

Bonnie Reed, Cal/Val Scientist

General Dynamics - IT, Formerly of the NPOESS Integrated Program Office

Gary Route, IDPS Chief Engineer

Raytheon Intelligence and Information Systems, Aurora CO

Figure 1 – Algorithm Validation Categories and Maturity Levels

Hour 0 1 2 3 4 5 6 7 8 9 10 11 12 13

Time of Day

(Mountain Time) 0800 0900 1000 1100 1200 1300 1400 1500 1600 1700 1800 1900 2000

Change approved

Review and assign

Fix

Build

Install at GISF

Factory Test and Evaluate Results

Prepare Patch Documentation

Internal Review and Approve

Deploy to NESDIS

Margin

14 15 16 17 18 19 20 21 22 23 24

2100 2200 2300 2400 0100 0200 0300 0400 0500 0600 0700

Install on I&T Env

Checkout Installation

Notify ICV team

AMS 2011