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.