Vivarium and Animal Colony Management Software: Why Census, Per Diem Billing and IACUC Limits Never Reconcile

Why a vivarium breaks the systems you point at it

It is 6:20am in a barrier room. A husbandry technician walks a rack with a clipboard, marking cages that need changing, cages with a new litter, and one cage card that reads five animals when there are seven in the box. That card was printed three weeks ago. The census in the facility spreadsheet says something different again, because the last three weanings were emailed to the manager on a Friday and never entered. On the following Friday, the per diem invoice for that investigator's grant goes out on the spreadsheet number, and it is wrong in the direction that costs the facility money.

Every part of that is normal, and none of it is carelessness. A vivarium is not a warehouse with animals in it. A box of screws does not breed, get genotyped, get transferred to a different protocol, die overnight, or count against a federally approved ceiling. The objects you are tracking change identity while you are holding them. Three separate obligations attach to the same cage at the same time: welfare and regulatory compliance under the Animal Welfare Act and the PHS Policy, financial chargeback to a specific fund, and scientific traceability for the study the animals are on. Systems built for one of those three treat the other two as an export.

What RockStep Climb, tick@lab and Topaz actually leave on the floor

These are real products and each is competent at a large part of the job. Climb is the most modern of the three and handles rodent colony structure, genotypes and matings well. tick@lab covers census, ordering and health reporting across a large multi species facility and is used at genuine scale. Topaz Technologies has been in animal facilities a long time and knows the domain properly. None of them is a bad choice on capability grounds.

Where each of them costs you weeks is at the edges specific to your institution. Per diem rate structure is the first. Your rates vary by species, by housing type, by whether the cage sits on a ventilated rack, by quarantine or isolation status, and they change at the start of your fiscal year through a rate approval process that finance controls. That charge then has to land in your institution's general ledger as a journal entry against a fund and account string with a format your finance office dictates. Packaged products ship a billing module built around their rate model, not yours, and the gap between the two gets covered by a spreadsheet and a manual upload every month.

The second edge is the IACUC boundary. Approved animal numbers, species, pain category and protocol expiry usually live in a protocol management system, frequently a different product entirely, while the animals live in the colony system. Nothing joins them continuously. The census can pass the approved number on a Tuesday and nobody sees it until a semiannual review or an annual report is being assembled.

The third edge is hardware. Cage card printing on your printers, your card stock, your barcode symbology and your required fields is a surprisingly large amount of work, and it is the piece your technicians touch every single day. If the cards print slowly or wrong, the system does not get used, and everything downstream reverts to paper.

The protocol limit is a number nobody watches in real time

Exceeding an approved animal number is a reportable matter, and the awkward part is that it almost never happens through a deliberate decision. It happens through breeding. A colony producing more pups than the study needs pushes the cumulative count past the ceiling weeks before anyone runs a report. By the time it surfaces, the animals exist, and the conversation with the committee is about a violation rather than an amendment.

A custom build treats the approved number as a live constraint rather than a document. Every animal record carries the protocol it is assigned to. Weanings, transfers, imports and births write against that protocol's counter as they happen. The system warns at a threshold you set, typically eighty percent of approved, and it warns the investigator and the veterinary staff at the same time so an amendment can be filed while it is still an amendment. It also has to handle the messy realities: animals held on a breeding protocol before assignment to a study protocol, animals transferred between protocols, and the difference between animals used and animals currently alive, because different reporting contexts want different denominators.

Per diem is where the money quietly leaks

Per diem billing looks like a solved problem and never is. The daily charge depends on cage count, not animal count, so a cage that empties on the fourteenth still bills for fourteen days and not thirty. Census changes have to be dated correctly or the month is wrong. Then there are the exceptions that every facility runs: a grace period on newly weaned litters, a reduced rate for quarantine, a flat charge for a procedure room, a subsidy from a core budget for a pilot study, a chargeback split across two funds for a collaboration.

Facilities that bill from a spreadsheet typically undercharge, because the safe error is to leave a charge off rather than to invoice an investigator incorrectly and spend a week arguing about it. Across the animal facility builds we have delivered, the recovered revenue in the first full year has repeatedly covered a meaningful share of the build, purely from charges that were previously being dropped. A custom system computes the charge from dated census events, applies your rate table with your effective dates, produces an investigator facing statement they can actually check line by line, and exports a journal entry file in the exact format your finance system ingests. That last item sounds trivial and it is usually the single most requested feature by the person who signs the invoice.

