Family Field Descriptions

This field displays the earliest date that is calculated using the compliance setup duration and the instance creation date.

For example, if you enter 1 in the Compliance Horizon field, select week from the Compliance Horizon Interval drop-down list, and you create an instance every week for two months, then the due date is calculated by adding the creation date of the instance to 1 week.

Similarly, the due date is calculated for all the instances and the earliest date is displayed here.

The due date (which is the compliance date) appears in red if the instance has not met compliance by that date.

This field displays the date only when the Compliance Tracking button is enabled in the Plan Routes section of Rounds Designer after you create a schedule. Else, the next due date is displayed, which is the date when the next instance gets created if a schedule is available.

This field is enabled if you have selected EAM in the BASIS FOR OCCURRENCE field. This is a unique number. You can manually populate this number.

Number associated with the equipment.

This is a unique alphanumeric number.

Character

Indicates the status of the equipment

FREQUENCY

Numeric

The duration at which a route schedule recurs.

This field displays a number for the duration at which a route schedule recurs.

FREQUENCY INTERVAL

Character

The time unit to measure the duration at which the route schedule recurs.

The date by when the latest instance was completed and checked-in on the route master.

If the route does not have a schedule set, then the due date is the earliest date among all the next due date values specified for all the steps in the route.

After the scheduled job is created and a Route Instance is added, the next due date must be calculated to reflect on the route master.

If the route master has an active schedule with compliance turned on, and Compliance Horizon and Compliance Horizon Interval are defined, whenever an instance is created on this route master, it needs to be completed within the defined interval. The due date (which is the compliance date) appears in red if the instance has not met compliance by that date.

If compliance is turned off, the instances that are created before disabling the compliance, are still tracked for compliance and the due date (which is the compliance date) appears in red if the instance has not met compliance by that date.

If compliance is turned on, the due date is displayed. Else, the next due date is displayed, which is the date when the next instance gets created if a schedule is available.

If the route does not have a schedule set, then the due date is the earliest date among all the next due date values specified for all the instances.

After the scheduled job is created and a Route Instance is added, the next due date must be calculated to reflect on the route master.

This column does not appear by default. To select this column, use the Column Chooser box in the Open Instances page.

If compliance tracking is enabled, and the next due date exceeds the date by which the next instance must be generated, then the date appears in red.

• Alert (Red)
• Warning (Yellow)
• Normal (Green)

• Numeric
• Character

• The last reading that was recorded for the step.
• Message indicating if the step is conditional.
• Health indicator.
• Health indicator messages.

• For a numeric step, you can enter numbers and decimal.
• For a character step, you can enter a character string.
• For a picklist, you can select the values assigned to the picklist that appear in the drop-down list.
  Note: You can clear the selected value and assign another value from the drop-down list before you check in the changes.

The value that you enter is recorded for a step as the reading value and saved to the mobile database. After you check in the changes, the values are saved to the server and cleared from the field.

The route instance title displays the name of the route instance that is accessed from the My Routes page. The name assigned to the route in the Create Route page in Rounds Pro appears in this field.

This is the name of the person proposing the recommendation.

• Yes: This option is selected by default. All the other Work request details are enabled. The work request is sent to the connected EAM system after the recommendation is saved to the APM database.
• No: Work request details are not enabled.

• Alert (Red)
• Warning (Yellow)
• Normal (Green)

• Numeric
• Character

• The last reading that was recorded for the step.
• Message indicating if the step is conditional.
• Health indicator.
• Health indicator messages.

• For a numeric step, you can enter numbers and decimal.
• For a character step, you can enter a character string.
• For a picklist, you can select the values assigned to the picklist that appear in the drop-down list.
  Note: You can clear the selected value and assign another value from the drop-down list before you check in the changes.

The value that you enter is recorded for a step as the reading value and saved to the mobile database. After you check in the changes, the values are saved to the APM server and cleared from the field.

When you scan the code, if there is a single match in the checked-out route instances, the Step Details page appears, and the step is unlocked. However, if there are multiple matches, you can choose the step that you want to unlock, or you can unlock all the steps.

The step title displays the name of the parent asset for the step, the Asset ID, and the text indication of the relative step position under the asset, for example Step 2 of 8.

The name assigned to the step in the Rounds Designer appears in the field.