C1000-132 Practice Questions

IBM Maximo Health is the application specifically designed to help organizations manage the health of their assets and make strategic decisions about maintenance and replacement. It consolidates asset data, calculates health scores based on various factors (age, condition, maintenance history), and uses this information to identify at-risk assets. A core capability of Maximo Health is its investment optimization feature, which allows users to create and generate long-term plans for repairing or replacing assets to maximize budget effectiveness and minimize risk.

A. Maximo Predict: This application uses AI to predict asset failures. It provides crucial data for a replacement plan but does not generate the strategic plan itself.

C. Maximo Health, Safety and Environmental (HSE): This is an add-on focused on managing safety protocols, incident reporting, and environmental compliance, not strategic asset replacement planning.

D. Maximo Manage: This is the core CMMS/EAM for managing work orders and asset data. It executes the replacement work but lacks the advanced health scoring and investment planning tools to generate the plans.

1. IBM Documentation for Maximo Application Suite, Maximo Health, "Planning for asset replacement." This document explicitly states, "In the Maximo Health application, you can create plans to identify the assets that you want to repair or replace. You can also use investment optimization to determine the best course of action for your assets."

2. IBM Documentation for Maximo Application Suite, Maximo Health, "Overview of Maximo Health." This overview confirms the application's purpose: "You can use Maximo Health to understand asset performance and to plan for replacement or refurbishment."

3. IBM Documentation for Maximo Application Suite, Maximo Predict, "Overview of Maximo Predict." This source details that Predict's function is to "use artificial intelligence (AI) to optimize asset management and improve reliability by creating predictive models for asset failure." This confirms it provides input to, but does not create, replacement plans.

When changing the status of a location in IBM Maximo to DECOMMISSIONED, the system presents a dialog box with an option to "Roll New Status down to All Assets in All Changed Locations?". This feature allows an administrator to apply the same decommissioned status to all assets residing within that location and its hierarchy simultaneously. This is a unique function of the location decommissioning process because locations act as containers for assets. This option is not available when decommissioning a single asset, as an asset does not hierarchically contain other assets in the same manner.

B. Remove All Reference to This Location from All Contracts?

Decommissioning does not automatically purge historical or contractual references for either locations or assets; this is a separate data cleanup activity.

C. Remove All References to This Location from All Job Plans?

Changing a location's status does not automatically update or remove references from existing Job Plan records; it only prevents its use on new work orders.

D. Delete Associated Service Addresses That will be made Redundant?

The decommissioning process for a location does not include an option to automatically delete its associated service address record, even if it becomes redundant.

1. IBM Maximo Manage 8.7 Documentation, "Changing the status of locations": This official documentation describes the process of changing a location's status. It explicitly details the dialog box option: "If you want to apply the status change to all assets in the location, select the Roll New Status down to All Assets in All Changed Locations? check box." This confirms the action is specific to the location status change process.

2. IBM Maximo Manage 8.7 Documentation, "Changing the status of an asset": This document outlines the procedure for changing an asset's status. The description of the process and the associated dialog box options do not include any feature to "roll down" a status, as this concept is not applicable to a single asset, thereby highlighting the difference from the location decommissioning process.

Admin mode is a specific operational state in IBM Maximo designed to allow administrators to apply database configuration changes without requiring a full shutdown of the application server. When Admin mode is enabled, it prevents non-administrative users from logging in and halts background processes (cron tasks). This ensures a stable environment for modifying the database schema, such as adding new objects or attributes, thus preventing data corruption while maintaining server uptime for the administrative task.

A. System Properties changes are typically applied using the "Live Refresh" action within the System Properties application, not by enabling Admin mode.

C. Changes made in Application Designer, such as modifying the user interface, are saved and applied directly without requiring the system to enter Admin mode.

D. This option is too general. While applying database changes is an administrative function, many other administrative tasks (e.g., user management) are performed during normal operation.

1. IBM Maximo Manage 8.6 Documentation, "Admin mode". This document states, "Admin mode is a system setting that you can use to make administrative changes to your system. When admin mode is on, you can make changes to the database configuration, but regular users cannot log in to the system."

2. IBM Maximo Manage 8.6 Documentation, "Configuring the database". In the "Before you begin" section, the first step listed is: "Turn on administration mode and stop the cron tasks." This directly links Admin mode to the process of database configuration.

The IoT Connector is an integration component within the Maximo Application Suite that enables applications like Maximo Manage, Health, and Predict to utilize IoT device data. It is specifically designed to connect to and pull data from two primary IoT data sources: IBM Maximo Monitor, which is the native IoT platform within the suite, and the IBM Watson IoT Platform, a cloud-based IoT service. This connection allows for the creation of work orders from device alerts, the calculation of asset health scores, and the generation of failure predictions based on real-time sensor data.

A. Maximo Spatial provides geospatial context and map-based visualization for Maximo assets; it is not an IoT data source for the connector.

