Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nectarclimate.com/llms.txt

Use this file to discover all available pages before exploring further.

If you use IBM Envizi for utility bill analytics and sustainability reporting, Nectar can complement and simplify your day-to-day utility data operations.

How Envizi workflows are usually organized

Public Envizi documentation highlights:
  • Hierarchy-based data navigation across groups, locations, and accounts
  • Utility bill analytics for cost and consumption
  • Meter and virtual-meter concepts for utility data tracking
Teams often want a faster operational layer for intake, issue resolution, and recurring exports.

How your Envizi data maps to Nectar

Envizi-style source conceptNectar destinationMigration notes
Group or business hierarchyCompanyMirror major reporting segments as companies.
Location entitiesSitePreserve location IDs for cross-system traceability.
Utility accountsAccountMaintain account identifiers as source references.
Physical and virtual meter recordsMeterKeep meter lineage metadata for aggregated meters.
Utility bill analytics recordsBill + usage dataSeparate bill totals from usage metrics for cleaner QA.
Variance flags and exceptionsData Quality workflowsMove from report-only exceptions to actionable queues.
1

Select initial migration scope

Prioritize utility types and sites with the highest reporting impact and cleanest historical datasets.
2

Export hierarchy and utility datasets

Export groups, locations, accounts, meter metadata, and historical utility bill records for mapping.
3

Map hierarchy to Nectar structure

Align groups to companies and locations to sites, then connect accounts and meters.
4

Pilot and reconcile

Validate monthly totals and usage trends between Envizi exports and Nectar for a representative sample.
5

Operational cutover

Use Nectar for intake, QA, and export workflows while preserving your reporting continuity.

What improves in Nectar

  • More operational control for utility data intake and correction
  • Faster issue triage through dedicated quality workflows
  • Smoother handoff between operations teams and downstream reporting users

Features to evaluate in Nectar

Depending on your Envizi implementation, Nectar may add:
  • Utility connection onboarding and credential collection workflows
  • Built-in invitations for client or field-team data collection
  • Unified operational workflows across Data Input, Data Inventory, Data Quality, and Data Export

Nectar support during migration

Nectar provides:
  • Hierarchy and field mapping workshops
  • Pilot-side reconciliation with acceptance criteria
  • Cutover support and post-go-live tuning

Ready to migrate from Envizi?