The OSCRE Industry Data ModelTM is a single, object-oriented, relational data model that comprises over a thousand entities and extensive code lists, attributes and associated codes and classifications. It covers the real estate asset life cycle from development to demolition, many global jurisdictions, and almost all asset classes. Navigating such a vast and deep resource could be complex. So we've made it simpler by classifying the content in several ways.
The most important classification of the Industry Data ModelTM is the Use Case. A Use Case is a subset of the data model that applies in a specific situation.
The picture opposite illustrates how each use case draws from the extensive data model shown underneath as a collection of nodes (entities or code lists) and relationships, and creates a subset for a specific situation - the shaded shape on the upper level of the diagram.
There are more than 130 use cases, each defining a subset that applies in its own unique context. Some of these use cases are small containing only twenty attributes, and some contain several thousand attributes.
To help identify the use cases that are relevant to a particular organization, each is classified to make it easy to filter the full list and quickly find the most relevant standards.
The classifications include:
- Function: This identifies the functional area that each use case applies to, for example Facilities Management or Portfolio Information Exchange.
- Project or working group: Standards are often developed is a collection of use cases that support a particular process, for example Development Handover. These use cases collections can be easily identified by the project or work group that developed them.
- Partner or organization: OSCRE routinely incorporates third party content where they exist into the Industry Data Model to provide a single source for standards. Sometimes this content also gives rise to specific use cases, and sometimes OSCRE partners with specific industry groups to develop new use cases.
- Type of standard: Use cases fall into one of two types: data model standards describe data at rest (e.g. stored in a database, perhaps for analytics, or representing a specific report or certificate) and data exchange standards describe data in motion (for example a transfer from one organization to another or from one system to another).
Each use case has its own metadata, and in many cases this includes the stakeholders it applies to, or activities it supports, and specific benefits. Use cases also have 'renditions' - particular formats that describe the contents of the use case - to support their implementation. These renditions typically include formats like JSON, XML and Excel.
OSCRE Industry Data ModelTM
While use cases are a convenient way of finding specific content, and are the way in which specific standards are delivered, the entire IDM is actually greater than the sum of these parts.
There are three reasons for this:
- The IDMTM contains definitions and codes that are not used in any specific use case, but are terms that have been defined in the course of developing use cases.
- Use cases that are rendered as JSON or XML schemas are necessarily simplified to be hierarchical, even though the underlying data model is relational. From a technical perspective this means determining the direction of each association between entities in each use case so that aggregation associations can be converted to composition associations.
- When a use case selects its subset of the full IDM, this not only means a subset of the entities, but also a subset of the attributes on those entities, and a subset of the codes on each code list. When browsing the definitions in a use case, the number of attributes or codes that are omitted from that particular use case but that exist in the full data model is shown as a footnote.