Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| UDM Domain | Location |
| Intended Audience | Internal UBC |
Change Log
| Standard Version Date | Change Log |
|---|---|
| 2022-12-12 |
Mapping of Invalid values From Systems(s) of Record (SoR) to Common Services sub-section of Compliance section added |
| 2022-03-09 |
Reference Data Compliance for Data Integration sub-section of Compliance section added |
Purpose
This standard aims to achieve consistency around the data collected for Building Complexes across the University (Vancouver and Okanagan campuses and regional sites), and the format in which it is collected and stored across the University.
This standard applies to all UBC applications collecting Building Complex information. Exceptions are listed in the Dispensation section.
Standard
Definition: Building Complex is a grouping of Buildings as defined in the Campus Building Data Standard.
Note: Building data is comprehensively captured across the University. The building complex is required when a hierarchical relationship from the complex to the building and to some sub-buildings, is needed as listed in the following guidelines below:
- based on significant named spaces, including buildings that may be interconnected physically and/or in close proximity (e.g. UBC Botanical Garden)
- based on a civic address assigned at the complex level, but each building within the complex requires a primary address (e.g. Robert F. Osborne Centre)
- based on operational needs for a complex, including relationships between systems (e.g. Totem Park Residence).
| Attribute | Requirement | Definition |
|---|---|---|
| Building Complex UID | Required | Unique Building Complex identifier. |
| Building Complex Name | Required | Name of Building Complex. |
| Building Complex Short Name | Required | A short name for the Building Complex. |
| Building Complex Status | Required | Status of a Building Complex (e.g.: Complete, Mixed, Under Construction). |
| Building Complex Usage | Required | Building Complex usage |
| GBA | Required | Gross Building Area; Total summed area from building for Building Complex. |
Accepted Data Values for Building Complex Status:
| Accepted Data Value | Definition |
|---|---|
| Complete | All buildings within a Building Complex have received an Occupancy Permit. |
| Under Construction | All buildings within a Building Complex have received a Building Permit. |
| Mixed | Not all buildings within a Building Complex have received an Occupancy Permit. |
Compliance
This standard about Building Complex must be complied with every stage of the data lifecycle with the exception of any dispensations (see Dispensation section):
- All applications must collect Building Complex 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.