B. Maximo Assist is an AI-powered guidance tool for technicians; it consumes asset data but does not serve as a primary IoT data source.

D. Maximo Safety is an application focused on worker safety using wearables and environmental sensors; it is a consumer of IoT data, not the foundational platform the connector pulls from.

1. IBM Maximo Application Suite Documentation - IoT Connector: "By deploying the IoT Connector application, you can integrate Maximo Manage with an IoT tool to pull in IoT device data... You can configure the IoT Connector to connect to an instance of IBM Maximo Monitor or IBM Watson IoT Platform."

Source: IBM Maximo Application Suite 8.10 Documentation, Home > Administering applications > Administering Maximo Manage > Integrating with other applications > Integrating with the IoT tool.

2. IBM Maximo Application Suite Documentation - Integrating with IBM Maximo Monitor: "You can configure the IoT Connector to connect to an instance of IBM Maximo Monitor that is deployed in the same Red Hat OpenShift cluster as Maximo Manage."

Source: IBM Maximo Application Suite 8.10 Documentation, Home > Administering applications > Administering Maximo Manage > Integrating with other applications > Integrating with the IoT tool > Integrating with IBM Maximo Monitor.

3. IBM Maximo Application Suite Documentation - Integrating with IBM Watson IoT Platform: "You can configure the IoT Connector to connect to an instance of IBM Watson IoT Platform that is hosted on IBM Cloud."

Source: IBM Maximo Application Suite 8.10 Documentation, Home > Administering applications > Administering Maximo Manage > Integrating with other applications > Integrating with the IoT tool > Integrating with IBM Watson IoT Platform.

To modify an active Job Plan in IBM Maximo, a user must initiate the "Revise Job Plan" action. This process creates a new revision of the Job Plan and sets its status to 'REVISED'. While in the 'REVISED' status, the Job Plan is fully editable, allowing users to add new tasks, modify existing ones, or make other necessary changes. Once the modifications are complete, the revised Job Plan can be activated, replacing the previous active version.

A. NEW: 'NEW' is not a standard, out-of-the-box status for Job Plans in IBM Maximo. The initial, editable status for a newly created Job Plan is 'DRAFT'.

C. INACTIVE: A Job Plan with an 'INACTIVE' status is retired. It cannot be modified or applied to new work orders. To edit it, its status must first be changed.

D. PNDREV: 'PNDREV' (Pending Revision) is a transitional status, often used in workflow, indicating the record is awaiting review. The record is typically read-only in this state.

1. IBM Maximo Manage 8.7 Documentation, "Job plan statuses": This official documentation outlines the lifecycle of a Job Plan. It explicitly states, "To change an active job plan, you must first create a revision of it. The new revision has a status of Revised. You can make changes to the revised job plan, and then change its status to active." This directly confirms that modifications occur in the 'REVISED' status. The document also lists the standard statuses as DRAFT, PNDREV, ACTIVE, REVISED, and INACTIVE, confirming 'NEW' is not a standard status.

Source: IBM. (2023). Job plan statuses. IBM Maximo Manage 8.7 Documentation. Retrieved from https://www.ibm.com/docs/en/mas-manage/8.7?topic=plans-job-plan-statuses

2. IBM Maximo Manage 8.7 Documentation, "Revising a job plan": This section details the procedure for modifying an active Job Plan. It specifies that the revision process places the new version in 'REVISED' status, where changes can be made.

Source: IBM. (2023). Revising a job plan. IBM Maximo Manage 8.7 Documentation. Retrieved from https://www.ibm.com/docs/en/mas-manage/8.7?topic=plans-revising-job-plan

In IBM Maximo Manage, the Data Sheet Template application is the designated location for creating and managing the detailed specifications required for asset calibration. This application allows users to define reusable templates that include asset functions, calibration points, setpoints, input/output ranges, and acceptable tolerances. These templates are then associated with specific asset records. When a calibration work order is generated for an asset, the information from the associated data sheet template is copied to the work order to guide the calibration process.

A. Classifications: This application is used to categorize assets and define general specification attributes, not the detailed, structured calibration points and tolerances found in a data sheet.

B. Asset: The Asset application is where a data sheet template is applied to a specific asset, but the specifications within the template are created and managed elsewhere.

D. Improvements: This application is part of the Maximo Health, Safety and Environment (HSE) Manager and is used for tracking improvement initiatives, which is unrelated to defining asset calibration specifications.

1. IBM Maximo Manage 8.7 Documentation, "Data sheet templates": "You use the Data Sheet Template application to create and manage data sheet templates. A data sheet template contains the calibration points and other information that is related to the performance and calibration of an instrument. You can apply a data sheet template to one or more asset records. When you generate a work order for an asset that has a data sheet template, the information from the template is copied to the work order." (Accessed under Maximo Manage > Managing assets > Calibration > Data sheet templates).

