{"id":3832,"date":"2026-11-05T17:00:00","date_gmt":"2026-11-05T09:00:00","guid":{"rendered":"https:\/\/cnbygele.com\/?p=3832"},"modified":"2026-11-04T19:16:48","modified_gmt":"2026-11-04T11:16:48","slug":"meter-decommissioning-data-handover","status":"publish","type":"post","link":"https:\/\/cnbygele.com\/tr\/blog\/meter-decommissioning-data-handover\/","title":{"rendered":"G\u00fc\u00e7 \u00d6l\u00e7er Kapatma: Verileri Koruyun ve Toplama Yollar\u0131n\u0131 Kapat\u0131n"},"content":{"rendered":"

Power meter decommissioning should preserve a traceable final observation, transfer the historical records and their interpretation, and close obsolete collection paths without destroying the evidence needed for future reporting. Define the retirement boundary before removal, identify the person accepting the archive, and verify that reports handle the retired point correctly. Physical removal and electrical isolation require qualified personnel and the applicable site procedure. This guide focuses on the data handover around that work; it does not provide instructions for disconnecting a meter or changing current-transformer circuits.<\/p>\n

Define what is being retired<\/h2>\n

A meter asset, a collecting point and a reporting series are related objects, but retiring one does not automatically retire the others. An instrument can be removed while its old point continues to appear in a dashboard. A database series can remain useful after the instrument leaves service. Start with an inventory connecting the physical device, measured circuit, collection route and reports that depend on its readings.<\/p>\n

Record whether the project is a permanent retirement, a temporary removal or replacement with another device. This distinction changes the handover. Permanent retirement closes a measurement boundary. Replacement creates a boundary between two instruments that may have different scales, starting values or configuration. Temporary removal requires a defined way to recognize and review the period without valid observations.<\/p>\n

Use the existing asset identity reconciliation guide<\/a> for the mapping between labels and data points. Decommissioning adds a lifecycle decision: what stops, what remains accessible and who accepts responsibility after the final collection.<\/p>\n

Agree the final observation before field work<\/h2>\n

Specify which observations are required and who will capture them under the approved maintenance process. A final energy record needs a quantity, unit, timestamp, identity and quality state. If relevant configuration affects interpretation, retain that configuration with the observation. Do not record an unexplained number and expect the archive owner to reconstruct its meaning later.<\/p>\n

Distinguish the final valid reading from the time of physical removal and from the last database import. Those times may differ. A late upload can contain an earlier measurement. An application timestamp can describe processing rather than observation. State the meaning of each time field, including its offset or timezone, and preserve the original record where practical.<\/p>\n

The RFC 3339 timestamp specification<\/a> provides a precise representation for date-time values and offsets. It does not decide the plant’s retirement boundary or reporting rules. The project must still define whether a timestamp describes a measurement, interval boundary, export or administrative event.<\/p>\n

\"Power
Reference-based illustration: a disconnected BY194 front beside external review documents. These conceptual props do not demonstrate installed functions, firmware update support or communication behavior.<\/figcaption><\/figure>\n<\/p>\n

Build an archive someone else can interpret<\/h2>\n

An archive should contain more than a file named final-export. Include a short manifest explaining the device identity, measured circuit, observation period, quantity definitions, units, quality indicators and any transformations performed by the collecting system. Preserve original files separately from cleaned or reformatted copies.<\/p>\n

If the receiving system needs a different format, record the transformation and reconcile a representative sample against the original. A readable spreadsheet can still be wrong if it changes timestamps, drops quality flags or converts cumulative energy into an apparent interval value. Keep the source and destination field mapping so the recipient can explain how a record acquired its final meaning.<\/p>\n

The DOE federal metering guidance<\/a> provides broader context for metering data storage and management. The handover worksheet below is a practical project structure, not a prescribed universal retention schedule or a claim that the meter itself contains a historical archive.<\/p>\n

\n\n\n\n\n\n\n\n\n\n\n
Handover item<\/th>\nInformation to preserve<\/th>\nRecipient verification<\/th>\nUnresolved issue to record<\/th>\n<\/tr>\n<\/thead>\n
Device and circuit identity<\/td>\nAsset label, model, circuit and point mapping<\/td>\nMatch records to the intended measurement boundary<\/td>\nAmbiguous label or reused point name<\/td>\n<\/tr>\n
Final valid observation<\/td>\nQuantity, value, unit, time and quality<\/td>\nReproduce its interpretation from the manifest<\/td>\nReading unavailable or known to be invalid<\/td>\n<\/tr>\n
Historical data<\/td>\nOriginal files, covered period and known gaps<\/td>\nOpen files and inspect representative records<\/td>\nMissing period or unexplained duplicates<\/td>\n<\/tr>\n
Configuration context<\/td>\nRelevant ratios, scales and transformation owners<\/td>\nExplain how engineering values were produced<\/td>\nConfiguration revision cannot be established<\/td>\n<\/tr>\n
Collection closure<\/td>\nRetired route and approved effective boundary<\/td>\nConfirm no new valid records are assigned to the old asset<\/td>\nQueued data or stale display remains ambiguous<\/td>\n<\/tr>\n
Archive ownership<\/td>\nLocation, access owner and retention policy reference<\/td>\nRecipient confirms practical access<\/td>\nAccess depends on an account being retired<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

Mark missing or invalid final data honestly<\/h2>\n

A failed instrument may not provide a reliable final observation. Record that limitation explicitly and preserve the last known valid data with its original quality state. Do not invent a final reading, silently carry forward the last value or replace an unavailable interval with zero energy.<\/p>\n

If the project requires estimation, keep the estimate separate from observed data and identify the approved method, inputs and accepting authority. Industrial monitoring, internal cost allocation and regulated settlement can have different rules. This article does not prescribe a billing method or transfer one jurisdiction’s utility procedure to every CNBYG installation.<\/p>\n

For reporting continuity, see the existing maintenance data-gap guide<\/a>. It explains why missing observations need their own treatment. A retirement record should point to the applicable gap decision rather than hiding uncertainty inside an apparently complete export.<\/p>\n

Close the collection route at the correct layer<\/h2>\n

Identify the scheduler, gateway mapping, application point and report inclusion separately. Closing a dashboard widget does not necessarily stop collection, and stopping polling does not automatically remove a retired point from totals. Assign an owner to each layer and record the approved effective boundary.<\/p>\n

Consider buffered or queued observations. Records arriving after retirement may still belong to the valid pre-retirement period. Classify them by their documented measurement time and identity rather than discarding everything received after the administrative event. Conversely, a stale value must not acquire a new measurement time simply because the application refreshes its screen.<\/p>\n

Preserve the closure evidence without retaining unnecessary active access. The NIST operational technology security guide<\/a> provides lifecycle and access-management context. Apply the site process to obsolete accounts, remote routes and device records; do not delete shared dependencies until their owners have confirmed that other active equipment does not rely on them.<\/p>\n

Keep replacement histories separate until reconciled<\/h2>\n

When another meter replaces the retired unit, preserve two asset identities and a documented boundary. A new cumulative counter may start at a different value. A changed ratio or collecting profile can change interpretation. Joining the series without recording those differences can create a false energy jump or erase genuine consumption.<\/p>\n

Prepare a reconciliation note explaining the last valid old-device observation, the first valid new-device observation and the period between them. If the measurements overlap, define how reports avoid double counting. If they do not overlap, retain the gap and its treatment. Do not make the historical series appear seamless merely because that produces a cleaner chart.<\/p>\n

This distinction matters for future investigations. A reviewer should be able to identify whether an apparent trend change came from the process, the replacement boundary or a data transformation. Keeping the original identities and records makes later analysis possible without reconstructing the maintenance event from memory.<\/p>\n

A hypothetical retirement handover<\/h2>\n

Consider an industrial panel meter scheduled for permanent retirement after a circuit change. Before the approved field work, the data owner identifies the final observation requirements, exports the relevant history and documents the collecting point. The recipient opens the archive and checks several records against the original application before accepting it.<\/p>\n

The instrument is then retired under the site’s electrical procedure. The application owner marks the old point inactive at the agreed boundary. A later import contains delayed observations from before that boundary. The team preserves them under the old asset and records the import time separately, rather than treating them as evidence that the retired instrument returned to service.<\/p>\n

Finally, the reporting owner confirms that the old point no longer contributes new valid observations while its historical records remain available. A known gap stays visible in the manifest. This is an illustrative workflow, not a customer case or evidence that a particular BY194 variant offers internal logging, file export or remote retirement functions.<\/p>\n

\"Power
Reference-based illustration: a disconnected BY194 front beside external review documents. These conceptual props do not demonstrate installed functions, firmware update support or communication behavior.<\/figcaption><\/figure>\n<\/p>\n

Product context and a practical support request<\/h2>\n

The BY194 multifunctional power instrument family<\/a> supplies the real product context for the reference illustrations. The family page does not establish a universal internal archive, export format or decommissioning command. Historical data in a project may reside in an external gateway, database or energy management application.<\/p>\n

When requesting support, provide the exact model, installed option, measured circuit and collecting-system details. Explain whether the instrument is permanently retired or replaced, which records remain accessible and what interpretation is unresolved. Ask for applicable product documentation without assuming that the manufacturer controls every external database or reporting rule.<\/p>\n

For the communication layer, the Modbus setup guide<\/a> offers complementary integration context. Use it with the approved project records to identify the actual collection route that needs closure, rather than guessing from a generic network diagram.<\/p>\n

Further learning: energy units<\/h2>\n

The Khan Academy lesson below explains the relationship between power and energy units. It helps an archive recipient understand why a cumulative energy reading and an instantaneous power observation cannot be substituted for each other. It is conceptual education, not a meter removal procedure or a demonstration of product features.<\/p>\n