Jeffrey Kronenwetter PLT Director PLT Coordination & Field Campaign Preparations.

Slides:



Advertisements
Similar presentations
GLAST LAT ProjectLAT Engineering Meeting, April 1, 2003 GLAST Large Area Telescope: Performance & Safety Assurance Darren S. Marsh Stanford Linear Accelerator.
Advertisements

GLAST LAT ProjectISOC CDR, 4 August 2004 Document: LAT-PR-04500Section 3.11 GLAST Large Area Telescope: Instrument Science Operations Center CDR Section.
RockSat-C 2011 SITR Payload Subsystem Integration and Testing Report University/Institution Team Members Date.
GLAST LAT ProjectISOC Peer Review - March 2, 2004 Document: LAT-PR Section 2.1 Requirements 1 Gamma-ray Large Area Space Telescope GLAST Large.
Unit 8: Tests, Training, and Exercises Unit Introduction and Overview Unit objectives:  Define and explain the terms tests, training, and exercises. 
GLAST LAT Project ISOC Peer Review - March 2, 2004 Document: LAT-PR Section 2.3 Verification and Validation 1 Gamma-ray Large Area Space Telescope.
Section 15-1GLAST Ground System Design Review August 18&19, 2004 ISOC Organization ISOC Manager R Cameron Commanding, H&S Timeline Planning Command Generation.
GLAST LAT Project ISOC Peer Review - March 2, 2004 Document: LAT-PR Section 3 LOF Operations Concept 1 Gamma-ray Large Area Space Telescope GLAST.
GLAST LAT ProjectISOC CDR, 4 August 2004 Document: LAT-PR-04500Section 4.11 GLAST Large Area Telescope: Instrument Science Operations Center CDR Section.
Page 1HMI Team Meeting – January 26, 2005 HMI Mission Operations Rock Bush HMI Stanford Program Manager Stanford University
July 10, 2013 Space Weather Product Team (SWPT). Outline 2 SWPT Roster SWPT Timeline (1) GOES-R Pre-launch Timeline (1) SPADES Overview (2) Cal/INR/Product.
NOAA Satellite Science Week 2015 Bob Iacovazzi GOES-R Cal/Val Coordination Team (CVCT) Lead February 23, 2015 GOES-R Cal/Val.
ESC/EN Engineering Process Compliance Procedures August 2002.
Page 0 COMSTAC RLV Task Force on Training RLV TASK FORCE ON TRAINING May 15, 2008 Maurice Kennedy.
CPA is a UKAS company The Assessment Process 2014 Seminars.
May 15, 2013 Space Weather Product Team (SWPT) Making Sense of the Nonsensical.
March 26, 2014 Space Weather Product Team (SWPT) Kick Off Meeting.
LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.
Effective Methods for Software and Systems Integration
Unit 5:Elements of A Viable COOP Capability (cont.)  Define and explain the terms tests, training, and exercises (TT&E)  Explain the importance of a.
1. 2 Purpose of This Presentation ◆ To explain how spacecraft can be virtualized by using a standard modeling method; ◆ To introduce the basic concept.
Presented to: SBAS Technical Interoperability Working Group Date: 21 June 2005 Federal Aviation Administration Certification of the Wide Area Augmentation.
NASA’s Goddard Space Flight Center LRO Operations Concept Richard Saylor Jr. HTSI/Code 444 August 16-17, 2005.
Sentinel-3 Validation Team (S3VT) Meeting ESA/ESRIN, Frascati, Italy, th November 2013 General Presentation Template for S3VT meeting Project name.
.1 RESEARCH & TECHNOLOGY DEVELOPMENT CENTER SYSTEM AND INFORMATION SCIENCES JHU/MIT Proprietary Titan MESSENGER Autonomy Experiment.
NMP EO-1 TECHNOLOGY WORKSHOP Section 2 Meeting Objectives.
GOES Users’ Conference IV May 1-3, 2006 Broomfield, CO Prepared by Integrated Work Strategies, LLC 1 GOES USERS’ CONFERENCE IV: Discussion Highlights Algorithm.
1 Mission Discussion & Project Reviews 祝飛鴻 10/14/93.
IAEA International Atomic Energy Agency. IAEA Outline Learning Objectives Objectives and goals of a follow-up mission Requesting an IRRS follow-up mission.
1 GOES-R Series Program Update OCONUS Proving Ground Meeting Anchorage, Alaska Greg Mandt GOES-R System Program Director May 12, 2015.
NOAA Science Week – Kansas City, MO. 30 April 2012 Non Export-Controlled Information GOES-R – System Validation and User Readiness Planning Stephen D.
Comparability Protocols Lore Fields MT(ASCP)SBB Consumer Safety Officer DBA/OBRR/CBER September 16, 2009.
24b - 1 NASA’s Goddard Space Flight Center LRO Safety Dave Bogart Code 302 August 16-17, 2005.
Solar Probe Plus A NASA Mission to Touch the Sun March 2015 Instrument Suite Name Presenter's Name.
Dr. John MacCarthy UMBC CMSC 615 Fall, 2006
DUSEL Beamline Working Group Meeting March 09, :00 AM – Snake Pit (WH2NE) By Dean Hoffer - OPMO.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Stephen Ambrose GOES-R Data Operations Manager (DOM) OSPO/SPSD March 12, 2013 GOES-R Ground Segment Project Data Operations Support Team System Validation.
Committee on University Effectiveness Working Group on Institutional Assessment April 8, 2011.
1 Community-Based Care Readiness Assessment and Peer Review Overview Department of Children and Families And Florida Mental Health Institute.
SRR and PDR Charter & Review Team Linda Pacini (GSFC) Review Chair.
ORDER ENVIRONMENTAL PROTECTION PROGRAM WORKSHOP OVERVIEW OF ORDER Larry Stirling
K. Mercier, Shanghai meeting, 19th-22 May 2014 CNES, 5 th June 2014 Karine MERCIER EUSO Balloon Key Point Flight Acceptance Organisation.
GLAST LAT ProjectI&T&C Pre PDR Presentation– Oct 2, 2001 Darren Marsh1 I&T&C Organization Chart I&T&C Manager Elliott Bloom WBS I&T Engineer B. Grist.
N A T I O N A L O C E A N I C A N D A T M O S P H E R I C A D M I N I S T R A T I O N NPP DATA ACCESS Mitch Goldberg JPSS Program Scientist June 21, 2012.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
RBSP Radiation Belt Storm Probes RBSP Radiation Belt Storm Probes RBSP/EFW CDR /30-10/1 9 EFW Overview and Status Keith Goetz University of Minnesota.
IV&V Facility 7/28/20041 IV&V in NASA Pre-Solicitation Conference/ Industry Day NASA IV&V FACILITY July 28, 2004.
Matt Seybold (OSPO/SPSD) GOES-R Data Operations Manager & PRO Team Lead NOAA Satellite Proving Ground and User Readiness Meeting May 9, /9/2016NOAA.
Matt Seybold (OSPO/SPSD) GOES-R Data Operations Manager & PRO Team Lead NOAA Satellite Proving Ground and User Readiness Meeting May 9, /9/2016NOAA.
Principal Investigator ESTCP Selection Meeting
JLab Phase 4 Final Results
I&T&C Organization Chart
Software Configuration Management
Principal Investigator ESTCP Selection Meeting
GLAST Large Area Telescope:
Enterprise Algorithm Change Process
Development Test Overview
Phase 2 Tollgate Review Discussion Template
SDO Flight Dynamics Subsystem
Jesper Schou Instrument Scientist
GOES-R Program Systems Engineering (PSE) Cal/Val Lead
Launch and On-orbit Checkout
Principal Investigator ESTCP Selection Meeting
LAT Operations Scenario Subsystem Meetings
goes-16/17 abi lunar calibration
PSS verification and validation
Integration & Test Instrument Operations Coordination
Principal Investigator ESTCP Selection Meeting
Presentation transcript:

