The height and width of each element is represented by a variable expressed in terms of the objects height, width or diameter. When the object is placed, the variables that are its geometric parameters can be changed to match the object it represents in real world terms. A new set of shape rules is proposed in this section to correspond to classical architectural elements.

To accompany the new shape rules, a new parametric design for classical architecture is also presented. The parametric design includes GDL codes for original and efficient GDL codes, which develop 3D models based on the shape rules for elements of classical architecture. The parameters allow for representation of volume and angular orientation within a 3D space in addition to the specification for materials and texture. The rules of classical architecture can be described as a grammar.

Shape grammars Stiny and Gips, , introduced the concept that buildings are based on different architectural styles and can be divided and represented by sets of basic shapes which are a limited arrangement of straight lines in three-dimensional Euclidian space. These shapes are governed by replacement rules whereby a shape can be changed or replaced by transformations and deformations.

The shape commands combined with a new library of primitives, allow for all configurations of the classical orders in relation to uniform geometry. Non-uniform and organic shapes are developed in GDL through a series of procedures attempting to maximise parametric content of the objects.

These shapes are stored as individual parametric objects or combined to make larger objects in a library. When the parametric objects are used in the HBIM platform they can be transformed and deformed to match real-world requirements. In Figure 23, the additions and transformations of rectangular shapes in two dimensions illustrate the construction elements of the Doric column.

On the left hand side of the figure the rectangular elements start with column and base and increase to include pediment etc. The joining elements are the small rectangles which represent the mouldings described as the atoms of the structure De Luca, Figure Shape change Capo, 4. By starting with the design of parametric mouldings as the smallest building block, followed by the parametric design of elements such as columns, pediments, walls, windows and roofs new parametric design and shape rules are presented.

The shape and parametric design rules are the foundation in the creation of a library of elements for modelling of classical architecture. The shape rules commence with simple rectangular and circular shapes, which evolve as a result of replacement rules whereby a shape can be changed or replaced by transformations and deformations. These new shape rules are illustrated on the left hand side of Figure 24 and represented by an array of shapes a to w.

On the right hand side of the figure a profile of an Ionic entablature Chitham, is illustrated whereby the mouldings are associated with the shape rules on the left side of the figure.

Figure Shape grammar – architectural mouldings Drawing of profile of Ionic entablature on right of figure Chitham, 4. The cross-section of a moulding is represented in two dimensions by its profile.

Mouldings alongside carvings and sculpting are used as additions to walls, openings, columns and beams and conform to the classical architectural rules. These classical descriptions and geometries for mouldings can be represented by the shape rules, which are detailed in Figure 24, to facilitate their modelling within a virtual environment.

In Figure 25 and Figure 26 these new shape rules, and their evolution are applied to classical mouldings. The simplest moulding is called a band or fascia see in Figure 25a , which is a plane-projecting surface and if it is small in cross section it is described as a fillet, which can be raised or sunk, horizontal, vertical, or inclined. A convex moulding is called an ovolo, or a torus, which is illustrated in Figure 25b.

If it is a small torus is called a bead, astragal, or reed. Concave mouldings are referred to as cavetto and are illustrated in Figure 25c.

A moulding with double curvature is called a cyma; a cyma recta is illustrated in Figure 26a, and the cyma reversa is illustrated in Figure 26b. These double curvature mouldings are evolved from rectangular and segmental shapes detailed within Figure A small cyma is called a cymatium, which is placed above a band or any larger moulding. To increase the cylindrical profile quadrants, projections are introduced by the addition of straight lines as illustrated in Figure 26c.

A double concave moulding is called a scotia or three-quarter moulding and is illustrated in Figure 26d. When a convex and a concave moulding meet, instead of being tangent they come together at an angle, they constitute a beak moulding as illustrated in Figure 26e.

Rectangular or square profiles are used to mark the boundary between each different cylindrical moulding profile to emphasise the change and shape. The contour or outline of cylindrical mouldings is formed from quadrants, or segments, of circles through rotation or addition but further deformations can be introduced with elliptical, parabolic or hyperbolic shapes. An example of a deformation of a cylindrical moulding is illustrated as an elliptical quadrant moulding and is illustrated in Figure 26f.

In Figure 28, the shape rules illustrated in Figure 25 and Figure 26 are extruded to form 3D objects, which can then be combined in varied sequence to form architectural elements, as illustrated by the moulded architrave on the right hand side of Figure Figure Shape array – 3D Objects mouldings 4.

The shape and parametric rules are designed to exploit and maximise the full range of geometric parameters, deformation of shapes and abstract transformations using efficient and dynamic GDL scripts. The use of such protocols is necessary as the consistent use in naming variables allows them to be combined into compound objects allowing each component part to transform uniformly.

Variables can also provide information concerning transformations, scale, the current pen and the material settings. Parameters can be locked within a script where they are fixed or user modifiable allowing the user to change settings. When an object is built it contains a list of user modifiable parameters visible within a user interface or a dialog box, which controls the object. Parameters can be dimensions and angles, numbers and integers, materials and pens, text or fill patterns Watson, In the example in Figure 28, a semi-circular object Torus in Figure 25b is illustrated.

In the GDL script on the right hand side of Figure 28, a prism command is used to represent the objects profile and depth is used to represent its extrusion. The difficulty with this particular script is that it is very long and does not contain many variables to facilitate deformation or transformation.

The parametric design introduced in Figure 29, overcomes these problems by replacing the numeric values with poly-line codes Watson, , which represents curve values. The curve values can then be represented by variables and additional variables for the rotational value of the curve deg and the cylinder radius r. When different values are attributed for each of the variables the object is transformed and can represent an array of convex, concave and double curvature objects as detailed in Figure In the GDL script in Figure 30, a command is used to revolve the object to form the cylinder or column shaft.

The diameter of the base of the column is represented by the cylinder radius r1 allowing the moulding to deform in proportion to the column and other elements. The radius of the moulding profile r2 can vary depending on the profile geometry and negative values can be inserted to change from convex to concave profiles. As before poly-lines are used in the code to establish the construction of the curve in the profile, these can be radius, tangent or point and angle based syntax.

In addition numeric codes represent masking values for the surfaces Watson, Figure Shape array circular mouldings A Doric column is represented in Figure 32, using coordinate transformations the primitives are stacked on the Z-axis or alternatively moved on the x and y-axis to form the column see a, b and c.

In the exploded Figure 32b, a cylinder represents the base of the column followed by the appropriate series of mouldings.

The mouldings are detailed from the pattern books and transformed from shapes in Figure 32a, on the left hand side of the figure. A cylinder and a cone are added on the z-axis to represent the column shaft the cone represents the tapering of the column one third up the shaft.

These primitives are combined with the primitives in Figure 32a on the left side of the figure to form the column with its mouldings. The variables used to represent each value for the primitives are expressed in terms of the base diameter of the column, for example the r1 is equal to the half the diameter of the column base. A series of conical shapes can be used to represent further deformations in the column shaft to represent column enthasis, which is a gradual deformation of the conical section of the column shaft.

Figure Doric column The Doric Entablature above the column shaft, which is illustrated in Figure 33, has decorated cornices, friezes and architraves, which are developed using the shape rules in Figure 25 and Figure All of the primitives and mouldings are combined into a compound object, in this case a Doric column and entablature. Additional transformations can re-scale the subsequent whole or parts of shapes or rotate the object around any of its axes. When the object is placed, the variables and parameters can be changed to match the object it represents in real world terms; other common parameters are formation level and rotational transformations.

The components or objects are placed in libraries or databases; the use of flow control, macros, subroutines and loops can re-introduce these objects in repetition or revised state partially illustrated in Figure 33b. Figure Doric column and entablature 4. Figure 34, below illustrates a method for the construction of the Ionic volute of the capital of the Ionic columns. The volute is constituted of twelve quarter-circles, the centres of which are situated inside the eye. These centres are inscribed along the diagonal of a square that is placed within a larger square and rotated 45 degrees.

The eye of the volute is placed in the inner square. The diagonals of the inner square are divided into six equal parts, resulting in the identification of a total of twelve points. The centres of the respective quarter-circles are numbered progressively from 1 to 12 clockwise from the exterior to the interior. The point of the compass moves each time to the next successive centre.

The left drawing in is attributed to Batty Langley and the right is the drawing from Andrey and Galli Langley and Langley, , Andrey and Galli, Meshing was then used to add the irregular depth of the leaf. Group and solid Boolean operations were used to create the bend in the leaf around the column and the bend at the top of the leaf, which is illustrated in Figure 36b. The object is bent in two directions by intersecting the two objects and the intersection results in the creation of leaf illustrated in Figure 36c.

The range of parameters attributed to the Acanthus leaf is limited to its bounding box i. Finally the leaf is repeated to match the columns diameter through a looping procedure as shown in detail d and stacked with additional ornament to form the Corinthian capital see Appendix A21 to A A large amount of the original elements of Georgian buildings are still in place and date back to the early eighteenth century or have evolved with additions over the centuries Innocent, Because of the variation in size, texture, bonding, pointing and condition GDL models cannot compete with the laser survey detail.

The external walls in Georgian buildings in Dublin are mainly constructed in brick and laid in a Flemish Bond using a mortar mix of lime and sand. Flemish and English bonds were the principle bonds used in 17th and 18th centuries. The bricks vary in size because they were handmade. A sample of brick dimensions measured from the scan survey indicate an average size of nine inches in length and two and one half inches high, although.

The colours of bricks varied from red, purple, or grey in the late 17th century and up until the early s, imported brick from Holland was grey in colour Lynch, , Nicholson, , Roundtrees, ,. These observations are presented to assist in developing a protocol for representation of external building fabric. Samples of laser scan products such as textured point-cloud or ortho-image are illustrated in Figure 37 below.

Orthographic textured point clouds can therefore represent the external brick fabric. The first image in Figure 37a, is a dense point cloud from which it is not feasible to abstract brickwork dimensions. The second scan in Figure 37b illustrates a textured point cloud whereby bonding, texture and pointing details can be observed and measured.

The parametric design for size and position of openings can be developed from rules of proportion outlined in the pattern books. The top windows are made up of a single circle, in the next set of windows intersecting circles and finally in the lower set of windows the circles are placed one on top of each other.

The height of the opening dictates the angle of the brickwork head Langley, a. The construction of the golden section Fletcher, , Frings, , a geometric proportion used in classical architecture can determine bay widths. The golden mean or golden section is illustrated in figure 39c. The section is formed initially by constructing a square, inscribing a circle from the centre of one of the sides of the square, side A is extended by the distance B to meet the tangent, and the rectangle is completed.

The rectangle represents the golden section and is represented as red lines in Figure 38e. The vertical distance between window openings are usually asymmetrical with the diameter of the circle d1, as shown in 19d.

The application of proportional rules assist in representing the facade as a GDL object allowing for a parametric design to include for variables in opening sizes and their relative positions. The alterations to the facades can include removal or enlarging of brick walls, window and door openings and parapets.

Two variables are introduced, the width of the window based on the diameter of a circle and the distance between the windows which is also dependent on the diameter of the circle. A series of openings are established using a GDL script for cutting the openings in the wall panel. The openings are laid out according to the proportions illustrated in Figure 38d and Figure 38e. The golden section is not taken into account in the shape rules in this instance.

The single panels can be adjusted for any opening size or distance between openings. A sample code is illustrated in Figure 39b of a single opening panel which can be placed in any position and will cut an opening in a solid wall panel see Appendix A36 to 45 for GDL code. Calp, a local limestone, is used in the walls to some of the basements and is mainly covered with a render. Local granite is used in plinths, cornices, steps, cills and copings.

Imported Portland stone is used in the construction of more complicated mouldings and carvings associated with door cases, porticos and architraves around openings etc. Local sandstone is also used to a lesser extent for intricacies in carved work for the later elements Lewis, Stone shapes are much larger and better defined than brickwork and can more easily be represented as 3D models using GDL. An arrangement of stone shapes is illustrated in Figure 40 to create a composite wall with an arched opening.

A semi-circular object is subtracted using solid element operations from a larger block which represents a wall shape.

Ashlar stone is represented using an array of block shapes; plinth and corbels are then combined with the other objects to create the final composite object see Appendix pages A53 to 54 for GDL code. The sliding sash window was preceded by hinged casement windows. Original earlyth construction methods used for sash windows exposed the timber boxes in which sashes were held. A sectional detail of the timber boxes is detailed Figure 41b.

In addition no reveal was included as the windows were often flush with the brick- work Innocent, Building regulation in Ireland in changed this practice, stating that the window had to be set back from the facade by at least four inches.

