Private Cloud Implementation

Once your organization or lab chooses eLabJournal ELN as the best suited ELN solution, a dedicated account manager is assigned to you and will guide you step-by-step through the implementation of eLabJournal ELN.

1 – System Installation
After signing the agreement for delivery of service, eLabNext will start with the installation of the server infrastructure and application. In case specific technical requirements such as SSO/LDAP/AD FS or IP range restrictions are required, eLabNext will reach out to the IT contact person in your organisation. Setting up automated software updates, system monitoring, and automatic back-ups are also part of the system installation procedure.

2 – System Validation
After system installation has been completed, the system is validated by our Quality Assurance (QA) team. A validated data set is migrated to your Private Cloud 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 is the system released for the next step.

3 – Data Migration
In each Private Cloud, 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 using or are currently using the Cloud, the existing data of those labs can be included with the system deployment.

4 – Key-User Training
To ensure that the transition to the electronic lab notebook runs smoothly, the appointed Key-User receives a Key-User training. During this session, the Key-User is trained in basic and administrative 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, perform system maintenance tasks, and provide basic support for end-users in the organization.

5 – System Acceptance
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.

6 – System Delivery
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 Private Cloud 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 Private Cloud.

Get started with eLabNext today

Personal demo, free lab workflow assessment, and friendly expert guidance.