You are browsing the archive for infrastructure.

Bentley Adds Geotechnical and Geoenvironmental Capabilities Through Acquisition of gINT Software

October 13, 2009 in Bentley, CAD

CHARLOTTE, N.C. – Be Inspired: Infrastructure Best Practices Symposium and Awards – Bentley Systems, Incorporated, the leading company dedicated to providing comprehensive software solutions for the infrastructure that sustains our world, today announced, at this invitation-only gathering of top users from around the globe, that it has acquired gINT Software.
Source: Bentley News – Bentley Adds Geotechnical and Geoenvironmental Capabilities Through Acquisition of gINT Software
Go to Source: Bentley News

Bentley Announces Winners of 2009 Be Inspired Special Recognition Awards

October 9, 2009 in Bentley, CAD

Bentley Systems, Incorporated, the leading company dedicated to providing comprehensive software solutions for the infrastructure that sustains our world, will announce the winners of its 2009 Be Inspired Awards next week during its Be Inspired: Infrastructure Best Practices Symposium and Awards in Charlotte, N.C.
Source: Bentley News – Bentley Announces Winners of 2009 Be Inspired Special Recognition Awards
Go to Source: Bentley News

GIS Databases Negatively Impacted by As-Built Problem

August 4, 2009 in AutoCAD, CAD

I just returned from Dallas, Texas this week where I delivered a seminar discussing data to design workflows and CAD/GIS integration. During the seminar, which was hosted by Expert Computing Solutions, an interesting discussion on the topic of the as-built backlog arose. Recall from one of my previous posts that the as-built backlog refers to the delay between when infrastructure has been constructed and when information about this construction is entered into GIS and records databases. According to seminar participants, that delay ranges anywhere from a few months to several years. Some participants revealed an indefinite delay; in other words, their databases were never up-to-date!

So, what are the problems of such a delay? What are the consequences of not having an up-to-date GIS database? Well, the impacts are many; listed below are just a few…

Poor decision making: Out-of-date information about the type, location and other related attributes about the above and below ground infrastructure can lead to inaccuracies in predicating future repair and maintenance requirements which can lead to decreased infrastructure life expectancy and premature replacement.

Decreased efficiency: When work orders are based on out-of-date databases, field activities are impacted; for example, when crews are dispatched in response to a repair or routine maintenance request only to find that upon arriving at the field location that they have the wrong equipment, crews must make a trip back to the warehouse to retrieve the correct piece of equipment. The result is an inefficient use of resources with time, dollars and fuel all wasted.

Re-work: Re-work occurs when the information in the GIS database must continually be verified against paper as-built drawings simply because this as-built information had not been loaded into the database yet.

Data confidence: When users know that the corporate database is not current, confidence in the data can be eroded to the point where users stop relying on the corporate database in favor of their own records. The result is data redundancy and all its corresponding problems.

Insufficient budgets: When infrastructure budgets are derived from out-of-date databases, a budget shortfall becomes a real possibility, especially in areas of rapid growth.

Environment and public safety issues: Worse yet, when users trust out-of-date information, bad decisions can be made – decisions which can harm the environment, impact public safety and create liability exposure. For example, according to the National Post, trusting old design drawings proved to be a costly mistake, when a contractor ruptured a crude oil pipeline in Burnaby, BC almost two years ago. The result was a toxic geyser that spewed almost a quarter of a million litres of crude oil onto residences, streets and into the Pacific Ocean.

Inaccurate regulatory reports: The accuracy of reports on capital assets in response to regulatory requirements such as PSAB 3150 and GASB 34 becomes suspect when based on GIS databases that are suppose to have a current inventory of above and below ground infrastructure but instead are potentially years out-of-date.

I’m sure the as-built problem generates additional consequences. However, given the above, can corporate GIS databases that are months or years out-of-date really be trusted? Caution is prudent.


If you know of other as-built related issues or have related comments, I would enjoy hearing from you…

Source: geoExpressions – GIS Databases Negatively Impacted by As-Built Problem
Go to Source: geoExpressions

GIS Skills for the Engineering and CAD Professional

August 4, 2009 in AutoCAD, CAD

ENGIS: It's not Engineering or GIS; it's Engineering and GIS!

Last week I had the pleasure of visiting Calgary, Alberta and facilitating a half-day seminar aimed at demonstrating the crucial GIS skills needed by engineering and CAD professionals. This well attended seminar, hosted by Pacific Alliance Technologies, highlighted the differences between CAD and GIS workflows, reviewed the obstacles to CAD/GIS integration and discussed the importance of an Engineering GIS approach.

