Sub-Building Data Standard

Intended Audience and Contact Information

Contact	Chief Data Officer, Office of the CIO
UDM Domain	Location
Intended Audience	Internal UBC
Data Standard ID	DS0022

Change Log

Standard Version Change Log

Standard Version Date	Change Log
2024-08-02	1.0 Addition of 'Format' column to Attributes of a Sub-Building section, with addition of standard formats for all attributes. 2.0 Removal of 'Form Type' attribute and related reference data section of the same name. 3.0 Addition of 'Sub-building Type' attribute, definition and reference data section of the same name.
2021-03-30	Data Standard published.

Standard Version Date

Change Log

2024-08-02

1.0 Addition of 'Format' column to Attributes of a Sub-Building section, with addition of standard formats for all attributes.

2.0 Removal of 'Form Type' attribute and related reference data section of the same name.

3.0 Addition of 'Sub-building Type' attribute, definition and reference data section of the same name.

2021-03-30

Data Standard published.

Definition

A Sub-building is a portion of a Building, as defined in the UBC's Building Data Standard.

Purpose

This standard aims to achieve consistency across the University (Vancouver and Okanagan campuses and Reginal Sites) around the data collected for Sub-Building, and the format in which it is collected and stored.

This standard applies to all UBC applications collecting Sub-Building information. Exceptions are listed in the Dispensation section.

Standard

Guiding Principles

Attributes of a Sub-Building

Attribute	Requirement	Definition	Format
Sub-Building Name	Required	Name of sub-building.	Text
Sub-Building UID	Required	Unique sub-building identifier.	Text
Sub-Building Status	Required	Status of the sub-building (Complete, Under Construction).	Text
GBA	Optional	Gross Building Area; Total area of sub-building where it sums to a building (where required).	Numeric
Building UID	Required	BLDG_UID of Parent Building as recorded in Building database.	Text
Sub-Building Usage	Required	Primary Usage based on occupancy.	Reference List See Sub-Building Usage section for accepted values.
Sub Building Type	Required	Describes the purpose of the sub-building.	Reference List See Sub-Building Type section for accepted values.
Grade	Optional	The term used to indicate whether a sub-building is above or below the ground level.	Text
Construction Material	Optional	Classification of building based on construction material type. As specified in the Development Permit.	Text

Sub-Building Usage

The following are the accepted values for Sub-building Usage:

Accepted Data Value	Definition
Academic	Building used for instruction, education, laboratory, or student services purposes.
Administrative	Building used for administrative purposes, mainly offices.
Athletics	Building used for athletics and recreation purposes.
Commons	Building that is located in the mixed-use (primarily student housing with academic) areas identified in the Vancouver Campus Plan.
Commercial	Building used for commercial purposes.
Housing	Building used for residential purposes in neighborhoods.
Operations	Building used for operational purposes, with limited offices.
Other	Building used for other purposes that are not defined by the other usages. Examples include Theological colleges.
Parking	Building used for parking.
Research	Building used for research purposes. Examples include NRC, TRIUMF.
Services	Building used for the purposes of providing a service to the UBC Community, including students, faculty, staff and residents. Examples include cultural attractions, hospitals, child care centers, and community centers.
Student housing	Building used for student housing purposes.

Sub-Building Type

The following are the accepted values for Sub-building Type:

Accepted Data Value	Definition
Section	A specific named portion of a building, includes wings, blocks, and houses.
Occupant	A portion of a building allocated to a department.

Compliance

This standard about Sub-Building must be complied with every stage of the data lifecycle with the exception of any dispensations (see Dispensation section):

All applications must collect Sub-Building as recommended in this standard.
Enterprise Data Integration must adopt this standard.

Reference Data Compliance for Data Integration

The use of accepted reference data values in this standard for data integration among applications must comply with the enterprise integration pattern of leveraging the reference data common service API (Application Programming Interface) published in UBC MuleSoft Exchange.

Any application that intends to access real-time, case-level reference data should have the application owner or manager complete and submit a Request API Access form.

Mapping of Invalid Values from System(s) of Record (SOR) to Common Services

A common service can only accommodate standard reference data enumerations that are available in the SoR as approved by the Data Governance Steering Committee or Data Trustee.

A reference data value that does not match any of the standard reference data value enumerations is considered ‘invalid’. Any records from a SoR containing an invalid reference data value for a given data element or attribute must be mapped as an ‘empty’ value in common service(s). Where a reference data value may potentially have the same meaning as a standard enumeration but named differently in the system of record can be corrected to match the appropriate standard enumeration. Please consult with the EDG team in such cases.

Additional Reference Data values in a SoR that are not part of the standard reference data enumerations are to be omitted in the common service.

Dispensation

None.

For any compliance questions or requests for a temporary dispensation, please contact the Enterprise Data Governance Team.

Sub-Building Data Standard

Intended Audience and Contact Information

Change Log

Standard Version Change Log

Definition

Purpose

Standard

Guiding Principles

Attributes of a Sub-Building

Sub-Building Usage

Sub-Building Type

Compliance

Reference Data Compliance for Data Integration

Mapping of Invalid Values from System(s) of Record (SOR) to Common Services

Dispensation

Related Documents

Office of the CIO

Related Sites

Need Help?

About UBC

UBC Campuses

UBC Sites