Breeding colonies are a genetics problem in an inventory costume

A general inventory system can tell you that a cage contains four animals. It cannot tell you that this cage is a homozygous intercross, that pups are due for genotyping on day 21, that this line carries two alleles you track separately, or that the strain nomenclature on the publication has to match what the repository expects. Colony management is pedigree management, and the data model is a graph, not a list.

What a build has to get right here is the mating record as a first class object with dam, sire, plug or pairing date, litter, wean event and resulting cages, plus genotype results attached to individual animals with the assay and date that produced them. Genotyping results usually arrive as a spreadsheet from a core or a vendor, so an import that maps sample identifiers back to animals without manual retyping is not optional. Strain nomenclature should be stored in a form you can present correctly rather than as free text, because free text guarantees that the same line appears three ways within a year.

What a custom vivarium build has to include

• Cage and animal records with dated event history, so census on any past date is reconstructable rather than recomputed from today.
• Protocol assignment with live counters against approved numbers, threshold alerts and amendment linkage.
• Cage card design and printing on your hardware, with barcodes that scan reliably in a room with sanitiser on the gloves.
• Per diem engine with species, housing type and status based rates, effective dating, exceptions, and a general ledger export in your finance system's format.
• Breeding module with matings, litters, weans, pedigree and genotype import.
• Health surveillance records, sentinel programme results and room level status that drives access rules.
• Ordering and receiving from approved vendors with quarantine workflow.
• Investigator facing views so principal investigators can see their own census and charges without emailing the manager.
• An append only audit trail, because inspection questions are about who changed what and when.

What it costs and how long it takes

Across the projects Digital Heroes has delivered in this category, a first release covering census, cage cards, protocol limits and per diem billing runs $70,000 to $150,000 and ships in 14 to 20 weeks. That is a system your husbandry staff use on day one, not a pilot. Adding breeding and genetics, health surveillance, ordering, investigator portal and IACUC protocol integration takes the total to $180,000 to $420,000, phased across 8 to 14 months.

What pushes the number up in animal facilities specifically: multiple species with genuinely different husbandry and reporting, because non human primates, large animals and aquatics are not rodents with a different label. Multiple buildings or institutions sharing one system, because rate tables and IACUC governance then differ per site. Cage card printer and rack reader hardware integration. Barcode or radio frequency identification tagging at the individual animal level. Integration with an existing protocol management system, which is a real interface project rather than a data feed. What keeps the number down: starting with rodents in one building, your current rate table, and the reports you actually send today rather than the ones you wish you had.

When you should buy instead

Buy, and do not spend money with us, if you run under about 2,000 cages, one species, one building, and bill a small number of internal accounts. Climb or tick@lab will cover you and the annual licence is far cheaper than a build. The same answer applies if your facility is stable and your finance office is happy to receive a spreadsheet, because then the integration work that justifies a build has no payoff.

Build when two or more of these are true. Your per diem rate structure has exceptions that no vendor's billing module expresses, and someone spends days a month fixing invoices. You run several species or several buildings under different governance. You have already been cited or nearly cited on an animal number and you know the census is not trustworthy. Your genotype and pedigree data lives in a lab spreadsheet completely disconnected from the census. Or you have an existing system whose vendor will not integrate with the protocol management platform your institution just bought, which is the most common trigger we see.

How to choose a developer for vivarium software

Ask them to draw the data model before you sign anything. A developer who has done this work will separate cage, animal, protocol assignment and event, and will explain why census has to be derived from dated events rather than stored as a running number. A developer who draws animals and locations has built an asset tracker and is about to learn animal science on your budget.

Ask specifically how per diem is computed and how a correction to a past month is handled. If the answer does not include effective dated rates and a restatement path, the finance office will reject the output in month two.

Ask what they have integrated. A protocol management system, a general ledger, a genotyping vendor's result file and a cage card printer are four different classes of problem. Ask for the specific system and the specific interface, not a general claim about integrations.

Ask who owns the code and get it in writing before kickoff. You should own the repository, the infrastructure accounts and the right to hire anyone else to continue the work. At Digital Heroes the code is yours from the first commit, and we would tell you to walk away from any developer who hedges on that.