Managing Review and Approval Workflows with BIM 360 Document Management

PRESENTER: We are going to begin. I got the door closing behind us. So thank you. Welcome to day one of AU and right after lunch.

So I'm going to try and keep it upbeat, keep you awake. Those of you who have got like big time zone changes, it's awfully hard when you cannot see the sun. but we've got one hour. We got a lot to cover. And so let's get started.

First of all, I'm a product manager at Autodesk. And I live in two worlds. One is here today in talking with you and talking with customers about the functionality that we have today.

But I'm always planning and working with my partner in crime, Don Yang over there. Stand up. He is a bi user experience. We call UX designer for BIM 360 Docs. And we're always thinking about the next thing.

And so a lot of times we'll say, that's roadmap. So just so you know whatever I say today is true today from what I understand it to be. But it might change tomorrow depending on priorities and all of that. So just have to say that.

And anyway, now let's get on with the show. First of all, we're going to do some polls. So I don't know how many of you-- I see a few faces that were here early this morning in this same room. I can't believe I have the exact same room for both of my classes.

And we did a technology-- it's called Poll Everywhere. And it's fun. You can just use your smartphone. Go onto a browser pollev.com/bim360docs. And I'm just going to ask a couple of questions.

It's just a way for us to get to know each other a little better and inform me as I start speaking about this exciting new feature that was just released November 7-- the Review and Approval Workflow.

We will have a dedicated Q&A at the end. We have one hour. I'm going to try and speed through all of this in about 45 minutes. So that we've got a good 15 minutes of questions.

And the presentation will be posted afterwards. I will post a PDF up to the AU website. And I didn't do it before, because I like to make last minute tweaks. And so that's what's happening. They also are recording this session.

So I don't know exactly where you find the recordings. But I'm sure it will be very intuitive once you go home and find that.

So here's what we're going to do-- a few introductions, a few questions. Just going to do a brief overview of BIM 360 Docs. What's available today. Then I'm going to go straight into the Review and Approval Workflow. And then talk about how you might apply this workflow capability that we have today to certain workflows.

There's a couple that I've heard over and over again from customers. One being, hey, I have drawings that I want to make available to the field. But my project engineer-- I want to review what they send out before it goes. So that's one.

The second one is more of the BIM level two PAS 1192 type workflows that is more typical in Europe and Australia, New Zealand, and how you might manage that review and approval in that formal process to go from Work in Progress to Shared and from Shared to Published. So those are a couple of examples we'll look at. And then we'll do the Q&A.

So the first one-- it's working. Tell me where you're from. If you were not here this morning you won't get how relieved I am that this is actually showing up. But very funny-- this morning I had someone who was like-- oh, OK. There you are again. Who is that person?

So it's fun. You can just zoom in on your phone. You can pick your spot. So we've got a lot from North America. We've got a few folks from Europe and the northern part of the hemisphere and-- oh, my person down by Antarctica has moved.

So that's probably good. It'd be a little cold and lonely down there. I'm not quite sure what you're building. So anybody still filling it out? You got it?

OK. This gives me a good idea. So mostly North America, Europe, and Canada-- all right-- and Australia. Nobody in New Zealand.

One more question, again. This one is-- sorry. Let me make it so you can see what the question is. It is tell me your role. You can see it. I can't. Unfortunately these folks here at Autodesk University changed my screen resolution. And now it made it kind of interesting.

So, yeah, it's like who's here? I see BIM managers, VDC, drafting, lead-- like the leaders here, directors, engineering, technology. So it's a really good mix of folks. But in general, I'd say the theme here is you're trying to control and manage this process.

That's what you're trying to do and make this standardized for your company. You are in the absolute right place. Now BIM manager, awesome. I love that.

So very quickly I'm just going to talk a little bit about Autodesk BIM 360. You're probably hear this a lot. But just to set the context for what I'm about to show. Many of you have probably seen this before.

This is the overall BIM 360 platform for the AEC industry, from design through construction and in the handover and operations.

And there are three layers on the bottom. The first one is our Autodesk Forge. This is our cloud platform. This is where all the open APIs are. This is where you can connect to those third-party applications.

The next layer up, Project Data. That's where I live. That's where Dong and I are working all the time to enhance and improve and add to that single source of truth, that common data environment for all your project models, drawings, files, specifications, manuals-- whatever that might be-- the photos. All of that is in that centrally Manage Project Data.

