The ideal communication flow on a construction project would look something like this: Project information is sent in real time from the subcontractors to the general contractor on the jobsite. The general contractor then consolidates it and sends it back to the office where it’s processed, stored and then sent to the owner, who can access the information in an easy-to-understand format, such as a dashboard or a report. The project data is entered once and travels instantaneously among all of the project collaborators, even though they are all using different systems. No data is lost, nothing needs to be re-entered and everyone is on the same page.
A few years ago, this scenario would have seemed impossible, but XML—a computer language that allows the transmission of information regardless of the software involved—has made it a reality.
XML, or Extensible Markup Language, has bounced around the business world for a while and recently started to gain ground in the construction industry. Essentially, XML transfers information without caring what the information is or what system is going to use it. XML tags information so different computer systems can read it and exchange it.
On a traditional construction project, the general contractor, subcontractors and owner use their own software systems. Each has a system for financials, a system for operations, a system for employee information and an additional system to create reports. This approach creates silos of information, with RFIs, change orders and other project data stored in each system. For large projects, multiple versions of documents can exist in multiple systems, and each time something changes, every version must be updated.
This often leads to problems between the general contractor and the owner, who may feel the contractor is holding back crucial pieces of information, while the general contractor struggles to keep all the systems updated to present the best information and make the best decisions. Even if a contractor uses a system that integrates financials and operations on the same database, other project collaborators might struggle to access the project information.
The inherent inefficiency in this method is staggering, and for large companies performing large projects, more resources might be spent on managing information flow and computer systems than on managing the project.
Eliminating the Mess
XML eliminates this mess and allows information to be exchanged seamlessly between systems. With the right XML adapter, the project information flows back and forth without being translated from one system language to another.
XML overcomes the terminology hurdle as well—a general contractor’s invoice becomes an owner’s request for payment. Both databases are updated at the same time, so all parties involved in the project can make decisions using the most recent information.
XML also can help incorporate a diverse set of applications into the project. For example, using XML, a BIM application can be integrated into the financial or project management computer system, so information from the 3-D model can be used in job costing, material procurement and forecasting. As the project develops, information such as the required number of doors or the tons of concrete poured can be sent back to the model, and the changes are represented in 3-D.
XML adapters can be used to incorporate other applications, such as online payment software, plan rooms for drawings and specs, and scanning solutions for invoices and other documents. Given the right technical expertise, almost any kind of application can be incorporated into a system using XML—creating the prospect of a one-stop, total software solution that manages all aspects of a construction project.
The business implications are massive, and it’s not pie-in-the-sky. Some contractors already have employed XML to strengthen relationships with owners, provide better customer service, and save time, energy and money.
![]()
Wednesday, September 8, 2010