ISO 10303

ISO 10303 is an ISO standard for the computer-interpretable representation and exchange of product manufacturing information. Its official title is: Automation systems and integration — Product data representation and exchange. It is known informally as "STEP", which stands for "Standard for the Exchange of Product model data". ISO 10303 can represent 3D objects in Computer-aided design (CAD) and related information.

Overview

The international standard's objective is to provide a mechanism that is capable of describing product data throughout the life cycle of a product, independent from any particular system. The nature of this description makes it suitable not only for neutral file exchange, but also as a basis for implementing and sharing product databases and archiving.[1]

Typically STEP can be used to exchange data between CAD, computer-aided manufacturing, computer-aided engineering, product data management/enterprise data modeling and other CAx systems. STEP addresses product data from mechanical and electrical design, geometric dimensioning and tolerancing, analysis and manufacturing, as well as additional information specific to various industries such as automotive, aerospace, building construction, ship, oil and gas, process plants and others.

STEP is developed and maintained by the ISO technical committee TC 184, Automation systems and integration, sub-committee SC 4, Industrial data. Like other ISO and IEC standards STEP is copyright by ISO and is not freely available. However, the 10303 EXPRESS schemas are freely available, as are the recommended practices for implementers.

Other standards developed and maintained by ISO TC 184/SC 4 are:[2]

  • ISO 13584 PLIB - Parts Library
  • ISO 15531 MANDATE - Industrial manufacturing management data
  • ISO 15926 Process Plants including Oil and Gas facilities Life-Cycle data
  • ISO 18629 PSL- Process specification language
  • ISO 18876 IIDEAS - Integration of industrial data for exchange, access, and sharing
  • ISO 22745 Open technical dictionaries and their application to master data
  • ISO 8000 Data quality

STEP is closely related with PLIB (ISO 13584, IEC 61360).

History

The basis for STEP was the Product Data Exchange Specification (PDES), which was initiated during the mid-1980s and was submitted to ISO in 1988.[3] The Product Data Exchange Specification (PDES) was a data definition effort intended to improve interoperability between manufacturing companies, and thereby improve productivity.[4]

The evolution of STEP can be divided into four release phases. The development of STEP started in 1984 as a successor of IGES, SET and VDA-FS.[5] The initial plan was that "STEP shall be based on one single, complete, implementation-independent Product Information Model, which shall be the Master Record of the integrated topical and application information models".[6] But because of the complexity, the standard had to be broken up into smaller parts that can be developed, balloted and approved separately.[7] In 1994/95 ISO published the initial release of STEP as international standards (IS) with the parts 1, 11, 21, 31, 41, 42, 43, 44, 46, 101, AP 201 and AP 203.[8] Today AP 203 Configuration controlled 3D design is still one of the most important parts of STEP and supported by many CAD systems for import and export.

In the second phase the capabilities of STEP were widely extended, primarily for the design of products in the aerospace, automotive, electrical, electronic, and other industries. This phase ended in the year 2002 with the second major release, including the STEP parts AP 202, AP 209, AP 210, AP 212, AP 214, AP 224, AP 225, AP 227, AP 232.[9] Basic harmonization between the APs especially in the geometric areas was achieved by introducing the Application Interpreted Constructs (AIC, 500 series).

A major problem with the monolithic APs of the first and second releases is that they are too big, have too much overlap with each other, and are not sufficiently harmonized. These deficits led to the development of the STEP modular architecture (400 and 1000 series).[10] This activity was primarily driven by new APs covering additional life-cycle phases such as early requirement analysis (AP 233) and maintenance and repair (AP 239), and also new industrial areas (AP 221, AP 236). New editions of the previous monolithic APs on a modular basis have been developed (AP 203, AP 209, AP 210). The publication of these new editions coincided with the release in 2010 of the new ISO product SMRL, the STEP Module and Resource Library, that contains all STEP resource parts and application modules on a single CD. The SMRL will be revised frequently and is available at a much lower cost than purchasing all the parts separately.

In December 2014 ISO published the first edition of a new major Application Protocol, AP 242 Managed model based 3d engineering, that combined and replaced the following previous APs in an upward compatible way:

  • AP 201, Explicit draughting. Simple 2D drawing geometry related to a product. No association, no assembly hierarchy.
  • AP 202, Associative draughting. 2D/3D drawing with association, but no product structure.
  • AP 203, Configuration controlled 3D designs of mechanical parts and assemblies.
  • AP 204, Mechanical design using boundary representation
  • AP 214, Core data for automotive mechanical design processes

In addition AP242 edition 1 contains extensions and significant updates for

Two APs had been modified to be directly based on AP242 and thus become supersets of it:

  • AP 209, Composite and metallic structural analysis and related design
  • AP 210, Electronic assembly, interconnect and packaging design. The most complex and sophisticated STEP AP.

The development of a second edition of AP242 has started which is extending the scope for electrical harness.

Structure

STEP is divided into many parts, grouped into

  • Environment
  • Integrated data models
    • The Integrated Resources (IR), consisting of
      • Parts 4x and 5x: Integrated generic resources
      • Parts 1xx: Integrated application resources
      • PLIB ISO 13584-20 Parts library: Logical model of expressions
    • Parts 5xx: Application Interpreted Constructs (AIC)
    • Parts 1xxx: Application Modules (AM)
  • Top parts
    • Parts 2xx: Application Protocols (AP)
    • Parts 3xx: Abstract Test Suites (ATS) for APs
    • Parts 4xx: Implementation modules for APs

In total STEP consists of several hundred parts and every year new parts are added or new revisions of older parts are released. This makes STEP the biggest standard within ISO. Each part has its own scope and introduction.

