← all work

case-study / ecocommons

EcoCommons — national ecological modelling platform

TECHNICAL LEAD & SOLUTIONS ARCHITECT · GRIFFITH UNIVERSITY · 2020–2023

ardc.edu.au/project/ecocommons — public; reference available ↗

ECOCOMMONS · PLATFORM SCREENSHOT

platform UI · public ARDC asset · ~1200×675

EcoCommons is Australia's national platform for ecological and environmental modelling — species distribution, climate projection, biodiversity and biosecurity analysis — used by researchers and government across the country. I was its Technical Lead and Solutions Architect: I designed the platform and its infrastructure, and led the engineering team and partner institutions through to launch.

The hard part was never any single model. It was making national-scale, reproducible science work across nine partner organisations, four scientific disciplines, and a decade of incompatible legacy systems — and making domain experts productive on infrastructure they didn't build. EcoCommons re-engineered earlier research tools (BCCVL, ecocloud, CSDM) into one coherent, modern platform: a curated microservice “app store” of analytical workflows, an integrated data explorer wiring in national and global providers (ALA, TERN, GBIF, OBIS, IMOS), a cloud analysis sandbox with JupyterLab and virtual desktops, and reproducible-by-design environments so a published result can actually be re-run.

Two lessons from that work shape how I build AI systems now. First, reproducibility as a load-bearing requirement rather than a nicety — versioned environments, FAIR data, provenance on every result — which is exactly the discipline I now bring to evals and agent telemetry. Second, that the real engineering problem in a multi-stakeholder platform is making domain experts productive on systems they didn't design: give the expert a clean surface, hide the orchestration, keep the trust boundary honest. That turns out to be the same problem as agent design.

ECOCOMMONS · DATA + COMPUTE TOPOLOGY

9 institutions · multi-cloud · FAIR pipelines · ~1000×500

This is the national-scale, multi-institution, ship-it-to-launch credential beneath everything else on this site — the twenty-year foundation the frontier work is built on.

signal

role
Technical Lead & Solutions Architect
scope
national · 9 partner institutions
program
~$5M · 3 years · 2020–2023
domains
biodiversity · biosecurity · hydrology · agriculture

tech

distributed cloud + HPC microservice architecture species-distribution & climate models FAIR data pipelines JupyterLab / virtual-desktop sandboxes reproducible-by-design environments

Want something like this built?

Thirty minutes. Bring the architecture diagram or the screenshot of the bug — whichever is closer to where you're stuck. I'll tell you what I'd build, what I wouldn't, and whether I'm the right person for it.