Skip to content

Declaring Custom Profiles

The Tool supports standard CIM profiles, which are declared in StandardConfig.xml under \CIMSpy\config. The main reason for defining a custom profile is to support the CIM extension. Once a custom profile is defined, the extended models governed by this custom profile will behave just like standard CIM models. Users can edit the extended properties and run the validation against the custom profiles. This process is part of model personlization.

The following example defines a sample custom CIM profile:

Declaring Custom Profiles – figure 1

ProfileGroup defines the common attributes shared by each of the profile. The following attributes are defined:

  • name: name of the profile group.
  • customized: optional flag indicating whether the profile group is a customized version of CIM.
  • customCode: unique code used to identify the custom version of the profile group, required if m_customized is true.
  • baseProfileGroup: name of the base profile group, required when m_customCode is true.
  • cimTypeLocation: location where the cim type XSD is stored.
  • cimVersion: uri of the CIM version.

A ProfileGroup may contain multiple profiles, such as EQ, TP, or SV, etc. Each profile must defined the following attributes:

  • name: name of the profile.
  • location: location where the profile XSD is stored.

The custom profiles shall be declared in the CustomConfig.xml under \CIMSpy\config.

Need help? Contact cimspy_help@power-gem.com