IntelliPlan

2017-07-11

Video Text

00:00 Good afternoon everyone. Welcome to our webinar today. We'll be looking at, uh, the blue streak until a plan, features and functionality. I believe Todd Wenzel will be our speaker today. And please feel free to raise your hand during the presentation for questions as well as after the presentation as well. We'll have some more time. So todd, please take it away.

00:26 Let me switch over here.

00:28 Yeah,

00:34 OK. Should be able to see that now so we can just get into this presentation. So we're going to go through today. Pretty simple. Um, I'm not sure how much time we'll spend on this, so we'll see. I haven't timed it. So basically what it is and a plan I'm part of that. I'm going to talk about embedded processes and specifications and something called process rules and show you some examples on now one of our sites and then a final questions. If anybody has anything, we'll skip the first plan. So I'll give you the marketing spiel here. So it's a way of a building sophisticated processes on a new work order basically on the fly, and then you can take that process that was built for that work order and put it on a customer part and make that a sort of official part process.

01:36 And um, so it's, um, it utilizes, I'm specification library, um, but it's not a best way to do was have advanced specification library and then until the plan sort of an add on to it. And um, this was originally designed to handle pleading requirements, uh, which can be kind of, um, um, particular and different types of platings specifications. You're going to do one thing and then you've got to do these three other things first. And so that's where it was originally designed by the. It's generic, exactly. So it can work for just about any industry. I'll show an example here. I asked one of our blue streak users, um, who was instrumental in defining this, how they utilized it. Now this is just, you know, very kind of high level and um, if you've got any, uh, you know, you want to see this stuff and talk about in more detail, then just contact us and we'll go through and talk about it some more.

02:47 Um, but basically, um, this particular a company they do played in his, but that's not the only thing they do. They do a lot of aerospace work. Um, they do, um, uh, testing, um, a dye penetrant, um, exams, they'll do different types of coatings. They've got basically they've got a half a dozen what I would consider commercial shops as departments. So a router or a work order for them can be pretty complicated because it's one work order that flows through all these different departments and each of those departments can have their own process of what they're doing. So, um, when they do it, here's an example, it's just very simple. Know they would have, um, an operation for receiving parts and they would insert some type of, uh, in this example, some type of a chemical, a conversion coating process. And then they might move somewhere else. And then there's a painting process going on and then, uh, there's a, a packaging operation.

03:59 So I'll show you in tell plan where you kind of, you kind of build this process like just like this through a series of individual operations steps and embedded processes. And I'll talk a little bit more involvement. Been at processes. Uh, so here's an example here of this particular cadmium plating and the way they set it up is that they've got this base, sort of a process name and they've got nine different variations for the Acadiana planning based on the type one, type two, type three and then the three different classes. And to be able to pick the correct process or embedded process, they utilize specifications and um, what you may not have seen before, which are process rules. And those are like kind of target, um, specific customers and parts and attributes of apart to be able to kind of filter down the list of all the possible processes you have to the, to the one or the couple that make sense based on the departure entering. So, um, I won't show this example. I'm going to show a very, very generic, so you should be able to extrapolate this into, uh, into your process.

05:26 So embedded processes, um, they're really, it's, it's just a process within a process and um, if you remember, everybody knows that a process is made up of operation steps, so it's nothing more than just a, it could be a little process, that many process or a big process, but you insert that in as I'll show you as an operation step within the process. So this gives you the ability to manage common processes in a single spot. So if you've got a, maybe it's a, um, a contract review process that might have several operations steps and maybe it's the same thing. You do the same thing on every work order and then you decide that, you know, we need to modify this contract review process that we do and we want to add a couple more steps into where rearrange things. Then if you have that set up as an embedded process and you modify that embedded process, it's basically automatically updated, um, in any process that uses it.

06:33 And, uh, it doesn't really go in and update all those, it's just that the embedded processes, a single reference and these other processes. So, um, I'll show you how that kind of expands out of any process can be used as an embedded process. So there's no limitation of processes. The process, realistically a, we've limited tid, um, this, uh, this embedding the process within process, the two levels now we could easily take it on sort of forever. You're going to have a process in the process and a process and a process and the process. But realistically, um, you know, our brains overload at that point. So we said really two levels probably makes the most sense, so I can have a process with a, with a embedded process in it. So that is what we referred to as a first level embedded process. That embedded process could have another embedded process or a series of embedded processes. But that's as far down as we want to take it because anything beyond that is just, it's too hard for people to manage that and keep it straight. So this has given everyone who's uses has plenty of flexibility and for these embedded processes there is no special re licensing required. So it's just, it's just built into a process. Um, I don't know how many people have been using this. Some people use it quite extensively and other people really don't have a need for it.

