1 / 17

Agenda

Agenda. Contract issues? Review AP 214 Linkage mechanisms Review external reference mechanisms Populate PDM schema Next Steps. Interim SCIM Approach. AP 214. Commercial CAD Translator. CAD System. XML CAD Attr. Linkage between geometry and attributes. CAD DB. Interim SCIM

rylee-whitehead
Download Presentation

Agenda

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. Agenda • Contract issues? • Review AP 214 Linkage mechanisms • Review external reference mechanisms • Populate PDM schema • Next Steps

  2. Interim SCIM Approach AP 214 Commercial CAD Translator CAD System XML CAD Attr Linkage between geometry and attributes CAD DB Interim SCIM Translator PDM System XML SCIM Transform proprietary XML data into SCIM format Adding additional PDM data

  3. Action Items • Ben, Art – produce small segment of STEP and XML illustrating linkage which we can use in report • Heidi – how are schema files generated, how can we modify • Heidi – How are PDM and other schemas link? • Heidi, All – how are schemas integrated into single schema • Heidi, All – discuss SCIM file format (current ARM schema) • Art – replace shape_rep with select • Pete – review impact of replacing Shape_rep • Bryan, Thomas – provide info on Atlantec referencing

  4. Action Items • Pete, Art, Ted – how to define external reference in SCIM • Ben – Are frame systems exported by CATIA? • Or must this be generated from the PDM? • Ron – provide SCIM issue spreadsheet to update • Ted, All – document format to record proposed SCIM changes and recommendations • Ted, Art – Populate TWR hull test case • Ben – Investigate SC4D from ShipConstructor

  5. Next Steps • Resolve schema issues • Define test case and who will produce • Depends on schema issues

  6. Test Cases • Moulded Form (INGR) • TWR hull • Configuration / versioning – PDM • Equipment • Map XML attributes to SCIM • Weight by grand block • MEL by compartment • Structural Detailing • Map XML attributes to SCIM • Piping • Map XML attributes to SCIM • Interim products • Ties to Atlantec – NASSCO NSRP project

  7. Technical Approach • Add Select type for external reference and Shape_repin SCIM for all shape_representation • Ties to product or product_definition in AP214 • Depends on translator • External reference • File name (URI), product.id or product_definition.id • Also direction and position • Assembly • Ignore AP214 assembly structure • Use SCIM assembly as required • SCIM - for this project using AP214 • No shape representation in SCIM • Only placement and orientation • Only explicit geometry

  8. Technical Approach • Populate via spreadsheet • Assuming not too many object types

  9. Next Meetings • Telecon – April 1 • ISE6 demo – Wed morning - possible • San Diego NSRP Panel Meeting – May 6,7 • Philadelphia NSRP Panel Meeting – Sept 15-17 • Providence SNAME – Oct - final brief • Telecon – Tues 1:00 EDT

  10. Discussion Slides

  11. SCIM File format • SCIM defines semantics, not syntax • Potentially could translate P28 back into EXPRESS • Only EPM supports? • Requirements • Populated Test Cases should be in a useful, readable format • Alternatives • P28 • ISE format – is this different? • Adopting published schema file forces choice of format

  12. SCIM • Mapping table from SCIM to STEP Shipbuilding ARM • UML model in deliverable • EXPRESS-G model exists • Created from UML?

  13. Representation • Separate AP214 to ensure receiving system can process • Could pull geometry into SCIM • Many translators would still read geometry • But more complicated – must correctly process geometry • Transforms, parametric spaces • Atalantec • Both attachment • Also extract and convert to internal rep • URI mechanism into file, mime type • General clkass, separate subtypes • Doc ref or bring in file

  14. ISDP • Last digit of product.name – version number • CATIA • Product_definition • Id (ties to Product_part_number) • Shipconstructor • SC4D format – from Marine Reporter • Developed from NSRP project with Bollinger (standard parts) • Assembly • Would like to have in SCIM or attribute file

  15. External References • External Model Module • References a AP214 file, give geometric location • Need external reference to instance within AP214 file • Assume many parts in an AP214 file • SCIM Pdm_design_definition • Now references Shape_representation • Needs to be select for Product in external file or Shape representation

  16. Versioning • Handled at file level? • ISDP • workflow • DDG • PDM system – no baseline yet • SCIM • Versioning at occurrwaance and definition level

More Related