Keep retail refrigeration circuit identities through a cabinet refit

Anil Khatwani

Oct 14

6 min read

A contractor writes “cabinet 09” on a job sheet. The finance export says “dairy case”. The latest floor plan connects that cabinet to a different rack from the one shown last month. Joining all three records by the current asset name can put a genuine service event against the wrong system.

This guide is for retail facilities coordinators and inventory preparers resolving those joins. Its fictional store refit produces a dated relationship map, an event-by-event decision and a list of unanswered questions. It does not calculate refrigerant emissions or advise anyone how to modify equipment.

Start with the technician’s system identities

EPA’s GreenChill guide distinguishes centralised systems serving multiple display cases from other designs, including secondary loops. A sales-floor cabinet list therefore need not be a list of separate refrigerant systems. Ask a qualified technical owner to identify the actual arrangement; do not infer it from appearance.

The example covers one company-operated grocery store and June 2026. Its fictional technical owner confirms two separate systems, R1 and R2, using the same specified refrigerant, R-448A. Twelve cabinets have internal asset labels C01–C12. A store document maps each cabinet to its system for a stated interval. These are case assumptions, not a recommended design or refrigerant selection.

Use “system” here for the technical owner’s confirmed refrigerant boundary. A rack label, cabinet, pipe branch and separately charged circuit are not automatically interchangeable identities. If a rack contains independent circuits, obtain their separate identifiers.

Office air-conditioning, vehicle cooling, other stores and contractor-held cylinders are outside this selected record-matching exercise. That selection does not exclude them from an eventual corporate inventory. The reporting lead still needs a separate completeness and boundary decision.

Keep three connected records

System record: retain R1 or R2 as the stable identifier, the technical owner’s supporting reference, the source wording for the gas and the period for which that identity is confirmed. Keep unknown fields visibly unresolved. A finance asset number is an alias only after its relationship has been checked.
Relationship record: store the cabinet ID, system ID, start and end of the confirmed interval, the change reference and who supplied it. Preserve superseded intervals. Do not replace the old relationship with today’s map.
Event record: keep the original ticket reference, event date and time when relevant, source asset wording, proposed system match and supporting relationship version. Record whether the join is confirmed, ambiguous or rejected, with an owner for the next question.

This three-record design is an original working arrangement for the example. It is not an EPA form or prescribed reporting template. Retain source files unchanged alongside it. Correcting a derived match should not silently rewrite the contractor’s document.

Freeze the relationship before and after the refit

Map M1 is valid from 1 June up to, but not including, 20 June at 14:00 local time, UTC+05:30. It links C01–C09 to R1 and C10–C12 to R2. The result is nine cabinet links to R1 and three to R2. R1 and R2 remain two system identities, not twelve.

A fictional completed-work record W20 and the technical owner’s clarification establish that C09 is linked to R2 from 20 June at 14:00. Map M2 therefore links C01–C08 to R1 and C09–C12 to R2: eight links and four links. Both maps cover twelve cabinets; only one cabinet’s relationship changes.

The source pack in this example explicitly confirms the change time and the continued identities R1 and R2. Without that evidence, an administrator could not create these facts merely by comparing floor plans. A revised drawing’s issue date is also not necessarily the date physical work became effective.

The relationship change says nothing by itself about quantities added, recovered or lost during the work. Preserve the refit’s technical records as their own evidence. Do not manufacture a zero-movement entry because the cabinet count stayed at twelve. Technical interpretation belongs with the qualified owner and inventory-method lead.

Fictional C09 record links: J11 on 10 June matches M1 and R1; J22 on 22 June matches M2 and R2. J20 on the change date remains unresolved because its time is missing. — Original fictional record map. The confirmed change is effective at 14:00 on 20 June, UTC+05:30. This shows document relationships, not physical piping or refrigerant movements.

Join the event using the relationship valid at that time

