Condition inspections calculate the Overall Condition Index (OCI) for an asset. OCI is calculated for the date of the inspection. The minimum condition is used to calculate the asset’s failure point. Inspections should have data for every condition category with weights, impacts, and a performance curve.

There are two types of OCI calculations, Inspection and Estimated:

Inspection OCI Calculations

Inspections calculate the Inspection OCI. The Inspection OCI is calculated for the date of the inspection. The inspection OCI is a weighted average of the inspection’s condition category indexes. Inspections should have data for every condition category with weights.

Inspections provide a procedure to better manage your organization’s assets and equipment by planning and predicting.

  • The Inspected Overall Condition Index (OCI) calculate only after an inspection’s status is Complete.
  • Each asset has an Inspections child recordsets for capturing more inspection details.
  • Condition Categories list the asset’s attributes or criteria being inspected. For example, a picnic table’s Structure and Surface are Condition Categories.
  • Additional Inspection details can be recorded if structure is added to the Inspection recordset. For example, Observations.
  • The Condition Category library contains the criteria, weight, and the index mappings to calculate the Inspection OCI, which is used to set the Inspection OCR based on the asset’s Overall Ratings library.
  • Each inspection record contains a hidden, automatically generated ID in the Current ID field. This ID also displays parent level to the Asset and is called Current Inspection ID. The most recent inspection’s ID is used as the asset’s Current Inspection ID.

When a Condition Category is marked Not Inspected (NI):

  • If it has a performance curve, the NI icon displays and the index for the condition category is calculated using the performance curve for that condition category.
  • If it does not have a performance curve, the NI icon displays and a warning message displays that the index cannot be estimated, and the Condition Category is not included in the weighted estimate of the inspected OCI.

With the Advanced Asset Extension:

  • Inspections also help to determine the performance or OCI of any asset over its life cycle. The inspection data entered is used to calculate the Estimated OCI of the asset.
  • The inspection index of each condition category is incorporated into the asset’s performance curve, which estimates the deterioration of the asset. Completed tasks with an identified impact also affect the asset’s performance curve.

Estimated OCI Calculations

The estimated OCI for an asset is calculated by taking into account the asset’s age, predicted performance, and inspections and tasks performed on the asset. Using this data, the estimated OCI for the asset is determined.

Assets should have an installed or replaced date, fall into a condition group and prediction group as well as have data for every condition category with weights, impacts, and a performance curve.

This functionality automatically begins whenever an asset’s condition needs to be updated. For example, when a task or inspection is saved. The calculations also update when the Cartegraph Asset Condition Recalculator runs.

The values in the following fields are recalculated:

  • Prediction Group
  • Condition Group
  • Act Before
  • Estimated OCI
  • Estimated OCR
  • All the data in the Performance Curve on the asset record

A Condition Group is selected based on the Condition Group filters. A Prediction Group is selected based on the Prediction Group filters. If a Prediction or Condition Group cannot be found for the asset, no calculations are performed.

An asset’s Performance Curve is shifted based on completed inspections and tasks. The age of the asset as of today is plotted on the adjusted curve to determine today’s estimated condition. These results are stored in the Estimated OCI (Overall Condition Index) field. The point where the adjusted curve falls below the minimum index for the asset’s condition group is stored in the Act Before field.


[ut_one_half]
[ut_service_column color=”#FDA527″ icon=”fa-desktop” headline=”User Interface” margin_bottom=”0″ shape=”normal” align=”left” last=”true”]

[ut_service_column color=”#FDA527″ icon=”fa-comments” headline=”Request Management” margin_bottom=”0″ shape=”normal” align=”left” last=”true”]

[ut_service_column color=”#FDA527″ icon=”fa-wrench” headline=”Work Management” margin_bottom=”0″ shape=”normal” align=”left” last=”true”]

[ut_service_column color=”#FDA527″ icon=”fa-bar-chart” headline=”Asset Management & Analytics” margin_bottom=”0″ shape=”normal” align=”left” last=”true”]

[/ut_one_half]
[ut_one_half_last]

[ut_service_column color=”#FDA527″ icon=”fa-money” headline=”Resource & Inventory Management” margin_bottom=”0″ shape=”normal” align=”left” last=”true”]

[ut_service_column color=”#FDA527″ icon=”fa-sitemap” headline=”Report Management” margin_bottom=”0″ shape=”normal” align=”left” last=”true”]

[ut_service_column color=”#FDA527″ icon=”fa-tablet” headline=”Mobile Management” margin_bottom=”0″ shape=”normal” align=”left” last=”true”]

[ut_service_column color=”#FDA527″ icon=”fa-sitemap” headline=”Workflow Management” margin_bottom=”0″ shape=”normal” align=”left” last=”true”]

[ut_service_column color=”#FDA527″ icon=”fa-sitemap” headline=”System Management” margin_bottom=”0″ shape=”normal” align=”left” last=”true”]

[ut_service_column color=”#FDA527″ icon=”fa-puzzle-piece” headline=”Integration Management” margin_bottom=”0″ shape=”normal” align=”left” last=”true”]

[/ut_one_half_last]


[ut_button color=”orange” target=”_self” link=”http://www.appliedgeologics.com/schedule-a-software-demonstration/” size=”medium” shape=”round” title=”SCHEDULE A DEMONSTRATION” ]SCHEDULE A DEMONSTRATION[/ut_button]