MeetCarbon
Open Cloud
Data access hub

Many sources in, standard records out

MeetCarbon Cloud data access hub keeps sources, connectors, field mappings, and standard datasets on one ledger. Manual entry, bulk import, and the thin IoT channel all become standard records. A failed job can be rerun. A quality item can be released or rejected. Carbon inventory, product footprints, and zero-carbon targets read by subscription. They do not each integrate the source again.

Book a demoSee pricing
Datasets
Activity, energy, materials, logistics
Four sources
Manual, IoT, API, and import
Quality inbox
A release is not a completed inventory
One trace
Record, job, and attestation share it
Overview
Sample data
48
Ingest jobs
jobs · sample
12,640
Standard records
Sample data
7
Quality inbox
Source mix
  • Manual22%
  • IoT41%
  • API24%
  • Import13%
To handle
  • Energy-quantity job failedRerun
  • External API connector probe failedAbnormal
End to end

From a source to a downstream subscription

A source and a connector come first, then a mapping onto a standard dataset. Entry or a pull becomes a record. Quality marks the inbox. After a pass, the trace can be attested, and subscribers read what they subscribed to.

  1. 01

    Register a source

    Internal APIs, external APIs, files, and manual entry stay apart, and so do production and sandbox.

    Sources
  2. 02

    Add a connector

    Manual, IoT, external systems, plus ERP and SRM samples. A disabled connector stops pulling.

    Connectors
  3. 03

    Map to a dataset

    Fields land on activity data, energy quantity, material flow, or a logistics leg. Reserved types stay labeled reserved.

    Dataset catalog
  4. 04

    Enter or pull

    Forms, CSV, and connector jobs all carry a trace. A failed job can be rerun.

    Entry and jobs
  5. 05

    Quality inbox

    Pass, warning, and failure stay apart. A failure can be released or rejected. A release is not a completed inventory.

    Quality
  6. 06

    Trace and deliver

    One trace opens the job and the record. After a pass, an attestation batch can be submitted. Subscribers read by dataset.

    Trace · subscribe
Capability tour

Walk setup, operations, and consumption

The overview is the hero. The nine items below cover sources, connectors, datasets, jobs, quality, trace, attestation, subscriptions, and the developer portal.

Data access hub / Sources

Sources

Ingest setup
In-page views
Internal APIExternal APIFileManual
This page answers

Each origin has one profile, marked production or sandbox, and can be probed. A failed probe is listed on its own.

  • Four origin types stay apart
  • Production and sandbox are not mixed
  • A failed probe is not marked connected
SampleInternal API
External APIProd · ok
Sandbox fileSandbox
Probe failedNot marked connected

Job counts and inbox counts on the sample cards explain the layout. They are not an organisation’s inventory result.

Run states

Connectors, quality, and attestation each keep their own marks

A failed probe and a failed job are not marked successful. A quality release only means the batch may move on. A failed attestation can be retried. A demo transaction id is not a public chain.

Connector

Whether this channel can receive data now.

  • Enabled
    Enabled
    It can pull or receive
  • Disabled
    Disabled
    It no longer pulls
  • Probe failed
    Abnormal
    Listed on its own, not marked connected

Jobs and quality

How far this batch has gone.

  • Job succeeded
    Succeeded
    Written as a standard record
  • Failed, can rerun
    Failed
    Stays on the job list
  • Quality passed
    Passed
    Rules passed and the batch may move on
  • Warning
    Warning
    Read the reason before a release
  • Failed inbox
    Inbox
    Release or reject. A release is not a completed inventory

Attestation

The batch for this trace.

  • Attested
    Attested
    The batch finished
  • In progress
    In progress
    No result yet
  • Failed
    Failed
    It can be retried. A demo id is not a public chain

11 statesOrganisational inventories, reports, and product footprints are finished in the downstream products. A release or an attestation on this page does not replace those conclusions.

Who uses it

Access, mapping, entry, quality, and downstream each open a different page

One ingest ledger. Someone owns sources, someone lines up fields, someone enters numbers, someone clears the inbox, someone reads a subscription.

Question to answer

How many connectors are enabled, which probes failed, and did sandbox mix into production?

What they check
  • Jobs and exceptions on the overview
  • Source probe results
  • Connector status
Menus they use
OverviewSourcesConnectors
Operating loop

Read the overview, run one batch, then clear the inbox

One connection starts on the overview and ends when the record can be traced and a subscriber can read it. Every step can return to the trace.

  1. 1
    Read the overview

    Jobs, the inbox, and connector exceptions decide whether to drill in.

  2. 2
    Open the channel

    Register the source, enable the connector, and keep production apart from sandbox.

  3. 3
    Line up the fields

    Map onto an enabled dataset. Reserved types stay reserved.

  4. 4
    Run one job

    Enter, import, or pull. Failures stay on the list for a rerun.

  5. 5
    Clear the inbox

    Pass, warning, and failure stay apart. A release keeps a record.

  6. 6
    Trace it and leave it downstream

    Open the trace, submit attestation when needed, and let subscribers read.

