Standard Practice for Constructing FAST Diagrams and Performing Function Analysis During Value Analysis Study

SCOPE
1.1 This practice covers a logical structure for the function analysis of a building project or process.
1.2 This practice provides a system to identify unnecessary costs of a project.
1.3 The values stated in SI units are to be regarded as the standard. The inch-pound units given in parentheses are for information only.
1.4 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use.

General Information

Status
Historical
Publication Date
09-Apr-1999
Technical Committee
Drafting Committee
Current Stage
Ref Project

Relations

Buy Standard

Standard
ASTM E2013-99 - Standard Practice for Constructing FAST Diagrams and Performing Function Analysis During Value Analysis Study
English language
17 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


NOTICE: This standard has either been superseded and replaced by a new version or withdrawn.
Contact ASTM International (www.astm.org) for the latest information
An American National Standard
Designation:E2013–99
Standard Practice for
Constructing FAST Diagrams and Performing Function
Analysis During Value Analysis Study
This standard is issued under the fixed designation E 2013; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (e) indicates an editorial change since the last revision or reapproval.
1. Scope 4.3 Function analysis helps design professionals justify the
value of their concepts. It also provides the owners/users/
1.1 This practice covers a logical structure for the function
stakeholders with a justification of their investments.
analysis of a building project or process.
1.2 This practice provides a system to identify unnecessary
5. Significance and Use
costs of a project.
5.1 This practice establishes a communication format
1.3 The values stated in SI units are to be regarded as the
through which all owners/users/stakeholders can understand,
standard. The inch-pound units given in parentheses are for
analyze, revise, and agree on the purposes of the project. This
information only.
practice presents a method by which owners’/users’/
1.4 This standard does not purport to address all of the
stakeholders’ needs and desires are compared to the cost to
safety concerns, if any, associated with its use. It is the
satisfy those needs and desires. This is done by identifying the
responsibility of the user of this standard to establish appro-
low preference/high cost functions and high preference/low
priate safety and health practices and determine the applica-
cost functions. These data will be used in the value analysis
bility of regulatory limitations prior to use.
study as a basis to create alternative solutions.
2. Referenced Documents 5.2 This practice helps developers, owners, users, stake-
holders, planners, contractors, architects, engineers, value ana-
2.1 ASTM Standards:
lysts,costprofessionals,andanyonewhoisresponsibleforthe
E 833 Terminology of Building Economics
budget, construction, maintenance, or operation of the project.
E 917 PracticeforMeasuringLife-CycleCostsofBuildings
5.3 A Practice E 1699 has been published. As part of the
and Building Systems
value analysis study, perform function analysis after the
E 1557 Classification for Building Elements and Related
collectionofrelevantinformationandpriortotheidentification
Sitework - UNIFORMAT II
of alternatives. FAST data helps the user identify the alterna-
E 1699 Practice for Performing Value Analysis (VA) of
tives that are highly valued with respect to their cost.
Buildings and Building Systems
6. Procedure
3. Terminology
6.1 Function analysis consists of five sequential steps: (1)
3.1 Definitions:
select a building component, (2) define the needs and desires
3.1.1 For definitions of terms used in this practice, refer to
(functions), (3) classify functions, (4) allocate cost to each
Terminology E 833.
function, and (5) analyze the importance and expected “per-
4. Summary of Practice
formance level” of the functions.
6.2 Selection of a Building Component—For cost-
4.1 This practice provides an organized approach for deter-
effectiveness, select building components that offer a signifi-
mining the needs and desires of the owners/users/stakeholders
cant opportunity for improvement of performance, reduction in
during the Value Analysis (VA) of a project. These needs and
cost, or both.
desires are presented as functions of the project.
6.3 Definition of Needs and Desires (Functions)—Define
4.2 This practice establishes a logical procedure for allocat-
eachsignificantneedordesireoftheowners/users/stakeholders
ing cost to each function.
in two words using an active verb and a descriptive noun. The
two-word definitions are the functions of the project.
ThispracticeisunderthejurisdictionofASTMCommitteeE-6onPerformance
6.4 Classification of Functions—Categorizethefunctionsof
of Buildings and is the direct responsibility of Subcommittee E06.81 on Building
thebuildingcomponentasbasic(essentialtomeettheowners’/
Economics.
users’/stakeholders’ needs) or supporting (enhances the satis-
Current edition approved April 10, 1999. Published August 1999.
faction of the owners’/users’/stakeholders’ needs and desires).
Annual Book of ASTM Standards, Vol 04.07.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.
E2013–99
FIG. 1 Function Analysis Systems Technique (Technical FAST)
6.5 Distribution of Cost to Functions—Divide cost of each 6.6.2.2 There are four important concepts in a Technical
component into smaller sections based on the specific use of FAST diagram:
the project and distribute cost to each function.
1. 9How-Why9 Logic Questions
6.6 Analysis of Functions:
2. Scope Line
6.6.1 Analyze functions through a structured logical format
 Higher Order Function