Then I'm going to skip up to the top to these different phases of construction from design, preconstruction, field execution and handover. We have different capabilities that's all part of the BIM 360 portfolio.

And all of those capabilities-- whether it's field management, quality, safety commissioning, model coordination, design collaboration-- all of that works and directly integrates with that project data that's managing BIM 360 Document Management.

So it all works together. It's all Next Gen. So you'll hear us talk about that. We talk about classic BIM 360 Field or classic BIM 360 Glue. Then we talk about Next Gen. This is all Next Gen including Docs.

We just happened to have released our first version two and 1/2, almost three years ago, a little earlier than the others. But it's all part of our Next Gen platform. And then, of course, it's also integrated with our design applications.

The overall platform, this just gives you a little more sense of the different modules. At the bottom we have Unified Administration, Account Administration, Project and Administrations. This is where you add users, where you've set their overall rolls and the overall rules.

Then with Document Management, that's where I live and breathe. And some of the capabilities around markups, reviews, and set management and document reviews and approval and all of that. We also have our home page. We have dashboards and reports.

These are all for the standard processes we have today, whether it's issue management, RFIs-- if you're using the project management-- up above the field management, Next Gen. We just announced Cost Management. So this is new.

It's in a limited availability at the moment. But this is really about managing your project cost. Model Coordination, that's a next generation of what we do with Navisworks and Glue. It's all in the cloud. And then Design Collaboration, which is that cloud worksharing connected all into BIM 360.

So all those cloud worksharing models go straight into Docs. And you can see them there as well. So that's the overall platform. Now, with Document Management, there's four buckets of capabilities.

Managing and Control-- that's why you're here today. That's a big part of what we do. It's also about publishing and sharing and making available to the right people at the right time-- the review and collaboration, markups, issue management, approval workflows, and then those connected workflows.

So there's a lot to cover in our very short time today. So I'm not going to go into a great level of detail. But this is just to give you a sense of the overall capabilities in BIM 360 Docs today. Permission controls, we have the activity log. Everything is tracked. So you have a full audit trail. .

We have all new issue management. We have the standardized project folders. So when you set up a project you can have it look the same way, with the same folder structure every time. Around publishing and sharing, you'll hear me talk about PDF drawings. Because there's a lot of PDF drawings out there on the job site. And we need to support that.

But we also have some great capabilities around design data, whether it's from Revit or AutoCAD or DWS, or other formats as well. You can do 3D viewing 2D viewing, all of that directly within the browser or on iOS and Android apps.

Couple of other things just to think about and know-- model compare. So managing risk of understanding what has changed. So we have 3D and 2D compare of Revit data as well as 2D compare of PDFs and DWFs and DWGs and IFC as well.

And then finally, it's just about being this connected, single source of truth. So that is Docs as fast as I could possibly talk about it. I could also talk all day. I actually did talk about Docs all day yesterday at the Connecting Construct Summit. And I still have a voice. You can tell I like this stuff.

Document Management-- bunch of different workflows. All those capabilities, those features, if you will, they really boil down to these types of workflows for your project teams-- whether it's design sharing talk about Document Review and Approvals, change identification, comparison, managing that risk, Document Set Management, Issue Management, getting docs to the field, whether it's drawings or models, and just overall managing your project data throughout that lifecycle.

So like I said, if you had seen this last year at AU I would have shown you, hey, we have these other modules that now work with docs. But they all had a big red preview label on them, except for Docs. The previews are all gone. This is all available.

It's very, very exciting. We now have really taken that Next Generation platform to the next level in availability. So now without any further ado, I'm just going to talk about Document Reviews and Approvals.

This is a brand new feature released November 7. That was last Wednesday. So it is hot off the presses if you will. And what is it? It's really to help people who are in that Document Manager role to manage and organize that process and really facilitate it and automate it, so it's really easy for the participants to just use Docs. And it works in a very intuitive way and run through the workflow.

So they don't really have to think as much about what do I do with this next, because there's a configurable workflow engine underneath the hood that is supporting-- OK. Here's what's next. This is the next logical step. And this is what we do.

At the end of the workflow, what you end up with is what you see here. This is a zoomed in view of the approval status. It's a new column and the list view in any Document Management folder. And this is for project files or for the plans folders, those published folders.

