AU Class
AU Class
class - AU

Document Workflows in Autodesk Construction Cloud

共享此课程
在视频、演示文稿幻灯片和讲义中搜索关键字:

说明

With Autodesk's acquisition of PlanGrid and release of Autodesk Construction Cloud there are several tools that assist in the flow of project information. This class will show various workflows not only with the supported software tools like Revit, Civil 3D, and AutoCAD Plant 3D, but also with approval workflows, RFIs, submittals, ways sheets flow through a project, and ways you can use Autodesk Construction Cloud Connect to transfer data across different cloud platforms. This class will inspire you to expand your use of Autodesk Construction Cloud.

主要学习内容

  • Learn the document control features and approval workflows available in Autodesk Docs.
  • Learn how to manage sheets, RFIs, and submittals inside Autodesk Build.
  • See workflows between Revit, Civil 3D, and AutoCAD Plant 3D in the cloud.
  • Learn how to use Autodesk Construction Cloud Connect to transfer data across cloud platforms.

讲师

  • Philip Russo 的头像
    Philip Russo
    I have been in this industry since 1986 working primarily with Autodesk software solutions. I currently work as the Head of Digital Design and BIM for the Americas with Ramboll. My primary focus is to guide our technology and workflow efforts across all disciplines and business units.
  • David J Cusano 的头像
    David J Cusano
    As a Technology & Digital Design Lead for the Energy market at Ramboll, David plays a crucial role in driving and managing the integration of technology and digital design within the market and across various geographical Country Market Units. He has the responsibility of collaborating with the Innovation & Digital Transformation Director to build and develop efficient governance and organizational structures, empowering the organization to excel in the technological and digital realms. This involves the management of technology tools and E&A tools portfolios, ensuring that business-critical tools and applications are expertly organized and supported. David's role requires active participation in cross-market collaboration, contributing to a shared vision and execution within Technology & Digital Design. David's position demands a strategic oversight for the standardization and streamlining of work processes, best practices, and methodologies, ensuring they are developed, agreed upon, and maintained across the market. Technology & Digital Design Leads are mandated with fostering a professional digital design network to facilitate common standards and the adoption of digital design practices. They are pivotal in driving the implementation of standardized processes, supporting projects in digital design to success, and aligning digital design processes with the global market. This includes the implementation and training of digital design across the market, thereby reinforcing Ramboll's commitment to innovation and digital transformation. The role requires an acute understanding of the market-specific challenges, and opportunities presented by Technology & Digital Design, along with a deep knowledge of the industry trends and vendor roadmaps.
Video Player is loading.
Current Time 0:00
Duration 26:04
Loaded: 0.64%
Stream Type LIVE
Remaining Time 26:04
 
1x
  • Chapters
  • descriptions off, selected
  • en (Main), selected
Transcript

PHILIP RUSSO: Welcome, everyone. This class is all about document workflows in the Autodesk Construction Cloud. We have a lot of information to cover, and I'm sure some of it you already know, but hopefully, we uncover some useful tidbits you can benefit from. My name is Philip Russo, and I am the head of Digital Design and BIM for Ramboll in the Americas. And co-presenting with me today will be David Cusano, who is the head of Visualization for Ramboll in the Americas.

Let's jump quickly into the agenda and some basics so we can dive into the presentation-- give you some stats on Ramboll, review the learning objectives, go through some workflows with some technical software, then some internal workflows in Autodesk Docs and Autodesk Build.

So Ramboll is a global company with over 300 offices and 15,000 plus employees. We're broken down into global business units covering buildings, energy, transportation, and then environmental and health with its headquarters located in Denmark. We've been leveraging the Autodesk Construction Cloud for quite some time.

This slide shows that we have more than 7,000 active members and over 1,300 active projects at any given time. Most of these projects are primarily based on Revit Collaboration, but recently, we're using ACC for Civil 3D and Plant 3D alongside Revit and venturing into most of the other available modules in the cloud platform. One point I would like to make just before we dive into the presentation is that the handout that accompanies this presentation will have a lot of step-by-step instruction, extra tidbits, and several links to different resources.

