How To Use COMET

The Problem

Today you receive PCFs from 50 suppliers in 50 different formats. Supplier A reports in CO₂e per kg using GaBi, Supplier B reports per tonne using SimaPro with different allocation methods. You cannot compare them without weeks of manual normalization.

With COMET

COMET gives every PCF a shared structure. When your suppliers tag their data with COMET classes, you get comparable footprints automatically — same functional unit, same system boundary definition, same data quality score. Your procurement system ingests COMET-tagged data and ranks suppliers by verified carbon intensity.

The Problem

Scope 3 accounts for 70–90% of most companies’ emissions, but you’re relying on spend-based estimates and industry averages. Category 1 (purchased goods) alone might have hundreds of suppliers, and you have no way to collect, validate, or aggregate their actual footprint data.

With COMET

COMET maps all 15 GHG Protocol Scope 3 categories to specific ontology classes. Your suppliers report using COMET’s SupplyChainLink and ActivityDataRecord classes. The data arrives structured, validated against SHACL shapes, and ready to aggregate — replacing estimates with measured values.

The Problem

You model a product in SimaPro or openLCA, generate a beautiful PCF, then spend days reformatting it for each downstream consumer. The CBAM authority wants XML. The buyer wants a PDF. The PACT platform wants JSON. Each translation introduces errors and costs time.

With COMET

COMET provides a universal export layer. Model your PCF in any LCA tool, export to COMET’s L4 classes, and every downstream system — CBAM, PACT, buyer platforms, verifiers — reads the same structured object. One export, many consumers. No translation errors.

The Problem

You receive a 200-page verification dossier. You manually check emission factors against databases, validate system boundaries against ISO 14067, cross-reference supplier attestations — all by reading documents. Each verification takes 40–80 hours.

With COMET

COMET structures verification claims as machine-readable objects. The AssuranceLevel, AuditTrail, and QualifiedVerifier classes encode the full chain of custody. SHACL shapes auto-validate that all ISO 14067 required fields are present and correctly typed. Your software does the document cross-referencing; you focus on judgment calls.

The Problem

Every new customer integration is bespoke. Customer A uses Ecoinvent, Customer B uses GaBi, Customer C has a proprietary format. You spend 40% of engineering time on data translation layers that add no product value.

With COMET

Build on COMET’s ontology and every COMET-compliant system becomes your customer instantly. npm install @comet/ontology gives you typed classes, SHACL validation, and JSON-LD context — out of the box. New integrations go from 3 months to 3 days.

The Problem

CBAM alone will generate millions of embedded emissions declarations. Your staff reviews them manually. Each declaration references different emission factors, different methodologies, different units. You cannot automate quality checks at scale.

With COMET

When declarants use COMET, their submissions arrive in a structured, validated format. SHACL shapes enforce that every required field is present and correctly typed. Your systems can auto-validate declarations, flag anomalies, and focus human review on edge cases — not data formatting.

The Problem

Carbon risk models rely on disclosed Scope 1+2 data and sector-average emission factors. You cannot distinguish between a steel producer using best-available-technology EAF and one running a century-old blast furnace — they show up in the same sector bucket.

With COMET

COMET’s market signal layer (L7) enables product-level carbon pricing. Each ProductCarbonFootprint carries verified, granular data — specific emission factors, specific processes, specific verification levels. Carbon premiums, CBAM shadow tariffs, and EAC spot prices become tradeable data objects.

The Problem

You develop a DAC project and register it with Gold Standard. A buyer wants Verra-format data. Another wants CAD Trust attestation. A third wants CORSIA-eligible documentation. Each registry has its own data model, and translating between them is manual, error-prone, and expensive.

With COMET

COMET’s L5 EAC layer and CAD Trust v2.0.2 mapping provide a universal credit data structure. Register your project data once using COMET classes, and any registry, buyer, or Article 6 authority can read it. The 13 CAD Trust tables (project, unit, issuance, retirement, verification) are already mapped.