说明
主要学习内容
- Learn how to use constraints to iterate on and optimize a production schedule.
- Learn how to create scheduling scenarios to plan for constraint changes, such as changes to resource availability and deadlines.
- Learn how to use resource shaping to refine a schedule for specific resource classes to better optimize resource usage.
讲师
- JPJessica ParsonsWith 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.
JESSICA PARSONS: Hi, everyone. I'm excited to be here today to be talking to you about Flow Generative Scheduling. 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 with the goal of making sure that anyone who tries to use Flow Production Tracking is able to use it successfully and has a positive experience doing so.
My background is in production management, primarily for visual effects, post-production, animated series, and independent games. Before I get into Flow Generative Scheduling, I want to introduce Flow Production Tracking for anyone who is unfamiliar with the product because I will be speaking a little bit about it today. So Flow Production Tracking is Autodesk 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 automotive design and manufacturing.
You can use Flow Production Tracking to setup, track, and schedule every step of a production, from tracking task deadlines and progress, managing teams and tracking productivity, resourcing projects, and sharing and reviewing media. Managing lots of project data can be complex, so centralizing data tracking is an essential part in optimizing the production process so that teams can be agile and react quickly to changes.
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. This is where Flow Production Tracking is designed to consolidate the number of tools you're using into just one. The idea is to plan, schedule, and track from the same place. So you might be wondering where Flow Generative Scheduling fits into all of this.
If you've ever had to put together a project schedule, how many times have you had to change your plans from what you initially thought? Early in my career, I admit I was a bit naive about scheduling. I'd say things like. The schedule is done. And be so sure that it was. But I don't think that the schedule has ever really been done, at least not until the project is over. Plans are always changing, and that's just the reality of production.
What we need is a way to adapt our schedules when changes need to happen. Sure, we can update our schedules manually, but on large-scale m or any project with a lot of connecting parts, this can be a really time consuming task. We all know this, especially for something is going to change again. So that's where Flow Generative Scheduling comes in. Flow Generative Scheduling is a new tool that works alongside Flow Production Tracking.
It can quickly generate level schedules using the task information from your Flow Prediction Tracking site. Task data, including task dependencies, duration, pipeline steps, and department will get pulled from your site into a playground. From your playground, you'll be able to create different scenarios and use constraints, priorities, and resource shaping to level your different scenarios. When you have a scenario that you're happy with, you can send it back to Flow Production Tracking and apply it as your schedule.
Your tasks don't even need to be scheduled in the first place to use the tool. Generative scheduling can actually generate the initial schedule for you. So what I want to show you today is how to use generative scheduling. I'm going to start by showing the round-trip process from Flow Production Tracking. Next, I'll talk about using constraints and priorities to iterate on your schedule. Then, I'll cover creating different scheduling scenarios. And finally, I'll look at refining the schedule even further with resource shaping.
So let's start with the round-trip process. First, I'm going to open one of my Flow Production Tracking sites and show you a project that I'd like to schedule. Here I am on my site. And I have a project called Luna. This project is a visual effects film project with sequences and shots. And each shot has a series of tasks that need to be completed. In order for you to use Flow Generative Scheduling, there's a few requirements that your tasks need to meet.
First, each task needs to have a duration. This is the estimate of how long each task will take. Next, each task needs to have a pipeline step. In Flow Production Tracking, pipeline steps are linked to departments, and so are people. So this is how generative scheduling will know your resource utilization. Finally, your tasks need dependencies. There are lots of different ways dependencies can be set up in Flow Production Tracking, but essentially, dependencies tell Generative Scheduling which tasks need to be completed before others.
Generative Scheduling will use this information to schedule all of your tasks in the right order. So we have duration, pipeline step, and dependency. These tasks look good. They all have the information that's required, but what they don't have is dates. And so that's where we want to use Flow Generative Scheduling. Now, let's make a schedule. I'm going to move forward along the following premise that I'm going to start work on Luna on November 1, and I want it to be finished around March 30.
So to get started, you're going to navigate to Flow Generative Scheduling through the app's dropdown menu on your Flow Production Tracking site. You can control access to a lot of features in Flow Production Tracking through permission roles. So access to the app can be restricted if you want it to be. With Generative Scheduling open, the first thing you want to do is make sure that you're connected to the correct Flow Production Tracking site.
You're going to do this by using the Connection Setup tool, which you can find in the top right-hand corner of the screen under the Admin menu. From the Connection Setup tool, you'll be prompted for your Flow Production Tracking site URL and login. So you'll enter those and select Connect. Once you get confirmation that your site is connected, it'll look like this. You can start bringing in task data from your site. Now, here, I'm already connected to the correct site, so I can go ahead and close this.
But if I wasn't connected to the correct site or I wanted to be connected to a different site, I would just select Disconnect and log-in to the other site. Now, the task data you bring into Flow Generative Scheduling is going to be created as a playground. A playground is a sandbox in which you will create your schedule scenarios. Each playground is a snapshot of the schedule from the time it was pulled as opposed to being a live production data.
And all of your playgrounds will be visible from the home page. Here, you can see I have a lot of different playgrounds, and I can access any of them. For now, we want to create a new playground for the Luna project. So I can go ahead and select Create New Playground. Next, you'll be prompted for a data source. I won't talk about this today, but you do have the option to work with Open Schedule Format, or OSF.
However, I want to work from my Flow Production Tracking site, so I'm going to select Use Schedule Data for Flow Production Tracking and select Next. Now, we'll be prompted to choose a project from your Flow Production Tracking site. I'm going to choose Luna and hit Next. Next, you'll configure the playground by choosing a name and description to identify it. And you'll choose a date from which you want your schedule to start.
I'll go ahead and choose November 1 because that's when I want the schedule to start from when I want to start working on this particular project. Now, you can hit Next, review the details, and select Create Playground. Now, without doing anything except importing task data, you've got a schedule. All you did was tell the tool when you wanted your schedule to start from. And with information about how long each task should take, what kind of resources are required for each task, and what tasks are dependent on others, all data that came from Flow Production Tracking, Flow Generative Scheduling has created an as-soon-as-possible version of the schedule.
Now, this is a great start, but it could be even better. Generative Scheduling can help you create a level schedule much faster than you could do by hand. I'll cover this in detail in the next section, but I'm going to go ahead and add a finish-no-later-than constraint on the project of March 30, which is an internal deadline. I actually don't need to finish this project until November of next year, but let's be super optimistic and set it to the end of March.
Now, I can select Generate, which will run the solver on my data. Not only will generating the schedule help to better determine prospective schedule dates, but the solver will do it in a way that helps you avoid peaks and valleys in resource utilization without having to do all the time-consuming balancing of resources yourselves. OK, so now let's say you're happy with this schedule. To send your schedule to Flow Production Tracking, you're going to select the Export icon on the top right of the screen and choose Send to Flow Production Tracking and then hit Send Scenario.
So once this process begins, it can't be canceled. The process can take several minutes, just depending on the size of the project. Last time I did this, it took me about 18 seconds. For some context, this project contains 10 sequences with a total of 990 shots and 5,451 individual tasks. So not too bad for 18 seconds. OK, so now that that's done and the scenario has been sent, you can go back to your Flow Production Tracking site to see what Flow Generative Scheduling has done.
Taking a look at our tasks here, it doesn't look like anything has changed. We still don't have start or end dates. So what did Generative Scheduling do? When you send your new schedule to Flow Production Tracking, Flow Generative Scheduling didn't directly modify your existing schedule. Instead, the dates you just sent over will be added to a date field called Proposed Start Date, which had hidden, and I'm bringing it now.
Now that the field is visible, we can see all of the dates from the scenario we just sent over from Generative Scheduling. This allows you to review the dates or even to change your mind before applying any kind of schedule. It essentially protects your live production schedule from accepting changes until you're ready for them. When you're ready to apply the new schedule, you can go ahead and select all of the tasks you would like to apply the new schedule to.
Right Click and select Apply Proposed Start Date. This can take a few minutes to process, again, just depending on how many tasks you're updating at once. Now, when the Apply Proposed Start Date option is used, the value of the proposed start date is cleared. So you can see here that the Proposed Start Date field is now empty. The value of the Proposed Start Date field replaces any existing value in the Start Date field.
So again, you can see that the date that was in the Proposed Start Date field has been transferred over to the Start Date field. And the value of the Due Date field is updated automatically based on the task duration. This is the way Flow Production Tracking works. If there is a task with a duration of five days and a start date of November 1, then the end date would be November 5. We just add 5 days to whatever day we're starting on.
And as an additional note, Flow Production Tracking also has the ability to set up work schedules. So it's smart enough to know that November 2 and 3 are actually a weekend where nobody will be working. So if the task starts on November 1, the duration is five days, and the second and third are non-working days because that's a weekend, then the end date will be November 7 instead of November 5.
Project work schedules will import to Generative Scheduling when you create a playground. So when you're working on your schedule, the weekends or non-working days will be taken into consideration. You can actually see this here, because I've set up Wednesdays to be a non-working day. So the Gantt chart is displaying gray columns over Saturday, Sunday, and Wednesday. And the Task Start and Due Dates have taken those non-working days into consideration.
So that's it. I just added dates to a schedule with 5,451 tasks from scratch in less than 15 minutes, plus a couple of minutes of talking. It's as easy as that. So now, let's talk about using constraints and priorities to iterate on your schedule. A constraint is a time-based limitation used to describe when work can or should occur. All activities in Flow Generative Scheduling can have constraints. An activity in Flow Generative Scheduling is a task milestone or summary, such as a shot, asset, or sequence.
So let's apply a constraint. To easily apply a constraint, you're going to start by opening your playground. So I'll open the Luna playground. Next, you can make sure the Schedule tab is open. The Schedule tab shows us all the activities we're scheduling, details about them, and displays everything in a Gantt chart. So you've opened up the Schedule tab. Now, you'll select an activity. So in this case, I'll select a shot.
Your project's activities will be displayed in the same hierarchy that they exist in Flow Production Tracking. So here, I have a project with sequences. Each sequence contains shots, and each shot contains a series of tasks, and I can see that reflected in my hierarchy. Now, go over to the Activity Options, which are the four icons on the right-hand side of the screen. The Information tab at the top shows you general information, such as activity type, tags, and categories.
The Controls icon displays information about the constraints and priority for an activity. The Dependencies tab displays upstream and downstream dependencies, both local and external. Internal dependencies are within the same summary. So for example, tasks within the same shot that are dependent on each other are local dependencies. External dependencies are across different summaries. So an example of this on a film project would be a task on a shot that is dependent on a task on an asset.
And then you have the Calendar tab, which displays the standard working days for the activity, along with any work day exceptions. So this is what I was talking about earlier when I mentioned work schedules from Flow Production Tracking. OK, so I just showed you four activity options. Right now, because we want to work with constraints, we want to open the Controls tab. Right now, I still have a task selected, so I'll go ahead and select the shot.
Now in the Controls tab, under Basic Constraints, you can select, Add a Constraint, and choose a constraint from the list. When you hit the Generate button, the newly set constraints will be taken into consideration in the output schedule. Now, constraints can be used to enforce that work must start as soon or as late as possible, start or finish on a specific date, start no earlier or later than a specific date, and finish no earlier or later than a specific date.
The available constraints will depend on the activity and also other constraints that have already been applied. Here, if I select a shot, I get a lot less options than if I select a task within that shot. By setting constraints, you can make sure certain aspects of your schedule get prioritized. So let's test this out with our current example here. Let's say you're making a movie, and you have a few sequences you need completed by a certain date. So you can select a sequence and open the Controls tab, select Add a Constraint, choose Finish No Later Than, and choose a date.
Now, some of these dates are going to be red. That's because they're infeasible. What the red is telling us is that, based on the amount of time each task in the sequence is going to take, there's just no way that all the work in this sequence can be completed by these dates. You can, however, choose any one of the black dates and you'll be good. Now, I talked about using constraints as a way of setting priorities on your schedule, but you can actually set a priority value.
You can think of constraints like hard goals or requirements and priorities more like soft goals or nice to have. Maybe you have lots of shots to complete, but you'd like one done sooner than later. The client isn't asking for it sooner, but you want to get it out of the way, maybe because of the types of resources it will use or maybe its level of complexity or something like that. Whatever the reason, you can give your activities, in this case shots, a priority number, which will make Flow Generative Scheduling try to schedule the shots relative to other priorities.
But if it doesn't work within the various constraints or hard requirements you've set, then it'll do what it can within the limits of those constraints. So you can select a shot and give it a priority value. You can choose any value between minus 1,000 and plus 1,000. The numbers are just relative to each other. So if you planned on using lots of priorities, you could jump by tens or hundreds, whatever works for you. Let's assign a priority of 1,000.
On the next shot, we can set a priority of 900. On the next, we can do 800. And we'll leave the rest at 0, which is the default value. Now, when we generate our schedule, an attempt will be made to schedule these to be completed ahead of the other shots. And we can already see that reflected in the schedule in the Gantt chart. So now, what happens if you want to create different scenarios?
You might, you probably will, find yourself in a situation where you want to explore a few different options for your schedule. Within your playground, you can create as many scenarios as you want. You can create a new scenario from scratch that uses your initially imported data, or just go ahead and duplicate a scenario that you want to make a few tweaks too to create a variation or alternative version of a schedule.
I'm going to go ahead and create a new scenario so you can see what it's like to compare them. To create a new scenario, you can go over to the Scenarios tab and choose the New button. You can give the scenario a different name to differentiate it, a description, and hit Create. To clarify the difference here between duplicating a scenario versus creating a new one, creating a new scenario will use your originally imported data, the scheduling data that was imported at the time the playground was created, which means you will also be able to choose a new schedule from date.
So this is great if you want to plan for scenarios with different start dates. Duplicating a scenario will duplicate the data in a scenario you've already been refining. So any constraints or priorities that you set will get copied over. And whatever schedule from date you set originally will also be maintained. I'm going to start fresh with a new scenario so that you can see it better comparison between the two scenarios since we've already made a few edits on our initial scenario.
Now, before we compare these two scenarios, I want you to notice that each scenario has a version number. When you duplicate a scenario or create a new scenario, this is version 1 of that particular scenario. So you can see with the new scenario I just created, it's a V1. When you select Generate, the scenario will version up. So your scenarios start on V1, and every time you hit Generate, you're creating a new version of that scenario.
So the version number is really just a marker of how many times you've hit Generate on the particular scenario. We've hit the Generate button twice on this first scenario, so it's V3. The icon to the left of each scenario will indicate if the latest changes to the scenario have been generated or not. A green icon means the latest edits have been generated. If I go ahead and make an edit on this new scenario, the orange icon means that the scenario has been edited, but that the latest edits have not been generated.
OK, so let's go back to comparing scenarios. We've got two scenarios in this playground. And you can easily switch between them to compare the schedules and see how the dates and resource utilization stack up over time based on the various constraints and priorities you've set. The easiest way to visualize the comparison is actually from the Resources tab. The Resources tab shows us resource utilization over time.
The resources overview graph is displayed at the top of the Resources tab and is a visual representation of your resourcing needs over time. You can choose to display the overview graph as stacked stream or list, and it can be styled to be smooth, linear, or stepped, whatever your preference is. Right now, beneath the overview graph, you can see the resource table. The table displays information about each resource class, including total resources, total tasks, and the planned start and finish for that resource class.
Which fields are displayed can be toggled on and off from the Column Display Menu. With a Resource class selected from the overview graph or from the resource table, all of the resource class details will appear. So for example, here, I selected Animation. Now, I can see details about the resource utilization for animation. To the left, the detail graph displays resource utilization over time. Planned usage and ideal usage are both visible.
Ideal usage is the theoretical ideal utilization, while planned usage is the actual utilization of a particular resource class. So it might be ideal to have a static number of artists over the course of a project. And Flow Generative Scheduling will attempt to achieve the ideal usage for a resource class. But this is not always possible to do while respecting the constraints that have been specified for the schedule.
While the ideal utilization of a resource class might be a static number, reality will usually differ and there will be variations in the planned usage of a resource class over the course of a schedule. As an example, maybe your ideal usage is to have 10 animators working on a project for the week, but the reality of the schedule dictates that planned usage would be five people on Monday, eight people on Tuesday, and 10 people on Wednesday, just due to when the upstream dependencies will actually be ready for animators to start on tasks.
So all that to say that you can choose on your graphs if you want to display the ideal or planned usage. Beneath the detail graph, you can see information about the selected resource class, so in this case, animation, including the total tasks and duration, the effort days based on an eight-hour work day, planned max and ideal max resources, and the max deviation, average deviation from the ideal.
Now, to the right in the Detail panel, you can edit and view more information about activities that are a part of the resource class on display. And I'm going to get into this more in the next section. Before I do that, remember that we created two scenarios. The cool thing with the overview graph is that you can more easily visualize the differences in resource utilization over time between different scenarios than you can from the Gantt chart.
In the Schedule tab, you're looking at the schedule of individual activities, while in the Resources tab, you're looking at the resource usage across the entire timeline of the project. So let's go ahead and look at these two scenarios. And you can see the differences in resource utilization between them. In the baseline scenario, I can see a project end at the end of March and a relatively level utilization of resources across that time.
In the second scenario, which we haven't generated yet, an as-soon-as-possible version of the schedule is created, which has the project ending mid-December, with a big spike in resources at the beginning of the project. So we can see this quickly just by flipping between these two scenarios. So we talked about using constraints and priorities to iterate on your schedule and working across different scenarios. So now, I want to look at the other way you can refine your schedule, which is through resource shaping.
Now, all resources in Flow Generative Scheduling can be shaped. For each resource class, resource shaping allows you to adjust start and end dates, add minimum resources, add easing in and out of resources, and set the total capacity. To shape your resources, you will work with the detailed graph and the Edit tab underneath the overview. Right off the bat, I see a big problem. Remember that this project contains over 5,000 tasks that need to be completed, and I know this project is, for my team at least, about a year's worth of work.
But when this schedule was generated, I set a finish-no-later-than constraint of March 30. To complete this project by the end of March, several hundred resources have been allocated. And since I know I have a small team, this schedule is just not going to work for me. So before resource shaping, you can set constraints on your project to make sure the timeline makes sense. You can go to the Schedule tab and edit the finish-no-later-than constraint we set earlier, and choose a date in the future.
So I'll choose November 1, giving a year for this project, which, if you remember, was my real due date to begin with. And now, I'll select Generate. When I jump back over to the Resources tab, I can see my resource utilization is much lower and spread out over a much longer period of time. This is better for me. Now, I can start shaping my resources. All right, so what if I have an entire department that I know will need to start late?
Let's say you're working on a film, and it's your compositing team that won't be able to start until a certain date. Here, you can go select your resource class, so I'll choose compositing. Now, you can change the earliest start date to when that team will be available. My project starts November 1, and I won't have any compositing resources until January 1. So to set this up under the Edit tab, I'll change the earliest start date from November 5 to January 1.
Now, you might notice that there's a lot of grayed out dates, including the date that I need. Earlier, I set up a finish-no-later-than constraint on the ATH sequence. If I go over to the Schedule tab, you can see the constraint is set to December 27. So going back to our earliest start date, what the gray shows is that based on the constraints that have been set on this project, the compositing team can't start any later than December 19 if we're going to hit that December 27 deadline.
Shaping happens within the confines of the constraints that have been set. If I go back to the Schedule tab, I remove the constraint on the sequence and go back to edit the date, the limitation is gone. And now, I can choose January 1. Scheduling is always a give and take between deadlines and resource availability. If that constraint I set isn't realistic or even a real deadline, I can remove it. If it is a real deadline, then Generative Scheduling will help me to avoid making impossible scenarios where those deadlines can't be met.
So how else can I shape my resources? You can choose to set a minimum number of resources for a resource class. For example, let's check out the layout team. I may want to maintain a minimum number of one layout artist, so I have one person on my team at all times. In this case, I can put one under Minimum Resources. We can also quite literally shape our resources using the Ease In-Out toggle to turn on the gradual increase and decrease of resources.
You can drag the peak start and finish around and see how the easing in and out is reflected. When you hit Generate, you'll see that Generative Scheduling is going to try to match the resource utilization you've shaped. In this case, we're talking 1 to 2 resources, so we're not seeing a huge difference. But of course, with a larger team, this visual will be more noticeable if your team has a maximum number of people, you can also enter a number in the Capacity field to indicate the max number of resources.
Now, Flow Generative Scheduling will do its best to work with that number. However, it will prioritize the constraints that have been set. If you have one month to complete this project, but you have three months worth of work to do, and you have a capacity of one person, something's got to give. But by applying capacity, you can see visually that, hey, maybe you need to look at hiring or finding more resources within your company or even changing some of your project start or end dates.
Here, I'll set a capacity limit of two layout artists and move around the points of my peak usage to see how I can optimize my resource utilization. You can generate the schedule throughout this process to see how utilization changes. This department really only needs two people anyways. Let's try setting capacity limits with another resource class. So here, I've selected the lighting department, and I'll do the same thing. I'll set a capacity limit of 8 and hit Generate.
And now, I can see the resource class. Let's see what it does. So it never really goes above that number except at the very end of the project. Just like with the earliest start date, if the resource utilization was going above the capacity number, this would have to do with constraints that you've already set. So if your project has certain deadlines, but you try to limit the capacity of a resource to less than what's needed to achieve that deadline, the constraints will override the capacity limitation for those periods of the project where both just aren't possible.
So it's really that simple. You can generate a schedule as many times as you need. Each time, the schedule will vary slightly. And when you're happy with it, you can send it back to Flow Production Tracking and apply the dates. All right. So we've looked at the round-trip process from Flow Production Tracking. We've looked at using constraints and priorities, setting up scheduling scenarios, and resource shaping.
Now, the example we've been running through is a brand new project that had a bunch of tasks that I was free to schedule in whatever way I wanted. What would you do if you have a project in progress that you need to update? Let's go ahead and create a playground for a project that's already in progress, started last month, and has a few more months of work still to be done. First, I'll go to my home page and select Create New Playground.
I'll choose to use scheduled data from Flow Production Tracking. I'll choose my project. In this case, it's Lowlands. And I'll hit Next. I'll give the playground a name and description. Now, I'll set the schedule from date, and I'll select Keep Assign Dates for Tasks that Begin Before my New Date. So this means that anything that was already completed or any tasks that were started but not yet finished, they won't be rescheduled.
It's just everything that hasn't started yet or anything without dates that will be scheduled. This project started mid-August, but we need to take a hiatus for reshoots that are happening. We're not sure yet how many shots will be impacted, so we're going to go ahead and pause any work that hasn't been started yet. So the schedule from date will be November 1, which is about when I think my client will be ready to start work again.
Now, I can go ahead and add constraints and priorities. So I'm going to select the project, add a finish-no-later-than constraint of December 20. I know once the client is ready to start this project, I need to get it done quickly. I know the FLC sequence is priority for the client, so I'll set a start-as-soon-as-possible constraint on the entire sequence. FLC-10 is a priority shot within that sequence. That will be a key shot that will impact the work done in the surrounding shots, so I'm going to give it a priority of 100.
I've generated the schedule. And now, I can look at my resource utilization in the Resources tab. I'm going to flip through each of my resources and ease resources in and out and shift the peaks of resource utilization a little. You'll see as I work that the original dates are maintained. Locked activities happen when a schedule is imported with activities that start in the past. Any activities that are done will be locked and won't be editable.
They'll display, as you can see on the left hand of the screen here, with diagonal lines, which will show in the Gantt chart and in the overview graphs. When you're happy with the schedule, you can send it back to Flow Production Tracking. So I'm going to go ahead, send to Flow Production Tracking, Send Scenario. Give it a few seconds to complete. Now, when you open Flow Production Tracking, you'll see the new dates in the proposed start date field.
But for the tasks that were already completed, you'll see that the dates are the same, that there's no change, which is what we asked Generative Scheduling to do. Now, we can apply the new proposed start dates and the schedule will get updated. But again, everything that has start dates in the past or had end dates in the past will be respected. Before I finish, I wanted to bring up the generative part of Flow Generative Scheduling.
And more specifically, I wanted to talk about how this tool uses your data. Flow Generative Scheduling creates a unique Artificial Intelligence, or AI, model for each run of the solver, i.e. for each click of the Generate button. The model is derived only from the data set that is imported and does not utilize any models trained on or derived from any data from other users or third parties. Similarly, any data that's imported into Flow Generative Scheduling is not used in the training of any other AI models.
You don't need to worry about your personal data or schedules being used in training or worry about the quality of the training material of the AI used because it doesn't use any. As for how it actually works, that is a topic for another presentation and definitely a more technical one for which I'm not qualified to begin explaining. So I won't get into that today. So to conclude this presentation, project plans are always changing.
We need a way to adapt our schedules when changes need to happen, which they will. With Flow Generative Scheduling, you can quickly generate level schedules using the task information from your Flow Production Tracking site, create different scenarios to plan for project changes, and prepare for hypotheticals, apply constraints and priorities to your schedule to ensure that what matters the most to you happens first, and use resource shaping to balance resourcing across your different scenarios to avoid peaks and valleys in your resource utilization.
I hope this class has been able to give you some insight on what Flow Generative Scheduling can do to help you quickly generate and iterate on your project schedules and manage the ever-changing reality of the schedule changing again. Thank you.