Programming | Planning | Furniture | Let's share | Visit Places

Program Types

Overview

Initialization

Scope and Goals

Data Collection

Space Standards

Detail Listings

Space Summary

Building Feasibility

Data Analysis

Proximity

Space Distribution

Blocking/Layering

Final Program

Develop Data Base and Collect Data

Before any data collection, the programmer first identifies the data base and develops the methodologies for data collection. Through interviews and discussions with the client, the programmer reviews, verifies and filters all data received and resolves any discrepancies that might arise during the process.

Information to be Collected:
The types and the amount of information to be collected vary according to the need, complexity and history of the company. Information list:

  1. Collect company backgound:
    • existing company image
    • nature of business
    • company historical data from 5 to 20 years if available
    • company administrative policies
    • company organization structure
    • personnel hierarchy
    • dramatic changes in the past and their influence

  2. Collect information on all organizational units and subunits
    • existing organizational units and subunit names
    • existing organizational units and subunit codes
    • existing company organization chart showing company structure and relationships of major units or subunits
    • existing personnel organization charts of each organizational unit showing the names of individual users, job categories, hierarchy, and how they relate to each other within each unit.

  3. Collect existing personnel information
    • names of hierarchy levels : executives, managements, mid-managements, low-managements, supervisories, non-supervisories, professionals, non-professionals, non-managements
    • listing of types of spaces: private, semiprivate, open
    • listing of all personnel job categories and how they relate to each hierarchy level
    • listing of existing space standards showing space sizes, furniture sizes, types and area arrangements with assignment to corresponding job categories
    • policies regulating selection options of finishes and accessories with corresponding job categories

  4. Collect existing operational requirements by unit:
    • Listing of personnel requirements by organizational unit showing corresponding job categories and existing space standards assignments
    • listing of support space requirements for work groups within each organizational unit: space size, funiture, equipments, area arrangements and any special conditions
    • listing of special use area requirements within each organizational unit: space size, funiture, equipments area arrangement and any special conditions
    • listing of common use area requirements that are shared by all organizational units on the company level: space size, funiture, equipments area arrangement and special conditions

  5. Collect communication requirements
    • adjacency information between organizational units or subunits
    • adjacency information between common use spaces and the organizational units
    • adjacency information between individuals within each organizational units or subunits
    • adjacency information between support and special use spaces with individuals within each organizational unit or subunits
    • Listing of organizational units and subunits with frequent public contact
    • Listing of organizational units with heavy paper flow
    • Listing of organizational units with frequent telephone, fax or computer contacts

  6. Collect information on existing inventories
    • Document existing furniture and equipments by types, styles, sizes, manufacturers
    • Identify items that are reusable and in good condition
    • Identify items that are reusable but requires refinishing or reupholstering
    • Identify items that are salvageable for resale
    • Identify items that are to be thrown away

  7. Collect personnel history and forecast
    • Collect personnel historical data of each organizational unit and subunit and that of the total company if available
    • Identify significant data that is used for past personnel projection if available
    • Collect personnel forecast from Personnel unit or from Administrative unit
    • Collect personnel forecast from each organizational unit showing specific job categories if available
    • Collect group space forecast if available
    • Identify any issues or use of technology that might affect future personnel and space forecast

  8. Identify constrains, existing and/or anticipated problems
    • Listing of design priorities
    • Listing of budget priorities
    • Identify time schedule
    • Identify quality expectation: expensive, average or economical
    • Identify building constrains: size, shape, location, building modules, mechanical, structural, electrical, communication systems and physicial limitations
    • Identify administrative structure: stable or dynamic
    • Identify company flexibility requirements in the past and future
    • Identify employee productivity
    • Identify new or change of image
    • Listing of existing problems within the organizational units or within the group spaces

Data Collection Techniques
Most consulting firms use similar methodologies to collect the client's data. The common techniques are interviews, questionnaires and observations. Since the data collection process can be quite tedious and timely, the programmer's responsibility is to select the best method or methods suited to the project that allows for speedy completion and interpretation.

1. Observations
The programmer always starts the project with a tour of the client's facility. The tour allows the programmer to note down essential information regarding the client's existing environments, function, operational requirements, special situations and problems. In most cases, it clarifies project requirements and expectations and enable the programmer to get a feel for the project scope and budget.

2. Interviews
Interviews provide programmers a way of collecting qualitative information on users' requirements, clarifies directions, exchange views and resolve discrepancies. Programmer first develops an interview list identifying the individuals or groups for the interviews, the time frame for each and the required information list. The interviews may be repeated many times until the programmer gets all the necessary information. In the case of a small project, the interviews and observations are sufficient for data collection.

Major personnel to interview and available information:

Chairperson of the board and Executives
The Chairperson and executives establish company goals, project overview, company image and mission, company direction, and overall budgets. They are very knowledgeable on general company history, direction, and overall administrative policies.
Personnel director
The personnel director keeps up-to-date records of total company personnel forecasts, personnel policies and administration.
Office or facility director
The facility director and staff manage the needs of the company. They are familiar with the needs of the organizational units, their functions and the personnel requirements. They manage on a daily basis all furniture inventories, yearly replacement budgets, and the building's maintenance requirements.
Organizational units' directors
The director of each organizational unit is knowledgeable on details. They provide more specific personnel forecasts, personnel space requirements, group space requirements, personnel proximity, the unit's proximity with other organizational units and with common shared facilities, and any special environmental, structural, electrical or security situations within each unit.
Individuals with special needs
These are individuals with special furniture, equipment or space needs. Examples are equipment operators, laboratory technicians, security officers, mail carriers, food providers, health care providers and those with physical handicap. Their furniture, equipment or area arrangement might have impacts on furniture selections or the planning of their units.

3. Questionnaires
Programmers develop questionnaire forms to collect quantitative and detail information about the organizational units, the individual users and group spaces. The technique is most common for large scale projects when interviews with individual users are time-consuming or not feasible. Many programmers develop specific questionnaires to collect specific information relating to a company. Others use standard forms developed for past projects that proved to be effective or use those developed by leading furniture manufacturers for general purpose programming.

 return Home
 return to Programming main level
 onto Space Standards
© 1996-2008 Jane Wong. All rights reserved.
Please send comments to: Jane Wong jmwong@ku.edu