The APs are the top parts. They cover a particular application and industry domain and hence are most relevant for users of STEP. Every AP defines one or several Conformance Classes, suitable for a particular kind of product or data exchange scenario. To provide a better understanding of the scope, information requirements and usage scenarios an informative application activity model (AAM) is added to every AP, using IDEF0.

STEP is primarily defining data models using the EXPRESS modeling language. Application data according to a given data model can be exchanged either by a STEP-File, STEP-XML or via shared database access using SDAI.

Every AP defines a top data models to be used for data exchange, called the Application Interpreted Model (AIM) or in the case of a modular AP called Module Interpreted Models (MIM). These interpreted models are constructed by choosing generic objects defined in lower level data models (4x, 5x, 1xx, 5xx) and adding specializations needed for the particular application domain of the AP. The common generic data models are the basis for interoperability between APs for different kinds of industries and life cycle stages.

In APs with several Conformance Classes the top data model is divided into subsets, one for each Conformance Class. The requirements of a conformant STEP application are:

  • implementation of either a preprocessor or a postprocessor or both,
  • using one of the STEP implementation methods STEP-File, STEP-XML or SDAI for the AIM/MIM data model and
  • supporting one or several conformance classes of an AP.

Originally every APs was required to have a companion Abstract test suite (ATS) (e.g. ATS 303 for AP 203), providing Test Purposes, Verdict Criteria and Abstract Test Cases together with example STEP-Files. But because the development of an ATS was very expensive and inefficient this requirement was dropped and replaced by the requirements to have an informal validation report and recommended practises how to use it. Today the recommended practises are a primary source for those going to implement STEP.

The Application Reference Models (ARM) is the mediator between the AAM and the AIM/MIM. Originally its purpose was only to document high level application objects and the basic relations between them. IDEF1X diagrams documented the AP of early APs in an informal way. The ARM objects, their attributes and relations are mapped to the AIM so that it is possible to implement an AP. As APs got more and more complex formal methods were needed to document the ARM and so EXPRESS which was originally only developed for the AIM was also used for the ARM. Over time these ARM models got very detailed till to the point that some implementations preferred to use the ARM instead of the formally required AIM/MIM. Today a few APs have ARM based exchange formats standardized outside of ISO TC184/SC4:

There is a bigger overlap between APs because they often need to refer to the same kind of products, product structures, geometry and more. And because APs are developed by different groups of people it was always an issue to ensure interoperability between APs on a higher level. The Application Interpreted Constructs (AIC) solved this problem for common specializations of generic concepts, primarily in the geometric area. To address the problem of harmonizing the ARM models and their mapping to the AIM the STEP modules were introduced. They contain a piece of the ARM, the mapping and a piece of the AIM, called MIM. Modules are built on each other, resulting in an (almost) directed graph with the AP and conformance class modules at the very top. The modular APs are:

  • AP 209, Composite and metallic structural analysis and related design
  • AP 210, Electronic assembly, interconnect and packaging design
  • AP 221, Functional data and schematic representation of process plants
  • AP 236, Furniture product data and project data
  • AP 239, Product life cycle support
  • AP 242, Managed model based 3d engineering

The modular editions of AP 209 and 210 are explicit extensions of AP 242.

Coverage of STEP Application Protocols (AP)

The STEP APs can be roughly grouped into the three main areas design, manufacturing and life cycle support.

Design APs:

  • Mechanical:
    • AP 207, Sheet metal die planning and design
    • AP 209, Composite and metallic structural analysis and related design
    • AP 235, Materials information for the design and verification of products
    • AP 236, Furniture product data and project data
    • AP 242, Managed model based 3d engineering
  • Connectivity oriented electric, electronic and piping/ventilation:
    • AP 210, Electronic assembly, interconnect and packaging design. The most complex and sophisticated STEP AP.
    • AP 212, Electrotechnical design and installation.
    • AP 227, Plant spatial configuration
  • Ship:
    • AP 215, Ship arrangement
    • AP 216, Ship moulded forms
    • AP 218, Ship structures
  • Others:
    • AP 225, Building elements using explicit shape representation
    • AP 232, Technical data packaging core information and exchange
    • AP 233, Systems engineering data representation
    • AP 237, Fluid dynamics has been cancelled and the functionality included in AP 209

Manufacturing APs:

Life cycle support APs:

  • AP 239, Product life cycle support
  • AP 221, Functional data and schematic representation of process plants
  • AP 241, Generic Model for Life Cycle Support of AEC Facilities (planned)

The AP 221 model is very similar to the ISO 15926-2 model, whereas AP 221 follows the STEP architecture and ISO 15926-2 has a different architecture. They both use ISO-15926-4 as their common reference data library or dictionary of standard instances. A further development of both standards resulted in Gellish English as general product modeling language that is application domain independent and that is proposed as a work item (NWI) for a new standard.

The original intent of STEP was to publish one integrated data-model for all life cycle aspects. But due to the complexity, different groups of developers and different speed in the development processes, the splitting into several APs was needed. But this splitting made it difficult to ensure that APs are interoperable in overlapping areas. Main areas of harmonization are:

  • AP 212, 221, 227 and 242 for technical drawings with extension in AP 212 and 221 for schematic functionality
  • AP 224, 238 and 242 for machining features and for Geometric dimensioning and tolerancing

For complex areas it is clear that more than one APs are needed to cover all major aspects:

  • AP 212 and 242 for electro-mechanical products such as a car or a transformer. This will be addressed by the second edition of AP242 that is currently under development
  • AP 242, 209 and 210 for electro/electronic-mechanical products
  • AP 212, 215, 216, 218, 227 for ships
  • AP 203/214, 224, 240 and 238 for the complete design and manufacturing process of piece parts.

