Sources and inspection limits

Note edition 0.1.4 · Source register edition 0.1.4 · 1 October 2026 · Companion to From BMS to Dataset

The source register is aligned with this note edition. The original dataset and document versions remain as cited below; no source was newly inspected for this editorial revision.

What was checked

This edition uses selected documentary examples. It distinguishes a publisher's description from an independently verified measurement property. No new telemetry statistics or controller experiments were performed to create this note.

Weihai: published schema

• Source: Qu, Jingbo, Dataset for: A Multi-Agent AI Framework for Explainable Battery System Maintenance, Zenodo record 20094787, v1. Public description.
• Locator: description §§5–7, operation and rack time-series structure. Checked online on 1 October 2026.
• Supports: the listed field structure and the scope of that description. A request–limit–execution event chain is not supplied by that list.
• Does not establish: completeness of the entire operating archive, absence of internal control logs, acquisition synchrony, or the cause of an operating change. This edition did not reopen the raw MAT files.

OpenCEM: acquisition and context documentation

• Source: Bartels and colleagues, OpenCEM: Multimodal photovoltaic and battery microgrid dataset with context records and sky imagery, Zenodo 21436223, v1.0.0. Version record.
• Locators: the deposited README.md; code/acquisition/README.md inside opencem-v1.0.0-support.zip. The latter was read directly from the previously received archive, whose SHA-256 was checked against its receipt.
• Supports: documented rotating polling, retained register values, exception behavior and shared snapshot timestamp; separate context applicability and entry times.
• Does not establish: actual acquisition time for every field, a complete audit of recorder operation, or controller use of context. Proprietary component details are not made public by the release README.
• Local copies: release README, acquisition README, data/documentation licence, and code-directory MIT licence. Preserved without editing. The deposited Zenodo version is used; a live repository may contain a different export.
• Licence scope: the release README and LICENSE-DATA.txt assign documentation to CC BY 4.0 and code to MIT. The acquisition README is located under code/, whose MIT notice also refers to associated documentation. We retain both original notices, attribution and unchanged bytes, rather than assigning that README exclusively to one licence from its directory alone. No OpenCEM code is redistributed in this note.

M5BAT: request, delivery and mode definitions

• Source: Lucas Koltermann, Mauricio Celi Cortés, Sebastian Zurmühlen, Jonas van Ouwerkerk and Dirk Uwe Sauer, M5BAT Large-Scale Battery Storage System Dataset: Evaluation Operation Report 04/2023, 13 May 2024. DOI record.
• Locator: PDF pp. 6–7, station and battery-unit field tables. The existing project-held report was read directly for this edition; the DOI page did not return usable content through the web tool during this check.
• Supports: the documented distinction among P_AC_Set, P_AC, inverter modes, SPA_ask_P and SPA_exec_P, and the documented UTC coordinate. Page 6 defines SPA_ask_P as “Request for active power for setpoint adjustment” and SPA_exec_P as “Active power for setpoint adjustment”, both in kW. Page 14 describes SPA's SOC-management purpose and 15-minute intraday continuous-market context; these are not market-order or trade-execution field definitions.
• Does not establish: the reason for any mismatch, the correctness of every row, physical synchrony or visibility of all protection decisions. No new CSV analysis was performed.
• Local copy: original report PDF. The document states CC BY 4.0 on pp. 1 and 23; bytes are unchanged.

Verify the retained documentation

Source hashes and bibliographic locators identify the copies included here. A matching hash establishes which document was retained, not that every statement in it is physically correct. The original publications remain the source of the authors' claims; LFR's interpretation is labelled separately in the note.

The bundled documents are offered as public evidence routes for this note. Their original licence terms remain applicable. The data-chain card is a proposed template, not an adopted standard.

Reuse of LFR's own content. The original research-note prose and data-chain card, including its filled fragment and HTML/Markdown/JSON forms, are licensed under CC BY 4.0. Credit Pingxin Wang / LFR, identify the edition, link to the licence and indicate changes. This grant excludes third-party quotations, documents, datasets, fonts, stylesheets and code; their own terms remain applicable. The file LICENSE-LFR-CONTENT.txt specifies the scope and suggested attribution. Reuse permission is not method certification or endorsement of an application.

Selection and exclusions

The examples were chosen for contrasting documentation relationships, not randomly or through an exhaustive search protocol. Repositories, individual releases and multiple releases from the same facility are not interchangeable units of evidence.

The broader working catalogue's yes/unknown counts are not reproduced as industry estimates. This edition does not certify that a field is absent from every file whenever a description fails to mention it.

The following remain outside this note: unverified national standards comparisons; numerical near-zero-current findings whose record selection and origin need further checking; material mechanisms; health, safety and operational benefit; the detailed design of a proposed BMS.

Correction and further evidence

A correction can identify the affected passage, the source version and a more specific locator or contradictory record. Possible amendments include narrowing a statement, changing its inspection status, or selecting a better-documented example. A source update should not silently change the version to which an earlier statement referred.

No independent reader study or scientific validation is claimed by this note. Source checking, reader comprehension, release clearance and operational validation are different questions.