Import Data to MultiSpeak

The next step in the data flow is to import the GIS data into MultiSpeak for analysis using the Vendor API component MMMultiSpeakEAAPI (the MultiSpeak API). The MultiSpeak API accepts the transformed XML that was exported by the Analysis API. Once this data is imported into your MultiSpeak analysis engine, you may perform engineering analysis.

Interfaces:
IMMXMLData

If your data model conforms to the Schneider Electric MultiSpeak data model, the sample implementation component provided with Network Adapter can be used as it is. If the data model has been customized, then the classes and fields in the geodatabase that do not match the Schneider Electric MultiSpeak data model must be mapped to their corresponding objects and attributes in the MultiSpeak standard. The best way to accomplish this is to use a custom style sheet in addition to the style sheet provided with Network Adapter (NetAdapterMspEAExport.xsl). NetAdapterMspEAExport.xsl is installed in the Bin\Style Sheets folder of the ArcFM Solution installation directory. The MultiSpeak API component applies this style sheet to the exported XML.

This could be used as a starting point for a project to create its own style sheet to transform non-standard tables and fields to the MultiSpeak standard. The MultiSpeak Engineering Analysis sample implementation can be modified to call a custom style sheet before NetAdapterMspEAExport.xsl is called. It is recommended that projects do not completely replace NetAdapterMspEAExport.xsl in order to remain compatible with future releases.

The MultiSpeak API component also implements IMMXMLData. In this case, the IMMXMLData::ImportDataFromDOM method is used to create the final MultiSpeak compliant XML document which is saved to a file. MultiSpeak API transforms the XML document passed in to IMMXMLData::ImportDataFromDOM with an XSL style sheet (NetAdapterMspEAExport.xsl).

Importing Results and Table Names

When importing results data into MultiSpeak, the tables created in NetworkAdapter.mdb are named according to the database to which you're logged in.

Logged into the export database: The tables are named after the feature classes from which they were exported (e.g., LoadFlow_DynamicProtectiveDeviceBank).
Not logged into the export database: The tables are named after the element names in the MultiSpeak schema (e.g., LoadFlow_OvercurrentDeviceBank).