C1000-132 Questions and Answers

In IBM Maximo, costs for certain types of invoice line items can be distributed across multiple GL accounts. Specifically, the following types of line items are eligible for cost distribution:

Direct Issue: These are items directly issued to a work order, asset, or location rather than being stored in inventory. Costs for direct issue items can be distributed across multiple GL accounts based on the relevant cost centers or departments associated with the purchase

Service Item: For service-related invoice lines, costs can also be distributed across multiple GL accounts. This is useful when a service, such as consulting or maintenance, benefits multiple departments, allowing for cost allocation to relevant GL accounts​

Other options like "Credit Line," "Split Invoice," and "Hard Reserved" are not applicable for GL account distribution in this context.

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/

a Kit Item can be associated with A. Non Rotating item. When you create a kit record for an item in the Item Master application, you can define the structure of the kit using the Item Assembly Structure tab1. When adding a kit to a storeroom, if the component items do not exist in the storeroom, inventory records are created for these items1. However, you cannot create item kits that contain condition-enabled, rotating or lotted items1.

In IBM Maximo Manage v8.0 implementation, when viewing a Storeroom in the Manage Inventory Work Center, the three record sets (tabs) that can be viewed are Child Storerooms, Counts, and Balances. These record sets provide different views of the inventory and allow users to manage and track inventory levels and movements.

Asset Depreciation can be configured in the following three applications:

C. Asset Templates: You can define depreciation settings within asset templates to standardize how assets of the same type depreciate. This ensures consistency and saves time when creating new assets. (Reference: IBM Maximo Manage v8.0 documentation - Asset Templates)

E. Assets: Depreciation can be configured directly on individual asset records. This allows for flexibility if an asset has unique depreciation circumstances that differ from the template. (Reference: IBM Maximo Manage v8.0 documentation - Assets application)

F. Item Master: When creating an item record that will be used as an asset, you can specify depreciation information. This is useful for items that are commonly capitalized and tracked as assets. (Reference: IBM Maximo Manage v8.0 documentation - Item Master application)

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.

In the Receiving application in IBM Maximo Manage, the three statuses that show the overall receipt status of the purchase order are COMPLETE, PARTIAL and NONE.

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.

The Graphical Scheduling application in Maximo Manage v8.0 uses histograms to provide a visual representation of resource allocation. To generate these histograms for work orders, it relies on the following information:  

Craft Quantity: This refers to the number of personnel from a specific craft (e.g., electricians, mechanics) required to complete the work order.

Hours: This represents the total number of hours that the specified craft is needed for the work order.

By combining these two pieces of information, the histogram displays the overall workload demand for each craft across the scheduled work orders. This allows schedulers to:

Identify potential resource bottlenecks: See if there are periods where the demand for a particular craft exceeds its availability.  

Optimize resource allocation: Allocate crafts effectively to ensure that enough personnel are available to complete the work within the scheduled timeframe.

Balance workloads: Distribute work among crafts to avoid overloading specific teams. (Reference: IBM Maximo Manage v8.0 documentation - Graphical Scheduling application)

In Maximo Manage, the Server IP Addresses and Logged in users can be observed in the Maximo Management Interface Work Center.

When decommissioning a location in IBM Maximo Manage, you can roll the new status down to all assets in all changed locations. This cannot be done when decommissioning an asset.

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.

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.

Locations, assets and storerooms are defined at the Site level in IBM Maximo Manage.

https://maximosecrets.com/2022/04/14/failure-codes-and-failure-reporting/

In IBM Maximo, only one failure report can be created per work order. This failure report captures details about the issues encountered, including the failure class, problem, cause, and remedy codes. It is recorded in the Failure Reporting tab within the Work Order Tracking or Quick Reporting applications, and is designed to provide a structured report on the failure encountered for the specified work order​

​

​

While Maximo allows for multiple failure details to be reported across different work orders, each individual work order is limited to a single failure report. Tasks or child work orders associated with the main work order do not support additional, separate failure reports for each task; instead, the primary work order holds the single comprehensive report.

two automation script launch points that can be triggered directly by a workflow are B. Custom Condition and D. Action. An action launch point associates a script with an action and executes when the specified action occurs1. A custom condition launch point associates a script with a condition and executes when the specified condition is evaluated2.

https://www.ibm.com/docs/en/mam/7.6.0?topic=lp-script-action-launch-point

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.

When a Service Level Agreement (SLA) is applied to a WORKORDER object in IBM Maximo Manage v8.0 implementation, the Commitment Type that will be missing from the lookup is DELIVERY. The other possible Commitment Types in Maximo Manage are DOWNTIME, AVAILABILITY, and CONTACT.

The Contract Administration application is used to set contract property defaults for specific contract types. For example, you can set whether early termination is allowed by the customer for a specific contract type.