Biomass Open Origin Standard for Tracking (BOOST) Data Standard

Living Document,

Editors:
(Carbon Direct)
(Carbon Direct)
Version:
v3.2.0-21-g6c03488

Abstract

The Biomass Open Origin Standard for Tracking (BOOST) data standard defines a comprehensive, interoperable framework for tracking biomass materials through complex supply chains. BOOST enables transparent, verifiable, and consistent data exchange to support sustainability verification, regulatory compliance, and supply chain integrity across the biomass economy. The standard implements a TraceableUnit (TRU)-centric model supporting media-interruption-free tracking, multi-species composition management, and comprehensive plant part categorization across 33 interconnected entities organized into 7 thematic areas.

Status of This Document

This specification was published by the Biomass Open Origin Standard for Tracking (BOOST) W3C Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Final Specification Agreement (FSA) other conditions apply. Learn more about W3C Community and Business Groups.

This document is governed by the W3C Community License Agreement (CLA). A human-readable summary is available.

Publication as a Community Group Report does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

How to Give Feedback

This specification is primarily developed on GitHub. The best way to contribute to this specification is to:

  1. File issues and suggestions in the BOOST GitHub repository

  2. Submit pull requests for specific changes

  3. Participate in community discussions via GitHub Discussions

  4. Join the W3C Community Group mailing list for broader discussions

1. Introduction

The Biomass Open Origin Standard for Tracking (BOOST) data standard defines a comprehensive, interoperable framework for tracking biomass materials through complex supply chains. BOOST enables transparent, verifiable, and consistent data exchange to support sustainability verification, regulatory compliance, and supply chain integrity across the biomass economy.

1.1. Community Development Process

BOOST is developed through the BOOST W3C Community Group with collaborative input from industry stakeholders, regulatory agencies, and technical experts. The standard implements a TraceableUnit (TRU)-centric model supporting media-interruption-free tracking, multi-species composition management, and comprehensive plant part categorization across 33 interconnected entities.

Working Group Leadership:

1.2. Current Development Status

Current Version: v3.2.0-21-g6c03488 - Complete BOOST Documentation Build System with integrated HTML and PDF generation

Recent Enhancements:

1.3. Participation and Feedback

How to Contribute:

Meeting Schedule: Regular working group meetings with notes and action items published via GitHub

1.4. Purpose and Scope

This specification defines the BOOST (Biomass Open Origin Standard for Tracking) data standard for biomass supply chain tracking and verification. The standard provides:

1.5. Background and Motivation

The development of comprehensive biomass traceability systems addresses critical needs for sustainability verification, regulatory compliance, and supply chain transparency in the growing biomass economy. This standard enables interoperability between reporting systems, registries, and certification bodies.

The initial version of this data standard is funded through a grant from the California Department of Conservation, with an initial focus on California as the jurisdictional context while maintaining broad applicability to generalized biomass chain of custody requirements.

1.6. Relationship to Existing Standards

BOOST builds upon and integrates with established standards including:

1.7. Community Group Process

This specification was developed through the W3C Community Group process with balanced stakeholder participation including civil society organizations, government agencies, small and large businesses, and independent technical experts. Recruitment and engagement efforts were made to avoid overrepresentation of any single stakeholder group.

The group operates under the Community and Business Group Process, seeking organizational licensing commitments under the W3C Community Contributor License Agreement (CLA) for all substantive contributions.

2. Use Cases and Requirements

BOOST addresses critical use cases across the biomass supply chain, from forest management and harvesting through processing, transportation, and final delivery. The standard supports both regulatory compliance and voluntary certification scenarios.

2.1. Core Use Case Categories

2.1.1. 1. Complete Harvest-to-Mill Traceability Chain

Objective: Verify end-to-end traceability from standing tree to mill processing

Key Steps:

2.1.2. 2. Multi-Species Mixed Material Processing

Objective: Track individual species within mixed material flows

Key Features:

2.1.3. 3. California LCFS Regulatory Compliance

Objective: Generate quarterly LCFS compliance reports with complete audit trails

Integration Points:

2.1.4. 4. Multi-Certification Scheme Management

Objective: Maintain multiple certification claims across processing operations

Capabilities:

2.1.5. 5. Biometric Media-Interruption-Free Tracking

Objective: Maintain continuous traceability without physical tag dependencies

Technical Features:

2.1.6. 6. Plant Part Value Optimization

Objective: Optimize material routing based on plant part composition

Economic Applications:

2.2. Stakeholder-Specific Use Cases

2.2.1. Forest Management Organizations

2.2.2. Processing Facilities

2.2.3. Transportation Companies

2.2.4. Regulatory Agencies

2.2.5. Certification Bodies

3. Conformance

This section describes the conformance requirements for BOOST implementations. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] and [RFC8174] when, and only when, they appear in all capitals, as shown here.

3.1. Conformance Classes

3.1.1. BOOST Core Conformance

Implementations claiming BOOST Core conformance MUST support:

3.1.2. BOOST Extended Conformance

Implementations claiming BOOST Extended conformance MUST support Core conformance plus:

3.1.3. BOOST Full Conformance

Implementations claiming BOOST Full conformance MUST support Extended conformance plus:

3.2. Implementation Requirements

Conforming implementations MUST:

NOTE: A comprehensive Python reference implementation is available that demonstrates all required BOOST conformance features with dynamic schema adaptation capabilities.

4. BOOST Traceability System

The BOOST Traceability System implements a revolutionary approach to biomass supply chain tracking that eliminates the traditional weak points where traceability is lost during material transfers and processing operations.

4.1. Key Implementation Features

4.1.1. Media-Interruption-Free Traceability

TraceableUnit (TRU) entities maintain continuous identification through biometric signatures and optical pattern recognition, eliminating dependency on physical tags or attachments that can be lost or damaged during handling and processing operations.

4.1.2. Three Critical Tracking Points

The system establishes standardized measurement and verification infrastructure at:

4.1.3. Multi-Species Support

Species-specific tracking capabilities enable:

4.1.4. Complete Processing Chain Documentation

MaterialProcessing entities provide comprehensive audit trails by:

4.2. TraceableUnit (TRU) Central Concept

The TraceableUnit entity serves as the central hub for all biomass tracking operations. Every TRU MUST have:

4.3. Media-Interruption-Free Tracking

BOOST implementations MUST support continuous traceability through:

4.4. Three Critical Tracking Points

Implementations MUST support measurement and verification at:

4.5. Processing Chain Methodology

All material transformations MUST be documented through:

5. Data Model Architecture

The BOOST data model provides a comprehensive framework for representing all aspects of biomass supply chain operations. The model consists of 33 interconnected entities that work together to provide complete traceability from forest to final product.

5.1. Key Features

5.1.1. Comprehensive Entity System

5.1.2. Enhanced Geographic Integration

5.2. Interactive Entity Relationship Diagram

The BOOST data model comprises 33 interconnected entities organized into 7 thematic areas. For comprehensive exploration of entity relationships and schema definitions, use our interactive ERD Navigator.

5.2.1. ERD Navigator Overview

The **Interactive ERD Navigator** provides:

Entity Areas:

  • Core Traceability (5 entities) - TraceableUnit, MaterialProcessing, ProcessingHistory, LocationHistory, BiometricIdentifier

  • Organizational Foundation (6 entities) - Organization, Certificate, CertificationBody, CertificationScheme, Audit, Operator

  • Material & Supply Chain (7 entities) - Material, SpeciesComponent, Supplier, Customer, SupplyBase, SupplyBaseReport, Equipment

  • Transaction Management (3 entities) - Transaction, TransactionBatch, SalesDeliveryDocument

  • Measurement & Verification (4 entities) - MeasurementRecord, Claim, VerificationStatement, MoistureContent

  • Geographic & Tracking (2 entities) - GeographicData, TrackingPoint

  • Compliance & Reporting (6 entities) - LcfsPathway, LcfsReporting, ProductGroup, EnergyCarbonData, DataReconciliation, MassBalanceAccount

5.2.2. Quick Access

5.2.3. Navigation Between ERD and Specification

The ERD Navigator is fully integrated with this specification:

This bidirectional navigation enables seamless exploration between the visual entity relationships and detailed technical specifications.

5.3. Hub-and-Spoke Design

The data model implements a hub-and-spoke architecture with TraceableUnit as the central hub. All other entities MUST maintain direct or indirect relationships to TRUs to ensure complete traceability.

5.4. Foreign Key Conventions

All foreign key relationships MUST follow the EntityNameId pattern:

6. Plant Part Categorization System

The plant part categorization system enables detailed tracking of biomass components through processing operations, supporting value optimization and circular economy principles.

6.1. System Overview

6.1.1. 17 Standardized Plant Parts Taxonomy

The BOOST standard defines a comprehensive taxonomy of plant components:

Primary Structural Components:

Secondary Structural Components:

Photosynthetic and Reproductive Components:

Processed Components:

6.1.2. Processing Transformations

The system tracks detailed transformations during processing operations:

6.1.3. Value Optimization Applications

Plant part categorization enables sophisticated material routing:

6.1.4. Circular Economy Integration

The system supports comprehensive waste stream management:

6.2. Standardized Plant Parts Taxonomy

Implementations MUST support the following 17 standardized plant parts:

7. Core Data Entities

The BOOST data model defines 33 core entities organized into 7 thematic areas. Each entity serves a specific purpose in the biomass supply chain tracking ecosystem and maintains relationships with other entities to ensure complete traceability.

7.1. Core Traceability Entities

Implementations claiming BOOST Core conformance MUST support these entities:

7.1.1. TraceableUnit

The central entity in BOOST’s hub-and-spoke architecture. Every TRU connects to Organization, Material, and GeographicData entities.

**🗂️ View TraceableUnit in ERD Navigator**

8. TraceableUnit

8.1. TraceableUnit

8.1.1. Overview

The TraceableUnit object represents the fundamental unit of traceability in the BOOST media-interruption-free timber supply chain tracking system. A TRU can be an individual log, pile, volume aggregation, or processed batch that maintains continuous data linkage throughout its lifecycle. This entity replaces MaterialBatch as the primary traceable unit and supports biometric identification, species composition tracking, and complete audit trails.

8.1.2. Fields

Field Type Required Description Examples
traceableUnitId string Yes Unique identifier for the TRU (primary key) TRU-LOG-001, TRU-PILE-CA-Klamath-042
unitType string Yes Type of traceable unit (enum) individual_log, pile, volume_aggregation, processed_batch
uniqueIdentifier string Yes Biometric signature, RFID tag, or QR code BIO-OAK-12345, RFID-TAG-67890, QR-CODE-ABC123
totalVolumeM3 number Yes Total volume of the traceable unit in cubic meters 12.5, 250.75, 1000.0
currentGeographicDataId string (FK) No Foreign key to current location (GeographicData entity) GEO-MILL-ENTRANCE-001, GEO-FOREST-ROAD-23
harvestGeographicDataId string (FK) Yes Foreign key to harvest location (GeographicData entity) GEO-HARVEST-SITE-CA-001
createdTimestamp string (date-time) Yes When the TRU was created 2025-07-21T08:30:00Z
harvesterId string (FK) Yes Foreign key to harvesting organization ORG-HARVESTER-001
operatorId string (FK) No Foreign key to operator OP-JOHN-DOE-001
materialTypeId string (FK) Yes Foreign key to Material entity (reference table) MAT-TYPE-PINE, MAT-TYPE-FIR
assortmentType string No Type of wood assortment (enum) sawlog, pulpwood, biomass, chips
qualityGrade string No Quality grade classification (enum) A, B, C, structural, fuel
isMultiSpecies boolean Yes True if contains multiple species true, false
attachedInformation array<string> No All data linked to this TRU ["moisture_content: 12%", "bark_removed: true"]
processingHistory array<string> No Complete processing chain references (Phase 2) ["PROC-FELL-001", "PROC-LIMB-002"]
parentTraceableUnitId string (FK) No For split/merge operations (Phase 2) TRU-PARENT-001
childTraceableUnitIds array<string> No For split/merge operations (Phase 2) ["TRU-CHILD-001", "TRU-CHILD-002"]
currentStatus string No Current status of the TRU (Phase 2, enum) active, processed, delivered, consumed
sustainabilityCertification string No FSC, PEFC, etc. claims (Phase 2) FSC-Mix Credit, SBP-compliant
mediaBreakFlags array<string> No Points where data continuity was lost (Phase 2) ["RFID_tag_lost_at_forest_road", "GPS_signal_interrupted"]
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/traceable-unit/TRU-001
lastUpdated string (date-time) No Timestamp of the most recent data update 2025-07-21T15:45:00Z

8.1.3. Key Features

  1. Media-Interruption-Free Traceability Continuous data linkage from harvest to mill entrance Multiple identification methods (biometric, RFID, QR codes) Media break detection and flagging

  2. Species Composition Support Multi-species flag for complex piles and batches Integration with SpeciesComponent entity for detailed tracking Species-specific sustainability claims

  3. Complete Audit Trails Processing history with complete transformation records Location history through LocationHistory entity Measurement reconciliation through DataReconciliation entity

  4. Split/Merge Operations Parent/child relationships for TRU genealogy Volume conservation validation Claim inheritance tracking

8.1.4. Example Use Cases

  1. Individual Log Tracking Type: individual_log Unique biometric signature from optical scanner Single species with specific quality grade Complete harvest-to-mill tracking

  2. Multi-Species Pile Type: pile RFID tag identification Multiple species tracked via SpeciesComponent entities Volume aggregation with species percentages

  3. Processed Batch Type: processed_batch Parent TRU references for split operations Processing history with transformation details Sustainability claim inheritance

8.1.5. Relationships

8.1.6. Organization

Defines harvesters, processors, and supply chain participants. Referenced by TraceableUnit and connects to Certificate entities for certification management.

**🗂️ View Organization in ERD Navigator**

9. Organization

9.1. Organization

9.1.1. Overview

The Organization entity manages companies and institutions with geographic data references and certification management capabilities as part of the BOOST traceability system enhancements. This entity serves as the foundational record for all organizational entities participating in the timber supply chain, including harvesters, processors, certifiers, and other stakeholders.

9.1.2. Fields

Field Type Required Description Examples
organizationId string Yes Unique identifier for the organization (primary key) ORG-001, ORG-FORESTCO-PACIFIC
organizationName string Yes Legal name of the organization Pacific Forest Products LLC, Klamath Sustainable Forestry
organizationType string Yes Type of organization (enum) harvester, processor, certifier, transporter, supplier, manufacturer, producer, importer, blender, distributor
primaryGeographicDataId string (FK) No Foreign key to primary operational location GEO-MILL-PACIFIC-001, GEO-OFFICE-KLAMATH
operationalAreas array<string> No List of geographic areas where organization operates ["GEO-FOREST-AREA-01", "GEO-MILL-SITE-02"]
contactEmail string (email) No Primary contact email address operations@pacificforest.com
contactPhone string No Primary contact phone number +1-555-123-4567, +1-800-FOREST-1
certifications array<string> No List of certification IDs held by organization ["CERT-FSC-001", "CERT-SFI-002"]
establishedDate string (date) No Date organization was established 1995-03-15, 2010-07-01
taxId string No Tax identification number 12-3456789, 98-7654321
website string (uri) No Organization website URL https://www.pacificforest.com
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/organization/ORG-001
lastUpdated string (date-time) No Timestamp of the most recent data update 2025-07-21T15:45:00Z

9.1.3. Organization Types

  1. harvester Forest harvesting and timber extraction operations Responsible for initial TRU creation and identification Manages harvest site operations and equipment Provides raw material to processing facilities Examples: Logging companies, forest management companies

  2. processor Manufacturing and processing operations Transforms raw timber into finished products Operates sawmills, paper mills, and other processing facilities Manages quality control and product specifications Examples: Sawmills, paper manufacturers, engineered wood producers

  3. certifier Third-party certification and validation services Conducts audits and issues certifications Validates sustainability claims and compliance Provides independent verification services Examples: FSC certifiers, SFI certification bodies

  4. transporter Transportation and logistics services Manages supply chain movement and tracking Maintains chain of custody during transport Provides tracking point management Examples: Trucking companies, rail transport, shipping companies

  5. supplier Supply chain intermediaries and distributors Manages inventory and product distribution Coordinates between producers and end users Provides market access and logistics coordination Examples: Timber brokers, wood product distributors

  6. manufacturer End-product manufacturing and assembly Creates finished goods from processed timber Manages final product quality and specifications Provides consumer-ready products Examples: Furniture manufacturers, construction companies

  7. producer Primary production and manufacturing of renewable fuels or products Operates refineries and production facilities for biofuels Manages feedstock conversion and processing operations Subject to LCFS regulatory requirements and reporting Examples: Renewable diesel producers, biodiesel refineries, ethanol plants

  8. importer Import operations for renewable fuels and products Manages international supply chain and customs operations Handles regulatory compliance for imported fuels Subject to LCFS import reporting requirements Examples: Fuel importers, biofuel trading companies

  9. blender Fuel blending and distribution operations Mixes renewable fuels with conventional petroleum products Manages fuel quality and specification compliance Subject to LCFS blending and distribution requirements Examples: Fuel blending terminals, distribution facilities

  10. distributor Distribution and retail operations for renewable fuels Manages fuel delivery and retail sales operations Handles end-consumer fuel distribution Subject to LCFS distribution reporting requirements Examples: Fuel distributors, retail gas stations, fleet operators

9.1.4. Key Features

  1. Geographic Integration Primary location tracking with GeographicData references Multiple operational area management Location-based service area definition Spatial analysis of organizational footprint Regional operational compliance tracking

  2. Certification Management Multiple certification tracking and management Certification expiry and renewal tracking Audit trail for certification activities Integration with claim validation processes Certification scope and applicability management

  3. Multi-Location Operations Support for organizations with multiple facilities Operational area geographic boundary definition Location-specific capability and capacity tracking Regional compliance and regulation management Site-specific environmental impact assessment

  4. Supply Chain Integration Role-based organizational classification Supply chain relationship management Service capability and capacity tracking Partner organization integration Stakeholder communication and coordination

9.1.5. Geographic Data Integration

  1. Primary Location Main operational headquarters or facility Administrative and management location Primary contact and communication center Financial and legal registration address Strategic planning and coordination hub

  2. Operational Areas Forest management areas for harvesters Processing facility locations for manufacturers Service territories for transporters Market areas for suppliers Geographic service boundaries

  3. Facility-Specific Data Processing capacity and capabilities by location Equipment and infrastructure by facility Environmental permits and compliance by site Workforce and operational capacity by location Location-specific certifications and approvals

9.1.6. Certification Integration

  1. Certificate Management Current certification status tracking Certification scope and applicability Expiry date monitoring and renewal management Multi-standard certification support Certification body relationship management

  2. Compliance Tracking Regulatory compliance monitoring Environmental permit management Safety and quality standard compliance Industry-specific requirement tracking Audit and inspection history

  3. Claim Validation Authority to validate sustainability claims Certification-based claim verification Third-party validation services Independent assessment capabilities Conflict of interest management

9.1.7. Validation Rules

  1. Identification Requirements organizationId must be unique across system organizationName must be non-empty organizationType must match business operations Contact information must be valid and current

  2. Geographic Consistency primaryGeographicDataId must reference valid GeographicData operationalAreas must reference valid geographic boundaries Geographic areas must be logically consistent with organization type Location data must align with legal and regulatory jurisdictions

  3. Certification Logic certifications must reference valid certification records Certification types must be appropriate for organization type Certification scope must align with operational areas Certification expiry dates must be monitored and maintained

9.1.8. Example Use Cases

  1. Integrated Forest Products Company organizationType: harvester, processor Multiple operational areas including forest lands and mill sites FSC and SFI certifications for both forest management and processing Complex supply chain with internal transfer tracking Multi-facility operations requiring coordination

  2. Independent Harvesting Contractor organizationType: harvester Single primary location with mobile operations Multiple operational areas across regional forest lands SFI contractor certification Service provider to multiple forest landowners

  3. Third-Party Certification Body organizationType: certifier Office locations with regional service areas Authority to issue and validate multiple certification types Independent status and conflict of interest management Audit and inspection service capabilities

9.1.9. Relationships

9.1.10. Material

Material type classifications referenced by TraceableUnit. For multi-species materials, connect to SpeciesComponent entities.

**🗂️ View Material in ERD Navigator**

10. Material

10.1. Material

10.1.1. Overview

The Material entity serves as a reference table for material types with geographic data references and processing specifications to support species-specific sustainability claims in the BOOST traceability system. This entity has been refactored from a traceable entity to a reference table, with TraceableUnit now serving as the primary traceable entity for individual wood pieces.

10.1.2. Fields

Field Type Required Description Examples
materialTypeId string Yes Unique identifier for the material type (primary key) MAT-TYPE-001, MAT-DOUGLAS-FIR-SAWTIMBER
materialName string Yes Descriptive name of the material type Douglas Fir Sawtimber, Mixed Hardwood Chips
materialCategory string Yes Category classification (enum) softwood, hardwood, mixed
defaultAssortmentTypes string No Default assortment classifications for this material sawtimber, pulpwood, veneer, lumber
standardQualityGrades string No Standard quality grades available for this material Grade A, Grade B, Utility, Select, Common
carbonStorageRate string No Carbon storage characteristics 0.47 tCO2/m3, 0.52 tCO2/m3
density string No Material density specifications 450 kg/m3, 380-420 kg/m3
applicableProcessingTypes array<string> No Processing types applicable to this material ["felling", "delimbing", "crosscutting"]
typicalSpecies array<string> No Species typically included in this material type ["douglas_fir", "ponderosa_pine"]
standardMoistureContent string No Standard moisture content ranges 8-12%, 15-20%
energyContent string No Energy content specifications for biomass applications 18.5 MJ/kg, 16.2-19.8 MJ/kg
applicablePlantParts array<string> No Plant parts included in this material type ["trunk", "heartwood", "sapwood"]
excludedPlantParts array<string> No Plant parts excluded from this material type ["bark", "branches", "needles"]
plantPartProcessingSpecs object No Processing specifications by plant part {"trunk": {"processingMethods": ["sawing"]}}
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/material/MAT-TYPE-001
lastUpdated string (date-time) No Timestamp of the most recent data update 2025-07-21T15:45:00Z

10.1.3. Material Categories

  1. softwood Coniferous species material types Typically used for construction lumber Examples: Douglas Fir, Ponderosa Pine, Western Hemlock Higher structural strength characteristics Common processing: sawtimber, dimension lumber

  2. hardwood Deciduous species material types Varied applications from furniture to pulp Examples: Oak, Maple, Cherry, Poplar Higher density and varied grain patterns Common processing: furniture stock, flooring, pulpwood

  3. mixed Multi-species material combinations Biomass and chip applications Variable composition by harvest location Averaged characteristics across species Common processing: chipping, pelletizing

10.1.4. Plant Part Categories

10.1.4.1. Woody Components
10.1.4.2. Foliage Components
10.1.4.3. Reproductive Components
10.1.4.4. Agricultural Components

10.1.5. Key Features

  1. Reference Table Design No longer a traceable entity Provides specifications for TRU material typing Standardized material classifications Processing guidance and specifications Carbon accounting reference data

  2. Species Integration Links to typical species compositions Species-specific processing guidelines Biodiversity impact assessments Sustainability claim foundations Multi-species material support

  3. Processing Specifications Applicable processing type definitions Quality grade standardizations Assortment classification guidelines Equipment compatibility specifications Processing efficiency expectations

  4. Carbon and Energy Data Carbon storage rate specifications Energy content for biomass applications Density and moisture content standards Sustainability metric foundations Environmental impact references

10.1.6. Processing Type Applications

  1. felling Tree cutting and initial processing Species identification during harvest Initial volume and quality assessment Primary processing operation

  2. delimbing Branch removal preparation Clean stem material preparation Volume refinement specifications Quality improvement processing

  3. crosscutting Length optimization specifications Market requirement alignment Quality grade maximization Assortment classification support

  4. chipping Biomass preparation specifications Size and quality requirements Mixed species chip production Energy content optimization

  5. debarking Clean wood preparation Processing facility requirements Volume loss expectations Quality improvement specifications

10.1.7. Quality Grade Standards

  1. Structural Grades Load-bearing capacity classifications Strength and stiffness requirements Defect limitations and allowances Construction application suitability

  2. Appearance Grades Visual quality classifications Grain pattern and color consistency Surface quality requirements Furniture and millwork applications

  3. Industrial Grades Functional performance requirements Processing suitability specifications Chemical composition consistency Industrial application compatibility

10.1.8. Validation Rules

  1. Classification Consistency materialCategory must align with typicalSpecies applicableProcessingTypes must be appropriate for category Quality grades must match industry standards Species list must be ecologically consistent

  2. Processing Logic Processing types must be technically feasible Quality grades must be achievable through specified processing Assortment types must align with material characteristics Equipment requirements must be reasonable

  3. Carbon and Energy Data Carbon storage rates must be scientifically valid Energy content must align with species characteristics Density specifications must be within reasonable ranges Moisture content ranges must be practical

10.1.9. Example Use Cases

  1. Douglas Fir Sawtimber Specifications Material type for high-grade construction lumber Processing through felling, delimbing, crosscutting Quality grades from Select to Utility Carbon storage rate: 0.47 tCO2/m3 Typical density: 450 kg/m3

  2. Mixed Hardwood Chip Material Multi-species biomass material type Processing through chipping and pelletizing Industrial grade specifications Variable species composition Energy content: 17-19 MJ/kg

  3. Softwood Dimension Lumber Standard construction material type Structural grade classifications Standardized processing specifications Moisture content: 19% or less Multiple species applicability

10.1.10. Relationships

10.1.11. GeographicData

Spatial data in GeoJSON format for location tracking. Referenced by TraceableUnit and LocationHistory for comprehensive location management.

**🗂️ View GeographicData in ERD Navigator**

11. GeographicData

11.1. GeographicData

11.1.1. Overview

The GeographicData entity provides comprehensive spatial data support for the BOOST framework using GeoJSON standards. This entity enables precise location tracking, geographic boundaries definition, and spatial relationship management throughout the biomass supply chain. It supports the BOOST traceability system’s requirement for complete location-based traceability and addresses California agency engagement commitments for spatial data integration.

11.1.2. Fields

Field Type Required Description Examples
geographicDataId string Yes Unique identifier for the geographic data (primary key) GEO-HARVEST-001, GEO-MILL-PACIFIC-01
geoJsonData object Yes Valid GeoJSON object (Point, Polygon, LineString, etc.) See GeoJSON examples below
dataType string Yes Type of geographic data (enum) harvest_site, processing_location, administrative_boundary, supply_base_area
description string Yes Human-readable description of the geographic area Klamath Ridge Harvest Site Unit 4, Pacific Lumber Mill Entrance
lastUpdated string (date-time) No Timestamp of the most recent data update 2025-07-21T15:00:00Z
coordinateSystem string No Coordinate reference system (default: WGS84) WGS84, UTM Zone 10N, NAD83
accuracy number No GPS accuracy in meters 3.5, 10.0, 1.2
elevationM number No Elevation in meters above sea level 1250.5, 450.0, 2100.8
administrativeRegion string No Administrative region or jurisdiction California, Humboldt County, Klamath National Forest
accessRestrictions string No Any access restrictions or special conditions Seasonal road closure Nov-Apr, Permit required for access
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/geographic-data/GEO-001

11.1.3. GeoJSON Data Types

11.1.3.1. Point (Single Location)
{
  "type": "Point",
  "coordinates": [-124.2345, 41.7891]
}
11.1.3.2. Polygon (Area/Boundary)
{
  "type": "Polygon",
  "coordinates": [[
    [-124.2345, 41.7891],
    [-124.2300, 41.7891],
    [-124.2300, 41.7850],
    [-124.2345, 41.7850],
    [-124.2345, 41.7891]
  ]]
}
11.1.3.3. LineString (Road/Path)
{
  "type": "LineString",
  "coordinates": [
    [-124.2345, 41.7891],
    [-124.2320, 41.7885],
    [-124.2300, 41.7870]
  ]
}

11.1.4. Data Type Classifications

  1. harvest_site Specific locations where timber harvesting occurs Typically Point or small Polygon geometries Links to TraceableUnit harvest locations

  2. processing_location Locations where MaterialProcessing occurs Mills, sorting yards, chipping facilities Point geometries with facility boundaries

  3. administrative_boundary Regulatory or administrative boundaries County lines, forest service boundaries, permit areas Polygon geometries

  4. supply_base_area Overall supply base geographic boundaries Large Polygon geometries encompassing multiple harvest sites Links to SupplyBase entities

  5. skid_road / forest_road Transportation infrastructure LineString geometries showing road networks Critical for tracking point infrastructure

  6. mill_entrance Specific points where TRUs enter processing facilities Point geometries at facility gates Final tracking points in BOOST traceability system

11.1.5. Key Features

  1. GeoJSON Compliance Full GeoJSON specification support Multiple geometry types (Point, Polygon, LineString, etc.) Properties object for additional spatial metadata

  2. Coordinate System Support Default WGS84 for global interoperability Support for regional coordinate systems (UTM, NAD83, etc.) Accuracy metadata for GPS precision tracking

  3. Hierarchical Relationships Support for nested geographic relationships Harvest sites within supply base areas Administrative boundaries containing operational areas

  4. Agency Integration Designed for California agency mapping requirements Support for regulatory boundary definitions Integration with GIS systems and spatial databases

11.1.6. Example Use Cases

  1. Harvest Site Tracking Precise GPS coordinates of harvest operations Links to TraceableUnit harvest locations Support for environmental compliance reporting

  2. Supply Base Boundaries Large polygon areas defining operational scope Integration with forest management plans Regulatory compliance boundary definitions

  3. Transportation Networks Skid road and forest road mapping Route optimization and planning Infrastructure maintenance tracking

  4. Processing Facility Locations Mill entrance points for final tracking Processing location definitions Facility boundary and access point mapping

11.1.7. Relationships

11.2. Extended Traceability Entities

Implementations claiming BOOST Extended conformance MUST support Core entities plus these additional entities:

11.2.1. MaterialProcessing

Documents material transformation operations linking input and output TraceableUnit entities. Often references Equipment and Operator entities for operational details.

**🗂️ View MaterialProcessing in ERD Navigator**

12. MaterialProcessing

12.1. MaterialProcessing

12.1.1. Overview

The MaterialProcessing entity tracks all technical manipulations with input/output TRU references and species composition changes to support complete audit trails in the BOOST traceability system. This entity captures every processing operation that transforms, moves, or modifies TRUs throughout the supply chain, maintaining complete traceability and volume conservation validation.

12.1.2. Fields

Field Type Required Description Examples
processingId string Yes Unique identifier for the processing operation (primary key) PROC-001, PROC-FELL-KLA-042
inputTraceableUnitId string (FK) Yes Foreign key to input TRU being processed TRU-TREE-001, TRU-LOG-CA-042
outputTraceableUnitId string (FK) Yes Foreign key to output TRU created (may be same as input) TRU-LOG-001, TRU-PILE-CA-042
processType string Yes Type of processing operation (enum) felling, delimbing, crosscutting, chipping, debarking, assortment
processTimestamp string (date-time) Yes When the processing operation occurred 2025-07-15T07:15:00Z
processingGeographicDataId string (FK) No Foreign key to location where processing occurred GEO-HARVEST-SITE-001, GEO-MILL-001
operatorId string (FK) No Foreign key to operator who performed processing OP-HARVESTER-001, OP-MILL-TECH-02
inputComposition string No Species composition before processing Douglas Fir: 100%, Mixed: DF 60%, PP 40%
outputComposition string No Species composition after processing Douglas Fir: 100%, Separated by species
inputVolume number Yes Input volume before processing (cubic meters) 25.5, 85.25, 150.0
outputVolume number Yes Output volume after processing (cubic meters) 24.2, 80.75, 140.5
volumeLoss number No Volume lost during processing (cubic meters) 1.3, 4.5, 9.5
qualityMetrics string No Quality measurements and assessments Grade A: 80%, Grade B: 20%, Moisture: 12%
equipmentUsed string No Equipment used for processing harvester_head, chainsaw, chipper, debarker
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/material-processing/PROC-001
lastUpdated string (date-time) No Timestamp of the most recent data update 2025-07-21T15:45:00Z

12.1.3. Processing Types

  1. felling Tree cutting and initial processing Standing tree to log conversion Initial volume measurement Species identification and verification Primary processing operation

  2. delimbing Branch removal from felled trees Clean stem preparation Volume refinement and measurement Quality assessment after delimbing Preparation for transport or further processing

  3. crosscutting Log cutting to specified lengths Length optimization for market requirements Multiple output logs from single input Volume distribution and measurement Quality grade assignment

  4. chipping Conversion to wood chips Volume reduction and format change Species mixing or separation Moisture content adjustment Final product preparation

  5. debarking Bark removal from logs Clean wood preparation for processing Volume loss measurement Bark disposal or utilization tracking Quality improvement operation

  6. assortment Sorting and classification by quality/species Grade assignment and segregation Market specification preparation Quality-based value optimization Inventory organization

12.1.4. Key Features

  1. Complete Processing Chain Tracking Input/output TRU relationship mapping Chronological processing sequence Volume conservation validation Quality transformation tracking Operator accountability

  2. Species Composition Management Before/after species composition tracking Multi-species processing support Species separation and mixing operations Composition validation and verification Biodiversity impact assessment

  3. Volume Conservation Validation Input volume measurement Output volume calculation Volume loss quantification and justification Processing efficiency metrics Mass balance verification

  4. Quality Transformation Tracking Quality metrics before and after processing Grade assignment and modification Defect identification and impact Processing quality assurance Value optimization tracking

12.1.5. Processing Efficiency Metrics

  1. Volume Recovery Rates Standard recovery rates by processing type Equipment-specific efficiency tracking Operator performance metrics Quality impact on recovery rates

  2. Quality Transformation Grade improvement through processing Defect removal effectiveness Value-added processing metrics Market specification achievement

  3. Species-Specific Processing Species-appropriate processing methods Species-specific recovery rates Quality outcomes by species Processing optimization by species

12.1.6. Validation Rules

  1. TRU Relationship Validation inputTraceableUnitId must reference existing TRU outputTraceableUnitId must be created or reference existing TRU processTimestamp must be ≥ input TRU creation timestamp Output TRU creation must be ≥ processTimestamp

  2. Volume Conservation outputVolume + volumeLoss should approximately equal inputVolume Volume loss must be reasonable for processing type Volume calculations must account for species composition changes

  3. Processing Logic Processing type must be appropriate for input TRU type Equipment must be suitable for processing type Operator must be qualified for processing operation Location must support specified processing type

12.1.7. Example Use Cases

  1. Tree Felling Operation Input: Standing tree (estimated volume) Process: Felling with chainsaw Output: Felled tree/log with measured volume Volume loss: Sawdust and cutting waste Quality assessment: Initial grade assignment

  2. Log Crosscutting Input: Long log (25.5 m³) Process: Crosscutting to market lengths Output: Multiple shorter logs (24.2 m³ total) Volume loss: Saw kerf and end trim (1.3 m³) Quality: Length optimization for grade recovery

  3. Multi-Species Pile Processing Input: Mixed species pile Process: Species sorting and assortment Output: Separate species piles Composition change: Mixed to segregated Quality improvement through sorting

12.1.8. Relationships

12.1.9. ProcessingHistory

Chronological tracking of all processing operations affecting TraceableUnit entities throughout their lifecycle. Complements MaterialProcessing with TRU-centric audit trails and genealogy tracking.

**🗂️ View ProcessingHistory in ERD Navigator**

13. ProcessingHistory

13.1. ProcessingHistory

13.1.1. Overview

The ProcessingHistory entity provides chronological tracking of all processing operations that affect a TracableUnit throughout its lifecycle. This entity creates a complete audit trail of transformations, movements, and quality changes, enabling comprehensive genealogy tracking and supporting media-interruption-free traceability requirements of the BOOST traceability system.

ProcessingHistory serves as the TRU-centric complement to the operation-centric MaterialProcessing entity, providing a unified timeline view of how materials evolve through the supply chain.

13.1.2. Purpose

13.1.3. Fields

