AU Class
AU Class
class - AU

Work Smarter: Using Project Data and Insights with Autodesk Flow Production Tracking

共享此课程

说明

The complexities of managing a production can be a challenge to any production team, particularly when dealing with substantial amounts of data across various tools. Centralizing data tracking plays an essential part in optimizing the production process—a necessary strategy in any dynamic, client-centered industry where production teams need to be agile and capable of making swift adjustments to schedules and priorities. In this introductory session, we'll look at how to use Autodesk Flow Production Tracking software's cloud-based data management capabilities, demonstrated in the context of a simple games workflow. We'll explore the interface, explain the structure of data within Flow Production Tracking, and demonstrate how to use pages to track data and provide insights that decision makers can use to inform the success of their productions.

主要学习内容

  • Discover the organization of data within the Flow Production Tracking schema through examples.
  • Learn how to facilitate easy access to cloud-based data across multiple teams, locations, and projects.
  • Learn how to design pages to guide decision making, and extract insights into project requirements and progress.

讲师

  • Jessica Parsons
    With over six years of experience in production management across the media and entertainment industry, Jessica Parsons has worked on projects ranging from visual effects post-production and episodic animation to video games and virtual reality films. Jessica is on a mission to to simplify and streamline daily production tracking practices. Jessica currently works as a Technical Account Specialist for Flow Production Tracking at Autodesk, based out of Montreal.
Transcript

JESSICA PARSONS: Hi, everyone. I'm excited to be here today talking to you about Flow Production Tracking.

First, a little about me-- my name is Jessica Parsons, and I currently work as a technical account specialist for Flow Production Tracking with Autodesk. I'm currently based out of Montreal, and my role is to support product adoption and develop training resources to help make your adoption and usage journey as smooth as possible. My background is in production management, primarily for visual effects post-production in animated series and independent games.

So if you made it to this class today, it's likely because you're interested in learning what Flow Production Tracking can do to help leverage project data and insights to ultimately help you or your team work smarter, not harder. If you've worked on any kind of project, you know that things can get busy. Your attention gets pulled in so many different directions, whether by your team or by your clients or customers.

On top of that, you're often tracking large amounts of data or contributing to large amounts of data, whether that's task tracking, project tracking, status updates, resource management, costs, or all of the above. This is a beginner's session on Flow Production Tracking. And I'm going to be looking at it from the context of a game studio, using a very basic game project to demonstrate how Flow Production Tracking can help you track your data and how the data can be used to provide insights through data visualization. But everything I cover today about Flow Production Tracking can be applied to any kind of project you might be managing.

In this session, I will provide an introduction to Flow Production Tracking. So if you're unfamiliar with the tool, don't worry. I will cover a basic overview.

Next, I'll explain the organization of data within the Flow Production Tracking schema to help you understand how all of your data in Flow Production Tracking is connected together.

After that, I'll talk about how Flow Production Tracking can facilitate easy access to cloud-based data across teams, locations, and projects. Regardless of where your team members are located, everyone can have quick and easy access to the same information.

And last, but not least, we will get into designing pages to help guide decision-making and to extract insights into project requirements and progress.

So let's get started with a basic introduction to Flow Production Tracking. So Flow Production Tracking is Autodesk's production management software. It's heavily used in media and entertainment across film, TV, advertising, and games. But it's also becoming more common to see it used across the automotive, design, and manufacturing industries. You can use Flow Production Tracking to set up, track, and schedule every step of a project, from tracking test deadlines and progress, managing teams, resourcing projects and tracking productivity, and sharing and reviewing media.

For anyone who has worked on any kind of production, you know there's just so much data that goes into a project. And tracking all of that data can be a huge challenge, especially when you're tracking across multiple tools.

