Normalize sensor units through a versioned conversion table
Two device models emit watt-hours and kilowatt-hours under the same field name.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Data normalization · Versioning
Estimated field mix
- Data engineering100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional energy dashboard receives hourly device batches. Corrupt archives and late corrections leave operators unsure which readings reached reports.
Setup prerequisites
- Create synthetic device batches and local object-store fixtures.
- Understand checksums and bounded streaming.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Require a known unit and conversion version.
- Preserve raw numeric value and declared unit in lineage.
- Reject unsupported units and nonfinite measurements.
Implementation constraints
- Use decimal arithmetic for documented conversions.
Verification to include
- Convert synthetic Wh and kWh to equal canonical readings.
- Reject missing units and nonfinite input.
Deliverables
- Unit conversion contract and cases
Rollout and recovery
Publish conversion revisions for new runs; retain old mappings for replay.
Value of the work
For the engineer: Practice batch integrity, replay and data-quality boundaries.
For the team: Review whether operational data can be traced, corrected and recovered.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.