Smart Instrumentation Database Structure - Intergraph Smart Instrumentation - Help

Intergraph Smart Instrumentation Help

Language
English
Product
Intergraph Smart Instrumentation
Search by Category
Help
Smart Instrumentation Version
13.1

The following discussion is a very broad explanation of the internal structure of the Smart Instrumentation database. It is not meant to be a database primer, but rather an aid for the user to have a better understanding of what tables to select when customizing a report in InfoMaker.

Two of the important features of the Smart Instrumentation database are its hierarchical and relational structure.

Hierarchical Structure of the Database

The Smart Instrumentation database consists of a hierarchy, where each level of the hierarchy contains tables that are specific to that level. The highest level of the hierarchy is the Admin schema. On the next level of the hierarchy, there is a Domain schema for each domain you initialize in the database. Schemas include tables. Tables include table columns, which are represented in the interface as data fields.

Within each domain, there are plant hierarchy levels. By default, each domain has three default levels as follows: <plant>, <area>, and <unit>. The following table shows most common types of data you can define at each level of the hierarchy:

Level

Table Data Included

Notes

Admin schema

Users, user groups, naming conventions, access rights

Domain schema

instrument types and other supporting tables, spec forms, reference wiring data

<Plant>

Wiring data, custom fields

<Area>

None

Used as a container only

<Unit>

Loops, instruments

The software checks uniqueness at the <unit> level

There is a connection between the data settings at each level of the plant hierarchy, for example, an instrument tag includes data from various tables at the following levels:

  • COMPONENT table (contains instruments) at the <unit> level

  • Supporting tables at the domain level

  • PD_GENERAL table (contains process functions, such as pressure, flow, temperature, and so forth) at the <unit> level

  • SPEC_SHEET_DATA table (contains specification data) at the <unit> level

The schema name always appears prefixed to the table name separated by a period (.). For example, if your Domain schema logon name is DEMO, and in InfoMaker you select CABLE as your table name, the table name in InfoMaker appears are DEMO.CABLE. For details of database schemas and their descriptions, see Smart Instrumentation Database Structure and Schemas in the Internal Setup Utility help.

Relational Structure of the Database

The relational structure of the database is concerned with the associations defined between tables and columns. For example, if you want to create a customized cable report that includes only the cable description, color, manufacturer, and model, you need to know that these are columns that are associated with their respective tables. The following is a summary for this example.

Full Table Name

Table Description

Table Column Name

Display Name

DEMO.CABLE

Information stored about the existence of a cable

cable_desc

Cable Description

DEMO.CABLE_COLOR

The list of colors available for all cables

cable_color_name

Cable Color

DEMO.CABLE_MFR

The data structure for a list of cable manufacturers

cable_mfr_name

Cable Manufacturer

DEMO.CABLE_MFR_MOD

The model of the cable

cable_mod_name

Cable Model