Data traceability is the ability to verify which inputs and processing steps produced the final result. MRV data management requires connecting raw-data retention with calculation rules, calibration, and revision histories. Chapters 7 and 8 of Technology and Solutions for Demonstrating Carbon Reduction address metrological traceability and calculation traceability together.
Define the concept and scope of application first
Records should capture the source and transformation of values, the rules and people who applied them, and the reasons for changes. Adding a date to a file name may not be enough. The same inputs and processing rules must be available, and accessible under the necessary permissions. Retention periods should be set after checking the purpose of use, applicable programs, contracts, and privacy requirements. Keeping all data indefinitely is not appropriate. The system should retain what is needed for review while controlling use beyond its purpose and access to the data.
Even accurate equipment cannot make a conclusion reliable if the system boundary or baseline is inappropriate. Even if the calculation is correct, insufficient raw data and revision histories limit what can be verified. Accuracy and traceability do not substitute for each other. The quality of measurements and the process by which those values lead to a conclusion must both be checked.
Reporting (R) preserves context and calculations. It documents the entire process by which raw data were processed under particular rules to reach a conclusion. This includes how missing data were filled, which criteria were used to exclude outliers, which model and version were used, and how uncertainty was estimated. A report is evaluated by reproducibility, not by how impressive its conclusion sounds.
Quality control (QC) consists of activities that check consistency, completeness, and errors during data collection and calculation. Quality assurance (QA) includes reviewing whether the system and results meet defined quality objectives. Prevention at the planning stage, checks during implementation, and review of results should complement one another. Specific roles and procedures should follow applicable guidance; QA should not be narrowed to prevention alone, nor QC to corrections made after the fact.
Rules for handling missing data. Decide in advance what to do when data are missing: use linear interpolation, exclude the interval, or substitute a conservative value. Deciding after the fact can lead to choosing the method that produces a more favorable result.
Rules for outliers should also be established in advance. Distinguish values outside physical limits from statistically rare values, and preserve the raw data with reasons for exclusion noted. If criteria are changed after seeing the results, explain when they were changed and how the change affected the analysis.
Simply listing the equipment name does not make a result reproducible. The statement “measured with GreenFeed” is only a small part of the information needed for reproduction. Without details such as how many visits per day counted as valid, the minimum duration per visit, and how recovery rates were corrected, comparison with other studies is not possible. Keeping both protocol details and records of actual implementation is central to QA/QC.
Conditions and limitations of field application
Suppose two reports are prepared for the same period and their emissions-reduction figures differ. The calibration factor or method for handling missing data may have changed. It should be possible to determine which input was changed, when, and which period was affected. If only the result files remain, it is difficult to distinguish an improvement from an error or an inappropriate revision.
Good data combine quality suited to their purpose with traceability. Even if the same calculation can be reproduced, the result may still be wrong if the inputs have a common bias. Verifiability does not substitute for accuracy; it enables others to assess accuracy and scope of application.
A reduction estimate needs both metrological traceability and calculation traceability. Measurement values are linked to a reference through a documented calibration chain and uncertainty, while activity data, emission factors, and models are traced to the final result through their sources, versions, and conditions of application. Not every emissions reduction comes from a single direct measurement. Reviewers should check not only whether the calculation can be reproduced, but also whether the data and methods used are appropriate for the claim.
There is also a common misunderstanding about when verification takes place. If verification is treated as the final stamp on a results table, it is too late. Verification should be the first question in the design process. We need to know what must be verified in order to decide what to record. If someone says, “Let’s get it verified now,” after the project has ended, the necessary records are often no longer available.
Tracer-gas method. Air exchange is estimated using a known release rate or the pattern of concentration decline. Results depend on whether mixing and transport of the tracer gas are sufficiently similar to those of the target gas, and on how background concentration is handled. A method’s name alone does not ensure accuracy.
Evidence needed for investment review
Investors should distinguish a claim that data are stored from a claim that they can be reviewed again. They should check qualified reviewers’ access rights, versions of processing rules, and procedures for recovery and reproduction. Even data that are not disclosed can be structured to allow necessary review under appropriate security and contractual conditions.
Data lineage is the path showing which raw data and transformations produced a final figure. Record unit conversions, corrections, filtering, and aggregation rules along with the equipment and channel and the time of generation. Also retain who ran and approved each process and what was changed later, and why. The fact that raw data remain available and the fact that a qualified reviewer can recheck the processing are conditions that should be examined together.
If lineage is insufficient, reviewers may have difficulty checking how a figure was produced, and acceptance of the data may be limited depending on their intended use. Set retention periods for raw data and revision histories after checking applicable program, contract, and privacy requirements. Do not arbitrarily overwrite data that need to be retained, but do not make indefinite storage of all data the default.
Criteria to keep in view when making a decision
Traceability does not substitute for accuracy. It enables others to assess the suitability of inputs and the calculation pathway. When raw data, records, and review rights are connected, the meaning of the final figure and the reasons for changes can be explained.
About the author
Bongjun Lee graduated from the Graduate School of Management of Technology (MOT) at Sogang University. He spent seven years at Infitron Co., Ltd. and 20 years at Honeywell, working for a total of 27 years in gas measurement in service engineering, technical sales, and channel management. He is now the founder of AI Safety Korea Co., Ltd., where he is researching livestock methane monitoring and measurement, reporting, and verification (MRV) systems using sensors, AI, and data analytics.