Repair tickets in RAMP are used to report faults, request maintenance, and track repair progress for systems and assets within a garage.
Follow the steps below to correctly create a repair ticket.
Step 1: Navigate to the Tickets Section
Log in to RAMP.
From the main menu, go to Tickets.
Click Create New Ticket.
This will open the ticket creation form.
Ticket Fields Explained
When creating a repair ticket, you must complete several required fields. Each field ensures the issue is routed correctly and contains enough information for the vendor to act efficiently.
Step 2: Enter a Ticket Name
In the Ticket Name field:
Enter a short, clear, and descriptive name.
The title should summarise the issue at a glance.
Best practice examples:
“Roller Door 3 not closing fully”
“Wash Bay Pressure Loss”
“Boom Gate Intermittent Fault”
Avoid vague titles like:
“Door issue”
“Broken”
“Problem”
A clear ticket name helps with tracking and reporting later.
Step 3: Select the Relevant Garage
Choose the correct Garage from the dropdown list.
This ensures:
The issue is logged against the correct site.
The appropriate contacts and vendors are notified.
Reporting remains accurate.
If the wrong garage is selected, notifications and repair tracking may be impacted.
Step 4: Select the Relevant System and Asset (If Applicable)
Next, select:
The relevant System (e.g., Doors, Lighting, Access Control, Wash Bay, etc.)
The specific Asset, if the issue relates to a particular item
If the issue affects a specific asset (e.g., Door 4, Payment Terminal 2), always select that asset.
If the issue is system-wide, selecting only the system may be sufficient.
This helps:
Vendors understand exactly what is affected
Maintenance history remains accurate
Asset-level reporting stays consistent
Step 5: Review Assigned Contacts
Before submitting the ticket, review the Assigned Contacts section.
These contacts are typically drawn from configured contact groups.
Important:
Contact groups selected on the ticket will be notified when the ticket is created.
Notifications to those contacts depend on how the system has been configured.
This may include:
Maintenance teams
External vendors
Always confirm the correct stakeholders are included before proceeding.
Step 6: Set Issue Type, Priority, and Due Date
Complete the classification fields:
Issue Type
Select the type that best describes the problem (e.g., power outage, damage).
Priority
Choose the appropriate priority level based on urgency and impact.
For example:
High – Operations severely impacted or site unable to function properly.
Medium – Partial disruption.
Low – Minor issue with limited operational impact.
Due Date (Optional)
Set a due date if:
The issue requires resolution by a specific deadline.
If no specific deadline exists, this may be left blank.
Step 7: Add a Clear Issue Description
In the Issue Description field:
Provide enough detail for the vendor to understand the issue without needing follow-up clarification.
Include:
What is happening
When it started
Frequency (constant or intermittent)
Any error messages
Any troubleshooting already attempted
Safety concerns (if applicable)
Example of a strong description:
“Roller Door 3 is stopping halfway when closing. Issue began this morning at approximately 7:30am. The door opens fully but does not close without manual override. No visible obstruction. Site team has power cycled the system with no change.”
Final Review and Submission
Before clicking Create Ticket, confirm:
Ticket name is clear
Correct garage is selected
System and asset are accurate
Contacts are appropriate
Priority level is correct
Description is detailed and helpful
Then click Create Ticket to submit.
Once submitted:
Selected contact groups will be notified (depending on notification settings).
The ticket will enter the workflow for tracking and resolution.
Best Practice Summary
To raise an effective repair ticket in RAMP:
Be specific.
Select the correct garage, system, and asset.
Use priority appropriately.
Provide detailed descriptions.
Confirm the correct contacts will be notified.