Centralizing data tracking plays an essential role in optimizing the production process. This is where Flow Production Tracking is designed to be the solution to be a central hub that unifies production management. With Flow Production Tracking, you can set up and schedule every step of a production, import bids and use that information to compare how many days your clients are paying for versus the actual number of days your tasks will take; schedule delivery dates and project phases to keep track of the major stages of your project; book team members using bookings and visualize them with the crew planner; and schedule individual tasks, tracking assignments, dependencies, and hours logged to each task. With Flow Production Tracking, you can track deadlines to be sure teams are working on the right things at the right time and that they have the information they need to get it done.

Dashboards can give you an overview of where your project is at, who is doing what each week, and how close to your targets you are. Managers can use pages to review the work submitted in their departments before sending that work to supervisors. And individual contributors like artists can see what's been approved or is coming down the pipeline in their direction.

With Flow Production Tracking, you can also collaborate with media playback and review tools to give feedback with annotations and notes. You can use tools like RV, the overlay player, screening room, and the review notes app.

Ultimately, you don't want to lose any information through the course of a production. And that's where Flow Production Tracking is really there to help consolidate the number of tools you're using into just one. The idea is to plan, schedule, track, and review all from the same place. Everyone on a team can keep track of what is happening. So let's go ahead and take a look at the Flow Production Tracking interface.

Flow Production Tracking is essentially a website. You'll navigate your site using the global, project, and page navigation menus. The global navigation is at the top of the page, giving you quick access to your inbox, tasks, and sitewide information. In Flow Production Tracking, most people will find themselves working within specific projects. You will create a project or be added to one by another user. And from within a project, you'll be able to plan, schedule, track and review.

Here, you can see the projects on my site. And for today's demo, I'll be working within the Maple Game project. So I'll go ahead and select it.

Now, within this project is the project navigation, which is customizable with whatever pages are most relevant for your team. Each page has its own page navigation, which you'll use to work with the data on your project. Now, the goal for this session isn't to get into the nitty-gritty of where to click and how to add data to your site. What I really want to show you is how you can track and share your data and use it to better inform your decision-making. Since Flow Production Tracking is a website and you'll be working with web pages, pages are where you'll be able to see, share, and visualize your data.

So before we get any deeper into pages, I want to talk a little bit about what actually gets displayed on a page. So let's talk about the organization of data within the Flow Production Tracking schema.

Data in Flow Production Tracking is organized into entities. Each entity is a container in which data can be stored. You can almost think of it like a computer directory or folder. Assets, levels, tasks, time logs, even people-- these are all considered entities. Flow Production Tracking comes with a set of pre-designed entities, but there are also custom entities that you can use and customize however you want.

When I'm talking about the Flow Production Tracking schema, I'm referring to how the entities in Flow Production Tracking are used, configured, and connected to one another. I'm going to map a very simple game schema-- a very simple one-- to give you a better idea of what I'm talking about.

So here, we have our project called Maple. The project entity is the container for all the information tracked within Maple. Levels is one of many types of entities that fall within the Maple project. Individual assets are linked to levels, and they're broken out into various asset types, such as characters, props, environments, vehicles, and weapons.

For each asset, a series of tasks needs to be completed. And for each task, time logs will need to be created. In this example, the project, levels, assets, tasks, and time logs, they are all entities.

Many entities can fall within others. There are many different ways to connect to entities. And the hierarchy of entities on your site will depend on your project and the type of information that your team needs to track.

And just to be clear, many entities can appear multiple times throughout the hierarchy. So here, in addition to having tasks that need to be completed on each asset, we can also have tasks that need to be completed for each level. These tasks can also be dependent on each other. So I can have weapons or props that need to be modeled, textured, and rigged. Then those completed assets can be passed up to the team working on a particular level, who can then start their tasks that incorporate those props and weapons into loot chests that are scattered around the environment.

Since those assets are going to be used across many different levels, it doesn't make sense to incorporate them into the list of tasks that needs to be completed within one particular level, because then I'm going to have to recreate these tasks on every level that they appear in. But it might make sense to have loot boxes as its own entity type. This way, the assets get completed, then they get compiled into loot boxes, and those loot boxes can be distributed to the appropriate levels.