2. IBM Maximo Manage 8.7 Documentation, "Calibration overview": "You create data sheet templates that contain predefined specifications and apply them to assets. When a work order is generated for the asset, the data sheet is copied to the work order. The technician uses the data sheet to record the as-found and as-left readings." (Accessed under Maximo Manage > Managing assets > Calibration > Calibration overview).

In the IBM Maximo Manage Assets application, the "Copy Depreciation Schedules" action is used to duplicate one or more depreciation schedules from a source asset to other assets. This function is ideal for the scenario described, where a rebuilt engine (the new asset) needs to inherit the same depreciation plan as the used engine (the old asset) it is replacing. This action ensures consistency and saves time when multiple assets depreciate in the same manner.

A. Use the action Exchange Depreciation Schedules.

This action does not exist in Maximo. The term for a two-way exchange is "Swap," which serves a different purpose.

C. Use the action Swap Depreciation Schedules.

This action is used to correct data entry errors by exchanging the entire depreciation schedules between two assets, which is not the requirement here.

D. Use the action Split Depreciation Schedules.

This action is used when a part of an asset is sold or disposed of, dividing a single depreciation schedule into two separate schedules.

1. IBM Documentation for Maximo Manage 8.x:

Source: IBM Documentation, Maximo Manage, Managing assets, Depreciation schedules for assets.

Details: The section "Copying depreciation schedules" states, "You can copy one or more depreciation schedules from one asset to other assets. Copying depreciation schedules can save you time if you have many assets that depreciate in the same way." This directly supports the correct answer.

Details: The section "Swapping depreciation schedules" clarifies, "You can swap the depreciation schedules of two assets. Swapping depreciation schedules can be useful if you entered the schedules on the wrong asset records." This confirms why option C is incorrect.

Details: The section "Splitting depreciation schedules" explains, "You can split a depreciation schedule into two schedules. You might split a depreciation schedule if you sell part of an asset." This confirms why option D is incorrect.

The Contract Administration module, specifically the Contract Types application, is designed for setting up templates and defaults for different kinds of contracts. Within this application, an administrator can use the "Contract Property Defaults" action to define default values for specific properties, such as whether early termination is allowed. When a user creates a new contract and selects that specific contract type, these predefined property values are automatically applied, ensuring consistency and streamlining the contract creation process.

A. Database Configuration: This application is used to modify the underlying data structure (e.g., adding attributes to objects), not to set business-level default values for application data.

B. Organizations: This application sets high-level, organization-wide defaults (e.g., currency, default storerooms), not defaults for specific properties within a contract type.

C. System Properties: This application manages global, technical configuration settings for the entire Maximo system, not business-specific defaults for individual applications like contracts.

1. IBM Maximo Manage 8.7 Documentation, Contract Types application: "You use the Contract Types application to create and manage contract types. ... You can also specify default properties for a contract type. When you create a contract and specify a contract type, the default properties are copied to the contract." This documentation explicitly mentions the "Contract Property Defaults" action within the application. (Source: IBM Documentation, Maximo Application Suite as a Service, Contract Types application, "Actions for contract types" section).

2. IBM Maximo Manage 8.7 Documentation, Creating contract types: "In the Contract Types application, you can create contract types to classify your contracts. ... From the More Actions menu, select Contract Property Defaults to specify the default properties for the selected contract type." This provides the exact steps to perform the action described in the question. (Source: IBM Documentation, Maximo Application Suite as a Service, Managing contracts, "Creating contract types" section).

The appropriate order of phases in order to create a workflow process in IBM Maximo Manage is: Create the process: This involves designing the workflow process using the Workflow Designer application, including creating the activities, transitions, and conditions that make up the process. Validate the process: This involves ensuring that the process has been designed correctly and meets the desired requirements. This can be done by testing the process and making any necessary adjustments. Enable the process: This involves making the process available for use in the system by enabling it in the Workflow Designer application. Activate the process: This involves activating the process in the Workflow Administration application so that it is ready for use by the system.

In IBM Maximo Manage v8.0 implementation, the priority order for selecting a Safety Plan when a Job Plan is applied to a Work Order is: Use the Safety Plan associated with the Asset referenced on the Work Order. Use the Safety Plan associated with the Location referenced on the Work Order. Use the Safety Plan associated with the Asset's Rotating Item, for the Asset referenced on the Work Order. Use the Safety Plan associated with the Location's Rotating Item, for the Location referenced on the Work Order. This ensures that the appropriate Safety Plan is applied to the Work Order based on the relevant Asset and Location information. If a Safety Plan is not associated with either the Asset or Location referenced on the Work Order, the Safety Plan associated with the Asset's Rotating Item or the Location's Rotating Item may be used as a fallback option. This helps to ensure that worker safety is prioritized and that appropriate precautions are taken when performing work tasks.