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
How your Arcadia / Urjanet data maps to Nectar
Recommended onboarding plan
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
- Invitation-based 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