So now that we've gone over schema and the structure of data in Flow Production Tracking, I want to talk about how Flow Production Tracking facilitates access to your data. The answer here is pretty simple-- Flow Production Tracking is a website, and your site is hosted on the cloud, which means any data you add to your site is cloud based. Anyone who is given permission to access your site will be able to see your cloud-based data.

Now, who can see what data and what pages can be controlled through permission groups that get assigned to users. For example, you can limit page access, such as access to a dashboard. You can limit access to particular views of a single page, such as if you're displaying financial information. And you can limit field access so that pages and views are still accessible to everybody, but the data contained within particular fields that could be sensitive is not accessible to all users.

But what exactly is the data that you're sharing? Data here refers to any information that's captured and stored about a single entity, such as a level, an asset, or even a user. For example, if you're capturing and storing information about tasks, each task is a single record of the task entity, and each task's name, description, and duration are attributes of that entity record. All the information that you collect and store about your tasks is your data.

All your data can be accessed by the users you choose from anywhere with an internet connection. And you have the control over exactly what parts of that data they can view and edit. With Flow Production Tracking as the single source of truth, everyone can have quick access to the same information.

Teams working from different time zones don't necessarily need to share long handoff emails or recap updates and changes, since everyone on the team, no matter where they are, will have access to the information that's relevant to them.

So, for example, here, we see a list of assets on the Maple project. Each one of these assets is a record of the asset entity. Now, all fields in Flow Production Tracking are connected to an entity. Each one of these records has information on display, which has been filled into fields. The headers are the field names, and the cells are the data that has been added into those fields.

Since when entering data into Flow Production Tracking, you're entering data into a field, all of the data you enter is tied to an entity. While Flow Production Tracking essentially works as a website with web pages, the important takeaway here is that the data on each page is not page specific. Changing data on a page will impact that data displayed elsewhere on your site. Everything is connected. So you and I can be on the same site looking at two completely different pages, pulling up the same records, and we can see the same information regardless of what page that information was input to.

For example, I have two pages here. I've got the assets page and my project navigation where we just were. But I also have this custom page I created that also displays assets. Even though these are two completely different pages, the asset names, descriptions, type, status-- essentially, all of the details that were added into fields that we saw on the initial assets page-- that data is the same on both pages.

If I change data on one page, which I'll demo here by removing an asset description, this data will change on the other page because the data is connected to fields, which are connected to each unique entity record. And that data is universal across your site. This data is connected to the same record. We're just displaying it differently in two different places.

Now, I mentioned earlier that who can see what data and what pages can be controlled through permission groups that are assigned to users. Not only can you control what projects and pages users can access, but you can even control what entities and even what fields on an entity they can access.

For example, maybe I don't want all users to see the number of days a client has paid to complete assets. But to use Flow Production Tracking as my single source of truth, I need to have this information on my site. I still need to see it.

Here on my assets page, I've got a field for bid days, which represents how many days of work my clients are paying for. If this is sensitive information, I can restrict permission to this field. I can right-click the header and select Configure Fields. By going to permissions, I can decide which permission groups will have access to see and edit the field.

Now, I've already configured this to only allow managers and admins to see this field. If we go back to the page, this is the main assets page for the Maple project. I want to make sure that all users can see this page, so I don't want to restrict page access. But I do need to make sure that not all users can see the bid days field.

To test out what this will look like to a user who isn't in the manager or admin permission groups, under Page Settings, I can go ahead and use the use as another user function. Here, I'll type the name of a user that I know is in the artists' permission group, so she won't have permission to see this particular field.

Now we can see that Jordan can view the assets page, but that the bid days field isn't visible to her. Even if she tries to add in the field, she won't be able to see the field as an option. It's been completely hidden from her. So that's data.

Now that we've gone over data, I want to demonstrate how to use pages to display and track your data to provide you with insights. Page types can be broken down into three main categories, each containing their own sets of customizations and views. There are entity pages, canvas pages, and URL pages. Today, I'm going to talk about entity and canvas pages. The goal here is for you to understand how to make the most of the data that you have.

