Latest Articles

  • Maximo Applications (4 of 5)

    Service Level Module Application Description Service Level Agreements A service level agreement (SLA) is most commonly applied to a type of ticket or work order. An SLA can have multiple commitments and when applied to a ticket or work order these create target dates. An escalation can be set-up to monitor progress against the commitment…

    Read more: Maximo Applications (4 of 5)
  • Maximo Applications (3 of 5)

    Preventive Maintenance Module Application Description Preventive Maintenance The Preventive Maintenance (PM) application is used to create a template for routine maintenance or inspection of an asset, location or a set of assets defined with a route. The frequency in which the work orders are generated can be time or meter based or a mix of…

    Read more: Maximo Applications (3 of 5)
  • Maximo Applications (2 of 5)

    Financial Module Application Description Currency Codes A single page application used to define a currency code and its description. A currency code must be defined before you can define an organization, an organization can have two base currencies. Exchange Rates An exchange rate is defined between two currencies for a particular organization. An exchange rate…

    Read more: Maximo Applications (2 of 5)
  • Maximo Applications (1 of 5)

    Administration Module Application Description Sets A set is used to share data across multiple organizations. There are two types of set, item and company. Organizations This is the application where organizations and sites are defined and where there are options for how Maximo functions at system, organization and site level. An organization provides data sharing…

    Read more: Maximo Applications (1 of 5)
  • Responsibilities on Job Plans, PMs and Work Orders

    The responsibility fields exist on job plans, PMs and work orders but when a job plan or a PM is applied to a work order what are the defaulting rules on the work order?

    Read more: Responsibilities on Job Plans, PMs and Work Orders
  • Person Groups

    A Person Group is a collection of people and is used in various places throughout Maximo but was originally created to support Workflow.

    Read more: Person Groups
  • Ticket and Work Order Ownership

    The responsibility for a ticket or work orders can be assigned or a Maximo user can take ownership. The owner performs an administrative function to ensure that the ticket is reviewed or investigated and the work order is executed successfully. The owner need not be the person who executes the work order. The owner of…

    Read more: Ticket and Work Order Ownership
  • Job Plan Revisions

    Job Plan revisions became available with the release of Maximo 7.5 and with it the extension of the number of statuses. The initial revision number is zero. The action Revise Job Plan opens a dialogue box with the next revision number completed. A Revision Description is a mandatory attribute, it can have a long description.…

    Read more: Job Plan Revisions
  • Routes

    Routes are most often used with inspections. They consist of a set of locations or assets with a sequence that defines the order in which the inspection will take place, each record in the set is known as a Route Stop. Routes can be applied directly to a work order using the action Apply Route…

    Read more: Routes
  • Multisite Considerations

    There are several considerations to bear in mind when defining whether Maximo should have multiple Organizations or multiple Sites. Bear in mind that one organization and one site is the simplest data model to follow, multiple organizations and sites will add complexity and you should be aware of what you can and can’t do in…

    Read more: Multisite Considerations
  • Organizations and Sites

    The definition of Maximo Organizations and Sites will be one of the most important design decisions you will make during a Maximo implementation. To make a good decision you need to consider your future use of Maximo. For example, if you have a multi-phase project with an integration to a finance system to be performed…

    Read more: Organizations and Sites
  • Inheriting Service Addresses

    Locations and assets can inherit their service address. The starting point is to define a location system as an Address System, this is performed using the action Manage Systems in the Locations application. Only one location system per site can be nominated as the address system and it must be a hierarchical system it cannot…

    Read more: Inheriting Service Addresses
  • Service Address Options

    In Organizations application the action Service Address Options opens a dialogue box that can be used to change settings that effect the behaviour of service addresses, these are defined at the organization level.

    Read more: Service Address Options
  • Service Address

    A Service Address is used to represent a physical location where labor or crews are sent to perform work. The ship to, bill to, or other types of address used in the Supply Chain applications are not service addresses, these are addresses defined in the Organizations application.

    Read more: Service Address
  • Crew Types – Overview

    Crew Types is a template for Crews. A crew defines the labor and assets with specific craft-skill levels and qualifications needed to perform work. A crew type then is the required craft-skills, qualifications and tools that will need to be fulfilled by the members of a crew. Crew types are defined at the organization level…

    Read more: Crew Types – Overview