














































EAM2GO, also listed as eam2go, is a web-based maintenance and enterprise asset management application from Phitomas, an ERP and IT solutions company based in Petaling Jaya, Malaysia. Phitomas no longer features it on its website and the eam2go.com domain now hosts an unrelated site, but organizations that adopted it can still hold their asset records there. Software directories describe work order tracking, asset tracking, preventive maintenance scheduling, warranty and service contracts, purchasing and inventory control, with mobile access for technicians. A predictive maintenance product reads assets and locations through Makini's Unified API, so each monitored machine maps to its EAM2GO asset record. When a sensor trend points to a developing fault, it can create a work order where the connection supports writes, so the job appears in the maintenance team's queue. Inventory tools compare stock levels with open purchase orders, where the connection exposes them, and OEM vendors review the equipment they supplied at each site to plan spare parts. An EAM2GO user signs in through Makini Link, embedded in the vendor's product or sent as a magic link, so credentials never pass through the vendor's application. Data then syncs on an interval set by the Makini plan, not in real time. Agree with the customer's administrator on a dedicated user whose rights cover the records needed, and confirm the address of their EAM2GO instance. If it runs on the customer's own servers, IT may need to allow Makini's fixed IP addresses or set up a VPN.
Have any questions? We’re here to help You
EAM2GO's support status is unclear: Phitomas Sdn Bhd no longer features the product on phitomas.com, and the eam2go.com domain now hosts an unrelated site. Organizations that adopted it may still run it with years of asset and work order history. Ask each customer whether they hold an active support contract with Phitomas, and treat the integration as a way to keep that history usable.
EAM2GO has no public API reference available today, and Makini notes that some EAM2GO editions expose only limited or legacy APIs while many on-premise deployments have no usable API at all. Your product does not call EAM2GO directly. It calls Makini's REST API, and Makini maintains the EAM2GO connector when versions or endpoints change on the customer's side.
EAM2GO is described as web-based, but directories disagree on how it is delivered: G2 lists an on-demand Standard Edition at $60 per user per month, while ITQlick lists pricing from $500 per installation. Confirm with each customer where their EAM2GO instance runs. If it sits on their own servers, IT can allowlist Makini's five fixed IP addresses or set up a VPN.
Makini's EAM2GO page lists work orders, assets, purchase orders, stock, customers, vendors, accounts, locations, sites and organizations among its models. What a given connection returns depends on the customer's EAM2GO setup and the rights of the connecting user. Run a first sync and review which fields arrive filled before you build mappings, especially for older installations with custom codes.
EAM2GO is listed by ITQlick with parent and child asset relationships, serial tracking with transaction history, and warranty and service contract management. A reliability product can roll repeat faults on a component up to its parent machine, and a service product can check warranty coverage before suggesting a repair. These details may sit outside Makini's unified models, so confirm the connection exposes them.
EAM2GO writes are possible through Makini where the connection supports them, but start read only. Makini lists common write limits: read-only fields, business rule validation such as required fields or valid vendor codes, permissions of the connected account, and workflow states that block changes. Once mappings are confirmed, create work orders for a few agreed assets and check them with the customer's planners.
