TianGong PCR产品类别规则

Computer game software, packaged

Computer game software, packaged: This PCR covers published computer game software supplied on magnetic or optical physical media as a complete saleable packaged…

Lifecycle status
Candidate
Content maturity
Authored methodology
Current version
No published version
Readiness
Review required
Last updated

Methodology and translation states come from the source record; publishing this website does not change their review status.

Content languages

zh-CN · Aligned
Status, classification and source details

Readiness

  • Warnings methodology_not_reviewed Authored methodology is candidate guidance and still requires methodology review.

Classification mapping

CPC 3.0:47822 · exact

Source

1. Scope and Applicability

This PCR covers published computer game software supplied on magnetic or optical physical media as a complete saleable packaged product. The foreground boundary begins with accepted software source/build inputs and purchased unrecorded media and unit-packaging components, includes the electricity attributable to development/build work, physical-media replication, inspection and unit packaging, and ends with the packaged product at the publisher's distribution gate.

The product identity follows CPC 3.0 code 47822. Computer game cartridges designed for a specific console, software delivered only by download, and online game services are outside this PCR. Downstream distribution, gameplay electricity and hardware, maintenance, account services and end-of-life are excluded from the default cradle-to-gate dataset and require a separately declared boundary expansion.

The declared media route must be optical or magnetic. Only components and reject streams that actually occur in the modeled product and batch are included.

2. Product Category Identity

FieldValue
canonical_pcr_idpcr.metal-products-machinery-and-equipment.radio-television-and-communication-equipment-and-apparatus.computer-game-software-packaged
classification_refsCPC 3.0: 47822, Computer game software, packaged
covered_productsPublished computer game software presented on magnetic or optical physical media and sold as a packaged product
excluded_productsConsole-specific game cartridges; computer game software downloads; online games; system software; non-game application software
representative_productA complete saleable packaged copy containing recorded optical or magnetic media and the unit packaging declared by the producer
production_routeSoftware development/build followed by optical-media or magnetic-media replication, inspection and unit packaging
market_stateFinished, recorded, packaged software product at the publisher distribution gate

3. Reference Flow

FieldValue
WhatComplete saleable packaged computer game software on the declared optical or magnetic physical-media route
How much1 kg of finished packaged product, including recorded medium and all unit packaging supplied with the product
How wellPlayable or installable for the declared platform and media format; passes the producer's release, readability and packaging acceptance criteria
How long or cycleOne completed production batch at the publisher distribution gate; no gameplay or service lifetime is represented
reference_flow_linkreference_product
FieldValue
Reference amount1
Reference product flowComputer game software, packaged b4e24ad6-6c52-4158-b19f-a30bdf4da53a
Reference flow propertyMass 93a60a56-a3c8-11da-a746-0800200b9a66
Reference unit groupUnits of mass 93a60a57-a4c8-11da-a746-0800200c9a66
Reference unitkg
Required qualifierssoftware title or release family; declared platform; optical or magnetic media route; media format; included unit-packaging components; production geography; production period; publisher distribution-gate boundary

When constructing a foreground data package, the items listed in Required qualifiers must be declared in dataset metadata, process notes, reference flow comment, product description, or an equivalent data package field. Missing required qualifiers make the reference flow definition incomplete for that data package.

4. Measurement and Unit Rules

rule_idApplies toRequired propertyRequired unitRule
reference_product_massfinished packaged reference productMass 93a60a56-a3c8-11da-a746-0800200b9a66kgMeasure accepted finished units with their recorded medium and all unit packaging; exclude shipping cartons, pallets and downstream distribution packaging unless the declared boundary is expanded.
electricity_energydevelopment/build and replication/packaging electricityNet calorific value 93a60a56-a3c8-11da-a746-0800200c9a66MJRetain meter or invoice readings in their original unit and convert kWh to MJ using MJ = kWh × 3.6; record only electricity attributable to the declared production period and foreground activities.
component_massunrecorded media and packaging inputsMass 93a60a56-a3c8-11da-a746-0800200b9a66kgUse one consistent as-received mass basis for input, reject and accepted-output records; document tare removal and moisture assumptions where relevant.
count_to_massrecords available only by item countMass 93a60a56-a3c8-11da-a746-0800200b9a66kgConvert counts using a batch-representative measured average mass per item; preserve sample size, sampling date and calculation.

