Asset Hierarchy

Asset hierarchy data describes the physical side of metering: meters, the locations they sit at, and how they're linked to service delivery points (SDPs) over time. It's optional in the sense that DPU can process reads without it, but it's what unlocks location- and asset-aware fields in the marts and in features like Load Research.

What DPU models

Core asset tables include meter, meter_location, location, meter_type, and register_group, tied together through sdp_meter_xref — the record of which meter has served which SDP, and when.

Typical fields:

• meter_number — the physical meter identifier
• point_of_delivery_sdp — the SDP the meter is/was installed at
• active_timestamp / inactive_timestamp — install and removal dates
• street_number, street_name, gps_latitude, gps_longitude — location detail
• meter_type_code, multiplier (CT/PT ratio), register_group_code (register form)

Extended attributes surfaced through an SDP/meter attribute reference table include service_area, substation, feeder, mru, premise_type, and meter_form — used by filtering in features like Load Research.

Where it ends up

Asset data is conformed into core_dim_meter (an SCD2 dimension — one row per meter per version, so meter swaps and reconfigurations are preserved) and core_dim_service_point (current-state, one row per meter-at-SDP assignment). See Core.