🚢Deployment tracker

What we needed to support

We wanted to to solve several problems with the Deployment Tracker. All of which have to do with the process of removing carbon from the fast cycle and storing it in the slow cycle.

Contextualize and centralize the significant breadth of data gathered for each deployment
Provide a single source of truth for all inputs, records, and evidence of events happening during the lifecycle of a deployment
Streamline the process of carbon deployment operations by facilitating record-keeping and communications between Running Tide, production facilities, and vessel operators.

What we built

A software solution that models the processes used on site and provides an interface to capture various events throughout the lifecycle of each intervention. The primary focus of the solution is the tracking of terrestrial biomass sinking carbon deployments, but it also has capabilities for different types of research deployments such as open-ocean macroalgae growth and sensor-only trials.

Each Intervention could have associated data:

batches representing different recipes substrate being deployed
events
buoys
lab experiments
automatically generated reports
results from data model runs

The deployment tracker allowed us to visualize the tracks of individual buoys and understand the status of permits and lab experiments. We included these features to allow us to connect data to deployment activities, deployment events, and important documents of record.

What we would’ve wanted to build next

With new locations would come different processes that would need to be handled with different events and different data visualisations. More automation would have been required to publish quantification results and generate carbon ledger transactions. Data model results, which had historically been reviewed and added manually, would have been automatically published to individual interventions.