I was expecting the audience to consist mainly of engineering and CAD folks. So, I was surprised to discover that there was a 50:50 mix of both CAD and GIS professionals. It turned out that some of the geospatial participants were looking for a better understanding of CAD related workflows. They also wanted information on how to work and better communicate with their engineering and CAD counterparts so that they could potentially simplify their geospatial data integration tasks and drive productivity. Similarly, some of the engineering and CAD participants were seeking pointers on how to overcome resistance to GIS within their own engineering organizations.

So, why is there this resistance to GIS by some engineering firms?

Well, engineering is about design; it’s about creating documents that have the exact amount of detail necessary to construct what was designed and then ensuring that construction proceeds according to specification. To these firms, construction represents completion and so their design documents and as-built drawings reflect that.

However, according to the National Institute of Standards and Technology, the cost of inadequate interoperability for U.S. capital facilities during the operation and maintenance phases is estimated at $9 billion US. If you include infrastructure, like bridges and roads, then these costs sky-rocket even further!

Design documents and as-built drawings must be created with a new end in mind.

Engineering and CAD professionals must create their design documents in such a way that the embedded geospatial data can be utilized throughout the infrastructure lifecycle. Design data must be easily integrated with corporate databases so that this information can be used during infrastructure operation and maintenance activities. Engineering GIS can help.

As the original creators of our infrastructure data, I believe engineering and CAD professionals have a responsibility to ensure that this information can be easily integrated throughout the infrastructure lifecycle. To do otherwise, simply contributes to the billions of dollars already wasted due to the lack of interoperability and poor data integration.

Source: geoExpressions – GIS Skills for the Engineering and CAD Professional
Go to Source: geoExpressions

As-built Backlogs Impact Accuracy of PSAB 3150 Reports

August 4, 2009 in AutoCAD, CAD

As of January 2009, Section 3150 of the Public Sector Accounting Board (PSAB 3150) requires Canadian municipalities to report on their tangible capital assets including roads, bridges, utilities, water systems, sewer networks and land. The accuracy of such a report is based, in part, on the currency of a municipality’s infrastructure inventory databases. However, these databases are often out-of-date due to the as-built backlog.

The as-built backlog refers to the delay experienced between when infrastructure has been constructed and when information about this construction is entered into the records database. These delays often span months and sometimes years and make it difficult to provide reliable information about the infrastructure for field, management and regulatory requirements such as PSAB 3150.

The as-built backlog refers to the time needed to add construction data to the records database after construction is completeThe as-built workflow can be explained with an example. A new subdivision project typically starts by assembling a collection of cadastral maps, existing infrastructure data and other information from a variety of sources to create a base map. Subdivision design is next; new infrastructure is drafted, existing infrastructure is updated and detailed design drawings for construction are created. Then construction takes place and upon completion, information about the construction is collected and compared to the design documents to create an as-built drawing. This as-built information is then used to update the infrastructure inventory database.

The as-built problem arises for several reasons:

  • Accelerated development during booming economies often means that engineering and construction firms have all-hands-on-deck to keep up with construction demand. Consequently, creating as-built drawings is sometimes just not a priority.
  • As-built drawings are often created from paper design documents that contain redline markups describing the as-constructed information. These paper documents are then re-drafted to create an electronic version that is added to the infrastructure inventory database. The re-drafting effort is error prone and time consuming.
  • As-built drawings and the infrastructure inventory database are often maintained via different systems (typically CAD and GIS) and by different departments. Loading CAD data into a records database may require translation, editing for topology and other inefficient workflows.

As you can see, workflow contributes to the as-built backlog which impacts the currency of the infrastructure database and inadequate currency impacts the accuracy of PSAB 3150 reporting. If your infrastructure database is months or years out-of-date then how can you be sure that your PSAB 3150 reports on tangible capital assets are accurate?

The solution requires a new way of thinking. Stay tuned as I discuss proposed solutions to the as-built problem in future posts.

Until next time…

Source: geoExpressions – As-built Backlogs Impact Accuracy of PSAB 3150 Reports
Go to Source: geoExpressions

News Alert: Bentley Extends Design and Cost-Estimating Efficiencies of Bentley Expert Designer V8i to Support Water, Gas, and Communications Projects

July 8, 2009 in Bentley, CAD

EXTON, Pa. – May 21, 2009 – Bentley Systems, Incorporated, the leading company dedicated to providing comprehensive software solutions for the infrastructure that sustains our world, has extended the functionality of Bentley Expert Designer V8i beyond electric utility networks to include water, gas, and communications infrastructure.
Source: Bentley News – News Alert: Bentley Extends Design and Cost-Estimating Efficiencies of Bentley Expert Designer V8i to Support Water, Gas, and Communications Projects
Go to Source: Bentley News