So to go over some of the learning objectives we're going to accomplish during this presentation, number one, learn the document control features and approval workflows in Autodesk Docs, number two, learn how to manage Sheets, RFIs, and Submittals in Autodesk Build, and number three, see workflows in Revit, Civil 3D, and Plant 3D in ACC, and last, using ACC Connect to transfer data across cloud platforms.

So with any cloud platform, there are permissions and a hierarchy required to manage folders, files, and functionality. Let's take a look at some of these roles and permissions. And as we unpack the rest of this presentation, we'll be revisiting this topic. So the account administrator manages the company's account.

From the list, you can see the responsibilities. And I like to put this list and break it into two buckets. The first is project permissions, and the second is standards and automation. Project permissions are items like creating the project, adding members to the account, adding companies, business units, and defining roles. Folder permissions on a project can be assigned by an individual, by a company, or the role they play in the project. So having a clear understanding on this and having it set up correctly saves the project administrator a lot of time and gives them the control they need.

Then items like form templates, project templates, and activating apps aids in the automation and standards apply to the projects. This is just a quick snapshot of assigning permissions to your project folders. As mentioned, you can see you can assign an individual, a role, or a company to a folder. Then different permissions can be assigned from viewing all the way to managing the folder.

Now that we have some basic permission information out of the way, let's take a look at some workflows with the different technical applications starting with Revit. For basic Revit model collaboration, we will look at two different workflows. The first is direct model linking, and the second is using Design Collaboration, teams, and publishing. The requirement differences between these two workflows is based in design collaboration. You have to have Design Collaboration activated if you are going to be publishing and sharing your model versus the direct linking.

I am sure most everyone here has worked in Revit on a central model either in BIM 360, ACC, or on a local server. If you have not been in ACC, the only difference is that you are publishing your central model to the cloud. And in the cloud, you specify the hub, the project, and the folder you will push your Revit central model to. This all points back to your permissions. You must belong to the project and have the correct permissions on the folder you are publishing to.

Another item that will trip people up is being consistent with the Revit version you are using. Once that first Revit model gets published to the cloud, that project takes on that Revit version. For example, if somebody already published a model to this project and it was in Revit 2023 version, you will not be able to see that project if you are in Revit 2022 trying to push a model into that project.

With direct model linking, it works like we are all on a local server where the Revit designer synchronizes with central, and the latest changes get pushed to the central model in the cloud. If this is where other trades will link in your model for reference, they browse to that location through Autodesk Docs, which is made available when you have the Autodesk Desktop Connector installed.

The ACC platform gives us different functionality to consider when sharing our Revit model to other project stakeholders. The Revit model can be viewed from ACC without Revit. The version that is viewable is the latest published version. So if you log in to the Autodesk Construction Cloud through a web browser, the model that you see is the latest published version, which might be different than a model you see when you open it up inside of Revit.

This gives you control when you want to update the cloud version of your model. People that have permissions to the folder you publish to will be able to view your model. In Revit, you set up what views will be published. Then under the Collaborate ribbon, you select Manage Cloud Models. And once you browse to your model, you have the ability to publish based on your publish settings.

To go beyond direct file linking and add a level of control with model sharing, we can set up teams and be able to publish our Revit models for consumption by other discipline teams. Specifying your shared folder location and selecting the folder that contains your Revit model is all that is required for setting up your team for the first time.

The handout will go through step-by-step procedures on creating a package, but once a package is published and the model is placed in the shared folder, it gives other disciplines that are collaborating on the project a new option of linking from a shared folder if the project folder permissions allows this. This gives the team control on when they feel their model is ready to be shared. I personally prefer this method over doing the direct file linking.

Then ACC's preferred workflow takes it even one step further, and that's for a team to consume a package which will bring the Revit model into their own project space only available to their internal project team. In ACC, under the Design Collaboration Module, the designer can select the package they wish to consume. Once consumed, their model will be copied into their Consumed folder for file linking.

