M1, from ECI Software Solutions headquartered in Ft. Worth, is an all-in-one manufacturing ERP software solution, built for small and medium-sized discrete manufacturers.
N/A
SAP Manufacturing Execution
Score 9.0 out of 10
N/A
SAP Manufacturing Execution is the company's MES designed to digitally control, monitor, and automate manufacturing operations.
N/A
Pricing
M1
SAP Manufacturing Execution
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
M1
SAP Manufacturing Execution
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
M1
SAP Manufacturing Execution
Considered Both Products
M1
Verified User
Anonymous
Chose M1
We replaced Open Systems with M1 7 years ago. Our Open Systems software seemed to be more user-friendly and was not overburdened by reports and processes that were not needed for daily functions.
M1 is light years ahead in overall cost and proficiency. It allows so much more control and flexibility as compared to its competitors. When choosing M1 we went through many demos and M1 was the only ERP that met our needs and still does. We also control our own data which is a …
M1 is better with the manufacturing side of software whereas Sage 100 is better at the financial side. Which is frustrating that M1 implementation people are not accountants, so they got us up and running but did not do a good job of making sure the GL accounts were setup …
Our customization requirements were not that high and based on a price/cost benefit M1 was the winner. SAP was considered but the upfront costs and challenging learning curve together with the lack of flexibility in the SAP HANA public cloud version made the M1 choice more …
M1 does a good job of being able to handle our requirements. Some of our assemblies and sub-assemblies require a significant amount of detail and different levels in order to complete - and M1 handles that. Some of the other products I've used, or implemented else where fall …
There was no product evaluated before using SAP ME. This replaced the custom homegrown MES system. The custom MES system had a lot of issues with the integration with SAP ERP. While evaluating the situation, SAP MII was the initial tool used to create the integration of the …
Implementation is by far the weakest link in the ECI/M1 process. Although the tool is powerful, the client is expected to drive the process of learning the tool, planning the meetings with consultants, identifying risks and making mitigation plans, etc. without any samples, guidance or assistance on the part of ECI. The tool is best suited to high volume, standard product manufacturers who build to inventory or to order without much variation. The shop floor routing and time tracking are straightforward if you can master the convoluted Unit Of Measure calculations. The tool is either hosted locally or accessed through Remote Desktop. Shop floor is web enabled but the main desktop for M1 is still a relay which makes connectivity a potential issue. Moving this platform to a truly web hosted environment would substantially improve connectivity and eliminate compatibility issues with Apple products
SAP Manufacturing Execution is suitable for desecrate manufacturing. For the complex routing of the product, this software ensures users do not by mistake start executing the wrong steps. This is the best tool to track and work on nonconformance and rework scenarios. This is most suitable when the landscape has SAP ERP in place.
Manage inventory counts. Good precision on quantities in and out, through shipping, MI, MR, and receipts.
Job costing shows great details on labor, operations, and materials to be used. I wished that would do better in outside operations that would return, but we still think it is great.
Ability to track changes (changelog), showing all changes that had in a particular place. Such as where, when, and by whom a line item unit price was changed in a PO.
Link, traceability, keeping history. If done correctly, it is amazing to keep the history of a part/lot.
The amount of user rights/customization is unbelievable. It can be hard to set up in the beginning, but it is great that you can give some very specific access to a user, and it is not (in general) as a package.
Visual routing ensures the production line layout is as appropriate as shown on the application.
Production house needs a lot of data to do an in-process inspection of the product. ERP might not need that. SAP ME provides that place to do every data collection.
Nonconformance functionality ensures when needed the product goes to the appropriate station to get repaired. Also, data collection can raise NC and can move the product to a particular station to get an issue corrected.
All the information is well integrated with SAP ERP and makes SAP ME more valuable for the organization.
SAP MII also comes along with SAP ME helps to get the application well integrated with the shop floor equipment.
Some of the functions are pretty detailed - and so they take a while to generate screens and pages in reports.
We actually use it for 2 companies we own - and it would be nice if the inter company communication was a little smoother. It's hard to share some data, and not everything is possible to be shared.
Customized reports need to backed up before any updates to M1 or they're lost. It seems M1 overwrites the report folders everytime you run an update - so you have to keep track of what you've changed in Crystal Reports and restore it.
Because it would be helpful if ECI would provide better documentation, communication and workflows to understand how each field interacts within the system and how each of those touch other areas within M1. It would also be useful if ECI would provide prescheduled training for how to customize things with M1 through Design Studio
Our customization requirements were not that high and based on a price/cost benefit M1 was the winner. SAP was considered but the upfront costs and challenging learning curve together with the lack of flexibility in the SAP HANA public cloud version made the M1 choice more natural. SAP Services is usually more expensive compared to M1.
There was no product evaluated before using SAP ME. This replaced the custom homegrown MES system. The custom MES system had a lot of issues with the integration with SAP ERP. While evaluating the situation, SAP MII was the initial tool used to create the integration of the custom MES. We later found the fully functional tool SAP ME off the shelf had several functionalities out of the box.