Hardware Requirements
The minimum hardware requirements for a system to run SEDRI-LIMS are as follows:
Processor
Quad core 8th generation Intel or equivalent.
Memory
16 Gigabytes minimum, 32 Gigabytes recommended.
Storage
While this will depend on laboratory throughput and backup frequency, 100 Gigabytes is considered the minimum viable allocation.
Software Requirements
The minimum software requirements for a system to run SEDRI-LIMS are as follows:
Operating System
Windows Server 2019 or later.
Security
The connection between browser and back-end is secured by SSL. This requires a valid X.509 certificate, which is the host’s responsibility to purchase and configure. JSON Web Tokens (JWT) are used to secure a user session. Differential user access to system functions is managed using role based access control with highly granular permissions. Access to the server running the database & database security in general are the responsibility of the host.
Connectivity
Local UI Clients
Wired or wireless network access to the system must be provided to all required local clients, including desktop(s), laptop(s), tablet(s) or phone(s). Beyond a browser and network connectivity, there are no other client software dependencies.
External UI Clients
If extending the UI to remote clients via the Internet, firewall access will need to be provided. This is the responsibility of the host.
Laboratory Instruments
Bi-directional network access will be required for any laboratory instrument(s) with which SEDRI-LIMS is configured to interact. These may include the BioMerieux BacT/ALERT, Vitek 2 or Vitek MS, the BD BACTEC FX, Phoenix M50 or Brucker MALDI-ToF. Providing this network access is the responsibility of the host.
Installation Process
A PowerShell script will be made available to run on the target server. This will install an Azure Pipeline Agent (Azure Pipelines Agents - Azure Pipelines | Microsoft Learn), allowing Arcta to remotely install and configure all required artefacts, i.e. the application, Microsoft .Net 8 and Postgres. SQL scripts will also be executed to configure the database based on the needs of the specific deployment. Temporary access to the UI will be required for testing.
Backups
The database should be regularly and securely backed-up to a separate storage capability at a frequency of the host’s choosing. This is the responsibility of the host.
Support and Maintenance
There are various aspects and options depending on the level and type of support required.
Staging and Production Environments
A staging area is required for a separate app, database and web service to allow new versions of the system to be tested in situ prior to live use. This can be collocated with the live app or on a separate server. Following an upgrade, host sign-off will be required before a new version can be deployed to the production environment.
Raising Issues
Once the system has been fully deployed and is in active use, any issues must be raised via the official support channels, allowing them to be tracked by both parties to resolution. Access details will be provided.
Remote Access
Once the server is registered as an Azure Pipeline Agent (see Installation Process), updates can be performed remotely on pre-arrangement. Temporary access to the UI will be needed for testing updates before they are deployed to the production environment. Ongoing remote access will facilitate advanced configuration changes, debugging and retrieving log-files. For such purposes, VPN access would permit the use of RDC. Alternatively, other remote access applications can be used, under supervision, to provide managed access to the system. If remote access cannot be provided in any form, it will become the host’s responsibility to manage all configuration changes and to extract and provide system logs (on request) to assist with debugging any issues that may arise.