The early sash windows tended to be smaller, in line with Palladian principles, whereby the window cill was level with the dado rail. The different glazing arrangements of the sash window is illustrated in Figure 41c, Roche, Rivington, A typical 18th profile of a glazing bar profile sash frame is detailed in Figure 41a. A model of part of a semi-circular Venetian window Langley, a is illustrated in Figure 41d.

The centrepiece is usually accompanied by two sidelights not shown in this detail and is framed by ionic pilasters. This Venetian window is constructed using sash frames and appears in many Georgian buildings usually in isolation to the rectangular sash windows that form the main bays of the building facades.

Finally in Figure 41e to f, arrangements are detailed of a typical stone architrave surround to a sash window. The Doric and Ionic orders in the door cases represent complex GDL objects, which are an ensemble of the mouldings, and primitives that illustrate the shape rules and parametric design presented in this chapter Langley, a, Langley, , Halfpenny et al. Many of the original stone entablatures and pediments disappeared when neoclassical styles were introduced in the late 18th Century.

Sidelights and plaster enrichments were included around the fanlight O Neill, a, O Neill, b. The oak was replaced by imported Baltic pine and was used in a more economical fashion with lower pitches constructed usually as triple roofs with rafters, collars, ties, struts and purlins as detailed in detail c Innocent, , Rivington, , Nicholson, The roof coverings consisted of slate fixed onto battens in gable or hipped roof construction.

A series of shape arrangements for roof forms are laid out in Figure Meshing and mass commands in GDL allow for the introduction of height in addition to width and depth Watson, The object is raised at Z2, Z3 and Z4 to represent a half gable roof.

Bending is introduced by bringing Z4 back down to zero and a hip roof shape is formed. Figure Shape rules for roof construction In Figure 43a, b, c, d and e, the arrangement of components for a typical 18th century timber roof carcass is detailed.

The geometry for each component ceiling, joist, strut, ridge board etc. The arrangement for different configurations of roof covering is detailed in Figure 44i. This includes pitched f , hipped g and valley geometry h , which again is based on half the roof span and the pitch of the roof.

Different configurations of the roof carcass and covering can be constructed by changing variables of roof geometry. In Figure 45, the rules of classical architecture are illustrated in two examples of an ensemble of the classical orders. An arrangement for an Ionic colonnade and dome roof is detailed in 45b see pages A80 to The mapping process for plotting parametric objects onto laser scan survey data which is the next stage of HBIM, is detailed in the next chapter. The laser scan survey data can be considered as a skeletal framework, which is then mapped using parametric architectural elements to form the HBIM.

Three case studies are presented in this chapter to illustrate this mapping process. The three case studies presented in this chapter represent the design and evolutionary stages of the HBIM mapping process.

The addition of a web-based photo-scaling application for extracting numeric measurement data is presented as an outcome of the testing of HBIM. The testing of HBIM is presented in the following chapter to this one. Finally, in this chapter a series of examples illustrate the automation of conservation documentation from HBIM.

This data is imported in image and vector format for further processing within the HBIM platform. The point cloud is segmented to supply plans, elevations and sectional cuts for mapping of library objects. Further interrogation of the laser scan survey data supplies numeric values for parametric values for the library objects themselves. A project co-ordinate system was established by identifying a temporary benchmark 0, 0, 0 at ground level, located at a recognised point on the laser scan survey.

The formation level was set along this point horizontally on the x-axis. Formation levels can then be set for each story level at a central point between the window openings and horizontally along the x-axis see Step1 – Figure Step2 — Extracting measurements from the ortho-image The dimensions of the wall height, width and length were calculated from the ortho- image.

Co-ordinates x,y values are recorded using hotspots markers placed on the image that were then used to calculate length or angular values see GDL script in Figure A wall is normally defined by its parameters height, width and thickness and its position in a co-ordinate system relative to other objects.

The height of the wall can also be defined by its formation level at each story level and finishing level roof. The wall can be plotted for each story level, but in this case the wall was plotted from ground level to roof level. The thickness of the wall will depend on its composite construction. The materials and techniques that make up the wall construction can be determined from the ortho-image data. In this case the bonding of the brickwork is Flemish bond, which assists in the identification of the composite structure of the wall.

Based on this information, two and a half brick measuring mm was assumed as the wall thickness Nicholson, Step3 — Modelling the 3D wall The length and thickness of the wall was then positioned on plan and the dimensions of the object were inserted in a dialogue box, shown in Figure Step3.

The formation level, which in this case is zero, is inserted in the dialogue box to form the 3D wall. The other parameters such as texture, sectional fill details and other numeric and descriptive data can also be entered in the dialogue box for the wall.

The level of information requested regarding the objects parameters depends on the specifications in the original GDL script. Finally the 3D wall is represented in Figure 46 —Step3. The numeric data required for plotting and sizing the window and openings was extracted from the laser scan survey as an initial procedure.

By placing a marker on the points A, B, and C onto the orto-image detailed in Figure 47a , the x and y coordinates for each point were calculated. The lengths and formation levels were then obtained for the required parameters of the window and placed in a data sheets. Other parameters can then be calculated from the x and y coordinates such as angular values and distance between objects. The window openings as objects see GDL script in Figure 39 are positioned on plan on each story or on elevation as detailed in Figure 47c below.

The completed 3D model of the wall with openings is detailed in Figure 47d below. The sash windows as objects see page A65 in Appendix A for GDL script are plotted into position onto plan and elevation as detailed in Figure 48a and b.

The red vector lines in Figure 48b represent the window position in plan, based on the laser scan segmented survey data vector format. In Figure 49 a view of the window in 3D is detailed also showing the dialogue box for the window for fixing parameters.

Finally in Figure 50, the 3D model for the wall with openings and sash windows is illustrated. Historically door cases were copied from the pattern books and represent a re-production of the classical orders.

Consequently it is an ideal example to illustrate the building of a parametric object from laser survey data and the additional input of pattern book detail to augment the laser survey data. He does not however show detail of the regulae and rosette see Figure 51f this detail is taken from Langley Langley, The Classical proportioning which is used is based on a series of modular relationships based on the diameter of the base of the column.

In Figure 51a, detail 1 sets out the modular relationship, which are all based on one module 1M , which represents the diameter of the base of the column.

The pediment is made up of the entablature in the centre placed on the capital of the column supporting it and two raked cornices over the entablature. The Doric entablature is 2 modules high and is made up of the cornice, which is 0. Finally the raking cornice, which is constructed over the entablature, is 0. In Figure 51 below, a number of the objects are illustrated mapped onto the ortho-image on the left.

On the right of Figure 51, the objects are shown in the 3D model. The pattern books alongside the laser survey data see Figure 51e and f and Figure 52 are used to build the model of the pediment and establish the parameters of the main objects. The objects which make up the Doric pediment are the trigliphs see Figure 51b , cornice see Figure 51c , frieze see Figure 51d , the regulae and rosette see Figure 51e , and the architrave see Figure 51f.

The measurements for plotting the door case are extracted from this laser scan survey data as detailed previously on pages 91 to This data is combined with detail from the pattern books to model the door case. Figure Survey data for door case Step2 – Mapping columns from generic library objects In Figure 53a, the Doric column is mapped onto laser scan survey data as composite element.

The use of generic columns which allow for configuration of main geometric parameters dealing with height and diameter speeds up the mapping process. While this appears more efficient, conflicts will arise in arranging sub-elements and matching geometry between the survey data and that of the generic column. Step2A — Alternative to Step2 – Mapping columns from moulding geometry To overcome conflicts which occur between the geometry of the survey data and the generic GDL column object, the laser survey data is mapped using a series of cylindrical primitive parametric objects as detailed in Figure 53b.

The primitive mouldings are deformed for different geometric scenarios see examples in 53c. The objects are arranged to form the column base as detailed in Figure 53d. Interpretations from the pattern books Figure 53b detail 3 were then used to assist the mapping process. The remaining parametric objects, which make up the Doric column, which include the capital and shaft, were built up in a similar fashion to the base. The 3D model of the door case is detailed in Figure 53e. Figure Plotting columns, door case and pediment 5.

Additional historic data, such as the identities of builders and architects, assist in identifying the sequence of construction of the street. For example, Edward Lovett Pearce, who was one of the most prominent designers in Dublin in the early s, is accredited with the design of numbers 9 and 10 Henrietta Street. Pearce studied Renaissance manuscripts and in particular the Palladian styles that were popular in the early s in Ireland and Great Britain, and subsequently this influenced his designs for Henrietta Street Craig, There are no surviving design drawings for Henrietta Street.

The roof covering is black slates laid on hipped and gabled roofs. Some of the original elements of the buildings are still in place and date back to about at the earliest, or have evolved with additions over the centuries.

The terraces of Henrietta Street were laid out with basement areas bounded by wrought iron railings. In the 19th century, cast-iron balconies were applied to facades and wrought iron grilles guarded basement windows and fanlight windows. Setts Square block cobbles developed from cobbles are laid on the street and granite paving is laid on the footpaths and granite up-stands under the railings.

In Figure 54 the external structure, fabric and architectural elements of no 3 Henrietta Street were mapped. Detail a, represents the hipped and gable roof which is located in place on the external walls. Detail c, shows windows and door case and bounding railings mapped in position. In Figure 55a, the road is constructed directly from the point cloud by meshing and surfacing the point cloud data and introducing the mesh as an object into the street model.

The partially constructed model in Figure 55b consists of the repetitive terraced buildings, which can be modelled using standard facades as objects. Additional buildings were added to the model at both top ends of the street.

These buildings were modelled separately and were introduced into the model as objects as detailed in figure 55c and d. From a plug-in library, parametric objects representing architectural elements are plotted onto the laser survey data.

The parameters for objects are extracted as numeric data from the ortho-image and segmented point cloud data. The objects are then manually positioned onto the segmented plan and orthographic image in elevation and adjusted in side elevation and section using segmented data for angular displacement.

The image and segmented datasets represent the information for a particular plane on the x, y, and z-axis. The planes on x, y, and z-axis can therefore represent elevation, plan, or section of an object. When a library part or parametric object is placed into the HBIM, it is placed as an icon in 2D in the floor plan, separated by height or formation levels and is located along the x and y-axis. In section and in elevation, the object is positioned in relation to the z- axis relative to the x and y-axis.

The appropriate survey data are described in chapter 2 as segmented point cloud, structured mesh data and orthographic image data. The laser scan data provides a survey framework, which is then, mapped using parametric architectural elements to form the HBIM.

The library of parametric objects is designed as a plug-in for existing software platform Graphisoft ArchiCAD. The experiences of testing the HBIM this detailed in the next chapter in pilot case studies have identified the requirement for numeric data to accompany the segmented point cloud and image data. In this section an improvement is proposed for mapping objects onto the laser scan survey framework in relation to the extracting of parametric information from the laser survey data.

The previous case studies illustrate the different possibilities for plotting library objects onto a range of survey frameworks. A more robust system is required for the plotting stages of HBIM, which will accelerate the mapping process. This improved system can be introduced by semi-automatically supplying numeric and measurement data for adjusting the parameters and plotting the objects to establish the model.

The application is easy to access and portable and can be used on any operating system and browser and independent of commercial software platforms. The photo-scaling application is a web- based application and its design will allow for extending the application to work on mobile devices.

The application is used for measuring distances and angles between points using two-dimensional orthographical images and pixel based segmented point cloud data. The application is developed using Ruby on Rails which is an open source web framework RubyonRails, and Javascript JavaScript, A sample of the code for the application is detailed in Figure When the user uploads an image it is displayed on screen with a size of by pixels.

This scale is used irrespective of the original scale of the image, this way a standard distance between each pixel is maintained. Once the image is uploaded and displayed the user is asked to begin selecting two points. These first two points are control points, which are predetermined distances, based on real world measurements for the object. To mark the point on the image, which the user selects, a HTML div division is overlaid on that particular point with the size of 1 pixel.

Using JavaScript in this way the correct values will be determined regardless of the users screen resolution or, for example, if the browser is set to a certain zoom level. The code sample in Figure 56 below locates the current x and y position when the point is located on the image. The offset. Similarly the offset. A user enters a control measurement or known distance of x metres and the distance between the two pixels on screen is p, 1 metre on the screen is equal to p divided by x.

This value is stored then for the uploaded image and can be edited by the user at a later time if needed. The users can then select more points on screen; for each distance in pixels that is calculated the distance in metres is retuned.

Once these points have been selected the formula below is applied to get distance between the two coordinate points. Detail a, represents the variables that define the location of an opening these are illustrated in the vector diagram in the centre. The variable consist of the size of the opening and the distance of the opening from other objects in this case other openings. The GDL script is illustrated in detail b, which generates the single panel in detail c.

