|
|
|
When to use "OEE Manager" The PRIME "OEE Manager” software is unique, in that it is designed for use in manufacturing companies to provide all of the features that are necessary to support continuous improvement processes. It is a relational database using Microsoft Access, but with security features that are independent of Access. The OEE management features in "OEE Manager" are comprehensive, and provide all of the modelling options necessary for the full range of manufacturing processes, backed up with a set of essential reports/charts for driving a Lean Manufacturing or TPM approach to performance improvement. The CMMS functions in "OEE Manager" have been particularly designed for small/medium-sized manufacturing organisations, where the resources available for managing the work order and PPM functions is limited, and where the requirement is for simplicity without sacrificing any of the essential elements needed to drive maintenance improvement. Because "OEE Manager" is based on Microsoft Access it is an appropriate choice for most organisations, but may not be suitable in all situations. The guide below may be helpful for you to decide on the architecture you require.
Why choose Microsoft Access, and hence "OEE Manager" for your database needs? This discussion will help you identify the pros and cons of using Access as your database development system. Arguments for using Microsoft Access
Arguments against using Microsoft Access (Note that in some cases your computer systems may not be reliable enough to handle any database management system safely). · The Microsoft Office suite of software products is not in your company's approved technology set.· You need to capture time-critical transactions - e.g., from a lab instrument· Any single table in your database could have more than 1 million large to medium-width records, or 5 million small-width records (i.e. 3-4 numeric or short text fields). In practical terms, this means that a CMMS database will be able to hold over 20 years of job records if work is raised at a frequency of ca 100/day. This can be extended further by setting up an archiving arrangement and using union queries to combine data from both archived and current tables.· You would regularly have more than 15 people actively using the database at the same time - for example quick data entry and/or queries and reports. In practical terms, this means that a maintenance department of over 50 people would be supported comfortably.· Your database servers experience periodic, unexpected crashes - e.g. more than 1 per month (in this case you'll have problems with any database system).· You require extensive database security because of the highly sensitive nature of the data. (Although you can get around this issue by using SQL Server as the database engine with an Access front-end.). Additionally, "OEE Manager" is built using a separate, password-driven security system that does not rely on standard Access security.· You will be sharing the database with mixed operating systems (Windows 98, Windows ME, Windows 2000, Windows XP, etc). See an article by Microsoft on how Access databases get corrupted. |
|