The ISO TC184 SC4 standards for the exchange, sharing and storing of industrial data Howard Mason, BAE Systems Chair, ISO TC184/SC4: Industrial data Chair, CEN TC310 Chair: ISO/IEC/ITU/UNECE MoU/MG on eBusiness

What is the business problem? This presentation is intended as a set of slides that describe BAE SYSTEMS down to the level of entities reporting directly to a Chief Operating Officer. Copies of this presentation will be found on both the company internet site, www.baesystems.com, and on the company intranet, Connectus. On Connectus, the file can be downloaded in zip, html, or uncompressed PowerPoint. Comments, suggestions, changes, etc. should be directed to Corporate Communications, External Relations, +44-1252-384 797 . Materials for inclusion can be sent by email to comms.assistant@baesystems.com.

Current business environment Increasing lifecycle of platforms Sales of new platforms declining Continuous through-life upgrades Risk transfer from customer to prime Contractor logistics support Service provision Global partnerships Increased dependence on extended supply chain Need to support reorganisation of enterprises Changing commercial and legal environment Tracking individual components

Evolution of the extended enterprise Extended Enterprise of OEM’s, Customer, Partners and Suppliers PLCS Domain Define and implement the support solution, maintain the product configuration Suppliers Tier 2 Product Lifecycle Management (PLM) Tier 1 Suppliers Enterprise Integration through dedicated networks Extended Enterprise Integration Customers Partners Opportunity provided by Internet technology in supporting the ‘Extended Enterprise’ Start by referring to the axis On the X axis - the product life cycle from concept to disposal On the Y axis – the extended enterprise from local department through Company to customers and partners and the Tier1/Tier2 supply chain The initial build shows the extent of influence of traditional information systems, I.e. mainly design and manufacture, localized to functional departments and possibly some visibility within the company The second build (green) refers to enterprise integration through dedicated networks- possible involving major partners and the customer – the scope again mainly confined to design and manufacture phases – This is typically the domain supported by traditional client-server architectures The next build introduces the impact of the Internet – allowing the realistic prospect of large scale supplier integration and collaboration. This has long been the aim of concurrent engineering/collaborative engineering but until now the technology was not there to allow it to make it practical. The Internet opens up the opportunities for managing the product information through life – latest three letter acronym is PLM(Product Lifecycle Management) with the emphasis on Lifecycle PLCS scope is shown in purple, mainly in the support phase, but also extending back into design and manufacturing for the design for supportability and design of the support solution. Make reference to the fact that the x-axis scale distorts the impact of PLCS – In-service phase is typically 5-10 times longer than the design/manufacture phase. Example: B52 bomber will have a total lifecycle of 100 yrs when it is eventually withdrawn from service. The final build shows the importance of operational feedback – providing the ability to update the as-maintained configuration and provide valuable operating experience to influence new designs. Domain specific information systems (e.g. CAD, MRPII, Planning) Enterprise Dept Concept Assessment Demonstration Manufacture In-Service Disposal Operational Feedback Product Life Cycle in stages

Importance of the life cycle PLCS Domain Design for Supportability In Service Support and Operational Feedback Suppliers Tier 2 5 – 10 years Typically 25 – 50 years Operational Life Tier 1 Suppliers Extended Enterprise Integration Customers Partners Opportunity provided by Internet technology in supporting the ‘Extended Enterprise’ Start by referring to the axis On the X axis - the product life cycle from concept to disposal On the Y axis – the extended enterprise from local department through Company to customers and partners and the Tier1/Tier2 supply chain The initial build shows the extent of influence of traditional information systems, I.e. mainly design and manufacture, localized to functional departments and possibly some visibility within the company The second build (green) refers to enterprise integration through dedicated networks- possible involving major partners and the customer – the scope again mainly confined to design and manufacture phases – This is typically the domain supported by traditional client-server architectures The next build introduces the impact of the Internet – allowing the realistic prospect of large scale supplier integration and collaboration. This has long been the aim of concurrent engineering/collaborative engineering but until now the technology was not there to allow it to make it practical. The Internet opens up the opportunities for managing the product information through life – latest three letter acronym is PLM(Product Lifecycle Management) with the emphasis on Lifecycle PLCS scope is shown in purple, mainly in the support phase, but also extending back into design and manufacturing for the design for supportability and design of the support solution. Make reference to the fact that the x-axis scale distorts the impact of PLCS – In-service phase is typically 5-10 times longer than the design/manufacture phase. Example: B52 bomber will have a total lifecycle of 100 yrs when it is eventually withdrawn from service. The final build shows the importance of operational feedback – providing the ability to update the as-maintained configuration and provide valuable operating experience to influence new designs. This slide provides a greater impression of the time and opportunity to impact through life aspects. Enterprise Dept C A D M In-Service D Product Life Cycle in years