So it works throughout the folder hierarchy. And you have different approval statuses. So a little more detail. And don't worry about craning your eyes to see this. Because I'm actually going to demo it live. Here's the key components.

The first one is workflow templates. You can set up any number of workflow templates for your project. You can edit them as you need to. You can decide who can start a workflow, who can be a reviewer, who can be an ultimate approver.

You can also then for the individual, they can initiate a workflow. They can select documents and start the process based on what that admin, that document controller set up for them. They might have a choice of one workflow. Or they might have five depending upon who they are and how you want them operating.

There are notifications. So the workflow engine is going to say, this person is assigned. And you could see that in the ball in court in the action items. Right now it's in the list view of all the workflows much like we have with issues in RFIs.

But you can also send notifications. You can also notify other people. So you want to-- some stakeholders-- you want to make sure they know that this is going on. This has been issued for review and copy them on the notifications.

Once the review starts, you can use the markup tools as well as new capabilities to add comments at the document level. And this is encompassed within that workflow. So you can always see those written comments in addition to markups that are on the drawings or models.

And the approval itself-- you can configure what the terminology is. So you don't have to use approved or rejected. There's basically a status of is it approved or is it not?

But there's those shades of gray, where, it's approved with comments or, revise and resubmit. You can use your own terminology whatever makes sense for your region, since we've got people from all over the world. Everybody does it a little differently.

And then the action after approval. So by default we will then apply that status like I showed on the previous screen. But in addition, you can choose the option to copy the approved documents or models or files from one folder to another.

And this is how you facilitate that Work in Progress to Shared-- these approved documents are now in a folder that has much wider audience. It's going from the internal design team to the external design team, from the contractor to the subcontractor.

So that's what that is intended to do. And it all follows the rules of the permissions that you've set up in the folders. And then finally, this is fully available in both our US and EMEA data centers. So just from the get go, we had made it available for both. So it's available for all.

Now I'm going to take you through some screenshots and then I'm going to go live. But I wanted to have these to just walk you through it and show what we do. The first thing is the workflow itself.

We have this concept of somebody is an initiator. There are reviewers. There can be more than one review step. But for the sake of this demo, I'm going to just say there's somebody who starts the process. Then there's a reviewer. And then there's an approver.

And in this case, whoever initiates it will select the documents for review. They will select the available workflow, whatever workflow they've been given permission to use. And then they will initiate that review. They'll select the documents. They'll say, yep. That's what I'm going to do. And then it goes to the reviewer.

The reviewer will receive that notification. They'll see themselves in the list as it's your ball. You got to grab it. And they'll start the initial review. They can add markups and comments and then submit. So by virtue of then submitting that, it will go to the next stage.

Now I also wrote submit review or release task? We put that in there because somewhat you could have a workflow setup where multiple people could go in and review that. But someone grabbed the ball.

And the way we've set it up now in our first release is that one person out of many would grab that ball and then take care of it. In the future, we intend to add a parallel step where you'd have multiple people that all have to review it.

But for now, one person grabbed that. And then they didn't get to it. Or they got sick. Or they went on vacation. Or they say, you know what? I need Don to take care of this for me. So I'm going to release the task.

But what if they were out and they hadn't finished? As a project admin, you can go in and release the task from them so that you have control and keep the ball moving. So someone else could grab it. So then it goes through the markups and comments. And now it's going to go to the approver.

And here you start the final review. Again, it's talking to the workflow engine. And you say, OK, I'm grabbing this. Start the final review, add markups and comments if needed, select the approval status, whatever status was set up in the workflow setup. And then Submit and Close.

That's it. It's really logically set up to make it really easy for someone to start the workflow, let the folks know who need to take action. And then go through to approval. So now we're going to take a look at what does that look like in BIM 360?

So here you have to be a project admin to set this up. So you'd go into project administration. Under Document Management, we've added a new tab. So we used to have just Activity and Advanced Settings. Now we have Reviews tab. You select Create Approval Workflow. And you start the process.

You can select from one of three templates. Now, I want to make it clear-- underneath the hood, we have a configurable workflow engine. What we have done is said, we are going to build some templates out of the box, out of the cloud so that it's easy to just grab them and use them.

