In this lesson we're going to model parametric runs using global parameters. More specifically, we're going to evaluate the most common thing-- lights. We first need to create a global parameter. To do this we need to be in any of the modules, and we need to be in detailed mode. If we right click on the project, we can create a global parameter. We have to give it a name and we're going to call this “LPD.” It's always a good idea to give it a name of what it is going to be because you could have multiple global parameters. The type is going to be numeric, and the parameter value is going to be 1.2 watts per square foot. Leave the label out of it for now since this is just a numeric value. Once we click OK it's going to list the global parameter added to our current list of global parameters. Since we had no existing global parameters, we only have one here. We can click done. We've created the global parameter. eQUEST doesn't know what to do with it based on the word “LPD.” We actually have to apply this to our lights. So we can go to the internal loads module, select spreadsheet, and select one of the spaces. Then we have to go to display mode, and lighting. If you look here, you'll notice that not all of the spaces have lights because some of them are plenum spaces, which makes sense. This makes lights in miscellaneous loads a little bit different than some other things. If we want to apply our global parameter, what we can often do is right click, and if we wanted to change everything we can usually go to the edit and view user default, but if we look there's some sort of complex expression so that we don't accidentally assign lights to spaces that don't have lighting schedules. That's a little bit more complex than we need to get into right now. We need to explain simple effective and fast anyway. If we right click and all we do is select edit/view user expression. We can type in # (which is just a command sign for the D2 engine) pa (“LPD”). This is the standard format that you use to enter any global parameter into any field. If the global parameter was named lights, we could type in “lights,” but the format would stay the same. We just click OK and we'll now see a magenta value listed for the lighting watts per square foot. A very fast way to go through this is to hit control+C, the down arrow, control+V, down, control+V, skip through the values that are not available, and now we're done if we wanted to apply this to all our spaces. We can save this. The purpose of doing this was not to run one single run, though. We want to compare this to another run. Let's say we're going to compare it to the same building with 1.0 watts per square foot. What we would need to do is go up to the parametric runs. If we select tools, parametric runs, we can create a parametric run and we're going to call this “LPD.” Keep in mind, we can keep adding additional runs onto the existing runs, but right here we're just going to change the lights. It's based on the baseline run. We have to add a parametric component. We're going to call the parametric component LPD 1. The name just needs to be something that you're going to recognize. The type is a BDL command. The component type is global parameter. Once we select global parameter, it will prompt us to select the global parameter type, which is numeric. Then it will list all of the global parameters existing in the project. We only have one, and we can check it. Once we check it, it fills out our data modifications with the default value, and all we have to do is change the value to 1.00. Now we can click done. When we go to stimulate this project, we'll have two parametric runs, the baseline (which is 1.2 watts per square foot of lighting), and the LPD run (which is 1.0 watts per square foot lighting). This can be applied to basically any other parameter.