Instrument booking and analysis for your imaging and flow core
Book your imaging and flow instruments in the same place you take in samples and run analysis for the labs you serve, so scheduling stops being a system of its own.
One analysis platform for every lab you serve
Each lab works in its own projects, with every image, FCS file, and result tied to the sample it came from and the analysis that produced it.
Booking
Book instruments against the operating hours you set for each one, with maintenance and calibration downtime that cancels the sessions it lands on and tells the people who booked them to pick a new slot. Everyone gets a reminder before their session. Charging that instrument time back to each lab's grant stays in the billing system you already use.
How most labs do it today. The instrument calendar lives in a system of its own, apart from the samples the core takes in and the analysis it runs, so scheduling is one more tool to keep in step by hand.
Intake
Record every sample that comes into the facility with structured metadata, so what is received, in progress, and returned is one list rather than an archaeology exercise.
How most labs do it today. Knowing what arrived, whose it is, what stage it is at, and what has been returned means cross-referencing three places and asking someone.
Image analysis
Cell detection, area, intensity, and colocalization on LIF, TIFF, and PNG in any browser, z-stacks included: slice navigation, MIP, average, and sum projections, and counts per plane across a stack. Every user analyzes their own data at once, with no per-workstation licence and no install.
How most labs do it today. There's one licensed analysis workstation and a queue for it. Users who can't get a seat leave with raw files, and the analysis waits on the queue.
Flow analysis
Compensation, gating, and clustering in the browser for every user the core serves, with gating templates the facility can standardize on.
How most labs do it today. The same queue, for the same reason. A rotation student who needs one gating run has to wait for a seat or borrow someone's laptop.
Delivery
Results land in the PI's own project with the analysis attached, ready to open, re-run, or export to the formats their lab uses.
How most labs do it today. The handoff is a dead end. The PI gets files with no record of how they were produced, and comes back in six months asking what the settings were.
Locations
Map rooms, freezers, and storage, with equipment records for what they hold and the conditions each location maintains, so the facility is documented rather than remembered.
How most labs do it today. Which freezer holds the returned samples, which room the second cytometer moved to, and what temperature that shelf holds live on a whiteboard rather than in a record.
Reporting
Report what the facility actually produced: how many labs it served, how many analyses ran, and how many figures came out of them.
How most labs do it today. Hours booked is the only number you have, and it measures demand for a machine rather than the science the core enabled.
Start with one instrument
Upload a run and hand back the analysis instead of a folder of raw files, then see what the labs you serve do with it.