Business drivers today Reduced Cost of Ownership Users of products are seeking improved availability, reliability, maintainability and lower cost of ownership through life Sustainable Business Growth Companies are seeking to make money through the life cycle support of their products to improve profits, improve quality and be more competitive Protect investment in product data Users of information systems want more open platforms to reduce IT costs and ensure longevity in use of information to support the lifecycle

The Information Environment Pervasive use of IT Smaller range of COTS products for product definition Highly tailored PDM systems Wide range of through-life support systems Web-enabled applications needing to share information Many small, dynamic transactions Growing overlap between traditional engineering information streams and the rest of the business

Implications for product data Digital data as sole authority Product data held in digital form represents major investment Use of product data where and when needed throughout the extended enterprise throughout the life of the product Barriers to communication can arise from: Different ways of using the same system Different systems hold data in different forms New systems and technologies Rising customer expectations

Product data capabilities Industry requires complete, accurate and timely data exchange and use Between all the participants in a value chain Throughout the entire life cycle Across all business functions Data integration and extraction Consistent models Common vocabulary Consistent reference data Information quality

The other challenges Information lifecycle exceeds life of equipment software people Long term information retention Recovery Reuse Preservation of knowledge Generation to generation

How can standards help? This presentation is intended as a set of slides that describe BAE SYSTEMS down to the level of entities reporting directly to a Chief Operating Officer. Copies of this presentation will be found on both the company internet site, www.baesystems.com, and on the company intranet, Connectus. On Connectus, the file can be downloaded in zip, html, or uncompressed PowerPoint. Comments, suggestions, changes, etc. should be directed to Corporate Communications, External Relations, +44-1252-384 797 . Materials for inclusion can be sent by email to comms.assistant@baesystems.com.

ISO TC184 SC4 - Industrial Data The mission of SC4 is to develop and promulgate standards for the representation of scientific, technical and industrial data, to develop methods for assessing conformance to these standards, and to provide technical support to other organizations seeking to deploy such standards in industry

What is industrial data? Product Definition data Long life span - 30-50 years Large, complex products, needing configuration management Data Warehousing Simpler model, data driven Component Libraries and Catalogues Different views - geometry, metadata Different forms of lists - explicit, algorithm, class Manufacturing Management data (ISO 15531) Factory resource and control Process Specification (ISO 18629) Underpinned by consistent terminology

STEP - ISO 10303 - Status In production use since 1995 Aimed at structured information exchange and sharing Common integrated resources used to support multiple different user viewpoints EXPRESS product data definition language predates UML etc

EXPRESS Data Definition Language STEP for the Web User View User View User View Application Protocols map the user view into the STEP data models STEP EXPRESS Data Definition Language STEP Physical File XML Database Language

STEP - ISO 10303 - Scope Current scope includes Geometry Configuration Management Process planning Manufacturing Finite Element Analysis Printed Circuit Assemblies Wiring looms Mechanical Design Construction industry Shipbuilding Product Life Cycle Support

AP 203: Configuration Controlled Design of Mechanical Parts Configuration Management Authorisation Control(Version/Revision) Effectivity Release Status Security Classification Supplier Geometric Shapes Advanced BREP Solids Faceted BREP Solids Manifold Surfaces with Topology Wireframe with Topology Surfaces and Wireframe without Topology Specifications Surface Finish Material Design Process CAD Filename Product Structure Assemblies Bill of Materials Part Substitute Part Alternate Part