So let's go back to the Maple project. First, I'll cover entity pages. Entity pages display entity records. The types of entity pages that can be created will reflect the available entities on your site. Entity pages can be broken into two main types, list pages and detail pages.

List pages allow you to see information about a list of entity records, such as a list of assets. This assets page that we've been looking at is an entity list page. Then you have detail pages, which allow you to see information about a single record, such as a single asset. From the details pages here, you can see all of the tasks, all of the notes, versions, and time logs associated with this particular asset and any other information that you want to see.

Going back to a list page, I'll open the levels page here for this example. There are a few different layout options. List view is the main view of most entity list pages, allowing you to see a list of entity records. Then here, we have detail view, which lets you take advantage of entity list and detail pages at the same time. You can see information about a single record on the right-hand side, such as a single level, while able to jump through the list of levels on the left. And then there's thumbnail view, which presents records as a gallery of viewable thumbnails. These can be customized to display any fields you want, so it doesn't only need to be an image attached to the little card.

OK, so you've got a Flow Production Tracking site, you have a project, and you've got entity pages. So now let's talk about displaying and tracking this data.

Entity pages allow you to track and display the exact information you're looking for. You can choose what fields are displayed and how the information looks to narrow down the data you need. You can group or sort data on a page to organize it in a way that visually represents what you're trying to get out of it. So, for example, you can group tasks by asset to see the progress of the individual tasks needed to complete an asset. Or you can group tasks by due date to see the progress of all work assigned by week, month, or day, depending on how you want to view it.

You can display summaries of fields and groups to get an overview of field information as it applies to a group of information. So, for example, you can see the earliest start dates and latest due dates of tasks to see what the project timeline is looking like. You can see a sum of the duration of tasks to see how many days' worth of work there is to do in total. Or you can see a percentage of tasks that are final.

Just by grouping your data in different ways, you can visualize high-level information to make quick decisions. If there are key fields that you need your eyes to go to when you're looking at a page, you can format header and cell colors. You can set the color of any field header to bring attention to it. There's a couple of options here. I'm setting the start date to pink.

Same for cells and rows-- you can set the background color of any cell or row. So here, I'll do the same thing. I'll format my cell colors, and I'll also change it to pink. And we can see it reflected in our column here.

Another tracking tool is conditional formatting rules. You can format the background color of rows or cells based on any criteria you set. So, for example, you can highlight tasks due this week, highlight overdue tasks, or highlight important deliveries using tags or any other field information that you've filled in.

As an example of this, I'll go ahead and set a rule on the due date field for tasks due this month by right-clicking over the due date header and choosing Change Cell Color with Rules. Here, I'll add a new page rule called Due This Month. And I'll set the conditions to be due date is in calendar month current. I'll change the background color to orange and hit Save.

Now, I want to make another rule for tasks that are in sprint 2. I can go ahead and make this rule by right-clicking over any cell and choosing Format All Rows, Change Row Color with Rules. So here, instead of formatting the cells in a single column, I'm going to format a row. Here, I'll add a new page rule called Sprint 2. I'll set the condition to be sprint is sprint 2, and I'll change the text color to blue and hit Save.

With these two rules applied, I can quickly and visually identify which of these tasks are due this month, which are part of sprint 2. The cool thing with due this month is that each month, the highlighted tasks will change. So this rule will always be current. And that's really going to help me to visualize what's important.

Filters allow you to filter your data based on the information of the fields linked to each record. You can use the filter panel to turn filters on or off. Filters can be inclusive or exclusive, so you have the ability to search for data that includes or exclude certain information.

You can also create saved filters, which allow you to not only save time when you're constantly filtering for the same types of information, but allow you to get much more specific with how the data is filtered, where conditions aren't only inclusive or exclusive.

You can also create filter groups. So you can search for data that meets completely different types of conditions. Your filter can be set up to search for all filter group for conditions or for any.

