EnergyCarbonData Entity Schema Review

[pwt-cd]

EnergyCarbonData Entity Schema Review

🔗 Related Links

• Issue: EnergyCarbonData #109 (EnergyCarbonData entity)
• ERD Navigator: View in full context →

🎯 Purpose

The EnergyCarbonData entity captures energy consumption and carbon emissions data throughout the biomass supply chain. This entity enables:

• GHG Calculations: Supporting lifecycle assessment and carbon accounting
• Regulatory Compliance: Meeting emissions reporting requirements
• Supply Chain Transparency: Tracking environmental impact at each stage
• Market Verification: Enabling carbon credit and sustainability claims

📋 Proposed Schema

Core Attributes

Attribute	Data Type	Description
energyCarbonDataId	String (PK)	Unique identifier for the energy/carbon data record
dataType	Enum	Type of data: "moisture", "transport", "fuel_consumption", "processing_energy", "ghg_emissions"
value	Decimal	Numerical value of the measurement
unit	String	Unit of measurement (e.g., "kWh", "kg CO2e", "MJ", "km")
source	String	Source of the data: "measured", "calculated", "estimated", "default_factor"

Measurement and Context

Attribute	Data Type	Description
measurementMethod	String	How the data was obtained or calculated
reportingPeriod	String	Time period this data covers
linkedEntityId	String (FK)	Reference to associated Material, TransactionBatch, or Organization
linkedEntityType	Enum	Type of linked entity: "material", "transaction_batch", "organization"

Transport and Supply Data

Attribute	Data Type	Description
transportDistance	Decimal	Distance traveled (if transport-related)
transportMode	String	Method of transport: "truck", "rail", "ship", "pipeline"
fuelType	String	Type of fuel used in transport or processing
fuelConsumption	Decimal	Amount of fuel consumed
batchSpecific	Boolean	Whether data applies to specific batch vs. averaged
upstreamDataSource	String	Source of upstream energy/carbon data

🤔 Questions for Feedback

1. Data Granularity

• What level of detail is needed for different use cases?
• Should energy and carbon data be separate entities or combined?

2. Calculation Methodology

• How should we handle different calculation methods (measured vs. estimated)?
• What validation is needed for data quality?

3. Integration Points

• How should this entity link to Material, TransactionBatch, and Organization entities?
• What relationships are needed with VerificationStatement entities?

4. Temporal Aspects

• How do we handle data that changes over time?
• What archival/versioning is needed?

5. Multi-Scheme Compatibility

• How can this schema work across different certification programs?
• What additional attributes might be needed for specific regulatory frameworks?

6. Transport Integration

• Is the merged approach for transport and supply chain data appropriate?
• What additional transport-specific attributes are needed?

💬 How to Provide Feedback

• 👍 Thumbs up if this schema direction looks good
• 💬 Comment below with specific suggestions, missing attributes, or real-world use cases
• 🔄 React with specific emojis to highlight priority areas:
  • 🎯 for core functionality
  • ⚠️ for potential issues
  • 💡 for additional ideas

🏆 Success Criteria

A successful EnergyCarbonData entity will enable:

• Consistent tracking of energy and carbon data across certification schemes
• Comprehensive support for lifecycle assessment and carbon accounting
• Seamless integration with diverse regulatory and market requirements
• Robust data transparency and auditability across supply chains

Your expertise in biomass supply chains, energy data, and carbon accounting will help create a robust, practical standard! 🌱