1 / 55

Interagency Ocean Observation Committee DMAC Steering Team 4 th Meeting – November 19-20, 2013

Interagency Ocean Observation Committee DMAC Steering Team 4 th Meeting – November 19-20, 2013. Consortium for Ocean Leadership, Washington, D.C. Opening remarks…. Introductions (members/stakeholders/others) Review: Terms of Reference – our mission Recent efforts (since Feb ’13)

kyle
Download Presentation

Interagency Ocean Observation Committee DMAC Steering Team 4 th Meeting – November 19-20, 2013

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interagency Ocean Observation Committee DMAC Steering Team 4th Meeting – November 19-20, 2013 Consortium for Ocean Leadership, Washington, D.C.

  2. Opening remarks… • Introductions (members/stakeholders/others) • Review: Terms of Reference – our mission • Recent efforts (since Feb ’13) • Timeline for next steps • Meeting Agenda • Questions/Discussion DMAC ST Meeting – November 19-20, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  3. Introductions… Invited Stakeholders Federal Members • Charles Alexander (Chair) NOAA/US IOOS • LCDR Jonathan Andrechik USCG/OSTP • Ken Casey NOAA/NODC • Jeff deLaBeaujardiere NOAA/NESDIS • Mark Fornwall USGS/OBIS • Michelle Gierach NASA/JPL • Walter Johnson BOEM • Erica Key NSF • Kevin Kirby EPA • John Lever USN • Jeff Lillycrop USACOE • Rich Signell USGS/Woods Hole • Samantha Simmons MMS • Derrick Snowden NOAA/US IOOS • Erik Stabenau NPS/Everglades • Nadine Alameh OGC • Karl Benedict UNM/ESIP • Janet Fredericks WHOI • Eoin Howlett RPS/ASA • Dave Jones SCC, Inc. • David Mann Loggerhead Inst. • Ru Morrison NERACOOS • Krish Narasimhan unaffiliated • Henry Norris FL FWC • David Parrish VIMS • Roger Proctor IMOS (Australia) • Kurt Schwehr Google • Julie Thomas Scripps/SCCOOS • Steve Uczekaj Boeing DMAC ST Meeting – November 19-20, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  4. DMAC ST “Terms of Reference” Purpose, Scope and Goals: • Provide the IOOC with strategic guidance on DMAC-related activities and challenges • Maintain focus on DMAC subsystem elements (i.e. discovery, transfer, access, archive) • Identify and solve specific data management challenges within the ocean observing realm; and • Serve as a forum for collaboration among IOOS agencies and partners on DMAC issues DMAC ST Meeting – November 19-20, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  5. Participant Roles… Federal members: • represent agency data management practices and priorities • formulate DMAC guidance and recommendations for the IOOC • two year terms, maximum of two consecutive terms Non-federal stakeholders: • align DMAC guidance and standards with realistic implementation which non-federal entities are often responsible for executing • repeated meetings with one group of individuals must be avoided DMAC ST Meeting – November 19-20, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  6. Review of Feb 2013 Meeting… • USGS/Rich Signell virtual host • OGC Interoperability Experiments (Nadine Alameh) • US IOOS DMAC update (Derrick Snowden) • Priority tasks for ST: in-depth discussions • Standards: accelerate adoption at IOOC member agencies • Establish DMAC as a distributed system w/centralized catalog • Focus on catalog services • Metadata documentation and compliance DMAC ST Meeting – November 19-20, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  7. The way forward (Feb 2013)… • Guided by but not driven by IOOS Summit priorities • Include connections to/recommendations for global • More systematic and routine engagement with IOOC • Meet more often (phone/video, etc.) for shorter durations • Focus on viable solution sets for the IOOS enterprise • Develop a 12-18 month work plan with milestones/products • Re-boot when milestones/products complete (new ST/chair) DMAC ST Meeting – November 19-20, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  8. 3 IOOS Summit Recommendations • 3 NOC Milestones • ST project to “test” discovery, access, use of ocean observations DMAC ST Meeting – November 19-20, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  9. Our agenda… DMAC ST Meeting – November 19-20, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  10. Data Accessibility Testing and Evaluation Project determine how easy it is to FIND, ACCESS, and USE ocean observations data from IOOC member agencies using community best practices Advances current ST Priorities: • accelerating adoption of standards • improving overall use of metadata • DMAC as a a federation of data discovery catalogs IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  11. Data Accessibility Testing and Evaluation Project Objectives: • Definition of the specific scenario(s) from which the data and service requirements will be derived • Identification of the applicable community best practices for data format, access and documentation in the context of the requirements of the defined scenario(s) • An assessment (documented in a report summarizing by dataset/metadata/service component) of the current ability of IOOC member agencies to fulfill the requirements defined for the scenario(s). • Development of recommendations for strategies for closing the gap between current capabilities and those defined in the scenario specification IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  12. Data Accessibility Testing and Evaluation Project Notional Schedule: FY2014 IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  13. US IOOS Program’s System Integration Test • Purpose: Exercise the IOOS distributed data discovery and publication architecture to document performance and identify needed improvements. • Description: • demonstrate the ability to discover and access ocean observations via multiple scenarios on a subset of specific data types and data providers • answering test “questions” or developing a key product will be addressed with the same path: search for the data, discover the data, and use the data IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  14. US IOOS Program’s System Integration Test Notional Schedule: FY2014 IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  15. US IOOS Program’s System Integration Test Data Accessibility Testing and Evaluation Project $19K from IOOC $275-300K from IOOS Collaborate on a “single” Systems Integration Test Project in FY2014 IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  16. Next steps – schedule • integrate planning for ST and IOOS Program “Systems Integration Test” project (Oct-Nov) • convene DMAC ST meeting/workshop (Nov) • virtual host • “Test” project – next steps • refining responses to Summit Recommendations and NOP Milestones • initiate first tasks of “Test” project (Nov-Dec) • complete actionable inputs to Summit Recommendations and NOC Milestones in coordination with Biology Team and Post Summit Task Team (Dec) IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  17. Thank You! Questions/Discussion IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  18. 3 IOOS Summit Recommendations • 3 NOC Milestones • ST project to “test” discovery, access, use of ocean observations IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  19. IOOS Summit – Nov 2012 25 Recommendations 4 on Data Management & Communications (nos. 21, 22, 23, 24) IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  20. emergency events • common data access & visualization tools • power outages • timeliness of data delivery • personal-scale decision products • IOOS response teams IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  21. Responses to Recommendation #21 • Move toward a common operating platform to enable direct sharing of geospatial data • Understanding and implementing Open Geospatial Consortium standards • Remote data staging and access via the cloud • Systematically address potential power failure points • For personal-scale products, provide scalable, multi-resolution data sets that also contain metadata to trigger scale-dependent constraints • Technology Focused Contingency Planning such as a cloud-based virtual Emergency Operations Center • Collaborate with ORR on capabilities and limits of ERMA for response planning • Test the effectiveness of data discovery and access services for an emergency response scenario IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  22. standards & protocols • global observations • business & industry • satellite data IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  23. Responses to Recommendation #22 • Standardize a process for bringing new data types or user groups into the IOOS standards • Implement an IOOS approved data standard and protocol list that includes IOOS branding. Existing IOOS-compatible systems in public and private sectors could seek certification, establishing a core of functional IOOS systems. • Increased band-width across the internet combined with improved software for data extraction techniques will enable better integration of satellite data with other IOOS observations • Evaluate current data services and interoperability via a series of discovery, access and use tests driven by one or more scenarios IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  24. quality assurance/quality control • metrics on users & usage • functionality of data assembly centers IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  25. Responses to Recommendation #24 • Instead of focusing on instrument calibration, it may be more productive to encourage or even mandate reporting of error and uncertainty measurements including model outputs • Develop a QARTOD (Quality Assurance for Real-time Oceanographic Data) software “layer” to implement recommended tests that can be widely shared and implemented • Investigate QA/QC options, e.g. implemented locally/regionally versus at a central data assembly center • It is not clear which “liability” issues need to be resolved • Metrics on data access and use is essential and can be programmatically implemented not just for web sites, but also for data access to web services • Number, type and functionality of DACs is very important including guidelines on lifespan of data availability and procedures for archiving IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  26. NOP Implementation Plan – April 2013 3 Milestones for IOOC agencies assigned to DMAC Steering Team IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  27. Milestone 1 “Develop, evaluate, and expand an integrated geospatial database of Federal and non-Federal, certified and non-certified ocean observation data to provide access to public information and provide extracts or contact information for privately held information (IOOC Member Agencies)” Proposed IOOC Action: Assign to DMAC ST • Assess current integrated geospatial databases per this milestone (July 2013) • Identify limitations to existing databases (September 2013) • Suggest improvements to existing databases (November 2013)

  28. Responses to NOC Milestone #1 • A wide assortment of new and emerging tools and technologies are broadly enabling increased discovery and access to ocean observing data • However, significant but solvable obstacles remain including semantic (how data are described) and syntactic (data formats and communications protocols) • Adoption of an increasingly small range of data formats are helping improve interoperability • Non-profit organizations such as OGC and Unidata are improving open source tools that are widely used – this includes a core set of web services developed and tested through sponsored forums by OGC and enhancements to data formats such as netCDF supported by Unidata as a set of software libraries and self-describing, machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. • Data brokering is also emerging from the NSF-sponsored EarthCube project as a process for negotiating and resolving interoperability obstacles between service-based data providers. IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  29. Milestone 4 “Identify the existing data services and systems, as well as the requirements to support integrated discovery and access through an information management system and integrative functions required for the management system. (IOOC Member Agencies)” Proposed IOOC Actions: Assign to DMAC ST • Assess current data services, systems, and requirements (July 2013) • Identify limitations to data services, systems, and requirements (September 2013) • Suggest improvements to data services, systems, and requirements (November 2013)

  30. Responses to NOC Milestone #4 • Imperative to assess the readiness of interoperability for current data services, systems and requirements perhaps via a simple template to capture respective methodologies • The assessment of interoperability will help identify commonality across organizations such as the IOOC member agencies and the types of tools and resources needed • Key questions that could be resolved include impacts on the consumer (e.g. does the system allow subsetting? is the delivery in a framework with sufficient tools for translating or assimilating?) and discoverability (e.g. can the system be brought into a discovery tool such as a catalog service? are the data adequately described?) • A DMAC ST-led process to census this type of information might take 12 months to provide meaningful discussion and productive results. IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  31. Milestone 5 “Identify the limitations of existing methodologies for integrating observational data, including coastal and global ocean remote and in situ data, physial and biological data, and ocean observations and socioeconomic data. (NASA, NOAA, NSF, DOI [USGS], DOE)” Proposed IOOC Actions: • Partially fulfilled by IOOS Summit Report, Bio Task Team, and DMAC ST actions under 1 & 4 • Requires additional effort by identified agencies 

  32. Responses to NOC Milestone #5 • Communicating/disseminating clearly to technical implementors the landscape of compliant data services, encodings, vocabularies, etc. • Development/deployment of service validation tools that provide constructive, actionable feedback to service providers • Promoting the use of integrated or distributed standard-compliant services and catalogs will be the key, including client code to facilitate this process • Increased attention to a synchronized process for the integration of biological data with the emerging DMAC architecture – it is still problematic to fully integrate biological data into a bio-physical system because of the generally different approaches to measurement and the lack of equivalent standards for data delivery • Cannot hope to produce reliable, quantifiable climate-change forecasts without a better understanding of how bio-physical processes integrates up to the bigger picture IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  33. IOOC Meeting – September 23, 2013 DMAC Steering Team IOOC Interagency Ocean Observing Committee

  34. Interagency Ocean Observation Committee’s DMAC Steering Team 3rd Meeting – February 27-28, 2013 Charly Alexander – U.S. IOOS Program - Chair Consortium for Ocean Leadership, Washington, D.C. February 27-28, 2013 – COL, Wash, DC IOOC DMAC Steering Team Interagency Ocean Observation Committee

  35. Opening remarks… • Introductions (members/stakeholders/others) • Terms of Reference – our mission • Timeline – our work to date • Update on the IOOS Summit • The way forward • Questions/Discussion February 27-28, 2013 – COL, Wash, DC IOOC DMAC Steering Team Interagency Ocean Observation Committee

  36. Introductions… Others February 27-28, 2013 – COL, Wash, DC IOOC DMAC Steering Team Interagency Ocean Observation Committee

  37. Timeline – our work to date… Four meetings: • May 11-12, 2011 • January 18-19, 2012 • skipped June 2012 to work on CWP for IOOS Summit • September 5-6, 2012 • February 27-28, 2013 February 27-28, 2013 – COL, Wash, DC IOOC DMAC Steering Team Interagency Ocean Observation Committee

  38. Review of May 2011 Meeting… • US Army Corps of Engineers – challenges/contributions • US DMAC status report (DMAC Plan) • QARTOD • Observing asset inventory • NSF’s OOI-CI • Standards recommendation process discussion • Agency updates February 27-28, 2013 – COL, Wash, DC IOOC DMAC Steering Team Interagency Ocean Observation Committee

  39. Review of Jan 2012 Meeting… • DAY 1 • Introduction/Re-Orientation • US IOOS DMAC Update (D. Snowden) • NASA Data Management Challenges (M. Gierach) • OGC Web Services (L. Bermudez) • Update on NSF’s OOI Cyber-infrastructure (M. Arrott) • DAY 2 • U.S. IOOS QARTOD(C. Alexander/D. Snowden) • NSF Earth Cube (J. Schopf) • Emerging Priorities/Recommendations • Wrap-Up/Next Steps February 27-28, 2013 – COL, Wash, DC IOOC DMAC Steering Team Interagency Ocean Observation Committee

  40. Review of Jan 2012 Meeting… Steering Team Roles & Responsibilities • Clarify how findings/recommendations are processed • Design/conduct DMAC customer satisfaction survey • Recast meetings; 1-2 outcomes, breakouts, etc. Standards & Best Practices • Adopt use of data catalogs as a standard tool • Industry adopt use of Sensor Model Language for all instruments • Promote uniform guidance on use of netCDF February 27-28, 2013 – COL, Wash, DC IOOC DMAC Steering Team Interagency Ocean Observation Committee

  41. Next Steps – action items (Jan 2012) • Post materials to updated web site (done) • Meeting minutes/summary report (drafts complete) • IOOC briefing on findings/recommendations (today) • IOOC designate permanent ST Chair (US IOOS recommends C. Alexander) • OGC analysis of survey results • OOI-CI: questions and conference call • NSF’s Earth Cube: review capabilities document • Recommend specific execution priorities to IOOC? • Potential engagement mapping priorities to IOOS summit? • Planning/coordination for 2nd 2012 meeting February 27-28, 2013 – COL, Wash, DC IOOC DMAC Steering Team Interagency Ocean Observation Committee

  42. What the DMAC ST needs from the IOOC • Guidance (criteria?) on how to proceed with next steps • suggest ST moves forward on 1-2 specific priorities • suggest ST activates “tiger teams” to identify or specify a data management protocol on a test case and IOOC helps identify participants • Organizational support for broader engagement on DMAC • suggest ST members identify key POCs for IOOC members to contact • suggest IOOC members share ST reports, etc. with IT/data management leadership in their organizations • Support for mapping DMAC priorities to upcoming IOOS Summit • suggest asking ST for volunteers for an IOOS Summit DMAC team • suggest a ST member begin attending IOOS Summit planning meetings February 27-28, 2013 – COL, Wash, DC IOOC DMAC Steering Team Interagency Ocean Observation Committee

  43. Review of Sept 2012 Meeting… • DAY 1 • Icebreaker – DMAC Concept Mapping • EPA: Virtual Host Presentation/Discussion (K.Kirby) • Priorities for a USE CASE – orientation/assignments • Breakout Sessions I (candidate use cases) & II (relevant DMAC priorities) • DAY 2 • IOOS Summit Update (R. Morrison) • IOOC Request – Assessment of Summit white papers (D. Legler) • USE CASE writing teams • Wrap-Up/Next Steps February 27-28, 2013 – COL, Wash, DC IOOC DMAC Steering Team Interagency Ocean Observation Committee

  44. First – our Summit white paper… October 22, 2012 – COL, Wash, DC DMAC Steering Team

  45. … and our Recommendations • Implement IOOS standards and evolving best-practice protocols for the whole data life cycle, including metadata, quality control, discovery, and archiving. • Build from the bottom up with an agile, use-case-driven approach instead of a multiyear, top-down design • Develop tools that query and handle standards-based responses for major development and research languages. • Provide training, up-to-date educational materials, and support on these protocols for providers and users. • Ensure development of social media that enable providers and users to share code, techniques and experiences. • Develop IOOS compliance procedures and a compliance-testing suite. October 22, 2012 – COL, Wash, DC DMAC Steering Team

  46. Use Case discussions Group 1: Human Health & Beach Closures Group 2: Emergency Response, Renewable Energy Group 3: Biophysical conditions based on human impacts, Ocean Energy October 22, 2012 – COL, Wash, DC DMAC Steering Team

  47. Request from IOOC 1. DMAC Assessment of other Summit white papers: 34 of the 100+ papers were judged to have a DMAC component or intersection with ST white paper (reviewed 24 at ST meeting) October 22, 2012 – COL, Wash, DC DMAC Steering Team

  48. Request from IOOC • 2. Possible DMAC break-out session at Summit • Lightning talks on key themes/DMAC successes • Based on DMAC correlations among white papers • Proxy for bringing one or more use cases forward • Calibrate with messages emerging in Summit proceedings/chapters • Demonstrate connections to Ocean.data.gov October 22, 2012 – COL, Wash, DC DMAC Steering Team

  49. Next Steps • Review EPA’s System of Registries (DMAC ST, on-going) • Get clear guidance on ability to revise or update Summit white papers (IOOC Support Office, 9/14) • Develop DMAC session for the IOOS Summit (Alexander/Signell/Casey, 9/21) • Finalize Oil Spill Case Study (emergency response) (Signell/Norris, 10/19) • Finalize beach closure case study (Kirby/Morrison, 10/19) • Finalize hypoxia case study (Thomas/Gierach, 10, 19) October 22, 2012 – COL, Wash, DC DMAC Steering Team

  50. Post-Summit UpdateEric LindstromInteragency Ocean Observation CommitteeTUES 22 JAN 2013

More Related