Field Type Required Description Examples
processingHistoryId string Yes Unique identifier for the processing history record (primary key) PROC-HIST-TRU-LOG-CA-042-001, PROC-HIST-SPLIT-KLA-015
traceableUnitId string (FK) Yes Foreign key to TRU this history record belongs to TRU-LOG-CA-042, TRU-PILE-SORTED-001
materialProcessingId string (FK) Yes Foreign key to MaterialProcessing operation that created this history PROC-FELL-KLA-042, PROC-CROSSCUT-001
timestamp string (date-time) Yes When this processing step occurred 2025-07-15T08:30:00Z
processSequenceNumber integer Yes Sequential order of this processing step for the TRU (starts at 1) 1, 2, 3
processingEventType string Yes Type of processing event (enum) transformation, split, merge, quality_change, loading
inputTRUIds string[] Yes Array of input TRU IDs (multiple for merge operations) ["TRU-TREE-CA-042"], ["TRU-LOG-001", "TRU-LOG-002"]
outputTRUIds string[] Yes Array of output TRU IDs (multiple for split operations) ["TRU-LOG-CA-042"], ["TRU-PILE-A", "TRU-PILE-B"]
processingDuration string (ISO8601) No ISO 8601 duration format for processing time PT45M, PT2H30M, PT1D
qualityChangeDescription string No Description of quality changes during processing Grade assessment: A-grade sawlog, Moisture reduced from 25% to 15%
operatorId string (FK) No Foreign key to operator who performed processing OP-HARVESTER-KLA-001, OP-MILL-TECH-02
equipmentUsed string No Equipment used for this processing step harvester_head_001, crosscut_saw, loader_CAT_320
volumeChangeRatio number No Ratio of output volume to input volume (1.0 = no change) 0.94, 1.0, 0.85
speciesCompositionChange string No How species composition changed during processing (enum) unchanged, separated, mixed
plantPartTransformation string No Summary of plant part changes during processing trunk→trunk (sized), branches→chips
isCurrentProcessingState boolean No True if this represents the current processing state true, false
processingGeographicDataId string (FK) No Foreign key to location where processing occurred GEO-HARVEST-KLAMATH-04, GEO-MILL-001
previousProcessingHistoryId string (FK) No Foreign key to previous processing history record (forms chain) PROC-HIST-TRU-LOG-CA-042-001, null
nextProcessingHistoryIds string[] No Array of next processing history record IDs (for split operations) ["PROC-HIST-TRU-042-002"], ["PROC-HIST-A", "PROC-HIST-B"]
volumeConservationData object No Volume conservation validation data See Volume Conservation section
mediaBreakData object No Media break detection and recovery information See Media Break section
claimInheritanceData object No Sustainability claim inheritance tracking See Claim Inheritance section
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/processing-history/PROC-HIST-001

13.1.4. Processing Event Types

  1. transformation Standard processing operations that change material characteristics Includes felling, delimbing, crosscutting, chipping, debarking Single input TRU → Single output TRU with changed properties Volume, quality, or plant part composition changes

  2. split One input TRU divided into multiple output TRUs Examples: Log crosscutting, pile sorting by grade, load division Single input TRU → Multiple output TRUs Volume conservation across all outputs required

  3. merge Multiple input TRUs combined into single output TRU Examples: Pile consolidation, load combining, batch aggregation Multiple input TRUs → Single output TRU Species and plant part composition tracking required

  4. quality_change Processing that primarily affects quality without volume change Examples: Grading, moisture testing, defect assessment Quality characteristics updated without physical transformation May trigger claim validation requirements

  5. loading Transportation-related processing with material transformation Examples: Pile to truck conversion with volume settling Configuration or accessibility changes during transport preparation Bridges pure movement (LocationHistory) with processing

  6. transport_processing Processing operations that occur during transportation Examples: In-transit sorting, consolidation stops, quality monitoring Combines spatial movement with material transformation Requires both ProcessingHistory and LocationHistory records

  7. measurement Processing events focused on data collection and validation Examples: Volume reconciliation, biometric scanning, quality testing May not change material but updates TRU characteristics Critical for media-break prevention and data validation

13.1.5. Volume Conservation Data

Complex object tracking volume conservation across processing operations:

{
  "totalInputVolume": 25.5,
  "totalOutputVolume": 24.2, 
  "volumeLoss": 1.3,
  "lossReason": "sawdust",
  "conservationValidated": true
}

Volume Loss Reasons:

13.1.6. Media Break Data

Information about media breaks and recovery procedures:

{
  "mediaBreakOccurred": false,
  "breakDuration": null,
  "breakReason": null, 
  "recoveryMethod": null,
  "dataIntegrityValidated": true
}

Media Break Recovery Methods:

13.1.7. Claim Inheritance Data

Tracking sustainability claim inheritance through processing:

{
  "inheritedClaims": ["CLAIM-FSC-MIX-KLA-042"],
  "newClaims": ["CLAIM-GRADE-A-SAWLOG"],
  "claimValidationRequired": true,
  "claimValidationCompleted": true
}

13.1.8. Relationships

13.1.9. Usage Examples

13.1.9.1. Simple Transformation Chain
-- Get complete processing timeline for TRU
SELECT * FROM ProcessingHistory 
WHERE traceableUnitId = 'TRU-LOG-CA-042'
ORDER BY processSequenceNumber;
13.1.9.2. Split Operation Tracking
-- Find all TRUs created from split operation
SELECT outputTRUIds FROM ProcessingHistory
WHERE processingEventType = 'split' 
AND 'TRU-PILE-ORIGINAL' = ANY(inputTRUIds);
13.1.9.3. Volume Conservation Analysis
-- Analyze volume losses by processing type
SELECT 
  mph.processType,
  AVG(ph.volumeChangeRatio) as avg_recovery_rate,
  SUM((ph.volumeConservationData->>'volumeLoss')::numeric) as total_loss
FROM ProcessingHistory ph
JOIN MaterialProcessing mph ON ph.materialProcessingId = mph.processingId
GROUP BY mph.processType;

13.1.10. Transportation Classification Framework

This entity supports the transportation classification framework where:

  1. Pure Transportation → LocationHistory only (spatial movement)

  2. Transformative Transportation → ProcessingHistory + MaterialProcessing (material changes)

  3. Complex Transportation → Both ProcessingHistory and LocationHistory (movement + transformation)

See transportation classification documentation for detailed decision framework.

13.1.11. Business Rules

  1. Sequence Integrity: ProcessSequenceNumber must be sequential and unique per TRU

  2. Volume Conservation: Total input volume should equal total output volume plus documented losses

  3. Claim Inheritance: Claims must be properly inherited based on volume percentages and processing type

  4. Media Break Prevention: Each processing step must maintain traceability chain integrity

  5. Geographic Consistency: Processing location should be consistent with LocationHistory records

  6. Temporal Ordering: Timestamp sequence should align with processSequenceNumber ordering

13.1.12. Integration with BOOST Traceability System

ProcessingHistory directly supports BOOST traceability system requirements:

13.2. Organizational Foundation Entities

*Note: Organization is now part of Core Traceability Entities - see § 8.1.6 Organization*

13.2.1. Certificate

Certification documents for Organization entities. Links to CertificationBody and CertificationScheme for comprehensive certification management.

**🗂️ View Certificate in ERD Navigator**

14. Certificate

14.1. Overview

The Certificate object represents a formal record of certification issued by a certification body (cbId) to an organization under a specific certification scheme. The primary key is certificateNumber.

14.2. Fields

Field Type Required Description Examples
certificateId string No Optional internal identifier SFI-CERT-001
certificateNumber string Yes Official certificate number (primary key) SFI-2025-12345
certificationSchemeId string Yes FK to Certification Scheme SFI-CoC
cbId string Yes FK to Certification Body SFI
organizationId string Yes FK to Organization receiving the certificate ORG-FORESTCO-001
dateOfIssue string (date) Yes Date of issuance 2025-01-01
dateOfExpiry string (date) Yes Expiry date 2030-01-01
status string Yes Current certificate status active, expired, revoked, etc.
scopeOfCertification string Yes Summary of certification coverage Chain of Custody for lumber and pulp
versionNumber string Yes Version of standard applied 2022
conditionalRequirements array No Special conditions or requirements [{"type": "surveillance", "frequency": "annual"}]
suspensionHistory array No History of suspensions [{"date": "2023-06-01", "reason": "non-compliance"}]
auditSchedule object No Scheduled audit information {"nextAudit": "2025-12-01", "type": "surveillance"}
certificateDocument string No Link or reference to certificate document https://sfiprogram.org/certificates/2025-12345.pdf

14.3. Relationships

14.3.1. Parent Entities

14.3.2. Child Entities

14.4. Business Rules

  1. Certificate Number Uniqueness: certificateNumber must be unique across all certificates

  2. Date Validation: dateOfExpiry must be after dateOfIssue

  3. Status Consistency: Status must reflect current validity based on dates and conditions

  4. Scheme Alignment: Certificate scope must align with the capabilities of the certification scheme

  5. Organization Eligibility: Only organizations meeting scheme requirements can receive certificates

14.5. Common Queries

14.6. Integration Points

14.7. Additional Essential Entities

*Note: Material is now part of Core Traceability Entities - see § 9.1.10 Material*

14.7.1. SpeciesComponent

Multi-species composition data for Material entities. Essential for mixed-species TraceableUnit tracking with percentage validation.

**🗂️ View SpeciesComponent in ERD Navigator**

15. SpeciesComponent

15.1. SpeciesComponent

15.1.1. Overview

The SpeciesComponent entity enables detailed species-level tracking within multi-species TraceableUnits (TRUs). This entity supports biodiversity compliance, species-specific sustainability claims, and detailed forest composition analysis as required by the BOOST traceability system for comprehensive timber traceability. Each component represents a distinct species within a TRU with specific volume, quality, and origin data.

15.1.2. Fields

Field Type Required Description Examples
componentId string Yes Unique identifier for the species component (primary key) SC-PINE-001, SC-FIR-KLAMATH-042
traceableUnitId string (FK) Yes Foreign key back reference to TraceableUnit TRU-PILE-CA-Klamath-042
species string Yes Species name (common or scientific) Douglas Fir, Pinus ponderosa, Western Hemlock
volumeM3 number Yes Volume of this species within the TRU in cubic meters 45.75, 120.50, 8.25
percentageByVolume number Yes Percentage of total TRU volume for this species (0-100) 53.7, 25.0, 12.8
qualityGrade string No Species-specific quality grade Grade A Douglas Fir, Structural Pine, Pulp Grade Hemlock
sourceGeographicDataId string (FK) No Foreign key to geographic origin of this species GEO-HARVEST-RIDGE-01, GEO-STAND-NORTH-23
harvestingMethod string No Method used to harvest this species (enum) chainsaw, harvester, manual, mechanical
harvestTimestamp string (date-time) No When this species was harvested 2025-07-15T07:30:00Z
carbonStorage string No CO2 data for this species component 12.5 tons CO2/m3, Carbon_class_A
scientificName string No Scientific/Latin name of the species Pseudotsuga menziesii, Pinus ponderosa, Tsuga heterophylla
dbhCm number No Diameter at breast height in centimeters 45.2, 78.5, 32.1
heightM number No Average tree height in meters 28.5, 35.2, 22.8
ageYears integer No Estimated age in years 65, 85, 45
moistureContent number No Moisture content as percentage (0-100) 12.5, 18.2, 8.7
defects array<string> No List of defects or quality issues ["small_knots", "slight_bow"], ["bark_beetle_damage"]
plantPartComposition object No Plant part breakdown within this species component {"trunk": {"volume": 18.5, "percentage": 75}}
primaryPlantPart string No Primary plant part represented by this species component trunk, heartwood, bark
structuralClassification string No Functional classification of the primary plant part structural, protective, metabolic
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/species-component/SC-001
lastUpdated string (date-time) No Timestamp of the most recent data update 2025-07-21T15:45:00Z

15.1.3. Key Features

  1. Species-Level Detail Both common and scientific name support Detailed forestry metrics (DBH, height, age) Species-specific quality grading Individual harvesting method tracking

  2. Volume Integrity Precise volume tracking in cubic meters Percentage composition within parent TRU Validation that components sum to 100% of TRU volume Support for volume conservation in processing

  3. Geographic Origin Tracking Link to specific harvest locations Support for species migration tracking Integration with supply base area boundaries Environmental compliance reporting

  4. Quality and Condition Assessment Species-specific quality grades Defect tracking and categorization Moisture content monitoring Structural integrity assessment

  5. Carbon and Environmental Data Species-specific carbon storage calculations Integration with environmental impact assessments Support for carbon credit accounting Biodiversity compliance reporting

15.1.4. Species Classification Examples

  1. Softwood Species Douglas Fir (Pseudotsuga menziesii) Ponderosa Pine (Pinus ponderosa) Western Hemlock (Tsuga heterophylla) Incense Cedar (Calocedrus decurrens)

  2. Hardwood Species California Black Oak (Quercus kelloggii) Pacific Madrone (Arbutus menziesii) Bigleaf Maple (Acer macrophyllum) Tanoak (Notholithocarpus densiflorus)

15.1.5. Harvesting Method Classifications

15.1.6. Quality Grade Standards

Species-specific quality grades vary by:

15.1.7. Validation Rules

  1. Volume Conservation Sum of all SpeciesComponent volumes must equal parent TRU volume Sum of all percentageByVolume must equal 100%

  2. Data Consistency harvestTimestamp must be ≤ parent TRU createdTimestamp volumeM3 must be > 0 percentageByVolume must be between 0 and 100

  3. Multi-Species Requirements Only required when parent TRU has isMultiSpecies = true Single-species TRUs may optionally use SpeciesComponent for detailed tracking

15.1.8. Example Use Cases

  1. Mixed Softwood Pile Multiple SpeciesComponents for Douglas Fir, Pine, Hemlock Volume percentages sum to 100% Species-specific quality grades and harvesting methods Individual geographic origins within supply base

  2. Selective Harvest Tracking Individual tree species from selective cutting operations Detailed forestry metrics (DBH, height, age) Species-specific carbon storage calculations Biodiversity impact assessment data

  3. Processing Operation Input Species composition before and after processing Volume conservation validation Species-specific claim inheritance Quality grade preservation or transformation

15.1.9. Relationships

15.1.10. Operator

16. Operator

16.1. Operator

16.1.1. Overview

The Operator entity represents personnel within the BOOST biomass chain of custody system, tracking individual workers who perform critical operations throughout the supply chain. This entity manages certification requirements, equipment authorizations, and operational responsibilities to ensure accountability, safety, and regulatory compliance across all biomass tracking and processing activities.

16.1.2. Fields

Field Type Required Description Examples
operatorId string Yes Unique identifier for the operator (primary key) OP-ANDERSON-HARVEST-001, OP-PACIFIC-MILL-QA-042
organizationId string (FK) Yes Foreign key reference to employing organization ORG-KLAMATH-HARVEST-OPERATIONS-001
operatorName string Yes Full name of the operator John Anderson, Maria Rodriguez-Chen
employeeId string No Internal employee identification number EMP-001234, H-5678
operatorType string Yes Type/role of operator within the supply chain (enum) harvester_operator, quality_inspector
certifications array<string> No Array of certifications held by the operator ["CDL_Class_A", "Chainsaw_Safety"]
equipmentAuthorizations array<string> No Equipment the operator is authorized to operate ["HARVESTER-001", "MILL-SCALE-A"]
contactInfo string No Phone/email contact information 555-0123, john.anderson@klamathops.com
isActive boolean Yes Current employment status - true if actively employed true, false
hireDate string (date) Yes Date when operator started employment 2018-04-15
skillsQualifications array<string> No Relevant skills and qualifications ["10+ years experience", "Bilingual"]
supervisorOperatorId string (FK) No Foreign key reference to direct supervisor operator (optional) OP-SUPERVISOR-HARVEST-001
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/operator/OP-ANDERSON-HARVEST-001
lastUpdated string (date-time) Yes Timestamp of last record modification 2025-07-22T09:15:00Z

16.1.3. Operator Types

  1. harvester_operator Operates harvesting equipment and machinery Responsible for tree felling and initial processing Creates initial TRU records and biometric captures Manages harvest site operations and safety Examples: Feller buncher operators, chainsaw operators

  2. transport_driver Responsible for timber transportation Manages chain of custody during transport Operates tracking point check-ins and check-outs Maintains load documentation and manifests Examples: Log truck drivers, chip truck operators

  3. mill_operator Operates processing equipment and machinery Manages TRU processing and transformation Responsible for quality control and grading Operates measurement and verification equipment Examples: Saw operators, debarker operators

  4. quality_inspector Conducts quality assessments and grading Validates measurements and specifications Performs audit and compliance inspections Documents quality metrics and defects Examples: Lumber graders, quality control technicians

  5. processing_technician Operates specialized processing equipment Manages technical processing operations Documents processing steps and quality metrics Maintains equipment calibration and performance Examples: Delimbing technicians, sorting specialists

  6. equipment_maintenance Maintains and repairs operational equipment Ensures equipment calibration and accuracy Manages preventive maintenance schedules Troubleshoots equipment malfunctions Examples: Mechanic technicians, calibration specialists

  7. loading_operator Operates loading and material handling equipment Manages TRU loading and unloading operations Documents material transfer activities Ensures safe and efficient material handling Examples: Crane operators, loader operators

  8. scaling_specialist Operates weighing and measurement systems Manages tracking point measurement activities Documents volume and weight measurements Maintains scale calibration and accuracy Examples: Truck scale operators, volume measurement technicians

  9. environmental_monitor Monitors environmental compliance and conditions Documents environmental impact assessments Ensures regulatory compliance adherence Manages environmental data collection Examples: Air quality monitors, soil impact assessors

  10. safety_coordinator

    • Oversees workplace safety and compliance

    • Manages safety training and certification programs

    • Conducts safety inspections and audits

    • Coordinates emergency response procedures

    • Examples: Safety officers, training coordinators

16.1.4. Key Features

  1. Certification Management Professional certification tracking and validation Equipment qualification documentation Training record management and renewal tracking Competency assessment and verification Regulatory compliance monitoring

  2. Geographic Assignment Primary work location assignment Mobile operator location tracking Multi-site operator assignment capabilities Tracking point responsibility assignment Regional operational area access control

  3. Equipment Integration Equipment qualification and authorization Equipment-specific training requirements Operator-equipment pairing for accountability Equipment access control and security Performance tracking by equipment type

  4. Accountability and Traceability Individual operator identification in all operations Activity logging and audit trail creation Performance metrics and quality tracking Incident and issue responsibility assignment Chain of custody operator verification

16.1.5. Certification Categories

  1. Professional Licenses Commercial Driver’s License (CDL) Certified Logger credentials Professional engineer licenses Safety training certifications Equipment operator licenses

  2. Equipment Qualifications Harvester operation certification Crane operator qualification Scale system operation training Biometric scanner certification GPS system operation training

  3. Safety Certifications OSHA safety training First aid and CPR certification Hazmat handling certification Confined space entry training Fall protection certification

  4. Industry Certifications Lumber grading certification Chain of custody training Quality control certification Environmental compliance training Sustainable forestry practices

16.1.6. Equipment Qualifications

  1. Harvesting Equipment harvester_head: Harvester head operation feller_buncher: Feller buncher operation delimber: Delimbing equipment operation forwarder: Log forwarding equipment skidder: Skidding equipment operation

  2. Transportation Equipment log_truck: Log truck operation chip_truck: Chip truck operation heavy_haul: Heavy haul equipment crane: Crane operation certification log_loader: Log loading equipment

  3. Processing Equipment sawmill: Sawmill equipment operation debarker: Debarking equipment chipper: Chipping equipment operation planer: Planing equipment operation sorter: Sorting equipment operation

  4. Measurement Equipment scale_system: Scale operation and calibration optical_scanner: Optical measurement systems biometric_scanner: Biometric identification equipment GPS: GPS and location systems moisture_meter: Moisture content measurement

16.1.7. Validation Rules

  1. Identification Requirements operatorId must be unique across system operatorName must be non-empty employeeId must be unique within organization organizationId must reference valid Organization

  2. Role and Qualification Consistency operatorRole must align with job responsibilities certifications must be appropriate for operatorRole equipmentQualifications must be relevant to work assignments Training records must support certification claims

  3. Geographic and Assignment Logic primaryWorkLocationId must reference valid GeographicData assignedTrackingPoints must be within operational area Work location must be consistent with organization operations Equipment access must align with location assignments

  4. Active Status and Compliance activeStatus must reflect current employment status Certification expiry dates must be monitored Training requirements must be current and valid Contact information must be current and accessible

16.1.8. Example Use Cases

  1. Mobile Harvesting Operator operatorRole: harvester Multiple equipment qualifications for harvesting machinery Mobile work assignments across forest locations Safety and professional logging certifications GPS and biometric scanner training

  2. Mill Scale Operator operatorRole: scale_operator Fixed assignment to mill entrance tracking point Scale system certification and calibration training Quality inspector qualifications Measurement accuracy and documentation responsibilities

  3. Multi-Role Supervisor operatorRole: supervisor Oversight responsibilities for multiple operators Broad equipment qualifications and certifications Quality control and compliance authority Training and certification management duties

16.1.9. Relationships

16.1.10. Equipment

17. Equipment

17.1. Overview

The Equipment entity represents forestry machinery and equipment used in biomass harvesting, processing, and transportation operations. This entity enables tracking of equipment ownership, utilization, maintenance, and operational status within the BOOST supply chain.

17.2. Business Purpose

17.3. Core Fields

17.3.1. Identity Fields

17.3.2. Organizational Relationships

17.3.3. Technical Specifications

17.3.4. Operational Management

17.3.5. Financial Information

17.4. Equipment Types

17.4.1. Primary Harvesting Equipment

17.4.2. Processing Equipment

17.4.3. Support Equipment

17.5. Usage Patterns

17.5.1. Equipment Assignment Workflow

  1. Acquisition: Equipment acquired by Organization, recorded with specifications

  2. Assignment: Equipment assigned to TrackingPoint (harvest site, mill yard)

  3. Operation: Current Operator assigned for daily operations

  4. Maintenance: Status updated for scheduled or unscheduled maintenance

  5. Reassignment: Equipment moved between locations as operations require

17.5.2. Cost Allocation

17.5.3. Compliance Tracking

17.6. Relationships

17.6.1. Organization → Equipment (One-to-Many)

17.6.2. Equipment → Operator (Many-to-One, Optional)

17.6.3. Equipment → TrackingPoint (Many-to-One, Optional)

17.7. Data Quality Considerations

17.7.1. Required Information

17.7.2. Optional but Important

17.7.3. Validation Rules

17.8. Integration Points

17.8.1. TraceableUnit Integration

17.8.2. MaterialProcessing Integration

17.8.3. Compliance Integration

This Equipment entity provides comprehensive asset management capabilities while supporting the operational and regulatory requirements of biomass supply chain management.

17.8.4. BiometricIdentifier

Enables media-interruption-free tracking for TraceableUnit entities through optical pattern recognition and biometric signatures.

**🗂️ View BiometricIdentifier in ERD Navigator**

18. BiometricIdentifier

18.1. BiometricIdentifier

18.1.1. Overview

The BiometricIdentifier entity provides optical biometric identification for TRUs with multi-species support to enable attachment-free wood identification as required by the BOOST traceability system. This entity captures unique optical patterns from individual pieces of wood without requiring physical attachments, supporting media-interruption-free traceability through natural wood characteristics.

18.1.2. Fields

Field Type Required Description Examples
biometricId string Yes Unique identifier for the biometric record (primary key) BIO-001, BIO-DOUGLAS-FIR-KLA-042
traceableUnitId string (FK) Yes Foreign key to TRU being identified TRU-LOG-001, TRU-PILE-CA-042
biometricSignature string Yes Optical pattern data (encoded string) Base64 encoded pattern data or hash
captureMethod string Yes Method used for biometric capture (enum) optical_scanner, photo_analysis
captureGeographicDataId string (FK) No Foreign key to location where biometric was captured GEO-HARVEST-SITE-001, GEO-MILL-001
captureTimestamp string (date-time) Yes When the biometric was captured 2025-07-15T06:45:00Z
trackingPointId string (FK) No Foreign key to tracking point where captured TP-HARVEST-001, TP-MILL-ENTRANCE-01
speciesBiometrics array<string> No Individual species biometric data for multi-species TRUs ["Pine: pattern_hash_123", "Fir: pattern_hash_456"]
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/biometric-identifier/BIO-001
lastUpdated string (date-time) No Timestamp of the most recent data update 2025-07-21T15:45:00Z

18.1.3. Capture Methods

  1. optical_scanner Dedicated optical scanning equipment High-resolution cameras with controlled lighting Automated pattern extraction algorithms Real-time processing and signature generation Integration with tracking point infrastructure

  2. photo_analysis Mobile device camera capture Manual or semi-automated photo capture Post-processing pattern analysis Cloud-based or local analysis systems Field verification and backup identification

18.1.4. Key Features

  1. Attachment-Free Identification No physical tags or markers required Natural wood grain pattern recognition Unique optical signatures for individual logs Non-invasive identification process Environmentally friendly approach

  2. Multi-Species Support Species-specific biometric algorithms Multiple pattern recognition within single TRU Complex pile and batch identification Species composition validation Mixed-species pile tracking

  3. Pattern Recognition Technology Machine learning algorithms for pattern matching Unique signature generation from wood grain Bark pattern and texture analysis End-grain pattern recognition Cross-sectional analysis capabilities

  4. Quality Assurance Pattern uniqueness validation False positive prevention Multiple angle capture support Lighting condition normalization Pattern degradation tracking over time

18.1.5. Biometric Signature Formats

  1. Hash-Based Signatures Cryptographic hash of pattern data Compact storage and fast comparison Privacy-preserving identification Tamper-evident signature format

  2. Vector-Based Signatures Mathematical representation of patterns Machine learning feature vectors Scalable similarity matching Advanced pattern analysis support

  3. Image-Based Signatures Processed image data storage Visual pattern verification Human-readable verification support Quality assessment capabilities

18.1.6. Validation Rules

  1. TRU Integration traceableUnitId must reference existing TRU captureTimestamp must be ≥ TRU creation timestamp Species biometrics must match TRU species composition

  2. Pattern Quality biometricSignature must be non-empty and valid format Capture method must be appropriate for equipment type Pattern uniqueness must be verified within system

  3. Location Consistency captureGeographicDataId must reference valid location trackingPointId must be consistent with location Capture equipment must be available at location

18.1.7. Multi-Species Biometric Tracking

  1. Complex Pile Analysis Individual log identification within piles Species-specific pattern databases Multiple biometric signatures per TRU Pattern correlation and validation

  2. Species Composition Validation Biometric confirmation of species identification Cross-validation with visual species assessment Pattern-based species classification Biodiversity compliance verification

  3. Processing Chain Continuity Pattern preservation through processing steps Split/merge operation pattern tracking Parent/child TRU pattern inheritance Continuous identification chain

18.1.8. Example Use Cases

  1. Harvest Site Identification Initial biometric capture during felling End-grain pattern analysis of fresh cuts Species verification through pattern analysis Unique identification without physical tags

  2. Mill Entrance Verification Final biometric verification before processing Pattern matching with harvest site capture Quality assessment through pattern analysis Processing authorization through identification

  3. Multi-Species Pile Processing Individual log identification within mixed piles Species-specific processing routing Pattern-based quality grading Biodiversity compliance documentation

18.1.9. Relationships

18.1.10. LocationHistory

Tracks movement history for TraceableUnit entities, connecting to GeographicData and TrackingPoint entities.

**🗂️ View LocationHistory in ERD Navigator**

19. LocationHistory

19.1. LocationHistory

19.1.1. Overview

The LocationHistory entity implements comprehensive location history tracking for TRUs with timestamps, processing links, and verification methods to support complete movement audit trails. This entity enables tracking every location change, transport method, and verification approach throughout the TRU lifecycle as required by the BOOST traceability system for media-interruption-free traceability.

19.1.2. Fields

Field Type Required Description Examples
locationHistoryId string Yes Unique identifier for the location history record (primary key) LH-001, LH-KLA-042-MOVE-003
traceableUnitId string (FK) Yes Foreign key to TRU being tracked TRU-PILE-CA-Klamath-042
geographicDataId string (FK) Yes Foreign key to location at this point in time GEO-HARVEST-001, GEO-MILL-ENTRANCE-01
timestamp string (date-time) Yes When TRU was at this location 2025-07-21T10:30:00Z
locationEventType string Yes Type of location event (enum) arrival, departure, processing, storage, measurement
materialProcessingId string (FK) No Processing event that triggered location change (optional) PROC-LIMB-KLA-002, PROC-SORT-003
operatorId string (FK) No Operator responsible for location change OP-TRUCK-DRIVER-001, OP-CRANE-002
equipmentUsed string No Equipment used for location change harvester, forwarder, truck, crane
notes string No Additional context about location event Weather delay due to rain, Quality inspection completed
distanceTraveled number No Distance from previous location in kilometers (optional) 12.5, 45.8, 150.2
transportMethod string No Method of transportation (enum) truck, rail, ship, conveyor, manual
isCurrentLocation boolean Yes True if this is the current location true, false
verificationMethods array<string> No Methods used to verify location (enum array) ["GPS", "RFID"], ["visual_confirmation", "biometric_scan"]
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/location-history/LH-001
lastUpdated string (date-time) No Timestamp of the most recent data update 2025-07-21T15:45:00Z

19.1.3. Location Event Types

  1. arrival TRU arrives at a new location Timestamp marks arrival time Often paired with verification methods May trigger processing events

  2. departure TRU leaves a location Timestamp marks departure time Transport method usually specified Distance to next location may be calculated

  3. processing TRU undergoes processing at location Links to MaterialProcessing entity Location remains same, but TRU state changes Processing operation triggers location history entry

  4. storage TRU stored at location for extended period Temporary holding or staging May include storage conditions in notes Duration calculated from arrival/departure timestamps

  5. measurement Measurement activity at location Links to MeasurementRecord entities Quality assessment or volume verification Often occurs at tracking points

19.1.4. Transport Methods

19.1.5. Verification Methods

19.1.6. Key Features

  1. Complete Movement Tracking Chronological location history for each TRU Transport method and distance tracking Equipment and operator accountability Current location flag management

  2. Processing Integration Link to MaterialProcessing operations Processing-triggered location events State change tracking at same location Complete transformation history

  3. Verification Support Multiple verification methods per event Automated and manual verification options GPS accuracy and reliability tracking Biometric integration for identification

  4. Audit Trail Completeness Every location change documented Operator accountability for movements Equipment usage tracking Notes for contextual information

19.1.7. Validation Rules

  1. Timeline Integrity Timestamps must be chronological for same TRU Only one current location per TRU (isCurrentLocation = true) Processing events must have valid materialProcessingId

  2. Location Consistency geographicDataId must reference valid GeographicData Transport method must be appropriate for distance Verification methods must be realistic for location type

  3. Current Location Management Only one LocationHistory entry per TRU can have isCurrentLocation = true Current location must be most recent timestamp Location updates must update previous current location flag

19.1.8. Example Use Cases

  1. Harvest to Mill Transport Departure from harvest site with truck transport Arrival at forest road staging area Departure from staging area Arrival at mill entrance with final verification

  2. Processing Location Events Arrival at processing facility Processing event at same location (delimbing, crosscutting) Storage event while awaiting next processing step Departure after processing completion

  3. Multi-Modal Transportation Truck transport from forest to rail loading Rail transport for long-distance movement Truck transport from rail to final destination Complete distance and method tracking

19.1.9. Relationships

19.1.10. MeasurementRecord

20. MeasurementRecord

20.1. MeasurementRecord

20.1.1. Overview

The MeasurementRecord entity captures measurements at different tracking points with TRU references and species-specific data to support automated reconciliation between forest and mill measurements. This entity enables complete volume tracking, quality assessment, and measurement validation throughout the supply chain as required by the BOOST traceability system.

20.1.2. Fields

Field Type Required Description Examples
recordId string Yes Unique identifier for the measurement record (primary key) MR-001, MR-KLAMATH-LOG-042
traceableUnitId string (FK) Yes Foreign key to TRU being measured TRU-LOG-001, TRU-PILE-CA-042
measuredVolume number No Volume measurement in cubic meters 12.5, 85.75, 245.2
measuredLength number No Length measurement in meters 8.2, 12.5, 16.0
measuredDiameter number No Diameter measurement in centimeters 45.2, 78.5, 32.1
measurementMethod string Yes Method used for measurement (enum) harvester, mill, manual, optical
measurementGeographicDataId string (FK) No Foreign key to location where measurement taken GEO-HARVEST-001, GEO-MILL-ENTRANCE-01
measurementTimestamp string (date-time) Yes When the measurement was taken 2025-07-21T08:30:00Z
operatorId string (FK) No Foreign key to operator who took measurement OP-JOHN-DOE-001, OP-SCALE-TECH-02
trackingPointId string (FK) No Foreign key to tracking point where measured TP-HARVEST-001, TP-MILL-ENTRANCE-01
speciesMeasurements array<string> No Individual species measurements for multi-species TRUs ["Pine: 45.2m3", "Fir: 28.8m3"]
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/measurement-record/MR-001
lastUpdated string (date-time) No Timestamp of the most recent data update 2025-07-21T15:45:00Z

20.1.3. Measurement Methods

  1. harvester Automated measurements from harvesting equipment High precision volume calculations Real-time data collection during harvest operations Integration with harvester computer systems

  2. mill Scale and measurement systems at processing facilities Final volume and quality assessments Integration with mill processing equipment Quality grade determination

  3. manual Hand measurements using calipers, measuring tapes Field verification measurements Quality control spot checks Backup measurement method

  4. optical Optical scanning and measurement systems Non-contact measurement techniques 3D scanning for precise volume calculation Integration with biometric identification

20.1.4. Key Features

  1. Multi-Point Measurement Measurements at harvest, transport, and processing points Tracking point integration for location-based measurements Chronological measurement history

  2. Species-Specific Data Individual species measurements within multi-species TRUs Species composition validation Species-specific volume tracking

  3. Method Validation Multiple measurement methods for cross-validation Automated vs manual measurement comparison Quality assurance through redundant measurements

  4. Geographic Integration Location-based measurement tracking Integration with tracking point infrastructure Spatial validation of measurement locations

20.1.5. Validation Rules

  1. Measurement Consistency All volume measurements must be ≥ 0 Length and diameter measurements must be ≥ 0 Measurement timestamp must be valid date-time

  2. TRU Integration traceableUnitId must reference existing TRU Measurement timestamp must be ≥ TRU creation timestamp Sum of species measurements must equal total measurement

  3. Location Validation measurementGeographicDataId must reference valid location Tracking point integration for location consistency Operator assignment validation

20.1.6. Example Use Cases

  1. Harvest Measurements Harvester-based automated volume calculation Real-time measurement during tree processing Species-specific measurements for multi-species stands GPS location integration

  2. Mill Entrance Verification Scale-based volume verification Quality grade assessment measurements Final reconciliation with harvest measurements Processing facility integration

  3. Quality Control Measurements Manual verification measurements Spot check validation of automated systems Defect assessment and grading Compliance verification measurements

20.1.7. Relationships

20.1.8. MoistureContent

21. MoistureContent

21.1. MoistureContent

21.1.1. Overview

The MoistureContent entity tracks moisture measurements for biomass materials throughout the BOOST traceability system. Moisture content is a critical quality parameter affecting material processing, energy content, pricing, and regulatory compliance. This entity provides comprehensive moisture tracking with measurement validation, quality assurance protocols, and integration with processing operations and regulatory requirements.

21.1.2. Fields

Field Type Required Description Examples
moistureContentId string Yes Unique identifier for the moisture content record (primary key) MC-001, MC-TRU-LOG-CA-042-20240315
traceableUnitId string (FK) Yes Foreign key to TRU being measured for moisture TRU-LOG-001, TRU-PILE-CA-042
moisturePercentage number Yes Moisture content as percentage of weight (0-100%) 12.5, 18.2, 45.7
measurementMethod string Yes Method used to determine moisture content (enum) oven_dry, electrical_resistance, near_infrared, microwave
measurementDate string (date-time) Yes When the moisture measurement was taken 2024-03-15T10:30:00Z, 2024-07-22T14:15:00Z
measurementGeographicDataId string (FK) No Foreign key to location where measurement was taken GEO-MILL-ENTRANCE-001, GEO-HARVEST-SITE-KLA-04
operatorId string (FK) No Foreign key to operator who performed measurement OP-MILL-TECH-001, OP-QUALITY-INSPECTOR-02
standardReference string No Standard procedure followed for measurement (enum) ASTM_D4442, ISO_13061, CEN_EN_14774, local_standard
sampleSize integer No Number of measurement points taken 3, 5, 10
measurementAccuracy number No Estimated accuracy of measurement (± percentage points) 1.0, 0.5, 2.0
temperatureDuringMeasurement number No Temperature during measurement (Celsius) 20.5, 15.2, 28.0
humidityDuringMeasurement number No Relative humidity during measurement (%) 45.0, 62.5, 38.0
calibrationDate string (date-time) No Last calibration date of measurement equipment 2024-01-15T09:00:00Z, 2024-06-01T08:30:00Z
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/moisture-content/MC-001