AP 202: Associative Draughting

AP209: Composite & Metallic Analysis & Related Design Configuration Control, Approvals Part, product definitions Finite element analysis model, controls, and results Analysis Discipline Product Definitions Finite Element Analysis Model (Nodes, Elements, Properties,...) Controls (Loads, Boundary Constraints,...) Results (Displacements, Stresses,...) Analysis Report Design Discipline Product Definition Shape Representations Assemblies Information Shared Between Analysis & Design 3D Shape Representations Composite Constituents Material Specifications & Properties Part Definitions Ply Boundaries, Surfaces Laminate Stacking Tables Reinforcement Orientation Composites Homogeneous (metallics) 3D Shape Representation AP202/203 Commonality Plus Composite Specific 3D Shapes Advanced B-Representation Facetted B-Representation Manifold Surfaces With Topology Wireframe & Surface without Topology Wireframe Geometry with Topology Composite Constituent Shape Representation

AP 210: Electronic Assembly, Interconnect and Packaging Design Product Structure/ Part Connectivity Functionality Termination Shape 2D, 3D Single Level Decomposition Material Product Characteristics Functional Packaged Physical Component Placement Bare Board Geometry Layout items Layers non-planar, conductive & non-conductive Material product Configuration Mgmt Identification Authority Effectivity Control Requirement Traceability Analytical Model Document References Geometry Geometrically Bounded 2-D Wireframe with Topology Surfaces Advanced BREP Solids Constructive Solid Geometry Requirements Design Allocation Constraints Interface Rules Design Control Technology Geometric Dimensioning and Tolerancing Fabrication Design Rules Product Design Rules

AP 214: Core Data for Automotive Mechanical Design Processes Geometry Solids Data Surface Data Wireframe Measured Data Presentation Drawing Visualization Manufacturing NC-Data Process Plans Analysis Simulation Technology Data Material Data Form Features Tolerance Data Surface Conditions Specification/Configuration Product Structure Data Management Data

AP224: Process Planning Using Machining Features

AP 225: Building Elements Using Explicit Shape Representation Building Element Shape Component Structure Explicit Shape Representation Elementary (planar), Analytic (simple geometry) & Free Form (complex geometry) Building Element Types Structural Service Elements Fixtures, Equipment Building Structure Composition Location of Elements Assemblies of Elements Building Element Properties Simple Property Simple Classification

AP227: Plant Spatial Configuration Plant Item Type Connections Functional/Physical Definition/Occurrence Plant Layout Location of Plant-items Site Description Change Control Shape Explicit Shape Brep CSG Plant Systems Line Definitions Composition Capabilities Component Connectivity Functional/Analysis Interference Performance Requirements Requirement Satisfaction

