ArcFM Desktop Developer Guide
XSL Style Sheet
The MultiSpeak Vendor API expects the the MultiSpeak data model format. If your data model is not in this format, the XML sent to the Vendor API must be modified in the Implementation component to look like the ArcGIS Electric Distribution data model.
Interfaces:
IMMMessageCallbackCoClasses:
MMSelectionAnalysisAPISupported Attributes:
MultiSpeak
All table names, field names, relationships, and domain values must reflect the Minerville standard. The Supported Attributes table in each Vendor API section shows facility attributes that are supported by the Vendor API. If a customer’s geodatabase does not contain one of these attributes, the Implementation component can add the attribute to the XML node for the feature.
If the attribute is not exported from the geodatabase or provided by the Implementation, the Vendor API will use the default values shown in the Supported Attributes table. However, the attributes with names in bold must be included in the XML for the Vendor API to correctly load data.
The Implementation can include default values by appending a DEFAULTS node to the XML export, containing nodes for each table requiring default values. Default values can be included for load attributes as well.
The Implementation component is a self-contained application that does not provide interfaces to outside components. The sample projects installed with the SDK each contain a toolbar implementation that uses various command button implementations.
One command button opens the export object, which references MMSelectionAnalysisAPI to export XML data from the geodatabase. The code within the object then transforms the XML to a format acceptable to the Vendor API. This transformation includes adding equipment IDs to features and adding default attributes. When the transformation is complete, the export object references the Vendor API to load the XML to the analysis engine.
There are two methods to transform XML received from the Analysis API. You may create an XSL style sheet or write custom code that converts table names and attributes to match the format required by the Vendor API.
The Implementation component notifies the user of any errors that occurred during an export. The errors can be displayed on the screen, saved to a file, or both. The export object implements IMMMessageCallback to listen for status messages and progress information from the Vendor API. This way, the Implementation controls the output of all messages to the user. The Implementation also listens for progress information from the Analysis API during the export.
Load Cases (classic implementations only): Because load cases are imported into a table into the Network Adapter database during the Analysis API, an XSL to convert the load data is not necessary. The data in the Network Adapter table is in the correct format.
MultiSpeak Users: You may change the location and name of your import and export XSL style sheets by modifying keys in the registry. Network Adapter looks in two places (in the order shown below) for each style sheet. To modify the path or name, change the registry key. Remember that if you change the #2 registry key, #1 must be empty, otherwise Network Adapter will use the first one.
Depending on your setup, there are two XSL and two DTD files to configure:
| Windmil - Standard Electric Distribution Data Model | Purpose |
| NetAdapterElecDistToMsp_Windmil.xsl | This is the stylesheet that makes the transformation. This is the file that should be configured in the XSL Transformation Pipeline rule. |
| NetAdapterElecDistToMsp_DMSEquipment.xsl | Equipment Stylesheet. This generates equipment IDs based on some key attributes in the feature database. |
| NetAdapterElecDistToMspFields.dtd | This DTD defines field names. |
| NetAdapterElecDistToMsp.dtd | This DTD defines class names, relationships, subtype codes, and int. |
| Windmil - Multispeak Electric Distribution Data | Purpose |
| NetAdapterMspEAExport.xsl | This is the stylesheet that makes the transformation. This is the file that should be configured in the XSL Transformation Pipeline rule. |
| NetAdapterMspEAExport_Equipment.xsl | Equipment Stylesheet. This generates equipment IDs based on some key attributes in the feature database. |
| NetAdapterMspEAExportFields.dtd | This DTD defines field names. |
| NetAdapterMspEAExport.dtd | This DTD defines class names, relationships, subtype codes, and int. |
Samples