The panel can then be repeated to form the full panel in detail d. The GDL scripts for different arrangements of openings, stone cladding and architrave surround for wall panels are detailed in full on pages A35 to A57 in Appendix A. The visualisation of objects is achieved through viewing 2D and 3D features, plans, sections, elevations and 3D views Aouad and Lee, , Eastman, Where conservation or restoration work is to be carried out on an object or structure, conventional orthographic or 3D survey engineering drawings are required.

To a large extent current research concerning automated surveying systems for cultural heritage objects has concentrated on the identification of suitable hardware and software systems for the collection and processing of data.

As a result, the output is the accurate 3D model mainly suitable for visualisation of a historic structure or artefact. The objects in this case are historic structures brought through the design process in the opposite direction, revealing information about the original design and construction.

A sample of street elevation drawings are illustrated in Figure 59a, b, and d. In addition typical section and elevation details are shown in Figure 59d, e and f. Finally in Figure in figure 59g a partial 3D drawing is produced of the street.

Similarly in Figure 60 a set of plan, elevation and section drawings are detailed. The 3D drawings detailed in Figure 60c and d are described as 3D documentation, in this instance showing cuts between wall, floor and windows. Finally window schedules are automatically produced as part of HBIM process. Mapping the objects directly onto the point cloud, is not practical as the data size of the point cloud is large which will slow down data processing.

The proposed solution is to map the objects in 2D onto segmented point clouds and orthographic images in elevation, plan and section. A more robust system has been developed for the plotting stages of HBIM.

One of the main features of this system is a web-based application for semi-automatically supplying numeric and measurement data for adjusting the parameters and plotting the objects to establish the HBIM.

The first evaluation is an end-user test of the software and the second a qualitative assessment of documentation generated using HBIM. An explanation of scenario testing followed by a definition of conservation documentation is presented initially in this chapter. Conservation documentation is an outcome of the HBIM process and features in both evaluations. The procedures, findings and analysis and review of both evaluations, which are the end user test and the qualitative assessments of documentation, are then presented.

In addition, a data sample of HBIM documentation is compared with related ground truth data to assess accuracy. Conventional software design and evaluation methods can be carried out through tasks described by fictional applications to evaluate end user requirements as proposed in scenario-based design Carroll, The fictional applications for the software are established through the use of credible stories, which then identify problems and the potential for improvements in the software.

Because of the diversity and complexity of architectural conservation projects, simulated conservation scenarios were used to represent an example of this diversity in order to evaluate HBIM. The process began by constructing or developing alternative scenarios and then integrating the context of those scenarios into constructing a Historic Building Information Model related to the laser scanning survey of Henrietta Street. In addition to developing the fictional applications, discussion and dialogue with the test participants created a continual input resulting in on-going review and revision of the software design.

The purpose of documentation is to enable through the supply of accurate information the correct conservation, monitoring and maintenance for the survival of an artefact Fai et al. Every stage of the work of cleaning, consolidation, rearrangement and integration, as well as technical and formal features identified during the course of the work, should be included.

This record should be placed in the archives of a public institution and made accessible to research workers. Suitable models for appropriate standards for recording and documenting historic structures are detailed in national guidelines such as the Historic American Building Surveys and English Heritage Metric Survey Practice Bryan et al.

At an international level recording standards have been established by the International Council on Monuments and Sites ICOMOS , which is, an international non-governmental organisation of professionals, committed to the conservation of the world’s historic monuments and sites ICOMOS, a.

Its main purpose is the improvement of all methods for surveying of cultural monuments and sites. The work of CIPA has been instrumental in developing new automated methods of digital recording and storage in addition to the standards required for accuracy of surveying and documentation of the built heritage. RecorDim is a CIPA initiative in collaboration with other international heritage conservation organisations to improve and develop standards for the documentation of architectural heritage CIPA, They propose a system using a series of case studies to exploit the object intelligence within BIM to archive and present both tangible and intangible cultural assets Fai et al.

The European Committee for Standardization CEN provides for European standards and technical specifications in almost all areas of economic activity. The participants were all male and ranged in age from 19 years to 35 years. A series of three training workshops were held with the group to train them in the application and use of HBIM and 3D CAD as outlined in the scenario above. In total twenty-six students attended the training workshops and fourteen volunteered to participate in the scenario test.

The participants were required to produce a set of conservation documents, to include plans, elevation, cut sections, window details and schedules in addition to 3D documentation. The scenario tests were held after the training workshops in a computer laboratory in the Dublin Institute of Technology. The participants constructed the model over four two-hour sessions using identical software platforms and under supervision.

At the end of the exercise the participants were interviewed and completed an online questionnaire. These are illustrated in Figure The ortho-image is illustrated in Figure 61a, the vector data showing positions of openings is illustrated in Figure 61b. The dimensions and formation levels for the library a sample of library objects windows are detailed in Figure 61c.

The library objects supplied for the scenario exercise included window and door wall openings, sash widow including all components for each opening size and a Doric door case as a composite library object. Finally, the sequence for plotting the 3D model illustrated in Figure 61e.

In the following part of the test, the users were asked to assess the efficiency of each of the plotting stages for creating the model based on the laser scan survey data. The survey data for plotting the 3D model in HBIM consists of a range of data; these are Ortho — Image, Vector plot, Data sheets containing numeric data and a combination of all of these.

The reason for associating error with the ortho-image is because of possibility of incorrect scaling of the image data when it is imported into HBIM.

This problem can be overcome by embedding measurements or coordinates within the ortho-image, which are verified before the image data is used. In addition, measurements and angular values can be extracted directly from both ortho-image and vector data and then stored independently in data sheets. The library object for the opening was rectangular in shape. The majority of the users see right hand side of Figure 68 indicated that HBIM could produce the full list of automated documents.

A small minority did not include the production of scheduling from HBIM, whereas they indicated that 3D CAD was capable of automating a much smaller range of conservation documentation as detailed on left-hand side of Figure 68 below. The advantages of the HBIM system become evident in the last section of the user test in relation to the quality of documentation and the behaviour of the library objects in HBIM.

It is obvious that objects within HBIM contain a vast number of parameters ranging from geometry and texture to conservation analysis and that not all of these designed parameters will function in a 3D CAD environment.

The introduction of an additional help and learning centre for HBIM can improve ease of working in HBIM, reducing the effort in time to use and learn the software. The problems associated in extracting measurements to size library objects were overcome by introducing the specialised WEB based ortho-photo scaling application detailed in Chapter 5.

The application was developed as a result of the issues that were raised in the end user tests and is specifically designed to operate outside of the BIM environment. Improving texture options for objects can be achieved by applying the colour and texture from ortho-images.

The image is matched with the 3D object and edited by cutting out openings leaving only wall texture. Figure Texturing objects Introducing improvements in the range of object parameters and the plotting of the objects onto the survey data can be achieved using standard coding protocols for each library object. The improvements for scaling, rotation and anchor points will be included as a template in coding all objects. In Table 3 below, solutions are summarised for resolving the potential for errors occurring in the system.

Importation of the Incorrect scaling of Imbedded measurement laser survey data into orto-images data onto ortho-image HBIM and possible causes of error 2. Calculating Errors in extracting Use specialised WEB WEB based ortho- parameters and sizing measurements from based ortho-photo photo scaling of library objects imported survey scaling application for application was data within HBIM extracting measurements developed from end user testing 3. Improving objects No parameters for Re-code object for parameters creating irregular creating openings in openings walls No realistic texturing Use ortho-image from options for surfaces laser scan survey to texture objects 4.

The seminars were held in October , October and November Each seminar consisted of a series of presentations from experts in laser scanning, BIM and the recording of historic structures.

The participants who attended the seminars were practitioners and researchers from architectural conservation and surveying. In order to draw on the experience of the seminar participants for the development of HBIM, a consultative expert group were identified from the seminar participants. The consultative expert group who agreed to participate consisted of: 1. An engineer specialising in existing structures, who was familiar with the use of BIM models for assessing existing structures; 3.

A general practice conservation surveyor who was one of the authors of the conservation plan for Henrietta Street which was funded by Dublin City Council. A full time researcher in the Dublin Institute of Technology in the area of laser scanning and the recording of historic structures. The group consisted of three males and one female between the ages of 22 and In this evaluation a sample set of conservation documentation is produced using HBIM; the documentation is based on conservation scenarios.

The conservation expert group became familiar with the HBIM process through the series of seminars described on the previous page. A number of meetings were organised with the expert group, in order to develop the context and content of the conservation scenarios.

This comprised of identifying key conservation problems and translating them into the scenarios. The second scenario was constructed around the conservation of the historic facade, the windows and the door case of number 3 Henrietta Street. A wider range of conservation documentation was therefore required to complete the exercise. The documents consist of a sample of location drawings, survey data, 3D models, orthographic drawings and schedules produced as a result of scenario 2.

Their opinion was, in general that, in contrast to conventional 3D CAD, HBIM produces a wider set of conservation documentation containing information related to geometry, building detail, geographical information, details of materials and other numerical data or schedules relating to the historic structure. They all agreed that the conservation documentation could be automatically extracted to assist with solutions for the different conservation scenarios.

They also concurred that the analysis based on the HBIM documentation can produce the following information; visualisation models, survey data, building details, specifications and information sharing.

In particular, they identified the advantage of using the 3D models as a cost effective method for simulation of conservation interventions. The overall agreement amongst the conservation experts for the second scenario indicated that the documentation produced provided correct detail for completing the outlined conservation scenario. The question of dissatisfaction related to the need for national standards in Ireland for producing conservation documentation using new technologies.

Although it was agreed by the group that the standards produced by English Heritage Bryan et al. The average error between the total station measurements and plot A was 0. The average error between the total station and plot B was 0. In plot B the error on the x-axis was 8mm and 18mm on the y- axis, English Heritage recommend a precision of 15mm for a similar structure.

The first plot A did not compare as favourable showing an average error of 24 mm on the y-axis and an average of 13mm on the x-axis. Table 8: Density of point cloud and measurement precision Bryan et al. Errors can also be caused by point definition, which is obstructed by decay of materials at edges. Defining the points using intersecting vectors on the ortho-image can assist the accuracy of point location.

In Figure 71, below, the base of a Doric column is illustrated. In the ortho-image, the definition of the elements, which make up the base of the column are obscured because of both decay and occlusions. Other image data and detail from historic data are introduced to define the missing data and build up the base of the column as detailed in Figure 71a. The approach identified improvements in the use of the software through end-user testing and a qualitative evaluation through a discussion and dialogue amongst an expert group.

If there is a change location of duct for example during construction, the contractor will make the changes and communicate the changes with the designers. In those issues are reflected in 93 percent of their claims. This is not to suggest that actual design work is less important in managing risk today but that the internal processes a firm uses to support the design are having a greater impact on claim frequency. It is a reasonable assumption that unless internal processes are properly aligned with the use of BIM enabled technologies then participants will fall prey to the same problems that plague our industry now.

The technology will not be the reason, but rather the way we use the technology will have a greater impact if we are already prone to be laxed in the four main risk drivers already. In that rate grew to 37 percent. This will help owners define the most appropriate uses for BIM within their own organization along with identifying the services that they should procure to gain benefit within the design and construction processes.

This should be established. Develop a clear and comprehensive scope of work related to the use of BIM that is linked to the clients project expectations. This may mean that BIM has a very specific and possibly limited role depending on the scope of work and services to be provided.

Identify BIM contract requirements before any modeling work commences. Issues that are important to include within the owner’s contracts with service providers should be identified and categorized so that the owner can more easily develop BIM related contract requirements 2. Develop the BxP and outline to the client roles and responsibilities If a contractor is involved CM, IPD, etc then the entire team will need to share their agreements to make sure they have filled gaps around BIM usage.

If a client is a risk in this area then their lack of knowledge of BIM will only compound problems. Get an accurate picture of the client s experience in the project type and assess how BIM will be used. Clients need to understand that the complexity of design and construction has materially changed in the last 10 years and will change immensely as BIM is employed by the entire AEC industry. In addition, design error is the claim trigger with MEPs 63 percent of the time, the highest of all disciplines.

Training and continuing education on BIM related issues and usage becomes increasingly more important. Match the BIM technical aspects of the project with the knowledge and abilities of the staff in the same way they would assign a seasoned architect, engineer or technologist to deal with building envelope or similar complex issues.

Not assign staff just because they re available or underutilized. A Identify staff that have proven BIM capabilities to be more strategic and closely aligned with the expected project outcomes.

In addition, there is the human factor – the main problem of communication in the AEC community lies in the lack of stakeholders ability to empathize with the other parties involved v. AE s should: Clearly define the level of Development LOD ev and the level of detail LOD et expected of all the participants and embed these in the BxP Have clearly understood BIM processes that focus on the deliverables and having the BIM Manager communicate this to the entire team Recognize that a schedule for the design and construction deliverables is as important as the overall construction schedule.

