Free C1000-132 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

In the standard IBM Maximo procurement lifecycle, a Purchase Requisition (PR) must first be in an 'APPR' (Approved) status before its lines can be used to create a Purchase Order (PO) or a Contract. Once all lines on the approved PR have been successfully copied to one or more POs or Contracts, the system automatically changes the PR's status to 'COMPLETE'. This status signifies that the requisition's purpose—to request goods or services—has been fulfilled by formalizing it into a binding procurement document.

A. INPRG: This status indicates that an approved PR is currently being revised, which is a different action than processing its lines onto a PO.

C. CLOSE: This is a final, typically manual, status applied after the entire procurement cycle is finished, meaning the associated POs are also closed (e.g., fully received and paid).

D. APPR: This is the prerequisite status before lines can be copied to a PO or Contract, not the resulting status after the action is completed.

1. IBM Maximo Manage 8.7 Documentation, "Purchase requisition statuses": This official documentation explicitly defines the 'COMPLETE' status. It states, "All lines on the purchase requisition have been transferred to one or more purchase orders or contracts." It also clarifies the 'APPR' status as the prerequisite for this action and the 'CLOSE' status as a subsequent step.

Source: IBM. (2023). Purchase requisition statuses. IBM Documentation for Maximo Manage. Retrieved from https://www.ibm.com/docs/en/mas-cd/maximo-manage/8.7?topic=requisitions-purchase-status (Section: Statuses and descriptions).

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).

In Maximo Manage/MAM, every crew type or crew position must be tagged with one of the three system-supplied position types. The product ships with exactly three default values—Leader, Driver, and Helper—which distinguish the role’s responsibility (overall lead, vehicle operator, or supporting member). No other position codes (for example, Technician, Supervisor, Apprentice) exist until an administrator creates them manually.

B. Supervisor – Not delivered as a built-in position type; would need to be user-defined.

E. Apprentice – Not among the shipped position types; only available if added through configuration.

F. Technician – Likewise not a default position type; must be created by users if required.

1. IBM Maximo Application Suite – Manage v8.5 Knowledge Center, topic “Position types for crews” (kc link), para. 1: “The three default position types are Leader, Driver, and Helper.”

2. IBM Maximo Asset Management 7.6 Administration Guide, ch. ‘Managing Crews’, p. 224: “In the Type field you can select one of the three predefined values: Leader, Driver, Helper.”

3. IBM Maximo Asset Management 7.6 Knowledge Center, “Defining positions for a crew type” (kc link), step 6.

Selecting the "Validate GL Component Combinations" checkbox in the Chart of Accounts application configures IBM Maximo Manage to enforce strict validation on the entire General Ledger (GL) account string. When this option is active, the system verifies that the complete combination of all GL components used in a financial transaction matches a predefined, valid GL account listed in the GL Account Configuration. This prevents users from forming a GL account from individually valid components that, when combined, do not represent an authorized account. The validation is performed on the full account string, not on its individual parts.

A. Any GL component can be used.

This is incorrect because enabling validation restricts usage; it does not permit the use of any component without checks.

B. Any valid GL component can be used.

This describes the behavior when "Validate GL Component Combinations" is not selected. In that state, Maximo only validates each component individually, not the complete combination.

D. Validates transactions occurred during an active financial period.

This is incorrect as it describes financial period validation, which is a separate function managed within the Financial Periods application, not the GL component validation in the Chart of Accounts.

1. IBM Maximo Manage Documentation, Chart of Accounts application.

Reference: In the section describing the Chart of Accounts application, the documentation states: "If you select the Validate GL Component Combinations check box, Maximo® Manage validates the full general ledger account code against the accounts that you define in the GL Account Configuration window. If you do not select this check box, Maximo Manage validates each component of the general ledger account code individually." This directly supports that only valid, full GL accounts (combinations) can be used.

Source: IBM Documentation, Maximo Application Suite > Manage > Financial management > Chart of accounts > Chart of Accounts application. (The exact URL may vary by version, but the content is consistent for Maximo Manage 8.x).

2. IBM Maximo Manage Documentation, Financial management overview.

Reference: The overview of financial management distinguishes between the Chart of Accounts structure and Financial Periods. It explains that the Chart of Accounts defines the valid GL accounts, while Financial Periods define the timeframes for posting transactions. This clarifies that validating GL combinations (Option C) is distinct from validating against financial periods (Option D).

Source: IBM Documentation, Maximo Application Suite > Manage > Financial management > Financial management overview.

In the Safety Plans application, a Work Asset is either a location or an asset that requires the safety

plan. Each safety plan record must have at least one work asset specified, and the work asset can be

a location or an asset.

In IBM Maximo, the Calendars application is used to define periods of availability, such as work shifts, holidays, and non-work periods, which is critical for scheduling. Calendars can be directly associated with records that have operational schedules or require resource planning. The primary record types that utilize calendars for managing availability are Assets (for defining maintenance windows), Locations (for defining access times), and Person records (for defining labor shifts and vacations). These associations are fundamental to the functionality of modules like Preventive Maintenance and Work Order Tracking for effective resource and work scheduling.

A. Items: Items are inventory records for materials and services; they do not have operational schedules that would require an associated calendar.

C. Job Plan: A job plan is a template for work, not a schedulable entity; calendars are applied to the resources on the resulting work order.

