280 likes | 420 Views
eGIS Steering Committee Update Legacy Data Migration MapGuide Evolution 2013-Q1 Release Estimation 2012-Q4 Progress Dashboard Next Steps 2012 eGIS Program Accomplishments APPENDIX – Details & Other Info. PRESENTATION FOR E GIS WORKING GROUP. eGIS Steering Committee Update.
E N D
eGIS Steering Committee Update Legacy Data Migration MapGuide Evolution 2013-Q1 Release Estimation 2012-Q4 Progress Dashboard Next Steps 2012 eGIS Program Accomplishments APPENDIX – Details & Other Info PRESENTATION FOR EGIS WORKING GROUP
eGIS Steering Committee Update • Last meeting: 12/6/12 • Next meeting: 1/10/13
Legacy Data Migration (LDM) Update “Plan for the Plan” LDM Track 1 • Identify non-EAM datasets, decide on a default order, and start converting datasets – Underway since early 2012 • Establish backfill process – Done LDM Track 2 • Map process (swim lanes) – Done • Estimate future schedule based on historical throughput and interdependencies – In progress • Build initial ArcGIS training plan for Data Stewards / Data Editors based on schedule • Estimate data backfill effort implied by schedule • Understand what non-GIS software systems are dependent on the legacy GIS data, and the tasks needed to ensure their continuity
MapGuide Evolution Update “Plan for the Plan” MapGuide Track • Collect and analyze MapGuide feature usage across all stakeholder groups – Responses coming back from Working Group • Revise legacy data migration schedule to accelerate the redundancy of MapGuide • Precipitate action planning by setting 7/1/2013 as turn-off date for edit ability in MunSys/MapGuide for all non-EAM datasets • Identify critical tasks to support turn-off date for MapGuide, and establish priorities with Working Group for Steering Committee approval • If staff augmentation would accelerate progress, make request to Steering Committee
MapGuide Apps Potential Legacy MapGuide applications that could be recommended for the 2013-Q1 Release
MapGuide Evolution Planning Grid As of 12/19/12
eGIS Working Group - Next Steps • Official start for Q1 2013 Release on 1/2. • Go Live for Q4 2012 Release on 1/9. • Confirm final Q1 2013 Release contents on 1/10. • Review draft Legacy Data Migration plan/schedule with committee on 1/10. • Initiate analysis for Legacy MapGuide Evolution. Dec – Feb. • Dependent on Legacy Data Migration • Needs, requirements analysis • Solution recommendations • Initiate Training analysis. Dec – Jan. • How to expend remaining credits? • Coordinate desktop training with Legacy Data Migration?
Review of 2012 eGIS Accomplishments • ELA Signed • Infrastructure procured, installed, functional testing, and load tested • ArcGIS Online Pilot • Data Migration (Planning, PSS, EMA) • New Data Layers (Economic Development, MPO) • ArcGIS Desktop 10.1 available for deployment. Call BTS CSC at x3HELP • Election Polling Places in production • Aerial Image Viewer in production • Working Group formation and launch • Requirements repository and gathering, scoring & prioritization process • Quarterly Release strategy and execution • Added Team Members (Service Owner, PM, BA) • EAM-GIS Change Order • Community Map Agreement – final stages • ArcGIS Online Agreement – final stages
Details & Other Information APPENDIX
Legacy Data MigrationDefault Priority Order Non-EAM Only
Legacy Dataset Migration Detail Non-EAM Only
Legacy Dataset Migration Detail Non-EAM Only
Legacy Dataset Migration Detail Non-EAM Only
Legacy Dataset Migration Detail Non-EAM Only
Legacy Dataset Migration Detail Non-EAM Only
Legacy Dataset Migration Detail Non-EAM Only
Legacy Dataset Migration Detail Non-EAM Only
Legacy Dataset Migration Detail Non-EAM Only
Legacy Dataset Migration Detail Non-EAM Only
eGIS Legacy Migration Process Swim Lanes Contents (3 pages): Develop Data Model to Develop Workflow for Data Cleansing Create Meta Data to Turn Over Maintenance Responsibility Develop Backfill Scripts to Publish Feature Service Annotations: Rotated blue text indicates a progress dashboard tracking event Art Stadlin
Legacy Dataset Migration Process (1 of 3) eGIS WORKING GROUP Working Group Approved Priorities DATA STEWARD AND/OR DEPT. SME Work With Carol Work With Carol Work With Carol Work With Toni Availability To Do Work Develop Data Model Initial Data Conversion / Validation Identify Data Steward Move Data into Editing Environ. eGIS TECHNICAL TEAM Develop Data Cleansing Rules / Process Develop Workflow Process (for Cleansing) Receive Notification of Migrated Data A eGIS BUREAU CAB Seek CAB Approval of Change to Publish DB ArcGIS Desktop 10.1 Install ArcGIS Desktop 10.1 Training (Reviewer) DESKTOP SUPPORT INITIAL CONVERSION FINAL CONVERSION
Legacy Dataset Migration Process (2 of 3) DATA STEWARD AND/OR DEPT. SME Approve Data Cleansing Bureau will maintain Who Will Maintain These Data? Turn Over Maintenance Resp. Dept will maintain Move Data to Editing Environment Replicate to Publishing DB eGIS TECHNICAL TEAM B Create Meta Data Develop Workflow Process (for Production Maintenance) eGIS BUREAU A Data Cleansing Seek CAB Approval of Change to Publish DB CAB QA (QUALITY ASSURANCE) ArcGIS Desktop 10.1 Training (Edit) DESKTOP SUPPORT PUBLISH (INTERNAL)
Legacy Dataset Migration Process (3 of 3) Work With Carol DATA STEWARD AND/OR DEPT. SME Develop Backfill Scripts / Process (where needed) eGIS TECHNICAL TEAM Test Backfill Script (with Data Steward or SME) Implement Script in Legacy Environ. B eGIS BUREAU Seek CAB Approval of Change to Publish DB CAB Publish Feature / Map Service eGIS TEAM PUBLISH (EXTERNAL)