Fixture platforms already show what connected products do after installation. blueproof.ai uses that operating evidence as the project side of a source-linked water record, then adds a separate baseline, method, assumptions, and calculation so customers can support the result in reporting or independent review.
Connected fixtures already create value through operations, water-use reporting, device health, alerts, and product performance. That foundation is not replaced or reduced to a data feed.
blueproof.ai tests an adjacent use for the same strength. It preserves the fixture evidence and product context, relates them to a separately documented without-project baseline, and prepares the record a customer or reviewer needs behind a reported water result.
When a customer carries the project into owner or ESG reporting, the activity, reported use, fixture identity, and product context remain part of the evidence behind the number.
The fixture platform continues serving operations. The same established evidence can also support a defined project result in reporting, incentive review, or independent assurance.
A pilot can define the permissions, product context, baseline evidence, review format, and customer question needed to repeat the use without changing the core operating workflow.
Connected fixtures report activity, water use, identity, health, and product context through the manufacturer's established operating system.
The integration carries the relevant fixture-side records into a defined project and reporting period with their source references intact.
Pre-project specifications and building records support the modeled without-project baseline. The versioned method, assumptions, exceptions, and calculation remain visible.
The result can move into owner or ESG reporting, incentive review, tenant requests, or assurance with a path back to the fixture evidence behind it.
Sloan gave ScopeLimited access to its SC Argus Pro sandbox and API. blueproof.ai uses that interface for locations, devices, SKUs, fixture activity, reported water use, health, and alerts. The remaining question belongs in a customer deployment: whether the combined record supports a defined reporting need.
See the platform →The evidence layer is designed to preserve each manufacturer's source fields and product context while applying the same separate-baseline and review discipline.
We look at API access, activation semantics, flow-rate metadata, verifier exports, and how the manufacturer is represented to building owners.