Up until now, they may have had experience with all the methods discussed. A new feature in the Construction Cloud is being able to bridge files across projects to share. This could be a result of multiple projects under different project numbers and they're running in parallel, or maybe you're working on your own personal hub, and other clients that you're collaborating with want your model copied into their hub for their own file linking, but you aren't collaborating together. So the bridge function in the Autodesk Construction Cloud will allow this to work.

Currently, the catch for Revit models is that the bridge function only works with shared cloud models and not the main work in progress central file. There are rumors that this is on the roadmap for Autodesk, but as of today, it only works with the shared cloud models. So now I'd like to pass the presentation over to Dave Cusano to discuss ACC workflows with Plant 3D.

DAVID CUSANO: Thank you, Phil. In the spring of 2022, Ramboll in the Americas made a decision to move all of our process mechanical users not only to the ACC platform, but also, to the AutoCAD Plant 3D platform. This followed several months of testing and planning with the help of other geographies within the company and users based in the Americas with previous experience with Plant 3D. Next slide.

The first step in the process is to create your AutoCAD Plant 3D project. This can be done either working without-- next slide-- or with a project template. At this time, roughly 95% of the AutoCAD Plant 3D projects we create are done without a template. However, we do have a core group of users in the process of developing an Americas template for use on both Plant and P&ID projects. Next slide.

Once your project has been created, the next step is to use the Collaborate ribbon to share your project with the ACC platform. Next slide. This process is relatively straightforward and should only take a few moments to perform depending on the size of your project and whether a template was used or not. Once you've received the dialog indicating your project is cloud powered, you're ready to begin work. Next slide.

Once the project has successfully been linked with the ACC platform, you'll notice the icon change next to the name of the project in the Project Manager. You'll also now see a status indicator bubble next to each of your drawings in your project, indicating whether they are checked in or out and whether local copies exist on your machine. Next slide.

One additional process that may prove necessary in the life of your project is to move or archive the project off the ACC platform. This can be done at any time by right-clicking on the project name in the Project Manager and choosing the Create Project Backup option. You'll be told the size of the resulting backup and be asked for a location for the backup to be created. Once the necessary selections have been made, you can now simply click the Backup Project Now button. Next slide.

One last workflow we needed to root cause was the best way to collaborate with our Revit team on ACC projects. After much back and forth, it was determined the use of an IFC export provided the most stable representation of the AutoCAD Plant 3D geometry within Revit. The only wrinkle in the process is there is no IFC export capability within AutoCAD Plant 3D. So we are instead using AutoCAD MEP to achieve this result. Last slide.

On my last slide, you can see examples of linking the AutoCAD Plant 3D DWG directly into Revit shown on the left versus using the IFC export and then linking the resulting file within Revit on the right. Clearly, the IFC model provides a much richer representation of our process mechanical models for our Revit user base. As Phil mentioned, there will be more detailed descriptions of all the processes discussed in the class handout, and I'll now turn things back over to Phil.

PHILIP RUSSO: Thanks, Dave. So one of ACC's hidden gems that is underutilized is the document approval workflows. You can predefine the workflow on approving a document within your project. Within ACC Docs, you can set up an approval workflow. These workflows can be multiple steps by individuals or by defined groups. Once the workflow is assigned to a document or a series of documents, the review process will be automated.

Once a review is complete, you can have the document or documents copied to a completed folder. I prefer this option because I can give view permissions to the project team for the approved folder so they only see the completely review documents and do not get confused by documents that are not ready for the project to consume. After the document is submitted for review by the initiator, the first reviewer will be notified by email. And once the reviews are in process, you can go to the Summary page to get a status of all the progress for the reviews running on the project.

Earlier, I mentioned the ability to bridge your Revit model across to other projects. Here, I just wanted to point out visibility of the files that are being bridged. The main bridge menu will show you any incoming documents that have been bridged to your current project, outgoing Sheets or files that are being bridged outside your current project, automations that have been set up, and then a status of all Bridge projects and documents.

By selecting the Share function in Docs, you can activate the function of Bridge by sharing with another project. When you select Sync Updates, you are in effect automating this task by syncing changes with the project you are bridging to. Any time the Bridge folder gets updated at the source, it will be updated in the copy in the Bridge project. Once the folder is shared and bridged across projects, you will receive an email notification. This new connection will now be visible in Bridge projects.