21.1.3. Measurement Methods

  1. oven_dry

    • Laboratory standard method using controlled heating

    • High accuracy (±0.5-1.0%) but time-intensive

    • Requires sample removal and laboratory facilities

    • ASTM D4442 and ISO 13061 standard compliance

  2. electrical_resistance

    • Portable probe method using electrical conductivity

    • Moderate accuracy (±1-2%) with immediate results

    • Species-specific calibration required

    • Field-suitable for routine measurements

  3. near_infrared

    • Non-destructive spectroscopic analysis

    • High accuracy (±0.5-1.5%) with rapid results

    • Expensive equipment but minimal sample preparation

    • Suitable for continuous monitoring applications

  4. microwave

    • Rapid moisture determination using microwave energy

    • Moderate accuracy (±1-2%) with fast results

    • Requires sample preparation and specific equipment

    • Good for bulk material assessment

  5. gravimetric

    • Weight-based calculation using before/after drying

    • High accuracy reference method

    • Time-intensive but reliable

    • Used for calibrating other methods

  6. capacitive

    • Dielectric measurement of moisture content

    • Fast results with moderate accuracy

    • Portable equipment for field use

    • Species and density dependent

21.1.4. Quality Grade Requirements

  1. Grade A (Premium)

    • Maximum moisture: 18%

    • Structural and appearance applications

    • High-value products requiring stability

    • Enhanced durability and workability

  2. Grade B (Standard)

    • Maximum moisture: 22%

    • General construction and manufacturing

    • Good balance of quality and cost

    • Suitable for most commercial applications

  3. Grade C (Utility)

    • Maximum moisture: 30%

    • Lower-grade applications and processing

    • Cost-effective for specific uses

    • May require additional drying for some applications

  4. Structural

    • Maximum moisture: 19%

    • Load-bearing construction applications

    • Engineered wood products

    • Building code compliance requirements

  5. Fuel Grade

    • Maximum moisture: 50%

    • Biomass fuel applications

    • Energy content directly affected by moisture

    • Economic optimization for fuel efficiency

21.1.5. Key Features

  1. Quality Assurance

    • Standardized measurement protocols

    • Equipment calibration tracking

    • Environmental condition monitoring

    • Sample size and accuracy documentation

  2. Processing Integration

    • Pre- and post-processing moisture tracking

    • Drying operation effectiveness monitoring

    • Volume adjustment calculations

    • Quality grade validation support

  3. Regulatory Compliance

    • LCFS biomass moisture requirements

    • FSC chain of custody moisture tracking

    • SBP per-batch moisture validation

    • Export/import documentation support

  4. Business Intelligence

    • Processing efficiency analysis

    • Quality control trend monitoring

    • Economic optimization through moisture management

    • Customer specification compliance verification

21.1.6. Validation Rules

  1. Measurement Consistency

    • moisturePercentage must be between 0 and 100%

    • measurementDate must be ≥ TRU creation timestamp

    • Measurement location must be valid if specified

    • Operator must be qualified for measurement method

  2. Processing Logic

    • Drying operations must reduce moisture content

    • Storage may increase moisture within limits

    • Transportation should not significantly change moisture

    • Quality grade must be compatible with moisture level

  3. Quality Assurance Requirements

    • Equipment calibration must be current

    • Standard procedures must be followed

    • Environmental conditions must be recorded

    • Sample size must be adequate for accuracy

21.1.7. Example Use Cases

  1. Sawlog Processing Moisture Control

    • Initial measurement at harvest: 35% moisture

    • Measurement method: electrical_resistance probe

    • Processing: Air drying to 18% for Grade A lumber

    • Final verification: oven_dry method for accuracy

    • Quality assurance: Multi-point sampling with ASTM D4442

  2. Biomass Fuel Delivery Verification

    • Delivery requirement: Maximum 45% moisture content

    • Measurement method: near_infrared for rapid assessment

    • LCFS compliance: Documentation for carbon intensity calculation

    • Quality control: Continuous monitoring during unloading

    • Contract validation: Meeting customer specifications

  3. Export Lumber Certification

    • Export requirement: 19% moisture maximum

    • Measurement method: oven_dry for regulatory compliance

    • Phytosanitary documentation: Moisture levels for pest control

    • Customer specifications: Meeting international standards

    • Quality certification: Third-party verification support

21.1.8. Relationships

21.1.9. TrackingPoint

22. TrackingPoint

22.1. TrackingPoint

22.1.1. Overview

The TrackingPoint entity implements the three critical tracking points (harvest site, skid road, forest road, mill entrance) as defined in the BOOST traceability system for media-interruption-free traceability. These tracking points serve as infrastructure nodes where TRUs are identified, measured, and verified throughout the supply chain using various equipment and identification technologies.

22.1.2. Fields

Field Type Required Description Examples
trackingPointId string Yes Unique identifier for the tracking point (primary key) TP-001, TP-HARVEST-KLAMATH-04
pointType string Yes Type of tracking point (enum) harvest_site, skid_road, forest_road, mill_entrance
geographicDataId string (FK) Yes Foreign key to location of tracking point GEO-HARVEST-SITE-001, GEO-MILL-ENTRANCE-01
equipmentUsed string Yes Equipment deployed at this tracking point RFID_reader, QR_scanner, biometric_system, GPS
operatorId string (FK) No Foreign key to operator responsible for tracking point OP-HARVEST-TECH-001, OP-MILL-GATE-02
establishedTimestamp string (date-time) Yes When the tracking point was established 2025-07-15T06:00:00Z
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/tracking-point/TP-001
lastUpdated string (date-time) No Timestamp of the most recent data update 2025-07-21T15:45:00Z

22.1.3. Tracking Point Types

  1. harvest_site Initial capture point where TRUs are created Biometric identification at felling/delimbing Species identification and initial measurements GPS coordinate capture for harvest location

  2. skid_road Secondary aggregation and sorting point TRU consolidation from multiple harvest sites Quality grading and assortment classification Load preparation for transport

  3. forest_road Transport verification and load documentation Final forest-based measurement and verification Transport method and vehicle assignment Departure timestamp and route planning

  4. mill_entrance Final verification point before processing Scale-based measurement and reconciliation Quality assessment and acceptance Processing facility intake documentation

22.1.4. Equipment Categories

22.1.5. Key Features

  1. Critical Point Infrastructure Implements BOOST traceability system’s three critical points Equipment redundancy for media break prevention Location-based verification capabilities Operator accountability and management

  2. Multi-Technology Support RFID tag reading capabilities QR code scanning systems Biometric pattern recognition GPS location verification Integration with multiple identification methods

  3. Process Integration MeasurementRecord capture at tracking points BiometricIdentifier scanning locations LocationHistory event triggers Processing workflow integration

  4. Quality Assurance Equipment calibration and maintenance tracking Operator training and certification requirements Performance monitoring and validation Backup identification methods

22.1.6. Equipment Specifications

  1. RFID Systems UHF RFID readers for tag detection Range: 1-10 meters depending on tag type Integration with handheld and fixed readers Weather-resistant installation options

  2. Optical Biometric Systems High-resolution cameras for wood pattern capture Machine learning algorithms for pattern recognition No physical attachment requirements Multi-species pattern database support

  3. GPS Systems Sub-meter accuracy for location verification WAAS/EGNOS correction support Integration with geographic data systems Offline capability for remote locations

22.1.7. Validation Rules

  1. Location Consistency geographicDataId must reference valid GeographicData pointType must be appropriate for geographic location Equipment must be suitable for environmental conditions

  2. Equipment Requirements At least one identification method must be specified Equipment must be appropriate for pointType Operator must be certified for equipment operation

  3. Establishment Timeline establishedTimestamp must be valid date-time Equipment installation must precede TRU processing Operator assignment must be current and valid

22.1.8. Example Use Cases

  1. Harvest Site Setup Establish biometric scanning equipment at harvest location GPS coordinate verification for precise location Operator training for equipment operation Integration with harvester computer systems

  2. Mill Entrance Configuration Scale system integration with RFID readers Quality assessment station setup Final measurement and reconciliation equipment Processing facility intake procedures

  3. Mobile Tracking Points Portable equipment for temporary harvest sites Quick setup and calibration procedures Weather-resistant equipment configurations Remote location connectivity solutions

22.1.9. Relationships

22.1.10. DataReconciliation

23. DataReconciliation

23.1. DataReconciliation

23.1.1. Overview

The DataReconciliation entity reconciles measurements between forest and mill with TRU references and species-specific discrepancies to ensure data accuracy and prevent media breaks. This entity enables automated comparison of harvest measurements with mill scale measurements, identifies discrepancies, and tracks resolution status as required by the BOOST traceability system for measurement validation.

23.1.2. Fields

Field Type Required Description Examples
reconciliationId string Yes Unique identifier for the reconciliation record (primary key) DR-001, DR-KLA-042-RECON-001
traceableUnitId string (FK) Yes Foreign key to TRU being reconciled TRU-PILE-CA-Klamath-042
transactionId string (FK) No Foreign key to associated transaction TXN-PACIFIC-MILL-001
forestMeasurement number Yes Measurement taken in forest (cubic meters) 85.25, 120.50, 45.75
millMeasurement number Yes Measurement taken at mill (cubic meters) 84.75, 119.25, 46.10
discrepancy number Yes Difference between measurements (forest - mill) 0.50, -1.25, 0.35
reconciliationStatus string Yes Current status of reconciliation (enum) pending, resolved, disputed
discrepancyReason string No Reason for discrepancy Natural moisture loss, Scale calibration error, Bark loss
reconciliationDate string (date-time) Yes When reconciliation was performed 2025-07-21T15:00:00Z
reconciliationOperator string No Operator who performed reconciliation OP-QUALITY-TECH-001, OP-SCALE-MANAGER-02
speciesDiscrepancies array<string> No Per-species discrepancies for multi-species TRUs ["Douglas Fir: +0.25m3", "Pine: -0.15m3"]
tolerancePercentage number No Acceptable tolerance percentage (0-100) 2.5, 5.0, 1.0
resolutionNotes string No Notes on how discrepancy was resolved Accepted within tolerance, Remeasurement confirmed mill scale
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/data-reconciliation/DR-001
lastUpdated string (date-time) No Timestamp of the most recent data update 2025-07-21T15:30:00Z

23.1.3. Reconciliation Status Values

  1. pending Reconciliation process initiated but not completed Measurements compared, discrepancy calculated Awaiting review or resolution action Default status for new reconciliation records

  2. resolved Discrepancy has been addressed and accepted Resolution notes document how discrepancy was handled TRU can proceed in transaction processing Final status for acceptable discrepancies

  3. disputed Discrepancy exceeds acceptable tolerance Requires investigation or remeasurement TRU processing may be held pending resolution Escalation to quality assurance team

23.1.4. Key Features

  1. Automated Comparison Systematic comparison of forest vs mill measurements Automatic discrepancy calculation Tolerance-based status assignment Species-level discrepancy tracking

  2. Quality Assurance Tolerance percentage enforcement Discrepancy reason categorization Resolution process documentation Audit trail for measurement validation

  3. Species-Specific Tracking Individual species discrepancy tracking Multi-species TRU reconciliation support Species composition validation Detailed discrepancy analysis

  4. Process Integration Transaction processing integration TRU status workflow integration Operator accountability tracking Measurement record validation

23.1.5. Discrepancy Analysis

  1. Common Discrepancy Reasons Natural moisture loss: Drying during transport Bark loss: Natural bark shedding during handling Scale calibration: Equipment calibration differences Measurement method: Different measurement techniques Species misidentification: Incorrect species classification

  2. Tolerance Guidelines High-value timber: 1-2% tolerance Pulp wood: 3-5% tolerance Biomass fuel: 5-10% tolerance Multi-species piles: Higher tolerance for complexity

  3. Resolution Strategies Within tolerance: Accept discrepancy, document reason Exceeds tolerance: Investigate and remeasure Systematic error: Calibrate equipment, adjust process Species composition: Verify species identification

23.1.6. Validation Rules

  1. Measurement Consistency forestMeasurement and millMeasurement must be ≥ 0 discrepancy = forestMeasurement - millMeasurement tolerancePercentage must be between 0 and 100

  2. Status Workflow Initial status must be "pending" Status changes must be documented with reconciliationDate Resolved status requires resolutionNotes

  3. TRU Integration traceableUnitId must reference existing TRU reconciliationDate must be ≥ TRU measurement timestamps Species discrepancies must match TRU species composition

23.1.7. Example Use Cases

  1. Standard Reconciliation Forest measurement: 85.25 m³ Mill measurement: 84.75 m³ Discrepancy: 0.50 m³ (0.6%) Status: Resolved (within 2% tolerance) Reason: Natural moisture loss during transport

  2. Disputed Reconciliation Forest measurement: 120.50 m³ Mill measurement: 115.25 m³ Discrepancy: 5.25 m³ (4.4%) Status: Disputed (exceeds 3% tolerance) Action: Remeasurement and investigation required

  3. Species-Specific Reconciliation Multi-species pile with individual species discrepancies Overall discrepancy within tolerance Individual species discrepancies documented Species composition validation completed

23.1.8. Relationships

23.2. Certification and Claims Entities

23.2.1. CertificationBody

24. CertificationBody

24.1. Overview

The CertificationBody object represents an independent organization authorized to issue certificates under specific certification schemes. The primary key is cbId.

24.2. Fields

Field Type Required Description Examples
cbId string Yes Unique identifier for the certification body (primary key) SFI, FSC-US, PEFC-001
cbName string Yes Official name of the certification body Sustainable Forestry Initiative
cbType string Yes Type or category of certification body scheme-owner, third-party, accredited-body
accreditationStatus string Yes Current accreditation status active, suspended, expired
authorizedSchemes array Yes List of schemes the CB can certify under ["SFI-CoC", "SFI-FM"]
contactInformation object Yes Contact details {"email": "certs@sfiprogram.org", "phone": "+1-202-555-0100"}
operationalRegions array Yes Geographic regions where CB operates ["US", "CA", "MX"]
accreditationBody string No Organization that accredited this CB ANSI-ASQ National Accreditation Board
validityPeriod object Yes Period of CB authorization {"start": "2020-01-01", "end": "2025-12-31"}

24.3. Relationships

24.3.1. Parent Entities

24.3.2. Child Entities

24.4. Business Rules

  1. Unique Identification: cbId must be unique across all certification bodies

  2. Scheme Authorization: CB can only issue certificates for schemes in authorizedSchemes

  3. Regional Compliance: CB must operate within authorized operationalRegions

  4. Accreditation Requirements: Must maintain valid accreditation status

  5. Validity Period: Cannot issue certificates outside validityPeriod

24.5. Common Queries

24.5.1. CertificationScheme

25. CertificationScheme

25.1. CertificationScheme

25.1.1. Overview

The CertificationScheme entity defines certification standards and requirements with geographic applicability as part of Phase 2 BOOST traceability system enhancements. This entity provides the foundational definitions for sustainability certifications, their requirements, and applicable contexts for use throughout the timber supply chain.

25.1.2. Fields

Field Type Required Description Examples
certificationSchemeId string Yes Unique identifier for the certification scheme (primary key) CERT-SCHEME-FSC-001, CERT-SCHEME-SFI-COC
schemeName string Yes Official name of the certification scheme FSC Chain of Custody, SFI Chain of Custody
schemeType string Yes Type of certification scheme (enum) forest_management, chain_of_custody, biomass_sustainability
schemeStandard string No Standard or version identifier FSC-STD-40-004 V3-1, SFI-2015-2019 COC
issuingOrganizationId string (FK) Yes Foreign key to organization that issues this scheme ORG-FSC-INTERNATIONAL, ORG-SFI-INC
schemeDescription string No Detailed description of the certification scheme Ensures responsible forest management
applicableGeographicAreas array<string> No Geographic areas where this scheme is applicable ["GEO-REGION-NORTH-AMERICA"]
eligibleMaterialTypes array<string> No Material types eligible for this certification scheme ["softwood", "hardwood", "mixed"]
claimTypes array<string> No Types of claims supported by this scheme ["FSC Mix", "FSC 100%", "FSC Recycled"]
auditRequirements string No Audit and verification requirements Annual surveillance audits
chainOfCustodyRequirements string No Chain of custody tracking requirements Physical or percentage-based system
documentationRequirements array<string> No Required documentation and record-keeping ["purchase_records", "sales_invoices"]
validityPeriod string No Typical validity period for certifications 3 years, 5 years
website string (uri) No Official website for the certification scheme https://fsc.org/
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/certification-scheme/CERT-SCHEME-FSC-001
lastUpdated string (date-time) No Timestamp of the most recent data update 2025-07-21T15:45:00Z

25.1.3. Scheme Types

  1. forest_management Certifies responsible forest management practices Covers forest planning, biodiversity conservation, and social impacts Examples: FSC Forest Management, SFI Forest Management Applies to forest owners and managers Long-term forest stewardship focus

  2. chain_of_custody Tracks certified material through supply chain Ensures segregation and proper mixing calculations Examples: FSC Chain of Custody, SFI Chain of Custody Applies to processors, manufacturers, and traders Material flow and claim verification

  3. controlled_wood Ensures wood avoids controversial sources Risk assessment and mitigation requirements Examples: FSC Controlled Wood, SFI Fiber Sourcing Due diligence and supply chain verification Minimum acceptable standards

  4. biomass_sustainability Verifies sustainable biomass production and sourcing Greenhouse gas emission reductions and land use criteria Examples: SBP (Sustainable Biomass Partnership) Regional risk assessments and supply base evaluations Energy and environmental benefits focus

  5. carbon_offset Quantifies and verifies carbon sequestration and emission reductions Additionality, permanence, and measurement requirements Examples: Verified Carbon Standard (VCS), Climate Action Reserve Forest carbon projects and methodologies Third-party verification and monitoring

  6. environmental_management Comprehensive environmental management systems ISO 14001 and other environmental standards Continuous improvement and compliance frameworks Environmental impact assessment and mitigation Stakeholder engagement and reporting

25.1.4. Key Features

  1. Geographic Applicability Regional and national scheme variations Jurisdiction-specific requirements and adaptations Local stakeholder consultation requirements National forest legislation compliance Cultural and social context integration

  2. Material Type Specificity Scheme requirements vary by material type Species-specific requirements and considerations Product category eligibility and restrictions Processing method compatibility End-use application suitability

  3. Claim Management Supported claim types and calculation methods Percentage thresholds and mixing allowances Label use requirements and restrictions Marketing claim validation requirements Consumer communication standards

  4. Verification Requirements Audit frequency and scope requirements Certification body accreditation standards Competency requirements for auditors Stakeholder consultation processes Complaint and dispute resolution procedures

25.1.5. Chain of Custody Systems

  1. Physical Separation Complete segregation of certified and non-certified materials Separate storage, processing, and handling systems No mixing of certified and non-certified materials Highest integrity but most restrictive system Premium pricing and marketing advantages

  2. Percentage System Allows mixing of certified and non-certified materials Volume-based or mass-based percentage calculations Rolling average calculations over defined periods Balance monitoring and claim reconciliation Flexibility for complex supply chains

  3. Credit System Credits earned from certified purchases Credits applied to sales of eligible products Time-based credit accumulation and application Complex accounting and verification requirements Maximum supply chain flexibility

25.1.6. Documentation Requirements

  1. Purchase Records Supplier information and certification status Volume and material type documentation Certificate numbers and validity verification Purchase order and invoice records Chain of custody claim verification

  2. Production Records Input material tracking and inventory management Processing records and yield calculations Quality control and specification compliance Waste and by-product tracking Production planning and scheduling

  3. Sales Documentation Customer information and requirements Product specifications and claims Delivery documentation and tracking Invoice and shipping records Certificate and label application

  4. Training and Competency Staff training records and competency assessment Chain of custody system understanding Procedure compliance and verification Continuous improvement and corrective actions Management system documentation

25.1.7. Validation Rules

  1. Scheme Identification certificationSchemeId must be unique across system schemeName must match official scheme designation schemeStandard must reference current valid version issuingOrganizationId must reference valid organization

  2. Geographic and Material Consistency applicableGeographicAreas must reference valid geographic boundaries eligibleMaterialTypes must align with scheme scope claimTypes must be officially recognized by issuing organization Geographic coverage must not exceed scheme authority

  3. Requirement Specifications auditRequirements must specify minimum frequency and scope chainOfCustodyRequirements must be technically feasible documentationRequirements must support verification needs validityPeriod must align with scheme standards

25.1.8. Example Use Cases

  1. FSC Chain of Custody Implementation Multi-site certification for integrated forest products company Percentage-based system for mixed material processing Species-specific claims for biodiversity conservation Third-party audits with annual surveillance International supply chain verification

  2. SFI Fiber Sourcing Program Regional fiber sourcing with controlled wood requirements Training programs for logger and landowner education Biodiversity conservation and water quality protection Community involvement and stakeholder engagement Research and development support

  3. Biomass Sustainability Partnership (SBP) Regional risk assessment and mitigation implementation Supply base evaluation and verification Greenhouse gas emission analysis and reporting Energy efficiency and carbon footprint reduction Independent third-party evaluation

25.1.9. Relationships

25.1.10. Claim

26. Claim

26.1. Claim

26.1.1. Overview

The Claim entity enables species-specific sustainability claims with TRU references and inheritance tracking for comprehensive certification chain-of-custody in the BOOST traceability system. This entity supports multiple certification schemes and enables granular tracking of sustainability claims through the processing chain, including parent-child TRU inheritance.

26.1.2. Fields

Field Type Required Description Examples
claimId string Yes Unique identifier for the claim (primary key) CLAIM-001, CLAIM-FSC-KLA-042
traceableUnitId string (FK) Yes Foreign key to TRU this claim applies to TRU-LOG-001, TRU-PILE-CA-042
claimType string Yes Type of sustainability claim (enum) FSC Mix, SBP-compliant, PEFC, organic
certificationSchemeId string (FK) No Foreign key to certification scheme details CERT-FSC-001, CERT-SBP-GLOBAL
statement string Yes Formal claim statement FSC Mix 70%, SBP-compliant biomass
validated boolean Yes Whether the claim has been validated true, false
validatedBy string (FK) No Foreign key to validator (Organization/Person) ORG-FSC-CERTIFIER-001, OP-AUDITOR-02
validationDate string (date-time) No When the claim was validated 2025-07-15T09:00:00Z
applicableSpecies array<string> No Specific species this claim applies to ["douglas_fir", "ponderosa_pine"]
claimPercentage number No Percentage of material covered by claim (0-100) 70.5, 100.0, 45.2
claimScope string No Scope of the claim through supply chain harvest, processing, transport, full_chain
evidenceDocumentId string (FK) No Foreign key to supporting evidence document DOC-CERT-FSC-001, DOC-AUDIT-RPT-042
claimExpiry string (date-time) No When the claim expires 2026-07-15T23:59:59Z
inheritedFromTRU array<string> No TRU IDs from which this claim was inherited ["TRU-PARENT-001", "TRU-PARENT-002"]
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/claim/CLAIM-001
lastUpdated string (date-time) No Timestamp of the most recent data update 2025-07-21T15:45:00Z

26.1.3. Claim Types

  1. FSC Mix Forest Stewardship Council mixed content claims Percentage-based certification claims Chain of custody requirements Species-specific applicability Controlled wood component tracking

  2. FSC 100% Full FSC certified content Complete chain of custody verification No non-certified material mixing Premium certification status Strict processing segregation

  3. FSC Recycled Post-consumer recycled content claims Recycled content percentage tracking Source material verification Environmental impact claims Circular economy support

  4. PEFC Programme for the Endorsement of Forest Certification Regional forest management standards Sustainable forest management claims International mutual recognition National scheme integration

  5. SBP-compliant Sustainable Biomass Partnership compliance Biomass sustainability verification Regional risk assessment integration Supply base evaluation compliance Biomass-specific claim requirements

  6. ISCC EU International Sustainability and Carbon Certification European Union renewable energy directive compliance Greenhouse gas emission reduction verification Sustainability criteria compliance Mass balance chain of custody

  7. RED II Renewable Energy Directive II compliance EU renewable energy sustainability requirements Greenhouse gas emission thresholds Land use change restrictions Sustainability governance requirements

26.1.4. Claim Scopes

  1. harvest Claims applicable to harvesting operations Forest management practice compliance Sustainable harvesting method verification Species-specific harvest practices Ecosystem impact assessments

  2. processing Manufacturing and processing compliance Processing facility certification Chemical treatment restrictions Processing efficiency requirements Quality management systems

  3. transport Supply chain transportation compliance Segregation maintenance during transport Chain of custody documentation Transport emission considerations Logistics sustainability practices

  4. full_chain Complete supply chain claim coverage End-to-end certification maintenance Comprehensive audit trail requirements Multi-stakeholder verification Complete chain of custody

26.1.5. Key Features

  1. Species-Specific Claims Individual species claim applications Multi-species claim distribution Species composition validation Biodiversity compliance verification Conservation impact tracking

  2. TRU Inheritance Tracking Parent TRU claim inheritance Split/merge claim distribution Processing chain claim continuity Chain of custody maintenance Audit trail preservation

  3. Percentage-Based Claims Partial certification content tracking Mixed source material claims Controlled wood component identification Claim percentage validation Mass balance calculations

  4. Validation and Verification Third-party validation support Evidence document linking Expiry date management Validation timestamp tracking Auditor accountability

26.1.6. Claim Inheritance Rules

  1. Split Operations Claims inherited by all child TRUs Percentage adjustments for volume changes Species-specific claim distribution Volume-weighted claim allocation Conservation of total certified volume

  2. Merge Operations Claims combined from parent TRUs Percentage recalculation for combined volume Species composition impact on claims Claim compatibility verification Mixed claim scenario handling

  3. Processing Operations Claim continuity through processing Processing-specific claim restrictions Equipment contamination considerations Segregation requirement compliance Processing facility certification requirements

26.1.7. Validation Rules

  1. TRU Integration traceableUnitId must reference existing TRU Claim must be compatible with TRU species composition Claim percentage must not exceed 100% Inheritance tracking must reference valid parent TRUs

  2. Certification Logic Claim type must be compatible with certification scheme Validation must be performed by authorized validator Evidence documents must support claim statement Expiry dates must be reasonable and future-dated

  3. Species Consistency applicableSpecies must be subset of TRU species composition Species-specific claims must sum to valid totals Multi-species claims must account for all species Species claim percentages must align with composition

26.1.8. Example Use Cases

  1. FSC Mix Inheritance Parent TRU with 70% FSC Mix claim Crosscutting operation creates 3 child TRUs Each child inherits 70% FSC Mix claim Volume distribution tracked for mass balance Chain of custody documentation maintained

  2. Multi-Species Claim Application Mixed species TRU with Douglas Fir and Pine FSC claim applies only to Douglas Fir component Species-specific claim percentage calculation Pine component tracked as controlled wood Overall claim percentage reflects species mix

  3. Processing Chain Claim Continuity Harvest site TRU with SBP-compliant claim Processing through felling, delimbing, crosscutting Claim maintained through each processing step Processing facility certification verified Final product maintains SBP compliance

26.1.9. Relationships

26.2. Supply Chain and Commerce Entities

26.2.1. ProductGroup

27. ProductGroup

27.1. ProductGroup

27.1.1. Overview

The ProductGroup object represents a distinct category of materials or products, classified based on shared characteristics such as origin, transformation method, and chain-of-custody rules. These groups support traceability, classification, and certification alignment in biomass and materials supply chains. The primary key is productGroupId.

27.1.2. Fields

Field Type Required Description Examples
productGroupId string Yes Unique identifier for the product group (primary key) PG-FS-BIOCHAR-001
productGroupName string Yes Commercial or descriptive name of the product group Forest Slash-Derived Biochar
productCategory string Yes High-level category of the product (enum) solid_biomass, liquid_biofuel, biogas
classification string No Industry or regulatory classification code ISO 17225-8, ISCC-EU-205
description string Yes Detailed description of the product group and its characteristics Forest Slash-Derived Biochar (Western U.S., Wildfire Mitigation)
typicalUses array<string> No Common applications and end-uses for products in this group ["Soil amendment", "Carbon sequestration"]
qualityStandards array<string> No Quality standards and specifications applicable to this group ["IBI Biochar Standards", "EBC Premium Grade"]
certificationRequirements array<string> No Required certification schemes for this product group ["FSC Controlled Wood", "SBP-compliant biomass"]
regulatoryClassification string No Regulatory status or classification "Biomass Byproduct - CAR Protocol"
relatedMaterials array<object> No Materials that belong to this product group See Material Object below
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/product-group/PG-001
lastUpdated string (date-time) No Timestamp of the most recent data update 2025-07-01T15:00:00Z

27.1.3. Material Object

Field Type Required Description
id string Yes ID of the material
@type string Yes Should equal Material

27.1.4. Example Use Cases

  1. Forest Slash-Derived Biochar Category: solid_biomass Uses: Soil amendment, carbon sequestration Standards: IBI Biochar Standards, EBC Premium Grade Certifications: FSC Controlled Wood, SBP-compliant biomass

  2. Refined Bio-oil Category: liquid_biofuel Uses: Transportation fuel, industrial heating Standards: EN 14214, ASTM D6751 Certifications: ISCC EU, RSB Global

27.1.5. Relationships

27.1.6. Transaction

28. Transaction

28.1. Transaction

28.1.1. Overview

The Transaction entity manages comprehensive business transactions within the BOOST traceability system. Transactions represent formal business agreements for the transfer of biomass materials, wood products, or energy feedstocks between organizations. This entity integrates financial management, regulatory compliance, supply chain traceability, risk management, and contract administration to support complete transaction lifecycle management across complex supply chain operations.

28.1.2. Fields

Field Type Required Description Examples
transactionId string Yes Unique identifier for the business transaction (primary key) TXN-001, TXN-PACIFIC-2024-001
OrganizationId string (FK) Yes Primary organization involved in transaction (seller/supplier) ORG-PACIFIC-FOREST-001, ORG-KLAMATH-HARVEST
CustomerId string (FK) Yes Customer organization (buyer) CUST-GREEN-ENERGY-CORP, CUST-PACIFIC-PAPER-MILLS
transactionDate string (date) Yes Date of business agreement 2024-03-15, 2024-07-22
SalesDeliveryDocumentId string (FK) No Foreign key to sales/delivery documentation SDD-PACIFIC-DELIVERY-2024-001, SDD-BIOMASS-SHIPMENT-789
contractValue number Yes Total monetary value of the transaction 125000.00, 2500000.50, 850000.00
contractCurrency string Yes Currency code for contract value (enum) USD, EUR, CAD, GBP
contractTerms string No Incoterms delivery conditions (enum) FOB, CIF, DDP, EXW, FCA
paymentTerms string No Payment conditions and timeline Net 30 days, 50% down, balance on delivery, Letter of credit
transactionStatus string Yes Current status of business transaction (enum) pending, confirmed, delivered, completed, cancelled
GeographicDataId string (FK) No Primary transaction location GEO-MILL-ENTRANCE-001, GEO-PORT-EXPORT-TERMINAL
BrokerOrganizationId string (FK) No Optional intermediary broker organization ORG-TIMBER-BROKER-PACIFIC, ORG-BIOMASS-TRADING-001
contractSignedDate string (date) No Date when contract was executed 2024-03-10, 2024-07-18
expectedDeliveryDate string (date) No Expected completion/delivery date 2024-04-15, 2024-08-30
complianceRequirements array<string> No Regulatory compliance requirements for transaction ["FSC_Chain_of_Custody", "LCFS_Reporting", "SBP_DTS_Registration"]
LcfsPathwayId string (FK) No CARB-certified pathway identifier for LCFS compliance CA-RD-001-Tier1-Bio, CA-ET-002-LookupTable
fuelVolume number No Volume of fuel in transaction for LCFS reporting 50000.0, 125000.5, 2500000.0
fuelVolumeUnit string No Unit of measurement for fuel volume (enum) gallons, liters, GGE
fuelCategory string No Category of fuel for LCFS classification (enum) renewable_diesel, ethanol, sustainable_aviation_fuel, biodiesel
reportingPeriod string No LCFS reporting quarter in YYYY-QN format 2024-Q1, 2024-Q3, 2025-Q2
regulatedPartyRole string No Role of regulated party in LCFS transaction (enum) producer, importer, blender, distributor
traceableUnitIds array<string> No TRUs included in this transaction ["TRU-LOG-001", "TRU-PILE-002", "TRU-BATCH-003"]
reconciliationStatus string No Transaction reconciliation status (enum) pending, resolved, disputed
trackingPointIds array<string> No Location trail references ["TP-HARVEST-001", "TP-FOREST-ROAD-002", "TP-MILL-ENTRANCE-003"]
speciesCompositionAtTransaction array<object> No Species breakdown at transaction time [{"species": "Douglas Fir", "percentage": 65.0}, {"species": "Hemlock", "percentage": 35.0}]
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/transaction/TXN-001

28.1.3. Transaction Status Workflow

  1. pending

    • Initial transaction creation and negotiation phase

    • Contract terms under discussion

    • Awaiting final approvals and signatures

    • No material transfer or payment processing

  2. confirmed

    • Contract signed and terms finalized

    • Transaction authorized for execution

    • Material preparation and logistics coordination

    • Payment processing initiated according to terms

  3. delivered

    • Materials physically delivered to customer

    • Delivery documentation completed and verified

    • Quality inspection and acceptance procedures

    • Awaiting final payment and transaction closure

  4. completed

    • All contract obligations fulfilled

    • Payment processed and received

    • Documentation finalized and archived

    • Transaction closed with full compliance

  5. cancelled

    • Transaction terminated before completion

    • Cancellation terms and penalties applied

    • Partial deliveries and payments reconciled

    • Documentation updated for audit trail

  6. disputed

    • Transaction issues under dispute resolution

    • Quality, quantity, or delivery discrepancies

    • Legal or arbitration proceedings active

    • Resolution pending with partial execution

28.1.4. Financial Terms Management

  1. Contract Value Structure

    • Base price per unit or total contract value

    • Currency specification and exchange rate handling

    • Price adjustments for quality variations

    • Volume-based pricing tiers and discounts

  2. Payment Terms

    • Payment schedule and milestone requirements

    • Down payment and progress payment structures

    • Payment methods and processing procedures

    • Late payment penalties and interest charges

  3. Risk Management

    • Force majeure clauses and conditions

    • Quality guarantees and performance bonds

    • Insurance requirements and coverage

    • Dispute resolution mechanisms and procedures

  4. Financial Controls

    • Credit limits and approval authorities

    • Payment security and collateral requirements

    • Multi-currency transaction management

    • Financial reporting and audit trail requirements

28.1.5. LCFS Compliance Integration

  1. Pathway Management

    • CARB-certified pathway identification and validation

    • Carbon intensity value assignment and tracking

    • Energy economy ratio calculations

    • Regulatory benchmark comparison and compliance

  2. Fuel Classification

    • Renewable fuel category determination

    • Advanced biofuel qualification assessment

    • Low carbon fuel standard compliance verification

    • California Air Resources Board reporting requirements

  3. Credit Calculations

    • LCFS credit generation calculations

    • Fuel volume and energy content verification

    • Lifecycle emission reductions quantification

    • Quarterly reporting aggregation and submission

  4. Regulated Party Compliance

    • Producer, importer, blender role identification

    • Compliance obligation calculation and tracking

    • Credit trading and banking system integration

    • Annual compliance demonstration requirements

28.1.6. Supply Chain Integration

  1. TRU Traceability

    • Complete traceable unit inclusion and tracking

    • Species composition documentation and verification

    • Processing history and transformation tracking

    • Quality specifications and grade compliance

  2. Tracking Point Coordination

    • Multi-point location tracking and verification

    • Chain of custody maintenance across locations

    • Media-interruption-free tracking validation

    • Geographic verification and compliance

  3. Processing Integration

    • Material processing coordination and scheduling

    • Quality control and specification compliance

    • Volume reconciliation and measurement validation

    • Processing facility integration and coordination

  4. Documentation Management

    • Sales and delivery document coordination

    • Certificate and compliance documentation

    • Audit trail maintenance and verification

    • Regulatory reporting and submission coordination