5. System Boundary

Boundary Abstraction

FieldValue
declared_starting_conditionAccepted software source/build inputs plus purchased unrecorded physical media and unit-packaging components received for the declared production batch
starting_condition_roleForeground starting condition; upstream burdens of purchased electricity, media and packaging remain linked through supplier datasets
product_classification_scopePackaged computer game software on magnetic or optical media under CPC 3.0 code 47822
recursive_input_ruleA purchased packaged game-software input used in production remains a separately recorded product input and links to an upstream dataset; its production is not recursively recreated inside this foreground system
upstream_dataset_requirementLink every purchased electricity, medium, packaging component and material development/build hardware exchange to a geographically and technologically representative upstream dataset and disclose any proxy
disclosureDeclare software release, platform, physical-media route, included package configuration, production geography and period, allocation basis, development-hardware materiality assessment, cut-offs and any boundary expansion
rule_idApplies toRulesource_ids
boundary_product_identityproduct selectionInclude only a packaged computer game product presented on magnetic or optical physical media; exclude cartridges, downloads and online game services.un-cpc-3-0-explanatory-notes-2025
boundary_foreground_gateforeground systemInclude development/build work attributable to the release, physical-media replication, inspection, rejects and unit packaging through the publisher distribution gate.
boundary_software_infrastructuresupporting compute and infrastructureInclude electricity and other exchanges only for supporting resources actually used by the declared software-production work and allocate shared resources transparently.green-software-foundation-sci-1-1-0
boundary_development_hardwaredevelopment/build hardwareAssess all servers, desktop workstations, portable computers, storage and network devices, and test consoles or other test devices used to produce the release. For every material device, add one separate atomic product input using the actual device identity and an upstream hardware LCA dataset; disclose and justify every exclusion against the declared materiality cut-off.green-software-foundation-sci-1-1-0
boundary_downstream_exclusionsdownstream stagesExclude downstream distribution, gameplay, maintenance, online services and end-of-life unless a boundary expansion is explicitly modeled and separately reported.
boundary_recursive_inputsame-category purchased inputsKeep any purchased packaged game-software input visible as an upstream-linked product exchange; do not recurse into another foreground copy of this PCR.

6. Process Inventory Structure

Process Map

process_idprocess_nameinclusioninclusion_conditionrolequantitative_reference
software_development_buildSoftware development and release buildrequiredAlways include electricity attributable to development, compilation, integration, testing and release-build work, complete the development-hardware materiality assessment, and add separate atomic hardware product exchanges for every material device used for the declared release.foreground productionAllocated to the accepted packaged-product mass of the declared batch
media_replication_packagingPhysical-media replication and unit packagingrequiredAlways include the selected optical or magnetic route, inspection, rejected media, accepted product and the unit-packaging components actually used.foreground production1 kg accepted packaged product
downstream_distributionDownstream distributionexcluded_by_defaultInclude only in a separately declared boundary expansion.downstream optionalDeclared expanded reference flow
gameplay_and_maintenanceGameplay, hardware use and maintenanceexcluded_by_defaultInclude only in a separately declared use-stage study with a service functional unit.downstream optionalDeclared expanded functional unit
end_of_lifeProduct end-of-lifeexcluded_by_defaultInclude only in a separately declared end-of-life expansion with destination-specific flows.downstream optionalDeclared expanded reference flow

Process: Software development and release build (software_development_build)

Inputs

Product flows
Development and release-build electricity (development_electricity)

Purchased electricity crosses the foreground boundary for development workstations, build servers, test equipment and supporting infrastructure attributable to the declared software release.

  • Selected flow: Electricity 890a70b7-b677-4e2a-8a1b-7d017e0a10ae
  • Flow property / unit: Net calorific value 93a60a56-a3c8-11da-a746-0800200c9a66 / MJ 93a60a57-a3c8-11da-a746-0800200c9a66
  • Amount rule: Metered or invoiced electricity attributable to the declared activities and period, allocated to the accepted packaged-product mass
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per 1 kg accepted packaged product
  • Basis kind: Reference flow (reference_flow)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_development_electricity
  • Sources: green-software-foundation-sci-1-1-0

