4specs.com    4specs.com Home Page

DESIGN PHILOSOPHY Log Out | Topics | Search
Moderators | Register | Edit Profile

4specs Discussion Forum » Ralph W. Liebing, RA, CSI, CDT » DESIGN PHILOSOPHY « Previous Next »

Author Message
(Unregistered Guest)
Unregistered guest
Posted on Wednesday, November 24, 2010 - 07:43 am:   Edit PostDelete PostPrint Post

112310
DESIGN PHILOSOPHY Happy Thanksgiving!
by Ralph Liebing, RA, CSI, CDT
Cincinnati, OH


Design, in the architectural context, is often mistakenly assumed to be an effort at a purely artistic approach to a project. In essence though, it is at the forefront of the project, the theme—the initial statement. And the effort is to bring all elements of the proposed project into proper focus and context. It is an effort to convert information, wants, needs and desires into the reality of a comprehensive and properly functioning facility for the client.

It is an attempt to incorporate a fixed set of approaches, concepts, rules or procedures, which will henceforth be applied in an inflexible, unwavering manner. The statement of a design philosophy is not an attempt to establish or implement a policy or system regarding project design to every project. Should the specifications writer be part of the team that develops the philosophy for the project?

The statement of design philosophy is mostly a dedication to provide each client with an individualized design solution which best serves the various functions of the client, which provides for new, different, and expanded operations, and which presents a reasonable direction and opportunity for future expansion or re-configuration. Nothing less should be professionally acceptable. Is there a chair at the table for the specifications writer?

However, in addition, the architectural effort has a responsibility for gathering and interpreting information, combining it into a comprehensive and workable solution, and providing a facility for all of the various other systems and functions. This needs to be an effort that is studied, controlled, reasonable, image-enhancing [for the client], and which coordinates the overall project into a complete and cohesive enclosure-- meeting both budget and schedule parameters of the client.

Within this effort, it must be understood that the client has several aspects of the projects available, but usually will not be able to control all of them. Cost and scope are obvious examples of principle items the client is concerned with. So, too, schedule is playing an increasing role in the client's concerns.

In this, one element has an inherent ability to assist the other functions in varying ways. This is quality! While present in every discipline's work, in the overall scheme, the architectural effort is the first to establish which level of quality is attainable given the other considerations. Often what is established in this sequence will have some impact on the others. Therefore there is a need for a fully coordinated effort, on the part of all disciplines, as equal partners, even when not immersed in the project work. The need if for a continual flow and exchange of information, in the level of detail available or needed, so proper and due consideration can be given to the information, systems and other designs.

In summary, the architectural effort has the initial and ongoing responsibility to establish and maintain the direction and cohesiveness of the project, encompassing and accommodating all disciplines, in a form which provides the client with a satisfactory aesthetic as well as functional solution. Several parties may lay claim for the non-existent role of leader of the project, but it is the architect who has the broadest and most involved role. Knowing the project from the get-go, and all the innuendos and side comments included as part of the programming, the architect has a sense of the “flavor” of the project, unlike the others. This leads to a higher sense of need or desire on the owner’s part and in turn priories the features included in the project and their relative importance. Specifications data and input are essential from the start of the project design!

This is simply a matter of fact, and not a grab for prominence or control-- it is the natural extent of the role required by the Architect-Owner service agreement.

The in-depth knowledge of the project that lies solely with the architect creates a point of concern and a need for mutual appreciation in the use of that knowledge. Since no other party has this distinct bundle of data, that architect needs to set out as the sole recourse for certain information. Following the path that architect developed for the concern all participants will work to a uniform as a common goal. We need to remind ourselves of this quite off, when conflict and glitches begin to show up. As specifiers, too often given little regard, we need, continually to express the specifications’ input to the philosophy!

A good portion of the construction concept, detailing, selection of material, and information comes from the architect, so it is well to have the sole source within the project “company” where it can disseminated to all others in uniform and timely manner. This is not a matter of status of control but a way to convey the owners’ desire, etc. to the construction and field personnel-- it is a matter of clarity, decisiveness and accuracy. You know that-- but do all of your colleagues?

Add Your Message Here
Post:
Username: Posting Information:
This is a public posting area. Enter your username and password if you have an account. Otherwise, enter your full name as your username and leave the password blank. Your e-mail address is optional.
Password:
E-mail:
Options: Automatically activate URLs in message
Action:

Topics | Last Day | Last Week | Tree View | Search | Help/Instructions | Program Credits Administration