So, for example, I have a saved filter here called upstream dependencies-- or, sorry, upstream completed. And I'll select Edit so you can see what it's filtering. So this filter searches for modeling tasks where the status of the art task is approved and for breaking tasks where the status of the model task is approved.

Now, narrowing down pages into different views-- which are displayed on the top right of the page here-- with saved filters allows you to track very specific and very different data without having to create different pages or have too many saved filters on a single page. So, for example, you can have a page for tracking tasks, and each view can show you tasks due this week or tasks due in a specific department.

This way, again, you don't have to filter your tasks page every time. You can just change views. Each of these views can be organized in a different way with different fields, formatting, and headers. So that's entity pages.

Let's move on to canvas pages. Canvas pages start as a blank slate, or canvas, without any data on them at all that can be customized to present the information that you need in a more visual way. Canvas pages are populated with widgets, which are visual elements that display information.

Some of the built-in widgets include a thumbnail widget, which we can see on the left here, that can display the thumbnail image of a single entity. So here, we're seeing the project entity thumbnail.

A countdown widget marks the number of days until an important milestone, such as a project delivery or end date-- so here, we're counting down the days until the end of the project. The graph widget allows you to choose from multiple graph types to visualize a filtered group of records. You can select the visualization type that suits your data the best, including bar, line, area, step, and pie.

So first on this page, we have a pie chart that is showing us the number of tasks in each sprint. I can tell just by looking at this graph that sprint 3 and 4 are heavier with tasks and will be a busier period on the project overall. Below that, a vertical bar chart shows the number of tasks due this week by department. So I've got 40 tasks in total and 19 with the modeling team. So I can see what teams are going to be busy. To the right of that is another pie chart showing the status of all levels on the Maple project, giving me a nice little overview of where the project is at, since I know when all my levels are done, and done the project altogether.

Below is a horizontal bar graph, which is graphing tasks by pipeline step, similar to the vertical bar chart above. But it also has them grouped by status. So at a glance, I can really see where each department stands on this project.

To the right, I have another horizontal bar graph displaying the total number of assets in each level. This gives me an idea of which levels I maybe want to tackle first. Maybe I can get some quick wins if I complete the assets in the levels that require fewer assets overall, I can get those levels done and out of the way.

Now, grids are another kind of widget on the bottom left here. They can display the same information as a standard entity page. It looks just like an entity list page here. So we have a list of levels on the project with our descriptions and status, and I can add in any other fields that I want to see. To the right is another grid widget and thumbnail view to see all the latest media versions on the project.

You've got a site, you've got data, so how can you make your own pages and dashboards? All you need to do is go to Project Pages and select New Page. From here, you can give the page a name and choose the page type. If you are creating an entity page, you can start by choosing the type of entity records you want to see, whether that's level, person, or version. If you're creating a canvas page, you can scroll down to the bottom and choose Canvas.

I'll start with a Canvas page. I'm going to make a department dashboard, so I'll name the page Department Dashboard and then select Create Page.

Now that the page has been created, I can enter design mode and start visualizing my data. I want to see what is going on in each department. So let's start with my first pipeline step, which is the art department. Instead of a widget, you'll simply drag and drop it into your canvas page.

So first, I'll bring in a grid widget that shows all of the bookings on this project. Under widget settings, you can give the widget a name, which is going to appear in the header at the top of the widget. So here, I'll choose our team.

Next, you can set the text and background color for the header in case you want to use colors to identify your widget. You can also choose if the graph will be collapsible on the page or if it has an outline. These settings are really all about making the widget work the best visually for you on the page, depending on how many other widgets you have on your canvas page and how you and your team best visualize data.

Next, I'll set up a filter to show me bookings linked to the Maple project and where the person who's assigned to the booking is from the art department. I also want to be sure to capture only those people who are actively booked today, so people whose bookings are essentially in progress.