See also

Notes

  1. ^ ISO 10303-1:1994 Industrial automation systems and integration -- Product data representation and exchange -- Part 1: Overview and fundamental principles
  2. ^ Standards and projects under the direct responsibility of ISO/TC 184/SC 4 Secretariat [1]
  3. ^ Kutz, Myer (22 Jul 2002). Handbook of Materials Selection. John Wiley & Sons. p. 498. The IGES/PDES Organization was coordinated in the late 1970s from industry, government, and academia to develop standards and technology for the exchange of product information between different CAD systems. This group focused its efforts on two projects, the Initial Graphics Exchange Specification (IGES) and the Product Data Exchange Specification (PDES) using STEP. This effort resulted in the publication of IGES in 1980, which was subsequently adopted as an ANSI standard. ... A second-generation Product Data Exchange (PDE) technology, Product Data Exchange Specification (PDES), was initiated during the mid-1980s and was submitted to ISO in 1988. The international community adopted it as the basis for ISO 10303 (STEP). Today, the ongoing PDE technology efforts include the Product Data Exchange using STEP (PDES), an American National Standard (ANS). This project is the primary U.S. project providing industry inputs into to this ISO activity. Fourteen international standards have been created as a result of this effort. More than 20 countries worldwide have approved STEP, including all major U.S. trading partners.
  4. ^ Powers 2003, p. 9.
  5. ^ ISO TC184 / SC4 resolution 1, Gaithersburg - July 1984
  6. ^ ISO TC184 / SC4 resolution 33, Tokyo - December 1988
  7. ^ ISO TC184 / SC4 resolution 55, Paris - January 1990
  8. ^ ISO TC184 / SC4 resolution 195 and 196, Davos - May 1994
  9. ^ ISO TC184 / SC4 resolution 361, Bad Aibling, Germany – June 1998
  10. ^ ISO TC184 / SC4 resolution 394, San Francisco, California - January 1999

References

External links

STEP programs

Boundary representation

In solid modeling and computer-aided design, boundary representation—often abbreviated as B-rep or BREP—is a method for representing shapes using the limits. A solid is represented as a collection of connected surface elements, the boundary between solid and non-solid.

EXPRESS (data modeling language)

EXPRESS is a standard data modeling language for product data. EXPRESS is formalized in the ISO Standard for the Exchange of Product model STEP (ISO 10303), and standardized as ISO 10303-11.

Fault (technology)

In document ISO 10303-226, a fault is defined as an abnormal condition or defect at the component, equipment, or sub-system level which may lead to a failure.

In telecommunications, according to the Federal Standard 1037C of the United States, the term fault has the following meanings:

An accidental condition that causes a functional unit to fail to perform its required function. See § Random fault.

A defect that causes a reproducible or catastrophic malfunction. A malfunction is considered reproducible if it occurs consistently under the same circumstances. See § Systematic fault.

In power systems, an unintentional short-circuit, or partial short-circuit, between energized conductors or between an energized conductor and ground. A distinction can be made between symmetric and asymmetric faults. See Fault (power engineering).

General-purpose modeling

General-purpose modeling (GPM) is the systematic use of a general-purpose modeling language to represent the various facets of an object or a system. Examples of GPM languages are:

The Unified Modeling Language (UML), an industry standard for modeling software-intensive systems

EXPRESS, a data modeling language for product data, standardized as ISO 10303-11

IDEF, a group of languages from the 1970s that aimed to be neutral, generic and reusable

Gellish, an industry standard natural language oriented modeling language for storage and exchange of data and knowledge, published in 2005

XML, a data modeling language now beginning to be used to model code (MetaL, Microsoft .Net [1])GPM languages are in constrast with domain-specific modeling languages (DSMs).

Geometric dimensioning and tolerancing

Geometric dimensioning and tolerancing (GD&T) is a system for defining and communicating engineering tolerances. It uses a symbolic language on engineering drawings and computer-generated three-dimensional solid models that explicitly describe nominal geometry and its allowable variation. It tells the manufacturing staff and machines what degree of accuracy and precision is needed on each controlled feature of the part. GD&T is used to define the nominal (theoretically perfect) geometry of parts and assemblies, to define the allowable variation in form and possible size of individual features, and to define the allowable variation between features.

Dimensioning specifications define the nominal, as-modeled or as-intended geometry. One example is a basic dimension.

Tolerancing specifications define the allowable variation for the form and possibly the size of individual features, and the allowable variation in orientation and location between features. Two examples are linear dimensions and feature control frames using a datum reference (both shown above).There are several standards available worldwide that describe the symbols and define the rules used in GD&T. One such standard is American Society of Mechanical Engineers (ASME) Y14.5-2009. This article is based on that standard, but other standards, such as those from the International Organization for Standardization (ISO), may vary slightly. The Y14.5 standard has the advantage of providing a fairly complete set of standards for GD&T in one document. The ISO standards, in comparison, typically only address a single topic at a time. There are separate standards that provide the details for each of the major symbols and topics below (e.g. position, flatness, profile, etc.).

Graphical Kernel System

The Graphical Kernel System (GKS) was the first ISO standard for low-level computer graphics, introduced in 1977. A draft international standard was circulated for review in September, 1983.

Final ratification of the standard was achieved in 1985.GKS provides a set of drawing features for two-dimensional vector graphics suitable for charting and similar duties. The calls are designed to be portable across different programming languages, graphics devices and hardware, so that applications written to use GKS will be readily portable to many platforms and devices.

GKS was fairly common on computer workstations in the 1980s and early 1990s.

