For Implementers

BuildingSync® is a standardized language for commercial building energy audit data that software developers can use to exchange data between audit tools. Taking the form of an XML schema BuildingSync can be implemented by building owners and audit program managers to allow data analysis and aggregation across multiple buildings in order to evaluate program performance and analyze trends.

Where do I start?

Integrating BuildingSync into your application generally follows a four step process to ensure compliance and maximize interoperability. This process will inform the life-cycle of your implementation.

Understanding Use Cases

A BuildingSync use case is a workflow within which BuildingSync is leveraged for data exchange in platform(s). Depending on the connected platform(s), various users can collect, report, process, and analyze audit data through BuildingSync to meet their specific objectives. BuildingSync considers the needs and interests of a wide range of users in the energy audit industry, including building owners, auditors, software developers, utilities and program managers. It is important to note that a single BuildingSync file can satisfy multiple use cases if the requirements are met. Typical BuildingSync use cases include:

  • Building energy assessment software integrating the ability to export BuildingSync-compatible files into their software
  • Energy auditing services choosing to use software that can output BuildingSync-compatible files
  • Building owners incorporating BuildingSync into their next RFP for a building energy audit by requiring the auditor to provide data in a BuildingSync-compatible format
  • Utilities choosing to recommend or require software that uses BuildingSync-compatible files for any programs involving energy audits.
Explore Use Cases Submit a Use Case

Understanding the Schema

To understand which of your application data can be expressed in a BuildingSync-compliant file, adopters can interface with the BuildingSync Schema in a number of use case-specific ways. There are three main parts to the Schema that when used in tandem, produce a complete model (see table below). Additionally, each release of the schema includes several supporting documents: the Schema, a Data Dictionary, List of Measures, and Full Documentation.

  • Schema - defines the structure of elements and their polymorphic ontologies.
  • Data Dictionary - The data field “dictionary” includes field names, definitions, units, and other attributes for the enumerated fields. The data dictionary is aligned with BEDES, but includes only the subset of data fields that are relevant for energy audits.
  • Measures - contain a TechnologyCategory and a list of valid enumerations.
View the Schema Current Schema releases

Working with BuildingSync

Creating a BuildingSync XML file can be as simple as opening your favorite text editor and manually building up nested elements. However, to make this process easier, we have a set of resources to assist you during the schema adoption process.

There are a number of technologies supported for the development of XML files. If you are unsure about where to start, we suggest the native XML python module or the lxml python package.


BuildingSync uses Schematron as the assertion engine for validating against specific use cases. Each use case is paired with a Schematron file defining its requirements. Below are the use case and Schematron resources.