Development hardware materiality and dataset-added atomic exchanges. Complete protocol cp_development_hardware_materiality for every site, cloud allocation and test environment within the declared release boundary. For each material server, desktop workstation, portable computer, storage device, network device, test console or other test device, add a separate product-input exchange using the actual Tiangong device identity, its own flow property and supplier-dataset reference unit. Allocate each device exchange by its documented time share and reserved-resource share. Do not combine different devices under a selected flow such as “development hardware.” If a device is excluded, retain its identity, screening result, declared cut-off, quantitative basis and approval.

Waste flows

None required by this PCR. Record any specific waste that actually crosses the process boundary as a separate atomic exchange.

Elementary flows

None prescribed. Direct elementary exchanges must be measured and added as individual flows when they occur; upstream electricity emissions remain in the linked electricity dataset.

Outputs

Product flows

No separately exchanged product output is prescribed. The release build is an internal result transferred to media_replication_packaging; its shared burdens are allocated to the final packaged reference product.

Waste flows

None prescribed.

Elementary flows

None prescribed.

Process: Physical-media replication and unit packaging (media_replication_packaging)

Inputs

Product flows
Replication and packaging electricity (replication_packaging_electricity)

Electricity used by recording, replication, inspection and unit-packaging equipment crosses the foreground boundary.

  • Selected flow: Electricity 890a70b7-b677-4e2a-8a1b-7d017e0a10ae
  • Flow property / unit: Net calorific value 93a60a56-a3c8-11da-a746-0800200c9a66 / MJ 93a60a57-a3c8-11da-a746-0800200c9a66
  • Amount rule: Metered batch electricity less documented non-production loads
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per 1 kg accepted packaged product
  • Basis kind: Reference flow (reference_flow)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_replication_electricity
  • Sources:
Unrecorded optical medium (unrecorded_optical_media)

Include this input only for an optical-media product route. It is the unrecorded physical medium received for replication.

  • Selected flow: Optical media, not recorded 714535e8-24d4-44bf-8496-4837f638fdd4
  • Flow property / unit: Mass 93a60a56-a3c8-11da-a746-0800200b9a66 / kg 93a60a57-a4c8-11da-a746-0800200c9a66
  • Amount rule: As-received optical-medium mass issued to the batch
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per 1 kg accepted packaged product
  • Basis kind: Reference flow (reference_flow)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_media_mass
  • Sources:
Unrecorded magnetic medium (unrecorded_magnetic_media)

Include this input only for a magnetic-media product route. It excludes magnetic-stripe cards.

  • Selected flow: Magnetic media, not recorded, except cards with a magnetic stripe 40bcd8b1-541d-4314-9e57-fc1250fd692e
  • Flow property / unit: Mass 93a60a56-a3c8-11da-a746-0800200b9a66 / kg 93a60a57-a4c8-11da-a746-0800200c9a66
  • Amount rule: As-received magnetic-medium mass issued to the batch
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per 1 kg accepted packaged product
  • Basis kind: Reference flow (reference_flow)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_media_mass
  • Sources:
Rigid polypropylene media case (rigid_polypropylene_media_case)

Include this input only when the saleable unit contains a rigid polypropylene media case. The exact Tiangong UUID remains unresolved.

  • Selected flow: Rigid polypropylene media case
  • Flow property / unit: Mass 93a60a56-a3c8-11da-a746-0800200b9a66 / kg 93a60a57-a4c8-11da-a746-0800200c9a66
  • Amount rule: Net mass of accepted and rejected cases issued to the batch
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per 1 kg accepted packaged product
  • Basis kind: Reference flow (reference_flow)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_case_mass
  • Sources:
Paper box (paper_box)

Include this input only when a paper box forms part of the saleable unit.

  • Selected flow: Paper box 12d5d744-7725-4dbc-b102-43c80547f777
  • Flow property / unit: Mass 93a60a56-a3c8-11da-a746-0800200b9a66 / kg 93a60a57-a4c8-11da-a746-0800200c9a66
  • Amount rule: Paper-box mass issued to the batch
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per 1 kg accepted packaged product
  • Basis kind: Reference flow (reference_flow)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_paper_box_mass
  • Sources:
Packaging paper insert (packaging_paper_insert)

