The investigator initiates a project by creating an account on the LIMS portal (if none exists) and entering a project description in the laboratory notebook and by submitting all ancillary data such as buffer composition, analyte properties, gel images, absorbance scans, etc. to the database. Subsequently, an experimental design is added to the notebook. Next, the operator sets up the experiment by directly linking all acquired AUC data from within the data acquisition software (AU-AOS) with the investigator’s database entries for each sample and commences the data acquisition. Communication between the AU-AOS and the US LIMS database is brokered by the NDS module. At this point, each experiment has a unique identification and the investigator identity associated with it which will carry forward through all data processing, analysis, and results presentation. During data collection all experimental data are forwarded to the US LIMS for storage in an internal, compressed binary format for maximum efficiency. A separate data conversion module assists with the import of data in legacy formats into the US LIMS. An export module permits export of US LIMS data to legacy formats for import into existing third party analysis software. In the next step, the experimental data are edited by storing all necessary transformations (meniscus position, data range minimum and maximum, baseline corrections, etc.) in the LIMS database as a separate dataset for each channel. Third party software will be able to import experimental data, store analysis results, and query the LIMS via the NDS. Edited data can be further processed by either a supercomputer-based analysis or by local UltraScan analysis using a control file to store experiment, cell, and channel information relevant to the analysis. Each channel produces a number of result files which are uniquely named by the analysis software according to a predefined standard. All analyses belonging to a channel are then grouped into a compressed archive and stored in the results database tables. During off-line operation, the data can be processed from the user’s computer without the requirement of an Internet connection. When Internet connectivity is again available, the results can be synchronized with the contents of the database. The proposed database structure is shown in the electronic supplementary material (Figure SI 1).