SIST EN 9300-200:2018
(Main)Aerospace series - LOTAR -LOng Term Archiving and Retrieval of digital technical product documentation such as 3D, CAD and PDM data - Part 200: Common Concepts for Long term Archiving and Retrieval of Product Structure Information
Aerospace series - LOTAR -LOng Term Archiving and Retrieval of digital technical product documentation such as 3D, CAD and PDM data - Part 200: Common Concepts for Long term Archiving and Retrieval of Product Structure Information
In most modern industrial environments, product data is maintained and managed using product data
management (PDM) systems. In general, these systems:
— Manage the use of the primary technical data contained, for example, in CAD models and
documents;
— Allow organization of primary technical data into structures to represent the relevant products;
— Support definition and maintenance processes for products.
Within the EN 9300 context, several domain specific parts address LTA&R for the primary technical
data (e.g. CAD, CAx, Documents) as generated by the relevant technical “authoring” systems. The
EN 9300-2xx series provides information for LTA&R of product management data for the relevant
documents, structures and processes.
NOTE The terms “PDM data” and “product management data” are synonymous.
This is illustrated in the Figure below.
Luft- und Raumfahrt - LOTAR - Langzeit-Archivierung und -Bereitstellung digitaler technischer Produktdokumentationen, wie zum Beispiel von 3D-, CAD- und PDM-Daten - Teil 200: Allgemeine Konzepte für die Langzeitarchivierung und Bereitstellung von Produktstruktur-Informationen
2.1 PDM Daten im Kontext von EN 9300
In den meisten modernen Industrieumgebungen werden Produktdaten mit Hilfe von Produktdatenmanage¬mentsystemen (PDM Systemen) gepflegt und verwaltet. Im Allgemeinen tun diese Systeme Folgendes:
Verwaltung der Nutzung der primären technischen Daten, die zum Beispiel in CAD Modellen und Doku¬menten enthalten sind;
Ermöglichen der Organisation primärer technischer Daten in Strukturen zur Darstellung der relevanten Produkte;
Unterstützung der Definitions und Wartungsprozesse für Produkte.
Im Kontext der Normenreihe EN 9300 beschäftigen sich mehrere typspezifische Normen mit der LTA&R primärer technischer Daten (z. B. CAD, CAx, Dokumente), die von den relevanten technischen Autorensystemen generiert werden. Die Normenreihe EN 9300 2xx liefert Informationen zur LTA&R von Produktmanagementdaten für die relevanten Dokumente, Strukturen und Prozesse.
Dies zeigt das folgende Bild.
2.2 Ziele und Anwendungsbereich
Diese Norm behandelt die Langzeit Archivierung und Bereitstellung (LTA&R) von Produktmanagement-daten und relevanten prozessbezogenen Informationen (z. B. Anforderungen an die Produktstruktur). Was die prozessbezogenen Informationen anbetrifft, gelten nur die Prozessergebnisse als im Anwendungsbereich liegend, da sie stabile und statische Merkmale aufweisen. Der Arbeitsablauf zur Erstellung der Informationen liegt nicht im Anwendungsbereich. Die gewonnenen Informationen, z. B. Änderungsgenehmigung, Zulassun¬gen/Signaturen, CAD Modelle, Attribute, liegen im Anwendungsbereich.
Produktmanagementdaten spiegeln genau die lokalen Geschäfts und Datenverarbeitungsprozesse eines Unternehmens wider. Deshalb kann ein offener Standard nur eine gemeinsame generische Untergruppe all¬gemeiner Anforderungen definieren. Andere Daten, die nur von lokaler Relevanz sind oder von der lokalen Anwendungsumgebung abhängen, werden durch lokale Verfahren definiert. Für jede Anwendungsumge¬bung muss der komplette Satz an Standards, Methoden und Verfahren im Zusammenhang mit den archivier¬ten Produktmanagementdaten durch offene Standards, Industriestandards oder Unternehmensstandards und verfahren definiert und dokumentiert werden. Es wird dringend empfohlen, offene Standards zu verwenden, wann immer dies möglich ist, um den Austausch, die gemeinsame Nutzung, die Archivierung und Auditierbarkeit von Daten zu erleichtern.
Drei wichtige Ziele der LTA&R von Produktmanagementdaten sind:
Ermöglichung der einwandfreien Bereitstellung archivierter primärer technischer Daten bei der Ausfüh¬rung von Abfragen bezüglich Produktstruktur, beziehungen, gültigkeit, status usw.;
Bewahrung der Verbindungen zwischen primären technischen Daten und den zugeordneten Produkt-managementdaten;
Bereitstellung aller in den zugeordneten Produktmanagementdaten enthaltenen relevanten Eigenschaf¬ten primärer technischer Daten.
2.2.1 Architekturdefinition
(...)
Série aérospatiale - LOTAR - Archivage long terme et récupération des données techniques produits numériques telles que CAD 3D et PDM - Partie 200 : Concepts généraux pour l’archivage long terme et la réutilisation des informations de structure de produits
2.1 Données PDM dans le contexte de l’EN 9300
Dans la plupart des environnements industriels modernes, les données de produits sont conservées et gérées au moyen de systèmes de gestion des données techniques (PDM). En général, ces systèmes :
Gèrent l’utilisation des données techniques primaires contenues, par exemple dans les modèles et documents CAO ;
Permettent d’organiser les données techniques primaires en structures pour représenter les produits concernés ;
Prennent en charge les processus de définition et de maintenance pour les produits.
Dans le contexte de l'EN 9300, plusieurs parties spécifiques au domaine traitent du LTA&R pour les données techniques primaires (par exemple : CAO, CAx, Documents) telles qu’elles sont générées par les systèmes « auteurs » techniques correspondants. La série EN 9300-2xx fournit des informations pour le LTA&R de données de gestion de produit pour les documents, structures et processus correspondants.
NOTE Les termes « données PDM » et « données de gestion produit » sont des synonymes.
2.2 Objectifs et domaine d’application
Cette partie traite de l’archivage à long terme (LTA&R) des données de gestion produit et des informations associées des processus correspondants (par exemple : les exigences concernant la structure de produit). En ce qui concerne les informations associées au processus, seuls les résultats du processus sont considérés comme couverts par le champ d’application, car ils possèdent des caractéristiques stables et statiques. Le workflow utilisé pour créer les informations n'est pas couvert par le domaine d’application. Les informations qui en résultent, telles que les documents d’autorisation de modifications, les approbations/signatures, les modèles CAO, les données d’attributs sont couvertes par le domaine d’application.
Les données de gestion produit reflètent strictement les processus opérationnels locaux et de traitement des données de chaque entreprise. Par conséquent, une norme ouverte ne peut définir qu’un sous-ensemble générique commun de la totalité des exigences. Les autres données, qui sont uniquement utiles au niveau local ou qui dépendent de l’environnement local de l’application sont définies par des procédures locales. Pour chaque environnement d’application, l’ensemble complet de normes, méthodes et procédures associées aux données de gestion de produit archivées doit être défini et documenté par des normes ouvertes, des normes industrielles ou des normes et procédures de l’entreprise. Il est fortement recommandé d’utiliser des normes ouvertes chaque fois que c’est possible, afin de faciliter l’échange, le partage, l’archivage et l’audit des données.
Les trois principaux objectifs du LTA&R des données de gestion produit sont les suivants :
Permettre la bonne récupération des données techniques primaires archivées lors de l’exécution de requêtes relatives à la structure, aux relations, à l’efficacité, au statut du produit, etc. ;
Préserver les liens entre les données techniques primaires et les données de gestion de produit associées ;
Fournir toutes les propriétés pertinentes des données techniques primaires, telles qu’elles figurent dans les données de gestion de produit associées.
(...)
Aeronavtika - LOTAR - Dolgoročno arhiviranje in pridobivanje digitalne tehnične dokumentacije o izdelkih, kot so podatki o 3D, CAD in PDM - 200. del: Splošni pojmi za dolgoročno arhiviranje in pridobivanje informacij o strukturi izdelka
V sodobnih industrijskih okoljih se za vzdrževanje in upravljanje podatkov o izdelkih večinoma uporabljajo sistemi za upravljanje podatkov o izdelkih (PDM). Navedeni sistemi na splošno:
– upravljajo uporabo glavnih tehničnih podatkov, ki jih, na primer, vsebujejo modeli CAD in dokumenti;
– omogočajo organiziranje glavnih tehničnih podatkov v strukture, ki predstavljajo zadevne izdelke;
– podpirajo postopke opredelitve in vzdrževanja izdelkov.
Standard EN 9300 vsebuje več delov, ki se nanašajo na posamezne domene in obravnavajo dolgotrajno arhiviranje in iskanje glavnih tehničnih podatkov (npr. CAD, CAx, dokumenti), ki jih ustvarjajo zadevni sistemi za »pisanje«: tehničnih vsebin: Standard EN 9300-2xx podaja informacije za dolgotrajno arhiviranje in iskanje podatkov o upravljanju izdelkov za zadevne dokumente, strukture in procese.
OPOMBA: izraza »podatki PDM« in »upravljanje podatkov o izdelkih« sta sinonima. To je prikazano na spodnji sliki.
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Luft- und Raumfahrt - LOTAR - Langzeit-Archivierung und -Bereitstellung digitaler technischer Produktdokumentationen, wie zum Beispiel von 3D-, CAD- und PDM-Daten - Teil 200: Allgemeine Konzepte für die Langzeitarchivierung und Bereitstellung von Produktstruktur-InformationenSérie aérospatiale - LOTAR - Archivage long terme et récupération des données techniques produits numériques telles que CAD 3D et PDM - Partie 200 : Concepts généraux pour l’archivage long terme et la réutilisation des informations de structure de produitsAerospace series - LOTAR -LOng Term Archiving and Retrieval of digital technical product documentation such as 3D, CAD and PDM data - Part 200: Common Concepts for Long term Archiving and Retrieval
of Product Structure Information49.020Letala in vesoljska vozila na splošnoAircraft and space vehicles in general35.240.30Uporabniške rešitve IT v informatiki, dokumentiranju in založništvuIT applications in information, documentation and publishing01.110L]GHONHTechnical product documentationICS:Ta slovenski standard je istoveten z:EN 9300-200:2018SIST EN 9300-200:2018en,fr,de01-julij-2018SIST EN 9300-200:2018SLOVENSKI
STANDARD
SIST EN 9300-200:2018
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 9300-200
April
t r s z ICS
r sä s s râ
u wä t v rä u râ
v {ä r t r English Version
Aerospace series æ LOTAR æ LOng Term Archiving and Retrieval of digital technical product documentation such as
uDá CAD and PDM data æ Part
t r rã Common Concepts for LOng Term Archiving and Retrieval of Product Structure Information Série aérospatiale æ LOTAR æ Archivage long terme et récupération des données techniques produits numériques telles que CAD
uD et PDM æ Partie
t r r ã Concepts généraux pour l 5archivage long terme et la réutilisation des informations de structure de produits Luftæ und Raumfahrt æ LOTAR æ LangzeitæArchivierung und æBereitstellung digitaler technischer Produktdokumentationená wie zum Beispiel von
uDæá CADæ und PDMæDaten æ Teil
t r rã Allgemeine Konzepte für die Langzeitarchivierung und Bereitstellung von ProduktstrukturæInformationen This European Standard was approved by CEN on
z January
t r s zä
egulations which stipulate the conditions for giving this European Standard the status of a national standard without any alterationä Upætoædate lists and bibliographical references concerning such national standards may be obtained on application to the CENæCENELEC Management Centre or to any CEN memberä
translation under the responsibility of a CEN member into its own language and notified to the CENæCENELEC Management Centre has the same status as the official versionsä
CEN members are the national standards bodies of Austriaá Belgiumá Bulgariaá Croatiaá Cyprusá Czech Republicá Denmarká Estoniaá Finlandá Former Yugoslav Republic of Macedoniaá Franceá Germanyá Greeceá Hungaryá Icelandá Irelandá Italyá Latviaá Lithuaniaá Luxembourgá Maltaá Netherlandsá Norwayá Polandá Portugalá Romaniaá Serbiaá Slovakiaá Sloveniaá Spainá Swedená Switzerlandá Turkey and United Kingdomä
EUROPEAN COMMITTEE FOR STANDARDIZATION COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre:
Rue de la Science 23,
B-1040 Brussels
9
t r s z CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Membersä Refä Noä EN
{ u r ræ t r rã t r s z ESIST EN 9300-200:2018
EN 9300-200:2018 (E) 2 Contents
Page European foreword . 3 Foreword . 4 1 Preface . 5 2 Scope . 6 3 Normative references . 9 4 Terms, definitions and abbreviations . 10 5 Applicability . 18 6 Fundamentals and concepts for long term archiving and retrieval of PDM data . 18 7 Requirements for customization of off-the-shelf PDM systems . 27 8 Methods of implementation of the given requirements . 28 9 Preservation Planning for archived PDM information . 34 10 Administration and monitoring . 41 11 Definition of Archive Information Packages for PDM Data . 42 12 Conformance Classes . 45
(informative)
Notional Information Objects in relation to product life cycle views . 48
Figures Figure 1 — PDM Data and Primary Technical Data . 7 Figure 2 — Life Cycle View of PDM Data . 21 Figure 3 — PDM data within product life cycle . 24 Figure 4 — Data characteristics per view . 25 Figure 5 — Detailed data characteristics per view . 25 Figure 6 — Identify PDM Data Sub-Structure to be archived . 29 Figure 7 — Links between Use Cases, essential information and EN 9300 parts . 31 Figure 8 — Links between Use Cases, essential information and EN 9300 parts . 37 Figure 9 — Relationship of Conformance Class to EN 9300-2xx Parts . 45 Figure A.1. 48
Tables Table 1 — Mapping table for Part 2xx structure . 6 Table 2 — Subparts of EN 9300-2xx series and their generic characteristics . 26 Table 3 — Scaled conformance levels in accordance to specific requirements . 46
SIST EN 9300-200:2018
EN 9300-200:2018 (E) 3 European foreword This document (EN 9300-200:2018) has been prepared by the Aerospace and Defence Industries Association of Europe - Standardization (ASD-STAN). After enquiries and votes carried out in accordance with the rules of this Association, this Standard has received the approval of the National Associations and the Official Services of the member countries of ASD, prior to its presentation to CEN. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by October 2018, and conflicting national standards shall be withdrawn at the latest by October 2018. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN shall not be held responsible for identifying any or all such patent rights. According to the CEN-CENELEC Internal Regulations, the national standards organisations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. SIST EN 9300-200:2018
EN 9300-200:2018 (E) 4 Foreword This standard was prepared jointly by AIA, ASD-STAN, PDES Inc. and the PROSTEP iViP Association. The PROSTEP iViP Association is an international non-profit association in Europe. For establishing leadership in IT-based engineering it offers a moderated platform to its nearly 200 members from leading industries, system vendors and research institutions. Its product and process data standardization activities at European and worldwide levels are well known and accepted. The PROSTEP iViP Association sees this standard and the related parts as a milestone of product data technology. PDES, Inc. is an international non-profit association in USA. The mission of PDES, Inc. is to accelerate the development and implementation of ISO 10303, enabling enterprise integration and PLM interoperability for member companies. PDES, Inc. gathers members from leading manufacturers, national government agencies, PLM vendors and research organizations. PDES, Inc. supports this standard as an industry resource to sustain the interoperabity of digital product information, ensuring and maintaining authentic longevity throughout their product life cycle. Readers of this standard should note that all standards undergo periodic revisions and that any reference made herein to any other standard implies its latest edition, unless otherwise stated The Standards will be published under two different standards organizations using different prefixes. ASD-STAN will publish the standard under the number EN 9300–xxx. AIA will publish the standard under the number NAS 9300–xxx. The content in the EN 9300 and NAS 9300 documents will be the same. The differences will be noted in the reference documentation (i.e. for EN 9300 Geometric Dimensioning & Tolerancing will be referenced in ISO 1101 and ISO 16792, and for NAS 9300 the same information will be referenced in ASME Y14.5M and Y 14.41). The document formatting etc. will follow that of the respective editorial rules of ASD-STAN and AIA. rein to any other standard implies its latest edition, unless otherwise stated. SIST EN 9300-200:2018
EN 9300-200:2018 (E) 5 1 Preface The EN 9300 series defines long term archiving and retrieval (LTA&R) for digital product data. Product data comprises both the content data defining a product and the respective metadata. In complex product environments, the metadata are managed in a product data management (PDM) system. Consequently, the EN 9300 series will comprise a series of domain specific standards to deal with LTA&R of PDM data. 1.1 Justification LTA&R of only the original technical data defining a product does not give sufficient information to satisfy the obligation to provide supporting documents for proof of evidence, since essential usage information for these data will be missing. Hence evidential weight of these data in most cases can only be guaranteed by long term archiving and retrieval of a minimum set of the respective metadata. Two business scenarios describe the basic requirements for LTA&R of PDM data: 1) Assure evidence of product data for verification, certification, or product liability. This is the minimum requirement for LTA&R and provides sufficient product management data to indicate the proper usage of the primary technical data. Since this is limited to static information on defined product instances and their configurations and is only intended to enable viewing of these data, it can be extracted from PDM systems with attached primary technical data in a viewing format. However this will not allow the re-use of the PDM data. 2) Enable reuse of the archived product data. LTA&R of PDM data which enables reuse of product data over the complete life cycle of a product is needed for business requirements which increasingly assume the availability of this data. However, this requires deeper integration of processes and PDM data compared to the previous scenario. More detailed information on these scenarios and their use cases is given in the detailed EN 9300-2xx Parts. 1.2 Long Term Archiving and Retrieval of PDM data in EN 9300 context Since the EN 9300 series defines LTA&R for digital product data, it addresses both the data defining a product and the associated management data, including: — product usage of the primary technical data; — organization/structure of the data; — configuration management of the data (effectivity, status, etc.). The product management data describe the primary technical data generically in a PDM framework, independently of their specific type (CAD data, for example), which are described in the domain specific parts of EN 9300 series. SIST EN 9300-200:2018
EN 9300-200:2018 (E) 6 1.3 Location in EN 9300 document structure The EN 9300-2xx series of domain specific parts within the EN 9300 context are dedicated to product management data. All concepts of the generic process parts of EN 9300 apply unless stated otherwise. Reflecting the standard EN 9300 document structure, the EN 9300-2xx series is structured as a Part 200 describing the fundamentals and concepts for the series, followed by several domain specific sub-parts. The documents listed below define metadata requirements for specific PDM domains, see Table 1: Table 1 — Mapping table for Part 2xx structure Data domain specific part Document Number Product Management Data in an as designed view EN 9300-210 Product Management Data in an as planned view EN 9300-220 Product Management Data in an as delivered/maintained view EN 9300-230 Product Management Data In-development (including prelim design review, critical design review, etc.) EN 9300-240 Change documentation EN 9300-250
2 Scope 2.1 PDM data in EN 9300 context In most modern industrial environments, product data is maintained and managed using product data management (PDM) systems. In general, these systems: — Manage the use of the primary technical data contained, for example, in CAD models and documents; — Allow organization of primary technical data into structures to represent the relevant products; — Support definition and maintenance processes for products. Within the EN 9300 context, several domain specific parts address LTA&R for the primary technical data (e.g. CAD, CAx, Documents) as generated by the relevant technical “authoring” systems. The EN 9300-2xx series provides information for LTA&R of product management data for the relevant documents, structures and processes. NOTE The terms “PDM data” and “product management data” are synonymous. This is illustrated in the Figure below. SIST EN 9300-200:2018
EN 9300-200:2018 (E) 7
Figure 1 — PDM Data and Primary Technical Data 2.2 Objectives and scope of application This part covers long term archiving (LTA&R) for product management data and relevant process related information (e.g. product structure requirements). Regarding process related information, only the process results are considered in scope as these have stable and static characteristics. The workflow used to create the information is not in scope. The resulting information, e.g. change authorization document, approvals/signatures, CAD models, attribute data, are in scope. Product management data closely reflects the local business and data handling processes of each company. Therefore, an open standard can define only a common generic subset of the overall requirements. Other data that are only of local relevance or dependent on the local application environment are defined by local procedures. For each application environment, the complete set of standards, methods, and procedures related to the archived product management data shall be defined and documented by open standards, industry standards, or company standards and procedures. It is strongly recommended to use open standards whenever possible to ease data exchange, sharing, archiving, and ability to audit. Three main objectives for LTA&R of product management data are: — enable the proper retrieval of archived primary technical data when performing queries relative to product structure, relationships, effectivity, status, etc.; — preserving the links between primary technical data and the associated product management data; — providing all relevant properties of primary technical data as contained within the associated product management data. SIST EN 9300-200:2018
EN 9300-200:2018 (E) 8 2.2.1 Architecture Definition The product management data and the primary technical data may be managed in different environments (e.g. a database system for the product management data and a file system for the primary technical data with a reference in the database to the unique identifier and location for the file). In many cases, the primary technical data are held by the primary generating systems (e.g. CAD, systems engineering tool set) attached to a PDM backbone architecture. The relationship between product management data and primary technical data is typically established by referencing mechanisms. The referencing mechanisms and the systems managing them shall be taken into account when archiving. This can be done by describing the complete architecture of systems involved in the management of the relevant information and by defining common system requirements and procedures, such as synchronization, applied quality level, security requirements, and auditing. The overall capability of the architecture requires all systems within the architecture to comply with the common requirements. The complete architecture definition shall comply with requirements defined in the applicable EN 9300 common process parts. 2.2.2 Archival of frequently changing PDM data Product management data frequently changes and methods are employed to properly document the changes, and to provide traceability to authorizing change documentation. The long term archiving process may be applied to frequently changing data to record its condition at a specific point in time, as defined by the management process. The granularity and timing of long term archival processes can vary depending on relevant business processes, the system architecture, and the application environment (i.e. versions of applications). 2.2.3 CAD Authored Data Replicated in PDM CAD assembly structures (defined within CAD assembly models) show how parts are organized into higher level assemblies, showing their interrelationships and hierarchy. For example, some systems show the configuration of one product instance by visualizing the 3D CAD models in relevant position, where the position information is defined in the CAD Assembly. Another example would be mass properties which are defined in the CAD Assembly, but are also shown as meta data in the PDM system. The ability to view CAD assembly structures in the context of a product configuration requires configuration management aspects such as change control, variants (e.g. optional configurations), and effectivities. However, these are only provided in a PDM environment. CAD model defined assembly structures are not in scope for the LTA&R use cases defined in the EN 9300-2xx series, and are addressed in the EN 9300-115. 2.3 Out of Scope The EN 9300-2xx series does not address primary technical data content or operation of the configuration management process itself. The EN 9300-2xx series only delivers methods for long term archiving and retrieval of PDM data. Methods for long term archiving and retrieval of primary technical data (content data) attached to PDM data is not in scope of the EN 9300-2xx series. These are delivered within the scope of other parts of EN 9300 as 1xx series for CAD or by applying existing available standards. SIST EN 9300-200:2018
EN 9300-200:2018 (E) 9 Examples for these are given below: — 3D Geometry \ EN 9300-1xx series; — 2D Drawings \ TIFF G4; — Documents \ PDF A (ISO 19005); — Document/Database \ XML (W3C recommendation); — Technical Publications \ Spec. S1000D. 3 Normative references The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN 9300 (all parts), Aerospace series — LOTAR — LOng Term Archiving and Retrieval of digital technical product documentation such as 3D, CAD and PDM data EN ISO 1101, Geometrical product specifications (GPS) — Geometrical tolerancing — Tolerances of form, orientation, location and run-out EN ISO 9000, Quality management systems — Fundamentals and vocabulary ISO 10007, Quality management systems — Guidelines for configuration management ISO 10303-203, Industrial automation systems and integration — Product data representation and exchange — Part 203: Application protocol: Configuration controlled 3D design of mechanical parts and assemblies ISO 10303-214, Industrial automation systems and integration — Product data representation and exchange — Part 214: Application protocol: Core data for automotive mechanical design processes ISO 10303-239, Industrial automation systems and integration — Product data representation and exchange — Part 239: Application protocol: Product life cycle support ISO 10303-242, Industrial automation systems and integration — Product data representation and exchange — Part 242: Application protocol: Managed model-based 3D engineering ISO 12006 (all parts), Building construction — Organization of information about construction works ISO 14721, Space data and information transfer systems — Open archival information system (OAIS) — Reference model ISO 15226, Technical product documentation — Life cycle model and allocation of documents ISO 15926 (all parts), Industrial automation systems and integration — Integration of life-cycle data for process plants including oil and gas production facilities ISO 16792, Technical product documentation — Digital product definition data practices ISO 19005 (all parts), Document management — Electronic document file format for long-term preservation SIST EN 9300-200:2018
EN 9300-200:2018 (E) 10 ISO/IEC 2382-1, Information technology — Vocabulary — Part 1: Fundamental terms IEC 61346-1, Industrial systems, installations and equipment and industrial products — Structuring principles and reference designations — Part 1: Basic rules ISO/IEC 82045 (all parts), Document management Spec. S1000D, International Specification for Technical Publications ASME Y14.5:2009, Dimensioning and Tolerancing ASME Y14-41:2012, Digital Product Definition Data Practices EIA 649 B, National Consensus Standard for Configuration Management 4 Terms, definitions and abbreviations For the purposes of this document, the terms, definitions and abbreviations given in EN 9300-007, and the following apply. Terms and definitions defined only in this standard or referenced from other standards are intended to be included in EN 9300-007. ISO and IEC maintain terminological databases for use in standardization at the following addresses:
IEC Electropedia: available at http://www.electropedia.org/
ISO Online browsing platform: available at http://www.iso.org/obp
4.1 archival storage from the OAIS model, the process that ensures data remains available for access [SOURCE: EN 9300-007:2017, 3.1.7] 4.2 archive <1> repository for historical information [SOURCE: EN 9300-007:2017, 3.1.8] 4.3 archive <2> any repository conforming to the OAIS standard [SOURCE: EN 9300-007:2017, 3.1.9] 4.4 certification <1> process of assessing a process or product against some particular set of criteria [SOURCE: EN 9300-007:2017, 3.1.14] SIST EN 9300-200:2018
EN 9300-200:2018 (E) 11 4.5 certification <2> particular process of certifying an aircraft type as being airworthy Note 1 to entry: For clarity, LOTAR uses the term “Type certification” as defined in CFR in this context. [SOURCE: EN 9300-007:2017, 3.1.15] 4.6 configuration <1> product attributes of an existing or planned product, or a combination of products [SOURCE: EIA 649 B] 4.7 configuration <2> one of a series of sequentially created units or instances of a product [SOURCE: EIA 649 B] 4.8 configuration <3> configuration is the association of a Class condition association or a Class specification association object with a design or with a process in order to define a valid usage of it in the context of a certain Product_class Note 1 to entry: The validity of the association may be limited by a time period through assigning an Effectivity object to it. Note 2 to entry: The semantics of the kind of association is defined by the attributes “configuration_type” and “inheritance_type”. [SOURCE: ISO 10303-214:2010, 4.2.100] 4.9 configuration arrangement of the elements of a system [SOURCE: ISO 9000:2000] 4.10 configuration control activities comprising the control of changes to a configuration item after formal establishment of its configuration documents [SOURCE: ISO 10007:1995, 3.5] 4.11 configuration management management process for establishing and maintaining consistency of a product’s performance, functional, and physical attributes with its requirements, design and operational information throughout its life [SOURCE: EIA 649 B] SIST EN 9300-200:2018
EN 9300-200:2018 (E) 12 4.12 configuration management <1> discipline of managing the information relating to a product design, encompassing planning and management, change management, configuration identification, status accounting and audit. Note 1 to entry: This is the preferred sense in the aircraft industry, and in the EN 9300 documentation. [SOURCE: EN 9300-007:2017, 3.1.17] 4.13 configuration management <2> rules relating to the choice and combinations of options used when configuring a particular physical example of a product [SOURCE: EN 9300-007:2017, 3.1.18] 4.14 content subject information of a document [SOURCE: ISO/IEC 82045-1:2001, 3.2.2] 4.15 data reinterpretable presentation of information in a formalized manner suitable for communication, interpretation or processing [SOURCE: ISO/IEC 2382-1:1993, 01.01.02] 4.16 designated community from OAIS, the community for which the system is designed. In the case of EN 9300, it is the community that will use the information retained in an archive [SOURCE: EN 9300-003:2017, 3.1.24] 4.17 document this term covers a family of usages, from a physical paper document, through electronic files which can be thought as representing a document, to synthetic view derived from multiple sources for which the user's conceptual model is that of reading a document. See also EN 9300-003, 5.3.1 “Archiving Product Models vs. Archiving Documents” [SOURCE: EN 9300-007:2017, 3.1.27] 4.18 domain specific part LOTAR parts are either general or domain specific. LOTAR parts 100 upwards are the domain specific parts, and deal with the particularities of each type of data such as 3D CAD. The general parts (1 to 99) apply tom all types of data. [SOURCE: EN 9300-007:2017, 3.1.28] SIST EN 9300-200:2018
EN 9300-200:2018 (E) 13 4.19 effectivity <1> attribute associated with PDM structures which define application of PDM structure nodes and associated documents to individual units. Values of effectivity attribution may include options, range of units, and date. A resolved product structure is determined by evaluating effectivity for selected options, range, and/or date 4.20 effectivity <2> designation, defining the product range; e.g. serial numbers, block numbers, batch numbers, lot numbers, model, dates or event, at which a specific product configuration applies, a change is to be or has been affected, or to which a variance applies [SOURCE: EIA 649 B] 4.21 effectivity <3> this unit of functionality provides the capability to represent information concerning the validity of data. Implicit propagation of data specifying validity is not available. The validity of data can be expressed by effectivities that specify time ranges within which data may be used and by retention periods that specify how long data have to be kept and when they may or have to be deleted. Both concepts can make use of explicit dates or of dates expressed by events in order to represent the relevant points in time [SOURCE: ISO 10303-214:2010, 4.1.25] 4.22 effectivity <4> identification of the valid use of a document version tracked by date or event [SOURCE: ISO/IEC 82045-1:2001, 3.4.2] 4.23 electronic signature defined method to sign an object in electronic environments. It provides means to authenticate the signatory and the signed object in an unambiguous and safe way by attaching to or logically associating data in electronic form to other electronic objects. (See EN 9300-005) [SOURCE: EN 9300-007:2017, 3.1.29] 4.24 evidential weight from Code of Practice for Legal Admissibility, in the case where electronic information is used as evidence in a court case, the degree of reliance that the information is what it purports to be [SOURCE: EN 9300-007:2017, 3.1.31] 4.25 fixity information ancillary information that show a particular set of informat
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.