Family Field Descriptions
Step Template Details Records
Step Template Details records store details about Step Templates that are used to create multiple steps. This topic provides a list and description of the fields that exist for the Step Template Details family. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
ACTION PICKLIST | Character | The action categories that you can select to perform on a step. | This field contains the categories defined in Actions section of the Picklist Management page. For every Reading Type, corresponding values are defined for the Action Picklist. |
ACTION VALUES | Character | The values defined for the selected action category. | This field contains the values defined for the action category in the Actions section of the Picklist Management page. Selecting the value displays the value as a chip in the box. You can add only one name at a time to the box. You can add a maximum of 15 chips for a step. The corresponding drop-down list of Action Values matches the order of the chips in the Action Values field. |
ASSIGNED ASSETS | Character | The names of the assets to which the template will be applied. | This is a read-only field, which allows you to search, filter, and select multiple assets to which you want to apply the template. Note:
|
DISPLAY MESSAGE | Character | A message providing information on the limit value or the health indicator. | Enter a display message associated with the limit or the health indicator in the Generate Health Indicators section. The message can contain up to 50 characters. You can see this message when you enter the readings for the step using Rounds Pro Mobile application. |
HEALTH INDICATOR TYPE (Numeric reading type) | Character | Displays the following indicators with the appropriate color code:
| The appropriate indicators appear against each limit based on the upper and lower threshold levels:
|
HEALTH INDICATOR TYPE(Picklist reading type) | Character | Displays the following indicators with the appropriate color code:
| The appropriate indicators appear against each limit based on the upper and lower threshold levels:
|
READING PICKLIST | Character | The reading types that you can select from the categories available. | This field contains the values defined in the Readings section of the Picklist Management page. |
READING TYPE | Character/Numeric | The type of data that users can enter when creating a reading linked to the Step. | This field contains the following values:
This is a required field. |
READING VALUES | Character/Numeric | The values defined for the selected reading category. | This field contains the values defined for the action category in the Readings section of the Picklist Management page. Selecting the value displays the value as a chip in the box. You can add only one name at a time to the box. You can add a maximum of 15 chips for a step. Note: Click in the chip to delete a value appearing in the box. |
STEP DESCRIPTION | Character | A description of the Step. | In this box, you can enter a description of the action users will be completing when they enter readings for this step. For example, Pump Check, Vibration Check, or Temperature Check. The description can contain up to 100 characters. |
STEP TYPE | Character | The category to which the Step belongs. |
By default, this field has the value Measurement Location. This is a required field. |
TEMPLATE NAME | Character | The name of the Step Template. |
You can enter a unique alphanumeric name that you want to assign to the Step Template. The template name can contain up to 50 characters. This is a required field. |
Step Details Records
Step Details records store details about Steps that are included in a route. This topic provides a list and description of the fields that exist for the Step Details family. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
ACTION PICKLIST | Character | The action categories that you can select to perform on a step. | This field contains the categories defined in Actions section of the Picklist Management page. |
ACTION VALUES | Character | The values defined for the selected action category. | This field contains the values defined for the action category in the Actions section of the Picklist Management page. |
ALLOW PHOTOS | Radio Button | This option allows you to enable Photos section in the Step details page of Rounds Pro mobile application to add images. | You can select one of the following options:
|
ASSET | Character | Displays Asset which is selected from the Asset Hierarchy. | You can add a conditional step from an asset that is different from the parent asset. |
CONDITIONS | Character/Numeric | This field stores the value of the Step condition. | Select or enter the reading value to set the condition. This condition combined with the value in the OPERATOR box, will activate the conditional step to appear. If the Step type is picklist, the picklist values for that step appear in the drop-down list. If the Step type is numeric, then you can enter a number only. If the Step type is character, then you can enter a character string. |
CONDITIONAL STEP | Character | This field displays the step that must be performed if the condition set for the primary Step is met. | Select a Step that exists under the asset where the primary step exists or type to search for the step that must be activated if the reading values meet the condition set. |
DISPLAY MESSAGE | Character | A message providing information on the limit value or the health indicator. | Enter a display message associated with the limit or the health indicator in the Limits Only or Generate Health Indicators section. The message can contain up to 50 characters. You can see this message when you enter the readings for the step using Mobile Rounds. |
GENERATE HEALTH INDICATORS | Radio button | This option allows you to create health indicators based on the threshold level for readings. | Select this option to create health indicators based on the threshold level for readings. |
HEALTH INDICATOR TYPE (Numeric reading type) | Character | Displays the following indicators with the appropriate color code:
| The appropriate indicators appear against each limit based on the upper and lower threshold levels:
|
HEALTH INDICATOR TYPE(Picklist reading type) | Character | Displays the following indicators with the approriate color code:
| The appropriate indicators appear against each limit based on the upper and lower threshold levels:
|
Jobs Queue (x) | Drop-down List Box | Displays the status of each job. | When you update a Step or a Step Template, the Jobs Queue (x) shows the status of each Step and Step Template. |
LIMIT | Character/Numeric | The threshold value for the readings entered for the Step in Rounds Pro mobile app. | Based on the value selected for READING TYPE you can enter the following readings:
|
LIMIT COLOR | Character | The color and the name of the color associated with the limit value. | Select the Limit color from the drop-down list to be associated with the limit value. |
None | Radio Button | This option allows you to delete the Limits values, if any generated for the health indicators. | Select this option to delete Limits values when the READING TYPE is Numeric or Picklist: Single Select. |
Open Strategy | Link | Displays a link associated with a Strategy Step. | This link appears in the Details workspace only when you select a Strategy Step in the Assets hierarchy. You can select this link to navigate to the Strategy Details page. |
Open Template | Link | Displays a link associated with a Step Template | This link appears in the Details workspace only when you select a step associated to a template in the Assets hierarchy. You can select this link to navigate to the Step Template Details page. |
OPERATOR | Character | This field specifies the operators that determine if the reading value entered for the primary Step meet the condition specified. | Select the required operator from the drop-down list. The values available in this drop-down list are dependent on the value in the PRIMARY STEP NAME:
|
PRIMARY STEP NAME | Character | The name of the step in a route, to which you want to add conditional steps. | The field contains the name of the current step in the route to which you want to add conditional steps. Note: Subsequent conditional steps that are added are displayed as STEP NAME. |
READING PICKLIST | Character | The data that is displayed if value for READING TYPE is Picklist. | This field contains the values defined in the value set. |
READING TYPE | Character/Numeric | The type of data that users can enter when creating a reading linked to the Step. | This field contains the following values:
|
READING VALUES | Character/Numeric | The values defined for the selected reading category. | This field contains the values defined for the action category in the Readings section of the Picklist Management page. Click Save to save the changes. If the chip is in use in the current step, then the chip is greyed out and cannot be deleted. If the chip is in use in a limit or a conditional in any other step linked to the parent asset, then the deletion does not happen. When multiple chips are selected for deletion and you click Save, in case there are conflicts for deleting any of the chips, the Save Conflicts window appears. The window displays information about the chips that were not deleted and their relationships to other steps. The step details page is refreshed with the changes. |
Schedule | Character | The schedule using which you want to take readings for the Measurement Step. | You can set a schedule, modify, or remove a schedule from the step. |
STEP DESCRIPTION | Character | A description of the Step. | In this box, you can enter a description of the action users will be completing when they enter readings for this step. For example, Pump Check, Vibration Check, or Temperature Check. |
STEP NAME | Character | The name of the Step. |
You can enter a unique alphanumeric name that you want to assign to the Step. This is a required field. |
STEP TYPE | Character | The category to which the Step belongs. |
By default, this field has the value Measurement Location. This is a required field. |
STRATEGY INTERVAL | Character | Frequency at which the Step must be carried out. | This field contains the following values:
|
STRATEGY INTERVAL | Numeric | Displays the frequency at which the Step is carried out. |
This field appears in the Details workspace when you open a Step that is linked to Strategy. This is a read-only field. Note: This field is available only if the Step is a Strategy Step. The subscript s in the Step icon indicates that the Step is a Strategy Step.
|
STRATEGY INTERVAL UNITS | Character | Displays the frequency measurement unit at which the Step is carried out. |
This field is read-only that contains the following values:
Note: This field is available only if the Step is a Strategy Step. The subscript s in the Step icon indicates that the Step is a Strategy Step. |
UNIT OF MEASUREMENT | Character | The unit of measure that users can specify when entering a numeric reading value for the Step. | You can select a value from the list. The values are populated from the System code table – UOME. This field is disabled if the STEP TYPE field contains the value Character. |
Reference Documents Records
Reference Documents records store details about reference documents that are linked to a step included in a route. This topic provides a list and description of the fields that exist for the Reference Documents family. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
ADDED BY | Character | This field stores the name of the individual who added the reference document. | None |
ADDED DATE | Numeric | This field stores the date on which the user added the reference document. | None |
ADDITIONAL INSTRUCTIONS | Character | This field stores the additional instructions that is provided to follow while performing a step. | You can enter additional instructions that need to be followed by the operators while performing the step. The text can contain containing a maximum of 500 characters. The additional instructions appear in the step details page of the Rounds Pro mobile application. |
FILE | Character | This field allows you to attach a file to link to the step. | This field appears in the Add Reference Document window when you select the FILE option. Select to browse and select a file, to link to the step as a reference document. You can link the following file types:
|
HYPERLINK | Character | This field allows you to enter the URL of the hyperlink to reference in the step. | This field appears in the Add Reference Document window when you select the HYPERLINK option. Add the URL of the hyperlink that you want to reference in the step. |
NAME | Character | This field stores the name of the reference document. | The name entered in the REFERENCE DOCUMENT NAME field when you add a document or a hyperlink to the step. |
PHOTO | Image | Displays small image of the photo attached to the step. | You can attach a maximum of one photo to the step to provide more information related the step. |
TOTAL KB | Numeric | This field stores the size of the attached document. | None |
REFERENCE DOCUMENT NAME | Character | This field allows you to enter the name of the reference document. | Enter a name for the reference document or hyperlink that you want to add to the step. |
TYPE | Character | This field stores the type of the reference document linked to the step. | One of the following values is displayed based on the document type:
|
Plan Route Records
Plan Route records store details about how the route is scheduled to be performed and completed for the assets. This topic provides a list and description of the fields that exist for the Plan Routes family. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
ACTIVATE ROUTE | Button | Create or update a route instance as per the defined schedule. | Enable the button to create a route instance at the scheduled time. If the button is disabled, then route instances are not generated based on the defined schedule. Disable the button to delete the schedule defined to create the route instances.Note: You can enable or disable this button only if a schedule is defined. |
Adjust for Daylight Saving Time | Character | Adjust the schedule for Daylight Saving Time (DST). | For schedules that are set to recur every certain number of hours or minutes after the specified Start time, for time zones that use Daylight Saving Time (DST), you can specify whether you want the schedule to adjust for DST automatically. Select the check box to adjust the schedule for daylight savings so that the Route will be due at the same time of day whether or not DST is in effect. If you do not select this option, the Route will be due at the actual time as per the increment defined, whether or not DST is in effect. |
APPLY SCHEDULE | Character | Create or modify a job schedule that is defined for the route. | Select the button to create or modify the job schedule as per the time and date defined in the Edit Schedule window. The details of the schedule appear in the SCHEDULE SUMMARY box. |
ASSIGN TO | Character | Name of the person or team responsible for ensuring the route is completed. | Enter the name of the person or the team who would be responsible for ensuring the Route is completed. You can enter the characters to search for the names. After you select the field, the names of the users and teams appear in the list. After you start entering the characters, the search results appear in a drop-down list. At a given time, a maximum of 50 names appear in the drop-down list. When you scroll down to the last name in the list the next 50 names get added to the drop-down. Selecting the name displays the name as a chip in the box. You can add only one name at a time to the box. After four rows of names appear in the box, you can scroll down to move to the next row that is added when you select additional names. The name that is added in the box does not appear in the drop-down list during the next search. Note: Select in the chip to delete a name appearing in the box. This field is applicable for both the Route Master and Route Instance. The summary of the users or teams assigned appear in the ASSIGNED TO column in the Route Masters page.Select Save, to save the changes to the database. |
BASIS FOR OCCURRENCE | Character | The source of occurrence of the route. | This field contains the following values:
|
COMPLIANCE HORIZON | Numeric | The frequency based on which the route must be completed. | Enter the number to specify the frequency in time units, such as days, weeks, and so on, based on which the route instance must be completed. Note: The time units values are supported by the MI_TIME_UNITS table, which you can configure with the additional values as needed. |
COMPLIANCE HORIZON INTERVAL | Character | Interval within which the route instance must be completed. | This field contains the time units to measure the frequency based on which the route instance must be completed. The values can include the following:
Note: The time units values are supported by the MI_TIME_UNITS table, which you can configure with the additional values as needed. |
COMPLIANCE TRACKING | Button | Track a job scheduled on a route for compliance. | Enable the button to activate compliance tracking for a schedule on a route. If the button is disabled, then the compliance is not tracked for a defined schedule. You can enable this button only if :
For example, if you enter 1 in the Compliance Horizon field and select week in the Compliance Horizon Interval drop-down list, whenever an instance is created on this route master, it needs to be completed withing 1 week of creation. If compliance is turned off, the instances that are created before disabling the compliance are still tracked for compliance and the due date in the Open Instances page appears in red if the next due date is past the compliance date. |
EAM REFERENCE NUMBER | Numeric | Number associated with the route. | 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. |
EDIT SCHEDULE | Character | The schedule by which you want to take readings for this Route. | When you select Schedule in the drop-down list, the Edit Schedule option appears. Select Edit Schedule. The Edit Schedule window appears which allows you to define the schedule to generate route instances from an associated route. |
END | Character | The date or time until when the schedule is active and allows generation of route instances. | This field contains the following values:
For example, if the Start time is January 1, 2021 and the end time is December 31, 2021, this means that for the schedule that gets executed daily at 8:00 A.M, instances are generated only during the year 2021. Note: The start and end dates determine the period during which the route instances can be created, and not when they can be executed. |
EVERY | Character | The frequency at which the route schedule recurs. | You can select the duration from the following values:
|
FLOC EQUIP REF |
Character |
The number associated with the equipment. | This is a unique alphanumeric number. You can enter this number based on the functional location of the equipment. |
FLOC EQUIP STATUS |
Character |
Indicates the status of the equipment. |
You can select the equipment status from the following values:
Note: This field is supported by the FLOC_EQUIPMENT_STATUS table, which you can configure with the additional values as needed. |
FREQUENCY |
Numeric |
The duration at which a route schedule recurs. |
You can enter a number for the duration at which a route schedule recurs. Note:
|
FREQUENCY INTERVAL |
Character |
The time unit to measure the duration at which the route schedule recurs. |
You can select the time unit from the following values:
Note: You must provide values in both the fields, Frequency and Frequency Interval , if needed. |
ROUTE DESCRIPTION | Character | A description of the route. | In this box, you can enter a description of the action which users will be completing when they enter readings for the Steps included in the route. For example, Pump Check, Vibration Check, or Temperature Check. |
ROUTE FREQUENCY | Character | Frequency at which the route must be carried out. |
This field contains the following values:
|
ROUTE INSTANCE | Button | Creates a Route Instance with the selected list of assets and steps. |
Select this button to create a Route Instance with the selected list of steps and assets. The created route instance appears in the Open Instances page. |
ROUTE INSTANCE DESCRIPTION | Character | A description of the route instance. | In this box, you can enter a description of the instance which users will be completing when they enter readings for the Steps included in the ad-hoc route instance. |
ROUTE INSTANCE NAME | Character | The name of the route instance. |
You can enter a unique alphanumeric name that you want to assign to the route instance. This is a required field. |
ROUTE MASTER | Button | Creates a Route with the selected list of assets and steps. |
Select this button to create a Route with the selected list of steps and assets. The created route appears in the Route Masters page. |
ROUTE NAME | Character | The name of the route. |
You can enter a unique alphanumeric name that you want to assign to the route. This is a required field. |
SCHEDULE SUMMARY | Character | Summary of the job schedule created to generate route instances from a route. | The details that are entered and saved in the Edit Schedule window appear in the form of a summary. Select to modify the schedule details from the Edit Schedule window. After saving the changes, the modified summary appears. Select to delete the scheduled job. The schedule summary is removed from the box. |
START | Date | The date or time when the schedule becomes active and allows generation of route instances. | The Start date is the date when the schedule becomes active. The Start date is the date when the schedule becomes active and route instance can be generated from the defined schedule. This date, along with the end date, if defined, creates a period when the schedule definition is active for the route master and allows the creation of route instances.For example, if the Start time is January 1, 2021 and the end time is December 31, 2021, this means that for the schedule that gets executed daily at 8:00 A.M, instances are generated only during the year 2021. Note: The start and end dates determine the period during which the route instances can be created, and not when they can be executed. |
TIMEZONE | Character | The timezone in which the route schedule is activated when it is due. | The schedules that you define include a specific time zone. The Route will become due at the specified time in that time zone, irrespective of the time zone of the logged in user. For example, if you set a Route to be due at 8:00 A.M. every day in Eastern Standard Time, the Route would be due at 5:00 A.M. every day in Pacific Standard Time. |
Route Preview Records
Route Preview records store details about the list of assets and associated steps included in a route. This topic provides a list and description of the fields that exist for the Route Preview Records family. The information in the table reflects the baseline state and behaviour of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
ADDITIONAL INSTRUCTIONS | Character | Displays the additional instructions included for the step with text, and small images of the photos attached, if any. | This section does not appear if the step does not include additional instructions or an attached image. |
ASSET NAME | Character | Name of the asset included in the route. | The asset name is displayed with the name of the parent asset, and Asset ID in the grey box. You can expand or collapse each Asset row to view or hide the list of steps assigned to the route. |
CONDITIONALS | Character | Displays the condition to be met for the conditional step to be activated and the number of conditional steps included within the primary step. | If the current reading value recorded for the primary step meets the condition specified, then the term CONDITIONAL STEP appears in red along with the condition specified for the conditional step to be activated. Expand Conditionals to view the conditional steps included for a step. |
MAIN STEPS | Character | List of the steps assigned under each asset. |
Displays the list of steps associated with the asset. For example, Pump Check, Vibration Check, or Temperature Check. Select the step for which you want to view the attached list of reference documents, conditional steps, and additional instructions, if any. |
REFERENCE DOCUMENTS | Character | Displays the reference documents that are linked to a step included in a route. | Select the hyperlinks to access the attached documents. |
Route Masters Records
Route masters records store details about routes available in the route masters. This topic provides a list and description of the fields that exist for the Route Masters family. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
ACTION | Drop-down menu | Displays the options to perform specific actions from the Route Masters page. | The drop-down list displays the following options:
|
ASSIGNED TO | Character | Summary of the users and teams to which the route is assigned. | This field displays a summary of the users and teams to which the route is assigned. Click the summary link to view a detailed list of the individuals or the teams in alphabetical order. Note: You cannot sort or filter data in this column. |
BASIS FOR OCCURRENCE | Character | The source of occurrence of the route. |
This field contains the following values:
Note: This column does not appear by default. To select this column, use the Column Chooser box in the Route Masters page.
|
DUE DATE | Numeric | The earliest due date among all the next due dates specified for all the instances |
This field displays the earliest date that is calculated using the compliance setup duration and the instance creation date. The date appears only when the Compliance Tracking button is enabled in the Plan Routes section after you create a schedule. For example, if you enter 1 in the Compliance Horizon box, select Week from the Compliance Horizon Interval drop-down list, and 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. Note: You cannot sort or filter data in this column.
|
EAM REFERENCE NUMBER |
Character | The Number associated with the route. |
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. Note: This column does not appear by default. To select this column, use the Column Chooser box in the Route Masters page.
|
ENTITY KEY | Numeric | A unique number associated with the route. | This key is generated automatically when you create a route. Note: This column does not appear by default. To select this column, use the Column Chooser box in the Route Masters page.
|
FLOC EQUIP REF |
Character |
Number associated with the equipment. |
This is a unique alphanumeric number. Note: This column does not appear by default. To select this column, use the Column Chooser box in the Route Masters page.
|
FLOC EQUIP STATUS |
Character |
Indicates the status of the equipment |
This field displays one of the following values:
Note:
|
FREQUENCY |
Numeric |
The duration at which a route schedule recurs. |
This field displays a number for the duration at which a route schedule recurs. Note:
|
FREQUENCY INTERVAL |
Character |
The time unit to measure the duration at which the route schedule recurs. |
This field displays one of the following values:
Note: This column does not appear by default. To select this column, use the Column Chooser box in the Route Masters page.
|
IS ACTIVE? | Character | Indicates if the Route is active after the job schedule was created. |
This field displays one of the following values:
|
LAST DATE | Numeric | The last date by when the route must be completed. | The date by when the latest instance was completed and checked-in on the route master. |
LOCATION | Character | The physical location where the routes need to be performed. | This field displays the physical location of the plant with the assets where the routes need to be performed. |
NEXT DATE | Numeric | The date when you must complete the route next based on the route schedule. | If the route does not have a schedule set, then the next date is the earliest date among all the next due date values specified for all the instances of the route master. After the scheduled job is created and a Route Instance is added, the next due date must be calculated to reflect in the Route Master. The column appears by default. However, the value appears in the column only if a schedule is created for the route and the value in the IS ACTIVE field is Yes. |
ROUTE NAME | Character | The name of the route. | This is the name assigned when the route is created. |
ROUTE SIZE | Numeric | Total size of the route including all the steps and attached reference documents. |
Note: This information does not appear on a small screen device.
|
STEP COUNT | Numeric | Number of primary steps associated with the route. | This field displays a count of the primary steps that are added to the route. The count does not include the conditional steps. |
Route Instance Records on Web Application
Route instance records on the Open Instances page and Instance History pages store details about the routes included for an asset. This topic provides a list and description of the fields that exist for the Route Instance Records family. The information in the table reflects the baseline state and behaviour of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
Is Ad-hoc | Boolean | Indicates if the route instance that is created is a Adhoc instance or not. |
This field is set to True in the following instances:
This field is set to False when the Route instance is created from a schedule. |
ASSIGNED TO | Character | Name of the person or team responsible for ensuring the route is completed. | This field displays the name of the person or the team who would be responsible for ensuring the route is completed. |
CHECKED IN BY | Character | Name of the individual who has checked in the route instance. | None |
CHECKED IN DTTM | Character | Date and time when the route instance was checked in. | None |
CHECKED OUT BY | Character | Name of the individual who has checked out the route instance. | This field displays the name of the individual who has checked out the route instance. |
CHECKED OUT DTTM | Character | Date and time when the route instance was checked out. | None |
CREATED BY | Character | The user who has created the route. | None |
CREATED DTTM | Character | Date and time when the route instance was created. | None |
DUE DATE | Character | Date by when the route must be completed. |
If the route master has an active schedule with compliance turned on, and Compliance Horizon and Compliance Horizon Interval are defined, then whenever an instance is created on this route master, the instance must be completed within the defined compliance interval. The date appears in red indicating non-compliance if:
If compliance tracking is turned off, the instances that are created before disabling compliance tracking are still tracked for complaince. The due date (which is the compliance date) appears in red if the instance has not met compliance by that date. |
LAST UPDATED BY | Character | Name of the individual who last updated the route instance. | None |
LAST UPDT DTTM | Character | Date and time when the route instance was last updated. | None |
LOCATION | Character | The physical location where the routes need to be performed. | This field displays the physical location of the plant with the assets where the routes need to be performed. |
NEXT DUE DATE | Numeric | The date when the next instance of the route will be generated if the route master corresponding to the instance has an active schedule. | 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 generated, the next due date is calculated and reflects on the route master. If the Route Master does not have an active schedule, then no value is displayed in this field. The column does not appear by default. Note: You can select this column using the Column Chooser box in the Open Instances page, to see when the next route instance gets created. If compliance tracking is enabled, and the next due date exceeds the date by when the next instance must be generated, then the date appears in red. |
ROUTE INSTANCE NAME | Character | Names of all route instances that have been generated from the routes in the route masters. | This field displays the name of the route that was assigned when the route was created. |
ROUTE INSTANCE SIZE | Numeric | Size of the route. | This field displays the total size of the route including all the steps and attached reference documents. |
STEPS COMPLETED | Numeric | The number of steps in the route that have been completed. | This field displays the number of steps completed out of the total number of steps assigned to the various assets included in the Route. |
WO NUMBER | Alphanumeric | The work order number assigned to the route. | This field displays the alphanumeric work order number for the route. Note: You can specify a value for this field in the Open Instances page using the datasheet. In the Instance History page, this field cannot be edited. |
Route Instance Details Records
Route Instance Details records store information about the steps that are included in a route instance. The Route Instance Details records appear when you expand the Routes on the Open Instances or Instance History pages on the web application. This topic provides a list and description of the fields that exist for the Route Instance Details family. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
ACTION TAKEN | Character | The action values defined for the action category added to the step. | Displays the action picklist reading value recorded for a step in the Rounds Pro mobile app. |
HAS HI | Character | Indicates if the step has a health indicator. | Displays one of the following values:
|
IS CONDITIONAL | Character | Indicates if the step is a conditional step. | Displays the value Yes if the step in the route will be triggered by a condition being met. Displays the value No if the step is not triggered due to any condition. |
LAST DATE | Numeric | The last date by when the step must be completed. | None |
READING |
| The following parameters appear:
|
The readings appear based on the last reading that was collected using Rounds Pro mobile application and saved to the server. Alerts appear based on the limits and health indicators configured in the Rounds Designer for the Step. The minimum indicators configured are:
|
RECOMMENDATION | Character | The recommendation added for the steps. | None |
STEP NAME | Character | The name of the Step. | The name assigned when the step was created. |
STEP TYPE | Character | The category to which the step belongs. | By default, this field has the value Measurement Location. |
Steps Page Records
Step records on the Steps page store details about Steps that are generated using the Rounds Designer. This topic provides a list and description of the fields that exist for the Step family. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
ASSET | Character | The name of the asset associated with the step. | This field displays the name of the asset to which the step is associated. |
HAS HI | Character | Indicates if the step has a health indicator. | Displays one of the following values:
|
HAS SCHEDULE | Character | Displays if a step has a scheduled date. | Displays one of the following values:
|
INTERVAL | Character | Displays the frequency at which the Step is carried out. | None |
INTERVAL UNITS | Character | Displays the frequency measurement unit at which the Step is carried out. | This field is read-only and contains the following values:
|
LAST DATE | Numeric | The last date by when the step must be completed. | None |
LAST READING | Character | The last reading that was recorded for the step. | The readings appear based on the last reading that was collected using the Rounds Pro mobile application and saved to the server. |
NEXT DATE | Numeric | The date when you must complete the step next based on the route schedule. | None |
PHOTO EVIDENCE | Image | Displays a thumbnail image and a number to indicate the number of photos that are attached to the steps. | When you attach photos to a step in the step details page of the Rounds Pro mobile application, this field displays the indication of the presence and number of photos attached to the step. You can select the thumbnail to enlarge the image or download the image to the local database. |
ROUTE | Character | The name of the route. | The name assigned when the route was created. |
STEP NAME | Character | The name of the Step. | The name assigned when the step was created. |
STEP TYPE | Character | The category to which the step belongs. | By default, this field has the value Measurement Location. |
Route Masters Records on Rounds Pro mobile app
Route Masters records on Rounds Pro mobile app store details about routes available in the Route Masters. This topic provides a list and description of the fields that exist for the Route Masters family for Rounds Pro mobile app. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
DUE DATE | Numeric | The earliest due date among all the next due dates specified for all the instances |
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. |
EAM REFERENCE NUMBER | Character | Number associated with the route. |
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. Note: This column does not appear by default. To select this column, use the Column Chooser box in the Route Masters page.
|
FLOC EQUIPMENT REF NUMBER | Character |
Number associated with the equipment. |
This is a unique alphanumeric number. Note: This column does not appear by default. To select this column, use the Column Chooser box in the Route Masters page.
|
FLOC EQUIPMENT STATUS |
Character |
Indicates the status of the equipment |
This field displays one of the following values:
Note:
|
FREQUENCY |
Numeric |
The duration at which a route schedule recurs. |
This field displays a number for the duration at which a route schedule recurs. Note:
|
FREQUENCY INTERVAL |
Character |
The time unit to measure the duration at which the route schedule recurs. |
This field displays one of the following values:
Note: This column does not appear by default. To select this column, use the Column Chooser box in the Route Masters page.
|
LAST DONE DATE | Numeric | The last date by when the route must be completed. |
The date by when the latest instance was completed and checked-in on the route master. Note: This field does not appear on a small screen device by default. However, you can view this field after you check-in the route instance using the My Routes tab on the device.
|
NEXT DUE DATE | Numeric | The date when you must complete the route next based on the route schedule. |
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. |
ROUTE NAME | Character | The name of the route. | This is the name assigned when the route is created. |
ROUTE SIZE | Numeric | Total size of the route including all the steps and attached reference documents. |
Note: This information does not appear on a small screen device.
|
STATUS | Character | Indicates if you have added the route to the My Routes list. | You can add the route to the list if it has not been added. |
STEP COUNT | Numeric | Number of steps assigned with the route. | None |
Route Instance Records on Rounds Pro mobile app
Route instance records on Rounds Pro mobile app store details about the routes included for an asset . This topic provides a list and description of the fields that exist for the Route Instance Records family. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
ACTION | Character | Indicates the action you can take on the route instance. |
This field contains the following values:
|
DUE DATE | Numeric | Date by when the route must be completed. |
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. |
LAST DATE | Numeric | The last date by when the route must be completed. | The date by when the latest instance was completed and checked-in on the route master. Note: This field does not appear on a small screen device by default. However, you can view this field after you check-in the route instance using the My Routes tab on the device.
|
NEXT DUE DATE | Numeric | The date when you must complete the route next based on the route schedule. |
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. |
PROGRESS | Numeric | Percentage of completion of the steps in the route instance. | This value indicates the progress of the route completion based on the number of steps completed out of the total steps assigned to the route. |
ROUTE NAME | Character | Names of all route instances that are assigned to you or the team to which you belong. | The name assigned to the route in the Rounds Designer appears in the field. |
ROUTE SIZE | Alphanumeric | Size of the route. | This field displays the total size of the route including all the steps and attached reference documents. Note: This information does not appear on a small screen device. |
STEP COUNT | Numeric | Number of steps assigned with the route. | This field displays the total number of steps assigned to various assets included in the route. |
WO NUMBER | Alphanumeric | The work order number assigned to the route. | In this box, you can enter the alphanumeric work order number for the route, only if the route is checked out to you. If the route is not checked out to you or is checked out to another individual, this field is not enabled to edit. Note: This information does not appear on a small screen device. |
Route Instance Details Records on Rounds Pro mobile app
Route Instance Details records on Rounds Pro mobile app app store information about the route instances assigned to you or your team and included for an asset. This topic provides a list and description of the fields that exist for the Route Instance Details records family. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
ASSET NAME | Character | Name of the asset included in the route instance. | The asset name title displays the name of the parent asset, Asset ID, and the text indication of the number of steps in progress out of the total steps linked to the asset, for example 1 of 8 Steps. |
CONDITIONAL STEPS | Character | Displays the condition to be met for the conditional step to be activated. | If the current reading value recorded for the primary step meets the condition specified then the term CONDITIONAL STEPS appears in red along with the condition specified for the conditional step to be activated. |
HEALTH INDICATOR MESSAGES | Character | Displays the health indicator messages. | When you enter one of the defined limit values, health indicator messages appear based on the health indicator messages configured in the Rounds Designer for the Step. |
HEALTH INDICATOR TYPE | Character | Displays health indicators with the appropriate color code. | When you enter one of the defined limit values, an alert appears based on the limits and health indicators configured in the Rounds Designer for the Step. The minimum indicators configured are:
|
LAST READING |
| The following parameters appear:
| You can enter the current readings for the step based on data type assigned to the field:
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. Note: You cannot enter data that is not appropriate for the data type specified for the field. |
ROUTE NAME | Character | Name of route whose instance is open. |
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. |
STEP NAME | Character | Name of step | The name assigned to the step in the Rounds Designer appears in the field. |
Recommendation Records on Rounds Pro mobile app
Recommendation records on Rounds Pro mobile app store information about the recommendation linked to an asset step. This topic provides a list and description of the fields that exist for the Recommendation Details records family. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
Check In | Button | Allows you to check in the Route. | None |
Create Stand Alone | Option | Allows you to create a standalone recommendation. | A standalone recommendation is not linked to the step or an asset. |
CREATED BY | Character | The name of the Security User who was logged on to Rounds Pro mobile app when the recommendation was created. |
This is the name of the person proposing the recommendation. |
HEADLINE | Character | Displays a brief summary of the recommendation subject. | The text that appeared in the Headline cell when the Recommendation was saved on the mobile device. |
PHOTOS | Image | Displays an indication of the presence of photos attached to the recommendation and the number of photos attached. | You can access the photos for the route that you access. Photos are downloaded to the device if the route is in progress. |
TIMESTAMP | Date | The date and time on which the recommendation was created. | None |
Recommendation Details Records on Rounds Pro mobile app
Recommendation records on Rounds Pro mobile app store information about the recommendation linked to an asset step. This topic provides a list and description of the fields that exist for the Recommendation Details records family. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
Add Picture | Image | Allows you to take a picture using your mobile device camera and attach the photo to the recommendation. For a device without a camera support, you can select the photos from the local database. | None |
ASSET ID | Numeric | The ID of the Asset for which the recommendation is being made. | This is unique for a particular equipment. This field is auto-populated. |
CREATE WORK REQUEST? | Radio buttons or Slider | Enables a work request. | You can select one of the following options:
|
DESCRIPTION | Character | Details of the recommendation. | You can type in the description in the text box. |
HEADLINE | Character | A brief summary of the recommendation subject. | None |
PHOTOS | Image | Displays small images of the of the photos attached to the recommendation and the number of photos attached. | None |
PRIORITY | Picklist | The priority of recommendation for implementation. | You can select a priority level from the picklist. |
RECOMMENDATION ID | Character | A value that identifies the recommendation record. | This is a unique ID and is generated by the system. |
STEP DESCRIPTION | Character | For recommendations, other than standalone recommendations created on a mobile device, this field is populated automatically with the value that is stored in the Step Description field of the Step for which the recommendation was created. | You cannot enter any values in this field. This field is auto-populated. |
Step Details Records on Rounds Pro mobile app
Step Details records on Rounds Pro mobile app store information about the step assigned to a route instance. This topic provides a list and description of the fields that exist for the Step Details records family. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
ACTION | Character | The action values defined for the action category added to the step. | This field contains the values defined for the action category in the Actions section of the Picklist Management page in the Rounds Designer. Note: The Action picklist is available only if the related step has an Action Picklist and Action Values defined. You can select one value from the picklist. The value that you select 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. The value that is checked in appears in the ACTION TAKEN column for the selected step in the Open Instances and Instance history page of the Web application. |
ADDITIONAL INSTRUCTIONS | Character | This field displays additional instructions that are provided in the ADDITIONAL INSTRUCTIONS section of the Reference Documents page in the Rounds Designer. Below the ADDITIONAL INSTRUCTIONS section, a small image of the photo attached to the step appears. | This is a read-only field. You can view the additional instructions that are provided and need to be followed while performing the step. You can scroll down to access the photo attached to the step, if any. Note: When you check out a route instance, and if a step associated with the route instance has Additional Instructions and image attached, then you can access these details even when your mobile device is offline. |
ATTACHMENTS | Image, PDF, Doc | Displays a list of reference documents attached to the step. | You can access the attached documents when the mobile device is online. |
COMMENTS | Character | You can enter comments to add additional information about the step. | You can enter up to 1000 characters. |
CONDITIONAL STEPS | Character | Displays the condition met that has activated the conditional step. | If the current reading value recorded for the primary step meets the condition specified then the term CONDITIONAL STEPS appears in red along with the condition specified for the conditional step to be activated in the step title. |
HEALTH INDICATOR MESSAGES | Character | Displays the health indicator messages. | When you enter one of the defined limit values, health indicator messages appear based on the health indicator messages configured in the Rounds Designer for the Step. |
HEALTH INDICATOR TYPE | Character | Displays health indicators with the appropriate color code. | When you enter one of the defined limit values, an alert appears based on the limits and health indicators configured in the Rounds Designer for the Step. The minimum indicators configured are:
|
PHOTOS | Image | Displays small images of the photos attached to the step. | Select the image thumbnail to access the photos attached to the step of a route. |
READING |
| The following parameters appear:
| You can enter the readings for the step based on data type assigned to the field:
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. Note: You cannot enter data that is not appropriate for the data type specified for the field. |
READINGS HISTORY | Character | Displays the trend chart based on the values recorded for the Step. | The trend chart changes based on the edited or cleared readings. |
RECOMMENDATIONS | Text | Displays the recommendation title and an option to create a recommendation. | Select to create a recommendation. |
SCAN ID | Character | Indicates the SCAN ID associated with the step. | For a barcode or QR code, enter the scan code. For an NFC tag, enter the serial number without colons. For example, if the serial number is 96:DB:46:AA, enter 96DB46AA. 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. |
SCAN TO UNLOCK | Boolean | Indicates whether, a step should be locked until the device scans the associated Scan code (Barcode, QR code etc.). | When you switch the toggle on, the Scan ID would be a required field and you must scan the barcode associated with the step to record a reading. By default, the toggle switch is Off. Note: This functionality is not available. |
STEP NAME | Character | Name of step and the step title. |
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. |
Compliance Track Family
The Compliance Track family integrates with other Rounds Pro families, such as Step, Step Reading, and Route Instance.
Field | Data Type | Description | Behavior and Usage |
---|---|---|---|
Due Date | Date | Due date for the step reading | Due date is the date when the reading is due based on the schedule defined. For example, if the Schedule is set as “Every day at 8AM”, due date is Today 8AM. If the Step has its own schedule, this field is populated based on the schedule defined at the step level. If the Step doesn’t have its own schedule, this field is populated based on the schedule defined at the Route Master level. Note: If the schedule is defined both at the route Master level as well as at the Step level, this fields is populated based on the schedule at Step level. This field is populated at the time of instance creation. |
Non-Compliance Date | Date | Non-Compliance date for the step reading | Non-Compliance date is the date when the reading is considered as non-compliant based on the schedule defined. For example, if the Schedule is set as “Every day at 8AM”, Non-compliance date is Tomorrow 8AM. If the Step has its own schedule, this field is populated based on the schedule defined at the step level. If the Step doesn’t have its own schedule, this field is populated based on the schedule defined at the Route Master level. Note: If the schedule is defined both at the route Master level as well as at the Step level, this fields is populated based on the schedule at Step level. This field is populated at the time of instance creation. |
Completed Date | Date | Date when the reading is completed | This is the reading taken date by the operator on the field. This field is populated after the instance is checked in. If the reading is not taken, this field would be null. |
Is Conditional Step Excluded | Boolean | Boolean field to track if the Conditional step is excluded. | This field is set to true if the step is a conditional step and the parent step is not executed or is not required. In all other cases this field is set to false. This field helps you understand which fields are skipped legitimately. |
FK_MI_RTE_INST_0_G | Character | Holds the entity key of the Route Instance | Useful in reporting. Helps in identifying the instance of the Step Reading. |
FK_MI_RTE_STRCT_STP_0_G | Character | Holds the entity key of the Route structure step | Useful in reporting and is required to support the sharable nature of the steps. |
FK_MI_STP_0_G | Character | Holds the entity key of the step. | Useful in reporting. Identify the Step to which the step reading belongs to. |
FK_MI_STP_RDNG_0_G | Character | Holds the entity key of the step Reading. | Useful in reporting. |
FK_MI_RTE_STRCT_STP_1_G | Character | Holds the Immediate parent Structure step entity Key | This will be blank for all parent Steps, for all the child steps it will hold the immediate parent Structure step entity Key. |
FK_MI_RTE_STR_STP_COND_0_G | Character | Holds the entity key of the Route Structure Step condition. | For reporting this will help determine if steps under the same condition are executed. |