Private Cloud Implementation

For a smooth transition from paper lab notebooks to eLABJournal ELN

Once your organisation or lab chooses eLABJournal ELN as the best suited ELN solution, a dedicated account manager is assigned to you and will help you step-by-step with the implementation of eLABJournal ELN.

1 – System Installation

After signing of the agreement for delivery of service, Bio-ITech will start with the installation of the server infrastructure and application. In case of specific technical requirements such as SSO/LDAP/AD FS or IP range restriction are required, Bio-ITech will contact the IT contact person in your organisation. Also setting up automated software updates, system monitoring and automatic back-ups is 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 eLABJournal 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, the system is released for the next step.

3 – Data Migration

In each eLABJournal Private Cloud, one or more Key-Users are appointed by the organisation. The Bio-ITech 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 eLABJournal Cloud, the existing data of those labs can be included with the system deployment.

4 – Key-User Training

To ensure that 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 is 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.

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 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 eLABJournal Private Cloud and all system configurations in the eLABJournal Cloud are activated to ensure correct routing of all apps and add-ons. In case there are users in the eLABJournal 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.