08:08 So specifications in process rules. I'm not going to dive into specifications. We have other webinars that talk about that. Um, so you can, uh, we've got, uh, the, our, our channel. Um, if you go to in blue streak, um, there is a, uh, webinars and training, I believe it is link you should see at the top of all your pages and you can click on that and there should be, um, one of the things in there that's just a way for us to show you what all the different webinars and training opportunities that are coming up. And part of that should be a listing to A. Actually, it's actually a go to webinar channel that we have set up. So all of these webinars were, and you can see them there. So you can go there and look for, um, advanced specification library, so you want to drill a little deeper on that.

09:02 Um, and so the specifications are really used for documenting a industry or prime or internal specifications, ah, and for really qualifying equipment, personnel vendors, um, that's sort of the high level use of specifications and um, you can also use it for a documenting operating procedures and all that stuff. But we've got, we've got blue docs now that take care of a lot of that stuff. And um, the um, functionality I'm showing you here, um, is really the most powerful when you use it, when it's used with production pathway. So when you're setting up these processes and specifications in particular are really useful in production pathway because that's where you can qualify people and equipment.

09:59 So process rules might be something, a new idea at this point and it's really functionality that's available with our licensing plan now until applying the short for intelligent planning. And I'm in a nutshell, it's really used to define these process rules are used to define exclusionary or exclusionary rules that you can use for either promote a process, um, or hide it from being selected, uh, within, uh, the specific user interface that we call the plan process builder. And these rules are primarily based on part attributes, um, but it's also based on the customer. So you can see these right now, these are all the attributes, um, that we, you can set up as a rule on any given process and you can have multiple roles on a process. It can be based on the customer, it could be based in part number, part type and alloy ela class alloy type received condition, prime received hardness min and Max settings and received surface finish. So this is the list of attributes we can test for in the [inaudible] plan process builder. This is easily expand if people need some other information, uh, to be able to have the person who's doing the order entry or building or selecting a process or an embedded, you know, building the process on the work quarter if they need some other information to define and kind of hone in on the right on the process that they should be picking up, easily expanded.

11:51 So let's just get into some demos here. I bring up my other page. OK, so I'm just going to go over to set up and processes and already have some processes a selected here. At first I just want to kind of take a look at, uh, an embedded process and I'll take a look at, um,

12:17 well this one first. So take a look at this, you know, see my generic names here. So I'm embedded to process embedded too. If I look at the operation steps that are, part of it is just too individual operation steps. That's all that's in there. You could have one operation step if you want. Um, so it was just a process. I know the naming doesn't, is that important, uh, other than for some human to be able to understand that this is something that we usually use as an embedded process, but that really doesn't matter. It's just the process. The next one here, the embedded process one has, would, looks like for operation steps. So we can see this one here is just an operation step, but the second step here is really an embedded process and it's the embedded process to put in here. Now you can see that there's a lot of things that go away.

13:19 So if it's an embedded process, it tells you here you can't, you can't modify it all here. You're just saying at operation step two when this process. So if I select embedded process one and I put that on a work quarter, I would see this operation step show up and then the, um, two or three operations steps that are part of embedded process to would, would show up starting at step two and then they would be followed by these other two steps. I'll show you what that looks like in an actual work order. Um, so this is kind of far down as you probably want to go with embedded processes. So I have a process that I use that I am bed that has another one in it. I could have multiple embedded processes in here, doesn't matter. And then, uh, we'll just take a look at process one here and we can see I'm going to get very generic things here. So I've got two operations steps than I have embedded [inaudible] process inserted here. And then when embedded one gets filled out inside, one of its operation steps is that we just saw was, was this other embedded operation, a process too, and it'll get expanded out as well. And then we, uh, end with this, uh, other, um, operation step here.

