Patent Description:
Reference is also made to the following patent publications of assignee:.

The present invention relates to construction engineering generally and more particularly to implementation of construction projects.

Various types of computer-aided engineering technologies are known in the prior art. <CIT> discloses an adaptive modelling of building during construction. <CIT> discloses a computation of point clouds and joint display of point clouds and building information models with project schedules for monitoring construction progress, productivity, and risk for delays. <NPL>, places focus on the utilization of BIM for quality management in highway and bridge construction.

The present invention seeks to provide improved methods and systems for construction engineering, particularly for large scale infrastructure projects such as roads.

There is thus provided in accordance with a preferred embodiment of the present invention a method for dynamic modeling of infrastructure projects over time, the method including receiving an infrastructure project design comprising: at least one of a three-dimensional view of an infrastructure project to be built and a set of two-dimensional views of the infrastructure project; and material layer defining information relating to the infrastructure project, defining a plurality of design volume-surface-objects (DVSOs), each corresponding to a material layer of the infrastructure project, ascertaining at least a volume of each of the DVSOs, repeatedly imaging the infrastructure project over time during construction thereof to produce multiple images acquired at a plurality of different times, automatically generating a point cloud representing the infrastructure project at each of the plurality of different times, based on the images, the point cloud including multiple points each having known Cartesian coordinates, automatically generating a surface mapping representing the infrastructure project at each of the plurality of different times, based on the point clouds, automatically generating a plurality of as-built volume-surface-objects (ABVSOs), each based on a pair of the surface mappings, each of the ABVSOs corresponding to one of the plurality of DVSOs, and employing the ABVSOs and the DVSOs for constructing and managing the infrastructure project.

Preferably, the set of two-dimensional views includes at least one horizontal alignment view of the infrastructure project, at least one vertical alignment view of the infrastructure project, and a multiplicity of sectional views taken perpendicular to the at least one horizontal view.

Preferably, the employing the ABVSOs and the DVSOs for constructing and managing the infrastructure project includes at least one of providing control instructions to construction machinery used in constructing the infrastructure project, accounting and paying for at least one of excavating and moving earth for constructing the infrastructure project, accounting and paying for materials used in the infrastructure project, monitoring progress of the infrastructure project vis-à-vis a predetermined schedule and monitoring progress of the infrastructure project vis-à-vis a pre-defined design.

Preferably, the method also includes graphically representing the infrastructure project at each of the plurality of different times.

In accordance with a preferred embodiment of the present invention, the imaging includes at least one of photographing by a camera and laser scanning.

Additionally or alternatively, the method also includes employing RTK GPS positioning techniques to enhance a precision of the multiple points including the point cloud.

In accordance with another preferred embodiment of the present invention, defining a plurality of DVSOs includes automatically defining at least one DVSO and automatically defining within the a least one DVSO sub-DVSOs included in the at least one DVSO.

Preferably, the method also includes assigning at least one parameter to the at least one DVSO, the sub-DVSOs included in the at least one DVSO automatically inheriting the at least one parameter from the at least one DVSO.

Preferably, the assigning at least one parameter includes at least one of assignation of a sub-contractor contracted to construct the at least one DVSO, assignation of scheduled start date for construction of the at least one DVSO, assignation of a scheduled completion date for construction of the at least one DVSO, and assignation of an identification number of the at least one DVSO.

Preferably, the method also includes importing at least one modeled finite element to be located at a location within the infrastructure project, from an external Building Information Modelling (BIM) platform having modeled the finite element to the plurality of DVSOs, and incorporating the at least one finite element within ones of the plurality of DVSOs corresponding to the location.