Include this input only when a paper manual, leaflet or printed insert is supplied inside the saleable package.

  • Selected flow: Packaging, paper insert b4681b7b-ff95-4df8-804a-fff06aa3c3aa
  • Flow property / unit: Mass 93a60a56-a3c8-11da-a746-0800200b9a66 / kg 93a60a57-a4c8-11da-a746-0800200c9a66
  • Amount rule: Paper-insert mass issued to the batch
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per 1 kg accepted packaged product
  • Basis kind: Reference flow (reference_flow)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_paper_insert_mass
  • Sources:
Waste flows

No waste input is prescribed.

Elementary flows

None prescribed. Direct elementary exchanges must be recorded individually if they occur.

Outputs

Product flows
Accepted packaged computer game software (reference_product)

The accepted output is the complete recorded medium and all unit packaging supplied as the saleable product at the publisher distribution gate.

  • Selected flow: Computer game software, packaged b4e24ad6-6c52-4158-b19f-a30bdf4da53a
  • Flow property / unit: Mass 93a60a56-a3c8-11da-a746-0800200b9a66 / kg 93a60a57-a4c8-11da-a746-0800200c9a66
  • Amount rule: exactly 1 kg of accepted finished packaged product
  • Value mode: Fixed value (fixed_value)
  • Specificity: Generic (generic)
  • Normalization basis: reference flow
  • Basis kind: Reference flow (reference_flow)
  • Evidence kind: Identity reference (identity_reference)
  • Collection protocol:
  • Sources: un-cpc-3-0-structure-2025; un-cpc-3-0-explanatory-notes-2025
Waste flows
Rejected optical medium (rejected_optical_media)

Include only for an optical-media route when rejected recorded or unrecorded optical media leave the foreground process as waste. The exact Tiangong UUID remains unresolved.

  • Selected flow: Rejected optical media
  • Flow property / unit: Mass 93a60a56-a3c8-11da-a746-0800200b9a66 / kg 93a60a57-a4c8-11da-a746-0800200c9a66
  • Amount rule: Measured net mass transferred to the documented waste destination
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per 1 kg accepted packaged product
  • Basis kind: Reference flow (reference_flow)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_reject_mass
  • Sources:
Rejected magnetic medium (rejected_magnetic_media)

Include only for a magnetic-media route when rejected recorded or unrecorded magnetic media leave the foreground process as waste. The exact Tiangong UUID remains unresolved.

  • Selected flow: Rejected magnetic media
  • Flow property / unit: Mass 93a60a56-a3c8-11da-a746-0800200b9a66 / kg 93a60a57-a4c8-11da-a746-0800200c9a66
  • Amount rule: Measured net mass transferred to the documented waste destination
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per 1 kg accepted packaged product
  • Basis kind: Reference flow (reference_flow)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_reject_mass
  • Sources:
Polypropylene case waste (polypropylene_case_waste)

Include only when rejected or damaged polypropylene cases leave the foreground process as waste.

  • Selected flow: Polypropylene Wastes 88215d1b-e6b6-4ec7-af7f-83375e80637b
  • Flow property / unit: Mass 93a60a56-a3c8-11da-a746-0800200b9a66 / kg 93a60a57-a4c8-11da-a746-0800200c9a66
  • Amount rule: Measured net waste mass transferred to the documented destination
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per 1 kg accepted packaged product
  • Basis kind: Reference flow (reference_flow)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_reject_mass
  • Sources:
Paper packaging waste (paper_packaging_waste)

Include when rejected paper boxes, inserts or other paper unit-packaging components leave the foreground process as waste.

  • Selected flow: Paper and cardboard packaging waste a318022d-c960-4eb5-a81c-04a9c4dda7e4
  • Flow property / unit: Mass 93a60a56-a3c8-11da-a746-0800200b9a66 / kg 93a60a57-a4c8-11da-a746-0800200c9a66
  • Amount rule: Measured net waste mass transferred to the documented destination
  • Value mode: Foreground record (foreground_record)
  • Specificity: Site-specific (site_specific)
  • Normalization basis: per 1 kg accepted packaged product
  • Basis kind: Reference flow (reference_flow)
  • Evidence kind: Collected record (collected_record)
  • Collection protocol: cp_reject_mass
  • Sources:
Elementary flows

None prescribed. Add separately measured direct elementary releases only as species-specific flows.

