Project Planning and Design Introduction

6m 17s

In this ARE 5.0 NCARB-approved Project Planning and Design Exam Prep course you will learn about the topics covered in the ARE 5.0 PPD exam division. A complete and comprehensive curriculum, this course will touch on each of the NCARB objectives for the ARE 5.0 Project Planning and Design Exam.

Instructor Mike Newman will discuss issues related to the generation or evaluation of design alternatives that synthesize environmental, cultural, behavioral, technical and economic issues.

When you are done with this course, you will have a thorough understanding of the content covered in the ARE 5.0 Project Planning and Design Exam including design concepts, sustainability/environmental design, universal design, and other forms of governing codes and regulations. 

The planning and design exam is gonna be about all things about making the design and making the ideas real, so we've started with the idea of programming. We've moved from programming, starting to go into schematic design. That was all in exam three, in that programming and analysis where you're gathering information and you're looking for opportunities. Now, we're moving into this sense of, alright, we've thought about all of those issues. Now, we have to start making it real. We have to start weeding out the things that aren't gonna be used on the project.

We're starting to get at sort of real design issues and making sure that, okay, we had this idea that would be really great if we did, you know, X, but now, will it fit, we have to see if it will fit. We have to really make sure it's gonna work, so this is where the rubber meets the road. We are making sure that what we're talking about, these design ideas are actually now plans. They're actual designs that are moving forward in this process, so we are kind of moving from schematic, very early schematic thinking, kind of more detailed, getting it to be more thoughtful and more real, having maybe a couple of different options, analyzing those options, making decisions about which is the correct way to go and then moving in from there into design development, so we're talking about schematic design.

We're talking about design development. We're kind of moving our way into this as a process and getting more and more real.

We're still gonna be looking at site information, especially how we're gonna place the building, so this would've been a discussion from before. Opportunities would have been discussed before. What are our goals for creating the right spot to be able to put this building? Now, we're talking about, okay, where does it actually go? What are the specifics to how we're gonna place this building? We're gonna be thinking about alternatives and options.

How do we feel about the actual sustainability and environmental issues? Before, we're talking about all the possibilities in the world that could be available to us for this particular site. Now, we're starting to say, alright, not that one, not that one, not that, oh, geothermal, perfect for this site, so we're aiming in and we're making design decisions in order to then, at some point, get through the CD sets, get permits and get this thing into construction. While we're talking about all of these things, that idea of making things more real, one of the things that we're doing is we're synthesizing quite a lot of information.

In the programming phase, and even, to an extent, in the schematic design phase, there's a lot of separation of issues. We start talking about structural systems and HVAC systems and electrical systems in those very early phases. We have an idea that they're coming and we're trying to not do anything that's gonna get in the way, but now, we're at a spot where we have to start putting those things, integrating them together, synthesizing all of that in a clear way so that all of that is making logical sense and one issue is helping the other issue, so that it all is kind of going in the same direction.

Well, while that's true with something like structure and HVAC, it's also true with things like behavior, like will people use this the way that we're talking about it?

So in schematic design, we're kind of making these big generalized decisions, but by the time we get to the end of design development, we better feel very comfortable that, alright, we were talking about putting the door in that location because that matches, you know, some idea of what the client needs or wants, but will people on the street know that's the front door? Is there sort of an expectation that a door that looks like that or is in that location in this context is the place that I'm supposed to go? So we're starting to synthesize together not just what the client wants in the program, but also what's expected, what's the real world experience, what is the cultural expectations for how people are gonna actually use this structure, whatever it is, so we're trying to put all that stuff together, and you know, we're calling it schematic design and then design development, so we're moving from the previous ideas of the early schematic designs.

Now, we're going into the finalizing. We're making sure we have a set of options that we really like and that are really meeting the goals of the program.

We're choosing the correct one, working with the various teams. We're making sure we're on track, taking that one and rolling into design development, fulfilling all of the thoughts there, making sure that the decisions are the right decisions. We're checking it against the codes. We're doing all of that kind of work and we're sort of getting through to the point where we can, at some point, say alright, we are no longer thinking about this from a design standpoint.

We are now thinking about this from a detailing and documentation standpoint, and that would be the next exam, so in this exam, we're taking the ideas from before and we're getting them ready and sort of making them real world, making sure it all fits together, that the look is right, that the design is right, that it's planned correctly, it fits for people's lives, and then we're ready to start doing documentation and detailing down the road, and at some point, we're also ready to then go build it and have a contractor get involved, so right in that middle spot, where this is the real, sort of workhorse part of the design process.

This is where most of the real design work is happening. Everything else is sort of playing out the ideas from this phase, so this is where all those real, sort of finalized design decisions are happening that we are hopefully matching to those initial goals that we set under programming, and we're setting ourselves up for a really positive documentation process, but right now, we're in the design phase.

Log in to access files

From the course:
ARE 5.0 Project Planning & Design Exam Prep

Duration: 30h 57m

Author: Mike Newman