Last Updated on April 16, 2024 by maximosecrets
Superseded by https://maximosecrets.com/2024/04/16/maximo-manage-modules/
Financial Module
| Application | Description |
| Currency Codes | A single page application used to define a currency code and its description. A currency code must be defined before you can define an organization, an organization can have two base currencies. |
| Exchange Rates | An exchange rate is defined between two currencies for a particular organization. An exchange rate has an active date and an expiration date. |
| Chart of Accounts | Used to define the structure, component values and valid component value combinations that are used as General Ledger (GL) codes throughout Maximo. These are defined for each organization. Financial periods and validation options are also defined in this application. |
| Cost Management | Used for project cost accounting separate from general ledger based fields. A project can exist in a hierarchy and can have multiple tasks. A work order can reference a project task and hence can collect costs against a project. |
| Budget Reporting | Used to define budget lines for GL components, GL accounts, locationsA physical place where assets exist and where work can be performed. More, and assets, and then to determine how the estimate, commitment and actuals are calculated against the budget line. |
IT Infrastructure Module
| Application | Description |
| Configuration Items | A configuration item (CI) is any component that is under configuration control. This may be an asset, location, item or service, but it might also be a document. A CI can have a classification whose attributes can be used to define the configuration. A CI can be related to other CIs but an asset or location can only have one related CI record. Most often CIs are associated with technology infrastructure. |
| Relationships | Used to create a relationship type that describes a dependency or connectivity point between multiple assets or configuration items. A relationship can be unidirectional or bidirectional. |
| Collections | A collection is any set of configuration items, asset or locations. Most often used to control access to these records through an object data restriction defined in the Security Groups application. Can add records to a service request or work order by selecting them from a collection. Can be easily added to the advanced search of applications to find the records associated to the asset, locations or CIs in a collection. |
Integration Module
| Application | Description |
| Object Structures | An object structure is the common data layer that the integration framework components use for sending and receiving data. An object structure consists of one or more related business objects that define the content of an integration message. The objects are linked together using relationships. Objects structures are used in integration, reports and migration manager. |
| Publish Channels | A publish channel is used for outbound interfaces or the export of data through the integration framework. A publish channel uses the schema created from the associated object structure. |
| Invocation Channels | An invocation channel provides Maximo with the ability to call an external system and process the responses. The integration is a synchronous Service Oriented Architecture (SOA) interface and the invocation channel is called from an action in a workflow process, escalation or user interface control. |
| Enterprise Services | An enterprise service is used for inbound interfaces or the import of data through the integration framework. The message content is based on the schema of the associated object structure. |
| Web Services Library | A web service can be created in the integration framework to allow external systems to send messages or queries to the Maximo database. Web services can be based on an object structure an enterprise service or there are a set of standard services for objects like asset, ticket, work order, item, etc. The web service schema and
Web Service Description Language (WSDL) files can be generated from this application and the xml data for each operation and response xml can be viewed. |
| End Points | An end point and its associated handler routes outbound messages to an external system. The combination of an end point and handler specifies the transport protocol to use, such as HTTP or web service, and provides the communication data required to reach the destination, such as a URL. End points and handlers are used for outbound integration only. |
| External Systems | An external system is the system to which data is sent or received. Publish channels and enterprise services are linked to the external system in this application. JMS queues are configured through this application. |
| Logical Management Operations | Logical management operations are used to identify the actions that an integration module supports, for example, get status, deploy software. They may be used during change and release processes to automate system processes through an operational management product (OMP). Most often used by IBM Control Desk to communicate with other Tivoli products. |
| Integration Modules | Integration modules are used by a process management product (PMP) to invoke an external operational management product (OMP). This application is where you link the logical management operations to the OMP. Most often used by IBM Control Desk to communicate with other Tivoli products. |
| Launch in Context | A launch entry record provides the ability to open the console of an external application from within Maximo either in the same or a different browser session. The external system must be enabled for the web and support the land in context feature. The launch entry can be linked to a record in the action menu, a hyperlink or a button of a Maximo application. The launch entry can pass data as parameters in the url calling the external application. |
| Message Tracking | The Message Tracking application tracks and displays the processing history of queue based publish channel and enterprise service messages. When you use the Message Tracking application, you can determine which messages are flagged with an error. You then can select a failed message and go to the Message Reprocessing application to take appropriate action to correct erroneous data. Enabled message tracking will also write processed messages to the database. Message tracking functions are set up on the associated publish channel or enterprise service. |
| Message Reprocessing | The Message Reprocessing application allows you to view the integration messages that have been flagged with an error, modify and reprocess the message, change the status or delete the record. |
| OSLC Providers | Maximo can be configured as an OSLC (Open Services for Lifecycle Collaboration) consumer where UI-based interactions could be configured between Maximo and an OSLC provider application, for example to link Maximo to Rational Team Concert. OSLC allows users to share and update data between products or to query data. |
| OSLC Resources | Business objects are made available as OSLC resources. The consumer application can query, create, update, or delete these resources in the provider application. OSLC resources are implemented using object structures. |
| JSON Resources | This application is part of the REST API framework and is used to define the data resource of an external system whose data is shared with Maximo by using a federated MBO. |
| JSON Mapping | This application is used for mapping the attributes of a JSON message to the attributes in a Maximo Object Structure. |
| Notifications | Notifications are used to communicate the status of your assets. In the Notifications application, you can create, update, or delete notifications. In the Work Center, you can manage notifications and your subscriptions to notifications. |
Interactions Sub Module of Integration Module
| Application | Description |
| Create Interaction | This is the application used to create an interaction. An interaction can start a web service and send data to it from an application. The interaction can then display data returned from the web service and save this data to the Maximo database. This application creates an interaction using a wizard approach. |
| Interactions | After the interaction has been created it can be reviewed, modified, and deleted from the Interactions application. |
Inventory Module
| Application | Description |
| Item Master | The Item Master application is used to define material items and items that are used as a reference point for rotating assets. Items may have a parent or children and collectively known as an item assembly structure (IAS). The IAS can be applied to assets or locations to create a hierarchy. Items may be stocked in storerooms as part of inventory records, they may exist as kits of items. Items belong to an item set and can be shared across multiple organizations that share that item set. |
| Service Items | Service items are another type of item, services are not held in storerooms. These standard services can be requested on work orders and ordered through the purchasing applications, there may be a standard price for the service as part of a contract. |
| Tools | Tools are the third type of item, tools can be held in storerooms, issued and returned. Tool items can also be set as rotating allowing tool assets to be created and tracked. Tools are charged to work orders using an hourly rate. Tool items are added to storerooms from this application. |
| Stocked Tools | The Stocked Tools application is where tools are held in storerooms and where balances of the tool exist. This is the application from which you issue, return and transfer tools between storerooms or look for availability of a tool item across storerooms. For rotating tools you can see the whereabouts of the tool assets. |
| Inventory | The Inventory application is where material items exist in storerooms with their balances and reorder points. Reservations can be reviewed and items issued and returned. Consignment stock from a vendor can also be held. |
| Inventory Usage | Items and tools can be issued, returned and transferred between storerooms using an inventory usage document which has a status and which could be used in a workflow process. The inventory usage document provides capability for both staging of multiple items prior to shipment and processing of the shipment receipt through the Shipment Receiving application. The application is useful for inter storeroom logistics. |
| Shipment Receiving | The Shipment Receiving application is for the receiving of items and tools into a storeroom transferred from another storeroom via an inventory usage document. Items can be transferred between storerooms in the same site, across sites and across organizations. Inspection and receipt of assets can be part of the receiving process. After receipt balances are adjusted in the destination storeroom. |
| Condition Codes | A single page application for defining condition codes. Material items defined in the Item Master application can exist with multiple condition codes and can be held in a storeroom with balances held at the condition code level. An item with a condition code while not new may still have a cost value for charging purposes and can be issued to a work order. |
| Storerooms | The application used for creating storerooms and setting up various related GL accounts. A storeroom is a type of location. There is a view of the items held in the storeroom including cost and balance information. |
| Issues and Transfers | An application which is an alternative to the Inventory Usage application and which may be used by a storeman for issuing, returning and transferring items between storerooms, particularly if those storerooms exist within the same physical location. Many clients would now use the Inventory Usage application and the Shipment Receiving application for receipt of items at a destination storeroom. |
Planning Module
| Application | Description |
| Job Plans | A job plan is a template for a work order. The applications allows you to define the tasks and labor, material, service and tool requirements needed to fulfil the job plan and its tasks. A job task can have a classification and can reference another job plan thereby creating a multi-level hierarchy when applied to a work order. |
| Routes | A route is a set of locations and or assets that are used in inspections and maintenance. Often the inspection or work to be performed at each route stop is the same, but a route stop can also reference a job plan. |
Safety Sub Module of Planning Module
| Application | Description |
| Hazards | The Hazards application can be used to define a hazard and the precautions needed to mitigate the hazard or a hazardous material. The application also shows associated tag outs for locations and assets. |
| Precautions | Used to create a library of precautions which are associated with hazards or added to safety plans. Additional precautions can be added to a work order to mitigate a hazard. |
| Lock Out / Tag Out | This application provides the ability to define the lock out operations on assets and locations and the sequence required in order to safely isolate (tag out) another asset or location. |
| Safety Plans | The safety plan collects together the hazard and their precautions, hazardous material and lock out / tag out operations to safely service a set of work assets and locations. A safety plan can be associated with a job plan and the work assets so that it is automatically applied when the job plan is applied to a work order for the referenced asset or location. |
Leave a Reply