1 / 15

ILE Project Integrated Logistics Environment Kickoff Meeting

ILE Project Integrated Logistics Environment Kickoff Meeting. Subtask 1.1 Migrating VIRGINIA Class IPDE Data Presented by: Dr. Burton Gischner. Objectives. Tools and Methods for Supporting Next Generation Shipbuilding IPDE (SCIM Evaluation)

eyad
Download Presentation

ILE Project Integrated Logistics Environment Kickoff Meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ILE ProjectIntegrated Logistics EnvironmentKickoff Meeting Subtask 1.1 Migrating VIRGINIA Class IPDE Data Presented by: Dr. Burton Gischner

  2. Objectives • Tools and Methods for Supporting Next Generation Shipbuilding IPDE (SCIM Evaluation) • This task will demonstrate the capabilities of the NPDI SCIM as the means for supporting the next generation IPDE • Subtask 1.1 - Migrating VIRGINIA Class IPDE Data • This subtask will apply the tools and methods developed by the ISE team to the VIRGINIA Class IPDE data migration • Moreover, this subtask will use the NPDI Ship Common Information Model (SCIM) as the basis for this pilot • As a result, this subtask will potentially benefit the VIRGINIA program, but its primary objective will be to validate and demonstrate the capabilities of the SCIM

  3. Justification for SCIM Philosophy • Neutral file exchange requires translators from vendors • Minimal interest from CAD or PDM vendors has been shown in supporting the STEP Shipbuilding APs • Product data may reside in multiple systems of an IPDE, so (even when it is developed) a given vendor’s translator may not be sufficient • SCIM allows for neutral file exchanges using ISO 10303-28 (STEP XML) • However, it also permits the use of other XML translators which may be available on the sending or receiving systems • Such a transfer would involve the use of a “Mediator” • STEP APs contain more product model data than is available in current IPDEs or at points in the design process where data must be exchanged • Even Conformance Classes in the STEP APs do not resolve this problem • SCIM attempts to define a subset of each STEP AP that contains a minimum information model and can be supported in today’s IPDE environments • It is recognized that this minimum subset may have to be modified to meet the needs of a particular program or ship class, but in general it should be very close to the desired solution

  4. Using the SCIM • Assume that in the system below we need to transfer information to do a Pipe Stress Analysis • For Pipe P-1 the following properties are required: • Diameter • Material Description • Length • Wall Thickness P-1

  5. Location in SCIM of Needed Properties for Pipe P-1 Required Properties for P-1 are Identified in Red Entity: Required_material_description Entity: Plant_item Properties: Description Name Status Type Properties: Material_requirement_id Description Entity: Piping_system_component Entity: Piping_size_description Properties: Coating_reference Corrosion_allowance Heat_tracing_type Lining Properties: Dimensional_standard Ovality_allowance Entity: Piping_component Properties: Side_connector Standard_point PMI_record Mill_sheet_number Entity: Outside_and_thickness Properties: Outside_diameter Thickness Entity: Pipe Properties: End_1_connector End_2_connector Additional_length Entity: Inside_and_thickness Properties: Inside_diameter Thickness Entity: Straight_pipe Properties: End_to_end_length End_to_end_cut_length Cold_spring Longitudinal_welding_seam_orientation

  6. Extracting SCIM Compliant Data from the Product Model (XML Data File) Product Model Data <?xml version="1.0" encoding="UTF-8"?> <edo227d:uos xmlns:xsi="http://www.w3.org/2001/ XMLSchema-instance" xmlns:edo="urn:iso10303-28:osb/ edo" xmlns:osb="urn:iso10303-28:osb" " " xmlns:edo227d="urn:iso 10303-28:osb/Edo/Design/Detailed/Piping/Edo227_detailed_design“ xmlns:aim_mea="urn:iso10303-28:osb/Aim/Aim_geometry/“ <!-- ************** APPLICATION INSTANCES **************--> <ppid:Straight_pipe_def_Key x-id="i872" x-href="CDM" x-model= "VICTOR_BEND_AND_ELBOW" Id="*ASEG34" x-rev="" x-owner= "i870" x-ob="i872.N10FFD"/> <ppid:Straight_pipe_def x-id="i872.N10FFD" End_to_end_length= "NaN" Size-r="i872.N11006"/> <psit:Size_description x-id="i872.N11006" Outside_diameter="88.9“ Thickness="" Nominal_size="88.9"/> <mat:Material x-id="i870.N10FB2" Id="ASTM A 53" Selection_type= "Carbon steel"/> <ppi:Straight_pipe_part_Key x-id="i953" x-href="CDM" x-model= "VICTOR_BEND_AND_ELBOW" x-rev="" x-owner="i953.N10F9A“ x-ob="i953.N10FA6"/> <pdm:Product_item_master_Key x-id="i953.N10F9A" Id=“ *ASEG35"/><ppi:Straight_pipe_part x-id="i953.N10FA6 " Description="" pdma:Part_item_to_definition-r="i955" ppi: End1-r="i983" ppi:End2-r="i994" Materials-r="i953.N10FB2"/> <mat:Material x-id="i953.N10FB2" Id="ASTM A 53" Selection_type="Carbon steel"/> <ppi:Swept_bend_pipe_part_Key x-id="i1026" x-href="CDM" </edo227d:uos> Piping Detail Drawing XML Extract Material File Geometry File Material for P-1 Wall Thickness of P-1 Length of P-1 Diameter of P-1 P-1 Sending IPDE File in XML Format (with SCIM Properties)

  7. Mediator Tool Maps SCIM Properties Between Sending and Receiving XML Formats <?xml version="1.0" encoding="UTF-8"?> <edo227d:uos xmlns:xsi="http://www.w3.org/2001/ XMLSchema-instance" xmlns:edo="urn:iso10303-28:osb/ edo" xmlns:osb="urn:iso10303-28:osb" " " xmlns:edo227d="urn:iso 10303-28:osb/Edo/Design/Detailed/Piping/Edo227_detailed_design“ xmlns:aim_mea="urn:iso10303-28:osb/Aim/Aim_geometry/“ <!-- ************** APPLICATION INSTANCES **************--> <ppid:Straight_pipe_def_Key x-id="i872" x-href="CDM" x-model= "VICTOR_BEND_AND_ELBOW" Id="*ASEG34" x-rev="" x-owner= "i870" x-ob="i872.N10FFD"/> <ppid:Straight_pipe_def x-id="i872.N10FFD" End_to_end_length= "NaN" Size-r="i872.N11006"/> <psit:Size_description x-id="i872.N11006" Outside_diameter="88.9“ Thickness="" Nominal_size="88.9"/> <mat:Material x-id="i870.N10FB2" Id="ASTM A 53" Selection_type= "Carbon steel"/> <ppi:Straight_pipe_part_Key x-id="i953" x-href="CDM" x-model= "VICTOR_BEND_AND_ELBOW" x-rev="" x-owner="i953.N10F9A“ x-ob="i953.N10FA6"/> <pdm:Product_item_master_Key x-id="i953.N10F9A" Id=“ *ASEG35"/><ppi:Straight_pipe_part x-id="i953.N10FA6 " Description="" pdma:Part_item_to_definition-r="i955" ppi: End1-r="i983" ppi:End2-r="i994" Materials-r="i953.N10FB2"/> <mat:Material x-id="i953.N10FB2" Id="ASTM A 53" Selection_type="Carbon steel"/> <ppi:Swept_bend_pipe_part_Key x-id="i1026" x-href="CDM" </edo227d:uos> Mediator Note: For Discussion about Creation of Mediators , see Slide #9 <?xml version="1.0" encoding="UTF-8"?> <edo227d:uos xmlns:xsi="http://www.w3.org/2001/ XMLSchema-instance" xmlns:edo="urn:iso10303-28:osb/ edo" xmlns:osb="urn:iso10303-28:osb" " " xmlns:edo227d="urn:iso 10303-28:osb/Edo/Design/Detailed/Piping/Edo227_detailed_design“ xmlns:aim_mea="urn:iso10303-28:osb/Aim/Aim_geometry/“ <!-- ************** APPLICATION INSTANCES **************--> <ppid:Str_pipe_def_Key x-id="i872" x-href="CDM" x-model= "BEND_AND_ELBOW" Id="*ASEG34" x-rev="" x-owner= "i870" x-ob="i872.N10FFD"/> <ppid:Str_pipe_def x-id="i872.N10FFD" End_to_end_len= "NaN" Size-r="i872.N11006"/> <psit:Size_desc x-id="i872.N11006" Outside_diam="88.9“ Thick="" Nominal_size="88.9"/> <mat:Matl x-id="i870.N10FB2" Id="ASTM A 53" Selection_type= "Carbon steel"/> <ppi:Str_pipe_part_Key x-id="i953" x-href="CDM" x-model= "BEND_AND_ELBOW" x-rev="" x-owner="i953.N10F9A“ x-ob="i953.N10FA6"/> <pdm:Product_item_master_Key x-id="i953.N10F9A" Id=“ *ASEG35"/><ppi:Str_pipe_part x-id="i953.N10FA6 " Desc="" pdma:Part_item_to_definition-r="i955" ppi: End1-r="i983" ppi:End2-r="i994" Matls-r="i953.N10FB2"/> <mat:Matl x-id="i953.N10FB2" Id="ASTM A 53" Selection_type="Carbon steel"/> <ppi:Swept_bend_pipe_part_Key x-id="i1026" x-href="CDM" </edo227d:uos> Sending IPDE File in XML Format (with SCIM Properties) Receiving IPDE File in XML Format (with SCIM Properties)

  8. SCIM Data is Loaded into an IPDE where Analysis will be Performed (XML Data File) P-1 <?xml version="1.0" encoding="UTF-8"?> <edo227d:uos xmlns:xsi="http://www.w3.org/2001/ XMLSchema-instance" xmlns:edo="urn:iso10303-28:osb/ edo" xmlns:osb="urn:iso10303-28:osb" " " xmlns:edo227d="urn:iso 10303-28:osb/Edo/Design/Detailed/Piping/Edo227_detailed_design“ xmlns:aim_mea="urn:iso10303-28:osb/Aim/Aim_geometry/“ <!-- ************** APPLICATION INSTANCES **************--> <ppid:Str_pipe_def_Key x-id="i872" x-href="CDM" x-model= "BEND_AND_ELBOW" Id="*ASEG34" x-rev="" x-owner= "i870" x-ob="i872.N10FFD"/> <ppid:Str_pipe_def x-id="i872.N10FFD" End_to_end_len= "NaN" Size-r="i872.N11006"/> <psit:Size_desc x-id="i872.N11006" Outside_diam="88.9“ Thick="" Nominal_size="88.9"/> <mat:Matl x-id="i870.N10FB2" Id="ASTM A 53" Selection_type= "Carbon steel"/> <ppi:Str_pipe_part_Key x-id="i953" x-href="CDM" x-model= "BEND_AND_ELBOW" x-rev="" x-owner="i953.N10F9A“ x-ob="i953.N10FA6"/> <pdm:Product_item_master_Key x-id="i953.N10F9A" Id=“ *ASEG35"/><ppi:Str_pipe_part x-id="i953.N10FA6 " Desc="" pdma:Part_item_to_definition-r="i955" ppi: End1-r="i983" ppi:End2-r="i994" Matls-r="i953.N10FB2"/> <mat:Matl x-id="i953.N10FB2" Id="ASTM A 53" Selection_type="Carbon steel"/> <ppi:Swept_bend_pipe_part_Key x-id="i1026" x-href="CDM" </edo227d:uos> XML Load Program Analysis Diameter Material Results Receiving IPDE File in XML Format (with SCIM Properties) Length Thickness IPDE Common Services

  9. Generation of Mediator Software (XML Mapping File) (XML Mapping File) Mapping from Sending IPDE to SCIM Mapping from Receiving IPDE to SCIM Mediator Generator The Mediator Generator is a generic piece of software for each application area that reads the mapping tables for any two systems and creates a Mediator between those mappings A Mediator is an XSL stylesheet that reads a compliant XML file from the Sending System and produces an XML file that can be read by the Receiving System Mediator

  10. SCIM-compliant Part 28 File • If both systems support ISO 10303-28 (STEP XML) then a Mediator is not required • The IPDE shall be able to receive product model data in the same SCIM-compliant XML format for each of these application areas

  11. VIRGINIA Class IPDE Data Migration • VIRGINIA Class submarine is in the midst of its production cycle with several more hulls pending • VIRGINIA Class IPDE platform is approaching its end of life and EB is in the process of implementing a new next generation IPDE • VIRGINIA Class IPDE is a highly customized solution that evolved and grew as the VIRGINIA Class design progressed and as new requirements and issues revealed themselves • Thus, the exact entities, attributes, properties, and relationships that must be migrated to the new IPDE are not obvious • Several difficult technical questions must be resolved before a successful data migration can be completed

  12. Extraction of Piping & Structural Models • SCIM is intended to provide the information requirements to guide the extraction of product data and specifies the entities, attributes, and properties required in each discipline • SCIM was not available in time to support early efforts of VIRGINIA data migration • Thus this task will be primarily focused on validating the SCIM, rather than on assisting VIRGINIA Class data migration • Focus will be on Piping & Structural Models • These represent a major portion of the VIRGINIA product model • SCIM chapters relating to these disciplines have already been completed • Piping & Structural Models will be extracted from the current CATIA / CDM IPDE and transformed to SCIM representation • SCIM models will be analyzed manually to identify errors or discrepancies

  13. Load SCIM Models into NX / TeamCenter Environment • Translators and/or mediators will be developed as required to load the SCIM models into the new IPDE environment using NX and TeamCenter • These models can be evaluated in the new IPDE as far as completeness and accuracy • Models will be processed on the new system to verify their validity and completeness

  14. Validate SCIM Models - Note Any Deficiencies • Any deficiencies revealed in the SCIM chapters relating to Piping or Structures will be noted and corrected as part of Task 2 under the ILE Project • Also, if difficulties are encountered in using the SCIM because of incompleteness or lack of clarity in the SCIM descriptions, an attempt will be made during Task 2 to improve the format of all the SCIM chapters to resolve these problems

  15. Subtask 1.1 Deliverables and Milestones MonthDeliverable 2 Report on Extraction of Piping Data in SCIM Format from VIRGINIA IPDE 5 Report on Extraction of Structural Data in SCIM Format from VIRGINIA IPDE 8 Analysis of SCIM Piping & Structural Models vs. Data Needed for VIRGINIA Migration 11 Final Wrap-up Meeting & Report of SCIM Deficiencies in Piping & Structural and Recommendations

More Related