Geodatabase configuration

GeoAdministrator links records in the Infor Operations and Regulations database to records in the ArcMap geodatabase. An address, for example, is represented by a record in each database. The geodatabase stores geographic information for the address. The address record in the Infor Operations and Regulations database stores legal and administrative information, and links to other records such as assets and service requests.

To link the address records in the two databases, you must add an ADDRKEY column to the GIS address table. The ADDRKEY column in the Infor Operations and Regulations ADDRESS table stores keys that uniquely identify each address record. You can link the address records in the two databases by adding the same keys to the GIS table.

Other types of records require you to add additional columns. Parcels require two columns: PRCLKEY and PRCLID (parcel ID). After these fields are added to the GIS parcel table, you can use them to link parcel records in the two databases.

Note: Although parcel records in the two databases could be linked based on the PRCLKEY alone, the additional columns provide better data synchronization. The QAQC process in GeoAdministrator can compare records based on more than their key values. For example, the QAQC process can identify records whose keys have changed as long as the other primary fields match. It can also identify cases in which the keys do match, but values in the other primary fields don’t. These cases are referred to as bad data.

This same note also applies to the required columns for the Infor Operations and Regulations asset tables.

Assets can require up to seven additional columns, depending on the asset type. At a minimum, a point asset such as a manhole or a street sign requires three columns: COMPKEY, COMPTYPE, and UNITID. The COMPKEY is the primary key, the COMPTYPE is a numeric code indicating the type of asset (such as 12 for a hydrant asset), and the UNITID is the name or identification code that the user assigns to the asset when it is created.

Note: COMP is an abbreviation of “component.” Because assets were called components in previous versions of the Hansen/Infor Operations and Regulations software, the table names still use the abbreviation COMP. Note also that each COMPKEY is stored in two different tables in the Infor Operations and Regulations database. The central COMP table stores keys for all asset records, and each asset type has an individual table. For example, COMPSMN is used for sewer mains, COMPWMTR for water meters, COMPVEH for vehicles, and so on.

Mainline assets, such as sewer or water mains, require additional columns. A main in Infor Operations and Regulations is identified as the stretch of pipe between two other assets, such as two manholes. Thus, in addition to the COMPKEY and COMPTYPE, the table for a main requires columns for the COMPTYPE and UNITID of each endpoint.

Other asset types, such as street segments and roadways, also require additional columns. The required columns for each type of record are listed in the tables below.