Overview
A maintenance stop can involve three separate actions: resolving the maintenance Assignment, reopening the Location and closing the Downtime record. Agree who owns each action so none is mistaken for the others.
Follow your site’s return-to-service procedure throughout. A status change in Mobaro records an action; it does not replace the required inspection or authorization.
At a glance |
|
Who can do this | Authorized Assignment resolvers, eligible RideOps Operators, and Operations › Manage Downtime for the final record review. |
Where | RideOps, Assignments and Downtime |
Works on | RideOps, Backend (web), Mobile app |
Availability | Contact your CSM for RideOps access |
💡 Why this matters: A clear handoff lets maintenance record the repair, operations check readiness and the reporting owner confirm the interruption’s duration.
Confirm the stop and work
1. Identify the blocking Downtime
When the fault occurs, record it using the configured Downtime workflow and check whether an Assignment is linked. A linked Assignment makes the Downtime blocking. Include the fault description and any required evidence in the appropriate records.
Use the configured Downtime template rather than assuming every category creates a task. Template Assignment creation policy determines that behavior. See Downtime templates.
Complete the maintenance handoff
2. Resolve the work and confirm the state
The authorized person completes the work and records the resolution, evidence and any required supervisor sign-off. Follow the Assignment Definition’s allowed status transitions. See resolving Assignments.
Resolving the linked Assignment changes its blocking Downtime to Resolved. This does not itself open the Location, and it does not confirm the final Downtime duration.
Tell the Operator what changed.
Use your site’s handover process to communicate the repair and any restrictions or follow-up checks. If your setup uses mandatory handover notes, the Operator must also acknowledge the relevant note. See handover notes.
Check readiness and reopen
3. Refresh and check the remaining requirements
The Operator refreshes RideOps and checks the current readiness information, required Checklists, staffing Positions and other blocking work. Reopen only when those requirements and your site’s authorization are satisfied.
For a non-blocking Downtime, the organization setting controls whether Operators can resolve it in RideOps. Depending on readiness, RideOps may offer to resolve it or resolve and reopen. This is not a per-category permission. See the Operator workflow.
🛑 Critical: Do not use Close Downtime merely to bypass an unresolved maintenance Assignment. Closing the record removes that Downtime’s block while leaving the Assignment active; other readiness checks may still apply.
Close the reporting record
4. Confirm Actual Downtime and close the record
The reporting owner opens the Downtime in the Backend and chooses Close Downtime. Check the actual interruption, categories and Actual Downtime, including the effect of configured opening hours. Record the agreed duration and close it.
Closing is a separate administrative action from resolving the fault. The Operational History Details widget includes closed Downtimes; leaving the record resolved but unclosed leaves the reporting review unfinished. Use the Downtime lifecycle guide for the full state and editing reference.
Best practices
Name the maintenance, operating and reporting owners in your procedure.
Review the linked Assignment and Downtime together.
Check the first post-repair operating period and complete the record review promptly.
Frequently asked questions
Can an Operator resolve every Downtime in RideOps?
No. The organization setting applies to non-blocking Downtime. A blocking Downtime follows the linked Assignment workflow. See template policy and your site’s authorization procedure.
Is Resolved the same as Closed?
No. Resolved records the end of the interruption, such as resolution of the linked Assignment. Closed confirms the Downtime record and its duration. Resolving an Assignment does not itself reopen the ride.
How do I make a fault block reopening?
Configure a Downtime template to create an Assignment, following your organization’s setup. The linked Assignment makes it blocking; a category name alone does not. See creating a blocking template.