Cooperative Institute Director s Meeting 2 -3 June 2005

Скачать презентацию Cooperative Institute Director s Meeting 2 -3 June 2005 Скачать презентацию Cooperative Institute Director s Meeting 2 -3 June 2005

e7dd5cfb2198af67c5b154e51cce84ca.ppt

  • Количество слайдов: 21

Cooperative Institute Director’s Meeting 2 -3 June 2005 Al Powell Deputy Director, ORA Cooperative Institute Director’s Meeting 2 -3 June 2005 Al Powell Deputy Director, ORA

Center for Satellite Applications and Research* April 22, 2005 GOES-R Product and Algorithm Development Center for Satellite Applications and Research* April 22, 2005 GOES-R Product and Algorithm Development Al Powell and Mitch Goldberg * Pending approval, formerly the Office of Research and Applications (ORA)

Why a Govt-led Product and Algorithm. Team? • Lessons-learned indicated the need for greater Why a Govt-led Product and Algorithm. Team? • Lessons-learned indicated the need for greater involvement from the government, academic communities and the commercial sector for algorithm development, applications and other aspects of data processing. • Experience has shown that algorithm development and selection needs to be inclusive so that the best solution(s) is determined from several approaches.

Algorithm Working Group (AWG) The government-led AWG, chaired by ORA, will • broker and Algorithm Working Group (AWG) The government-led AWG, chaired by ORA, will • broker and select algorithms from among government, academic and commercial sources, • support the prototyping and demonstration of algorithm performance including algorithm/product meta-data generation techniques, standards, and formats, • provide algorithm software, documentation, test data sets, and benchmarks as potential solutions for the product generation functions, • review and assess applicable GOES Incident Reports (GIRs) Integrated Collaborative Environmental Development Test Bed (ICED-T) (Phased Approach)

NOTIONAL GOES-R Product & Algorithm Process - Provide algorithm recommendations - Recommend demonstrated algorithms NOTIONAL GOES-R Product & Algorithm Process - Provide algorithm recommendations - Recommend demonstrated algorithms - Direction to the System Prime - Provide recommendations on System Prime alternatives System Prime GOES-R PROGRAM OFFICE GOES-R Program Manager GOES-R Contract Representative - Algorithm acceptance - Provide alternative solution or recommendation Algorithm Working Group ORA Senior Management - Review System Prime alternatives

PROPOSED APPLICATIONS TEAMS Algorithm Working Group Hydrology Ocean Details Clouds Land Surface Imagery Aviation PROPOSED APPLICATIONS TEAMS Algorithm Working Group Hydrology Ocean Details Clouds Land Surface Imagery Aviation Soundings Cryosphere Winds Space Environment Radiation Budget Aerosols / Air Quality / Atmos. Chemistry Patterned after NASA MODIS teams 12 Teams by Specialty 5 members per team (including chair, no ties) Membership from: NASA, Cooperative Institutes, Universities, Do. D, ORA, etc. ORA Chairs each Application Team

GOES-R Product Generation Development GOES-R Risk Reduction Exploratory Operational Product Development Operational Demonstration System GOES-R Product Generation Development GOES-R Risk Reduction Exploratory Operational Product Development Operational Demonstration System Prime AWG Operational Transition Operational Production AWG will continue to develop and improve algorithms over the life cycle of GOES-R

Notional GOES-R Phase Timeline PG&D - Product Generation and Distrib PDR – Preliminary Design Notional GOES-R Phase Timeline PG&D - Product Generation and Distrib PDR – Preliminary Design Review CDR – Critical Design Review SIT - Software/Sys Integration & Test FAT - Factory Acceptance & Test SAT - System Acceptance & Test Operational Production Operational Transition Operational Demonstration Phase Operational Product Dev Phase Notional approx. 10 Exploratory Phase mos duration HES PDR 2007 GLM / SIS / SEISS CDRs Ground PDR 2008 for SIT, FAT, and SAT Ground CDR HES CDR 2009 2010 Ground Readiness 2011 ORA FINAL Test Data Available 2012 GOES-R Launch Relative Number of Algorithms Delivered Product Generation & Distribution 2013