called FunctionAnalysis Systems Technique (FAST). FAST is
 Basic Function
 Required Secondary Functions
a diagramming technique which specifically illustrates the
 Causative Function
relationships and interrelationships of all functions within a
specific project using a “How-Why” logic pattern. There are 3. Critical Functions
two FAST variations.
4. Supporting Functions
6.6.2 One variation, known as Technical FAST, develops a
 Design Objectives
critical path to define the basic needs of the project. This  All The Time Functions
 Caused-by/Same-time Functions
diagramhelpstheusercalculatetheratiooftotalcosttocritical
functions.
6.6.2.3 Function analysis requires analyzing why a function
6.6.2.1 Technical FAST diagramming is effective in a spe-
exists and how a function satisfies other functions to complete
cific situation or element within a project. The situation or
the link between them. This “How-Why” logic assures that all
element is an assembly or a portion of a construction design.
the required functions are listed in the FAST diagram.
Terms or functions are oriented to technical activities. A
6.6.2.4 Begin the Technical FAST diagramming with a
Technical FASTdiagram has a specific structural form (Fig. 1).
higher order function of the project and two scope lines. All
“FunctionAnalysis-The Stepping Stone to Good Value,” Snodgrass, Thomas J.
Certification Examination Guidelines, SAVE International, Northbrook, IL. and Kasi, Muthiah, University of Wisconsin, Madison, 1983.
E2013–99
FIG. 2 Function Analysis System Technique (Task-Oriented FAST)
functions that the selected element fulfills are bounded by the becomes a required secondary function. Once the basic func-
two scope lines. The basic function is on the right of the tion is verified, the remaining required secondary functions are
left-handscopeline,andthehigherorderfunctionisontheleft. identified. This group makes up the critical functions.
The purpose of the element or project for which a FAST 6.6.2.6 The last group of functions is supporting functions.
diagram is developed is the higher order function. The rela- There are three types. The first type, “caused by”or“same
tionship between the higher order function and the basic time” functions, connects directly to a critical function. These
function is determined by asking “Why” the basic function functions result from the performance characteristics of par-
candidate performs as it does.The answer should be the higher ticular critical functions and act as modifiers. The second type,
order function. The logic check must be completed by asking “all the time functions,” modifies two or more of the critical
“How” the higher order function performs. The logical answer functions.Thethirdtype,“design objectives,”representsspeci-
must be the basic function candidate. It is still necessary to fications that are added to the design, often by the stakeholder
confirm the required secondary function to the left of the or group that is developing or operating the process.
right-hand scope line. When the “How” question is asked of 6.6.3 The second variation, known as Task-oriented FAST,
this function, the answer will be an outside function candidate. creates distinct functions for owners’/users’/stakeholders’ con-
The outside function is called the causative function, since it cerns and is always headed by four primary functions: (1)
really starts the critical functions. assure dependability, (2) assure convenience, (3) satisfy
6.6.2.5 Determining the basic function often requires select- owners/users/stakeholders, and (4) attract owners/users/
ing functions from the list of suggestions and applying the stakeholders.
“How” and “Why” questions. If the “Why” question is 6.6.3.1 The Task-oriented FAST diagram logically displays
answered by another identified function, that function is the the owners’/users’/stakeholders’ needs and desires (see Fig. 2).
next candidate for the basic function. The function to the right Task-oriented FAST diagramming is especially effective in the
E2013–99
planning or conceptual phase. Use conceptual layout and 6.6.6.3 Makes the element appear to be better in the opinion
building plans to develop these FAST diagrams. of the stakeholder, but not necessarily in the opinion of the
6.6.3.2 There are four parts to the Task-oriented FAST
designer. (Sometimes these opinions are reflected in the stan-
diagram: dards and specifications of a particular agency/owner.)
1. Task
6.6.7 Attract Owners/Users/Stakeholders—Any function
that attracts owners/users/stakeholders and has at least one of
2. Basic Functions
the following attributes:
 Primary
 Secondary
6.6.7.1 Emphasizes the visual aspect (sight) or other senses,
and
3. Supporting Functions
 Assure Dependability
