Schema mapping in Smart Electrical has some important rules and limitations.
Rules for Mapping Documents and SmartPlant Foundation Revisions
In Smart Electrical, a document object has various properties but only the document type property is mapped to a document category enumeration list in the SmartPlant schema. A list of Smart Electrical documents that can be published and retrieved is defined in the SmartPlant schema and can be viewed in the Schema Editor.
Also, SmartPlant Adapter for Smart Electrical supports mapping of SmartPlant Foundation revisions. Whenever a Smart Electrical user creates a new revision, the SmartPlant Client calls a common dialog in which the user defines the revision schema and the revision number, this number is saved in SmartPlant Foundation and SmartPlant Foundation returns this number to Smart Electrical via the adapter.
Rules for Property Naming
The names of the properties in the Smart Electrical tool schema must exactly match the names of the properties in the Smart Electrical data model, including the case.
Limitations of the SmartPlant Schema
The retrieve map is updated directly from the contents defined in the SmartPlant schema; therefore, the following restriction on the SmartPlant schema exists: in rare cases, if an entry is removed from the SmartPlant schema, you may need to edit the retrieve map file to remove the deleted entry. You should use the Schema Editor delivered with the SmartPlant Schema Component for this purpose.
Map File Location and Definition Restrictions
By default, the SPELMap.xml is installed in the Smart Electrical home folder. You can change the map file location in the SmartPlant resource path box in the Locations window of the Options Manager utility.
Although, using the Schema Editor, it is possible to change the content of the map file, the file name must remain SPELMap.xml.
Equipment Inheritance Mapping Restrictions
Currently, Smart Electrical equipment inheritance is not implemented in the tool schema. This is a subject of future development. You have to map properties of equipment manually. Because there is no equipment inheritance, mapping is only performed on the level of a concrete (tangible) object class. To define relationships between various object classes, interfaces in the tool schema are used. Interfaces in the tool schema do not contain properties.