




IMS provides maintenance management software that enables scheduling of preventive and corrective maintenance, tracking of work orders and parts inventory, and logging of equipment history to help industrial and facility teams streamline maintenance activities and improve asset reliability.
Have any questions? We’re here to help You
Yes, Makini provides extensive customization options for field mappings. Through the connection settings interface, you can view how each system's fields map to Makini's unified model. You can remap fields, add custom field mappings, or create entirely new custom fields that will appear in API responses. These customizations are connection-specific, allowing different mapping configurations for different customers. Mapping changes take effect immediately without requiring code changes. For standardized workflows, default mappings typically provide sufficient coverage. Custom mappings are most useful when integrating with heavily customized systems or when you need fields beyond the standard unified model.
Testing should cover authentication, data retrieval, data writing, error handling, and workflow logic. Start by connecting a test system through Makini's authentication flow. Use sandbox or non-production instances of your target systems when available. Test API calls for each entity type you'll use (purchase orders, work orders, etc.) to verify data mapping and field coverage. Test error scenarios by providing invalid inputs or attempting operations without proper permissions. For workflow-based integrations, test each workflow step independently before testing end-to-end. Verify webhook delivery and signature verification. Test with realistic data volumes to identify performance issues. Include tests for connection failure scenarios and verify your error handling and retry logic work correctly.
Makini maintains API stability and provides advance notice of breaking changes. The current API version is v1. When we introduce breaking changes, we release a new API version while maintaining the previous version for a transition period (typically 12 months minimum). Non-breaking changes (like adding new fields or endpoints) are introduced into the current version without requiring updates. We announce upcoming version changes through multiple channels: email notifications, dashboard announcements, and release notes. API responses include version information in headers. We recommend specifying the API version explicitly in your requests to ensure consistent behavior. During version transitions, we provide migration guides and support for updating integrations.
Yes, through Makini Flows, which includes connectors for popular databases including Snowflake, PostgreSQL, MySQL, MongoDB, and others. This enables workflows that synchronize data between industrial systems and your data warehouse or analytics platforms. For example, you can sync purchase orders from SAP to Snowflake for analytics, or use database queries to drive integration logic. Database integrations use the same workflow builder as other integrations, making it easy to combine industrial system data with database operations. For direct database-to-database syncing, we can help design optimized workflows. Database connections are treated as custom integrations and may require additional workflow development.
