1. Integration and Collaboration A Simple Networked Information System

2. PNAMP Principles (from the Executive Network Charter Resource Policy and Management: 1.The purpose of monitoring efforts is to provide the most important scientific information needed to inform public policy and resource management decisions. 2.Efficiency and Effectiveness: Cooperative monitoring will enhance efficiencies and effectiveness of our respective and collective efforts. 3.Scientifically Based: Environmental monitoring must be scientifically sound. 4.Shared Information: Monitoring data must be accessible to all participants on a timely basis.

3. Information Flow—First Steps

4. PNAMP Goals Improve communication between monitoring programs across state, tribal, and federal organizations. Improve scientific information needed to inform resource policy and management questions and decisions. Seek efficiencies and cost-effectiveness across monitoring programs through compatible and cooperative monitoring efforts. Promote science-based credibility of monitoring and assessment efforts. Share resources and information between monitoring programs across state, tribal, and federal organizations.

5. Goals for 2008 Support PNAMP’s Immediate Role to Research Monitoring and Evaluation Science Integrate with other Information Sharing Efforts Disseminate Information Broadly Synchronize Collaboration and Communication with Product Dissemination Optimized Internal Organization Support Work Groups and Products E-Publication of existing and future recommendations

6. Examples of Simple Disjointed Information Sites (DIS) University of Oregon Blackboard Elsevier Pacific Northwest Cooperative Ecosystem Studies UnitPacific Northwest Cooperative Ecosystem Studies Unit The Coalition for Networked Information National Environmental Methods Index North Cascades National Park Service ComplexNorth Cascades National Park Service Complex What’s missing? PNW Aquatic Monitoring Methods, Protocols and Techniques Recommendations and… Collaboration between and Among: PNAMP and its (EN), RCO, CSMEP, The Puget Sound Partnership, The Federal Caucus, WA Monitoring Forum, OWEB, WA Salmon Recovery Boards, etc….and, links to all the above.

7. Even in Bulgaria?

9. PNAMP Charter Elements VI Communications as it applies to Networked Information (from PNAMP Charter) Internal – The Coordinator and workgroup leads will use electronic means to facilitate informal routine communications to the extent possible; other methods will be explored as dictated by need. External – The Steering Committee and Coordinator will provide external communications via electronic means including development and use of internet access to PNAMP products and information, […]

10. Short and Long Term Goals and Needs Short Term Product Dissemination Collaboration Communication Organization Optimizing RME Deployment of an NIS (Summer 08) Nominal Resources Integration w/ long term pilot and data system efforts Long Term Integration w/ long term pilot and data system efforts Access Clearinghouse Portals New FTE’s Data Access Data Management Metadata Advanced Functions

11. Conclusions NIS’s are designed to expand and upgrade PNAMP’s internal and external organizational needs and streamline our production and external outreach needs There is an expectation that PNAMP help focus the five-six RME organizations towards a single and straightforward goal of coordination PNAMP is well suited to do the NIS pilot project because our goal is simple and needs are immediate and we are committed and chartered to integrate Structured workgroups with short and long term planning and PRODUCTS Most data management, and/or design information has become difficult to agree upon and/or deploy StreamNet’s new scope provides an opportunity to manage larger and more complex systems, and, NWHI is a proven exception. An NIS system will allow PNAMP to help many groups to compare and contrast methods. Finally, PNAMP and its partners will have expanded potential to provide products (e.g. details ranging from statistical designs to field logistics) and provide them as reviewed and vetted recommendations.

12. Total Success Methodology 1.Planning  2.Design (in process)  3.Operation (Subcommittee – Spring 08) 4.Optimization (Platform- Spring Summer 08) 5.Content (ready, waiting and future) 6.Deployment and Delivery (sooner, not later—Summer/Fall 08-Beta) = Success (Deployment, Communication, Collaboration and Integration (Fall/Winter 08-09) Next Steps: 1.Integration with Data Management, Metadata 2.Extensibility of NIS + +