28.1.7. Example Use Cases

  1. Renewable Diesel Feedstock Transaction

    • Transaction: Large-scale used cooking oil supply contract

    • LCFS Compliance: Tier 1 pathway with verified carbon intensity

    • Financial Terms: $2.5M contract with quarterly deliveries

    • Traceability: Complete supply chain documentation from collection to processing

    • Compliance: CARB LCFS reporting with verified sustainability claims

  2. Export Lumber Transaction

    • Transaction: Container shipment of certified lumber to international customer

    • Certification: FSC Chain of Custody with species-specific claims

    • Financial Terms: Letter of credit with FOB shipping terms

    • Traceability: Individual log tracking from forest to port

    • Compliance: Phytosanitary certification and export documentation

  3. Biomass Energy Supply Agreement

    • Transaction: Long-term biomass fuel supply contract

    • SBP Compliance: Sustainable biomass partnership verification

    • Financial Terms: Multi-year agreement with price escalation clauses

    • Traceability: Supply base reporting and mass balance tracking

    • Compliance: Regional risk assessment and mitigation measures

28.1.8. Validation Rules

  1. Transaction Requirements

    • transactionId must be unique across system

    • OrganizationId and CustomerId must reference valid entities

    • contractValue must be positive number

    • transactionStatus must follow valid workflow progression

  2. Financial Consistency

    • contractCurrency must be supported currency code

    • Payment terms must be realistic and enforceable

    • Contract value must align with material quantities and market rates

    • Financial terms must comply with applicable regulations

  3. LCFS Integration

    • LcfsPathwayId must reference valid CARB-certified pathway

    • Fuel category must align with pathway feedstock specifications

    • Fuel volume must be consistent with TRU quantities

    • Reporting period must be current or future quarter

  4. Supply Chain Consistency

    • traceableUnitIds must reference valid TRUs available for transaction

    • trackingPointIds must represent logical supply chain progression

    • Species composition must align with TRU species data

    • Geographic locations must be consistent with operational areas

28.1.9. Relationships

28.1.10. TransactionBatch

29. TransactionBatch

29.1. TransactionBatch

29.1.1. Overview

The TransactionBatch entity manages physical material batches within business transactions in the BOOST traceability system. Transaction batches represent specific, physically aggregated quantities of materials that are prepared, transported, and delivered as cohesive units within larger commercial transactions. This entity provides detailed tracking of material composition, quality characteristics, transportation logistics, certification validation, and complete traceability across the physical supply chain from preparation through final delivery.

29.1.2. Fields

Field Type Required Description Examples
transactionBatchId string Yes Unique identifier for the physical material batch (primary key) TB-001, TB-PACIFIC-2024-SHIPMENT-001
transactionId string (FK) Yes Foreign key to parent business transaction TXN-PACIFIC-2024-001, TXN-BIOMASS-EXPORT-789
productionBatchId string (FK) No Foreign key to source production batch PB-MILL-2024-Q1-001, PB-HARVEST-SPRING-123
quantity number Yes Physical quantity of material in this batch 1250.5, 25000.0, 500.75
quantityUnit string Yes Unit of measurement for quantity (enum) cubic_meters, metric_tons, board_feet, cord, green_tons
traceableUnitIds array<string> Yes Array of TRU IDs included in this batch ["TRU-LOG-001", "TRU-PILE-002", "TRU-BATCH-003"]
claimId string (FK) No Foreign key to primary sustainability claim CLAIM-FSC-MIX-75, CLAIM-SBP-COMPLIANT
additionalClaimIds array<string> No Array of secondary claim IDs ["CLAIM-PEFC-CERTIFIED", "CLAIM-SFI-SOURCING"]
speciesComposition array<object> No Species breakdown with percentages and volumes [{"species": "Douglas Fir", "percentage": 65.0, "volume": 812.8}, {"species": "Hemlock", "percentage": 35.0, "volume": 437.7}]
qualityGrade string No Overall quality grade for the batch (enum) Grade_A, Structural, Sawlog, Fuel, Mixed
processingHistoryIds array<string> No Array of processing history record IDs ["PH-SAWMILL-001", "PH-PLANER-002", "PH-KILN-003"]
reconciliationStatus string No Status of volume/quality reconciliation (enum) pending, in_progress, resolved, disputed, escalated
trackingHistory string No Complete location trail summary Harvest Site A → Skid Road 101 → Forest Road Main → Mill Yard → Loading Dock
measurementRecordIds array<string> No Array of measurement record IDs ["MR-SCALE-001", "MR-MOISTURE-002", "MR-GRADE-003"]
mediaBreakDetected boolean No Flag indicating if traceability continuity was broken false, true
batchStatus string Yes Current status of the physical batch (enum) prepared, in_transit, delivered, accepted, rejected
batchCreatedDate string (datetime) No When the batch was prepared/created 2024-03-15T08:30:00Z, 2024-07-22T14:45:00Z
deliveryDate string (datetime) No Actual delivery timestamp 2024-03-18T11:15:00Z, 2024-07-25T09:30:00Z
deliveryGeographicDataId string (FK) No Foreign key to delivery location GEO-MILL-ENTRANCE-001, GEO-PORT-TERMINAL-EAST
qualityMetrics object No Detailed quality assessment metrics {"moistureContent": 12.5, "density": 450.0, "defectRate": 2.1, "contaminationLevel": "minimal"}
plantPartComposition object No Plant part composition breakdown {"trunk": {"volume": 1000.0, "percentage": 85.0}, "branches": {"volume": 150.0, "percentage": 12.0}}
transportationData object No Transportation and logistics information {"carrierOrganizationId": "CARRIER-001", "transportMethod": "truck", "vehicleId": "TRUCK-789"}
certificationValidation object No Certification and compliance validation data {"certificateIds": ["CERT-FSC-001"], "validationRequired": true, "validationCompleted": true}
lastUpdated string (datetime) No Timestamp of last modification 2024-03-20T16:45:00Z, 2024-07-28T10:30:00Z
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/transaction-batch/TB-001

29.1.3. Batch Status Workflow

  1. prepared

    • Batch assembled and ready for shipment

    • Quality assessment completed and documented

    • All TRUs allocated and consolidated

    • Transportation arrangements finalized

  2. in_transit

    • Batch loaded and en route to destination

    • Transportation tracking active

    • Chain of custody maintained during transport

    • Estimated arrival time being monitored

  3. delivered

    • Physical arrival at destination location

    • Delivery documentation completed

    • Initial receipt confirmation obtained

    • Awaiting quality inspection and acceptance

  4. accepted

    • Quality inspection completed successfully

    • Batch accepted by receiving party

    • Final documentation and certificates validated

    • Batch integration into recipient’s inventory

  5. rejected

    • Quality inspection failed or non-conforming

    • Batch refused by receiving party

    • Return logistics or rework arrangements required

    • Documentation updated with rejection reasons

  6. partially_delivered

    • Partial delivery due to transportation constraints

    • Remaining materials scheduled for follow-up delivery

    • Partial acceptance and payment processing

    • Split batch tracking and reconciliation

29.1.4. Quality Metrics Components

  1. Physical Properties

    • moistureContent: Moisture percentage (0-100%)

    • density: Material density in kg/m³

    • defectRate: Percentage of defective material (0-100%)

    • contaminationLevel: Contamination assessment (none, minimal, moderate, significant, unacceptable)

  2. Assessment Methods

    • gradingMethod: Grading technique (visual, mechanical, optical, combination)

    • qualityAssessmentDate: When assessment was performed

    • assessorId: Qualified assessor identification

    • gradingStandards: Applicable quality standards and specifications

  3. Performance Indicators

    • Conformance to customer specifications

    • Market grade equivalency and value

    • Processing suitability and efficiency

    • End-use application compatibility

29.1.5. Plant Part Composition Structure

  1. Wood Components

    • trunk: Main stem portion with volume and percentage

    • branches: Branch material inclusion

    • bark: Bark content and separation

    • heartwood/sapwood: Wood type differentiation

  2. Biomass Components

    • leaves/needles: Foliage content for energy applications

    • twigs: Small branch and twig material

    • seeds/nuts/cones: Reproductive material content

    • stalks/straw: Agricultural residue components

  3. Processing Residues

    • husks/hulls: Processing by-product inclusion

    • chaff: Fine material and particle content

    • stubble: Field residue components

    • sawdust: Mill residue integration

29.1.6. Transportation Data Management

  1. Carrier Information

    • carrierOrganizationId: Transportation company identification

    • vehicleId: Specific vehicle or container identification

    • driverOperatorId: Personnel responsible for transport

    • transportMethod: Mode of transportation (truck, rail, ship, barge)

  2. Logistics Coordination

    • pickupDate: Scheduled and actual pickup times

    • estimatedArrival: Projected delivery schedule

    • routeOptimization: Route selection criteria and efficiency

    • transitTime: Duration and schedule performance

  3. Transportation Compliance

    • Weight and dimension regulations

    • Hazardous materials handling requirements

    • International shipping documentation

    • Insurance and liability coverage

29.1.7. Certification Validation Process

  1. Certificate Verification

    • certificateIds: Applicable certification references

    • validationRequired: Compliance verification necessity

    • validationCompleted: Verification completion status

    • validationDate: When verification was performed

  2. Compliance Assessment

    • validatorId: Qualified validator identification

    • validationNotes: Detailed verification findings

    • Chain of custody validation

    • Sustainability claim verification

  3. Documentation Management

    • Certificate authenticity verification

    • Expiration date and renewal tracking

    • Audit trail maintenance

    • Third-party verification coordination

29.1.8. Reconciliation Status Management

  1. pending

    • Initial batch creation with preliminary measurements

    • Awaiting final quality assessment and validation

    • Documentation compilation in progress

    • Quantity and quality verification pending

  2. in_progress

    • Active reconciliation process underway

    • Measurements being verified and cross-checked

    • Quality assessments being completed

    • Documentation review and validation ongoing

  3. resolved

    • All measurements and quality assessments completed

    • Documentation validated and approved

    • Quantity and quality reconciliation successful

    • Batch ready for final delivery and acceptance

  4. disputed

    • Measurement or quality discrepancies identified

    • Customer or supplier disagreement on specifications

    • Resolution process initiated with stakeholders

    • Additional verification or rework may be required

  5. escalated

    • Dispute resolution unsuccessful at operational level

    • Management or legal intervention required

    • Third-party arbitration or mediation initiated

    • Contract terms and penalties under review

29.1.9. Traceability Integration

  1. TRU Aggregation

    • Complete tracking of all constituent TRUs

    • Maintenance of individual TRU identity within batch

    • Species composition aggregation and validation

    • Processing history consolidation across TRUs

  2. Chain of Custody Maintenance

    • Unbroken traceability from source to delivery

    • Documentation of all custody transfers

    • Geographic tracking and location verification

    • Media break detection and remediation

  3. Processing History Integration

    • Consolidation of processing records across TRUs

    • Value-added processing documentation

    • Quality transformation tracking

    • Certification maintenance through processing

29.1.10. Example Use Cases

  1. Lumber Export Shipment

    • Transaction Batch: Container load of FSC-certified Douglas Fir lumber

    • Quantity: 45 cubic meters of Grade A structural lumber

    • Composition: 100% Douglas Fir from certified forest management unit

    • Quality: Kiln-dried to 12% moisture, mechanically graded

    • Transportation: Truck transport to port, container loading

    • Certification: FSC Chain of Custody validation completed

  2. Biomass Fuel Delivery

    • Transaction Batch: Truck load of SBP-compliant wood chips

    • Quantity: 25 metric tons green weight biomass fuel

    • Composition: Mixed species (60% hardwood, 40% softwood)

    • Quality: <50% moisture content, minimal contamination

    • Transportation: Direct delivery from processing facility

    • Certification: SBP sustainability verification completed

  3. Multi-Species Log Load

    • Transaction Batch: Logging truck load from selective harvest

    • Quantity: 40 cubic meters mixed species sawlogs

    • Composition: Douglas Fir (50%), Hemlock (30%), Cedar (20%)

    • Quality: Grade B sawlogs with visual grading assessment

    • Transportation: Forest road to mill yard delivery

    • Certification: Multiple certificate validation for species mix

29.1.11. Validation Rules

  1. Batch Requirements

    • transactionBatchId must be unique across system

    • transactionId must reference valid Transaction entity

    • quantity must be positive number greater than zero

    • quantityUnit must be appropriate for material type

  2. TRU Integration

    • traceableUnitIds must reference valid existing TRUs

    • All TRUs must be available for batch allocation

    • TRU species composition must align with batch species data

    • TRU processing history must be consistent with batch claims

  3. Quality Consistency

    • qualityGrade must align with quality metrics assessment

    • Species composition percentages must sum to 100%

    • Plant part composition percentages must sum to 100%

    • Quality assessment date must be within reasonable timeframe

  4. Transportation Validation

    • carrierOrganizationId must reference valid Organization

    • Transport method must be appropriate for material type

    • Pickup and delivery dates must be logically sequenced

    • Route optimization must align with transportation method

  5. Certification Compliance

    • Certificate IDs must reference valid active certificates

    • Validation requirements must be met before delivery

    • Certification scope must cover all materials in batch

    • Validator must be qualified for certification scheme

29.1.12. Relationships

29.1.13. SalesDeliveryDocument

30. SalesDeliveryDocument

30.1. SalesDeliveryDocument

30.1.1. Overview

The SalesDeliveryDocument entity manages sales and delivery documentation for business transactions within the BOOST traceability system. These documents serve as formal records of material transfers, providing essential transaction details, party information, and product specifications. This entity supports transaction documentation, delivery verification, and compliance record-keeping for supply chain operations.

30.1.2. Fields

Field Type Required Description Examples
documentId string Yes Unique identifier for the sales delivery document (primary key) SDD-001, SDD-PACIFIC-DELIVERY-2024-001
dateIssued string (date) Yes Date when the document was issued 2024-03-15, 2024-07-22
buyerName string Yes Name of the purchasing organization Pacific Paper Mills LLC, Green Energy Corporation
buyerAddress string No Address of the purchasing organization 123 Industrial Way, Portland, OR 97201, 456 Mill Road, Sacramento, CA 95814
sellerName string Yes Name of the selling organization Klamath Forest Products, Pacific Timber Harvesters LLC
sellerAddress string No Address of the selling organization 789 Forest Road, Klamath Falls, OR 97601, 321 Logging Way, Eureka, CA 95501
productDescription string Yes Detailed description of the products being delivered Douglas Fir sawlogs, Grade A, 24-foot lengths, Mixed hardwood chips, moisture content 15%
quantity number Yes Quantity of product being delivered 125.5, 2500.0, 1850.75
transactionId string (FK) No Foreign key reference to associated transaction TXN-PACIFIC-2024-001, TXN-BIOMASS-DELIVERY-789
certificateCode string No Certification code applicable to the delivered products FSC-C123456, SFI-SFIS-COC-123456, SBP-DTS-001
transportReference string No Transportation reference or tracking number TRUCK-001-20240315, RAIL-CAR-ABC123, CONTAINER-HLXU1234567
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/sales-delivery-document/SDD-001

30.1.3. Document Types

  1. Sales Invoice

    • Primary commercial document for completed transactions

    • Includes pricing, payment terms, and financial details

    • Legal document for accounting and tax purposes

    • Links to purchase orders and delivery confirmations

  2. Delivery Receipt

    • Proof of material delivery and acceptance

    • Includes quantity verification and quality confirmation

    • Signed acknowledgment by receiving party

    • Critical for chain of custody documentation

  3. Bill of Lading

    • Transportation document for shipped materials

    • Includes carrier information and transportation details

    • Legal document for cargo responsibility transfer

    • Required for interstate and international shipments

  4. Packing List

    • Detailed inventory of shipped materials

    • Includes individual TRU references and specifications

    • Quality grades, species composition, and certifications

    • Support document for delivery verification

30.1.4. Key Features

  1. Transaction Documentation

    • Complete transaction record keeping

    • Buyer and seller information management

    • Product specification and quantity tracking

    • Payment and delivery term documentation

  2. Certification Integration

    • Certificate code tracking and validation

    • Chain of custody documentation support

    • Sustainability claim transfer documentation

    • Third-party certification compliance

  3. Transportation Coordination

    • Transport reference and tracking integration

    • Delivery scheduling and coordination support

    • Multi-modal transportation documentation

    • Logistics and routing optimization

  4. Compliance Support

    • Regulatory documentation requirements

    • Audit trail and record keeping

    • Tax and customs documentation support

    • Legal document archival and retrieval

30.1.5. Product Description Guidelines

  1. Species Information

    • Common and scientific species names

    • Species composition percentages for mixed materials

    • Grade classifications and quality specifications

    • Processing stage and product form

  2. Quantity Specifications

    • Volume measurements in cubic meters

    • Weight measurements in metric tons

    • Piece counts for individual logs or products

    • Unit conversion factors and calculations

  3. Quality Parameters

    • Moisture content percentages

    • Grade classifications (A, B, C, etc.)

    • Defect descriptions and tolerances

    • Processing specifications and requirements

  4. Certification Status

    • Applicable certification schemes

    • Percentage-based claims (FSC Mix 70%)

    • Certificate numbers and validity periods

    • Chain of custody claim statements

30.1.6. Example Use Cases

  1. Sawlog Delivery Documentation

    • Document Type: Bill of Lading + Delivery Receipt

    • Product: Douglas Fir and Hemlock sawlogs

    • Quantity: 125.5 cubic meters

    • Certification: FSC Mix 75% with certificate FSC-C123456

    • Transportation: Logging truck with GPS tracking

  2. Biomass Fuel Delivery

    • Document Type: Sales Invoice + Packing List

    • Product: Wood chips for biomass power plant

    • Quantity: 2,500 metric tons (dry weight basis)

    • Certification: SBP-compliant biomass

    • Transportation: Rail car shipment with moisture monitoring

  3. Export Documentation

    • Document Type: Commercial Invoice + Export Certificate

    • Product: Lumber products for international export

    • Quantity: Container load with detailed inventory

    • Certification: PEFC certified with phytosanitary certificate

    • Transportation: Container shipping with customs documentation

30.1.7. Validation Rules

  1. Document Requirements

    • documentId must be unique across system

    • dateIssued must be valid date format

    • buyerName and sellerName must be non-empty

    • productDescription must provide adequate detail

    • quantity must be positive number

  2. Transaction Integration

    • transactionId must reference valid Transaction if provided

    • Document details must be consistent with transaction terms

    • Delivery dates must align with transaction timeline

    • Parties must match transaction buyer and seller

  3. Certification Consistency

    • certificateCode must be valid format if provided

    • Certificate must be active and applicable to products

    • Chain of custody claims must be supported by documentation

    • Certification scope must cover described products

30.1.8. Relationships

30.1.9. Customer

31. Customer

31.1. Customer

31.1.1. Overview

The Customer entity represents buyer organizations in the BOOST traceability system. Customers are organizations that purchase biomass materials, wood products, or other materials tracked through the supply chain. This entity supports transaction management, delivery coordination, and supply chain relationship tracking by providing essential customer information and geographic location data.

31.1.2. Fields

Field Type Required Description Examples
customerId string Yes Unique identifier for the customer (primary key) CUST-001, CUST-PACIFIC-MILLS
customerName string Yes Legal name of the customer organization Pacific Paper Mills LLC, Green Energy Corporation
address string No Physical address of the customer 123 Industrial Way, Portland, OR 97201, 456 Mill Road, Sacramento, CA 95814
GeographicDataId string (FK) No Foreign key to customer’s geographic location GEO-CUSTOMER-PACIFIC-001, GEO-MILL-DELIVERY-SITE
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/customer/CUST-001

31.1.3. Key Features

  1. Transaction Integration

    • Direct integration with Transaction entities as buyers

    • Support for multiple concurrent transactions

    • Purchase order and contract management

    • Payment terms and financial relationship tracking

  2. Delivery Coordination

    • Geographic location management for deliveries

    • Multiple delivery site support through GeographicData

    • Logistics and transportation coordination

    • Delivery documentation and tracking

  3. Supply Chain Relationships

    • Multi-vendor relationship management

    • Supplier performance and quality tracking

    • Contract negotiation and management

    • Long-term partnership establishment

  4. Geographic Integration

    • Precise location data for delivery planning

    • Multi-site customer management

    • Regional market analysis support

    • Transportation cost optimization

31.1.4. Customer Categories

  1. Manufacturing Customers

    • Paper mills and pulp facilities

    • Sawmills and lumber processors

    • Engineered wood product manufacturers

    • Furniture and construction companies

  2. Energy Customers

    • Biomass power plants

    • Biorefinery facilities

    • Pellet manufacturing plants

    • Renewable energy producers

  3. Trading Organizations

    • Commodity trading companies

    • Biomass brokers and distributors

    • Export/import organizations

    • Market intermediaries

  4. End-Use Industries

    • Construction companies

    • Packaging manufacturers

    • Chemical industry consumers

    • Agricultural operations

31.1.5. Example Use Cases

  1. Paper Mill Customer

    • Customer: Large integrated paper manufacturing facility

    • Multiple delivery locations across processing facilities

    • Regular bulk purchases with long-term contracts

    • Quality specifications for fiber content and species

  2. Biomass Energy Customer

    • Customer: Renewable energy power plant

    • Consistent fuel supply requirements

    • LCFS compliance and carbon intensity tracking

    • Seasonal demand variations and storage coordination

  3. Export Customer

    • Customer: International trading organization

    • Port delivery locations with container coordination

    • Species-specific export requirements

    • Certification compliance for international markets

31.1.6. Validation Rules

  1. Identity Requirements

    • customerId must be unique across system

    • customerName must be non-empty string

    • customerId must follow pattern ^CUST-[A-Z0-9-_]+$

  2. Geographic Consistency

    • GeographicDataId must reference valid GeographicData entity

    • Address should be consistent with geographic location

    • Multiple delivery sites supported through GeographicData

  3. Transaction Integration

    • Customer must be referenceable by Transaction entities

    • Customer information must be current for active transactions

    • Contact information must be maintained for business operations

31.1.7. Relationships

31.1.8. Supplier

32. Supplier

32.1. Supplier

32.1.1. Overview

The Supplier entity represents organizations that provide biomass materials, wood products, and related materials in the BOOST traceability system. Suppliers are critical supply chain participants who harvest, process, or distribute materials to other organizations. This entity supports certification management, claim tracking, and supply chain relationship coordination with comprehensive supplier information and capability tracking.

32.1.2. Fields

Field Type Required Description Examples
supplierId string Yes Unique identifier for the supplier (primary key) SUPP-001, SUPP-KLAMATH-FOREST-CO
supplierName string Yes Legal name of the supplier organization Klamath Forest Products, Pacific Timber Harvesters LLC
address string No Physical address of the supplier 789 Forest Road, Klamath Falls, OR 97601, 321 Logging Way, Eureka, CA 95501
certificateCode string No Primary certification code for the supplier FSC-C123456, SFI-SFIS-COC-123456, PEFC/05-33-123
claim string No Primary sustainability claim offered by supplier FSC Mix 70%, SBP-compliant biomass, PEFC Certified
supplierType string No Classification of supplier operations harvester, processor, trader, integrated, contractor
GeographicDataId string (FK) No Foreign key to supplier’s geographic location GEO-SUPPLIER-KLAMATH-001, GEO-HARVEST-BASE-PACIFIC
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/supplier/SUPP-001

32.1.3. Supplier Types

  1. harvester

    • Forest harvesting and timber extraction operations

    • Primary material production from standing forests

    • Logging contractors and forest management companies

    • Initial TRU creation and biometric identification

  2. processor

    • Manufacturing and material transformation operations

    • Sawmills, pulp mills, and processing facilities

    • Value-added processing and product manufacturing

    • TRU transformation and split/merge operations

  3. trader

    • Material trading and distribution organizations

    • Commodity brokers and market intermediaries

    • Import/export operations and logistics coordination

    • Supply chain optimization and market access

  4. integrated

    • Vertically integrated operations across multiple stages

    • Combined harvesting, processing, and distribution

    • End-to-end supply chain management

    • Complex organizational structures with multiple facilities

  5. contractor

    • Service providers and specialized contractors

    • Equipment operation and maintenance services

    • Specialized processing or transportation services

    • Support services for primary operations

32.1.4. Key Features

  1. Certification Management

    • Primary certification tracking and validation

    • Multiple certification scheme support

    • Certificate expiry monitoring and renewal tracking

    • Audit and compliance history management

  2. Claim Verification

    • Sustainability claim documentation and validation

    • Species-specific claim management

    • Chain of custody claim inheritance

    • Third-party verification support

  3. Supply Chain Integration

    • Multi-customer relationship management

    • Transaction history and performance tracking

    • Quality specifications and delivery capabilities

    • Long-term contract and partnership management

  4. Geographic Operations

    • Primary operation location management

    • Multi-site operational capability tracking

    • Regional market coverage and access

    • Transportation and logistics coordination

32.1.5. Certification Examples

  1. Forest Stewardship Council (FSC)

    • Certificate Code: FSC-C123456

    • Claims: FSC 100%, FSC Mix 70%, FSC Recycled

    • Chain of custody and forest management certifications

    • Species-specific and percentage-based claims

  2. Sustainable Forestry Initiative (SFI)

    • Certificate Code: SFI-SFIS-COC-123456

    • Claims: SFI Certified Sourcing, SFI Chain of Custody

    • Fiber sourcing and chain of custody standards

    • Regional sustainable forestry practices

  3. Programme for the Endorsement of Forest Certification (PEFC)

    • Certificate Code: PEFC/05-33-123

    • Claims: PEFC Certified, PEFC Controlled Sources

    • International mutual recognition system

    • National scheme integration and compliance

32.1.6. Example Use Cases

  1. Integrated Forest Products Supplier

    • Supplier Type: integrated

    • Operations: Combined harvesting and processing

    • Certifications: FSC Forest Management + Chain of Custody

    • Claims: FSC Mix 85% for both harvested and processed materials

    • Geographic coverage: Multiple forest areas and processing facilities

  2. Specialized Biomass Harvester

    • Supplier Type: harvester

    • Operations: Forest residue collection and preparation

    • Certifications: SBP Data Transfer System registration

    • Claims: SBP-compliant biomass from sustainably managed forests

    • Focus: Biomass fuel supply for renewable energy markets

  3. Regional Timber Trader

    • Supplier Type: trader

    • Operations: Regional timber marketing and distribution

    • Certifications: FSC Chain of Custody for trading

    • Claims: Variable based on source suppliers

    • Services: Market access and logistics coordination for small suppliers

32.1.7. Validation Rules

  1. Identity Requirements

    • supplierId must be unique across system

    • supplierName must be non-empty string

    • supplierId must follow established pattern conventions

  2. Certification Consistency

    • certificateCode must be valid format for certification scheme

    • claim must be consistent with certificate authority and scope

    • Certification expiry dates must be monitored and maintained

  3. Operational Validity

    • supplierType must align with actual operational capabilities

    • Geographic location must be consistent with service areas

    • Claims must be supported by valid certification documentation

32.1.8. Relationships

32.1.9. SupplyBase

33. SupplyBase

33.1. SupplyBase

33.1.1. Overview

The SupplyBase entity manages geographic and operational areas for biomass supply operations within the BOOST traceability system. Supply bases represent coordinated geographic regions where organizations conduct harvesting, processing, and material collection activities. This entity supports area-based management, equipment deployment coordination, species availability tracking, and comprehensive supply chain planning across defined operational boundaries.

33.1.2. Fields

Field Type Required Description Examples
supplyBaseId string Yes Unique identifier for the supply base (primary key) SB-001, SB-KLAMATH-FOREST-REGION
OrganizationId string (FK) Yes Foreign key to managing organization ORG-PACIFIC-FOREST-001, ORG-KLAMATH-HARVEST
supplyBaseName string Yes Descriptive name of the supply base area Klamath National Forest Region, Pacific Northwest Operations
description string Yes Detailed description of supply base operations and scope Sustainable forest management operations across 50,000 acres of mixed conifer forests
harvestSites array<string> No Array of harvest site identifiers within supply base ["GEO-HARVEST-001", "GEO-HARVEST-002", "GEO-HARVEST-003"]
skidRoads array<string> No Array of skid road infrastructure identifiers ["GEO-SKID-ROAD-A", "GEO-SKID-ROAD-B", "GEO-SKID-ROAD-C"]
forestRoads array<string> No Array of forest road infrastructure identifiers ["GEO-FOREST-ROAD-101", "GEO-FOREST-ROAD-102"]
equipmentDeployment array<string> No Array of equipment deployed across supply base ["EQ-HARVESTER-001", "EQ-FORWARDER-002", "EQ-LOADER-003"]
traceableUnitIds array<string> No Array of TRUs originating from this supply base ["TRU-LOG-001", "TRU-PILE-002", "TRU-BATCH-003"]
speciesAvailable array<string> No Array of species available within supply base ["Douglas Fir", "Ponderosa Pine", "Western Hemlock", "Incense Cedar"]
GeographicDataId string (FK) No Foreign key to primary geographic boundary of supply base GEO-SUPPLY-BASE-KLAMATH-001, GEO-REGION-PACIFIC-NW
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/supply-base/SB-001

33.1.3. Supply Base Types

  1. Forest Management Area

    • Comprehensive forest management operations

    • Multiple harvest sites with coordinated planning

    • Long-term sustainable forestry practices

    • Integration with forest management plans

  2. Biomass Collection Region

    • Specialized biomass and residue collection

    • Coordination with timber harvesting operations

    • Focus on energy and biofuel feedstock supply

    • Integration with processing facility requirements

  3. Multi-Owner Cooperative Area

    • Coordination across multiple land ownerships

    • Shared infrastructure and equipment utilization

    • Collaborative harvesting and transportation

    • Economies of scale for small landowners

  4. Processing Facility Supply Zone

    • Geographic area supplying specific processing facilities

    • Optimized transportation and logistics coordination

    • Species and quality specifications alignment

    • Just-in-time inventory management

33.1.4. Key Features

  1. Geographic Coordination

    • Area-based planning and management

    • Infrastructure development and maintenance

    • Transportation route optimization

    • Environmental compliance coordination

  2. Equipment Management

    • Coordinated equipment deployment across area

    • Maintenance scheduling and resource sharing

    • Equipment utilization optimization

    • Multi-site operational efficiency

  3. Species Management

    • Species availability tracking and planning

    • Biodiversity conservation coordination

    • Market demand alignment with species availability

    • Sustainable harvesting level management

  4. TRU Coordination

    • Central tracking of all TRUs from supply base

    • Quality management across multiple sites

    • Processing coordination and scheduling

    • Supply chain optimization within area

33.1.5. Infrastructure Components

  1. Harvest Sites

    • Active timber harvesting locations

    • GPS coordinates and boundary definitions

    • Species composition and volume estimates

    • Access road and equipment requirements

  2. Skid Roads

    • Primary extraction routes from harvest sites

    • Load capacity and equipment compatibility

    • Maintenance requirements and seasonal access

    • Integration with forest road network

  3. Forest Roads

    • Main transportation arteries within supply base

    • Connection to public road systems

    • Multi-use coordination with other forest users

    • Long-term infrastructure maintenance planning

  4. Storage and Staging Areas

    • Temporary material storage locations

    • Equipment parking and maintenance areas

    • Material sorting and quality assessment sites

    • Weather protection and security facilities

33.1.6. Management Coordination

  1. Operational Planning

    • Seasonal harvesting schedule coordination

    • Equipment deployment and utilization planning

    • Material flow optimization across sites

    • Workforce coordination and safety management

  2. Environmental Compliance

    • Regulatory compliance across entire supply base

    • Environmental impact assessment coordination

    • Water quality protection and monitoring

    • Wildlife habitat conservation management

  3. Quality Management

    • Consistent quality standards across all sites

    • Species identification and grading protocols

    • Processing specifications and requirements

    • Customer specification compliance

  4. Economic Optimization

    • Cost minimization through coordinated operations

    • Transportation efficiency and logistics optimization

    • Shared infrastructure utilization

    • Market price optimization and timing

33.1.7. Example Use Cases

  1. Integrated Forest Management Supply Base

    • Supply Base: 75,000-acre managed forest region

    • Organization: Large integrated forest products company

    • Operations: Multiple harvest sites with coordinated planning

    • Infrastructure: Comprehensive road network and equipment fleet

    • Species: Mixed conifer forest with Douglas Fir, Pine, and Hemlock

  2. Biomass Collection Cooperative

    • Supply Base: Regional biomass collection network

    • Organization: Biomass producer cooperative

    • Operations: Coordinated residue collection from multiple timber operations

    • Infrastructure: Shared equipment and transportation coordination

    • Species: Mixed species biomass for energy production

  3. Small Landowner Aggregation Area

    • Supply Base: Multiple small private forest ownerships

    • Organization: Forest management service company

    • Operations: Coordinated harvesting across fragmented ownership

    • Infrastructure: Shared access roads and equipment services

    • Species: Variable species composition based on site conditions

33.1.8. Validation Rules

  1. Identity Requirements

    • supplyBaseId must be unique across system

    • OrganizationId must reference valid Organization

    • supplyBaseName and description must be non-empty

    • Geographic boundaries must be clearly defined

  2. Infrastructure Consistency

    • harvestSites must reference valid GeographicData locations

    • Infrastructure elements must be within supply base boundaries

    • Equipment deployment must be appropriate for terrain and operations

    • Transportation networks must be logically connected

  3. Species and TRU Management

    • speciesAvailable must reflect actual forest composition

    • traceableUnitIds must reference TRUs created within supply base

    • Species claims must be supported by forest inventory data

    • TRU origins must be traceable to specific harvest sites

33.1.9. Relationships

33.1.10. SupplyBaseReport

34. SupplyBaseReport

34.1. SupplyBaseReport

34.1.1. Overview

The SupplyBaseReport entity manages sustainability reporting documentation for supply base operations within the BOOST traceability system. Supply Base Reports are comprehensive documents that detail sustainability practices, environmental management, social considerations, and operational performance across defined supply base areas. This entity supports regulatory compliance, certification requirements, stakeholder communication, and continuous improvement tracking for sustainable forest management operations.

34.1.2. Fields

Field Type Required Description Examples
sbrId string Yes Unique identifier for the supply base report (primary key) SBR-001, SBR-KLAMATH-2024-ANNUAL
organizationId string (FK) Yes Foreign key to organization preparing the report ORG-PACIFIC-FOREST-001, ORG-KLAMATH-HARVEST
preparationDate string (date) Yes Date when the report was prepared or finalized 2024-03-31, 2024-12-31
supplyBaseSummary string No Executive summary of supply base operations and performance Annual report covering 75,000 acres of sustainably managed forest operations
sourcingPractices string No Description of sourcing practices and methodologies Selective harvesting with ecosystem-based management principles
sustainabilityMeasures string No Summary of sustainability measures and performance indicators Biodiversity conservation, water quality protection, carbon sequestration
publicationUrl string (uri) No URL where the complete report is publicly accessible https://reports.company.com/supply-base/SBR-KLAMATH-2024.pdf
reportGeographicDataId string (FK) No Foreign key to geographic area covered by report GEO-SUPPLY-BASE-KLAMATH-001, GEO-REGION-PACIFIC-NW
supplyBaseIds array<string> No Array of supply base identifiers covered by this report ["SB-KLAMATH-FOREST", "SB-CASCADE-REGION", "SB-OLYMPIC-UNIT"]
reportingPeriod string No Time period covered by the report 2024 Annual Report, Q1-Q3 2024, January 1 - December 31, 2024
certificationCompliance array<string> No Certification schemes addressed in the report ["FSC Forest Management", "SFI Forest Management", "PEFC Sustainable Forest Management"]
stakeholderEngagement string No Summary of stakeholder consultation and engagement activities Community meetings, indigenous consultation, environmental group engagement
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/supply-base-report/SBR-001

