Category: Service Management

  • Ticket Templates

    Ticket Templates

    Learn how a Ticket Template can be used to default fields for a Service Request. We start with an introduction to Tickets and finish with how a Ticket Template can be applied through the Quick Insert Portlet on a Start Center or via the Quick Actions card on the Operational Dashboard.

    Read more: Ticket Templates
  • Service Groups

    Service Groups

    Learn about Service Groups where they are used across Maximo and how they can be used to relate similar Service Requests (tickets).

    Read more: Service Groups
  • Ticket Communications (3)

    Ticket Communications (3)

    Contents This is the last of the three articles on Ticket Communications and will focus on the Communication Templates and Roles provided for Tickets in the out of the box Maximo system. The illustrations will show two of the Global Ticket Communication Templates in action, one for Incidents and one for Problems, which can be…

    Read more: Ticket Communications (3)
  • Ticket Communications (2)

    Ticket Communications (2)

    Contents This is the second article of three reviewing the functionality behind the Create Communication action on the ticket-based applications. The first article introduced the Create Communication dialog and the three tabs that you get when you open the To field’s Select Value to look up a recipient of the email. In the article we…

    Read more: Ticket Communications (2)
  • Ticket Communications (1)

    Ticket Communications (1)

    Contents This is the first of three articles on Ticket Communications, and they focus on the Create Communication action in the Ticket based applications. The articles do discuss a bit about Roles and Communication Templates but only to see how they are applied, there is scope for other articles on those two applications. To help…

    Read more: Ticket Communications (1)
  • Work View

    Work View

    Contents The Work View is not a database view but an application in Maximo with some surprisingly special capabilities for an application that does not allow inserts, updates or deletes. The Work View was designed to provide a single view of all the tickets and work orders that a user is responsible for or where…

    Read more: Work View
  • Solutions

    Solutions

    Contents Solutions are used as a knowledge base and can be searched by end users from the Self-Service module. This article will cover all aspects associated with Solutions. Solutions Application In the article on Incidents and Problems we used the Create Solution action to create solution 1047 at DRAFT status. You cannot see which record…

    Read more: Solutions
  • Incidents and Problems

    Incidents and Problems

    Contents When I started this article, I had wondered whether to make the title Corrective Action and Preventive Action (CAPA) instead. The two applications are called Incidents and Problems, and so I decided to stick with that. I have also used this article to discuss the Duplicate and Delete actions. Incidents – Corrective Actions, Problems…

    Read more: Incidents and Problems
  • Ticket Time Tracking

    Ticket Time Tracking

    Contents This article will first look at recording time against the Service Request. However, you can also record time against the activities of a ticket, therefore we will follow with recording time against an Incident. The Incidents application has an Activities tab, the Service Requests application while supporting activities, does not have an Activities tab. …

    Read more: Ticket Time Tracking
  • Status Inheritance on Tickets

    Status Inheritance on Tickets

    Contents There are three scenarios where the status could be inherited on a ticket. A ticket can have one or more activities and like there is a rolldown of statuses from a parent work order to its children there is a rolldown of the ticket status to child activities. To remind ourselves of the different…

    Read more: Status Inheritance on Tickets