Boundary

Standard records stay here

Sources, mappings, quality, trace, and subscriptions stay in the data access hub. Device protocols, inventory reports, and energy ledgers have their own products.

This product owns

  • Sources, connectors, and field mappings
  • The dataset catalog and manual entry
  • Ingest jobs, record search, and export
  • Quality rules, releases, and rejections
  • Trace by id and attestation batches
  • Subscriptions, key quotas, monitoring, and the debug bench

Neighboring products own

Hazardous-waste flows and supplier packages are reserved in the catalog. They are not described as vendor-connected. A demo attestation id is not a public chain and not an authority filing.

Getting started

Six steps to connect one source

Create the source and the connector, save a mapping, prove one entry or pull, then quality can show an inbox item and the record can be opened by trace.

Before you start
  • 1Endpoint, credentials, and whether it is production or sandbox
  • 2The standard dataset to write
  • 3One period or meter point you can sample
  • 4The downstream apps that should subscribe

Do not treat a reserved dataset as enabled. A debug sample does not become a formal quality decision.

  1. 1
    Register the source

    Pick internal API, external API, file, or manual, and run one probe.

    Done when · Probe has a result
  2. 2
    Add the connector

    Set the type and enable it. IoT only pulls energy quantity.

    Done when · Status is enabled
  3. 3
    Save the mapping

    Line source columns up with the standard fields of an enabled dataset.

    Done when · Mapping saved
  4. 4
    Prove one write

    Run a form, a CSV, or a pull and keep the trace.

    Done when · Job opens
  5. 5
    See the inbox

    After the rules run, pass, warning, or failure shows in the inbox.

    Done when · Inbox can be handled
  6. 6
    Open the trace

    From the record, return to the job and the source. Submit attestation when you need it.

    Done when · Trace opens
Platform

Many organisations, a trail, and export

The same ingest desk is split by organisation. Sandbox and production, calls, quality decisions, and attestation keep a record. Deployment and price are on the pricing page.

Many organisations

Sources, jobs, records, and subscriptions are split by organisation.

Sandbox and production

A source is marked with an environment. Sandbox samples do not mix into production records.

Call trail

Jobs, quality decisions, key calls, and attestation batches keep a record.

Records can be exported

Export standard records by dataset, period, and source.

SaaS

Turned on per project, on the same account system as MeetCarbon inventory and footprints.

Private deployment

When records and keys must stay on the customer network, the platform can run there.

Neighboring products
Carbon inventoryOrganisational accounting and reports.ViewIoT device managementThing models and device protocols.ViewPricingSaaS, private deployment, and implementation.View
Scenes

Activity data, energy quantity, and material flows all land on this ledger

The main path is the standard record. Downstream apps read by subscription. Reserved datasets stay labeled and are not mixed with enabled types.

Organisational activity data

After activity data and energy quantity are written, carbon inventory reads them by subscription. The inventory stays there.

See the neighboring page

Energy quantity

The thin IoT channel writes time series as energy quantity. Meter models stay in IoT. Sub-meter totals stay in EMS.

See the neighboring page

Materials and logistics

Material flow and logistics legs serve product footprints. Hazardous waste and supplier packages stay reserved.

See the neighboring page

Many downstream subscriptions

The same standard record can be subscribed by inventory, footprint, and zero-carbon targets. They do not each integrate the source again.

See the neighboring page
FAQ

Records, inventories, and device protocols

These five points are what teams check before going live.

How does this split from IoT?

Thing models, device protocols, and field connections stay in IoT. The IoT connector on this page only writes existing time series as energy-quantity records. Meter protocols are not configured here.

How does this split from carbon inventory?

Activity data and energy quantity are stored, checked, and traced here. Organisational boundaries, emission accounting, reports, and disclosure stay in carbon inventory. Inventory reads by subscription. This page does not issue the report.

Does a quality release mean the inventory is finished?

A release only means the standard records may move on, and it keeps a decision record. Emission totals, reports, and footprint conclusions are finished in carbon inventory or the product footprint.

Is attestation a public chain?

The trusted data space submits an attestation batch by trace. States are attested, in progress, and failed. A transaction id in the demo environment only shows the flow. It is not a public chain and not an authority filing.

Can reserved datasets connect to a vendor now?

Hazardous-waste flows and supplier packages are marked reserved in the catalog. The field notes can be read. They are not connected to a real hazardous-waste vendor, and supplier packages are not marked enabled.

Lay out the records from one source

Tell us where the data comes from, which standard dataset it should land in, and whether the subscriber is carbon inventory or a product footprint. We will walk mapping, quality, trace, and subscriptions for that scope.

Book a demoSee pricing