*1.What best describes your profession?(Required.)

Consultant

Client Side

BMS Service Provider

SaaS / Analytics Service Provider

Other

*2.What best describes your or your organisation’s current involvement with HVAC operational data?(Required.)

Operate systems that generate data

Integrate systems

Consume data through automated systems

Consume data through manual systems

Do no currently work with HVAC data but have aspirations to do so

*3.What best describes the frequency of your interactions with HVAC operational data?(Required.)

Always: Wrangling HVAC data is the majority of my role

Daily: I frequently interact with HVAC data to support my core activities

Weekly: I occasionally interact with HVAC data

Less than weekly: I rarely interact with HVAC data

Aspirational: I do not use HVAC data but intend to start

*4.Which metadata systems does your organisation use to structure data?(Required.)

Project Haystack

Brick Schema

RealEstateCore

Google Digital Buildings Ontology

Other open source schema

A proprietary schema developed for internal use

None

*5.Which of the following describes your greatest pain points with structured HVAC operational data?(Required.)

The tools I have access to do not natively contain enough detail to accurately model the systems I interact with

I only have access to raw data from systems because no metadata model exists

The systems my organisation uses do not derive any benefit from structured data

The metadata models in systems I extract data from are often incomplete or incorrect, so I need to manually recreate the models to achieve interoperability

I do not have access to tools to verify the correct application of data models, so I discover errors when bugs occur

I consume data using manual methods and I just want access to raw data

Other or none

*6.Which of the following improvements would you like to see from the industry?(Required.)

More user friendly tools/A reduced barrier to entry for applying and using metadata models

A straightforward way to look up the current best practice schema/tags for a piece of equipment using an API

A straightforward way to look up the current best practice schema/tags for a piece of equipment using a webpage

A straightforward way to translate between metadata models

Tools to validate new integrations against a specification

The current tooling and documentation is fit for purpose

I don't see a market or level of demand for structured data that justifies additional investment in this space

*7.Are there any areas specific to the Australian market that require attention from the AIRAH / OAP working group?(Required.)

Localisation of naming, where terminology in Australia differs from the metadata systems

Expansion or extension of described systems, where the Australian market uses plant or equipment not well described by existing metadata systems

Opportunities to support Australian risk, compliance and rating spaces

Other (please specify)

*8.Would you like to be kept up to date about AIRAH's activities in this space?(Required.)

Yes

No

9.Please provide your email address if you would like to be kept up to date