설명
주요 학습
- Understand the End-to-End Publishing Workflow on Autodesk Construction Cloud (ACC)
- Master Collaboration Techniques and Strategies on ACC
- Optimize Workflow Efficiency and Ensure Data Integrity in ACC Publishing
발표자
- Kristina YoungblutKristina Youngblut is an Autodesk Expert Elite Team member. A CAD solutions and technologies expert with over 20 years of experience in the AEC community. Her main focus is on providing innovative solutions and technologies for manufactured product professionals. She is also an active Autodesk author, sharing tips and solutions with various Autodesk software. Her expertise in guiding manufacturers to understand their product requirements better, creating standards and formats for maintaining file and data integrity, and developing symmetrical content for seamless collaboration across multiple programs. Kristina's passion lies in designing dynamic and constraint-based solutions that help others build confidence and bring their ideas to life through efficient and innovative CAD solutions.
KRISTINA YOUNGBLUT: Welcome, everyone, to ACC Publishing 101-- Strategies for Success and Mistakes to Avoid. I'm your presenter Kristina Youngblut, and I am very excited to have you join me as we explore the possibilities and workflow of content through Autodesk Construction Cloud.
Throughout this instruction, we will learn the ways we can control and manage our various files within the ACC environment, taking advantage of the features and tools available within the out-of-the-box solution. I do understand that there are third-party apps and add-ons that can enhance your ACC experience, but this class is aimed at equipping you with the knowledge and understanding of the default platform. You don't know what you need until you know what you have.
Covering the safe harbor statement from Autodesk. Autodesk frequently releases new updates and features to all of their software. ACC generally has about a two-month schedule when new features and updates and enhancements to different features and software is released. So please check with the Autodesk Help Guide, the ACC Help Guide if you notice any discrepancies between my presentation and the version of ACC that you are using.
Once again, my name is Kristina Youngblut, and I am very much looking forward to taking you for a tour through ACC and watching our content work for us. I've worked within the AC industry for over 20 years in roles across the spectrum, from content aggregation, to software development, to supporting design professionals at engineering firms like CIMA+.
I am constantly seeking knowledge, learning new solutions, making mistakes, and optimizing workflows. My passion is in ensuring teams take advantage of the solutions made available to them, removing their limitations, automating workflows, and fostering a collaborative environment.
Let's take a look at our learning objectives for this instructions. To start, we're going to look at understanding the publishing workflow of our content through the ACC platform. We're going to look at mastering collaboration techniques and strategies. And then, finally, we're going to look to optimize our workflow efficiency and assure our data integrity within the ACC platform.
I have left breadcrumbs for you throughout this entire presentation to help you on your ACC journey. Curious for more details, scan the QR codes throughout this presentation to unlock additional insights. To start off, we have a ACC Learning Center, where you can connect with modules and various tutorials for all aspects of the ACC platform. If you have issues or need help navigating any of the aspects of ACC, this is where you will begin.
Next, we have ACC resources. This is articles, learning links, and forums. Connect with minded professionals within your industry. Lastly, ACC support. This will allow you to reach out to technical specialists related to issues or limitations that you might be having with the software. Your journey to deeper knowledge starts here.
I have built this class to benefit users from all stages of experience within ACC environment. I would like you to head over to the forums that I have created in relation to this class and comment on your current skill level within ACC. While there, please introduce yourself and get connected with others who have joined this class or are seeking additional knowledge. I will share a link at the end of this-- I will share a link with you at the end of this presentation.
No matter the stage you are at in your ACC journey, we always have room to grow. Never assume you know more than 50% to 70% of anything that you are using. Remember, we can never touch every feature. We can't touch every tool. There is always more to learn.
As we only have so much time to go through the workflow of BIM process through ACC, I have saved a few tips to the very end that will help you support your design staff in navigating issues. These are things that come up for me on a daily basis or weekly that I'm able to do to support my design team. So I hope that you find some value in them as well.
Let's take a look at our possibilities. ACC is an extremely complex and robust system, and as we will not be able to cover everything, I do want to cover-- I will be focusing on the front end service, primarily on the project and content management features related to my BIM process workflow. We will begin with Autodesk Docs, covering the basic structure and function that will drive our entire project.
Moving on to design collaboration and model coordination, this is where we can integrate some control and content sharing management, pushing our design throughout the ACC environment and project duration. And, finally, Autodesk Build. This is management's preferred interface and collaboration environment.
Lastly, we're going to-- or sorry, not lastly. We're also going to cover the differences between BIM Collaborate and BIM Collaborate Pro. At the end, as mentioned, I have a few tips and tricks to help you and your design team in all of your daily workflow processes.
Our next breadcrumb-- did you know that you can access ACC on your mobile device? If you have this already installed, feel free to follow along for parts of this session. If you're just learning about this now, please use the following QR code in the slide to install and experience the presentation hands on. You are not obligated to do so. But we all learn differently. And I fostered the ability for everybody to learn however they need.
All right, another breadcrumb-- this one is to the ACC Learning Center related to Docs. This module contains all of the tutorials related to the ACC Docs module. If you follow this QR code, you'll be able to access all of that directly from this link.
So let's start our adventure with a base foundation of the ACC platform resides. Here you can run all of the processes a project-- and here you can run all of the processes your project needs at the most basic level of design without all the bells and whistles. Doc starts on all new projects and cannot be turned off. This initializes with every new project that is started on the ACC hub.
How you start your projects will dictate the amount of effort and time you will need to manage during your design process. Start with a good foundation. We're going to look at how we can start our projects and set up our folders. We'll look at how we can get our files started and integrated into the system. We are going to look and discuss the purpose of bridging, its limitations, and the workflow.
We're going to look at reviewing the differences of save, sync, and publish and how it manages our content within ACC. We are also going to look at versioning and what it is and how can we use it. And, finally, reviewing and communication, how to collaborate with your team in ACC.
All right, I'm just going to head over to Autodesk Docs now. So starting with setting up your project and your folders, it is very important to start from a good foundation. I like to follow the UDS format for my naming conventions, but use whatever is required at your firm or your standards for your company.
Please keep your folders nice and clean. This helps us as we're transitioning content throughout the system because then we don't have this big mess and people aren't trying to find where everything is located. It's also good to start with a clean name. This makes sure that it is easy to find and easy to access and people know what they are working on.
If we head over to the main dashboard, this is where you can-- you would also be able to see the project number as well. So you don't need your project number in your name because this is all searchable within the ACC platform. If you're going to start new templates for your projects, you can actually build these off of a project you have already initialized on your ACC hub.
There's a button under your settings that says Save As Template. You do need to be an account administrator for this. But if you set this up in the beginning, this will save you a lot of time and headache in the future. Remember, how we start our project will dictate the amount of effort we're going to need to control it later.
Let's move into our files. So files on ACC generally don't have a problem. Most of them are drag and drop capable. You can also upload them here.
But one file doesn't act like the rest. This would be Revit models. And please don't confuse this with Revit families. These are separate file formats. This is related to RVT files.
Most files are-- as soon as you save it or upload it, it has created a new version of that file on ACC. But with Revit models, these depend on the state of the file. Are they a cloud-based or work-shared model?
When you're working with the Revit templates with the Revit models, you actually need to synchronize these from Revit to the ACC platform. This is the only way that people will be able to work with them and interact with them. Otherwise, they would just be resource files on your ACC platform. So make sure that you understand how your files are used and how they need to be managed within the system so that you can make sure that people have the appropriate access.
I also like to pay attention to my permissions for my folders. Depending on how you've set them up, your permissions will differ based on your project foundation. So this project has design collaboration initialized on it.
So under my permissions, you can see that this folder only has the architect available, plus two administrators. So anybody with the architectural role will automatically be added to this project. But I don't need others from other disciplines seeing this content. This is the live content within ACC. They would receive their files as consumed packages through the design collaboration. And we will get to that shortly.
Let's head over to bridging. So bridging is to connect with other projects or for other projects to connect with you. This allows you to send or receive information between various hubs or various projects. This content's purpose is for resource content only. It is not intended to be worked on.
So if you need to edit or manage these files, you will need to download it and upload them as a separate entity because you cannot work on your bridge models. If you are required to work on those bridge models directly, it would be best if you were working off that project hub specifically to manage that content.
Let's discuss save, sync, and publish. Most files, save is all you need. This is what will create your version, your new versions, and your subsequent versions of that file moving forward. But with Revit models and the different states of cloud-based or work-shared models, you have the ability to synchronize and publish that content, which would become your versions on ACC hub.
Cloud-based models, you only have your save and publish function. But with your work-shared models, you have the option to save, sync, and publish. Save only will save a copy of that to your desktop.
With the synchronization, this will save a editable version to ACC for the people with editor rights or higher permission on your ACC hub for that file. And publish will be the actual released version of that file on the ACC hub. So understand what your files purpose is, and the way that you're going to set up your project is going to dictate how it will function within this platform.
Now moving on to versioning and understanding what it is and how we can use it. So when you're in a folder and you see your file, under the column version, if you select it, you will see all of the versions, all the saves or publish of that file that have been uploaded to ACC. You have the ability to select two files to compare.
And you also have the ability to make an older version current. In case one of your files becomes corrupted or unusable, you have the ability to go back to another version of that file. I have not had to use this often. But when I have, that has come in handy a few times.
Let's move on to viewing, reviewing, and communication and how to collaborate within ACC. Let's start here with the compare. So this is how we can view some of our content.
Let's view a different version of this file to see what changes had happened. So you need to make sure that you are looking at the exact same file you can. It says that you can change it, but you cannot change it to another file. If you want to view two different files together, that's what model coordination is for. You also cannot view 3D and 2D models together.
So once we have selected our files, I can press Compare. And now I'm able to view those models together with different options on how I can visualize them. And it also shows me some changes and stuff like that. So it's pretty handy.
I can also go into any of the models. And this viewing screen is different depending on the file that you select and the file that you open. But most of them do have the ability for you to comment or add issues to those pages to communicate with your design team on this project. So I can easily just go and add an issue directly to this file, and other people can see it when they view it as long as they have editing rights to this folder.
I can also open other files in here. This is a PDF. And you can see that options that we have available are more robust than it was on the Revit file.
So I actually have the ability to add markups and stuff. And when I add a markup to this file, I have the ability to connect with the design team directly on this file and explain some issues or limitations that it might be having. All of it is contained within the ACC environment.
I also have the ability to compare directly from this view as well, and I can set issues and communicate with the team throughout this entire page. I also have the ability to go through different views if they're available and different visibility types if needed.
Not all files are viewable on ACC. Go to the ACC Help Guide to find out which files you can view or you can't view on the system. I have never had an issue uploading any files to the system before. So if you encounter any files that you're unable to access or unable to upload to the system, head over to the forums and comment and let us know what limitations you're experiencing.
All right, here's another poll. I would like to know what software powers your ACC platform. Please head over to the forums and comment on the software that you manage through your ACC environment.
I have not yet found a file I cannot upload. So if you experience any limitations, please let us know. We would like to know more about it. Are there any files you would like more access to? Are there files that you can't view? Again, head over to the forums and let us know.
Let's move on to design collaboration. And here's another breadcrumb for you. This one is to the ACC Learning Center for Design Collaboration. This will provide you with all the models and tutorials to support you in your journey learning Design Collaboration. If you have any questions or have any issues navigating the space, I suggest that you head over there to find out more information.
First, we're going to look into the importance of setting up your space, discussing the teams and permission settings required, looking into the project status and seeing what information is available to us, the importance of creating packages and how we can create those and how we can share our content. What does consuming of content mean? We're going to take a quick look at meetings and issues and, once again, cover viewing, reviewing, and communication. Let's head over to Design Collaboration.
Before you can start any Design Collaboration, you're going to need to go over your settings. And you're going to need to set your shared folder. This is the folder that all of the consumed files that you will create through this home, through the swim lanes, through the processing, this is where all of it will get shared.
You do also have the ability to set up various coordination spaces as well if you want a more controlled or specific review of information. I have one here set for structural design. And this actually allows my structural team to clash their models with itself. As long as we have the right folders-- or sorry. As long as we have the right publish set up, they're able to clash their model within this system.
Moving on to team setup. And this is why it was so important that we pay attention to the way that we set up our project in the beginning. When I set up my folders and teams within ACC Docs, they are automatically locatable within Design Collaboration. So when I set this up, the system automatically had found these teams for me and carried over the members as well. So I didn't really need to do any work. I just needed to approve it.
I don't recommend adding new members on this screen. I generally try and add them in Autodesk Docs. But if it is something that you need to do because this is the only place they need access, then by all means, do what you feel is necessary.
I do limit my access to users for Design Collaboration because this is just the data and content work-- this is just the data and content processing for the rest of the ACC modules and system. So not a lot of people actually need access to this. I would generally keep it to the BIM process team or the PA for this project.
All right, before we go into the home, I am just going to quickly go over project status because this gives us an overview of the content that has been published and processed that will be coming into the Design Collaboration. It will tell me the files, when it was published, and also the folder link, which I can select on and go directly to that folder within Autodesk Docs.
It also has details. And I will admit that I don't use this as often because I can find all the information I need on ACC Docs, but if you find use in the information provided here, please head over to the forums and share your information with us and let us know.
As you can see, a new team has been discovered. I'm not going to add this right now, but that is what mean. The way that we start our projects is going to dictate how much effort I'm going to need at a later time. The system is going to do the work for me.
Heading over to the home. So as you might be aware, your project n timeline is at the top of your screen. And this shows me the swim lane for all of my teams and projects. You can tell which is the active team based on the one that is at the bottom or the one that's in big, bold letters in the middle of your screen. This tells you which team you are looking at.
We also have the ability to look at individual files within that folder. You actually can create a package from just an individual file. If you are going to view it from the entire swim lane, you will be creating a package of all of the content available within that folder that you are allowing the system access to. For information on what the swim lane icons mean, please head over to the ACC Help Guide. It will describe what these statuses mean and how to read this timeline.
Once we create a package, this also allows us to pick and choose which content will be passed through to the other teams. This is the content that is consumed by the other teams. So if there's information that I don't want to share because maybe that information is only available to the design, the engineering lead for architecture, then I will not publish it.
I will not publish it into the set and consume it into the other teams packages and only the people available, if we go back to Autodesk Docs, in that teams folder, in those files would be able to access that information. So, again, make sure you set your files up correctly. It'll dictate how much effort you need to put in later.
Heading over to meetings and issues. So meetings and issues, we all have them all of the time from the project initialization to project handoff. Hosting your meetings through ACC maintains all of that content within your ACC project and its hub, and it will always be available at any time for review. So it keeps it all contained within the same system.
Please note that when you do create a meeting, this actually creates a new meeting series and not an individual meeting for one of these. If you would like to add a meeting to a series you've already created, that is a follow up.
Also, note that items that you add to initial meetings when you create a subsequent meeting, they will be carried over. I also try not to close anything in an active meeting or a past meeting and try and close it out on a future meeting. But, again, how you guys manage your content and your project is completely up to you.
When you add items to your meetings, they're actually added to this item list over here. I ran into an issue once where I created a meeting in the Meetings tab, and my items didn't come over here. I then created a meeting within the items category. And my items started showing up. This has only happened once. But in case you run into that error, that was my workflow to navigate that problem.
And looking at some viewing, and reviewing, and communication. So very similar to Autodesk Docs. You can actually view the content within these packages and provide comments or issues within this. But because I limit the access to Design Collaboration, I don't find that anyone really needs to comment or mark up in here because they'll be able to do that in Autodesk Docs or actually Autodesk Build, which we will get to later.
All right, I did forget consuming. So let's just hop back over there and quickly cover that one before we leave. So consuming, all this is the package that I created for that previous team, I'm allowing another team to consume. So we can head over to structural. And if there was a little circle with a dotted little lines-- it's a hollow circle, which I don't have one on me right now.
That is a file, a package that we have not consumed. And that is the content that will be uploaded to the client, to the teams consume package. And that will be the information that they will have access to. So make sure that the content you make available to the other teams is appropriate and is going to fulfill the requirements for them to review that content against their own.
Now over to Model Coordination. Here's another breadcrumb for you, ACC Learning Center, Model Coordination. If you need additional help or support navigating Model Coordination, head over to the ACC Learning Center to have the ability to take tutorials or training modules related to each one of these items and the rest of the system.
We're going to look at covering models and what this information is and how it got there. We're going to look at views and how we can utilize these to support teams in their review process. We're going to look at clashes. And when in a game where 0 is the winner, this area can cause a lot of people headaches and anxiety if the number is a lot higher.
We're going to quickly touch on meetings and issues. But honestly, this is the exact same as it was on Design Collaboration. Looking at viewing, reviewing and communication.
Though this is similar to the other modules, there are some differences here. And we're going to take a look at that. And finally, we're going to have a quick discussion about Model Coordination versus Design Collaboration. Let's head over to Model Coordination now.
OK, so the landing page for Model Coordination is the models. Earlier, I had said that we can set up different coordination spaces. You can do that here as well.
So I can head over to Settings. And here I have the ability to add more coordination spaces. I can set a name. I can select specific folders, and I can identify if clashing is on and off.
You can see up here that I have a few spaces that I've created. This shared one is the default one that is created from Design Collaboration when I initialize the module on that side. These three, architectural review, structural, and live, these ones are related to the actual files and content on Autodesk Docs, the content that our design professionals have access to.
So this structural review will allow my structural team the ability to review clashes within their live models. No one else is going to have access to it because this is just related to our structural team. But this gives them an ability to live clash their content.
Heading over to views. Actually, before we head into view, let's create one. So when I create-- when I select a few models to look at, it will bring up the viewer for me. But at the bottom, it will also say, Save View. All you need is a title, set your privacy, and add a description.
Always be clear when you're setting this stuff up because if you're going to be lazy now, no one's going to understand it later. So pay attention to how you set up your projects.
So once I've created a view, I can head over to Views. And now I can see that I have a few views available to me. I can save this to Docs. It tells me when it was created on and also the last time it was updated. And it'll also tell me the privacy. These are both global, so that is fine.
I can expand details and I can see all of this information again. You can also select the name or open to open that specific view. And this will save the conditions and settings that were preset to that view that we saved when initially created.
You'll also have the ability to go to Model Browser, and you can view the information related to this model in here. So this is part of the viewing, reviewing, and communication portion of Model Coordination. Heading over to clashes, this is the clashing matrix. This is where I was saying that in a game where 0 is the winner, this guy is not looking really good.
So this is where the files that have been processed through Design Collaboration or connected through Autodesk Docs is available. And the matrix shows the files clash against each other. So these dark gray ones, it's because these are the same two files, and it's not clashing it together. And then the rest of them will be able to tell you how many clashes between those two files.
I've turned off some files on here, and that's why you can see that these ones, they automatically clash off because I didn't need these files coming through. There were extra files in their published. I didn't need to see those. These are live and not processed through Design Collaboration, so I'm not able to control the content that had come through for this file.
When I set up issues within Model Coordination, those are visible here. These are separate than the issues that are in Autodesk Docs and Design Collaboration because these are related to two separate models being clashed together and unlike the Compare tool that we access through Autodesk Docs.
As discussed earlier, meetings in this area is the exact same as Design Collaboration. There are no differences. So what you set up over in Design Collaboration will be available for you in Model Coordination, but it allows people who don't have access in one module to still have access to the information in the other model. But make sure that the permissions are set up correctly and they have the right modules initialized for their account.
We're going to look at some more viewing, and reviewing, and options. So if we select on a view set that we've created here, we can go and check out the clashes. And we can review some of the issues that were set here. I can then go to an issue. We can set new issues, but I can also comment on this one.
So if I go to the bottom, I can add references, and I can add comments. This is now going to allow maybe the architectural team to comment something to the structural team. And it is retained within the ACC environment. It is all interconnected. And your ability to stay connected within a project is very easy as long as you've set it up correctly.
Now let's review the differences between Model Coordination and Design Collaboration. Design Collaboration is intended for projects that need a little bit more hand-holding. They might need you to process specific information and only give access to specific content at certain times.
Not every team needs to see every published version from another team. So Design Collaboration allows you to control the flow of that information. If your projects are small enough, as I've shown you, you can connect Model Coordination to Autodesk Docs and is very useful for smaller projects.
I have a lot of designers that prefer to live link their models instead of connecting to the consumed packages. So in those cases where a lot of the information doesn't need to be manipulated or transcribed through Design Collaboration, I'll actually just use ACC Docs and Model Coordination for a project. It just depends on what you need. And the features that you require will depend on what you need. How much information do you need to pass through?
Here's another breadcrumb for you. This one is related to ACC Learning Center Build. This module contains all tutorials and help that you will need to navigate Autodesk Build. If you have any issues or would like to learn more, follow this QR code for more information.
Autodesk Build is what Docs is for designers, but for management and contractors. This is the place that they can go to access the content and push it throughout the design phase. They are not designing the project, which is what ACC Docs is for. They are managing the content and sharing that information with outside resources, clients, additional contractors, subs, whoever it may be.
So this is where most of your management will reside. We're going to quickly go over the Home dashboard, then into Sheets and Sharings. We're going to look at the forms, RFIs, and submittals. We're going to discuss correspondences and how we can use it. And then, finally, we're going to have a quick discussion about the difference between Autodesk Build and Autodesk Docs.
So when you initialize Build, your home screen will kind look like this. And this is why management likes this. It gives them the ability to see some of the issues that have been uploaded, and they can access them, some quick links to sheets, and also some information related to meetings, overdue work, or anything like that. They don't have to worry about what's going on in the design phase and if you're having any issues with that. They just need to focus on the management portion of the project.
We're going to go to Files before we go to Sheets because this is where your content is going to come from. And, again, as we said in the beginning, how you start your project will dictate the amount of effort you're going to need later on. So because I've already set this stuff up correctly, the next portion is going to be relatively easy.
I had mentioned earlier that I like to use UDS standard for my naming conventions and stuff like that. So this is my file naming convention that you see A-100. Well, ACC actually uses the same structure, which I will show you in a second under Sheets.
The only files you can process to Sheets is either PDFs or Revit models. When you select the Revit model, you can publish it directly to Sheets. So these are the publish sets that you have initialized, the 2D files within that model.
PDFs, on the other hand. they give you the option to go to Build Sheets or Specifications. ACC does not understand the difference of a PDF and what its content is. So make sure you upload it to the right location. Specifications can only accept PDFs.
So with Desktop Connector, I have the ability to work on my Word document for the specification. And when I plot it, I plug it back to that Desktop Connectors folder as a PDF. As I update my Word document and republish, so does-- ACC accepts that as a new version of that file. So these two files are updating simultaneously.
From here, I have the ability to publish to Specifications. But as you can see, I also have the option for Sheets. So make sure that you are paying attention to where your information is going because you don't want to make yourself a mess later. Let's quickly head over to Sheets to show you how the content that you upload gets processed.
So as you can see here, I have discipline. And it is already identifying the team that is associated to. I did not set this. Because of the way that I set up my project and Autodesk defaults to UDS standards, the disciplines are already pre-set up.
So the first designator, the first letter of my sheet, will automatically associate it to the correct team, the correct discipline. If this is not the order that you have or you use a different designator for different teams, you can edit it here. But I generally recommend following an industry standard. But if your company has its own specific sets and templates that you have to use, please follow what you need. This is completely customizable.
But when I publish my sheets to here, they automatically add. And I have the ability to work with these files. Something unique about sheets from ACC in comparison to BIM 360, BIM 360 used to be able to update these sheets to a new version. It actually now needs to be a new version set to become a new version.
So if you were working on a model and you found out A-100 was actually incorrect and you needed to upload a new copy of it, you would need to remove it to be able to get that version, that correct file up on there. So, again, pay attention, work with your content within your files, make sure you communicate correctly because you only want to publish to sheets when you're ready for these files to be utilized.
OK, Forms, RFIs and Submittals. I'm not going to actually open these because the information that is utilized for those sections comes from all of the work that we just did, all the sheets, and files, and everything that we just set up.
If you set your content up correctly, this information is going to be very easy to use. You're going to be able to transmit your content and be able to provide your information to outside resources or within the ACC environment with little to no issue. So please make sure that your content is set up correctly and working through these sections will be very easy for you.
Let's head over to Correspondence. Were you aware that you could actually send emails through ACC? You can create-- I don't want to do it because it creates a new instance right now. But you could create emails directly in here, or I can even upload an email that I may have received from outside of this platform and upload it. And it retains all of this information within the ACC environment connected to this project.
So I don't use it that often, but I'm trying to change my habits. And I'm trying to adapt to this. If this is something that you've been using and you maybe have some pros or cons about it, please head over to our forums and leave a comment. Let us know.
Let's do a quick compare of Autodesk Build versus Autodesk Doc. So very similar to Design Collaboration and Model Coordination. Depending on the amount of effort or size of your project, you may not need both modules.
With Docs and Build, if your management team is not going to be exporting your content or sharing it through the ACC sub-- maybe they're using external services for that-- then you don't actually need Build. You can perform all the duties that you need within Autodesk Docs. Autodesk Build provides management with the opportunity to access the content and be able to share it for design phases and submissions and for releasing the project at the end.
One more thing in design in ACC Build is that we actually have the ability to export an as built model from ACC. I won't lie, I don't use this yet because the features and options available are pretty limited. But I would be curious to hear from you about if you've used this and maybe any issues or benefits that you have experienced while using the Create As Built option within ACC Build. Please head over to the forums and let us know how that's gone for you.
All right, another breadcrumb, this one is actually going to send you to the BIM Collaborate website and allow you to view the differences and pricing and contracts related to BIM Collaborate and BIM Collaborate Pro. They are the exact same software, except that BIM Collaborate Pro has co-authoring capabilities.
So this is the difference between our cloud and our work-shared model. If cloud-based models only require BIM Collaborate, that only means one person can work on that Revit model at a time. BIM Collaborate Pro allows us to convert our Revit models into work-shared files with work sets and allow multiple people to access that model and edit it at a single time. It does lock out work sets so people aren't jumping into the same thing at the same time. But they are still able to work within the same file.
So depending on your project and the requirements that you need, make sure that you have the appropriate subscription for that service. If somebody is trying to access-- if somebody is trying to access a work-shared model and they do not have BIM Collaborate Pro, they will not be able to access it. It is a little bit more expensive. So pay attention to your projects and to figure out what you need. If you need help converting a work-shared model to a cloud-based, go to the ACC Help Guide for information on how to do so.
We've made it to the end. I really hope you've enjoyed my workflow and processes through ACC and that you were able to understand how I can utilize my files and content to be able to push my project from project initialization to project handoff. So these tips are things that I experienced honestly on a weekly basis and things that have helped my design team be able to navigate issues and be able to continue working without getting bogged down.
So the first one is forced relinquishing. This one might not be a weekly thing, and I think I've actually only used it twice. But it has come in very handy. I don't want you to be scared, but be cautious.
Say somebody leaves on vacation or they have left the company. And they have a work set still open under their name. And you're not able to access it. You are able to force relinquish that model and kick everybody off of that file.
If somebody does have that model open when you do a forced relinquish, it will decentralize, detach their model from ACC, and they will be required to reconnect it. It's not impossible. It's just a pain in the butt. So be cautious.
Next, the advanced BIM process. And that is what I was demonstrating here today. Design Collaboration and Model Coordination really help enhance the BIM process in allowing us to streamline the conversion and management of that content through the ACC platform and making sure that the appropriate parties have access to the appropriate information.
Now, you guys may use ACC and all of these modules differently, but this is how I utilize the software, and the workflow, and ideas that I've come up with at my role at CIMA+. The next one, ACC files, delete doesn't really exist. I'm actually going to head over to ACC Docs right now to show you what I mean about this. You can never, ever, ever delete anything ever off ACC.
Please don't upload multiple copies of a single file. You will regret it. All content is available under it's folder under delete. I can access anything that I want that has been deleted in the past at any given time. You can see that I can access a file from February. And all I need to do to bring it back to the project is press Restore.
You can never delete anything. That is why it's important to set up your folders and your files correctly, making sure that you have clear and consistent naming so that people can easily locate and find that information.
If content needs to be available to multiple people, put it in a resource file or somewhere else, making sure that people have the appropriate access that they need and that they're not having to make copies and duplicate things because that is only going to create a mess. Make sure that your project administrators and people who have managing access to your ACC actually know how to use the system.
Because if somebody gets in there and doesn't know what they're doing, they could treat this as a cloud-sharing service. And that is only slightly the purpose of ACC. But if they treat it that way, this could become a mess. And using the other modules will become a nightmare.
All right, Revit. This one is specifically related to the Revit models. And this is more access than just the published models that get put up onto ACC. So I showed you how we can revert back to an older copy of that model. But with Revit models, in Revit itself, you actually have access. So if you go to a file, you go to Version History, you have access to the synced models of that as well. This is only related to Revit RVT files.
So from here, I can also restore to this version. So just say a last published, the two publishes, there was some type of issue. And I actually had to go back to a synced version. This gives me the ability.
I've only needed to use this once in the last year. But there was no other way to get what we needed without this feature. So it is not a common action. But when it's going to come in handy, you're going to appreciate that it's there.
And, finally, Desktop Connector. This one I do experience possibly daily. Ah, weekly for sure. The last couple of weeks, it has been daily. Most people's issue when they can't view content and it's not related to permissions or access to their ACC content is related to Desktop Connector and actually their cache.
So using the reset utility for Desktop Connector will clear out their cache from the system. This does not delete ACC, and this does not delete their access to the file. This just cleans off their computer. And next time that they open it, it will reestablish that link and redownload the content. I promise you, this has covered at least 95% of my Desktop Connector issues over the last year.
I would like to give some special thanks to some groups and communities that have supported me and have been a huge part of my path and journey with Autodesk and with ACC. To start with, I have the ACC Community blogs. I joined the ACC Community blogs a few years ago looking for an opportunity to share some of my knowledge and experience and connect with like-minded individuals.
I found more than that here. I found colleagues and friends that I would have found in no other way and some of the most important people to me. So if you are looking for a family, if you are looking for community, I strongly suggest you check out the ACC Community blogs and begin to interact with us over there. You can find me there as well.
Next, we're going to head over to The Big Room. I actually found this accidentally when I was taking courses from ACC Learning Center. When you're looking at the modules and tutorials through this ACC Learning Center hub, you actually have the ability to earn points within The Big Room. And you can turn these points into actual Autodesk items that you can have, so like keychains or speakers or something like that. It's a great opportunity to earn and learn.
But while you're over there, they have great meetups. They have great discussion topics. And they have fun little games and stuff going on all the time. So like Autodesk Community blogs, The Big Room is a great place to meet with like-minded individuals and connect on a different level.
Lastly, AUGI. I have been a part of AUGI since 2004. But, mainly, I was using the forums and other things, looking for information and getting help. Over the last few years, though, I was approached to start writing articles for AUGIWORLD magazine. And then I was asked to join their board of directors.
I have been part of it for so long that this community means a lot to me. And the people and individuals that I have met over there have supported me in my growth and my ability to even be here today. So for all of these groups, thank you very much for contributing to who I am today and to where we are.
Next, we're going to look at some additional forums. I have left some more breadcrumbs here for you here to help you gain access to these forums and to these ideas. First is ACC Discussion forum. This is a place where you can go and ask questions or find out issues that other people are experiencing. Maybe you know how to solve their problems.
It also sometimes has new features and functions that may be being released within ACC. So head over there and go and find additional information that you're looking for, as well as the forum that I've created for this class will be held within the ACC Discussion forum hub. So please head over there to go and stay connected with us and to share your knowledge.
Next is ACC Ideas. Every software, every program that we use could always use enhancements and changes or updates. You're always finding something. So head over to the ACC Ideas. And you can actually have an opportunity to share your ideas with the community.
Not every idea gets through, but you have the ability to upvote and to help contribute to the potential advancements of ACC in the future. But hey, you never know, maybe your idea will get through too. But if you're looking for a collaborative environment to discuss those ideas before you get there, again, please head over to this instructions forum on the ACC Discussion forum to share and connect with like-minded professionals.
As I mentioned, I have created a discussion forum specific for this class that you can find on the ACC Discussion forum. You can get answers and ask questions to your classmates and to myself. I will head over there as well. You can share knowledge and experience or maybe some tips or tricks to help people in their own workflow. And you can connect with like-minded individuals to work through challenges and build your community.
All right, if you have any questions, again, please head over to the forum. Please ask them there. We would be happy to communicate and interact with you and being able to support you in your journey through ACC.
If you would like to stay connected with me or find out a little bit more about me, I have provided two last breadcrumbs for you. One is related to my LinkedIn profile, which will give you access directly to me on LinkedIn. And the other is to my Autodesk Community profile, where you can find blogs and articles that I have written and shared with the Autodesk community. Together, we can learn and grow.
Thank you, everyone, for joining me as I discuss my BIM process workflow through ACC. I hope that you have found some useful tips and tricks that will help you optimize your projects and give you the ability to streamline your workflow within your projects today. Thank you, and have a great day.