Enterprise Data Access, Analysis, and Reporting Strategy (EDAAR)

1. Enterprise Data Access, Analysis, and Reporting Strategy (EDAAR) May 1, 2007 Ken Tootle, Accountability Information System (AIMS) Coordinator

2. Why Do We Need EDAAR? Background: NRCS has a large amount of data collected, but it is poorly organized by application instead of business process and contains data for all levels of the agency. Bottom Line: The agency is data rich and information poor.

3. Vision • Have data, tools and information that are: • easily accessible (web site) • secure • integrated (across data stores) corporate data • easy to use • Facilitate major business processes for internal and external customers • Results • More efficient and effective operations

4. What is EDAAR? • A strategy to EDAAR enable all applications, by designing the information architecture into logical integrated reports, by developing standards for data design, geo enabling, google enabling, operating principles, etc. • A central web portal that provides application data viewers and integrated data at the summary and analysis levels

5. Strategy Portion of EDAAR • Developing the agency information architecture including categorization and taxonomy associated with data, analysis tools, and reports. • Define the standard look and feel of data/information across applications • Define NRCS data access and availability standards • Define where data should exist to help eliminate reporting/data redundancy • Define major business processes and information needed for the process • Providing standards and conventions for data marts, data access, data analysis tools, and reports. • Consistent integration and visualization of data, charts, and maps • Consistent ability to download and post process data for analysis purposes • Consistent approach for metadata use and display

6. Deliverables from EDAAR • A web site(s) that provides information for various customer segments • Develop appropriate infrastructure (data marts, data access tools, data viewers) • A document listing the acceptable tools for data analysis, data viewing and reporting tools (Data Viewer, Dashboard, Etc.) • All EDAAR data/information will be made available so that it can be used in other applications such as Word, Excel, Arc GIS, etc. • Google enable data/information • Geo-enabling data • Map by Land units, Contract locations, Service Centers, Counties, watersheds, ecoregion, etc.

7. EDAAR Strategy Core business applications (PRS, ProTracts, etc) that capture data and provide standard application centric reports and analysis tools. EDAAR Portal: One stop for data viewers, integrated data reports, expanded analysis tools in common one-stop business centric portal. Customer Relations Management (CRM) Software – Integrated data access at a customer centric level Data Marts

8. EDAAR Project Operation • Steering Team to work with other efforts such as CRM, Dashboard • Design Team made up of Field and State users to provide input • Focus Groups to help test and give input to system. • Periodic feedback to FOTBCC

9. National Steering Team • Kathy Gugulis – Co-Executive Sponsor • Tom Christensen – Co-Executive Sponsor • Ken Tootle, Natural Resource Manager, OMOD/SPA • Wendall Oaks, Director, ITC • Jon D. Vrana, Team Leader Programs Business Tools Team, PGM • Noller Herbert, National Software Engineer, S&T • Marjorie Harper, Program Analyst, SSRA • Kristie McKinley, Resource Specialist, OMOD/SPA • Paul Taylor, Jr., Asst. State Conservationist for Operations, NRCS Washington State Office • Kathy Green, Management Analyst, Programs Business Tools Team, PGM • Mary Grande, Business Tools Specialist, Programs Business Tools Team, PGM

10. Steering Team Nominations Due 5-15-07 – See NB 330.7.4

11. Timeline Overview 24-36 Months to Complete Entire Project • FY 07 – Phase 1 – Internal Field Level Data Access • Data Viewers of 5 Operational Databases (limited integration between databases) • FY08 – Phase 1 – Internal Field Level • Web Site and Integration of Data and Reporting Products • FY08 – Phase 2 – Internal Above Field Level • Continue developing data and reporting products for the State and National internal customers • FY09 – Phase 3 – External Customers • Continue developing data and reporting products for the external customers

12. Deliverables for Phase 1 FY 07 The Internal Field Level Business Processes • Information architecture • Data mart architecture • Web site design • Initial data standards • Field level operations data needs • What data is available and is not available • Data permissions/security/preferences • Metadata for EDAAR information products

13. Phase1 Deliverables Continued Data Viewers: Make the basic data available for the five primary operational databases • Financial (FFIS, Fund Manager, CIS, TCAS) • Contracting (Pro Tracts) • Customers (SCIMS) • Performance (PRS, POINTS, ABC) • Planning (NCP)

14. Phase 2 FY 08(Internal State and National Level Business Processes) Define • Identify and Integrate other data needed above field level such as natural resource data, employee data, FSA data, etc., • Complete data access and reports for the other levels of the agency and integrate the ERS site and products with the Internal Customer Segmentation Study.

15. Phase 2 Deliverables FY 08 • Integrated Reports & Viewers in the I am a… and I want to… approach • Integrate 5 Operational Databases • Integrate reports from other databases such as Web Soil Survey, NRI, EMPower, Program Allocation Data mart, EFOTG, Conservation Practice Standards, etc. • Integrate EDAAR data with the Customer relations Management software effort.

16. Integration Considerations • Customer Segmentation Analysis • Business Process Mapping or Analysis • Cross application integration (combining data from the major databases and creating information) • New USDA-NRCS web page design • Customer Relationship Management Software (CRM) • Geospatial team recommendations • Lean six sigma grants programs (FMMI & Protracts)

17. EDAAR Welcome to EDAAR Reports March 12, 2007-The new reporting tab provides you with the five operational data marts available by using data viewers and standard reports. Contracting Pro Tracts Performance PRS Practices/Programs NCP Customers SCIMS Financial FFIS EDAAR Phase 1 Potential Data Viewers

18. I want to work on… • Conservation Operations • Conservation Programs • Contracting • Financial • Monitoring • Performance Potential Future Look of EDAAR

19. 90% of All Business Operations Should be answered by “I Want To…” approach • Conservation Operations • Conservation Compliance • Conservation Planning • Program Contracts • Practices • Customers • Financial • NRCS Operations • Performance • Employee • Outreach & Civil Rights • Science & Technology • Resource Inventory • Cartographic/Geospatial • Engineering/Technical

20. Conservation Planning • I want a list of plans that include the tract, names, addresses that have practices scheduled that have not been applied for all fiscal years. • I want to see a map or list of all plans with at least one practice scheduled this fiscal year. • I want to build a map by practice (s), by program, by land use, etc. • I want to know how many CNMP plans (100 code) have practices scheduled to be completed by FY. • I want to know how many plans have been applied but not reported to PRS. • I want to know how many duplicate plans I have by business id. • I want to know how many plans have missing or erroneous data.

21. Currently you have to do multiple searches in PRS and Pro Tracts to find the data.

22. EDAAR will have information from both ProTracts & PRS in one report.

23. Thanks!