Esri UC 2016 - Central San and the Local Government Information Model
•
1 like•279 views
The story of how Central San built a new integrated spatial asset management platform, and how the Esri Local Government Information Model (LGIM) provided the foundation.
Report
Share
Esri UC 2016 - Central San and the Local Government Information Model
- 1. Central San and the Local Government Information Model Laying the Foundation for a GIS-Centric Wastewater Agency Carl Von Stetten GIS Analyst @cfvonner
- 2. Central Contra Costa Sanitary District (aka Central San or CCCSD)
- 3. Central San Fun Facts • Wastewater collection and treatment for 327,000 residents and business customers • Wastewater treatment for 134,000 residents of the cities of Concord and Clayton • Household hazardous waste collection for all residents in central Contra Costa County • Treat average of 30 MGD (up to 53 MGD in wet weather) • 1,500 miles of collection system pipelines
- 4. First, a little bit of history…
- 5. Central San GIS - BC* *(Before Computers)
- 6. Central San GIS 1996-2006 • Produce paper maps more efficiently • MicroStation + MGE • Intergraph CLIX workstations, then PCs with Windows NT 3.51 • Custom data model • Reliability issues • Frequent MicroStation file corruption
- 7. Central San GIS 1996-2006 • Started thinking about web maps in 1999 • Implemented 1st production web maps ~2002 • Autodesk MapGuide + Allaire ColdFusion • Creative solutions to linking to other systems/databases • Problems reliably converting MGE tiled data into seamless MapGuide files
- 8. Central San GIS 2005-2006 • Moved to Intergraph GeoMedia ‘05-’06 • Developed custom data model • Designed to balance needs of paper map production with web map accessibility • Better connectivity with other systems, especially Sussex (Accela) CMMS • Hired Intergraph to write custom code to automate tasks and build the linkages to CMMS and other systems
- 9. Central San GIS 2005-2006 • Rewrote entire MapGuide/ColdFusion web GIS to work with new data model • Used Safe Software’s FME to translate between GIS and database formats
- 10. Central San GIS 2006-2016 The level of integration we wanted… …what we actually ended up with. Photo Credits: Kmr1985 (Own work) [CC BY-SA 4.0 (http://creativecommons.org/licenses/by-sa/4.0)], via Wikimedia Commons (left image) & By sv1ambo [CC BY 2.0 (http://creativecommons.org/licenses/by/2.0)],via WikimediaCommons (right image)
- 11. Central San GIS 2006-2016 • Realization that maintaining two diverging inventories (GIS & CMMS) was our Achilles heel • Both inventories tracked similar attribute data • Inventories don’t match • >6% records don’t have matching IDs • Significantly larger number of records with attribute differences • Connecting to other business systems was similarly hard
- 12. A Fresh Start • Replace our GIS (GeoMedia + MapGuide) AND our CMMS (Sussex/Accela) • Implement a sustainable desktop/web GIS platform • Implement a GIS-centric CMMS • GIS would be inventory authority of record
- 13. Other Systems Requiring GIS Integration • Planning & Applied Research Group • Innovyze InfoWorks ICM SE for dynamic hydraulic modeling • Innovyze InfoMaster for asset integrity management and capital planning • Collection System Operations Division • WinCan / Granite XP / IT Pipes for CCTV inspection • Plan Review/Permits/Inspection Groups • Sungard (HTE) for permits, sewer billing, and parcel ownership/tax roll managment
- 14. Central San GIS Ecosystem
- 15. Choosing the Platforms • Esri ArcGIS Desktop / Server / Portal • Integrated solutions from single vendor • Azteca Cityworks AMS • Tight integration with ArcGIS Server • Features met needs of our Collection System Operations division • Management decided to convert our Plant CMMS to Cityworks too to consolidate asset management
- 16. Getting the Help We Needed • Signed an EEAP contract with Esri in March 2013, renewed once • Signed 3-year ELA with Esri in November 2014 • Issued RFP for CMMS implementation/ migration services • Awarded contract to Woolpert
- 17. Let’s Design Another Data Model From Scratch (uh… no) • As part of EEAP, Esri staff started to assemble a custom data model from previous customer implementations • Central San GIS staff started looking at the Local Government Information Model (LGIM) • Decided the LGIM was a good fit for our organization
- 18. LGIM Advantages • Supported by many Esri partners • Sets an industry standard • Improves data interoperability/ sharing • Provides structured framework for data model consistency • Out-of-the-box maps and applications for both desktop and web • Attribute Assistant automates many tasks • Support for parcel fabrics/ geometric networks • Use as much/as little as you need
- 19. LGIM Example Feature Datasets Feature Classes
- 21. Automating the Data Migration • Split workload of developing ETL processes for various data sets with Esri • Developed FME ETL processes for everything except parcel fabric • Esri tools for parcel data import
- 22. Example FME ETL Process ETL for SewerStormwater Feature Dataset
- 23. Planning the Infrastructure • All GIS servers are virtualized • (Microsoft Windows on VMware vSphere) • GIS group controls our own VMware cluster • Freedom to deploy virtual machines as needed • Separate testing/production environments • SQL Server enterprise Geodatabases • ArcGIS servers • Dedicated ArcGIS servers for Cityworks map services
- 24. ArcGIS Infrastructure – Initial Plan MS SQL Server 2012 Standard Edition “Default” Instance = Production “TESTING” Instance = Testing/Training Esri ArcGIS Server 10.3 Image services (tile caches) Esri ArcGIS Server 10.3 Production map services for web apps Esri ArcGIS Server 10.3 Production map services for Cityworks AMS MS SQL Server 2012 Developer Edition Runs on each Analyst’s workstation for Geodatabase development Esri ArcGIS Server 10.3 Map service development/testing Portal for ArcGIS Server 10.3 GIS Services Gateway
- 25. Web GIS – A Change In Plans • Originally planned to build web maps/apps using Esri tools • Portal for ArcGIS Server / ArcGIS Online • Web App Builder or JavaScript API • Compressed schedule called for a different approach
- 26. Geocortex Essentials • Provides a web map application interface in front of ArcGIS Server map/feature services • >80% of the user interface (UI) features we needed were available in the product • No custom code – just configuration through web administrator UI • Fantastic global search, including geocoder results • Responsive design for desktop/mobile/phone • HTML5/JavaScript viewer works with all modern browsers, no plugins (Flash/Silverlight) required
- 27. ArcGIS Infrastructure – Final Plan
- 28. 2015 2017Dec Feb Apr Jun Aug Oct Dec Feb Interim Data Migration 01/31/16 Begin Geocortex Testing 05/02/16 Final Data Migration 07/27/16 Cityworks Go Live (CSO) 09/26/16 Geocortex Go Live 10/06/16 Cityworks Go Live (Plant) 01/23/17 1/4/2016 - 5/2/2016Geocortex beta dev. 5/2/2016 - 6/3/2016Focused beta testing 6/3/2016 - 10/6/2016District-wide beta testing 7/27/2016 - 10/6/2016GIS Post-migration data cleanup 9/26/2016 - 11/30/2016CMMS Post-migration data cleanup GIS Implementation
- 29. Wrap Up… • The LGIM provided an industry-standard framework with many supporting maps and tools • We customized the LGIM to meet our specific needs
- 30. Thank You for Assistance and Support Esri Staff • Srinivas Suryanarayanaiah • Margaret Gregory • Michelle Johnson • Reginald Warren • Katja Krivoruchko • Suzanne Timani • David Wachal Central San Staff • Asset Management/GIS Team • Dana Lawson (Senior Engineer) • Carolyn Knight (GIS/CMMS Administrator) • Ian Morales (GIS Analyst) • Mike Matthews (Eng. Tech) • Managers • Jean-Marc Petit (Engineering Dept. Director) • Danea Gemmell (Planning & Development Services Div. Manager) • Special thanks to Central San Board President Tad Pilecki
- 31. Questions??? • Contact Information: Carl Von Stetten Email: cvonstetten@centralsan.org Web: http://centralsan.org Twitter: @cfvonner Slack: @cfvonner http://gisdevs.slack.com signup: http://bit.ly/1HxiNv1