Use pages, sections, and tasks to keep a round plan easy to follow on mobile. A clear structure reduces searching and helps Operators complete checks in the intended order.
Pages break a long round into manageable stages.
Sections group related tasks for an asset, location, system, or activity.
Tasks describe one clear check, reading, confirmation, or evidence requirement.
Response types define how the Operator records the result.
Organize these elements in the order the Operator will perform the physical inspection.
In the Select Locations window, select locations and click
Next.
Figure 1. Select Locations
In the Select Assets window, select assets and click
Add.
Figure 2. Select Assets
Note:
Requires SAP integration. When you select locations
and assets, mRounds automatically pulls and synchronizes asset and location
metadata (codes, locations, specifications) from SAP/ERP and shows it at the
task level during round plan creation.
In the Route and Tasks screen, lay out the locations and
assets the operator will visit.
Click the Add Locations/Assets icon to add more from the left pane. Drag and drop
into hierarchy or flat-list view. The hierarchy view doubles as the route plan, so
the order you set here is the order the Operator walks.
Switch between hierarchy, flat-list, and route-plan views using the icons
provided.
Click the More icon and select Show Hierarchy to see the
locations and assets hierarchy. You can also copy and delete locations and assets
from here.
Note:
When a Functional Location ID is updated in
master data, the latest ID is automatically reflected in the Locations/Assets panel
of existing round plans.
The Round Plans screen provides the following ways to organize a plan:
Add, copy, and delete pages and sections.
Cut, copy, paste, and move tasks, including copying a task to all or to selected
locations and assets.
Add Logic: configure what a given response triggers. See
Conditional Logic.
Required: makes the task mandatory.
History: shows the last five readings. Number and Slider
response types only.
Additional Details: click Add to add
Tags and Attributes (Label and Value, up to 250 characters).
For Multiple Choice and Picklist responses you can mark specific values as
exceptions — marking Abnormal on a motor condition
picklist, for instance — so exception reports flag them and planners can act. Figure 3. Response Type Exceptions
In the Historian Tag field add the unique identifier
obtained from Aveva PI. Link the tag, if you want the operator’s reading to be
saved in your plant’s PI historian. When the operator submits the round, the
system automatically sends the reading to PI with the time it was recorded.
For
example, link the task Record discharge pressure at gauge PG-101 to the PI tag
for PG-101. Each submitted reading is added to PI.
Figure 4. Historian Tag
If the content already exists elsewhere, import it instead of building it
again.