There is also provided in accordance with another preferred embodiment of the present invention a system for dynamic modeling of infrastructure projects over time, the system including a project design generator operative to generate an infrastructure project design including at least one of a three-dimensional view of an infrastructure project to be built and a set of two-dimensional views of the infrastructure project and material layer defining information relating to the infrastructure project, a design volume-surface-objects (DVSOs) generator operative to define a plurality of DVSOs, each corresponding to a material layer of the infrastructure project, a DVSO geometrical property calculator operative to ascertain at least one geometrical property of each of the DVSOs, an image generator operative to repeatedly image the infrastructure project over time during construction thereof to produce multiple images acquired at a plurality of different times, a point cloud generator operative to automatically generate a point cloud representing the infrastructure project at each of the plurality of different times, based on the images, the point cloud including multiple points each having known Cartesian coordinates, a surface mapping generator operative to automatically generate a surface mapping representing the infrastructure project at each of the plurality of different times, based on the point clouds, an As-Built Volume-Surface Object generator operative to automatically generate a plurality of as-built volume-surface-objects (ABVSOs), each based on a pair of the surface mappings, each of the ABVSOs corresponding to one of the plurality of DVSOs and project construction and management functionality operative to employ the ABVSOs and the DVSOs for constructing and managing the infrastructure project.

Preferably, the set of two-dimensional views includes at least one horizontal alignment view of the infrastructure project, at least one vertical alignment view of the infrastructure project and a multiplicity of sectional views taken perpendicular to the at least one horizontal view.

Preferably, the project construction and management functionality is operative to at least one of provide control instructions to construction machinery used in constructing the infrastructure project, account and pay for at least one of excavating and moving earth for constructing the infrastructure project, account and pay for materials used in the infrastructure project, monitor progress of the infrastructure project vis-à-vis a predetermined schedule and monitor progress of the infrastructure project vis-à-vis a pre-defined design.

Preferably, the project construction and management functionality also includes project reporting functionality operative to graphically represent the infrastructure project at each of the plurality of different times.

In accordance with a preferred embodiment of the present invention, the image generator includes at least one of a camera and a laser scanner.

Additionally or alternatively, the image generator includes RTK GPS positioning equipment.

Preferably, the DVSO generator is operative to automatically define at least one DVSO and to automatically define within the a least one DVSO sub-DVSOs included in the at least one DVSO.

Preferably, the DVSO generator is operative to assign at least one parameter to the at least one DVSO, the sub-DVSOs included in the at least one DVSO automatically inheriting the at least one parameter from the at least one DVSO.

Preferably, the DVSO generator being operative to assign at least one parameter to the at least one DVSO includes at least one of assignation of a sub-contractor contracted to construct the at least one DVSO, assignation of scheduled start date for construction of the at least one DVSO, assignation of a scheduled completion date for construction of the at least one DVSO, and assignation of an identification number of the at least one DVSO.

Preferably, the system is further operative to import at least one modeled finite element to be located at a location within the infrastructure project, from an external Building Information Modelling (BIM) platform having modeled the finite element to the plurality of DVSOs, and to incorporate the at least one finite element within ones of the plurality of DVSOs corresponding to the location.

The present invention will be understood and appreciated from the following detailed description, taken in conjunction with the drawings in which:.

Reference is now made to <FIG>, which is a simplified functional block diagram of a construction management system constructed and operative in accordance with a preferred embodiment of the present invention.

The construction management system of the present invention combines the use of design data, such as design data generated by conventional computerized design systems and software, and empirical data, such as data derived from aerial photographs, to define and employ design volume-surface-objects (DVSOs) and as-built volume-surface-objects (ABVSOs) generated at various times for implementation of construction projects, monitoring and reporting progress and accounting throughout the duration of construction projects and maintenance following completion of the construction project.

While it is appreciated that the system and method of the present invention may be employed in any suitable construction project, the system and method of the present invention are particularly suitable for use in large construction projects, such as road building. Accordingly, much of the description which follows relates to the use of the invention in the context of a road building project.

Referring to <FIG>, it is seen that a construction management system <NUM> of the present invention may comprise a project design generator <NUM>. Initially a project design, such as an infrastructure design, is generated by the project design generator <NUM>. Examples of suitable project design generators <NUM> include workstations, such as a conventional PC or workstation running AutoCAD Civil 3D software, commercially available from Autodesk, Inc. of San Rafael, CA, USA.

The project design produced by the project design generator <NUM> may include a set of two-dimensional views of the project. The set of two-dimensional views preferably includes at least one horizontal alignment view of the project. An example of a horizontal alignment view of a portion of a road project appears in <FIG> references a start point, which is an arbitrary point along the road to be built, from which the view begins. In the example of <FIG>, it is seen that the road curves initially to the right, and thereafter to the left and thereafter to the right.