E. Contracts: Contracts define commercial terms, conditions, and payment schedules, not the operational availability of physical resources or personnel.

1. IBM Maximo Application Suite Documentation. "Calendars application." IBM. Accessed 2023. In the overview of the Calendars application, the documentation explicitly states, "You can associate calendars with records for labor, assets, locations, and other types of records to extend the capabilities of other applications." This directly confirms that Assets, Locations, and Person (Labor) are the intended record types.

Source: IBM Documentation, Maximo Manage 8.11, Administering Maximo Manage > Planning and scheduling resources > Calendars application. (URL: https://www.ibm.com/docs/en/mas-manage/8.11?topic=resources-calendars-application)

The overall receipt status of a Purchase Order (PO) in the IBM Maximo Receiving application is summarized by three distinct statuses. 'NONE' indicates that no line items on the PO have been received. 'PARTIAL' signifies that some, but not all, of the ordered quantity has been received. 'COMPLETE' is used when all line items on the PO have been fully received. These statuses are visible in the PO application and provide a quick overview of the receiving progress for the entire order.

B. RETURNED: This is a status for a specific transaction when a previously received item is returned to the vendor; it is not an overall PO receipt status.

E. WINSP: This status, meaning "Waiting for Inspection," applies to individual receipt lines, not the overall purchase order.

F. VOID: This status is used to cancel a specific receipt transaction, for example, if it was created in error. It does not represent the overall PO receipt state.

1. IBM Documentation - Maximo Manage 8.5, Receiving items process: "The receipt status of a purchase order indicates whether items on the PO have been received. The possible values are None, Partial, and Complete." (Source: IBM Documentation, Maximo Manage, Managing inventory, Receiving items, Receiving items process).

2. IBM Documentation - Maximo Database Schema: The PO database table contains a column named RECEIPT. This column is associated with the RECEIPTSTATUS synonym domain, which defines the valid values as NONE, PARTIAL, and COMPLETE. (Source: IBM Maximo Data Dictionary, Table: PO, Column: RECEIPT, Domain: RECEIPTSTATUS).

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

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.

The Master PM application serves as a template to manage common information for a group of associated Preventive Maintenance (PM) records. Key information managed includes the job plan, asset details, and scheduling frequency. When scheduling information, such as the frequency, is updated on the Master PM and then applied to the associated PMs, it directly changes the calculated due dates for future work. The PM Forecast is a projection of these future due dates. Therefore, updating the Master PM's scheduling data effectively updates the forecast for all linked PMs.

A. Work Order Status: Work Order Status is managed in the Work Order Tracking application after a work order is generated from a PM; it is not updated from the Master PM.

C. Generate Work Orders: This is an action performed on individual PM records to create work orders. It is not a data field that is updated within the Master PM template itself.

D. PM Hierarchy: A PM hierarchy, which defines parent-child relationships between PMs, is configured directly in the Preventive Maintenance application, not through the Master PM application.

1. IBM Maximo Manage 8.0 Documentation, "Master PMs": "A master PM is a template that is used to create preventive maintenance (PM) records. You can use a master PM to specify job plan, frequency, and asset information for a group of PMs... When you change information on the master PM, you can choose to apply the changes to the associated PMs." This confirms that frequency, a key driver of the forecast, is managed here.

2. IBM Maximo Manage 8.0 Documentation, "Forecasting PMs": "You can generate a forecast for a preventive maintenance (PM) record to see the dates on which work orders are due to be generated. The forecast is based on the frequency information in the PM record and on the work order generation criteria." This directly links the forecast to the frequency information managed by the Master PM.

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.

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.

In IBM Maximo Manage, the failure reporting mechanism is designed for precise tracking. The system allows for the creation of one distinct failure report for the main work order header. This report captures the primary problem, cause, and remedy. In addition, for work orders that have multiple tasks, a separate and single failure report can be created for each individual task. This enables granular failure analysis on complex jobs where each task might address a different component or failure mode. The system architecture enforces this one-to-one relationship between a failure report and its associated record (either the work order header or a specific task).

B. unlimited failure reports for either a work order or any of its tasks

This is incorrect. The standard functionality enforces a one-to-one relationship; you cannot create multiple, separate failure reports for the same work order header or the same task.

C. unlimited failure reports for each work order, but none for a task

This is incorrect because failure reports can be created at the task level, and the system does not permit an unlimited number of reports for the work order header.

D. just one failure report

This is too restrictive. While only one report can be made for the work order header, additional reports can be created for each of its associated tasks.

1. IBM Maximo Manage 8.7 Documentation, Work Orders, "Reporting failures": This official documentation states, "You can report a failure for a work order or for a work order task. When you create a failure report, you create a record of the failure hierarchy that is associated with the work order." This confirms that reports can be created for both the work order and its tasks. The use of singular nouns ("a failure", "a record") implies a one-to-one relationship for each object.

2. IBM Maximo Manage 8.7 Documentation, Database information, FAILUREREPORT table: The database schema for Maximo includes the FAILUREREPORT table. This table contains the attributes WONUM, SITEID, and TASKID. The application logic uses this structure to link a single failure report record to either a work order header (where TASKID is null) or a specific work order task (where TASKID is populated), thereby enforcing the one-report-per-object rule.