IGES

IGES
US Government (NIST), traced by User:Stannered · Public domain · source
Name	IGES
Developer	U.S. Department of Defense; Electronic Industries Association
Released	1970s
Latest release	Version 5.3 (1996)
Programming language	N/A
Operating system	Cross-platform
File extension	.igs, .iges
Genre	CAD data exchange

Contents

Introduction
History and Development
File Format and Structure
Applications and Industry Use
Advantages and Limitations
Compatibility and Conversion
See also

IGES

IGES is a standardized file format and protocol for the exchange of digital product data among computer-aided design and manufacturing systems. It was created to enable interoperability among disparate systems used by aerospace, automotive, shipbuilding, and electronics firms, linking design environments such as Boeing, General Dynamics, Lockheed Martin, Raytheon Technologies, and contractors working with agencies like the U.S. Department of Defense and the National Aeronautics and Space Administration. The format facilitated data transfer between systems from vendors like Auto-trol Technology, IBM, Intergraph, Elliott, and later commercial products from Dassault Systèmes, Siemens PLM Software, and PTC.

Introduction

IGES (Initial Graphics Exchange Specification) provides a neutral, vendor-independent mechanism to represent 2D vector graphics, 3D geometry, wiring harnesses, and annotation metadata in a plain-text exchange file. It served as a practical bridge among proprietary systems such as CATIA, Unigraphics, Pro/ENGINEER, SolidWorks, and legacy CAD environments developed at research institutions including MIT and Stanford University. IGES files commonly use the extensions .igs or .iges and encode entities like curves, surfaces, and assemblies to facilitate downstream processes at manufacturers like Ford Motor Company, General Motors, and Toyota.

History and Development

Work on IGES began in the 1970s under the auspices of the U.S. Department of Defense to reduce costly data translation between contractors and suppliers during procurement programs such as those managed by DARPA and NAVSEA. Early development involved industry groups and standards bodies including the Electronic Industries Alliance and technical contributors from Bell Labs, Lockheed, and university research labs. The specification evolved through iterative committee work and public review, culminating in formal releases and updates coordinated with organizations like the National Institute of Standards and Technology and international partners such as IEC-aligned entities. IGES influenced later standards efforts exemplified by STEP (ISO 10303), and its stewardship intersected with initiatives from ANSI and ISO committees addressing product data representation.

File Format and Structure

An IGES file is organized into designated sections—Start, Global, Directory Entry, Parameter Data, and Terminate—each carrying records that conform to fixed-column formatting and free-form parameter lists. The Global section contains metadata referencing organizations like Airbus, Northrop Grumman, and Boeing that might appear in cross-company exchanges. Directory Entry records enumerate entities (e.g., lines, arcs, B-spline surfaces) and point to the Parameter Data where entity definitions reside. The format supports explicit boundary representation entities used by systems such as Nastran and ANSYS, as well as annotation primitives compatible with plotting systems from Hewlett-Packard and rasterizers used by Adobe Systems.

Applications and Industry Use

Industry adoption of IGES was strongest in sectors with long supply chains and multi-vendor toolchains: aerospace programs at Boeing and Airbus, automotive platforms at Ford Motor Company and Daimler AG, and ship design at Newport News Shipbuilding. Contract manufacturers and tooling shops used IGES to receive geometry for machining centers by vendors like Fanuc and Mitsubishi Heavy Industries. Electronic design groups interfaced IGES with photoplotters and CAD/CAM suites from Siemens and Mentor Graphics; research laboratories at Sandia National Laboratories and Lawrence Livermore National Laboratory exploited IGES for multidisciplinary modeling. Additionally, standards organizations and procurement authorities in institutions such as European Space Agency and NASA referenced IGES in interoperability guidelines.

Advantages and Limitations

Advantages: IGES offered vendor neutrality that reduced translation expenses among firms such as General Electric and Siemens Energy, and it provided explicit human-readable representations enabling debugging and archival of design intent by archives like the Smithsonian Institution. The plain-text structure allowed simple parsing by utilities on hosts such as DEC VAX and Sun Microsystems workstations.

Limitations: IGES lacks full support for modern feature-based design intent found in systems like PTC's early kernels and does not standardize parametric history used by SolidWorks and Autodesk Inventor. Complex topology and assembly semantics sometimes suffered lossy conversion, causing interoperability problems in multi-domain programs overseen by DOE or multinational consortia such as SESAR. The standard’s textual and fixed-format heritage imposes verbosity and ambiguity relative to more structured specifications like STEP.

Compatibility and Conversion

Many CAD vendors and standalone utilities provide import/export translators between IGES and native formats used by CATIA, NX (Unigraphics), Creo, and SolidWorks. Conversion tools from third-party providers such as TransMagic and legacy translator suites from Elysium automate healing of topology and reparameterization to recover features for downstream simulation with MSC Software and Altair. Interchangeability is improved by using neutral translators and intermediary formats like STEP (ISO 10303), or by applying quality-check suites recommended by procurement agencies such as DEF STAN and MIL-STD programs.