OCO Reporting Requirements How to Win Funds and Influence Program Managers

1
OCO Reporting Requirements How to Win
FundsandInfluence Program Managers

• Joel Levy
• NOAA Office of Climate Observation

NOAA Office of Climate Observation Annual Program
Review Meeting May 11, 2006
2
A Few Words About .

• Project Summary
• FY 2006 Annual Progress Report
• FY 2007 Work Statement and Budget
• FY 2007 Add Tasks

3
First Priority Understand the Context of the
Reporting Requirements
i.e. Understand the NOAA budget process
4
(No Transcript)
5
Second Priority Understand the Exercise

• i.e.
• What do OCO program managers need?
• Why do we need it?

6
What do Program Managers Provide?

• Develop program requirements
• GCOS plans (international covering fire)
• CCSP plans/priorities (national covering fire)
• NOAA plans/priorities (where rubber meets road)
• Procure funding
• Washingtonian politics
• NOAA bureaucracy
• Allocate funding
• Apples v. oranges
• Administer funding
• Negotiate the obstacle course

7
What do Program Managers Need from You?

• Scientific context for ocean observations
• Technical knowledge of
• What we measure
• How we measure it
• Why the measurements matter
• Detailed understanding of budget requirements

? Reports Acuity and readability are everything!
8
Why do Program Managers Need Reports from You?
to fight for the bones!
Also
We need enough insight to map resources to
current (scientific and political) funding
drivers ? who gets s
and why
9
Project SummaryNew use for an existing submission

• To be posted on the web
• Possibly to be featured in OCO Annual Report
• One-time task per project (update periodically)
• Who, what, why, where, when
• Scientific American level
• Audience includes generalists public

?
This is our public face!
10
The Annual Report RequirementsCurrent Thinking

• FY 2006 Annual Progress Report
• What you did last year
• FY 2007 Work Statement and Budget
• What you will do next year
• FY 2007 Proposed Add Tasks
• Pre-proposals for newly funded tasks

• Stand-alone documents
• We use them separately
• Independently revisable
• OK to cross-reference

11
Annual Progress Report

• New guidelines and format
• Brief scientific context (to make it
  stand-alone)
• Why you did it
• Tasks accomplished (report on deliverables)
• What you did
• Scientific Findings
• Why it matters
• Appendix - all the administrative stuff goes
  here
• Boiler plate linkages, relationship to program
  plan, etc.
• Updates publications, community service,
  statistics, etc.

• Do NOT merge with
• Next years work statement/budget
• Add tasks

12
Work Statement and Budget

• Work Statement Guidelines
• Narrative on scientific or technical challenge
  addressed by project
• Rationale
• Concise (e.g., 2-3 pages?)
• Description of proposed tasks for FY 2007
• Detail, detail, detail - no broad
  generalizations!
• List of deliverables - basis for next years
  annual progress report
• Budget Guidelines
• Detailed breakouts - do not lump sums
• NSF review quality
• Detailed budget justifications
• Personnel - why we need each person
• Equipment - details
• Travel - detailed justification

13
Travel Budgets

• Give best estimate
• We know it will change

14
Add TasksPretty Much Unchanged

• Scope
• Somewhere between a Letter of Intent and a
  Pre-Proposal (1-3 pages)
• Adequate detail to be evaluated by an ad-hoc
  panel
• Lumped budget
• Anticipate request for expanded detail later

15
OCO Annual Report

• State of the Ocean
• Expanded BAMS State of Climate report
• For what audience for what purpose?
• Repackage separately?
• Project Reports
• Project Summaries
• Progress Reports
• User Community
• Satellites
• Models
• Medium
• Print
• Electronic