Preferably, the set of two-dimensional views of the project produced by the project design generator <NUM> also includes at least one vertical alignment view of the project. An example of a vertical alignment view of a portion of a road project appears in <FIG> preferably also references a start point, which is an arbitrary point along the road to be built, from which the view begins. In the example of <FIG>, it is seen that the road dips initially and then rises and thereafter dips.

Additionally, the set of two-dimensional views of the project produced by the project design generator <NUM> also preferably includes a multiplicity of sectional views taken perpendicular to the progression of the horizontal view of <FIG>. An example of such a sectional view in a road-building project appears in <FIG> and shows not only the cross-sectional topography at the outset of the project but also the cross-sectional configuration of the proposed finished road and its surrounding right of way. In road building design, preferably sectional views are generated at a multiplicity of locations spaced from each other by approximately <NUM> meters all along the length of the road to be built.

Additionally or alternatively, the project design generator <NUM> may produce a three-dimensional (3D) view of the project. An example of 3D view of a portion of a road project appears in <FIG>.

Further, the project design produced by the project design generator <NUM> also preferably includes material layer defining information, indicating the structural elements incorporated in the project. Such information may be in the form of an image, such as that which appears in <FIG>, and shows a cross-sectional configuration and thicknesses of the various material layers in a road to be built. The project design generator may include only one material layer defining view, such as that shown in <FIG>, or more than one material layer defining view, depending on the specific material layer structure of the project. It is understood that in the case that project design generator produces a 3D design view, such a 3D design view may in some instances include material layer defining information, such that no additional material layer defining view is required.

Returning to <FIG>, a Design Volume-Surface-Objects (DVSOs) Generator <NUM>, receives the above-described data from the project design generator <NUM> and, preferably automatically, generates a plurality of Design-Volume-Surface Objects (DVSOs). DVSOs may be any suitable constructed object. In the context of road building, each separate material layer, such as each of the material layers shown in <FIG>, may be a DVSO.

The material volume of the DVSO is preferably calculated by a DVSO Geometrical Property Calculator <NUM> and subsequently employed for project progress reporting and accounting, as is described in greater detail henceforth. It is understood that DVSO Geometrical Property Calculator <NUM> is not limited to calculating the volume of the DVSO, but may also calculate other geometrical properties of the DVSO, including, for example, surface area, surface length, slope, and any other relevant properties.

The generation of DVSOs by DVSO generator <NUM> may be better understood with additional reference to <FIG>, which is a simplified conceptual illustration of automatically generated DVSOs in the context of a road to be built.

As seen in <FIG>, a portion <NUM> of a road to be built may comprise multiple layers <NUM>, which layers <NUM> are automatically derived from the data input to DVSO generator <NUM> from project design generator <NUM>. Each of layers <NUM> may be defined by two surfaces, such as an upper surface <NUM> and a lower surface <NUM>, illustrated with respect to one of layers <NUM>. Upper and lower surfaces <NUM> and <NUM> may be linearly connected to one another at boundaries thereof by linear connecting lines <NUM>. It is appreciated that upper and lower surfaces <NUM> and <NUM>, connected at boundaries thereof by linear connecting lines <NUM>, enclose and define a volumetric geometrical unit <NUM>. Such a volumetric geometrical unit <NUM> may be automatically generated by DVSO generator <NUM> for each of layers <NUM> of road portion <NUM>.

DVSO generator <NUM> is preferably operative to create a computerized volumetric virtual memory unit corresponding to and representing each volumetric geometrical unit <NUM>. The volumetric geometrical unit <NUM> and the volumetric virtual memory unit by which the volumetric geometrical unit <NUM> may be represented are referred to interchangeably herein as a volume-surface-object (VSO). The volume of each VSO, as enclosed by the bounding lines and surfaces thereof (for example, <NUM>, <NUM> and <NUM>) may be automatically calculated by DVSO calculator <NUM>.

It is appreciated that layers <NUM> and VSOs <NUM> defined based thereon are shown in an even, staggered highly simplified configuration in <FIG> for the purpose of simplicity and clarity of presentation thereof. In actuality, layers <NUM> may have mutually different sizes and shapes and be arranged in various fully or partially overlying configurations with respect to one another, depending on the design of the project to be built.

