How SciCord ELN Works

The SciCord ELN feature set is designed to quickly propel your organization into the digital age. It delivers on this promise using a secure architecture and a versatile Software-as-a-Service model.

  • SaaS minimizes your total cost of ownership
  • Maintenance and backups are included minimizing IT overhead
  • SciCord provisions required hardware, eliminating initial hardware purchase and refreshes
SciCord is provided through a SaaS model

SciCord is designed with Security in mind
  • Award winning Azure cloud platform meets a broad set of international and industry-specific compliance standards, such as General Data Protection Regulation (GDPR), ISO 27001, HIPAA, FedRAMP, SOC 1 and SOC 2.
  • Encryption at rest and in transit
  • Replicated solution across two physical locations
  • Backups to two physical locations, Incremental Daily, Full Weekly, Full Monthly
  • Completed document bundles provided to customer for on-site storage

Azure Servers utilized by SciCord

SciCord ELN utilizes the Azure server network, making a SciCord Solution accessible around the globe.


  • SciCord ELN is designed to integrate into a customer’s environment.
  • For applications such as LIMS, SAP, ESM, and Metrology, the integration method of choice is Web Services with bidirectional exchange of information.
  • Other supported integration techniques include API, Database Access, and File Transfer.
SciCord integrates with a variety of third party software

SciCord Client is deployed on an IIS web server and is downloaded and executed on the user’s desktop either inside a Browser supporting the Silverlight plugin, or out of the browser, using the Silverlight standalone client (OOB – out of browser).  Data interactions occur between the SciCord Client application and SciCord Data Service that will read and write changes to the underlying database. The same happens for the BLOB interactions, where SciCord client reads and writes binary files calling a corresponding SciCord Web Service that, on its end, connects to the Azure BLOB infrastructure.

Additional applications or systems may interface to the system as well, consuming services exposed by SciCord WebApi or listening to the Events System.

Documents, experimental data, and templates are stored in the SQL Server database and in the Azure BLOB infrastructure. SciCord client can connect to the local PC serial port and can open TCP sockets to connect to “real-time” instruments line digital balances and scales.

SciCord Portal connects to the SQL Server database and the storage service, through the standard shared connection layer as well.

SciCord Bundler is a Windows Service that listens for incoming requests sent through specific Azure Blob Queue and, asynchronously, access the database though separated instances of the standard access layer library.

SciCord is built on a robust, secure architecture