Objectives of BIM/Model Origin and Setup

Updated 26/07/2017

BIMFix Blog is pleased to announce the release of a "BIMFix Framework for Shared Model Establishment" which can be downloaded for free from here. This framework document shows how the below can be implemented on a project.

A:- Premise:
A.1.1:- When it comes to the BIM model origin, coordinates and project setup; Three Dimensional (3D) virtual models (BIModels) have to meet many goals. This includes:
  1.  Limited survey data available at early project design stage
  2. World Geodetic System
  3. Limitations of computer computation algorithms and units
  4. Different project team member needs
  5. Different BIM deliverable needs
  6. Scalable within projects sizes and types
  7. Building relocation management
  8. Allocation of responsibility and risk mitigation
  9. Allowance for human error, and follow-up resolution
  10. Work within international standards

A.1.2:- Do your project model processes and workflows take all these into account? If they don't; you are potentially limiting the use of the model, or adding risk for the party needing to relocate or modify the model to meet the omitted goal?

A.1.3:- Over the past two decades, 3D models are commonly circulated between project teams to enhance coordination, communication and meet deliverables. When dealing with 2D (CAD files & Paper), very few drafters were concerned with CAD file origins accommodating other parties workflows. Other parties drawings had the sole purpose of providing backgrounds or visual coordination underlay references.

A.1.4:- (Australia is given as an example in this article, however, the same principles are applicable globally)

A.1.4:- Today, however; there are many potential uses of models:

  1. Components from one discipline can be hosted directly on another disciplines element,
  2. Identical components across discipline models may have spatial monitoring engaged,
  3. Consultants may be obtaining geodetic coordinates from the Architect’s model,
  4. Components may be tagged and annotated across discipline models,
  5. Components of the model can be directly used for element set-out (e.g. Trimble robotic total station),
  6. Models are becoming the center of team communication, with file formats such as BCF (BIM Collaboration Format). This may need to work between relevant applications involved.
  7. There is greater use of models across multiple deliverables and they are expected to seamlessly integrate between disciplines and applications,

A.1.5:- An inappropriate origin set-up can have a direct impact on project teams. Let’s elaborate on the above list and understand the challenges and goals:

1. Limited survey data available at early project design stages
1,0.1:- It is rare to have a comprehensive site survey at project kick-off, or even concept/sketch design stage. Ideally, a CAD survey is available from the Land Surveyor, about 8 weeks before the end of Sketch Design.

1.0.2:- On the first few days of building modeling conception, relative levels and spatial coordinates are not a high priority on most projects. There are, of course, exceptions. Designers need to evolve the design principles with limited site information. Model users may not understand the potential consequences of a bad project set-up, and thus, a simple, user-friendly approach (plan) is likely to succeed.

2. World Geodetic System
2.1:- Geocentric Datum
2.1.1: - Australia’s official geodetic datum is Geocentric Datum of Australia,1994 (GDA94). 
This coordinate system fits into the global coordinate system. It came into use in 1994 and is compatible with the Global Positioning System (GPS). It includes Grid coordinates (Universal Transverse Mercator (UTM), using the GRS80 ellipsoid); called Map Grid of Australia (MGA94). Note: This replaces the former grid system Australian Map Grid (AMG).
UTM was first developed by the United States Army Corps of Engineers.

          Above image: Map Grid of Australia 1994
2.1.2: - Each country, and in the US; States, have their own Universal Transverse Mercator (UTM) or similar Map Grid, In the UK it's called the Ordnance Survey National Grid, in the US it's the State Plane Coordinate System.

2.1.3: - MGA94 fits within the global “Longitude” grid (vertical) and is 6⁰ of separation (giving 60 Zones). It starts at the International Date Line and works anti-clockwise around the earth. Each grid sector is allocated a Zone number. Australia is between Zone 49 (West W.A) and Zone 56 (East N.S.W. / QLD.). It uses the Cartesian coordinate system in a positive X,Y (Easting’s and Northing’s) to locate a point/position. A helpful converter from UTM Coordinates to Geographic (latitude, longitude) coordinate system: AWSM website.

2.1.4: - When in the Northern Hemisphere the Northing origin is measured from the Equator line. For the Southern Hemisphere in order to maintain positive values, the origin is measured 10,000KM south (down) of the Equator line (very close to the South-Pole). The measurement takes the North/South curvature of the earth into account. All coordinates are in meters.
Location examples (approximate):

