Q. Do fears such as differing data standards, system incompatibility, data accuracy issues or perceived confidentiality breaches threaten to undermine a sharing infrastructure between QSs and their fellow Construction Professionals? Or is seamless interfacing now a reality?
John Whitehead, Snape Computers Ltd.
Exchanging data reliably between the different parties of the construction chain is very important today. There is, however, a major difference between how smaller organizations will exchange the critical information necessary for effective construction management and how the major clients, national contractors and the large professional practices will operate on major projects.
Recently, my company provided a custom software solution for handling the measurement, specification and costing for the building works of a major retailer. All parties in the chain use the software: architects, quantity surveyors, contractors, major subcontractors and project managers. Files are exchanged via the Internet. The results have worked exceptionally well for all parties.
We provided first-rate software for the project, but there was also real clarity of thinking, combined with quality management of the client's particular needs and the operational requirements of the contractors and surveyors. For major clients and contracts it is both desirable and possible to lay down well thought out standards and channels by which information is passed, and insist that all parties conform. With good implementation, all parties gain substantially.
It is just as desirable that the smaller players can exchange information as efficiently as the "big boys," but the starting point of making this process work is to recognise the world as it really is.
Most contractors/ PQSs/ project managers work with many different organizations. Inevitably these firms will be using different software that is not directly compatible, and therefore exchanging data using an intermediate file format, commonly C.I.T.E, ASCII, Excel, and Microsoft Word / RTF (XML is likely to become important in the future.) Our users are nevertheless exchanging files as a matter of routine. The process is usually seamless, but it should be remembered that all these intermediate "standards" leave room for different interpretation that can cause hiccups.
Take Microsoft Excel as an example. There is a vast range of different ways that Bill of Quantities can be created. Descriptions can be in a single cell or spread over a number of separate cells. There may or may not be a blank line between each description or there may be lined, blank or hidden columns for internal reference or calculation. Graphic images may be put in a column that is normally used for another purpose or the length of page, treatment of headers and footers, collections and summaries may vary. The bill may be created on a single sheet, or spread over several.
Our approach with our software programs is to cater for as many standards as possible and make the import and export routines as flexible as possible, so they can accommodate these many different interpretations. Critically, we provide a first-rate technical support service so if we are e-mailed a file, we can advise what is necessary to make import/export routines work.
The best results are achieved when the software vendor takes the time to explain the issues involved.
Paul Watkins, Masterbill
When you consider that the majority of information passed between the members of a project team is in drawn format and that the majority of designers now use CAD software and CAD systems that will produce an AutoCAD dwg format, file data standards, system incompatibility and data accuracy are not really major issues.
Confidentiality breaches could be an issue as designers are now issuing drawings in a format that can easily be re-used and/or manipulated. But when you consider that most projects have unique design solutions and paper-based drawings could be easily scanned or traced, then it is hard to believe that this is any more of an issue now than it was twenty years ago. The fear of a breach in this area should not undermine a sharing infrastructure, as any real fear could be overcome with the adoption of a confidentiality agreement signed by all members of the project team.
Seamless interfacing is an ideal that implies that all parties will have the same systems, when in reality this is not the case. But we are now at a point where each party can adopt their own specialist solutions in order to interface with the specialist solutions adopted by other parties, albeit that an agreed file format may need to be adopted.
With regards to electronic tendering, it seems that whilst data standards have been set in the past, their partial adoption by software vendors and users means their true benefits are yet to be realised, which in turn has led to a number of QSs becoming frustrated with the standards and looking to alternative options for streamlining this process.
In our experience, the biggest obstacle to realising the benefits of electronic tendering continues to be the unwillingness of contractors to work with the QS to ensure mutual benefit, such as thinking only how the estimator is able to import the BQ into their estimating system, rather than considering how it could be returned once completed.