1. Join us on Twitter: #AU2013 GS1583-R: One Year Later: Migrating to Autodesk AutoCAD Map 3D Enterprise Electric Andy Morsell, P.E. Technical Consultant – Autodesk Global Services Utilities and Telecom John Keith CAD/GIS Supervisor – Independence Power & Light

2. At AU 2012, Andy Morsell of Autodesk Consulting and John Keith of Independence Power and Light (IPL) in Independence, Missouri, presented a class about migrating a medium-sized municipal electric utility to Autodesk AutoCAD Map 3D Enterprise Electric while the project was still underway. Here we are 1 year later! This year the completed application is in production use. Our roundtable session discusses the challenges we faced when interfacing with other systems and integrating with processes and workflows employed at IPL. We will discuss the custom Autodesk® Infrastructure Map Server and Autodesk Consulting Mobile Viewer applications deployed at IPL. Interfaces include a service for receiving updates from their custom information system and interfaces to legacy systems that need to remain functional while they are being replaced. We will also discuss MultiSpeak® exports to IPL's Milsoft DisSPatch® outage management system. Introductions and Class summary

3. At the end of this class, you will be able to:  List the business needs driving migration needs  Identify potential business areas where project problems might arise  Describe challenges you might encounter when interfacing with other systems  Identify challenges faced during production rollout of a new application Key learning objectives

4. Independence Power & Light Project Background – A very quick overview

5. IPL Project Background – Former System Architecture

6. IPL Project Background – New System Architecture Replaced the old mapping system with Autodesk Map 3D Enterprise and also replaced most other pertinent systems. This option utilizes as many Commercial Off The Shelf (COTS) products as possible and utilizes the Oracle database as the primary “Single Point of Truth” for all data with little or no data duplication between systems.

7. Roundtable

8.  We will discuss only five, well-defined topics. We have about 10 minutes per topic.  We are the facilitators of this roundtable, not class presenters or instructors  Everyone has a fair and equal opportunity to speak  We want to establish a “seek to understand” atmosphere  We want to spark debate and acknowledge many points of view  We want to establish an in depth understanding of topics  We are recording this discussion and will be preparing a “Summary Brief” of the outcomes and key takeaways generated around the topics. This document will be available on the AU web site by December 15th Roundtable Format and Ground Rules

9.  Conversation starter: How we did this project. The Waterfall Method.  Pilot Project  Gap Analysis  Full Requirements documentation  Migration Specifications development and documentation  Migration script creation  Interface development  Deploy to test servers for User Acceptance Testing and fixes  Final deployment, documentation and training  Ongoing adhoc support  How have others have done projects like this?  What worked and did not work with your projects?  What would you do differently next time? Topic 1 – Project Structure

10.  Conversation Starter: How the consultant relationship worked on this project.  Autodesk Consulting was the primary consultant  Brockwell IT Consulting as a sub-contractor to Autodesk Consulting for some tasks  Brockwell IT is also IPL’s Autodesk Reseller  What have your experiences been with consultants and their sub-contractors?  We find that frequent task reviews ensure that all parties are doing what they should be when they should be doing it and that all expectations are on the same page. What is the right frequency for these meetings? What is the best way to meet? Ultimately strive to work as a complete team. We all have the same goal – PROJECT SUCCESS! Topic 2 – Working with Consultants and Sub- Contractors

11.  Conversation starters: What we found on this project  Two types of external and internal task ownership: Project management and technical.  Cannot assume that things are being followed up with. Be a proactive leader, not reactive.  It is possible to have too many “cooks in the kitchen”. Be sure that “single point of contact” leadership is clearly defined at all project levels.  How do you establish leadership on your projects?  How do you want your consultants to establish their leadership?  What specific issues have you encountered on this topic in your projects? Topic 3 – Establishing Leadership and Task Ownership

12.  Conversation starters: What we found on this project  A very formal acceptance process is key to delivery success  User Acceptance Testing  Formal test cases need to be developed. Mostly a client activity.  A single point of contact from the client is useful.  A formal test management system to log defects is critical.  End-user project acceptance must be considered by the UAT testers.  What has worked for you when testing and accepting projects? What hasn’t worked? Topic 4 – Acceptance of Project

13.  Conversation starters: What we found on this project  Managing project scope is important for all parties.  Addressing and prioritizing wish list items that have come up during the project.  Addressing enhancement or productivity items that have come up.  Follow-up Ad-hoc support might be valuable.  How do you handle end-user wishlist and enhancement items within your organization?  Do you contract out for ad-hoc support?  Final thoughts ? Topic 5 – After the Implementation

14. Autodesk is a registered trademark of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. © 2013 Autodesk, Inc. All rights reserved. Questions? Please contact either of us. Andy Morsell – andy.morsell@autodesk.comandy.morsell@autodesk.com John Keith - JKeith@indepmo.org- JKeith@indepmo.org