Melbourne    MGA Zone 55    E 320,000 (Easting)      N 5,800,000 (Northing)
Sydney         MGA Zone 56    E 330,000 (Easting)      N 6,250,000 (Northing)

                   Above image: MGA Zone origins - 500,000m West of the Central Meridian.

2.2:- Universal Transverse Mercator (UTM) 
2.2.1:-  UTM represents ellipsoidal positions (latitude & longitude) as Grid coordinates (Easting and Northing) on a cylindrical surface, resulting in a number of zones. Uniform scale factor, false origins, and zone size and numbering have been adopted for the Universal Transverse Mercator Projection.

Image above – concept of Universal Mercator and Universal Transverse Mercator system – I.e. the attempt to flatten an Oblate Spheroid (the Earth) onto a flat surface. 

2.2.2: - Typically, World Maps use the Universal Mercator, however, MGA maps use the Transverse Mercator system enabling less distortion in a North / South direction. There is an East / West distortion and it can be a Scale Factor varying from 0.9996 (Point A) and 
1.00071 (Point C) as shown in the below sectional diagram.
Above diagram: Extract from The Map Grid of Australia 1994A Simplified Computational Manual,  showing the Scale Factor will vary with the distance of the survey from the Central Meridian allowing for the East-West curvature of the Earth. 

2.2.3:- The Australian Government provides a free to use Calculator, which computes the scale factor (Point Scale) East-West deviation. Thus an MGA survey with an Eastings of 510,200 (Close to the Central Meridian), as per the above calculator, will have a Point Scale of 0.99960128. Thus; 100 meters measured East-West in the CAD drawing will be in fact 100/0.99960128 = 100.040 meters on site. About +40mm out.

2.2.4:- Some local areas are a sub-section of MGA. Perth projects often work to Perth Coastal Grid (PCG). These smaller local grids allow for greater accuracy as they reduce some of the unfolding deviations which occur within the Universal Transverse Mercator (UTM).
The bottom paragraph of this link provides guidance when working on large linear projects to minimize distortion.

2.3:- Elevation (Altitude)
2.3.1:- The “Z” coordinates (Elevation), Australian Height Datum (AHD) is used. This is the mean sea level (Geoid) for 1966-1968 and was assigned a value of 0.000m with the surveying of 30 stations around Australia. All surveys refer to AHD, and again the units are in meters.
Please also note the height above mean sea level will also affect the output scale factor.

Above diagram: Shows, as the Elevation increases the Ground Distance increases vs. the Grid Distance. 

2.4:- Building Set-out (Layout)
2.4.1:- When annotating the set-out of a standalone commercial building, it is common to give Easting and Northing for the primary building set-out Grid (See Figure A.1 image below). and an AHD relative level for each floor level.

2.4.2:- Civil Engineers, Land Surveyors, Transport Engineers all work to this official coordinate system, and it is an imperative any building information exchange integrate with them.

3. Limitations of computer computation algorithms and units
3.1.1:- The above mentioned Geodetic UTM coordinates can become very large:
             6,000,000 m      -        i.e 7 Figures before the decimal point, or
             6,000,000,000 mm -  i.e 10 Figures before the decimal point. 

