On this page you'll find terms and definitions associated with the Building Energy Data Exchange Specification (BEDES).

Data Specification, or Spec

A data spec establishes clear field names, definitions, formats (e.g. number, text) and enumerations (categorical lists) It serves as a guide to ensure that data is consistent among a range of sources and uses. For example, Green Button is a data specification that is used for utility customers' energy consumption information.

Data Schema

A data schema (or model) describes the structural relationships, hierarchies, and dependencies between data fields. For example, a schema might dictate that energy consumption data should be associated with a meter and a space in a building. A data specification could be used as the basis for a schema. Schemas are then implemented in databases, software tools and platforms.

Database

A database stores data in an organized structure and allows for the data to be defined, added, edited and queried. The data are typically organized using a spec and schema that support software tools.

File Format

A file format is a specific encoding of a data spec in a computer file to be imported or exported by a software tool or viewed by a user. File extensions are used to denote different file formats. For example, a file formatted as comma separated values would have a file extension of .CSV. Many software tools and databases interact using .XML (Extensible Markup Language).

Software Tool

A software tool is a Web or desktop-based computer program that performs specific activities for a user, such as building energy data analysis or data management. The software's source code establishes instructions on how to complete different activities using structured data. Portfolio Manager is an example of a Web-based software tool that conducts analysis and stores information in a database.

Software Platform

A software platform is a specific combination of data specifications, databases and software tools that is delivered as a system for users. The Buildings Performance Database is an example of a platform that utilizes the BEDES spec, contains a database, provides its own software tool, and can also be accessed by third-party tools.

Use Case

A use case describes a scenario of activities used to achieve a desired outcome. Software tools and platforms are designed to serve specific use cases. For example, a building owner may conduct several analytical tasks in order to make an investment decision. The purpose of this report is to ensure that BEDES can be effectively utilized by databases, tools, and platforms that serve specific use cases.

Guidelines

A guideline is a set of protocols or best practices to utilize when collecting and/or analyzing data for a specific use case. Guidelines often do not prescribe use of a specific data spec, tool or platform. For example, ASHRAE's Procedures for Commercial Building Energy Audits and DOE's Uniform Methods Project describe analytical tasks that could be completed using the BEDES spec or other data formats.