Overview
A Downtime Template prefills a Downtime's description and categories in RideOps. Its Assignment Creation Policy determines whether an Assignment is created and therefore whether the Downtime is Blocking. Use templates for recurring stops, such as a weather hold or technical stop.
Downtime Templates are a RideOps feature: the Mobaro app and the Backend don't offer them. In RideOps they're also the only way to give a Downtime a category, because the RideOps Downtime dialog has no category picker.
At a glance |
|
Who can do this | Super Users, or a Role with Organization › Administrate |
Where | Configuration › Downtime › Downtime Template |
Works on | Backend (web) to set up; RideOps to use |
Availability | All organizations |
Downtime Template settings
Setting | What it does | Default |
Name | The button label Operators see in RideOps. Required | Empty |
Description | Pre-fills the Downtime description. The Operator can change it before starting | Empty |
Downtime Category | The categories the Downtime gets. You can pick several. Required when your Downtime categories are set to Required | None |
Limit to | The Locations or Location Groups where the template appears. Leave empty for every RideOps Location | Empty (all) |
Color | The colour of the template's button in RideOps. Required | None |
Assignment Creation Policy | Inherit, Create or Do not create: whether the Downtime gets an Assignment | Inherit |
Create a Downtime Template
1. Open Configuration › Downtime
In the Backend, go to Configuration and open the Downtime tab. Templates are in the Downtime Template table, next to the Downtime categories and Downtime Settings. Click + (Create Template).
2. Fill in the General tab
Enter the Name at the top of the dialog. On the General tab, add the Description, pick the Downtime Category, set Limit to if the template only applies to some rides, and choose a Color.
3. Choose the Assignment Creation Policy
Open the Assignment Configuration tab and pick the Assignment Creation Policy. If you pick Create, choose the Assignment assignee (User Group) (required) and, where offered, the Assignment's type, priority and categories.
4. Save the template
Click Ok. The template appears in the table and in RideOps for the Locations it applies to.
How the policy decides Blocking
Policy | What happens when an Operator starts the Downtime |
Inherit | Follows Create an assignment when a new downtime is started in Downtime Settings. On: an Assignment is created with those settings and the Downtime is Blocking. Off: no Assignment; the Downtime is Open. |
Create | An Assignment is always created with the template's settings. The Downtime is Blocking: the ride can't reopen until the Assignment is resolved or the Downtime is closed in the Backend. |
Do not create | No Assignment is created. The Downtime is Open (non-blocking). |
The Assignment is named after the Location and the Downtime description. A RideOps Downtime started without a template follows Create an assignment when a new downtime is started. For the Downtime states and settings, see Using downtime in Mobaro and How to Get Started with Downtime in Mobaro.
What Operators see in RideOps
When an Operator starts a Downtime, RideOps lists the Location's templates under Templates as coloured buttons. Tapping a template selects it and fills in Description, which the Operator can still edit; tapping it again clears the choice. Start downtime starts the Downtime and closes the ride.
|
 |
With Create, RideOps tells the Operator the ride can't reopen until qualified staff resolve the Assignment. With Do not create, the Operator can tap Resolve downtime or Reopen ride only if Allow RideOps operator to resolve non blocking downtime is on in Downtime Settings.
⚠️ Heads-up: With that setting off, a Do not create Downtime still keeps the ride closed in RideOps: the Operator is asked to contact an administrator, who resolves it by opening the Location in the Backend or the Mobaro app.
Edit, reorder or delete templates
Edit: select a row and click Edit Template. Changes apply to Downtimes started afterwards.
Reorder: drag the rows, then click Save Order. RideOps shows the buttons in this order.
Delete: select a row and click Delete Template. It disappears from RideOps. Downtimes already started from it keep their description and categories.
Categories: renaming a Downtime category updates every template that uses it; deleting one removes it from every template.
🛑 Critical: Delete Template deletes the template straight away, with no confirmation and no undo. To take a template out of use for some rides only, change Limit to instead.
Best practices
Give every template a Downtime Category; in RideOps it's the only way a Downtime gets one.
Use short, consistent names so Operators find the right button fast, such as Lift stop – high and Lift stop – low.
Use Create for stops that always need maintenance sign-off, and Do not create for weather holds and planned pauses.
If you use Do not create, turn on Allow RideOps operator to resolve non blocking downtime so Operators can reopen the ride.
Put the most-used templates first with Save Order.
Frequently asked questions
How do I set downtime categories in RideOps?
With Downtime Templates. The RideOps Downtime dialog has no category picker, so give each template a Downtime Category. A Downtime started without a template has no category; add one in the Backend when you close it. See Using downtime in Mobaro.
How do I set up a blocking downtime template?
Set the template's Assignment Creation Policy to Create and choose the Assignment assignee (User Group). Every Downtime started from it gets an Assignment, so the ride can't reopen until the Assignment is resolved or the Downtime is closed in the Backend.
Can I use downtime templates on the website or in the mobile app?
No. Templates only appear in RideOps. In the Mobaro app, Operators add a description and categories in the Start Downtime dialog. See Managing Downtime and uptime from the mobile app.
Operators can't reopen the ride after a non-blocking downtime. Why?
Allow RideOps operator to resolve non blocking downtime is off. Turn it on in Configuration › Downtime › Downtime Settings. Until then, an administrator reopens the Location from the Backend or the Mobaro app.