Sheets is a menu in the Autodesk Build module and has the functionality brought in from Autodesk acquisition of Plan Grid. There is a four-step process for adding Sheets to your project. Select the files from your computer or files from your Project folder in step one. Then you assign a version set and issue date for the second step in the process. Step three is to verify the Sheet numbers. And step four is to define the titles and tags before you publish the Sheet to the project team.

This slide shows the different steps adding the Sheets workflow will step you through. The handout will go more into detail and step by step of this functionality. But one important thing that I'd like you to understand is that the Sheet function within Build has different subscription levels representing the total number of Sheets that you can have access to. However, if you just publish a PDF and store that within a doc folder for review, it will not count against your total Sheet count.

When you use the Sheet function and have these sheets accessible in the field with the Plan Grid Build mobile app, then that will go against your total Sheet count. So keep that in mind. We discovered that the hard way on a project where we got notified that we exceeded the total Sheet count. I just wanted to point that fact out to you.

Creating RFIs is another function within Autodesk Build and has automated workflows built in. First, there are some rules and roles to understand. The project administrator can assign the creator and manager roles in settings. You must be a project administrator, a creator, or a manager to create an RFI.

When creating an RFI, you can assign people during the RFI creation process to be a coreviewer. A coreviewer cannot produce a legal answer to an RFI, but they can provide feedback in the comments. And then it's up to the reviewer to review those comments and include them in the final response to the RFI if needed. Other team members can be added to the distribution list as watchers to be made aware of the RFI but not expected to provide any comments or feedback.

These two screenshots are the sections of the RFI form where people are assigned in the RFI. The ball in court is the initial reviewer assigned to the RFI. The coreviewer, as mentioned, will be notified of the RFI and be able to provide comments. And the watchers are the distribution list to be made aware but not expected to provide any information.

During the RFI review process, the reviewer can attach references from the project or from their computer. The reviewer can solicit feedback by using the @ symbol as a prefix to the team member in the activity log to loop them in. This is a good practice to put in place instead of sending off emails so that all communication is contained within the RFI for visibility to the project team.

In the main RFI log, you can export an individual RFI by selecting the three dots at the end of the row containing the RFI, or you can export all RFIs on the project from the Export button highlighted in the image. Once the RFI is answered, the manager can accept the answer, close the RFI, and distribute. Once the RFI is distributed, the entire project team will be able to see the history of the RFI and the result.

Creating product submittals is another function of Build with built-in workflows. The project administrator will assign a submittal manager. The submittal manager has the sole responsibility to submit items for review and close them out as they are approved. Other submittal settings include default review time and a watcher list. Project members that are added to the watcher list can see new items as they are submitted. Under Responses, you can program in your own custom responses to the submittals. The last item under submittal settings is specifying the types of submittals being created.

The submittal function in ACC allows you to enter items individually, import from a spreadsheet template, and create submittal packages. We'll take a closer look at where to access these settings during the live demo. These three images show the breakdown of the Create Submittal form from the spec section through planning response times.

Connecting data across cloud platforms is a function of ACC Connect. This web service is a utility that requires recipes to automate workflows. At Ramboll, we're finalizing some recipes to transfer our deliverable documents from the Autodesk Construction Cloud over to ProjectWise. You define your connections to be validated, create a trigger for an event that will perform a function. And at Ramboll, we will have ACC watch a deliverable folder in the Construction Cloud project. When a document gets updated or gets added, ACC Connect will copy this data and transfer it to the same folder inside of ProjectWise.

Now I'm going to jump over to the Autodesk Construction Cloud to show where some of these main functions are located. First, I'm going to start off as the account administrator. So it's up to the account administrator to create new projects, add members-- it's currently going to sign me out here. Let me just jump back in quick-- assigning members, adding companies, and defining roles, and all of these play a key part in setting up your project.

So if I jump over into a demo project here and I look at the folder structure, when I hover over these three dots and select Permissions, this is where I can add permissions. And I could do it by user. I could do it by a company. Or I can do it by the role that that person plays. So having all that in order gives the project administrator control over working with the project.

