Current location: Home » IOOS Summit » Recommended Priorities

Recommended Priorities

 

Members of the IOOC and IOOS Program Office met and prioritized the 25 broad recommendations to the top 9 that are executable starting in the first 3 years of project implementation. They are as follows:

9   High-Priority Recommendations for IOOC    
# Recommendation  Anticipated   Products/Deliverables Suggested   Next Steps/Timeline Assigned To
Design   Processes and Integration    
Design Process    
13.0 We   recommend the IOOC direct the IOOS Program Office, IOOS Association and U.S.   component of GOOS to work together to develop a draft plan, by August 2014,   of clear, common, repeatable processes for the basic work of the IOOS   enterprise: Create   a short list of ongoing activities and suggestions for adapting them to meet   the needs of the IOOS.
   
   
 

IOOC  
   

IOOS Program Office

IOOS Association

13.1 A   process to define observation requirements across the many uses and scales of   IOOS enterprise. We recommend the Framework for Ocean Observations (FOO)   approach of addressing essential ocean variables (EOVs) be considered as a   way of spanning the many users and scales of IOOS requirements.  For implementation, consider starting with   sea surface temperature (SST), winds, and surface currents      
13.3 A   process for identifying and endorsing key “indicator” measurements for   ecosystem health, regional climate change for input to global models, water   quality indicator observations co-located with physical and biological   measurements, and similar cross-cutting issues.      
13.4 A   process of comprehensive, periodic assessments against the collection of core   variables to identify unnecessary duplication and high-priority gaps; and a   workable process for eliminating the duplications to free up funds for the   gaps.      
13.5 A   process to test and assess the maturity of new technologies for inclusion in   the IOOS system of systems      
13.6 A   process for aligning data reporting standards across the IOOS enterprise   to  improve efficiency, accessibility,   and costs.             
13.7 A   process to optimize design of the IOOS ocean observing system by   consolidating many disparate observing efforts and maximizing the number of   high-priority variables observed at each site      
Assessments    
16.0 We   recommend the IOOC direct the development of, and oversee the preparation of,   periodic IOOS-wide assessments, based on observations of defined essential   ocean variables (EOVs) across all observing technologies and for all uses. Select   pilot effort to assess observing systems of EOVs and choose a few examples,   on physical and one biological, to assess the level of integration.
   
Choose   a variable like Ocean temperature, or sea level, in order to assess these   variables across different scales of observations, which each use their own   technological infrastructure in order to make these assessments (in situ,   regional modeling, satellite). 

IOOC
   

IOOS Program Office

16.1 The   assessments should include metrics of users and usage of various IOOS data   and  products      
16.2 The   assessments should highlight progress, and roadblocks, toward linking the   global/national/ regional/local components, and the biogeochemical and   physical components of IOOS      
16.3 The   metrics should identify under-performing or under-used parts of the system to   support funding decisions      
System Integration Projects and Drills    
17.0 We   recommend the IOOS Program Office, IOOS Association, and U.S. component of   GOOS work together to choose and organize IOOS participation in at least one   large-scale, disaster response drill annually, with IOOC oversight. Create   a matrix of when these things are happening and agree as a group what type of   participation may be optimal.
   
    Over time the participating groups will report on lessons-learned to be   utilized by other relevant agencies and groups throughout IOOS.
   
    This feedback will then be used by the IOOC in providing guidance toward   meeting IOOS objectives during participation in future disaster response and   recovery activities.
   
After   an initial polling of member agencies and a gathering of background on   planned and ongoing activities for the coming year, make it the subject of   conversation at an upcoming IOOC meeting.   

IOOC
   

IOOS Program Office

