Analysis Models and Elements

Introduction

Analysis Models are models used to facilitate analyses of infrastructure. Analyses that require an Analysis Model typically cannot be performed directly on Physical Models as the physical world is too complex; these analyses require simplified geometry and other data. Analysis Models are similar in purpose to Functional Models, but have one significant difference: they are models in true world coordinates.

Not all analyses require an Analysis Model. Examples of analyses that would not require Analysis Models are clash, cost and schedule analyses.

Typically each Analysis Model is relevant to only one type of analysis. A particular Physical Model (e.g. a building) may have multiple associated Analysis Models. Examples of the analyses facilitated by Analysis Models are hydraulic analysis, building energy analysis, roadway analysis and structural analysis.

Analysis Elements

As discussed in Element Fundamentals, Analysis Elements are simplified representations of real physical infrastructure. An example of an Analysis Element is a Pipe Segment (not a physical pipe) in a hydraulic analysis model. This Pipe Segment might have a simple 2D line segment location, together with a set of hydraulic analysis properties; it would also likely have relationships to other hydraulic Analysis Elements in the network being analyzed.

Analysis Elements must always be contained in Analysis Models. Analysis Elements will frequently have relationships to the Physical Elements that model the same real world infrastructure. This relationship, however, is not always 1:1.

Analysis Models

As discussed in Model Fundamentals, Analysis Models exist to facilitate the analyses of infrastructure. Analysis Models contain – directly or indirectly - all of the information necessary for one or more analysis of single type. For some analysis domains, it may be appropriate to have more than one AnalysisModel for a PhysicalModel.

Contents of Analysis Models

Analysis Models contain Analysis Elements, but they may also contain other types of Elements. Analysis Models will frequently contain InformationElements. AnalysisModel3ds may contain SpatialElement3ds. Analysis Models never contain PhysicalElements.

Analysis Models in Model Hierarchy

As Analysis Models are used to assist in the design or understanding of physical infrastructure, Analysis Models are often linked to PhysicalModels.

Typical Analysis Model Workflows

Analysis Models are expected to be used in three basic scenarios:

  1. Analysis Model is derived from a PhysicalModel
  2. PhysicalModel is derived from an Analysis Model
  3. Analysis Model is used without relationship to a PhysicalModel.

Deriving an Analysis Model from a PhysicalModel is expected to be a common workflow. Existing or planned infrastructure will frequently be modeled and need to be analyzed. The derivation of the Analysis Model may be automated, partially automated or manual. The derivation will typically create relationships between the PhysicalElements and the Analysis Elements. These relationships can be used later to assist with updating the Analysis Model when the PhysicalModel changes, or in creating a two-way syncing of information between the two models.

Deriving a PhysicalModel from an Analysis Model may be a common workflow for new infrastructure when the analytical design of the infrastructure occurs before the physical design. The derivation of the PhysicalModel from the Analysis Model is often a simple automated operation, but typically does not produces a fully-detailed PhysicalModel. As with the Physical-to-Analysis derivation, relationships between PhysicalElements and Analysis Elements will typically be created. These relationships can be used for updating and two-way syncing.

A standalone Analysis Model that is not related to a PhysicalModel is a valid configuration. This configuration might be used when the organization using the iModel is only involved in the analytical investigation.

Last Updated: 06 December, 2018