14:45 So let's take a look at these rules. So we can see right here, we've got rules for process one, there's two of them here and we'll take a look and see what that says. Set up here for two different customers. Now there's a lot of um, all those attributes that I mentioned are, I'm showing here, so, you know, pick the cost. So if I want to make this customer specific, I'll pick the customer. So this is kind of like, um, if a corrective action preventive actions where you have, uh, the, um, sort of target items, um, if, if you, um, and also like in quoting for pricing if you want, if you care about some attributes, you have to define it. If I don't, you don't care about it, don't define them. So here I'm saying I'm being fairly specific that for customer Portland tool, um, if the park cut type comes in machine, now you know, if I have a [inaudible] doesn't make sense, just bear with me, but I just picked some stuff here. So if it comes in a machine, all these drop-downs, you can control a list in there. So you, you do that in the alloys. [inaudible] and received condition is finished and the prime, uh, it happens to be bowing. I want this particular process too to be emphasized for the order entry person, um, when they're in order for a part that has these attributes

16:32 for this one here, for acne metals, it's similar but different. So we have acme metals when we say at the park comes in machine and it's a two.

16:44 I have this set as an exclusion rule, which means if it's acme mantles parts ice machine and the alloy is a [inaudible] I do not want this process to be something that an operator can select so you can exclude these processes or process from showing up in the list. This is, and I'm only talking about the Intel or plan, um, drop-down list of processes and I'll show you where that, where that shows up. So that's exclusion. You can mix and match these. You can have a in inclusions and excluded, um, um, rules here as many rules as you want on a process, but you got to keep it so that you can, uh, you know, system doesn't have a problem with it, but you know, people might have a problem, um, you know, managing a hundred and 50 rules on this process. So what that looks like and the specifications. Anybody using specifications already knows what that Kinda looks like. But I've got to specs here. I just have, again, merchant generic stuff, internal spec one internal SPEC to. So what I'm doing is I'm so setting this process with these two particular specifications and that can use that as a mechanism to filter down this process or combination of specifications if I want to do that and rules allow us to filter down the list of possible processes that the order entry person can pick from.

18:20 So let's go and just enter an order here. I'm going to do this report plan. We've got a couple other things who don't care about right now. So I will say, well I had a hundred and 50 of these parts coming in. Um,

18:42 OK,

18:47 so we'll call it some new part.

18:55 Yeah,

18:55 it's a widget. And now this is um, this is sort of a, I always refer to this as sort of backward planning, um, and some industries just kind of flow better this way when we first originally designed blue streak. If you're going to do something for a customer part of very specific process, then you would set up that customer part. You had set up the process for it. And um, and then when that part came in and they just pick it from the part down here and then all of that information, all that planning and all that just gets put on the work order control plan, quality characteristics, all that stuff.

19:41 But this is where you can pick apart, that's not a customer part. And um, and even if it is a customer for you can still, you can pick an existing one, but quite often this is done for parts that aren't set up yet and so they're kind of set up as the work order has been entered and as the work order is being processed through multiple departments and each of those departments can have a different process. You can use this mechanism of Intel plan to kind of plan the first part of the work order. And then when it gets to a point where OK, we're going into a coding department, but we don't really know exactly the process to put on it, the supervisor or the manager is going to do that over in that department. Then we get to that point. That person can go and say, OK, and then Nicky's tell a plan to figure out the process they want to put on there and kind of finish out the work order.

20:37 So you can do that in multiple departments. So I, this is not a part number that exists the park type I want to kind of match up, um, those requirements. So we put in on the rules for one of these and the prime is going to be following and the alloy is going to be an a to so this map up, not normally, if I had picked a customer part, usually the process would've been associated with it already. There's no process here. Um, this is the builder. So we have Intel plan licensing. You'll have this little button and that gets you into the [inaudible] plan. Your why. And so what this is, it doesn't, uh, the simplicity here Kinda doesn't really reveal the complexity behind it, but if I just click on the process. So, so what I'm gonna do is I'm going to build what this is going to do.

21:30 I'm going to build a process based on operation steps and other processes. So maybe I want to start out here with, um, I'm just going to do a contract approval and I add it. So here's my operation step and it's going to be starting on a sequence one. The next thing I want to do, um, is at a process. Now when I click on here, right away, this is a little slightly different process. A viewer, you can see there's a ranking here and um, and some details of the ranking. So based on the attributes of the part in that rapid edd order screen, it looked at processes that had rules if a process didn't have a rule like this one and these other ones, um, but it seems to match, um, because it wasn't being excluded or wasn't being promoted here with a higher rank, it's going to show up here with a zero.

22:37 So zero rank as a, you find rules that, um, match up with, uh, the, um, part information on this order that I'm trying to build right now. It'll give you a ranking and it's just a simple ranking by how many of those part attributes matched up on it so we can see here we've got a process and a process to the higher, so the idea here is that the highest ranking one goes at the top of the list, meaning this is the most likely process that you want to do and you can see it's got a five because it had matched up on customer type alloy received condition, and the prime, this one only has ranking it to it only matched on customer an alloy. So these two particular processes have some rules in it. Make sense? Now if I do say start filtering this down, then I'm going to get down to things that just have process and the name.