34.1.3. Report Types

  1. Annual Sustainability Report

    • Comprehensive yearly performance assessment

    • Financial, environmental, and social performance metrics

    • Stakeholder engagement and community impact summary

    • Continuous improvement goals and achievements

  2. Certification Compliance Report

    • Specific reporting for certification scheme requirements

    • FSC, SFI, PEFC, or other certification standard compliance

    • Audit findings and corrective action implementation

    • Certificate maintenance and renewal documentation

  3. Regulatory Compliance Report

    • Government agency reporting requirements

    • Environmental impact assessment updates

    • Endangered species protection compliance

    • Water quality and air quality monitoring results

  4. Stakeholder Communication Report

    • Public disclosure of sustainability practices

    • Community engagement and social impact assessment

    • Indigenous rights and consultation documentation

    • Transparency and accountability demonstration

34.1.4. Key Components

  1. Supply Base Description

    • Geographic boundaries and area coverage

    • Forest type and species composition

    • Ownership structure and management arrangements

    • Infrastructure and operational capabilities

  2. Sustainability Performance

    • Environmental protection measures and outcomes

    • Biodiversity conservation initiatives and results

    • Carbon sequestration and climate change mitigation

    • Water quality protection and monitoring

  3. Social Responsibility

    • Community engagement and consultation processes

    • Indigenous rights recognition and implementation

    • Worker safety and welfare programs

    • Local economic impact and development

  4. Economic Viability

    • Financial performance and operational efficiency

    • Market access and customer satisfaction

    • Innovation and technology adoption

    • Long-term economic sustainability

34.1.5. Reporting Standards

  1. Global Reporting Initiative (GRI)

    • Internationally recognized sustainability reporting framework

    • Comprehensive environmental, social, and governance metrics

    • Stakeholder engagement and materiality assessment

    • Standardized performance indicators and disclosure requirements

  2. Forest Stewardship Council (FSC) Requirements

    • Annual surveillance report requirements

    • Management plan implementation and monitoring

    • Stakeholder consultation documentation

    • Continuous improvement demonstration

  3. Sustainable Forestry Initiative (SFI) Standards

    • Annual progress report on SFI objectives

    • Fiber sourcing and procurement practice documentation

    • Conservation and biodiversity protection measures

    • Community engagement and outreach activities

  4. Sustainable Biomass Partnership (SBP) Framework

    • Supply base evaluation and risk assessment

    • Mitigation measure implementation and effectiveness

    • Monitoring and verification system performance

    • Continuous improvement and adaptive management

34.1.6. Key Features

  1. Multi-Standard Compliance

    • Integration of multiple certification scheme requirements

    • Comprehensive coverage of sustainability dimensions

    • Alignment with international reporting standards

    • Streamlined reporting for multiple audiences

  2. Geographic Integration

    • Spatial analysis and mapping of operations

    • Geographic information system (GIS) integration

    • Regional and landscape-level impact assessment

    • Multi-jurisdictional compliance coordination

  3. Performance Monitoring

    • Key performance indicator tracking and analysis

    • Environmental monitoring data integration

    • Social impact measurement and evaluation

    • Economic performance assessment and benchmarking

  4. Stakeholder Transparency

    • Public accessibility and transparency

    • Stakeholder feedback integration

    • Community consultation documentation

    • Third-party verification and validation

34.1.7. Example Use Cases

  1. FSC Forest Management Annual Report

    • Report Type: Annual certification compliance report

    • Coverage: 50,000-acre FSC-certified forest management unit

    • Content: Environmental monitoring, social engagement, economic performance

    • Audience: FSC auditors, stakeholders, local communities

    • Publication: Public website with full transparency

  2. SBP Supply Base Evaluation Report

    • Report Type: Biomass sustainability assessment

    • Coverage: Regional biomass supply base covering multiple counties

    • Content: Risk assessment, mitigation measures, monitoring results

    • Audience: SBP certification body, biomass customers, regulators

    • Publication: SBP public database and company website

  3. Integrated Multi-Standard Report

    • Report Type: Comprehensive sustainability report

    • Coverage: Large integrated forest products company operations

    • Content: FSC, SFI, and PEFC compliance plus GRI framework

    • Audience: Multiple certification bodies, investors, communities

    • Publication: Annual report with detailed appendices

34.1.8. Validation Rules

  1. Report Requirements

    • sbrId must be unique across system

    • organizationId must reference valid Organization

    • preparationDate must be valid date format

    • Report must cover defined time period and geographic area

  2. Content Consistency

    • supplyBaseIds must reference valid SupplyBase entities

    • reportGeographicDataId must encompass all covered supply bases

    • Certification compliance must align with organization certificates

    • Performance data must be supported by monitoring evidence

  3. Publication Standards

    • publicationUrl must be accessible if provided

    • Report must meet applicable transparency requirements

    • Stakeholder consultation must be documented appropriately

    • Third-party verification must be completed if required

34.1.9. Relationships

34.2. Regulatory and Compliance Entities

34.2.1. LCFSPathway

35. LcfsPathway

35.1. LCFSPathway

35.1.1. Overview

The LCFSPathway entity represents CARB-certified fuel pathways for California’s Low Carbon Fuel Standard (LCFS) compliance. Each pathway defines the carbon intensity, feedstock type, production process, and regulatory status for specific fuel production routes. This entity enables LCFS credit calculations and regulatory reporting by linking transactions to certified carbon intensities.

35.1.2. Fields

Field Type Required Description Examples
pathwayId string Yes CARB-assigned pathway identifier (primary key) CA-RD-2025-LMR-001, CA-ET-2025-CRN-042
pathwayType string (enum) Yes CARB pathway certification tier Lookup_Table, Tier_1, Tier_2
feedstockCategory string (enum) Yes Primary feedstock type for pathway logging_and_mill_residue, corn, algae
fuelProduct string (enum) Yes Final fuel product produced renewable_diesel, ethanol, biodiesel
facilityLocation string Yes Production facility location Stockton, CA, Iowa, Western_US
carbonIntensity number Yes Certified carbon intensity in gCO2e/MJ 19.85, 74.32, 12.41
energyEconomyRatio number Yes Energy economy ratio multiplier for credit calculation 1.0, 1.5, 2.0
certificationDate string (date) Yes CARB pathway certification date 2025-01-15
expirationDate string (date) No Pathway certification expiration date 2028-01-15
verificationStatus string (enum) Yes Current CARB verification status active, suspended, expired
caGreetVersion string Yes CA-GREET model version used for certification 3.0, 2.1
facilityCapacity number No Annual production capacity in gallons 50000000, 125000000
processDescription string No Brief description of production process Hydrotreated renewable diesel production
geographicScope string (enum) No Geographic applicability of pathway California, Western_US, National
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/lcfs-pathway/CA-RD-2025-LMR-001
lastUpdated string (date-time) No Timestamp of most recent pathway data update 2025-07-21T14:30:00Z

35.1.3. Key Features

  1. CARB Pathway Integration Direct mapping to official CARB pathway database Standardized pathway ID format validation Certification tier tracking (Lookup Table, Tier 1, Tier 2)

  2. Carbon Intensity Tracking Certified CI values from CA-GREET modeling Energy Economy Ratio for electric vehicle pathways Regulatory benchmark comparison support

  3. Feedstock Classification Comprehensive feedstock categories for all LCFS fuel types Forest biomass subcategories for waste vs. purpose-grown materials Integration with BOOST material tracking entities

  4. Regulatory Compliance Active/suspended/expired status tracking Certification and expiration date management CA-GREET version compatibility

35.1.4. Example Use Cases

  1. Renewable Diesel from Forest Residue Pathway Type: Tier_1 Feedstock: logging_and_mill_residue Carbon Intensity: 19.85 gCO2e/MJ Energy Economy Ratio: 1.0

  2. Ethanol from Corn Pathway Type: Lookup_Table Feedstock: corn Carbon Intensity: 74.32 gCO2e/MJ Energy Economy Ratio: 1.0

  3. Sustainable Aviation Fuel Pathway Type: Tier_2 Feedstock: used_cooking_oil Carbon Intensity: 12.41 gCO2e/MJ Energy Economy Ratio: 1.0

35.1.5. Relationships

35.1.6. Credit Calculation Formula

LCFS credits are calculated using pathway data:

Credits = (Benchmark_CI - Pathway_CI) × Fuel_Volume_MJ × EER

Where:

35.1.7. Validation Rules

35.1.8. LCFSReporting

36. LcfsReporting

36.1. LCFSReporting

36.1.1. Overview

The LCFSReporting entity represents quarterly compliance reports submitted by regulated entities to the California Air Resources Board (CARB) for the Low Carbon Fuel Standard (LCFS) program. Each report aggregates transaction data, calculates credit/deficit positions, and tracks submission status for regulatory compliance.

36.1.2. Fields

Field Type Required Description Examples
reportingId string Yes Unique identifier for quarterly report (primary key) LCFS-RPT-2025-Q1-PACIFIC001
regulatedEntityId string (FK) Yes Reference to regulated Organization entity pacific-renewable-fuels-001
reportingPeriod string Yes Reporting quarter in YYYY-QN format 2025-Q1, 2025-Q2, 2025-Q3
totalFuelVolume number Yes Total fuel volume reported in gallons 5075000.0, 8250000.0
totalCreditsGenerated number Yes Total LCFS credits generated in reporting period 54580477.10, 0.0
totalDeficitsIncurred number Yes Total LCFS deficits incurred in reporting period 0.0, 2500000.0
netPosition number Yes Net credit/deficit position (credits - deficits) 54580477.10, -2500000.0
complianceStatus string (enum) Yes Overall compliance status for reporting period compliant, deficit, pending
submissionDate string (date-time) No Date and time report was submitted to CARB 2025-04-15T10:30:00Z
verificationDate string (date-time) No Date of third-party verification completion 2025-04-10T14:00:00Z
verificationRequired boolean No Whether third-party verification is required true, false
reportingDeadline string (date) No CARB deadline for report submission 2025-05-15
transactionIds array<string> No Array of Transaction entity IDs included in report ["TXN-2025-Q1-001", "TXN-2025-Q1-002"]
pathwaySummary array<object> No Summary of activity by LCFS pathway See pathway summary structure below
calculationParameters object No Calculation parameters used for credit computation See calculation parameters structure
complianceMetrics object No Additional compliance and environmental impact metrics See compliance metrics structure
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/lcfs-reporting/LCFS-RPT-2025-Q1-PACIFIC001
lastUpdated string (date-time) No Timestamp of most recent report update 2025-07-21T16:45:00Z

36.1.3. Nested Structures

36.1.3.1. Pathway Summary
Each pathway summary object contains:
36.1.3.2. Calculation Parameters
36.1.3.3. Compliance Metrics

36.1.4. Key Features

  1. Quarterly Reporting Compliance Standardized reporting period format (YYYY-QN) Automatic deadline calculation and tracking Submission status monitoring

  2. Credit/Deficit Calculation Aggregated credit generation from all transactions Net position calculation (credits - deficits) Compliance status determination

  3. Third-Party Verification Verification requirement tracking based on entity size Verification completion date tracking Compliance timeline management

  4. Pathway Activity Summary Breakdown of activity by CARB pathway Transaction count and volume aggregation Feedstock type categorization

36.1.5. Example Use Cases

  1. Large Regulated Producer Multiple pathways and high transaction volume Third-party verification required Net credit generator with surplus for trading

  2. Small Regulated Importer Single pathway, lower transaction volume Self-certification allowed Compliance through purchased credits

  3. Blender/Distributor Mix of conventional and renewable fuels Deficit position requiring credit purchases Complex pathway attribution

36.1.6. Relationships

36.1.7. Credit Calculation Logic

The report aggregates credits calculated at the transaction level:

Total Credits = Σ[(Benchmark_CI - Pathway_CI) × Transaction_Volume_MJ × EER]

For each transaction in the reporting period, using:

36.1.8. Validation Rules

36.1.9. Audit

37. Audit

37.1. Audit

37.1.1. Overview

The Audit entity tracks certification audits and compliance verification activities within the BOOST traceability system. Audits are conducted by certification bodies to verify that organizations meet sustainability standards, maintain proper chain of custody procedures, and comply with certification scheme requirements. This entity supports audit trail management, compliance verification, and certification maintenance tracking.

37.1.2. Fields

Field Type Required Description Examples
auditId string Yes Unique identifier for the audit (primary key) AUDIT-001, AUDIT-FSC-PACIFIC-2024-01
auditType string Yes Type of audit being conducted (enum) Initial, Surveillance, Transfer
auditDate string (date) Yes Date when the audit was conducted 2024-03-15, 2024-07-22
organizationId string (FK) Yes Foreign key to organization being audited ORG-PACIFIC-FOREST-001, ORG-KLAMATH-HARVEST
cbId string (FK) No Foreign key to certification body conducting audit SFI, FSC-US, PEFC-001
findings string No Summary of audit findings and recommendations No major non-conformities found, Minor issues with record keeping resolved
reportUrl string (uri) No URL link to detailed audit report https://audit-reports.example.com/AUDIT-FSC-001.pdf
auditGeographicDataId string (FK) No Foreign key to location where audit was conducted GEO-MILL-PACIFIC-001, GEO-OFFICE-KLAMATH
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/audit/AUDIT-001

37.1.3. Audit Types

  1. Initial

    • First-time certification audit for new certificate applicants

    • Comprehensive assessment of all certification requirements

    • Establishes baseline compliance and capability assessment

    • Results in initial certificate issuance or rejection

    • Typically requires 6-12 months preparation period

  2. Surveillance

    • Ongoing monitoring audits for existing certificate holders

    • Annual or periodic verification of continued compliance

    • Focused review of key processes and risk areas

    • Maintains certificate validity and identifies improvements

    • Less comprehensive than initial audits

  3. Transfer

    • Audit conducted when changing certification bodies

    • Verification of records and compliance history transfer

    • Ensures continuity of certification without gaps

    • Review of previous audit findings and corrective actions

    • Required for seamless certificate transfer

37.1.4. Key Features

  1. Compliance Verification

    • Systematic verification of certification scheme requirements

    • Documentation review and process assessment

    • Staff interviews and competency evaluation

    • Physical inspection of facilities and operations

  2. Audit Trail Management

    • Complete audit history tracking for organizations

    • Corrective action follow-up and closure verification

    • Continuous improvement monitoring and progress tracking

    • Certificate maintenance and renewal timeline management

  3. Multi-Standard Support

    • FSC (Forest Stewardship Council) audit management

    • SFI (Sustainable Forestry Initiative) compliance verification

    • PEFC (Programme for the Endorsement of Forest Certification) auditing

    • SBP (Sustainable Biomass Partnership) assessment support

  4. Geographic Integration

    • Multi-site audit coordination and planning

    • Location-specific compliance assessment

    • Regional regulation and standard adaptation

    • Travel and logistics optimization for audit teams

37.1.5. Audit Process Workflow

  1. Pre-Audit Phase

    • Audit scheduling and scope definition

    • Document review and preparation

    • Stakeholder notification and coordination

    • Resource allocation and team assignment

  2. Audit Execution

    • Opening meeting and scope confirmation

    • Document review and record examination

    • Process observation and staff interviews

    • Facility inspection and equipment verification

  3. Post-Audit Activities

    • Finding documentation and classification

    • Corrective action plan development

    • Report preparation and review

    • Certificate decision and issuance

37.1.6. Finding Classifications

  1. Conformity

    • Full compliance with certification requirements

    • No corrective actions required

    • Positive findings supporting certificate maintenance

    • Best practice examples for improvement

  2. Minor Non-Conformity

    • Small deviations from requirements

    • Corrective action required within defined timeframe

    • Certificate maintained with monitoring

    • Follow-up verification in next surveillance audit

  3. Major Non-Conformity

    • Significant failure to meet requirements

    • Immediate corrective action required

    • Certificate suspension or withdrawal risk

    • Additional audit required to verify corrections

37.1.7. Example Use Cases

  1. FSC Chain of Custody Initial Audit

    • Audit Type: Initial

    • Organization: New sawmill seeking FSC certification

    • Scope: Complete chain of custody system assessment

    • Duration: 2-3 days including forest operations review

    • Outcome: Certificate issuance with minor corrective actions

  2. SFI Surveillance Audit

    • Audit Type: Surveillance

    • Organization: Existing certified logging contractor

    • Scope: Annual compliance monitoring

    • Duration: 1 day focused on high-risk areas

    • Outcome: Continued certificate validity confirmed

  3. Multi-Site Transfer Audit

    • Audit Type: Transfer

    • Organization: Integrated forest products company

    • Scope: Multiple facilities across different states

    • Duration: 5 days with coordinated audit team

    • Outcome: Successful certificate transfer to new certification body

37.1.8. Validation Rules

  1. Audit Requirements

    • auditId must be unique across system

    • auditType must be valid enumerated value

    • auditDate must be valid date format

    • organizationId must reference valid Organization

  2. Relationship Consistency

    • cbId must reference valid CertificationBody if provided

    • auditGeographicDataId must reference valid GeographicData location

    • Organization must have active or pending certification status

  3. Audit Logic

    • Initial audits must precede Surveillance audits for same organization

    • Transfer audits require existing certificate from different certification body

    • Audit findings must be consistent with audit type and scope

37.1.9. Relationships

37.1.10. VerificationStatement

38. VerificationStatement

38.1. VerificationStatement

38.1.1. Overview

The VerificationStatement entity manages third-party verification statements for certification compliance within the BOOST traceability system. Verification statements are formal declarations issued by authorized certification bodies confirming that materials, processes, or transactions meet specific sustainability standards. This entity supports audit trails, compliance verification, and certification maintenance across supply chain operations.

38.1.2. Fields

Field Type Required Description Examples
statementId string Yes Unique identifier for the verification statement (primary key) VS-001, VS-FSC-PACIFIC-2024-001
verificationDate string (date) Yes Date when the verification was completed 2024-03-15, 2024-07-22
issuingBody string Yes Name of the certification body issuing the statement FSC United States, SFI Inc., PEFC Council
scope string No Scope and coverage of the verification statement Chain of custody for Douglas Fir sawlogs, SBP biomass sustainability verification
transactionBatchId string (FK) No Foreign key to transaction batch being verified TXN-BATCH-PACIFIC-2024-Q1, TXN-BATCH-BIOMASS-001
verificationResult string No Result of the verification process (enum) compliant, non_compliant, conditional_compliance
certificationSchemeId string (FK) No Foreign key to certification scheme being verified CERT-SCHEME-FSC-001, CERT-SCHEME-SBP
validityPeriod string No Period for which the verification statement is valid 12 months, 2024-01-01 to 2024-12-31, Until next audit
verificationDetails string No Detailed findings and verification methodology FSC Mix 70% verified through complete chain of custody review, All SBP requirements met
documentUrl string (uri) No URL link to complete verification statement document https://certificates.fsc.org/statements/VS-FSC-001.pdf
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/verification-statement/VS-001

38.1.3. Verification Types

  1. Chain of Custody Verification

    • Verifies material flow and custody transfers

    • Confirms segregation and mixing calculations

    • Validates certificate claims and percentages

    • Ensures proper documentation and record keeping

  2. Sustainability Compliance Verification

    • Confirms adherence to sustainability standards

    • Validates environmental and social criteria

    • Verifies supply base assessments and risk evaluations

    • Ensures compliance with regulatory requirements

  3. Product Specification Verification

    • Confirms product meets specified requirements

    • Validates quality grades and technical specifications

    • Verifies species composition and processing methods

    • Ensures delivery compliance with contract terms

  4. Transaction Verification

    • Verifies transaction completeness and accuracy

    • Confirms payment and delivery terms compliance

    • Validates regulatory reporting requirements

    • Ensures proper documentation and record keeping

38.1.4. Verification Results

  1. compliant

    • Full compliance with all verification criteria

    • No corrective actions required

    • Statement validates claims and certifications

    • Materials approved for use with specified claims

  2. non_compliant

    • Failure to meet verification criteria

    • Corrective actions required before approval

    • Claims cannot be supported by evidence

    • Materials may require reclassification or rejection

  3. conditional_compliance

    • Partial compliance with minor deficiencies

    • Specific conditions must be met for full compliance

    • Limited approval with restrictions

    • Follow-up verification required

38.1.5. Key Features

  1. Third-Party Validation

    • Independent verification by accredited bodies

    • Objective assessment of compliance claims

    • Professional auditor expertise and credentials

    • Impartial evaluation of evidence and documentation

  2. Multi-Standard Support

    • FSC (Forest Stewardship Council) verification

    • SFI (Sustainable Forestry Initiative) validation

    • PEFC (Programme for the Endorsement of Forest Certification)

    • SBP (Sustainable Biomass Partnership) assessment

  3. Transaction Integration

    • Batch-level verification for grouped transactions

    • Supply chain verification across multiple parties

    • Integration with transaction processing workflows

    • Support for complex multi-party transactions

  4. Documentation Management

    • Complete verification statement archival

    • Document version control and access management

    • Integration with certificate management systems

    • Audit trail and compliance history tracking

38.1.6. Certification Body Integration

  1. FSC United States

    • Chain of custody verification services

    • Forest management standard compliance

    • Controlled wood verification programs

    • Multi-site and group certification support

  2. SFI Inc.

    • Fiber sourcing verification programs

    • Chain of custody standard compliance

    • Procurement standard verification

    • Logger and landowner education validation

  3. PEFC Council

    • International certification scheme recognition

    • National scheme compliance verification

    • Chain of custody program validation

    • Due diligence system verification

  4. SBP Approved Certification Bodies

    • Biomass sustainability verification

    • Supply base evaluation compliance

    • Regional risk assessment validation

    • Mass balance system verification

38.1.7. Example Use Cases

  1. FSC Chain of Custody Verification

    • Verification Statement: FSC Mix 75% for lumber shipment

    • Issuing Body: FSC-accredited certification body

    • Scope: Complete supply chain from forest to mill

    • Result: Compliant with all FSC standards

    • Validity: 12 months from issuance date

  2. SBP Biomass Sustainability Verification

    • Verification Statement: SBP-compliant biomass fuel

    • Issuing Body: SBP-approved certification body

    • Scope: Supply base evaluation and mass balance verification

    • Result: Conditional compliance pending risk mitigation

    • Validity: Until next surveillance audit

  3. Multi-Standard Transaction Verification

    • Verification Statement: Combined FSC and PEFC materials

    • Issuing Body: Mutually recognized certification body

    • Scope: Complex transaction with multiple certification claims

    • Result: Compliant with segregation requirements

    • Validity: Transaction-specific validity period

38.1.8. Validation Rules

  1. Statement Requirements

    • statementId must be unique across system

    • verificationDate must be valid date format

    • issuingBody must be authorized certification body

    • Verification scope must be clearly defined

  2. Certification Body Authority

    • issuingBody must be accredited for verification scope

    • Certification scheme must be within body’s authority

    • Verification methods must follow approved procedures

    • Statement must be within body’s geographic scope

  3. Transaction Integration

    • transactionBatchId must reference valid TransactionBatch

    • Verification scope must cover transaction materials

    • Verification date must be appropriate for transaction timeline

    • Statement validity must cover transaction period

38.1.9. Relationships

38.1.10. MassBalanceAccount

39. MassBalanceAccount

39.1. MassBalanceAccount

39.1.1. Overview

The MassBalanceAccount entity manages mass balance accounting for material flow tracking and compliance reporting within the BOOST traceability system. Mass balance accounting is a fundamental requirement for certification schemes like FSC (Forest Stewardship Council), SBP (Sustainable Biomass Partnership), and PEFC (Programme for the Endorsement of Forest Certification) that allow mixing of certified and non-certified materials while maintaining accurate accounting of certified content percentages. This entity tracks material inputs, outputs, and balances across defined periods to ensure certification compliance and enable accurate sustainability claims.

39.1.2. Fields

Field Type Required Description Examples
accountId string Yes Unique identifier for the mass balance account (primary key) MBA-001, MBA-FSC-MILL-2024-Q1
organizationId string (FK) Yes Foreign key to organization maintaining the account ORG-PACIFIC-MILL-001, ORG-BIOMASS-PROCESSOR
productGroupId string (FK) Yes Foreign key to product group being tracked PG-LUMBER-PRODUCTS, PG-WOOD-CHIPS, PG-PULPWOOD
periodInputs number No Total certified material inputs during balancing period 15000.5, 250000.0, 75000.25
periodOutputs number No Total certified material outputs during balancing period 14750.0, 245000.0, 73500.0
currentBalance number Yes Current account balance of certified material credits 2500.0, -1500.0, 8750.5
balancingPeriod string No Time period for mass balance accounting 2024-Q1, January 2024, 2024-01-01 to 2024-03-31
conversionFactors number No Conversion factor for input/output calculations 0.85, 1.0, 0.92, 1.15
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/mass-balance-account/MBA-001

39.1.3. Mass Balance Principles

  1. Certification Scheme Compliance

    • FSC Controlled Wood mass balance system

    • SBP biomass sustainability mass balance

    • PEFC Due Diligence System (DDS) tracking

    • Sustainable sourcing percentage calculations

  2. Material Flow Accounting

    • Certified material inputs from suppliers

    • Non-certified material inputs identification

    • Processing efficiency and conversion rates

    • Output allocation to certified and non-certified products

  3. Balance Maintenance

    • Credit accumulation from certified inputs

    • Debit allocation to certified output claims

    • Account balance monitoring and reconciliation

    • Compliance threshold management

  4. Periodic Reconciliation

    • Regular accounting period closure

    • Physical inventory verification

    • Documentation and audit trail maintenance

    • Certification body reporting requirements

39.1.4. Account Balance Management

  1. Positive Balance

    • Surplus of certified material credits available

    • Ability to make certified content claims

    • Capacity for future certified product output

    • Compliance buffer for operational flexibility

  2. Negative Balance

    • Deficit requiring corrective action

    • Temporary non-compliance status

    • Need for additional certified inputs

    • Potential suspension of certified claims

  3. Zero Balance

    • Exact match between inputs and outputs

    • Optimal certification scheme compliance

    • Maximum utilization of certified materials

    • Efficient resource allocation

39.1.5. Conversion Factors and Processing

  1. Volume-Based Conversions

    • Green weight to dry weight conversions

    • Log volume to lumber volume yields

    • Bark inclusion and exclusion factors

    • Species-specific density adjustments

  2. Processing Efficiency

    • Mill recovery rates and sawing efficiency

    • Biomass processing and densification

    • Energy conversion efficiency factors

    • Co-product allocation methodologies

  3. Quality Adjustments

    • Grade recovery and quality sorting

    • Moisture content standardization

    • Size and dimensional standardization

    • Species composition accounting

39.1.6. Balancing Period Management

  1. Quarterly Accounting

    • Standard three-month accounting periods

    • Alignment with certification reporting cycles

    • Seasonal operation considerations

    • Cash flow and inventory optimization

  2. Monthly Reconciliation

    • More frequent balance monitoring

    • Rapid identification of compliance issues

    • Improved inventory management

    • Enhanced operational control

  3. Annual Reporting

    • Comprehensive yearly certification reporting

    • Long-term trend analysis and planning

    • Certification body annual assessments

    • Strategic sourcing planning

  4. Campaign-Based Accounting

    • Project-specific mass balance tracking

    • Single-source material campaigns

    • Special product run accounting

    • Customer-specific certification requirements

39.1.7. Certification Scheme Integration

  1. FSC (Forest Stewardship Council)

    • FSC Mix products with percentage claims

    • Controlled Wood verification and accounting

    • Chain of custody maintenance requirements

    • Credit system and transfer mechanisms

  2. SBP (Sustainable Biomass Partnership)

    • Supply base evaluation compliance

    • Regional risk assessment integration

    • Mass balance system requirements

    • Controlled feedstock accounting

  3. PEFC (Programme for the Endorsement of Forest Certification)

    • Due Diligence System implementation

    • Controversial sources exclusion

    • Percentage-based claims support

    • Multi-site operation coordination

  4. Custom Certification Programs

    • Company-specific sustainability programs

    • Regional certification scheme requirements

    • Customer-mandated tracking systems

    • Voluntary sustainability commitments

39.1.8. Input and Output Tracking

  1. Certified Inputs

    • FSC, PEFC, or SBP certified material receipts

    • Supplier certificate validation and verification

    • Volume and quality documentation

    • Species and origin verification

  2. Controlled Inputs

    • Low-risk or controlled source materials

    • Due diligence verification completion

    • Risk assessment and mitigation documentation

    • Acceptable source verification

  3. Non-Certified Inputs

    • Conventional material without certification

    • Unknown or unverified source materials

    • High-risk source identification

    • Segregation requirements

  4. Certified Outputs

    • Products sold with certification claims

    • Certificate number and claim validation

    • Customer delivery documentation

    • Claim percentage calculation and verification

39.1.9. Account Monitoring and Controls

  1. Real-Time Balance Tracking

    • Continuous account balance monitoring

    • Automated alert systems for low balances

    • Proactive sourcing recommendations

    • Compliance risk management

  2. Audit Trail Documentation

    • Complete transaction history maintenance

    • Supporting documentation archival

    • Certificate and claim verification records

    • Third-party audit preparation

  3. Exception Management

    • Balance deficit identification and resolution

    • Sourcing adjustment and corrective actions

    • Certification body notification procedures

    • Customer communication protocols

39.1.10. Example Use Cases

  1. FSC Mix Lumber Production

    • Account: FSC Mix lumber mass balance

    • Inputs: 60% FSC certified logs, 40% controlled wood

    • Processing: 85% mill recovery rate conversion factor

    • Outputs: Lumber products with 60% FSC Mix claims

    • Balance: Positive balance allowing continued certified production

  2. SBP Biomass Processing

    • Account: SBP compliant wood chip production

    • Inputs: 100% SBP-compliant feedstock from risk-assessed supply base

    • Processing: 1.0 conversion factor for chip production

    • Outputs: Wood chips with full SBP compliance claims

    • Balance: Maintained at optimal level for continuous operations

  3. Multi-Scheme Compliance

    • Account: Combined FSC and PEFC mass balance system

    • Inputs: Mixed certified materials from multiple schemes

    • Processing: Product-specific conversion factors

    • Outputs: Segregated products with appropriate scheme claims

    • Balance: Separate accounting for each certification scheme

39.1.11. Compliance Monitoring and Reporting

  1. Internal Controls

    • Monthly balance reconciliation procedures

    • Quarterly compliance assessment reports

    • Annual management review processes

    • Continuous improvement identification

  2. External Reporting

    • Certification body quarterly reports

    • Customer certification status updates

    • Regulatory compliance documentation

    • Third-party verification support

  3. Audit Preparation

    • Complete documentation organization

    • Balance calculation verification

    • Supporting evidence compilation

    • Staff training and preparation

39.1.12. Validation Rules

  1. Account Requirements

    • accountId must be unique across system

    • organizationId must reference valid Organization

    • productGroupId must reference valid ProductGroup

    • currentBalance must be tracked continuously

  2. Balance Integrity

    • periodInputs must be non-negative when provided

    • periodOutputs must be non-negative when provided

    • currentBalance calculation must be mathematically consistent

    • conversionFactors must be positive numbers when provided

  3. Period Management

    • balancingPeriod must be clearly defined timeframe

    • Period inputs and outputs must align with specified timeframe

    • Account balance must be updated for each accounting period

    • Historical balances must be maintained for audit purposes

  4. Certification Compliance

    • Account balance must not remain negative beyond certification limits

    • Input documentation must support balance calculations

    • Output claims must not exceed available certified content

    • Conversion factors must be verified and justified

39.1.13. Relationships

39.1.14. EnergyCarbonData

40. EnergyCarbonData

40.1. EnergyCarbonData

40.1.1. Overview

The EnergyCarbonData entity manages energy and carbon intensity data for lifecycle assessments and regulatory compliance within the BOOST traceability system. This entity captures comprehensive carbon accounting information, energy content measurements, and environmental impact data required for Low Carbon Fuel Standard (LCFS) compliance, renewable fuel certification, and sustainability reporting. It integrates field measurements, laboratory analysis, and lifecycle modeling to provide complete energy and carbon profiles for materials throughout the supply chain.

40.1.2. Fields

Field Type Required Description Examples
energyCarbonDataId string Yes Unique identifier for the energy/carbon data record (primary key) ECD-001, ECD-MOISTURE-ANALYSIS-2024-001
dataType string Yes Type of energy/carbon data being recorded (enum) moisture, carbon_intensity, energy_content, emissions, lifecycle_assessment
value number Yes Numeric value of the measurement or calculation 12.5, 45.2, 18.7, 102.3
unit string Yes Unit of measurement for the value (enum) percentage, kg_CO2e, MJ, gCO2e/MJ, MJ/kg
source string Yes Source or method of data acquisition (enum) field_measurement, laboratory_analysis, default_values, calculated
measurementMethod string No Specific measurement or calculation method (enum) oven_dry, CA-GREET3.0, GREET2023, near_infrared, LCA_Modeling
traceableUnitId string (FK) No Foreign key to associated traceable unit TRU-LOG-001, TRU-BIOMASS-BATCH-456
measurementRecordId string (FK) No Foreign key to detailed measurement record MR-MOISTURE-ANALYSIS-001, MR-CARBON-LAB-789
measurementTimestamp string (datetime) No Date and time when measurement was taken 2024-03-15T10:30:00Z, 2024-07-22T14:45:00Z
measurementGeographicDataId string (FK) No Foreign key to location where measurement was taken GEO-LAB-FACILITY-001, GEO-FIELD-SITE-HARVEST
temperatureConditions number No Temperature during measurement (Celsius) 20.5, -2.3, 35.8
humidityConditions number No Relative humidity during measurement (percentage) 45.2, 78.5, 23.1
lcfsPathwayType string No LCFS pathway tier classification (enum) Lookup_Table, Tier_1, Tier_2, Not_LCFS
energyEconomyRatio number No Energy economy ratio for LCFS credit calculation (0.5-3.0) 1.0, 2.5, 0.8, 1.75
lifeCycleStage string No Lifecycle stage for carbon intensity data (enum) feedstock, production, transport, distribution, combustion
regulatoryBenchmark number No CARB regulatory benchmark for comparison (gCO2e/MJ) 90.27, 88.45, 82.15, 95.12
caGreetVersion string No CA-GREET model version used for calculation 3.0, 4.0, 4.1, 5.0
qualityAssurance string No Quality assurance and validation notes Third-party laboratory verified, ISO 17025 certified, CARB approved methodology
@id string (uri) Yes Unique URI identifier for JSON-LD https://github.com/carbondirect/BOOST/schemas/energy-carbon-data/ECD-001

40.1.3. Data Types and Applications

  1. moisture

    • Moisture content percentage for biomass materials

    • Critical for energy content and carbon intensity calculations

    • Required for LCFS pathway qualification

    • Impacts processing efficiency and fuel quality

  2. carbon_intensity

    • Lifecycle carbon intensity in gCO2e/MJ

    • Primary metric for LCFS compliance assessment

    • Used for regulatory credit calculations

    • Compared against CARB regulatory benchmarks

  3. energy_content

    • Energy content in MJ/kg or MJ/gallon

    • Higher heating value (HHV) or lower heating value (LHV)

    • Essential for fuel quality specifications

    • Required for energy economy ratio calculations

  4. transport

    • Transportation-related energy consumption and emissions

    • Fuel consumption for logistics operations

    • Distance-based emission factors

    • Modal transport efficiency analysis

  5. fuel_consumption

    • Equipment and process fuel consumption data

    • Harvesting, processing, and handling energy use

    • Direct measurement or calculated consumption

    • Basis for lifecycle emission calculations

  6. emissions

    • Direct greenhouse gas emissions measurements

    • Process-specific emission factors

    • Scope 1, 2, and 3 emission categories

    • Supporting data for carbon intensity calculations

  7. lifecycle_assessment

    • Comprehensive LCA results and analysis

    • Cradle-to-grave or cradle-to-gate assessments

    • Multiple impact categories beyond carbon

    • Full system boundary analysis

40.1.4. Measurement Methods and Standards

  1. Physical Measurement Methods

    • oven_dry: Standard oven-drying method for moisture content

    • electrical_resistance: Electrical moisture meters

    • microwave: Microwave moisture analysis

    • near_infrared: NIR spectroscopy for rapid analysis

    • gravimetric: Weight-based measurement techniques

  2. Carbon Intensity Modeling

    • CA-GREET3.0: California-modified GREET model version 3.0

    • GREET2023: Latest Argonne National Lab GREET model

    • Direct_Measurement: Field or facility-based measurements

    • LCA_Modeling: Comprehensive lifecycle assessment modeling

  3. Quality Assurance Standards

    • ISO 17025 laboratory accreditation

    • ASTM standard test methods

    • CARB-approved methodologies

    • Third-party verification protocols

