2.1k likes | 2.38k Views
NPOESS Data Exploitation (NDE) Preliminary Design Review. November 21, 2006 NSOF Building 4231 Suitland Road Room 2001. Welcome -J. Silva. PDR Agenda. 8:00 a.m. Welcome 8:15 a.m. Introduction/Background 9:00 a.m. Project Overview 10:45 a.m. NDE Context and Hardware
E N D
NPOESS Data Exploitation (NDE)Preliminary Design Review November 21, 2006 NSOF Building 4231 Suitland Road Room 2001
PDR Agenda • 8:00 a.m. Welcome • 8:15 a.m. Introduction/Background • 9:00 a.m. Project Overview • 10:45 a.m. NDE Context and Hardware • 11:15 a.m. Algorithm Development • 12:00 p.m. Lunch • 1:00 p.m. Data Handling System • 2:30 p.m. IT Security • 3:00 p.m. Communications Study • 3:40 p.m. Closing Remarks • 4:00 p.m. PDR Board Review of RFAs
Agenda • 8:00 a.m. Welcome • 8:15 a.m. Introduction/Background • 9:00 a.m. Project Overview • 10:45 a.m. NDE Context and Hardware • 11:15 a.m. Algorithm Development • 12:00 p.m. Lunch • 1:00 p.m. Data Handling System • 2:30 p.m. IT Security • 3:00 p.m. Communications Study • 3:40 p.m. Closing Remarks • 4:00 p.m. PDR Board Review of RFAs • Introduction/Background J. Silva • Mission & Design Drivers J. Silva • Architectural Overview G. Goodrum • Data Products T. Schott
Chairperson: Vanessa Griffin, (NESDIS/OSD) Ground Systems Division Chief Mike Mignogno (NESDIS/OSD) Polar Program Manager Mike Tanner (NESDIS/HQ) Senior Program Advisor Reginald Lawrence (NESDIS/OSDPD), Environmental Satellite Processing Center Chief David Benner (NESDIS/OSDPD) Satellite Services Division Chief Mitch Goldberg (NESDIS/STAR) Satellite Meteorology and Climatology Division Chief Joseph Mulligan (NOAA/IPO) NPOESS Interface Data Processing Segment Lead Kevin Schrab, Ph.D. (NWS) Satellite Product Improvement Manager Brian Gockel (NWS/OST/SEC) Systems Engineer Lt. Amanda Bittinger (NESDIS/STAR) Satellite Oceanography and Climatology Division Charles MacFarland NESDIS/OCIO Representative NDE Design Review Board
Request for Action Briefing Title: Slide Number: _________________________________________ Comment/ Question: _________________________________________ Background on Comment or Question: _________________________________________ Team response: ___________________________________________ Submitted by: _________ • RFAs are available on tables at back of room • RFAs to be submitted to a Review Board Member • All RFAs are due today by the end of the meeting (4:00 p.m.) • Please state your questions clearly • Review Board will disposition RFAs • Board Members are requested to convene to disposition RFAs
System Modeling Ann Al-Jazrawi Stan Cutler Geof Goodrum Barbara Hickman Raj Khanna Peter MacHarrie Gary Roth Hongming Qi Jim Silva Gary Sloan Tom Bishop Geof Goodrum Raj Khanna Gary Roth Tom Schott Management Team Geof Goodrum Stan Cutler Lou Fenichel Raj Khanna Jim Silva Ed Wilson Requirements IDPS I/F Design Geof Goodrum Raytheon Peter MacHarrie Ed Wilson Algorithm I/F Design Brian Merandi Peter MacHarrie Ann Al-Jazrawi CLASS I/F Design Maurice McHugh Tony Conrad OSDPD Product Leads Bill Reupke STAR Product Leads Krishna Tewari Barbara Hickman Rich Mumaw Tom Suhrstedt Customer Reps Comm. Study Emily Graham ESPC CM Team Configuration Management ESPC Architecture Tom Bishop Brian Callicott Wendy Holmes Barbara Hickman The NDE IT Design Team
Today’s Objective • Objectives: To ensure that NDE’s design concepts are consistent with NPOESS and NOAA architectures and that NDE plans are feasible • NDE Design Review Board roles and responsibilities: • Review NDE system conceptual design • Review project plans necessary to reach Critical Design Review (CDR) in August 2007 • Review strategies (acquisition, development, testing, implementation, transition) • Assess risks • Request actions that will improve NDE designs and plans
Assessment Criteria • Does the proposed preliminary design satisfy the contractual requirements? • Has the overall system framework been clearly presented? • Has the functionality been appropriately allocated to subsystems? • Have the interfaces between subsystems and to external entities, including users, been identified? • Have the security features and controls been defined? • Have delivery strategies been defined for the subsystems (build, buy, reuse)? • Are the plans and schedules leading to CDR feasible?
NDE Requirements & Performance Measures Software Engineering Infrastructure Systems Management Data Retention & Archive Interfaces Operational Product Generation Communications & Distribution • Project Plan v.2 • Scope • Organizational Views • Roles and Responsibilities • Project Approach • Schedule • Acquisition Strategy • Budget • Concept of Operations • Scope • Justification • System Concepts • Operational Scenarios • Impacts • Analysis of Proposed System Background Documents See NDE Web site: http://projects.osd.noaa.gov/nde
Agenda • 8:00 a.m. Welcome • 8:15 a.m. Introduction/Background • 9:00 a.m. Project Overview • 10:45 a.m. NDE Context and Hardware • 11:15 a.m. Algorithm Development • 12:00 p.m. Lunch • 1:00 p.m. Data Handling System • 2:30 p.m. IT Security • 3:00 p.m. Communications Study • 3:40 p.m. Closing Remarks • 4:00 p.m. PDR Board Review of RFAs • Introduction/Background J. Silva • Mission & Design Drivers J. Silva • Architectural Overview G. Goodrum • Data Products T. Schott
Mission The NPOESS Data Exploitation (NDE) will provide critical environmental products derived from NPP and NPOESS observations to NOAA’s operational community in near-real time
NDE Project:Capabilities Assessment Current StateTarget State Orbital Processing ΔGranule Processing • Granule (data structure) Processing • Instrument specific • SafetyNet • “Continuous” ingest • Near-real time = <30 minutes • All data packaged as HDF5 • Orbital Processing • Near-real time = 156 minutes from observation to product NDE systems must adapt to all new input formats, alter formats to user needs, take advantage of improved latency
NDE Project:Capabilities Assessment Current StateTarget State Stove-pipe Applications Processing Δ Centralized IT Architecture • Centralized IT Architecture • Reusable objects • Database Technologies & Data Management • Common CM, testing, and transition processes • Common toolsets • Centralized management and control • Stove-pipe Applications Processing • Duplicated, redundant functionality • High cost of management & control NDE will establish latest proven technologies and manage them in 3 basic environments: Development, System Test, Operations
NDE Project:Capabilities Assessment Current StateTarget State 300 GB/day Distribution Δ ~6 (tbc) TB/day Distribution • Product benefits realized by relatively small customer base • Limited number of dissemination options • “orders” require developer intervention • FTP (pull) in most cases • Increase customer base (increase benefits) • Online subscriptions • GUIs • More Dissemination Options: • Push, pull, network, fiber, internet, etc. NDE to establish a Communications Architecture in collaboration with NOAA’s Network Advisory Committee (NAC) and AWIPS
The Transition Challenge • Environmental satellite industry challenge • NESDIS history: ~ 2 ½ years from data availability, through research, to provision of products to operational users (R2O) • All new NOAA projects must have Transition Teams and submit Transition Plans for approval • NDE submitted plans (MIRS, CrIS/ATMS, Sea Surface Temperature) developed with SPSRB oversight • NDE’s Goals • Minimize IT obstacles as algorithms migrate through development, test, and operational environments • Work with end users to prepare operations for products
Agenda 8:00 a.m. Welcome 8:15 a.m. Introduction/Background 9:00 a.m. Project Overview 10:45 a.m. NDE Context and Hardware 11:15 a.m. Algorithm Development 12:00 p.m. Lunch 1:00 p.m. Data Handling System 2:30 p.m. IT Security 3:00 p.m. Communications Study 3:40 p.m. Closing Remarks 4:00 p.m. PDR Board Review of RFAs • Introduction/Background J. Silva • Mission & Design Drivers J. Silva • Architectural Overview G. Goodrum • Data Products T. Schott
NDE System Objectives • Disseminate NPOESS Data Records to NOAA Operational Community • Generate and disseminate tailored NPOESS Data Records (versions of NPOESS Data Records in previously agreed alternative formats and views) • Generate and disseminate NOAA-unique products (augmented environmental products constructed from NPOESS Data Records) • Deliver NOAA-unique products, product processing elements, and associated metadata to CLASS for long-term archiving • Provide services to customers, including NDE product training, product enhancement, and implementation support across NOAA • Provide software for NPOESS Data Record format translation and other data manipulations
NPOESS Data Exploitation (NDE) Mission Context Diagram NOAA Environmental Satellite Processing Center (ESPC) NPOESS Ground System Data Records (xDRs) NPOESS Data Exploitation (NDE) NOAA Unique Products Tailoring Tools Data Records (xDRs) NPOESS will deliver more than 100 different data records (xDRs) Tailored Products Data Records (xDRs) NOAA Unique Products CLASS Near Real-time Customers CLASS xDRs Climate Community Near Real - time Near Real Near Real - - time time Climate Tailoring Tools Customers Customers Customers Community NOAA - Unique Products
NDE Phasing Deployment Lifecycle Requirements & Critical Release Release Preliminary Planning Design Preliminary Release Release Closeout Design Scope & Requirements • Design, develop and implement • Development Environments for NPP/NPOESS • System Test Environment for NPP/NPOESS • Operational Environment for NPOESS
Vision:3 Environments, Common Standards Environmental Satellite Processing Center NDE System Test/Backup Environment NDE Operational Environment NDE Development Environment Shared Capabilities, Common Standards
Design Considerations • Algorithm modularity • Reuse • Centralization • Scalability
Seg Int Complete 11/10/06 CUT Complete 4/21/06 Qual lite Complete 2/28/07 SWIC Complete 7/7/06 1.4 CDW 11/14/05 NPP Launch 9/30/09 SWIC QUAL- Lite CUT Seg Int B1.4: Continuous Segment INT IDPS Algorithm Sci2Ops ACI ATP 8/30/05 ACI CDW 2/23/06 NPP Sys Test / Sys Readiness Activities ACI Design ACI CUT Site HW Procure / Pre-Ship 1/4/08 Performance: NESDIS SAT/ AFWA SIT 9/30/08 Initial HW Procure 10/1/07 Performance Analysis & Prototyping Pre- FAT Int 4/11/08 FAT Complete 6/27/08 SWIC Complete 7/27/07 Alg FO Deadline 3/30/07 CUT Complete 5/30/07 Seg Int Complete 10/30/07 CDW 1/11/07 BAR 10/12/06 Qual Complete 4/4/08 B1.5: Final Perf Verif 3/30/09 (TBR) BAR Prep Detailed Design CUT Seg Int QUAL FAT A-SAT SWIC FAT Int N-SAT Cont Segment INT FAT Install and Prep Site Installs and Prep IDPS Algorithm Sci2Ops Characterization Updates/Final Verif Small algorithm changes to SPCR work-off O&S Late/large algorithm changes 1Q2009 2Q2005 2Q2005 4Q2008 3Q2005 3Q2005 4Q2005 4Q2005 1Q2006 1Q2006 2Q2006 2Q2006 3Q2006 3Q2006 4Q2006 4Q2006 1Q2007 1Q2007 2Q2007 2Q2007 3Q2007 3Q2007 4Q2007 4Q2007 1Q2008 1Q2008 2Q2008 2Q2008 3Q2008 IDPS / NPP & NDE Integration Timeline NDE PreliminaryDesign NDE-NPP Integration NDE CriticalDesign NDE System Test Environment … Concepts in work Note: New NPP IPAC Verification events (Performance Verification) not yet Planned
Risk Handling and MitigationAssessment of impact and project plans • Mitigating steps in NDE’s current plans • Develop a risk management plan • For IT work, schedule control via earned value management • Develop lifecycle cost and benefit estimates • Develop the project budget • Plan for needed resources • Design systems to support reliability requirements • Monitor NOAA and DoC security requirements • New risk mitigating activities • Develop and implement a quality management plan to address system and data quality, quality assurance, and quality control. • Develop and implement NDE continuity plans that are coordinated among participating organizations. • Coordinate development of preliminary (pre-launch) data with the IPO and instrument designers
Risk Management Summary • Risks management plan will be revised as risks are handled, new risks are identified, or stakeholder views change • Continued input from stakeholders and other sources • Developers have a critical responsibility to identify issues, risks, and challenges and their potential impact on operations • Preliminary design review will identify issues and challenges for key design elements
Agenda 8:00 a.m. Welcome 8:15 a.m. Introduction/Background 9:00 a.m. Project Overview 10:45 a.m. NDE Context and Hardware 11:15 a.m. Algorithm Development 12:00 p.m. Lunch 1:00 p.m. Data Handling System 2:30 p.m. IT Security 3:00 p.m. Communications Study 3:40 p.m. Closing Remarks 4:00 p.m. PDR Board Review of RFAs • Introduction/Background J. Silva • Mission & Design Drivers J. Silva • Architectural Overview G. Goodrum • Data Products T. Schott
Product Definitions • Products delivered by NPOESS contractor • xDRs • Raw Data Records (RDR) • Sensor Data Records (SDR) • Temperature Data Records (TDR) • Environmental Data Records (EDR) • Intermediate Products (IP) • Pre-planned Product Improvements (P3I) • Products produced by NOAA using xDR information • Tailored xDRs and IPs • NOAA Unique Products (NUPs)
Current Polar Products Line Office Needs NOAA Mission Goal Needs (CORL) NPOESS Products Requirements Integrated Program Office (IPO) Deliverables Contract Document Requirements Document NPOESS Integrated Operational Requirements Document (IORD – II) Dec 10, 2001 NPOESS Technical Requirements Document Sensor, Temperature, Environmental Data Records (xDRs) NPOESS Data Exploitation (NDE) (1) Tailored xDRs (2) NOAA-unique products (NUPs) NDE Product Development NDE Product Matrix
Sample from Mission Goal Version of Product Matrix Products Line Office Mission Goal Review (CORL items in gray) Master, W&W, Climate, Ecosystems, C&T spreadsheets Motivation: Develop NPOESS products to meet all NOAA user requirements
05 06 07 08 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 09 CALENDAR YEAR N N’ C1 (-) PM NPP Acquisition StrategyEmphasis POES Mission Continuity • Nunn-McCurdy process restructured NPOESS acquisition efforts • POES mission continuity might rely on NPP data operationally
Define NPP Products • POES and EOS Mission Continuity • Essential that we address these products • Development products • Under development and could go operational prior to NPP launch • New products • Never provided to user community and not under development within NESDIS
Agenda 8:00 a.m. Welcome 8:15 a.m. Introduction/Background 9:00 a.m. Project Overview 10:45 a.m. NDE Context and Hardware 11:15 a.m. Algorithm Development 12:00 p.m. Lunch 1:00 p.m. Data Handling System 2:30 p.m. IT Security 3:00 p.m. Communications Study 3:40 p.m. Closing Remarks 4:00 p.m. PDR Board Review of RFAs • Project Overview G. Sloan • Requirements Mgmt L. Fenichel • Development Approach E. Wilson • Tool Selection E. Wilson
A Reminder Parts of NPP, NPOESS, and NDE are subject to: • ITARs (International Trafficking in Arms Restrictions) • “NOFORN” Classification
Topics • Requirements Management • Development Approach • Algorithm Development • Data Handling System • IT Security • Data Distribution • The Way Forward
Management Approach • Staff the NDE Design Team with experienced professionals • Use design tools • Prototype of Development Environment • IBM p570 using AIX • Use NPP as the NDE risk reduction mission • Maximize use of COTS and GOTS (minimize custom code) • Collaborate with similar, current projects • Develop prototypes to validate requirements and design • Sell-off requirements as early as possible
Lessons Learned from NASA’s EOSDIS Core System • Integrate Algorithms with the Data Handling System early in the life cycle • Test the system under full operational load – data driven systems behave in strange ways • Build in Operator Dashboard and System Metrics for reporting • NetIQ and CA’s Unicenter are candidates • Configuration Parameters • Put in Database for change control, audit trail • Document CPs, min/max values, default, suggested values • Use “Rolling Wave” technology refresh approach • Constant effort • Keeps budgets flat – no large peaks every 5 years • Just in Time Hardware buys
NDE Design Assumptions • All NDE users are registered users • Users get data by entering an NDEsubscription • Subscriptions have two types • Standing Order (no expiration date) • Ad-Hoc (covers a limited time period) • Subscription to NOAA-unique products to be archived to CLASS will be determined by Archive Review Board • NDE will subscribe to all IDPS xDRs (in lieu of implementing complex logic using IDPS API to order only xDRs needed) • NDE will not distribute RDRs in near-real time to users (exception: Telemetry) • Users will need to request RDRs from CLASS • Product latency is customer and product specific
Data Access • NDE will flag customers as authorized for data or not during data denial • Use Initial Joint Polar System (IJPS) Data Denial Implementation Plan for initial authorization guidance • NDE will maintain a customer database that will contain sufficient attributes in order to set flag • Restricted data will be delayed for subscriptions from unauthorized customers • Timeliness more an issue for NPOESS than NPP • Only authorized users will be notified of data access status • End User License Agreement with customer restricts redistribution
Agenda 8:00 a.m. Welcome 8:15 a.m. Introduction/Background 9:00 a.m. Project Overview 10:45 a.m. NDE Context and Hardware 11:15 a.m. Algorithm Development 12:00 p.m. Lunch 1:00 p.m. Data Handling System 2:30 p.m. IT Security 3:00 p.m. Communications Study 3:40 p.m. Closing Remarks 4:00 p.m. PDR Board Review of RFAs • Project Overview G. Sloan • Requirements Mgmt L. Fenichel • Development Approach E. Wilson • Tool Selection E. Wilson