23:37 So I've got a short list. So as he typed that stuff, it's still makes it shorter and shorter and shorter, but you can see the ranking of these things promotes the operative picking a higher, you know, picking something with a higher rank. Now you can do that just like that. That's just using process rules, but you can also use um, specifications or a combination of specifications and process roles. So if I go to specifications here and I say, ah, this is an internal spec one, uh, now when I click here, I only get, I haven't typed in anything yet, uh, to limit the search. I don't. There's only two possible ones that match. So there are only two processes that, that match up that have this particular specification specification connected to it. And you can see that these have high rankings because they, they match a lot of data that's on the work order for the part, you know, that we're entering right now.

24:44 So that's really how that works. Now if I want to say I'm going to take a process one, I just select it and say we add it and then maybe I can come down here and we're going to do a shipping operations can make this very simple ad that. So there it is. I'm Kinda like on a work order if you want to adjust these around, I can move them around, but I don't want to ship them before I process themselves and put it back there. So this tells you this is an operation is an operation. This is a process in here. So it looks like we only have three operations steps, we really have a lot more than that. So that's really how this process building works. Now I can show some other things showing up here. Let me just clear this out and I can show you what happens.

25:33 So I'm just looking at process rules right now. We can see that um, process one is a, is a high ranking bliss. Go and change that rule on process one here. Instead of making that in what I refer to as in inclusionary rule, I'm going to make an uh, uh, an exclusionary rule. So I'm saying when, when all this stuff matches up, I don't want to see this process. This process should not be selectable, um, by the person doing order entry. So we'll do that. And with a little luck, I clear this out. You can see that process, one is gone now from this list and the highest ranking will now is process too. So that's how that works is really pretty simple. Once you, once you see that, I'll make that included again, come back here and there. It's back in our list to pick from.

26:34 So that's basically how that works. You know, the idea is kind of simple of what's going on here. Uh, you have to think about it though, how you want to. Do you want to control this? Um, but that's, that's what we have. So let's just make this a um, I'm gonna accept this process and it was down here. It says the process builder. So we don't have a prop. We didn't put a single process on this work order. We have a process builder from plan. So that's just telling us, you know, making sure we don't pick another process that um, we're using the process builder right now and if that's good enough, I'm just going to hit continue.

27:17 And here's the workload was generated. Now you notice there's a lot more operations in the three that I had selected and we've got some icons showing here. Now, when you see one of these chevrons are triangles that tells you it's an embedded process, a single one means this is the first, uh, first level embedded process and a double means it's a second level embedded process. Um, it also tells you some information. You know, what this embedded process was. You can see this is from process one rep zero. In fact, even even these with a double say, it's from process one rep zero. So all of these came from process. One, Miss I know is going to be an embedded process within process one, but we're just showing you sort of the top level process and there are some changes in the July release. Um, that'll make some, some changes here and make it look a little different.

28:17 But as functionality is all the same. So you can see we've got all of our [inaudible] operations. So really what happened is that we took those three steps, the second one being an embedded process and we kind of blew them all out into their individual operations steps and that, and this, um, process one had an embedded process, uh, another one in that actually had to have an embedded process one which had another embedded process within that. So you can do a couple of things here. You can, will minus the UI is going to change a little bit here in July release. But uh, this functionality is still the same. You can kind of what we usually refer to as dehydrate this process down to it's, um, it's a, it's sort of simplest form of operation steps and embedded process, first level embedded processes. And the July release, uh, will show first and second you can, you can expand it or do you hydrate it down here or traded down to the second level embedded process if you want to view it that way.

29:26 But this is a simple way to view it. And then you can expand it back out again to, it's all of its operations steps, they can go to the plan. So if you need to adjust something you come back to here which looks familiar now and if I wanted to move around or add another step in here or at another embedded process, um, you can just work with it through this particular process builder again. So this is helpful as I mentioned, if you've got the complexity in your shop or you've got different departments and each of those departments really have their own process that they need to do to the parts and, but you want to have one work order that kind of moves the parts through these different departments and each of those departments can basically define their own process that they're going to do plans the way to go for, for building that stuff, in managing that.