6.6.7.2 Projects a favorable image (that is, trademarks or
 Assure Convenience
endorsement by public figures).
 Satisfy Owners/Users/Stakeholders
 Attract Owners/Users/Stakeholders
6.6.8 The fourth step is to classify the functions as primary,
secondary, or tertiary.
4. Classify Functions
 Primary
6.6.8.1 The link between the task and basic functions is the
 Secondary
sequence of the logical question “How-Why”. The “How-
 Tertiary
Why” concepts must work between the selected task and the
6.6.3.3 The first step is to determine the task. The task
primary basic functions. These primary basic functions are
satisfies the overall needs of the stakeholder. Establish a scope
interdependent and both are essential to the performance of the
line just to the right of the task. Functions that answer “why
task.
perform the task” lie outside of the scope.
6.6.8.2 Once the primary basic functions have been identi-
6.6.3.4 The second step is to separate the identified func-
fied, the question “How” can be asked of each of the primary
tions into basic and supporting functions. Basic functions are
basicfunctions.Functionsthatanswerthequestion“How”will
those which are essential to the performance of the task.
be found in the expanding branches. These are the secondary
Without the primary basic functions, the project or process will
basic functions. There must be two or more secondary basic
not work.
functions to justify branching from the primary function.
6.6.3.5 The third step is to group the remaining functions
6.6.8.3 In a similar manner, the secondary supporting func-
into the four primary supporting function groups. Supporting
tions branch to the right from the primary supporting functions
functions play an important role in a building. Structural
when the question “How” is applied.Again, there must be two
engineers, for instance, concentrate primarily on the basic
or more secondary functions to justify branching.
functions, with heavy emphasis on the primary supporting
function “Assure Dependability.” Mechanical engineers and
6.6.8.4 This rule also affects further branching off to the
electrical engineers pay more attention to the supporting
third (tertiary) level. Usually, the tertiary level completes the
function “Assure Convenience,” while architects’ ideas satisfy
branchingbasicfunctions.Theendofthebranchingisobtained
the basic and supporting functions “Satisfy Owners/Users/
when the hardware description or action is the noun of the
Stakeholders” and “Attract Owners/Users/Stakeholders.”
function.The branches must also satisfy the“Why” question in
6.6.4 Assure Dependability—Any function that assures de-
the opposite direction, that is, logic check.
pendability has at least one of the following attributes:
6.6.9 Cost Estimate:
6.6.4.1 Makes the elements of the project stronger or more
6.6.9.1 Obtain cost estimates for the proposed building
reliable or effective,
components and related sitework. Classification E 1557 pro-
6.6.4.2 Makes it safer to use,
vides a useful format for allocating cost to functions.
6.6.4.3 Lengthens the life of the parts or minimizes main-
6.6.10 Function Cost:
tenance cost, or both, and
6.6.10.1 Mostcomponentsofabuildinghavemorethanone
6.6.4.4 Protects the environment.
function to satisfy. Distribute cost of each component to each
6.6.5 Assure Convenience—Any function that assures con-
one of these functions, proportionate to their time cost. Use the
venience has at least one of the following attributes:
elemental format, UNIFORMAT II, for the development of
6.6.5.1 Modifies the basic function to make it convenient to
cost estimates.This expedites the completion of function costs.
use,
Allocate all life-cycle costs, including first cost, operation cost
6.6.5.2 Enhances spatial arrangements,
and maintenance cost.
6.6.5.3 Facilitates maintenance and repairs, and
6.6.10.2 Whencostisdistributedtoallfunctions,reviewthe
6.6.5.4 Furnishes instructions and directions to owners/
users/stakeholders. total distribution. In the Technical FAST, the ratio of total cost
6.6.6 Satisfy Owners/Users/Stakeholders—Any function to the cost of critical functions is called the value index. The
that satisfies owners/users/stakeholders has at least one of the value index varies from 1.5 to 6.0.As this ratio gets higher, the
following attributes: opportunity to reduce cost is higher for the selected compo-
6.6.6.1 Modifies the basic function to satisfy the individual nent. A value index of 1.5 means a very basic design with
desires, minimum cost of supporting functions. If most of the total cost
6.6.6.2 Makes the stakeholders’ life more pleasant; for is spent on critical functions, the value index is approximately
example, minimizes noise, and 1.5. The construction of a fast food restaurant, for example,
E2013–99
TABLE 1 Illustration of Cost Distribution TABLE 2 Illustrat
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.