7. Allocation and Co-product Handling

rule_idApplies toRulesource_ids
allocation_avoidall foreground processesPrefer subdivision and direct metering by software release, production line and batch before applying allocation.
allocation_developmentshared development/build electricityAllocate measured supporting-resource electricity by documented CPU time, workstation hours or another causal activity measure attributable to the declared release; if no causal measure exists, use a disclosed time-based share and justify it.green-software-foundation-sci-1-1-0
allocation_development_hardwarematerial development/build hardwareFor each separately identified device, allocate the linked hardware inventory by both the fraction of expected device life reserved for the release and the fraction of device resources reserved for the release. Preserve actual device identity and do not allocate downstream gameplay hardware unless it was also used to produce or test the release.green-software-foundation-sci-1-1-0
allocation_replicationshared replication and packaging operationsAllocate shared batch electricity and materials by accepted packaged-product mass when products use the same equipment; use a documented causal machine-time basis when routes materially differ.
allocation_recyclingwaste and recycling outputsApply cut-off at the point the waste leaves the foreground boundary unless an avoided-burden expansion is explicitly declared; do not credit potential recycling in the default dataset.

8. Foreground Data Collection, Calculation, and Quality Rules

Data Collection Protocols

protocol_idprocess_idflow_rolerecord_typeraw_fieldscollection_methodunitfrequencytemporal_coveragesite_scopeaggregation_rulequality_evidence
cp_development_electricitysoftware_development_builddevelopment_electricitymeter, utility invoice and workload-allocation recordmeter period; kWh; site; equipment scope; release identifier; CPU time or workstation hours; allocation shareReconcile meter or invoice totals to the declared period, subtract excluded loads, then apply the documented release-specific allocation driver.kWh raw; MJ reportedmonthly and at release closefull declared development/build periodall included development and build sitessum attributable kWh by site and period before conversion and reference-flow normalizationmeter export or invoice; equipment scope; allocation worksheet; reconciliation sign-off
cp_development_hardware_materialitysoftware_development_builddataset-added atomic development-hardware product inputsdevice register, materiality screen, upstream LCA link and allocation recordactual device type; manufacturer and model or provider resource identity; function; site or cloud region; Tiangong product-flow UUID when exact; upstream dataset; supplier reference unit; total device inventory amount; commissioning and retirement dates or expected life; time reserved for release; resources reserved; total resources; screening result; cut-off; justificationScreen every device used for development, build, storage, networking and testing. Add one atomic product exchange for each material device and apply the documented time-share and resource-share allocation; retain a quantitative justification and approval for every cut-off.each device's supplier-dataset reference unit; allocated fraction dimensionlessat release close and whenever the hardware estate or allocation changesfull declared development/build periodevery included site, cloud allocation and test environmentpreserve device-level records; aggregate only after separate identity, upstream link and allocation have been calculateddevice or provider inventory; procurement/configuration record; upstream LCA metadata; expected-life evidence; reservation logs; materiality worksheet; cut-off approval
cp_replication_electricitymedia_replication_packagingreplication_packaging_electricitymeter and production-batch recordopening and closing reading; kWh; batch id; operating time; excluded loads; accepted massReconcile interval electricity to production records and deduct documented non-production loads.kWh raw; MJ reportedeach batch or metered campaignrepresentative production periodeach replication and packaging sitesum batch-attributable kWh, then normalize by accepted packaged-product massmeter record; batch log; downtime and exclusion record
cp_media_massmedia_replication_packagingunrecorded_optical_media; unrecorded_magnetic_mediaissue, return and scale recordroute; supplier item; lot; issued count; returned count; average item mass; issued mass; rejected massReconcile stores issues and returns to scale measurements; include exactly one declared media route.kgeach batchrepresentative production periodeach replication siteissued mass minus documented returns; retain rejects separatelycalibrated-scale record; stock reconciliation; route declaration
cp_case_massmedia_replication_packagingrigid_polypropylene_media_caseissue and scale recordcase specification; issued count; returned count; average case mass; rejected countMeasure a representative sample and reconcile item counts to issued mass.kgeach packaging batch where applicablerepresentative production periodeach packaging sitenet issued count × measured average mass; retain rejected-case waste separatelysample record; scale calibration; stock reconciliation
cp_paper_box_massmedia_replication_packagingpaper_boxissue and scale recordbox specification; issued count; returned count; average box mass; rejected countMeasure a representative sample and reconcile item counts to issued mass.kgeach packaging batch where applicablerepresentative production periodeach packaging sitenet issued count × measured average mass; retain paper rejects separatelysample record; scale calibration; stock reconciliation
cp_paper_insert_massmedia_replication_packagingpackaging_paper_insertissue and scale recordinsert specification; page count; issued count; returned count; average insert massMeasure the complete insert supplied per package and reconcile counts.kgeach packaging batch where applicablerepresentative production periodeach packaging sitenet issued count × measured average insert mass; retain paper rejects separatelysample record; scale calibration; stock reconciliation
cp_reject_massmedia_replication_packagingrejected_optical_media; rejected_magnetic_media; polypropylene_case_waste; paper_packaging_wastescale, reject and waste-transfer recordmaterial identity; route; batch id; gross mass; tare; net mass; destination; transfer dateSegregate by atomic material, remove tare and reconcile reject logs to waste transfer records.kgeach batch and transferrepresentative production periodeach replication and packaging sitesum net mass by row_id and destination; never merge material identitiescalibrated-scale record; reject log; waste-transfer document