Returning to <FIG>, DVSO parameter assigning functionality <NUM> preferably assigns parameters to the DVSOs generated by DVSO generator <NUM>.

Each VSO preferably has the properties of a computerized data object and may contain a number of parameters, computational functions or links to other VSOs or databases. By way of example only, as shown in <FIG>, a VSO such as VSO <NUM> may contain parameters such as the name of the material comprising the VSO <NUM>, the task ID assigned to the VSO <NUM>, the design volume of the VSO <NUM>, the design area of the VSO <NUM>, the name of the sub-contractor responsible for constructing the VSO <NUM>, the bill of quantities associated with the VSO <NUM> and the time schedule and tasks associated with the VSO <NUM>, such as the planned start and completion date of the VSO. Other relevant properties may be added, depending on the particular nature of the project to be constructed. These parameters are assigned by DVSO parameter assigning functionality <NUM> based on the relevant parameters being input to DVSO parameter assigning functionality <NUM> in the form of the various design data generated by project design generator <NUM>, as well as from other external data sources, such as, by way of example only, MS Project files, Primavera and SKN.

The generation of VSOs thus allows automatic partition of the project to be built, such as a road, into discrete 3D units, which units enable and form the basis of BIM management of the project, as is described in further detail henceforth.

In one preferred embodiment of the system of the present invention, each VSO may contain sub-VSOs in a tiered manner. For example, DVSO generator <NUM> may automatically define a primary or top tier DVSO as the entirety of the road portion <NUM>, based on the top-most and bottom-most surfaces thereof. Within that top tier VSO, second tier sub-VSOs may be automatically defined, corresponding to individual material layers <NUM> within road portion <NUM>, such as VSOs <NUM> shown in <FIG>. Some or all of these sub-VSOs may be further partitioned into third tier sub-sub VSOs, such as third tier sub-sub VSOs <NUM> of second tier sub-VSOs <NUM>, shown in <FIG> and corresponding to sub-material layers within ones of the second tier sub-VSOs. Lower tier sub-VSOs, such as VSOs <NUM> and <NUM> may automatically inherit parameters of higher tier 'parent' VSOs in order to simplify the assignment of parameters between VSOs by parameter assigning functionality <NUM>. Thus, for example, parameters of the top tier VSO representing the entirety of road portion <NUM> may be automatically assigned once to the top tier VSO and then automatically bequeathed to lower tier VSOs, such as VSOs <NUM> and <NUM>, partitioned from within the top tier VSO.

The automatic partition of the road into multiple tiers of VSOs and the automatic inheritance by lower tier VSOs of parameters associated with upper tier VSOs may be modified by a user of system <NUM>. For example, a user of system <NUM> may modify the automatic partition of VSOs to select additional or alternative VSOs and/or may adjust the parameters thereof.

Additionally, 3D finite BIM elements may be imported into system <NUM> and integrated with the DVSOs defined by DVSO generator <NUM>. Such BIM finite elements may then be handled by system <NUM> as DVSOs and assigned the same parameters and functionalities as DVSOs. An example of an imported finite element in the form of a pipe <NUM> is shown in <FIG>. As seen in <FIG>, pipe <NUM> may be located within DVSO <NUM> and span several ones of sub-DVSOs <NUM>. A volume of DVSOs <NUM> and relevant ones of sub-DVSOs <NUM> may be automatically adjusted by DVSO calculator <NUM> to take into account the presence of pipe <NUM>. Furthermore, the importation of finite BIM elements from other BIM platforms into system <NUM> may be useful in assessing potential geometrical conflicts between the positions of such elements within the project to be built.

Returning to <FIG>, in accordance with a preferred embodiment of the present invention, the project is then imaged, preferably by an Image Generator <NUM>. Image generator <NUM> may be embodied as a photograph generator, employing one or more drones and photograph compositing software, and photographing the project at selected time intervals, which may be predetermined and may be periodic, such as weekly, throughout the duration of the project. Multiple photographs are produced and stored by the photograph generator <NUM>.