J11, 10 June: the signed ticket identifies C09 and records 4.0 kg of R-448A added. M1 places C09 on R1 on that date. Keep the quantity with J11 and record R1 as the confirmed system match.
J22, 22 June: the signed ticket identifies C09 and records 3.0 kg of R-448A added. M2 places C09 on R2. The same cabinet ID now has a different confirmed system match.
J25, 25 June: the ticket names R2 directly and records 2.0 kg of R-448A added. Its attachment lists C09 and C10 as inspection locations. Retain one 2.0 kg addition event. The two location labels do not create two additional quantities.
J20, 20 June: the ticket identifies C09 and records 1.0 kg of R-448A added, but provides no event time or system ID. The relationship changed at 14:00 that day. Leave this match unresolved until the contractor clarifies which system received the addition.

A date-only field is adequate for J11 and J22 in this case, but not for J20. Do not default an absent time to midnight. Nor should an invoice date, upload time or drawing revision date be substituted for the service time. If the contractor cannot resolve J20, record that limitation rather than making the sum look complete.

Remove the duplicate representation, not the original evidence

The finance export has five rows: J11 4.0 kg; J22 3.0 kg; J25 2.0 kg; J20 1.0 kg; and invoice INV44 3.0 kg. The invoice identifies J22 as its sole underlying gas line. The accounts owner confirms that the last row is another representation of J22, not a second addition.

The raw rows sum to 13.0 kg. The four distinct documented addition events sum to 4.0 + 3.0 + 2.0 + 1.0 = 10.0 kg. Retain INV44 and its link to J22 in the evidence pack; suppress its second contribution only in the derived event schedule. This is a documented relationship decision, not a rule to delete every repeated quantity.

If two tickets both showed 3.0 kg on the same day, that coincidence would not establish a duplicate. Conversely, changed asset wording would not establish a new event. Review the source references, job context and the supplier’s clarification. A multi-line invoice may need several links rather than one invoice-level match.

Explain the mapped and unmapped quantities together

The confirmed matches give R1 4.0 kg from J11 and R2 5.0 kg from J22 plus J25. J20 contributes a separate unresolved 1.0 kg. Thus 4.0 + 5.0 + 1.0 = 10.0 kg, matching the distinct-event total. The unresolved line has not disappeared, been assigned to both systems or been entered as zero.

Recorded additions are not an emissions result. EPA’s fugitive-emissions guidance requires method-specific data. Its simplified material balance excludes certain situations, including refrigerant-stock tracking and conversion to a different gas during the reporting period. Confirm applicability separately.

Using M2 for every June record would wrongly send J11’s 4.0 kg to R2. Using the cabinet’s first known system forever would wrongly send J22’s 3.0 kg to R1. Both shortcuts can preserve the 10.0 kg store total while corrupting the system history. Reconciliation of the grand total alone would miss the error.

Suppose the contractor later confirms that J20 occurred at 10:30 and concerned R1. Preserve the dated clarification and move its 1.0 kg from unresolved to R1. R1 becomes 5.0 kg, R2 remains 5.0 kg and unresolved becomes zero. The 10.0 kg event total stays unchanged. This is an alternative completed example; the original unresolved position remains part of the history.

Hand over the decisions and the unresolved join

Facilities supplies M1, M2, W20 and the technical identity confirmations. It owns the question about J20’s actual receiving system and service time.
Accounts supplies the five imported rows, INV44 and the documented J22 relationship. It explains the 3.0 kg duplicate contribution without deleting either source document.
The coordinator supplies the four-event schedule, interval matches and the three-part 10.0 kg reconciliation. Each conclusion points to the evidence that supports it.
The inventory lead determines the applicable method and other required inputs. The case has not established complete store coverage, the full refit gas movements, an emissions total or a leak rate.

Start with the cabinets whose relationship changed, then check the unchanged population as well. Keep a named owner for missing technical evidence and an explicit version for the handover. The useful output is a defensible explanation of which source event belongs where, including the point at which the evidence stops.

Continue the records handover

For the broader contractor request, read the office AC service-record guide. To discuss a scoped data-preparation assignment, see Nitium Advisory’s carbon inventory support or contact Nitium with a non-confidential outline of the records and unresolved questions.

All store IDs, records, dates and quantities are fictional. Sources checked 14 October 2026. The US technical references are used for system and accounting context, not as statements of Indian legal duties. This is record-preparation guidance; it provides no equipment-handling instruction, professional assurance or verification of the underlying work.