Jump to content

Form, fit and function

From Wikipedia, the free encyclopedia

This is the current revision of this page, as edited by Викидим (talk | contribs) at 17:32, 27 September 2024 (Reverted 1 edit by 69.174.134.3 (talk) to last revision by Citation bot). The present address (URL) is a permanent link to this version.

(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

Form, Fit, and Function (also F3 or FFF) is a concept used in various industries, including manufacturing, engineering, and architecture, to describe aspects of a product's design, performance, and compliance to a specification. F3 originated in military logistics to describe interchangeable parts: if F3 for two components have the same set of characteristics, i.e. they have the same shape or form, same connections or fit, and perform the same function, they can be substituted one for another.[1] The idea behind F3 is to contractually require the original manufacturer to provide the customer (US government) with the free use of F3 data so that the customer can second source the part and thus enable competition between multiple suppliers. In practice, F3 is usually used not for final products (like entire weapon systems), but for the procurement of components and subsystems.[2]

FFF refers to a set of characteristics or requirements that are essential for the design and compatibility of products, components, or systems, and can have legal considerations in regulated industries like aviation and defense (e.g., for technical data rights and configuration management).[3][4][5]

The concept originates in the 1960s, and in some cases called "form-fit-function".[6] The United States (US) Government formally recognized it in the legal incorporation of Public Law 98-525 regarding technical data and design changes.[7] F3 can also refer to the ability of a replacement unit or technology upgrade to be compatible with existing systems, or be compatible with change control procedures (e.g., NASA's use in reliability via military standards).[8][9][10]

Alternate Uses

[edit]

Some organizations have supplemental considerations for F3. The United States Navy has been using Form, Fit, Function, and Interface (F3I) since the 1970s, and NASA has published references to Form, Fit, Function, and Reliability to facilitate reliable designs.[11][12][13]

Definitions

[edit]

In the Code of Federal Regulations - US Government

[edit]

Source:[14]

Form The form of a commodity is defined by its configuration (including the geometrically measured configuration), material, and material properties that uniquely characterize it. For software, the form means the design, logic flow, and algorithms.

Fit The fit of a commodity is defined by its ability to physically interface or connect with or become an integral part of another commodity. For software, the fit is defined by its ability to interface or connect with a defense article.

Function The function of a commodity is the action or actions it is designed to perform. For software, the function means the action or actions the software performs directly related to a defense article or as a standalone application.

References

[edit]
  1. ^ Moore, James W. (May–Jun 1994). "Structure for a Defense Software Reuse Marketplace". ACM Ada Letters. XIV (3): 88. doi:10.1145/181468.181473.
  2. ^ Deets 1985, Abstract.
  3. ^ "Title 48, Chapter 2, Subchapter H, Part 252, Subpart 252.2, Section 252.227-7015". Electronic Code of Federal Regulations. Retrieved 2023-10-14.
  4. ^ "Chapter 11: Configuration Management". GlobalSpec. Retrieved 2023-10-14.
  5. ^ "NASA Procedural Requirements: Configuration Management". NASA. Retrieved 2023-10-14.
  6. ^ "Form-Fit-Function" (PDF). Defense Technical Information Center. Retrieved 2023-10-14.
  7. ^ "Public Law 98-525" (PDF). U.S. Government. Retrieved 2023-10-14.
  8. ^ "Commercial Plastic Microcircuits: A Total Solution For Military Applications" (PDF). NASA. Retrieved 2023-10-14.
  9. ^ "Quick Search Document: 69354". Defense Logistics Agency. Retrieved 2023-10-14.
  10. ^ "Quick Search Document: 67840". Defense Logistics Agency. Retrieved 2023-10-14.
  11. ^ "NASA Systems Engineering Handbook" (PDF). NASA. Retrieved 2023-10-14.
  12. ^ "Configuration Management" (PDF). Defense Technical Information Center. Retrieved 2023-10-14.
  13. ^ "NAVAIR Configuration Management Policy Manual" (PDF). AcqNotes. Retrieved 2023-10-14.
  14. ^ "Title 22, Chapter I, Subchapter M, Part 120, Subpart C, Section 120.42". Electronic Code of Federal Regulations. Retrieved 2023-10-14.

Sources

[edit]