RESET® Standard

Welcome to the FAQ section for RESET Data Providers.

Click here to go back to RESET Data Providers.
Click here to go back to the FAQ list.

1. Accreditation Process

In order for a data provider platform to start interfacing with the RESET Cloud, we will need to use the API and confirm a successful data transfer. Should we submit a letter of intent to RESET at info@reset.build prior to this?

Yes. Please refer to the instructions in the RESET Data Provider Process page.

Do we need to sign an NDA or similar privacy agreements as needed for assurance of security and data accuracy?

We do not require an NDA, but many data providers have requested for one.

What do we need to prepare for in regards to system auditing requests from RESET?

Data provider auditing does not happen unless we suspect that there might be data falsification. For requests, RESET might request for random raw data from monitors to compare with the averaged data submitted to the RESET Cloud in the form of a .csv.

How long is the process to become a RESET Accredited Data Provider?

The process takes anywhere from 2 weeks to 2 months. It really just depends on the API connection development. If the API is developed smoothly and connects to the RESET Cloud properly on the first try, then 2 weeks is the best case scenario.

2. Data Provider Requirements

What is required in regards to the presentation of data (display and communication) to the occupants of the RESET Project?

You must demonstrate to RESET that you have a way to display and communicate data to the occupants. There is no required way to show the data.

Live Data Display in Public Spaces: Please clarify visibility, do we need to provide the occupants with screens in building public spaces?

For certification, you only need to demonstrate that there is a way for occupants to access the data. This could be via an app. A live public display is currently not necessary.

Accessible Live Data: This seems straight forward but just to confirm, if we provide occupants with live data off of our website for their particular project this will satisfy this need?

Yes.

For display and communication, will a website that shows all 5 parameters per monitoring station for all building monitoring station with access via a building-centric username/password suffice?

That will suffice. Screenshots on how you would display the data to occupants will suffice for submission purposes.

3. API & Data Requirements

You can find the Data Provider API documentation here: https://doc.reset.build/providers/v2/.

How can we get access to the API? Since it is only after confirmation of successful data transfer that a data provider will receive the accreditation, how does a data provider test the data transfer on a scaled-up operation in the meantime?

Our development team will provide a token for you to communicate with the RESET Cloud servers to test the API.

What are the options for how often data is sent from the data provider to the RESET Cloud?

There are two options: once every 24 hours or once every 30 minutes. Final frequency just means that you have options for how often and when, which would be finalized when implementing the API.

If we intend to push data from our server once every 24 hours, where the data will represent an average of 30 minutes for each of the 5 parameters per a single monitoring station (averaging data intervals of 1 min for Grade A or 5 Minutes for Grade B), will that work?

Yes. That fulfills our requirements of 30 minute averaged data submitted at least once every 24 hours.

Are there any specific rules for the format for station_code?

There are no specific rules other than it must be unique from your data provider platform. We typically recommend to use the UUID of the monitor.

If a data provider is designed to create new monitors dynamically, we need to check programmatically if a monitor already exists. Is there an API we can use to check if a monitor exists already based on station_code?

Unfortunately, there is currently no API for checking monitors, but it is probably something we should consider. For now, if you want to create monitors dynamically, the current solution includes the following two ways:
a）Keep an "added monitors" list on your side. A monitor should have been added if you received ‘ack’:’true’ for the monitor create message.
b）Use a redundancy creation strategy since we currently do not have any restrictions around creating a monitor on top of an existing monitor.

Is there a way to delete monitors?

No, there is currently no way to delete monitors programmatically. If it is necessary, please contact us.

Is there a limit on the number of monitors a data provider can create?

There are currently no limits as to the number of monitors you can create.

RESET^® Data Providers FAQ

目录

1. Accreditation Process

2. Data Provider Requirements

3. API & Data Requirements

RESET® Data Providers FAQ

目录

1. Accreditation Process

2. Data Provider Requirements

3. API & Data Requirements

RESET^® Data Providers FAQ