Storage sites

A storage site is a location where carbon is stored. What a site represents depends on your protocol: You add and manage your sites in the Storage sites section. The section also holds the additional data your protocol requires for those sites, on separate tabs. A Biochar project has a Biochar applications tab. A project whose modules require sample data has a tab for each sample type.

​

Add storage sites

Every storage site must have a name, a unique reference ID, a storage method and a geometry. Certify offers two ways to provide the geometry. The way you see depends on your protocol. The table lists each site with its name, reference ID, description, storage method, geometry and validation status. Click a row to open the site. If a site is a polygon, click View on map in the geometry column to see it on the map. To delete sites, select them with the checkboxes and click the Delete X items button. A site that other data already links to shows a lock icon, and you cannot delete it.

​

Biochar applications

A Biochar project logs each application of biochar to a storage site on the Biochar applications tab. A biochar application is a discrete instance in which a specific amount of a defined batch of biochar is applied to a storage site at a particular point in time. Each application must have a unique reference ID, report the application rate, and include verifiable evidence of the mass of biochar applied.

​

Upload biochar applications

1. Go to the Biochar applications tab.
2. Click CSV template to see the columns Certify expects, or Data example to see populated data.
3. Populate the template and export it as a CSV.
4. Click Add biochar applications, select your file, and click Submit.

The template contains these columns:

​

View biochar applications

The Biochar applications tab on the Storage sites page lists every application in the project. To see only the applications for one site, open that site and go to its Biochar applications tab. Each row shows the reference ID, the application date, the production batch, the storage site, the application rate, both truck masses, and the sources attached to the application. Click the production batch or storage site reference ID to open that asset. To delete applications, select them with the checkboxes and click the Delete X items button. An application that a GHG entry already links to shows a lock icon, and you cannot delete it.

​

Storage sites with monitoring requirements

Projects using protocols with storage modules may require regular submission of monitoring reports to comply with module requirements. Certify supports creation of monitoring submissions through either the UI or API. Monitoring requirements are defined by the storage modules included in your protocol. Monitoring submissions are currently configured for projects using the following storage modules:

• Biomass or Bio-oil Storage in Salt Caverns
• Subsurface Biomass Storage
• Biomass or Bio-oil Storage in Permeable Reservoirs (or the modules superseded by it)
• CO₂ Storage in Depleted Hydrocarbon Reservoirs

The CO₂ Storage in Saline Aquifers Module will be supported shortly. Watch this walkthrough to understand the process and read the documentation below.

​

The monitoring plan

Monitoring submissions are added for specific storage sites, which must be created prior to submitting monitoring data. See Add storage sites. Storage sites have a “Requirements” tab, detailing requirements required for validation, and a “Reversal monitoring” tab, that shows the site’s monitoring plan and where submissions of monitoring data can be made at verification. A site’s monitoring plan is made up of a list of monitoring requirements. These detail the monitoring data that needs to be submitted for ongoing project validity. Each requirement has the following attributes:

• Monitoring phase (Operation, Pre-operation or Post-operation)
• Parameter name
• Frequency (e.g. Every day, Once, Monthly, Optional)
• Monitoring method

Monitoring requirements are generated automatically for each storage site when it is created, based on the storage modules in your project.

​

Site validation

After creating a storage site, on the “Requirements” tab make submissions against all requirements. There are two requirements regarding submission of an operational monitoring plan and a post-operation/post-injection monitoring plan. For these, complete your plan in the “Reversal monitoring” tab and use the text submission to highlight any deviations or additional requirements not covered. To complete your monitoring plan in the “Reversal monitoring” tab, first set the frequencies for requirements that are “As per site” (requirements “As per module” already have their frequency set). Then, describe the monitoring method for all requirements. Once your plan is complete in the “Reversal monitoring” tab and all validation requirements have submissions, submit your site for validation.

​

Monitoring submissions

Once the monitoring plan is defined on your project you can add data submissions against each monitoring requirement. This is required for verification. To add a submission in Certify, click the action link on the monitoring requirement and then the + Add submission button. The submission dialog will allow you to upload a data source file, set the validity period of the submission and add any guidance notes for the verifier to pay attention to, for example a specific page number within a multi-page report. The same submission can be linked to multiple requirements, for example if a single report evidences multiple. Sources can also be reused from across Certify.

​

Including monitoring submissions in your GHG statement

Monitoring submissions will be automatically included in the data package for a GHG statement if the validity period of the submission falls within the reporting period of the GHG statement. This means that the submission of monitoring data can be independent from the preparation of GHG entries and GHG statements. The view of your GHG statement in Certify includes a Monitoring tab. This will show all storage sites and their following statuses for the reporting period:

• Valid: monitoring submissions have been uploaded to all monitoring requirements covering the full reporting period
• Partial: monitoring submissions have been uploaded covering part of the reporting period
• Missing: no submissions have been uploaded within the reporting period