Automating and Scheduling Data Usage and Reporting
Download as PPTX, PDF0 likes1,388 views
The document outlines a presentation by Austin Hildreth regarding the automation and scheduling of data usage and reporting at the Washington State Revenue Department. It details the business needs for insight into progress, resources for report building, and outlines the tools utilized, such as Safe Software and Esri. Key benefits include process transparency and resource efficiency, with lessons learned highlighting the importance of leveraging existing tools for optimal results.
Automating and Scheduling Data Usage and Reporting
- 1. Automating and scheduling data usage and reporting Austin Hildreth Department Washington State Revenue
- 2. PRESENTATION AGENDA 1 2 3 4 Business Need Tools for Solution Build Solution Production and Output 5 Benefits and Lessons Learned
- 4. What was needed? ● Manager needs insight to progress and workload. ● Weekly updates to enterprise data. ● Multiple spatial data sets. ● Time/resources to build reports. ● XX hours to create custom report.
- 6. Safe Software • Desktop 2018 • Server 2018 Microsoft • Management Studio 2014 • Server 2012 ESRI • Desktop 10.6.1 • AGS 10.6.1 • Portal 10.6.1 Tools
- 8. Conceptual Workflow 1. Clip the current data to a snapshot from previous weeks data. 2. Write Added and Deleted data to a table. 3. Run workspace for new snapshot. 4. Run workspace for email notification.
- 9. Production dataset compared to snapshot
- 10. Whole Workspace
- 11. Feature Writer
- 13. FME Server Job Submitters
- 15. FME Server Job Submitters
- 18. How does it all start? Scheduler!
- 19. The Email
- 21. Benefits and Lessons Learned
- 22. Benefits - Transparency of process. - Ease of access and sharing. - Resources can do other work. - 2 weeks to implement.
- 23. Lessons Learned - Custom Transformers. - Leverage all the tools of FME server. - Let FME do the work.
Editor's Notes
- #5: Describe what cartographers are editing – and how (
- #11: Basic flow is replicated 6 tines for each dataset. Topographically related and make sure changes in one place that it also happens on a corresponding layer.
- #12: We have started replacing writers with Feature Writers. This lets the workflow continue (examples; logging, emails trigger next WS, validate and terminate)
- #17: Truncates the snapshot data and copies the production data.
- #18: How dores it run and what do we get?
- #19: Scheduler runs every Monday at 7:00 am