40.1.5. LCFS Pathway Integration

  1. Lookup Table Pathways

    • Pre-approved carbon intensity values

    • Simplified pathway requirements

    • Standard feedstock and production processes

    • Limited documentation requirements

  2. Tier 1 Pathways

    • Site-specific carbon intensity calculations

    • Enhanced data requirements

    • Facility-specific operational data

    • Moderate verification requirements

  3. Tier 2 Pathways

    • Comprehensive lifecycle assessment

    • Detailed process modeling

    • Extensive data collection and verification

    • Highest accuracy and regulatory scrutiny

  4. Non-LCFS Applications

    • Carbon accounting for non-regulated markets

    • Voluntary sustainability reporting

    • Corporate carbon footprint analysis

    • Research and development applications

40.1.6. Lifecycle Stage Analysis

  1. feedstock

    • Raw material production and harvesting

    • Land use change considerations

    • Agricultural or forestry practices

    • Feedstock transportation to processing

  2. production

    • Processing facility operations

    • Energy consumption for conversion

    • Process emissions and efficiency

    • Co-product allocation and credits

  3. transport

    • Finished fuel transportation

    • Distribution network efficiency

    • Modal transport optimization

    • Regional distribution considerations

  4. distribution

    • Retail distribution and storage

    • Terminal and station operations

    • Final delivery to end users

    • Infrastructure energy requirements

  5. combustion

    • End-use combustion emissions

    • Vehicle or equipment efficiency

    • Criteria pollutant emissions

    • Direct carbon dioxide releases

  6. full_lifecycle

    • Comprehensive cradle-to-grave analysis

    • All lifecycle stages included

    • System boundary completeness

    • Total environmental impact assessment

40.1.7. Regulatory Compliance Integration

  1. CARB LCFS Compliance

    • California Air Resources Board requirements

    • Quarterly reporting obligations

    • Credit generation calculations

    • Pathway certification maintenance

  2. EPA RFS Integration

    • Renewable Fuel Standard compliance

    • D-code pathway qualification

    • RIN generation and tracking

    • Lifecycle threshold requirements

  3. International Standards

    • ISO 14067 carbon footprint standards

    • RED II sustainability criteria

    • CORSIA aviation fuel requirements

    • National renewable fuel programs

40.1.8. Energy Economy Ratio Applications

  1. LCFS Credit Calculations

    • EER values between 0.5 and 3.0

    • Fuel type and application specific

    • Efficiency compared to petroleum baseline

    • Credit multiplier for advanced biofuels

  2. Technology Assessment

    • Vehicle efficiency comparisons

    • Engine technology improvements

    • Fuel system optimization

    • Performance benchmarking

40.1.9. Example Use Cases

  1. Biomass Moisture Content Analysis

    • Data Type: moisture measurement for wood chips

    • Value: 35.2% moisture content (wet basis)

    • Method: Oven-dry analysis per ASTM D4442

    • Application: Energy content calculation for LCFS pathway

    • Quality Assurance: ISO 17025 certified laboratory

  2. Renewable Diesel Carbon Intensity

    • Data Type: Tier 1 pathway carbon intensity

    • Value: 22.5 gCO2e/MJ lifecycle emissions

    • Method: CA-GREET 3.0 modeling with facility data

    • Application: LCFS credit generation calculation

    • Benchmark: 90.27 gCO2e/MJ regulatory standard

  3. Transportation Emission Factor

    • Data Type: Transport stage emissions

    • Value: 5.8 gCO2e/MJ for 100-mile trucking

    • Method: Direct fuel consumption measurement

    • Application: Lifecycle assessment component

    • Integration: Combined with feedstock and production data

40.1.10. Data Quality and Validation

  1. Measurement Accuracy

    • Calibrated instrumentation requirements

    • Measurement uncertainty quantification

    • Traceability to national standards

    • Regular equipment maintenance and verification

  2. Data Verification

    • Third-party validation protocols

    • Chain of custody for samples

    • Documentation requirements

    • Audit trail maintenance

  3. Regulatory Acceptance

    • CARB methodology approval

    • EPA verification protocols

    • International standard compliance

    • Certification body recognition

40.1.11. Validation Rules

  1. Data Requirements

    • energyCarbonDataId must be unique across system

    • dataType must align with measurement method

    • value must be positive number appropriate for data type

    • unit must be compatible with data type and value

  2. Measurement Consistency

    • measurementMethod must be appropriate for data type

    • measurementTimestamp must be within reasonable timeframe

    • Environmental conditions must be documented for sensitive measurements

    • Quality assurance must meet applicable standards

  3. LCFS Integration

    • lcfsPathwayType must be valid for data application

    • energyEconomyRatio must be within allowable range (0.5-3.0)

    • regulatoryBenchmark must reference current CARB standards

    • caGreetVersion must be approved for regulatory use

  4. Traceability Integration

    • traceableUnitId must reference valid TRU if provided

    • measurementRecordId must reference valid measurement record

    • Geographic location must be consistent with TRU origin

    • Lifecycle stage must align with TRU processing history

40.1.12. Relationships

41. Schema Definitions

The BOOST schema system provides comprehensive validation and structure definitions for all entities in the data model. All schemas are defined using JSON Schema Draft-07 format and include business logic validation rules.

41.1. JSON Schema Format

All BOOST entity definitions MUST be provided as [JSON-SCHEMA] Draft-07 compliant schemas with the following REQUIRED structure:

NOTE: The Python reference implementation automatically loads and generates dynamic models from these schema definitions.

{
  "schema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "$id": "https://github.com/carbondirect/BOOST/schemas/entity-name",
    "title": "Entity Name",
    "type": "object",
    "properties": { ... },
    "required": [ ... ]
  }
}

42. Business Logic Validation

Implementations MUST validate entities against 8 categories of business rules to ensure data consistency, regulatory compliance, and supply chain integrity throughout the BOOST traceability system.

NOTE: The Python reference implementation provides a comprehensive example of all business logic validation categories with configuration-driven rules.

42.1. Volume/Mass Conservation

Physical conservation laws MUST be enforced across all processing operations to ensure material balance accuracy and prevent fraudulent volume/mass reporting.

42.1.1. MaterialProcessing Volume Conservation

Core Rule: Input volume MUST always be greater than or equal to output volume plus documented volume loss:

inputVolume ≥ (outputVolume + volumeLoss)

Implementation Requirements:

Approved Volume Loss Reasons:

Exception Handling:

42.1.2. Mass Balance Validation

Core Rule: Mass can only decrease through processing; increases indicate data errors:

inputMass ≥ outputMass

Density Consistency Checks: All calculated densities MUST fall within realistic species ranges:

42.1.3. Split/Merge Operations

Split Validation: When one TraceableUnit becomes multiple units:

parentTRU.volume = Σ(childTRU[i].volume) + documentedProcessingLoss
parentTRU.mass = Σ(childTRU[i].mass) + documentedMassLoss

Merge Validation: When multiple TraceableUnits combine:

Σ(parentTRU[i].volume) ≥ resultTRU.volume
Σ(parentTRU[i].mass) ≥ resultTRU.mass  

Chain of Custody Preservation: Split and merge operations MUST maintain certification claim percentages proportionally.

42.2. Temporal Logic

Date and time consistency validation MUST ensure chronological accuracy and prevent temporal impossibilities in supply chain operations.

42.2.1. Processing Sequence Validation

Core Requirements: All timestamps MUST follow logical supply chain sequence:

harvestTimestamp < firstProcessingTimestamp < subsequentProcessingTimestamps < transactionTimestamp

Implementation Rules:

42.2.2. Certificate Validity Periods

Temporal Coverage Requirements:

Certificate Renewal Handling:

42.2.3. Seasonal and Geographic Constraints

Harvest Season Validation:

42.2.4. Event Sequence Integrity

LocationHistory Temporal Rules:

42.3. Geographic Logic

Spatial relationship validation MUST verify location consistency, operational boundary compliance, and transport feasibility throughout the supply chain.

42.3.1. Operational Boundary Validation

Organization Territory Compliance: Every TraceableUnit location MUST fall within the operational boundaries of the responsible Organization:

GeoJSON Boundary Checking: Implementations MUST support point-in-polygon calculations using the GeographicData entity’s geoJsonGeometry field:

// Validation pseudocode
function validateLocationWithinBoundary(point, organizationBoundaries) {
    return organizationBoundaries.some(boundary => 
        pointInPolygon(point.coordinates, boundary.geoJsonGeometry)
    );
}

42.3.2. Transport Distance and Time Validation

Reasonable Transport Times:

Route Feasibility:

42.3.3. Cross-Border Compliance

International Transport Requirements:

42.3.4. Facility Authorization

Processing Facility Validation:

42.4. Species Composition

Percentage validation for multi-species materials MUST enforce mathematical consistency and support accurate claim allocation throughout the supply chain.

42.4.1. Mathematical Consistency

Percentage Sum Validation: All SpeciesComponent percentages MUST sum to exactly 100% with tolerance for floating-point precision:

Σ(speciesComponent[i].percentage) = 100.0 ± 0.01%

Individual Component Constraints:

42.4.2. Species Composition Changes Through Processing

Processing Impact Documentation: Different processing operations may affect species composition ratios:

Composition Tracking Requirements:

42.4.3. Mixed-Species Certification Claims

Proportional Claim Allocation: Certification claims for mixed-species materials MUST be allocated proportionally:

materialClaim.percentage = Σ(speciesComponent[i].percentage × speciesComponent[i].certificationClaim)

Species-Specific Restrictions:

42.4.4. Scientific Name Validation

Taxonomic Accuracy:

42.5. Certification Logic

Chain of custody validation MUST ensure certification integrity, prevent claim inflation, and maintain audit trail compliance throughout supply chain operations.

42.5.1. Certificate Validity and Scope

Certificate Status Validation:

Multi-Scheme Certification: Organizations MAY hold multiple certificates (FSC, SFI, PEFC) simultaneously:

42.5.2. Chain of Custody Percentage Tracking

Claim Percentage Calculation: Downstream certification claims CANNOT exceed input certified percentages:

outputClaim.percentage ≤ (inputCertifiedVolume / totalInputVolume) × 100

Mass Balance Accounting:

Claim Inheritance Rules:

42.5.3. Third-Party Verification

Audit Requirements:

Verification Statement Validation:

42.6. Regulatory Compliance

Jurisdiction-specific rules MUST be enforced based on operational location, material destination, and applicable regulatory frameworks.

42.6.1. California LCFS Compliance

Pathway Registration Requirements:

Quarterly Reporting Obligations:

42.6.2. Species-Specific Regulations

CITES Compliance: Protected species under CITES require special handling:

Endangered Species Act (ESA):

42.6.3. International Trade Requirements

Export Documentation:

Import Compliance:

42.6.4. Regional Certification Requirements

European Union Requirements:

United States Federal Requirements:

42.7. Economic Logic

Price and payment validation MUST ensure commercial reasonableness, prevent money laundering, and support market transparency for biomass supply chain transactions.

42.7.1. Market Price Validation

Price Range Validation: Transaction prices MUST fall within acceptable market ranges for material type, quality, and geography:

Regional Price Benchmarks:

42.7.2. Payment Terms and Commercial Reasonableness

Standard Industry Payment Terms:

Commercial Relationship Validation:

42.7.3. Anti-Money Laundering (AML) Compliance

Suspicious Transaction Indicators:

Know Your Customer (KYC) Requirements:

42.7.4. Volume-Price Correlation

Quantity Discount Validation: Large volume transactions typically command lower per-unit prices:

Market Depth Analysis:

42.8. Quality Assurance

Material quality constraints MUST be enforced throughout the supply chain to ensure end-use suitability, maintain product integrity, and support quality-based market differentiation.

42.8.1. Material Quality Grade Validation

Grade Classification Standards: Quality grades MUST align with established industry standards:

Grade-Specific Requirements: Each quality grade has specific dimensional and quality criteria:

42.8.2. Moisture Content Management

Moisture Content Validation Rules:

Moisture Content Change Tracking:

42.8.3. Quality Degradation Tracking

Degradation Factor Documentation: Quality may degrade through handling and processing:

Quality Improvement Documentation: Some processing operations may improve quality grades:

42.8.4. End-Use Compatibility Validation

Application-Specific Requirements: Material quality must be suitable for intended end use:

Quality Chain Preservation:

42.9. Implementation Requirements

All BOOST conforming implementations MUST implement comprehensive validation across all eight business logic categories with configurable rules, clear error reporting, and comprehensive audit trail capabilities.

42.9.1. Validation Engine Requirements

Core Validation Capabilities:

Error Reporting Standards:

42.9.2. Configuration Management

Rule Configuration Structure:

Extensibility Requirements:

42.9.3. Audit and Compliance Support

Validation Audit Trails:

Compliance Reporting:

43. Serialization and Exchange

BOOST supports multiple serialization formats to enable broad interoperability across different systems and use cases. JSON-LD is the preferred format for semantic web integration and linked data applications.

43.1. JSON-LD as Primary Format

43.1.1. What is JSON-LD?

JSON for Linking Data (JSON-LD) is a lightweight Linked Data format built on top of JSON that provides a way to express Linked Data using JSON syntax. Unlike standard JSON, JSON-LD includes semantic context that makes data self-describing and machine-interpretable across different systems and organizations.

Key characteristics of JSON-LD:

43.1.2. Why BOOST Uses JSON-LD

BOOST adopts JSON-LD as its primary serialization format to address critical challenges in biomass supply chain data exchange:

43.1.2.1. Semantic Interoperability
Traditional JSON lacks semantic context, making it difficult for different organizations to exchange data without extensive coordination. JSON-LD’s semantic context ensures that:
43.1.2.2. Supply Chain Integration
Biomass supply chains involve diverse participants (harvesters, processors, certifiers, regulators) using different systems:

JSON-LD enables seamless data flow between these heterogeneous systems without requiring proprietary APIs or custom integration points.

43.1.2.3. Regulatory Compliance
Multiple jurisdictions have different reporting requirements:

JSON-LD’s semantic flexibility allows the same core data to satisfy multiple regulatory frameworks simultaneously.

43.1.2.4. Future-Proofing
As new regulations, technologies, and participants enter the biomass ecosystem:

43.1.3. JSON-LD Benefits in BOOST

43.1.3.1. Enhanced Data Exchange
{
  "@context": "https://boost-standard.org/context/v1",
  "@type": "TraceableUnit", 
  "@id": "https://forestco.example/tru/LOG-001",
  "traceableUnitId": "TRU-LOG-CA-042",
  "totalVolumeM3": 25.5,
  "harvesterId": "https://forestco.example/org/HARVESTER-001",
  "materialTypeId": "https://boost-standard.org/materials/douglas-fir"
}

This example demonstrates how JSON-LD makes BOOST data:

43.1.3.2. Cross-System Compatibility
Organizations can:
43.1.3.3. Knowledge Graph Integration
JSON-LD enables transformation to RDF triples for:

43.1.4. Technical Requirements

BOOST data MUST be serializable to [JSON-LD11] format with:

43.1.4.1. JSON-LD Context Structure
{
  "@context": {
    "@version": 1.1,
    "@vocab": "https://boost-standard.org/vocabulary/",
    "schema": "http://schema.org/",
    "prov": "http://www.w3.org/ns/prov#",
    "qudt": "http://qudt.org/schema/qudt/",
    "unit": "http://qudt.org/vocab/unit/",
    "geo": "http://www.w3.org/2003/01/geo/wgs84_pos#",
    
    "TraceableUnit": {
      "@id": "boost:TraceableUnit", 
      "@context": {
        "totalVolumeM3": {
          "@type": "qudt:QuantityValue",
          "qudt:hasUnit": "unit:M3"
        },
        "harvestLocation": {
          "@type": "geo:Point"
        }
      }
    }
  }
}
43.1.4.2. Validation Requirements

Systems MUST:

44. JSON-LD Context and Semantic Web Integration

BOOST implements JSON-LD (JSON for Linking Data) as its primary serialization format, enabling semantic web compatibility, data linking, and machine-readable context definitions. This section explains the JSON-LD context structure, semantic annotations, and integration with existing ontologies.

44.1. JSON-LD Overview

JSON-LD extends standard JSON with semantic web capabilities through:

44.2. BOOST Context Definition

The BOOST JSON-LD context maps entity properties to established vocabularies:

{
  "@context": {
    "schema": "http://schema.org/",
    "prov": "http://www.w3.org/ns/prov#",
    "gs1": "https://gs1.org/voc/",
    "biomass": "http://example.org/biomass#",
    "geo": "http://www.w3.org/2003/01/geo/wgs84_pos#",
    "qudt": "http://qudt.org/schema/qudt/",
    "unit": "http://qudt.org/vocab/unit/",
    
    "TraceableUnit": "biomass:TraceableUnit",
    "Organization": "schema:Organization",
    "Transaction": "schema:Order",
    "MaterialProcessing": "prov:Activity",
    
    "traceableUnitId": {
      "@id": "schema:identifier",
      "@type": "schema:Text"
    },
    "organizationId": {
      "@id": "schema:identifier",
      "@type": "schema:Text"
    },
    "createdAt": {
      "@id": "schema:dateCreated",
      "@type": "xsd:dateTime"
    },
    "modifiedAt": {
      "@id": "schema:dateModified",
      "@type": "xsd:dateTime"
    }
  }
}

44.3. Vocabulary Mappings

44.3.1. Schema.org Integration

BOOST entities map to Schema.org types for web compatibility:

44.3.2. W3C PROV Ontology

Provenance tracking using PROV vocabulary:

44.3.3. GS1 Vocabulary

Supply chain standards alignment:

44.4. Entity Context Examples

44.4.1. TraceableUnit with Context

Complete JSON-LD representation of a TraceableUnit:

{
  "@context": "https://boost.org/context.jsonld",
  "@type": "biomass:TraceableUnit",
  "@id": "https://example.org/tru/TRU-2025-001",
  
  "traceableUnitId": "TRU-2025-001",
  "unitType": "pile",
  "totalVolume": {
    "@type": "qudt:QuantityValue",
    "qudt:value": 500.0,
    "qudt:unit": "unit:M3"
  },
  "speciesComposition": [{
    "@type": "biomass:SpeciesComponent",
    "species": "Pseudotsuga menziesii",
    "percentage": 75.0
  }],
  "harvestLocation": {
    "@type": "geo:Point",
    "geo:lat": 45.5231,
    "geo:long": -122.6765
  },
  "prov:wasGeneratedBy": {
    "@id": "https://example.org/harvest/HARV-2025-001"
  },
  "prov:wasAttributedTo": {
    "@id": "https://example.org/org/ORG-FOREST-001"
  }
}

44.4.2. Transaction with Linked Data

Transaction linking multiple entities:

{
  "@context": "https://boost.org/context.jsonld",
  "@type": "schema:Order",
  "@id": "https://example.org/txn/TXN-2025-001",
  
  "transactionId": "TXN-2025-001",
  "schema:seller": {
    "@id": "https://example.org/org/ORG-SUPPLIER-001"
  },
  "schema:buyer": {
    "@id": "https://example.org/org/ORG-BUYER-001"
  },
  "schema:orderedItem": [{
    "@id": "https://example.org/tru/TRU-2025-001"
  }],
  "schema:price": {
    "@type": "schema:PriceSpecification",
    "schema:price": 85.50,
    "schema:priceCurrency": "USD"
  },
  "prov:startedAtTime": "2025-01-15T09:00:00Z",
  "prov:endedAtTime": "2025-01-15T14:30:00Z"
}

44.5. Advanced Features

44.5.1. Named Graphs

Support for multi-source data using named graphs:

{
  "@context": "https://boost.org/context.jsonld",
  "@graph": [{
    "@id": "https://example.org/graph/supplier",
    "@graph": [
      {
        "@type": "Organization",
        "organizationId": "ORG-001",
        "name": "Forest Products Inc"
      }
    ]
  }, {
    "@id": "https://example.org/graph/certification",
    "@graph": [
      {
        "@type": "Certificate",
        "certificateId": "CERT-FSC-001",
        "issuedTo": {"@id": "ORG-001"}
      }
    ]
  }]
}

44.5.2. Framing

JSON-LD framing for specific data views:

{
  "@context": "https://boost.org/context.jsonld",
  "@type": "TraceableUnit",
  "harvestedBy": {
    "@type": "Organization",
    "certifications": {
      "@type": "Certificate",
      "certificationType": "FSC"
    }
  }
}

44.5.3. Compaction and Expansion

BOOST supports JSON-LD algorithms:

44.6. Context Negotiation

44.6.1. Content Type Headers

HTTP content negotiation support:

44.6.2. Profile Parameters

Profile-based context selection:

Accept: application/ld+json; 
        profile="https://boost.org/profiles/extended"

44.7. Implementation Guidance

44.7.1. Python Implementation

Using PyLD library for JSON-LD processing:

from pyld import jsonld
import json

# Load BOOST context
with open('boost_context.jsonld') as f:
    context = json.load(f)

# Create entity with context
tru = {
    "@context": context,
    "@type": "TraceableUnit",
    "traceableUnitId": "TRU-001",
    "totalVolume": 100.0
}

# Expand to full IRIs
expanded = jsonld.expand(tru)

# Compact with custom context
compacted = jsonld.compact(expanded, context)

# Convert to RDF
rdf = jsonld.to_rdf(tru)

# Frame for specific view
frame = {"@type": "TraceableUnit"}
framed = jsonld.frame(tru, frame)

44.7.2. JavaScript Implementation

Browser and Node.js support:

const jsonld = require('jsonld');

// Process BOOST data
async function processBoostData(data) {
  // Add context
  data['@context'] = 'https://boost.org/context.jsonld';
  
  // Validate structure
  const expanded = await jsonld.expand(data);
  
  // Generate RDF
  const nquads = await jsonld.toRDF(data, {format: 'N-Quads'});
  
  return nquads;
}

44.8. Semantic Validation

44.8.1. SHACL Constraints

Shape validation for semantic correctness:

{
  "@context": {"sh": "http://www.w3.org/ns/shacl#"},
  "@type": "sh:NodeShape",
  "sh:targetClass": "biomass:TraceableUnit",
  "sh:property": [{
    "sh:path": "biomass:totalVolume",
    "sh:datatype": "xsd:decimal",
    "sh:minInclusive": 0,
    "sh:maxInclusive": 10000
  }]
}

44.8.2. Reasoning and Inference

Automatic inference capabilities:

44.9. Benefits and Use Cases

44.9.1. Interoperability Benefits

44.9.2. Supply Chain Use Cases

The JSON-LD context provides BOOST with semantic web capabilities essential for modern supply chain interoperability and regulatory compliance.

45. Regulatory Program Compliance

The BOOST standard provides comprehensive support for regulatory compliance across multiple biofuel programs, with specialized frameworks for the California Low Carbon Fuel Standard (LCFS), EPA Renewable Fuel Standard (RFS), and EU Renewable Energy Directive (RED II). This section documents complete programmatic reporting workflows, compliance requirements, and implementation guidance for regulatory submissions.

45.1. California Low Carbon Fuel Standard (LCFS)

45.1.1. LCFS Program Overview

The California Low Carbon Fuel Standard, administered by the California Air Resources Board (CARB), is California’s market-based regulation designed to reduce greenhouse gas emissions from transportation fuels by 20% below 2010 levels by 2030. The program creates economic incentives for low-carbon fuels through a credit trading system based on carbon intensity benchmarks.

45.1.1.1. Regulatory Background

Program Administration:

Key Regulatory Concepts:

Regulated Parties:

45.1.1.2. CARB Reporting Requirements

Quarterly Reporting Timeline:

Required Reporting Elements:

Key Regulatory Terms:

45.1.2. BOOST’s Role in LCFS Compliance

BOOST provides a comprehensive framework for LCFS compliance by integrating supply chain traceability with regulatory reporting requirements:

Supply Chain Integration:

Regulatory Compliance Support:

45.2. LCFS Entity Integration

45.2.1. Core LCFS Entities

BOOST provides specialized entities for LCFS compliance that extend core supply chain entities with regulatory-specific attributes:

45.2.1.1. LcfsPathway Entity

The LcfsPathway entity manages CARB-certified fuel pathways with complete regulatory attributes:

Required Fields:

Optional Fields:

Pathway Validation Rules:

// Pathway must be active for transaction date
function validatePathwayStatus(pathway, transactionDate) {
    const certDate = new Date(pathway.certificationDate);
    const expDate = new Date(pathway.expirationDate);
    const txnDate = new Date(transactionDate);
    
    return txnDate >= certDate && 
           txnDate <= expDate && 
           pathway.verificationStatus === 'active';
}

// Carbon intensity must align with CARB specifications
function validateCarbonIntensity(pathway, carbDatabase) {
    const officialCI = carbDatabase.getPathwayCI(pathway.lcfsPathwayId);
    return Math.abs(pathway.carbonIntensity - officialCI) < 0.01;
}
45.2.1.2. Enhanced Transaction Entity

Standard BOOST Transaction entities are enhanced with LCFS-specific fields for regulatory compliance:

LCFS Extension Fields:

Credit Calculation Fields:

45.2.1.3. LcfsReporting Entity

Quarterly aggregation entity for CARB submissions:

Primary Aggregation Fields:

Aggregated Metrics:

Verification Fields:

45.2.2. Entity Relationships and Data Flow

The LCFS compliance workflow creates specific relationships between BOOST entities:

Entity Relationship Flow:
Organization → operates → LcfsPathway
LcfsPathway → certifies → Transaction  
Transaction → aggregates to → LcfsReporting
Transaction → references → TraceableUnit
TraceableUnit → sources from → Material
Material → has composition → SpeciesComponent
Organization → submits → LcfsReporting
LcfsReporting → verified by → VerificationStatement

Additional relationships:
EnergyCarbonData → calculates CI for → LcfsPathway
Certificate → validates sustainability → TraceableUnit
GeographicData → documents origin → TraceableUnit

Key Relationship Rules:

45.3. Programmatic Reporting Workflows

45.3.1. Complete LCFS Compliance Workflow

The end-to-end LCFS compliance process using BOOST involves seven phases:

45.3.1.1. Phase 1: Pathway Registration and Management

Initial Pathway Setup:

# Create LcfsPathway entity for CARB-certified pathway
renewable_diesel_pathway = {
    "lcfsPathwayId": "CA-RD-2025-LMR-001",
    "pathwayType": "Tier_1",
    "feedstockCategory": "logging_and_mill_residue",
    "fuelProduct": "renewable_diesel", 
    "carbonIntensity": 19.85,
    "energyEconomyRatio": 1.0,
    "certificationDate": "2025-01-15",
    "expirationDate": "2030-12-31",
    "verificationStatus": "active",
    "caGreetVersion": "CA-GREET3.0",
    "facilityLocation": "Stockton, CA"
}

Ongoing Pathway Monitoring:

45.3.1.2. Phase 2: Supply Chain Data Collection

Feedstock Tracking:

Integration with BOOST Traceability:

45.3.1.3. Phase 3: Fuel Transaction Recording

Transaction Data Capture:

# Example LCFS transaction with complete regulatory attributes
lcfs_transaction = {
    "transactionId": "TXN-2025-Q1-001", 
    "transactionType": "fuel_sale",
    "transactionDate": "2025-03-15",
    "organizationId": "ORG-PACIFIC-001",
    "customerId": "CUST-FUEL-DIST-001",
    
    # LCFS-specific fields
    "lcfsPathwayId": "CA-RD-2025-LMR-001",
    "fuelVolume": 875000.0,
    "fuelVolumeUnit": "gallons",
    "fuelCategory": "renewable_diesel",
    "reportingPeriod": "2025-Q1",
    "regulatedPartyRole": "producer",
    
    # Credit calculation fields
    "benchmarkCI": 98.47,
    "actualCI": 19.85,
    "energyEconomyRatio": 1.0,
    "creditsGenerated": 9543945.25,
    
    # Traceability linkages
    "traceableUnitIds": ["TRU-FOREST-RES-001", "TRU-FOREST-RES-002"],
    "sustainabilityClaims": ["FSC_certified", "CARB_compliant"]
}

Data Validation Rules:

45.3.1.4. Phase 4: Credit and Deficit Calculations

CARB Credit Calculation Formula: The official LCFS credit calculation uses:

Credits = (EBenchmark - EPathway) × Fuel_Volume × 0.000001

Where:
EBenchmark = Benchmark_CI × Energy_Density × EER
EPathway = Pathway_CI × Energy_Density × EER

Detailed Calculation Example:

def calculate_lcfs_credits(transaction):
    # Standard values for renewable diesel
    energy_density = 138.7  # MJ/gallon for renewable diesel
    benchmark_ci = 98.47    # 2025 diesel benchmark (gCO2e/MJ)
    pathway_ci = 19.85      # Logging residue pathway CI
    eer = 1.0               # Heavy-duty diesel application
    fuel_volume = 875000    # gallons
    
    # Energy calculations
    e_benchmark = benchmark_ci * energy_density * eer
    e_pathway = pathway_ci * energy_density * eer
    
    # Credit calculation
    credits = (e_benchmark - e_pathway) * fuel_volume * 0.000001
    
    return {
        "credits_generated": credits,
        "e_benchmark": e_benchmark,
        "e_pathway": e_pathway,
        "ci_reduction": benchmark_ci - pathway_ci,
        "co2_reduction_mt": credits  # 1 credit = 1 MT CO2e
    }

Real-World Calculation Result:

result = calculate_lcfs_credits(lcfs_transaction)
# Output:
{
    "credits_generated": 9543945.25,
    "e_benchmark": 13657.139,
    "e_pathway": 2754.1955,
    "ci_reduction": 78.62,
    "co2_reduction_mt": 9543945.25
}
45.3.1.5. Phase 5: Quarterly Report Generation

Automated Report Aggregation:

def generate_quarterly_lcfs_report(organization_id, reporting_period):
    # Aggregate all transactions for reporting period
    transactions = get_transactions_by_period(organization_id, reporting_period)
    
    # Group transactions by pathway
    pathway_groups = group_transactions_by_pathway(transactions)
    
    # Calculate aggregated metrics
    report_data = {
        "lcfsReportId": f"LCFS-{organization_id}-{reporting_period}",
        "organizationId": organization_id,
        "reportingPeriod": reporting_period,
        "reportingDeadline": get_carb_deadline(reporting_period),
        "reportStatus": "draft",
        
        # Aggregated totals
        "totalFuelVolume": sum(t.fuel_volume for t in transactions),
        "totalCreditsGenerated": sum(t.credits_generated for t in transactions),
        "totalDeficitsIncurred": sum(t.deficits_incurred for t in transactions),
        "netPosition": sum(t.credits_generated - t.deficits_incurred for t in transactions),
        
        # Pathway breakdown
        "pathwayBreakdown": [
            {
                "pathwayId": pathway_id,
                "fuelVolume": sum(t.fuel_volume for t in group),
                "creditsGenerated": sum(t.credits_generated for t in group),
                "transactionCount": len(group),
                "averageCI": sum(t.actual_ci for t in group) / len(group)
            }
            for pathway_id, group in pathway_groups.items()
        ],
        
        # Verification requirements
        "verificationRequired": calculate_verification_threshold(transactions),
        "verificationStatus": "pending" if verification_required else "not_required"
    }
    
    return LcfsReporting(**report_data)
45.3.1.6. Phase 6: Data Quality Validation

Pre-Submission Validation Checklist:

Completeness Validation:

Accuracy Validation:

Consistency Validation:

45.3.1.7. Phase 7: Regulatory Submission and Compliance Monitoring

CARB Submission Process:

  1. Export to CARB Format: Convert BOOST data to CARB-required XML format

  2. LRT-CBTS Upload: Submit through CARB’s online reporting system

  3. Validation Processing: Monitor CARB validation results and error reports

  4. Correction Submission: Submit corrections for any identified errors

  5. Final Acceptance: Confirm CARB acceptance of quarterly report

Compliance Monitoring:

45.3.2. Pacific Renewable Fuels Case Study

Complete Q1 2025 LCFS Implementation Example

This comprehensive example demonstrates BOOST’s LCFS compliance capabilities using Pacific Renewable Fuels Corp, a renewable diesel producer operating in Stockton, California.

45.3.2.1. Company Profile
45.3.2.2. Q1 2025 Production Summary

| Metric | Value | Unit | |--------|--------|------| | Total Fuel Volume | 5.075 | Million gallons | | Total Credits Generated | 54.58 | Million LCFS credits | | Estimated Credit Value | $109.16 | Million USD (at $2.00/credit) | | Average CI Reduction | 78.39 | gCO2e/MJ below benchmark | | CO2 Reduction Achievement | 55,249 | Metric tons CO2e | | Number of Transactions | 6 | Quarterly fuel sales | | Pathways Utilized | 4 | Different CARB-certified pathways |

45.3.2.3. Pathway Performance Analysis

| Pathway ID | Feedstock Type | Volume (gal) | Credits Generated | CI (gCO2e/MJ) | CI Reduction | |------------|----------------|--------------|-------------------|---------------|--------------| | CA-RD-2025-LMR-001 | Logging & Mill Residue | 1,650,000 | 17.99M | 19.85 | 78.62 | | CA-RD-2025-AGR-001 | Agricultural Residue | 2,350,000 | 24.89M | 22.14 | 76.33 | | CA-RD-2025-GRW-001 | Grass Residue Waste | 650,000 | 7.17M | 18.92 | 79.55 | | CA-RD-2025-FHR-001 | Forest Harvest Residue | 425,000 | 4.53M | 21.67 | 76.80 |

45.3.2.4. Detailed Transaction Example

Transaction TXN-2025-Q1-001 (Largest Volume):

{
  "@context": "https://boost-standard.org/context.jsonld",
  "@type": "Transaction",
  "@id": "https://pacificrenwable.com/transactions/TXN-2025-Q1-001",
  
  "transactionId": "TXN-2025-Q1-001",
  "transactionType": "fuel_sale",
  "transactionDate": "2025-03-15T10:30:00Z",
  "organizationId": "ORG-PACIFIC-001",
  "customerId": "CUST-FUEL-DIST-001",
  
  "fuelVolume": 875000.0,
  "fuelVolumeUnit": "gallons", 
  "fuelCategory": "renewable_diesel",
  "lcfsPathwayId": "CA-RD-2025-LMR-001",
  "reportingPeriod": "2025-Q1",
  "regulatedPartyRole": "producer",
  
  "benchmarkCI": 98.47,
  "actualCI": 19.85,
  "energyEconomyRatio": 1.0,
  "creditsGenerated": 9543945.25,
  "deficitsIncurred": 0.0,
  
  "traceableUnitIds": ["TRU-LOGGING-RES-001", "TRU-MILL-RES-001"],
  "sustainabilityClaims": ["FSC_certified", "SFI_certified", "CARB_compliant"],
  "verificationStatus": "verified",
  
  "contractValue": 2625000.0,
  "contractValueCurrency": "USD",
  "paymentTerms": "Net 30"
}

Credit Calculation Details:

Fuel Volume: 875,000 gallons
Energy Density: 138.7 MJ/gallon (renewable diesel)
Total Energy: 875,000 × 138.7 = 121,362,500 MJ

Benchmark CI: 98.47 gCO2e/MJ (2025 diesel benchmark)
Pathway CI: 19.85 gCO2e/MJ (logging residue pathway)
CI Reduction: 98.47 - 19.85 = 78.62 gCO2e/MJ

Credits = 78.62 × 121,362,500 × 0.000001 = 9,543,945 credits
45.3.2.5. Quarterly Report Generation
{
  "@context": "https://boost-standard.org/context.jsonld",
  "@type": "LcfsReporting",
  "@id": "https://pacificrenewable.com/reports/LCFS-2025-Q1",
  
  "lcfsReportId": "LCFS-PACIFIC-2025-Q1",
  "organizationId": "ORG-PACIFIC-001", 
  "reportingPeriod": "2025-Q1",
  "reportingDeadline": "2025-05-15",
  "submissionDate": "2025-05-10T14:25:00Z",
  "reportStatus": "submitted",
  
  "totalFuelVolume": 5075000.0,
  "totalCreditsGenerated": 54580477.10,
  "totalDeficitsIncurred": 0.0,
  "netPosition": 54580477.10,
  "complianceStatus": "compliant",
  
  "verificationRequired": true,
  "verificationBodyId": "VB-CARB-ACC-001",
  "verificationDate": "2025-05-08",
  "verificationStatus": "verified",
  
  "pathwayBreakdown": [
    {
      "pathwayId": "CA-RD-2025-LMR-001",
      "fuelVolume": 1650000.0,
      "creditsGenerated": 17990254.75,
      "transactionCount": 2,
      "averageCI": 19.85
    },
    {
      "pathwayId": "CA-RD-2025-AGR-001", 
      "fuelVolume": 2350000.0,
      "creditsGenerated": 24888836.15,
      "transactionCount": 2,
      "averageCI": 22.14
    },
    {
      "pathwayId": "CA-RD-2025-GRW-001",
      "fuelVolume": 650000.0,
      "creditsGenerated": 7168722.35,
      "transactionCount": 1,
      "averageCI": 18.92
    },
    {
      "pathwayId": "CA-RD-2025-FHR-001",
      "fuelVolume": 425000.0,
      "creditsGenerated": 4532663.85,
      "transactionCount": 1,
      "averageCI": 21.67
    }
  ]
}

