Latest Articles

  • Roles

    Roles

    A role is a pointer that resolves to a person or team, a person group. For example, the person who reports a service request, the buyer of a purchase order, the team responsible for safety, etc. Once it has found a person or team Maximo can derive an email address and use this in email…

    Read more: Roles
  • Ticket Communications (3)

    Ticket Communications (3)

    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 used…

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

    Ticket Communications (2)

    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 showed…

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

    Ticket Communications (1)

    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 you…

    Read more: Ticket Communications (1)
  • Work View

    Work View

    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 they…

    Read more: Work View
  • Solutions

    Solutions

    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 created…

    Read more: Solutions
  • Incidents and Problems

    Incidents and Problems

    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

    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.  Time…

    Read more: Ticket Time Tracking
  • Status Inheritance on Tickets

    Status Inheritance on Tickets

    There are three scenarios where the status could be inherited on a ticket. Inherit Status from a Follow-up Ticket Inherit Status from a Global Issue Inherit Status from a Follow-up Work Order A ticket can have one or more activities and like there is a rolldown of statuses from a parent work order to its…

    Read more: Status Inheritance on Tickets
  • Service Level Agreements (4) – Related SLAs

    Service Level Agreements (4) – Related SLAs

    This article will show how we can have one SLA supporting another. For example, a customer SLA may have multiple supporting SLAs, these may be of type INTERNAL, an Operational Level Agreement, or of type VENDOR, an underpinning agreement. There is nothing stopping one Customer SLA supporting another Customer SLA, but this would be less…

    Read more: Service Level Agreements (4) – Related SLAs
  • Service Level Agreements (3) – Applying Multiple SLAs

    Service Level Agreements (3) – Applying Multiple SLAs

    This is the third article in a series on the Service Level Agreements application. The first two in the series: Introduced SLAs and showed how you could manually apply them to a Service Request. You can find the article here: http://maximosecrets.com/2021/11/08/service-level-agreements-1-an-introduction/ Discussed the SLA filter criteria and matching process that applies a single SLA to…

    Read more: Service Level Agreements (3) – Applying Multiple SLAs
  • Service Level Agreements (2) – Applying a Single SLA

    Service Level Agreements (2) – Applying a Single SLA

    This is the second article in the series on Service Level Agreements. In this article we look at the filter criteria and matching process when applying a single SLA to a Service Request (SR). You can find the first article where we manually applied SLA 1029 to Service Request 1307 here: http://maximosecrets.com/2021/11/08/service-level-agreements-1-an-introduction/ SLA Filter Criteria…

    Read more: Service Level Agreements (2) – Applying a Single SLA
  • Service Level Agreements (1) – An Introduction

    Service Level Agreements (1) – An Introduction

    The Service Level Agreements (SLA) application is a powerful application but can be a bit difficult to understand. Then there are two versions the one you get in base Maximo and the one which Maximo for Service Provider clients use, which is the one embedded in other Maximo products like Maximo for Aviation or IBM…

    Read more: Service Level Agreements (1) – An Introduction
  • Service Requests – Multiple Assets

    Service Requests – Multiple Assets

    The Service Request application can reference multiple assets, locations, and configuration items (CIs). This article reviews this feature, and what you can do with the records once they have been added. Using the New Row on the Multiple Asset, Location and CIs table For this scenario I have created a new Service Request 1301 with…

    Read more: Service Requests – Multiple Assets
  • Service Request – Work Logs

    Service Request – Work Logs

    This article will look at three scenarios to show that by default work log records are visible in other applications than the one they were created in. Creating a Log Note from View Service Request In a previous article REDDING – Tony Redding created a service request 1273, we can see this in the Self-Service…

    Read more: Service Request – Work Logs