 |
| Purchase Information |
| Use this form to request purchase information on TECHAMERICA online subscriptions. |
|
|
Document TECHAMERICA EIA-649-A is offered by IHS as part of an online subscription. This subscription contains many documents on the same topic.
You may also purchase this document alone from the IHS Standards Store.
TECHAMERICA EIA-649-A Document Information:
Title
National Consensus Standard for Configuration Management
TechAmerica
Publication Date:
Oct 28, 2004
Scope:
This standard defines Configuration Management (CM) terminology and
describes a CM process using
five CM functions and their underlying fundamental principles.
The extent and degree of rigor of CM implementation is commensurate
with the type of product and
its application environment. A complex product such as an electronic
system, a military weapon, or
other product that must be supported over the complete product life
cycle and therefore requires a
robust CM approach. A simpler CM process may be applied to non-complex
products and still maintain
the needed consistency between essential requirements, product
configuration information and the
product.
The degree to which the CM principles in this standard apply to a
product varies over the product's
life cycle. Some principles may not apply during every phase of the
product's life cycle.
The HB-649 provides the information on planning and implementing CM
practices commensurate with
each applicable CM principle appropriate for the product environment.
NOTE: HB-649 is in draft at the time of publication of this EIA 649
revision.
This standard is not intended for use as a compliance document for CM
programs. However, it is
intended for use as a source and reference document. Appropriate
application of the functions and
principles in this standard will enable the user to plan and implement
a CM program for a product,
project, or enterprise.
References to terms such as the enterprise, performing activity,
developing activity, or producing
activity refer to that organization or agency that has the
responsibility for performing
Configuration Management for a product during some period of its life
cycle. This organization
could be a commercial enterprise, a contractor, a subcontractor, or a
government agency. References
to the customer should be interpreted as the organization(s) that
specify requirements (performance
attributes) for the product or those that acquire and use the product.
A customer may be external
to the developing and producing organization, or may be an internal
customer such as marketing,
management, or the using department. In Table 1, the life cycle of a
product has been broken into
different phases with a generic title and characteristic for each
phase. These phase names are
intended to be as generic as possible so that they can be easily
mapped to the myriad of different
life cycle models in use. To encompass this broad range of
environments, Table 1 illustrates some
of the aliases for each phase and identifies a few aliases or
characteristics that may apply in
more than one product life cycle phase.
Configuration Management functions related to a product may be the
responsibility of several
organizations during its life cycle. For example, one organization
with the responsibility to
design and build a product will perform Configuration Management
during the definition and build
phases; a second organization with responsibility for upgrading the
product and servicing units
will perform Configuration Management during the operation phase.
Regardless of the titles chosen for these phases, or whether the
product is a facility, computer
software, an airplane or a machine screw, at some time in its history
a product will go through all
or most of these phases. The phases can have considerable overlap, or
the sequence of the phases
might change or be repeated; e.g., re-commissioning. Approved
configurations of a product can be in
build, distribution, operation, and disposal phases simultaneously.
Changes to approved
configurations can be occurring simultaneously during any life cycle
phase.
Aliases for the neutral terms used in this standard are provided Table
2, Table of Common Aliases.
There is no intent to express preference for any particular
terminology set. When planning and
documenting a CM program, these terms and other aliases may be
substituted for the neutral
terminology.
About IHS
IHS (NYSE: IHS) is a leading global provider of critical technical information, decision-support tools and related services in a number of industries including aerospace and defense, automotive, construction, electronics, and energy. IHS serves customers ranging from large governments and multinational corporations to smaller companies and technical professionals in more than 100 countries. IHS been in business for more than 45 years and employ more than 2,300 people around the world.
