Skip to main content
Cartegraph Campus

Import Inspections

You must have administrator rights to access this feature.

This overview describes the steps needed to import large amounts of Inspection data into Cartegraph.

You must have:

  • Administration rights to Cartegraph
  • Security permissions to create and update the records being imported
  • Familiarity with standard Cartegraph import processes
  • Already entered the asset records into Cartegraph

All imports must be ordered by date with the oldest records at the beginning of the file and the newest records at the end.

Import New Inspections

Set Up the Inspection Format File

In order to create an inspection through import, verify the inspection format minimally contains the following:

  • Parent Asset ID
  • Task ID (Optional. Refer to the Include Task ID in the Inspections Format File section.)
  • Inspection ID (Matching field)
  • Inspection Date
  • Background RA (Signs only, optional)
  • Legend RA (Signs only, optional)
  • Status
  • Inspected By (If this field is excluded, the value will be set to the labor log associated with the user running the import, if the user has an associated labor record)

Create a Completed Inspection

The system automatically marks condition categories as Not Inspected when an inspection is created with a status of complete. This does not apply to background RA (sign only), and legend RA (sign only), whose indexes are system calculated.

The associated inspection task is marked as completed if it was automatically generated by the system when the inspection was created and the inspection was marked as complete.

Include Task ID in the Inspections Format File

This process is optional.

Cartegraph recommends that you leave the task ID out of the inspection format file so that the system automatically generates and associates a task to the new inspection.

If you do include the Task ID field and the task exists, the system associates the inspection to that task if the following business rules are satisfied:

  • Inspection date must be on or after the task's actual start date and on or before task's actual stop date.
  • Task cannot have a different inspection associated to it.
  • Task activity must be marked as inspect.
  • Task must be associated to the same asset the inspection is being performed on.

If the task ID is supplied and the task does not exist, the system automatically creates an inspection task with that ID value.

If the provided task ID exists in the database and the task can be associated to the inspection being created, the system uses the existing task and does not create a new task.

For a task the system automatically creates when creating inspections, the task has its actual start date field set to the inspection's inspection date field and have its activity field set to Inspect.

Inspection Status Is Complete. Task Status Is Completed.

If the inspection being created has its status set to Complete, the automatically created task has its Actual Stop Date field set to the inspection's Inspection Date field and its Status field set to completed.

An inspection cannot be marked as complete if all of the applicable condition categories do not have at least one of the following: an index, a measured value, or NI (not inspected) set to true. If the Inspection being created has its status set to completed and a condition category does not have a value for its Measured Value field or Index field, the condition category is marked as NI so the inspection can be completed.

Exceptions to this include:

  • Signs: Background Ra is optional
  • Signs: Legend Ra is optional

Condition categories marked as NI only have an Index if the system was able to calculate a value.

The inspection can be marked as complete regardless if the system is able to calculate an index for these condition categories.

It is possible to have a completed pavement or pavement area inspection without a PCI index. This happens if it was marked NI and there is missing condition data or if a sample is saved without distresses and is not marked as no distresses found.

Import Condition Categories

Cartegraph automatically generates the condition categories that apply to an asset inspection upon save of the inspection. You only need to update the condition category records you have inspected.

Some of the generated condition categories are system calculated condition categories. For signs, the background Ra and legend Ra condition categories are calculated. For pavement and pavement area, the PCI condition category is calculated. Do not import index values for these or mark them as not inspected.

Set Up the Condition Category Specification File

In order to update a condition category through import, verify the specification file minimally contains the following:

  • Inspection ID
  • Condition category (matching field)
  • Not inspected
  • Index

Set Up the Condition Category Data File

In a program like Excel, merge your inspection data with the condition categories generated by Cartegraph. For condition categories you inspected, provide the index or rating and verify Not Inspected is false. For condition categories you did not inspect, remove them from the file as they are already saved with Not Inspected as true.

The condition category data file must follow the format defined by the spec as well as conform to the following business rules:

  • The index must be greater than or equal to 0 and less than or equal to 100.
  • Duplicate condition categories for the same inspection are not allowed.
  • You cannot set the condition category to Not Inspected and set the rating or index value.

Import Samples

This step applies to pavement and pavement area inspections only.

Import Distresses

This step applies to pavement and pavement area inspections only.