What They Do and How to Use Them
You can follow the text guide below or if you would like to see a more visual representation you can follow our Slideshow
Basic Function
Chekhub offers three different types of tickets to help with the planning and performing of operational and maintenance tasks. The different ticket types are easily defined by what types of operations they are meant to assist with.
- Ticket - A basic ticket that can be used for ad-hoc operations.
- Preventative Maintenance (PM) - Used to set a maintenance schedule for a specific asset on a recurring basis.
- Round - Used to set a scheduled task that occurs hourly or daily, such as a building walkthrough.
Additional information about each ticket type is available from the links below.
Which type of ticket do I use?
Each ticket type has its own unique strengths that allow it to better fit into different types of workflows. Preventative Maintenance or PM type tickets and Round type tickets are both recurring ticket types.
- Round type tickets are best suited to be used when creating frequent recurring tasks. Creating something such as a Daily Walkthrough as a Round will allow you to set the task to occur at the same time every day. So for example, having your Daily Walkthrough occur every day at 11am when you have a shift change will ensure that this task happens before every shift begins. Rounds also use their own type of checklist that is created for a specific asset and location.
- PM type tickets also can be used to set a task to occur on a certain time period, but these are best suited for tasks that happen on a longer term basis, such as monthly. For example, if you have an asset that undergoes monthly maintenance, creating a PM type ticket will allow you to ensure that it happens during the correct time periods. Unlike our round Daily Walkthroughs, this task does not need to happen at an exact time, but on more generalized days or weeks.
- Issue type tickets are better suited for individual tasks that do not reoccur on a set time interval. These are best suited for individual or ad-hoc tasks. For example, you may create an Issue type ticket for a new round of computer upgrades. This is not something that happens frequently so it will only require a singular ticket.