Why it matters
Without it, breeding decisions risk genetic bottlenecks, misalignment with SSP goals, unapproved transfers, and welfare concerns that can trigger inspections, licensing issues, and accreditation risks.
From design to safety
Design
AI guides genetic planning and SSP alignment
The system reads studbook kinship values, species SSP goals, risk thresholds, welfare considerations, and the genetic management plan to propose initial breeding and transfer strategies with audit-ready rationales.
- Genetic Diversity Database
- ZIMS Breeding and Transfers Module Server
- EEP/SSP Planning Binder
Build
Implement data pipelines for planning
Data feeds from studbook databases, EEP/SSP documents, pathology reports, health surveillance, and transfer permits validate and tune the initial breeding plan for live use.
- Animal Genetics Lab Computer Workstation
- Genetic Diversity Database Archive
- Quarantine Entry Isolation Chambers
Operation
Ongoing optimization of breeding plans
The system runs quarterly re-evaluations of pairings, fertility windows, genetic metrics, and transfer readiness using updated health and welfare data and keeper observations.
- ZIMS Breeding and Transfers Module Server
- Animal Transfer Tracking Console
- Genetic Diversity Database Archive
Maintenance
Maintain data integrity and records
Regular audits of pedigree, kinship coefficients, heterozygosity indices, and permit compliance ensure records stay current for regulatory reviews and SSP reporting.
- Animal Genetics Lab Computer Workstation
- Genetic Diversity Database Archive
- EEP/SSP Planning Binder
Safety
Safeguard welfare, compliance, and licensing
The AI flags welfare risks, ensures permits are valid, and routes alerts to registrars and licensing bodies for review, while enabling documented post-action reviews.
- Quarantine Entry Isolation Chambers
- Staff Training and Welfare Evaluation Room
- EEP/SSP Planning Binder
Part by part
- 1
Genetic Diversity Database
- Watch for
- Mismatch between kinship values and observed inbreeding indicators; unexpected allelic dropout in genotyping results.
- AI action
- Flag risk level, trigger review, and propose alternative pairings for discussion.
- 2
ZIMS Breeding and Transfers Module Server
- Watch for
- Data lag or missing transfer permits in PIFs and CITES documentation; inconsistent fertility windows.
- AI action
- Trigger data reconciliation, alert breeding coordinator, and lock plan modifications pending review.
- 3
EEP/SSP Planning Binder
- Watch for
- Outdated SSP goals not aligned with current population genetics or disease risk profiles.
- AI action
- Suggest SSP update agenda, recommended transfers, and contingency routes.
- 4
Animal Genetics Lab Computer Workstation
- Watch for
- Anomalous kinship estimates from genotypic panels; sample mislabeling detected.
- AI action
- Run quality checks, flag anomalies, and propose confirmatory tests with results routing.
- 5
Genetic Diversity Database Archive
- Watch for
- Inconsistent digitization of pedigree records across subspecies; deprecated identifiers.
- AI action
- Initiate harmonization workflow, enforce standardized metadata, and secure backups.
- 6
Staff Training and Welfare Evaluation Room
- Watch for
- Gaps in welfare indicators linked to transfer pressure; enrichment scores stagnate.
- AI action
- Recommend welfare review, design enrichment adjustments, and document trainer observations.
Worked example
Catching a sealed transfer risk before a charter
Illustrative scenario with sample data.
A mid-sized zoo anticipates a transfer under SSP guidelines and requires a genetics-backed recommendation to avoid inbreeding while meeting permit conditions.
Signal in
kinshipMatrix: 0.12; populationSize: 42; plannedTransfers: 3; SSPGoals: ‘increase_Y subspecies’; permitStatus: ‘pending’; healthFlags: ‘clear’; fertilityWindow: ‘28-35 days’; recentGenomicPanel: ‘OK’; cageMatch: ‘yes’
System out
alert: low-risk mating pair found; recommended transfer window: 3 weeks; route: internal • permit: pending review by registrar; notes: confirm quarantine bed availability; welfareScore: 78; geneticDiversityIndex: 0.62; documentation: complete
Human sign-off: Breeding Coordinator reviews alert, validates permits, veterinarian signs welfare review, and signs off before notifying transport team; SSP Manager approves final plan and records in ZIMS.
How to roll it out
Phase 1
Weeks 1 to 4
Baseline data integration, SSP alignment, and governance sign-off across breeding plans and permits.
Phase 2
Weeks 5 to 8
Pilot recommendations run in parallel with existing workflows; policy adjustments documented for cross-park use.
Phase 3
Weeks 9 to 12
Full adoption with governance sign-off, routine SSP reporting, and archival of decisions for licensing.
Where people stay in charge
- Decisions about mating and transfer timing must be approved by a certified breeding coordinator or registrar with rationale.
- All genetic risk flags require veterinary and animal welfare committee review before action with written authorization.
- Permits, licenses, and welfare constraints must receive sign-off from licensing authorities and accreditation bodies with audit trails.
Questions owners and crews ask
What data sources feed the AI breeding recommendations?
The system ingests studbook kinship values, population genetics metrics, SSP/EEP goals, health records, fertility windows, and current transfer permits for decision support.
Who approves AI-driven mating or transfer plans?
A breeding coordinator or registrar reviews AI-generated recommendations, with veterinary and welfare committee sign-off as required by policy.
How does the system handle welfare risks flagged during planning?
It elevates welfare alerts to the animal welfare committee and requires enrichment and welfare adjustments before any action.
What records are produced for licensing and accreditation?
Generated mating plans, transfer itineraries, permit references, health flags, and welfare assessments are archived in ZIMS and the SSP planning binder.