stephen ambrose goes-r data operations manager (dom) ospo/spsd
DESCRIPTION
GOES-R Ground Segment Project Data Operations Support Team System Validation Activities Brief to NWS-NESDIS/SPSD Quarterly Meeting. Stephen Ambrose GOES-R Data Operations Manager (DOM) OSPO/SPSD. March 12, 2013. The GOES-R System-Operational View. 137 o. 75 o. BEACONS. HRIT/EMWIN, GRB. - PowerPoint PPT PresentationTRANSCRIPT
Stephen AmbroseGOES-R Data Operations Manager (DOM)
OSPO/SPSD
March 12, 2013
GOES-R Ground Segment Project
Data Operations Support Team System Validation Activities
Brief to NWS-NESDIS/SPSD Quarterly Meeting
The GOES-R System-Operational View
Data and Products
Suitland, MDFairmont, WV
Enterprise Management
Mission Management
ProductGeneration
L2+ Data and Products
Product Distribution
LAN
NSOFRBU
LAN
• MM• EM• PG (L0, L1b, L2+ GLM,
GRB, KPP)• PD
MM: Mission ManagementEM: Enterprise ManagementPG: Product GenerationPD: Product Distribution
HRIT/EMWIN, GRB
SARSAT
GE
OL
UT
BE
AC
ON
S
DCS
DR
GS
Da
ta Co
llectio
n
Pla
tform
s (D
CP
)
• MM• EM• PG• PD
Wallops, VA
75o
WAN
137o
Product
Dis
t. & A
cces
s (P
DA)
(GO
ES-R A
cces
s Sub
syst
em- G
AS)
User Community
Operate Satellites
Operate Ground Seg
MaintainGround Seg
ProduceProducts
Data and Products
LAN
WCDAS
DCPC
DCPRDCS
L1b, L2+ GLM,GRB, KPP
L0,
3
DOM/DOST “Mission”
• DOM = Data Operations Manager• DOST = Data Operations Support Team
• Prepare OSPO to operate the Core GS Data Processing and Distribution System (DPDS)
• Validate that the Core GS “DPDS” is Mission Capable and Mission Ready
• Facilitate Consumer System Readiness for GOES-R Data Operations
• Accomplished by– Procedure and CONOP Development– Prototypes and Exercises– Facilitation of Test Data– Planning and Execution of two Pre-Launch “Data Operations Tests” (DOT)– Support for Post-Launch Tests
4
Data Operations Tests
• Two Pre-Launch Validation Opportunities– DOT-1: Directly following GS Release One– DOT-2: Directly after GS is complete (Release 1a and Release 2)
• One month sustained data operations– Continuous “Forecast Based” Level 1B– Interrupts for special test cases
• Facilitate readiness testing of downstream users
Direct BroadcastCommunity
NOAAPortCommunity
Climate, Research, and Academia
NWSForecast Offices
Operational User Community
NOAA Centers, DOD, NCEP, International Partners
WCDAS
NSOF
RBU
C
C
C
PDAP
DPG
MM
PD
PG
MM
PD
PG
MM
TNCF
BNCF
ANCF
NCDC
NGDC
AncillarySources
Validation ResponsibilityConsumer System Readiness Support
Data Flow through the GOES-R System
NOAAPortCommunity
Climate, Research, and Academia
NWSForecast Offices
Operational User Community
NOAA Centers, DOD, NCEP, International Partners
WCDAS
NSOF
RBU
C
C
C
PDAP
DPG
MM
PD
PG
MM
PD
PG
MM
TNCF
BNCF
ANCF
NCDC
NGDC
AncillarySources
Validation Responsibility Consumer System Readiness Support
ForecastBasedFixed GridL1b
ForecastBasedFixed GridL1b
PretendSat
Normal DOT Data Flow
Direct BroadcastCommunity
*
NOAAPortCommunity
Climate, Research, and Academia
NWSForecast Offices
Operational User Community
NOAA Centers, DOD, NCEP, International Partners
WCDAS
NSOF
RBU
C
C
C
PDAP
DPG
MM
PD
PG
MM
PD
PG
MM
TNCF
BNCF
ANCF
NCDC
NGDC
AncillarySources
Validation Responsibility Consumer System Readiness Support
SimulatedCCSDSPacket Stream
SimulatedCCSDSPacket Stream
PretendSat
Canned “End-to-End” Test during DOT-1
8
DOT Planning
VMRD
ValidationObjectives
TestObjectives
TestDesign
Development: Test ProceduresData and Component SimulatorsAnalysis Tools
Approaching with Systems Engineering Discipline
Test Execution and AnalysisDOT-1DOT-2
Validation Assessment
GRD
9
Left Side of the V – Validation Objectives
• Validation Objectives– Validation is not a repeat of Verification
• Incorporate the People and Mission aspect• Run in a “dirty” environment• Interact with the real world
– Validation Objectives are to Validation • …as Requirements are to Verification• Decompose them like requirements• Account for them like requirements• But…• V.O.s can be subjective, not necessarily pass/fail• Use V.O.s to establish shared expectations with Stakeholders
GOES-R Ground Segment Project Status Review 11
DOST Project Overview
• Phase One – Project Definition – Completed
• Phase Two – Preliminary Design – Dec 2012 – Apr 2013
• Phase Three – Detail Design – Apr 2013 – Oct 2013
• Phase Four – Implementation – Nov 2013 – Apr 2014
• Phase Five – Execution of Pre-Launch Testing – May 2014- Apr 2015
• Phase Six – Execution of Post-Launch Testing
Month DD, YYYY
GOES-R Ground Segment Project Status Review 12
Phase Two Overview
• Validation Objectives Review• Validation Objective Decomposition• Development of Ops Procedure List• Preparation of Validation Plan version 1• Coordination of External Validation Objectives Development
Month DD, YYYY
GOES-R Ground Segment Project Status Review 13
Phase Three Overview
• Validation Preliminary Design Review• Test Designs• Data Set and Simulator Specifications• Analysis Tool Specifications• Oversight of Ops Procedure Development• Preparation of Validation Plan rev 2• Coordination with External Validation Test Developments
Month DD, YYYY
GOES-R Ground Segment Project Status Review 14
Phase Four Overview
• Validation Critical Design Review• Data Set and Generator Implementation• Tools Implementation• Test Procedure Development• Ops Procedure Evaluation and Development• Early Opportunity Testing
Month DD, YYYY
GOES-R Ground Segment Project Status Review 15
Phase Five Overview
• DOT-1 Test Readiness Review• Execution of DOT-1• DOT-1 Analysis and Reporting• DOT-2 Test Readiness Review• Execution of DOT-2• DOT-2 Analysis and Reporting
Month DD, YYYY
GOES-R Ground Segment Project Status Review 16
As of:
DOST Top Level Schedule
August 30, 2012
December 31, 2012FY12 FY13 FY14 FY15 FY16
Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2
Current Milestone Deliverable Development Construction Integration / Test Current MonthMilestone Slip/Change
Fiscal YearTask #
GOES-R Program Milestones1
Ground Segment2
Validation Objectives Review3
DOST Phase Two4
DOST Phase Three5
DOST Phase Four6
DOST Phase Five7
DOST Phase Six8
5/12
KDP II 8/12
CDR I
11/12
CDR II
10/13
SIR
1/14
MOR
5/14
ETE1
8/14
ETE2
12/14
ETE3
1/15
FOR
3/15
ETE4
4/15
ORR
8/15
ETE5
9/15
MRRLRD10/15
7/12
GS CDR
8/13
Form DOST
10/14
DOT1
1/15
DOT2
4/15GSP ORRReady.
7/15
PLPT
9/15
GRD
9/12
1/13
ObjectivesReview 3/13
Submit OpsProc List
5/13Data Operations Validation
Prelim Planning Review
5/13
Start DesignIn-house Ops Proc
8/13
StaffDOST 10/13
Data Ops Validation PlanApproved
12/13
Data Ops ValidationCPR 2/14
Test Proc.Dev Cmplt
4/14Data Ops Validation
Proc Approved
6/14
DOT-1TRR 7/14
DOT-1Test Cmplt
12/14
DOT-2TRR 1/15
DOT-2 Test ExecutionComplete
3/15
DOT-2 ReportApproved
7/15
PLPTTRR 8/15
PLPT ReleaseReport
Notes:
CDR: Critical Design Review DOT: Data Operational Testing MOR: Mission Operations Review ORR: Operational Readiness Review TRR: Test Readiness Review
17
As of:2012 2013 2014 2015 2016
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2
Current Milestone Deliverable Construction Integration / Test SlackPlanned Available Date
YearTask #
Data Operations Support Team
1
Mission Operations Support Team
2
Core Ground Segment3
ESPDS / PDA/ ADRS4
CLASS Upgrades5
AWIPS6
5/13
Data OpsValidation
PPR
8/13
FormDOST
Data OpsValidationCDR 12/13
4/14 Data OpsValidation
Proc Approved
DOT-1TRR6/14
DOT-110/14
DOT-2TRR12/14
DOT-24/15
9/15GRD
PLPT 11/15
10/13
SIR
1/14
MOR
5/14ETE1
8/14ETE2
12/14ETE31/15
FOR
3/15ETE44/15
ORR
8/15ETE5
9/15MRR
LRD10/15
2/13
ECP007IBR
6/13
RelMM
8/13
GSIR
2/14
RMMa
8/14
R1
10/14
R2
12/14
R1a
9/15
Core GSReadiness
1/13
Inc 1 TRR
10/13
Inc 1 ORR
2/14
Inc 2 TRR
10/14
Inc 2 ORR
12/12
Upgrade
8/13
Available forETE
12/13
Available for R1 I/F
4/14
CTRN Available for ETE
10/12
Phase 1
TNCF Readiness for Interface testing (w/WCDAS)
11/13 Phase 211/13
BNCF Readiness for Interface
fail-over testing 11/13
Integrate & Checkout RBU OE 12/13
ANCF & BNCF Oper. Upgrade 6/14
10/14
GOES-R SW Install
12/15
Operational GOES-R SWInstall on NCF
Notes:
CDR: Critical Design Review DOT: Data Operational Testing ETE: End to End Test MOR: Mission Operations Review ORR: Operational Readiness Review PDR: Preliminary Design Review PSR: Pre-Ship Review SIR: Systems Integration Review TRR: Test Readiness Review
Validation Testing Dependencies January 31, 2013
18
Summary
• DOM – Data Operations Manager• DOST – Data Operations Support Team• DOTS – Two One-Month Pre-Launch Shakedown Cruises
• Focus: System Validation/Readiness of Data Processing & Distribution
• DOVOs – Data Ops Validation Objectives• EDOVOs – External Stakeholder Data Ops Validation Objectives
• Not “Re-Verification”• Not “Product Science Validation”