Additionally or alternatively, image generator <NUM> may include one or more laser scanning machines, which laser scanning machines may be terrestrial, mobile and/or airborne. An example of a laser scanner suitable for use as image generator <NUM> is a Laser Scanner machine commercially available from Leica Geosystem of St. Gallen, Switzerland or Trimble Inc. of Sunnyvale, CA, USA.

Further additionally or alternatively, image generator <NUM> may include an RTK GPS or Total Station measurement system. RTK GPS equipment is commercially available from geodetic geospatial providers, such as Leica Geosystem of St. Gallen, Switzerland, Trimble Inc. of Sunnyvale, CA, USA, or Topcon Positioning of Tokyo, Japan. RTK GPS or Total Station measurements may be used as stand-alone measurement systems. Alternatively, RTK GPS or Total Station measurements may be used in combination with photographs and/or laser scanning, in order to enhance the precision of point clouds generated based thereon.

It is a particular feature of an embodiment of the present invention that information from the image generator <NUM> is employed by a Point Cloud Generator <NUM> for automatically generating a point cloud representing the project at each of the plurality of different times, the resulting point cloud including a multiplicity of points each having known Cartesian coordinates.

The Point Cloud Generator182 preferably generates a point cloud by one of several methods. In a first method, Point Cloud Generator <NUM> generates the point cloud based on laser images measured by laser scanning machines, which measure thousands of points and generate X, Y, Z coordinates by distance and angle measurements. In a second method, the Point Cloud Generator <NUM> generates a point cloud using conventional photo-scan generation algorithms, based on computer vision science that converts a set of images taken by a digital camera, in a way that preserves overlaps between images of the same photographed area, to point clouds. These algorithms are typically software implemented, such as Agisoft Metashape software, commercially available from Agisoft LLC of St. Peterburg, Russia, Pix4D mapper software, commercially available from Pix4D S. of Prilly, Switzerland, or DatuSurvey software, commercially available from Datumate, Yoqneam Ilit, Israel.

Real Time Kinematic (RTK) GPS or Total Station measurements may be used to enhance the precision of the points in the point cloud. Furthermore, point cloud generator <NUM> may additionally receive multi-sensor datasets, including infrared and spectral data relating to the imaged project. Data from these data sets may be integrated within the point cloud, by combining the sensed data with the points forming the point cloud.

In a third method, the Point Cloud Generator <NUM> generates a point cloud using RTK GPS or Total Station measurements. It is appreciated that Point Cloud Generator may generate a point cloud in accordance with a combination of these methods or any other suitable method or methods, as may be known in the art.

Irrespective of the particular type or types of data received by point cloud generator <NUM>, point cloud generator <NUM> is preferably operative to calculate the precision and accuracy of each data set provided thereto, eliminate artefacts therein and perform data smoothing in order to generate the point cloud. Furthermore, point cloud generator <NUM> may characterize the data set in terms of the geodetic quality thereof based the resolution, precision and accuracy of the data set. The precision and accuracy of the data set on which the point cloud is based may be provided to a user of system <NUM>.

The point cloud is preferably employed by a Surface Mapping Generator <NUM> for automatically generating a surface mapping representing the project at each of the plurality of different times that the project is imaged, based on the point clouds.

Surface Mapping Generator <NUM> preferably generates a surface mapping using one or more conventional algorithms, for example using triangulation methods or grid methods, based on one or more of grid points, random points point cloud, Contour Lines or Horizontal Profile, as seen in <FIG>. It is understood that the surface mapping methods illustrated in <FIG> are by way of example only and that any suitable surface mapping methods, various types of which are known in the art, may be employed. More preferably, surface mapping generator184 generates a surface based on either contour lines for building the DVSO given by designers or by using one or more of the horizontal alignment, as seen in <FIG>, the vertical profile, as seen in <FIG>, the horizontal profile, as seen in <FIG>, the 3D design view, as seen in <FIG>, and the road layer structure, as seen in <FIG>.

The surface mapping is preferably employed by an As-Built Volume-Surface-Objects (ABVSOs) Generator <NUM>, which generates each ABVSO, preferably based on a pair of surface mappings at two points in time. It is a particular feature of an embodiment of the present invention that each of the ABVSOs corresponds to one of said plurality of DVSOs.

