Transcript Interim SCIM and STEP Implementation 2009 System

Interim SCIM and STEP Implementation
2008 NSRP System Technology Panel Project
Ted Briggs, Intergraph Corp.
Mike Olson, Northrop Grumman Information Systems
Ron Wood, Northrop Grumman Shipbuilding
Pete Lazo, Product Data Services
Ben Kassel, NSWC CD
Shipbuilding Data Exchange Problems
–
–
–
–
Proprietary exchange formats
Point to point interfaces
3D geometry not linked with ship design data
AP 203/214 STEP geometry only
Addressed through use
of standards
Problem with commercial
CAD translators for the
foreseeable future.
Analysis Tools
Shipyard
CAD File
CAD Tool
Navy
Integrated
Prod. Data Env.
(IPDE)
Design
Data
Design
Tools
Design
Data
10/23/2009
SNAME 2009
Class Society
Other
IPDE
2
Current Ship Programs
10/23/2009
SNAME 2009
3
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
10/23/2009
SNAME 2009
4
NPDI Scope
Tool Integration
Other Shipyards
Ext. Application
MRP
Procurement
Publishing
Collaboration
Reqts. Mgmt.
Logistics Support
Test
Construction
Planning
Material Mgmt.
Engineering
Design
Integrated Product Development Environment (IPDE)
Data Exchange
IPDE Core Capabilities
Product Data Management
• Configuration Mgmt
• Change Mgmt
• Status Dep. Mgmt
• Document Mgmt
•
•
•
•
Product Data Access
Product Model Navigation
Collaboration Tools
Visualization Tools
Reporting Tools
•
•
•
•
Process Control
Access Control
Requirements Tracking
Work Authorization
Reconfigurable IPDE
Product Data Manager
10/23/2009
SNAME 2009
5
NPDI SCIM
Preliminary
Concept
Detail
Construction/Test
In Service Support
Decomm.
Milestone Reviews/
Decision Points
IPDE/PDMs maintained by
Maintenance Contractor
SCIM
IPDE/PDM maintained by Design Agent/Builder
To
External Systems/
IPDEs
10/23/2009
Archive
SNAME 2009
6
Panel 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
10/23/2009
SNAME 2009
7
Panel Project (Cont.)
 Scope
–
–
–
–
Develop linkage between AP 214 and SCIM file
Ship and Molded Form test cases
Structural test cases
Piping test cases
 Deliverables
– Test Cases
– SPS paper – technical approach
– Final Report – includes SCIM recommendations
10/23/2009
SNAME 2009
8
Current Situation for IPDE
 3D geometry linked with CAD Attributes
