Once your organisation or lab chooses eLabNext products, a dedicated account manager is assigned to you and will help you step-by-step with the implementation of eLabJournal ELN.
After signing the agreement for delivery of service, eLabNext will contact the IT contact person in your organisation to assist in setting up the server infrastructure. Once the servers have been set up, eLabNext’s system engineers will install the product application on your servers. eLabNext also provides general guidelines to set up system monitoring and automatic back-ups to make sure that end-users receive the best possible service.
After system installation has been completed, the system is validated by our Quality Assurance (QA) team. A validated data set is migrated to your On-Premises installation to perform a full functionality test of all basic system functions as well as all installed components and available add-ons. Incorrect configurations are reported back to the system engineer and only after these issues have been resolved, the system is released for the next step.
In each On-Premises installation, one or more Key-Users are appointed by the organisation. The eLabNext account manager will set-up system accounts for the appointed Key-Users in a dedicated Functional Key-User Group. If labs in your organisation have been using or are currently using the Cloud installation, the existing data of those labs can be included with the system deployment.
To ensure that the transition to the use of the electronic lab notebook runs smoothly, the appointed Key-User receives a Key-User training. During this training, the Key-User has trained in the basic and advanced end-user functionalities as well as the advanced system features. As a Key-User, you are also trained in how to control system settings and policies, how to perform system maintenance tasks, and to provide basic support for end-users in the organisation. Read more about the training services we provide.
Once the system installation has been completed, the system is delivered to the organisation Key-User for formal acceptance. In case data of existing groups is migrated into the system, the Key-User can verify with the existing group administrators and end-users that all data has been correctly migrated. During the system validation test, the Cloud environment remains available for end-users to work in.
After System Acceptance of the eLabJournal installation, the final date for the delivery of the system will be scheduled. During the system delivery, the most recent data is migrated in the On-Premises installation and all system configurations in the Cloud are activated to ensure correct routing of all apps and add-ons. In case there are users in the Cloud, access to the Cloud will be blocked prior to system delivery to prevent users from entering data in the Cloud that is not migrated to the On-Premises installation.