45.3.3. Implementation Examples

45.3.3.1. Python Implementation for Credit Calculation
class LCFSCreditCalculator:
    """
    LCFS credit calculation engine using BOOST entities
    Implements official CARB calculation methodology
    """
    
    # 2025 CARB benchmark values (gCO2e/MJ)
    BENCHMARKS_2025 = {
        'gasoline': 95.61,
        'diesel': 98.47, 
        'jet_fuel': 89.0,
        'natural_gas': 78.8
    }
    
    # Energy density values (MJ/gallon)
    ENERGY_DENSITIES = {
        'renewable_diesel': 138.7,
        'biodiesel': 126.2,
        'ethanol': 84.5,
        'renewable_gasoline': 125.0
    }
    
    def calculate_transaction_credits(self, transaction, pathway):
        """
        Calculate LCFS credits for a single transaction
        
        Args:
            transaction: BOOST Transaction entity with LCFS fields
            pathway: BOOST LcfsPathway entity
            
        Returns:
            dict: Credit calculation results with detailed breakdown
        """
        # Validate inputs
        self._validate_transaction(transaction)
        self._validate_pathway(pathway, transaction.transactionDate)
        
        # Get benchmark and energy values
        fuel_category = transaction.fuelCategory
        benchmark_ci = self.BENCHMARKS_2025.get(
            fuel_category.replace('renewable_', '')
        )
        energy_density = self.ENERGY_DENSITIES[fuel_category]
        
        # Calculate energy values
        fuel_volume = transaction.fuelVolume
        total_energy = fuel_volume * energy_density  # MJ
        
        pathway_ci = pathway.carbonIntensity
        eer = pathway.energyEconomyRatio
        
        # CARB credit formula
        e_benchmark = benchmark_ci * energy_density * eer
        e_pathway = pathway_ci * energy_density * eer
        
        credits = (e_benchmark - e_pathway) * fuel_volume * 0.000001
        
        return {
            'credits_generated': max(0, credits),
            'deficits_incurred': max(0, -credits),
            'total_energy_mj': total_energy,
            'benchmark_ci': benchmark_ci,
            'pathway_ci': pathway_ci,
            'ci_reduction': benchmark_ci - pathway_ci,
            'co2_reduction_mt': max(0, credits),
            'energy_economy_ratio': eer,
            'calculation_details': {
                'e_benchmark': e_benchmark,
                'e_pathway': e_pathway, 
                'fuel_volume': fuel_volume,
                'energy_density': energy_density
            }
        }
    
    def _validate_transaction(self, transaction):
        """Validate transaction has required LCFS fields"""
        required_fields = [
            'fuelVolume', 'fuelCategory', 'lcfsPathwayId', 
            'reportingPeriod', 'transactionDate'
        ]
        for field in required_fields:
            if not hasattr(transaction, field) or getattr(transaction, field) is None:
                raise ValueError(f"Transaction missing required LCFS field: {field}")
    
    def _validate_pathway(self, pathway, transaction_date):
        """Validate pathway is active for transaction date"""
        if pathway.verificationStatus != 'active':
            raise ValueError(f"Pathway {pathway.lcfsPathwayId} is not active")
        
        cert_date = datetime.fromisoformat(pathway.certificationDate)
        exp_date = datetime.fromisoformat(pathway.expirationDate) 
        txn_date = datetime.fromisoformat(transaction_date)
        
        if not (cert_date <= txn_date <= exp_date):
            raise ValueError(
                f"Transaction date {transaction_date} outside pathway validity "
                f"period {pathway.certificationDate} to {pathway.expirationDate}"
            )

# Usage example
calculator = LCFSCreditCalculator()

# Calculate credits for Pacific Renewable Fuels transaction
result = calculator.calculate_transaction_credits(
    transaction=lcfs_transaction,
    pathway=renewable_diesel_pathway
)

print(f"Credits Generated: {result['credits_generated']:,.0f}")
print(f"CO2 Reduction: {result['co2_reduction_mt']:,.0f} MT")
print(f"CI Reduction: {result['ci_reduction']:.2f} gCO2e/MJ")
45.3.3.2. Quarterly Report Generation System
class LCFSQuarterlyReporter:
    """
    Automated quarterly report generation for CARB submission
    Integrates with BOOST entities and validation systems
    """
    
    def __init__(self, boost_client, carb_api_client=None):
        self.boost = boost_client
        self.carb_api = carb_api_client
        self.calculator = LCFSCreditCalculator()
    
    def generate_quarterly_report(self, organization_id, reporting_period):
        """
        Generate complete quarterly LCFS report
        
        Args:
            organization_id: BOOST Organization ID
            reporting_period: Quarter in YYYY-Q# format
            
        Returns:
            LcfsReporting: Complete quarterly report entity
        """
        # Step 1: Collect all transactions for reporting period
        transactions = self.boost.get_transactions(
            organization_id=organization_id,
            reporting_period=reporting_period,
            transaction_type='fuel_sale'
        )
        
        if not transactions:
            raise ValueError(f"No fuel transactions found for {reporting_period}")
        
        # Step 2: Validate and calculate credits for each transaction
        validated_transactions = []
        total_credits = 0
        total_deficits = 0
        total_volume = 0
        
        for transaction in transactions:
            # Get associated pathway
            pathway = self.boost.get_lcfs_pathway(transaction.lcfsPathwayId)
            
            # Calculate credits
            credit_result = self.calculator.calculate_transaction_credits(
                transaction, pathway
            )
            
            # Update transaction with calculated values
            transaction.creditsGenerated = credit_result['credits_generated']
            transaction.deficitsIncurred = credit_result['deficits_incurred']
            transaction.benchmarkCI = credit_result['benchmark_ci']
            transaction.actualCI = credit_result['pathway_ci']
            
            validated_transactions.append(transaction)
            total_credits += credit_result['credits_generated']
            total_deficits += credit_result['deficits_incurred']
            total_volume += transaction.fuelVolume
        
        # Step 3: Generate pathway breakdown analysis
        pathway_breakdown = self._generate_pathway_breakdown(validated_transactions)
        
        # Step 4: Check verification requirements
        verification_required = total_credits + total_deficits > 15000  # >15,000 MT CO2e
        
        # Step 5: Create quarterly report entity
        report = LcfsReporting(
            lcfsReportId=f"LCFS-{organization_id}-{reporting_period}",
            organizationId=organization_id,
            reportingPeriod=reporting_period,
            reportingDeadline=self._get_carb_deadline(reporting_period),
            reportStatus="draft",
            
            totalFuelVolume=total_volume,
            totalCreditsGenerated=total_credits,
            totalDeficitsIncurred=total_deficits,
            netPosition=total_credits - total_deficits,
            
            verificationRequired=verification_required,
            verificationStatus="pending" if verification_required else "not_required",
            
            pathwayBreakdown=pathway_breakdown,
            transactionIds=[t.transactionId for t in validated_transactions]
        )
        
        # Step 6: Run validation checks
        validation_results = self._validate_quarterly_report(report, validated_transactions)
        if not validation_results['valid']:
            raise ValueError(f"Report validation failed: {validation_results['errors']}")
        
        return report
    
    def _generate_pathway_breakdown(self, transactions):
        """Generate pathway-level aggregation for quarterly report"""
        pathway_groups = {}
        
        for transaction in transactions:
            pathway_id = transaction.lcfsPathwayId
            
            if pathway_id not in pathway_groups:
                pathway_groups[pathway_id] = {
                    'pathwayId': pathway_id,
                    'fuelVolume': 0,
                    'creditsGenerated': 0,
                    'deficitsIncurred': 0,
                    'transactionCount': 0,
                    'ci_values': []
                }
            
            group = pathway_groups[pathway_id]
            group['fuelVolume'] += transaction.fuelVolume
            group['creditsGenerated'] += transaction.creditsGenerated
            group['deficitsIncurred'] += transaction.deficitsIncurred
            group['transactionCount'] += 1
            group['ci_values'].append(transaction.actualCI)
        
        # Calculate averages
        for group in pathway_groups.values():
            group['averageCI'] = sum(group['ci_values']) / len(group['ci_values'])
            del group['ci_values']  # Remove working array
        
        return list(pathway_groups.values())
    
    def _get_carb_deadline(self, reporting_period):
        """Get CARB submission deadline for reporting period"""
        year, quarter = reporting_period.split('-')
        year = int(year)
        quarter = int(quarter[1])
        
        deadlines = {
            1: f"{year}-05-15",  # Q1 due May 15
            2: f"{year}-08-15",  # Q2 due Aug 15  
            3: f"{year}-11-15",  # Q3 due Nov 15
            4: f"{year+1}-02-15" # Q4 due Feb 15 next year
        }
        
        return deadlines[quarter]
    
    def export_to_carb_xml(self, report, output_file):
        """Export quarterly report to CARB XML format"""
        # Implementation would generate CARB-compliant XML
        # This is a simplified example showing the structure
        
        xml_template = """<?xml version="1.0" encoding="UTF-8"?>
        <LCFSQuarterlyReport>
            <ReportHeader>
                <ReportID>{report_id}</ReportID>
                <OrganizationID>{org_id}</OrganizationID>
                <ReportingPeriod>{period}</ReportingPeriod>
                <SubmissionDate>{submission_date}</SubmissionDate>
            </ReportHeader>
            <FuelTransactions>
                {transaction_xml}
            </FuelTransactions>
            <Summary>
                <TotalFuelVolume>{total_volume}</TotalFuelVolume>
                <TotalCredits>{total_credits}</TotalCredits>
                <TotalDeficits>{total_deficits}</TotalDeficits>
                <NetPosition>{net_position}</NetPosition>
            </Summary>
        </LCFSQuarterlyReport>"""
        
        # Generate transaction XML for each pathway
        transaction_xml_parts = []
        for pathway in report.pathwayBreakdown:
            transaction_xml_parts.append(f"""
                <PathwayGroup>
                    <PathwayID>{pathway['pathwayId']}</PathwayID>
                    <FuelVolume>{pathway['fuelVolume']}</FuelVolume>
                    <CreditsGenerated>{pathway['creditsGenerated']}</CreditsGenerated>
                </PathwayGroup>
            """)
        
        # Format complete XML
        xml_content = xml_template.format(
            report_id=report.lcfsReportId,
            org_id=report.organizationId,
            period=report.reportingPeriod,
            submission_date=datetime.now().isoformat(),
            transaction_xml=''.join(transaction_xml_parts),
            total_volume=report.totalFuelVolume,
            total_credits=report.totalCreditsGenerated,
            total_deficits=report.totalDeficitsIncurred,
            net_position=report.netPosition
        )
        
        with open(output_file, 'w') as f:
            f.write(xml_content)
        
        return output_file

# Complete workflow example
reporter = LCFSQuarterlyReporter(boost_client)

# Generate Q1 2025 report for Pacific Renewable Fuels
q1_report = reporter.generate_quarterly_report(
    organization_id="ORG-PACIFIC-001",
    reporting_period="2025-Q1"
)

# Export for CARB submission
reporter.export_to_carb_xml(
    report=q1_report,
    output_file="pacific_renewable_q1_2025_submission.xml"
)

print(f"Generated report with {q1_report.totalCreditsGenerated:,.0f} credits")
print(f"Net position: {q1_report.netPosition:,.0f} credits")

45.4. Multi-Program Compliance Framework

45.4.1. EPA Renewable Fuel Standard (RFS) Integration

BOOST’s regulatory compliance framework extends beyond LCFS to support the EPA Renewable Fuel Standard and other biofuel programs:

45.4.1.1. RFS Program Overview
45.4.1.2. BOOST RFS Extensions

Enhanced Transaction Fields:

RFS Reporting Entity:

45.4.2. EU Renewable Energy Directive (RED II) Compliance

45.4.2.1. RED II Requirements
45.4.2.2. BOOST RED II Extensions

Sustainability Tracking:

45.4.3. Regional Program Support

45.4.3.1. State-Level Clean Fuel Programs

Oregon Clean Fuels Program:

Washington Clean Fuel Standard:

British Columbia Low Carbon Fuel Standard:

45.4.3.2. Implementation Strategy for Multi-Program Compliance

Unified Entity Model:

class MultiProgramTransaction(Transaction):
    """
    Extended transaction entity supporting multiple regulatory programs
    """
    # LCFS fields
    lcfs_pathway_id: str = None
    lcfs_credits_generated: float = 0
    
    # RFS fields  
    rin_generated: str = None
    d_code: str = None
    epa_pathway_id: str = None
    
    # RED II fields
    ghg_savings_percent: float = None
    certification_scheme: str = None
    iluc_risk: bool = False
    
    # Regional programs
    oregon_cfp_credits: float = 0
    washington_cfs_credits: float = 0
    bc_lcfs_credits: float = 0
    
    def calculate_all_programs(self):
        """Calculate credits/RINs for all applicable programs"""
        results = {}
        
        if self.lcfs_pathway_id:
            results['lcfs'] = self._calculate_lcfs_credits()
        
        if self.epa_pathway_id:
            results['rfs'] = self._calculate_rfs_rins()
        
        if self.certification_scheme:
            results['red_ii'] = self._validate_red_ii_compliance()
        
        return results

45.5. Data Quality and Compliance

45.5.1. CARB Data Validation Requirements

45.5.1.1. Completeness Requirements

Transaction Coverage:

Data Integrity Checks:

class CARBValidationEngine:
    """CARB-specific validation rules for BOOST data"""
    
    def validate_quarterly_completeness(self, organization, reporting_period):
        """Validate 100% transaction coverage requirement"""
        
        # Get all fuel inventory movements for quarter
        inventory_movements = self.get_inventory_movements(organization, reporting_period)
        
        # Get all reported transactions
        reported_transactions = self.get_lcfs_transactions(organization, reporting_period)
        
        # Calculate volumes
        inventory_volume = sum(m.volume for m in inventory_movements)
        reported_volume = sum(t.fuel_volume for t in reported_transactions)
        
        # CARB allows 0.5% tolerance for volume differences
        volume_difference = abs(inventory_volume - reported_volume)
        tolerance_threshold = inventory_volume * 0.005
        
        if volume_difference > tolerance_threshold:
            return ValidationResult(
                valid=False,
                error=f"Volume reconciliation failed: {volume_difference:.2f} gallon difference "
                      f"exceeds {tolerance_threshold:.2f} gallon tolerance"
            )
        
        return ValidationResult(valid=True)
    
    def validate_pathway_assignments(self, transactions):
        """Validate all pathway assignments are correct and active"""
        
        validation_errors = []
        
        for transaction in transactions:
            pathway = self.get_carb_pathway(transaction.lcfs_pathway_id)
            
            # Check pathway is active for transaction date
            if not self.is_pathway_active(pathway, transaction.transaction_date):
                validation_errors.append(
                    f"Transaction {transaction.transaction_id} uses inactive pathway "
                    f"{pathway.lcfs_pathway_id} on {transaction.transaction_date}"
                )
            
            # Check feedstock alignment
            if not self.validate_feedstock_alignment(transaction, pathway):
                validation_errors.append(
                    f"Transaction {transaction.transaction_id} feedstock does not align "
                    f"with pathway {pathway.lcfs_pathway_id} specifications"
                )
        
        return ValidationResult(
            valid=len(validation_errors) == 0,
            errors=validation_errors
        )
45.5.1.2. Accuracy Standards

Measurement Precision Requirements:

Quality Control Procedures:

  1. Automated Validation: Run validation checks before each quarterly submission

  2. Cross-Reference Verification: Validate all external data against authoritative sources

  3. Statistical Analysis: Monitor for unusual patterns that might indicate data errors

  4. Exception Reporting: Flag transactions that fall outside normal parameters

45.5.2. Third-Party Verification Requirements

45.5.2.1. Verification Thresholds

Mandatory Verification:

Verification Timeline:

45.5.2.2. BOOST Support for Verification

Audit Trail Maintenance:

class VerificationAuditTrail:
    """Comprehensive audit trail system for third-party verification"""
    
    def generate_verification_package(self, organization_id, verification_period):
        """Generate complete data package for verifier review"""
        
        package = {
            'organization_profile': self.get_organization_details(organization_id),
            'pathway_certifications': self.get_pathway_documentation(organization_id),
            'transaction_records': self.get_all_transactions(organization_id, verification_period),
            'feedstock_documentation': self.get_feedstock_traceability(organization_id, verification_period),
            'calculation_worksheets': self.generate_credit_calculations(organization_id, verification_period),
            'supporting_certificates': self.get_sustainability_certificates(organization_id),
            'quality_control_records': self.get_qc_documentation(organization_id, verification_period),
            'system_controls': self.document_data_management_controls(organization_id)
        }
        
        return package
    
    def track_verifier_findings(self, finding):
        """Track and manage verifier findings with corrective actions"""
        
        finding_record = VerificationFinding(
            finding_id=self.generate_finding_id(),
            verification_body_id=finding.verifier_id,
            organization_id=finding.organization_id,
            finding_type=finding.finding_type,  # 'non_conformity', 'observation', 'clarification'
            description=finding.description,
            affected_transactions=finding.transaction_ids,
            corrective_action_required=finding.finding_type == 'non_conformity',
            status='open',
            due_date=self.calculate_due_date(finding.finding_type)
        )
        
        return finding_record

Verifier Data Access:

45.5.3. Regulatory Change Management

45.5.3.1. Adaptive Framework for Regulatory Updates

Change Detection System:

class RegulatoryChangeManager:
    """Monitor and adapt to regulatory requirement changes"""
    
    def monitor_carb_updates(self):
        """Monitor CARB website and database for regulatory changes"""
        
        # Check for pathway updates
        current_pathways = self.get_carb_pathway_database()
        stored_pathways = self.get_boost_pathway_cache()
        
        pathway_changes = self.compare_pathway_databases(current_pathways, stored_pathways)
        
        if pathway_changes:
            self.process_pathway_updates(pathway_changes)
            self.notify_affected_organizations(pathway_changes)
        
        # Check for benchmark updates
        current_benchmarks = self.get_carb_benchmarks()
        stored_benchmarks = self.get_boost_benchmark_cache()
        
        if current_benchmarks != stored_benchmarks:
            self.update_benchmark_values(current_benchmarks)
            self.recalculate_affected_transactions(current_benchmarks)
        
        # Check for regulatory text changes
        regulatory_updates = self.check_lcfs_regulation_updates()
        if regulatory_updates:
            self.analyze_regulatory_impact(regulatory_updates)
            self.update_validation_rules(regulatory_updates)
    
    def implement_regulatory_changes(self, change_notice):
        """Implement changes based on official CARB change notices"""
        
        implementation_plan = self.analyze_change_impact(change_notice)
        
        # Update schema definitions
        if implementation_plan.requires_schema_updates:
            self.update_entity_schemas(implementation_plan.schema_changes)
        
        # Update validation rules
        if implementation_plan.requires_validation_updates:
            self.update_validation_rules(implementation_plan.validation_changes)
        
        # Migrate existing data
        if implementation_plan.requires_data_migration:
            self.migrate_existing_data(implementation_plan.migration_procedures)
        
        # Notify users of changes
        self.send_change_notifications(implementation_plan.user_impacts)
        
        return implementation_plan

Version Control and Backward Compatibility:

45.6. Technical Implementation

45.6.1. API Architecture for LCFS Operations

# FastAPI implementation for LCFS operations
from fastapi import FastAPI, HTTPException, Depends
from typing import List, Optional
import asyncio

app = FastAPI(title="BOOST LCFS API", version="1.0.0")

@app.get("/lcfs/pathways")
async def get_active_pathways(
    feedstock_category: Optional[str] = None,
    fuel_product: Optional[str] = None,
    active_only: bool = True
) -> List[LcfsPathway]:
    """Retrieve CARB-certified pathways with filtering options"""
    
    pathways = await pathway_service.get_pathways(
        feedstock_category=feedstock_category,
        fuel_product=fuel_product,
        active_only=active_only
    )
    
    return pathways

@app.post("/lcfs/transactions")
async def create_lcfs_transaction(
    transaction: LcfsTransactionCreate,
    validate_pathway: bool = True
) -> LcfsTransactionResponse:
    """Create new LCFS fuel transaction with validation"""
    
    if validate_pathway:
        pathway = await pathway_service.get_pathway(transaction.lcfs_pathway_id)
        if not pathway or pathway.verification_status != 'active':
            raise HTTPException(
                status_code=400, 
                detail=f"Invalid or inactive pathway: {transaction.lcfs_pathway_id}"
            )
    
    # Calculate credits automatically
    credit_result = credit_calculator.calculate_credits(transaction, pathway)
    
    # Create transaction with calculated values
    created_transaction = await transaction_service.create_transaction(
        transaction_data=transaction,
        credits_generated=credit_result.credits_generated,
        deficits_incurred=credit_result.deficits_incurred
    )
    
    return LcfsTransactionResponse(
        transaction=created_transaction,
        credit_calculation=credit_result
    )

@app.get("/lcfs/reports/{reporting_period}")
async def generate_quarterly_report(
    reporting_period: str,
    organization_id: str,
    format: str = "json"
) -> LcfsReportResponse:
    """Generate quarterly LCFS report for CARB submission"""
    
    # Validate reporting period format
    if not re.match(r'^\d{4}-Q[1-4]$', reporting_period):
        raise HTTPException(
            status_code=400,
            detail="Invalid reporting period format. Use YYYY-Q# format."
        )
    
    # Generate report
    report = await report_service.generate_quarterly_report(
        organization_id=organization_id,
        reporting_period=reporting_period
    )
    
    # Export in requested format
    if format == "xml":
        xml_content = await export_service.export_to_carb_xml(report)
        return Response(content=xml_content, media_type="application/xml")
    
    return LcfsReportResponse(report=report)

@app.post("/lcfs/credits/calculate")
async def calculate_credits(
    calculation_request: CreditCalculationRequest
) -> CreditCalculationResponse:
    """Calculate LCFS credits for transaction scenarios"""
    
    result = credit_calculator.calculate_credits(
        fuel_volume=calculation_request.fuel_volume,
        fuel_category=calculation_request.fuel_category,
        pathway_ci=calculation_request.pathway_ci,
        reporting_year=calculation_request.reporting_year
    )
    
    return CreditCalculationResponse(
        credits_generated=result.credits_generated,
        co2_reduction_mt=result.co2_reduction_mt,
        calculation_details=result.details
    )

45.6.2. Integration with External Systems

45.6.2.1. CARB LRT-CBTS Integration
class CARBIntegrationService:
    """Integration service for CARB LRT-CBTS system"""
    
    def __init__(self, carb_api_credentials):
        self.carb_client = CARBAPIClient(carb_api_credentials)
        self.xml_formatter = CARBXMLFormatter()
    
    async def submit_quarterly_report(self, lcfs_report: LcfsReporting):
        """Submit quarterly report to CARB LRT-CBTS system"""
        
        # Convert BOOST report to CARB XML format
        carb_xml = self.xml_formatter.format_quarterly_report(lcfs_report)
        
        # Validate XML against CARB schema
        validation_result = self.xml_formatter.validate_against_carb_schema(carb_xml)
        if not validation_result.valid:
            raise ValueError(f"XML validation failed: {validation_result.errors}")
        
        # Submit to CARB
        submission_response = await self.carb_client.submit_report(
            xml_content=carb_xml,
            report_period=lcfs_report.reporting_period
        )
        
        # Update BOOST entity with submission status
        lcfs_report.submission_date = submission_response.submission_timestamp
        lcfs_report.carb_confirmation_id = submission_response.confirmation_id
        lcfs_report.report_status = "submitted"
        
        return submission_response
    
    async def sync_pathway_database(self):
        """Synchronize CARB pathway database with BOOST entities"""
        
        # Fetch current CARB pathway data
        carb_pathways = await self.carb_client.get_current_pathways()
        
        # Compare with BOOST pathway cache
        boost_pathways = await self.get_boost_pathways()
        
        sync_results = {
            'new_pathways': [],
            'updated_pathways': [],
            'expired_pathways': []
        }
        
        for carb_pathway in carb_pathways:
            boost_pathway = next(
                (p for p in boost_pathways if p.lcfs_pathway_id == carb_pathway.pathway_id), 
                None
            )
            
            if not boost_pathway:
                # New pathway from CARB
                new_pathway = self.create_boost_pathway_from_carb(carb_pathway)
                sync_results['new_pathways'].append(new_pathway)
            
            elif self.pathway_needs_update(boost_pathway, carb_pathway):
                # Existing pathway with updates
                updated_pathway = self.update_boost_pathway_from_carb(boost_pathway, carb_pathway)
                sync_results['updated_pathways'].append(updated_pathway)
        
        # Identify expired pathways
        for boost_pathway in boost_pathways:
            if not any(cp.pathway_id == boost_pathway.lcfs_pathway_id for cp in carb_pathways):
                boost_pathway.verification_status = 'expired'
                sync_results['expired_pathways'].append(boost_pathway)
        
        return sync_results

45.6.3. Performance Optimization and Scalability

45.6.3.1. High-Volume Transaction Processing
class HighVolumeTransactionProcessor:
    """Optimized processing for high-volume LCFS operations"""
    
    def __init__(self):
        self.batch_size = 1000
        self.max_concurrent_batches = 10
        self.credit_calculator = LCFSCreditCalculator()
    
    async def process_transaction_batch(self, transactions: List[Transaction]):
        """Process large batches of transactions efficiently"""
        
        # Group transactions by pathway for batch credit calculation
        pathway_groups = self.group_transactions_by_pathway(transactions)
        
        # Process each pathway group concurrently
        batch_tasks = []
        for pathway_id, pathway_transactions in pathway_groups.items():
            task = self.process_pathway_group(pathway_id, pathway_transactions)
            batch_tasks.append(task)
        
        # Execute with concurrency limit
        semaphore = asyncio.Semaphore(self.max_concurrent_batches)
        
        async def process_with_semaphore(task):
            async with semaphore:
                return await task
        
        results = await asyncio.gather(
            *[process_with_semaphore(task) for task in batch_tasks]
        )
        
        # Flatten results
        processed_transactions = []
        for batch_result in results:
            processed_transactions.extend(batch_result)
        
        return processed_transactions
    
    async def process_pathway_group(self, pathway_id: str, transactions: List[Transaction]):
        """Process all transactions for a specific pathway"""
        
        # Get pathway data once for the entire group
        pathway = await self.get_pathway_cached(pathway_id)
        
        # Batch credit calculations
        processed_transactions = []
        
        for transaction in transactions:
            # Calculate credits for this transaction
            credit_result = self.credit_calculator.calculate_credits(transaction, pathway)
            
            # Update transaction with results
            transaction.credits_generated = credit_result.credits_generated
            transaction.deficits_incurred = credit_result.deficits_incurred
            transaction.actual_ci = pathway.carbon_intensity
            
            processed_transactions.append(transaction)
        
        return processed_transactions
    
    @functools.lru_cache(maxsize=1000)
    async def get_pathway_cached(self, pathway_id: str) -> LcfsPathway:
        """Cache frequently accessed pathways"""
        return await pathway_service.get_pathway(pathway_id)

45.7. California Bioenergy Renewable Auction Mechanism (BioRAM)

45.7.1. BioRAM Program Overview

The Bioenergy Renewable Auction Mechanism (BioRAM) is California’s competitive procurement program for biomass-fired electrical generation, administered by the California Energy Commission (CEC). BioRAM addresses California’s dual challenges of wildfire risk management and renewable energy generation by creating economic incentives for the utilization of biomass feedstocks from fire hazard zones.

45.7.1.1. Regulatory Background

Program Administration:

Key Program Objectives:

Regulated Parties:

45.7.1.2. CEC Reporting Requirements

Quarterly Reporting Timeline:

Required Reporting Elements:

Key BioRAM Terms:

45.7.2. BOOST’s Role in BioRAM Compliance

BOOST provides comprehensive support for BioRAM compliance by integrating biomass supply chain tracking with facility operational reporting:

Supply Chain Documentation:

Facility Operations Support:

Regulatory Reporting Integration:

45.8. BioRAM Entity Integration

45.8.1. Core BioRAM Entities

BOOST provides specialized entities for BioRAM compliance that extend core supply chain entities with program-specific attributes:

45.8.1.1. BioramPathway Entity

The BioramPathway entity manages CEC-certified pathways for biomass power generation:

Required Fields:

Optional Fields:

45.8.1.2. Enhanced Transaction Entity

Standard BOOST Transaction entities are enhanced with BioRAM-specific fields:

BioRAM Extension Fields:

Compliance Documentation Fields:

45.8.1.3. BioramReporting Entity

Quarterly aggregation entity for CEC submissions:

Primary Aggregation Fields:

Operational Metrics:

Verification Fields:

45.8.2. Entity Relationships and Data Flow

The BioRAM compliance workflow creates specific relationships between BOOST entities:

Entity Relationship Flow:
Organization (Facility) → operates under → BioramPathway
BioramPathway → defines eligibility for → Transaction (Fuel Purchase)
Transaction → aggregates to → BioramReporting
Transaction → references → TraceableUnit (Biomass)
TraceableUnit → sourced from → Material (Feedstock)
Material → located in → GeographicData (Fire Hazard Zone)

Additional relationships:
Organization (Supplier) → provides → TraceableUnit
Certificate (Supplier Qual) → validates → Organization
MoistureContent → measures quality of → TraceableUnit
VerificationStatement → verifies → BioramReporting

Key Relationship Rules:

45.9. BioRAM Implementation Examples

45.9.1. Sherwood Power Station Case Study

Complete Q3 2025 BioRAM Compliance Example

This comprehensive example demonstrates BOOST’s BioRAM compliance capabilities using Sherwood Power Station, a 15 MW biomass power facility in Sherwood, California.

45.9.1.1. Facility Profile
45.9.1.2. Q3 2025 Operational Summary

| Metric | Value | Unit | |--------|--------|------| | Total Biomass Consumed | 1,500 | Bone dry tonnes | | Total Energy Generated | 1,200 | MWh | | Overall Efficiency | 36% | Electrical conversion | | Efficiency Target | 35% | Contract requirement | | Fire Hazard Zone Usage | 100% | Very High FHSZ | | Average Haul Distance | 85 | Miles | | Compliance Status | ✅ Compliant | All targets met |

45.9.1.3. Detailed Transaction Example

Transaction TXN-BIO-2025-Q3-001 (Mill Residue Procurement):

{
  "@context": "https://boost-standard.org/context.jsonld",
  "@type": "Transaction",
  "@id": "https://sherwoodpower.com/transactions/TXN-BIO-2025-Q3-001",
  
  "transactionId": "TXN-BIO-2025-Q3-001",
  "transactionType": "biomass_purchase",
  "transactionDate": "2025-09-15T08:30:00Z",
  "organizationId": "ORG-SHERWOOD-PWR-001",
  "supplierId": "SUP-SIERRA-LUMBER-001",
  
  "bioramPathwayId": "BIORAM-PWR-2025-LMR-001",
  "fuelVolumeBDT": 1500.0,
  "moistureContent": 42.5,
  "heatingValueMJ": 18500,
  "fireHazardZone": "Very High",
  "haulDistance": 85.2,
  "sourceLocationSRA": true,
  "facilityEfficiencyCredit": 0.36,
  
  "calFireVerification": "CALFIRE-FHSZ-CERT-2025-091501",
  "supplierCertification": "BIO-SUP-QUAL-2025-SL-001",
  "qualityAssurance": {
    "moistureTest": "ASTM-E871-Standard",
    "heatingValueTest": "ASTM-E711-Standard",
    "ashContentPercent": 2.1,
    "certificationBody": "Biomass Quality Labs"
  },
  
  "traceableUnitIds": ["TRU-MILL-RES-001"],
  "contractValue": 120000.0,
  "contractValueCurrency": "USD",
  "paymentTerms": "Net 15"
}
45.9.1.4. BioRAM Pathway Configuration
{
  "@context": "https://boost-standard.org/context.jsonld",
  "@type": "BioramPathway",
  "@id": "https://cec.ca.gov/bioram/pathways/BIORAM-PWR-2025-LMR-001",
  
  "pathwayId": "BIORAM-PWR-2025-LMR-001",
  "fuelType": "lumber_mill_residual",
  "targetFacilityType": "biomass_power_plant",
  "efficiencyStandard": 0.35,
  "carbonIntensity": 15.2,
  "certificationDate": "2025-01-15",
  "eligibilityStatus": "active",
  
  "geographicScope": "California_SRA",
  "fireHazardZoneEligibility": ["Very High", "High"],
  "haulDistanceLimit": 125,
  "cecVersion": "2.1",
  "seasonalRestrictions": ["fire_season_restrictions"],
  "moistureContentLimits": {
    "minimum": 10,
    "maximum": 55,
    "preferredRange": "35-50"
  }
}
45.9.1.5. Quarterly Report Generation
{
  "@context": "https://boost-standard.org/context.jsonld",
  "@type": "BioramReporting",
  "@id": "https://sherwoodpower.com/reports/BIORAM-2025-Q3",
  
  "reportingId": "BIORAM-RPT-2025-Q3-SHWD001",
  "facilityEntityId": "ORG-SHERWOOD-PWR-001",
  "bioramContractId": "BR-RFO-2024-01-A",
  "reportingPeriod": "2025-Q3",
  "submissionDate": "2025-10-28T16:45:00Z",
  "complianceStatus": "compliant",
  
  "totalBiomassVolume": 1500.0,
  "totalEnergyGenerated": 1200.0,
  "overallEfficiency": 0.36,
  "efficiencyTarget": 0.35,
  "averageHaulDistance": 85.2,
  
  "fireHazardZoneUtilization": {
    "Very High": {
      "volume": 1500.0,
      "percentage": 100.0,
      "energyGenerated": 1200.0
    },
    "High": {
      "volume": 0.0,
      "percentage": 0.0,
      "energyGenerated": 0.0
    }
  },
  
  "verificationRequired": true,
  "verificationDate": "2025-10-25T14:30:00Z",
  "verifierEntityId": "VER-BIORAM-ACC-001",
  "verificationStatus": "verified",
  
  "facilityPerformanceMetrics": {
    "capacityFactor": 0.32,
    "availabilityFactor": 0.95,
    "fuelConversionEfficiency": 0.36,
    "gridDeliveredMWh": 1200.0
  }
}

45.9.2. Python Implementation for BioRAM Compliance

