230 likes | 342 Views
The Fellowship of Asset Management. By: Mike Morris and Rick Ehlin. 2009 Utility Work Flow. Noblesville GIS. Cityworks. GIS- centric Asset Management System Built specifically for ESRI ArcGIS Service Requests Work Orders Inspection Projects. Two Flavors. Server.
E N D
The Fellowship of Asset Management By: Mike Morris and Rick Ehlin
Cityworks GIS- centric Asset Management System Built specifically for ESRI ArcGIS Service Requests Work Orders Inspection Projects
Two Flavors Server Requires ArcServer license Only need intranet access Initial Cost is high Software Maintenance on one computer Great for multiple users Desktop • Requires at least an ArcEngine license • Must be installed on every computer • Initial Cost is low • Software Maintenance on every computer • Only 35 users for the Utility
Woolpert Local Lead the Nation in Implementations Familiar Staff
Steps to implementation Decide what Assets (features) were going to be used Place all Assets in one file geodatabase Add “non-feature” assets to file geodatabase Related those “non-feature” assets to feature assets Create an AssetID field for every feature
Steps- continued Create Work Orders Create Service Requests Create Inspections Employee List with security Material List Equipment List
Almost There GIS installed either ArcEngine or ArcView plus Cityworks Desktop on each computer Trained supervisors on Cityworks and Administration Lastly- trained all Operators Go Live- Fall of 2009 (6 to 9 months)
Streets 17 Users Unlimited Cityworks Desktop licenses 7 Concurrent ArcView licenses GIS haves- Centerlines, street lights and some trees GIS have nots- sign posts, rest of trees, cemetery, sidewalks and maintenance buildings
Parks 8 Users Unlimited Cityworks Desktop Licenses 7 Concurrent ArcView licenses GIS haves- park boundary and trails GIS have nots- park activity areas, park structures (grills, water fountains, etc), park buildings Golf- no GIS at all
Cityworks Recap for Departments • Utilities • Go live 2009 • 35 users • 15 ArcEngine (Computer Specific) and 7 ArcView Concurrent • Streets • Go live 2011 • 17 users • 7 ArcView Concurrent • Parks • Go live 2011 (Limited) • 8 users • 7 ArcView Concurrent • Future? PROBLEM?
Solution • Initially looked to County to host map services • ArcGIS Server Standard Workgroup • File Geodatabase • Virtual server
ArcGIS Server Standard Workgroup • Benefits • Lower costs • Purchase • Maintenance • Functionality • Limitations • 10 simultaneous multi-user geodatabase connections • 10 GB storage capacity • Single-server installation only for up to 4 cores
File Geodatabase • Supports existing editing processes • No additional administration • ArcSDE tuning • ArcSDE administration • DBMS tuning • No practical size limit
Migration to Server Decision made in 2011 Work began early 2012 Cityworks Server 2012 SP1 in test environment on April 23 Went live July 9
Problems or what we would do different • Problems • Reporting is difficult • Runs on Silverlight • Done different • Visit another Cityworks site • Stayed on one Domain
Future • Bring more departments on (Engineering) • Fine tune the inspection and print templates • GO MOBILE