Description
Key Learnings
- Explore advanced integration concepts such as automating data transfer processes between Vault, Autodesk Construction Cloud, and Factory Design Utilities.
- Discover workflows for organizing factory design data effectively in Vault and Autodesk Construction Cloud to ensure easy retrieval and maintain data consistency.
- Discover how integration enhances collaboration, data management, and workflow efficiency in factory design projects.
Speakers_few
- RGRGS GorleRaghavendra Gowri Shankar (RGS) Gorle is a highly skilled consultant with 14 years of experience in IT and engineering services, specializing in mechanical engineering and product lifecycle management (PLM). He brings over five years of expertise in designing and modeling heavy engineering components, such as hydraulic tube fittings and casted valves, with proficiency in CAD tools and simulation applications. RGS Gorle's PLM consulting experience spans more than nine years, focusing on Autodesk Vault PDM/PLM deployments. He excels in end-to-end implementation processes, including server creation, system integration, application deployment and customization to align with organizational needs. RGS has managed comprehensive Autodesk Vault deployments, overseeing server setup and integration with existing systems and ensuring smooth transitions during upgrades. His expertise extends to delivering practical training, covering all aspects of Autodesk Vault, from basic operations to advanced functionalities. His adeptness at managing PLM systems and leading design projects has significantly enhanced operational efficiency and user adoption, making him a valuable asset in engineering and PLM domains.
- MAManikandeswar AmaranathanManikandeswar, a University of Leeds alumnus with a postgraduate degree in Automotive Engineering, boasts more than a decade of professional expertise in the CAD/CAE/PDM/PLM industry. His versatile roles have ranged from QA Jr. Engineer to Corporate Trainer, Technical Writer, Business Support Specialist, Application Engineer, Technical Consultant, and Design Manager, giving him substantial exposure to tools like Creo, Catia v5, Ansys workbench, and AutoCAD. His tenure as a Technical Consultant has seen him contribute to numerous PLM/CAD/CAE/FDU projects, devising custom assets, and optimizing processes in the D&M industry. His hands-on experience in the plant industry has led him to skillfully combine laser scanning methods and Recap to streamline plant design and manufacturing processes. In his role as a Design Manager, Manikandeswar has overseen the entire lifecycle of an oxygen production manufacturing plant, from concept to execution, including packaging, loading, and assembly. Recently, as an Implementation Consultant, he has been instrumental in implementing Vault, collaborating with ACC sync, and directing Inventor FDU activities. He has successfully created frameworks for data flow, facilitated external collaborations, and provided valuable guidance on Inventor best practices. Manikandeswar's success lies in his ability to listen and align his expertise with client needs. His open-minded approach to each project ensures a deep understanding of unique client requirements, making him a highly effective consultant.
- SPSupriya PrakashWith 13+ years of experience, Supriya Prakash has made a name in the manufacturing domain. Expert in Revit API, AutoCAD API, Inventor API, ACC, BIM360, Vault, Civil3D, Plant3D, APS, and .Net Full stack development, her technical proficiency has been instrumental in various projects across global customers. Going beyond technical skills, Supriya is a team player, believing in the power of collective efforts for optimal results. Her fine-tuned interpersonal skills make collaboration with diverse teammates and customers a breeze. As a mentor, she has guided many professionals. Her ability to simplify complex concepts aids others in broadening their knowledge. What sets Supriya apart is her curiosity and quick learning. Always updated with latest trends, her adaptability not only aids her personal growth but also contributes to innovation. In a nutshell, Supriya Prakash is a skilled professional, a team player, a mentor, and an ever-learner, always ready to tackle new challenges.
RAGHAVENDRA GOWRI SHANKAR GORLE: Hello, all. Welcome to today's session. The title is "Beyond the blueprint-- Linking Factory Design and the outside world through Hybrid Data Management." Statements regarding planned or future development efforts for our products and services are not intended to be a promise for the future availability of the products. Purchasing decisions should not be made based on these statements.
Hi, I'm Rághavendra Gowri Shankar Gorle, a consultant and implementation specialist with a strong focus on Autodesk Vault and Inventor. I have successfully worked on projects like developing plugins to automate customer assembly modules and provide value-added services to my clients, especially during regular maintenance. I also deliver customer training on Autodesk products such as Inventor, Vault, covering basic to advanced topics. We have Mani and Supriya with us in today's session. Mani?
MANIKANDESWAR AMARANATHAN: Hi, this is Manikandeswar. I'm a senior implementation consultant based in Bangalore, India, with a background in automotive and mechanical engineering. I bring over 11-plus years of experience in the engineering industry. I specialize in helping manufacturing and plant engineering customers implement and integrate tools, process, and workflow to achieve their business goal. My expertise includes Vault, Fusion 360 Manage, ACC Docs when it comes to PDM and PLM, and AutoCAD Inventor, Inventor of Factory Design Utilities, Fusion 360 when it comes to product and factory design. And thank you.
SUPRIYA PRAKASH: Hi, I'm Supriya Prakash. I'm a principal technical consultant. I'm an electronics and communication engineer by education. I have close to 13-plus years of experience in developing customized solutions for AEC and D&M industries, building business plans in collaboration with various disciplines, and ensure effective solution delivery. I can easily relate with modelers, designers, and prioritize solutions which are scalable and easily adhere to customer requirements.
RAGHAVENDRA GOWRI SHANKAR GORLE: Thanks, Mani and Supriya. Let's dive into today's subject. Most manufacturers have disconnected workflows between teams and stages of the product life cycles, especially between product design, manufacturing, operations, and the reviewers. A disconnected workflow impacts the overall product life cycle by limiting the ability to analyze a new product design and consider manufacturability, supply chain, material selection, production cost, quality, and other factors.
As Henry Ford once said, "Coming together is a beginning, staying together is progress, and working together is a success." And working together in today's world of data, we call it hybrid data management. Today we'll focus on the key outcomes of hybrid data management-- improved collaboration, optimized efficiency, and increased flexibility.
Hybrid data management breaks down silos, ensuring that teams, whether on-site or remote, work together seamlessly. We reduce delays and enhance project visibility by syncing data between systems like Vault and ACC. By syncing data between systems, we eliminate redundant processes. Users can work with the latest information, reducing errors and improving turnaround time on design revisions and approvals.
Finally, hybrid data management provides the adaptability needed in today's fast-changing environments, whether you are managing data on premise or in the cloud. The system works to you, scale and pivot as needed, offering resilience in the face of new challenges. Now let's have a look at raw facts.
Real-world data from a study conducted by McKinsey. By eliminating redundant process and enhancing collaboration, there was a 20% to 25% improvement in labor productivity. With hybrid data management, teams could achieve a 30% increase in throughput. This translates to more products being completed and delivered in less time, optimizing the flow from design to production. Finally, business saw a 50% decrease in machine downtime by streamlining data and improving communication across systems.
So what will you learn from this session? You'll learn how to integrate workflows between Autodesk Vault and ACC seamlessly. We'll walk you through connecting these platforms to enable smooth data flow, and you'll see the quantitative and qualitative benefits at the end. Now let's understand what's beyond the blueprint. Now my partner Mani will speak about the workflow.
MANIKANDESWAR AMARANATHAN: Hi. Let's consider a typical workflow of collaborating with different stakeholders in design change. Next slide, please. The concept and designs. So the workflow begins with the concept and design phase, where ideas are brought to life through initial designs. This phase is crucial for setting the foundation of the project, ensuring innovative and creative solutions are explored.
Once we finish with that internal review-- very important one-- the draft layout is then shared internally to collaborate with colleagues and gather insights of improvement. This collaborative effort leverages the expertise of the team to refine the design and identify any potential issues early in the process. And then, after an internal feedback, the design is reviewed by external teams to access potential contribution and gather additional feedback.
Engaging external stakeholders provide broad perspectives, ensuring that all aspects of the designs meet the necessary standards and requirements. And finally, we collect all the feedbacks and analyze to streamline the design process. This comprehensive analysis helps in understanding the strengths and weaknesses of the current design, paving the way for informed design-making.
Based on all the feedback we collect, design iterations are made to refine and finalize the factory layout. This iterative process is essential for continuous improvement and ensuring the final design is both effective and efficient. This flow is achieved when we connect Vault and ACC together. So next, move on and see how that works technically.
So let's consider a scenario where it is an engineer wants to share a WAP file for collaborations. There's a design phase, where a design engineer creates or modifies a WAP file in Autodesk Vault, and Vault is used to manage the version control, track change, and ensure data security. The engineer decides to share this WAP file with a site engineer for further collaboration and review.
And to do that, the design engineer uses Autodesk Desktop Connector to bridge the gap between the local environment-- when I say local, it's about Vault-- and then the cloud, where the ACC is accessed. So the Desktop Connector allows the design engineer to easily upload the WAP file from the Vault to the ACC. This is done by configuring the Project Sync in Vault, which upload the data to the Desktop Connector folder linked to ACC.
And when I talk about ACC, the WAP file is now available in Autodesk Docs, the document management module within ACC. This ensures that the site engineer and the other team members have access to the latest design data. The site engineer can view markup and make necessary changes to the WAP file directly within the ACC environment.
This syncs, right? Like any modification made by the site engineer in ACC are saved and updated within the ACC Docs, and Desktop Connector continuously sync files between the local environment and the cloud. Therefore, the changes made in ACC are automatically mirrored in the Desktop Connector folder, and the design engineer, based on the Project Sync configuration, he can utilize the file from Vault. This ensures that the latest modifications are recorded, versioned, and securely stored in Vault. Now let's just walk through the integrations we have done to streamline the collaboration.
RAGHAVENDRA GOWRI SHANKAR GORLE: Thank you, Mani. Now that we have an idea on the workflow, let's explore the integration. Before we explore the integrations, let's have a look at what we are talking about. While integrating Autodesk Vault and ACC offers great value, it also comes with some challenges that we need to address head on. We choose the three most important of them.
The first challenge is syncing the data in real time or on the fly. Keeping everything updated without delay can be tricky when multiple teams work across different systems. The complexity lies in ensuring that changes made in one system are immediately reflected in the other without interrupting workflows.
The second challenge is managing conflicts that arise from parallel edits. Imagine two users editing the same file at the same time, one in Vault, the other one in ACC. This creates conflicts that need to be resolved in a way that ensures data integrity and minimizes errors and rework.
The third challenge is getting markups from ACC into Vault seamlessly. Markups are essential for reviewing and providing feedback, but transferring these annotations between two platforms without losing context or details can be challenging. We need a reliable process to capture and sync those markups effectively.
Now that we have identified the challenges, let's talk about the resolution we have implemented. Schedule Sync hold engineers to wait till the time to sync. To tackle this challenge, we rely on Desktop Connector and Project Sync's Schedule option. The Desktop Connector ensures that files from ACC are easily accessible and synchronized with local drives, streamlining data flow between platforms.
To mitigate the scheduled or on-time sync, Vault now has the on-demand sync, namely Upload to Cloud Drive and Download from Cloud Drive option, as out-of-the-box features, which allows the teams to trigger file syncs as needed, offering greater control and ensuring the latest data is always available without waiting for scheduled syncs. Our next challenge is to avoid parallel edits in ACC and Vault. Our technical consultant, Supri Prakash, will explain this better. Supriya?
SUPRIYA PRAKASH: Thanks, RGS. So let's look at this challenge where we are trying to avoid parallel edits in ACC and Vault. A notable challenge arises when designs are still in progress, meaning which is work in progress, and collaborators from different environments want to access and modify the files simultaneously. This specifically involves concurrence access issues, where we have external collaborators and internal collaborators working in the Vault and ACC environment, and version control and synchronization, conflicting resolutions, and communication and coordination. Now let's see how we have addressed this challenge.
So we have come up with a plugin that helps users from restricting from checking out the files in Vault. As you can see in this Vault environment, when the user tries to check out a file, we are adding a restriction, which is restricting the user from checking out the file as the same file is accessed in ACC because the ACC side, the file has been unlocked by another user. This way, we are avoiding the changes that conflict.
How did we achieve this? Let's look at the workflow. So we have our files residing both on Vault and ACC Docs. As we already mentioned, the main issue here is the users working on the file simultaneously. We have achieved this by using the capability which is already within ACC that is Lock and Unlock feature. Within Vault, this was not accessible. But what we have done right now is we have implemented Desktop Connector as a medium through which we can get the status of the file, whether it is locked or unlocked.
How did we implement this technically? Let's look at that. So we have used the DLLs available in Desktop Connector and Vault. So we have used a particular method that's exposed, which is called the GetLockStatus. This returns the status of the file, whether it has been unlocked or not locked or locked by me or another user. Based on these three statuses, what we do on the Vault, we try to add a check in and check out restrictions whenever a user is trying to perform this actions. This way, we are avoiding users making simultaneously changes and avoiding conflicts.
Let's look at our third challenge, which is sync or viewing ACC markup in Vault. Syncing markups will be ensuring that all the stakeholders are getting the latest comments, changes, and notes, boosting communication and teamwork-- real-time updates, unified data. source, and version control. So what we have developed here is we have given a new button in the context of Vault. So this particular plugin is right now developed for a PDF document.
So let's say a user on the ACC front goes to a particular PDF file and adds a markup-- creating certain callouts, making certain decision changes, removing certain assemblies, and making additions. So how does a Vault user end up getting to know that these information exist on the same file? This is achieved with our plugin which says Display ACC Markups. So whenever user is trying to click on this, so we display a PDF which is getting downloaded from ACC through which the user can access to the markups on ACC within Vault system.
Now let's explore how this is technically integrated in Vault. So for this, we have used the ACC data management APIs, which exports PDF files from ACC by including markups using five simple steps. What are these steps? First, we find the folder ID of the file that needs to be exported.
Next, we select the latest version of the file that needs to be downloaded with the markups. And then we finally check if the job is complete, and then we get the PDF exported, which is then displayed into the Vault simultaneously. This is how we are trying to address all these challenges that we have discussed.
So what is our proposed solution? Our solution gives the bridge to gap between the manufacturing and construction personas by allowing them to view the files across the systems. Over to RGS.
RAGHAVENDRA GOWRI SHANKAR GORLE: Thank you, Supriya, for a detailed explanation. Now I request Mani to give an application demo on the same.
MANIKANDESWAR AMARANATHAN: Let us get started on how to set up the Vault Project Sync before we get into what are the challenges we addressed. So we click on the Tools, go to Administrations, Vault Settings. And Collaborate. Configure. This is under Project Sync Management. You can click on it.
In order to map the new folder here, we just make sure, click on New and create a mapping, and you can define the name. I can say that it can be the factory collaboration, anything. And then click on the root folder from Vault. So I'm selecting the Vault folder here, and click on this three dots. And selecting the root folder and able to see that. And click OK. And you can also select another root folder from the cloud drive. So I'm just selecting here.
You can able to choose Autodesk Docs and the respective ACC environment, and I'm selecting that. Select the project files from here. So once you click on this, and you can able to choose the options here, like you want to enable the cloud drive mapping, enable manual sync. If it is needed, you can check or uncheck. Upload related file based on release by us. So when we say release by us, if it is released on a particular version, only then we can able to upload it. And you can include the design documentations files if you want. So we can control the options here.
And then what are the folders we want to sync between this Vault domain and the ACC domain? So you can click on this folder and then the Define Folder Sync dialog box appears. You can select here. And you can choose the respective folders. So if you want the factory layout design, I can choose factory layout design. And similarly, I want to make sure whether what options we need to prefer during this folder sync.
When I say Upload to cloud drive, that means it is one way between Vault to ACC. When I say Download from cloud drive, it is one way between ACC to Vault. When we say Bidirectional sync, it is about Vault to ACC and ACC to Vault. So it will always be in sync. And we have other options, like Apply selected action to subfolders. You can make sure the same applies to all the subfolders. You can select this.
And you can even sync data in files. For example, we have the [INAUDIBLE] files, which would be [INAUDIBLE] in Vault. If you want to sync that also, you can check or uncheck based on the needs, OK? I'm just clicking OK. That ensures that we have added here. But later, it's about scheduling.
So here we have an option of whenever we want to make our ACC and Vault sync. So when I say Daily, that means if my work starts at 9:00 AM, I can set up my timing as 8:00 AM, so that makes sure every 8:00 AM, this will trigger, and the job process syncs the data from Vault to ACC. The second option is every eight hours. So the minimum is eight hours, and you can extend it. So if I want, I can say 12 hours, but the minimum is eight hours, yes. So every eight hours or 12 hours, it syncs my Vault and ACC.
And if you don't want to do the scheduled sync, you can choose None. That means it is always be a manual sync. OK? And there is one more option here called Filter. So for example, I don't want to add my entire file to be synced. Instead, I want to make sure only a certain extension-- for example, only the DWG file-- I want to get it synced. Then I can able to add this particular filter, and that makes sure upload files that matches this criteria. So that means if it is only DWG file, only then that upload happens. OK?
So you can define all those things, and then you can click OK about it. Similarly, you can go and add multiple folders. No restriction on that. You can keep adding based on the requirement. OK? This is how we set up our cloud drive. Now, this ensures us that both Vault and ACC are in sync, and if there is any engineer wants to share the data immediately, this is not possible with the scheduled sync. And that is where we have on-demand sync.
So when I say on-demand sync, if I want to sync my data immediately, then we can choose this. So I can go here and able to choose any of my design files from Vault, and it can be multiple selection also. There is no issue. So you can select multiple or a single file. And just make sure you go here and then click on this Upload to cloud drive. So this ensures that this data are being shared to ACC environment on demand, so you don't need to wait until the sync happens. You can always prefer this, and then this data will get uploaded to the respective folders.
At the same time, if I want to pull the data, the latest data from ACC side, what I need to do is I again need to go to this Download from cloud drive. You can able to see that in the top right. Just need to select on the Download from cloud drive. When I click on that, I will get the folder options, where I can click Next. So that makes sure I can able to choose which file I want to select. So I can choose here. I can choose what are the files I wanted to select, and then hit Download.
So when I say hit Download, that means it is syncing the data from ACC to Vault. So this makes sure, right? So we have a constant download and upload between ACC and Vault without waiting for the schedule. And whenever we click these things, you can able to see that that scheduled the jobs. So you can able to see there is a manual download which is happening and the scheduled sync which is happening. This is from the earlier option, and this is for the manual download options. So we can able to see that job server is on the queue about it, and that will execute the process. OK?
Now, as a collaborative service, both design engineers and site engineers can work on the synced files. We can notice that FDU file is also available in the ACC environment. So when I say ACC environment, I can go and then able to open that. And you can able to see all those files which you see it in Vault. Both are available in ACC also. OK? So this is where we can able to see both ACC and Vault together, the sync.
So now when design engineer needs to work on file, can directly check out from here, from Vault. And similarly, an ACC engineer, I can able to directly select here and then start working on that from the ACC. As there is no restriction or control over the check out or check in data from Vault to ACC, or lock or unlock status, you can able to still see that the people can easily work parallelly.
And when they start work parallelly, and that brings the version conflicts. So whenever the sync happens, it will only update the latest version of either Vault or from ACC. So to avoid these conflicts, we have utilized the APIs which Supriya explained before, how it has been configured, and the PDM APIs here to create a restriction in Vault during check out and check in.
So what that mean is, when I go to ACC, and if you see that in the ACC, the files are locked and locked and all those things are there, what happens here is if the files are unlocked, right? So you can able to see I'm going to take an example of this FDU data set 01 factory DWG. And you can able to see even in the Vault, it is not checked out. It is in checked in state. Now, both are available. I can able to open it and edit it. Right?
But here, if the file is not locked in ACC, what we have done is the people who wants to open it in Vault, if [? data ?] is to do that-- so I can show you that. Right, click here. And then I'm going to check out. So when I do the check out, it makes sure it provides the restrictions. So you can able to see that. So the restriction is about the Vault user cloud upload. The file cannot be checked out, as it is being used by another user from ACC. That ensures unless otherwise the file is locked, it will not get checked out.
So now what I need to do is I need to go here, back to ACC, and make sure this file says lock. So now we can able to see that is lock, and I can even open the local Desktop Connector to make sure that it's getting synced. So here you can able to see there is no symbol yet, but once the sync is made, you can able to see a lock symbol here. Yes. Can you see this? So based on once this lock [? sign ?] appears, now I can come here to the Vault and select on the file, right-click, and check out.
Now you can able to see the check out is successful, and that ensures nobody in ACC can open it and then work on it. OK? At the same time, now involved people can start work on it. You can ask, OK, if I've checked out here and in ACC, if somebody goes-- and there is some limitations here in ACC, right? So I can go here and then I can do some lock here. So the person goes here and then unlock this. So that happens here.
So when he unlocks those file, and now the Vault user doesn't know about it. But if you want to try to check out or check in back those files, so what happens here is you can again see the Desktop Connectors. Make sure that the locks goes off. And then I'm coming back here. I'm trying to check in this file again. So this makes sure unknowingly, nobody can able to have the parallel edits done. So now it will show another restrictions, saying that the file cannot be checked in, as it is being used by another user from ACC. Because it has been unlocked.
So this is the announcement what we added to make sure that people who works parallely doesn't conflict with their versions. So after check out, if any user unlocked the file in ACC during the check in of Vault file, it will restrict the user. Is how we make sure that it's been achieved.
Let's consider a scenario in a review stage. When site engineer works on ACC and do markups for providing inputs to the design engineer, now the design engineer needs to get that particular input and start working on it. But in actual scenario, that is not quite possible. So what happens here is I've clicked on this particular PDF, and you can able to see that being a site engineer, we can do all the markups here. You can able to see that markups.
And now, in order to get this markups in Vault, what Supriya does, she has created a plugin, and now I can able to go and right-click on those particular file and select Display ACC markups. So I can able to see that. So when I click on this, that brings the new page where I can able to see the ACC markups over here. So now you can able to see the same ACC markups which gets reflected here.
And this ensures that the design engineer being working from Vault can get the latest markups done by a person who's working on ACC environment. That makes sure that there is no delay in the latest data. At the same time, any design changes related to this particular communications can made it very fast. This ensures, OK?
And this has been shown in the PDF viewer directly. You will have noticed that. And then this makes sure the design engineers gets the latest feedback from the site engineer and modify the design engineer's update, the design changes, with respect to those inputs. Thank you. And this is all about the applications demo, which we want to show, which address all the challenges which we discussed in the previous slides. Thank you.
RAGHAVENDRA GOWRI SHANKAR GORLE: Thank you, Mani, for a very clear demo on the solutions. Now let's see what the benefits of the feature improvements are. The qualitative improvements brought by this integration. With the syncing mechanism in place, there's no risk of teams working on or sharing outdated or incorrect files. This ensures that all stakeholders always access the most up-to-date versions, reducing errors and the need of rework.
The integration fosters a truly connected environment. Teams, whether working remotely or in house, can collaborate effortlessly across Vault and ACC. This seamless connection breaks down silos and encourages real-time communication, keeping everyone on the same page. Finally, the integration boosts flexibility. Users don't need to switch between Vault and ACC to view markups or updated files. Everything can be accessed directly from Vault, which saves time and allows for a more streamlined workflow. Whether it's markups or updates, it's all available within the same environment.
By implementing real-time syncing and on-demand features, we have seen a significant reduction in data and sync times, around 30% to 35%. This means faster access to updated files and less downtime waiting for data to sync across systems. With integrated workflows and real-time collaboration, issue resolution has become quicker, by about 15% to 20%. Teams can spot and address problems faster, since everyone is working with the latest data and receiving feedback promptly through synced markups.
Perhaps the most impactful result has been 20% to 25% reduction in rework costs. By ensuring that teams always have access to the correct, most up-to-date files, we have dramatically minimized the errors and miscommunications that lead to costly rework. And now we have got something extra for you-- some bonus insights that will help you use Vault to the most.
The CAD dashboard is a POC that provides a centralized view of CAD data directly within the Vault. This tool helps you monitor project status, track revisions, and gain insights into your design processes from one convenient location, which will give you the most active time of Vault users, the most revised assemblies, time graphs, revision graphs, and many more.
Coming to the Drawing Inspector. Our next bonus is an Autodesk App Store app, Drawing Inspector. This app fits into the Vault as an add-in, gives us a tab in the display window, and compares existing drawings of all parts in the selected assembly. And those that don't, this allows us to see which part or parts will need the drawings.
We acronym Job Processor Log Consolidation Utility as JPLCU. This is an independent utility that converts raw job log data into a structured CSV file, which gives us insight into the total number of jobs, average times, total unique jobs, jobs ran in each server, whatnot. Everything about the jobs involve job processor. Not only that, we can then use CSV files to link to Power BI and take advantage of Power BI's visualization capabilities to build a powerful, one-stop dashboard for log analysis.
As we wrap up our session, let's summarize the key takeaways. We learned the advantages of hybrid data management, including the on-demand sync in Vault and the ability to sync when needed as an out-of-the-box feature. We are now aware that Vault and ACC have the capability to lock and unlock files to avoid parallel edits. And we were successful in getting and opening the markups created in ACC.
And last but not least, please don't forget the additional resources we discussed, like the CAD dashboard, Drawing Inspector app, or the JPLCU, which can further enhance your productivity and project management capabilities. Thanks for attending our session. Have a great day.
Downloads
Tags
Product | |
Industries | |
Topics |