




















































































Asset Essentials by Brightly is a modern CMMS that centralises asset data, manages preventive maintenance, schedules work orders and tracks facility performance. It is used by organisations across education, manufacturing, government and healthcare to reduce downtime and streamline maintenance workflows.
Have any questions? We’re here to help You
Integration timelines vary by complexity. For standard implementations with no customizations, connections can be live within 1-2 weeks. This includes authentication setup and basic workflow configuration. For implementations requiring custom workflows or specific business logic, timelines typically range from 2-6 weeks depending on the scope. Complex enterprise deployments with multiple systems and custom requirements may take 6-10 weeks. These timelines are significantly shorter than traditional integration projects, which often take 2-24 months.
Makini provides sandbox connections for testing without affecting production systems. Sandbox connections include sample data representing common scenarios: standard purchase orders, orders with custom fields, orders in various states (draft, approved, completed), and error cases like invalid vendors or out-of-stock items. Sandbox data is read-only for safety—write operations return success responses without modifying data. This allows thorough testing of your integration logic without risk. For testing with specific systems, we recommend using dedicated test instances of the actual systems (like SAP sandbox environments) connected through Makini, which provides the most realistic testing experience.
Yes, through a combination of sandbox environments, test data, and Makini Flows. For testing different data states, use sandbox connections with predefined test scenarios. For testing system behavior like delays, errors, or specific responses, you can build test workflows in Makini Flows that simulate various scenarios. For testing with actual systems, set up dedicated test instances of your target systems. During implementation, we work with you to identify critical test scenarios and ensure your testing environment supports them. For specific edge cases or unusual system configurations, we can help create custom test scenarios.
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.