AP 239: Product Life Cycle Support (PLCS) Change Directives Standard Commercial Transactions Feed & Extract Scope of STEP today Product Structure Product Representations Product Performance Life Cycle Data Shared Data Maintain/Dispose Query Support Environment Support Performance Failure Analysis Task Resource Data Maintenance Analysis Fleet Statistics ` Support and Operational Feedback Derived Disposable Data Respond Use

STEP - ISO 10303 - Development path New areas of application Systems Engineering (AP233) Materials (AP235) Furniture (AP236) STEP-NC (AP238) Increasing use of modular architecture Smaller usable exchange sets - DEX Increasing use of simple reference data for code lists and other standard structures Uses 15926 structures Risks of losing interoperability XML schema, Web services, UML representations Interfaces to transaction standards

Oil and Gas - ISO 15926 - Status Representation of information associated with engineering, construction and operation of oil and gas production facilities, supporting: information requirements in all life-cycle phases sharing and integration of information ISO 15926 will include: a generic, conceptual data model a reference data library of common information rules for developing and maintaining additional reference data libraries templates for viewing information subsets Basic model published as standard Targeted at information integration and warehousing

Oil and Gas - ISO 15926 - Development path Initial reference library balloted as 15926-4 First 12000 reference data classes Extensions under development for geometry, and proposed for mesh, based on STEP models Another 30-40K classes to be added Development of templates to provide views of subsets of the model for particular applications Considering implementation in OWL (Web Ontology Language)

PLIB - ISO 13584 - Status Description of supplier part library structure Supporting automatic integration into user libraries Representations of lists of “similar parts” - related by geometry, part of same product, etc defined explicitly or implicitly dictionary data exchange (developed jointly with IEC 61360-2) API for generating geometric models Structuring for part family definitions Supplier codes View exchange protocols Some shared resources with STEP

PLIB - ISO 13584 – Development path Current standard published Update to dictionary model XML schema for dictionary exchange Deployment for product catalogues Joint ISO/IEC guidelines under preparation

Standards for industrial data ISO 10303 - STEP ISO 15926 - Oil and Gas Model Model Reference data ISO 13584 - PLIB Reference data Reference data Model Library Reference data Parts library

Convergence Smaller, reusable model components DEX, templates,….. Common reference data, external to model Support for XML and Web services

How does this fit into the bigger picture? This presentation is intended as a set of slides that describe BAE SYSTEMS down to the level of entities reporting directly to a Chief Operating Officer. Copies of this presentation will be found on both the company internet site, www.baesystems.com, and on the company intranet, Connectus. On Connectus, the file can be downloaded in zip, html, or uncompressed PowerPoint. Comments, suggestions, changes, etc. should be directed to Corporate Communications, External Relations, +44-1252-384 797 . Materials for inclusion can be sent by email to comms.assistant@baesystems.com.

The eBusiness framework Semantics - Terminology Service assembly Scenarios Registry/Repostory for Discovery, Presence, Availability Consraints Contractual and regulatory Security Process models Data Assembly Information content/components Classification schemes Component libraries Enterprise data and metadata Reference data Identifiers Process definition mechanisms Information definition mechanisms Service definition mechanisms Representation options Transport options Networks Guidelines Physical representation Rev 4 – 2005-06-10

Information Product Classification Product Libraries (13584) Cataloguing (8000) Product Description data Product Definition data 10303, 15926 Product Identification Reference data 10303, 15926 Industrial terminology (22745)

Open Technical Dictionary – eOTD (ISO/TS 22745) Goal is to lower costs and improve quality by enabling cataloging at source Eliminate most manual aspects of cataloging Eliminate data mapping Open Technical Dictionary of properties for cataloging Use existing ISO and IEC terminology where available Harmonization process to ensure synchronization with ISO and IEC terminology Implementation guide on integration of catalog data in STEP Document guidelines for the use of dictionary elements defined in the OTD as reference data for the incorporation of cataloging information into ISO 10303 product data files Enable automated extraction of catalog descriptions from STEP files Current status: NWI accepted but with many comments

ISO 8000 Management standard for cataloguing Aimed at ensuring consistency of catalogued information Essential for quality Major support from NATO, US and the users of the NATO Codification system

What are the opportunities for the future? This presentation is intended as a set of slides that describe BAE SYSTEMS down to the level of entities reporting directly to a Chief Operating Officer. Copies of this presentation will be found on both the company internet site, www.baesystems.com, and on the company intranet, Connectus. On Connectus, the file can be downloaded in zip, html, or uncompressed PowerPoint. Comments, suggestions, changes, etc. should be directed to Corporate Communications, External Relations, +44-1252-384 797 . Materials for inclusion can be sent by email to comms.assistant@baesystems.com.

Current exploitation Exploiting information models to support other standards ISO 13399 for tooling PLIB for ISO TC2 fasteners Process measuring equipment - overlap with IEC SC65B removed ECCMA Electronic Open Technical Dictionary Common ISO/IEC guide for PLIB exploitation Potentially impacts all ISO and IEC product standards

Opportunities for further exploitation Lifecycle management and use of product data Product characteristics derived from single model Integration of engineering and procurement functions Procurement information derived from single source Web-enabling reference data Consistent reuse and enhanced interoperability Challenge of the business model for maintenance Making it really easy for SMEs

The strengths Massive investment in information models Growing investment in reference data Structures that can be used by other groups Basis for addressing new challenges Information quality Long term information retention Recovery Reuse Preservation of knowledge Generation to generation