© PDES, Inc. 2010 Modular STEP Application Protocol Content, Status, and Use Charlie Stirk Technical Advisory Committee Chair PDES Inc.

Slides:



Advertisements
Similar presentations
IATI Technical Advisory Group Technical Proposals Simon Parrish IATI Technical Advisory Group, DIPR March 2010.
Advertisements

Linking Technology and Defense. Introduction It stands for Product Life Cycle Support It is an International Standard It is an information standard It.
ISO Implementation and Processor Validation Keith Hunten, P.E. Lockheed Martin Aeronautics April, 2002 ESA-NASA Workshop
1 INCOSE Chesapeake Chapter Enterprise SE Panel Discussion L. Mark Walker/LMC 21 March 2007.
C O P Y R I G H T E U R O S T E P G R O U P Changes to ISO Rob Bodington, Phil Spiby.
Reference ontologies for manufacturing Bob Young - R Young, N Hastilow, M Imran, N Chungoora Z Usman and A-F Cutting-Decelle.
® DODAF CADM/AP233 Interoperability Project David Price OSJTF March 2006.
ISO TC184/SC4 Future architecture Rotterdam Progress on the Future SC4 Architecture PWI Friday 13 th November 2009.
DEX Publication Project OASIS PLCS TC Telecon 29 April 2008 Trine Hansen.
TC3 Meeting in Montreal (Montreal/Secretariat)6 page 1 of 10 Structure and purpose of IEC ISO - IEC Specifications for Document Management.
® Eurostep.ESUKPC v0.1©Copyright Eurostep Limited AP233 – CADM Data Interchange Demo NDIA M&S Presentation David Price February 2005.
Program Cost and Schedule Integrated with Systems Engineering Models
Dr Rob Bodington Eurostep
Product Life Cycle Support (PLCS) The Information Backbone to transform the Logistics Enterprise PLCSlib status PLCS OASIS TOG Filton, UK Rob.
System Design/Implementation and Support for Build 2 PDS Management Council Face-to-Face Mountain View, CA Nov 30 - Dec 1, 2011 Sean Hardman.
Application of PDM Technologies for Enterprise Integration 1 SS 14/15 By - Vathsala Arabaghatta Shivarudrappa.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
Model Based Systems Engineering (MBSE) using SysML GSFC Systems Engineering Seminar June 8, 2010 Sanford Friedenthal Lockheed Martin
1 Proposed PLCS TC Organization and Functional Responsibilities Revision
Systems Modeling Language ™ Overview Cris Kobryn and Sandy Friedenthal SysML Partners ( October 2003.
Reuse Standards Dr. Carma McClure Extended Intelligence, Inc. Copyright (c) 1998 by Extended Intelligence, Inc.
Aerospace Industries Association - Aerospace and Defense Industries Association of Europe – Standardization (AIA-ASD Stan) LOTAR LOng Term Archiving and.
Howard Mason, BAE Systems Chair, ISO TC184/SC4: Industrial data
1 Data Exchange Mark E. Sampson EMIS 8340 Systems Engineering Tool—applying tools to engineering systems.
OASIS ebXML Registry Standard Open Forum 2003 on Metadata Registries 10:30 – 11:15 January 20, 2003 Kathryn Breininger The Boeing Company Chair, OASIS.
The Development of Support for PMI in STEP AP203E2 and AP214
1 Synchronize work on DEXs and reference data between PLCS pilots and OASIS/PLCS - Proposed PLCS TC Organization and Functional Responsibilities.
CAM-I Scalable Flexible Manufacturing Initiative NGMS Task 6.1.
Development Process and Testing Tools for Content Standards OASIS Symposium: The Meaning of Interoperability May 9, 2006 Simon Frechette, NIST.
1 Click to edit Master title style ROCKWELL COLLINS STEP VISION Jack R. Harris Director, Advanced Manufacturing Technology Rockwell Collins
1 Schema Registries Steven Hughes, Lou Reich, Dan Crichton NASA 21 October 2015.
ISO edition 2 Publication plan R. Bodington Eurostep Limited ISO edition 2.
1 ILE Project Integrated Logistics Environment Kickoff Meeting Task 2 Completion of the Ship Common Information Model Presented by: Dr. Burton Gischner.
1 ISO TC184/SC4 Industrial Data ISO JTC1/SC32 Meeting Berlin, Germany Gerald Radack Concurrent Technologies Corp.
Publish ISO Technical Corrigenda for ISO , and NSRP Systems Technology Panel Project Pete Lazo Product Data Services Corporation.
OSLC PLM Reference model April Summary of the OSLC PLM Reference Model V0.4 April 4th 2011 Gray Bachelor Mike Loeffler OSLC PLM Workgroup.
PLCS DEXs Trine Hansen DNV 20 April Content OASIS / PLCS Organization PLCS DEXs DEX architecture Process – define and verify capabilities Way forward.
1 Registry Services Overview J. Steven Hughes (Deputy Chair) Principal Computer Scientist NASA/JPL 17 December 2015.
STEP for Multi-Disciplinary Model Management: “Intelligent PDM”
STEP Tutorial: “ Fundamentals of STEP” David Briggs, Boeing January 16, 2001 ® PDES, Inc NASA STEP Workshop step.nasa.gov.
1 Margaret Christison Head of Product Data Standards Product Information Standards Defence Logistics 2004.
11 th NASA/ESA Workshop on Product Data Exchange 2009 Allison Barnard Feeney, NIST David Price, Eurostep.
STEP Tutorial Effective Exchange of STEP data January 16, 2001 ® PDES, Inc.
Synchronise work on DEXs and reference data between PLCS pilots and OASIS/PLCS Workshop #3 10 – 11 November 2004.
Recommendations from PLCS TOG Meeting Filton, UK Aug 2011.
Manufacturing Systems Integration Division Development Process and Testing Tools for Content Standards Simon Frechette National Institute of Standards.
Progetto OPTIMUS PLM and Interoperability in the defense sector Vico Equense (NA) – April, Xenia Fiorentini.
OASIS ebXML Registry Standard Open Forum 2003 on Metadata Registries 10:30 – 11:15 January 20, 2003 Kathryn Breininger The Boeing Company Chair, OASIS.
DEX Publication Project OASIS PLCS TC Face to Face meeting 10 March 2008 Trine Hansen.
Slide 1 of 14© 2015 ENGISIS INTEROPERABILITY FOR PRODUCT LIFECYCLE MANAGEMENT Ing. Xenia Fiorentini PLM and Interoperability in the defense sector.
Synchronize work on DEXs and reference data between PLCS pilots and OASIS/PLCS - Background, Lessons learned, Conclusions, Recommendations, Plan forward.
Application of the ISO for BIM Xenia Fiorentini, Engisis.
Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.
Technical Operations 12 th July 2010 Dr Phil Spiby Eurostep Limited Integrating Systems Engineering Information with AP233.
International Workshop 28 Jan – 2 Feb 2011 Phoenix, AZ, USA Modeling Standards Activity Team Model-based Systems Engineering (MBSE) Initiative Roger Burkhart.
SysML/AP233 Mapping Status INCOSE IW MSDS Report Phil Spiby and Allison Feeney 1.
OSLC PLM Reference model February Summary of the OSLC PLM Reference Model V0.2 February 22 nd 2011 Gray Bachelor Mike Loeffler OSLC PLM Workgroup.
Overview of CATIA V5.
AFNeT Standardization Days Paris
Autodesk Inventor and STEP Solutions
CAx Implementor Forum Jochen Boy, ProSTEP iViP
Theorem CADverter for STEP AP242
SysML v2 Formalism: Requirements & Benefits
Systems Modeling Language (SysML) Overview
Electrical wiring harness interoperability: functionalities of AP242 ed2; preparation of the STEP 'electrical' Implementer Forum By Sophie Hérail (CIMPA.
Geometry Services for ISO – STEP standards linking product definition, management and visualization in the value chain Jean Brangé :
System Modeling Assessment & Roadmap Joint OMG/INCOSE Working Group
SysML Overview October 19, 2004 Sanford Friedenthal
Engineering IT Summary & Recommendations
Presentation transcript:

© PDES, Inc Modular STEP Application Protocol Content, Status, and Use Charlie Stirk Technical Advisory Committee Chair PDES Inc.

© PDES, Inc Outline Overview of PDES & STEP modular standards Update on STEP for 3D CAD Product Life Cycle Support & OASIS DEX Systems Engineering

© PDES, Inc SCRA HOST CONTRACTOR THE BOEING COMPANY LOCKHEED MARTIN IBM PTC RAYTHEON ROCKWELL COLLINS NARANASANIST GEORGIA TECH SANDIA NATIONAL LABORATORIES/ KCP PDES, Inc. ® JOTNE EPM TECHNOLOGY NorwaySweden EUROSTEP UK THEOREMSOLUTIONS Germany LKSOFT France AIRBUS PDES, Inc. Members United States COSTVISION ADOBE CCAT DSN INNOVATIONS MECHDYNE CAPVIDIA INTERNATIONAL TECHNEGROUP BAE SYSTEMS BAE SYSTEMS Belgium PURDUE

© PDES, Inc PDES, Inc. Members as of March 2010 Industry Large Vendor Small VendorGovernmentUniversityNon-Profit AirbusAdobeCostVisionNARAGeorgia TechCCAT BAE SystemsIBMEurostepNASAPurdueDSN Innovations BoeingPTCITINIST Lockheed Martin JOTNE EPM Technology Sandia Nat’l Labs RaytheonMechdyne Rockwell CollinsLKSoft Theorem Capvidia

© PDES, Inc PDES Organization Update Revised PDES membership agreements –Small Vendor – reduced to 400 hours or $6,000 –University – no staff hour requirements, yearly report instead LTDR re-established for non-aerospace applications –Long Term Data Retention –Eg. Shipbuilding, vehicles, construction, nuclear plants –LOTAR focused on aviation requirements Ad-hoc working groups –Simulation data management –Application Programming Interfaces (API) –STEP-OAGIS harmonization –PLCS Interest Group exploring a PLCS-IF with OASIS PLCS TC

© PDES, Inc Modular STEP AP’s Application Protocol (AP) Modularization Benefits –Standards as a Database Faster revision process (months rather than years) –Interoperability of implementations through module reuse Requirements, structure, etc. Modular AP Domains –AP203 Mechanical CAD (parts & assemblies) –AP209 CAE (FEA and CFD) –AP210 EDA/MCAD (electrical and mechanical assemblies) –AP233 Systems Engineering –AP239 Product Life Cycle Support (PLCS)

© PDES, Inc Mandates for ISO (STEP) 7 requirement for Computer-Aided Engineering, Design and Manufacturing systems used by NASA to have interchange tools that support ISO –NASA-STD-2817 Chief Information Officer (1999) “procure all product/technical data in attachment (1) digital formats and ensure product model data meets ISO/STEP requirements specified in attachment (1).” –ASN RDA Memo by John Young, Oct. 23, 2004, STEP for 2-D and 3-D CAD “implement a similar approach that adopts ISO to enhance interoperability” as described in Young memo above –OSD ATL Memo by Ken Krieg, June 21, 2005, STEP for UID “Ratifying nations agree to apply ISO for product data management in cooperative NATO acquisition programs.” –NATO STANAG 4661, ratified by US “The PM shall require the use of International Standards Organization (ISO) 10303, Standard for Exchange of Product (STEP) Model Data, AP239, Product Life Cycle Support, for engineering data “ –AFI , April 17, 2009, PLCS for engineering data

© PDES, Inc What’s New in AP203ed2? Published by ISO in 2009 New capabilities –Catalog Data –Composite Structure & Shape –GD&T –Validation Properties –Draughting –3D Camera Views –External Libraries Test Model for Supplemental Geometry

© PDES, Inc Been in 203, but little used Beyond Geometry –Requirements –Functional Breakdowns –Activity, Work Order –Project, Contract –Information Rights –Approvals –Security Classification –Product Concept Can associate these with other model entities Future use in CAD-PDM Production Model

© PDES, Inc Conformance to AP203ed2 Test Model for User Defined Attributes 77 Conformance Options –Advanced B-Rep. –Colors and Layers –Construction Geometry –Edge Based Wireframe –Enhanced Assembly –Materials –Person and Organization –Product Configuration … Conformance Class –Part and Version ID –Part View Definition

© PDES, Inc CAx-Implementer Forum Joint testing effort of PDES Inc. & ProSTEP iViP –Participants: Adobe, AutoDesk, CostVision, Dassault Systemes, DataKit, Eurostep, ITI TranscenData, Kubotek, PTC, Siemens, T-Systems, Theorem Solutions, Vistagy Bi-annual rounds of testing of CAD data exchange –Cooperate on implementing STEP –Accelerate translator development –Promote interoperability –Scope is AP203 and AP214 Test Model for PMI Semantic Presentation and Representation

© PDES, Inc CAX-IF Benefits Individual results covered by non-disclosure –Publish only aggregate results Regular conference calls to discuss test rounds Draft Recommended Practices documents to guide implementation Alternate meetings Spring in US and Fall in Europe Test Model for PMI Polyline Presentation

© PDES, Inc CAx-IF Test Cases Past Functionalities Tested Density and Material Name Supplemental Geometry Wireframe Geometry External References Colors, Layers & Groups Cloud of Points AP Interoperability Current Test Cases Geometric Validation Properties PMI Polyline Presentation PMI Representation and Presentation User Defined Attributes Problematic production models Composites

© PDES, Inc Composites Composite meta-data Ply orientation angle and thickness Material specification Shape 2 ½ D wireframe and surfaces Explicit solids Shared between AP203ed2 for CAD AP209ed2 for CAE Composite Design

© PDES, Inc AP209ed2 Multidisciplinary Analysis and Design Combines CAD, CAE, PDM capabilities –Superset of AP203ed2 –Finite Element Analysis (FEA) –Computational Fluid Dynamics (CFD) –General numerical analysis –Shares base analysis models with AP233 Systems Engineering Developing binary API –Based on open source HDF5 toolkit Simulation Data Management (SimDM) project –Analysis data management –Repository for archiving –Interfaces to commercial and proprietary simulation tools Publically sharable Finite Element Model for testing

© PDES, Inc AP210ed2 Electro-Mechanical Projects Current projects 3D multi-domain component models and central repository Schematics data exchange model with IPC Existing implementations DFM and DFT Rule Checkers Gerber to AP210 translator Visualization/virtual product walkthroughs ECAD-MCAD data exchange Previous implementations PCB stackup design and warpage analysis

© PDES, Inc Convergence of AP203 (Aero) and AP214 (Auto) Create single superset standard for MCAD –203 x 214 = 242 –Modularization for interoperability across domains –Already harmonized for geometry (translators handle both) 214 adds the following capabilities –Manufacturing process planning Relate plans, operations, tools, raw/in-process/finished, projects, other activities, etc. –Kinematics –Machining Features –OMG PLM Services (web services API) for Engineering Change Enable association with 203 unique capabilities –Catalog, Composites, Construction History, Requirements

© PDES, Inc Proposed New Functionality for AP 242 3D shape quality 3D parametric / geometric constraints design 3D kinematics assembly 3D GD&T at assembly level Sustainability information Access rights / Digital Rights Management Software / mechatronics 3D electrical harness 3D piping - more -

© PDES, Inc Benefits of 242 For Standards Developers –Eliminates overlapping development and maintenance –Eliminates time consuming harmonization Software Vendors –Upward compatibility for existing implementations –Single standard so reduced cost and time to conform –Combination of 203- and 214-unique capabilities can lead to new software capabilities End Users –Unified approach to PDM exchange –Interoperability with other domains such as CAE, PLCS, SE

© PDES, Inc Product Life Cycle Support (PLCS) 20 Product Description Capability to define product requirements and configuration, including relationships between parts and assemblies in multiple product structures (as-designed, as-built, as-maintained) Work Management Capability to request, define, justify, approve, schedule and capture feedback on work (activities) and related resources. Property, State and Behaviour Capability that describes and captures feedback on product properties, operating states, behaviour and usage Support Solution and Environment Capability to define the necessary support for a given set of products in a specified environment and to define support opportunity, facilities, personnel and organizations AP 239 Capabilities AP 239 Capabilities

© PDES, Inc PLCS - Information Modeling Principles 21  Create a durable data model standard that can be extended/adapted over time without re-modelling or re-ballot  Identify key generic concepts and relationships  Extend/adapt by classification and reference data libraries  Build on existing standards:  PDM Schema and the STEP Modular Architecture  Accommodate values that change over time  Support multiple values for the same property  Support back-tracking & audit  Maintain unambiguous histories  Product Structure, State, Activity  Aim: enable optimisation of support through life

© PDES, Inc Mapping with Reference Data Entities/relationships 233/239 are general –e.g. Product, Activity, Product_relation –Most entities are subtypes of Product e.g. Requirement, Part, Interface, … Inherit structure and relationships of Product Other subtyping is by classification assignment –Specialization of entities/relationships/attributes –External classes of reference data –e.g. INCOSE subtypes for requirement_version Functional, Performance, Reference, Validation, … –Map to a domain by developing reference data

© PDES, Inc OASIS DEX Architecture Reference data in Web Ontology Language (OWL) tailors to domain Templates are assembled into Data EXchange Specification (DEX) Open source infrastructure and free development tools Web Ontology Language (OWL) for Reference Data Library (RDL) Semantics

© PDES, Inc Extension by Subtyping ISO Information Model OASIS Taxonomy

© PDES, Inc ISO Information Model OASIS Taxonomy XML exchange document Classification says “Activity x” is classified as a “Repair” XML Schema Is generated from Is validated against Solid box is an instance of Activity named “Activity x” Empty box is an instance of Classification

© PDES, Inc STEP AP 233 Systems Engineering Sister standard to PLCS –Share 70% of model content –Same modeling patterns –Implementation similarly through reference data INCOSE Professional Society Support –AP233 developed alongside SysML from same INCOSE concept model –AP233 received INCOSE Product of the Year 2009 Working Group Award (Model Driven System Design Group) Publish as International Standard in 2010 –Information modeling is complete

© PDES, Inc What Does AP233 Enable? Program management –Issue Activities Approvals –Risk Probability & Consequence Source & Impact Contingency plans –Project Organizational structure Project breakdown Schedule Work structure Management information resources System modeling –Decision support Requirements management Measures of effectiveness Analysis interface Verification & Analysis Justification –System structure Product data management Breakdown Interface –System behavior Function based behavior State based behavior

© PDES, Inc AP233 Implementations Migration between versions of SE tools UGS Slate to UGS Systems Engineering Exchange between Requirements Management tools IBM Requisite Pro and Telelogic DOORS Model management of SysML and interoperability with other domains i.e. Risk, Program/Project, downstream CAD/CAM, PLCS DoDAF to AP233 for exchange and archive CADM representation of views Multi-domain simulation management Requirements through analysis – EU Vivace & Crescendo Earned Value Management XML Schema mapping into 233 reference data Associate cost & schedule with systems engineering.. And remember PLCS implementations are AP233 implementations where they overlap

© PDES, Inc Systems EngineeringPLCS Risk Management State Machines Function Diagrams V & V Link to Analysis Change Management Product Structure Requirements Management Schedule Activities Organizations Property Classification Approvals, Security, Status Maintenance Support Tasks APSI Support History Messaging They share a common core! Issue WBS

© PDES, Inc AP233 AP209 Drawings Construction History GD&T Presentation 3D Models Change Management Product Structure GD&T Property Classification Approvals, Security, Status Risk Management State Machines Function Diagrams V & V Schedule Issue Composite Structure Analysis Management Requirements Mgmt. Organizations Schedule

© PDES, Inc AP233 AP210 Risk Management State Machines Function Diagrams V & V Link to Analysis Change Management Product Structure Requirements Management Schedule Activities Organizations Property Classification Approvals, Security, Status Netlists Production Rule Interfaces Evaluation Results Requirement Allocation Issue Multi-level Tech Component Models Design Models Simulation Models Constraints

© PDES, Inc PLCS Edition 2 Incorporate required changes identified from PLCS deployments New capabilities from 233 Systems Engineering Risk, Decision Support, Verification & Validation Compatibility with 203ed2 through STEP modules as a database publication Information modeling complete and now moving through the ISO ballot process

© PDES, Inc STEP is Most common CAD exchange format Interoperable with other engineering domains Usable across the life cycle Extendable with reference data Supporting web services and SOA Mandated for government programs Harmonizing with other standards

© PDES, Inc Questions? Charlie Stirk CostVision Inc., Boulder, CO