GKS formed the basis of Digital Research's GSX and GEM products; the latter was common on the Atari ST and was occasionally seen on PCs particularly in conjunction with Ventura Publisher. It was little used outside these markets and is essentially obsolete today except insofar as it is the underlying API defining the Computer Graphics Metafile. A descendant of GKS was PHIGS.

A main developer and promoter of the GKS was José Luis Encarnação, formerly director of the Fraunhofer Institute for Computer Graphics (IGD) in Darmstadt, Germany.

GKS has been standardized in the following documents:

ANSI standard ANSI X3.124 of 1985.

ISO 7942:1985 standard, revised as ISO 7942:1985/Amd 1:1991 and ISO/IEC 7942-1:1994, as well as ISO/IEC 7942-2:1997, ISO/IEC 7942-3:1999 and ISO/IEC 7942-4:1998

The language bindings are ISO standard ISO 8651.

GKS-3D (Graphical Kernel System for Three Dimensions) functional definition is ISO standard ISO 8805, and the corresponding C bindings are ISO 8806.The functionality of GKS is wrapped up as a data model standard in the STEP standard, section ISO 10303-46.

ISO 10303-21

STEP-File is the most widely used data exchange form of STEP. ISO 10303 can represent 3D objects in Computer-aided design (CAD) and related information. Due to its ASCII structure, a STEP-file is easy to read, with typically one instance per line. The format of a STEP-File is defined in ISO 10303-21 Clear Text Encoding of the Exchange Structure.ISO 10303-21 defines the encoding mechanism for representing data conforming to a particular schema in the EXPRESS data modeling language specified in ISO 10303-11. A STEP-File is also called p21-File and STEP Physical File. The file extensions .stp and .step indicate that the file contains data conforming to STEP Application Protocols while the extension .p21 should be used for all other purposes.

ISO 10303-22

ISO 10303-22 is a part of the implementation methods of STEP with the official title Standard data access interface or simply SDAI.

SDAI defines an abstract Application Programming Interface (API) to work on application data according to a given data models defined in EXPRESS. SDAI itself is defined independent of a particular programming language. Language bindings exist for

Part 23 - C++ language binding of the standard data access interface

Part 24 - C binding of the standard data access interface

Part 27 - Java binding to the standard data access interface with Internet/Intranet extensions

The development of language bindings for FORTRAN and the interface definition language (IDL) of CORBA were canceled.The original intent of SDAI and its bindings to programming languages was to achieve portability of software applications from one implementation to another. This was soon abandoned because there were only a few commercial implementations and they differed significantly in their detailed APIs. Today the term SDAI is sometimes used for all kinds of APIs supporting STEP, even if they only partially follow the strict functionality as defined in ISO 10303-22 and its implementation methods, or not at all. Part 35 of STEP (Abstract test methods for SDAI implementations) provides a formal way how to prove the conformance of an implementation with SDAI.

The main components of SDAI are:

SDAI dictionary schema, a meta level EXPRESS schema to describe EXPRESS schemas

Managing objects

SDAI session to control the whole SDAI environment for a single user/thread including optional transaction control

SDAI repository the physical (typically) container to store SDAI models and Schema instances, e.g. a database

SDAI model a subdivision of an SDAI repository, containing entity instance according to a particular EXPRESS schema

Schema instance a logical grouping of one or several SDAI models, making up a valid population according to a particular EXPRESS schema

Operations

to deal with the managing objects

to create, delete and modify application data (entity instance, attribute values, aggregates and their members)

to validate application data according to all the constraints and rules specified in EXPRESS

ISO 10303-28

STEP-XML is a short term for ISO 10303-28, Industrial automation systems and integration—Product data representation and exchange—Part 28: Implementation methods: XML representations of EXPRESS schema and data.

STEP-XML specifies the use of the Extensible Markup Language (XML) to represent EXPRESS schema (ISO 10303-11) and the data that is governed by those EXPRESS schema. It is an alternative method to STEP-File for the exchange of data according to ISO 10303.

The following specifications are within the scope of ISO 10303-28:

Late Bound XML markup declaration set, independent of all EXPRESS schemas, to describe the XML representation of the data governed by each schema

Early Bound XML markup declaration sets, for each of the schemas, to describe the XML representation of the data governed by that specific schema

The mapping between the schema-specific and schema-independent XML markup declarations

The form of XML documents containing EXPRESS schemas and/or data governed by EXPRESS schemas

The XML markup declarations that enables XML representation of EXPRESS schemas

The representation of EXPRESS primitive data type values as element content and as XML attribute values.The following specifications are outside the scope of ISO 10303-28:

XML markup declarations that depend on the semantic intent of the corresponding EXPRESS schema

The mapping from an XML markup declaration to an EXPRESS schema. Note: Given an XML markup declaration set and its corresponding data set(s), it is possible to create an EXPRESS schema that captures the semantic intent of the data. However, this would requires an understanding of the meaning and use of the data that may not be captured by the XML markup declarations.

The mapping from an XML representation of an EXPRESS schema back to the initial EXPRESS schema

The mapping from the XML markup declarations that have been derived from an EXPRESS schema back to the initial EXPRESS schema

The mapping of the final use of an XML schema.

ISO 10303 Application Modules

The STEP Application modules define common building blocks to create modular Application Protocols (AP) within ISO 10303. Higher-level modules are built up from lower-level modules. The modules on the lowest level are wrappers of concepts, defined in the Integrated Resources (IR) or Application Integrated Constructs (AIC). Modules on a medium level link lower level modules with each other and specialize them. Only modules on the highest levels completely cover a particular area so that they can be implemented.

Implementation modules and modules defining conformance classes:

Part 403 – AP203 configuration controlled 3d design of mechanical parts and assemblies

Part 409 - AP209 multidisciplinary analysis and design