Ultimately, our customers have asked for, well, I really want a tool that allow me to create however many steps I want. Don't worry. If you'd been at my roadmap session, you would have heard that, yes, we hear you. And we will get to that place at some point in the future.

But for now, we have these templates that we validated with a lot of customers that it meets the bulk of their needs for the time being. So you select a template. Here, I chose two steps. It's going from the initiator to the reviewer to the approver.

All right, let's set this up. This is where you then can give it a name. Call it whatever you want, whatever makes sense for your business. You can give it a description. And then you set a user role or company-- just like everything else in BIM 360-- who can start a workflow, who can be a reviewer, who can be an approver and how much time they have.

So you can set durations for each step so that if it is overdue, that's going to show up in the approval list dashboard. Now scroll down because it's a little more setup to go. Here is where you set those status labels. Like I said, you can call them whatever you want. And you can set the action upon completion.

So that is how you set up a workflow. Takes a couple minutes at most. And then you can manage your workflows here. So now I magically went from having no workflows to all of a sudden, how many are there? And at any point, you can deactivate a workflow.

You can activate it. You can copy it by duplicating it and then doing some massaging to it so that you don't have to just start from scratch every time. So it's really for project admins, for the document controllers to control when and if these types of workflows are used.

You can imagine that, hey, at one point in the project you have certain workflows you want to make available. Once you moved-- later on in the project, you may not need that anymore. And so you can then deactivate those. And it won't be in the face of everybody who's trying to set a workflow up.

So that is how you manage them. And with that, I'm now going to go to a live demo. Here is the fun part. So I'm logged in to Docs. As you can see here is a new tab. There's Issues and Folders. You also see a new tab called Photos. This is because my project has early access to the new photos feature that we're announcing here as well.

But we're here for reviews. So I'm going to talk about reviews. This is just list just like you see with issues, with RFIs and everything else and-- Field Management, for example, this list of these workflows. And it shows who created it, who's responsible for it, when's the next action due, what's included in it. And if done you can see which ones-- if they're closed out, approved or rejected.

So this is just a way to access those. But what I first want to do is go into Project Admin and just show you up close setting that up. And why is that there?

So when you go from Docs to Project Admin. There you go. I go into this Reviews tab. What I'm going to do is just go and show you a live one here. It's been set up already. But it's good to see it with all the information filled in.

So you give it a name. In this case, I tried to follow some of the PAS 1192 nomenclature with S1 issued for coordination. And give it a description. I've defined who can initiate it. Who can review it, who can approve it.

And then I can also go in here with the approval status. So for example, if I didn't want to use the term approved, I can use whatever term I want-- rejected, not accepted. All of that is completely configurable.

I can also choose the icon if it's not accepted, if it's approved with comments or let's say-- and then I can choose one that has an indicator that there's a comment there.

I can add other statuses as well. So in this case, I can say it is rejected. And I want to say revise and resubmit. I can remove these, have that control as well. Of course, if it's revise and resubmit I think I'm going to make that the big red X.

And then here's the other part, this action upon completion, where I can say, copy approved documents to a specific folder. I can select that. And then it's just going to take me through my folder structure to say, OK, this one. I'm trying to set this up from Work in Progress to Shared. So I'm going to select that Shared folder and then click Save.

So I'm going to cancel this though. And cancel it since I have a bunch of reviews in progress. And I didn't want to change that. But that's it. That's how easy it is to set these up. And like I said, you can also edit it, configure it, duplicate it, deactivate them, add more. You can have a whole list here. It's really up to you on how you want to use this new capability.

So I'm going to go back to Docs, and also go back to my slides while that's happening. And go to the next step. So participating in a Review and Approval workflow goes something like this.

Again, we went through this diagram before. So now I'm really getting into showing you what it's like for that individual to initiate and then for the reviewer and for the approver. So it's simply a matter of having those models, drawings, whatever they might be, uploaded to a folder in BIM 360.

And then you go ahead and select them. You can select all the documents in a folder or just some. , . Click, click, click, and then you see over here in the menu a new option, Submit for Review. You select Submit for Review. And you'll see a little screen. And I actually cut it in half. So you could see the whole thing on one slide.

You select the workflow. This particular individual has three different workflows they could be using. And so they're going to select the Issued for Internal Review and Comment. They can see it's got three steps.