ABVSO generator <NUM> preferably generates an ABVSO utilizing two as-built surfaces, the first as-built surface being generated from images taken at an initial point in time and representing a first, lower surface of the ABVSO and the second as-built surface being generated from images taken at a later point in time and representing a second, upper surface of the ABVSO. The pair of as-built surfaces may, but do not necessarily, correspond to two immediately sequential points in time. The as-built surface is preferably based on a point cloud, generated as described above using cameras and/or laser scanners, and/or may be based on plural arbitrary measured points X, Y, Z or grid points X, Y, Z, which may be derived by known geodetic measurement instruments, such as a Real Time Kinematic (RTK) GPS, commercially available from geodetic geospatial providers, such as Leica Geosystem of St. Gallen, Switzerland, Trimble Inc. of Sunnyvale, CA, USA, or Topcon Positioning of Tokyo, Japan.

It is appreciated that As-Built surfaces are based on the same coordinate system as the coordinate system used in the design on which the DVSO is based, preferably, utilizing Ground Control Points (GCPs) measured in the field during the Point Cloud and the plural points generation.

ABVSO generator <NUM> preferably generates each ABVSO by linearly connecting boundaries of the two as-built surfaces, so as to define and enclose a volumetric geometrical unit, the volume of which may be calculated by an ABVSO geometric property calculator <NUM> and subsequently employed for project progress reporting and accounting, as is described in greater detail henceforth. It is understood that ABVSO Geometrical Property Calculator <NUM> is not limited to calculating the volume of the ABVSO, but may also calculate other geometrical properties of the ABVSO, including, for example, surface area, surface length, slope, and any other relevant properties.

ABVSO generator <NUM> is preferably operative to create a computerized volumetric virtual memory unit corresponding to and representing each ABVSO. The as-built volumetric geometrical unit and the volumetric virtual memory unit by which the as-built volumetric geometrical unit may be represented are referred to interchangeably herein as an As Built volume-surface-object (VSO). Parameters may, although are not necessarily assigned, to some or all of the ABVSOs. For example, actual costs incurred to date in constructing the ABVSO may be input to system <NUM> by a user thereof or a photograph of the as-built surface may be assigned to the ABVSO.

The system of the present invention preferably automatically classifies each ABVSO to a DVSO based on the 3D position of the ABVSO in the same coordinate system of the design, as seen in <FIG>, wherein an upper surface <NUM> of an ABVSO is located within a material layer <NUM> of the road design and thus classified as matching the DVSO corresponding to that material layer <NUM>. Once a particular ABVSO has been classified as matching a given DVSO, the system of the present invention may automatically assign to the particular ABVSO those parameters previously assigned to the given DVSO corresponding to the ABVSO. However, such parameters may be modified or added to by a user of system <NUM>.

ABVSOs are typically defined progressively by adding As-Built surfaces during the monitoring progress life cycle each time a mapping process is done by a user in the field using one or more of the following methods: taking images by drone and generating point cloud by photo-scan algorithm, laser scanning using one or more Laser Scanner machines, and/or using RTK GPS geodetic measurements machines for plural points coordinates dataset, and/or any other suitable image generating mapping process. The most recent Surface As-Built added will be the top surface defined in the ABVSO in the system of the present invention.

It is a particular feature of an embodiment of the present invention that the system is operative to store each DVSO and the corresponding ABVSO for each time that the project is imaged or measured. By comparing the ABVSOs to each other and to the DVSO, Project Construction, Reporting and Accounting Functionality <NUM> may automatically produce construction implementation instructions, progress reports and quantity reports based on each individual DVSO and corresponding ABVSO.

Comparing the ABVSOs to each other and to the corresponding DVSOs may involve a variety of types of comparisons performed between ABVSOs and DVSOs corresponding thereto and/or between the same ABVSOs at different points in time, based on which computerized analytics and reports useful to a user of the present invention may be automatically generated. Such analytics may be provided with respect to entire or portions of specific, individual ABVSOs and corresponding DVSOs, or with respect to multiple ABVSOs and corresponding DVSOs.

By way of example, a geometric comparison may be performed between an ABVSO and the DVSO corresponding thereto. Such a geometric comparison may involve computing differences, in three dimensions, between the ABVSO and the DVSO corresponding thereto, including differences in volume and area.

