Every engineering department has work that nobody likes doing. It is not difficult work, but it's the kind of work that quietly steals engineering time. For example, updating custom properties, exporting step and the Excel files, maintaining standards, running the same process hundreds of times every month. Mind you, these tasks are necessary, but every minute spent on them it's a minute not spend designing, solving problems, or innovating. They do not improve the model. They do not move the project forward or add direct engineering value. They simply must get done. And guess what? That is exactly the problem. Solid Q changes that Solid Q provides a powerful library of automation tasks. These are not simple macros. They can be configured to match your organization's requirements. Tasks can process individual files, entire folders, usually thousands of files in batch turning work that can take hours manually into processes that will require your attention for minutes. But automation is only part of the story. The real value comes from creating workflows that support engineers throughout the entire design process. As a standalone platform, solid Q can automate large scale batch processing operations such as generating step the PDF files, updating custom properties, validating file data, processing large collections of files automatically. But as a SOLIDWORKS add in, solitude becomes part of the designer's everyday workflow. For example, a user may temporarily adjust image quality setting while working on a complex model. It happens every day in all companies. That's often the right thing to do for the task at hand. Different projects and different design activities sometimes require different settings. The problem is that most likely is going to forget to bring it back to the company standard, and it will save that file. The settings will remain in the file long after they are needed. That can affect performance for the next person scope on the files, the wider team working downstream, or really anyone trying to reuse the data later. Solid Q can automatically restore the company's prefer settings when the file is saved or close, you simply save the file. That's it. You don't have to remember anything. Designers get the flexibility they need. While the organization maintains consistent, standard and optimized performance. The result is better quality models and improved performance for everyone who uses them downstream. The same approach can be applied to custom properties, document settings, naming conventions, templates, pretty much any manufacturing deliverables, many other standards that organizations typically manage through training procedures and manual reviews. And this is the cool stuff. Instead of asking engineers to remember every rule, every process, every procedure, every exception, solitude quietly handles those responsibilities in the background. This creates a seamless workflow where the SolidWorks adding supports engineers, designers, users while they work, and the standalone automation platform handles larger batch processes whenever they need it. The result is higher quality data, greater consistency, fewer repetitive tasks, and more time spending on designing engineering instead of administration. For managers, that means more reliable outputs for users, designers, engineers, it means less low value manual work getting in the way of the job they were hired to do. Let solid Q handle repetitive work so your engineers can focus on designing great products. Speak to a solid Q specialist to identify where automation could remove repetitive work from your workflow, and give valuable engineering time back to your team. So for example, we have a client here that is reporting slowdowns with with his assembly. And one of the reasons is quickly revealed by the performance evaluation, the image quality settings for his assemblies all over the place, actually for the components of his assembly. So you can see. Let me do it again when I go here. Notice that there. These numbers are all different. In order to use consistent in order to use multi-core processing of graphics data. This this have to be consistent, right. So that's one issue. Another thing if I reveal what's hiding in this assembly was lurking inside. You're going to see a lot of complex features. Center of mass bounding boxes for each and every one of the subassemblies. For each and every one of the subassemblies of service employees. For each and every one of the parts. The reason they are there is because whoever created the templates for this component initially had this very heavy features in the in the template. So any new product created, any assembly that they created would require this to fix this. You're going to have to open each and every one of these parts. They already told me, well, we don't really need these guys, right? So I need to delete them. And if I do this by for each and every one of the parts is going to be extremely, extremely time consuming. All right. So delete this. Close it. Save it. Move on to next one and next one. And next one is going to be extremely extremely time consuming. Solid queue will. And you can see look how long it takes to go back to the assembly after this I'm still waiting. I did one little change and this blue circle of that is spinning. Feel free to zoom into this blue circle of that, right. I'm still waiting. I'm still waiting for the assembly to update. Did such a simple change. Just waiting and waiting and waiting and waiting and waiting again. Obviously we cannot show this waiting time right now. It's still waiting, waiting, waiting, waiting. It's. It's maddening. Wow. This is crazy. Now remember, imagine doing this for each and every one of the parts. There are probably a few thousand parts in here and few hundreds of subassemblies to to. I don't know how you can show this in the video in a few seconds, but if there is a way. To explain the fact that a user like this would work probably one hour a day, the other eight hours are spent waiting for the blue circle to disappear. That would be ideal. Maybe you can see the user now is board to that. It's just moving the mouse on the screen and now it's back plug plus look at look at the mess that's here on the screen. So what we're going to do instead we're going to start solid Q. And we're going to run a little macro actually a series of tasks. So first of all let's add the folders that are required. Now here please. As I'm searching for this please hide the And what I want is to run an image quality setting. So image quality setting I'm going to drop it to the same level. So let's say 10% for all of them. I'm also going to use macros that are going to delete those pesky features that we're. In the template for each part. So I'm going to say here delete bounding box. And the name of the feature is going to be bounding box okay. And then let's do it again. Delete center of mass. And the name is center of mass. Alternatively we can just suppress them if they would require type of this type of things. Other thing maybe I would like to declutter the graphic area. hide certain features. Like pretty much anything that's an axis, a curve, a plane, a point or a sketch. Right? And finally, let's do a zoom to fit. To to this part. Very important I'm going to make and this is where solid is so cool. You can specify the order of processing this information. I think we're mentioning that somewhere in the video. So bottom up I'm going to start with the parts then subassemblies and then top level assembly. And if something happens if there is a crash, we have lots of tools that can control what's going to happen. Okay. If it's if we're using PDM, I can automatically check in and check out files. So lots of things here that you can take and put in your. In the video okay. So let's process these tools. So now so this is going to look for the order of processing and starting SolidWorks. So I'm going to let this run. I'm going to let this run for a minute or so. So you can pick up whatever is going to open. Those bounding boxes are deleted. The center of the mass are deleted. Zoom to fit. As you can see I'm going to let it run. Pick whatever you think it's important from here, but imagine a user doing this work for hours and hours and hours. And in the meantime, solid queue can show you the progress reporting log warnings information, right? I can say, hey, is there any actually problem here? No. No problem. We're good. Okay. Let's keep going then. All this information is there. It's very, very nice. I can also go by order. I mean so many things would be available here. Lots of good information. Also, you can see that it's telling me how many files are being processed out of how many left. So it's it's pretty nice. I let it run for 100 files because I want to, to show you that after 100 files, I set SolidWorks to restart. I think I mentioned that in the video two. So don't if you want to. Maybe. Show this without overwhelming them too much. As you can see how these numbers are changing here as I'm processing the files and it's telling you everything that happens to them, which task is being processed, what's the success for that task? Lots of cool information. So pay attention to this number. Now we're getting to 92. You're going to see when it gets to 100. Solid Q is going to restart SolidWorks. This is great for making sure that we are not. Consuming windows resources. Look at that number 100 now and you're going to see Solid works closing. And now it's going to restart again. Okay. So it continues the work. Now I'm going to stop it. Don't want to. Waste your time. But I think it was it was a good idea to show what happens with existing files. Now what about what about files that are new or are being worked by the users? Many companies are trying to. Force the users to behave a certain way. Right. So for example, if I'm looking at, I don't know this, let's pick up this part. So I'm looking at this actually let me find an assembly so you don't have to use the. Let's see if I can find something useful because this is a yeah this this could be a good one. Or even better, let me let me open the higher level assembly. I'm going to open this assembly. Again. You probably cannot use this footage yet. Just bear with me. I think I'm going to find something really useful. What I want to show is the fact that users can be free to do whatever they want, with the zero impact on the teams. Performance. With solid without solid CU, they have to follow procedures. They have to remember things. It's it's crazy. So let's see if I can use this. This might be a good one. The artist part of a subassembly block to that. Let's see. This. Okay. I'm just going to create a server for these three things just for fun. So for this assembly. Three or this is already perfect. Yeah I think I can do it. 123 okay. Form yourself assembly. Just ignore everything I'm doing so far. Ignore ignore ignore. And now. Let's see what we got here. Okay. This this actually showed things really, really well. So imagine okay. So you can you can start recording here a user with okay. So a user my many times they might need to do a visual check to make sure that things are not interfering. So I'm going to zoom in here. And man don't you agree that these two seem to interfere. The reason for that is the image quality is pretty low, right. So image quality is low. I'm going to increase it. Oh no more interference. Right. Looks much better because I it's it's looking all right. The problem is if I save it right now, this thing is going to be saved with a really, really high image quality. Right. So the user have to remember to drag this back to wherever the company standard is. And I don't remember what it was it here. Was it here. God knows. It's kind of hard to remember. So what I'm going to do instead I'm going to use I'm going to make sure the solid Q so solid Q can be run as an ad in. Which means that when I run solid Q, I can I can add ad commands to the typical buttons of solvers instead of hitting save. Right now, I'm just going to make sure that event based tasks. So the user opens this assembly and it wants to do a visual check to make sure that there are no interferences, and all because of the polygon or shape due to the image quality, standard image quality used by the company, it looks like these guys are interfering. Is it true or is it a mirage? So to ensure that image quality is not a factor, she will increase the image quality to a much larger value. Now it looks fine. No. No problem. The challenge is if they hit save right now, it's going to destroy the performance of her teammates, right? Because the image quality is going to be a different than the rest. Fortunately, they have solid cue as an ad in. So with solid cue you can establish event based tasks like before hitting save. I'm automatically going to adjust the image quality to the company standard. Maybe I'm going to zoom to isometric and I might even hide certain features right. So right now the only thing I need to do is hit save. I'm going to hit save. All right. Let's see the result. It's automatically set to isometric. And look at the image quality setting. It's back to the company standard. You don't have to think at all. Another example let's say I'm inside this part. And I wanted to see these planes because well I can I want to see the sketch. I want to see this sketch. Right. So it creates quite a bit of a mess. Later on, maybe this sketch I'm going to color to orange so I can see it. The other one I'm going to color as cyan so I can see it. And now it's a mess right. If I hit save right now, I'm going to impact my my colleagues. Fortunately, again with solid cue as an ad in. We are we can hide features right. So again I hide automatically sketches planes things like that. Right. So the only thing I need to do is press the save button. And this returns to the company standard. Right. So this is a good example of what we can do. Rather example. This is coming from another client of mine. They would have an assembly that contains all kind of parts. For example this part has a well-meant right. So what they would like to do is to add here a custom property called is Well-Meant. Let's do it. The custom level is Well-Meant. And the value is going to be yes. So that's that's a manual approach. Now what this allows you to do is to quickly be able to select all the well-meant by pressing a button. Okay. But then you have to manually go through all of them. So for example I want to go through this one. This time I don't want to go through here I don't want to type this name. I'm going to go to Solid Queue. And I'm going to add to the save command the ability to add a custom property. Okay. So let's say add. Is realmente equal. Yes. And I'm going to add it is meant property value is yes. Now I want to run this only if it has a well-made feature. Okay. What if it doesn't have a well-known feature. Let me duplicate the task and say, well, if it doesn't have a one man feature, this is going to be no. So I'm going to go to the property and I'm going to invert the Wellman feature. I'm going to invert this. What if I have a sheet metal part. Let me duplicate this. So is sheet metal. Is yes. Okay. So in this case this guy is going to be not above the well-meant. But if it is sheet metal. Now duplicate it one more time and I'm going to say no. And no. Okay. So in this case this is going to be reverse. Okay. That's it. So now let's hit save. Look at the property. Now let's do this for this part. What do you see here. No property right. I'm just going to hit save. Look at the property. Sheet metal is well right. Let's do another one. This one? I think it's a sheet metal part. So I'm going to hit save. Look at this property. Yes. No. Good. Now what if I try to automatically select all the sheet metal parts. Let's isolate. Right. Let's try. Select all the Wellman's. Isolate. This is great also for bill of material. Great for many, many reasons. Okay so all this automatically with solid. There are lots of other things that we can we can look at. So if you're looking at what solid you can do. It is pretty crazy how many tasks are available. And the cool thing you can just search for them right. So add custom properties. We can obviously just do that file open. I can quickly add those tasks. So I don't know if you if you need more information let me know. I think you can pick quite a lot of information from here. How to install solid. You already.