Interim SCIM and STEP Implementation 2008 System Technology Panel Project Ted Briggs, Intergraph Mike Olson, Northrop Grumman Ron Wood, Northrop Grumman.

Slides:



Advertisements
Similar presentations
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
Advertisements

ISE 6 Phase 2 Demo Scenario Nov 20, Stakeholders ISEA –NSWC PHD (Combat Systems) –NSWCCD SSES (HM&E) Program Offices –PMS 500, etc. –IWS 1 (Combat.
1 IS 4420 Database Fundamentals Chapter 2: Database Development Process Leon Chen.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Configuration Management
Software Documentation Written By: Ian Sommerville Presentation By: Stephen Lopez-Couto.
System Design/Implementation and Support for Build 2 PDS Management Council Face-to-Face Mountain View, CA Nov 30 - Dec 1, 2011 Sean Hardman.
® Eurostep.ESUKPC v0.1©Copyright Eurostep Limited DoDAF CADM ISO AP233 OMG UML Converter Interim Report David Price November 2004 INCOSE/OMG Meetings.
Ship Common Information Model (SCIM)
Chapter 6– Artifacts of the process
Tango Asset Management Capabilities Presentation 1.Desktop & Web Architecture 2.Equipment Management 3.Condition Management 4.Data Mining 5.Parameter Trending.
2 Apr ‘08 1 DDG 1000 Logistics Data and Structure DDG 1000 Design Data and Structure Link between design and logistic data Current Logistics data import.
Systems Analysis and Design: The Big Picture
Vice President, Engineering NSRP Executive Director
Interim SCIM and STEP Implementation 2008 NSRP System Technology Panel Project Ted Briggs, Intergraph Corp. Mike Olson, Northrop Grumman Information Systems.
Reuse and Data Module Code Naming Considerations Mike Olson, Northrop Grumman IT Ted Briggs, Intergraph Integrated Shipbuilding Environment (ISE) ISE-6.
Agenda  Contract issues?  Review AP 214 Linkage mechanisms  Review external reference mechanisms  Populate PDM schema  Next Steps.
CSI315 Web Applications and Technology Overview of Systems Development (342)
MAHI Research Database Data Validation System Software Prototype Demonstration September 18, 2001
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Integrated Logistics Environment (ILE) NSRP Joint Panel Meeting 7 – 9 December 2010 New Orleans, LA 1 Presented by: Michael Olson Northrop Grumman Technical.
1 ILE Project Integrated Logistics Environment Kickoff Meeting Subtask 1.2 Sharing Structural Design Data with Manufacturing Systems Presented by: Michael.
Autodesk Inventor ® Professional Design, Validate and Document the Complete Machine Autodesk Inventor ® Professional Introduction.
Relationships July 9, Producers and Consumers SERI - Relationships Session 1.
Software Engineering Management Lecture 1 The Software Process.
STEP Shipbuilding Demonstration Highlights Integrated Shipbuilding Environment 4 (ISE 4) 26 June 2006 Ron Wood.
27 Apr ‘06 1 Integrated Shipbuilding Environment (ISE) Overview April 27, 2006.
1 ILE Project Integrated Logistics Environment Kickoff Meeting Location:Mystic Marriott Hotel Groton, CT Date:Thursday, June 17, 2010 Overview Presented.
1 Integrated Logistics Environment (ILE) Project Presented by : Dr. Burton Gischner Date:May 3, 2011 NSRP Joint Panel Meeting San Diego, CA.
30 April Enabling Shipbuilding Interoperability ISE-6 Project Exchange of Product Models for Life Cycle Support ISE-6 Final Demonstration Overview.
2 Apr ‘08 1 DDG 1000 Logistics Data and Structure DDG 1000 Design Data and Structure Link between design and logistic data Current Logistics data import.
1 Schema Registries Steven Hughes, Lou Reich, Dan Crichton NASA 21 October 2015.
Leading Edge Architecture for Prototyping Systems An Overview.
1 Navy Product Data Initiative Overview May 2007.
1 ILE Project Integrated Logistics Environment Kickoff Meeting Task 2 Completion of the Ship Common Information Model Presented by: Dr. Burton Gischner.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
3 February Enabling Shipbuilding Interoperability ISE-6 Project Exchange of Product Models for Life Cycle Support ISE Overview Presentation (to.
Publish ISO Technical Corrigenda for ISO , and NSRP Systems Technology Panel Project Pete Lazo Product Data Services Corporation.
Systems Analysis and Design in a Changing World, Fourth Edition
Ben Kassel NSWCCD Ted Briggs Intergraph Corporation An Alternate Approach to the Exchange of Ship Product.
Implementing Parametric CAD in STEP ???? Kenneth E. Wolsey May 16, 2007
ISE4 Alternate Demo Scenario Incorporates suggestions B. Kassel, S. Gordon, & B. Gischner with input from: T. Briggs and S. Moore May 23, 2005.
ISE4 Integrated Demo Ver 2 May 11, ISE4 Integrated Demo2 Revised Arrangements Demo Scenario Design agent –Export AP 216 hull form Navy –Import hull.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Systems Development Life Cycle
ISE 6 Phase 2 Demo Scenario Sept 11, 2008 NSWC CD.
ISE6 Demo Scenario From 8/30/2007 Telecon. 8/30/2007 ISE6 Demo Scenario 2 Demonstration Core idea: –Use of PLCS enables: Maintaining the right configuration.
Welcome and Introductions 1 Ron Wood ILE Kick-off Meeting on June 17, 2010 Technology Investment Agreement (TIA): Integrated Logistics Environment.
1 Margaret Christison Head of Product Data Standards Product Information Standards Defence Logistics 2004.
November 4, An Integrated Logistics Environment for an Effective Shipbuilding & Supporting Enterprise Prepared by: Dr. Burton GischnerElectric Boat.
1 ILE Project Integrated Logistics Environment Kickoff Meeting NPDI Project & SCIM Summary & Status Presented by: Rick Lobsitz (NGTS)
Publish ISO Technical Corrigenda for ISO , and NSRP Systems Technology Panel Project Pete Lazo Product Data Services Corporation.
March 24, ISE-6 Phase 2 Demo March 24, 2009.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
1 S HIP T ECH 2011 A S HIPBUILDING T ECHNOLOGIES I NFORMATION E XCHANGE Total Ownership Cost/Quality/Energy Efficiency Completion and Validation of the.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
1 Integration of the LCP Reporting Into the E-PRTR Scope and Technical proposal November 3rd.
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.
1 Long Term Retention of Product Model Data Ben Kassel Naval Surface Warfare Center Carderock Division Distribution Statement A : Approved For Public Release;
Technical Operations 12 th July 2010 Dr Phil Spiby Eurostep Limited Integrating Systems Engineering Information with AP233.
Slide 1 PDT Europe 2014, October 2014, Paris 1 AeroSpace and Defence Industries Association of Europe Through Life Cycle Interoperability as developed.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
TK2023 Object-Oriented Software Engineering
Software Engineering Management
Chapter 6: Database Project Management
Software Documentation
AP 231: Process Design and Process Specifications of Major Equipment
Reportnet 3.0 Database Feasibility Study – Approach
Presentation transcript:

Interim SCIM and STEP Implementation 2008 System Technology Panel Project Ted Briggs, Intergraph Mike Olson, Northrop Grumman Ron Wood, Northrop Grumman Pete Lazo, Product Data Services Ben Kassel, NSWCCD

Overview  Problem / vision  NPDI and SCIM  Project  Technical Approach  Next Steps 5/6/20092

Problem Today  Exchanging 3D geometry linked with ship design data Design Tools IPDE Analysis Tools Integrated Prod. Data Env. (IPDE) CAD Tool Shipyard LEAPS Class Society CAD Files Visualization Files Design Data Proprietary Formats - CAD Files - Design Data 5/6/20093

Vision  Exchanging 3D geometry linked with ship design data Design Tools IPDE Analysis Tools Integrated Prod. Data Env. (IPDE) CAD Tool Shipyard LEAPS Class Society CAD Files Visualization Files Design Data Standard data format Integrated 3D and design data - STEP files - NPDI SCIM files 5/6/20094

Current Programs 5/6/20095

NPDI & SCIM  NPDI(Navy Product Data Initiative) –To specify the requirements for and drive the implementation of product data systems based on an open architecture having suitable functionality and enterprise-wide interoperability to support affordable Navy ship design, construction and service life support –Initial version of the IPDE Specification has been written and delivered to the Navy for review and comment  SCIM(Ship Common Information Model) –SCIM will codify the models developed and prototyped by the ISE Project under NSRP over the past nine years –It will be a separate document from the IPDE Specification being produced by the NPDI Project, but it will be referenced by that IPDE Specification –Full version of the SCIM has not yet been completed Six of fifteen proposed chapters have been developed One of the remaining chapters deals with Product Life Cycle Support and will be based on the results of the ISE-6 Project 5/6/20096

NPDI Scope Integrated Product Development Environment (IPDE) Product Data Manager IPDE Core Capabilities Product Data Management Configuration Mgmt Change Mgmt Status Dep. Mgmt Document Mgmt Process Control Access Control Requirements Tracking Work Authorization Reconfigurable IPDE Product Data Access Product Model Navigation Collaboration Tools Visualization Tools Reporting Tools Tool Integration Material Mgmt. Collaboration Reqts. Mgmt. Logistics Support PublishingDesignEngineeringPlanningTestConstruction Ext. Application ProcurementMRP Other Shipyards Data Exchange 5/6/20097

NPDI SCIM ConceptDetailConstruction/Test In Service SupportDecomm. Milestone Reviews/ Decision Points SCIM To External Systems/ IPDEs Preliminary IPDE/PDMs maintained by Maintenance Contractor IPDE/PDM maintained by Design Agent/Builder Archive 5/6/20098

Project  Purpose –To determine the feasibility of using existing AP214 translators with NPDI SCIM data to improve the exchange of early and detail design data, and perform an initial validation of the SCIM.  Benefits –Develop an effective interim solution Develop recommendations for existing ship programs Demonstrate feasibility of using NPDI SCIM to exchange design data for DDG-1000 program and Navy LEAPS repository. –Lay groundwork for adoption of SCIM Initial validation of NPDI SCIM Generate SCIM test cases 5/6/20099

Project  Execution –Phase 1 Initial evaluation of SCIM information models Develop linkage between AP 214 and SCIM file Ship and Molded Form test cases –Phase 2 Structural test cases Piping test cases  Deliverables –Test Cases –SPS paper – technical approach –Final Report – includes SCIM recommendations 5/6/200910

Current Situation  Exchanging 3D geometry linked with ship design data Design Tools Integrated Prod. Data Env. (IPDE) CAD Tool Shipyard CAD Files Visualization Files Design Data AP 214 XML CAD Attr CAD Translator 3D Shapes Attributes in CAD tool (CAD vendor specific) XML PDM Attr Attributes in PDMtool (Ship program specific) 5/6/ Limiting factor – CAD translator No other way to extract 3D data Requires translator from vendor’s IPDE translator – usually XML based Relatively easy to modify IPDE Translator

CAD Translator Example - ISDP 5/6/ STEP AP 214 File #1012=PRODUCT(': m:1412:170347:40:',': m:usr:avlpd609005_00','equipment',(# 1002)); #1013=PRODUCT_RELATED_PRODUCT_CATEGORY('item','',(#1012)); #1014=PRODUCT_DEFINITION_FORMATION_WITH_SPECIFIED_SOURCE(': m:1412: :40:','equipment',#1012,.NOT_KNOWN.); #1015=PRODUCT_DEFINITION('','equipment',#1014,#1003); #1016=PRODUCT_DEFINITION_SHAPE(': m:usr:avlpd609005_00','equipment',#1015); XML Attribute File <ss_om_eqp comp_path=": m:usr:avlpd609005_00" comp_tagx=": m:1412:170347:40:" symbology="300:2:1:0:" class_name="VDequipment“ rep="4" macro_name="avlpd609005" macro_lib="avlpdmech03"> <ss_om_collector eqp_family="avtank01" eqp_partno="1CC97-LP-V " eqp_partrev="000" p_macro="avlpd609005" nomenclature="Receiver, Storage" mac_name="avlpd609005" /> <ss_om_collector eqp_number="RAC-TK1" eqp_descr="AC_UNIT_REFRIG_TANK" unit_number="1440" compt_number=" Q" sirobid="NULL" mark_user="double 0" sirid=" " system_name="RAC" zone_number="1440" />

CAD Translator Example - CATIA 5/6/ STEP AP 214 File #13=PRODUCT_DEFINITION('BR549501XXXDG00000',' ',#6,#3) ; #6=PRODUCT_DEFINITION_FORMATION_WITH_SPECIFIE D_SOURCE('',' ',#5,.NOT_KNOWN.) ; #3=PRODUCT_DEFINITION_CONTEXT('part definition',#1,' ') ; #1=APPLICATION_CONTEXT('automotive design') ; #5=PRODUCT('BR549501XXXDG00000','','',(#2)) ; #2=PRODUCT_CONTEXT(' ',#1,'mechanical') ; #8=PRODUCT_RELATED_PRODUCT_CATEGORY('part',$,(# 25,#39482)) ; #39465=NEXT_ASSEMBLY_USAGE_OCCURRENCE('B ','B000027','',#13,#27,' ') ; #27=PRODUCT_DEFINITION('PLANT_AC_500_TON',' ',#26,#3) ; #26=PRODUCT_DEFINITION_FORMATION_WITH_SPECIFI ED_SOURCE('Added maint space for condenser and chiller tubes removal',' ',#25,.NOT_KNOWN.) ; #25=PRODUCT('PLANT_AC_500_TON','','ENGINEERING DIAGRAM FOR AC PLANT, RAFT AND HARD MOUNTED EQUIPMENT',(#2)) ; #44957=NEXT_ASSEMBLY_USAGE_OCCURRENCE('B ','B000094','',#13,#39484,' ') ; #39484=PRODUCT_DEFINITION('EVAC_ASSY_500T_ AC_PLANT',' ',#39483,#3) ; #39483=PRODUCT_DEFINITION_FORMATION_WITH_SPEC IFIED_SOURCE('',' ',#39482,.NOT_KNOWN.) ; #39482=PRODUCT('EVAC_ASSY_500T_ AC_PLANT','','DEVELOPED FROM: YORK INTERNATIONAL; DWG NO , REV C.\X2\0009\X0\CONNECTIONS PER ANSI B16.22 AND MIL- V ',(#2)) ; XML Atribute File - - ………..

AP203 or AP214 to define shape. Explicit geometry SCIM defines product structure, design parameters, and the relationships between objects. Geometry vs Product Structure 5/6/200914

AP 214 XML SCIM CAD System Commercial CAD Translator Interim SCIM Translator PDM System Transform proprietary XML data into SCIM format, adding additional PDM data Linkage between geometry and attributes CAD DB XML CAD Attr Interim SCIM Approach 5/6/200915

Technical Approach  All geometry in AP 214 file –Externally referenced from SCIM file –Modify SCIM schema to add external refernce  All product structure in SCIM –Ignore AP 214 assembly structure  Create product structure based on information in CAD database and/or PDM system 5/6/200916

Work Remaining  TWR hull test case in progress –Discussed tomorrow in team meeting  Continue to investigate SCIM model –Presented as separate specification vice integrated schema –Separate schemas  Develop additional Phase 1 test cases  Develop Phase 2 test cases 5/6/200917

5/6/200918