There is a close correlation between the processes of developing the building virtually and that of the reality in construction. Keep the owner and contractor if on the team involved in the progress.

Create a culture that brings bad news into the open as soon as it s discovered and then deals with the issue quickly and correctly documenting the outcomes and communicating these amongst the teams Hold virtual coordination sessions to resolve conflicts. Staff access to BIM project data held on the network servers shall be through controlled access permissions. Whether it is output to 2D CAD for subsequent drawing production or output for 3D visualisation or analysis, the preparation and methods adopted to compose the BIM will ultimately determine its successful application within other software packages and technologies.

The suitability of incoming data shall be confirmed prior to making it available project-wide through the project Shared area. Modifications shall only be carried out with the approval of the person responsible for co-ordination. Data shall be cleansed prior to importing, referencing or linking to the main model to remove any irrelevant or extraneous data that is not approved. CAD data may need be shifted to 0,0,0 prior to import.

Ownership of this cleansed data is transferred from the originator to the cleansing discipline. Cleansed data is stored within the discipline s WIP area unless deemed appropriate to share project-wide, in which case it is stored in the Shared area. Where the BIM is required to deliver all of these purposes, the Project BIM Execution Plan needs to define at which stages of work and for which packages these purposes will be delivered.

BIM data shall be prepared, checked and exchanged taking into account the requirements of any recipient software applications, to ensure that error free, reliable data is exchanged e.

Example: When modelling structural frames, some analysis software may dictate that columns need to be stopped at each floor level regardless of whether, in reality they continue as a single length. The appropriate export layer tables shall be used during export to CAD. This section deals with the principles of subdividing a model for the purposes of: multi-user access, operational efficiency on large projects, Inter-disciplinary collaboration.

The following practices shall be followed: The methods adopted for data segregation shall take into account, and be agreed by, all internal and external disciplines to be involved in the modelling. No more than one building shall be modelled in a single file.

Further segregation of the geometry may be required to ensure that model files remain workable on available hardware. In order to avoid duplication or co-ordination errors, clear definition of the data ownership throughout the life of the project shall be defined and documented.

Element ownership may transfer during the project time-line this shall be explicitly identified in the Project BIM Execution Plan Document. Construction joints such as podium and tower. Work packages and phases of work. Document sets Work allocation such as core, shell and interiors. Properly utilised, division of a model can significantly improve efficiency and effectiveness on projects of any size, but in particular multi-user projects.

Appropriate model divisions shall be established and elements assigned, either individually or by category, location, task allocation, etc. Division shall be determined by the lead designer in conjunction with the person responsible for co-ordination.

To improve hardware performance only the required models should be opened. A project shall be broken into a sufficient number of models to avoid congestion in workflow.

Where required, access permissions and model ownership shall be managed to avoid accidental or intentional misuse of the data. In normal circumstances this period should be at least once per hour. Users shall not save without consideration for and resolution of any issues which arise to avoid delays to other team members. This may be either other parts of a project which are too big to manage in a single file, or data from another discipline or external company.

Some projects require that models of single buildings are split into multiple files and linked back together in order to maintain manageable model file size. In some large projects it is possible that all the linked models may never be brought together as one. Various container files will exist to bring model files together for different purposes. Task allocation shall be considered when dividing the model so as to minimise the need for users to switch between models.

When referencing, the models must be positioned relative to the agreed project origin: – The real-world co-ordinates of a point on the project shall be defined and coordinated in all models, – The relationship between True North and Project North is correctly established Inter-Disciplinary Referencing Each separate discipline involved in a project, whether internal or external, shall have its own model and is responsible for the contents of that model.

A discipline can reference another discipline s Shared model for coordination. Agreed project coordinates and direction of North shall be agreed and documented at the outset. Each discipline shall be conscious that referenced data has been produced from the perspective of the author and may not be modelled to the required specification for other purposes.

In this case, all relevant parties shall convene to discuss the potential re-allocation of ownership. Should a team develop a starter model for a partner discipline, such as defining the structural model in conjunction with the architecture, this shall be done in a separate model which can then be referenced as required to allow development of the continued design. With models produced for Building Services, several disciplines may be collated in a single model, as a single piece of equipment may require connection to various services.

In this scenario, the model may be split in various ways. Concept Grade 1 – see Graded Component Creation elements shall be used to form categorised place-holders in the model.

As the design develops, and precise materials and components are chosen, data will be added to the objects. These concept objects can be swapped, individually or en-masse, for more specific Grade 2 or Grade 3 variants should a higher level of modelling detail be required. For structural components, indicative members which are representative of steel or concrete elements shall be used. The frame shall be constructed from these placeholders.

If the section size is known from an early stage it can be chosen from the libraries, but no assumptions shall be made by opting for a default section. Model initially created using concept grade components. Concept components substituted for Grade 2 or 3 components as design progresses. The graphical appearance is completely independent to the metadata included in the object.

For example, it is possible to have a Grade 1 Concept object with full manufacturer s data, cost and specification attached. This is particularly relevant to electrical symbols which may never exist as a 3D object. Component Grade 1 G1 Concept Simple place-holder with absolute minimum level detail to be identifiable, e.

Superficial dimensional representation. Created from consistent material: either Concept White or Concept Glazing. Component Grade 2 G2 Defined Contains relevant metadata and technical information, and is sufficiently modelled to identify type and component materials. Typically contains level of 2D detail suitable for the preferred scale.

Sufficient for most projects. Component Grade 3 G3 Rendered Identical to the Grade 2 version if scheduled or interrogated by annotation.

Differs only in 3D representation. Components may appear more than once in the library with different grades and the naming must reflect this. When in doubt, users should opt for less 3D geometry, rather than more, as the efficiency of the BIM is largely defined by the performance of the components contained within.

Adherence to the above grading and Model Development Methodology may result in multiple versions of the same element existing at different grades. This is accommodated in the object naming strategy defined in Section 8. Further purposes of the BIM will lead to additional specifications of the content, which should be built to suit the purposes of the deliverables.

Objects generated in the development of a project will be stored in the WIP area of the project folder structure.

The person responsible for co-ordination will assess and verify minimum quality compliance before submitting new objects to the corporate library stored in the central resource folder. The intended purpose of the components shall be considered and the results checked and verified prior to large scale use. For instance, structural analysis applications may require elements with certain naming conventions or other criteria, without which they will not be recognised.

Too little and the information will not be suitable for its intended use; too much and the model may become unmanageable and inefficient. It shall be dictated in the Project BIM Execution Plan the point at which 3D geometry ceases and 2D detailing is utilised to prepare the published output.

Intelligent 2D linework shall be developed to accompany the geometry and enhance the required views without undue strain on the hardware. Detailing and enhancement techniques shall be used whenever possible to reduce model complexity, but without compromising the integrity of the model.

Fully assembled compilation of views and sheets within the BIM environment preferred. Export views in the form of output files for assembly and graphical enhancement using 2D detailing tools within a CAD environment. Whichever methodology is chosen, the 3D model shall be developed to the same maximum extent before 2D techniques are applied. Be produced to true height above project datum.

Adopt the established project coordinate system across all BIM files to allow them to be referenced without modification. In order to comply with these rules, models should always be constructed the centre point 0,0,0 of the file, as information becomes less accurate and may cause significant errors the further it is from this location.

Real world coordinate values shall then be assigned to a known point of the model using the relevant BIM authoring software tools. Files that do not use this methodology and are drawn in true space need to be shifted to 0,0,0 prior to import into the BIM. Data exported from the BIM can then be either real world or local and whilst the majority of data will need to be delivered in OS co-ordinates for the purposes of collaboration and cross-referencing, some software e.

For export to such software, local coordinate systems can be utilised. CIPS takes the view that the outsourcing of services to specialist providers can often lead to better quality of services and increased value for money. Purchasing and supply management professionals should. Fourth generation techniques 4GT The term fourth generation techniques 4GT encompasses a broad array of software tools that have one thing in common. Each enables the software engineer to specify some.

All rights reserved. This document is provided for the intended. Software B. CAD Methods 1. Layer Standards 2. Font 3. Lineweights 4. Queensland recordkeeping metadata standard and guideline June Version 1. Posted at www. This article may not be.

Russell 2? External References 5. Introduction and Overview The Relationship Manager Banking is an apprenticeship that takes years to complete and is at a Level 6.

Contracts, agreements and tendering 1 Introduction This guidance note provides an overview of the types of contracts and other agreements you might need to use in setting up and running a local energy. Stages within this process are detailed further in this document. Mapping the Technical Dependencies of Information Assets This guidance relates to: Stage 1: Plan for action Stage 2: Define your digital continuity requirements Stage 3: Assess and manage risks to digital.

A siloed business architecture. What is BIM History of BIM Why Implement BIM Integrated project delivery, design-build, and other alternative project. Information Management Advice 39 Developing an Information Asset Register Introduction The amount of information agencies create is continually increasing, and whether your agency is large or small, if.

Contents 1. Statement 1. Compliance 3. HR Security 3. But what constitutes good BIM management? What does it mean to outsource BIM management,. Overview: The FDA requires medical device companies to verify that all the design outputs meet the design inputs.

The FDA also requires that the final medical device must be validated to the user needs. Our Promise. TPM is dedicated to provide the most extensive and high-quality training programs to help you maximize your investment.

Although the investment in time and money may seem substantial, it will. The dimensions refer to the outside edge or cut line. Tekla Structures More than a detailing tool Precast concrete Much more Than a detailing tool a Tekla Structures is much more than design and detailing software: it is the most accurate and comprehensive.

What How? Facility management briefing checklist The checklist has been prepared as a complementary document to BS Facility management briefing. Code of practice. BS is a standard for facility designers,. Project Management Process Description It gives the project organisation,. What is effective Design Management? Design Management is becoming increasingly recognised as critical to the success of complex construction projects.

However, the role of the Design Manager is poorly. Whitepapers Process Streamlining Written by A Hall Operations Director So, your processes are established and stable, but are clearly inefficient and you are not meeting your performance expectations. Many project-driven. Request for Proposal Autodesk CAD Support Introduction Denver Water is inviting your firm to submit a proposal to provide Autodesk product-based services and support to meet the requirements of Denver.

Introduction 3 2. Preparing Doctoral Theses 3 3. Submission Procedure 5 4. The Examination. Identifying Information Assets and Business Requirements This guidance relates to: Stage 1: Plan for action Stage 2: Define your digital continuity requirements Stage 3: Assess and manage risks to digital. Design without compromise. Log in Registration. Search for. Size: px. Start display at page:. Phillip Waters 5 years ago Views:.

View more. Similar documents.

 
 

Step01/13-autodesk revit architecture 2011-german tutorial 1/3 free download.Autodesk Revit Architecture 2011 German Tutorials

 

The cross-section of a moulding is represented in two dimensions by its profile. Mouldings alongside carvings and sculpting are used as additions to walls, openings, columns and beams and conform to the classical architectural rules. These classical descriptions and geometries for mouldings can be represented by the shape rules, which are detailed in Figure 24, to facilitate their modelling within a virtual environment.

In Figure 25 and Figure 26 these new shape rules, and their evolution are applied to classical mouldings. The simplest moulding is called a band or fascia see in Figure 25a , which is a plane-projecting surface and if it is small in cross section it is described as a fillet, which can be raised or sunk, horizontal, vertical, or inclined.

A convex moulding is called an ovolo, or a torus, which is illustrated in Figure 25b. If it is a small torus is called a bead, astragal, or reed. Concave mouldings are referred to as cavetto and are illustrated in Figure 25c. A moulding with double curvature is called a cyma; a cyma recta is illustrated in Figure 26a, and the cyma reversa is illustrated in Figure 26b. These double curvature mouldings are evolved from rectangular and segmental shapes detailed within Figure A small cyma is called a cymatium, which is placed above a band or any larger moulding.

To increase the cylindrical profile quadrants, projections are introduced by the addition of straight lines as illustrated in Figure 26c. A double concave moulding is called a scotia or three-quarter moulding and is illustrated in Figure 26d. When a convex and a concave moulding meet, instead of being tangent they come together at an angle, they constitute a beak moulding as illustrated in Figure 26e. Rectangular or square profiles are used to mark the boundary between each different cylindrical moulding profile to emphasise the change and shape.

The contour or outline of cylindrical mouldings is formed from quadrants, or segments, of circles through rotation or addition but further deformations can be introduced with elliptical, parabolic or hyperbolic shapes. An example of a deformation of a cylindrical moulding is illustrated as an elliptical quadrant moulding and is illustrated in Figure 26f.

