|
| 1 | +# BOOST Agency Engagement: CDFA |
| 2 | + |
| 3 | +--- |
| 4 | + |
| 5 | + |
| 6 | +## Outline |
| 7 | + |
| 8 | +- BOOST Overview (15-20 minutes) |
| 9 | +- Review BOOST Entity-Relationship Diagram (20-30 minutes) |
| 10 | + - *DISCUSSION:* Are we missing entities? |
| 11 | + - Specific entities *DISCUSSION*: |
| 12 | + - Do we have the right attributes? |
| 13 | + - What are we missing? |
| 14 | +- Discuss possible phase 2 pilot development |
| 15 | + |
| 16 | +Note: |
| 17 | +- We are hosting targeted meetings with CA agencies to ensure we understand need |
| 18 | +- Version 0.1 will be released in Q2 of 2025. |
| 19 | + |
| 20 | +--- |
| 21 | + |
| 22 | +<img src="img/boost_logo.png" alt="logo" style="height: 400px;"> |
| 23 | + |
| 24 | +-- |
| 25 | + |
| 26 | +## What is BOOST? |
| 27 | + |
| 28 | +- W3C Community Group |
| 29 | +- A "Data Standard" for biomass |
| 30 | +- v0.1 funded by California Department of Conservation |
| 31 | + |
| 32 | +-- |
| 33 | + |
| 34 | +## What BOOST Is Not |
| 35 | + |
| 36 | +- **Not Software**: BOOST does not prescribe specific applications, databases, or user interfaces. |
| 37 | +- **Not a Database**: BOOST does not create centralized storage or control where data resides. |
| 38 | +- **Not Dashboards or Analytics**: BOOST does not define how data should be visualized or analyzed. |
| 39 | +- **Not a Certification Scheme**: BOOST does not establish sustainability criteria or certification requirements. |
| 40 | + |
| 41 | +Note: |
| 42 | +- **Not Software** Organizations remain free to choose their preferred software platforms while adhering to BOOST data exchange requirements. |
| 43 | +- **Not Database** Each organization maintains control over their data while following standard formats for sharing. |
| 44 | +- **Not Dashboards or Analytics**: It provides the foundation that enables various analytical tools to work with standardized data. |
| 45 | +- **Not a Certification Scheme**: It provides the structure for documenting compliance with existing schemes. |
| 46 | + |
| 47 | +-- |
| 48 | + |
| 49 | +## What is the objective? |
| 50 | + |
| 51 | +*To develop and maintain a robust interoperable data standard for solid biomass comprised of schemas, protocols, and documenation for tracking biomass materials from source to end-use* |
| 52 | + |
| 53 | +-- |
| 54 | + |
| 55 | +## WHAT are the goals |
| 56 | + |
| 57 | +*To improve transparency, verification and trust in biomass supply chains* |
| 58 | + |
| 59 | +*Reduce operational costs and increase access to markets for biomass producers and consumers* |
| 60 | + |
| 61 | +-- |
| 62 | + |
| 63 | +## Who is involved? |
| 64 | + |
| 65 | +- Anyone! |
| 66 | +- stakeholders: |
| 67 | + - NGOs, independent certification bodies |
| 68 | + - fed/state agencies, |
| 69 | + - small and large businesses |
| 70 | + - independent technical experts |
| 71 | + - software developers |
| 72 | + |
| 73 | +--- |
| 74 | +## Data Standards ?? |
| 75 | + |
| 76 | +<img src="img/dm-metadata-standards.jpg" alt="logo" style="height: 200px;"> |
| 77 | + |
| 78 | +-- |
| 79 | +## What are Data Standards? |
| 80 | + |
| 81 | +*Data standards are agreed-upon approaches that allow for consistent measurement, qualification, or exchange of information* |
| 82 | + |
| 83 | +-- |
| 84 | + |
| 85 | +## Why develop a Data Standard |
| 86 | + |
| 87 | +Provides a structured framework and a common language for: |
| 88 | + |
| 89 | +- organizing, |
| 90 | +- documenting, |
| 91 | +- formatting **data** |
| 92 | + |
| 93 | +Facilitating **aggregation**, **sharing**, and **reuse** across different systems and organizations |
| 94 | + |
| 95 | +-- |
| 96 | + |
| 97 | +## What is Chain of Custody (CoC)? |
| 98 | + |
| 99 | +Documentation and recording of: |
| 100 | +- movement, |
| 101 | +- handling, |
| 102 | +- transformation |
| 103 | + |
| 104 | +of material through a supply chain |
| 105 | + |
| 106 | + |
| 107 | +-- |
| 108 | + |
| 109 | +## How do Data Standards Support CoC? |
| 110 | + |
| 111 | +For CoC software, data standards: |
| 112 | + - provide a data framework (entities, attributes, and relationships) |
| 113 | + - provide logic for tracking across complex processes and organizational boundaries |
| 114 | + - enable interoperability between systems |
| 115 | + - provide validation rules |
| 116 | + |
| 117 | +--- |
| 118 | + |
| 119 | +## OPEN Standards |
| 120 | + |
| 121 | +<img src="img/open-data-institute.jpg" alt="logo" style="height: 400px;"> |
| 122 | +<br> |
| 123 | +<em>Source: The Open Data Institute</em> |
| 124 | + |
| 125 | +-- |
| 126 | + |
| 127 | +## Benefits of Openness |
| 128 | + |
| 129 | +- encourages **interoperability** and digital integration across the supply chain |
| 130 | +- transparency and trust among stakeholders in complex supply chains |
| 131 | +- democratizes chain of custody data |
| 132 | +- software differentiates on performance not on customer coersion |
| 133 | + |
| 134 | +Note: |
| 135 | ++ proprietary data formats |
| 136 | ++ complex integration |
| 137 | ++ data migration obstacles |
| 138 | ++ lack of portability |
| 139 | + |
| 140 | +-- |
| 141 | + |
| 142 | +## Open Process in Practice |
| 143 | + |
| 144 | +- W3C Community Groups are open to all |
| 145 | +- Technical work in the BOOST group is conducted in public, utilizing: |
| 146 | + - Public mail lists |
| 147 | + - GitHub repositories |
| 148 | + - Google Docs when necessary |
| 149 | +- Ensures contributions and decisions are transparently tracked |
| 150 | +- Participation does not require W3C CLA but **we highly encourage it!** |
| 151 | + |
| 152 | + |
| 153 | +Note: |
| 154 | ++ joining the BOOST community group will ensure you are following the development |
| 155 | ++ without a membership fee requirement |
| 156 | ++ in the spirit of open collaboration |
| 157 | + |
| 158 | +--- |
| 159 | + |
| 160 | +## Core Components of the CoC Data Standard |
| 161 | + |
| 162 | +*DRAFT* [Entity Relationship Diagram](https://carbondirect.github.io/BOOST/erd-navigator/) |
| 163 | + |
| 164 | +**Framing Questions** |
| 165 | + |
| 166 | ++ *Did we get the right set of entities?* |
| 167 | ++ *Did we get the right attributes for entities you care about?* |
| 168 | ++ *Are the relationships between entities appropriate?* |
0 commit comments