45.9.2.1. BioRAM Efficiency Calculator
class BioRAMEfficiencyCalculator:
    """
    BioRAM efficiency calculation engine using BOOST entities
    Implements CEC BioRAM calculation methodology
    """
    
    # Standard BioRAM conversion factors
    BDT_TO_MWH_CONVERSION = {
        'lumber_mill_residual': 0.8,  # MWh/BDT typical
        'forest_harvest_residual': 0.75,
        'agricultural_residue': 0.85,
        'urban_wood_waste': 0.72
    }
    
    def calculate_facility_efficiency(self, transactions, energy_generated):
        """
        Calculate facility efficiency for BioRAM compliance
        
        Args:
            transactions: List of biomass fuel transactions
            energy_generated: Total MWh generated during period
            
        Returns:
            dict: Efficiency calculation with BioRAM compliance status
        """
        # Calculate total biomass input
        total_biomass_bdt = sum(t.fuelVolumeBDT for t in transactions)
        
        # Calculate weighted average heating value
        total_energy_content = sum(
            t.fuelVolumeBDT * t.heatingValueMJ for t in transactions
        )
        average_heating_value = total_energy_content / total_biomass_bdt if total_biomass_bdt > 0 else 0
        
        # Calculate efficiency (MWh out / theoretical MWh in)
        theoretical_energy_mwh = (total_energy_content / 1000) / 3.6  # Convert MJ to MWh
        efficiency = energy_generated / theoretical_energy_mwh if theoretical_energy_mwh > 0 else 0
        
        # Determine BioRAM compliance
        pathway_efficiency_target = self._get_pathway_efficiency_requirement(transactions[0])
        meets_efficiency_target = efficiency >= pathway_efficiency_target
        
        return {
            'total_biomass_bdt': total_biomass_bdt,
            'total_energy_generated_mwh': energy_generated,
            'facility_efficiency': efficiency,
            'efficiency_target': pathway_efficiency_target,
            'meets_target': meets_efficiency_target,
            'efficiency_margin': efficiency - pathway_efficiency_target,
            'average_heating_value_mj': average_heating_value,
            'theoretical_energy_mwh': theoretical_energy_mwh
        }
    
    def validate_fire_hazard_zone_compliance(self, transactions):
        """Validate fire hazard zone sourcing requirements"""
        
        zone_breakdown = {
            'Very High': {'volume': 0, 'percentage': 0},
            'High': {'volume': 0, 'percentage': 0}, 
            'Moderate': {'volume': 0, 'percentage': 0},
            'Low': {'volume': 0, 'percentage': 0}
        }
        
        total_volume = sum(t.fuelVolumeBDT for t in transactions)
        
        for transaction in transactions:
            zone = transaction.fireHazardZone
            if zone in zone_breakdown:
                zone_breakdown[zone]['volume'] += transaction.fuelVolumeBDT
        
        # Calculate percentages
        for zone_data in zone_breakdown.values():
            zone_data['percentage'] = (zone_data['volume'] / total_volume * 100) if total_volume > 0 else 0
        
        # BioRAM preference for Very High and High zones
        priority_zone_percentage = (
            zone_breakdown['Very High']['percentage'] + 
            zone_breakdown['High']['percentage']
        )
        
        return {
            'zone_breakdown': zone_breakdown,
            'priority_zone_percentage': priority_zone_percentage,
            'meets_fire_reduction_objectives': priority_zone_percentage >= 75.0,
            'total_volume_bdt': total_volume
        }
    
    def _get_pathway_efficiency_requirement(self, transaction):
        """Get efficiency requirement from pathway"""
        # In real implementation, would lookup from BioramPathway entity
        return 0.35  # 35% standard BioRAM efficiency requirement

# Usage example
calculator = BioRAMEfficiencyCalculator()

# Calculate Q3 2025 efficiency for Sherwood Power Station
efficiency_result = calculator.calculate_facility_efficiency(
    transactions=[bioram_transaction],
    energy_generated=1200.0  # MWh
)

zone_compliance = calculator.validate_fire_hazard_zone_compliance(
    transactions=[bioram_transaction]
)

print(f"Facility Efficiency: {efficiency_result['facility_efficiency']:.1%}")
print(f"Meets Target: {efficiency_result['meets_target']}")
print(f"Priority Zone Usage: {zone_compliance['priority_zone_percentage']:.1f}%")
45.9.2.2. BioRAM Quarterly Reporter
class BioRAMQuarterlyReporter:
    """
    Automated quarterly report generation for CEC BioRAM submission
    Integrates with BOOST entities and BioRAM validation systems
    """
    
    def __init__(self, boost_client):
        self.boost = boost_client
        self.calculator = BioRAMEfficiencyCalculator()
    
    def generate_quarterly_report(self, facility_id, reporting_period):
        """
        Generate complete quarterly BioRAM compliance report
        
        Args:
            facility_id: BOOST Organization ID for biomass facility
            reporting_period: Quarter in YYYY-Q# format
            
        Returns:
            BioramReporting: Complete quarterly report entity
        """
        # Step 1: Collect all biomass transactions for reporting period
        transactions = self.boost.get_transactions(
            organization_id=facility_id,
            reporting_period=reporting_period,
            transaction_type='biomass_purchase'
        )
        
        if not transactions:
            raise ValueError(f"No biomass transactions found for {reporting_period}")
        
        # Step 2: Get energy generation data
        energy_generated = self._get_energy_generation_data(facility_id, reporting_period)
        
        # Step 3: Calculate facility efficiency
        efficiency_result = self.calculator.calculate_facility_efficiency(
            transactions, energy_generated
        )
        
        # Step 4: Validate fire hazard zone compliance
        zone_compliance = self.calculator.validate_fire_hazard_zone_compliance(transactions)
        
        # Step 5: Determine overall compliance status
        compliance_status = self._determine_compliance_status(
            efficiency_result, zone_compliance
        )
        
        # Step 6: Create quarterly report entity
        report = BioramReporting(
            reportingId=f"BIORAM-RPT-{reporting_period}-{facility_id[-4:]}",
            facilityEntityId=facility_id,
            reportingPeriod=reporting_period,
            submissionDate=datetime.now().isoformat(),
            
            totalBiomassVolume=efficiency_result['total_biomass_bdt'],
            totalEnergyGenerated=efficiency_result['total_energy_generated_mwh'],
            overallEfficiency=efficiency_result['facility_efficiency'],
            efficiencyTarget=efficiency_result['efficiency_target'],
            complianceStatus=compliance_status,
            
            averageHaulDistance=self._calculate_average_haul_distance(transactions),
            fireHazardZoneUtilization=zone_compliance['zone_breakdown'],
            
            verificationRequired=efficiency_result['total_energy_generated_mwh'] > 1000,  # >1 GWh
            verificationStatus="pending" if efficiency_result['total_energy_generated_mwh'] > 1000 else "not_required"
        )
        
        return report
    
    def _get_energy_generation_data(self, facility_id, reporting_period):
        """Get energy generation data from facility operations"""
        # Implementation would integrate with facility SCADA/metering systems
        # For example purposes, using stored operational data
        return 1200.0  # MWh generated in Q3 2025
    
    def _determine_compliance_status(self, efficiency_result, zone_compliance):
        """Determine overall BioRAM compliance status"""
        if not efficiency_result['meets_target']:
            return "efficiency_shortfall"
        elif zone_compliance['priority_zone_percentage'] < 50.0:
            return "sourcing_violation" 
        else:
            return "compliant"
    
    def _calculate_average_haul_distance(self, transactions):
        """Calculate volume-weighted average haul distance"""
        total_volume = sum(t.fuelVolumeBDT for t in transactions)
        if total_volume == 0:
            return 0
        
        weighted_distance = sum(
            t.fuelVolumeBDT * t.haulDistance for t in transactions
        )
        
        return weighted_distance / total_volume

# Complete workflow example
reporter = BioRAMQuarterlyReporter(boost_client)

# Generate Q3 2025 report for Sherwood Power Station
q3_report = reporter.generate_quarterly_report(
    facility_id="ORG-SHERWOOD-PWR-001",
    reporting_period="2025-Q3"
)

print(f"Generated BioRAM report: {q3_report.reportingId}")
print(f"Facility Efficiency: {q3_report.overallEfficiency:.1%}")
print(f"Compliance Status: {q3_report.complianceStatus}")

45.10. BioRAM Integration with Core BOOST Entities

45.10.1. Supply Chain Traceability Enhancement

BioRAM compliance requires enhanced traceability features that leverage core BOOST entities:

45.10.1.1. Material Entity Extensions
{
  "@context": "https://boost-standard.org/context.jsonld",
  "@type": "Material",
  "@id": "https://sierralumber.com/materials/MILL-RES-001",
  
  "materialId": "MILL-RES-001",
  "materialType": "lumber_mill_residual",
  "materialCategory": "biomass_feedstock",
  
  // BioRAM-specific extensions
  "fireHazardZoneSource": "Very High",
  "calFireZoneVerification": "CALFIRE-FHSZ-CERT-2025-091501", 
  "haulDistanceToFacility": 85.2,
  "withinSRA": true,
  "bioramEligible": true,
  
  // Quality characteristics for BioRAM
  "moistureContentPercent": 42.5,
  "heatingValueMJ": 18500,
  "ashContentPercent": 2.1,
  "bulkDensity": 350.0
}
45.10.1.2. GeographicData Entity Integration
{
  "@context": "https://boost-standard.org/context.jsonld",
  "@type": "GeographicData",
  "@id": "https://calfire.ca.gov/zones/FHSZ-PLA-001",
  
  "geographicDataId": "FHSZ-PLA-001",
  "locationType": "fire_hazard_severity_zone",
  "primaryCoordinates": {
    "latitude": 39.1612,
    "longitude": -120.7983
  },
  
  // CAL FIRE specific data
  "fireHazardSeverityZone": "Very High",
  "stateResponsibilityArea": true,
  "calFireUnit": "Nevada-Yuba-Placer Unit",
  "countyJurisdiction": "Placer County",
  
  // BioRAM program eligibility
  "bioramEligible": true,
  "fireRiskReductionPriority": "high",
  "biomassAvailabilityEstimate": 15000  // BDT per year
}
45.10.1.3. Organization Entity BioRAM Fields
{
  "@context": "https://boost-standard.org/context.jsonld",
  "@type": "Organization", 
  "@id": "https://sherwoodpower.com/organization",
  
  "organizationId": "ORG-SHERWOOD-PWR-001",
  "name": "Sherwood Power Station",
  "organizationType": "biomass_power_facility",
  
  // BioRAM facility registration
  "bioramRegistrationId": "CEC-BIO-012",
  "cecFacilityId": "PWR-FAC-2024-015",
  "bioramContractNumber": "BR-RFO-2024-01-A",
  "utofftaker": "Pacific Gas & Electric",
  "contractCapacityMW": 15.0,
  "contractCommencementDate": "2025-01-01",
  "contractTermYears": 20,
  
  // Technical specifications
  "facilityEfficiencyTarget": 0.35,
  "biomassStorageCapacityBDT": 5000,
  "annualBiomassRequirementBDT": 18000,
  "gridConnectionPoint": "PG&E-Auburn-Sub-001"
}

45.10.2. Validation Workflows

45.10.2.1. BioRAM-Specific Business Logic Validation
class BioRAMValidationEngine:
    """BioRAM-specific validation rules for BOOST entities"""
    
    def validate_transaction_bioram_compliance(self, transaction):
        """Validate transaction meets BioRAM requirements"""
        validation_results = []
        
        # 1. Fire hazard zone validation
        if not self._validate_fire_hazard_zone(transaction):
            validation_results.append({
                'rule': 'fire_hazard_zone_eligibility',
                'status': 'failure',
                'message': f'Fire hazard zone {transaction.fireHazardZone} not eligible for BioRAM pathway {transaction.bioramPathwayId}'
            })
        
        # 2. Haul distance validation
        pathway = self._get_bioram_pathway(transaction.bioramPathwayId)
        if transaction.haulDistance > pathway.haulDistanceLimit:
            validation_results.append({
                'rule': 'haul_distance_limit',
                'status': 'failure', 
                'message': f'Haul distance {transaction.haulDistance} miles exceeds pathway limit {pathway.haulDistanceLimit} miles'
            })
        
        # 3. Fuel quality validation
        if not self._validate_fuel_quality(transaction):
            validation_results.append({
                'rule': 'fuel_quality_standards',
                'status': 'failure',
                'message': f'Moisture content {transaction.moistureContent}% outside acceptable range for pathway'
            })
        
        # 4. SRA validation
        if not transaction.sourceLocationSRA and pathway.geographicScope == "California_SRA":
            validation_results.append({
                'rule': 'sra_requirement',
                'status': 'failure',
                'message': 'Feedstock must originate from State Responsibility Area for this pathway'
            })
        
        return {
            'valid': len(validation_results) == 0,
            'validation_results': validation_results
        }
    
    def validate_facility_efficiency_compliance(self, reporting_entity):
        """Validate facility meets BioRAM efficiency requirements"""
        
        efficiency_margin = reporting_entity.overallEfficiency - reporting_entity.efficiencyTarget
        
        if efficiency_margin < 0:
            return {
                'valid': False,
                'efficiency_shortfall': abs(efficiency_margin),
                'message': f'Facility efficiency {reporting_entity.overallEfficiency:.1%} below target {reporting_entity.efficiencyTarget:.1%}'
            }
        
        return {
            'valid': True,
            'efficiency_surplus': efficiency_margin,
            'message': f'Facility efficiency {reporting_entity.overallEfficiency:.1%} exceeds target by {efficiency_margin:.1%}'
        }

    def _validate_fire_hazard_zone(self, transaction):
        """Validate fire hazard zone eligibility"""
        pathway = self._get_bioram_pathway(transaction.bioramPathwayId)
        return transaction.fireHazardZone in pathway.fireHazardZoneEligibility

    def _validate_fuel_quality(self, transaction):
        """Validate fuel quality parameters"""
        pathway = self._get_bioram_pathway(transaction.bioramPathwayId)
        limits = pathway.moistureContentLimits
        
        return (limits['minimum'] <= transaction.moistureContent <= limits['maximum'])

This comprehensive expansion provides implementers with detailed guidance for BioRAM compliance using BOOST, covering all aspects requested in Issue #236.

46. Python Reference Implementation

The BOOST standard provides a comprehensive Python reference implementation that demonstrates dynamic, schema-driven data models, validation, and supply chain tracking capabilities for biomass chain of custody operations.

46.1. Overview

The Python reference implementation uses a dynamic, schema-driven architecture that automatically adapts to changes in BOOST JSON schemas without requiring code modifications. Key features include:

46.2. Installation

46.2.1. Prerequisites

The Python reference implementation requires:

46.2.2. Dependencies

Core dependencies are defined in requirements.txt:

pydantic>=2.0.0      # Data validation and settings management
jsonschema>=4.0.0    # JSON Schema validation
requests>=2.28.0     # HTTP library for API calls
pyld>=2.0.0          # JSON-LD processor

Installation:

pip install -r requirements.txt

46.3. Architecture

The implementation follows a layered architecture with three main components:

┌─────────────────────────────────────────────────────────────────┐
│                    BOOST JSON Schemas                          │
│                                                                 │
│  ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌──────────┐  │
│  │organization/│ │traceable_   │ │transaction/ │ │   ...    │  │
│  │validation_  │ │unit/        │ │validation_  │ │          │  │
│  │schema.json  │ │validation_  │ │schema.json  │ │          │  │
│  └─────────────┘ │schema.json  │ └─────────────┘ └──────────┘  │
│                  └─────────────┘                               │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│            Schema Loader (Dynamic Model Generation)            │
│                                                                 │
│  • Automatic Schema Discovery  • Dynamic Model Generation      │
│  • Enum Generation            • Relationship Discovery        │
│  • Primary Key Detection      • Metadata Extraction           │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│       Dynamic Validation (Configuration-Driven Rules)         │
│                                                                 │
│  • Schema Validation       • Cross-Entity Validation          │
│  • Business Logic Rules    • Temporal Consistency            │
│  • Mass Balance Validation • Certification Logic             │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│        BOOST Client (High-Level API Interface)                │
│                                                                 │
│  • Entity Creation         • Supply Chain Analysis            │
│  • Schema Introspection    • JSON-LD Export/Import           │
│  • Comprehensive Validation • ID Generation                   │
└─────────────────────────────────────────────────────────────────┘

46.4. Core Components

46.4.1. SchemaLoader

The SchemaLoader (schema_loader.py) is the foundation component that provides dynamic schema loading and model generation:

Key Features:

Usage Example:

from schema_loader import SchemaLoader

# Initialize with automatic schema discovery
loader = SchemaLoader()

# Get dynamically generated Pydantic models
OrganizationModel = loader.get_model('organization')
TraceableUnitModel = loader.get_model('traceable_unit')

# Get enum values directly from current schemas
org_types = loader.get_field_enum_values('organization', 'organizationType')
print(f"Available organization types: {org_types}")

# Access relationship information discovered from schemas
relationships = loader.get_relationships('traceable_unit')
primary_key = loader.get_primary_key('organization')

46.4.2. DynamicBOOSTValidator

The DynamicBOOSTValidator (dynamic_validation.py) provides comprehensive, schema-driven validation using configuration-based business rules:

Validation Categories:

  1. Schema Validation: JSON Schema compliance and structural validation

  2. Volume/Mass Conservation: Physical conservation laws with configurable tolerance checking

  3. Temporal Logic: Date/time consistency rules and processing sequence validation

  4. Geographic Logic: Location-based constraints and transport distance validation

  5. Species Composition: Biological consistency and percentage validation

  6. Certification Logic: Chain of custody validation and certificate integrity

  7. Regulatory Compliance: LCFS, EU RED, and sustainability criteria validation

  8. Economic/Quality Logic: Market constraints and quality assurance validation

Usage Example:

from dynamic_validation import DynamicBOOSTValidator

validator = DynamicBOOSTValidator()

# Schema validation against current schema
is_valid, errors = validator.validate_entity("organization", org_data)

# Configuration-driven business logic validation
is_valid, errors = validator.validate_business_logic("material_processing", processing_data)

# Comprehensive cross-entity validation
entities = {
    'organization': [org1, org2],
    'traceable_unit': [tru1, tru2],
    'transaction': [txn1]
}
results = validator.comprehensive_validation(entities)

46.4.3. BOOSTClient

The BOOSTClient (boost_client.py) provides a high-level interface that uses the dynamic models and validation system:

Core Functions:

Usage Example:

from boost_client import create_client

# Initialize client with dynamic schema loading
client = create_client()

# Schema introspection
schema_info = client.get_schema_info()
print(f"Available entities: {schema_info['available_entities']}")

# Dynamic enum discovery
org_types = client.get_available_enum_values('organization', 'organizationType')

# Entity creation with schema validation
org = client.create_organization(
    organization_id="ORG-FOREST-001",
    name="Pacific Forest Products",
    org_type="harvester",  # Validated against current schema
    contact_email="ops@pacificforest.com"
)

# Comprehensive validation
validation = client.validate_all()
if validation['valid']:
    print("✓ All entities pass validation!")

46.5. Dynamic Schema Adaptation

A key strength of the Python implementation is its automatic adaptation to schema changes. Most schema modifications require no code changes:

46.5.1. Automatically Handled Changes

Adding New Fields:

Adding New Enum Values:

Adding New Entity Types:

Modifying Business Logic Rules:

46.5.2. Schema Change Detection

The system provides built-in tools for schema change management:

# Check current schema status
client = create_client()
schema_info = client.get_schema_info()

# Validate against current schema
validation = client.validate_all()
if not validation['valid']:
    print("Schema changes detected - validation errors:")
    for error in validation['errors']:
        print(f"  - {error}")

# Refresh schemas after updates
client.refresh_schemas()

46.6. Usage Examples

46.6.1. Basic Workflow

Complete example demonstrating fundamental BOOST operations:

from boost_client import create_client

# Initialize BOOST client
client = create_client()

# Create organizations with schema validation
harvester = client.create_organization(
    organization_id="ORG-001",
    name="Forest Products Inc",
    org_type="harvester",
    contact_email="ops@forestproducts.com"
)

processor = client.create_organization(
    organization_id="ORG-002", 
    name="Sawmill Operations LLC",
    org_type="processor",
    contact_email="info@sawmill.com"
)

# Create traceable units with automatic model generation
log_pile = client.create_traceable_unit(
    traceable_unit_id="TRU-LOGS-001",
    unit_type="pile",
    harvester_id="ORG-001",
    total_volume_m3=125.5,
    sustainability_certification="FSC Mix Credit 70%"
)

# Process materials with conservation validation
lumber = client.create_material_processing(
    processing_id="MP-001",
    input_tru_id="TRU-LOGS-001",
    process_type="sawing",
    processor_id="ORG-002",
    output_volume_m3=95.2  # Validates against conservation rules
)

# Execute transaction with comprehensive validation
transaction = client.create_transaction(
    transaction_id="TXN-001",
    organization_id="ORG-002",
    customer_id="CUST-001",
    transaction_date="2025-08-12",
    quantity_m3=50.0
)

# Comprehensive validation using all dynamic rules
validation = client.validate_all()
if validation['valid']:
    print("✓ All entities validated successfully!")
    
# Export to JSON-LD with semantic annotations
jsonld_output = client.export_to_jsonld(include_context=True)

46.6.2. Certification Management

Example showing certification claim management:

# Create FSC certified organization
fsc_harvester = client.create_organization(
    organization_id="ORG-FSC-001",
    name="Certified Forest Management",
    org_type="harvester",
    certifications=["FSC-FM/COC-001234"]
)

# Create certified traceable unit
certified_logs = client.create_traceable_unit(
    traceable_unit_id="TRU-FSC-001",
    unit_type="pile",
    harvester_id="ORG-FSC-001",
    total_volume_m3=200.0,
    sustainability_certification="FSC Mix Credit 70%",
    certification_claims=["FSC-FM/COC-001234"]
)

# Validate certification chain integrity
cert_validation = client.validate_certification_chain("TRU-FSC-001")
print(f"Certification valid: {cert_validation['valid']}")

46.6.3. Mass Balance Validation

Example demonstrating conservation law validation:

# Multiple input materials
input_tru_1 = client.create_traceable_unit(
    traceable_unit_id="TRU-INPUT-001",
    unit_type="pile", 
    total_volume_m3=100.0
)

input_tru_2 = client.create_traceable_unit(
    traceable_unit_id="TRU-INPUT-002",
    unit_type="pile",
    total_volume_m3=75.0
)

# Processing with multiple inputs
pellet_production = client.create_material_processing(
    processing_id="MP-PELLETS-001",
    input_tru_ids=["TRU-INPUT-001", "TRU-INPUT-002"],
    process_type="pelletizing",
    total_input_volume_m3=175.0,
    total_output_volume_m3=140.0,  # Within tolerance for pelletizing
    efficiency_percent=80.0
)

# Validate mass balance with configurable tolerance
balance_validation = client.validate_mass_balance("MP-PELLETS-001")
print(f"Mass balance valid: {balance_validation['valid']}")
print(f"Efficiency: {balance_validation['efficiency']}%")

46.7. Integration Guidance

46.7.1. API Development

Using the reference implementation for API development:

from boost_client import create_client
from flask import Flask, jsonify, request

app = Flask(__name__)
boost_client = create_client()

@app.route('/organizations', methods=['POST'])
def create_organization():
    data = request.json
    try:
        # Dynamic validation using current schema
        org = boost_client.create_organization(**data)
        return jsonify(org.model_dump(by_alias=True))
    except ValueError as e:
        return jsonify({"error": str(e)}), 400

@app.route('/validate/<entity_type>', methods=['POST'])
def validate_entity(entity_type):
    data = request.json
    validation = boost_client.validator.validate_entity(entity_type, data)
    return jsonify({
        "valid": validation[0],
        "errors": validation[1]
    })

# Schema introspection endpoint
@app.route('/schema/info')
def schema_info():
    return jsonify(boost_client.get_schema_info())

46.7.2. External System Integration

Integration patterns for external systems:

# Custom validation rules for specific systems
class CustomValidator(DynamicBOOSTValidator):
    def validate_regulatory_compliance(self, entity_type, entity_data):
        """Custom regulatory validation."""
        base_validation = super().validate_business_logic(entity_type, entity_data)
        
        # Add custom rules
        custom_rules = self.apply_custom_regulatory_rules(entity_data)
        
        return base_validation and custom_rules

# Integration with existing databases
def sync_with_existing_db(boost_client, db_connection):
    """Sync BOOST entities with existing database."""
    # Export BOOST data
    jsonld_data = boost_client.export_to_jsonld()
    
    # Transform and import to existing system
    transformed_data = transform_boost_to_legacy(jsonld_data)
    db_connection.bulk_insert(transformed_data)

46.8. Configuration

46.8.1. Schema Path Configuration

Customize schema loading:

# Default: automatic discovery from ../schema/
client = create_client()

# Custom schema path
client = create_client(schema_path="/path/to/boost/schemas")

# Multiple schema sources
loader = SchemaLoader()
loader.add_schema_source("/additional/schemas")

46.8.2. Business Logic Configuration

Business logic rules are defined in configuration files:

business_logic_validation.json:

{
  "volumeMassConservation": {
    "materialProcessing": {
      "sawing": {
        "tolerance": 0.05,
        "efficiency_range": [0.7, 0.9]
      },
      "pelletizing": {
        "tolerance": 0.10,
        "efficiency_range": [0.75, 0.85]
      }
    }
  },
  "temporalLogic": {
    "processingWindows": {
      "harvest_to_processing_max_days": 90
    }
  }
}

46.9. Testing and Validation

46.9.1. Comprehensive Test Suite

The implementation includes comprehensive tests:

# Run all tests
python test_enhanced_entities.py

# Test specific validation categories
python -m unittest test_enhanced_entities.TestDynamicValidation.test_mass_balance_validation

# Test schema change robustness
python -m unittest test_enhanced_entities.TestSchemaRobustness

46.9.2. Validation Examples

Test validation with example data:

# Load and validate example data
with open('examples/validation/comprehensive_validation_test_suite.json') as f:
    test_data = json.load(f)

validator = DynamicBOOSTValidator()
results = validator.comprehensive_validation(test_data)

print(f"Validation results: {results['summary']}")
for category, result in results['by_category'].items():
    print(f"  {category}: {'PASS' if result['valid'] else 'FAIL'}")

46.10. Performance Characteristics

46.10.1. Initialization Performance

46.10.2. Runtime Performance

46.10.3. Scalability Considerations

46.11. Standards Compliance

The Python reference implementation fully supports:

47. Examples

This section provides practical examples of BOOST data structures and common implementation patterns to help developers understand how to work with the standard.

All examples use the JSON-LD format with the BOOST context definition to ensure semantic interoperability.

47.1. Python Implementation Examples

47.1.1. Basic Client Usage

from boost_client import create_client

# Initialize BOOST client with dynamic schema loading
client = create_client()

# Check what entities and enums are available from current schemas
schema_info = client.get_schema_info()
print(f"Available entities: {schema_info['available_entities']}")

# Get valid enum values dynamically from schemas
org_types = client.get_available_enum_values('organization', 'organizationType')
print(f"Valid organization types: {org_types}")

47.1.2. Creating Organizations

# Create an organization using schema-validated enum values
harvester = client.create_organization(
    organization_id="ORG-FOREST-001",
    name="Pacific Forest Products",
    org_type="harvester",  # Validated against current schema
    contact_email="ops@pacificforest.com",
    contact_phone="+15415550123"  # Must match schema pattern
)

47.1.3. Creating TraceableUnits

# Get available unit types from schema
unit_types = client.get_available_enum_values('traceable_unit', 'unitType')
print(f"Valid unit types: {unit_types}")

# Create a traceable unit with all required fields
harvester_data = harvester.model_dump(by_alias=True)
log_pile = client.create_traceable_unit(
    traceable_unit_id="TRU-LOGS-001",
    unit_type="pile",  # Validated against current schema
    harvester_id=harvester_data['organizationId'],
    total_volume_m3=125.5,
    sustainability_certification="FSC Mix Credit 70%",
    unique_identifier="RFID-001-A",  # Required by schema
    is_multi_species=False  # Required by schema
)

47.1.4. Comprehensive Validation

# Comprehensive validation using dynamic business rules
validation = client.validate_all()
if validation['valid']:
    print("✓ All entities are valid!")
else:
    print("✗ Schema and business logic validation errors:")
    for error in validation['errors']:
        print(f"  - {error}")

# Export to JSON-LD
jsonld_output = client.export_to_jsonld()
print(jsonld_output)

47.2. Supply Chain Workflow Example

47.2.1. Complete Harvest-to-Processing Chain

# 1. Create harvest operation
harvest_site = client.create_geographic_data(
    geographic_data_id="GEO-HARVEST-SITE-001",
    coordinates={"type": "Point", "coordinates": [-123.1234, 45.6789]},
    location_type="harvest_site"
)

# 2. Create individual log TRUs
individual_logs = []
for i in range(1, 6):  # 5 logs
    log = client.create_traceable_unit(
        traceable_unit_id=f"TRU-LOG-{i:03d}",
        unit_type="individual_log",
        harvester_id="ORG-FOREST-001",
        total_volume_m3=2.5,
        unique_identifier=f"BIO-DOUGLAS-FIR-{i:03d}",
        harvest_geographic_data_id=harvest_site.geographicDataId,
        is_multi_species=False
    )
    individual_logs.append(log)

# 3. Create pile aggregation
log_pile = client.create_traceable_unit(
    traceable_unit_id="TRU-PILE-001",
    unit_type="pile",
    harvester_id="ORG-FOREST-001",
    total_volume_m3=12.5,  # Sum of individual logs
    unique_identifier="PILE-ROADSIDE-001",
    parent_traceable_unit_ids=[log.traceableUnitId for log in individual_logs],
    is_multi_species=False
)

# 4. Document processing operation
processing_op = client.create_material_processing(
    processing_id="PROC-SAWMILL-001",
    process_type="primary_breakdown",
    input_traceable_unit_ids=[log_pile.traceableUnitId],
    process_timestamp="2025-08-01T10:30:00Z",
    facility_id="FAC-SAWMILL-PORTLAND"
)

47.3. Basic TraceableUnit Example

{
  "@context": "https://boost-standard.org/context.jsonld",
  "@type": "TraceableUnit",
  "@id": "https://example.com/tru/TRU-001",
  "traceableUnitId": "TRU-FOREST-001",
  "unitType": "pile",
  "uniqueIdentifier": "BIOMETRIC-SIGNATURE-ABC123",
  "totalVolumeM3": 125.5,
  "materialTypeId": "MAT-DOUGLAS-FIR-SAWLOG",
  "isMultiSpecies": false,
  "harvesterId": "ORG-PACIFIC-FOREST",
  "currentGeographicDataId": "GEO-MILL-YARD-07"
}

48. Resources & Community

This section provides access to BOOST presentations, working group documentation, and community resources.

48.1. Presentations & Demonstrations

48.1.1. Core Presentations

BOOST Kickoff Presentation Overview of the BOOST data standard initiative, project goals, and working group approach. View Presentation →

Transaction Object Examples Technical demonstration of data structures and transaction examples in the BOOST standard. View Examples →

48.1.2. Agency Engagement

Presentations developed for California state agencies to demonstrate BOOST applicability and gather feedback.

CalRecycle Engagement BOOST presentation for California Department of Resources Recycling and Recovery, covering biomass conversion, SB 498 reporting, and waste diversion systems. View Presentation →

CDFA Engagement BOOST presentation for California Department of Food and Agriculture, exploring agricultural biomass traceability and potential pilot development opportunities. View Presentation →

Department of Conservation BOOST presentation for California Department of Conservation, focusing on forest management data standards and conservation tracking requirements. View Presentation →

48.1.3. Standards & Technical

Technical presentations exploring BOOST integration with existing regulatory frameworks and standards.

BOOST + LCFS Integration Technical presentation on BOOST integration with California’s Low Carbon Fuel Standard (LCFS), covering relevant entities and chain of custody requirements. View Presentation →

48.2. Interactive Tools

48.2.1. Entity Relationship Diagram Navigator

Explore the complete BOOST data model through our interactive ERD Navigator, featuring all 33 entities across 7 thematic areas.

**Interactive ERD Navigator**

The ERD Navigator provides:

Launch ERD Navigator →

48.3. Working Group Documentation

48.3.1. Meeting Notes

Access notes and documentation from BOOST working group meetings and presentations.

Kickoff Meeting Initial project kickoff meeting notes and presentation materials. Meeting Notes → Additional Notes →

June 11, 2025 Working group meeting notes and action items from June 11th session. Meeting Notes → Additional Notes →

June 25, 2025 Latest working group meeting notes and updates from June 25th session. Meeting Notes → Additional Notes →

48.4. Community Participation

48.4.1. BOOST Membership

Chair:

Participants:

48.4.2. Stakeholder Feedback

We welcome feedback from industry stakeholders on our entity schemas. Use our interactive ERD Navigator to explore the data model and provide input on each entity definition.

How to Provide Feedback:

  1. Explore entities using the ERD Navigator

  2. Review entity schemas and field definitions

  3. Submit feedback via GitHub Issues

  4. Join our W3C Community Group discussions

49. Security Considerations

The BOOST data standard involves the exchange of sensitive commercial and operational data across biomass supply chains. Implementations must carefully consider security implications at multiple levels:

49.1. Data Privacy

Implementations SHOULD consider privacy implications of biomass tracking data:

49.2. Data Integrity

Critical security measures include:

49.3. Supply Chain Security

Implementations SHOULD address:

50. Complete Entity Reference

This section provides a comprehensive reference to all 33 BOOST entities organized by thematic areas for improved usability and logical structure.

50.1. Core Traceability Entities

The foundational entities that enable end-to-end biomass supply chain tracking:

50.1.1. TraceableUnit

50.1.2. MaterialProcessing

50.1.3. ProcessingHistory

50.1.4. LocationHistory

50.1.5. BiometricIdentifier

50.2. Organizational Foundation Entities

Entities managing organizations, certifications, and supply chain participants:

50.2.1. Organization

50.2.2. Certificate

50.2.3. CertificationBody

50.2.4. CertificationScheme

50.2.5. Operator

50.2.6. Audit

50.3. Material & Supply Chain Entities

Entities managing material specifications, suppliers, and supply chain relationships:

50.3.1. Material

50.3.2. SpeciesComponent

50.3.3. Equipment

50.3.4. Supplier

50.3.5. Customer

50.3.6. SupplyBase

50.3.7. SupplyBaseReport

50.4. Transaction Management Entities

Entities handling commercial transactions and order fulfillment:

50.4.1. Transaction

50.4.2. TransactionBatch

50.4.3. SalesDeliveryDocument

50.5. Geographic & Tracking Entities

Entities providing location data and spatial tracking capabilities:

50.5.1. GeographicData

50.5.2. TrackingPoint

50.6. Measurement & Verification Entities

Entities supporting quality measurement, claims management, and verification:

50.6.1. MeasurementRecord

50.6.2. Claim

50.6.3. VerificationStatement

50.6.4. MoistureContent

50.7. Compliance & Reporting Entities

Entities supporting regulatory compliance and comprehensive reporting:

50.7.1. LCFSPathway

50.7.2. LCFSReporting

50.7.3. ProductGroup

50.7.4. MassBalanceAccount

50.7.5. DataReconciliation

50.7.6. EnergyCarbonData

50.8. Entity Relationship Summary

50.8.1. Core Dependencies

50.8.2. Thematic Integration

50.8.3. Optional Relationships

Acknowledgments

This specification was developed through the collaborative efforts of the BOOST W3C Community Group with significant contributions from:

Special recognition to the contributors of the Interactive ERD Navigator, Python reference implementation, and comprehensive schema validation tools that support this specification.

Index

Index

Terms defined by this specification

Conformance

Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.

All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]

Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example", like this:

This is an example of an informative example.

Informative notes begin with the word “Note” and are set apart from the normative text with class="note", like this:

Note, this is an informative note.

References

Normative References

[RFC2119]
S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. URL: https://tools.ietf.org/rfc/rfc2119

Informative References

[CA-LCFS]
Low Carbon Fuel Standard Regulation. 2024. URL: https://ww2.arb.ca.gov/our-work/programs/low-carbon-fuel-standard
[EU-RED-II]
Renewable Energy Directive II. Directive (EU) 2018/2001. URL: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2018.328.01.0082.01.ENG
[FSC-STD-40-004]
Chain of Custody Certification. Version 3.0, 2017. URL: https://fsc.org/en/document-centre/documents/resource/392
[ISO38200]
Chain of custody of wood and wood-based products. 2018. URL: https://www.iso.org/standard/69429.html
[JSON-LD11]
Gregg Kellogg; Pierre-Antoine Champin; Dave Longley. JSON-LD 1.1. 16 July 2020. URL: https://www.w3.org/TR/json-ld11/
[JSON-SCHEMA]
Austin Wright; Henry Andrews. JSON Schema: A Media Type for Describing JSON Documents. March 2019. URL: https://json-schema.org/specification.html
[PEFC-ST-2002]
Chain of Custody of Forest Based Products. 2020. URL: https://www.pefc.org/standards/chain-of-custody
[RFC8174]
B. Leiba. Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words. May 2017. URL: https://tools.ietf.org/rfc/rfc8174
[SBP-STANDARD-4]
Chain of Custody Standard. Version 1.0, 2013. URL: https://sbp-cert.org/documents/standards-documents/
[SBP-STANDARD-5]
Collection and Communication of Data. Version 1.0, 2013. URL: https://sbp-cert.org/documents/standards-documents/