Calculation Rules

rule_idApplies toFormula or ruleInputsOutputsource_ids
calc_kwh_to_mjboth electricity rowsMJ = measured kWh × 3.6attributable electricity in kWhelectricity in MJ
calc_development_allocationdevelopment_electricityAttributable electricity = included supporting-resource electricity × documented release activity sharereconciled electricity; CPU time, workstation hours or justified time sharerelease-attributable kWhgreen-software-foundation-sci-1-1-0
calc_development_hardware_shareeach dataset-added atomic development-hardware product inputAllocated device input = device inventory reference amount × (time reserved for the release ÷ expected device life) × (resources reserved for the release ÷ total device resources). Use consistent time units and preserve the unrounded factors.actual device identity and upstream reference amount; time reserved; expected life; resources reserved; total resourcesdevice-specific product-input amount allocated to the release in the upstream dataset reference unitgreen-software-foundation-sci-1-1-0
calc_batch_normalizationevery foreground-record inventory rowNormalized amount = batch-attributable amount ÷ accepted packaged-product mass in kgattributable amount; accepted product massamount per 1 kg reference product
calc_media_balanceselected media routeReconcile issued media mass = returned unused mass + recorded media in accepted output + rejected-media mass, adjusted only for documented measurement differences.issued, returned, accepted-product component and reject massesroute-specific mass-balance residual

Data Quality Requirements

requirement_idApplies toRequirementEvidence
dq_temporalall foreground recordsRecords shall cover a representative production period and identify the software release and batches represented.dated meters, invoices, batch logs and release identifiers
dq_geography_technologyelectricity, media and packaging inputsSupplier datasets shall match production geography, grid, medium technology and packaging specification where available; disclose every proxy.supplier dataset metadata and proxy justification
dq_completenessprocess inventoryReconcile the selected media route, all unit-packaging components and segregated rejects; document absent conditional rows as not applicable.route declaration, bill of materials, stock reconciliation and reject log
dq_measurementcount-to-mass conversionsPreserve calibrated-scale evidence, sampling date, sample size, average and variability for every count-to-mass conversion.scale calibration and sampling worksheet
dq_traceabilitycalculations and allocationPreserve raw values, exclusions, formulas, allocation drivers, conversion factors and sign-off so reported values can be reproduced.calculation workbook and approval record
dq_development_hardwaredevelopment/build hardwareThe materiality assessment shall cover the complete device register and record actual device identity, function, upstream LCA link, expected life, release-reserved time, reserved and total resources, allocation result and the quantitative basis for every cut-off.device register; procurement or provider configuration; upstream dataset metadata; reservation logs; materiality and allocation worksheet; cut-off approval

9. Validation Rules