Another area I want to jump into when we were discussing Revit, I want to jump into Design Collaboration. And again, Design Collaboration is required if you are going to set up teams and collaborate on a Revit project and be able to consume models. Or if you are using Civil 3D or Plant 3D, you have to have Design Collaboration activated.

So inside Design Collaboration, I want to take a look at a couple of items here. I'm going to go into Settings. And in Settings, this is where you specify where your shared folder is going to be located so that when you publish your models, this is where your models will get published for people to link to. And if you take it one step closer where you actually have physical teams set up, then in the team function, that is where you can go ahead and consume models.

So if I go to the Home page here and I go to this dropdown up here, this will show me the different teams that are set up. And then within the team, I can select a package, and I can go ahead and consume that package. And that will bring it within my team in the Consumed folder.

OK, so now I'm in the Build module, and the first place I want to go to is Sheets. And under Sheets, I just want to be able to show you that when you go ahead and add Sheets, this is where you can drag in a file that is on the project, or you could go from your computer. And then this is the four-step process where the files get added. You do your version set. You verify your Sheet numbers. And then you verify your titles and any tagged information.

Next, I'm going to jump into RFIs. And under RFIs, I'm going to go over to the right here to go to Settings. And under Settings, this is where you set up your permissions where you can add a member, and then you define the roles of the creator or the reviewer or the watcher.

If I go under Submittals, and under Submittals, I go to Settings, again, Permissions, default values, so who's going to be my default manager? What's going to be my default review time? And what is going to be my watcher list? And then under Responses, this is where I can control my different responses and add them, and then also, specify my different type of submittals.

Then the last thing I want to jump to is go over to Bridge. And in the Bridge app, this is where you have your incoming documents that are being bridged to your project, your outgoing documents that are bridged to other projects, your automations, which is when you turn on the syncing option because you can just bridge something one time and give it to a project versus syncing it which will create an automation. And then the Bridge Projects will show you all the projects and documents that are currently being bridged.

OK, so I gave you some highlights of where some of these various settings are located. And as mentioned earlier, the handout that follows along with this presentation goes much more into detail with some step-by-step workflows along with several links to some resources. So thank you for viewing this presentation about document workflows in the Autodesk Construction Cloud.

Downloads

______
icon-svg-close-thick

Cookie 首选项

您的隐私对我们非常重要,为您提供出色的体验是我们的责任。为了帮助自定义信息和构建应用程序,我们会收集有关您如何使用此站点的数据。

我们是否可以收集并使用您的数据?

详细了解我们使用的第三方服务以及我们的隐私声明

绝对必要 – 我们的网站正常运行并为您提供服务所必需的

通过这些 Cookie,我们可以记录您的偏好或登录信息,响应您的请求或完成购物车中物品或服务的订购。

改善您的体验 – 使我们能够为您展示与您相关的内容

通过这些 Cookie,我们可以提供增强的功能和个性化服务。可能由我们或第三方提供商进行设置,我们会利用其服务为您提供定制的信息和体验。如果您不允许使用这些 Cookie,可能会无法使用某些或全部服务。

定制您的广告 – 允许我们为您提供针对性的广告

这些 Cookie 会根据您的活动和兴趣收集有关您的数据,以便向您显示相关广告并跟踪其效果。通过收集这些数据,我们可以更有针对性地向您显示与您的兴趣相关的广告。如果您不允许使用这些 Cookie,您看到的广告将缺乏针对性。

icon-svg-close-thick

第三方服务

详细了解每个类别中我们所用的第三方服务,以及我们如何使用所收集的与您的网络活动相关的数据。

icon-svg-hide-thick

icon-svg-show-thick

绝对必要 – 我们的网站正常运行并为您提供服务所必需的

