XDL Data Flow Timing

Question 1

Three freshness tiers in XDL?

Answer 1

Near-real-time • Intra-day • Daily batch.

Question 2

Latency for near-real-time tier?

Answer 2

5–10 minutes after SA receives data.

Question 3

Main tables in near-real-time tier?

Answer 3

*_intervals, *_registers, *_events, device_group, account.

Question 4

How to eyeball freshness of a table?

Answer 4

Query MAX(ingest_timestamp) for that table.

Question 5

Latency goal for customer-portal data?

Answer 5

≈1 hour to XDL.

Question 6

Which tier is *_consumption?

Answer 6

Sub-daily batch (~4-hour latency).

Question 7

RNI ‘Consumption Aggregator’ schedule?

Answer 7

Runs every 4 hours, then pushes to SA & XDL.

Question 8

Latency for daily batch tables?

Answer 8

Available next calendar day before 04:00.

Question 9

Give two daily-batch tables.

Answer 9

metrology_device, fl_logs (FieldLogic).

Question 10

Why 10-minute target is ‘good enough’?

Answer 10

Meters cache locally; alarms within 1 polling cycle.

Question 11

What does SA stream every 5-10 min?

Answer 11

Intervals, registers, events, CIS deltas.

Question 12

Key control column to check freshness?

Answer 12

ingest_timestamp (or read_time_timestamp_local).

Question 13

Who drives near-real-time push?

Answer 13

Sensus Analytics micro-batch bus.

Question 14

Why not stream manufacturing data?

Answer 14

Rarely changes; daily batch saves bandwidth.

Question 15

FieldLogic AMR read cadence?

Answer 15

Daily pull into XDL.

Question 16

Portal_activity table freshness?

Answer 16

Hourly—good for same-day customer trends.

Question 17

Which table for outage pings?

Answer 17

electric_events (near-real-time).

Question 18

Which table shows firmware version?

Answer 18

metrology_device_history (daily).

Question 19

Default nightly ETL start time?

Answer 19

≈02:00 local utility time.

Question 20

One-liner to answer ‘How fresh is XDL’?

Answer 20

Intervals <10 min, consumption ≤4 h, metadata next-day.