Download to read offline
Uploaded bySSP Innovations
Learning Lessons the Hard Way: A Large Utility’s Experience Upgrading from ArcGIS 9 to 10
NiSource, a large utility company, upgraded their GIS system from ArcGIS 9.2 to 10 over a multi-year process. They identified key stakeholders, established a project team, and thoroughly tested all functions and business processes. The migration involved upgrading servers, data, and custom code while minimizing customizations. Testing uncovered issues that were resolved. Training emphasized differences between versions. Despite challenges, the overall process provided input, buy-in, and allowed them to successfully deploy the new system after celebrating accomplishments along the way.
More Related Content
Similar to Learning Lessons the Hard Way: A Large Utility’s Experience Upgrading from ArcGIS 9 to 10
More from SSP Innovations
Learning Lessons the Hard Way: A Large Utility’s Experience Upgrading from ArcGIS 9 to 10
- 1. Learning Lessons the HardWay: A Large Utility’s Experience Upgrading from 9 to 10 Terry Iffland Project Specialist, NiSource Matthew Stuart Project Manager, SSP Innovations Esri Electric and Gas User Group October 28, 2014
- 2. NiSource NiSource Gas Distribution •3.3 million gas customers • ~ 60,000 miles of pipeline NiSource Electric Operations • 470,000 electric customers Columbia Pipeline • ~15,000 miles of pipe in 20 states
- 3. SSP Innovations Ten-yearold GIS and operations consulting company Team of 19 based in the Denver area Work exclusively in the U.S. utility/telecom industries 100% of our work is performed at utilities that have Esri and Schneider Electric based GIS departments Began as a services company – now perform services and offer a line of software products
- 4. What and Why? Application • Using ArcGIS 9.2 – non-supported version • ArcFM 9.2 • 220 customized code functions Environment • Development, Test, Training, and Production Environments • Six SDE instances for each environment • Age and condition of hardware – replace 7 year old equipment • Upgrade server environment from Oracle 10g to Oracle 11g • Upgrade Citrix servers – hardware and Citrix version
- 5. Getting Started Identifykey stakeholders • This is beyond executive sponsors • Periodically review membership • Key stakeholders influence implementation Establish the project team • Project manager • Business analyst • Testers • Trainers • Technical experts & technical support • Corporate
- 6. One Call Buffers AutoCad Designs (Cad Exports) StreetLight Outage Reporting NORS Network Express Maximo CIS Detailed Images Opvantek (Vendor for Optimain) NIPSCO Service Cards (Legacy Cards) Open Text SynerGee CYME GIS Web Feederall ArcReader Mobile Client (Redliner) NGD WMS Data Warehouse OptiMain Placement Tool ESRI Online Services (e.g., Address Locators, Imagery) Ventyx (ArcEngine Compatability requirement creates version dependency)IRTH RouteSmart CITRIX – interface used to access GIS application ENVISTA Getting Started GIS Capital Work Area Update Gas Pressure System Laurel Hill QA/QC D Line Information CTR Tool EAIF Customer Connection Batch Interface Revised: 3/19/2015 Identify System Interfaces
- 7. Testing Make sureto have enough time for user acceptance testing Tests describe steps and expected results Detailed documentation for failed tests Retain test scripts Step 1 Log into ArcFM with a user ID that does not have the authorization to create system stored displays. Log into ArcFM Step 2 Do not open a session Blank map opened. Step 3 Add the data to your TOC that you want to work with Selected features on display Step 4 Set up the symbology that you want Symbology used Step 5 Build and turn on labels Symbology viewed Step 6 Group the Table of Contents (TOC) TOC organized Step 7 Pan and zoom to create a screen area to save as a stored display View reflects proper zoom and view Step 8 Select Stored Display Will get a dialog to save system stored display Step 9 Set Type to System so that others can use it. Display type is System Step 10 Click on Save Error message that user is not authorized to create a system stored display Step 11 Log out of ArcFM. Logged out.
- 8. Testing Test individualfunctions Business process testing in addition to functional testing Include batch processes (non-human factor) Test in the environment in which the users will operate Going live with unresolved defects
- 9. Migration You donot need to be at State 0! If you are on 9.2 to go to 10.x, you must first upgrade to 9.3 Minimize customizations Migration of data is impacted by the number of versions, sessions, and user documents
- 10. Migration Dry runfor data loads. • Comprehensive cut over plan • Know who is expected to do what and when Validation • Data comparisons • Feature counts Go/no-go meetings • In the end it provided good input • Also provided overall buy in • Stakeholders need to participate
- 11. Other Advice Esri’sVisual Basic Extension Required for ArcFM 10.1 • Obtained via Esri customer support Issue migrating user stored displays having joins and relates • Join points to the table in the SDE database from which migration is occurring • Repair joins to point to the table in the newer SDE database • Best solution is to reload the system stored display while in the session and save the session
- 12. Other Advice GeodatabaseManager (GDBM) • Monitor the queue initially • Consider prioritizing queue processes Esri QIP • The Esri QIP made a HUGE difference for us • Largest noticeable impact to version differences Esri templates • Some of our edit processes use the old editor template • Turning it off helped with performance
- 13. Deployment Training • Structuredwith the assumption that users already had experience with the 9.2 application • Content emphasized the differences between the current version and new version Avoid the holidays! • We planned to go live at the beginning of December. • Schedule changes pushed us into mid-January
- 14.
- 15.
Editor's Notes
- #5 220 customized code functions Re-evaluate customizations for commercial-off-the-shelf (COTS) based workflows Citrix sw 6.5
- #6 Review Key stakeholder members Organizations change Determine if members need to be added or removed Key stakeholders can stop your implementation Capital risk tool needed to be upgraded to be compatible with ArcMap 10.1 In August we were told they’d be ready for a December go live In September they thought they’d be ready for a December go live In October, things were doubtful, but the project team said we could go live without them In mid-November the stakeholder representing the group said we couldn’t upgrade to 10.1 if the capital risk project wasn’t ready Pushed deployment to January Along that same line, stakeholders can help you avoid problems We had discussed migrating Jan 10 (Thur) – Jan 13 (Sun) Stakeholders made us aware of a review with the state commission scheduled on Jan 11 that included a discussion of our GIS Having them involved with our planning helped us to avoid a potentially embarassing situation Deployment was moved to Jan 17-20 Testers Including actual end users can be helpful End users may not always do things the way you think everyone is doing something Will you need trainers? Are they some of the same people doing your testing? If not, can consider using them
- #7 Identify and keep system interfaces updates (notice revisions in lower right corner) Systems used to update / augment GIS data Integrated systems Systems used to view GIS data Systems extracting / consuming GIS data Support systems Future direction / plans Other constraints
- #8 User testing – anticipate pressure to execute faster, pass tests, accept test results, short circuit retest process Test Scripts NiSource uses HP’s Application Lifecycle Manager (ALM), but previously we used Excel spreadsheets. this is an example used to test ability/inability to save a system stored display. Be specific. Do not assume that someone knows how it is supposed to work If you have subtypes, tests should be written and conducted for each subtype Test Results Screen shots are important for when a test fails Test failures need to have specific details to help recreate the issue (including things like database, feature, and object id). Developers need to be able to recreate the problem. Retain test scripts Useful for future system changes
- #9 Test in environment where users will operate Ensures proper configuration Good measure of expected application’s performance Go live with unresolved defects Determine magnitude of defect’s impact Number of times it occurs Number of times functionality is used (hourly, daily, weekly, monthly, annually?) Try to find a work around Make sure stakeholder group is informed
- #11 Dry Run – things to schedule DBAs’ copy - when starts and how long it takes. Will need to have exclusive DB access. Establishes an expectation of how long tasks will take Clarifies what is supposed to be done for each step, by whom and when Iron out any issues you may not have identified during planning Feature Counts 100% of critical features Random sample of others if don’t have time to check all the features
- #12 Esri templates – show where this is turned off?
- #14 Training – timing the training, train the trainer, some of persons testing were part of training which put pressure on both activities
- #15 We determined there is a direct correlation between success and the number of blue shirts in the room!