1. © 2012 Autodesk Support Your Design Process with the AutoCAD Map3D Interface to WindMil Using MultiSpeak Frank Misurec Stephen Brockwell Brockwell IT Consulting

2. © 2012 Autodesk Class Summary In this class, you will learn how to enhance your design process by exporting designs created in AutoCAD Map3D software into WindMil circuit modeling software using the MultiSpeak interface. We will explain how to use the MultiSpeak export capability in AutoCAD Map 3D for both enterprise and file-based industry models. You will learn how to export AutoCAD Map3D electric industry models and how to configure the export to support customer-specific industry models.

3. © 2012 Autodesk Learning Objectives At the end of this class, you will be able to:  Explain the key concepts of the MultiSpeak standard  Export a feeder(s) from Map3D  Import a feeder(s) into WindMil  Configure your Industry Model to export your data  Create a MultiSpeak configuration file for your Industry Model  Install the MultiSpeak plug-in for Map3D

4. © 2012 Autodesk Overview - MultiSpeak ® Version 3.0

5. © 2012 Autodesk What is MultiSpeak ® ? “The MultiSpeak Initiative is a collaborative effort between the National Rural Electric Cooperative Association and software vendors serving the electric utility industry. Its purpose is to define standard data interfaces to help make available cost-effective, integrated software applications to serve the business needs of small electric utilities, such as rural electric cooperatives.” MultiSpeak ® Version 3.0 Specification

6. © 2012 Autodesk MultiSpeak ® Features  Standard interfaces – application independent  Supports batch transfers and web services  Interfaces between: Customer Information Systems (CIS), Geographic Information Systems (GIS), Engineering Analysis (EA), Integrated Voice Response (IVR), Staking, Supervisory Control and Data Access (SCADA), Automated Meter Reading (AMR), Load Management, Outage Management, Customer Relationship Management (CRM)

7. © 2012 Autodesk MultiSpeak Objects

8. © 2012 Autodesk MultiSpeak ® Interface: Features

9. © 2012 Autodesk MultiSpeak ® Interface: Features  Enterprise and File Based Industry Models  Industry Model Independent  Configured “out of the box” for NA Electric Model  Configurable for any data model  Supports “tight” integration with WindMil  Batch transfer  Validation

10. © 2012 Autodesk MultiSpeak ® Map3D User Interface

11. © 2012 Autodesk MultiSpeak Map3D User Interface  Is a Map3D Document Plug In Invoke Multispeak

12. © 2012 Autodesk MultiSpeak Map3D User Interface  Configuration File  Substation  Feeder  Output File  Log File

13. © 2012 Autodesk MultiSpeak Map3D Interface – Configuration File  Configuration File – XML  Defines Industry model to MultiSpeak object mappings  Defines Substation to Feeder mappings  MultiSpeakAutodeskConfig.xsd

14. © 2012 Autodesk MultiSpeak Map3D Interface – Substation  Choose Substation  Configuration file element msFeederList

15. © 2012 Autodesk MultiSpeak Map3D Interface – Feeder  Feeder(s) available to Export  Configuration file element msFeederList

16. © 2012 Autodesk MultiSpeak Map3D Interface – Export  Select Feeder(s)  Specify Output and Log File  Export

17. © 2012 Autodesk MultiSpeak Map3D Interface – Validation  Incorrect MultiSpeak Element Name  Incorrect Industry Model Table/Column Name

18. © 2012 Autodesk MultiSpeak Map3D Interface – Import to WindMil 1. WindMil File->Import 2. Choose Version

19. © 2012 Autodesk MultiSpeak Map3D Interface – Import to WindMil  Choose options  Can use sectionId to define name  Complete

20. © 2012 Autodesk MultiSpeak ® Interface Configuration

21. © 2012 Autodesk MultiSpeak ® Interface Configuration  Configuration File – XML  Defines Substation to Feeder mappings  Defines Industry model to MultiSpeak object mappings  MultiSpeakAutodeskConfig.xsd

22. © 2012 Autodesk MultiSpeak ® Interface Configuration  msConnectivity  msFeederList  msPartnerList  msElementList

23. © 2012 Autodesk Configuration - Connectivity  msConnectivity – utility model connectivity  Name – table/view name  fromId – Id of from section  fromClassId – Class Id of from section  toId – Id of to section  toClassId – Class Id of to section  Overrideable at the Element level

24. © 2012 Autodesk Configuration – Feeder List  msFeederList – required for user interface  Name – table/view name  Substation – Column identifies substation  Feeder  Column identifies feeder  msElement default feeder column

25. © 2012 Autodesk Configuration – Partner List  msPartnerList – Industry Model classes that are switches  Name – class name

26. © 2012 Autodesk Configuration – msElementList  msElementList – list of MultiSpeak data objects (msElement)  msElement – Defines mapping to MultiSpeak data object

27. © 2012 Autodesk Configuration – msElement  msElement  Attributes  msGeometryProperty  msChildElement  msElementList

28. © 2012 Autodesk Configuration – msElement Attributes  msElement Attributes  name – MultiSpeak Data Object name  source – Industry Model table/view  requiresParent – child element  parseBy – auto generate child list  feeder – overrides msFeederList  sectionId – use to define object name  parentSection – overrides msConectivity

29. © 2012 Autodesk Configuration – msElement Properties  msGeometryProperty – Geometry Mapping  name – MultiSpeak geometry  source – Industry Model geometry

30. © 2012 Autodesk Configuration – msElement Properties  msProperty – MultiSpeak/IM property mappings  name – MultiSpeak property name  source – Industry Model column name  autoGenerate – Generate value of “ParseBy”  Value – Sets property to a literal

31. © 2012 Autodesk Configuration – msElement Properties  msProperty – MultiSpeak/IM property mappings  name – MultiSpeak property name  source – Industry Model column name  autoGenerate – Generate value of “ParseBy”  Value – Sets property to a literal  Source/Value must match MultiSpeak type  Ie. phaseCode must be: A, B, C, AB, AC, BC, ABC

32. © 2012 Autodesk Configuration – msElement ChildElements  Child Elements  Explicit – msChildElement  Implicit - msElementList

33. © 2012 Autodesk Configuration – msElement msChildElement  msChildElement  name – MultiSpeak property  parentKey – key column in current element  childKey – key column in child  childName - child element name

34. © 2012 Autodesk Configuration – msElement msElementList  msElementList  name – MultiSpeak property

35. © 2012 Autodesk MultiSpeak ® Industry Model Configuration

36. © 2012 Autodesk Industry Model Configuration – Why?  MultiSpeak Data object properties may not be contained in one Industry Model Feature Class  Industry Model Domain tables  Industry Model Property transformations may be required

37. © 2012 Autodesk Industry Model Configuration – How?  Create a view to represent MultiSpeak data object  msElement “source” attribute is table/view name  Examples  V_MSPK_CIRCUIT_LIST – properties required from multiple tables  V_MSPK_EL_SWITCH  Get phase values from domain table  Perform data transformation on “state” to map to MultiSpeak values

38. © 2012 Autodesk Autodesk, AutoCAD* [*if/when mentioned in the pertinent material, followed by an alphabetical list of all other trademarks mentioned in the material] are registered trademarks or trademarks 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. © 2012 Autodesk, Inc. All rights reserved.