Further by way of example, a geometric comparison may be performed between ABVSOs at two different points in time, which ABVSOs correspond to the same DVSO. Such a geometric comparison may involve computing differences between one or more geometric parameters of the ABVSOs at two different points in time and/or one or more of the geometric parameters of the ABVSOs at two different points in time relative to one or more geometric parameters of the corresponding DVSO. Relevant geometric parameters to be computed may include, but are not limited to, volume, surface area, length and incline. Such a comparison may be useful for cost computation and future cost prediction.

Further by way of example, comparisons between ABVSOs corresponding to the same DVSO and between ABVSOs and the DVSOs corresponding thereto may be performed based on the time and schedule parameters thereof. This may involve computing the expected date at which an ABVSO will be completed, based on the past progress thereof, versus the design schedule of the DVSO corresponding to the ABVSO, in order to predict whether the ABVSO will meet the scheduled completion date. A computerized output may be provided to a user displaying whether or not the ABVSO is expected to meet the deadline thereof.

Further by way of example, comparisons between ABVSOs corresponding to the same DVSO and between ABVSOs and the DVSOs corresponding thereto may be performed based on cost and budget data associated therewith. For example, budgeted costs associated with a DVSO, for example by DVSO parameter assigning functionality <NUM> of <FIG>, may be compared to actual costs incurred in constructing the ABVSO corresponding thereto or the remaining cost expected to be involved in construction of the ABVSO may be calculated.

By way of example, based on comparing individual DVSOs to the ABVSOs corresponding thereto, control instructions may be provided to construction machinery used in constructing the project; based on comparing individual DVSOs to the ABVSOs corresponding thereto, accounting and paying may be carried out for at least one of excavating and moving earth for constructing the infrastructure project; accounting and paying may be carried out for materials used in the infrastructure project; progress of the project may be monitored vis-à-vis a predetermined schedule; and progress of the project may be monitored vis-à-vis a pre-defined design.

Furthermore, functionality <NUM> may include graphically representing the project at various times during the construction thereof, together with associated data, such as volume or area of the ABVSO, of interest to a user. The data may be presented to a user together with the accuracy thereof, for example as a ± error range, in order to allow the user to assess the accuracy of the data.

The method of the present invention, as may be performed by system <NUM>, is shown generally in <FIG> and <FIG> and in the context of road building in <FIG> and <FIG>.

Turning first to <FIG> and <FIG>, a method <NUM> in accordance with a preferred embodiment of the present invention may include, at a first step <NUM>, receiving an infrastructure project design including at least a 3D design view of an infrastructure project to be built and/or a set of 2D design views of the infrastructure project to be built. The set of 2D design views preferably includes at least one horizontal alignment view of the project to be built, one vertical alignment view of the project to be built and a multiplicity of sections taken perpendicular to the at least one horizontal alignment view. In addition to the 3D view and/or set of 2D views, at least one material layer defining view is also received at step <NUM>. It is understood that in the case that first step <NUM> includes receiving a 3D design view, such a 3D design view may in some instances include material layer defining information, such that no additional material layer defining view is required.

As seen at a second step <NUM>, method <NUM> further preferably includes defining a plurality of DVSOs, each corresponding to a material layer and calculating a volume of each of these DVSOs, as seen at a third step <NUM>. As seen at a fourth step <NUM>, method <NUM> further includes assigning parameters to each DVSO. As seen at a fifth step <NUM>, method <NUM> further includes imaging the infrastructure project over time, during the construction thereof, so as to produce multiple images at a plurality of different times.

As seen at a sixth step <NUM>, based at least on the multiple images, method <NUM> preferably includes automatically generating a point cloud representing the infrastructure project at each of the plurality of different times, each point cloud including multiple points each of which has known Cartesian coordinates.

As seen at a seventh step <NUM>, method <NUM> further preferably includes automatically generating surface mapping representing the infrastructure project at each of the plurality of different times based on the cloud points. As seen at an eighth step <NUM>, method <NUM> further preferably includes generating a plurality of ABVSOs, ABVSO being based on a pair of surface mappings taken at two different points in time, each ABVSO corresponding to a DVSO. Further, as seen at a ninth step <NUM>, the ABVSOs and DVSOs are preferably employed for constructing the infrastructure project.

