1 / 24

Managing Data & Information with the SECN Decision Support System

Managing Data & Information with the SECN Decision Support System. GWS Meeting New Orleans, LA M arch 14-18, 2011. Outline. Background and a brief history Planning Process Transition: MS Access to SQL Server SECN Decision Support System Next Steps. Assess Needs. Assess Needs.

turner
Télécharger la présentation

Managing Data & Information with the SECN Decision Support System

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. Managing Data &Information with the SECN Decision Support System GWS Meeting New Orleans, LA March 14-18, 2011

  2. Outline Background and a brief history Planning Process Transition: MS Access to SQL Server SECN Decision Support System Next Steps

  3. AssessNeeds AssessNeeds AssessNeeds AssessNeeds A Brief History Conceptual Modeling Conceptual Modeling Conceptual Modeling Conceptual Modeling Develop Protocols Develop Protocols Develop Protocols Develop Protocols VS Planning Implement Implement Conceptual Modeling System Design DM Planning • Information Needs Assessment (INA) • Standard IT approach to systems planning

  4. Outcomes of the Needs Assessment • Preliminary protocol development summary documents • Protocol reporting (output) requirements and the necessary inputs to meet those requirements • Preliminary conceptual object model • The foundation for database development • Describes required database components and the relationship between those components

  5. Conceptual Object Model

  6. Take home message • To meet the needs of our program and the expectations of end-users, our data management system should be an integrated, enterprise level solution that takes advantage of the following: • Data integration across protocols • Better performance, especially for larger datasets • Easier access across multiple locations • Minimal data redundancy • Robust, online access to the centralized system • Greater reporting capabilities

  7. Status: 2006-2007 • Initial database development efforts in MS Access for our fixed-station water quality monitoring protocol • Due to need for rapid database development • Lack of approval from IT to use SQL Server • Current staff not skilled in SQL server

  8. Fixed-station water quality monitoring • Data loggers collect data every 30 minutes, year round • >17,500 records, for 8 parameters, per station, per year • By late 2005 there were 5 stations operating • Currently there are 17 stations in operation • Discrete nutrient data also collected monthly and quarterly • Requires equipment inventory and maintenance records • Requires extensive pre- and post-deployment calibration • Requires extensive QA/QC procedures using ancillary weather data and manual examination of the data

  9. Database Problems for this Protocol • Issues with Implementing this protocol database in Access: • Multiple users required multiple database copies – leading to problems with database replication • QA/QC procedures difficult due to amount of data and performance issues • Other Issues • Unable to centralize due to poor performance • Database size limits rapidly approaching • Inadequate reporting capabilities

  10. Lessons Learned Involve local IT staff early in the process and throughout the process Make sure your staff have the skills necessary to support whatever database and applications that you build. Don’t start development until your protocol data collection procedures have been stabilized or finalized

  11. AssessNeeds Skipping ahead to today Conceptual Modeling System Design Implement During 2008, SECN transitioned from MS Access to SQL Server for existing databases Almost all new development takes place in SQL Server Development begins when the protocol is stable

  12. SECN SharePoint Site Windows Server 2003 SQL Server 2008, enterprise edition SQL Server Reporting Services Microsoft Office SharePoint Server (MOSS) 2007, enterprise edition Internet Information Services (IIS) 6.0 .NET framework 2.0 and 3.0 Dundas Data Visualization for Reporting Services Bing Maps Development tools: Microsoft InfoPath, Visual Studio

  13. Functionality Overview • Data Entry • Enter field data collection information • Update database lookup tables • Keep an inventory of equipment and repairs • Data QA/QC • Save an electronic copy of data sheet – as entered • Save an electronic copy of data sheet – as certified • Certify data entry • For data logger data – flag as suspect, delete • Data Analysis and Reporting • Standardized reporting available on SharePoint • Map viewer application

  14. SECN SharePoint Site http://secn

  15. Form is in MS InfoPath Matches data sheet * indicates required Built in QA/QC Data submitted directly to the database as provisional data Form saved as a record of data entry Data verification is a separate step

  16. Update lookup tables

  17. Inventory Equipment

  18. QA/QC – Certify Data

  19. Data Analysis and Reporting

  20. Next Steps Continuing development for protocols coming online Expanding our reporting capabilities and data access tools Working with US-FWS I&M program to take advantage of our system whenever protocols allow Moving our mapping application to NPMap

  21. Questions?

More Related