








































































































.webp)





















AVEVA PI System (formerly OSIsoft PI) is a real-time data infrastructure for collecting, storing, and analyzing operational data from industrial assets and sensors.
Have any questions? We’re here to help You
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.
Machine-to-Machine (M2M) authentication is a secure method that allows automated data exchange between NetSuite and other applications without requiring manual user login. It uses OAuth 2.0 Client Credentials grant flow with certificate-based authentication to establish secure, automated connections.
No. For M2M setup, both "Authorization Flow" and "Authorization Code Grant" should be unchecked. Only "Client Credentials (Machine To Machine) Grant" should be checked, along with the required scopes (Restlets and REST Web Services).
