IBM Maximo Manage v8 Admin key terms

The Maximo configuration tool used to modify applications, tabs, fields, and menus; it controls presentation and behavior through XML definitions stored in the metadata database rather than in code.

The Maximo application that reads object definitions and generates or alters the physical database tables and indexes. Changes are saved as pending and applied during a controlled update, often requiring administrative mode.

A restricted operating state in which only administrative users can log in while configuration changes such as database updates or application deployments are applied, preventing conflicting transactions during structural changes.

A field-level definition on a Maximo business object, specifying data type, length, persistence, title, and whether the value is stored in the database or derived at runtime.

The server-side Java class that represents a business entity and enforces logic, validation, and relationships. It maps to database tables and is exposed to applications through object structures.

A definition that exposes one or more related business objects and their fields for integration or external use, controlling which records and child objects are published or consumed.

A defined list of allowed values for an attribute, either a synonym or alphanumeric domain, used to validate data entry and drive lookup lists in applications.

A defined search that lets users select a valid record for a field, configured in the Lookups application and bound to an attribute so entries match an existing domain or table.

A rule written in the conditional expression language that controls field visibility, editability, or required status based on other values in the current record, evaluated by the application at runtime.

A named privilege attached to application controls and menu actions. Security groups grant or deny signature options, determining exactly which actions and fields a user can access.

A collection of users, signature options, and data restrictions. Authorization is granted to the group rather than the individual, and users inherit the combined privileges of every group they belong to.

A rule that limits which records a security group can view or modify, typically expressed as a query against an object such as site, organization, or labor, applied transparently to application and report queries.

An individual login record holding identity, default insert site and organization, labor link, and group membership. Users authenticate against a configured repository and inherit privileges from assigned security groups.

An organizational level representing a physical operating location within Maximo. Many records are site-specific, and the default insert site determines where new records are created for a user.

The highest-level data partition in Maximo, containing one or more sites. Records are typically scoped to an organization, and cross-organization access requires explicit configuration.

A record representing a person or crew available for work, linked to a user for self-service and time reporting. Labor records hold craft, skill, calendar, and availability information used in work assignment.

A classification of trade or skill, such as electrician or mechanic, assigned to labor records and used to match work requirements to available workers during assignment and scheduling.

The core record for planned or corrective maintenance work, carrying status, priority, location or asset, tasks, labor, materials, and costs through a defined workflow from creation to closure.

A configurable classification of work orders that controls numbering, status flow, required fields, and behavior, allowing different processes such as emergency repair versus planned maintenance.

A reusable template of tasks, labor, materials, tools, and services applied to work orders, reducing data entry and enforcing consistent maintenance procedures across similar jobs.

A scheduled maintenance definition with frequency, meter, or condition-based triggers that generates work orders automatically when due, based on a job plan and target asset or location.

A measurement definition attached to assets or locations, such as runtime hours or odometer readings. Meter readings can trigger preventive maintenance and condition monitoring thresholds.

The use of meter readings and thresholds to detect degrading equipment condition and automatically generate work orders or alerts when values cross defined limits.

A record representing a maintained item such as a pump or vehicle, with hierarchy, location, meter, and specification data used for maintenance planning, costing, and reliability analysis.

A record describing a physical place in the operating hierarchy, such as a building, floor, or system, to which assets are assigned and where maintenance work is performed.

A stocked material record with quantity on hand, storeroom, reorder point, and cost data, used to issue parts to work orders and to drive replenishment through purchasing.

A defined inventory location within a site that holds stocked items and tracks balances, bins, and issues. Storerooms control where materials are received, stored, and issued to work.

A procurement record for goods or services from a vendor, with lines, terms, and receipt tracking. Receipts can update inventory balances and work order material costs.

A supplier record holding company details, contacts, and purchasing terms, referenced by purchase orders, contracts, and service agreements to support procurement and invoice matching.

A business entity record representing an organization that Maximo interacts with, such as a vendor, manufacturer, or service provider, used across purchasing, contracts, and asset records.

A record of charges from a vendor for goods or services, matched against purchase orders and receipts to verify quantities and prices before payment approval.

The Maximo subsystem that exchanges data with external systems through object structures, publish and invoke channels, and processing rules, supporting both outbound publication and inbound creation or update.

An outbound integration definition that selects an object structure, target system, and processing rules to send Maximo data to external applications, often triggered by events or scheduled queues.

An inbound integration definition that receives external data, maps it to a Maximo object structure, and creates or updates records according to configured processing and validation rules.

A script written in a supported language such as JavaScript or Python that runs on defined launch points to extend Maximo behavior without changing base product code.

The binding that determines when an automation script executes, such as an object event, attribute action, or custom action, along with the context and variables passed to the script.

A scheduled rule that runs at defined intervals, evaluates a condition against records, and performs actions such as sending notifications or changing status when the condition is met.

A configurable process definition that routes records through nodes, roles, and conditions, assigning tasks and enforcing approvals from initiation to completion.

A named state in a record's lifecycle, such as waiting, in progress, or closed, controlling which actions are allowed and how the record moves through its workflow.

A reusable definition of message content, recipients, and delivery channel used by notifications, escalations, and workflow to send consistent email or other communications.