In Figure 28, the shape rules illustrated in Figure 25 and Figure 26 are extruded to form 3D objects, which can then be combined in varied sequence to form architectural elements, as illustrated by the moulded architrave on the right hand side of Figure Figure Shape array – 3D Objects mouldings 4.

The shape and parametric rules are designed to exploit and maximise the full range of geometric parameters, deformation of shapes and abstract transformations using efficient and dynamic GDL scripts. The use of such protocols is necessary as the consistent use in naming variables allows them to be combined into compound objects allowing each component part to transform uniformly.

Variables can also provide information concerning transformations, scale, the current pen and the material settings. Parameters can be locked within a script where they are fixed or user modifiable allowing the user to change settings. When an object is built it contains a list of user modifiable parameters visible within a user interface or a dialog box, which controls the object. Parameters can be dimensions and angles, numbers and integers, materials and pens, text or fill patterns Watson, In the example in Figure 28, a semi-circular object Torus in Figure 25b is illustrated.

In the GDL script on the right hand side of Figure 28, a prism command is used to represent the objects profile and depth is used to represent its extrusion. The difficulty with this particular script is that it is very long and does not contain many variables to facilitate deformation or transformation. The parametric design introduced in Figure 29, overcomes these problems by replacing the numeric values with poly-line codes Watson, , which represents curve values. The curve values can then be represented by variables and additional variables for the rotational value of the curve deg and the cylinder radius r.

When different values are attributed for each of the variables the object is transformed and can represent an array of convex, concave and double curvature objects as detailed in Figure In the GDL script in Figure 30, a command is used to revolve the object to form the cylinder or column shaft. The diameter of the base of the column is represented by the cylinder radius r1 allowing the moulding to deform in proportion to the column and other elements.

The radius of the moulding profile r2 can vary depending on the profile geometry and negative values can be inserted to change from convex to concave profiles. As before poly-lines are used in the code to establish the construction of the curve in the profile, these can be radius, tangent or point and angle based syntax. In addition numeric codes represent masking values for the surfaces Watson, Figure Shape array circular mouldings A Doric column is represented in Figure 32, using coordinate transformations the primitives are stacked on the Z-axis or alternatively moved on the x and y-axis to form the column see a, b and c.

In the exploded Figure 32b, a cylinder represents the base of the column followed by the appropriate series of mouldings. The mouldings are detailed from the pattern books and transformed from shapes in Figure 32a, on the left hand side of the figure. A cylinder and a cone are added on the z-axis to represent the column shaft the cone represents the tapering of the column one third up the shaft. These primitives are combined with the primitives in Figure 32a on the left side of the figure to form the column with its mouldings.

The variables used to represent each value for the primitives are expressed in terms of the base diameter of the column, for example the r1 is equal to the half the diameter of the column base.

A series of conical shapes can be used to represent further deformations in the column shaft to represent column enthasis, which is a gradual deformation of the conical section of the column shaft. Figure Doric column The Doric Entablature above the column shaft, which is illustrated in Figure 33, has decorated cornices, friezes and architraves, which are developed using the shape rules in Figure 25 and Figure All of the primitives and mouldings are combined into a compound object, in this case a Doric column and entablature.

Additional transformations can re-scale the subsequent whole or parts of shapes or rotate the object around any of its axes. When the object is placed, the variables and parameters can be changed to match the object it represents in real world terms; other common parameters are formation level and rotational transformations.

The components or objects are placed in libraries or databases; the use of flow control, macros, subroutines and loops can re-introduce these objects in repetition or revised state partially illustrated in Figure 33b. Figure Doric column and entablature 4. Figure 34, below illustrates a method for the construction of the Ionic volute of the capital of the Ionic columns. The volute is constituted of twelve quarter-circles, the centres of which are situated inside the eye.

These centres are inscribed along the diagonal of a square that is placed within a larger square and rotated 45 degrees. The eye of the volute is placed in the inner square. The diagonals of the inner square are divided into six equal parts, resulting in the identification of a total of twelve points.

The centres of the respective quarter-circles are numbered progressively from 1 to 12 clockwise from the exterior to the interior. The point of the compass moves each time to the next successive centre.

The left drawing in is attributed to Batty Langley and the right is the drawing from Andrey and Galli Langley and Langley, , Andrey and Galli, Meshing was then used to add the irregular depth of the leaf. Group and solid Boolean operations were used to create the bend in the leaf around the column and the bend at the top of the leaf, which is illustrated in Figure 36b. The object is bent in two directions by intersecting the two objects and the intersection results in the creation of leaf illustrated in Figure 36c.

The range of parameters attributed to the Acanthus leaf is limited to its bounding box i. Finally the leaf is repeated to match the columns diameter through a looping procedure as shown in detail d and stacked with additional ornament to form the Corinthian capital see Appendix A21 to A A large amount of the original elements of Georgian buildings are still in place and date back to the early eighteenth century or have evolved with additions over the centuries Innocent, Because of the variation in size, texture, bonding, pointing and condition GDL models cannot compete with the laser survey detail.

The external walls in Georgian buildings in Dublin are mainly constructed in brick and laid in a Flemish Bond using a mortar mix of lime and sand. Flemish and English bonds were the principle bonds used in 17th and 18th centuries. The bricks vary in size because they were handmade. A sample of brick dimensions measured from the scan survey indicate an average size of nine inches in length and two and one half inches high, although.

The colours of bricks varied from red, purple, or grey in the late 17th century and up until the early s, imported brick from Holland was grey in colour Lynch, , Nicholson, , Roundtrees, ,. These observations are presented to assist in developing a protocol for representation of external building fabric. Samples of laser scan products such as textured point-cloud or ortho-image are illustrated in Figure 37 below.

Orthographic textured point clouds can therefore represent the external brick fabric. The first image in Figure 37a, is a dense point cloud from which it is not feasible to abstract brickwork dimensions.

The second scan in Figure 37b illustrates a textured point cloud whereby bonding, texture and pointing details can be observed and measured. The parametric design for size and position of openings can be developed from rules of proportion outlined in the pattern books.

The top windows are made up of a single circle, in the next set of windows intersecting circles and finally in the lower set of windows the circles are placed one on top of each other. The height of the opening dictates the angle of the brickwork head Langley, a. The construction of the golden section Fletcher, , Frings, , a geometric proportion used in classical architecture can determine bay widths. The golden mean or golden section is illustrated in figure 39c.

The section is formed initially by constructing a square, inscribing a circle from the centre of one of the sides of the square, side A is extended by the distance B to meet the tangent, and the rectangle is completed. The rectangle represents the golden section and is represented as red lines in Figure 38e. The vertical distance between window openings are usually asymmetrical with the diameter of the circle d1, as shown in 19d.

The application of proportional rules assist in representing the facade as a GDL object allowing for a parametric design to include for variables in opening sizes and their relative positions.

The alterations to the facades can include removal or enlarging of brick walls, window and door openings and parapets. Two variables are introduced, the width of the window based on the diameter of a circle and the distance between the windows which is also dependent on the diameter of the circle.

A series of openings are established using a GDL script for cutting the openings in the wall panel. The openings are laid out according to the proportions illustrated in Figure 38d and Figure 38e. The golden section is not taken into account in the shape rules in this instance. The single panels can be adjusted for any opening size or distance between openings. A sample code is illustrated in Figure 39b of a single opening panel which can be placed in any position and will cut an opening in a solid wall panel see Appendix A36 to 45 for GDL code.

Calp, a local limestone, is used in the walls to some of the basements and is mainly covered with a render. Local granite is used in plinths, cornices, steps, cills and copings. Imported Portland stone is used in the construction of more complicated mouldings and carvings associated with door cases, porticos and architraves around openings etc.

Local sandstone is also used to a lesser extent for intricacies in carved work for the later elements Lewis, Stone shapes are much larger and better defined than brickwork and can more easily be represented as 3D models using GDL. An arrangement of stone shapes is illustrated in Figure 40 to create a composite wall with an arched opening. A semi-circular object is subtracted using solid element operations from a larger block which represents a wall shape.

Ashlar stone is represented using an array of block shapes; plinth and corbels are then combined with the other objects to create the final composite object see Appendix pages A53 to 54 for GDL code. The sliding sash window was preceded by hinged casement windows. Original earlyth construction methods used for sash windows exposed the timber boxes in which sashes were held. A sectional detail of the timber boxes is detailed Figure 41b. In addition no reveal was included as the windows were often flush with the brick- work Innocent, Building regulation in Ireland in changed this practice, stating that the window had to be set back from the facade by at least four inches.

The early sash windows tended to be smaller, in line with Palladian principles, whereby the window cill was level with the dado rail. The different glazing arrangements of the sash window is illustrated in Figure 41c, Roche, Rivington, A typical 18th profile of a glazing bar profile sash frame is detailed in Figure 41a. A model of part of a semi-circular Venetian window Langley, a is illustrated in Figure 41d. The centrepiece is usually accompanied by two sidelights not shown in this detail and is framed by ionic pilasters.

This Venetian window is constructed using sash frames and appears in many Georgian buildings usually in isolation to the rectangular sash windows that form the main bays of the building facades. Finally in Figure 41e to f, arrangements are detailed of a typical stone architrave surround to a sash window. The Doric and Ionic orders in the door cases represent complex GDL objects, which are an ensemble of the mouldings, and primitives that illustrate the shape rules and parametric design presented in this chapter Langley, a, Langley, , Halfpenny et al.

Many of the original stone entablatures and pediments disappeared when neoclassical styles were introduced in the late 18th Century. Sidelights and plaster enrichments were included around the fanlight O Neill, a, O Neill, b. The oak was replaced by imported Baltic pine and was used in a more economical fashion with lower pitches constructed usually as triple roofs with rafters, collars, ties, struts and purlins as detailed in detail c Innocent, , Rivington, , Nicholson, The roof coverings consisted of slate fixed onto battens in gable or hipped roof construction.

A series of shape arrangements for roof forms are laid out in Figure Meshing and mass commands in GDL allow for the introduction of height in addition to width and depth Watson, The object is raised at Z2, Z3 and Z4 to represent a half gable roof.

Bending is introduced by bringing Z4 back down to zero and a hip roof shape is formed. Figure Shape rules for roof construction In Figure 43a, b, c, d and e, the arrangement of components for a typical 18th century timber roof carcass is detailed.

The geometry for each component ceiling, joist, strut, ridge board etc. The arrangement for different configurations of roof covering is detailed in Figure 44i. This includes pitched f , hipped g and valley geometry h , which again is based on half the roof span and the pitch of the roof. Different configurations of the roof carcass and covering can be constructed by changing variables of roof geometry.

In Figure 45, the rules of classical architecture are illustrated in two examples of an ensemble of the classical orders. An arrangement for an Ionic colonnade and dome roof is detailed in 45b see pages A80 to The mapping process for plotting parametric objects onto laser scan survey data which is the next stage of HBIM, is detailed in the next chapter.

The laser scan survey data can be considered as a skeletal framework, which is then mapped using parametric architectural elements to form the HBIM. Three case studies are presented in this chapter to illustrate this mapping process. The three case studies presented in this chapter represent the design and evolutionary stages of the HBIM mapping process. The addition of a web-based photo-scaling application for extracting numeric measurement data is presented as an outcome of the testing of HBIM.

The testing of HBIM is presented in the following chapter to this one. Finally, in this chapter a series of examples illustrate the automation of conservation documentation from HBIM.

This data is imported in image and vector format for further processing within the HBIM platform. The point cloud is segmented to supply plans, elevations and sectional cuts for mapping of library objects. Further interrogation of the laser scan survey data supplies numeric values for parametric values for the library objects themselves.

A project co-ordinate system was established by identifying a temporary benchmark 0, 0, 0 at ground level, located at a recognised point on the laser scan survey. The formation level was set along this point horizontally on the x-axis. Formation levels can then be set for each story level at a central point between the window openings and horizontally along the x-axis see Step1 – Figure Step2 — Extracting measurements from the ortho-image The dimensions of the wall height, width and length were calculated from the ortho- image.

Co-ordinates x,y values are recorded using hotspots markers placed on the image that were then used to calculate length or angular values see GDL script in Figure A wall is normally defined by its parameters height, width and thickness and its position in a co-ordinate system relative to other objects.

The height of the wall can also be defined by its formation level at each story level and finishing level roof. The wall can be plotted for each story level, but in this case the wall was plotted from ground level to roof level. The thickness of the wall will depend on its composite construction. The materials and techniques that make up the wall construction can be determined from the ortho-image data.

