














































Trident Genesis (TG) is the enterprise asset management platform from Fielden Management Services, a Melbourne company that began building its Trident EAM package in 1984. Fielden open-sourced the TG technology and builds proprietary industry editions on it: TG Air for air navigation service providers, TG EAM for emergency services vehicles and facilities, TG ChEAM for chemical plants and RMS for rail rollingstock and infrastructure. Their data covers asset hierarchies, preventive and reactive maintenance, stores and inventory, purchasing, skills and certifications, and costs. A condition monitoring product can read the asset hierarchy through Makini's Unified API, so a sensor on a locomotive or a plant pump maps to the equipment record that maintenance planners already use, and it can raise a work order where the connection permits writes. Inventory optimization tools compare stock across warehouses and bins with open purchase orders and lead times. For emergency services fleets, a telematics provider can match vehicles to TG assets and review their maintenance history, where the connection exposes it. A TG user at the customer 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. Fielden tailors each TG deployment to its customer and offers local or cloud hosting, so entity names, custom fields and network access can differ between sites. Map custom fields and confirm IP allowlisting with the customer's IT team early.
Have any questions? We’re here to help You
Some editions of Fielden Trident Genesis expose an API, but it is often limited, legacy, or inconsistent between versions, and many on-prem deployments have no usable API at all. Makini gives you one modern REST API for Fielden Trident Genesis that lets you read and write Fielden Trident Genesis data, even for legacy or on-prem instances. You build against Makini once instead of integrating with Fielden Trident Genesis directly.
You integrate Fielden Trident Genesis through Makini's Unified API. Authenticate once and Makini normalizes Fielden Trident Genesis data into a single consistent schema you can read from and write to inside your product. The same connection reaches Fielden Trident Genesis plus 2,000+ other ERP, WMS and CMMS systems, so you build one integration instead of one per system.
Through Makini you can read and write Fielden Trident Genesis's core records as normalized, standardized resources, in both directions: pull data out of Fielden Trident Genesis and push updates back in. Every field is mapped to a consistent Makini schema, so you work with the same object model across Fielden Trident Genesis and every other connected system.
Days, not quarters. Because Makini already builds and maintains the Fielden Trident Genesis connector, you do not reverse-engineer the integration yourself: you authenticate and start reading and writing Fielden Trident Genesis data through the Unified API, typically within a few days. A Fielden Trident Genesis integration built in-house usually takes months plus ongoing maintenance.
Yes. Makini connects to Fielden Trident Genesis over encrypted connections on SOC 2 Type II certified infrastructure, and handles Fielden Trident Genesis credentials for you so they are never exposed to your app. You authenticate once, and access runs through Makini's managed, auditable layer. The same security model applies across Fielden Trident Genesis and every other connected system.
Makini owns the maintenance. When Fielden Trident Genesis changes its API, versions, or endpoints, Makini updates the connector, and your integration keeps working with no changes on your side. You get a stable Unified API with webhooks, and Fielden Trident Genesis upkeep stays off your roadmap.
