Security, accountability, and cloud access: Can you really have it all?

I’ve heard countless stories of conversations between project engineers and IT professionals who can’t come to an agreement on the level of security needed to protect their data while making it more accessible—not only externally, but also internally. 

April 03, 2014 |
Sasha Reed

Photo: patrisyu via

With all the talk today of collaboration and information sharing, conversations are quickly turning from the benefits of the cloud to questions regarding how to address security concerns. Security and tech are pretty hot topics, even outside of the AEC space. It seems you can’t turn on the news without hearing about some sort of security breach. 

In the AEC world, large-scale security breaches aren’t as much of a concern as are finding ways to improve information sharing while maintaining accountability. Even as technological advancements are implemented on active projects, allowing more team members to collaborate openly, project contracts still determine the final say in defining roles, responsibilities and, most importantly, liabilities.

What does this mean exactly? Well, as technology is blurring the lines of responsibility on your current project, someone still needs to be held responsible for final sign off.  

I’ve heard countless stories of conversations between Project Engineers and IT professionals who can’t come to an agreement on the level of security needed to protect their data while making it more accessible—not only externally, but also internally. In order to help firms find the right balance between collaboration and accountability, many technology solutions offer security options designed to help you find the right fit.  

Having been a fly on the wall for many of these conversations, I’ve come up with a list of questions to start the conversation and ultimately help you define your needs. 

Are you able to control information sharing with project team members today, both internal and external?  

  • You may find that email provides a sufficient level of security and authentication for CYA.  However, if you’re looking to track your documents better while still allowing access for both internal and external team members, a Document Management System (DMS) may be the better path.

Who do you need input from, and when?  

  • Does everyone need to access project documents at the same time, or separately?  A simple cloud depository or local server can offer controlled access to many.  However, a DMS can offer further control by implementing structured workflows, making it easier to move documents through the review process.   

What type of device will the team access information on – laptop, tablet, iPad, smartphone?  

  • Knowing that files may be accessed on a mobile device may help you determine how to create and organize your files. Do you want collated digital drawing sets, or separately saved single sheet files for easier access on a mobile device? Will you need access to project documents while offline as well? You will want to make sure there is an offline/syncing capability so information isn’t lost when your Internet connection is. 

How will you track approvals and final sign off? 

  • Since you’re no longer signing physical paper, will a replication of a wet signature suffice or do you need a digital signature?
    • Rather than signing and scanning your signature, wet signatures can be easily replicated using a vector-based PDF markup.  If you have an iPad, tablet PC or stylus, use the “Pen” to draw your signature on a PDF.
    • If you choose digital signatures, think carefully about when in the process to require them. Requiring them too soon will inhibit your ability to collaborate.
      • Will the signatures be used for internal sign off only?
        • A Windows-based certificate for all signers should suffice.
      • Will the signatures be required with external collaborators?
        • You may want to look into third-party verification services for digital signatures.

How will you store your project documents for easy reference by owner/maintenance teams after the project is complete?  

  • Many GCs are leveraging hyperlinks to make navigable digital drawings sets. You may want to put some thought into standardizing file naming conventions so that linked files remain intact at handover.
  • In addition to storing digital files on a hard drive, some teams are storing all linked project documents in the cloud, providing greater mobility for FM teams moving forward.

This list is just a beginner’s guide to ease into the longer conversation about security. What questions have you asked yourself to better define your collaboration/security needs?  

Editor's note: This is sponsored content. Text and images were provided by the sponsor company. 

Sasha Reed | Digital COM
Bluebeam, Inc.
Vice President of Strategic Development

As Vice President of Strategic Development at Bluebeam, Inc., Sasha Reed collaborates with leaders in the architecture, engineering and construction industry to guide Bluebeam’s technology, partnerships and long-term goals. She joined Bluebeam in 2007 and co-created the Concierge Approach, a distinctly branded process of customer engagement, product feedback and solution delivery to which much of Bluebeam’s success is attributed, and which today is replicated at every organizational level.

Sasha is known industry-wide as a “conversation facilitator,” creating platforms for exchanges necessary to digitally advance the industry, including the BD+C Magazine Digital COM Blog, which she authors and manages. She’s been a featured presenter at numerous national and international conferences, including the 2014 Design-Build Institute of America (DBIA), Federal Project Delivery Symposium and NTI Danish BIM Conference. Sasha also co-chairs the Construction PDF Coalition, a grassroots effort to provide a common industry framework from which to create and maintain construction PDF documents, serves on the City College of San Francisco BIM Industry Council, and is Advisor to the Board of Direction for the National Institute of Building Sciences BuildingSMART Alliance.

Related Blogs

March 15, 2017 | Digital COM

Who is succeeding, and on what terms? And what will it take for everyone to experience the benefits of that...

October 04, 2016 | Building Team | Digital COM

As the construction industry bounces back from the Great Recession, an entirely new class of tech-savvy con...

July 11, 2016 | Building Team | Digital COM

The lead up to AECX featured a discussion providing insight into the current state of the AEC technological...

June 23, 2016 | Digital COM

Two truths from the jobsite: 1) The best part about uncovering a problem is discovering its solution, and 2...

June 09, 2016 | AEC Tech | Digital COM

Rather than fighting to control the proliferation of apps, perhaps we should be training our eyes to look f...

December 17, 2015 | BIM and Information Technology | Digital COM

Sascha Vesterlund, a VDC Specialist, Design Processer with MT Højgaard, and Nathan Wood, Innovation at DPR...

November 25, 2015 | BIM and Information Technology | Digital COM

I recently sat down with two Architects-Turned-VDC-Process-Managers to discuss the ways in which they are l...

Is the PDF revolution advancing BIM workflows?

From left to right: Sasha Reed, V.P. Strategic Development at Bluebeam Software, Nathan Wood of DPR Construction, and Kris Lengieza, Director of VDC at Stiles Construction.

November 12, 2015 | BIM and Information Technology | Digital COM

Many project teams who struggle to get everyone up to speed with BIM, find PDFs a useful tool to bridge the...

Microsoft’s Surface Pro 3 – designed with the AEC industry in mind

Microsoft explains how they made the impossible, possible in building the Surface Pro 3 with Bluebeam Revu in their keynote presentation here:

October 07, 2015 | BIM and Information Technology | Digital COM

Sasha Reed sits down with Microsoft’s Senior Director of Programs, Pete Kyriacou to discuss the unique chal...

Add new comment

Your Information
Your Comment

Filtered HTML

  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Overlay Init