Tech Carbon Standard Schema v0.0.1
The Tech Carbon Standard Schema defines the specific structure for technology carbon emissions data, organised into four main categories that cover the complete technology lifecycle. This schema ensures consistent reporting of technology-related carbon emissions across organisations.
Schema Overview
Schema Information:
- Schema ID:
https://techcarbonstandard.org/schemas/tech_carbon_standard/v0.0.1.json
- Version:
0.0.1
- Parent Schema: Referenced by Emissions Report Schema
- Emission Units: All emissions must be reported in kgCO2e
Key Features:
- Four Emissions Categories: Upstream, direct, indirect, and downstream emissions
- Consistent Measurement: All emissions reported in kgCO2e for comparability
- Flexible Reporting: All categories and sub-categories are optional
- Methodology Documentation: Notes fields for calculation approaches
- GHG Protocol Compliance: Scope 2 emissions include method specification
Document Structure
{
"schema_version": "0.0.1",
"upstream_emissions": {
"software": { "emissions": 0, "notes": "..." },
"employee_hardware": { "emissions": 55000, "notes": "..." },
"network_hardware": { "emissions": 1000, "notes": "..." },
"server_hardware": { "emissions": 0, "notes": "..." }
},
"direct_emissions": {
"onsite_employee_hardware": { "emissions": 5000, "method": "location-based", "notes": "..." },
"networking": { "emissions": 1000, "method": "location-based", "notes": "..." },
"servers": { "emissions": 1000, "method": "mixed-methods", "notes": "..." },
"generators": { "emissions": 0, "notes": "..." }
},
"indirect_emissions": {
"offsite_employee_hardware": { "emissions": 3000, "notes": "..." },
"cloud_services": { "emissions": 5000, "notes": "..." },
"saas": { "emissions": 84000, "notes": "..." },
"managed_services": { "emissions": 1000, "notes": "..." }
},
"downstream_emissions": {
"end_user_devices": { "emissions": 1000, "notes": "..." },
"network_data_transfer": { "emissions": 1000, "notes": "..." }
}
}
Emission Object Structures
Standard Emissions
Most emission categories use this structure:
{
"emissions": 1000,
"notes": "Description of calculation methodology"
}
Field | Type | Required | Description |
---|---|---|---|
emissions | number | Yes | Carbon emissions in kgCO2e (minimum: 0) |
notes | string | No | Notes on calculation methodology or data sources |
Scope 2 Emissions
Direct operational emissions include an additional method field for GHG Protocol compliance:
{
"emissions": 1000,
"notes": "Electricity consumption calculated using grid carbon intensity",
"method": "location-based"
}
Field | Type | Required | Description |
---|---|---|---|
emissions | number | Yes | Carbon emissions in kgCO2e (minimum: 0) |
notes | string | No | Notes on calculation methodology or data sources |
method | string (enum) | No | “location-based”, “market-based”, “mixed-methods”, or “other” |
GHG Protocol Scope 2 Methods:
- location-based: Uses grid average emission factors for electricity consumption
- market-based: Uses emission factors from contractual arrangements (e.g., renewable energy certificates)
- mixed-methods: Combination of location-based and market-based approaches
- other: Alternative methodology (should be explained in notes)
Emissions Categories
1. Upstream Emissions
Embodied carbon in hardware and carbon impact of software development:
"upstream_emissions": {
"software": {
"emissions": 0,
"notes": "Emissions associated with developing and delivering off-the-shelf and open-source software installed on the organisation's systems."
},
"employee_hardware": {
"emissions": 55000,
"notes": "Embodied carbon emissions associated with hardware devices owned by an organisation, including emissions from the manufacture, transportation, installation, maintenance, and end-of-life of a device."
},
"network_hardware": {
"emissions": 1000,
"notes": "When considering the upstream emissions of a network, consider the embodied carbon of any networking devices that are owned by the organisation."
},
"server_hardware": {
"emissions": 0,
"notes": "Servers, storage systems, and data centre infrastructure installed on-premise."
}
}
Category | Description | Typical Calculation |
---|---|---|
software | Emissions from software development and delivery | Development team energy × time × emission factors |
employee_hardware | Embodied carbon in end-user devices | Device count × embodied carbon per device |
network_hardware | Embodied carbon in networking equipment | Equipment embodied carbon from manufacturer data |
server_hardware | Embodied carbon in on-premise servers | Server embodied carbon × quantity purchased |
2. Direct Emissions
Direct running costs attributed to electricity powering technology:
"direct_emissions": {
"onsite_employee_hardware": {
"emissions": 5000,
"notes": "Emissions associated with the operation and use of devices owned by an organisation.",
"method": "location-based"
},
"networking": {
"emissions": 1000,
"notes": "Emissions associated with the operation and use of networking and infrastructure.",
"method": "location-based"
},
"servers": {
"emissions": 1000,
"notes": "The energy consumed by on-premise servers and data centres.",
"method": "mixed-methods"
},
"generators": {
"emissions": 0,
"notes": "Any fossil fuel-powered generators, solar PV, wind turbines, or other systems installed on-site to supply electricity to technology equipment."
}
}
Category | GHG Scope | Description | Typical Calculation |
---|---|---|---|
onsite_employee_hardware | Scope 2 | Office electricity for employee devices | Device power × hours × grid carbon intensity |
networking | Scope 2 | Electricity for networking infrastructure | Equipment power × hours × grid carbon intensity |
servers | Scope 2 | Energy for on-premise servers and data centers | Server power × utilisation × grid carbon intensity |
generators | Scope 1 | On-site fossil fuel power generation | Fuel consumption × emission factors |
Note: Scope 2 categories support the optional method
field for GHG Protocol compliance.
3. Indirect Emissions
Indirect running costs attributed to external hardware and services:
"indirect_emissions": {
"offsite_employee_hardware": {
"emissions": 3000,
"notes": "The emissions incurred by computers (desktops, laptops), monitors, printers, and other devices used by employees, when used out-of-office."
},
"cloud_services": {
"emissions": 5000,
"notes": "The emissions associated with cloud platform services like compute, storage, and networking."
},
"saas": {
"emissions": 84000,
"notes": "The emissions associated with Software-as-a-Service (SaaS) applications."
},
"managed_services": {
"emissions": 1000,
"notes": "The associated emissions of Managed Security Operations, IT support and data backup services."
}
}
Category | Description | Typical Calculation |
---|---|---|
offsite_employee_hardware | Employee devices used outside office | Remote work energy estimates × emission factors |
cloud_services | Third-party cloud platform services | Provider carbon footprint tools and usage data |
saas | Software-as-a-Service applications | Spend-based estimation with industry carbon intensities |
managed_services | Externally managed IT services | Service-specific carbon intensity × usage |
4. Downstream Emissions
Carbon associated with customer use of organisation’s products and services:
"downstream_emissions": {
"end_user_devices": {
"emissions": 1000,
"notes": "This considers the emissions generated from the electricity consumption of devices such as desktops, laptops, tablets, and mobile phones that utilise the products or services provided by an organisation."
},
"network_data_transfer": {
"emissions": 1000,
"notes": "These emissions are associated with the infrastructure enabling data transmission, enabling end-users to access the products and services."
}
}
Category | Description | Typical Calculation |
---|---|---|
end_user_devices | Customer device electricity consumption | User base × device power × usage time × grid intensity |
network_data_transfer | Data transmission infrastructure | Data volume × network infrastructure carbon intensity |
Validation Requirements
Required Fields
schema_version
must be"0.0.1"
emissions
field is required for every emission object includedemissions
must be a non-negative number (≥ 0)
Optional Fields
- All emissions categories are optional at the root level
- All sub-categories within included categories are optional
notes
field is optional but recommended for transparencymethod
field is optional and only applicable to Scope 2 emissions
Validation Rules
- No additional properties allowed at any level
- Emission values must be non-negative numbers
- Method values must be exactly one of the four allowed options
- Schema version must be exactly
"0.0.1"
Complete Example
{
"schema_version": "0.0.1",
"upstream_emissions": {
"software": {
"emissions": 0,
"notes": "Not currently meaningfully calculable or estimatable"
},
"employee_hardware": {
"emissions": 55000,
"notes": "Embodied carbon of purchased laptops and monitors, using production and transportation figures from manufacturers' product lifecycle reports"
},
"network_hardware": {
"emissions": 1000,
"notes": "Loose estimate, based on minimal hardware purchase"
},
"server_hardware": {
"emissions": 0,
"notes": "No servers or storage hardware purchased"
}
},
"direct_emissions": {
"onsite_employee_hardware": {
"emissions": 5000,
"notes": "Calculated using UK grid carbon intensity 2023; exact laptop and monitor counts; and, average laptop and monitor power consumption figures",
"method": "location-based"
},
"networking": {
"emissions": 1000,
"notes": "Loose estimate, based on known minimal networking infrastructure"
},
"servers": {
"emissions": 1000,
"notes": "Loose estimate, based on known minimal infrastructure"
},
"generators": {
"emissions": 0,
"notes": "No generators"
}
},
"indirect_emissions": {
"offsite_employee_hardware": {
"emissions": 3000,
"notes": "Calculated using UK grid carbon intensity 2023; exact laptop and monitor counts; and, average laptop and monitor power consumption figures"
},
"cloud_services": {
"emissions": 5000,
"notes": "Full cloud estate measured using Cloud Carbon Footprinting tool"
},
"saas": {
"emissions": 84000,
"notes": "Spend-based estimate calculated using Plan A platform"
},
"managed_services": {
"emissions": 1000,
"notes": "Loose estimate, based on known minimal managed services"
}
},
"downstream_emissions": {
"end_user_devices": {
"emissions": 1000,
"notes": "Calculated based on www website traffic figures"
},
"network_data_transfer": {
"emissions": 1000,
"notes": "Calculated based on emissions estimate associated with www website and its traffic figures"
}
}
}
Common Validation Errors
Error | Cause | Solution |
---|---|---|
Negative emissions | Emission value < 0 | Ensure all emission values are ≥ 0 |
Invalid method | Wrong method value | Use exactly: “location-based”, “market-based”, “mixed-methods”, or “other” |
Missing emissions field | Emission object without emissions | Add required emissions field to all emission objects |
Wrong schema version | Incorrect version string | Use exactly "0.0.1" |
Additional properties | Extra fields in emission objects | Remove any fields not defined in the schema |
Technical Reference
Schema Definitions
The schema uses two main definitions for emission objects:
Standard Emissions (emissions_def
):
{
"type": "object",
"properties": {
"emissions": { "type": "number", "minimum": 0 },
"notes": { "type": "string" }
},
"required": ["emissions"],
"additionalProperties": false
}
Scope 2 Emissions (scope_2_emissions_def
):
{
"type": "object",
"properties": {
"emissions": { "type": "number", "minimum": 0 },
"notes": { "type": "string" },
"method": { "enum": ["location-based", "market-based", "mixed-methods", "other"] }
},
"required": ["emissions"],
"additionalProperties": false
}
JSON Schema Features
- $defs: Reusable emission object definitions
- $ref: References to shared definitions
- enum: Constrained values for methods and schema versions
- minimum: Validation ensuring non-negative emissions
- additionalProperties: false: Strict schema compliance
Related Documentation
- Router Schema - Entry point for TCS validation
- Reporting Organisation Schema v0.1.0 - Root document structure
- Emissions Report Schema v0.0.1 - Report-level structure
- Implementation Guide - Step-by-step implementation