Have you decided how many and which machines or production lines do you need to monitor?
Do you have your Payment Code or Transaction Id? You will need it to create your company in edinn.
If you need local service:
Have you signed and stamped the Installation Purchase Order and/or the Service Conditions and accomplished the indicated conditions?
Access and/or work documentation: if the edinn system installer is external to your company, and you require any type of documentation (Labor Risks Prevention or similar) and/or authorization to enter and/or work in your facilities: have you sent to the edinn installer this documentation to be able to enter and/or work in your facilities?
Has the edinn installer returned to you this documentation and it is all correct?
Have you nominated professionals inside your organization who will be the leaders of edinn? Their role will be to:
Take care of edinn (like if it was another machine of the facility) to assure that it is working properly, containing correct data, generating valuable information and satisfying the users.
Become the unique point of contact with edinn.
Please remember to nominate as many professionals as possible if your organization has a high personnel rotation.
Ethernet Data Network:
You need an ethernet computer data network to connect the machinery and the operation terminals with the EDINN server.
It is recommended that you separate your “office” network from the “production” (workshop) network. There are many ways to do this, but a simple way is to just create a different data network for the workshop. For example, the “office” data network could be 192.168.1.X, and the “production” data network could be 192.168.2.X. The easiest way to do this is by creating 2 separated data networks, installing 2 network cards to the edinn server and connecting each of these cards to each network, making this server the unique common point between these 2 data networks.
Have you requested, to the computer network responsible, the fixed IP addresses for the eBOXes and/or PLCs and the server?
Do you have available an RJ45 plug, or a Wi-Fi access point with RJ45 (not recommended to be USB), to supply data network to each of the operation terminals?
Do you have available an RJ45 plug, or a Wi-Fi access point with RJ45 (not recommended to be USB), to supply data network to each of the monitoring devices (eBOXes or PLCs)?
Power supply:
Do you have available a plug to supply electricity power to each of the operation terminals?
Do you have available a plug to supply electricity power to each of the monitoring devices (eBOX or PLC)?
Minimum requirements of the Internet connection:
When your edinn server is cloud:
Have you tested that the minimum download and upload bandwidth are achieved?
Upload: 3600 bits / second (normally is half of this).
Download: up to 350 K bits / second (normally is half of this).
When your edinn server is local:
If you require access to your edinn web reporting from outside your organization: have you opened the necessary ports in your firewall (normally is port number 80)?
If you require using the edinn eCloud Sync to be able to access your edinn web reporting tool from outside your organization and to assure a backup copy of all the data external to the organization: have you opened in your firewall the necessary ports? (please request to your installer what will be this port number).
Hardware minimum requirements. All hardware requested to edinn will comply with these minimum requirements:
For terminals or monitoring elements like sensors and PLCs: have you checked that these elements have the required minimum specifications?
Have you informed to the edinn installer about the work load that you estimate for your edinn server? Including:
The number of users that will use the system: number of terminals and number of users of the web reporting tool.
Software modules that will be activated, or that you think will be activated in the future.
If you are going to use your own monitoring elements (eBOXes or PLCs): have you assigned fixed IP addresses to these elements?
When your edinn server is local:
Minimum requirements for an edinn Server can be found in the Terms and Conditions.
Are you aware that the backup copies, the availability of the server and the possible redundant elements to guarantee its availability are under your responsibility?
Have you decided where will you store the files of the backup copies? It should be a safe storage unit outside of the server, and if possible, outside of the work center.
Have you considered the elements (Uninterruptible power supply, redundancy, etc.) that you require guaranteeing the maximum availability of the server?
Have you assigned a fixed IP address to the server?
The edinn support team uses its own tool (ISL) to provide remote on screen support:
Do you authorize the use of this tool, or should the edinn support team use your own remote support tool?
Have you opened the TCP/IP ports which are necessary for this remote support tool (for the edinn’s support tool, ISL, these ports are TCP 7615, 80 and 443) or the ports of your corporative remote support tool?
Operation Terminals. There are 3 possible applications to use the edinn platform:
Web reporting tool: edinn web reports are multiplatform and therefore they should run on every explorer, as long as it is not very outdated.
Edinn terminal for Windows (full functionality): we normally provide or recommend robust touch Microsoft Windows PC terminals which are IP-65 certified (protected against dust and water), at least in the front, and, therefore, there is no need to put the PC terminal inside a cabinet. The terminals can be placed on a table, or attached to walls or to metal cabinets. Please see picture below.
Minimum requirements for an edinn PC terminal can be found in the Terms and Conditions.
Edinn terminal for iOS, Android or Windows (limited functionality): PCs, mobile phones or Tablets can be used.
ERP Integration: the edinn platform has available a module which makes it compliant with the ISA-95 Standard. Please request more information if you are interested in connecting your edinn platform with your ERP (Microsoft Navision, SAP, etc.).
Production interruption: in most cases edinn can be installed without having to stop the affected processes. But sometimes, this is not the case:
To minimize the impact on production it is necessary that you schedule, with your edinn authorized installer, the possible stops of the machines where the edinn system will be installed.
Training: after installing the devices, verifying the installation and adjusting configuration, the training is performed to the people that will use the system, for them to know how to get the most out of it.
Have you designated the persons who should receive the training, considering these profiles?
Operators and supervisors: they will need approximately between 30 and 60 minutes of training.
Management and supervisors: they will need approximately 60 minutes of training.
Administrators of the system: they will need a minimum of 2 hours of training.
Have you considered that these persons will not be able to work while they are in this training?
Support: once the system is installed, for questions, issues or improvement suggestions, please use the edinn on-line support system available here: http://ecloud.edinn.com/support/
Please do not use any other channel to request service, like email or telephone, as to do so will worsen our service to you, due to the fact that the follow up is much more difficult through these other channels.
You need a user and password in order to use the edinn on-line remote support tool. If you do not have them yet, please request them by sending an email to support@edinn.com, indicating:
EMAIL: NAME: LASTNAME: NAME OF THE COMPANY: LOCATION: MOBILE TELEPHONE NUMBER (as dialed from another country): FIXED TELEPHONE NUMBER (as dialed from another country):.
