00:00:02:23 – 00:00:31:29
Oh, darn, I wanted to show you how to build a multi facility model out of separate individual facility models. You should just watch this video. After seeing the overview video and being comfortable with the single facility model. Otherwise, this is going to be a little confusing. So the first step because in the single facility model I had a non zero day baseline.
00:00:31:31 – 00:00:58:04
In other words I’m restarting the day at something other than midnight. I do need to set that up in here before I build my multi facility model. Now the utility I’m using as often comes up. Some of the verbiage is a little bit confusing or misleading. But this multi line model mapping import. Think of this as a multi project build tool.
00:00:58:08 – 00:01:23:41
So I am going to do a set up of five facilities. Again the line numbers do not really apply to you. However we need some of the functionality that goes along with it. So if you just think of the line numbers as equivalent to individual facility builds, that’ll be about right. So go ahead and hit apply.
00:01:23:41 – 00:01:47:28
That will generate my different rows. And actually before I do that I’m just going to act as if I have a stagger where one starts each month. You probably have a sense of what sort of stagger you would want to use. It is worth noting once these are set up in Aurora, you can change the stagger later on.
00:01:47:29 – 00:02:19:10
So this is not absolutely critical to get correct at this point. Now in this particular case I’m going to do the same. Schedule five times. So it’s going to be the schedule I went over in the sample model video. I’m going to do that process five times. If you had a couple different processes you were going to do, maybe you had three different variants.
00:02:19:14 – 00:02:49:06
You could do something like this and tagged each variant. And then you could define different source models. But in this case they’re all going to be the same variant. So if you do change the variance, just be sure to hit refresh rows so that it knows what novels to prompt you for. And then what you will do is for each, sort each flavor, you’re going to define a model for it to use.
00:02:49:10 – 00:03:19:30
And think of it as basically loading a copy of that model for each of these rows. Here. So I am going to do this guy okay. And once you’ve selected that go ahead and say build composite model. It’s just double checking. It knows that you will change the day baseline. So it detected that as an edit.
00:03:19:31 – 00:03:58:11
It just wants it basically wants to make sure that you know what you’re doing and you do. So that’s great. Usually I go ahead and go to view edit composite and I’ll save a copy. Mostly that is because you would probably be saving soon anyway. And this way if anything goes wrong, you haven’t lost work. So in this case, it is worth noting that because the basis version of Aurora you’re using doesn’t use really use flow types.
00:03:58:11 – 00:04:32:01
That’s why I got the nine days showing up multiple times. That won’t hurt anything. But if it bugs you, we can potentially change that. The key thing is that we have this showing five times, and you can potentially change them independently now that they are in the system, that they are going to interact in certain ways. But if, for example, I change activities or press events or some such in one, it will not directly affect the others.
00:04:32:05 – 00:04:39:05
So I’m going to go ahead and schedule.
00:04:39:09 – 00:05:08:35
And I’m going to show you a couple different views. So first, you may recall when I was going over the first model, I went on and on about the plane specific setting. This is where you will see the impact of the plane specific setting. So in the singleton model we were looking at before, the space zone it would call out was V1 or V2.
00:05:08:39 – 00:05:41:17
Now you can see V1 is not used. That is because it is making a per project variant for each of the projects. So this is the one for number one. This is the one for number two. This is the one for number three. So because it knows that each facility has its own set of zones, it basically auto generates a copy of the zones for use by each project.
00:05:41:21 – 00:06:03:03
And so that what that basically means is from a zone point of view, each of the projects is completely independent. They’re not going to interact with each other. On the flip side, if I come and make a histogram plot of my different labor.
00:06:03:07 – 00:06:29:32
These are not considered project specific. And so these are shared across the different projects. So what that means is if I’m going to just try to make it so that you can see what’s going on with that. So, what I’m going to do is come in and use that auto coloration that I was showing you in the first video.
00:06:29:36 – 00:06:50:14
And I am going to actually do them by flow. So this is doing it by project. So each project is going to have its own color. That was goofy. Let me try that again. I think that I missed something.
00:06:50:18 – 00:07:25:00
Okay. So I’m going to come in and do it by flow. One group per value. Okay. There we go. And hit okay. Okay. And so now I can see the way they actually interleave. And the labor availability will actually be driving especially the later projects. So in so far as you can see that on the zone view, the rhythm is a little different from from one, project to the next.
00:07:25:04 – 00:07:53:44
That is going to be because of the labor interactions, because the labor is the primary way the different projects are interacting right now. Okay. So other things I’ll just show you right quick. I mentioned that you could go ahead and change the offset after the fact, basically where I entered those dates that populate the early start date of each project so I can come in later and change it.
00:07:53:45 – 00:08:20:20
Maybe I want to change it to a six week gap, or maybe I want to just manually tweak each one. So it’s just perfect. I can do that. The other thing, because the user attributes actually are reflecting some of my layers and some of my layers are probably different between the projects. I may want to update some of those.
00:08:20:24 – 00:08:52:15
So what I would normally suggest doing is, is you can either do slow if you basically have if each of your individual builds has one project, then you have a 1 to 1 relationship between the data source and the project in the flow. If you wind up with an individual model having multiple projects, you have to get a little fancier because then you will have to look at a secondary property.
00:08:52:19 – 00:09:24:26
For now, I’m going to assume that you will just have one flow for each of your individual facility schedules. And so what that means is then you can basically sort by flow and update one at a time. So I’m going to assume that probably these fine grained ones, commodity and commodity build up. Those should be fine. If the facility is a different wings of course you might edit that.
00:09:24:30 – 00:09:57:14
Let’s say that first I’m doing A2A1 alpha one, and then I’m going to do alpha two. So then I would just set alpha two for all of these guys. And this is basically assuming that, the site corresponds with the project, which may or may not actually be true. Now you can see that when I do the copy and paste, it asks me whether to augment or overwrite.
00:09:57:18 – 00:10:24:06
In this particular use case, you would always pick overwrite. The reason it is asking is there are cases where you may have a user attribute that can have multiple values. So it’s not taking that for granted. But anyway, you can come in here and tweak the user attributes so that they actually make sense with your different projects. And at that point you should be good to go.
00:10:24:10 – 00:10:27:24
I hope this has been helpful. Thank you so much.