Understanding Az Ontrack Science Center
Az Ontrack Science Center is a specimen tracking and workflow management system designed for research labs that handle high-throughput sample processing. It runs primarily as a web-based platform with a local database backend, and it integrates with existing LIMS setups through REST API calls. Most labs deploy it to track samples from receipt through barcoding, storage location, and eventual disposition. The core value is eliminating the spreadsheet mess that grows organically once you cross fifty samples per week. Without it, someone is always losing track of which box contains which aliquot, and the reagent lot numbers end up scattered across three different Google Docs. Az Ontrack Science Center centralizes that data in a way that makes audits actually bearable.
Setting Up Az Ontrack Science Center
The standard deployment starts with installing the backend service on a dedicated machine or virtual server. You need at least 8 GB of RAM and a solid-state drive — the database queries on large sample sets will choke on spinning disks. The installer script handles most of the dependencies, but you will need Node.js version 18 or higher pre-installed, and the PostgreSQL backend version needs to be 14 or later. Anything older tends to throw timeout errors during batch imports. After installation, you create a workspace. The setup wizard walks you through defining your sample types, storage formats, and user roles. This step matters more than people usually give it credit for. If you define your freezer box layouts correctly upfront — including which drawer corresponds to which row on your rack maps — you save hours later when you're doing inventory reconciliation. I made the mistake early on of letting the default template handle my deep-freezer organization, and it assumed a standard 8x12 rack layout. My freezers use hybrid configurations with some 96-well plates and some cryovial boxes. The mismatch caused misreads whenever I tried to bulk-export location data for the first month of use.
How It Actually Works Day to Day
Once configured, the daily workflow is straightforward. You receive a shipment, scan the incoming barcode, and the system auto-populates the sample metadata form based on the manifest you uploaded. From there, you assign storage locations, which can be updated in bulk by importing a CSV mapping file. The interface shows your entire inventory as a grid with color-coded status indicators — received, processed, stored, exported, or quarantined. The quarantine flag is useful when you get a contaminated batch and need to isolate it without deleting records. One thing beginners miss is that the search function supports nested logical operators. You can query for samples that match multiple criteria simultaneously, like "stored in freezer B AND processed after 2024-03-01 AND associated with project X." This cuts down time on retrieval from maybe ten minutes of manual searching to about thirty seconds. The export feature also supports custom field selection, so you can pull just the barcodes and locations for a cold-chain audit without dumping the entire dataset. API access is where Az Ontrack Science Center really separates itself from cheaper alternatives. You can automate repetitive tasks like daily syncs with your sequencing core, automated aliquot tracking, or pulling QC metrics into your analysis pipeline. The documentation covers the standard endpoints well, but it does not cover edge cases like concurrent write operations from multiple users editing the same sample record at the same time. I ran into a conflict loop once where two technicians were updating the same plate record simultaneously, and the system silently dropped one of the changes. The fix was implementing a simple lockout mechanism on the high-turnover sample groups using the API's advisory lock endpoint. It adds about two seconds of latency per write, but it prevents data loss.
Get the Full Details
Pitfalls and What It Cannot Do
Az Ontrack Science Center does not handle hardware integration natively. If you want barcode scanners or robotic liquid handlers to feed data directly into the system, you need to build those connections yourself or use a middleware layer. Several labs I know have wrapped it with Python scripts that read from their plate readers and push updates every fifteen minutes. That works, but it is a maintenance burden. Another limitation is the licensing model. The per-seat pricing scales linearly, and if you have a large team with varying access levels, the costs add up faster than you might expect. Some institutions opt for the enterprise tier, which includes priority support and custom integrations, but the baseline tier is quite functional for smaller labs operating under twenty users. The mobile app exists but is essentially a read-only viewer with basic barcode scanning capability. You cannot perform full CRUD operations from the phone, which matters if your freezers are in a separate building and you need to log sample movements in real time. The workaround I use is keeping a dedicated tablet at each freezer station with the web interface pinned to the sample entry screen. It is not elegant, but it eliminates the trip back to the office to log a relocation.
Where to Get It
The official download and licensing portal is accessible through the Az Ontrack Science Center website. They offer a fourteen-day trial with full functionality, which is sufficient to evaluate whether it fits your lab's workflow. After that, you select a tier based on your user count and integration needs. Support responses during business hours are generally within a few hours, though ticket resolution for non-critical issues can take a day or two depending on the queue. If your lab already uses a major LIMS platform like LabWare or SampleManager, Az Ontrack Science Center can plug in as a complementary tracking layer rather than a full replacement. The integration points are documented in the developer portal, and the pre-built connectors cover the most common scenarios. Custom connectors require some development work, but the API is RESTful and well-structured, so it is not particularly difficult to build one if you have someone with web development experience on staff.