rule_idApplies toRulesource_ids
validate_identity_boundaryproduct and boundaryConfirm CPC 47822 packaged game software on magnetic or optical media and reject cartridges, downloads, online games and non-game software.un-cpc-3-0-structure-2025; un-cpc-3-0-explanatory-notes-2025
validate_reference_massreference flowConfirm the accepted output is exactly 1 kg and contains the recorded medium plus all declared unit packaging, with shipping packaging excluded.
validate_route_exclusivitymedia inputs and rejectsConfirm exactly one optical or magnetic media route is declared and only route-applicable media rows are included.
validate_atomic_flowsinventoryConfirm every included exchange is one atomic flow and conditional components are marked not applicable when absent.
validate_energy_allocationelectricityReconcile raw energy records, the 3.6 MJ/kWh conversion, excluded loads and the documented development and batch allocation drivers.green-software-foundation-sci-1-1-0
validate_development_hardwaredevelopment/build hardwareConfirm the materiality assessment covers every development, build, storage, network and test device in the declared release boundary. Each material device shall appear as a separate atomic product exchange with actual identity, upstream LCA link, expected life, time share and resource share; each excluded device shall have a quantitative cut-off basis and approval.green-software-foundation-sci-1-1-0
validate_mass_balancemedia and packagingReconcile input, return, accepted-product component and reject masses for the selected route; investigate and disclose residuals.
validate_unresolved_uuidUUID-empty rowsConfirm unresolved UUID rows remain specifically named and review metadata records the no-exact-candidate findings; do not substitute a proxy UUID.
validate_source_traceabilitysource-backed rulesConfirm every source id resolves to section 11 and that original-text location and applicability were reviewed.

10. Published Dataset Profile

FieldValue
dataset_roleForeground cradle-to-publisher-gate dataset for packaged computer game software
downstream_useInput to product carbon footprints, comparative LCA with equivalent declared media/package configurations, and lifecycle models that add explicit distribution, use and end-of-life stages
allowed_useDeclared optical or magnetic physical-media route with matching platform, package configuration, geography, period and allocation metadata
excluded_useDownloads, online games, console cartridges, software-as-a-service, or claims about gameplay/service performance without a separately modeled use-stage functional unit
required_metadatasoftware release; platform; media route and format; package bill of materials; production sites and period; accepted mass; allocation methods; development-hardware device register and materiality assessment; upstream dataset links; cut-offs; unresolved UUIDs
required_quality_disclosuremeasurement coverage; count-to-mass sampling; electricity allocation; device-level hardware time/resource allocation; route and mass-balance residuals; supplier proxies; excluded loads; conditional rows; data gaps
update_triggerChange of software release build scope, platform, physical-media format, package configuration, replication technology, production geography, allocation basis or material supplier dataset

11. Data Sources

Source idTypeReferenceUsed for
un-cpc-3-0-structure-2025official_guidanceUnited Nations Statistics Division, CPC Version 3.0 Structure, 30 June 2025, https://unstats.un.org/unsd/classifications/Econ/Download/In%20Text/CPC_Ver_3.0_Structure_30Jun2025.csvOfficial CPC 47822 code and English product title
un-cpc-3-0-explanatory-notes-2025official_guidanceUnited Nations Statistics Division, CPC Version 3.0 Explanatory Notes, 30 June 2025, https://unstats.un.org/unsd/classifications/Econ/Download/In%20Text/CPC_Ver_3.0_Exp_Notes_30Jun2025.pdfPhysical-media packaged-game boundary and explicit exclusions
green-software-foundation-sci-1-1-0standardGreen Software Foundation, Software Carbon Intensity Specification, version 1.1.0, https://sci.greensoftware.foundation/Software boundary, supporting-resource energy attribution, development-hardware time/resource allocation, functional-unit consistency and calculation traceability
cifa-lca-database-guideline-cpc-appendixofficial_guidanceChina International Freight Forwarders Association, LCA/碳足迹数据库构建导则——第六章附录, https://www.carbonfootprint.network/docs/cifa-guidelines/lca-database-guideline/chapter-6-appendixCPC 2.1 classification-table row 47822, used only to verify the professional Chinese product-title terminology; CPC 3.0 sources govern product identity and boundary

Raw downloads

These files are byte-identical to the canonical files for this revision in the repository.

Structured rule index

This index comes from verified structured.yaml and retains the canonical English rule text.

