“Special” InfoMaster Fields

One of the best features in InfoMaster is its flexibility in terms of leveraging GIS data and the ArcGIS data structure.  95% of the time, clients can apply data fields in whatever way they specify.  However, there are some fields InfoMaster looks at specifically for specific functions.  These are the 5%.  Below are brief descriptions of these ‘special’ fields.

‘Special’ Facility Fields

These fields are System Fields from the InfoMaster Facility Data Import or Facility and Asset Type Manager windows.  These fields directly relate to the clients Facility Types.

Special fields include:

Install Date – It is important to map to this System field so that the users Baseline Replacement Costs and Failure and Deterioration tools work properly.  This field is important in the LCCA extension as well.  Install Date is required for determining pipe age in these tools.

Material – Again this field is important to the Baseline Replacement Costs and Failure modeling tools as well.  Material is often an important variable in cohort analyses.

Pipe Length – This field appears in the Condition Assessment window for pipes and can override the GIS shape length if mapped correctly.  If left Null or not mapped, the shape length will be taken as the official pipe length.

To/From Structure IDs – Used to map CCTV inspection data to pipes and geocode defects.  Pipes don’t have to be snapped to end nodes, but should have correct To/From Structure IDs to help map CCTV inspection data.  If CCTV inspection data can’t be mapped to pipes via these fields, InfoMaster will try matching Pipe Segment Reference (another ‘special’ field; this one is in the PACP import window) in the CCTV inspection data to the Facility ID for Gravity Mains.  Make sure to import to this field when bringing in CCTV data if you want to match inspections to pipes in this way.

Zone – this is by no means a necessary field, but if you ever want to run risk analyses, failure analyses, rehab plans, etc. by zone, you must populate and map this field in order to do so.  All unique values in this field can be chosen in the dropdown where applicable.

Depth – again this is not a necessary field, but if it is left unpopulated, InfoMaster will try to calculate pipe depth based on the average of Upstream Invert and Downstream Invert.  These are also related ‘special’ fields because of this default calculation.  Users will see this calculation occur if they try to use the Depth option in the Consequence/Likelihood of Failure Wizard without populating that field.  A similar calculation will occur for Slope if it is left unpopulated.  This slope calculation will incorporate Upstream/Downstream Invert values as well as Pipe Length.

‘Special’ CCTV Import Fields

These fields can be found when importing CCTV.  Again, these fields are listed as System Fields.  While the required fields are highlighted red, there are a number of fields which are highly recommended.


Source ID – because InfoMaster generates a new, reindexed Inspection ID on the fly based on the required Inspection table fields, the original Inspection ID will not tie back from the InfoMaster database to the original CCTV database.  The Source ID field can be used to tie the original Inspection ID to the InfoMaster Inspection table.  For this reason, it is recommended that the same field mapped to the System field called Inspection ID be mapped to Source ID as well.

Note that even if you are importing a Standard Exchange PACP/MACP/LACP database, this Source ID will not be automatically mapped.

Pipe Segment Reference – see above.  This field can be used to tie inspections to pipes in lieu of correlating manholes.

Length Surveyed – controls the display of the inspection length within the Condition Assessment Window.

PACP_Code – this System Field is only available if importing NASSCO data, but other coding fields for other types of inspections work similarly.  This field must be populated for InfoMaster to generate scores for pipes/other facilities.  If the field assigned to PACP_Code contains values not found in the coding table, the unique values will be added to the coding table and can be assigned scores.

‘Special’ CapPlan Tables – Rehab Actions

InfoMaster’s Rehab Actions and Rehab Methods tables come with default values which users can completely customize for their own rehab plan purposes.  However, there are two rehab actions which if tie directly to other internal processes.

Replace (Rehab Action) – this rehab action directly ties to the Baseline Replacement Cost tool.  If it is removed or spelled differently, the Baseline Replacement Cost tool will not function correctly.

LATERAL REINSTATEMENT (Rehab Method) – this rehab method ties to the Connection Cost field in the Rehab Method table.  If another Rehab Method is assigned to assume Connection Costs, the LATERAL REINSTATEMENT method and associated costs will be assigned to the pipe as well.  This LATERAL REINSTATEMENT rehab method is directly tied to PACP defect codes such as CN, CX, and CI, and will be assigned wherever these connection codes appear in the CCTV data.

For more questions regarding ‘special’ fields InfoMaster may be using in specific ways, please contact Innovyze Support!

Share this post!
    This entry was posted in InfoAsset Planner, InfoMaster and tagged , , , , . Bookmark the permalink.