Qualtrics
我们通过 Qualtrics 借助调查或联机表单获得您的反馈。您可能会被随机选定参与某项调查,或者您可以主动向我们提供反馈。填写调查之前,我们将收集数据以更好地了解您所执行的操作。这有助于我们解决您可能遇到的问题。. Qualtrics 隐私政策
Akamai mPulse
我们通过 Akamai mPulse 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Akamai mPulse 隐私政策
Digital River
我们通过 Digital River 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Digital River 隐私政策
Dynatrace
我们通过 Dynatrace 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Dynatrace 隐私政策
Khoros
我们通过 Khoros 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Khoros 隐私政策
Launch Darkly
我们通过 Launch Darkly 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Launch Darkly 隐私政策
New Relic
我们通过 New Relic 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. New Relic 隐私政策
Salesforce Live Agent
我们通过 Salesforce Live Agent 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Salesforce Live Agent 隐私政策
Wistia
我们通过 Wistia 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Wistia 隐私政策
Tealium
我们通过 Tealium 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Tealium 隐私政策
Upsellit
我们通过 Upsellit 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Upsellit 隐私政策
CJ Affiliates
我们通过 CJ Affiliates 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. CJ Affiliates 隐私政策
Commission Factory
我们通过 Commission Factory 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Commission Factory 隐私政策
Google Analytics (Strictly Necessary)
我们通过 Google Analytics (Strictly Necessary) 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Google Analytics (Strictly Necessary) 隐私政策
Typepad Stats
我们通过 Typepad Stats 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Typepad Stats 隐私政策
Geo Targetly
我们使用 Geo Targetly 将网站访问者引导至最合适的网页并/或根据他们的位置提供量身定制的内容。 Geo Targetly 使用网站访问者的 IP 地址确定访问者设备的大致位置。 这有助于确保访问者以其(最有可能的)本地语言浏览内容。Geo Targetly 隐私政策
SpeedCurve
我们使用 SpeedCurve 来监控和衡量您的网站体验的性能,具体因素为网页加载时间以及后续元素(如图像、脚本和文本)的响应能力。SpeedCurve 隐私政策
Qualified
Qualified is the Autodesk Live Chat agent platform. This platform provides services to allow our customers to communicate in real-time with Autodesk support. We may collect unique ID for specific browser sessions during a chat. Qualified Privacy Policy

icon-svg-hide-thick

icon-svg-show-thick

改善您的体验 – 使我们能够为您展示与您相关的内容

Google Optimize
我们通过 Google Optimize 测试站点上的新功能并自定义您对这些功能的体验。为此,我们将收集与您在站点中的活动相关的数据。此数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Google Optimize 隐私政策
ClickTale
我们通过 ClickTale 更好地了解您可能会在站点的哪些方面遇到困难。我们通过会话记录来帮助了解您与站点的交互方式,包括页面上的各种元素。将隐藏可能会识别个人身份的信息,而不会收集此信息。. ClickTale 隐私政策
OneSignal
我们通过 OneSignal 在 OneSignal 提供支持的站点上投放数字广告。根据 OneSignal 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 OneSignal 收集的与您相关的数据相整合。我们利用发送给 OneSignal 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. OneSignal 隐私政策
Optimizely
我们通过 Optimizely 测试站点上的新功能并自定义您对这些功能的体验。为此,我们将收集与您在站点中的活动相关的数据。此数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Optimizely 隐私政策
Amplitude
我们通过 Amplitude 测试站点上的新功能并自定义您对这些功能的体验。为此,我们将收集与您在站点中的活动相关的数据。此数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Amplitude 隐私政策
Snowplow
我们通过 Snowplow 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Snowplow 隐私政策
UserVoice
我们通过 UserVoice 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. UserVoice 隐私政策
Clearbit
Clearbit 允许实时数据扩充,为客户提供个性化且相关的体验。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。Clearbit 隐私政策
YouTube
YouTube 是一个视频共享平台,允许用户在我们的网站上查看和共享嵌入视频。YouTube 提供关于视频性能的观看指标。 YouTube 隐私政策

icon-svg-hide-thick

icon-svg-show-thick

定制您的广告 – 允许我们为您提供针对性的广告