Part 410 – AP210 electronic assembly interconnect and packaging design

Part 1604 – AP210 assembly functional interface requirements

Part 1605 – AP210 assembly functional requirements

Part 1606 – AP210 assembly physical design

Part 1607 – AP210 assembly physical interface requirements

Part 1608 – AP210 assembly physical requirements

Part 1609 – AP210 assembly requirement allocation

Part 1610 – AP210 assembly technology constraints

Part 1611 – AP210 connection zone based model extraction

Part 1759 – AP210 datum difference based model definition

Part 1612 – AP210 device functional and physical characterization

Part 1614 – AP210 functional decomposition

Part 1615 – AP210 functional requirement allocation

Part 1616 – AP210 functional specification

Part 1617 – AP210 interconnect design

Part 1618 – AP210 interconnect design for microwave

Part 1619 – AP210 interconnect functional requirements

Part 1620 – AP210 interconnect physical requirements

Part 1621 – AP210 interconnect requirement allocation

Part 1622 – AP210 interconnect technology constraints

Part 1623 – AP210 laminate assembly design

Part 1624 – AP210 package functional and physical characterization

Part 1625 – AP210 packaged part white box model

Part 1626 – AP210 physical unit physical characterization

Part 1627 – AP210 printed part functional and physical characterization

Part 1630 – AP210 product rule

Part 421 – Functional data and schematic representation

Part 433 – AP233 system engineering and design

Part 436 – AP236 furniture catalog and interior design

Part 439 – AP239 product life cycle support

Part 1287 – AP239 activity recording

Part 1297 – AP239 document management

Part 1289 – AP239 management resource information

Part 1293 – AP239 part definition information

Part 1292 – AP239 product definition information

Part 1304 – AP239 product status recording

Part 1295 – AP239 properties

Part 1306 – AP239 task specification resourced

Part 1307 – AP239 work definition

Part 442 - AP242 managed model based 3D engineeringFoundation modules:

Part 1047 – Activity

Part 1259 – Activity as realized

Part 1272 – Activity characterized

Part 1049 – Activity method

Part 1249 – Activity method assignment

Part 1298 – Activity method characterized

Part 1261 – Activity method implementation

Part 1169 – Activity structure and classification

Part 1514 – Advanced boundary representation

Part 1025 – Alias identification

Part 1601 – Altered package

Part 1602 – Altered part

Part 1109 – Alternative solution

Part 1603 – Analytical model

Part 1001 – Appearance assignment

Part 1012 – Approval

Part 1631 – Area 2d

Part 1632 – Assembly 2d shape

Part 1633 – Assembly 3d shape

Part 1634 – Assembly component placement requirements

Part 1102 – Assembly feature definition

Part 1635 – Assembly functional interface requirement

Part 1636 – Assembly module design

Part 1637 – Assembly module macro definition

Part 1642 – Assembly module usage view

Part 1644 – Assembly module with cable component

Part 1638 – Assembly module with cable component 2d

Part 1639 – Assembly module with cable component 3d

Part 1643 – Assembly module with interconnect component

Part 1640 – Assembly module with macro component

Part 1645 – Assembly module with packaged connector component

Part 1641 – Assembly module with subassembly

Part 1647 – Assembly physical interface requirement

Part 1648 – Assembly physical requirement allocation

Part 1646 – Assembly shape

Part 1026 – Assembly structure

Part 1649 – Assembly technology

Part 1132 – Associative text

Part 1250 – Attachment slot

Part 1246 – Attribute classification

Part 1650 – Bare die

Part 1651 – Basic curve

Part 1652 – Basic geometry

Part 1369 – Binary representation

Part 1143 – Building component

Part 1144 – Building item

Part 1145 – Building structure

Part 1653 – Cable

Part 1211 – Cardinality of relationship

Part 1351 – Catalog data information

Part 1352 – Catalog data information and shape representation

Part 1044 – Certification

Part 1654 – Characteristic

Part 1655 – Chemical substance

Part 1070 – Class

Part 1071 – Class of activity

Part 1174 – Class of activity library

Part 1170 – Class of activity structure

Part 1171 – Class of composition of activity

Part 1158 – Class of composition of product

Part 1172 – Class of connection of activity

Part 1159 – Class of connection of product

Part 1160 – Class of containment of product

Part 1183 – Class of description by document

Part 1182 – Class of document

Part 1181 – Class of document library

Part 1173 – Class of involvement in activity

Part 1161 – Class of involvement of product in connection

Part 1188 – Class of person

Part 1077 – Class of product

Part 1162 – Class of product library

Part 1157 – Class of product structure

Part 1212 – Classification

Part 1114 – Classification assignment

Part 1111 – Classification with attributes

Part 1002 – Colour

Part 1657 – Component feature

Part 1656 – Component grouping

Part 1177 – Composition of individual activity

Part 1166 – Composition of individual product

Part 1253 – Condition

Part 1257 – Condition characterized

Part 1254 – Condition evaluation

Part 1296 – Condition evaluation characterized

Part 1756 – Conductivity material aspects

Part 1230 – Configuration controlled 3d parts and assemblies

Part 1058 – Configuration effectivity

Part 1056 – Configuration item

Part 1178 – Connection of individual activity

Part 1167 – Connection of individual product

Part 1658 – Connectivity allocation to physical network

Part 1131 – Construction geometry

Part 1119 – Construction history

Part 1731 – Constructive solid geometry 2d

Part 1068 – Constructive solid geometry 3d

Part 1168 – Containment of individual product

Part 1027 – Contextual shape positioning

Part 1062 – Contract

Part 1003 – Curve appearance

Part 1659 – Curve swept solid

Part 1370 – Data structure representation

