Overview
Assets are first-class targets in Mobaro, just like Locations and Location Groups. Any time you create a Schedule or an Assignment, you can target a specific Asset rather than its containing Location — putting the inspection, work order, or compliance task directly on the equipment, ride, or piece of infrastructure that needs it.
Why this matters: Targeting Assets directly is what makes per-equipment maintenance histories possible. Asset-driven Schedules give you "every roller coaster gets a daily pre-opening inspection." Asset-driven Assignments give you "this specific ride needs this specific repair." Both attach the work and its history to the equipment, not just the area it lives in.
Required access: To create Asset-driven Schedules, you need Schedules: Create on your Role and requires access to the Asset's Location.
When to target an Asset instead of a Location
Both Locations and Assets are valid Targets for Schedules and Assignments. Choosing between them is a question of scope:
Target a Location when… | Target an Asset when… |
The work covers an area, zone, or facility broadly | The work is for a specific piece of equipment, ride, or infrastructure |
The Checklist is the same regardless of which equipment is at that Location | The Checklist applies to a particular Asset's specifications, model, or condition |
You want the work tied to the area's operating cycle | You want a maintenance history attached to the Asset record |
Examples: pre-opening walkthrough, end-of-day clean, daily restroom check | Examples: ride pre-flight, asset-specific PM, manufacturer-recommended inspection |
Best practice: When in doubt, target the most specific scope that still makes sense. Asset-targeted work generates richer maintenance history and supports MTBF/MTTR reporting at the equipment level. Location-targeted work is fine for general operations but loses that per-equipment fidelity.
Create an Asset-driven Schedule
Asset-driven Schedules work the same way as Location-driven Schedules. The only difference is what you select in the Targets field during configuration.
Navigate to Schedules
From the Mobaro Backend, navigate to Schedules.
Click Create and choose a Schedule type
Click + Create and choose the Schedule type that fits the cadence:
Calendar Schedule — for time-bound, recurring inspections (e.g., daily pre-opening on a specific roller coaster).
Continuous Schedule — for inspections available on demand whenever the Asset is in use.
Ad Hoc Slot — for a one-off inspection of a specific Asset on a specific date.
Configure the Schedule with the Asset as Target
In the Configure Schedule section, fill in the required fields:
Title — name the Schedule descriptively (see naming below).
Checklist(s) — the Checklist(s) the Schedule will publish.
Target Type — select Assets as the Target Type to scope the inspection.
Target(s) — select the Location (or multiple Locations) and then select the Asset (or multiple Assets) the Schedule applies to.
Assignee(s) — Users or User Groups responsible for completion.
Save
Click Save and add time slots, Patterns, or master Calendars as needed for the Schedule type.
Note: A single Schedule can mix Target types — Locations, Assets, and Location Groups can all be selected on the same Schedule. The Checklist will publish for each Target individually.
Tip: After configuring an Asset-driven Schedule, use Schedule Metrics to verify that the assignees, the Asset's Location, and Role permissions are aligned correctly. Misaligned access is the most common reason an Asset-driven Schedule fires but no one sees the work.
See also: How to schedule a Checklist covers Schedule types, time slots, master Calendars, Patterns, and Exclusions in full detail.
Create an Asset-driven Assignment
Asset-driven Assignments target a specific piece of equipment for a one-time piece of work — a repair, an upgrade, a follow-up from a failed inspection.
Navigate to Assignments
From the Mobaro Backend, navigate to Assignments.
Click Create
Click + Create.
Configure the Assignment
Assignment Definition — the type of Assignment (work order, repair, follow-up, etc.).
Title and Description — describe the work.
Target — select the Location and then select the Asset the Assignment applies to.
Assignee — the User or User Group performing the work.
Deadline, Priority, and any other fields the Assignment Definition specifies.
Save
Click Save. The Assignment appears in the assignee's queue and is now visible in the Asset's history.
See also: How to create and delegate an Assignment covers the full Assignment creation flow including delegation, owners, and reviewers.
Visibility rules for Asset-driven work
Two visibility rules govern Asset-driven Schedules and Assignments. Both must be satisfied for an Assignee to see and act on the work:
The Assignee has access to the Asset's Location. Asset access flows through Location access. A User without access to the Location cannot see Schedules or Assignments targeting Assets at that Location, regardless of any other setting.
The Assignee's Role grants the relevant operation — viewing or completing Checklists, modifying Assignments, etc.
Watch out: When you assign work directly to a User who does not have access to the Asset's Location, the Assignment is created but the User cannot see it. This is the single most common cause of "I assigned this and they say they can't find it." Either grant Location access via a User Group or assign the work to a User who already has access.
Asset history and reporting
One of the strongest reasons to target Assets directly is the maintenance history that builds up on each Asset record. Over time, an Asset accumulates:
Every Result from completed Checklists targeting that Asset.
Every Assignment created against the Asset, completed or open.
Inspection deviations, photo evidence, and notes attached to past work.
Best practice: When you stand up a new Asset, set up its recurring Checklists as Asset-driven Schedules from day one. Backfilling history is hard; building it in real time is automatic. The maintenance record you'll have a year from now depends on the targeting decisions you make today.
Naming Asset-driven Schedules and Assignments
Asset-driven items benefit from a naming pattern that includes the Asset reference, since they will appear alongside Location-driven items in the same lists:
[Cadence] – [Asset reference] – [Type of work]
Examples:
Daily – Coaster A – Pre-opening InspectionWeekly – Pump Station 3 – Filtration CheckPM – Generator B – 500-hour ServiceAnnual – Lift Hill 2 – NDT Inspection
Anti-patterns to avoid
Watch out for these common Asset-driven Schedule and Assignment mistakes:
Targeting the Location when you mean an Asset — losing per-equipment history is hard to recover later. If the work is about a specific piece of equipment, target the Asset.
Targeting the Asset when you mean the Location — for area-wide work that doesn't depend on equipment, Location targeting is simpler and easier to maintain.
Assignees without Location access — the work fires but no one sees it. Audit access via Schedule Metrics before going live.
One Schedule covering many unrelated Assets — if the Checklist or cadence differs across Assets, you'll end up editing the Schedule constantly. Split into separate Schedules.
See also
Creating an Asset — the create flow for Assets.
Linking Assets to Locations — for the scoping relationship that drives Asset visibility.
How to schedule a Checklist — for the full Schedule creation walkthrough.
How to create and delegate an Assignment — for the full Assignment creation walkthrough.
Using Assignment Definitions — for restricting which Groups can create or be assigned specific kinds of Assignments.
Frequently asked questions
Q: Can a single Schedule target both Locations and Assets?
A: No. The Targets field on a Schedule ensures you define either Locations and Location Groups or Assets. The Schedule publishes the Checklist for each Target individually.
Q: Do Asset-driven Schedules support all the same features as Location-driven Schedules?
A: Yes. Compliance settings, master Calendars, Patterns, Exclusions, Reminders, and Grace Periods all work the same way regardless of Target type.
Q: When the same Checklist runs against both an Asset and its Location, do I get duplicate work?
A: Yes — each Target generates its own instance. If you don't want both, pick one Target type for that Schedule.
Q: If I move an Asset to a new Location, do active Schedules continue to fire?
A: Not unless the new Location is already scoped as a Target within the Schedules. Assignees who lost access via the move will stop seeing the work.
Q: Can I see all open Assignments for a specific Asset?
A: Yes. Open the Asset record to see its Assignment history, both open and completed. Reports and Dashboards can also be filtered to a specific Asset.