Privacy Policy Update Notice:

Sage North America updated its Privacy Policy on August 18, 2011. With this update, we made changes to the "Business Information Collection and Use by Sage" section of our policy to explain that our websites ("Sites"�) may use third party Internet advertisers that deliver custom ads to you. Such custom ads are based on information collected through cookies and web beacons when you visit our Sites. Please note that Sage does not control Internet advertisers' use of cookies or information collection. We also explain how you can opt-out of Internet advertisers' information collection. Click here to learn more. Sage North America values your privacy and is committed to maintaining your trust. Please read the full updated Privacy Policy, as you are bound by its terms when you use our Sites.

Close Privacy statement

Email this page to a Friend

Found this page interesting? Send it to your friend or co-worker by filling out this form. Add a personal message if you like.

Note: We will not use these e-mail addresses for any other purpose than sending your e-mail.

------ Privacy Policy Update Notice

Setting standards for greater construction collaboration

11/7/2014 at 1:16 pm by

Every construction company should have the freedom to use whatever software best fits its needs without running into roadblocks that prevent information exchange. As an early member of the Construction Open Software Alliance (COSA), Sage, along with other member firms, is steadily working towards this goal.

In my last post, I talked about how software integration has been the holy grail of the construction industry for years. Today, the quest for integration has only become stronger as contractors automate more tasks and software becomes more specialized.

How do we get the various software applications used by contractors to talk with each other?

In 2008 the Associated General Contractors of America (AGC) developed the agcXML standard as the first effort to standardize and encourage the efficient exchange of data between software solutions in the industry. Then COSA, an organization of software providers, joined the effort in 2012. Working alongside AGC to develop complementary standards, COSA also served as a voluntary test group for agcXML. That partnership took on a new dimension with the recent AGC announcement that COSA will now lead the agcXML effort to better connect construction project data across independent software providers.

Since 2012, agcXML and COSA have developed five standard schemas for the exchange of data between software systems. As construction software developers begin to add these standards to their products, contractors will be the beneficiaries. Here are some examples of what these schemas will allow you to do:

  • Contractor Record: If you’re like most contractors, contact information for your customers and business partners is often scattered in multiple locations (Microsoft Office, accounting programs, and customer and sales databases). This schema lets you easily share contact record data such as company names, addresses, trade designations, certificates, and licenses between various software programs.
  • Timesheets: Accounting and payroll staff are often frustrated because it’s hard to get timesheet information into the office for processing. This schema will help by allowing time capture information such as employee ID, number of hours worked, where your employees worked, and what they worked on to automatically flow into payroll systems.
  • Planroom: Wouldn’t it be nice to have plan room information automatically populate documents such as invitations to bid and submittals? This is just one example of how this schema will facilitate the transfer of project information such as descriptions, schedules, and owners and architect’s name from electronic plan rooms.
  • ConsensusDocs 721: Think of the time saved if subcontractors could submit statements of qualifications directly from their software into a GC’s system. With this schema licensing and registration, experience, safety record, financial details, references and other qualification can be exchanged between software systems.
  • RFI:The time required to review and respond to RFIs can negatively impact your project schedule. This new schema shortens the process by electronically exchanging RFI data between software systems used by contractors, designers, and owners. Data includes RFI name and number, issue date, project information, questions, relevant attachments, and requested reply date.

I have personally been involved with COSA over the past two years and believe that true integration in construction won’t happen without software developers working together to adopt standards. Only through this kind of cooperation can we give our customers the tools that will lead to greater collaboration in the building process.

About the Author

Dennis Stejskal has over 30 years of experience developing, supporting and selling software and technology to construction and real estate companies. His comprehensive product knowledge and understanding of customer and market needs propelled him into his current role as Vice President of strategy and customer success for Sage Construction and Real Estate. Dennis has been a member and co-chair on the CFMA Technology Committee and often speaks at industry events, including CFMA, AGC and NAHB meetings and conferences.

2 responses to “Setting standards for greater construction collaboration”

  1. Jan Maple says:

    I’ve been a Financial Controller / CFO in the Construction industry for over 20 years. The primary software that I’ve used/Implemented in various companies is Timberline and feel it is one of the best for the industry.
    I believe it would be fantastic to find a centralized area to better connect construction project across independent software providers. This will work well for many of the mid-sized to large construction companies. The problem to be identified is attempting to have the smaller subcontractors get “on-line” as many of them are “field” personnel and have little to no knowledge of computers, or the internet.

  2. Dennis Stejskal says:

    I agree 100% with your comments about challenges faced by smaller subcontractors, with many of the operational personnel always in the field.

    This is a perfect example of where I believe “Cloud / Mobile” based solutions will be the solution.

    A very simple example is the RFI process. Many RFI’s are initiated by the subcontractor. Envision the Subcontractor Supt./PM entering the RFI via a mobile device. The RFI could then go directly to the GC’s project site, or to both the sub’s project site and the GC’s project site.

    This is a scenario that was demonstrated at this years AGC Technology forum using agcXML. I would love to have a deeper conversation with you on this. Please email me at if you are interested.

Leave a Reply

Your email address will not be published. Required fields are marked *

Email this page to a Friend

Found this page interesting? Send it to your friend or co-worker by filling out this form. Add a personal message if you like.

Note: We will not use these e-mail addresses for any other purpose than sending your e-mail.