Part 1010 – Date time

Part 1014 – Date time assignment

Part 1660 – Datum difference based model

Part 1052 – Default tolerance

Part 1130 – Derived shape element

Part 1185 – Description by individual document

Part 1661 – Design management

Part 1628 – Design product data management

Part 1662 – Design specific assignment to assembly usage view

Part 1663 – Design specific assignment to interconnect usage view

Part 1664 – Device marking

Part 1362 – Dimension and tolerance callouts

Part 1050 – Dimension tolerance

Part 1121 – Document and version identification

Part 1184 – Document as individual

Part 1122 – Document assignment

Part 1123 – Document definition

Part 1290 – Document management

Part 1368 – Document order

Part 1126 – Document properties

Part 1124 – Document structure

Part 1180 – Document structure and classification

Part 1206 – Draughting annotation

Part 1207 – Drawing structure and administration

Part 1501 – Edge based wireframe

Part 1673 – Edge shape feature

Part 1057 – Effectivity

Part 1059 – Effectivity application

Part 1665 – Electrical network definition

Part 1004 – Elemental geometric shape

Part 1005 – Elemental topology

Part 1366 – Encoded text representation

Part 1265 – Envelope

Part 1064 – Event

Part 1364 – Event assignment

Part 1243 – Experience

Part 1342 – Expression

Part 1667 – Extended elemental geometric shape

Part 1666 – Extended geometric tolerance

Part 1106 – Extended measure representation

Part 1275 – External class

Part 1128 – External item identification assignment

Part 1033 – External model

Part 1129 – External properties

Part 1668 – Fabrication joint

Part 1669 – Fabrication requirement

Part 1670 – Fabrication technology

Part 1512 – Faceted boundary representation

Part 1671 – Feature and connection zone

Part 1127 – File identification

Part 1672 – Fill area style

Part 1006 – Foundation representation

Part 1453 – Function based behavior

Part 1674 – Functional assignment to part

Part 1216 – Functional breakdown

Part 1151 – Functional data

Part 1675 – Functional decomposition to assembly design

Part 1676 – Functional decomposition to design

Part 1677 – Functional decomposition to interconnect design

Part 1678 – Functional decomposition with nodal representation to packaged mapping

Part 1679 – Functional specification

Part 1680 – Functional unit requirement allocation

Part 1354 – Furniture interior decoration

Part 1007 – General surface appearance

Part 1341 – Generic expression

Part 1681 – Generic material aspects

Part 1051 – Geometric tolerance

Part 1039 – Geometric validation property representation

Part 1507 – Geometrically bounded surface

Part 1510 – Geometrically bounded wireframe

Part 1113 – Group

Part 1218 – Hybrid breakdown

Part 1021 – Identification assignment

Part 1349 – Incomplete data reference mechanism

Part 1036 – Independent property

Part 1099 – Independent property definition

Part 1038 – Independent property representation

Part 1176 – Individual activity

Part 1175 – Individual activity structure

Part 1179 – Individual involvement in activity

Part 1163 – Individual product structure

Part 1350 – Inertia characteristics

Part 1445 – Information packet

Part 1241 – Information rights

Part 1459 – Input output

Part 1682 – Interconnect 2d shape

Part 1683 – Interconnect 3d shape

Part 1684 – Interconnect module connection routing

Part 1685 – Interconnect module to assembly module relationship

Part 1686 – Interconnect module usage view

Part 1687 – Interconnect module with macros

Part 1688 – Interconnect non planar shape

Part 1689 – Interconnect physical requirement allocation

Part 1690 – Interconnect placement requirements

Part 1251 – Interface

Part 1691 – Interface component

Part 1294 – Interface lifecycle

Part 1165 – Involvement of individual product in connection

Part 1345 – Item definition structure

Part 1263 – Justification

Part 1692 – Land

Part 1008 – Layer assignment

Part 1693 – Layered 2d shape

Part 1694 – Layered 3d shape

Part 1695 – Layered interconnect module 2d design

Part 1696 – Layered interconnect module 3d design

Part 1697 – Layered interconnect module 3d shape

Part 1698 – Layered interconnect module design

Part 1699 – Layered interconnect module with design intent modifications

Part 1700 – Layered interconnect module with printed component design

Part 1701 – Layout macro definition

Part 1276 – Location

Part 1277 – Location assignment

Part 1358 – Location assignment characterized

Part 1146 – Location in building

Part 1288 – Management resource information

Part 1702 – Manifold subsurface

Part 1509 – Manifold surface

Part 1147 – Manufacturing configuration effectivity

Part 1091 – Maths space

Part 1092 – Maths value

Part 1118 – Measure representation

Part 1270 – Message

Part 1703 – Model parameter

Part 1105 – Multi linguism

Part 1340 – Name assignment

Part 1704 – Network functional design view

Part 1705 – Network functional usage view

Part 1706 – Non feature shape element

Part 1346 – Numeric function

Part 1344 – Numerical interface

Part 1258 – Observation

Part 1456 – Order condition

Part 1435 – Organization structure

Part 1240 – Organization type

Part 1707 – Package

Part 1708 – Packaged connector model

Part 1710 – Packaged part black box model

Part 1709 – Packaged part white box model

Part 1355 – Parameterized catalog data and shape representation

Part 1353 – Parameterized catalog data information

Part 1022 – Part and version identification

Part 1115 – Part collection

Part 1055 – Part definition relationship

Part 1711 – Part external reference

Part 1712 – Part feature function

Part 1713 – Part feature grouping

Part 1714 – Part feature location

Part 1715 – Part occurrence

Part 1716 – Part template 2d shape

Part 1717 – Part template 3d shape

Part 1718 – Part template extension