So I'm going to go ahead and set up that filter. And I'll bring in the thumbnail of the assigned user so I have a visual. I'll remove fields I don't want to see, and then I will uncheck Show Toolbar. Once I'm happy with this, adjust the layout, and I will save my widget. And I have my first widget with my art team.

Next, I'll bring in a graph widget to show tasks in the art department. So I'll drag a graph onto the canvas and choose the entity I want to graph, which in this case is tasks. And I'll hit Configure.

Now, if you choose the wrong entity, you can change it after you've hit configure. So you don't need to worry too much if you choose the wrong thing here.

Now we're going to configure the graph. On the left-hand side, you're going to be able to configure the same basic widget settings we had with the grid, the data set the graph is going to show, the filters applied to the data, as well as your display options.

Under data set, you can choose your graph type and graph style. If you choose a vertical or horizontal graph, you can choose from bar, line, smooth line, area, and step. If you choose a pie graph, you have no styling options. You just get a pie graph. For this demo, I'll stick with the horizontal bar graph.

Now, I mentioned that you can choose the entity type you're graphing after you create the widget. And this is where you would do that.

Next, you need to decide what about that entity you want to grab. So you're going to choose from the fields that exist for or are connected to that entity. For this demo for this dashboard, I'll graph my tasks by assigned to. This way, I can see what everyone's workload is.

For horizontal and vertical graphs, you have a few options about how the data is going to be displayed. Here, you can choose if your data will be graphed by exact value or by first letter. You can also sort the data alphabetically or by value. So let's change this to alphabetically so I can see the team in alphabetical order.

Next, you can choose to group your data. This gives another level of detail. For this demo, I'll group my tasks by status. And now I can see how many tasks are assigned to each person and their status.

So this is OK, but it could look better. We actually have the option to stack this information. So you can choose your stack type-- 100% is going to stack the bars with the statuses, but each bar is going to be the same length. Regular is going to stack the bar with the statuses and give us the visual total tasks assigned to one person versus another. This is what I want as part of that visualization piece I'm trying to achieve with this dashboard. So I'll choose regular stack.

Next, you can filter down your data set to display only what you need. I only want my graph to show me tasks in the art department. So I need to filter down the pipeline step to be the art department.

I also only want to see tasks with due dates in the current calendar week. This way, this page can be used as a weekly overview on each department. And so once you set your filters, you hit Update.

Next, we have our display options. So from here, we can choose to display values, which will add the total value at the end of each bar; totals, which will add the overall total records to the bottom of the graph; max categories, which will limit the total number of data displayed.

So, for example, here, I can set it to 2. It will truncate the data, and I now have the option to show all and expand the data. So if you had a lot of records and you wanted to limit how many are shown onscreen at once, you can do that.

Color in this case allows me to use status colors, since status happens to be something that has an associated color in Flow Production Tracking. But I'm not always going to have a color option for my graph. I do want to use my status colors, so I'll check the box.

This is a way that I like to visualize data, with status colors being consistent across my site. When I see gray, I know a task is waiting to start. When I see green, I know it's pending review. When I see blue, I know it's approved. This is a really easy way for me to visualize the status of tasks on the project. Once you're happy with your graph, you can hit Save and go back to your canvas pages design mode.

Now, I don't like the layout of these widgets, and this graph I just created looks a little squished. I can use the View tab to change the page layout and adjust the width of the widgets. If you need to edit the graph, just hit Edit on the widget while in design mode. When you're happy with your page, you can hit Save to save the page.

Now, before I save, I'm going to add a pie chart to show me all of the art tasks by status. So I'll grab the graph widget, drag it into position, set it to tasks, and configure it. Once I've given the widget a name, set the type to pie, and set my conditions-- which, in this case, will be art tasks with due dates in the current calendar week-- I'll save the widget.

Before I do that, I'm choosing my status colors again. I'm also making my pie chart into a ring, adding a value to the radius field. I'm also going to adjust the layout of this page again by going to the View tab.

Now I'm going to add another grid widget to see any media that has been added to the project related to art tasks. So to do this, I'll go back to the widgets, drag over a grid widget, and configure it for versions. Using the toolbar, I'll add a saved filter.

