This part of ISO 10303 specifies the use of the integrated resources necessary for the scope and information requirements for Technical Data Packages (TDPs) (see 3.5.28) to be exchanged among product data management systems.
Each enterprise uses content, format, and the level of configuration control as parameters when establishing its product exchange or access requirements among business partners. Because of the diverse set of products, product data, and lifecycle processes PDM systems support, this part of ISO 10303 allows many combinations of these parameters and their values.
Using a defined set of these parameters, the disclosure of product information needs to be sufficient to satisfy the business purpose of the TDP.
NOTE 1 TDPs may be prepared to a level where the product information is sufficient to evaluate a product definition concept. Or a TDP may be prepared to a level where the product information is sufficient to enable full design disclosure (see 3.5.9).
Requirements for this part of ISO 10303 were derived from functions that create and use TDPs and reside throughout the product's life cycle. The key informational aspects addressed in this part of ISO 10303 are shared and exchanged throughout the product's life cycle.
NOTE 2 Within a product's life cycle, there are many functions that create and use the technical information about a product. Figure 3 illustrates the functional usage of technical data within each life cycle phase of a product. The largest percentage of the technical data is developed in the concept development, concept and validation, and product and process development lifecycle phases. The operations and support lifecycle phase, for most products or commodities, is the longest and is impacted the greatest by the quality and usability of the TDP information. The production lifecycle phase typically has the second largest usage of the information contained within the TDP. In the production and product process development lifecycle phase, TDP data is used to build and deliver the product.
NOTE 3 The application activity model in annex F provides a graphical representation of the processes and information flows that are the basis for the definition of the scope of this part of ISO 10303.
Figure 3 -- Functional usage of technical data
EXAMPLE 1 The following represent different types of Technical Data Packages through a product's life cycle:
NOTE 4 Definitions for the preceding types of TDPs are given in Clause 3.5.
The content, form, and format of the data are critical to the core information content for exchange or access of the TDP. The following are within the scope of this part of ISO 10303:
NOTE 5 This part of ISO 10303 is defined independently of product or commodity.
-- Product definition data and product configuration control data pertaining to the concept development, concept and validation, product and process development, production, operations and support, and retirement phases of a product (herein called the product life cycle);
NOTE 6 ISO 10303 standards are referenced throughout the documentation of the requirements of this part of ISO 10303. This part utilizes ISO 10303 standards through the use of application interpreted constructs.
EXAMPLE 2 A finite element analysis (models, controls, and results) and testing reports are each a group of technical data.
EXAMPLE 3 Change activity is documented in the form of Drawing Revision Notices, Engineering Change Notices, and Drawing Change Notices.
NOTE 7 Identification of document version will be defined by this part of ISO 10303.
NOTE 8 File and file format information may be defined by this part of ISO 10303, another part of ISO 10303, National Standards or through mutual agreement between the sending and receiving parties of the TDP elements.
EXAMPLE 4 Digital media could include floppy disk, diskette, compact disk, and 9-track tape.
EXAMPLE 5 Non-digital media could include paper, mylar, aperture card, and vellum.
The following are outside the scope of this part of ISO 10303:
NOTE 9 A product data set may contain analysis or test data in a format other than this part of ISO 10303.
NOTE 10 Changes prior to release are considered informal change activity.
NOTE 11 ISO 10303-209  defines requirements for informal change activity prior to engineering release.
EXAMPLE 6 Business data could include schedule, cost, time standards, risk, and related management information.