Part 1719 – Part template non planar shape

Part 1720 – Part template shape with parameters

Part 1023 – Part view definition

Part 1116 – Pdm material aspects

Part 1011 – Person organization

Part 1013 – Person organization assignment

Part 1215 – Physical breakdown

Part 1721 – Physical component feature

Part 1755 – Physical connectivity definition

Part 1722 – Physical layout template

Part 1723 – Physical node requirement to implementing component allocation

Part 1724 – Physical unit 2d design view

Part 1726 – Physical unit 2d shape

Part 1725 – Physical unit 3d design view

Part 1727 – Physical unit 3d shape

Part 1728 – Physical unit design view

Part 1729 – Physical unit interconnect definition

Part 1613 – Physical unit non planar design view

Part 1730 – Physical unit shape with parameters

Part 1732 – Physical unit usage view

Part 1733 – Planned characteristic

Part 1291 – Plib class reference

Part 1242 – Position in organization

Part 1199 – Possession of property

Part 1735 – Pre defined datum 2d symbol

Part 1736 – Pre defined datum 3d symbol

Part 1734 – Pre defined datum symbol

Part 1760 – Pre defined product data management specialisations

Part 1737 – Printed physical layout template

Part 1252 – Probability

Part 1274 – Probability distribution

Part 1040 – Process property assignment

Part 1164 – Product as individual

Part 1248 – Product breakdown

Part 1016 – Product categorization

Part 1103 – Product class

Part 1060 – Product concept identification

Part 1231 – Product data management

Part 1278 – Product group

Part 1017 – Product identification

Part 1738 – Product identification extension

Part 1063 – Product occurrence

Part 1343 – Product placement

Part 1101 – Product property feature definition

Part 1024 – Product relationship

Part 1046 – Product replacement

Part 1739 – Product rule

Part 1134 – Product structure

Part 1156 – Product structure and classification

Part 1018 – Product version

Part 1020 – Product version relationship

Part 1019 – Product view definition

Part 1034 – Product view definition properties

Part 1041 – Product view definition relationship

Part 1061 – Project

Part 1436 – Project breakdown

Part 1433 – Project management

Part 1439 – Project management management resource information connector

Part 1441 – Project management organization structure connector

Part 1442 – Project management project breakdown connector

Part 1440 – Project management project management resource information connector

Part 1434 – Project management resource information

Part 1443 – Project management schedule connector

Part 1444 – Project management work structure connector

Part 1758 – Promissory usage in product concept

Part 1198 – Property and property assignment

Part 1030 – Property assignment

Part 1074 – Property condition

Part 1085 – Property identification

Part 1080 – Property space

Part 1244 – Qualifications

Part 1213 – Reference data library

Part 1228 – Representation with uncertainty

Part 1267 – Required resource

Part 1280 – Required resource characterized

Part 1233 – Requirement assignment

Part 1452 – Requirement categorization

Part 1740 – Requirement decomposition

Part 1140 – Requirement identification and version

Part 1348 – Requirement management

Part 1460 – Requirement model assignment

Part 1141 – Requirement view definition

Part 1142 – Requirement view definition relationship

Part 1269 – Resource as realized

Part 1283 – Resource as realized characterized

Part 1268 – Resource item

Part 1281 – Resource item characterized

Part 1266 – Resource management

Part 1282 – Resource management characterized

Part 1273 – Resource property assignment

Part 1264 – Risk

Part 1437 – Schedule

Part 1203 – Schematic and symbolization

Part 1204 – Schematic drawing

Part 1205 – Schematic element

Part 1208 – Schematic element library

Part 1260 – Scheme

Part 1015 – Security classification

Part 1357 – Selected item

Part 1741 – Sequential laminate assembly design

Part 1210 – Set theory

Part 1009 – Shape appearance layers

Part 1742 – Shape composition

Part 1743 – Shape parameters

Part 1032 – Shape property assignment

Part 1457 – Shared resource

Part 1502 – Shell based wireframe

Part 1744 – Shield

Part 1745 – Signal

Part 1133 – Single part representation

Part 1746 – Software

Part 1108 – Specification based configuration

Part 1112 – Specification control

Part 1747 – Specification document

Part 1104 – Specified product

Part 1271 – State characterized

Part 1255 – State definition

Part 1256 – State observed

Part 1748 – Stratum non planar shape

Part 1152 – Structure and classification

Part 1749 – Styled curve

Part 1110 – Surface conditions

Part 1209 – Symbolization by schematic element

Part 1448 – System behavior

Part 1449 – System behavior connector

Part 1214 – System breakdown

Part 1446 – System requirements

Part 1447 – System requirements connector

Part 1461 – System risk connector

Part 1450 – System structure

Part 1451 – System structure connector

Part 1262 – Task specification

Part 1262 – Test requirement allocation

Part 1757 – Test select product

Part 1136 – Text appearance

Part 1750 – Text representation

Part 1367 – Textual expression representation

Part 1752 – Thermal network definition

Part 1462 – Time duration relationship

Part 1065 – Time interval

Part 1365 – Time interval assignment

Part 1511 – Topologically bounded surface

Part 1463 – Transformation

Part 1454 – Transformation input output

Part 1455 – Transformation order

Part 1245 – Type of person

Part 1464 – User defined attribute

Part 1054 – Value with unit

Part 1753 – Value with unit extension

Part 1754 – Via component

Part 1347 – Wireframe 2d

Part 1043 – Work order

Part 1286 – Work order characterized

Part 1300 – Work output

Part 1301 – Work output characterized

Part 1042 – Work request

Part 1285 – Work request characterized

Part 1438 – Work structure

Part 1465 – Working draft system engineering

