Sync

Prometheus Mobile EAM

data

Work Orders

A work order is a document for organizing the execution of work or service, describing the task, location, resources, and deadlines

Asset

A physical or fixed asset tracked for both accounting purposes, such as depreciation and valuation, and operational purposes, such as maintenance and service history.

Purchase Order

A formal document confirming the commitment to buy or sell goods or services, issued to a vendor or received from a customer under agreed terms and quantities.

Stock

A record of a specific item held in stock at a particular location or bin, capturing on-hand quantity, reservation status, and lot or serial tracking details.

Customer

A partner entity representing a buyer of goods or services from the organization.

Vendor

A partner entity representing a supplier of goods or services to the organization.

Account

An internal financial account, such as a general ledger account or cost center, used to record and track monetary activity within the organization's chart of accounts.

Location

A physical site or facility within an organization, supporting nested hierarchies for structured representation of warehouses, buildings, or operational areas.

Site

An operational facility such as a plant, workshop, or office, within which resources, assets, and activities are organized and managed.

Organization

A tenant-level business unit or division within the system, serving as the top-level scope for data segregation and operational context.

...

Systems not found

Please check the system name of typos. If everything is correct, you can request this system to our team.

Request system

What is Mobile EAM?

Prometheus Mobile EAM, also sold as Prometheus Mobility, is Prometheus Group's mobile app for maintenance work in SAP, Oracle and IBM Maximo. Technicians, planners, supervisors and operations staff in asset-intensive plants use it on phones, tablets or computers to execute work orders and notifications, run operator rounds and inspections, record meter readings, and issue, count or receive parts, online or offline. Prometheus describes it as an extension of the EAM, not a separate system: field entries sync back to SAP, Oracle or Maximo. Products built on Makini's Unified API can use this connection to work with the field data the app handles, such as work orders and asset records, where the connection supports them. A reliability product can review work orders closed in the field, alongside the asset history, to see which failures recur. If a connection exposes readings from operator rounds, a condition monitoring tool can compare them with its own sensor trends. Where the connection permits writes, it can raise a follow-up work order. A user signs in through Makini Link, embedded in the vendor's product or sent as a magic link, so credentials never pass through that product. Data then syncs on an interval set by the Makini plan, not in real time. Because the app runs on top of SAP, Oracle or Maximo, confirm with the customer which of them backs their deployment and what the connection exposes. Work done offline syncs only after the device reconnects, so recent field activity can arrive late.