Now, all the media on my project is submitted by the artists assigned to do the work and linked to the tasks that they are assigned to. So in this case, I'm going to create a saved filter that shows versions where the linked task pipeline step is art and the linked task due date is in the current calendar week. Now I can save the filter, hide the toolbar, and save the widget.

I'm going to change the view of this page by adding a new row because I want to see the grid on a larger scale. I'll add a new row and set the columns to 1, then drag the grid widget into the new row. Now I can tweak the fields a little leaving only relevant information. And I'm also going to group the versions by artist.

Now I can see any media submitted for art tasks that are due this week, who submitted them, and their status. Now I can go ahead and save this page, and I've got a nice little dashboard for the art department to see who is working on the Maple project this week, what tasks they are assigned and the status of each, and what media has been submitted related to those tasks.

This is cool. But now I want to create a dashboard that all departments can use. So for this, I'm going to create different views. I'm going to go back into design mode. And from here, I'm going to name the default tab to art. Then I'm going to go ahead and duplicate the view.

Now I can rename this one modeling since I'm going to use this for the modeling department. And I can go ahead and edit the widgets, changing art out for modeling. I'll do that by selecting Edit and updating the filters one by one for each widget.

First, I'll change the bookings widget. Next, I'll change the task by assigned and status widget, and then I'll update the tasks by status widget.

Down at the bottom, instead of versions, I want to see a list of the modeling tasks that are either due to start or finish this week that haven't been started at all. So I'll delete the current widget and drag in another grid widget.

I'll give the widget a name and use the toolbar to set a saved filter that I will call Waiting to Start. I'm going to make two filter groups. I will set the pipeline step to model, the due date to the current calendar week, and the status to waiting to start. Then I will make the same filter again, but for start dates in the current calendar week instead of due dates.

So once I have this set up, I can save the filter and then organize the fields, hide the toolbar, and save. So when I'm happy with this and I want to use this view now for the remaining departments, so I'll duplicate this view again and go through the same process for the rigging department and for the texturing and character effects departments. For the sake of time, I won't update the widgets now, but then I can go ahead, create these views, and save the page.

Graphs are really powerful and can show us data in a way that a lot of pages can't. You can export this data into a CSV file if you ever need to create a report or send this information to someone. In the top right-hand corner of your widgets, there is a Download button with a few options.

Show Source Data is going to open up the data in the form of an entity list page. The layout of this pop-out can be customized. Save Image As downloads a screenshot of the graph if you wanted to use the visual in a report. Save Data As allows you to get adjacent or CSV export of your data. And Print will just print the actual graph image.

And you can also select any one of your widgets to expand the information being visually represented to see the data that's feeding that visual. Canvas pages are particularly helpful to get a broad overview of a project, since so much different information can be brought into a single page. If I want every department on my project to use this page, I can actually add it into my project navigation by going to the Page Settings dropdown and selecting Add To Navigation. Here, I can drag the new Department Dashboard I just created into whatever spot I want it to be in, hit Save, and now everyone on this project will be able to easily find and utilize the same visual information.

You can use canvas and entity pages as views on any page. So in that way, you can combine the best of entity and canvas pages to really narrow in on the views that will best help you to visualize your project data in a way that informs your decision-making.

So to conclude this presentation, managing data is complex. Centralizing data tracking is an essential part in optimizing the production process so that teams can be agile and react quickly to changes. Cloud-connected data means everyone on a team can have the same information from anywhere. Data can be restricted to only those who need it. Pages can be customized through layout, formatting, filtering, and views, to best display insights on the data you collect through your project's development.

You want your data to be organized and connected, accessible from anywhere, trackable by anyone, and insightful to those who rely on it to make decisions. I hope this class has been able to give you some insight onto what Flow Production Tracking can do to help you organize, access, track, and leverage your project data. Thank you.

______
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 的沟通更为顺畅。

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

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