System boundary rules · 6
Rule IDApplies toRuleSource IDs
boundary_product_identityproduct selectionInclude only a packaged computer game product presented on magnetic or optical physical media; exclude cartridges, downloads and online game services.un-cpc-3-0-explanatory-notes-2025
boundary_foreground_gateforeground systemInclude development/build work attributable to the release, physical-media replication, inspection, rejects and unit packaging through the publisher distribution gate.
boundary_software_infrastructuresupporting compute and infrastructureInclude electricity and other exchanges only for supporting resources actually used by the declared software-production work and allocate shared resources transparently.green-software-foundation-sci-1-1-0
boundary_development_hardwaredevelopment/build hardwareAssess all servers, desktop workstations, portable computers, storage and network devices, and test consoles or other test devices used to produce the release. For every material device, add one separate atomic product input using the actual device identity and an upstream hardware LCA dataset; disclose and justify every exclusion against the declared materiality cut-off.green-software-foundation-sci-1-1-0
boundary_downstream_exclusionsdownstream stagesExclude downstream distribution, gameplay, maintenance, online services and end-of-life unless a boundary expansion is explicitly modeled and separately reported.
boundary_recursive_inputsame-category purchased inputsKeep any purchased packaged game-software input visible as an upstream-linked product exchange; do not recurse into another foreground copy of this PCR.
Allocation rules · 5
Rule IDApplies toRuleSource IDs
allocation_avoidall foreground processesPrefer subdivision and direct metering by software release, production line and batch before applying allocation.
allocation_developmentshared development/build electricityAllocate measured supporting-resource electricity by documented CPU time, workstation hours or another causal activity measure attributable to the declared release; if no causal measure exists, use a disclosed time-based share and justify it.green-software-foundation-sci-1-1-0
allocation_development_hardwarematerial development/build hardwareFor each separately identified device, allocate the linked hardware inventory by both the fraction of expected device life reserved for the release and the fraction of device resources reserved for the release. Preserve actual device identity and do not allocate downstream gameplay hardware unless it was also used to produce or test the release.green-software-foundation-sci-1-1-0
allocation_replicationshared replication and packaging operationsAllocate shared batch electricity and materials by accepted packaged-product mass when products use the same equipment; use a documented causal machine-time basis when routes materially differ.
allocation_recyclingwaste and recycling outputsApply cut-off at the point the waste leaves the foreground boundary unless an avoided-burden expansion is explicitly declared; do not credit potential recycling in the default dataset.
Validation rules · 9
Rule IDApplies toRuleSource IDs
validate_identity_boundaryproduct and boundaryConfirm CPC 47822 packaged game software on magnetic or optical media and reject cartridges, downloads, online games and non-game software.un-cpc-3-0-structure-2025, un-cpc-3-0-explanatory-notes-2025
validate_reference_massreference flowConfirm the accepted output is exactly 1 kg and contains the recorded medium plus all declared unit packaging, with shipping packaging excluded.
validate_route_exclusivitymedia inputs and rejectsConfirm exactly one optical or magnetic media route is declared and only route-applicable media rows are included.
validate_atomic_flowsinventoryConfirm every included exchange is one atomic flow and conditional components are marked not applicable when absent.
validate_energy_allocationelectricityReconcile raw energy records, the 3.6 MJ/kWh conversion, excluded loads and the documented development and batch allocation drivers.green-software-foundation-sci-1-1-0
validate_development_hardwaredevelopment/build hardwareConfirm the materiality assessment covers every development, build, storage, network and test device in the declared release boundary. Each material device shall appear as a separate atomic product exchange with actual identity, upstream LCA link, expected life, time share and resource share; each excluded device shall have a quantitative cut-off basis and approval.green-software-foundation-sci-1-1-0
validate_mass_balancemedia and packagingReconcile input, return, accepted-product component and reject masses for the selected route; investigate and disclose residuals.
validate_unresolved_uuidUUID-empty rowsConfirm unresolved UUID rows remain specifically named and review metadata records the no-exact-candidate findings; do not substitute a proxy UUID.
validate_source_traceabilitysource-backed rulesConfirm every source id resolves to section 11 and that original-text location and applicability were reviewed.
Processes and inputs/outputs · 2
Process IDProcess nameInput flowsOutput flows
software_development_buildSoftware development and release build10
media_replication_packagingPhysical-media replication and unit packaging65

Complete field inspector

Loads this record’s complete manifest and structured projection on demand; values are never truncated. Requires JavaScript.

On this page