30:27 And if we look at it, we just do a quick print. I mean, this is just going to show our default work order here. Tracking. You can see with all these different operations steps in that they're all just shown. Um, we've got a lot of control here, a particular customer that, um, I showed you some of that calcium, um, played in information as they move around to different departments. They want to have basically a work order that's um, or a section of the work order that's just for them. So this is just a report, so we can, we can do that kind of stuff. Um, you can generate sort of a work order for every department that just shows they're processing information they needed to or it can be all one work order with multiple pages. Every time you get a new you come into a new, um, embedded process for his level embedded process, then you know, they, they can, uh, you just do kind of a page, page break and then give them a new, give them, you know, that departments, sort of their own router. I'm going to pages three through six is what they're using. So it's a lot of flexibility. Whatever you need to do there can usually be done.

31:48 And if you have any questions just raise your hand. Um, so the other thing I want to do is we go through, we build this thing, um, this work order sort of on the fly. We've got a control plan, characteristics we set up, we went to various specifications and then you want to say, OK, we've got this, you've, you've, it looks good or maybe you actually process all these parts. You like it, you want to save that part now as in all of this information as a real customer part. So the next time it comes in they can just pick the part and go, they don't have to go through a builder to build a process for it. And really it come over to the parts page. Um, this is not a customer part right now. So it's sort of a two step. If it's not a customer part of the two step, it's already an existing customer part. It's a one step to do this. But, uh, what I have to do is go into the editor and I can say, you know, all this information that we set up, um, for this part, I'm part time prime, receive commission on that kind of stuff and I'm going to say create a customer part

33:01 so it'll just verify that for you all that information, if you want to make any changes to it, you can and you click the insert and it's going to basically save that as a official customer part for that customer. And then it will update this. And now you can see we have a link here. It's my gray part number, some new part. Um, it's got a link here so you can go right into that customer part. So you know, it's official customer part at this point and now there's a new option here. Update part process. So if you want to save everything to this work order, all of its operations steps, all the specifications, I'm all this control plan characteristics. This is what you do and it's just Warren's or your boss or creating a new process for this customer part. And here's my name and description of it and I Click OK, I'm not going to do this right now, but it, so it would produce a new process.

34:00 The naming convention of that process. Uh, it's, it's, uh, in code right now. Um, I can't remember exactly how it was, but we can change that for you. So if you've got a specific naming convention, this might, I think this might take a, might be customer, May, customer number, first part number and maybe that's it, but if you've got some other way naming convention you always want to use here, we can easily change that for you. So that's what to do. So it would create a process connected to this part, this customer part, and will produce a control plan characteristic and our control plan and connect it to that part also. So that's all tied up the control plan. It's got a specific naming convention that's going to match the process naming convention. And so it all should tie together nicely for you. So that's, you know, that's the ability that you have to do this kind of stuff.

35:05 Now if I had started out with an existing part and say we are had this part where you already had a process on it and we put and we selected it and that process was put on this work order, maybe we made some changes to it on the worst quarter because of changes. Um, maybe, maybe it's a new revision of the part or some information you needed a tweak this work order or documentation on it. You can change it on the work order. Then you can come back to that part and say I want an update the part process. So instead of building a brand new one and hooking up, but I'll do this effectively. It'll delete the process that's there or I'm maybe wrong. I think it might leave it there and make a new revision of it and connect that new revision a two. But I have to, I spent a while since I worked on that, but it might just get rid of that old process if it's just connected with this part and build a new one with a new revision to it.

36:08 Um, so you can update it sort of on the back end, update these processes. Normally you would go, if you want to make a change to what you saw this process on work order, you can make some tweaks to it, you would probably go back to the original process and make the change there, maybe bring that process back on the work order or make the change on network quarter. Also, lawsuits take a work order and a change, uh, you know, processing information right from the work order for a given part. So I think that's all I really wanted her to get into here. So let's see. Yeah, so any questions I was raised your hand or type in something and if you have any questions, um, you don't have anything for me, formulated it now you can always just send in a help request and um, we can do it. That way I can get back to you on it so it doesn't look like anything right now. So I'm going to pass it back to gene here.

37:21 Yeah.

37:24 OK, let's see. Let's wrap it up with just a few announcements. Our next webinar will be August 15th and it will be the q three release, so you'll learn about new features and functionality within blue streak and there still is time to register for the class pricing within blue streak registration date is July 18th in the actual class is July 25th. So if you have any questions, give me a call or you can register on our website under the a blue streak university tab. So this concludes our presentation for the day. Thank you all for joining us and we'll see you next month. Bye.