Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| UDM Domain | Asset |
| 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 for classification of an asset to ensure efficient, effective management and control of assets. A classification is a grouping of assets based on their type, characteristic and or functionality.
This standard leverages the American Society for Testing Materials' (ASTM) Standard Practice as reference to build elements and site work. It applies to all UBC applications using Asset Classification.
This standard does not address any contractual requirements imposed upon the entity, and does not address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to ensure that all contractual requirements are met, as well as establish appropriate safety and health practices, and determine the applicability of regulatory limitations prior to use.
This standard is to be adhered to at all times. Exceptions are listed in the Dispensation section.
Standard
Asset classification cannot have more than seven levels. Following is the description of different levels and their codes guidelines. A business can choose a number of levels to implement as long they don't break the flow. For example, an application can use levels 1-5 or levels 2-6, but cannot select 1, 3, 5 etc.
| Asset Classification Levels | Definition | Level Code Rule |
|---|---|---|
| Level 0 (Optional) | Asset Type | Fixed reference codes as defined below. (Six Alphabets) |
| Level 1 | Asset Group | Fixed reference codes (two alphabets) |
| Level 2 | Asset Sub-Group | Value between 01 and 99 |
| Level 3 | Asset System | Value between 300 and 999 |
| Level 4 | Asset Sub-System | Value between 4000 and 4999 |
| Level 5 | Individual Asset | Value between 5000 and 5999 |
| Level 6 | Component | Value between 6000 and 6999 |
The table below shows allowable values for Level I and Level II. Codes, values, definitions and relationship cannot be modified with EDG consultation. See the Asset Management Terminologies Data Standard for the definitions of these terms.
| Asset Classification - Level 0 | Level 0 Values | Level 1 | Level 1 Values |
|---|---|---|---|
| SRVAST | Servicing Assets |
ME |
Mechanical Electrical Services Utility Services Fleet Services |
| INTAST | Intangible Assets | LE IN CP PT SF CM |
Lease Intellectual Property Copyright Patent Software Computer |
| CNSAST | Consumable Assets | ST | Stock |
| INFAST | Infrastructure Assets | TR LS WM |
Transportation Network Landscape Waste Management |
| MOVAST | Moveable Enabling Assets | FR TL |
Furniture Tools |
| BCMAST | Building Components | BE BI |
Building Envelope Building Interior |
An Asset Classification ID format is as follows:
"Level0Code.Level1Code.Level2Code.Level3Code.Level4Code.Level5Code.Level6Code"
For example,
Example 1: A code for level 2-4 classification is ME.20.341.4563
Example 2: A code for level 2-6 classification is TP.91.372.4782.5777.6123
The following rules apply when classifying an asset:
- Every asset record must align with asset classification depending upon the application applicability.
- An asset must align with at least Level I, II, and III.
- Classification must not exceed a maximum of seven levels.
- Level 0 is optional, but fixed code must be used when it is being used.
- Collibra is the system of record for Asset Classifications, so classification should not be managed locally.
- If certain changes are required, a proper review and communication should be performed with all the relevant stakeholders in UBCV and UBCO.
Compliance
This standard must be complied with every stage of the asset data lifecycle with the exception of any dispensations (see Dispensation section):
- All applications must define or align to Asset Classifications as shown in this standard.
- Enterprise Data Integration must adopt this standard.
- All data collection exercises should adhere to 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.