Skip to main content
If you currently use Arcadia or Urjanet-based utility data feeds, Nectar can map your normalized records into an operations-first workspace for ongoing intake, QA, and export.

How Arcadia / Urjanet workflows are usually organized

Public Arcadia and Urjanet materials describe a model centered on:
  • Utility account enrollment with credentialed data access
  • Normalized utility bill and account records across many providers
  • API-driven delivery for downstream reporting and analytics
This model is strong for data acquisition. Teams often add additional operational layers elsewhere for exception handling and day-to-day QA.

How your Arcadia / Urjanet data maps to Nectar

Arcadia / Urjanet-style conceptNectar destinationMigration notes
Provider account ID and account metadataAccountKeep source identifiers for traceability.
Service address and utility provider metadataSite + account attributesPreserve address normalization and provider names.
Meter-level usage payloadsMeter + usage dataMap interval and billing-period values by commodity.
Bill headers and bill chargesBillImport service period start/end, totals, and charges.
Enrollment or account statusesConnection and QA workflowsUse status-driven dashboards for onboarding and issue triage.
1

Export account and bill history

Pull representative account metadata, bill records, and usage payloads. Include status fields used for operational tracking.
2

Map IDs and hierarchy

Map provider account IDs to Nectar accounts, then align addresses to sites and company ownership.
3

Load a pilot portfolio

Import a subset of accounts and reconcile bill totals and usage for two to three billing periods.
4

Set up ongoing intake

Choose your production intake path: direct connections, scheduled uploads, or hybrid workflow.
5

Operationalize in Nectar

Move issue management into Data Quality and downstream delivery into Data Export.

What improves in Nectar

  • More complete operations loop from ingestion to QA to export in one place
  • Easier collaboration between implementation, operations, and reporting teams
  • Better handling of portfolio-level exception workflows

Features to evaluate in Nectar

Depending on your current Arcadia/Urjanet stack, Nectar may add:
  • Built-in UI workflows for data operations teams, not only API delivery
  • Magic-link onboarding for faster credential and source collection
  • Unified record editing and quality triage across bills, accounts, and meters

Nectar support during migration

Nectar provides:
  • Source-to-target mapping workshops
  • Pilot import QA and reconciliation support
  • Cutover planning with post-launch monitoring

Ready to migrate from Arcadia / Urjanet?