This is interesting. As someone who works in this space (building hospitals) we see a lot of trending movement to the iPad, though I question the longevity of PDFs.
We have a software suite for the construction industry, which has modules for inspection requests, punch-lists, occupancy planning (healthcare), room completion (healthcare), room readiness (healthcare) etc.
We also have a service around providing custom reports... however, we find that the need for dynamic data trumps the ability to simply view the latest plan digitally, i.e. we provide the ability to run a dynamic report on all inspections scheduled, performed, outstanding, etc... As well as the need to run a report that would "Show me all the rooms that have a Medication Dispensation Unit, on level two and assigned to unit Med Surge" - which outputs a colorized visio (or ZUI iPad floorplan).
The future is in granularity of reporting, rather than just blanket display, and I think this is a great step. Especially if you have many trades begining to use it. There is no reason the trades can't run multiple apps for specific purposes.
Although, I am not sure I agree with one number in the article; "For $1MM in construction, you can have as much as $3,500 in printing" -- I am only skeptical as I work on projects in the hundreds of millions (1.5B, 850MM, 800MM 100MM are the budgets for my (personally) active projects) I dont see them spending 3MM on printing for the 850MM project... but I might just not be privy to the numbers from every trade.
Here is an example of a dynamic room category report for an active project here in SF. We colorize the rooms based on type/use to familiarize the org with the spaces http://i.imgur.com/2DRah.jpg - We do a great deal more with the data and reports, this is just an example of many that the orgs use. Hospital transition planning is very complex, and costly. The vitals of the facility change a lot through the life of the project. The issue with educating THOUSANDS of people in prep for opening day such that they can SAFELY receive their first patient is critical.
Being able to very quickly synthesize and summarize vast amounts of information makes for a better, more successful project and a better, more educated and prepared staff.
Remember that while there are hundreds of people on a project team, there are thousands of people on the facility staff who are expected to move into the facility day-one and not cause fatal mistakes.
A project I am doing in Texas is 1.5MM square feet and dynamic, item-level granularity reporting is going to be key in the smooth success of the project.
I would love to see what PlanGrid can offer such large projects - and while I am a full proponent of the iPad in the field, in an industry where cost is king, I'd like to better understand how they convince construction companies of the ROI - esp. when tools and materials walk of the job all the time.
I think that Plangrid should talk to the designers (not just architects) as well; RTKL, Mazzetti, TEECOM, RLS, SMWM, SFM, etc...
If PlanGrid (love the name) wants to talk to me - my email is in my profile.
For us, the ROI on any project - but particularly large projects - is pretty simple: An iPad ($800) plus 3 years of PlanGrid ($1500 for the big plan) is almost always cheaper than the initial half-size set of thousands of drawings (a hospital project Tracy was on spent $2700 per planholder set of 3000 sheets), but when you add in the printing cost of MEPF coordination drawings, fabrication drawings, point-load drawings, deck-insert drawings, seismic bracing drawings, P&ID drawings, submittal shop drawings and the constant deluge of change order and supplemental sheets it's a huge money saver.
We are cheaper than just the printing costs alone, but our real value-add comes from the huge reduction in document control hours we bring. This, combined with our ability to mitigate the risk of building off outdated information, makes a huge win for almost every project if you do the math.
I'd be interested to see what the differential between 2D and BIM projects is.
Let me give you a concrete example; a hospital here in SF that is building a new facility has spent 30+ million dollars on coordination and constructability issues between all the trades.
There was far less printing of plans than there was hours spent coordinating the BIM model for changes.
Now, granted, this wasa project where there was an oversight in the design as it pertained to the owners intent and a number of critical technology spaces required were left out of the design.
This resulted in many hours of coordination efforts from all the trades to get these spaces into the facility, but a fraction of this was in printing.
If you can help with this problem, coordination, you have a much larger market.
The current industry trend is to err on the side of digital design and coordination meetings with IPD models, and reduce printing and field interference issues.
What might be an interesting opportunity for your service is to notify trades when changes occur that may affect them. THEN show them the new, updated PDF.
I don't know how this would occur -- other than the pushing of a constructability log or something....
Also, it would make sense that your app is much more focused on a the smaller project (HUGE market) of residential, smaller commercial etc..
Trying to force yourselves into solving the issues of massive scale projects may be suicide.
I agree that BIM is totally transforming constructability reviews and massively reducing MEP conflicts with clash-detection etc.
The problem is, after all this 3D BIM work, how does that information get to the field? What are the actual workers building off of?
Paper. Outdated, expensive, paper. THATS the problem we are solving. Big projects, little projects, they all use paper, they all pay waaaay too much for paper, and they all have trouble keeping it up to date.
Sure, but do you expect the 500+ builders onsite on any given day to have a fragile $800 device with a screen size less than 8.5x11" as their primary interface to information?
I don't think that is realistic.
Others are working on augmented reality interfaces to provide that updated information. Where a set of glasses connected through the construction wifi network would provide the needed updates.
Sure, there is a much larger technical issue there WRT engineering a solution, but the fact of the matter is that paper is actually a cheap way of conveying a vast amount of information VERY efficiently.
They can write and scribble and troubleshoot on the plans.
There is a LOT more information to present on 30x42.
Their batteries wont die.
Training people to absorb information off plans is thousands of years developed, efficient and CHEAP.
I think that granularity of message is important - and I think you can really excel here.
Rather than presenting the whole plan on PDF - tell them EXACTLY what they need to know BY ROOM/BY LOCATION that pertains to them at that moment.
I'd like you to see the Inspection Request Module that we have to understand this; where on a PDF/Visio of a plan an inspector can just trace out the walls that they inspected in the field at that time. This finger-trace gets captured and recorded. Then synthesized into the colorized maps I showed aboved so that the whole project team can run reports on status of the project (you can also run reports that show which trades are succeeding and which are behind in every aspect of deliverables... sometimes you just need to fire a plumbing contractor because they keep failing inspections)
Anyway - paper is not always bad. It is an extremely efficient method of conveying information.
You need to preempt the NEED for paper, not reduce it on the back-end. This is what BIM and coordination and IPD are all about. Reducing back-end paper and change-orders.
Paper is not what is bad, bad information is what is bad. Eliminate bad information you eliminate waste.
>I think that granularity of message is important - and I think you can really excel here.
>
>Rather than presenting the whole plan on PDF - tell them EXACTLY what they need to know BY ROOM/BY LOCATION that pertains to them at that moment.
>
This.
In my former life as an architectural designer and project manager for a design-build firm, we experimented with creating document sets that provided this level of room-by-room information. The documents were color printouts on 11x17 sheets, folded and contained in a binder. 160,000 SF remodel. Labor intensive to say the least, and only possible at all because we were doing mostly finish work.
But an app could make this level of granularity practical. The advantages to all stages of construction are numerous, from takeoffs to punch lists and inspection.
Comments
This is interesting. As someone who works in this space (building hospitals) we see a lot of trending movement to the iPad, though I question the longevity of PDFs.
We have a software suite for the construction industry, which has modules for inspection requests, punch-lists, occupancy planning (healthcare), room completion (healthcare), room readiness (healthcare) etc.
We also have a service around providing custom reports... however, we find that the need for dynamic data trumps the ability to simply view the latest plan digitally, i.e. we provide the ability to run a dynamic report on all inspections scheduled, performed, outstanding, etc... As well as the need to run a report that would "Show me all the rooms that have a Medication Dispensation Unit, on level two and assigned to unit Med Surge" - which outputs a colorized visio (or ZUI iPad floorplan).
The future is in granularity of reporting, rather than just blanket display, and I think this is a great step. Especially if you have many trades begining to use it. There is no reason the trades can't run multiple apps for specific purposes.
Although, I am not sure I agree with one number in the article; "For $1MM in construction, you can have as much as $3,500 in printing" -- I am only skeptical as I work on projects in the hundreds of millions (1.5B, 850MM, 800MM 100MM are the budgets for my (personally) active projects) I dont see them spending 3MM on printing for the 850MM project... but I might just not be privy to the numbers from every trade.
Here is an example of a dynamic room category report for an active project here in SF. We colorize the rooms based on type/use to familiarize the org with the spaces http://i.imgur.com/2DRah.jpg - We do a great deal more with the data and reports, this is just an example of many that the orgs use. Hospital transition planning is very complex, and costly. The vitals of the facility change a lot through the life of the project. The issue with educating THOUSANDS of people in prep for opening day such that they can SAFELY receive their first patient is critical.
Being able to very quickly synthesize and summarize vast amounts of information makes for a better, more successful project and a better, more educated and prepared staff.
Remember that while there are hundreds of people on a project team, there are thousands of people on the facility staff who are expected to move into the facility day-one and not cause fatal mistakes.
A project I am doing in Texas is 1.5MM square feet and dynamic, item-level granularity reporting is going to be key in the smooth success of the project.
I would love to see what PlanGrid can offer such large projects - and while I am a full proponent of the iPad in the field, in an industry where cost is king, I'd like to better understand how they convince construction companies of the ROI - esp. when tools and materials walk of the job all the time.
I think that Plangrid should talk to the designers (not just architects) as well; RTKL, Mazzetti, TEECOM, RLS, SMWM, SFM, etc...
If PlanGrid (love the name) wants to talk to me - my email is in my profile.
For us, the ROI on any project - but particularly large projects - is pretty simple: An iPad ($800) plus 3 years of PlanGrid ($1500 for the big plan) is almost always cheaper than the initial half-size set of thousands of drawings (a hospital project Tracy was on spent $2700 per planholder set of 3000 sheets), but when you add in the printing cost of MEPF coordination drawings, fabrication drawings, point-load drawings, deck-insert drawings, seismic bracing drawings, P&ID drawings, submittal shop drawings and the constant deluge of change order and supplemental sheets it's a huge money saver.
We are cheaper than just the printing costs alone, but our real value-add comes from the huge reduction in document control hours we bring. This, combined with our ability to mitigate the risk of building off outdated information, makes a huge win for almost every project if you do the math.
I'd be interested to see what the differential between 2D and BIM projects is.
Let me give you a concrete example; a hospital here in SF that is building a new facility has spent 30+ million dollars on coordination and constructability issues between all the trades.
There was far less printing of plans than there was hours spent coordinating the BIM model for changes.
Now, granted, this wasa project where there was an oversight in the design as it pertained to the owners intent and a number of critical technology spaces required were left out of the design.
This resulted in many hours of coordination efforts from all the trades to get these spaces into the facility, but a fraction of this was in printing.
If you can help with this problem, coordination, you have a much larger market.
The current industry trend is to err on the side of digital design and coordination meetings with IPD models, and reduce printing and field interference issues.
What might be an interesting opportunity for your service is to notify trades when changes occur that may affect them. THEN show them the new, updated PDF.
I don't know how this would occur -- other than the pushing of a constructability log or something....
Also, it would make sense that your app is much more focused on a the smaller project (HUGE market) of residential, smaller commercial etc..
Trying to force yourselves into solving the issues of massive scale projects may be suicide.
I agree that BIM is totally transforming constructability reviews and massively reducing MEP conflicts with clash-detection etc.
The problem is, after all this 3D BIM work, how does that information get to the field? What are the actual workers building off of?
Paper. Outdated, expensive, paper. THATS the problem we are solving. Big projects, little projects, they all use paper, they all pay waaaay too much for paper, and they all have trouble keeping it up to date.
Sure, but do you expect the 500+ builders onsite on any given day to have a fragile $800 device with a screen size less than 8.5x11" as their primary interface to information?
I don't think that is realistic.
Others are working on augmented reality interfaces to provide that updated information. Where a set of glasses connected through the construction wifi network would provide the needed updates.
Sure, there is a much larger technical issue there WRT engineering a solution, but the fact of the matter is that paper is actually a cheap way of conveying a vast amount of information VERY efficiently.
They can write and scribble and troubleshoot on the plans.
There is a LOT more information to present on 30x42.
Their batteries wont die.
Training people to absorb information off plans is thousands of years developed, efficient and CHEAP.
I think that granularity of message is important - and I think you can really excel here.
Rather than presenting the whole plan on PDF - tell them EXACTLY what they need to know BY ROOM/BY LOCATION that pertains to them at that moment.
I'd like you to see the Inspection Request Module that we have to understand this; where on a PDF/Visio of a plan an inspector can just trace out the walls that they inspected in the field at that time. This finger-trace gets captured and recorded. Then synthesized into the colorized maps I showed aboved so that the whole project team can run reports on status of the project (you can also run reports that show which trades are succeeding and which are behind in every aspect of deliverables... sometimes you just need to fire a plumbing contractor because they keep failing inspections)
Anyway - paper is not always bad. It is an extremely efficient method of conveying information.
You need to preempt the NEED for paper, not reduce it on the back-end. This is what BIM and coordination and IPD are all about. Reducing back-end paper and change-orders.
Paper is not what is bad, bad information is what is bad. Eliminate bad information you eliminate waste.
LEAN processes are good.
>I think that granularity of message is important - and I think you can really excel here. > >Rather than presenting the whole plan on PDF - tell them EXACTLY what they need to know BY ROOM/BY LOCATION that pertains to them at that moment. >
This.
In my former life as an architectural designer and project manager for a design-build firm, we experimented with creating document sets that provided this level of room-by-room information. The documents were color printouts on 11x17 sheets, folded and contained in a binder. 160,000 SF remodel. Labor intensive to say the least, and only possible at all because we were doing mostly finish work.
But an app could make this level of granularity practical. The advantages to all stages of construction are numerous, from takeoffs to punch lists and inspection.