1. 1 NWS Expectations - 2017 Satellite Data CONOPS Mike Johnson

2. GOES-R CONOPS 2017 System Deployment Expectations 2 Imagery – 16 Sectorized Cloud and Moisture Imagery Channels disseminated and displayed in AWIPS at earliest date available from NESDIS –GOES NOP Series will continue as East and West Operational Satellite until 1 year after GOES-R launch –GOES-R imagery provided on its own dedicated SBN channel AND via GRB to direct broadcast sites –AWIPS2/ D2D displays as discussed in this workshop with continued “tuning” through additional TOWRPro RPM deployments in response to feedback from operations –NAWIPS supported through ISSats via TOWR-S and NCO development. A2/NCP development and testing to continue. All in coordination with centers. Products – –Disseminated as soon as made available from ESPDS/PDA If multiple products are deployed at same time…will focus resources based on product priority Via operational end state systems where viable, otherwise based on product priority and SBN re-balanacing –AWIPS2 and NAWIPS expectations same as for imagery

3. GOES-R 2017 Data Flow CONOPs 3 After GOES-R release, continuous data except for during periods of testing (per Matt’s discussion) –Interruptions to planned testing for exceptional weather events only (per Matt’s discussion) Method of field notification for GOES-R data interruption (per Matt’s discussion) Method for coordination and requesting mesoscale sectors (per Matt’s & Dan’s discussion) Method / content for “product use qualification notes” for any product introduces before “validated” declaration (per Matt’s discussion) Coordination with NWS GOES-R OT&E will coincide with NWS GOES-R pre- operations during 2017 –TOWRPro RPM deployments changes to AWIPS state, NWS dissemination system enhancements, should occur with coordination similar to DOE-4 coordination

4. 2017 CONOPs system expectations for Non-GOES-R satellite data 4 Himawari upgrades –Centers backup and LDM delivery upgrade is dependent on ISatSS+ Networking on-boarding and scope prioritization by NWS leadership –NESDIS PDA milestone for on-boarding Himawari delivery currently provided by STAR dictates when full resolution Himawari data is supported on an operational versus experimental basis SNPP, JPSS, GCOM –Dependent on ISatSS on-boarding milestones –Dependent on JPO Block 2.0 / PDA deployment –Dependent on AWIPS Data Delivery functionality with PDA Terrestrial communications build out any SBN rebalancing that occurs –Operational versus experimental deployment & support expectations dependent on all these factors Jason, GPM, RadarSat-Sentinel –Same as SNPP, JPSS, GCOM