And then those are the documents. You will also confirm if those are all the documents. Or you can go back and add more and also add some notes.

The notes here says internal milestone review package. Please review and comment. And then you hit Submit. And literally, it talks to the workflow engine. And that assignment goes out. You also have the email that you can send to notify the reviewer about this as well as notifying other participants in the workflow.

So now that person who was assigned goes into their Reviews tab or they click on their email, and they're taken into the experience. So this is not just looking at a folder view this is looking at that approval, organized set of documents that need to be reviewed.

In this case, it's some 3D and 2D data out of Revit. They'll say, I'm going to grab that. Start the review. And then start reviewing the documents and say, OK, click.

And once you go through those documents you can go from one to the next. And think of it as a virtual envelope or a virtual tube of drawings that you're just going through those. You're not having to worry about anything else that was in that folder.

And then once you're ready, you can say, OK, Submit Review. Or like I said, in the description with the flow chart, you can release the task.

And if the whole thing is just, this is just not even worth sending on to your manager, to the person who's the final reviewer, you can also say, I'm just going to end this. This is a bust. We need to start again. And you can do that as well. So that's that end review.

Everything is tracked, like I said before, in the project level activity log. But we also have and display the progress of the approval as it's going through. So you can see who created, who started it, who reviewed it, who's got it now, and then setting that approval status.

You can see here I can add document level comments within this process for showing that. It's got a date. And it's got the time stamp and all of that as well. And you set the approval status. And let the workflow take it through to completion.

What will happen is when that final approval is done, it will apply the status to those documents in their source folder. And if you have set up, hey, I want to copy these over to a folder from WIP to Shared for example, then that will be going on in the background and just happening without you having to do anything.

So that's all about that automation. And here's that workflow list that I showed a little while ago. And something to note-- I happen to be logged in as myself at the time-- and so it highlights, hey, Joan, you actually have something. And it was due on October 16.

I was getting ready for AU. That's my excuse. So that's it. It's really meant to be easy to control and easy to use. So with that, I will go without a net again and go back into Docs and show that experience for a reviewer.

And give it a second. I'm using the Wi-Fi. They have a hard connection. But it doesn't work with my Surface. So there we go, great. And, again, you can start these from any folder in Doc. So it could be the plans folder. It could be project files.

And so let's say I go in here and select some documents that-- see what I've got in here. Oh, it's empty. Someone asked me give me an indication if there are documents in there. And, yes, we hear you. Go here.

I know there are documents in here. I'm going to pick some. These are some 3D models. And I'll just select them and say, I'm going to submit for review. I'll select the workflow. And it's going and saying, hey, what does this person have? OK. And I'll call that a shop drawing submission for fun.

And then I could add notes and submit. It's really as simple as that. And now it's just going through and figuring out who it needs to assign to-- this case-- I can also send this notification and go ahead and send that out.

So now when I go to the Reviews tab, I can see that this guy that I'm logged in as, Ben, has created it. And the next action is due by the project engineer. And it's due on November 16. It has four documents. And that's the current status. It's open.

You can see where there's open and closed here. So now I'm going to change hats or change-- this is the same person. They happen to be the approver on this particular project. And so you can see it went from one person to the next. All of that just happened today. And it is now at that last stage.

So, again, as a reviewer, I can go in. It's going to open this up for me. I get the option to create markups. If you're familiar with Docs, we have private markups and published markups. These are published markups. Because they have to be shared with others who are in this approval workflow.

And you just say, I want to create some markups. And there's a number of different options that we have here. I'm going to create a cloud. And then I'm going to select Done.

So now that's on that document associated with the workflow. Then I could go from document to document. And then I can add other comments as well. And telling the system, yep, I am starting the review. And all of that will then be tracked. It now knows I'm at that final approval status.

I actually had been in here a little earlier and did a few approvals and then left. It saved my work, which is a really good thing if you have a lot of documents. And I can go ahead and finish this off.

I don't know how many more. Or I can say release that task. And it'll send back, which is what I'm going to do and have someone else come in later. So that's all how you work with these reviews.

And then at the end, you can see the approved documents. So for example, this one here, will display-- is this one open? It's still open. Doggone it. Let me find on that's closed. Yeah, so this guy here is closed.

And so you begin. You see all that progress. And then you see the status here as well as if I went to that document in its folder, I would see that there. So we are moving right along. That is how you do these approval workflows.

