Reaching State Zero Without Losing Your Versions
•Download as PPTX, PDF•
0 likes•387 views
Reaching State 0 without losing your Versions Describes how we successfully helped Intermountain Rural Electric Assn (a Colorado utility) take their Esri/Schneider Electric GIS system to "state zero" (where no outstanding versions exist), without losing their many crucial versions and edits within those versions. Utilizing the SSP All Edits Reporting & QA Tool and the SSP Nightly Batch Suite product, we were able to record all version and edit information for critical versions that could not be lost, then delete the versions completely, taking the system to state zero. IREA was then able to perform various maintenance activities that are enjoyed at state zero. Once completed, SSP replayed the edits and versions back into the GIS, and users were utilizing the system as if nothing ever happened.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Reaching State Zero Without Losing Your Versions
Similar to Reaching State Zero Without Losing Your Versions (20)
More from SSP Innovations
More from SSP Innovations (20)
Recently uploaded
Recently uploaded (20)
Reaching State Zero Without Losing Your Versions
- 1. STATE 0 Reaching State 0 without losing your Versions
- 2. Agenda • Introduction • Business Drivers • Technology • Questions?
- 3. SSP Innovations Nine year old GIS and WMS consulting company based in Denver, CO area • Work exclusively in the United States utility industry • Includes Electric, Gas, Water, Wastewater/Sewer, Fiber Strong partnerships with Esri and Schneider Electric • Certified to implement/integrate/customize entire Esri & SE GIS suite • Also do GDB consulting & WMS consulting/implementations Began working with IREA 2/12: implementation of SSP-All Edits Report • Have since partnered on several projects (upgrades, custom reporting in Designer, custom support, education services)
- 4. Intermountain REA Service Area
- 5. Intermountain REA Statistics 147,000 Customers 200 Employees 5 GIS Employees 15 Designers 5,000 Square Miles 7,900 Line Miles 47 Substations 279 Feeders
- 6. Intermountain REA GIS ESRI 10.0 SP5 ArcGIS Desktop ArcGIS Server ArcGIS Online Arc Engine Schneider Elec. 10.0.3 ArcFM/Designer ArcFM Server Silverlight Viewer Engine Viewer Redliner GDBM
- 7. The Problem NAD27 to NAD83 Costs for new data Base Map data in ArcMap GPS Transformations ArcGIS Online Needed State 0 to transform the projection 300+ design versions Rebuilding the network Production down time
- 8. “Hatching the Plan” ESRI UC 2012 ArcGIS Online – the future of IREA’s GIS system Constant communication between IREA, Schneider Electric (formerly known as Telvent), and SSP Innovations “Why can’t we export the designs to XML and just replay the versions back in place?”
- 9. “This might work…” Engine Viewer with Redliner Save Redline sessions to XML Replays the session edits to the Enterprise GIS Telvent Design XML Tools Export/import capabilities for designs using XML Works on both WFM and GIS side SSP All Edits Stores all edit actions in database Has graphic display of edit locations
- 10. Decision Point SSP added feature classes to All Edits Not just graphic representation of edits Replay old versions Key to IREA State 0 Project SSP Nightly Batch Suite Provided the processing engine for the project
- 12. Technology How did we came up with the solution? • Utilizing two of our tools: • Night Batch Suite • All Edits Tool • The majority of the work was already done by our All Edits Tool • Reconciles a version and gets differences • Writes those differences to the database • Read those differences back from the database. • The remainder of the work was taken care of by the Night Batch Suite. • Write version to the database • Recreate version from the database • Update designs’ xml
- 13. State 0 Plan • Reproject Data over a weekend time frame. • Freeze production by COB on Thursday • Start preparation on Thursday. • Run processes over the weekend • Get users back in the system first thing Monday morning
- 14. Preparation Preparation • Deployed tools • Backed up production database • Copied production to a temp database (IGISTEMP) • Configured tables and feature classes to host data • Started processes
- 15. State 0 Surgery Write Versions to Database (242 versions) • Started process around 5:00pm on Thursday • Total processing time: 8 hours and 15 minutes • Checked log file first thing Friday morning. • Reprocessed any versions with errors (4) • Reran Write Versions to DB Get to State 0 • Somewhat a manual process
- 16. State 0 Surgery • Exported ArcFM Configuration (XML) • Used python script to delete all relationships • At this point we were at State 0 and ready to reproject the data • Created IGISNEW database for reprojection • Re-projected data from NAD27 to NAD83
- 17. Put it back together Rebuilt the Database • Recreated relationships using python script • Rebuilt geometry network • Set privileges and re-versioned database • Converted objects to ArcFM and Designer • Swizzled Store Display to point to the new database • Imported ArcFM Configuration • Kicked off CreateVersionsFromDB batch application
- 18. Put it back together If Schneider Electric Designer shop • Update the design graphics • Manually rebuilt Composite Favorites
- 19. State 0 Workflow
- 21. IREA’s Versions tree NAD83 Coordinate System
- 22. IREA & SSP Innovations The users never knew anything had changed
- 23. Challenges – Composite Favorites Composite Favorites: Store relative feature placement Store the projection in the record Stored as HUGEBLOB data type Solution: Create session in old database Place all Composite Favorites Process the State 0 and Re-Projection Recreate composite favorites from session
- 24. Challenges – Index Rebuild Two methods for Object Classes in new database: Create brand new w/ ArcCatalog Copy from old DB to new DB If copied from old DB, Rebuild indexes after relationships are created.
- 25. Challenges – User Stored MXD Two Check Items Here: Correct database source on any stored layers Change Data Frame coordinate system
- 26. Challenges – Double Check Logs Overnight CreateVersionFromDB Process bumped off NW Proceeded with rebuilding Processed missing versions Did not notice error in log Did not verify version count Discovered missing versions Rebuilt the lost versions Processed bad version later Moral of the story: Check your logs or …. The project goes from heart surgery to brain surgery P.S. Don’t forget to eat
- 27. QUESTIONS? Dennise A. Ramirez SSP Innovations dennise.ramirez@sspinnovations.com 720-891-0103 Duane Holt IREA dholt@irea.coop 720-733-5508
Editor's Notes
- WHO SSP IS: Just briefly a bit about who we are - SSP is focused on the electric, gas, water and fiber markets for core product implementation, customization, and systems integration. Chalk it to mostly GIS SERVICES work. We also partner heavily with Schneider Electric (previously known as Telvent) who provides a large set of utility specific products. Our main challenge with ArcGIS online was how to educate our customer base on this new platform because it really does present a fundamental shift in how utilities have traditionally used GIS.
- WHO SSP IS: Just briefly a bit about who we are - SSP is focused on the electric, gas, water and fiber markets for core product implementation, customization, and systems integration. Chalk it to mostly GIS SERVICES work. We also partner heavily with Schneider Electric (previously known as Telvent) who provides a large set of utility specific products. Our main challenge with ArcGIS online was how to educate our customer base on this new platform because it really does present a fundamental shift in how utilities have traditionally used GIS.
- WHO SSP IS: Just briefly a bit about who we are - SSP is focused on the electric, gas, water and fiber markets for core product implementation, customization, and systems integration. Chalk it to mostly GIS SERVICES work. We also partner heavily with Schneider Electric (previously known as Telvent) who provides a large set of utility specific products. Our main challenge with ArcGIS online was how to educate our customer base on this new platform because it really does present a fundamental shift in how utilities have traditionally used GIS.
- WHO SSP IS: Just briefly a bit about who we are - SSP is focused on the electric, gas, water and fiber markets for core product implementation, customization, and systems integration. Chalk it to mostly GIS SERVICES work. We also partner heavily with Schneider Electric (previously known as Telvent) who provides a large set of utility specific products. Our main challenge with ArcGIS online was how to educate our customer base on this new platform because it really does present a fundamental shift in how utilities have traditionally used GIS.
- WHO SSP IS: Just briefly a bit about who we are - SSP is focused on the electric, gas, water and fiber markets for core product implementation, customization, and systems integration. Chalk it to mostly GIS SERVICES work. We also partner heavily with Schneider Electric (previously known as Telvent) who provides a large set of utility specific products. Our main challenge with ArcGIS online was how to educate our customer base on this new platform because it really does present a fundamental shift in how utilities have traditionally used GIS.
- WHO SSP IS: Just briefly a bit about who we are - SSP is focused on the electric, gas, water and fiber markets for core product implementation, customization, and systems integration. Chalk it to mostly GIS SERVICES work. We also partner heavily with Schneider Electric (previously known as Telvent) who provides a large set of utility specific products. Our main challenge with ArcGIS online was how to educate our customer base on this new platform because it really does present a fundamental shift in how utilities have traditionally used GIS.