Shipyard
CAD Tool
Integrated
Prod. Data Env.
(IPDE)
CAD
Translator
CAD Files
Visualization Files
Design Data
AP 214
3D Shapes
10/23/2009
IPDE
Translator
Design
Tools
XML PDM
Attr
Attributes from PDM tool
(Ship program specific)
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
XML CAD
Attr
Attributes from CAD tool
(CAD vendor specific)
SNAME 2009
9
CAD Translator Example - ISDP
STEP AP 214 File
#1012=PRODUCT(':1440232005.m:1412:170347:40:',':1440232005.m:usr:avlpd609005_00','equipment',(#
1002));
#1013=PRODUCT_RELATED_PRODUCT_CATEGORY('item','',(#1012));
#1014=PRODUCT_DEFINITION_FORMATION_WITH_SPECIFIED_SOURCE(':1440232005.m:1412:1703
47:40:','equipment',#1012,.NOT_KNOWN.);
#1015=PRODUCT_DEFINITION('','equipment',#1014,#1003);
#1016=PRODUCT_DEFINITION_SHAPE(':1440232005.m:usr:avlpd609005_00','equipment',#1015);
XML Attribute File
<ss_om_eqp comp_path=":1440232005.m:usr:avlpd609005_00"
comp_tagx=":1440232005.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-51401-18" 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="5-33-0-Q" sirobid="NULL" mark_user="double 0" sirid="81290-0001-1"
system_name="RAC" zone_number="1440" />
<ss_om_cs matrix="doubles 16 0 -1 0 -39750 1 0 0 4200 0 0 1 7964.4 0 0 0 1" />
</ss_om_eqp>
10/23/2009
SNAME 2009
10
CAD Translator Example - CATIA
XML Atribute File
<RootProduct SP="4" CATIA="B18" CATSync="3.3.2"
#13=PRODUCT_DEFINITION('BR549501XXXDG00000','
RevItem="-1" Version="---"
',#6,#3) ;
PartNumber="BR549501XXXDG00000"
#6=PRODUCT_DEFINITION_FORMATION_WITH_SPECIFIE
Effectivity="[Engineering Effectivity] (R(1 - oo))"
D_SOURCE('',' ',#5,.NOT_KNOWN.) ;
InstanceName="BR549501XXXDG00000"
#3=PRODUCT_DEFINITION_CONTEXT('part definition',#1,' ')
XMLCreationDate="Thursday 30 October 2008 11:32:16">
;
- <Product PartNumber="PLANT_AC_500_TON"
#1=APPLICATION_CONTEXT('automotive design') ;
InstanceName="B000027">
#5=PRODUCT('BR549501XXXDG00000','','',(#2)) ;
- <AttributeList>
#2=PRODUCT_CONTEXT(' ',#1,'mechanical') ;
<Attribute Name="MelID" Value="001" />
#8=PRODUCT_RELATED_PRODUCT_CATEGORY('part',$,(#
<Attribute Name="NCN" Value="4120-DA0-760895" />
25,#39482)) ;
<Attribute Name="BIWCatalogNumber" Value="000001" />
#39465=NEXT_ASSEMBLY_USAGE_OCCURRENCE('B0000
<Attribute Name="System" Value="NULL" />
27','B000027','',#13,#27,' ') ;
<Attribute Name="CompartmentNumber" Value="x-xx-x-x" />
#27=PRODUCT_DEFINITION('PLANT_AC_500_TON','
<Attribute Name="CompartmentFunctionNumber"
',#26,#3) ;
Value="5016"
/>
#26=PRODUCT_DEFINITION_FORMATION_WITH_SPECIFI
<Attribute Name="DamageControlClassification"
ED_SOURCE('Added maint space for condenser and chiller
Value="NULL" />
tubes removal',' ',#25,.NOT_KNOWN.) ;
<Attribute Name="NavyComponentNumber" Value="NULL" />
#25=PRODUCT('PLANT_AC_500_TON','','ENGINEERING
<Attribute Name="Service" Value="NA" />
DIAGRAM FOR AC PLANT, RAFT AND HARD MOUNTED
<Attribute Name="DiagramNumber" Value="001" />
EQUIPMENT',(#2)) ;
<Attribute Name="DrawingNumber" Value="001" />
#44957=NEXT_ASSEMBLY_USAGE_OCCURRENCE('B0000
<Attribute Name="PieceNumber" Value="C0002" />
94','B000094','',#13,#39484,' ') ;
<Attribute Name="FindNumber" Value="AC PLANT NO. 4" />
#39484=PRODUCT_DEFINITION('EVAC_ASSY_500T_
<Attribute Name="ARFC" Value="RFS-BW-000" />
AC_PLANT',' ',#39483,#3) ;
<Attribute Name="Remarks" Value="NULL" />
#39483=PRODUCT_DEFINITION_FORMATION_WITH_SPEC
<Attribute Name="NormalValvePosition" Value="NA" />
IFIED_SOURCE('',' ',#39482,.NOT_KNOWN.) ;
<Attribute Name="MountingMethod" Value="NA" />
#39482=PRODUCT('EVAC_ASSY_500T_
<Attribute Name="Tightness" Value="NA" />
AC_PLANT','','DEVELOPED FROM: YORK INTERNATIONAL;
………..
DWG NO. 376-92108-000, REV
</AttributeList>
C.\X2\0009\X0\CONNECTIONS PER ANSI B16.22 AND MIL</Product>
10/23/2009
SNAME 2009
11
V-24578 ',(#2)) ;
STEP AP 214 File
Geometry vs Product Structure
AP203 or AP214 define shape
using explicit geometry.
1
11
12
2
21 22
3
31
32
4
41
42
51
52
SCIM defines product structure,
design parameters, and the
relationships between objects.
10/23/2009
SNAME 2009
12
Interim SCIM Approach
Commercial
CAD
Translator
AP 214
Linkage
between
geometry
and attributes
XML
SCIM
CAD
System
XML CAD
Attr
CAD DB
Interim
SCIM
Translator
PDM
System
Transform proprietary XML data into SCIM format,
adding additional PDM data
10/23/2009
SNAME 2009
13
Technical Approach
 All geometry is contained in AP 214 file
– Externally referenced from SCIM file
– Modify SCIM schema to add external reference
 All product structure is contained in SCIM file
– Ignore AP 214 assembly structure
 Create SCIM file based on information in CAD XML
file, CAD database and/or PDM system
10/23/2009
SNAME 2009
14
Test Case Methodology
 Define instance diagram
– Defines key objects and relationships
 Generate AP 214 file and CAD XML file
 Hand populate spreadsheet with SCIM attributes
 Generate XML SCIM Test Case File from
spreadsheet
10/23/2009
SNAME 2009
15
ISE Test Ship – TWR841
This ship is used to locate
and retrieve torpedoes and
missile drones. It has a
maximum payload capacity
of 42 long tons which
includes the deck cargo
plus full liquids, full
complement, and normal
stores.
10/23/2009
This ship was selected because
it is in-service, has a complete
set of drawings available for
distribution, and is:
Approved for Public Release:
Distribution Unlimited.
SNAME
16 2009
TWR Molded Forms
10/23/2009
SNAME 2009
17
AP 216 Instance Diagram
Ship
Global Axis Placement
Principal Characteristics
Spacing Table
Moulded Form
Functional Definition
Moulded Form
Moulded Form
Design Definition
10/23/2009
SNAME 2009
External
Reference
18
AP 216 Spreadsheet
10/23/2009
SNAME 2009
19
AP 214 File
STEP AP 214 File
#112=PRODUCT(‘INGR_0005',‘moulded form',(#02));
#113=PRODUCT_RELATED_PRODUCT_CATEGORY('item','',(#112));
#114=PRODUCT_DEFINITION_FORMATION_WITH_SPECIFIED_SOURCE(‘INGR_0005',‘moulded
form',#112,.NOT_KNOWN.);
#115=PRODUCT_DEFINITION('',‘moulded form',#114,#03);
#116=PRODUCT_DEFINITION_SHAPE(‘INGR_00005',‘mouloded form',#115);
#474= B_SPLINE_SURFACE_WITH_KNOTS('port_mid_edge',3,1,((#458,#460),(#462
,#464),(#466,#468),(#470,#472)),.UNSPECIFIED.,.U.,.U.,.U.,(4,4),(2,2),(
0.,1.),(0.,1.),.UNSPECIFIED.);
#4418= EDGE_LOOP('',(#4338,#4348,#4351,#4353));
#4420= FACE_OUTER_BOUND('',#4418,.T.);
#4421= ADVANCED_FACE('port_mid_edge Face',(#4420),#474,.F.);
#4463= OPEN_SHELL('MF_twrhull_comp',(#4416,#4421,#4426,#4431,#4436,#4441
,#4446,#4451,#4456,#4461));
#4465= FACE_BASED_SURFACE_MODEL('MF_twrhull_comp',(#4463));
#4467= MANIFOLD_SURFACE_SHAPE_REPRESENTATION('MF_twrhull_comp',(
#4465),#111);
#4470= PRODUCT_DEFINITION_SHAPE('','moulded form design definition',#334);
#6043=SHAPE_DEFINITION_REPRESENTATION(#116,#4470);
10/23/2009
SNAME 2009
20
Summary of Findings
 Demonstrated viability of approach
– External reference mechanism will be incorporated into
SCIM
 Enhanced SCIM
– Identified need to document geometry model
• Project used AP 214 geometry
– Triggered generation of fully expanded XML schemas
– Identified need to better define mandatory attributes
 Determined use of SCIM still requires access to ISO
STEP documentation
 Identified few minor discrepancies with ISO STEP
models
10/23/2009
SNAME 2009
21