SmartPlant Master Tag Registry is delivered with a default schema that supports a pre-defined set of handover registers (HRs). But you will likely want to customize the default set of properties associated with the supported registers.
The topics in this section illustrate how to model a custom property (Status) used on the Instrument Handover Register. This process involves modeling the property definition and the enumerated list (red, yellow, and green) it uses in the authoring, publishing, and consolidated data warehouse (CDW) schemas.
-
The following procedures show one way to implement a new property and create all the necessary relationships, but there are other approaches that you might take. For more information on using the SmartPlant Schema Editor, see SmartPlant Schema Editor Overview.
-
In the following example, the word Acme is used to represent the name of the fictional company performing this example. When Acme is used in the name of a file or schema object, it is used to represent a custom version of that object.
-
Before you begin this process, choose a location in which to store custom schema files that you will create. These files should not be stored in the same location as the delivered schema files, but should be placed in a location that is available to all users who will be using this process and that is backed up regularly. Throughout this example, this location will be referred to as your customization folder.
The following graphic illustrates the modeling required in this example.
The following work process diagram illustrates the primary tasks involved in this process:
What do you want to do?
-
Add the customizations to the SmartPlant Master Tag Registry tool map file
-
Load non-integration schema customizations into the database
Once you have extended the schema to include the new property, you will need to add
the new property to your register.