Once your organisation or lab has selected a license plan, a dedicated account manager will provide you with a step-by-step implementation of your chosen software.
After signing the agreement for delivery of service, eLabNext will start with the installation of the server infrastructure and application. If there are any technical requirements (i.e. SSO/LDAP/AD FS or IP range restrictions), eLabNext will reach out to the IT contact of your organisation. Also included in this step are software updates, system monitoring, and automatic back-ups.
The installed system is validated by our Quality Assurance team. A validated data set will then be migrated to your On-Premises installation. Next, a full functionality test is performed on all basic system functions, installed components, and available add-ons. Any incorrect configurations are reported back to the system engineer. Only after the resolution of these issues is the system 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 in eLabJournal. If labs in your organisation have been or are currently using the Cloud, the existing data of those labs can be included with the system deployment.
For a smooth integration of your electronic lab notebook, your appointed Key-User will receive Key-User training. The session includes training on basic, administrative end-user functionalities, and advanced system features. As a Key-User, you will be trained how to control system settings and policies, perform system maintenance tasks, and provide basic support for end-users in the organisation.
Once the system installation is complete, the system is delivered to the organisation Key-User for formal acceptance. If data of existing groups are migrated into the system, the Key-User may verify with the existing group administrators and end-users that
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 eLabJournal Cloud environment remains available for end-users to work in.
After System Acceptance of the 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 which won’t be migrated to the On-Premises installation.