Now let's talk about some use cases in the real world and how you might apply this. So the first one is controlled drawing review and publish. I had a general contractor based in the US, very large construction company. And he said, you've got this PDF drawing upload and review.

And what we do with PDFs is we do OCR. And then you extract the data out of the title blocks. And you can review those and see. And then get an automatic naming of those documents, drawing A101, A102, A103, like that. That's just pulled from the documents themselves.

However, this individual said, but, Joan, you know the people who were working on those documents and then making them published out to the field, they're usually the more junior person on the job. Because that's what we give them to do. And we really want to review that.

I want a superintendent. I want a project manager. I want somebody reviewing that all the documents are there. And it's all right before you go ahead and publish amount to the subcontractors.

I was like, OK. I think we could use the approval workflow for that. So that's the scenario. What you would do in that case is choose the 1 step workflow. And then choose the option to copy to a folder called published. That's that published folder that you would make available to the subcontractors.

So what does that look like? You've got the project engineer. I've just got two steps here-- just the gray initiator and the blue approval. The project engineer would upload that multi-page PDF, for example, to a folder for review.

They would go through the OCR process. They would review to the best of their abilities to get the information out of the title blocks and then say, publish. But what it's publishing to, in fact, is this for review folder.

Then they would select those documents. And instead of just notifying the project manager, they would actually use the workflow engine. Select the documents for review, select the right workflow, and initiate it.

And then from there, it would go to the project manager automatically who would then start that final review. And if they were markups or comments, they could reject it. But let's say it's all good. And they really just want to say, yep. it's all approved. This is good to go, submit.

And then because of the workflow setup, auto copying those specific versions of those approved documents for the subcontractors. And then that goes into that published folder.

And so they were able to build in that QA/QC process for their particular company and still utilize the right people at the right time using the right tools. And it's all right there on the web.

So that's one example. I'm sure you can come up with many, many more. So another example is more in the BIM level 2, PAS 1192 scenario, where you're trying to manage from Work in Progress to Shared for example. It's quite similar.

But I did want to go through this as we have a lot of customers from that part of the world that have been waiting for this feature and telling me, yes. It's going to meet their needs there. And so you would set up a folder Work in Progress.

You'd set up your shared folder. You'd have the appropriate permissions and the appropriate participants just like you always would with setting up folders and view permissions or upload permissions or whatnot.

And then in the workflow setup, configure the workflow. Give it the name. Most likely you'd use those types of codes like I did-- S1, S3, S4. And configure those. And then choose that option again a copy to a published folder.

Because everything in Docs is about you see what you have access to in folders. And that would be the target folder. So in this case, you've got a document controller in the middle there. Because typically what happens is someone-- the design team says, OK, we're ready to issue this.

It goes to the document controller. The document controller is going to do a QA/QC review. They're going to make sure all the drawing numbers are right. The PAS 1192 numbering is quite complex.

And I'm happy to say I finally understand the code after a lot of great customers explained it to me. And it actually is very logical and everything has meaning.

And document controllers in that part of the world need to check are all the numbers right. Is everything set before it goes to a technical reviewer?

So document controller goes through their step. And then I used a three-part workflow. And then the final one goes to more of a technical reviewer. Is the content right? This could be either-- in this case, it's probably an engineer or an architect doing that final review.

Use the workflow, start the review. Add markups and comments if needed. Select the approval status. They submit and close review. And then my slide like got too short. So then I came back around. And then that auto copy to shared just happens because it was set up properly in the workflow.

And then if those recipients in the shared folder have already set up a subscription notification, they'll get notified, hey, these new documents are there. So you can really blend the capabilities that existed in Docs before November 7 with these new capabilities to start to support your particular document control workflows.

So those are just a couple of examples. Like I said, I'm sure you have many, many more. And now right on time, I'm ready for any questions you might have. I will do my best to answer them. And before I start asking them, I've found that it helps to use a microphone.

You don't have to get up. I saw an arm. Yes? Thank you.

AUDIENCE: Are the workflows that you create can they be input to a template so that can be brought from project to project?

PRESENTER: Yeah, that's a wonderful question. Can they be templatized so you can use them from project to project? That's a goal of ours, much like everything else in BIM 360. At this point, it is set up at the project level. We wanted to get this out to market. But we intend in the future to make this more so you could standardize from project to project.