Part 1217 – Zonal breakdown

ISO 13584

The official title of ISO 13584 is Industrial automation systems and integration - Parts library, with the acronym PLIB. PLIB is developed and maintained by the ISO technical committee TC 184, Technical Industrial automation systems and integration, sub-committee SC4 Industrial data. See also ISO 10303.

PLIB consists of these parts:

ISO 13584-1, Overview and fundamental principles: Overview and fundamental principles

Logical resources

ISO 13584-20, Logical model of expressions

ISO 13584-24, Logical model of a supplier library

ISO 13584-25, Logical model of supplier library with aggregate values and explicit content

ISO 13584-26, Information supplier identification

Implementation resources

ISO 13584-31, Geometric programming interface. This part defines a Fortran API for the creation of product geometry. It is derived from the German VDA API DIN 66304

ISO 13584-32, Implementation resources: OntoML: Ontology Markup Language. This part specifies an XML based exchange structure of ISO 13584-25 compliant data. It provides for exchanging: (1) ontologies/reference dictionaries compliant with the common ISO13584/IEC61360 dictionary model, and (2) libraries of product compliant with ISO13584-25.

ISO 13584-35, Implementation resources: Spreadsheet interface for parts library. This part specifies a spreadsheet based exchange structure of ISO 13584-25 compliant data.

Description methodology

ISO 13584-42, Methodology for structuring part families

Others

ISO 13584-101, Geometrical view exchange protocol by parametric program

ISO 13584-102, View exchange protocol by ISO 10303 conforming specification

ISO 13584-501, Reference dictionary for measuring instruments -- Registration procedure

ISO 13584-511, Mechanical systems and components for general use -- Reference dictionary for fastenersPLIB and IEC 61360 Component Data Dictionary are using the same datamodel.

ISO 15926

The ISO 15926 is a standard for data integration, sharing, exchange, and hand-over between computer systems.

The title, "Industrial automation systems and integration—Integration of life-cycle data for process plants including oil and gas production facilities", is regarded too narrow by the present ISO 15926 developers. Having developed a generic data model and Reference Data Library for process plants, it turned out that this subject is already so wide, that actually any state information may be modelled with it.

Product and manufacturing information

Product and manufacturing information, also abbreviated PMI, conveys non-geometric attributes in 3D computer-aided design (CAD) and Collaborative Product Development systems necessary for manufacturing product components and assemblies. PMI may include geometric dimensions and tolerances, 3D annotation (text) and dimensions, surface finish, and material specifications. PMI is used in conjunction with the 3D model within model-based definition to allow for the elimination of 2D drawings for data set utilization.

Re2c

re2c is a free and open-source software lexer generator for C and C++. Originally written by Peter Bumbulis and described in his paper, it was put in public domain and has been since maintained by volunteers. It is the lexer generator adopted by projects such as PHP, SpamAssassin, Ninja build system and others. In combination with Lemon parser generator it is used in BRL-CAD as a platform-agnostic and easily compilable alternative to Flex and Bison. This combination is also used with STEPcode, an implementation of ISO 10303 standard.

S-Series of ILS specifications

The S-Series of ILS specifications is a common denominator for a set of specifications associated to different integrated logistics support aspects. Originally developed by AECMA (French acronym for the Association Européenne des Constructeurs de Matériel Aeronautique, later ASD), the S-Series suite of ILS specifications is managed currently jointly by multinational teams from the Aerospace and Defence Industries Association of Europe (ASD) and Aerospace Industries Association (AIA) reporting to the AIA/ASD ILS Council. The ILS Council established the term S-Series (of) ILS specifications as the common denominator for all its specifications, and this term was consolidated with the publication of SX000i.

STEP-NC

STEP-NC is a machine tool control language that extends the ISO 10303 STEP standards with the machining model in ISO 14649, adding geometric dimension and tolerance data for inspection, and the STEP PDM model for integration into the wider enterprise. The combined result has been standardized as ISO 10303-238 (also known as AP238).

STEP-NC was designed to replace ISO 6983/RS274D G-codes with a modern, associative communications protocol that connects computer numerical controlled (CNC) process data to a product description of the part being machined.

A STEP-NC program can use the full range of geometric constructs from the STEP standard to communicate device-independent toolpaths to the CNC. It can provide CAM operational descriptions and STEP CAD geometry to the CNC so workpieces, stock, fixtures and cutting tool shapes can be visualized and analyzed in the context of the toolpaths. STEP GD&T information can also be added to enable quality measurement on the control, and CAM-independent volume removal features may be added to facilitate regeneration and modification of the toolpaths before or during machining for closed loop manufacturing.

VDA-FS

VDA-FS is a CAD data exchange format for the transfer of surface models from one CAD system to another.

Its name is an abbreviation of "Verband der Automobilindustrie - Flächenschnittstelle", which translates to the "automotive industry association - surface data interface".

Standard was specified by the German organization VDA

VDA-FS has been superseded by STEP, ISO 10303.

Wirth syntax notation

Wirth syntax notation (WSN) is a metasyntax, that is, a formal way to describe formal languages. Originally proposed by Niklaus Wirth in 1977 as an alternative to Backus–Naur form (BNF). It has several advantages over BNF in that it contains an explicit iteration construct, and it avoids the use of an explicit symbol for the empty string (such as or ε).WSN has been used in several international standards, starting with ISO 10303-21. It was also used to define the syntax of EXPRESS, the data modelling language of STEP.

By type
See also
ISO standards by standard number
1–9999
10000–19999
20000+
CAD software
Free and open-source
Proprietary
File formats
Modeling kernels

This page is based on a Wikipedia article written by authors (here).
Text is available under the CC BY-SA 3.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.