Coarse Work Breakdown of GOES-R Product Development Phase Exploratory Operational Product Development Operational Demonstration Coarse Work Breakdown of GOES-R Product Development Phase Exploratory Operational Product Development Operational Demonstration Operational Transition GOES-R 3 Tasks Final Algorithm Selection, Operational Product Development, and Refinement Operational Algorithm Demonstration and Benchmarks Develop Automated Quality Assurance Deliver Algorithm Theoretical Basis Document (ATBD) Deliver Algorithm Code and Simulated / Proxy Data Set to Vendor Deliver Documentation to Vendor Collaboration with System Prime during Code Optimization Quality-Check Vendor Code Validate Vendor Products (Test Data) Final Products Systems Test Operational Production Validate Vendor Products (Real Data) User Quality Assurance / Assessment Reports Program Management

Collaborative Development 06 -07: 07 -09: 10 -11: Collaborative Development 06 -07: 07 -09: 10 -11:

End Withee April Brief • Transition to other topics End Withee April Brief • Transition to other topics

Collaborative Environment • IT Infrastructure Team Met for a Week in May 05 – Collaborative Environment • IT Infrastructure Team Met for a Week in May 05 – Varied Attendees (CIs. ORA, Commercial) – Basic agreement on a design – Basic concurrence on procedures & methods • Report being drafted – Available in late June • Plan to run pilot or demonstration capability in the office starting this summer – Purpose: to test before we ‘buy-in’ • Project will ‘touch’ more than ORA • VERY POSITVE FEEDBACK FROM THE GROUP!

GOES-R Planning • Asked by OSD to ‘dovetail’ GOES-R 3 plan into the AWG GOES-R Planning • Asked by OSD to ‘dovetail’ GOES-R 3 plan into the AWG Plan – In the works – coordinating with Paul Menzel – Hope to have this worked out in the near-term – Currently working schedule & requested changes • OSD asked to delete the ‘education and outreach’ • Menzel concurred (one exception, $50 K) • Details TBD – Additional changes may be on the horizon • OSD should provide additional guidance • In the interim, ORA is working on the program

Ground Systems Funds • Changing our approach to spending ground systems fund • Must Ground Systems Funds • Changing our approach to spending ground systems fund • Must comply with regulations for expenditures • These are not ‘science projects’ • Guidelines to sending hardware funds to universities being reviewed • Asked the leads at each of the CIs to provide a list of projects for consideration • All existing projects should have terminated this year per Paul Chang’s guidance the last couple of years.

Performance Metrics • Looking for CI metrics from you • Would like to see Performance Metrics • Looking for CI metrics from you • Would like to see what you propose • Additional guidance slow to come – Let’s develop a set and start to move forward – Let’s agree they’re useful to the CIs and ORA

Publications Policy • Last year a publications policy was announced with disclaimer statement required Publications Policy • Last year a publications policy was announced with disclaimer statement required • Haven’t noticed a significant change – Have you? If so, in what way? • Reviews of publications is going fairly well – Occasional ‘hic-cups’ in timing • Want to add a method of tracking to the ORA IT Infrastructure

Proposal Policy • Noticed a number of folks submitting proposals with ORA being just Proposal Policy • Noticed a number of folks submitting proposals with ORA being just a data provider – ORA must perform some ‘science analysis’ to participate in the future – Don’t think this affects the CIs – Just for your information

CI Proposals to ORA • Prioritized List of topics -- Was it helpful? • CI Proposals to ORA • Prioritized List of topics -- Was it helpful? • Need more coordination with funding sources – too many revisions • Seem to have an issue with funding amounts changing and proposals being send back for update – Suggestions on how to improve this?

ORA Operations Manual • Will list internal procedures for ORA staff & personnel • ORA Operations Manual • Will list internal procedures for ORA staff & personnel • Will include a variety of topics • To be posted on the web • In the final stages of review • New items for government: – Telework (will not be allowed at CIs – approval by exception only) – New Travel Comp Time Regulations

Roadmaps and Other • Closing in on: – Overarching roadmap – Working division roadmaps Roadmaps and Other • Closing in on: – Overarching roadmap – Working division roadmaps • Recent division roadmap decision – Roadmap (approx 30 pages and focus on direction) – Biennial Review (current work status, every two years) • Third generation Research Project Plans (RPPs) – Should be put on the web by the end of the summer

Final Slide • Any questions? Final Slide • Any questions?




  • Мы удаляем страницу по первому запросу с достаточным набором данных, указывающих на ваше авторство. Мы также можем оставить страницу, явно указав ваше авторство (страницы полезны всем пользователям рунета и не несут цели нарушения авторских прав). Если такой вариант возможен, пожалуйста, укажите об этом.