Manit is an older MES/SCADA platform designed to support controls systems in a variety of industries. Customers who use Manit tend to invest a lot in customizations designed to control machine processes, recipe management, and traceability. Data from Manit is stored in relational databases which is the primary method for integration.
Below is a list of general use cases for integration with MES/SCADA systems like Manit. This information contains the general workflow and best practices we have discovered working with our customers.
General Use Cases:
- Machine abnormalities that trigger Dispatch events and workflows.
- Predictive Maintenance based on Machine data
- Machine Cycle Counts for launching Preventative Maintenance (PM) dispatches
- Recording Line Level Production and Scrap Counts
Supported Versions Details:
All Integrations with Manit are custom. Contact support for customer references and additional guidance on best practices.
Integration Methods and Best Practices:
General Considerations
Manit integrations are customized based on database access to the data historian. L2L CloudDISPATCH integration API endpoints and use cases are well known and documented. Depending on your specific use cases and how you are storing data with Manit, you will likely need to customize how your integration works. Based on the limited online presence from this vendor, we can provide customer references if you choose to integrate with this vendor. Based on this experience we've streamlined our API endpoints to target only the most critical data to achieve the results our solution can deliver. For this reason, our integrations tend to be far easier and faster than your typically Manit implementation. This targeted data first approach means up to 1000x fewer data mappings and transfer requirements to CloudDISPATCH than you may expect. As a result, we don't become your "data historian" in the cloud. We become the shop floor management platform that drives improvement. A big distinction, with a faster ROI and a simpler implementation.
Manit Connectivity Options
The Manit backend database is Microsoft SQL Server which provides the way to get access to this data through the use of an ODBC connection from a customer integration or from a middleware product.
Middleware Solutions
Depending on your established company's integration standards, you might develop this integration using an existing middleware solution by pulling data from a SQL database using a middleware SQL connector. We have customers that have successfully completed this using some of the following middleware solutions:
https://help.boomi.com/bundle/connectors/page/r-atm-Database_connector.html
https://docs.mulesoft.com/db-connector/1.8/
https://success.jitterbit.com/display/DOC/Database
L2L API Code Examples
You might be asking yourself, I'm technical, can't I just do this myself? YES! Based on how easy it is to use our API, a lot of customers jump right in and write custom Manit integrations using the tools, programming languages, and platforms they are most comfortable with. If this is you, we've created a number of API code examples in all of the most popular programming languages. Check out our Github repository at:
https://github.com/leading2lean
Use an L2L Partner
We have a number of Machine Integration partners with experience. Please contact support if you would like an introduction.