In this case the bonding of the brickwork is Flemish bond, which assists in the identification of the composite structure of the wall. Based on this information, two and a half brick measuring mm was assumed as the wall thickness Nicholson, Step3 — Modelling the 3D wall The length and thickness of the wall was then positioned on plan and the dimensions of the object were inserted in a dialogue box, shown in Figure Step3.

The formation level, which in this case is zero, is inserted in the dialogue box to form the 3D wall. The other parameters such as texture, sectional fill details and other numeric and descriptive data can also be entered in the dialogue box for the wall. The level of information requested regarding the objects parameters depends on the specifications in the original GDL script. Finally the 3D wall is represented in Figure 46 —Step3.

The numeric data required for plotting and sizing the window and openings was extracted from the laser scan survey as an initial procedure. By placing a marker on the points A, B, and C onto the orto-image detailed in Figure 47a , the x and y coordinates for each point were calculated. The lengths and formation levels were then obtained for the required parameters of the window and placed in a data sheets.

Other parameters can then be calculated from the x and y coordinates such as angular values and distance between objects. The window openings as objects see GDL script in Figure 39 are positioned on plan on each story or on elevation as detailed in Figure 47c below. The completed 3D model of the wall with openings is detailed in Figure 47d below. The sash windows as objects see page A65 in Appendix A for GDL script are plotted into position onto plan and elevation as detailed in Figure 48a and b.

The red vector lines in Figure 48b represent the window position in plan, based on the laser scan segmented survey data vector format. In Figure 49 a view of the window in 3D is detailed also showing the dialogue box for the window for fixing parameters. Finally in Figure 50, the 3D model for the wall with openings and sash windows is illustrated.

Historically door cases were copied from the pattern books and represent a re-production of the classical orders.

Consequently it is an ideal example to illustrate the building of a parametric object from laser survey data and the additional input of pattern book detail to augment the laser survey data. He does not however show detail of the regulae and rosette see Figure 51f this detail is taken from Langley Langley, The Classical proportioning which is used is based on a series of modular relationships based on the diameter of the base of the column.

In Figure 51a, detail 1 sets out the modular relationship, which are all based on one module 1M , which represents the diameter of the base of the column. The pediment is made up of the entablature in the centre placed on the capital of the column supporting it and two raked cornices over the entablature. The Doric entablature is 2 modules high and is made up of the cornice, which is 0.

Finally the raking cornice, which is constructed over the entablature, is 0. In Figure 51 below, a number of the objects are illustrated mapped onto the ortho-image on the left. On the right of Figure 51, the objects are shown in the 3D model. The pattern books alongside the laser survey data see Figure 51e and f and Figure 52 are used to build the model of the pediment and establish the parameters of the main objects.

The objects which make up the Doric pediment are the trigliphs see Figure 51b , cornice see Figure 51c , frieze see Figure 51d , the regulae and rosette see Figure 51e , and the architrave see Figure 51f. The measurements for plotting the door case are extracted from this laser scan survey data as detailed previously on pages 91 to This data is combined with detail from the pattern books to model the door case.

Figure Survey data for door case Step2 – Mapping columns from generic library objects In Figure 53a, the Doric column is mapped onto laser scan survey data as composite element. The use of generic columns which allow for configuration of main geometric parameters dealing with height and diameter speeds up the mapping process. While this appears more efficient, conflicts will arise in arranging sub-elements and matching geometry between the survey data and that of the generic column.

Step2A — Alternative to Step2 – Mapping columns from moulding geometry To overcome conflicts which occur between the geometry of the survey data and the generic GDL column object, the laser survey data is mapped using a series of cylindrical primitive parametric objects as detailed in Figure 53b.

The primitive mouldings are deformed for different geometric scenarios see examples in 53c. The objects are arranged to form the column base as detailed in Figure 53d. Interpretations from the pattern books Figure 53b detail 3 were then used to assist the mapping process.

The remaining parametric objects, which make up the Doric column, which include the capital and shaft, were built up in a similar fashion to the base. The 3D model of the door case is detailed in Figure 53e.

Figure Plotting columns, door case and pediment 5. Additional historic data, such as the identities of builders and architects, assist in identifying the sequence of construction of the street. For example, Edward Lovett Pearce, who was one of the most prominent designers in Dublin in the early s, is accredited with the design of numbers 9 and 10 Henrietta Street.

Pearce studied Renaissance manuscripts and in particular the Palladian styles that were popular in the early s in Ireland and Great Britain, and subsequently this influenced his designs for Henrietta Street Craig, There are no surviving design drawings for Henrietta Street.

The roof covering is black slates laid on hipped and gabled roofs. Some of the original elements of the buildings are still in place and date back to about at the earliest, or have evolved with additions over the centuries.

The terraces of Henrietta Street were laid out with basement areas bounded by wrought iron railings. In the 19th century, cast-iron balconies were applied to facades and wrought iron grilles guarded basement windows and fanlight windows. Setts Square block cobbles developed from cobbles are laid on the street and granite paving is laid on the footpaths and granite up-stands under the railings. In Figure 54 the external structure, fabric and architectural elements of no 3 Henrietta Street were mapped.

Detail a, represents the hipped and gable roof which is located in place on the external walls. Detail c, shows windows and door case and bounding railings mapped in position. In Figure 55a, the road is constructed directly from the point cloud by meshing and surfacing the point cloud data and introducing the mesh as an object into the street model. The partially constructed model in Figure 55b consists of the repetitive terraced buildings, which can be modelled using standard facades as objects.

Additional buildings were added to the model at both top ends of the street. These buildings were modelled separately and were introduced into the model as objects as detailed in figure 55c and d. From a plug-in library, parametric objects representing architectural elements are plotted onto the laser survey data. The parameters for objects are extracted as numeric data from the ortho-image and segmented point cloud data.

The objects are then manually positioned onto the segmented plan and orthographic image in elevation and adjusted in side elevation and section using segmented data for angular displacement. The image and segmented datasets represent the information for a particular plane on the x, y, and z-axis. The planes on x, y, and z-axis can therefore represent elevation, plan, or section of an object. When a library part or parametric object is placed into the HBIM, it is placed as an icon in 2D in the floor plan, separated by height or formation levels and is located along the x and y-axis.

In section and in elevation, the object is positioned in relation to the z- axis relative to the x and y-axis. The appropriate survey data are described in chapter 2 as segmented point cloud, structured mesh data and orthographic image data. The laser scan data provides a survey framework, which is then, mapped using parametric architectural elements to form the HBIM. The library of parametric objects is designed as a plug-in for existing software platform Graphisoft ArchiCAD. The experiences of testing the HBIM this detailed in the next chapter in pilot case studies have identified the requirement for numeric data to accompany the segmented point cloud and image data.

In this section an improvement is proposed for mapping objects onto the laser scan survey framework in relation to the extracting of parametric information from the laser survey data. The previous case studies illustrate the different possibilities for plotting library objects onto a range of survey frameworks.

A more robust system is required for the plotting stages of HBIM, which will accelerate the mapping process. This improved system can be introduced by semi-automatically supplying numeric and measurement data for adjusting the parameters and plotting the objects to establish the model. The application is easy to access and portable and can be used on any operating system and browser and independent of commercial software platforms.

The photo-scaling application is a web- based application and its design will allow for extending the application to work on mobile devices. The application is used for measuring distances and angles between points using two-dimensional orthographical images and pixel based segmented point cloud data.

The application is developed using Ruby on Rails which is an open source web framework RubyonRails, and Javascript JavaScript, A sample of the code for the application is detailed in Figure When the user uploads an image it is displayed on screen with a size of by pixels. This scale is used irrespective of the original scale of the image, this way a standard distance between each pixel is maintained.

Once the image is uploaded and displayed the user is asked to begin selecting two points. These first two points are control points, which are predetermined distances, based on real world measurements for the object. To mark the point on the image, which the user selects, a HTML div division is overlaid on that particular point with the size of 1 pixel. Using JavaScript in this way the correct values will be determined regardless of the users screen resolution or, for example, if the browser is set to a certain zoom level.

The code sample in Figure 56 below locates the current x and y position when the point is located on the image.

The offset. Similarly the offset. A user enters a control measurement or known distance of x metres and the distance between the two pixels on screen is p, 1 metre on the screen is equal to p divided by x.

This value is stored then for the uploaded image and can be edited by the user at a later time if needed. The users can then select more points on screen; for each distance in pixels that is calculated the distance in metres is retuned.

Once these points have been selected the formula below is applied to get distance between the two coordinate points. Detail a, represents the variables that define the location of an opening these are illustrated in the vector diagram in the centre. The variable consist of the size of the opening and the distance of the opening from other objects in this case other openings.

The GDL script is illustrated in detail b, which generates the single panel in detail c. The panel can then be repeated to form the full panel in detail d. The GDL scripts for different arrangements of openings, stone cladding and architrave surround for wall panels are detailed in full on pages A35 to A57 in Appendix A. The visualisation of objects is achieved through viewing 2D and 3D features, plans, sections, elevations and 3D views Aouad and Lee, , Eastman, Where conservation or restoration work is to be carried out on an object or structure, conventional orthographic or 3D survey engineering drawings are required.

To a large extent current research concerning automated surveying systems for cultural heritage objects has concentrated on the identification of suitable hardware and software systems for the collection and processing of data. As a result, the output is the accurate 3D model mainly suitable for visualisation of a historic structure or artefact. The objects in this case are historic structures brought through the design process in the opposite direction, revealing information about the original design and construction.

A sample of street elevation drawings are illustrated in Figure 59a, b, and d. In addition typical section and elevation details are shown in Figure 59d, e and f. Finally in Figure in figure 59g a partial 3D drawing is produced of the street. Similarly in Figure 60 a set of plan, elevation and section drawings are detailed. The 3D drawings detailed in Figure 60c and d are described as 3D documentation, in this instance showing cuts between wall, floor and windows.

Finally window schedules are automatically produced as part of HBIM process. Mapping the objects directly onto the point cloud, is not practical as the data size of the point cloud is large which will slow down data processing. The proposed solution is to map the objects in 2D onto segmented point clouds and orthographic images in elevation, plan and section.

A more robust system has been developed for the plotting stages of HBIM. One of the main features of this system is a web-based application for semi-automatically supplying numeric and measurement data for adjusting the parameters and plotting the objects to establish the HBIM.

The first evaluation is an end-user test of the software and the second a qualitative assessment of documentation generated using HBIM. An explanation of scenario testing followed by a definition of conservation documentation is presented initially in this chapter. Conservation documentation is an outcome of the HBIM process and features in both evaluations.

The procedures, findings and analysis and review of both evaluations, which are the end user test and the qualitative assessments of documentation, are then presented. In addition, a data sample of HBIM documentation is compared with related ground truth data to assess accuracy. Conventional software design and evaluation methods can be carried out through tasks described by fictional applications to evaluate end user requirements as proposed in scenario-based design Carroll, The fictional applications for the software are established through the use of credible stories, which then identify problems and the potential for improvements in the software.

Because of the diversity and complexity of architectural conservation projects, simulated conservation scenarios were used to represent an example of this diversity in order to evaluate HBIM. The process began by constructing or developing alternative scenarios and then integrating the context of those scenarios into constructing a Historic Building Information Model related to the laser scanning survey of Henrietta Street.

In addition to developing the fictional applications, discussion and dialogue with the test participants created a continual input resulting in on-going review and revision of the software design. The purpose of documentation is to enable through the supply of accurate information the correct conservation, monitoring and maintenance for the survival of an artefact Fai et al.

Every stage of the work of cleaning, consolidation, rearrangement and integration, as well as technical and formal features identified during the course of the work, should be included. This record should be placed in the archives of a public institution and made accessible to research workers.

Suitable models for appropriate standards for recording and documenting historic structures are detailed in national guidelines such as the Historic American Building Surveys and English Heritage Metric Survey Practice Bryan et al. At an international level recording standards have been established by the International Council on Monuments and Sites ICOMOS , which is, an international non-governmental organisation of professionals, committed to the conservation of the world’s historic monuments and sites ICOMOS, a.

Its main purpose is the improvement of all methods for surveying of cultural monuments and sites. The work of CIPA has been instrumental in developing new automated methods of digital recording and storage in addition to the standards required for accuracy of surveying and documentation of the built heritage.

RecorDim is a CIPA initiative in collaboration with other international heritage conservation organisations to improve and develop standards for the documentation of architectural heritage CIPA, They propose a system using a series of case studies to exploit the object intelligence within BIM to archive and present both tangible and intangible cultural assets Fai et al.

The European Committee for Standardization CEN provides for European standards and technical specifications in almost all areas of economic activity. The participants were all male and ranged in age from 19 years to 35 years.