Turning now to <FIG> and <FIG>, a method <NUM> in accordance with another preferred embodiment of the present invention may include, at a first step <NUM>, receiving a road design including at least a 3D design view of a road to be built and/or a set of 2D design views of the road to be built. The set of 2D design views preferably includes at least one horizontal alignment view of the road to be built, one vertical alignment view of the road to be built and a multiplicity of sections taken perpendicular to the at least one horizontal alignment view. In addition to the 3D view and/or set of 2D views, at least one material layer defining view is also received at step <NUM>. It is understood that in the case that first step <NUM> includes receiving a 3D design view, such a 3D design view may in some instances include material layer defining information, such that no additional material layer defining view is required.

As seen at a second step <NUM>, method <NUM> further preferably includes defining a plurality of DVSOs, each corresponding to a material layer and calculating a volume of each of these DVSOs, as seen at a third step <NUM>. As seen at a fourth step <NUM>, method <NUM> further includes assigning parameters to each DVSO. As seen at a fifth step <NUM>, method <NUM> further includes imaging the road over time, during the construction thereof, so as to produce multiple images at a plurality of different times.

As seen at a sixth step <NUM>, based at least on the multiple images, method <NUM> preferably includes automatically generating a point cloud representing the road at each of the plurality of different times, each point cloud including multiple points each of which has known Cartesian coordinates.

As seen at a seventh step <NUM>, method <NUM> further preferably includes automatically generating surface mapping representing the road at each of the plurality of different times based on the point clouds. As seen at an eighth step <NUM>, method <NUM> further preferably includes generating a plurality of ABVSOs, ABVSO being based on a pair of surface mappings taken at two different points in time, each ABVSO corresponding to a DVSO. Further, as seen at a ninth step <NUM>, the ABVSOs and DVSOs are preferably employed for constructing the road.

Certain components of the system and method of the present invention for dynamic modelling of infrastructure projects over time, as described hereinabove with reference to <FIG>, may be executed by a processor, for example by a processor of local server or cloud based server. In accordance with embodiments of the present invention, a computer program application stored in a computer readable medium (e.g. register memory, processor cache, RAM, ROM, hard drive, flash memory, CD ROM, magnetic media, etc.) may include code or executable instructions that when executed may instruct or cause a controller or processor to perform one or more of the functionalities and methods discussed herein, such as a method for dynamically modelling infrastructure projects over time based on employing DVSOs and ABVSOs, in accordance with the present invention. The computer readable medium may be a non-transitory computer readable medium including all forms and types of computer-readable media.

Claim 1:
A method (<NUM>) for dynamic modeling of infrastructure projects over time, the method comprising:
receiving (<NUM>) an infrastructure project design comprising:
at least one of a three-dimensional view of an infrastructure project to be built and a set of two-dimensional views of said infrastructure project; and
material layer defining information relating to said infrastructure project;
defining (<NUM>) a plurality of design volume-surface-objects (DVSOs), each corresponding to a material layer of said infrastructure project;
ascertaining at least a volume of each of said DVSOs; repeatedly imaging (<NUM>) said infrastructure project over time during construction thereof to produce multiple images acquired at a plurality of different times;
automatically generating (<NUM>) a point cloud representing said infrastructure project at each of said plurality of different times, based on said images, said point cloud including multiple points each having known Cartesian coordinates;
automatically generating (<NUM>) a surface mapping representing said infrastructure project at each of said plurality of different times, based on said point clouds;
automatically generating (<NUM>) a plurality of as-built volume-surface-objects (ABVSOs), each based on a pair of said surface mappings comprising a first as-built surface generated from images taken at an initial point in time and representing a first, lower surface of the ABVSO and a second as-built surface generated from images taken at a later point in time and representing a second, upper surface of the ABVSO each said ABVSO being generated by linearly connecting boundaries of said two as-built surfaces, so as to define and enclose a volumetric geometrical unit, each of said ABVSOs corresponding to one of said plurality of DVSOs; and
employing (<NUM>) said ABVSOs and said DVSOs for constructing and managing said infrastructure project.