EDMmodelServerManager™ |
Opphavsrett
Denne programvaren inneholder opphavsrettsbeskyttet materiale, forretningshemmeligheter samt annet beskyttet materiale. Du skal ikke, og skal ikke forsøke å, modifisere, reversere, dekompilere Programvaren. Du kan heller ikke lage avledede verk eller andre arbeider som er basert på eller avledet fra Programvaren, helt eller delvis.
Jotne EPM Technology AS navn, logo og grafikkfil som representerer Programvaren skal ikke brukes på noen måte å markedsføre produkter utviklet med programvaren uten Jotne EPM Technologys godkjennelse. Jotne EPM Technology AS beholder den eneste og eksklusive eierskap til alle rettigheter, tittel og interesser i og for Programvaren og alle immaterielle rettigheter knyttet til dette.
Copyright lov og internasjonale opphavsrettstraktatbestemmelser beskytter alle deler av programvaren, produkter og tjenester. Ingen program, kode, del, bilde, eller tekst kan kopieres eller brukes på noen måte av brukeren unntatt som forutsatt innenfor rammene av programvarens naturlige bruk. Alle rettigheter som ikke uttrykkelig er gitt, er forbeholdt for Jotne EPM Technology AS.
Ansvarsfraskrivelse
Denne programvaren og tilhørende dokumentasjon leveres som den er og det gis ingen garantier for dens egnethet for et spesielt formål. Ikke under noen omstendigheter skal Jotne stilles ansvarlig for direkte eller indirekte tap eller skader, (inkludert men ikke begrenset til tap av data, tap av fortjeneste eller produksjonsstans), uansett årsak og ansvarsteori, verken som følge av bruken av denne programvaren eller av de data den produserer.
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
1 General
1.1 Abbreviations
1.2 External references
1.3 EDMmodelServer referances
2 Using the Area Calculator
2.1 Preconditions
2.2 How AC works
2.3 Storing AC results
2.4 Running Area Calculator
2.5 Handling of error situations while calculating areas
2.5.1 Overlapping IfcSpaces
2.5.2 Areas not covered by space or building element
2.6 Virtual Spaces
3 Rules for calculation
3.1 Walls
3.2 BTA for building storey
3.3 Openings
3.4 Inclined (pitched) ceilings
3.5 Columns and other "inner" elements in a space
3.6 Staircases and similar
3.6.1 Finding stair footprints
3.6.2 Area of stair itself
3.7 Stairs with irregular cut lines
3.7.1 Footprints of spiral / curved stair
3.7.2 Free form stair
3.8 Staircases and openings
3.8.1 Staircase spanning multiple storeys in an opening
3.8.2 Staircase spanning multiple storeys with floor under stair
3.8.3 Spiral staircase spanning multiple storeys
3.9 Some additional considerations
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...
Term | Norwegian | English | Kommentar |
AC | Arealkakulator | Area Calculator |
|
NTA | Nettoareal | Net Area | Ref [NS3940] [wiki] |
BTA | Bruttoareal | Gross Floor Area | Ref [NS3940] [wiki] |
KA | Konstruksjonsareal |
| Area occupied by walls, coloumns and similar. BTA = NTA + KA [wiki] |
MA (MW) | Måleverdig areal | Area Worthy of Measurement | Ref [NS3940-V] [wiki] |
iMA (NMW) | Ikke måleverdig areal | Area Not Worthy of Measurement | Ref [NS3940-V] [wiki] |
UA | Utleieareal | Gross Leasable Area | Formula: UA = BTA – iMA [NS3940]. Can also be seen as «sum of all BTA areas worthy of measurement" as described in [NS3940-V] |
pUA | Praktisert utleieareal | Applied Rentable Area | UA adjusted in accordance to agreements, local rules, tradition and similar. pUA could be a result of negotiations and can therefore not be defined mathematically. |
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Referanse | Beskrivelse |
[wiki] | https://no.wikipedia.org/wiki/Arealberegning_av_bygninger, Artikkel om klassifisering av areal |
[NS3940] | NS3940-2012 Areal- og volumberegning av bygninger |
[NS3940-V] | NS3940-2012 Veiledning for beregning av utleieareal i næringsbygg |
| http://taksteksperten.no/arealbegrep/ |
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Room (IfcSpace) |
|
Etasje (IfcBuildingStorey) |
|
Slabs (IfcSlab) |
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Base for calculation are IfcSpace geometry and not IfcWall or similar objects playing role as physical walls.
For outer walls the "Storey BTA polygon" for BTA of storey is used as limitation of "outer walls" instead of actual IfcWall instances. The BTA polygon is based on a "virtual BTA Space" that is supplied in the ArK data (CAD system). If the CAD system does not supply this space, it must be approximated by an AC component, this will impact accuracy significantly.
The produced result is not area values, but a set of polygons that defines different types of areas. The area values are calculated out of the polygons when needed. For each space and storey, the total area is composed of a set of polygons, each polygon composed of "outer" polygons representing positive contributions to the area, and a set of "inner" polygons intended for adjusting the area This is very common model and is usually called Simple Concave polygon with Holes (simplicity here means no self-intersection of edges).
.
Figure 1 Area polygons for a space
In this example UA is composed of two parts: PO1 og PO2, both of which has an "inner" polygon – a hole. The rest of the room is covered by an opening, represented by polygon O3.
The generated partial polygons are combined into composite polygons representing areas like UA, NTA etc. The rules for composing these polygons can relatively easy be adapted to national regulations and customer demands.
Generated composite polygons for UA can be edited using Polygon Editor as described in <TODO>.
The generated partial polygon types are listed in the following table:
Polygontype | Kommentar |
NTASpace | Source 2D shape of space object, obtained from corresponding space 3D geometry by CUT at floor + 10cm level. All other calculated shapes serve as addition or subtraction to this base shape. |
BTASpace | Resulting BTA area shape for a space, calculated internally in AC as NTASpace – NTAOverlap + BTAWalls, where -+ are 2D geometrical difference/union operations |
BTARentable | Resulting rentable area shape for a space, calculated internally in AC as NTASpace – NTAOverlap – BTAOpening – BTARoof190 – BTAStair190 + BTAStairBelow + BTAWalls - BTAWallsReduceForRA, where -+ are 2D geometrical difference/union operations. |
BTAOpening | Polygons representing areas within space, where floor (slab) is not found – according to spec, these areas will be removed from space. |
BTAWalls | Polygons representing parts of outer and inner walls/columns which need to be added to space according to NS to get proper BTA area for a space. In case when BTAStorey helper space is used, these areas can inlcude any parts of BTAStorey; otherwise, these areas are taken from KA (construction area) only |
BTAWallsReduceForRA | Polygons representing parts of outer and inner walls/columns which need to be subtracted from BTAWalls when calculating final BTARentable – usually due to slanted roof preventing full-height access to the wall. In case when BTAStorey helper space is used, these areas can inlcude any parts of BTAStorey; otherwise, these areas are taken from KA (construction area) only |
BTAStair190 | Polygons representing part of stair (its 2D projection on floor) which is not usable and to be removed from space. The (part of) stair should be located inside space, on current storey and have floor (slab) underneath. |
BTAStairBelow | Polygons representing area of the stair going DOWN (from current storey to the storey below) that is considered part of UA, ref section on stairs. This area should be completely inside BTAOpening. This area will be added to the space. |
NTAOverlap | Shape which need to be removed from NTASpace to eliminate any geometrical overlapping between spaces of storey. Note that space which completely overlaps (i.e. includes) any other space(s) - is just excluded from AC calculation. |
BTARoof190 | Polygons representing area of space which is unusable due to low ceiling/roof and thus should be subtracted from space. This part is calculated taking necessary 60cm correction as described in spec. |
BTAStorey | Given or calculated area for entire building storey outside external walls, |
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Calculation results are attached to the IfcSpace objects.
If space properties are used in lease contracts or similar, they cannot be changed. Hence, we must to a certain extent store both USED and CALCULATED values.
If a space is missing the BTAspace/NTAspace properties, the calculated properties can be copied directly . This is the usual case with a "new" BIM. For other situations, the transfer of calculated properties into used properties must be a managed process.
All properties are stored in the FM_Areas property set:
Property | Value Type | Comment |
BTAspace | IfcAreaMeasure | (Used) Rentable Area / Gross Areanot used anymore) |
NTAspace | IfcAreaMeasure | (Usednot used anymore) Net Area |
BTAcalculated | IfcAreaMeasure | Calculated BTARA |
NTAcalculated | IfcAreaMeasure | Calculated NTA |
OKcalculated | IfcBoolean | FALSE if Area Calculator indicates something is not correct for this space |
MSGCalculated | IfcDescriptiveMeasure | Message indicating the nature of calculation problem. |
...
- Name "FM_Areas_zzz_outer_xxx" identifies an outer polygon, where xxx is a number starting from 1 (without any particular ordering) and zzz is a polygon class (text label as in 3.1).
- Name "FM_Areas_zzz_inner_xxx_yyy" identifies an outer polygon, where yyy is a number starting from 1 (without any particular ordering) and zzz is a polygon class (text label as in 3.1) and xxx is a number of outer polygon to which this inner polygon is bound.
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...
There may exist spaces in the model that covers an entire wing, a zone or similar. Such aggregated spaces containing a lot of other spaces can be excluded from the AC process by marking them as "virtual". This can be done via report or with zoning tool. As mentioned in 3.3.1, such areas are excluded from calculations anyway, but 'virtual' mark will also remove them from result set.
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...
Figure 1 - Storey BTA polygon
Figure 2 – Walls defined by Space and BTA polygons
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...
In general, columns inside a space are not influencing the area calculation.
However, as some CAD models can create "holes" in the space geometry around columns, they can be taken into account indirectly. It is advised to make sure that no such holes are present.
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...
Text step is to add the area according to the 60cnm-rule in [NS3940-V]. Since the «cut line» C1-C2 is a straight line this is fairly straight forward:
Figur 6 – Kompensering for 60cm -regel
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Innhold
It is not as trivial as it sounds to identify "area below 1.90" under a stair. An important concept here is the "cut line" which is the common line between projected area (footprint) below 1.90 and projected area (footprint) above 1.90. For the simplest case this is a straight line. However, if the stair geometry is more complex the cut line will also be more complex. The reason for this could be as simple as a stir built as two beams bearing the foundation for the steps:
For the simplest case this is a straight line. However, if the stair geometry is more complex the cut line will also be more complex:
Figur 5 - Approximating the cut line
This approximation will probably only work if railings, fences etc is not taken into account. Until further notice, it is believed to be possible to filter these out by type.
If the stair includes railings and/or it is an open stair, the footprint becomes more complex:
Figur 6 - open stair with railings
The footprint of stair below 1.90 is lower left in figure. In this case it even contains "holes"; if these introduce problems it should be possibly to apply an algorithm to remove holes. Imposing the footprint for entire stair introduces several possibilities for points C1 and C2 and start/(en d of "cut line":
Figur 7 - footprints for symmetrical stair
As long as at least one of the C points can be found the previous algorithm should work. To ensure symmetry we can run algorithm twice, in CW and CCW directions, and pick first point found in both cases.
If it turns out to be problematic finding C points, we could apply an algorithm for making polygon convex on the stair-below-90 footprint:
Figure 8 – Apply convex footprint enclosing line
If the stair is "asymmetric" around its midpoint line, for example included railings but on only one side, the approach will not work the same way:
Figure 9 – Asymmetrical case
The line between identified points C1-1 and C2-1 are no longer a proper "cut line". TODO: Currently, a simple solution for this case is not identified. We must rely on stairs not including railings, or being symmetrical, and use C1C2 as cut line.
To enable polygon edit, and simplify the further calculation (60-cm rule), we should always perform this "cut line approximation" step.
When the "cut line" is approximated as a straight line the "60 cm rule" is rather easy to implement:
Figur 12 - Adding 60cm compensation
An acceptable and simple approximation is to create a rectangle with the cut line E1E2 as one of the sides, a parallel F1F1 as opposite side, the two other sides being 60cm in length.
There is one exception, for small curved/spiral staircases, where the compensation polygon will be a triangle version of the above: E1E2F1.
...
We might come across "free form stairs", a general approach is to "cut" the stair by bottom and top (next storey floor) and by again by 1.90 height and top, creating footprints, and analyze these in 2D. See figure below:
Figur 13 - Free form stair
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...
- In bottom storey U1 there is a floor under the stair, so rules for "staircase starting in this storey" apply.
- In the middle storeys 01 and 02 the footprint of the stair going DOWN from this storey is included in the BTA, while rest of the opening is NOT included.
- BTA = BTA0 – Op + S0p
- In top storey 03 likewise, the footprint of the stair going DOWN from this storey is included in the BTA, while rest of the opening is NOT included.
- BTA = BTA0 – Op + S0p
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...