A series of three training workshops were held with the group to train them in the application and use of HBIM and 3D CAD as outlined in the scenario above. In total twenty-six students attended the training workshops and fourteen volunteered to participate in the scenario test. The participants were required to produce a set of conservation documents, to include plans, elevation, cut sections, window details and schedules in addition to 3D documentation.

The scenario tests were held after the training workshops in a computer laboratory in the Dublin Institute of Technology. The participants constructed the model over four two-hour sessions using identical software platforms and under supervision. At the end of the exercise the participants were interviewed and completed an online questionnaire. These are illustrated in Figure The ortho-image is illustrated in Figure 61a, the vector data showing positions of openings is illustrated in Figure 61b.

The dimensions and formation levels for the library a sample of library objects windows are detailed in Figure 61c. The library objects supplied for the scenario exercise included window and door wall openings, sash widow including all components for each opening size and a Doric door case as a composite library object.

Finally, the sequence for plotting the 3D model illustrated in Figure 61e. In the following part of the test, the users were asked to assess the efficiency of each of the plotting stages for creating the model based on the laser scan survey data. The survey data for plotting the 3D model in HBIM consists of a range of data; these are Ortho — Image, Vector plot, Data sheets containing numeric data and a combination of all of these.

The reason for associating error with the ortho-image is because of possibility of incorrect scaling of the image data when it is imported into HBIM. This problem can be overcome by embedding measurements or coordinates within the ortho-image, which are verified before the image data is used. In addition, measurements and angular values can be extracted directly from both ortho-image and vector data and then stored independently in data sheets.

The library object for the opening was rectangular in shape. The majority of the users see right hand side of Figure 68 indicated that HBIM could produce the full list of automated documents.

A small minority did not include the production of scheduling from HBIM, whereas they indicated that 3D CAD was capable of automating a much smaller range of conservation documentation as detailed on left-hand side of Figure 68 below. The advantages of the HBIM system become evident in the last section of the user test in relation to the quality of documentation and the behaviour of the library objects in HBIM.

It is obvious that objects within HBIM contain a vast number of parameters ranging from geometry and texture to conservation analysis and that not all of these designed parameters will function in a 3D CAD environment.

The introduction of an additional help and learning centre for HBIM can improve ease of working in HBIM, reducing the effort in time to use and learn the software. The problems associated in extracting measurements to size library objects were overcome by introducing the specialised WEB based ortho-photo scaling application detailed in Chapter 5.

The application was developed as a result of the issues that were raised in the end user tests and is specifically designed to operate outside of the BIM environment. Improving texture options for objects can be achieved by applying the colour and texture from ortho-images. The image is matched with the 3D object and edited by cutting out openings leaving only wall texture. Figure Texturing objects Introducing improvements in the range of object parameters and the plotting of the objects onto the survey data can be achieved using standard coding protocols for each library object.

The improvements for scaling, rotation and anchor points will be included as a template in coding all objects. In Table 3 below, solutions are summarised for resolving the potential for errors occurring in the system. Importation of the Incorrect scaling of Imbedded measurement laser survey data into orto-images data onto ortho-image HBIM and possible causes of error 2.

Calculating Errors in extracting Use specialised WEB WEB based ortho- parameters and sizing measurements from based ortho-photo photo scaling of library objects imported survey scaling application for application was data within HBIM extracting measurements developed from end user testing 3.

Improving objects No parameters for Re-code object for parameters creating irregular creating openings in openings walls No realistic texturing Use ortho-image from options for surfaces laser scan survey to texture objects 4. The seminars were held in October , October and November Each seminar consisted of a series of presentations from experts in laser scanning, BIM and the recording of historic structures. The participants who attended the seminars were practitioners and researchers from architectural conservation and surveying.

In order to draw on the experience of the seminar participants for the development of HBIM, a consultative expert group were identified from the seminar participants. The consultative expert group who agreed to participate consisted of: 1. An engineer specialising in existing structures, who was familiar with the use of BIM models for assessing existing structures; 3.

A general practice conservation surveyor who was one of the authors of the conservation plan for Henrietta Street which was funded by Dublin City Council. A full time researcher in the Dublin Institute of Technology in the area of laser scanning and the recording of historic structures. The group consisted of three males and one female between the ages of 22 and In this evaluation a sample set of conservation documentation is produced using HBIM; the documentation is based on conservation scenarios.

The conservation expert group became familiar with the HBIM process through the series of seminars described on the previous page. A number of meetings were organised with the expert group, in order to develop the context and content of the conservation scenarios.

This comprised of identifying key conservation problems and translating them into the scenarios. The second scenario was constructed around the conservation of the historic facade, the windows and the door case of number 3 Henrietta Street. A wider range of conservation documentation was therefore required to complete the exercise. The documents consist of a sample of location drawings, survey data, 3D models, orthographic drawings and schedules produced as a result of scenario 2.

Their opinion was, in general that, in contrast to conventional 3D CAD, HBIM produces a wider set of conservation documentation containing information related to geometry, building detail, geographical information, details of materials and other numerical data or schedules relating to the historic structure.

They all agreed that the conservation documentation could be automatically extracted to assist with solutions for the different conservation scenarios.

They also concurred that the analysis based on the HBIM documentation can produce the following information; visualisation models, survey data, building details, specifications and information sharing.

In particular, they identified the advantage of using the 3D models as a cost effective method for simulation of conservation interventions. The overall agreement amongst the conservation experts for the second scenario indicated that the documentation produced provided correct detail for completing the outlined conservation scenario. The question of dissatisfaction related to the need for national standards in Ireland for producing conservation documentation using new technologies.

Although it was agreed by the group that the standards produced by English Heritage Bryan et al. The average error between the total station measurements and plot A was 0. The average error between the total station and plot B was 0.

In plot B the error on the x-axis was 8mm and 18mm on the y- axis, English Heritage recommend a precision of 15mm for a similar structure. The first plot A did not compare as favourable showing an average error of 24 mm on the y-axis and an average of 13mm on the x-axis. Table 8: Density of point cloud and measurement precision Bryan et al. Errors can also be caused by point definition, which is obstructed by decay of materials at edges.

Defining the points using intersecting vectors on the ortho-image can assist the accuracy of point location. In Figure 71, below, the base of a Doric column is illustrated. In the ortho-image, the definition of the elements, which make up the base of the column are obscured because of both decay and occlusions. Other image data and detail from historic data are introduced to define the missing data and build up the base of the column as detailed in Figure 71a.

The approach identified improvements in the use of the software through end-user testing and a qualitative evaluation through a discussion and dialogue amongst an expert group. Additional design work is required to introduce more flexibility for building non-uniform shapes. The accuracy in plotting can be improved through expanding the specialised WEB based ortho-photo scaling application for extracting measurements.

In the second scenario the conservation experts concurred that the standard of conservation documentation produced from HBIM was suitable and contained correct detail for completing the outlined conservation scenario. This is comprised a set of interrelated procedures for combining the new technologies of laser scanning and Building Information Modelling BIM for recording and documenting historic structures. The HBIM procedure begins with the recording of structures using laser scanning followed by the processing of the survey data.

The resultant processed survey data is then used as a mapping framework for plotting interactive parametric objects. These parametric objects represent architectural elements, which are then combined together to generate a virtual model of an historic structure. The architectural elements are constructed as virtual objects based on a set of new shape and parametric rules.

The new shape rules are based on the classical detail and design provided by architectural pattern books of the 18th and 19th centuries. The creation of shape and the parametric design for the objects is developed through the use of Geometric Descriptive Language GDL.

The objects are compiled in a plug-in library within the software platform ArchiCAD. A processing pipeline was developed for mapping the parametric objects onto the laser scan survey data. The mapping process is combined with a new web-based application for extracting measurements from the laser scan survey data for defining the parameters of architectural elements.

Conservation documentation in the form of survey data, orthographic drawings and schedules and 3D visualisation models can then be automatically produced from the Historic Building Information Model. The HBIM process was successfully tested and validated by both end users and conservation experts.

In addition the results of accuracy tests, which compared HBIM to related ground truths met with accuracy standards specified by English Heritage Bryan and Blake, This process consisted of defining scan positions, point cloud densities and scan overlaps suitable for the recording and surveying of the architectural period, location and ensemble for Georgian architecture.

The recording framework identified on page 30, establishes good practice for efficient use of laser scanning equipment. The laser scanning campaign requires good planning and a strategy to allow for optimal data capture within a reasonable timeframe in order to supply the required survey data. The identification of correct laser scan survey products used to construct the HBIM is the second important element identified as part of the recording framework.

The products identified are the ortho-image, the segmented point cloud and mesh data, which are generated from the pre and post-processing stages of the laser scan survey data.

The pre- processing stage consists of cleaning, sorting and registration by combining different sets of point cloud. Each stage of pre-processing is essential for generating segmented point cloud data, which can be used for part of the modelling process and also for organising data for the post-processing stage. Only BIM data or files that have been checked, approved and given the appropriate status code shall be transferred to the Shared Area see Preparation for Publication for checking process.

Sharing of models shall be carried out on a regular basis in order that other disciplines are working to latest validated information as defined in the Project BIM Execution Plan. Model files shall be issued in conjunction with verified 2D document submissions to minimise the risk of errors in communication. It is recommended that Model files should be issued exactly as produced with no additional merging, or editing.

All necessary references and linked files should also be issued. The Shared Area shall also act as the repository for formally issued data provided by external organisations that is to be shared across the project. Changes to the shared data shall be effectively communicated to the team through traditional drawing issues, change register or other suitable notice, such as , as defined in the Project BIM Execution Plan.

This may, in truth be synchronised locations for each stakeholder Publication and Document Issue Alongside other project documentation, exported data and 2D electronic drawings produced from the BIM shall be stored in the Published Area of the project once formally checked, approved and authorized.

A record of all issued deliverables shall be maintained in both softcopy and hardcopy where appropriate. Information within a BIM is inter-dependent and changes in one view may affect other views. As such the BIM files and all associated views shall be treated as Work In Progress or shared as un-controlled documents until such time as they leave the BIM environment in a non-editable format.

Only data and drawings which it has been deemed necessary to revise will be reissued following modification work. Additionally, at key stages of the design process, a complete version of the model, exported data and associated drawing deliverables should be copied into an archive location.

Archived data shall reside in logical folder repositories that clearly identify the archive status e. Sheets from the BIM shall be published to PDF preferred , DWF or other non-editable format, where they can be checked, approved, issued and archived as traditional documents.

Key Points Does the drawing border and title block need amending for work-in-progress? Is there a need for a model matrix to explain the file structure? If Phasing and Design Options are utilized these will require an explanation? The current sheets when viewed in the BIM are classed as work-in-progress and so it is preferable to remove them from the model to stop any confusion over what is validated information. For very large and complex projects it may be necessary to split the model up into zones or packages of works.

When this is occurs a model matrix should be created to document the file structure. The AEC CAN BIM Protocol-Model Validation Checklist document provides a check list as a guide for preparing the model file for issue, the intention being that the recipients of the model know that the file is fit for use and will not require additional work to fit within the project framework. A model publication checklist should contain as a minimum: It is advised that all drawing sheets and extraneous views be removed from the BIM.

If contractually pressured to deliver a model containing sheets then the sheet borders should be swapped for a transmittal border. However, in time, like any other significant industry-wide change it is expected that litigation will surface and the industry will respond accordingly.

Thus there is a danger in being overly cautious and putting BIM under a microscope resulting in an immobilized industry, simply slowing BIM uptake.

So rather than be reactive and focus too much on issues that simply are more fluid than concrete we have opted to be proactive and identify possible areas of risk, how they can be mitigated individually and collectively to reduce and marginalize potential problems with the employment of BIM enabled technologies.

There is no doubt that the AEC industry has suffered from a growing lack of interoperability that has led to waste at all levels, increased mistrust and reduced respect between all involved in the construction industry this in itself has triggered increased risk and in turn when that risk is shunted increased litigation where parties are ill-equipped to deal with it.

One such innovation is building information modelling. Many of the risks associated with BIM i use can be eliminated, limited, or managed by the use of BIM-specific contractual provisions. As with other risks, this requires identification and contemplation of the risk, crafting appropriate language to deal with it, discussion and negotiation, and ultimately agreement on specific terms.

Given the complexity of issues we would encourage you to seek legal advice in contractual matters especially with your insurers. On the other hand, some have suggested that aggressive use of disclaimers; indemnification and non-reliance clauses diminish or eliminate the benefits of BIM that may accrue to all parties.

Whether this type of model can be adapted to normal three-party arrangements that can become adversarial remains to be seen. Given the legal complexities our intent is to provide best practices that while actively encouraging the sharing of the BIM each participant can manage risk effectively and efficiently. It is hoped that this section becomes a living section where your suggestions can be added with the goal of reducing the risks associated with BIM enabled technologies over time and seeks ways to avoid litigation.

