Programming

Long ago, when architecture began, so did programming. Structures have always been based on programs: accommodations were needed, decisions were made, and something was designed, built and occupied.

Today, we define architectural programming as the research and decision-making process that identifies the scope of work to be designed. Since design is problem solving, programming is the search for sufficient information to clarify, to understand, to state the problem. The core idea is profound: Separating programming (analysis) from design (synthesis) brings tremendous clarity to the design problem. Focusing first on the goals, facts and concepts, then translating those into quantifiable needs (independent of the solution) facilitates decision-making and encourages innovation.

In the 1980s and 1990s, some architectural schools began to drop architectural programming from their curricula. The emphasis of the Post-Modern and Deconstruction agendas was instead on form-making (as important as form-making is). Programming and its attention to the users of buildings was not a priority. Now, several generations of architects have little familiarity with architectural programming and the advantages it offers:

• Involvement of interested parties in the definition of the scope of work prior to the design effort

• Emphasis on gathering and analyzing data early in the process so that the design is based upon sound decisions

• Efficiencies gained by avoiding redesign (and more redesign) as opportunities and requirements emerge in ad hoc fashion during architectural design.

Bottom line? The most cost-effective time to make changes is during programming. This phase of a project is the best time for interested parties to influence the outcome of a project. The owner, building occupants, and operation and maintenance personnel should be involved to contribute their understanding of how the building and its systems will work for them once they occupy it.

Programming may happen for different purposes and may impact the level of detail of investigation and deliverables. For instance, programming at the master planning level is more strategic in nature—providing information to building owners to make decisions regarding current and projected space needs and rough budgeting for implementation. Programming at the individual project level provides specific, detailed information to guide building design.

A programming consultant, like SCI•X Science Studio brings to a User Group an expertise in the programming process itself – the “Process Design” as well as particular benchmarking knowledge, and “a state of the art” understanding of particular building types. The advanced technology building types in which SCI•X has particular expertise include, Academic Laboratories, Healthcare (proton therapy in particular), Pharmaceutical facilities (both research and process) and Industrial (clean room applications in particular.)

How is working with SCI•X different from others?

First of all, we do not employ cookie cutter approaches. Your project is unique and our programming “Process Design” will be created to respond to your particular project.

And second, as our name implies, we understand the science behind your project. Whether it be the particle physics behind your proton therapy facility or the specific chemistry of the research planned in your laboratory, we speak the language of your clinical and research staff– hence our tag line: