IBM C1000-132 IBM Maximo Manage v8.0 Implementation Exam Practice Test

In the Work Order Tracking application, when a Work Order is generated from a Preventive Maintenance (PM) record, the target finish date is calculated as the Work Order target start date + the Job Plan duration.

The Hazards application in IBM Maximo Manage v8.0 allows users to associate Material Safety Data Sheets (MSDS), Hazardous Materials, and Precautions with a particular hazard. These associations help in managing safety information related to hazards and in ensuring compliance with safety regulations.

In IBM Maximo Manage, if a Purchase Order is not being revised, two statuses that will allow a receipt of new items to be processed in the Receiving application are APPR and INPRG.

It works on both locations and assets. https://maximosecrets.com/2020/08/17/item-and-locations/ and https://maximosecrets.com/2020/08/03/item-specifications-for-rotating-items/

https://www.ibm.com/support/pages/creating-service-request-categories-and-category-options-service-request-work-center#:~:text=In%20the%20Service%20Request%20Work%20Center%2C%20an%20administrator,Object%20parameter%20and%20Asset%20parameter%20set%20to%20SR .

In IBM Maximo Manage v8.0, Service Request Categories for the Service Request Work Center can be created in the Administration Work Center and through the Classifications Application:

Administration Work Center: The Service Request Configuration section within the Administration Work Center enables administrators to set up and customize service request categories specifically for use in the Service Request Work Center. This involves defining properties, categories, and issues users select when creating service requests​

​

Classifications Application: Categories are also managed by setting up classifications associated with service requests in the Classifications application. When a classification is created with associations to the "Asset" and "SR" (Service Request) objects, it becomes available as a category option in the Service Request tool. This approach allows issues to be assigned to specific categories using ticket templates tied to classifications​

​

These configurations provide a structured way to set up service categories that enhance service request management by ensuring users select relevant, predefined options during request creation.

One licensing method used to obtain the Maximo Asset Suite is a Cloud based license.

In IBM Maximo Manage, two records that can be included as a contract line item on a Lease/Rental Contract are a Rotating item and an Asset.

When you create a labor record in IBM Maximo Manage v8.0, you enable a person to report time against a work request1. Before you create a labor record, you must create a corresponding person record1. A person record is defined at the System level and when a person works across multiple organizations, they need multiple Labor records linked to the same Person record2.

In the IBM Maximo Automation Scripts application, several types of launch points can be configured to trigger scripts, including Integration launch points. The supported launch points in Maximo are:

Object Launch Point: Triggers on events related to specific objects (MBOs), such as creation, modification, or deletion​

​

Attribute Launch Point: Triggers when specific attributes within an MBO are accessed or modified​

​

Action Launch Point: Executes custom actions, often triggered by workflows or escalations, allowing for automation without custom Java code​

​

Condition Launch Point: Activates when a defined condition is met, commonly used for security or workflow condition logic​

Integration Launch Point: Designed specifically to interact with Maximo Integration Framework (MIF) components, including publish channels, enterprise services, and invocation channels. This enables automation scripts to respond to data exchanges between Maximo and external systems, making it a powerful tool for integration-related automations​

​

The Integration launch point is thus the correct answer as it allows scripts to be triggered by data flow events through MIF.

Apart from Standard and Average costing methods in IBM Maximo Manage’s Inventory application, three other costing methods that can be used are FIFO (First In First Out), LIFO (Last In First Out) and Weighted Average.

The default status in the Quick Reporting Application in IBM Maximo Manage is DRAFT.

In the Purchase Requisitions application with default settings in IBM Maximo Manage, when all lines of a Purchase Requisition have been copied to a Purchase Order or a Contract, the status of the Purchase Requisition changes to COMPLETE.

Two of the filters in the Select Value of a Location or Asset in the Service Requests application in IBM Maximo Manage are Service Address and Service Group/Services

https://www.ibm.com/support/pages/maximo-support-desk-change-default-filter-asset-lookup-create-service-request-application

In IBM Maximo Manage v8.0 implementation, the usage types in the Inventory Usage application are ISSUE, STAGED, and TRANSFER. ISSUE is used to relieve items from inventory for use in maintenance or other processes. STAGED is used to reserve items for future use. TRANSFER is used to move items from one inventory location to another, typically within the same organization.

The Organizations application is used to configure Flow Control for Work Orders. In this application, you can change the Start Status and Complete Status that will be used.

According to IBM Maximo documentation, SLAs can indeed be applied to various main objects beyond Work Order or Ticket Classes, including additional objects like assets, locations, and configuration items. This allows broader application across records where service level commitments need to be tracked

https://www.ibm.com/docs/en/maximo-for-aviation/7.6.1?topic=records-service-level-agreements-slas

In IBM Maximo Manage v8.0 implementation, the three default values used with the position of a Crew Type or Crew are Helper, Leader, and Apprentice. These values represent the different roles that members of a crew can assume.

In IBM Maximo Manage v8.0, the Master PM application is used to manage and control multiple Preventive Maintenance (PM) records through a central template known as the Master PM. The primary purpose of the Master PM application is to provide a standardized structure for PMs and streamline the maintenance process by enabling centralized updates to associated PM records.

The key updates that can be made to associated PMs through the Master PM application include:

Frequency and Scheduling Information - The Master PM can dictate the time- or meter-based frequency at which work orders are generated, and apply this to all associated PMs (or selectively if desired)​

Job Plans and Sequence - Users can specify job plans on a sequential basis, which helps in scheduling varied levels of maintenance activities. Changes to the job plan sequence in the Master PM can be propagated to all associated PMs​

​

Seasonal Dates - Active dates or seasonal adjustments to maintenance activities can be set up within the Master PM, and these adjustments can be transferred to associated PMs as necessary​

PM Hierarchy - The Master PM application allows users to configure and manage PM hierarchies, which helps in establishing parent-child relationships among PM records. This hierarchical structure is especially useful in organizing maintenance tasks for complex assets with interrelated components, ensuring that all relevant maintenance tasks are triggered appropriately​

​

Thus, option D (PM Hierarchy) correctly represents the feature that can be updated in the Master PM application for associated PM records.

In the Meters application, the three meter types are GAUGE, CHARACTERISTIC, and CONTINUOUS. GAUGE meters measure a discrete value or range of values, such as the oil pressure in an engine. CHARACTERISTIC meters measure a specific attribute of an asset, such as the temperature of an engine. CONTINUOUS meters track usage or consumption over time, such as the number of hours an asset has been in operation.

To associate a Master Preventive Maintenance record with multiple non-rotating assets, we can add the assets to the Multiple Assets table on the Master Preventive Maintenance record. This allows us to associate the preventive maintenance schedule with multiple assets, ensuring that the maintenance activities are performed on each of the associated assets as scheduled.