In our experience, based on hundreds of projects, these are the factors, in descending order of importance, for the success of an edinn project:

  1. Once edinn is installed, and after an adaptation period (for example 3 months), force the work center where edinn was installed to have their ratios (OEE and other), and their trend, to be available remotely through the edinn, and to be correct according to the diagnosis and trends reports.
  2. The work center is producing normally that which is about to be controlled and improved with edinn, at least, 1 month before installing edinn.
  3. The work center incorporates the ratios provided by edinn into its daily management routines.
  4. Correct management of those professionals which prefer not to be objectively evaluated and that do not want their superiors to have objective and real time information about their performance.
  5. Minimize personnel rotation or insufficiently trained on edinn. If this is not possible, it is recommended to:
    1. In organizations with multiple work centers (multi plant), train a small, specialized and centralized team which can provide support and lead the installation and use in case any of the work centers could not because of personnel rotation.
    2. To nominate multiple edinn local leaders in each work center.
  6. Sufficient training of the edinn local leaders in the work center.
  7. In organizations with multiple work centers, to have a small, specialized and centralized team (at least 1 person, but it could be more depending on the needs) to be, if necessary, 100% dedicated to the edinn platform, and to be trained and capable to support the work centers.
  8. Enough visibility of the edinn platform in terms of flat screens or screen savers in the terminals to get profit of the motivation that the edinn platform can provide.
  9. Wide and successful experience installing edinn of the installer team, with no linguistic barriers with the local edinn leaders.
  10. The edinn platform relies on multiple systems which must be fast and robust, because any slowness or failure of these systems will be attributed to edinn and its partners, although it is not being caused by the edinn standard. This happens because edinn is the visible part of many back-end systems, for example:
    • PLCs, OPC Servers and, in general, systems or developments for data acquisition.
    • Computerized infrastructure like servers, terminals, data networks, etc.
    • Customized developments (API and/or UDL).