3.1.2:- Most software applications (including CAD applications and MS Excel) have limitations on how large numbers are stored (.i.e.: 64 Bit precision. CAD applications have stored coordinate figures in a 64 Bit precision since the early-1980's). These include the number of calculated figures they can effectively work with, due to Floating Point Precision engaged via the IEEE 754 Standard. What this means; when we get to the 15th and 16th figures of coordinates, the computer starts to produce rounding errors (see example below). 

3.1.3:- To achieve the required functionality, ideally, 7 figures of precision are desired after the decimal point before the rounding error starts. Thus, If we have more than 8 figures, before the decimal point, we start to produce numerical/graphical errors, such as:

  1. radial arcs and tangential lines won't trim or display correctly, 
  2. graphical or view rendering errors (see image below),
  3. flickering/jumping items when orbiting/moving in 3D Open GL view,
  4. distortion/jumping when zooming in a long way 2D,
  5. lines may appear to flicker/jump on selection, 
  6. hatches won't display/print correctly,
  7. drawings disappearing or displaying as empty on layouts/viewports,
  8. renders are missing lights or objects,

3.1.4:- Sample UTM Coordinate for the Adelaide Convention Center:

             Coordinate Northing:              N  6,133,104.488,756,17 m
             Computer reads it as:                 6.13310448875616956502199172974E6
             Computer 64 Bit Binary Format:
            Above: the figure shows the floating point rounding issue.

3.1.5:- Also, consider some US CAD Building applications (e.g. Autodesk Revit) are hard coded in decimal feet, and changing the units does not change how the coordinate figures are stored. 

3.1.6:- With all of the above, this is one reason land surveyors work in meters. The software is too unpredictable if they worked in millimeters. 
Thus, Building Design and Construction teams who want to work in millimeters must use a known (Easting and Northing identified) "Local" datum origin point.

Above:  Example of importing a Civil model (Sewage Manhole drainage system) from an IFC file format into Autodesk Revit, with the "Y" (Northing) value 360,000,000mm away from the origin. The round manhole polygon distortion is very obvious.

3.2:- Software references of the above problem:

3.2.1:- Autodesk AutoCAD:
3.2.2:- Autodesk Revit:
3.2.3:- Bentley:
3.2.4:- Graphisoft ArchiCAD:
3.2.5:- Microsoft Excel:
3.2.6:- Vectorworks:
3.2.7:- Trimble Sketchup:
3.2.8:- Trimble Tekla:
3.2.9:-  McNeel Rhino:

4. Different project team member needs
4.1.1:- Most building projects can be split up into two camps; those dealing with the site infrastructure or civil works, and those dealing with the building itself. 

4.1.2:- The Meter was created in the early 1790's as one ten-millionth of the distance from the equator to the North Pole - French Academy of Sciences. That is; it was created by measuring a distance over land. All site related geodetic references (MGA & AHD) are in meters (meters are the SI Base Unit). As these disciplines are engaging large dimensional figures, it makes a lot of sense to work in meters. 

4.1.3:- However, within the Building and Fabrication disciplines, component set-outs and measurements are in millimeters.

Site Disciplines: 
(length units meters)
Building Disciplines: 
(length units millimeters)
Land Surveyors
Architects and Interior Designers
Civil Engineers
Structural Engineers
GIS (Geographic Information System) Consultants
Building Services Engineers
Transport Engineers
Building Surveyor / BCA Consultants

Façade Engineers

Acoustics Engineers

Other building specialist consultants

Building Component fabrication modelers
NOTE: Landscape Architects often may prefer to work in millimeters and thus must work off the local site origin.

4.1.4:- As disciplines use different units (meters/millimeters) and thus different origin points, an integrated workflow allowing for a coordinate data exchange needs to be established between all parties.

5. Different BIM deliverable needs
5.1.1:- When looking at the available BIM goals, many project team members will require a different approach to model coordinates and origins. Some examples;
  • 5.1.2:- Master Planning: When master planning a campus it can include GIS data, multiple buildings, staging strategies and integrate Geodetic Coordinate Systems.
  • 5.1.3:- Clash Detection: 95% of Clash detection on building projects takes place within the building itself (this will be different on infrastructure projects). On a commercial Building construction project, the site clash detection is often minimal. Building relocations during design stages should not temporally hold up the Clash Detection process. Clash Detection may also include fabrication model authoring applications which may not support Geodetic Coordinate Systems.
    Communication of Clash detection via (BCF) may require two-way communication. BCF files generally require identical model (hard coded) origins between the applications in use.
  • 5.1.4:- Sustainability Evaluation: When defining the rating scheme used to check the model, (e.g. Green Star or LEED), the building orientation to true north, longitude, and latitude position, are transferred into the analysis application often via the model.
  • 5.1.5:- Positive and Small Coordinates: Some analysis applications require the geometry to be close to the origin and for all geometry to be positive figures. This is to minimize and simplify the computations. It will result in the Model origin being in the bottom right of the model. 
5.1.6:- Thus, it is necessary for the approach to work with multiple units and coordinate systems.

 6. Scalable within projects sizes and types
6.1.1:- Whatever approach and process are used, it needs to be scalable. That is, to work with:
  1. a single green/brown field site building,
  2. a multi-building campus environment, all buildings unique,
  3. a multi-building campus environment, with multiple building units (modules),
  4. a multi-campus project, with multiple building units (modules) across different campuses,
  5. a large single building, comprised of multiple discipline sub-models (due to file size, or multiple production centers),
  6. a project containing existing conditions, staging, and/or building extensions.

7. Building relocation management
7.1.1:- From building design kick off, up until foundation concrete pouring, a building design relocation is likely to occur. This relocation can occur due to new data the design has to integrate. Building movements can occur in any of the X,Y,Z and rotation coordinates. So even if the building takes up 100% of the site, it may still move in the “Z” direction.

7.1.2:- If not planned for and managed appropriately; building relocations can have substantial adverse effects on project teams. Potentially adding weeks of documentation re-work for parties affected.

7.1.3:- During my time as a BIM consultant, it is rare to come across a design practice who have thoroughly investigated and documented the process on how building relocations are logged and executed. Failure to address this may open up liability to parties involved.

8. Allocation of responsibility and risk mitigation
8.1.1:- When it comes to “most” building projects (Infrastructure projects are an exception), the Architect is responsible for documenting where the building is located and set-out (layout) on the site. The Architect will determine this off a site survey provided during the early design stage by the Land Surveyor.

8.1.2:- As the design evolves, and the design location of the building updates, it is up to the Architect to take responsibility for relocation change and adequately communicate it to all relevant parties. All necessary processes are to be established to eliminate other design consultants or contractors, being requested to manually move their models or enter coordinates figures to align with an Architectural model. This is an unnecessary risk. 
If no processes and checking systems are in place, and parties get it wrong and costs are incurred, is the Architect going to reimburse them?

9. Allowance for human error, and follow-up resolution
9.1.1:- No matter how clever a process is, human error is often the weakest link. Thus, the overall workflow should take on board the following:
  1. A protection system in place, to avoid users accidentally moving linked models
  2. An audit at each deliverable stage to pick up coordinate/origin errors
  3. A backup coordinates reference system, to help in resolving any errors
  4. If all fails a reset option, which will have minimum effect on other parties

10. Work within international standards
10.1.1:- There are not many specific standards in regard to site set-up/establishment, so when there is one, it’s worth adhering to it where possible. BS 1192:2007+A2:2016 - Collaborative production of architectural, engineering and construction information – Code of practice has a specific section on site Coordinate establishment. Its relative section is Annex A (normative); Project space statement. This section identifies the establishment of a site map grid (engaging Easting’s and Northing’s map grids). It suggests a location for a project site local origin (site grid origin), and the identification of at least two building grid intersection coordinates and rotation. 
Above:  Figure A.1 Geodetic referencing from BS 1192:2007+A2:2016.

10.1.2:- This approach is very robust, and it also can be used to facilitate item “9” above. BS 1192:2007 is a requirement of UK BIM Level 1 & 2.

10.1.3:- Other relevant Project Establishment and Building Coordinate Standards:

  1. AEC (UK) BIM Protocol For Autodesk® Revit® v2.0 - Sections 6.3.1, 7.4
  2. AEC (UK) BIM Technology Protocol For ARCHICAD v2.0 - Section 7.4
  3. BS 1192:2007+A2:2016 Collaborative production of architectural, engineering and construction information - Section A2 & A3.
  4. BIMForum Level of Development Specification 2016 Draft for Public Comment - "Origins: Basis for all LOD". This section was subsequently removed from the final LOD Spec 2016. 
  5. BuildingSmart Australasia - Initiative - "Model Setup IDM" - Currently in a draft format. 2017.
  6. COBie 2.4 - Workbooks: "COBie.Floor.Elevation": Relative height to primary building entry Level.
    "COBie.Attribute" Facility Geo‐location:- Longitude, Latitude, Elevation & Rotation.
  7. New Zealand BIM Handbook - Appendix A - Modelling and documentation practice - Section 4.3 – July 2014

10.1.4:- Please advise if you are aware of any other industry standards in regard to Model Establishment.

B:- Close
B.1.1:- I can confirm, it is possible to establish a site set-up process to include all the above goals. Any Architectural firm sharing BIModels, need to take the initiative to develop and document (flowchart) the final process. 

B.1.2:- This workflow is then circulated to all relevant parties.
If you are a design consultant, insist you are provided with such a document by the Architect. Ensure you thoroughly test it and check it does not adversely affect your workflows. The consultants are the party most likely to be directly impacted in the event a building relocation is inadequately planned.

B.1.3:- There is no one item mentioned here which is difficult. An all-encompassing plan does take a while to develop and test. Yet it is one sure workflow all lead consultants need to have.

C:- Call for Review
C.1.1:- For any readers, reviewing the above and taking issue with any of the premises, I request you please provide Brian Renehan (the author) with the relevant constructive feedback (via below comment or email - see contact info). Identify the background and reason for your counter argument. The above premises “should” be universal for all building construction projects. If it led to universal software specific workflow outcomes, it would greatly benefit the industry.

No comments:

Post a Comment

Please partake in the discussion. We welcome all feedback and comments, however spam will be removed from the comments section.