DOCSLIB.ORG

Early Implementation of ISO 10303-AP239 for Product Life Cycle Support

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Early Implementation of ISO 10303-AP239 for Product Life Cycle Support Pre-print of paper for PDT Europe 2003, Manchester (UK) 25 to 27 November 2003 Early implementation of ISO 10303-AP239 for product life cycle support Dr. Timothy M. KING ([email protected]), LSC Group, UK (HTTP://WWW.LSC.CO.UK/) 1. Introduction Starting in November 1999, the Product Life Cycle Support (PLCS) initiative1 has developed a draft for Application Protocol 239 (AP239), "Product life cycle support" as part of the International Standard, ISO 10303, "Industrial automation systems and integration – Product data representation and exchange". During 2003, the emerging draft of the standard ISO 10303-239 has been the basis for early implementation. In the face of various technical challenges, the initial three-year PLCS work programme [1] was not able to complete the necessary amount of effort to deliver a draft standard. However, the sponsors embarked on a further year of work, which has been successful in achieving the intended goals in the period from November 2002. The PLCS work programme ended on 31 October 2003. 2. Key features of AP239 2.1. Evolution of the ISO 10303 Application Protocol concept Although being another in the extensive series of Application Protocols that are constituents of the ISO 10303 standard [2], AP239 also embodies major features that are an evolution of the traditional form of an Application Protocol. These features are: • product as individual; • use of Application Modules [3]; • a limited number of Conformance Classes in the Application Protocol, while development effort has resulted in parallel delivery of Data Exchange Set specifications; • use of reference data. 2.2. Product as individual Product as individual is a concept within the AP239 information model. This concept is a major requirement for the Application Protocol because through-life support processes are often in the context of specific activities on specific planned or realised individual products (usually with an identifying serial number). In general, prior ISO 10303 Application Protocols have been about design and manufacturing specifications and, thus, the product concept is typical (with an identifying part number) rather than individual. ISO 10303 has not really dealt clearly with these contrasting requirements previously but AP239 has successfully delivered a more precise consideration of this issue. 2.3. Application Modules The successful ballot of four cycles of Application Modules for PLCS has shown that ISO 10303 has been able to embrace this significant new architectural approach. AP239 relies on a total number of 136 1 The sponsors have included: Aerosystems International; Alvis Hägglunds; BAE SYSTEMS; Boeing; Det Norske Veritas (DNV); Finnish Defence Forces; FMV; IFS; Lockheed Martin; LSC Group; Pennant; PTC; Rolls-Royce; Royal Norwegian MoD; Saab Technology; UK MoD; US DoD. © LSC Group 2003 Page 1 of 8 Pre-print of paper for PDT Europe 2003, Manchester (UK) 25 to 27 November 2003 modules. Already many of these modules also form part of other Application Protocols that are at various stages of progress towards publication. This common usage is the result of harmonisation between the different development teams and is an important basis for interoperability and re-use between implementations of the different Application Protocols. AP239 has a close relationship and shares common Application Modules with two specific Application Protocols: • AP203 (Edition 2), "Configuration controlled 3D design of mechanical parts and assemblies"; • AP233, "Systems engineering data representation". The close relationship arises from the complementary nature of the three Application Protocols in addressing the total life cycle of the product [see Figure 2.1]. In the case of AP203 (Edition 2), the shared modules are from the set of so-called "product data management (PDM) modules", which represent a core capability for the identification, description and structuring of component and assembly design. (Geometry is the main feature of AP203 that is not part of the scope of AP239.) concept a s l s a e s s o s p m is e d n design t includes geometry d e m e specification, o c i n v s r through-life update & tr e a s - upgrade ti n o i n manufacture concept concept a a s s l s l s a e a e s s s s o s o s p systems m p product m is e is e d n d n engineering t life cycle support t d includes requirements d includes support engineering, e e m m e engineering, architecture e configuration management, o o c c i i n n v v s s r definition, systems r resource management, tr tr e e a a s s - - ti analysis & modelling maintenance feedback ti n n o o i i n n manufacture manufacture Figure 2.1 Interaction between product life cycle support, design and systems engineering throughout the life cycle AP239 and AP233 share modules that cover the key areas of requirements, product breakdowns (including system, functional, physical, zonal and hybrid) and product interfaces. 2.4. Data Exchange Sets Traditionally, ISO 10303 Application Protocols have included a number of Conformance Classes that embody different subdivisions of the total information model and reflect a suitable scope for implementation within a software application. For example, AP203 includes Conformance Classes that cover different forms of three-dimensional geometry, such as wireframe and boundary representation [2]. These different geometries are alternatives and, thus, a single software application is not necessarily going to support all the alternatives. In the case of AP239, the scope of the Application Protocol is extensive, expressed at the top level as the four domain areas of configuration management, support engineering, resource management and maintenance and feedback [1]. The PLCS work programme has been unable readily to refine this top-level view into definitive Conformance Classes that are suitable for inclusion in the standard. In these circumstances, PLCS adopted an alternative approach that involves a greater emphasis on business analysis to determine the requirements for implementation of the Application Protocol. © LSC Group 2003 Page 2 of 8 Pre-print of paper for PDT Europe 2003, Manchester (UK) 25 to 27 November 2003 The PLCS approach has resulted in the concept of the Data Exchange Set (DEX) that describes the application of the AP239 information model within a bounded business scope. Teams have been working to refine Data Exchange Sets for scopes that currently include [4]: • fault states; • maintenance plan; • operational feedback; • product breakdown for support; • work package definition; • work package report. The refinement of the Data Exchange Sets is an on-going requirement that will depend on implementation of AP239 to highlight the applicability of the standard. Under these circumstances, the PLCS sponsors sought a mechanism by which to conduct follow-up work. A major requirement was for this mechanism to be less demanding and rigid than the contract-based PLCS work programme. The identified option has been to form a new PLCS Technical Committee [5] as part of OASIS2, which is a "global consortium that drives the development, convergence and adoption of e-business standards" [6]. The Data Exchange Sets will not be a formal part of ISO 10303. However, eventually, a set of stable Data Exchange Sets is likely to be the basis for an Edition 2 of AP239, whereby each DEX can become a Conformance Class within the standard. 2.5. Reference data Early in the genesis of PLCS, the information modellers began to recognise one major feature of the through-life support business domain. Prior Application Protocols have generally been definitive about concepts in the information model. These concepts appear as a specific entity (for example, "Product_version") and the associated attributes are identifying (for example, "id" and "name") or descriptive (for example, "description"). However, certain entity attributes have required the specification of valid or suggested instance values, typically if the attribute is a string. One example would be the set of suggested instance values for the method of determination for property values3. This set includes 'calculated', 'designed', 'estimated', 'measured', 'required', and 'set point' and appears in the relevant Application Module [7]. Such examples are relatively uncommon and, thus, have not raised the profile of one major issue in having the values within the standard: the listed values are not necessarily complete or applicable to all implementations of the Application Protocol. In the case of through-life support, lists of instance values are apparently more pervasive than in prior Application Protocols. Examples include qualifications necessary for different types of task, operating environments for products and failure probability level (when expressed non-numerically). Such values are important to the way that individual organisations perform business operations but no universally acceptable and comprehensive collection of required values is possible within the published standard (certainly not within any timescale that would meet the needs of industry). AP239 has embraced the concept of reference data in order to address the inflexibility of using the Application Protocol information model as a definitive specification to deep levels of detail. This concept depends on the Application Module "External class" [8], which extends the more fundamental capability of classification. The AP239 information model allows the user to classify the vast majority of data instances and, in each of these cases, identify the class as existing in an external library of classes. 2 Organization for the Advancement of Structured Information Standards. 3 The set applies to the value_determination attribute of the Qualified_property_value_representation entity. © LSC Group 2003 Page 3 of 8 Pre-print of paper for PDT Europe 2003, Manchester (UK) 25 to 27 November 2003 These external libraries then form the mechanism by which organisations can specify the meaning of and manage those classes. The information model places no restrictions on the potential choice of technology for the external class library.
Load more

Recommended publications
  • Recommended Practices for AP242 BO Model XML Assembly Structure
    Recommended Practices for STEP AP242 TC Business Object Model XML Product & Assembly Structure Release 2.0 October 30, 2018 Contacts: Organizational Jochen Boy Phil Rosché Frédéric Darré PROSTEP AG ACCR, LLC. Cimpa Dolivostraße 11 125 King Charles Circle 4 Avenue Didier Daurat 64293 Darmstadt Summerville 31700 Blagnac Germany SC 29485 / USA France [email protected] [email protected] [email protected] Technical Guillaume Hirel Jochen Haenisch T-Systems Jotne EPM [email protected] [email protected] © PDM / CAx / JT Implementor Forum PDM-IF/CAx-IF/JT-IF Recommended Practices AP242 BO Model XML Product & Assembly Structure Version 2.0; October 30, 2018 Table of Contents 1 Introduction ........................................................................................................ 11 1.1 Document Overview ................................................................................................ 11 1.1.1 Goal and Objectives ........................................................................................................ 11 1.1.2 Scope ............................................................................................................................... 11 1.1.3 Intended Audience ........................................................................................................... 12 1.1.4 Intended Use.................................................................................................................... 12 1.1.5 Document Style...............................................................................................................
    [Show full text]
  • TP-1996-789.Pdf (141.1Kb)
    Nationaal Lucht- en Ruimtevaartlaboratorium National Aerospace Laboratory NLR NLR TP 96789 Overview and discussion of electronic exchange standards for technical information H. Kuiper and J.C. Donker DOCUMENT CONTROL SHEET ORIGINATOR'S REF. SECURITY CLASS. NLR TP 96789 U Unclassified ORIGINATOR National Aerospace Laboratory NLR, Amsterdam, The Netherlands TITLE Overview and discussion of electronic exchange standards for technical information PRESENTED AT the CALS Europe'96 conference, Paris, May 29-31, under the title "SGML, HTML, the paperless office... what about the forests and the trees", upon invitation of the NL MOD Representative in the conference committee. AUTHORS DATE pp ref H. Kuiper and J.C. Donker 960725 36 8 DESCRIPTORS Computer graphics Multimedia Document storage Software tools Document markup languages Standards Format Texts Hypertext Word processing Information dissemination ABSTRACT Nowadays more and more information is being exchanged electronically. Reasons for this include a higher degree of cooperation between information suppliers and users, an increasing demand for speed (of production and modification, and reduction of time to market), and cost reduction. On the technology side, the advent of the electronic highway enables effective and efficient electronic information exchange. For reasons of timeliness and life cycle costs, standards and specifications are becoming more important. The aim of this paper is to provide an overview of standards and specifications for electronic exchange of (technical document) information and to discuss the most common ones currently available for text, images, and document exchange. Emerging standards and specifications, such as for audio, video and virtual environments are also briefly discussed. Finally, a brief description is given of a standard for enterprise integration and product data exchange.
    [Show full text]
  • ISO/IEC JTC 1 N13604 ISO/IEC JTC 1 Information Technology
    ISO/IEC JTC 1 N13604 2017-09-17 Replaces: ISO/IEC JTC 1 Information Technology Document Type: other (defined) Document Title: Study Group Report on 3D Printing and Scanning Document Source: SG Convenor Project Number: Document Status: This document is circulated for review and consideration at the October 2017 JTC 1 meeting in Russia. Action ID: ACT Due Date: 2017-10-02 Pages: Secretariat, ISO/IEC JTC 1, American National Standards Institute, 25 West 43rd Street, New York, NY 10036; Telephone: 1 212 642 4932; Facsimile: 1 212 840 2298; Email: [email protected] Study Group Report on 3D Printing and Scanning September 11, 2017 ISO/IEC JTC 1 Plenary (October 2017, Vladivostok, Russia) Prepared by the ISO/IEC JTC 1 Study Group on 3D Printing and Scanning Executive Summary The purpose of this report is to assess the possible contributions of JTC 1 to the global market enabled by 3D Printing and Scanning. 3D printing, also known as additive manufacturing, is considered by many sources as a truly disruptive technology. 3D printers range presently from small table units to room size and can handle simple plastics, metals, biomaterials, concrete or a mix of materials. They can be used in making simple toys, airplane engine components, custom pills, large buildings components or human organs. Depending on process, materials and precision, 3D printer costs range from hundreds to millions of dollars. 3D printing makes possible the manufacturing of devices and components that cannot be constructed cost-effectively with other manufacturing techniques (injection molding, computerized milling, etc.). It also makes possible the fabrications of customized devices, or individual (instead of identical mass-manufactured) units.
    [Show full text]
  • Iso 10303-511:2001(E)
    This preview is downloaded from www.sis.se. Buy the entire standard via https://www.sis.se/std-617578 INTERNATIONAL ISO STANDARD 10303-511 First edition 2001-04-15 Industrial automation systems and integration — Product data representation and exchange — Part 511: Application interpreted construct: Topologically bounded surface Systèmes d'automatisation industrielle et intégration — Représentation et échange de données de produits — Partie 511: Construction interprétée: Surface délimitée topologiquement Reference number ISO 10303-511:2001(E) © ISO 2001 This preview is downloaded from www.sis.se. Buy the entire standard via https://www.sis.se/std-617578 ISO 10303-511:2001(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. © ISO 2001 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body in the country of the requester.
    [Show full text]
  • Forcepoint DLP Supported File Formats and Size Limits
    Forcepoint DLP Supported File Formats and Size Limits Supported File Formats and Size Limits | Forcepoint DLP | v8.8.1 This article provides a list of the file formats that can be analyzed by Forcepoint DLP, file formats from which content and meta data can be extracted, and the file size limits for network, endpoint, and discovery functions. See: ● Supported File Formats ● File Size Limits © 2021 Forcepoint LLC Supported File Formats Supported File Formats and Size Limits | Forcepoint DLP | v8.8.1 The following tables lists the file formats supported by Forcepoint DLP. File formats are in alphabetical order by format group. ● Archive For mats, page 3 ● Backup Formats, page 7 ● Business Intelligence (BI) and Analysis Formats, page 8 ● Computer-Aided Design Formats, page 9 ● Cryptography Formats, page 12 ● Database Formats, page 14 ● Desktop publishing formats, page 16 ● eBook/Audio book formats, page 17 ● Executable formats, page 18 ● Font formats, page 20 ● Graphics formats - general, page 21 ● Graphics formats - vector graphics, page 26 ● Library formats, page 29 ● Log formats, page 30 ● Mail formats, page 31 ● Multimedia formats, page 32 ● Object formats, page 37 ● Presentation formats, page 38 ● Project management formats, page 40 ● Spreadsheet formats, page 41 ● Text and markup formats, page 43 ● Word processing formats, page 45 ● Miscellaneous formats, page 53 Supported file formats are added and updated frequently. Key to support tables Symbol Description Y The format is supported N The format is not supported P Partial metadata
    [Show full text]
  • IDOL Keyview Viewing SDK 12.7 Programming Guide
    KeyView Software Version 12.7 Viewing SDK Programming Guide Document Release Date: October 2020 Software Release Date: October 2020 Viewing SDK Programming Guide Legal notices Copyright notice © Copyright 2016-2020 Micro Focus or one of its affiliates. The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Documentation updates The title page of this document contains the following identifying information: l Software Version number, which indicates the software version. l Document Release Date, which changes each time the document is updated. l Software Release Date, which indicates the release date of this version of the software. To check for updated documentation, visit https://www.microfocus.com/support-and-services/documentation/. Support Visit the MySupport portal to access contact information and details about the products, services, and support that Micro Focus offers. This portal also provides customer self-solve capabilities. It gives you a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the MySupport portal to: l Search for knowledge documents of interest l Access product documentation l View software vulnerability alerts l Enter into discussions with other software customers l Download software patches l Manage software licenses, downloads, and support contracts l Submit and track service requests l Contact customer support l View information about all services that Support offers Many areas of the portal require you to sign in.
    [Show full text]
  • IGOSS-Industry/Government Open Systems Specification
    NIST Special Publication 500-217 Computer Systems IGOSS-Industry/Government Technology Open Systems Specification U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Gerard Mulvenna, Editor Standards and Technology NIST RESEARCH INFORMATION NAT-L INST. OF STAND & TECH R.I.C. MAR 2 6 1996 "'^ NIST PUBLICATIONS CENTER QC 100 .U57 iO. 500-217 994 7he National Institute of Standards and Technology was established in 1988 by Congress to "assist industry in the development of technology . needed to improve product quality, to modernize manufacturing processes, to ensure product reliability . and to facilitate rapid commercialization ... of products based on new scientific discoveries." NIST, originally founded as the National Bureau of Standards in 1901, works to strengthen U.S. industry's competitiveness; advance science and engineering; and improve public health, safety, and the environment. One of the agency's basic functions is to develop, maintain, and retain custody of the national standards of measurement, and provide the means and methods for comparing standards used in science, engineering, manufacturing, commerce, industry, and education with the standards adopted or recognized by the Federal Government. As an agency of the U.S. Commerce Department's Technology Administration, NIST conducts basic and applied research in the physical sciences and engineering and performs related services. The Institute does generic and precompetitive work on new and advanced technologies. NIST's research facilities are located
    [Show full text]
  • ISO 10303-Part303.Pdf
    Note to reviewers: 1. This document closely reflects the changes recommended by Q&E at the ISO meeting in Kobe, Japan, June 1996 and editorial changes recommended by ISO staff review at the ISO meeting in Toronto, Canada, Oct 1996. 2. This document reflects the latest version of the ATS Guidelines methods document (N434 plus ballot comment resolutions). 3. This document will be submitted for TR ballot in the near future. ISO/TR 10303-303(E) Contents Page 1 Scope ........................................................................... 1 2 Normative references ............................................................... 1 3 Definitions ....................................................................... 2 3.1 Terms defined in ISO 10303-1 ................................................ 2 3.2 Terms defined in ISO 10303-22 ............................................... 3 3.4 Terms defined in ISO 10303-203 .............................................. 3 3.5 Other definitions ........................................................... 3 3.6 Abbreviations ............................................................. 4 4 Test purposes ..................................................................... 4 4.1 Application element test purposes ............................................. 5 4.2 AIM test purposes ........................................................ 15 4.3 Implementation method test purposes ......................................... 52 4.4 Domain test purposes .....................................................
    [Show full text]
  • ASTM Standards
    PUBLISHED BIWEEKLY BY THE AMERICAN NATIONAL STANDARDS INSTITUTE 25 West 43rd Street, NY, NY 10036 VOL. 32, #23 November 16, 2001 Contents American National Standards Call for Comment on Standards Proposals ............................................................. 2 Call for Comment Contact Information .................................................................... 12 Final Actions............................................................................................................... 14 Project Initiation Notification System (PINS)........................................................... 18 ISO and IEC Standards ISO Draft Standards ................................................................................................... 20 ISO and IEC Newly Published Standards................................................................. 22 CEN/CENELEC Standards Activity ............................................................................ 25 Registration of Organization Names in the U.S. ....................................................... 27 Proposed Foreign Government Regulations............................................................. 27 International Organization of Legal Metrology.......................................................... 28 Information Concerning .............................................................................................. 31 Standards Action is now available via the World Wide Web For your convenience Standards Action can now be downloaded from the following web address:
    [Show full text]
  • Introduction to ISO 10303 - the STEP Standard for Product Data Exchange
    TECHNICAL NOTE Introduction to ISO 10303 - the STEP Standard for Product Data Exchange Michael J. Pratt* National Institute of Standards and Technology Manufacturing Systems Integration Division Gaithersburg, MD 20899-8261, USA. [email protected] Background Since 1984 the International Organization for Standardization (ISO) has been working on the development of a comprehensive standard for the electronic exchange of product data between computer-based product life-cycle systems. Initial concentration has been on design and manufacturing applications. This standard, ISO 10303 [1,2,3], is informally known as STEP (STandard for the Exchange of Product model data). Its scope is much broader than that of other existing CAD data exchange formats, notably the Initial Graphics Exchange Specification (IGES), a US standard that has been in use for nearly twenty years. Whereas IGES was developed primarily for the exchange of pure geometric data between computer aided design (CAD) systems, STEP is intended to handle a much wider range of product-related data covering the entire life-cycle of a product. The development of STEP has been one of the largest efforts ever undertaken by ISO. Several hundred people from many different countries have been involved in the work for the past sixteen years, and development is as active now as it ever has been in the past. STEP is increasingly recognized by industry as an effective means of exchanging product-related data between different CAD systems or between CAD and downstream application systems [4]. The first parts of the standard were published in 1994 [1,2] after some ten years of work by members of the relevant standards subcommittee, ISO TC184/SC4, whose responsibility is `Industrial Data'.
    [Show full text]
  • WG-16 Presentation VM.Pdf
    Web3D Design Printing and Scanning WG formerly CAD Working Group Activities in support of 3D Visualization for CAX activities For presentation to SC 4 WG 16 Nov 2018 3D Visualization always involves a dynamic interactive scenegraph with elements of • 3D Geometry • Material Appearance (colors, visual properties) • Navigation and Perspective • Interactivity Our 3D visualizations: • Always refer to external objects, visual appearance is not their primary or sole purpose • Exist in the world of copyright, licenses, proprietary and intellectual rights, security and authorization needs, version control, traceability,…. Metadata and Annotation There is a need to clarify terminology and usage. DPS WG recognizes 3 distinct but related concepts. 2 are called metadata! 1. Metadata about the “document” , author, owner, version 2. Metadata about the elements of the scenegraph … and 1 is called, at least by a CoChair 3. Annotation : A visual feature presenting extended information about some element of the scenegraph. Examples are labels, dimensions, callouts. Related to term “helpers” from definitions prepared by STEP Geometry Services Existing STEP or ISO definition Add presentation Wikipedia source Definitions Defined by 23301 constructive solid geometry (CSG) 10303, they are defined here to make an important distinction between two helpers type of geometric modelling in which a solid is defined as the result of a fundamentally different modelling approaches. The present resource is Supplemental geometry used to construct or document the geometric
    [Show full text]
  • Development Architecture for Industrial Data Management
    Development architecture for industrial data management Yujiang Li Licentiate Thesis Royal Institute of Technology School of Industrial Engineering and Management Department of Production Engineering Stockholm, Sweden 2013 Abstract Standardized information modeling is important for interoperability of CAx systems. Existing information standards such as ISO 10303 STEP have been proposed and developed for decades for this purpose. Comprehensive data structure and various implementation methodologies make such standards strong in support of different industry domains, information types, and technical requirements. However, this fact also leads to increased implementation complexity and workloads for CAx system developers. This licentiate proposes the development architecture, STEP Toolbox, to help users implement standards with a simplified development process and minimal knowledge requirements on standards. Implementation difficulties for individuals are identified with analysis on implementation of the information standards in three aspects: tasks, users, and technology. Then the toolbox is introduced with an illustration of design of behavior and structure. Case studies are performed to validate the toolbox with prototypes. Internal and external observation has shown the around two-month learning process skipped and a great amount of workload reduction in implementation with the utilization of this architecture. Keywords: Information modeling, ISO 10303 STEP, CAx, API I Contents Abstract ........................................................................................................................
    [Show full text]