Importing SKM Files into EasyPower

Welcome everyone to the EasyPower Tuesday refresher webinar series. My name is Jim Chastain. I'm an applications engineer here at e c Power. And, today, we're talking about a topic that's often discussed and won't think that well disseminated. We're gonna be talking about what I what I call the method to import skm files, and I emphasize emphasize method, because I think you need to be fairly methodical in applying the process because it's not a procedure that one size fits all. So, we'll get into the details of that. Bye, if I don't mention it again, details for that persistanture process recovered fairly well an easy power user's guide, so by all means utilize it where you can or where you have questions. Like to start with a couple poll questions just to get some feedback. No obligation or a liability. But it would appreciate your perspective. And the first one is which tool suites do you have currently own? And this pertains specifically to the topic of importing s k m tools, files, and easy power. So let's give this a couple seconds to mass Looks like we're about fifty percent to a quorum. Alright. Couple more seconds. Okay. Here's how folks have weighed in. Alright. Thank you. Next question is why specifically you're attending today's presentation. Again, this is more subjective, but I would appreciate some feedback. And this, again, it goes to the emphasis on the methodology and need to be a methodical converter because it's a learning curve that's it's only gained by doing the process. So, let's give this another ten seconds. Thank you. Here's how people have responded there. And then, just out of curiosity, I'm I'm curious as to how many people have utilized the new database browser features in e c Power eleven point o. Those of you that have e c power, or at least you keep it updated with the current revision. And the reason for this, you'll see as I get into the presentation, There's a lot of the features that we utilize and the import process are, again, available in the database browser. So, here's how folks have weighed in. Excellent. Okay. Let's get on with the show. Now, it's fairly necessary, but it's important to understand that the CSV file that has to be imported from SKM has to be created in SKM. And in the user's guide, e c par user guide, starting on page six zero one, there's a description of two different procedures to create this export file from s k m. So I'm not gonna be covering that, but I will be covering everything from that point on. So now that Ecitate again to call it a procedure because it's not a single button press, and it's not one size fits all. But what I'm gonna emphasize are the procedures or the capabilities in MEC Power, they give us the ability to resolve issues that occur when we do this imported this file, and these include an error log that's created mapping files that we will describe a little bit, and then waste and improve the error results as you go through this. So once you've saved the import CSV files from the s k m tools, you want to put it into a folder that also has a folder, a subfolder called mapping files. We'll talk about those briefly. But once you create the import or click on the import button, does create the dot d e z file with the same name as the import file. It does create an error log, which you can save or not. Sometimes And which, what we're looking for is a successful import of the data. But most of the time is going to be spent on analyzing the import results, which is a separate report, that we can utilize then to reduce the errors and improve the mapping files. Now, just as a it's a spoiler alert. An easy par, there are some reserved keyboard characters that can't be used or shouldn't be used in the ID name. And so, if you haven't been told this yet, you will get an error created if you use any of these characters in the ID name. Now, why that's important and why that's Germaine is that in the first import, I realized some of these names and the file had commas, and so you'll see what I used as Excel to replace find and replace commas with a dash. And and so we're gonna not even go into that detail, but you'll see what what I'm talking about. So the import results folder or file looks like this, and what it shows is the equipment type the ID name, and then the error that's being generated. And and so the idea is to reduce the number of these errors because these have created a part number in the in the file or in the one line, but it's being underutilized because not all the data was imported. So, the the idea is to look for patterns. So, for instance, in this particular import, we have Repeating pattern here for this set of this breaker, it's all the same part number. This breaker's all the same part number. And, we can see that we're getting the same errors in each location. So, the discussion ends up being whether or not we create a mapping file to handle those errors or whether we do them manually. So part of this process is to go in and look at the data that's actually coming in and see what's causing them to mismatch. And then, going to the dialog box for that individual device, looking at the tabs. In this particular case, we notice a specification tab looks like reasonable source of data looks solid. If we look at the short circuit tab, It's auto calculated, and the part number has been retrieved from the device library, so that's a good sign. But when we go to the phase strip, we see none of that data has been imported. Now, one of the features that's available in EC Power has been for some amount of time is the ability to examine the collected data. So when we open up that folder or that tab, We can actually see the data that came in on the import file from the s k m export. And if we scroll down, we'll notice down here under settings that this is all the information that needs to be entered into our phase trip. So, at that point, we would In fact, in this case, I did it manually, I made the corrections in the database, and chose to reduce the number of errors we had that way. Now, I've referred to the mapping files. This is actually something that deals with the differences and the way SKM references certain elements in the database. And they can be consistent. And in very large files, it's very much I guess easier, if you do a gross mapping examination and specifically for multi k circuit breakers, because they're less complicated than the than the associated low voltage power circuit breakers. So by improving these mapping files, you can correctly identify You can identify the differences. So, let me kind of get into Easy Power and let's talk about this. So, what I'm gonna do starting with ECPAR is to import an s k m data file that I've stored in a path that already creates, that already has a folder, subfolder called mapping files. And so, this occurs under I've done this in stages, so we can we can say to see the progress. So, here's my original export from EZ Power, I mean, STM. Turns out the mapping files are all blank, and I'll look at those in a second. But now by importing this to state of file, we will generate the the reports that I was talking about. And so in the first report that shows up is an error report. And what it tells us is that the data has been successfully imported. It applied the mapping files, albeit blank as they were, but it went through the process fairly cleanly. And, frankly, I might want to say this, but because this is the first pass This is less important than this report, which is the import error warning. Now, this is where you're looking for patterns, and you're looking for repeating errors, and it's also where I noticed that there were commas in my file. If I go in and look at Let's say, this breaker here, as to what the problem is, I can either go to it on the one line, or I can edit it in the data dialog box. And so what I'm gonna do is look at the data dialog box. Alright, I see it's a moldy k circuit breaker, but nothing came in as far as the manufacturer. So, I'm gonna look at the collected data. This indicates that the manufacturer is a color hammer. So I can literally change or workaround the missing data by mapping what I read manually from the from the dialogue, the error report. And so this will show me the part number. It helps to be familiar with the elements We're looking for something that's rated for 1zero amps at four eighty volts, 25K interrupt rating, It looks like it's a type f d, so I'm gonna look under standard It's not an f d. It's an f t fifteen. And, again, it helps to know The year. Alright. So, again, the process that I'm trying to emphasize is I don't how to use this feature. And Looks like it's a series c. So let's Alright. Now, it's short circuit. It auto calculates it. It's rated for thirty five thousand amps. And So, I see a discrepancy there that causes me some concern. So, before I accept this, I wanna go back and and research that. Now, the other thing that shows up is it tells me I have an invalid text entry, and it highlights the ID name. And here's where I find that there's commas in the ID name. So at that point, I'm gonna stop what I'm doing and go back and change my import Let's go ahead and close this out. So I'm gonna do two things. I'm gonna Close this file and change the import with a find and replace. The commas with a a dash mark. So let's try this again. I've saved this in a separate file. So that's going to import two. Again, here, the mapping files are not blank, and I've actually started with We'll look at these in a second. Started with recommendations from EZ Power on what my mapping files could include. So, we're gonna import this. And, again, by two things going on. The errors caused by the comma should be eliminated, and now my mapping files are gonna be applied. Again, it imported successfully. It applied the mapping files and had some issues. So I'm not gonna save this. Now, you can see my errors reduced considerably. And now, the process is to go back, and it looks like I have issues with my low voltage power circuit breakers. So let's start off with this guy and see what's going on. Again, I'm gonna rely on the equipment data tab, collect the data tab, So it looks like GE was recognized, part number, solid state, sensor, and plug. Again, short circuits identifying the part automatically from the device library. Part this missing is my settings. So if I plot the t c c, And I look down here at the settings input, setting string, I see Long time pickup is set for point six. A long time delay is one point five, Take that back. Long time pick up is one. Again, this this should match what's on the datasheet and what's in the device library. Shortchimp, And I say that because if it doesn't, then we don't have the correct partner, and I need to do some research, either in the catalog or on in the Internet. So the short time pickup is one point five, and the delay is one. So short time pickup. And that delay is minimum. And the only thing left is instantaneous. Well, actually, I squared t is on, which is n. In the short term instantaneous or at instantaneous's two point five pickup. Now, and so this has been one zero two d, Which is this puppy right here. I'm gonna clear this, handles these errors down to here. Now, the the advantage of doing this is that as I clear them, they will no longer show up on the error report. So, if I were to save this file, let's say, if I'm gonna close it and save it, and close the year. One line diagram. And then open it at a later time. It it gives me the original one line that was was drawn. And then from my import, I can import the log and pick up where I left off with that. Device no longer on my analog. So, once we've done that, And once we've eliminated these these manually these devices manually, then we would end up with a file that looks more like may kinda go to my third example. This is where we wanna validate data for still missing devices. So if I come back to import three, Okay. So here's this has had some amount of Correction, and we'll see if we got an import log. Yeah, so now we're down to, we've resolved most of these as far as duplicated examples. And now, we can go into the one line and either correct them here or go into the database browser. So, if I and the difference being, any changes made in the database browser won't be recognized by the import logs. So, that's one disadvantage of doing it. Now, if we look at our base case, database browser, we can focus on each generic type of device and then examine things that are missing specific fields. So if our breakers, we can scroll down, and here's something where the new shred is not showing up. We can go to the item on the one line. It looks like it's a fairly important element, so let's find out what's going on. And we see it's not reflecting any data, and it turns out it's a cutler hammer with a that wasn't recognized by our import. So, again, this needs to be corrected and resolved. The one advantage of doing this in the database browser is that if the the device list is displayed in alphabetical order. And so as I scroll through the different devices, I can see duplications that I can copy and paste into the next next device that has the same settings. So, again, having access to the s t m data file, Thanks, Mike. It's relatively important. Okay. So, what we've fully covered is how to improve the mapping files. I'm gonna show those here briefly. How the descriptions can be accessed in the collected data tab on each element. And you don't have to be in the import mode to do it. You can do it anytime you have a one line diagram. And then you wanna correct as many as you can. The database browser allows us to inspect and research validity of any data and modify it, and we just saw how that works here. Let me go in and look at my files. I wanna make a point of looking at the So in this procedure in the book that it lists the need to generate a mapping file folder. And it gives you a link to a web page or website, an easy bar, that allows me to download this set of mapping files. But if you look at them, they're all blank. Now, it's important to realize that these are not typical Excel spreadsheets. These are CSV specific. And so what that particular link gives me is a blank structure, and the description, and the user's guide talks about anything that's within the segregation of the greater than or or less than comments, locations gives me what was imported. And if I want to map that to a specific easy power function, then I would put that, that element over here on the right side. So, let me show you what something looks like. It's gonna spin populate. And so in my second folder, where I did utilize mapping files, This, this set of CSV files, mapping files, can be requested from e c power, but there's no There's no guarantee as to accuracy, it's strictly just the updated file that that that we use. But you can see it's a very good way to look at the way things are done in the equipment file, the mapping file, if you oqualize on the top row. You can see how a b b, certain part numbers for a b b, and certain app bank functions get mapped with an easy power value based upon the recognition of that in the import file. So mapping files can be very important and reduce the workload. Okay. So, currently, devices that are imported without data include busways, current limiting reactors, c t's filters, generators, relays, and transmission lines, items that are not record it include this list, and this is straight out of the user's guide, but these may change in the future as more features are added. Now, with the folder that we're using, the initial layout looks something like this, and and it's relatively Because there's no coordinates associated with the part, It's relatively difficult to lay out anything that's similar to what was imported other than just the connections. DC Power gives us the ability, and it's difficult to see on this slide, but The different voltage levels can be color coded, so you can drag en masse to certain sections to be lower in the system versus say higher voltage, which you may want to have in a higher up on the one line. But in this example, this total process was a hundred and ten bus system The total time took about eight hours to do the whole import and resolution. And what I wanna emphasize is that once you're done, even if you don't have loads on the buses, you still should be able to execute a power flow solution just to ensure the integrity of the design. So let me kinda go back and show that. So, I have the finished file here that can bring up, kind of resolve or at least show how this is resulting. So, again, this is not This is not a one step one button process. It is an evolving solution, and here's what resolved from that initial import with the eight hours of work that it took, but as a result, we should be able to go to short circuit and get a clean one line, be able to fault the buses, And if we've got part number settings, we should be able to generate our flash result. Now, it's not to say it's coordinated. It's not to say it doesn't mean adjusting, but at least tool solves it, which means we have a clean one line. Likewise, we can go into power flow, get a solution set created there, and see power flow results. So, what I've tried to describe is a iterative process of importing and resolving errors and improving the result. Two things that I really didn't highlight that much is if I go into AC power I look at the colors. I look at the color options in my options file, I can change the equipment colors based upon the voltage on three phase equipments, and so here's the scale. Can be applied and the colors can be changed, but by doing that, now I have darker colors for my higher voltage and the tan colors for my for eighty volt systems. And if there's anything lower than that, I can do the granularity even smaller. And another tool or another capability is Let me kinda go back. Just is the ability to stub off cables, and that allows me to move things around without having to be concerned about the cable location. So, for instance, this cable If I look at the data block for it, it gives me all the details which is part of the import, but then if I don't show the entire line, to the to the load, to the subsystem, I can then select this, or everything below it, and move it to a different location. And then once I'm there, go back and reconnect to one line. Reconnect the cable description to show the entire line, and it'll redraw no matter where it showed up, where I moved it. So, that's another technique that's, I think, useful in the resolving process. Okay. Again, all this is covered in the user's guide. Everything I've I've displayed here is part of the basic package of EC Power. And certainly, you have access to support at e c power dot com. If you wanted copies of the mapping files, and appreciate your attendance today. Appreciate your time and attendance. If you got questions, you're more than welcome to shoot me an email, and if that'll do it for my presentation today. Appreciate the help and the part numbers. So, yeah, the question, does Easy Power have a service converted. The answer is yes. No. So, I take that back to conversion from an s t m, It's not something that EC Park could do, because we don't have SKM in house. However, if you contact tech support, they can refer you to third parties that can do the do the conversion. Do the setup of the import file from s k m. Now, the other part of the question that I've answered inadvertently is can e c power help with this resolution and mapping files, that too is answered, yes. And I encourage you to contact sales or support at easy par dot com and see what we can work out. Hopefully, that helped. Have a good day.