설명
주요 학습
- Discover what BIM 360 Docs is, and the common data environment
- Learn workflows for both 2D and 3D
- Discover some of the latest features like RFIs and Submittals
- Review the mobile capabilities of BIM 360 Docs
발표자
- Carl StormsCarl is a seasoned professional and Head of Community, Advocacy, and Technology at Newforma, with over 25 years of experience in Architecture, Engineering, Construction, and Operations (AECO). Renowned as a BIM Crusader, his expertise in Building Information Modeling (BIM), Virtual Design and Construction (VDC), and Project Information Management (PIM) allows him to seamlessly blend innovation with practicality. Carl has a knack for simplifying complex ideas and loves sharing his knowledge through blogging, speaking, podcasting, and as an Autodesk Expert Elite. Beyond AECO, he gets a thrill out of unraveling tech mysteries and learning new coding, no-code, and AI skills. These new additions to his skill set showcase his flexibility and dedication to keeping up with the latest in technology. Approachable and always up for a chat about the latest technologies, workflows, gadgets, or hacks, Carl is a valuable resource in the AECO industry.
CARL STORMS: So this is What's Up, Docs? We're going to be talking about the BIM 360 Docs platform. As you may or may not have heard me say a couple of times already, we're testing out a new technology here in this session.
So if you go to join.fxptouch.com and put in that number in your mobile device, iPad, what have you, you can play along. So we're going to have some poll questions as we're going through. You can make markups on the screenshots. You can save all that stuff. It'll get sent to your email at the end. So by all means, come along and play.
So let's go ahead and get started. And I'll put this information up again a little bit further on just in case you didn't get it now. So a quick little overview of what our agenda is going to be today-- so we're going to do some introductions.
We're going to talk about the FXP Touch. We're going to talk about myself. Actually, we're not going to talk about me, because that's weird. But I have a slide for that.
We're going to get into what we can do with BIM 360 Docs. We're going to do a little bit of summary. And then we're going to do the fun stuff.
I'm going to put away the PowerPoint. And I'm going to give you a live demo. We all know how great live demos go in these type of things. So we'll make sure that I try not to kill anything too much.
So the introductions part-- as I mentioned, we're testing out this great new technology here today. Here's sort of what you're going to see when you get it on your phone once you've went to the website, put in the code. You can personalize it.
You can have chat with other participants inside of the room. You can ask questions. You can take notes. You can even watch the current slide as we're going through.
Now, just as a heads up, the questions, I won't get them actually live during the presentation. I will get them after. And I will be able to answer them after the fact. But we won't be able to answer them live here today.
So to test this out, to make sure that everybody has access to the information, we're going to try this first slide. So someone says stop, what comes next?
[LAUGHTER]
OK, we'll give you a couple of seconds to bring that and choose your answer. All right, similar to the multiple choice quizzes that you all took in high school, the answer should definitely be C. And if you're not a Vanilla Ice fan, you should probably just leave right now.
No, it's OK. We'll keep you around. But that shows you how this technology works and what it comes in. And I see that right now C is the winner, 39%, and then B with 36%, and A coming up the rear.
So that's kind of how this is going to as as we're working our way through. As the questions come up, we'll give you about 15 seconds to answer. And then we'll carry on.
So in other introductions, this lovely fellow is myself. My name's Carl Storms. I work with IMAGINET. It's very awkward to talk about yourself. So that's why I had a marketing department make this lovely slide for me. And it sort of explains what we do.
So now that you all know who I am and what I do and my lovely hat, we shall carry on with what we're going to talk about today. So we're talking about BIM 360 Docs. And we're talking about the challenge that document manage gives us today.
So we're working with document management. We're trying to control all these documents that we have. And it's way more difficult than it was just a few years ago when we were carrying around a bunch of rolled up newspapers-- or newspapers as well-- but our construction dockets underhand from place to place.
Now that we're working in a BIM workflow, not only do we have documents, we've got PDFs. We've got 3D models. We've got all sorts of formats that we're dealing with.
And we have to be able to control all this stuff all at once. And we don't have that ability to have sort of that one person that sits in the trailer looking after all the documents like we used to. We now have to look after this in a much more high tech way.
And because of this, there's lots of technologies that have become available that we can use to do this. We've got cloud-based solutions where we can store everything under the sun, whether it's Dropbox, or OneDrive, or what have you. PDF has sort of taken over the world as our way to mimic and look after our products.
So we have PDF softwares that we can mark up. We can save to the cloud. We can share. And then, of course, now we have mobile devices.
We're all playing on our mobile devices now in this session, whether it's our iPhones, or our iPads, or what have you out in the field. So we have all these apps to look after all this stuff. The problem is when we have all of this stuff is exactly that. We have all of this stuff.
So we're walking around in the field. We've got all these different spots. This project we're using Dropbox. That project we're using Google Drive. Somebody's still got something on SharePoint. We're using that in a different project.
So where do we go to find that information? And whether we're using PDFs or some version there of it, everybody's got a different markup tool they've got [INAUDIBLE]. And then, of course, we can access all of that from mobile devices.
The problem is what if I save the stuff from Bill's project in Ted's Dropbox? Or what if I put the stuff from Ted's project in Bill's OneDrive? There's all this information floating all over the place. How do we control it? How do we look after it?
So that really is the issue. It starts putting us into our silos. And that's sort of the whole point of why we learn to love our friend BIM is we want to get out of those silos. We want to have a collaborative environment.
We want to be able to access what we want when we want it. And we want to make sure that we have that ability. But now that we have all of this new technology and all these great features, we've started to build those silos back up again, but now with technology.
Where do we find it? Where do we get it? What's the most current version of it? And that's what brings us to this slide, which is my favorite. And I'm sure we've all come across something like this.
And if you go to my naming convention, the super secret final version 3.2, that's sort of what I like to go when I go in there. But which version of the final is actually the final? And where does it come from?
So this is where we start getting into these issues. So what we want to do is we want to try to find a way that we can solve this. So here, this brings us another poll question for us to all play along.
You're going to get a thumbs up or a thumbs down. So if you're currently dealing with some sort of document management issue, problem, troubles, you're going to give a thumbs up. I know it sounds counterintuitive, but that basically means yes. If everything's hunky dory, no issues at all, you're going to give it a thumbs down. Again, counterintuitive, but it means no.
All right, so it looks like we're getting a whole lot of thumbs up, again, for a bad thing in this case. But it means a lot of people are dealing with this same type of issue. We're not just making it all go away. We have to find a solution.
And funnily enough, the next slide is entitled A Solution. Imagine that. You came here, and we're going to get you a solution today, BIM 360 Docs.
And what this helps us do is alleviate some of those problems that we just talked about. So another quick poll here-- how many people are actually using this the solution BIM 360 Docs right now? I need the Jeopardy! music. That's close enough.
All right, so we've got a few people that are using, a few people that have tried it out. But the majority of people right now, we're at about 70% haven't used it. So you're in the right spot. We're going to talk about that today. And we're going to see if we can get you to use it.
So when we're dealing with BIM 360 Docs, it's part of an overall platform that Autodesk works with, BIM 360. They have seven products right now currently. This kind of gives you an idea of where it fits inside of that scope.
Now, in this particular little slide, you'll see we've got Design all the way through the gamut to Operations. Now, to make it look nice and pretty here on the screen, I've made each section of time equal. Obviously, we know that that's not necessarily the case.
Operation is going to be a lot longer than design. But I think it gets the point across that, when we're working with docs, we can get into it very early on in the design phase. And we can use that all the way through to commissioning handover. And we can even take that into our operations if we want to keep that project alive and know where our information is.
So what was Docs designed for? It was designed for the entire team. Well, it has a definite construction flair. You don't have to be just into construction to take advantage of this.
Anyone working in AEC, whether it's the architectural or engineering realm, you could definitely get a use out of this. And the idea is it helps solve some of those issues we were talking about before. It gives us the ability to have that one central source of truth where we can store all of our content in one spot.
We can view our content in that same spot, whether it's 2D or 3D content and whether it's mobile or on an interface with our laptop. And another thing that I really like about working with Docs is it's one of the Autodesk products that actually supports Android and iOS. So if you haven't drank the Apple Kool-Aid, like myself, you still get to come and play.
So now that we've found the solution, how does it help us? Well, we've got five little things that we're sort of going to touch on here to talk about how it's going to help us work our way through. And we're going to talk about publishing.
We're going to talk about sharing, the view, how we look at our content, compare, very important. And then we're going to talk about markups. And we're just going to sort of go through this kind of like at the speed of light, so that we get sort of an overview of what it does. So we have more time for when we actually bring the real product up on the screen. And you can see what it looks like in real time, how it actually works.
So when we're publishing, what I mean by this is how we get our content out into the world once we put it up into our BIM 360 project. Well, inside of there, as I keep mentioning-- and you'll hear me say this all the time-- it's that single repository. It's that single source of truth.
There's one spot where we can store all of our project information. And even if we're uploading stuff that we can't view at some sort of file format we can't use, we still can bring all of our content into this one spot. Think of it as an old school FDP that's just way cooler.
So we can have stuff that we can just store up there and view. We have the stuff that we can interact with inside of the platform to make markups and all that great stuff. But all of this stuff happens in one location. We know where we have to go to get it.
One of the other really cool things is it has a OCR. So when we set up our title block, which we'll look at in the demo, it automatically knows where to look for the title of a sheet and a page of the sheet. And so when we throw up a big multi-page PDF, it pulls it all apart and gives us each individual sheet view.
We no longer have to take that monster sized PDF that they've given us and go through and open Adobe or what have you, Bluebeam, and pull it out one sheet at a time. It does it for us. And I think even cooler is it does that automatically with your Revit file.
You bring an RVT file. You put it inside of the proper location. It automatically extracts all the sheets that you have in the file, and then put them in sheet for you.
No more exporting, DWFs, PDFs, or whatever you have. You just put the model in the place. Boom, you're good to go. You've got the information that you need right away.
Share-- so, again, we're not working on these projects as individuals. We're not one person out there running the show. These projects, especially mega projects, have a bunch of people working together. So we need to get that information to those that need it.
So in the Share feature, we have the document registry. The way that we upload the files and how it's looked after is intuitive. We have access control. As you can kind of see in the picture there, there's lots of different levels of access that we can give people when they're bringing in here, so we know that right people see the right thing.
And this access isn't just user-based. But we also have user-based, we have role-based, and we have company-based. So you have very good control over who sees what and how they see it.
And, of course, we have version history. This is one of the big things that we saw in the beginning that was part of the problem is how do we know that we're working on the most current version of the product? The software automatically tells you that it's the most current version.
Now, I will give you the little asterisks, the little caveat, the little thing that we need to be aware of. It's the most current version uploaded. So if you happen to have a Bob in your office-- and I apologize to anybody named Bob in the office. He's just who I get picked on-- that uploaded a set from three weeks ago, it's going to come up as the most recent version.
But we can fix that. If we have a Bob in your office, mostly we fix that by telling Bob not to be in the office anymore. But that's a different story.
So we get into view. How do we seal this content? Well, we have these awesome built-in viewers. So not only can we see stuff in 2D, we can also see it in 3D.
And we have all kinds of different formats that we can view. We can view it on, as I mentioned, our iPads, our Android devices, on our tablets or laptops. And, of course, when we're in our 3D view, we're working with, say, a Revit model, we can also see the properties inside of the model proper. So if we select on a door inside of the file, we can navigate down inside of the properties tree the same way you would inside of Revit or Navisworks to see where that door came from.
Just a quick slide to give you an idea of the formats that are supported-- some are 2D. Some are 3D. We even have the ability, if you're giving an image, to save your image files in the same repository as well-- again, one spot to keep all of your content in one place.
Compare, so this is a really cool thing. We have the ability to know what's the difference between version one, version two, version seven. version 20. Any two versions that we want, we can compare with.
So we can take PDFs or our 2D sheets that came from our Revit file or AutoCAD file, whatever we're working with, and we can do a comparison to see what changed. So we can very quickly see the differences even if our coordination meeting didn't tell us what the differences were. One of the newer features is we now have the ability to do this in 3D as well. So when we get up into our 3D view, like we have in the screen, not only do we get to see what's different.
But we have levels that we can drill down in to see whether something's been added, whether something's been removed, and who's added or removed it based on discipline. And as I mentioned, any two versions that are inside your project can be compared. The key there is you need at least two versions before you can start comparing, which kind of makes sense.
AUDIENCE: Is it restricted to two?
CARL STORMS: It is restricted to two at this point. Markups, something we've all known to come and love, is how we can put our mark on things as we're working our way through. So markups, yes, we can do markups.
We can do them on our mobile device. We can do them on the laptop app. We can actually do issues in RFIs inside of here as well.
Now, one question that I do get and I'll sort of squash that right away here when we're working our way through, is, well, I've got BIM 360 Field. It has issues and RFIs, too. What's the difference?
It's a great question. When we're dealing with Docs, we want to think of it as issues and requests to deal with the documentation. And when we're working with Field, it's issues and requests to deal with that actual beam that's out in the field.
While the issue may be similar, usually when it comes up in the documentation, it'll be different. So I'm dealing with an issue on the documentation with Field. And I'm dealing with an issue while I'm standing beside that beam or that column in the field. And, of course, we also have access to reports to see and analyze our data that we're working with.
So a quick little summary about what we've learned before we hit the high speed internet is, what do we do? Single source of truth, that's where we want it to be. Just like Moulder used to say-- and I think still says, because they're coming back-- the truth is out there. We just want that truth to be in one spot. So that's what we do with Docs is make sure that we're working on the proper version.
We're able to sync between our office and our field. So we have our information with us. It's always up to date. Even if we're in the field, we have access to the information even if we're offline.
Now, of course, there's always caveats. The caveat with that being is that, if you're working on the field and you don't have internet, you don't have 4G data, the information that you make doesn't get synced until you get connected. But as soon as you get connected, that information becomes synced. And everybody has access to it, which also means you don't need to be online to use the apps.
And, of course, as I mentioned, it works for the entire AEC spectrum. But it really was sort of fit to be working with the construction teams from pre-construction all the way through to commissioning and handover. And as you saw, I sort of pushed that a little bit into design as well as into ownership and operation.
So, what's next? Well, if anybody was here yesterday for the construction part of the conference, you probably already know what's coming up on this slide, but an integrated platform. So all of our pieces talk to each other, data-centric.
So rather than worrying about which file format we have to worry about, which view we're working with, we're just concerned about the actual data. So we're able to channel the data and use that. And, of course, Autodesk Forge, which allows us to have access to third party APIs as well as our custom interfaces, so that we can talk together.
And one of the things that they talked about yesterday that came about is that there is now a-- I'm going to get the name wrong. But there is a marketplace now for BIM 360 products that you can go there. I think there's 50 products on there.
An example would be is you can go to the marketplace. And you can download an integration through Forge with Dropbox or with a Smartvid.io and link that information into your BIM 360 information. So we're now starting to bring those products together, again, creating an even bigger single source of truth.
And just to show you that complete product lifecycle that we have now with Autodesk and where the BIM 360 Docs interface kind of fits in there, this is what we're dealing with from Team to Glue, Docs, Layout, Plan, Field, and all the way down to BIM 360 Ops. All right, let's kill the PowerPoint. And let's take a look at this bad boy in action.
So this is BIM 360 Docs. This is the Home Page for my What's Up, Docs product. So the first thing you'll want to do when you set up a project is you want to make sure that you've got everybody you need to be involved involved.
So if I want to add another person, I can go here to my three little windows, or I guess nine. And you can see we have the ability to go to Project Admin. And from here, I can add people into my project.
So if I go to Members, I can start adding people into my project. We see who's available, what they're tied to. We can select Add and bring in new people.
The people can be from anywhere. The way that this project works is you have a set number of paid licenses. And those paid licenses can give you access to anybody.
There's no limit to your number of projects. There's no limit to your data in place. There's just a limit to the people that you're using.
So I go in Place. I can type in an address. I can find somebody that already exists if I happen to have it. So let's bring in Ned New Person.
I can select him. I can give him company information should I have it. Again, it starts popping up in place.
And then, again, we can give him role. We talked about how we can have permissions by roles, by user, by company. So by giving him a role, we can give him permission individually. Or, we can just say in general all architects or all designers have this level of permission. And so now that person's been added to our project.
Now, one thing to keep in mind as we're working through in doing this is that, as we're adding people, Ned New Person, he'll get an email that pops up. He has to go to that email, and he has to accept that email to become part of that project.
As I've invited him to the project-- so he would be a pending person, or at least a pending person to our project-- he's still a person regardless. But as he's pending, he's using up one of your licenses. So you want to make sure that he becomes part of that.
Or if he's not part of that, you want to make sure you remove him from the project. Because even if he's not active, he's still taking up one of your active licenses. So that's good to know.
Something else we can look at while we're in here-- will I kick it back in here? If I go into my services, the services associated with this, I'm going to quickly go down to document management. And the reason I'm coming down here is to take a look at the RFI process inside of Docs.
So if I select the RFI tabs up here, it shows me how the process works. So as we can kind of see up here on the screen, we have the creator, so the person that makes the RFI. We have the manager, so the person that reviews the RFI to see if it really is an RFI, if somebody needs to address it.
And then it goes on to the reviewer that actually approves that and brings it through. And as you can see, I can decide who is a creator. So on this particular project, everybody has the ability to make an RFI. But I can change that to only architects or only contractors. Or I can do it role-based or company-based.
I can come down to who the manager is, so who is the person or people that are reviewing those to see if there are really an RFI, and then brings it onto the actual reviewer who says, yes, that's answered and pushes that through. And there's a couple different ways we could do that. So we can also have the double review, so that it's not just one person tasked with answering all these and so what we have two sets of eyes to make sure that we're getting the right information during this process.
So now, I go back into the actual document management, and we'll look at what we've got set in place. So we've got two sort of locations inside of BIM 360 Docs. We've got our plans location, and then we've got our project file.
If we go to Plans, this is what we call our hard-wired file. And this is the file that we use to drag in our PDFs or our Revit files, so that it does either the OCR recognition or pulls the sheets out, so that we have access to it. When we come down into the project files, this is where we can have sort of a free for all, if you will.
This is where we can set up our folder system however we want it to be. And we can store all of our project documentation. So as you see, I've got the School Of Rock here.
As I go through, I can click on it. I have other folders that I've brought into place. If I wanted to create another folder underneath School Of Rock, I can select the three little dots, add a subfolder, give it a name, follow my system.
And, now, we've created another folder. So it's really easy to add folders, move folders around to get access to the content that you want inside of our locations. Now, we also have the ability to add attributes to our folders as we're working our way through.
So if there's things that don't come out of the box-- so up top here where all of our, you know, document name, file name version are-- if there's other information that we want to be able to access or to add, we can do that through adding an attribute. So let's say we go to our old stuff. There's nothing in there, but I can go to the little settings wheel.
I can also click the three little dots. And I can choose Add An Attribute. And I throw out an attribute. I can call it whatever I want.
First, you have to click on the spot. And then I have three options. So I can have a text file, where I just input information-- so comments, notes, whatever I want.
I can put in a date picker. So it says when. So when was it old? When was it verified-- whatever I want. And I pick a date through my calendar feature or a dropdown list. In the dropdown list, you fill in. Is it old? Yes. No.
So now, when I put content in there, I can go and I can click and say, is it old? Yes or no. Likewise, if I go up in to my DD and SD department where I actually have some content, I go into my AutoCAD, nothing in there. Go into Revit, PM on the project.
So once I actually have something to assign that attribute to, you see that I have access to the little pencil here. So now, I can select a pencil. In this case, who's the PM for this project?
Pull down, Carl's the PM for that project. And I can add that to that. So we can add this through all these different levels inside of this folder system into the projects at any stage that we need. And we can do that in our Project folder. We can also do it up in our hard-coded folder.
So one of the other things that we can do is we can bring in this content and take a look at it, so as we're bringing in a PDF and as we're bringing in an RVT file to see how it interacts. So I'm going to do that right now, because it takes a while to upload. And then I'm going to go on and show you some other stuff while it's happening.
So we choose where we want the information to go right in my subfolder. We can say Upload. If you happen to have split screen or multiple screen, you can also drag and drop at this stage to bring the information in.
So I uploaded the process, the PDF. It sort of gives me an overview of the process, of what it's going to do. Say OK. It's going to take a few minutes initializing as it's bringing up. And once it brings enough of it up into place-- boom, it's already done-- it's going to ask me for a template.
So the template is something that I've already set up. We'll look at it in a second here, so that it knows where to look for the drawing name and where to look for the drawing number. So that as it's going through doing the OCR recognition, it knows where the number is and where the name is.
So in this case, I've got one that's already in place. I say Continue. And it tells me that it's processing the drawing.
And as it's processing the drawing, I can carry on and do what I want to do. So as it's doing that, let's do the same thing with a Revit file, so we can see how it extracts the sheet. Again, just very quickly, upload the file.
So, again, same process, this tells me what it's going to do. It's going to initialize and take a few minutes. Once it's done initializing, I can say Continue.
And then once again, I can navigate away. I'll get an email when it's done. And I can come back to it.
Now, something you may have noticed as I was doing that, when I was in the Revit area or when I was uploading a Revit file, that I had the ability to upload a file or linked files. The application or the way that it works is similar, but the outcome is different. So if I'm working with structural, MEP, architectural, they each have their own model.
If in this hard-coded place that says Plans I upload the architectural file, I upload the MEP file, and I upload structural file, each one will have its own sheets extracted. If I'm working and I have a link to where I have the architectural file and all of those subtraits are linked into it and I uploaded it as a linked file, it uploads all three files at once. But I only see the sheets from the parent view, so in this case the architectural view.
And you can choose which one's the parent view. So instead of having three versions of the same sheet from each discipline, I just have the sheets from the main parent view. And a lot of times on big projects, if I don't have the other projects linked in, I'm missing information from my sheets-- so, again, a benefit of using that linked sheet view.
So as we're working through and loading that other content up to show you how that works, let me show you how the template process works. So if I right click up here on Plans, you'll see about near the bottom, I have the ability to click on Title Blocks. So when I'm working here inside of Title Blocks, I can setup that title block. That's how I know my OCR is going to work.
So I select this. I'm going to add another one. And it's not letting me. There we go.
So in this case, we've got a bunch of PDFs in place. You're going to need at least something up there to give you access. It's not going to know how to take a look at a title block if there's not one up there.
So I've got some title blocks up there. I choose a sheet as a sample. I say Open. It's going to take a look at the entire sheet.
So it takes a minute to come into focus. And so now, what it's asking me to do is tell it where the title block is. So I go down to the bottom. I select my little Image Crop. And I tell it where the title block is.
So now, it knows where to look on each sheet for the title block. Hit Next. And now, it's asking me for specific things. So what am I calling this title block?
So you click in here. Then we come down. Where is the title? So I activate the title interface. I choose the little selection again. And then I choose where the title is going to be.
And you can see it went in there. And it knows that it's called enlarged plans. Then I click into the number space. And that's not the right space. So then we click in there again.
All right, to video live demos, you get to do things twice. Everybody's excited about seeing things twice. All right, so let's try this again. So we select our titles.
There we go. There we go-- and our number area. And as you can see, sometimes you get a little too high, a little too low.
I, apparently, need my reading glasses today. And there we go. You guys are all much smarter than I am, so you'll do it much quicker than that.
So once we got it back in place, I now have the example. And as you saw, I have three or four of them in here. You can have different title blocks for different consultants, different projects, all that stuff put in place.
But so when you're bringing the information up, you choose the template that you want. And it knows where to look for your sheet number and for your project number as you're working your way through. If we start looking inside of our projects, to look at some of our content, so we start looking at some of our Revit files, right away we can see that they're versioned.
So as you can see, we've got a version number. If I select that version number, it tells me the history of the versioning. So you know when they were uploaded, what we want to do.
We can see we can make copies. We can also do that make current. Again, if we have that issue with Bob that uploaded the wrong information, we can make a previous version current.
If we select on an image-- so I just double clicked on one of the Revit sheets-- I have the ability to take a look at what we've got going on here. So I actually see the sheet view. So, you know, you can zoom in, move around, very similar interface to what you might be used to.
You'll also notice that there's this tiny little green location. So once it understands what the sheet numbers are, it automatically hyperlinks to those sheets. So I see that I've got a section through this area. I'm curious what's going on there.
I can select on that little hyperlink. It gives me a pop-up that says, this is where it goes to. Is that what you want to see? And I can say, yep.
And it takes me there. So, now, I see that information. So I went from my plan directly to the section that's relevant. I could do whatever I want inside of that section.
You'll also see that I can very quickly return back to my original view, or I go into a different location and go look, see what's going on from that section. So I have a lot of functionality. We also have the ability to look at multiple sheets kind of at the same time.
So down here at the bottom, I can select this. And it gives me access to all the sheets in this particular project. So I can jump back and forth between any of them as I need.
So I can select a sheet. It takes me to that sheet. And I see all of that information. Of course, now, if we need to start making some markups or anything like that, we absolutely can do that as well.
So on this side here when we're working inside of the interface for the web, we have the ability to create an issue, create a markup, create an RFI, or see version history. So I'll click that. It tells me the version history that I'm working with and what I'm dealing with. So I know that I'm working on the most recent document.
So we'll start with the markup. I select the markup. I can click Add. And then it becomes very familiar to what you may have done before. We select that, and then we have all of our little tools down at the bottom to make our markup.
So if I want to add a markup, I can just sort of freehand whatever I want inside of the space. I can add some information, maybe a little text. And then when I'm all finished, I can say Done. And it's added that markup into the project.
You'll also see that it has it set up as private. So perhaps this is something that I don't want to share with the rest of the team. I'm just contemplating. I'm speculating things for me to check later.
I don't have to push that out to the project right away. If I do want to push it out, I've decided, yeah, this is something that needs to be addressed, I want everybody to have access to this markup, then I can just go ahead and hit publish. And it will send it out.
It gives me a warning to make sure that I know that I'm going to publish it. And then now it syncs up to the project. And everybody that has access to that view inside of that project can absolutely see that.
Likewise, if you want to create an issue, I can select the issue. And then I choose Create. And what it's going to do now is it's going to give me sort of a little crosshair.
Because it's going to ask me to choose a location that this issue is dealing with. So you can zoom in. Select where you want it to be. Give it a name.
Put in whatever you want it to be about, description. And then we can see who we want to assign it to. And, again, we have the ability to assign it to a particular user, to assign it to a particular role, or to assign it to a particular company. So I'm going to send this to Eric, the engineer. We can add a location as well. Yes.
AUDIENCE: Are those translated over to newer versions?
CARL STORMS: From one version to another?
AUDIENCE: Yeah.
CARL STORMS: No.
SCOTT: Did the markups you created transfer your reversioned [INAUDIBLE]?
CARL STORMS: Oh, they do.
SCOTT: Yes.
CARL STORMS: See? That's why we keep Scott in the room. See? So that's why we do that. Awesome. Great stuff.
Now, the other thing is we can put them where we want the location to be. So lower level-- and I did that before I finished creating it. So you don't want to do that.
And then if you want, you can also choose a date when you want that completed by just to give you the access for what you're looking for. And you've gone ahead, and you've created that issue. And it goes through, and it's part of the process.
If we go back and take a look at our interface here-- a couple things. We see that we've got a little red icon here. So when I select that, it's going to show me that some of the information that I've brought through has been published and is ready to take a look at.
So say, for example, that PDF that I sent through, I can go say View. And what it's going to do here is it's going to tell me that information has come through. If I had sent through, say, 100 sheets and for some reason there was a sheet where the title block wasn't in the right spot or there was information missing, it's going to have us come through and review all of that.
So just like here, I have to tell it to publish it before it sends it out. So I went through. I made sure that I got that information correct. Yup, that's the right number. That's the right name.
You do a quick site verify that it's all OK. And then you go ahead and publish that out. And then once you publish it out, it goes ahead and sends it up. And everybody has the rest of the access.
And we can go through same thing with the project that came through. With the Revit file, you'll see that it tells me that it brought up one model, the model's all in place, and that now we have 10 total documents inside of that. So it went through. There was 10 sheets inside of that project. We now have access to all those sheets.
The other thing that we were talking about-- and as I was uploading, I sort of skipped over it quickly, but we definitely want to circle back-- is the permissioning. So, again, if we're adding permissioning, we talked about having a user base. We could do it at company or role level.
We could also do it at different levels inside of the project. So I can add a user-base permission to the main folder. Or I can come farther down into the project as I want. So as the further down you come, they have access after that level.
So if I go to the CD folder and I right click and I apply permissions, I'm now applying permissions to this particular folder. And you can see the two people that are the project admins inherit sort of the highest level of control for this particular project. We want to add more people in place.
So you can start typing in. So Eric the engineer, I can add him. And then they start with the very basic level of control. So they can just view stuff.
We want to get a little more information. You know, we can view and upload. We can upload and edit, or we can control. When you have control, that means inside of that location.
So if, for example, the CD folder, Eric would be able to invite people into that folder, nothing outside of that folder, but just in that folder. Because he has that permission. So we don't want to give him that much control. We'll just give him upload, control, and edit.
And now, we've given that permission. And again, whether I do that at this level, I can do it throughout the interface. And again, the big thing to keep in mind that I keep stressing-- user, company, as well as role. So there's lots of different ways to give that permission as you're working your way through. Question?
AUDIENCE: Do those permission characters [INAUDIBLE]?
CARL STORMS: Correct. They carry down. So if I were to give that permission, instead of at the CD level, if I went up to the School Of Rock, that would filter all the way down. So it goes down, but it doesn't go up. Yes.
AUDIENCE: You might have [INAUDIBLE] but are you able to link RFIs? Because I'm looking at this document management tool.
CARL STORMS: Yep.
AUDIENCE: The one thing that I haven't seen yet is being able to do my [INAUDIBLE] and link RFIs and turn over that file setting.
CARL STORMS: Yup.
AUDIENCE: So you have that function?
CARL STORMS: So link in what way? Again, remember, the RFIs and stuff is linked to the document itself. So what is it that you--
AUDIENCE: [INAUDIBLE]
CARL STORMS: Yep
AUDIENCE: [INAUDIBLE]. How does that work?
CARL STORMS: So let me show you. So if I go into the RFIs and I'm going to create an-- actually, let me go into the folder, so that I can do it actually on a document.
AUDIENCE: Say I don't get a new drawing, but it tells me that [INAUDIBLE] to the template.
CARL STORMS: Yup.
AUDIENCE: How am I going to show that on the documents?
CARL STORMS: So if you have a location to put on the document, you can select the document. So I can go into a folder. I can select the first floor plan. I can markup an area. And I can put information on there.
I can select a plan. And I can make an RFI without actually selecting anything on the plan. And you can make an RFI that has nothing to do with a plan or a model that's just based on that particular project.
AUDIENCE: I guess maybe I'll rephrase it. So if I'm managing a project, I've got an RFI that's been sent out, right? And I need to make sure that this RFI that's been answered is communicated to all my subs, specifically the ceiling contractor.
CARL STORMS: OK.
AUDIENCE: So he needs to know that. So I want to be able to mark up these plans that I'm sharing with everybody so that he can have that information. So I'm kind of looking at an RFI that's been answered, maybe a [INAUDIBLE]. And then it links it to RFI, so you can read that.
CARL STORMS: So when it comes in-- I'll do this here where we're looking at this particular view. We can see that we also have a colored scale that tells us what we are. So say, for example, you know, emergency door, we select this. And we go through, and it's going to tell us that this particular RFI was rejected.
Now, when we do this RFI, it can be assigned to a particular person. Or in this case, we're dealing with ceilings. You can assign it to the contractor or the ceiling contractor. And then they'll see all those RFIs.
And whether it comes to the entire team or whether there's a person that takes all that information and parses out the sub folder trade, they have access to all that information. And if you get the RFI and you send it to your ceiling contractor, he's going to get an email very away that says, there's an RFI based on whatever. And you click, and it comes up.
AUDIENCE: That would be a beautiful way that it works, but really what happens is is that my guy shows up on site. And he looks at a current plan that he just downloaded. If it's not valid, he's going to put it in the [INAUDIBLE]. Because that gets-- it gets [INAUDIBLE], right? If I send it to the project manager, he might have more options [INAUDIBLE]. How am I creating-- because, to me, this looks like a great way to manage a working set.
CARL STORMS: OK.
AUDIENCE: And also to get versions and stuff like that. How, when I tell that contractor, did you download the drawings today? Do you have the current plans? And he didn't see that there has been a change, because there's been no new document to modify that. All there is is an RFI. And I really want to put a [INAUDIBLE] on that [INAUDIBLE] and say, hey, you better look at this RFI, because you're responsible for that.
CARL STORMS: You could do that on the plan and send the RFI directly to him. You can send the RFI directly to him. So you can do that when you send it to-- whether you do it on the app or in the interface, you have that ability. And, again, there's that disconnect-- well, not disconnect-- the difference between what we're doing with RFIs on the document manager level and what we're doing with RFIs in the Field app in the actual field.
But the software only does so much. The software's not going to make people click the button to get that sort of recycle-- you know, what's the latest, make sure I update, make sure I do all that. There's a reason why it works like that. To the right, did I see another hand go up there?
All right, just while we're thinking about that, let's just take a look at what that interface actually looks like on the mobile device where we've got a few minutes here. All right, so this is that same project working on the iPad. So we go back.
We can see what we have access to. We've got our plans, our project files. We got little downloads, our issues, our RFIs.
Pull up our RFIs, it gives us information about all of the RFIs that we have there. Again, we can create another one. So if we're working through the field and we're looking at our plans and we want to create an RFI that's connected to an actual plan, we bring up our plans. We have access to them. We select their plan.
So then it comes into play. We can zoom into the area. Hit the little Add button. We get to choose what is it we want. So I'm going to put in an RFI.
Tap where it goes inside of the location. Enter what we want. Now, a little cool thing about this if you're working with Siri and you have access is that you can just hold down a talk. Med gas location, is the med gas in the proper place? Verified with the med gas in the proper place?
[LAUGHTER]
Med gas room?
[LAUGHTER]
So sometimes Siri's not perfect. But I will tell you that if you are on the job site and you have access, in that case you need 3G, because you need the internet-- way easier to do this through talk than it is to try to type as you're working your way through. So then I can choose when it needs it done by.
And then I can choose what sort of state. So I can leave it at draft. Maybe the guy's around the corner. I can just ask him or for whatever reason. Or you know, I'm going to send them all up when I get to there. Or I can put it into submitted, and I can save. And it's going to send that out.
And it's associated to that location in the plant. So, again, you asked where it is. I put it there. It's associated to that location. When they get the RFI and they click the link, it takes them to that location.
And you can sort of see that we have a very similar interface when we're working with it here on our iPad. Same way if I take my Android device, and I pull up the app on my device here, I can now go back and look at those RFIs. And if they showed up on my phone that I need to take a look at them, I can access them and make changes directly from my phone.
So med gas, I can select that, choose what I want to do. And I can make adjustments to it on the phone and send those back to the device as we're working our way through, again, depending on if you were the person that was given the access level as you working your way through to have that. So, again, it is all connected. We do, whether it's Android device, Apple device, on the screen, we have access to all of that information as we're working our way through.
AUDIENCE: So can I follow up my question?
CARL STORMS: Yes.
AUDIENCE: You just did a cloud right? I've got a question.
CARL STORMS: It wasn't a cloud. It was a TAC, but yes.
AUDIENCE: It was a TAC.
CARL STORMS: Yep.
AUDIENCE: Because that;s what my guys in the field are going to look at and see I've got an issue. Can you hyperlink that to that entered RFI?
CARL STORMS: Yeah, when you click the information, it takes you to that location.
AUDIENCE: Perfect.
CARL STORMS: And you can also add-- you can add additional-- you can add RFIs into the-- not RFIs, sorry-- links, hyperlinks in the project when you're doing that as well. So you could put a markup associated to that.
AUDIENCE: Is it only archives that are indicated here? Or if I've got an architect that's using a different RFI form or just a project, can I link that to a PDF?
CARL STORMS: So that's a good question. For now, I think it's just in the project. But I'm not 100% sure if they can link external RFI programs into it.
SCOTT: Can I follow up?
CARL STORMS: Yes, please.
SCOTT: So it is a PDF. You can upload that project files location as a PDF, create the archives in Pushpin. And then inside that RFI itself is an attachment. And you get attach it to that PDF document inside the document.
CARL STORMS: Oh, yes. Good call.
SCOTT: And [INAUDIBLE] actual view of the Pushpin, it'll show the [INAUDIBLE] actually associated with that [INAUDIBLE].
CARL STORMS: Yes. So just what he said there, I don't have that particular workflow in place. But if you look up here, you see all the issues. You'll see that one of them does, in fact, have the attachment here.
So if I click the wrong sync, I go to the next page. There's the attachment. I can select on it. And there's the markup what I have.
AUDIENCE: When you're mobile, the first thing an attachment wants to do is pull from the camera [INAUDIBLE].
CARL STORMS: That's right. That's exactly it. So if you pull up that--
AUDIENCE: [INAUDIBLE]. But you can also attach another document.
CARL STORMS: Yes, exactly. So after you do the photo, it'll give you the option to attach a document or multiple documents, bring them up either from inside your device to [? like amend. ?] Sorry, question. Yes.
AUDIENCE: Is there a way of initiating an issue and then taking it out, [? casting ?] it out to an RFI once the status changes?
CARL STORMS: As far as I know, an issue is an issue. And an RFI is an RFI. Now, you know, inside the realm of an RFI, you can go from draft to submitted to answer to reject. But an issue's an issue, and an RFI's an RFI.
AUDIENCE: [INAUDIBLE]
CARL STORMS: Yes.
AUDIENCE: Do team members get emails when another version gets uploaded?
CARL STORMS: They get emails for pretty much everything under the sun. And the reason that I say that is because, you know, I've seen them. Actually, did I have it uploaded here?
So you see here, I get it. You know, if there's been a new issue assigned to me, I've got an issue. I can say View Issue. It's going to take me right to that issue. And I can click on that.
Now, the one problem that it's going to have here is even though that issue went to Eric the engineer or Andrew the architect, because I'm logged in as me, Carl, it opens it up in my interface. You guys won't have that problem, because you're going to be logged in as you on the site, so it takes you directly to you. The only reason I say that is because the permissions or the levels of control that Andrew has are slightly different than I have as Carl.
So what you see here might be different. But the idea is it took me directly to the RFI. And I can see and do whatever I want. And we talked about adding stuff.
So here's that workflow. And if we had that linked in project, I go into my project, go to my downloads, bring in whatever it is that I want to bring in, you know, add the picture. And then it adds it up inside to the project. And I have access to that information through that.
And if I'm the one that has the ability to look after that issue, which in this case I do, I can make that change and say, you know, this is answered or closed. And if it's answered, I can put in a official response. So then it'll put as answered.
People will get an email saying that the RFI has been answered or closed or what have you. They'll get a link to it to go see what it is. In this case, they'll also get that little official response that the project has been closed.
So just before we close up, we are bringing the questions. We just have one more quick little slide here to go through while we're trying to get the interfaces. But now that we've been through this little thing and we've learned a lot and Scott's brought us in some great knowledge here, how likely are you to take BIM 360 Docs for a tour? And while you're taking advance on that, please go ahead. What was your question?
AUDIENCE: Oh, it was related to the other topic. I'm [INAUDIBLE].
CARL STORMS: Yeah. No, no. But go ahead and ask your question. It's all questions now.
AUDIENCE: It's all questions? Oh. So that's good. I'm using the 360 Doc for markups.
CARL STORMS: OK.
AUDIENCE: I actually [INAUDIBLE]. OK. And I do have some silly questions, but they're [INAUDIBLE].
CARL STORMS: No such thing as a silly question.
AUDIENCE: Yeah. let's start with that. How can I filter issues? I mean, I want to make all issues related to [INAUDIBLE] or all issues related to [INAUDIBLE]. I want to add [INAUDIBLE]. So how can I do that? It's extremely frustrating.
CARL STORMS: Sorry, I'm just pulling it up here. So they do give you some filtering ability when you're coming through. So when you're in the actual interface--
AUDIENCE: That I assigned to or in a location?
CARL STORMS: Correct. We see here up on the screen the status of, in this case, the issue, who it's assigned to, when it was created, when I was due. Those are the filtering options we have now.
AUDIENCE: That's actually not going to happen in a big project that use the [INAUDIBLE], OK, these are issues that [INAUDIBLE]. And I need to address them first. And then these are the issues [INAUDIBLE]. It has to be more interactive. You have to get rid of--
CARL STORMS: More ability to filter that out, that's good information for Scott to have him take back to the team, sure. But for now, that's what you have. But the beauty about Doc and all of the BIM 360 platform is, because it's cloud-based-- and events like this, where they get this feedback, the stuff is constantly changing and updating.
And the more we get that squeaky wheel and send that information off to Autodesk, the better the product's going to be. Question number? Sorry. Two, and then we'll come back to you.
AUDIENCE: This one I actually got the [INAUDIBLE] email from one of our collaborators. He wanted to upload the document. And he said, [INAUDIBLE], how can I upload the document that was [INAUDIBLE]? And how do I do it? Do I delete the old one and upload the new one, so they know that it's final? And, actually, it's quite [INAUDIBLE], because there's no approve [INAUDIBLE].
CARL STORMS: So there's two things about that. So the way that it works when we're working with whether it's Docs or the BIM 360 platform in general, is there's this sort of circle of trust if you've watched The Fockers. The idea here is that everybody that's working in the project works together. So we don't necessarily need that iron fist to say you can't touch that, you can't touch that.
We do have permissions, but the idea is that we understand that they're moving up. The way the system works, though, in that interface is that, if they call it project one, two, three draft and they change it to project one, two, three final, the system can't do its interface by giving it the name. Because it does it by the name.
So the first time I upload the file-- version one, version two, version three, version four. But if you change the name or make it a different file, it becomes a whole new upload. So these are things that, if you understand that process going in, they become part of your execution plan and part of the way that you set up your project, which can be an absolute bear to set up when you're dealing with a large project and different people, different ways, different things of setting it up. That's just part of the whole paradigm shift of working with a cloud-based platform with BIM in general. Yes.
AUDIENCE: So I didn't want to take everybody's time, but it was all to the permitted-- the notifications, right?
CARL STORMS: Yup.
AUDIENCE: You said everybody gets notificated all the time. Can you control that? Because if I get notificated all the time, I'm starting to ignore them.
CARL STORMS: Correct. And that was a bit of an exaggeration. You don't get blast with it. But if it's an issue or an RFI or something that pertains to you or your company role, then you get those issues.
AUDIENCE: Does the administrator have the ability to control that? And then does the use also say, I don't want to get these notifications.
CARL STORMS: So the way that it sets up is when you're put into the project, you're given those levels of permissions. The emails will go to your permission level, essentially. Some the other platforms do have the ability to do that, like Field, for example, where you can say, I don't want to get those emails. But this one, what it is is what you get.
That's our time. So thank you very much, everyone. I'll be here for a few minutes if you have any other questions.
[APPLAUSE]
Downloads
태그
제품 | |
산업 분야 | |
주제 |