




AssetWorks offers asset, fleet and infrastructure management software, helping organizations manage fixed assets, fleet operations and mobile inventory, primarily in government and infrastructure-intensive sectors.
Have any questions? We’re here to help You
Industrial systems are often heavily customized, and Makini is built to handle this. For reading data, Makini can access virtually any field or custom table in connected systems. Through the connection settings interface, you can specify custom fields, tables, or entities to include in API responses. These show up alongside standard fields in the unified model. For custom objects not in our default model, you can request them through the interface and they'll be available immediately. For writing data, customization support varies by system but covers most common scenarios. During implementation, we work with you to identify required customizations and ensure they're properly configured before going live.
Customers connect systems through Makini's authentication module, which provides a simple, guided connection flow. The process typically takes 2-5 minutes: Select the system from our list of 2,000+ products. Enter connection details (usually just the instance URL and credentials). Authorize the connection. Makini validates credentials and establishes the connection. The connection flow is designed for non-technical users and can be embedded directly in your application, allowing customers to connect without leaving your product. For systems requiring additional setup (like API token generation), we provide step-by-step guidance within the connection flow. Customers see real-time feedback during connection, and if any issues occur, clear error messages guide them to resolution.
Yes, customers can connect as many systems as needed. Each connection is independent with its own API token, allowing you to manage multiple ERP systems, CMMS platforms, or other integrations for a single customer. This is common in organizations with multiple subsidiaries, regional systems, or during migration periods when legacy and new systems run in parallel. Each connection consumes connection credits based on the system type and deployment model. There's no technical limit on the number of connections per customer. For customers using multiple instances of the same system (like regional SAP instances), each instance requires a separate connection with its own credentials and token.
Disconnecting a connection can be done through the Makini dashboard or API. In the dashboard, navigate to the connection and select disconnect. Via API, call the disconnect endpoint with the connection ID. Disconnecting immediately invalidates the API token and stops all scheduled syncs and workflows for that connection. The connection credits used are returned to your pool and become available for new connections. Disconnecting does not delete historical data that was previously synced—that remains accessible until you choose to delete it. Customers can reconnect the same system at any time, which will create a new connection with a new API token. Use disconnection for customers who churn or when permanently retiring a connection.
