FAQs

R2 Utility is a recording and reporting platform designed to manage operational records within a connected system. The platform allows users to track locations, assets, tasks, notices, reports, and related activity.

R2 supports flexible workflows. Core records such as locations, assets, tasks, and contacts can exist independently or be connected when your workflow requires it.

R2 is built around core record types including Locations, Assets, Tasks, Contacts, Notices, and related operational records.

These records can stand alone or be linked together. For example, an asset can be connected to a location, a task can be connected to an asset, and a contact can be associated with either record.

A Location represents a real-world place such as a property, building, facility, service address, site, unit, or other physical location your organization needs to manage.

An Asset represents equipment, infrastructure, an assembly, device, or another physical item that needs to be tracked and managed.

Yes. A single location can have multiple assets connected to it while each asset remains its own individual record.

Yes. Assets can exist independently and do not have to be connected to a location.

Connecting an asset to a location can provide additional operational context when the relationship is useful.

Asset records can contain identification information, specifications, category information, status, connected records, activity, tasks, notes, files, notices, and other information related to that asset.

Yes. If equipment is relocated, the asset record can be connected to a different location while retaining its record history and related information.

A Task represents work that needs to be completed.

Tasks can be used independently or connected to records such as Locations, Assets, Assemblies, Contacts, or assigned users depending on the workflow.

Yes. Tasks can be assigned to users so responsibility for the work is clearly identified.

Assigned tasks can appear throughout the Tasks section, including My Tasks, the Task Dashboard, Schedule, Routes, and the Task List depending on the task and workflow.

Yes. Tasks can be connected to Locations, Assets, Assemblies, and other records so the work remains tied to the records it affects.

Yes. Task assignments can be changed when responsibility for the work needs to move to another user.

When work is completed, the task may move through a review process depending on the workflow. The reviewer can approve the work, request changes, or close the task.

Completed tasks can then become part of the maintenance history for connected records.

Notices are created using notice templates. Templates define the structure and content used when generating notices.

Yes. Notices can be associated with records such as Locations or Assets depending on the type of communication being sent.

A report template defines the layout and data used to generate a report within R2.

Reports are generated by selecting the appropriate report template and the records or information that should be included.

Yes. Notices and reporting workflows can be automated through scheduled or trigger-based actions when those workflows are configured.

Triggers are automation rules that perform an action when a defined condition or event occurs within the platform.

Filters allow users to narrow record lists based on selected criteria so they can focus on the information relevant to their workflow.

No. Filters are saved at the individual user level so each user can maintain their own preferred workflow views.

Yes. Saved filters remain applied until they are changed or removed.

Yes. Record lists include search and organization tools to help users quickly locate the information they need.

Depending on the section, records can be displayed using multiple layouts such as Panel, Table, Mobile, Map, or List views.

Yes. Multiple authorized users can work within the system at the same time while accessing the records available to their account.

Yes. Each user has their own account access, allowing activity and preferences to remain associated with the individual user.

No. User-specific preferences such as saved filters and views remain associated with the individual user.

Yes. Core records such as Locations, Assets, Tasks, and Contacts can exist independently and only need to be connected when the relationship supports the workflow.

Yes. R2 maintains activity history that provides a timeline of actions associated with records.

Audit information can provide additional detail about changes, including who made a change, what was changed, and when the activity occurred.