When a Thai factory starts CO2 emissions visualization, the first requirement is not an impressive dashboard. It is a data foundation that can recalculate CO2e from electricity and fuel use and explain which invoice, meter, emission factor and approval supports every number. This guide takes Scope 1 and 2 as the practical starting point and covers calculation rules, factor version control, audit trails, RFP requirements, a 90-day proof of concept and acceptance testing.
CO2 emissions visualization is more than an electricity chart
An electricity trend does not by itself constitute a greenhouse-gas inventory. Kilowatt-hours are activity data. CO2e is a calculated result obtained by applying an appropriate emission factor and, where multiple gases are quantified, the applicable global warming potential. Energy monitoring and organisational GHG accounting are connected, but they do not produce the same deliverable.
Our guide to energy-saving measures for Thai factories helps prioritise reduction opportunities, while power-meter data collection and compressed-air monitoring explains practical shop-floor acquisition. This article adds the boundaries, factors, evidence and approvals needed to turn those readings into defensible CO2e data.
Five questions a useful system must answer
Even a polished management dashboard is incomplete if users cannot answer these questions:
- Which legal entity, factory, building, asset and reporting period are included?
- Did the activity data come from an invoice, purchase record, tank issue log or meter?
- Which factor, version, unit and intended use were applied?
- Who estimated, corrected or converted a value, and why?
- Can a closed period be rerun with the same inputs and produce the same result?
The dashboard is the end of the chain. Real visibility connects source evidence, transformations, decisions and approvals so that a number is not only visible but explainable.
Start manufacturing GHG emissions management with Scope 1 and 2
TGO describes a Carbon Footprint for Organization as organisational GHG emissions and removals expressed in kilograms or tonnes of CO2 equivalent. Its CFO page identifies Scope 1 as direct emissions from sources owned or controlled by the organisation, Scope 2 as emissions from generating purchased electricity, heat or steam consumed by the organisation, and Scope 3 as other indirect emissions. Starting a PoC with Scope 1 and 2 does not make Scope 3 unimportant. It gives the team a manageable boundary in which data owners and monthly controls can be established.
Decide organisational and reporting boundaries separately
List the legal entities, factories, warehouses and leased areas first. Then classify the sources at each site. Company-controlled boilers, factory vehicles and fugitive refrigerants may be Scope 1 sources. Purchased electricity is typically a Scope 2 source. Contracted transport and purchased materials normally belong to the later Scope 3 assessment and should not be forced into a 90-day Scope 1 and 2 PoC.
Acquisitions, leased assets, power-purchase agreements and renewable-energy instruments need a documented policy, not an assumption by the system vendor. Finance, EHS, legal and, where necessary, external specialists should decide the appropriate consolidation and reporting approach.
Build a source register around evidence flow
The register should describe how data moves, not merely list equipment names.
| Field | Example | Control purpose |
|---|---|---|
| Source ID | TH01-S1-BOILER-01 | Preserve identity after name changes |
| Site and cost centre | Rayong / Utilities | Assign aggregation responsibility |
| Scope and category | Scope 1 / stationary combustion | Maintain classification consistency |
| Activity-data source | Fuel invoice, issue log, flow meter | Define the system of record |
| Unit | L, kg, Nm3, kWh | Prevent conversion errors |
| Frequency and close date | Monthly, third business day | Fix the operating calendar |
| Data owner | Utility Manager | Chase missing submissions |
| Approver | EHS Manager | Create segregation of duties |
Recording the complete path from source to activity data, evidence and approval turns the register into system requirements.
Design the CO2e engine around emission-factor versions
The basic pattern is activity data multiplied by an appropriate factor. GWP may be applied to gas-specific quantities before combining them as CO2e. The arithmetic is easy; retaining why a factor was chosen and when it applied is the difficult part.
Do not mix the TGO CFO table with T-VER electricity factors
TGO’s CFO page labels its current table “Emission Factor CFO (January 2026)” and displays fuel or activity names, units, gas-specific values, total CO2e and references. Never copy a value without its context. Store the publisher, source URL, factor-set name, version, activity type, input and output units, effective dates, calculation method, registrant and reviewer.
TGO’s T-VER area also publishes notices and reference data, including electricity-factor material effective on 21 May 2026 for applicable projects or activities. That programme context is not automatically the same as an organisational Scope 2 inventory. A corporate inventory, a reduction project and a product footprint can require different boundaries or methods. “Newest Thai official value” is therefore not a sufficient selection rule.
Give every factor an immutable ID and validity period
Do not use a display label such as “Grid electricity” as the database key. A Thai translation or naming improvement must not make an old calculation look as if it used a new factor. Add a new record when a version changes and close the old validity period instead of overwriting it. A rerun of April 2026 should normally reproduce the factor approved for that reporting period.
Publication date and effective date may differ. If a retrospective change is required, identify every affected site, period and source. Record the result before and after recalculation, the approval and whether an external submission must be corrected. Recalculating all history with the newest value destroys reconciliation with numbers previously reported.
Treat unit conversions as auditable calculations
Fuel may be purchased in kilograms, issued in litres and paired with a kg CO2e per litre factor. Density, temperature conditions and the validity period of the conversion then become controlled data. Store the input value, input unit, conversion value and source, unrounded converted value and resulting unit. Hidden spreadsheet cells and personal knowledge are not a durable control.
Create an audit trail in the emissions data model
The centre of the platform is lineage, not an aggregate table. A minimum model has five layers: activity records, factor records, calculation results, evidence objects, and approval/change logs.
Preserve source-document granularity
One monthly electricity row may be convenient, but it is hard to explain when invoices cover several meters and reading periods do not match calendar months. Retain the invoice period, meter ID, invoice number, receipt date, file hash or controlled link, and the allocation rule used for the reporting month. For IoT data, specify raw-data retention, time zone, missing-data logic and cumulative-counter reset detection.
Correct records instead of silently overwriting them
The system should show values before and after a change. After close, preserve the original record and link a reversal or correction. Require a reason code, explanatory note and supporting evidence. Log who changed the item, when it happened and whether it came from a user interface or integration.
Show data quality beside CO2e
Several decimal places can hide whether a number is measured or estimated. A factory can define an internal scale such as measured from invoice or calibrated meter, measured with controlled conversion, approved allocation, and provisional estimate. This scale is an internal management example, not an official rating. Define each class, its acceptable share and remediation deadline. A jump in estimated data from 3% to 12% can reveal a broken acquisition process before it affects an external report.
Check formulas and rounding with a fictional scenario
The following factory is entirely fictional. The factors are invented to test calculation, units and rounding; they are not TGO factors, statutory factors or actual Thai grid values. Production use must replace them with applicable, approved and versioned sources.
| Activity | Fictional activity data | Fictional factor | Result |
|---|---|---|---|
| Purchased electricity | 1,240,000 kWh | 0.500 kg CO2e/kWh | 620,000 kg CO2e |
| Diesel | 18,500 L | 2.700 kg CO2e/L | 49,950 kg CO2e |
| LPG | 12,000 kg | 3.000 kg CO2e/kg | 36,000 kg CO2e |
| Total | — | — | 705,950 kg CO2e |
The calculation is activity data multiplied by the factor. Dividing 705,950 kg by 1,000 gives 705.950 t CO2e, displayed as 706.0 t CO2e when rounded to one decimal place. Retain the unrounded value and round only for presentation. Early row-level rounding can create material differences across many meters.
This example also creates acceptance tests: reject incompatible units, warn about a factor outside its validity period, verify kg-to-tonne conversion and expose the unrounded value through the audit view or API.
Connect electricity visualization to an energy management system
High-frequency electricity data is a valuable Scope 2 input, but utility invoices and submeter totals serve different purposes. The invoice is often the financial source of record. Submeters support allocation, production analysis and anomaly detection.
Reconcile invoice, main meter and submeters
A monthly control should:
- Import the invoice period and kWh.
- Compare the same-period difference from the incoming main meter.
- Compare submeter totals and unmetered load as an energy balance.
- Investigate time shifts, missing intervals, CT ratios, meter replacement or counter resets outside tolerance.
- Mark unresolved differences as approved allocations with a quality flag.
Flow-meter monitoring in Thai factories can similarly provide evidence for fuel, steam or compressed-air allocation. A sensor feed is not self-validating: calibration, communication loss, tag changes and time synchronisation remain part of the control environment.
Keep energy and carbon KPIs distinct
Electricity intensity may improve while CO2e intensity moves differently because of product mix or factor changes. A renewable-energy arrangement may change reported Scope 2 without improving machine efficiency. Display energy use, energy intensity, location-based emissions, market-based emissions when relevant, and data quality as separate KPIs.
Build the foundation for a carbon-neutral factory in a 90-day PoC
Do not promise a complete enterprise inventory in 90 days. Define the PoC as making one representative factory’s Scope 1 and 2 reproducible for one monthly close. Success measures should cover source completeness, evidence linkage, on-time approval and recalculation consistency rather than the number of dashboard pages.
Days 1–30: boundary, register and evidence diagnosis
Bring together EHS, finance, purchasing, utilities, IT and factory management. Trace three recent months of electricity invoices, fuel purchases and issues, refrigerant records and meter lists. Deliver an organisational and reporting boundary memo, source register, data-flow map, factor policy and issue log.
Do not limit interviews to API availability. Find changing CSV columns, non-calendar billing periods, fuels in multiple units and scanned-only invoices. Map local Thai names to corporate English names while keeping language-independent IDs.
Days 31–60: minimum pipeline and calculations
Implement controlled invoice upload, CSV or API ingestion, validations, factor selection, CO2e calculation and approval. Automation should follow risk and volume: frequent electricity can be integrated, while infrequent fuels may use controlled manual entry with unit lists, prior-month checks, mandatory evidence and two-person approval.
Provide drill-down by factory, scope, source and month. Every total should lead to the activity record, factor and evidence. A factor change should show its impact before approval and should not alter production totals prematurely.
Days 61–90: monthly close, exceptions and acceptance
Run one close with real operational data. Deliberately test missing intervals, duplicate uploads, late invoices, incompatible units, backdated factor changes and rejected approvals. A demo that handles only the happy path does not prove operational readiness.
At the end, document unmetered sources, reliance on estimates, off-system tasks and Scope 3 candidates as a prioritised backlog. A credible carbon-neutral factory roadmap begins with a baseline and reduction results that can be compared under consistent rules.
Write a comparable RFP for manufacturing GHG management
“We need a carbon dashboard” does not give bidders a consistent scope. Separate data, calculation, workflow, security, performance and operational-support requirements.
Separate mandatory PoC requirements from future options
Make Scope 1 and 2 for one factory, a monthly close, evidence, factor versioning, approvals and an audit export mandatory. Put Scope 3, product allocation, supplier portals, renewable-energy instruments, multi-entity consolidation, additional languages and external disclosure formats in a future roadmap.
Ask bidders directly:
- Are factors overwritten or versioned, and can old periods be reproduced?
- Can lineage from a reported total to source evidence be exported?
- How are correction, approval, reopening and access rights logged?
- Who receives an API or missing-data alert and within what time?
- How are bilingual labels separated from immutable IDs?
- Where are source files stored, encrypted, retained and backed up?
- Who can update factors and source registers after go-live?
- How are customer-specific requests separated from the corporate inventory?
Evaluate data portability, not only SaaS versus custom build
The organisation should be able to export activity data, factors, results, evidence metadata and approval history in documented formats. Confirm API limits, data location, retrieval time after contract termination and return of attachments. A tool change must not erase the base year or audit trail.
Use acceptance tests to prove operational control
At minimum, test these fifteen behaviours:
- Import a valid value, unit and period.
- Prevent double counting when a file is resubmitted.
- Quarantine an unknown meter or fuel code.
- Warn instead of silently converting an incompatible unit.
- Block a factor outside its effective period.
- Reproduce the same result with the same inputs and versions.
- Retain unrounded and displayed values separately.
- Prevent closure without required evidence.
- Separate preparer and approver.
- Retain rejection reasons and resubmission history.
- Export before-and-after values for post-close corrections.
- Process timestamps consistently in ICT.
- Restrict source evidence by site access.
- Restore from backup within the agreed objective.
- Trace an audit sample from total to source document.
Quantify pass criteria. Examples might be 100% of in-scope sources present in the register, at least 95% of monthly activity linked to source evidence, zero difference on recalculation of an approved period and zero critical defects. These thresholds are sample PoC decisions, not statutory limits.
Prepare for customer requests, Thailand Taxonomy and CBAM
Do not treat a policy label as a dashboard feature. Convert every external request into a data specification: who wants data, for which product, period, boundary, method and assurance level.
Use Thailand Taxonomy Phase 2 as a reference tool
Thailand Taxonomy Phase 2 was published on 27 May 2025 and added manufacturing, agriculture, construction and real estate, and waste management. The Bank of Thailand describes its use as a reference tool for defining and classifying environmentally sustainable activities and for policies, strategies, financing opportunities and climate-risk management. Its publication alone does not create a blanket legal CO2 reporting obligation for every Thai factory.
An investment or financing discussion may nevertheless refer to technical criteria, transition classifications or safeguards. Link capital projects, production lines, baseline and post-project activity, calculation methods and evidence so that a classification rationale can later be supported. Determine actual alignment against the relevant document and transaction terms.
Do not generalise CBAM to all Thai manufacturing
The EU CBAM definitive regime applies from 1 January 2026. The European Commission lists cement, iron and steel, aluminium, fertilisers, electricity and hydrogen. The principal declaration and certificate obligations concern EU importers or indirect customs representatives handling covered goods, not every manufacturer in Thailand.
A Thai producer or processor in a covered chain may still receive requests for embedded-emissions and process data. A supplier of non-covered goods may receive a customer’s voluntary questionnaire. Record the product, customs classification, production period, requested direct and indirect emissions, verification format and confidentiality rules. A product request is not identical to the factory’s corporate Scope 1 and 2 total, although the same controlled activity data can support both.
Design for future verification with ISO 14064-1
ISO 14064-1:2018 addresses organisation-level quantification and reporting and includes inventory design, development, management, reporting and verification. ISO states that the edition was confirmed in 2024 and remains current, while also showing revision work. ISO/TS 14064-4:2025 supplies application guidance.
Whether or not third-party verification or assurance is planned, relevance, completeness, consistency, accuracy and transparency are useful design tests for an RFP and acceptance plan. Any formal claim of conformity or assurance should be checked against the purchased standard, the applicable programme and verifier requirements.
Operate monthly controls after go-live
The most common operational weakness is unclear close ownership. Fix dates for submission, first review, exception resolution, approval, close and management reporting, and name a delegate for absences.
Management KPIs
- Scope 1 and 2 total and year-on-year change
- Emissions and energy intensity per production unit
- Contribution by source
- Share of measured, converted, allocated and estimated data
- Missing, unapproved and exception records
- Evidence-link rate
- Factor version and impact of updates
- Actual reduction results against the approved baseline
Total change alone cannot separate output growth, product mix, weather, factor revisions and efficiency. Use a bridge analysis to distinguish operational improvement from accounting-method changes.
Quarterly master-data review
Check new and retired assets, sites, fuels, PPAs, meter replacements and organisational changes. Monitor factor publishers and review applicability and affected periods before implementation. Master-data changes deserve the same approval discipline as the emissions total.
Conclusion: make CO2e explainable within 90 days
CO2 emissions visualization is a chain from activity data through conversions, factors, calculations, evidence and approvals. Fix a Scope 1 and 2 boundary, version every factor and run an actual monthly close in a 90-day PoC. That creates a practical foundation for customer responses, management decisions and later assurance. Treat Thailand Taxonomy and CBAM according to their real scope, and translate each request into specific data requirements instead of assuming a universal legal duty.
TOMAS TECH can help structure a source register, choose electricity and fuel acquisition methods, define factor governance, draft an RFP and set acceptance criteria for a 90-day PoC. If you are still assessing how much of your Thai factory’s current meters and records can be reused, contact us for an initial discussion.
FAQ about CO2 emissions visualization
What does CO2 emissions visualization mean?
It converts activity data such as electricity, fuel and refrigerant use into CO2e and lets users review the result by factory, scope, source and period. A robust implementation also traces source evidence, factor versions, conversions, approvals and corrections.
Should a manufacturing GHG project include Scope 3 from day one?
It depends on the objective and customer requirements. A 90-day PoC can establish controls for Scope 1 and 2 while identifying priority Scope 3 categories and data owners for phased expansion. This sequencing does not imply that Scope 3 is unimportant.
Is an electricity visualization system enough for Scope 2 reporting?
No. Meter readings are valuable activity data, but reporting also requires a boundary, billing-period treatment, missing-data rules, the selected method and factor, evidence and approval.
Is an energy management system the same as carbon management?
They share data but serve different purposes. Energy management focuses on equipment efficiency and anomalies. Carbon management adds organisational boundaries, factor governance, CO2e calculation, external reporting and audit trails.
Should the newest TGO factor be applied to all historical periods?
Not automatically. Confirm intended use, activity, unit, version, publication and effective dates, reporting method and recipient. Preserve the factor used for a previously closed period unless an approved recalculation is required.
Is Thailand Taxonomy mandatory for every Thai factory?
BOT presents Phase 2 as a reference tool. Its publication alone does not impose a uniform statutory CO2 reporting duty on all factories. Check the relevant financing terms, customer contract and corporate policy.
Does every Thai manufacturer need CBAM compliance?
No. The official sector scope covers selected goods in cement, iron and steel, aluminium, fertilisers, electricity and hydrogen, and the main obligations concern covered EU importers. Thai suppliers in relevant chains may nevertheless need to provide customer data.
What information makes 90-day PoC quotations comparable?
Give every bidder the same factories, source count, interfaces, data history, users, approval stages, evidence volume, languages, outputs and acceptance conditions. Separate licences, implementation, integration, cleansing, training and support.
References
- TGO: Emission Factor CFO, January 2026
- TGO: Carbon Footprint for Organization and scope definitions
- TGO T-VER announcements and reference data
- GHG Protocol Corporate Standard FAQ
- GHG Protocol Corporate Standard
- ISO 14064-1:2018
- ISO/TS 14064-4:2025
- Bank of Thailand: Thailand Taxonomy Phase 2
- Thailand Taxonomy Phase 2: Manufacturing
- European Commission: CBAM definitive regime