Jeffrey Kronenwetter PLT Director PLT Coordination & Field Campaign Preparations

1-1 PLT Phase The PLT phase is the nominal 6 month period after the Launch & Orbit Raising (LOR) phase when the observatory is positioned at its 89.5 ⁰ W checkout longitude. Pre-LaunchLOR PLT Deactiv ation Program Responsibility OSPO Responsibility OSPO involvement Handover Program involvement Launch PLPT Routine Operations Extended Val

1-2 PLT Scope To achieve the PLT objective, the GOES-R system elements will –Validate observatory and ground system operability and performance –Perform provisional validation of L1b and KPP products –Perform beta validation of L2+ products The scope of PLT include –Observatory testing that will validate operability and performance is as expected in on-orbit conditions and that continuous, uninterrupted L0 data can be used to generate calibrated L1b products –Ground testing that will assess operability and performance of mission management and product generation/distribution throughout the system and demonstrate readiness for operation by OSPO –Product testing (aka PLPT) that will inspect and compare L1b and KPP products with ground truth in order to assess instrument calibration, INR/pointing, and L1b product performance, and will demonstrate that L2+ products are generated when and where they should be and fall within expected measurement ranges

1-3 PLT Scope (cont’d) The scope of PLT does not include ‒ Re-verification of requirements ‒ Demonstration of lower level/derived requirements ‒ Characterization of observatory subsystems and associated products outside their planned operating configuration

1-4 PLT Forms Purpose: Mechanism for defining and placing under configuration management test plans and procedures for tests conducted during PLT Excludes activation (initial power on) of systems Excludes general trending of health and safety telemetry Excludes Routine Observations PLT forms will also be used as mechanism for scheduling (protecting) PLPT data collections only available prior to handover

1-5 Observatory PLT WG PLT/PLPT Test Development Process SC / Instruments Contractors Flight Project SE / SMEs / MOST leads Obs. PLT Eng. Review Board CWG CVCT OSPO Team PLT test requests (Impact to Observatory) PLT test requests Recommended Tests List And Forms GSP PLT test requests (Impact to Observatory) DOST CVCT PLT/PLPT WG GSP PLT WG CVCT PLPT CM GSP CM (PLPT tests that do not impact Observatory) (Ground tests that do not impact Observatory)

1-6 PLT Form Template

1-7 PLT Form Dictionary OBJECTIVE: Describe the objective of the PLT test. For specification PLTs, this field should reflect expectations of on-orbit compliance to any specification requirements listed in the "Specification References" field. For characterization and operational PLTs, the objective should reflect the value of conducting the PLT for operational concept validation. Also include the need for a passive data collection that requires nominal s/c and data configuration. DESCRIPTION: Provide a brief summary of the execution of the PLT test (detailed procedural execution will be provided in the “test procedure” field). In this field, a description of the deviation from the nominal on-orbit configuration of the subsystem under test should be included. Include a summary of any activities that will be performed outside of the NSOF environment. Include a summary of the restoration to nominal configuration.