18.0 We   recommend the IOOC Committee direct and oversee planning, implementation,   assessment of a ten-year series of annual IOOS system integration projects Creation   of an Integrated Project Team that operates on a theme or project area and   consists of members capable of working the project at all levels.  These teams will work from clearly defined   metrics for success and a timeline. These teams will provide an opportunity   to identify and consolidate resources toward a common goal across the   enterprise and/or to mature an area of capability/knowledge within the   system. It   may be that OBIS as a potential integration mechanism for integration at the   international level. (i.e. there is a IOOS / GOOS discussion in June).  The work being done by Marine Mammal   Commission (Sam Simmons) looking at biological variables (also see   Recommendation #17) could prove to be a launching place. Further, this could   include some potential for follow on from CoML as a suggested initial   project.

IOOC
   

IOOS Program Office

18.1 Identify   an end-to-end unifying issue/theme/specific challenge for each year      
18.2 Focus   on integration of national, regional, global, government, industry, academic,   observations, data management and modeling efforts for that theme      
18.3 Develop   metrics to assess success, provide lessons learned      
18.4 Work   through a Steering Team appointed by IOOC       
18.5  Include assessment of support to both rapid   response and long term issues      
18.6 Test   high-level policy issues like payment for products       
Observations and Technology    
19.0 We   recommend that the new processes for IOOS observing system design address the   following gaps identified at the 2012 IOOS Summit: Develop   process for identifying synergies among existing agency activities and task   forces that are currently working on variables that would address IOOS gaps   identified under Recommendation 19 (e.g. OA task force, groups that are   looking at specific problems, Climate Change task forces, and other groups   set up under by the National Ocean Policy).  

IOOC
   

IOOS Program Office

19.1 Biological,   geochemical and ecological observations      
19.2 More   observations in the nearshore environment      
19.3 A   dedicated observing effort in the boundary between coastal and global models      
19.4 Deep   ocean, under ice, coastal winds, biological/geochemical/ecological, long-term   climate, water quality monitoring, climate change indicators, ice, wind,   waves, bathymetry, surface currents, seafloor changes, sub-surface   oceanography, passive acoustic monitoring of animal movements      
Data Management and Communications    
22.0 We   recommend the IOOC direct and oversee the following initiatives by the IOOS   Program Office, the Data Management and Communications (DMAC) Steering Team,   the IOOS Association, and the Regional Associations, related to integration   across the IOOS enterprise: TBD   – Based on DMAC ST draft work plan      Work plan to IOOC anticipated in late June
   

IOOS   Program Office
   

DMAC Steering Team

22.1 Expand   data and product standards across new data types and new user groups      
22.2 Develop   and adopt key data standards and protocols across the entire IOOS enterprise   to greatly improve the exchange of observations across local, regional,   national and global programs      
22.3 Improve   access and interoperability of ocean observation data dissemination and   storage across the 18 participating IOOS Federal agencies; and develop common   formats and exchange protocols between the DMAC and regional IOOS Data Access   Centers (DACs)      
22.4 Ensure   appropriate local observations make it into global data sets and global   observations are available to inform local and regional analyses and products      
22.5 Make   Web services the primary standard for disseminating IOOS information      
22.6 Develop   a common look and feel for user access to IOOS data and products across the   enterprise      
22.7 Engage   the observation technology industry to report data to IOOS standards      
22.8 Increase   engagement with ‘middleman’ small businesses to address their data needs for   expanding their products for end users      
22.9 Integrate   satellite data better with other IOOS observations      
     
23.0 We   recommend the following data and product issues be addressed by the broad   IOOS community, with guidance and oversight by the IOOC: Three   products:
    1.) survey results for existing core biological variables,
    2.) federal agency needs for bio/ecosystem observation needs
    3.) outputs from expert workshop
   
1.5   years for the three deliverables (Feb 2015),  Biological   Task Team
23.1 Make   data from Marine Protected Area (MPA) monitoring available to IOOS, and   ensure the full range of IOOS data are available to MPA managers      
23.2 Integrate   more private sector data into the IOOS enterprise      
23.3 Develop   more complete standards for monitoring/reporting biological data, and make   much more biological data available to IOOS users      
23.4 Increase   the amount of biological data, and coastal data of all kinds, available on   the Global Telecommunication System (GTS)      
     
24.0 We   recommend the IOOC direct the national, global and regional data storage,   analysis, and dissemination personnel to work together on the following: Per   QA/QC (24.1-24.4): QA/QC Procedures Manuals for selected real-time   measurements  Per   QA/QC (24.1-24.4): See QARTOD Project Plan   (http://www.ioos.noaa.gov/qartod/)
    Metrics (24.5): not addressed
    DACs (24.6): not addressed
   

IOOS   Program Office
   

DMAC Steering Team

24.1 Increase   the focus on common calibration, Quality Assurance and Quality Control   (QA/QC) approaches for all IOOS data and products      
24.2 Adopt   Quality Assurance of Real-Time Ocean Data (QARTOD) as IOOS QA start      
24.3 Consider   the calibration and QC “best practices” of the global climate   observation community for use across the U.S. IOOS enterprise      
24.4 Increase   IOOS data use by adding data quality flags and resolving liability issues      
24.5 Develop   automated processes for collecting metrics on users and usage on standardized   websites across the IOOS enterprise      
24.6 Assess   — through design exercises or other means — the number, type, and   functionality of regional DACs needed; estimate future storage needs across   the IOOS enterprise; consider cloud solutions for storage and analysis             
 
25.0 We   recommend the greater IOOS modeling community work together and with   academia, under direction and oversight of the IOOC, on the following: Identify   a regional pilot project where there is already critical mass in terms of   needs/activities to develop an integrated model as a path finder for other   regions. IOOC   should engage with the formulation and planning of the IOOS modeling strategy   (as part of the  NOC deliverable) to   engage agency interests and needs as well as opportunities, in advance of an   October 13 start.

IOOC
   

IOOS Program Office
   

DMAC Steering Team
   

IOOS Association

25.1 Develop   a ten-year plan for merging regional, national, and global ocean modeling   efforts into coupled, nested, and ensemble models across the time- and   space-scales required for the full range of IOOS users      
25.2 Develop   improved, and more localized nowcast/forecast products for the location and   movement of Harmful Algal Blooms (HABs), and for the location and movement   of  protected/endangered species