Such laws are generally strong on individual rights but weak on collective rights. The creation of a BIM through the collaborative efforts of many project participants raises a question assuming that material generated by the BIM is subject to copyright protection as to who will be deemed to own the intellectual property and information in the BIM and therefore be eligible for copyright protection?

Suggestions ii for ways to move forward propose that in a BIM, the mechanical design for example is distinct from the architectural design and that there should be no change to how copyright in each individual part of the design is traditionally dealt with; the relevant designer would still own the copyright on its design. As such, designers should not necessarily be concerned that the use of BIM puts them in a weaker position in respect of copyright or intellectual property rights.

Does not require permission to use their individual parts of the BIM from the other model participants. Where the BIM is used post construction then such use is laid out in detail as to expectations of the metadata contained in the BIM Any copying or use of the composite image requires the consent of all the joint owners. Copying or use of the composite image requires consent of all the joint owners. If it is intended that the composite image should be reused, it would be advisable to set out the parties intentions clearly by way of an express contractual acknowledgement.

Clients often assume they will somehow be of future value, others think they can create a database of project information that will help them reduce future costs. Public Sector clients reason that the public, having paid for services, has a right to own the result.

In these situations the clients are confusing the services provided with the deliverables what often are characterized as instruments of professional service.

BIM facilitates a less adversarial way of working because it is collaborative by its nature. All parties are working in the interests of the project and not themselves. The adversarial component could be eliminated by the parties, including the client, by waiving liability against one another.

The theory behind waiving claims is that it prevents parties from acting defensively and encourages open discussion. The waiver of claims is also supported by industry bodies in other jurisdictions, such as the Strategic Forum for Construction in the UK. Generally, working with BIM each participant will: Recognize that responsibility and liability for design lies with each designer.

If there is a fault with the design in the BIM then the designer will make changes and communicate changes with the contractors. Recognize that contractors are responsible for what they build through ways and means.

If there is a change location of duct for example during construction, the contractor will make the changes and communicate the changes with the designers. In those issues are reflected in 93 percent of their claims. This is not to suggest that actual design work is less important in managing risk today but that the internal processes a firm uses to support the design are having a greater impact on claim frequency. It is a reasonable assumption that unless internal processes are properly aligned with the use of BIM enabled technologies then participants will fall prey to the same problems that plague our industry now.

The technology will not be the reason, but rather the way we use the technology will have a greater impact if we are already prone to be laxed in the four main risk drivers already.

In that rate grew to 37 percent. This will help owners define the most appropriate uses for BIM within their own organization along with identifying the services that they should procure to gain benefit within the design and construction processes. This should be established. Develop a clear and comprehensive scope of work related to the use of BIM that is linked to the clients project expectations.

This may mean that BIM has a very specific and possibly limited role depending on the scope of work and services to be provided. Identify BIM contract requirements before any modeling work commences. Issues that are important to include within the owner’s contracts with service providers should be identified and categorized so that the owner can more easily develop BIM related contract requirements 2.

Develop the BxP and outline to the client roles and responsibilities If a contractor is involved CM, IPD, etc then the entire team will need to share their agreements to make sure they have filled gaps around BIM usage.

If a client is a risk in this area then their lack of knowledge of BIM will only compound problems. Get an accurate picture of the client s experience in the project type and assess how BIM will be used. Clients need to understand that the complexity of design and construction has materially changed in the last 10 years and will change immensely as BIM is employed by the entire AEC industry. In addition, design error is the claim trigger with MEPs 63 percent of the time, the highest of all disciplines.

Training and continuing education on BIM related issues and usage becomes increasingly more important. Match the BIM technical aspects of the project with the knowledge and abilities of the staff in the same way they would assign a seasoned architect, engineer or technologist to deal with building envelope or similar complex issues.

Not assign staff just because they re available or underutilized. A Identify staff that have proven BIM capabilities to be more strategic and closely aligned with the expected project outcomes. In addition, there is the human factor – the main problem of communication in the AEC community lies in the lack of stakeholders ability to empathize with the other parties involved v.

AE s should: Clearly define the level of Development LOD ev and the level of detail LOD et expected of all the participants and embed these in the BxP Have clearly understood BIM processes that focus on the deliverables and having the BIM Manager communicate this to the entire team Recognize that a schedule for the design and construction deliverables is as important as the overall construction schedule.

There is a close correlation between the processes of developing the building virtually and that of the reality in construction. Keep the owner and contractor if on the team involved in the progress. Create a culture that brings bad news into the open as soon as it s discovered and then deals with the issue quickly and correctly documenting the outcomes and communicating these amongst the teams Hold virtual coordination sessions to resolve conflicts.

Staff access to BIM project data held on the network servers shall be through controlled access permissions. Whether it is output to 2D CAD for subsequent drawing production or output for 3D visualisation or analysis, the preparation and methods adopted to compose the BIM will ultimately determine its successful application within other software packages and technologies.

The suitability of incoming data shall be confirmed prior to making it available project-wide through the project Shared area. Modifications shall only be carried out with the approval of the person responsible for co-ordination. Data shall be cleansed prior to importing, referencing or linking to the main model to remove any irrelevant or extraneous data that is not approved. CAD data may need be shifted to 0,0,0 prior to import.

Ownership of this cleansed data is transferred from the originator to the cleansing discipline. Cleansed data is stored within the discipline s WIP area unless deemed appropriate to share project-wide, in which case it is stored in the Shared area.

Where the BIM is required to deliver all of these purposes, the Project BIM Execution Plan needs to define at which stages of work and for which packages these purposes will be delivered. BIM data shall be prepared, checked and exchanged taking into account the requirements of any recipient software applications, to ensure that error free, reliable data is exchanged e. Example: When modelling structural frames, some analysis software may dictate that columns need to be stopped at each floor level regardless of whether, in reality they continue as a single length.

The appropriate export layer tables shall be used during export to CAD. This section deals with the principles of subdividing a model for the purposes of: multi-user access, operational efficiency on large projects, Inter-disciplinary collaboration.

The following practices shall be followed: The methods adopted for data segregation shall take into account, and be agreed by, all internal and external disciplines to be involved in the modelling.

No more than one building shall be modelled in a single file. Further segregation of the geometry may be required to ensure that model files remain workable on available hardware. In order to avoid duplication or co-ordination errors, clear definition of the data ownership throughout the life of the project shall be defined and documented. Element ownership may transfer during the project time-line this shall be explicitly identified in the Project BIM Execution Plan Document.

Construction joints such as podium and tower. Work packages and phases of work. Document sets Work allocation such as core, shell and interiors. Properly utilised, division of a model can significantly improve efficiency and effectiveness on projects of any size, but in particular multi-user projects.

Appropriate model divisions shall be established and elements assigned, either individually or by category, location, task allocation, etc. Division shall be determined by the lead designer in conjunction with the person responsible for co-ordination. To improve hardware performance only the required models should be opened. A project shall be broken into a sufficient number of models to avoid congestion in workflow. Where required, access permissions and model ownership shall be managed to avoid accidental or intentional misuse of the data.

In normal circumstances this period should be at least once per hour. Users shall not save without consideration for and resolution of any issues which arise to avoid delays to other team members. This may be either other parts of a project which are too big to manage in a single file, or data from another discipline or external company. Some projects require that models of single buildings are split into multiple files and linked back together in order to maintain manageable model file size.

In some large projects it is possible that all the linked models may never be brought together as one. Various container files will exist to bring model files together for different purposes. Task allocation shall be considered when dividing the model so as to minimise the need for users to switch between models. When referencing, the models must be positioned relative to the agreed project origin: – The real-world co-ordinates of a point on the project shall be defined and coordinated in all models, – The relationship between True North and Project North is correctly established Inter-Disciplinary Referencing Each separate discipline involved in a project, whether internal or external, shall have its own model and is responsible for the contents of that model.

A discipline can reference another discipline s Shared model for coordination. Agreed project coordinates and direction of North shall be agreed and documented at the outset. Each discipline shall be conscious that referenced data has been produced from the perspective of the author and may not be modelled to the required specification for other purposes.

In this case, all relevant parties shall convene to discuss the potential re-allocation of ownership. Should a team develop a starter model for a partner discipline, such as defining the structural model in conjunction with the architecture, this shall be done in a separate model which can then be referenced as required to allow development of the continued design. With models produced for Building Services, several disciplines may be collated in a single model, as a single piece of equipment may require connection to various services.

In this scenario, the model may be split in various ways. Concept Grade 1 – see Graded Component Creation elements shall be used to form categorised place-holders in the model. As the design develops, and precise materials and components are chosen, data will be added to the objects.

These concept objects can be swapped, individually or en-masse, for more specific Grade 2 or Grade 3 variants should a higher level of modelling detail be required. For structural components, indicative members which are representative of steel or concrete elements shall be used.

The frame shall be constructed from these placeholders. If the section size is known from an early stage it can be chosen from the libraries, but no assumptions shall be made by opting for a default section. Model initially created using concept grade components. Concept components substituted for Grade 2 or 3 components as design progresses. The graphical appearance is completely independent to the metadata included in the object.

For example, it is possible to have a Grade 1 Concept object with full manufacturer s data, cost and specification attached. This is particularly relevant to electrical symbols which may never exist as a 3D object. Component Grade 1 G1 Concept Simple place-holder with absolute minimum level detail to be identifiable, e.

Superficial dimensional representation. Created from consistent material: either Concept White or Concept Glazing. Component Grade 2 G2 Defined Contains relevant metadata and technical information, and is sufficiently modelled to identify type and component materials. Typically contains level of 2D detail suitable for the preferred scale. Sufficient for most projects. Component Grade 3 G3 Rendered Identical to the Grade 2 version if scheduled or interrogated by annotation.

Differs only in 3D representation. Components may appear more than once in the library with different grades and the naming must reflect this. When in doubt, users should opt for less 3D geometry, rather than more, as the efficiency of the BIM is largely defined by the performance of the components contained within.

Adherence to the above grading and Model Development Methodology may result in multiple versions of the same element existing at different grades. This is accommodated in the object naming strategy defined in Section 8.

Further purposes of the BIM will lead to additional specifications of the content, which should be built to suit the purposes of the deliverables. Objects generated in the development of a project will be stored in the WIP area of the project folder structure. The person responsible for co-ordination will assess and verify minimum quality compliance before submitting new objects to the corporate library stored in the central resource folder. The intended purpose of the components shall be considered and the results checked and verified prior to large scale use.

For instance, structural analysis applications may require elements with certain naming conventions or other criteria, without which they will not be recognised. Too little and the information will not be suitable for its intended use; too much and the model may become unmanageable and inefficient.

It shall be dictated in the Project BIM Execution Plan the point at which 3D geometry ceases and 2D detailing is utilised to prepare the published output.

Intelligent 2D linework shall be developed to accompany the geometry and enhance the required views without undue strain on the hardware. Detailing and enhancement techniques shall be used whenever possible to reduce model complexity, but without compromising the integrity of the model. Fully assembled compilation of views and sheets within the BIM environment preferred.

Export views in the form of output files for assembly and graphical enhancement using 2D detailing tools within a CAD environment. Whichever methodology is chosen, the 3D model shall be developed to the same maximum extent before 2D techniques are applied. Be produced to true height above project datum.

Adopt the established project coordinate system across all BIM files to allow them to be referenced without modification. In order to comply with these rules, models should always be constructed the centre point 0,0,0 of the file, as information becomes less accurate and may cause significant errors the further it is from this location.

Real world coordinate values shall then be assigned to a known point of the model using the relevant BIM authoring software tools. Files that do not use this methodology and are drawn in true space need to be shifted to 0,0,0 prior to import into the BIM. Data exported from the BIM can then be either real world or local and whilst the majority of data will need to be delivered in OS co-ordinates for the purposes of collaboration and cross-referencing, some software e.

For export to such software, local coordinate systems can be utilised. CIPS takes the view that the outsourcing of services to specialist providers can often lead to better quality of services and increased value for money. Purchasing and supply management professionals should. Fourth generation techniques 4GT The term fourth generation techniques 4GT encompasses a broad array of software tools that have one thing in common.

Each enables the software engineer to specify some. All rights reserved. This document is provided for the intended. Software B. CAD Methods 1. Layer Standards 2.

 

– Step01/13-autodesk revit architecture 2011-german tutorial 1/3 free download

 
The design and evaluation of virtual learning environments for construction and surveying students is presented in this paper; by combining virtual learning. Part 13, section 82 of the Development Regulations (GovSA, a) buildings ( storeys or large scale multistorey)?. Furthermore, the Sendai area where ICCBEI will be held was affected by the disaster of the large earthquake in Especially, the.