Adobe Analytics
我们通过 Adobe Analytics 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Adobe Analytics 隐私政策
Google Analytics (Web Analytics)
我们通过 Google Analytics (Web Analytics) 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Google Analytics (Web Analytics) 隐私政策
AdWords
我们通过 AdWords 在 AdWords 提供支持的站点上投放数字广告。根据 AdWords 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 AdWords 收集的与您相关的数据相整合。我们利用发送给 AdWords 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. AdWords 隐私政策
Marketo
我们通过 Marketo 更及时地向您发送相关电子邮件内容。为此,我们收集与以下各项相关的数据:您的网络活动,您对我们所发送电子邮件的响应。收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、电子邮件打开率、单击的链接等。我们可能会将此数据与从其他信息源收集的数据相整合,以根据高级分析处理方法向您提供改进的销售体验或客户服务体验以及更相关的内容。. Marketo 隐私政策
Doubleclick
我们通过 Doubleclick 在 Doubleclick 提供支持的站点上投放数字广告。根据 Doubleclick 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Doubleclick 收集的与您相关的数据相整合。我们利用发送给 Doubleclick 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Doubleclick 隐私政策
HubSpot
我们通过 HubSpot 更及时地向您发送相关电子邮件内容。为此,我们收集与以下各项相关的数据:您的网络活动,您对我们所发送电子邮件的响应。收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、电子邮件打开率、单击的链接等。. HubSpot 隐私政策
Twitter
我们通过 Twitter 在 Twitter 提供支持的站点上投放数字广告。根据 Twitter 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Twitter 收集的与您相关的数据相整合。我们利用发送给 Twitter 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Twitter 隐私政策
Facebook
我们通过 Facebook 在 Facebook 提供支持的站点上投放数字广告。根据 Facebook 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Facebook 收集的与您相关的数据相整合。我们利用发送给 Facebook 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Facebook 隐私政策
LinkedIn
我们通过 LinkedIn 在 LinkedIn 提供支持的站点上投放数字广告。根据 LinkedIn 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 LinkedIn 收集的与您相关的数据相整合。我们利用发送给 LinkedIn 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. LinkedIn 隐私政策
Yahoo! Japan
我们通过 Yahoo! Japan 在 Yahoo! Japan 提供支持的站点上投放数字广告。根据 Yahoo! Japan 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Yahoo! Japan 收集的与您相关的数据相整合。我们利用发送给 Yahoo! Japan 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Yahoo! Japan 隐私政策
Naver
我们通过 Naver 在 Naver 提供支持的站点上投放数字广告。根据 Naver 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Naver 收集的与您相关的数据相整合。我们利用发送给 Naver 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Naver 隐私政策
Quantcast
我们通过 Quantcast 在 Quantcast 提供支持的站点上投放数字广告。根据 Quantcast 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Quantcast 收集的与您相关的数据相整合。我们利用发送给 Quantcast 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Quantcast 隐私政策
Call Tracking
我们通过 Call Tracking 为推广活动提供专属的电话号码。从而,使您可以更快地联系我们的支持人员并帮助我们更精确地评估我们的表现。我们可能会通过提供的电话号码收集与您在站点中的活动相关的数据。. Call Tracking 隐私政策
Wunderkind
我们通过 Wunderkind 在 Wunderkind 提供支持的站点上投放数字广告。根据 Wunderkind 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Wunderkind 收集的与您相关的数据相整合。我们利用发送给 Wunderkind 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Wunderkind 隐私政策
ADC Media
我们通过 ADC Media 在 ADC Media 提供支持的站点上投放数字广告。根据 ADC Media 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 ADC Media 收集的与您相关的数据相整合。我们利用发送给 ADC Media 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. ADC Media 隐私政策
AgrantSEM
我们通过 AgrantSEM 在 AgrantSEM 提供支持的站点上投放数字广告。根据 AgrantSEM 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 AgrantSEM 收集的与您相关的数据相整合。我们利用发送给 AgrantSEM 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. AgrantSEM 隐私政策
Bidtellect
我们通过 Bidtellect 在 Bidtellect 提供支持的站点上投放数字广告。根据 Bidtellect 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Bidtellect 收集的与您相关的数据相整合。我们利用发送给 Bidtellect 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Bidtellect 隐私政策
Bing
我们通过 Bing 在 Bing 提供支持的站点上投放数字广告。根据 Bing 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Bing 收集的与您相关的数据相整合。我们利用发送给 Bing 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Bing 隐私政策
G2Crowd
我们通过 G2Crowd 在 G2Crowd 提供支持的站点上投放数字广告。根据 G2Crowd 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 G2Crowd 收集的与您相关的数据相整合。我们利用发送给 G2Crowd 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. G2Crowd 隐私政策
NMPI Display
我们通过 NMPI Display 在 NMPI Display 提供支持的站点上投放数字广告。根据 NMPI Display 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 NMPI Display 收集的与您相关的数据相整合。我们利用发送给 NMPI Display 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. NMPI Display 隐私政策
VK
我们通过 VK 在 VK 提供支持的站点上投放数字广告。根据 VK 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 VK 收集的与您相关的数据相整合。我们利用发送给 VK 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. VK 隐私政策
Adobe Target
我们通过 Adobe Target 测试站点上的新功能并自定义您对这些功能的体验。为此,我们将收集与您在站点中的活动相关的数据。此数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Adobe Target 隐私政策
Google Analytics (Advertising)
我们通过 Google Analytics (Advertising) 在 Google Analytics (Advertising) 提供支持的站点上投放数字广告。根据 Google Analytics (Advertising) 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Google Analytics (Advertising) 收集的与您相关的数据相整合。我们利用发送给 Google Analytics (Advertising) 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Google Analytics (Advertising) 隐私政策
Trendkite
我们通过 Trendkite 在 Trendkite 提供支持的站点上投放数字广告。根据 Trendkite 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Trendkite 收集的与您相关的数据相整合。我们利用发送给 Trendkite 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Trendkite 隐私政策
Hotjar
我们通过 Hotjar 在 Hotjar 提供支持的站点上投放数字广告。根据 Hotjar 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Hotjar 收集的与您相关的数据相整合。我们利用发送给 Hotjar 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Hotjar 隐私政策
6 Sense
我们通过 6 Sense 在 6 Sense 提供支持的站点上投放数字广告。根据 6 Sense 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 6 Sense 收集的与您相关的数据相整合。我们利用发送给 6 Sense 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. 6 Sense 隐私政策
Terminus
我们通过 Terminus 在 Terminus 提供支持的站点上投放数字广告。根据 Terminus 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Terminus 收集的与您相关的数据相整合。我们利用发送给 Terminus 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Terminus 隐私政策
StackAdapt
我们通过 StackAdapt 在 StackAdapt 提供支持的站点上投放数字广告。根据 StackAdapt 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 StackAdapt 收集的与您相关的数据相整合。我们利用发送给 StackAdapt 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. StackAdapt 隐私政策
The Trade Desk
我们通过 The Trade Desk 在 The Trade Desk 提供支持的站点上投放数字广告。根据 The Trade Desk 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 The Trade Desk 收集的与您相关的数据相整合。我们利用发送给 The Trade Desk 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. The Trade Desk 隐私政策
RollWorks
We use RollWorks to deploy digital advertising on sites supported by RollWorks. Ads are based on both RollWorks data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that RollWorks has collected from you. We use the data that we provide to RollWorks to better customize your digital advertising experience and present you with more relevant ads. RollWorks Privacy Policy

是否确定要简化联机体验?

我们希望您能够从我们这里获得良好体验。对于上一屏幕中的类别,如果选择“是”,我们将收集并使用您的数据以自定义您的体验并为您构建更好的应用程序。您可以访问我们的“隐私声明”,根据需要更改您的设置。

个性化您的体验,选择由您来做。

我们重视隐私权。我们收集的数据可以帮助我们了解您对我们产品的使用情况、您可能感兴趣的信息以及我们可以在哪些方面做出改善以使您与 Autodesk 的沟通更为顺畅。

我们是否可以收集并使用您的数据,从而为您打造个性化的体验?

通过管理您在此站点的隐私设置来了解个性化体验的好处,或访问我们的隐私声明详细了解您的可用选项。