ARIA R.I.

ARIA Resource Intelligence documentation

ARIA R.I. is the specialist resource-intelligence capability for analyzing utility/resource records, identifying changes and cost leakage, preparing reviewable findings and supporting ongoing tracking.

Current implementation boundary: the customer dashboard now has ARIA R.I. product visibility and entitlement-aware locked/preview routing. The complete customer operational R.I. workspace and API integration are not represented as finished in this foundation.

Purpose

ARIA R.I. is designed to help organizations understand changes in utilities and other resource costs by extracting structured information from records, comparing periods and surfacing anomalies, leakage or savings opportunities for review.

Intended workflow

  1. Collect the customer questionnaire/context.
  2. Receive the relevant bills or source documents securely.
  3. Extract and normalize the required values.
  4. Compare documents across dates or periods.
  5. Generate explanations for increases, decreases and possible savings.
  6. Send findings through human review where required.
  7. Produce a branded report.
  8. Continue monthly tracking when the service includes it.

Bills and documents

The R.I. workflow is intended to support multiple uploaded bills/documents rather than collapsing a multi-file comparison into one record. Dates, account/resource identifiers, totals and other extracted values should remain traceable to the source document used in the comparison.

OCR/extraction quality can vary. Low-confidence or ambiguous fields should be flagged for review rather than treated as guaranteed facts.

Analysis and comparison

Useful R.I. outputs include:

  • Comparison of bills across arbitrary date ranges.
  • Direction and amount of change.
  • Potential explanations for the difference.
  • Cost leakage or unusual consumption indicators.
  • Potential savings opportunities that require customer/human validation.
  • Green-claims or resource-use checks when they are part of the agreed workflow.

ARIA R.I. should explain how it reached a finding instead of presenting an unexplained savings number.

Human review

Resource/cost recommendations can affect financial or operational decisions. The workflow therefore supports human review before a report is treated as final, especially where OCR quality, tariffs, contractual terms or unusual billing rules could change the interpretation.

Reporting

The intended deliverable is a readable, branded report that distinguishes source values, comparisons, findings, explanations and recommendations. Reports should identify the relevant date ranges rather than implying a month-to-month comparison when the documents cover different periods.

Monthly tracking

Where included in the customer's service, later bills can be compared against earlier records so the organization sees whether resource use or cost trends are improving, worsening or remaining stable.

Customer access

ARIA R.I. appears in the customer product catalog. If the organization is not entitled, it remains visible as Locked with a product explanation. Active operational access should only be granted after the required R.I. workflow/backend for that customer is configured.

Current implementation status

Earlier R.I. workflow work includes the extraction/normalization/compare/report direction and n8n-style processing stages. The current ARIA Console foundation has the entitlement and product-discovery layer, but the complete production customer R.I. module is still a separate integration task.

This documentation intentionally describes the product/workflow without claiming that every operational R.I. function is already reachable from the customer dashboard.

Data handling

Bills and resource documents can contain account and commercially sensitive information. Source documents and extracted values must remain scoped to the customer organization and handled according to the applicable privacy/security controls. See Security & privacy.