Jump to content

Integrated Computer-Aided Manufacturing: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
m clean up, typos fixed: Archictecture → Architecture using AWB
m clean up spacing around commas and other punctuation fixes, replaced: ,A → , A
 
(28 intermediate revisions by 23 users not shown)
Line 1: Line 1:
:''This article is about a specific US Air Force program. For general information see [[Computer-Aided Manufacturing]]''
{{about|a specific US Air Force program|general information|computer-aided manufacturing}}
[[File:Integrated Computer Aided Manufacturing.jpg|thumb|Online operations and support operations in an Integrated Computer Aided Manufacturing environment, 1977]]

'''Integrated Computer-Aided Manufacturing''' (ICAM) is a [[United States Air Force|US Air Force]] program to develop tools, techniques, and processes to support [[manufacturing]] integration and has influenced the [[Computer Integrated Manufacturing]] (CIM) and [[Computer Aided Manufacturing]] (CAM) project efforts of many companies.
'''Integrated Computer-Aided Manufacturing''' ('''ICAM''') is a [[United States Air Force|US Air Force]] program that develops tools, techniques, and processes to support [[manufacturing]] integration. It influenced the [[computer-integrated manufacturing]] (CIM) and [[computer-aided manufacturing]] (CAM) project efforts of many companies.
The ICAM program was founded in 1976 and initiative managed by the [[United States Air Force|US Air Force]] at [[Wright-Patterson Air Force Base|Wright-Patterson]] as a part of their technology modernization efforts. The program initiated the development a series of standards for modeling and analysis in management and business improvement, called ''Integrated Definitions'', short [[IDEF]]s.
[[Image:IDEF Methods.jpg|thumb|360px|Overview of the [[IDEF]] methods developed in the ICAM program.<ref>Richard J. Mayer (1995). [http://www.idef.com/pdf/compendium.pdf Information Integration for Concurrent Engineering (IICE) Compendium of methods report]. Knowledge Based Systems, Inc. 1995.</ref>]]
The ICAM program was founded in 1976 and initiative managed by the [[United States Air Force|US Air Force]] at [[Wright-Patterson Air Force Base|Wright-Patterson]] as a part of their technology modernization efforts. The program initiated the development a series of standard for modeling and analysis in management and business improvement, called ''Integrated Definitions'', short [[IDEF]]s.


== Overview ==
== Overview ==
The USAF ICAM program was founded in 1976 at the US [[Air Force Materials Laboratory]], Wright-Patterson Air Force Base in Ohio by [[Dennis E. Wisnosky]] and Dan L. Shunk and others.<ref name="Sav96"> Charles M. Savage (1996). ''Fifth Generation Management : Co-creating Through Virtual Enterprising, Dynamic Teaming, and Knowledge Networking'' Butterworth-Heinemann, 1996. ISBN 0750697016. p. 184.</ref> In the mid-1970s Joseph Harrington <ref>Joseph Harrington (1984). ''Understanding the Manufacturing Process''.</ref> had assisted Wisnosky and Shunk in designing the ICAM program and had broadened the concept of [[CIM]] to include the entire manufacturing company. Harrington considered manufacturing a "monolithic function".<ref name="Sav96"/>
The USAF ICAM program was founded in 1976 at the US [[Air Force Materials Laboratory]], Wright-Patterson Air Force Base in Ohio by [[Dennis E. Wisnosky]] and Dan L. Shunk and others.<ref name="Sav96">Charles M. Savage (1996). ''Fifth Generation Management : Co-creating Through Virtual Enterprising, Dynamic Teaming, and Knowledge Networking'' Butterworth-Heinemann, 1996. {{ISBN|0-7506-9701-6}}. p. 184.</ref> In the mid-1970s Joseph Harrington <ref>Joseph Harrington (1984). ''Understanding the Manufacturing Process''.</ref> had assisted Wisnosky and Shunk in designing the ICAM program and had broadened the concept of [[Computer Integrated Manufacturing|CIM]] to include the entire manufacturing company. Harrington considered manufacturing a "monolithic function".<ref name="Sav96"/>


The ICAM program was visionary in showing that a new approach was necessary to achieve integration in manufacturing firms. Wisnosky and Shunk developed a "wheel" to illustrate the architecture of their ICAM project and to show the various elements that had to work together. Wisnosky and Shunk were among the first to understand the web of interdependencies needed for integration. Their work represents the first major step in shifting the focus of manufacturing from a series of sequential operations to parallel processing.<ref name="Sav96"/>
The ICAM program was visionary in showing that a new approach was necessary to achieve integration in manufacturing firms. Wisnosky and Shunk developed a "wheel" to illustrate the architecture of their ICAM project and to show the various elements that had to work together. Wisnosky and Shunk were among the first to understand the web of interdependencies needed for integration. Their work represents the first major step in shifting the focus of manufacturing from a series of sequential operations to parallel processing.<ref name="Sav96"/>


The ICAM program has spent over $100 million to develop tools, techniques, and processes to support manufacturing integration and has influenced the CIM project efforts of many companies. The Air Force's ICAM program recognizes the role of data as central to any integration effort. ''Data is to be common and shareable across functions.'' The concept still remains ahead of its time, because most major companies will not seriously begin to attack the data architecture challenge until well into the 1990s. The ICAM program also recognizes the need for ways to analyze and document the major activities performed within the manufacturing establishment. Thus, from ICAM came the IDEFs, the standard for modeling and analysis in management and business improvement efforts. [[IDEF]] means ICAM DEFinition.<ref name="Sav96"/>
The ICAM program has spent over $100 million to develop tools, techniques, and processes to support manufacturing integration. The Air Force's ICAM program recognizes the role of data as central to any integration effort. ''Data must be common and shareable across functions.'' The concept still remains ahead of its time, because most major companies did not seriously begin to attack the data architecture challenge until well into the 1990s. The ICAM program also recognizes the need for ways to analyze and document major activities within the manufacturing establishment. Thus, from ICAM came the IDEFs, the standard for modeling and analysis in management and business improvement efforts. [[IDEF]] means ICAM DEFinition.<ref name="Sav96"/>


== The impact ==
== The impact ==
[[File:IDEF Methods.svg|thumb|Overview of the [[IDEF]] methods developed in the ICAM program.<ref>[[Richard J. Mayer]] (1995). [http://www.idef.com/pdf/compendium.pdf Information Integration for Concurrent Engineering (IICE) Compendium of methods report]. Knowledge Based Systems, Inc. 1995.</ref>]]

=== Standard data models ===
=== Standard data models ===
In order to get real meaning out of the [[data]]<ref name="Bar89"> Edward J. Barkmeyer (1989). [http://www.nist.gov/msidlibrary/doc/barkmeyer89b.ps "Some Interactions of Information and Controlin Integrated Automation Systems"]. U.S. National Bureau of Standards.</ref>, we must also have formulated, and agreed on, a model of the world the data describes. We now understand that this actually involves two different kinds of model<ref>Brodie, M., Mylopoulos, J., Schmidt, J.W., editors (1984). ''On Conceptual Modeling''. Springer-Verlag, New York</ref>:
To extract real meaning from the [[data]],<ref name="Bar89">Edward J. Barkmeyer (1989). [https://www.nist.gov/msidlibrary/doc/barkmeyer89b.ps "Some Interactions of Information and Controlin Integrated Automation Systems"]. U.S. National Bureau of Standards.</ref> we must also have formulated, and agreed on, a model of the world the data describes. We now understand that this actually involves two different kinds of model:<ref>Brodie, M., [[John Mylopoulos|Mylopoulos, J.]], Schmidt, J.W., editors (1984). ''On Conceptual Modeling''. Springer-Verlag, New York</ref>
* the static associations between the data and the real-world physical and conceptual objects it describes, called the [[information model]], and
* Static associations between data and real-world physical and conceptual objects it describes—called the [[information model]]
* the rules for the use and modification of the data, which are derived from the dynamic characteristics of the objects themselves, called the [[functional model]].
* Rules for use and modification of the data, which derive from the dynamic characteristics of the objects themselves—called the [[functional model]]


The significance of these models to data interchange for manufacturing and materials flow was recognized early in the Air Force Integrated Computer Aided Manufacturing (ICAM) Project and gave rise to the IDEF formal modeling project.<ref>"ICAM Conceptual Design for Computer Integrated Manufacturing Framework Document", Air Force Materials Laboratory, Wright Aeronautical Laboratories, USAF Systems Command, Wright-Patterson Air Force Base, OH, 1984</ref>. IDEF produced a specification for a formal [[functional model]]ing approach ([[IDEF0]]) and an [[information model]]ing language ([[IDEF1]]).<ref>"ICAM Architecture Part 2, Volume 5: Information Modeling Manual (IDEF1)",AFWAL TR-81-4023, Air Force Materials Laboratory, Wright Aeronautical Laborato-ries, USAF Systems Command, Wright-Patterson Air Force Base, OH, June, 1981</ref> The more recent "Product Data Exchange Specification" (PDES) project in the U.S., the related [[ISO 10303|ISO Standard for the exchange of product model data]] (STEP) and the [[CIMOSA|Computer Integrated Manufacture Open Systems Architecture]] (CIMOSA) [ISO87] project in the European Economic Community have whole heartedly accepted the notion that useful data sharing is not possible without formal [[semantic data model]]s of the context the data describes.<ref name="Bar89"/>
The significance of these models to data interchange for manufacturing and materials flow was recognized early in the Air Force Integrated Computer Aided Manufacturing (ICAM) Project and gave rise to the IDEF formal modeling project.<ref>"ICAM Conceptual Design for Computer Integrated Manufacturing Framework Document", Air Force Materials Laboratory, Wright Aeronautical Laboratories, USAF Systems Command, Wright-Patterson Air Force Base, OH, 1984</ref> IDEF produced a specification for a formal [[functional model]]ing approach ([[IDEF0]]) and an [[information model]]ing language ([[IDEF1]]).<ref>"ICAM Architecture Part 2, Volume 5: Information Modeling Manual (IDEF1)", AFWAL TR-81-4023, Air Force Materials Laboratory, Wright Aeronautical Laborato-ries, USAF Systems Command, Wright-Patterson Air Force Base, OH, June, 1981</ref> The more recent "Product Data Exchange Specification" (PDES) project in the U.S., the related [[ISO 10303|ISO Standard for the exchange of product model data]] (STEP) and the [[CIMOSA|Computer Integrated Manufacture Open Systems Architecture]] (CIMOSA) [ISO87] project in the European Economic Community have whole heartedly accepted the notion that useful data sharing is not possible without formal [[semantic data model]]s of the context the data describes.<ref name="Bar89"/>


Within their respective spectra of efforts, each of these projects has a panoply of [[information model]]s for manufactured objects, materials and product characteristics, and for manufacturing and assembly processes. Each also has a commitment to detailed [[functional model]]s of the various phases of [[product life cycle]]. The object of all of these recent efforts is to standardize the interchange of [[information]] in many aspects of product design, manufacture, delivery and support.<ref name="Bar89"/>
Within their respective spectra of efforts, each of these projects has a panoply of [[information model]]s for manufactured objects, materials and product characteristics, and for manufacturing and assembly processes. Each also has a commitment to detailed [[functional model]]s of the various phases of [[Product lifecycle (engineering)|product life cycle]]. The object of all of these recent efforts is to standardize the interchange of [[information]] in many aspects of product design, manufacture, delivery and support.<ref name="Bar89"/>


=== Further research with ICAM Definitions ===
=== Further research with ICAM definitions ===
The research in expending and applying the ICAM Definitions have proceeded. In the 1990s for example the Material Handling Research Center (MHRC) of the [[Georgia Institute of Technology]] and [[University of Arkansas]] had included the it in their Information Systems reseach area. That area focuses on the information that must accompany material movements and the application of artificial intelligence to material handling problems. MHRC's research involves expanding the integrated computer-aided manufacturing definition (IDEF) approach to include the information flow as well as the material flow needed to support a [[manufacturing]] enterprise, as well as models to handle unscheduled events such as machine breakdowns or material shortages. Past research resulted in software to automatically palletize random-size packages, a system to automatically load and unload truck trailers, and an integrated production control system to fabricate optical fibers.<ref>NSF (1997). [http://www.nsf.gov/pubs/1997/nsf9397/nsf9397.txt "Industry/University Cooperative Research Centers: Model Partnerships"]. May 27, 1997.</ref>
The research in expending and applying the ICAM definitions have proceeded. In the 1990s for example the Material Handling Research Center (MHRC) of the [[Georgia Institute of Technology]] and [[University of Arkansas]] had included it in their Information Systems research area. That area focuses on the information that must accompany material movements and the application of artificial intelligence to material handling problems. MHRC's research involves expanding the integrated computer-aided manufacturing definition (IDEF) approach to include the information flow as well as the material flow needed to support a [[manufacturing]] enterprise, as well as models to handle unscheduled events such as machine breakdowns or material shortages. Past research resulted in software to automatically palletize random-size packages, a system to automatically load and unload truck trailers, and an integrated production control system to fabricate optical fibers.<ref>NSF (1997). [https://www.nsf.gov/pubs/1997/nsf9397/nsf9397.txt "Industry/University Cooperative Research Centers: Model Partnerships"]. May 27, 1997.</ref>


== See also ==
== See also ==
Line 33: Line 34:


== Further reading ==
== Further reading ==
* Charles Savage, 1996, ''Fifth Generation Management, Dynamic Teaming, Virtual Enterprising and Knowledge Networking'', page 184, , ISBN 0750697016, Butterworth-Heinemann.
* Charles Savage, 1996, ''Fifth Generation Management, Dynamic Teaming, Virtual Enterprising and Knowledge Networking'', page 184, {{ISBN|0-7506-9701-6}}, Butterworth-Heinemann.
* Joseph Harrington (1984). ''Understanding the Manufacturing Process''. ISBN 978-0824771706
* Joseph Harrington (1984). ''Understanding the Manufacturing Process''. {{ISBN|978-0-8247-7170-6}}


[[Category:Computer-aided design]]
[[Category:Computer-aided design]]
[[Category:Manufacturing]]
[[Category:Software engineering]]
[[Category:Wright-Patterson Air Force Base]]
[[Category:Wright-Patterson Air Force Base]]
[[Category:Computer-aided manufacturing]]

Latest revision as of 14:17, 1 January 2024

Online operations and support operations in an Integrated Computer Aided Manufacturing environment, 1977

Integrated Computer-Aided Manufacturing (ICAM) is a US Air Force program that develops tools, techniques, and processes to support manufacturing integration. It influenced the computer-integrated manufacturing (CIM) and computer-aided manufacturing (CAM) project efforts of many companies. The ICAM program was founded in 1976 and initiative managed by the US Air Force at Wright-Patterson as a part of their technology modernization efforts. The program initiated the development a series of standards for modeling and analysis in management and business improvement, called Integrated Definitions, short IDEFs.

Overview[edit]

The USAF ICAM program was founded in 1976 at the US Air Force Materials Laboratory, Wright-Patterson Air Force Base in Ohio by Dennis E. Wisnosky and Dan L. Shunk and others.[1] In the mid-1970s Joseph Harrington [2] had assisted Wisnosky and Shunk in designing the ICAM program and had broadened the concept of CIM to include the entire manufacturing company. Harrington considered manufacturing a "monolithic function".[1]

The ICAM program was visionary in showing that a new approach was necessary to achieve integration in manufacturing firms. Wisnosky and Shunk developed a "wheel" to illustrate the architecture of their ICAM project and to show the various elements that had to work together. Wisnosky and Shunk were among the first to understand the web of interdependencies needed for integration. Their work represents the first major step in shifting the focus of manufacturing from a series of sequential operations to parallel processing.[1]

The ICAM program has spent over $100 million to develop tools, techniques, and processes to support manufacturing integration. The Air Force's ICAM program recognizes the role of data as central to any integration effort. Data must be common and shareable across functions. The concept still remains ahead of its time, because most major companies did not seriously begin to attack the data architecture challenge until well into the 1990s. The ICAM program also recognizes the need for ways to analyze and document major activities within the manufacturing establishment. Thus, from ICAM came the IDEFs, the standard for modeling and analysis in management and business improvement efforts. IDEF means ICAM DEFinition.[1]

The impact[edit]

Overview of the IDEF methods developed in the ICAM program.[3]

Standard data models[edit]

To extract real meaning from the data,[4] we must also have formulated, and agreed on, a model of the world the data describes. We now understand that this actually involves two different kinds of model:[5]

  • Static associations between data and real-world physical and conceptual objects it describes—called the information model
  • Rules for use and modification of the data, which derive from the dynamic characteristics of the objects themselves—called the functional model

The significance of these models to data interchange for manufacturing and materials flow was recognized early in the Air Force Integrated Computer Aided Manufacturing (ICAM) Project and gave rise to the IDEF formal modeling project.[6] IDEF produced a specification for a formal functional modeling approach (IDEF0) and an information modeling language (IDEF1).[7] The more recent "Product Data Exchange Specification" (PDES) project in the U.S., the related ISO Standard for the exchange of product model data (STEP) and the Computer Integrated Manufacture Open Systems Architecture (CIMOSA) [ISO87] project in the European Economic Community have whole heartedly accepted the notion that useful data sharing is not possible without formal semantic data models of the context the data describes.[4]

Within their respective spectra of efforts, each of these projects has a panoply of information models for manufactured objects, materials and product characteristics, and for manufacturing and assembly processes. Each also has a commitment to detailed functional models of the various phases of product life cycle. The object of all of these recent efforts is to standardize the interchange of information in many aspects of product design, manufacture, delivery and support.[4]

Further research with ICAM definitions[edit]

The research in expending and applying the ICAM definitions have proceeded. In the 1990s for example the Material Handling Research Center (MHRC) of the Georgia Institute of Technology and University of Arkansas had included it in their Information Systems research area. That area focuses on the information that must accompany material movements and the application of artificial intelligence to material handling problems. MHRC's research involves expanding the integrated computer-aided manufacturing definition (IDEF) approach to include the information flow as well as the material flow needed to support a manufacturing enterprise, as well as models to handle unscheduled events such as machine breakdowns or material shortages. Past research resulted in software to automatically palletize random-size packages, a system to automatically load and unload truck trailers, and an integrated production control system to fabricate optical fibers.[8]

See also[edit]

References[edit]

  1. ^ a b c d Charles M. Savage (1996). Fifth Generation Management : Co-creating Through Virtual Enterprising, Dynamic Teaming, and Knowledge Networking Butterworth-Heinemann, 1996. ISBN 0-7506-9701-6. p. 184.
  2. ^ Joseph Harrington (1984). Understanding the Manufacturing Process.
  3. ^ Richard J. Mayer (1995). Information Integration for Concurrent Engineering (IICE) Compendium of methods report. Knowledge Based Systems, Inc. 1995.
  4. ^ a b c Edward J. Barkmeyer (1989). "Some Interactions of Information and Controlin Integrated Automation Systems". U.S. National Bureau of Standards.
  5. ^ Brodie, M., Mylopoulos, J., Schmidt, J.W., editors (1984). On Conceptual Modeling. Springer-Verlag, New York
  6. ^ "ICAM Conceptual Design for Computer Integrated Manufacturing Framework Document", Air Force Materials Laboratory, Wright Aeronautical Laboratories, USAF Systems Command, Wright-Patterson Air Force Base, OH, 1984
  7. ^ "ICAM Architecture Part 2, Volume 5: Information Modeling Manual (IDEF1)", AFWAL TR-81-4023, Air Force Materials Laboratory, Wright Aeronautical Laborato-ries, USAF Systems Command, Wright-Patterson Air Force Base, OH, June, 1981
  8. ^ NSF (1997). "Industry/University Cooperative Research Centers: Model Partnerships". May 27, 1997.

Further reading[edit]

  • Charles Savage, 1996, Fifth Generation Management, Dynamic Teaming, Virtual Enterprising and Knowledge Networking, page 184, ISBN 0-7506-9701-6, Butterworth-Heinemann.
  • Joseph Harrington (1984). Understanding the Manufacturing Process. ISBN 978-0-8247-7170-6