CHOP 6.1 - PREDESIGN Flashcards
Feasibility Study
A report which outlines the research and subsequent analysis to determine the viability and practicability of a project. A feasibility study analyzes economic, financial, market, regulatory and technical issues.
Business Case
A document developed to establish the merits and desirability of the project and justification for further project definition and the commitment of resources.
Functional Program
A written statement which describes various criteria and data for a building project, including design objectives, site requirements and constraints, spatial requirements, relationships, building systems and equipment, and future expandability.
Gap Analysis
An analytical tool that identifies the difference between a current state and the desired state.
Pre-design Services
The architectural services provided prior to the schematic design phase which assist the client in establishing a functional program as well as the project scope, including a financial and scheduling plan.
The possible pre-design services that an architect may perform are far-reaching. This handbook describes some of the common examples, including:
- business cases and feasibility studies;
- project budgeting and cost planning;
- life cycle cost studies;
- functional programming;
- space relationships/flow diagrams;
- space planning and optimization;
- organizational and business planning;
- site evaluation and selection;
- master planning and urban design;
- building condition assessments;
- as-found drawings;
- project management framework;
- client-supplied data coordination;
- project scheduling;
- authorities having jurisdiction (consulting/review/approval);
- land-use analysis and re-zoning assistance;
- building code and fire safety analysis;
- presentations and project promotion (including public engagement and business collateral);
- design competitions brief or proposal calls documentation.
A project that has invested in pre-design work is more likely to be delivered on time, on budget, and to the client’s expectations.
An architect may also perform or coordinate other pre-design services, additional to those listed above. These services often require collaboration with experts in other fields.
Pre-design Services and Team Organization
Certain pre-design services, including many of the above-noted examples, will require the skills of specialist subconsultants to deliver.
The definitions of some of the typical pre-design services are often subject to different interpretations by all stakeholders involved in a design-construction program. For example, the term “program” can imply different things to different members of the team, and to the client. A “program” in the context of design refers to the document that contains the functional requirements that the design must satisfy. In a project management context, it refers to a grouping of projects and operations that are coordinated and managed together for greater efficacy.
Each architectural practice must decide whether it wishes to employ pre-design expertise in-house or offer these services via subconsultants.
Setting Up Project Workflows and Systems
Business Cases and Feasibility Studies
A business case is a document that justifies the financial investment and resources to turn an idea into reality. Information in a business case includes the background of the project, the expected business benefits, the options considered (with reasons for rejecting or carrying forward each option), the expected costs of the project, a gap analysis or the variance between business requirements, current capabilities, and the expected risks.
Business cases provide analysis on:
1) the background of the project;
2) the expected benefits, including financial benefits;
alternative options (with reasons for rejecting or carrying forward each option);
the expected costs of the project;
3) a gap analysis demonstrating the difference between the current state and the expected state upon completion of the endeavour;
4) possible risks, including both threats and opportunities;
5) analysis of the “doing nothing” option to account for the costs and risks of inactivity;
6) recommendations and plan for proposed next steps.
Feasibility Studies
Feasibility studies take many forms, but they generally expand on the financial focus of a business case by considering the broader macro-economic, regulatory, political, social, operational, and technical practicalities of an initiative, often incorporating:
1) official plans and community plans;
2) zoning and land-use controls;
3) designated activity districts within cities;
4) transportation issues;
heritage districts;
5) community organizations and concerns;
6) civic design panels;
building codes;
7) environmental issues.
Budgeting, Cost Estimating and Financial Planning
A budget is not a cost estimate, but a determination of the worth of the project to the client. In simple terms, a cost estimate must be compared against the budget. If the cost estimate is lower than the budget, the project may be worth undertaking. If the cost estimate is higher than the budget, the project may not be worth doing.
More detailed financial breakdowns, such as land costs, hard costs, soft costs, carrying costs and contingency, are usually first addressed at the pre-design phase
Financial plans break out these costs and are typically presented as a “pro forma,” not usually prepared by the architect, including:
1) hard development costs (construction and land costs);
2) soft development costs (such as professional fees, realtor fees);
3) financing and carrying costs;
market revenue analysis;
escalation;
4) rates of return on investment and capitalization.
Of these parameters, the architect can usually only comment on construction costs and professional fees. Other experts will be required to provide the client with the complete program cost estimate.
Life Cycle Cost Analysis
Architects can assist building owners and operators to understand the long-term financial commitment implied by their up-front capital investment in a building. Life cycle cost analyses are often used to demonstrate the return on investments of various energy-conserving strategies which may be under consideration for the project. The viability of leasing instead of building may also be shown by this kind of study.
Functional Programming
Functional programs may also be called design briefs, facilities programs, building programs, architectural programs, statements of requirements, space needs or, simply, programs. Regardless of the title, the purpose of a program is to identify the problem to be solved by asking fundamental questions, such as:
1) What are the client’s needs and objectives?
2) What is the scope of the project?
3) How much and what type of space is needed?
4) What kind of site is needed?
5) How will the spaces and systems relate to one another?
6) How will the facility adapt over time?
7) What other information is required to develop a proper architectural response? What are other constraints?
In preparing a functional program, the architect examines the client’s world in detail to uncover the cost, time, performance and formal criteria for evaluating later design solutions. When an architect reviews a program provided by a client, the architect must comprehensively, tactfully and proactively comment on the program to identify challenges, conflicts and risks.
The programming process seeks to answer the following questions:
1) What is the nature and scope of the project parameters, needs and opportunities?
2) What information is required to develop a proper architectural response?
3) How much and what type of space is needed?
- What space will be needed in the next five to 10 years or longer to continue to operate efficiently?
Preparing a functional program
A program may be a simple summarizing spreadsheet, or an exhaustive document which captures extensive information and data. As such, the architect should understand the client’s requirements and negotiate an appropriate scope, additional to any “basic” services being provided to the client. The time and money invested in programming will provide the design team and stakeholders with a clear idea of a building’s purpose, resulting in more effective design solutions.
During this iterative process, architects typically observe, document and analyze the uses intended within the prospective building.
- The user, functional areas, volumes per activity, precedents.
Additionally, the architect must also consider how the program relates to other external factors
- The site, environment, local infrastructure, regulatory…
With this information, the architect can then develop approximate floor areas, and document any special technical considerations
- Critical dimensions, durability, hardware requirements…
The process of functional programming results in a report which typically includes items such as:
1) the client’s goals and values
2) a stakeholder “charter” describing the shared vision and design principles for the project
3) itemized site requirements, such as parking, circulation, orientation, transportation and accessibility
4) a summary table of space types and areas (see Table 1 below)
5) detailed space data sheets (see Table 2 below), which include information such as: Activities, separations, special technical requirements per space.
6) a space-relationship (or “bubble”) diagram (see Figure 2) which graphically depicts:
- the relative sizes of spaces and their relationships to one another
- the primary entry, egress and circulation patterns
- any site considerations which the design should respond to, such as solar orientation, views, prevailing winds and noise
7) financial requirements, projected cash-flows, anticipated life cycle costs and a preliminary budget
8) project phasing, scheduling and milestones
9) a regulatory approvals strategy, including land use, building code and other applicable restrictions
10) a proposed procurement and project delivery method
11) community goals and concerns
12) ecological and environmental concerns
13) a recommended construction project delivery method