For downtime tracking, the process is well suited to tracking the operation of an entire process or plant; it is not suited to tracking individual equipment reliability. For inventory management, it is suited to tracking either bulk or discrete production, as its concepts are quite general. The Metrics engine is suited to smaller deployments; larger deployments would do better to extract and warehouse the raw data for external analysis and reporting.
MySQL is best suited for applications on platform like high-traffic content-driven websites, small-scale web apps, data warehouses which regards light analytical workloads. However its less suited for areas like enterprise data warehouse, OLAP cubes, large-scale reporting, applications requiring flexible or semi-structured data like event logging systems, product configurations, dynamic forms.
Learning curve: is big. Newbies will face problems in understanding the platform initially. However, with plenty of online resources, one can easily find solutions to problems and learn on the go.
Backup and restore: MySQL is not very seamless. Although the data is never ruptured or missed, the process involved is not very much user-friendly. Maybe, a new command-line interface for only the backup-restore functionality shall be set up again to make this very important step much easier to perform and maintain.
For teaching Databases and SQL, I would definitely continue to use MySQL. It provides a good, solid foundation to learn about databases. Also to learn about the SQL language and how it works with the creation, insertion, deletion, updating, and manipulation of data, tables, and databases. This SQL language is a foundation and can be used to learn many other database related concepts.
I give MySQL a 9/10 overall because I really like it but I feel like there are a lot of tech people who would hate it if I gave it a 10/10. I've never had any problems with it or reached any of its limitations but I know a few people who have so I can't give it a 10/10 based on those complaints.
We have never contacted MySQL enterprise support team for any issues related to MySQL. This is because we have been using primarily the MySQL Server community edition and have been using the MySQL support forums for any questions and practical guidance that we needed before and during the technical implementations. Overall, the support community has been very helpful and allowed us to make the most out of the community edition.
We evaluate a number of inventory management products; however, none provided the full pit-to-port coverage. There were only AVEVA Manufacturing Execution, powered by Ampla, and ION Qmastor. AVEVA Manufacturing Execution, powered by Ampla, provided a simpler interface, while the QMastor product seemed to be a collection of applications. There were other products evaluated, but they were not yet mature and proven.
MongoDB has a dynamic schema for how data is stored in 'documents' whereas MySQL is more structured with tables, columns, and rows. MongoDB was built for high availability whereas MySQL can be a challenge when it comes to replication of the data and making everything redundant in the event of a DR or outage.
Downtime classification has made sense of plant reliability data; whereas, before it was unstructured and could not be used for analysis
Production tracking and reporting. This solution is providing a unified, common source of production tracking for all departments, stored in a database rather than spreadsheets. A single source of truth ensures all data aligns and matches.
KPIs are providing a measurable indicator of performance against company-defined targets.
