SAWG MTG Minutes 2009-05-27

From NGDC Wiki
Jump to: navigation, search

In Attendance

  • Phil Jones
  • Drew Saunders
  • Dan Kowal
  • Jeremy Throwe
  • Scott McCormick
  • Don Collins
  • Tom Schott (SPSRB)

SPSRB Mtg. with Tom Schott


  • Reviewed Agenda.
  • Introductions
    • Tom Schott
      • Systems Development for 8 years.
      • "Research to Ops" focus (funds over 50+ 'R to O' efforts).
      • Involved in GOES/POES/MeTOP

How to Archive Process Review

  • Dan gave overview.
    • Tom shared that an SPBSRB committee (SPIWG?) gave input to the Appraisel/Approval Guidelines.
    • Discussed that CLASS needs a lot of advanced time to set up archive logistics - want as much information about a proposed data set as possible, the earlier the better.
    • Jeremy shared that ClASS goes through two major releases each year, and their CCB identifies what's going to be in each release.
    • Tom explained that they have about 50 products identified for the archive - should have a list created this upcoming October - that are comprised of new and extensions of existing products. It would be crazy to send 50 - 100 emails to the Data Centers requesting archive.
    • Chris Fox has engaged Mark Mulholland, OSD Dep. Director - works for Gary Davis - to work with Tom to define a process for how the SPSRB submits archive requests for products.

SPSRB Process Slides

  • Key SPSRB Processes Slide.
    • Tom explained that the Brown Box sits outside the SPSRB Process. All of the tasks identified in this box will be realized in the August timeframe.
    • Product Development is tracked in a secure database that is only accessible by government officials.
  • Tom recommendedthe Process Paper from the SPSRB website that explains the process slide. It explains the current process but has shortfalls identified in "red."
  • Tom reviewed the initial template that all product development requestors have to fill out. It has a specific order, fills in details about a project plan all the way to carving out milestones. He pointed out the places where initial archive requirements can be defined.
  • Tom reviewed the Operational template where the question is asked about the status of archive arrangements. He explained that there has been no Data Center representation at the meetings where operational plans are discussed.

Submission Agreements/SPSRB

  • Tom gave a history of receiving SA template and a questionnaire to use with the proposed products. Worked with John Bates, and Phil actually crafted these for the SBSRB.
  • They are out of date and should be removed from the website.
  • Tom is interested in someone taking over this webpage and supplying it with up-to-date information, product-archive guidance, links to data centers, SA template, examples. The "someone" would work with Tom and any additions to the webpage with require SPIWG approval.
  • Phil clarified that the SA is more of the results of the negotiation process between Archive and data providers.
  • Tom pointed out in their template-based process where the question about archiving is asked. Perhaps some additional info could be added here if the answer is "yes."
  • Project Plan Template. Tom described the response to the Final Archive Requirements Assessment question should indicate that the SA is pretty much mature at this point.

Final proposals/Funding

  • Timeframe for the overall process - preposal to approval: 1 year for simple requests to 3-5 years for complex products.
  • Final presentation can be as much as 1000 ppt slides!
  • 50% of proposals have an archive requirement.
  • Funding.
    • MetOP products example brought $5 mil to CLASS.
    • NODC example had $ allocated ($10k) from data provider.
    • OSD is contributing a lot of $ to CLASS.
    • Tom talked about that a manager like himself can decide how to allocate funding such as for archive purposes, but it usually need approval from above.

Review of the Tracking System

  • Tom gave a quick presentation of how they track the status of product proposals through the SPSRB process; show us ways to filter on POCs, assessments, Triage Board and other decisions.
  • He is willing to work on adding Archive Tracking feature, but it will take some time to augment the system. A report could consist of actions and decisions for Request to Archive, appraisel/approval status, etc.... Could create an interface if the Data Centers really want one.
  • He showed the three different types of product requests that can be filtered for new products, enhancements to pre-existing products that are already funded and customized-type products.
  • Two people manage the database - he's one of them and populates it manually.

Next Meetings

  • June 12 - Tracking Discussion.
    • (Come prepared with your "What to track list.") Phil sent out a template tracking sheet as an example.
    • Discuss mtg. with Tom Schott and how the SAWG can assist in updating their section on Submission Agreements.