Long-term Support

Support that continues after deployment

Initial acceptance closes the deployment phase. Long-term support defines what ClimaMind can continue to provide as the site operates: data stewardship, model improvement, visibility, site-specific tuning, and broader technical collaboration.

Not every customer needs every service below. Optional items are scoped during acceptance or in a separate service agreement so the operating boundary stays explicit.

Offerings

What we can provide after go-live

These are the main long-term support paths. Optional services are labeled and agreed before they become part of site operation.

Data collection & custody

Optional

When the customer wants ClimaMind to continue receiving and holding approved operating data, we can maintain the agreed data pipeline and retention boundary after deployment.

  • Continue BAS trend, meter, weather, and operating-context collection within the approved scope.
  • Apply the same security, access-control, and retention rules defined during deployment.
  • Keep data aligned to equipment, measurement boundary, and reporting needs for ongoing review.
  • Document what is collected, how long it is kept, and who can access it.

Long-term model optimization

When the customer shares operating data with ClimaMind, we can keep improving models and control strategies to raise energy savings over time rather than treating the first deployment model as final.

  • Recalibrate baseline and control models as weather, occupancy, tariffs, equipment, or operating modes change.
  • Review comfort, reliability, and equipment constraints before expanding or retiring strategies.
  • Use measured operating evidence to prioritize strategies that improve savings without breaking site rules.
  • Hold back changes that depend on missing signals, unclear permissions, or unverified operating modes.

Dashboard

Optional

When the customer wants a customer-facing operating view, ClimaMind can provide dashboard access for approved users to review status, performance, and agreed reporting views.

  • Give authorized users access to site status, telemetry quality, and agreed performance views.
  • Support operator review of optimization behavior, overrides, and issue escalation context.
  • Align dashboard scope to the deployment boundary rather than exposing unrelated building systems.
  • Apply the same authentication, access-control, and audit expectations as deployment security review.

Long-term partnership

For sites that want deeper collaboration, ClimaMind can maintain a long-term relationship focused on endpoint-specific optimization: tighter tuning for the systems, zones, or operating modes that matter most on that site.

  • Focus ongoing work on the systems and control opportunities inside the agreed measurement boundary.
  • Adjust strategy depth as the customer learns what operators will accept and what equipment can support.
  • Coordinate with facility teams, SI partners, and any agreed M&V partner on boundary or reporting changes.
  • Expand only where site evidence supports it; retire strategies that no longer fit operating reality.

Other technical collaboration

Beyond day-to-day optimization, customers may need adjacent technical work: integration extensions, reporting changes, measurement support, or engineering review tied to the deployed system.

  • Support integration or point-mapping updates when the BAS, metering, or operating context changes.
  • Help adapt reporting, M&V views, or customer-readable operating summaries to new commercial needs.
  • Provide engineering review for control-boundary changes, fallback updates, or staged write expansion.
  • Scope additional work explicitly so it stays separate from routine optimization service.

Engagement

How long-term support is agreed

Long-term support should be defined before or during acceptance so operators know what continues automatically and what requires a separate approval.

  • Acceptance closes deployment; long-term support starts from the agreed operating cadence and service scope.
  • Optional data custody and dashboard access are enabled only when the customer approves the boundary, users, and retention model.
  • Model optimization depth depends on data sharing, telemetry quality, and whether the site allows ongoing strategy review.
  • Site-specific partnership and additional technical work are scoped in writing when they go beyond the base optimization service.
  • Performance review, reporting cadence, escalation paths, and change control carry forward from acceptance into ongoing service.

Related

Related deployment topics

Long-term support connects back to acceptance, security, M&V, and operator workflows defined during deployment.

Acceptance

See how deployment closes and how the ongoing service cadence is defined at sign-off.

Security & Access Control

Review data transfer, dashboard access, remote support, and audit expectations for ongoing operation.

Measurement & Verification

Understand how savings evidence and reporting continue after initial acceptance.

Operator Change Management

Confirm operators know how to review, override, and escalate during long-term operation.

Back to deployment overview