I see a question way in the back. And then both of you, I will come next. OK? Hi.

AUDIENCE: Is this going to be available via the API yet?

PRESENTER: Is it going to be available via API? That is our intent as well. We don't have published APIs for it at this moment in time. But like many things in BIM 360, we tend to follow our APIs after we first release it.

AUDIENCE: OK. So I just wonder if you have a filter possibility on the reviews? If you can filter on different kinds of reviews?

PRESENTER: So filter on different types of reviews. In the list?

AUDIENCE: Yeah.

PRESENTER: Yes. I believe Don already has a design for that. He's shaking his head yes. So it's a matter of getting our developers to do that.

AUDIENCE: It has a tendency to kind of accumulate a lot of reviews. If you don't do the job after the acceptance. You need to follow it up all the time. And I also wonder if it's possible to get the dashboard to show the status of all the reviews at the same time.

PRESENTER: Yes, that is in our plan as well. So I can't give you exact timing. But what you have today with our dashboards and project home for Docs, in particular, it shows issues and issue trends. And we absolutely intend to add document status and approval status there too.

AUDIENCE: One final question, ma'am.

PRESENTER: Yes.

AUDIENCE: You could do markups when you decline or it gives some additional information to the review process. But could you also do the measuring inside there? Can you add measures?

PRESENTER: Yeah, can you add measures? You can do a markup that's a measurement there. We are considering what other tools would we make available in that approval process whether-- does it make sense to add some of those other tools. But, yeah, I think you can do the measure now that I think about it.

I'll need to check for sure. But just for kicks, let's take a quick look. So I'm looking at this document here. Yeah, I can do measure.

AUDIENCE: Can you kind of capture the measure?

PRESENTER: Yes you can. Because it is a markup tool that you can do a markup measurement.

AUDIENCE: Perfect.

PRESENTER: Sure. I'm so happy to say yes.

AUDIENCE: This has to do with the markup request with [INAUDIBLE] model where we can do version comparison. Let's say that part of my review would be to [INAUDIBLE] subcontracts, whatever, compare version one to version two, the changes that we made. I didn't see a comparison key at the bottom.

PRESENTER: We don't have any comparison tool today. That's an interesting idea to add that.

AUDIENCE: If you're sending it back to RFI saying, OK, we found this. We got some plaque mutation or whatever. I need to see if I'm going to send it back to the designer to compare [INAUDIBLE].

PRESENTER: Thank you. Something is weird with [AUDIO OUT] OK. I'm not going to blame you.

AUDIENCE: So with the comments, are you able to create issues from your comments and red lines? Or is that tracked differently?

PRESENTER: Yes. Today, the comments and red lines are specifically tracked within the-- specifically tracked within the approval workflow itself. And we don't have, at this point, that you could add issues in here as well. I've heard that feedback.

It's certainly reasonable to consider how we might do that. So we're very much driven by user feedback at this point. The whole plan for the delivery of this feature is to say, OK. we've got this out here. We listened to our customers. We did some early access with some beta customers.

Now we've made it available. We're really open to listening to feedback. And we're working on some usability settings. One of the questions I got earlier today. So I'm just going to say it. You saw me set the approval status one by one. Obviously, if you have 1,000 drawings, that could take a long time.

We are working on multi-select and apply to multiples at once. So those kinds of things are exactly what we've been hearing from customers who've had early access. And now it's all available to you.

If you don't know me, I do follow the forums and try to answer as quickly as humanly possible. Sometimes it might take a few days. But we do really want to hear from you and how we can make this better and better.

AUDIENCE: Are there plans to allow the workflows to interact with the title sheets within Revit?

PRESENTER: So the workflows to interact with Revit itself. Could you explain that a little bit more?

AUDIENCE: So in most tasks, then the title sheets will have the initials and the date of the reviewers.

PRESENTER: That's an interesting idea. We haven't really explored that. So I think something for us to look at. All right. I think we have a question over here. Good luck. If you have any--

AUDIENCE: I was wondering if you place the project or your files within the project files part of Docs, are you able to copy in between or move in between project files and plans today?

PRESENTER: Yeah, that is a very timely question. And today you do have to stay within your lane. So you're either working within folders within plans and above the line, as some people like to call it, or in project files.