Download presentation
Presentation is loading. Please wait.
1
Integrating MBSE and PLM
Wayne Collier Senior Functional Architect 1
2
Starting Point: Requirements and Trace Links
3
Starting Point: Diagram AutoLayout
3
4
Teamcenter for Manufacturing – Process BOM
5
Starting Point: Integrating Objects & Documents
6
Starting Point: WorkFlow and Change Management
6
7
The Core Product Lifecycle Management Question
Tank Check Valve Main Valve Pump P - 1 2 5 This is what the final routing system will look like. This is drawn in 2d, but pretend it is a 3d mechanical routing system. All of the occurrences are part of the fresh water system in the Aft module of the submarine – therefore, they are under the same WBS node. Note that there are NX .prt files for each piece part, but no assembly .prt for the WBS node.
8
Original Logical Design
Tank Check Valve Main Valve Pump P - 1 2 5 This is what the final routing system will look like. This is drawn in 2d, but pretend it is a 3d mechanical routing system. All of the occurrences are part of the fresh water system in the Aft module of the submarine – therefore, they are under the same WBS node. Note that there are NX .prt files for each piece part, but no assembly .prt for the WBS node.
9
Design Change #1 Drain Valve P - 3 2 4 Tank Check Valve Main Valve Pump 1 5 This change involves inserting P-3, P-4, and Drain Valve The effectivity of this change is for Tech Insertion #1 – think of it as an option. This is what the final routing system will look like. This is drawn in 2d, but pretend it is a 3d mechanical routing system. All of the occurrences are part of the fresh water system in the Aft module of the submarine – therefore, they are under the same WBS node. Note that there are NX .prt files for each piece part, but no assembly .prt for the WBS node.
10
Design Change #2 Tank Check Valve Globe Valve Pump P - 1 5 2 This change involves replacing the Main Valve with a Globe Valve. The effectivity of this change is for Tech Insertion #2 – think of it as another option. This is what the final routing system will look like. This is drawn in 2d, but pretend it is a 3d mechanical routing system. All of the occurrences are part of the fresh water system in the Aft module of the submarine – therefore, they are under the same WBS node. Note that there are NX .prt files for each piece part, but no assembly .prt for the WBS node.
11
Design Change #3 Hi Pressure Tank Check Valve Main Valve Pump P - 1 5 2 This change involves replacing the original Tank with a high pressure tank. The effectivity of this change is for Model #2. This is what the final routing system will look like. This is drawn in 2d, but pretend it is a 3d mechanical routing system. All of the occurrences are part of the fresh water system in the Aft module of the submarine – therefore, they are under the same WBS node. Note that there are NX .prt files for each piece part, but no assembly .prt for the WBS node.
12
Summary of Design Changes
Insert P3, P4, Drain Valve Replace Main Valve with Globe Valve Replace Tank with Hi Pres Tank Effectivity Tech Insertion #1 Tech Insertion #2 Model #2 and Up Before After
13
3 Independent Design Changes – Results in 8 Possible Configurations
Product Model = 1 Tech Insert #1 = No Tech Insert #2 = No Product Model = 1 Tech Insert #1 = Yes Tech Insert #2 = No Product Model = 1 Tech Insert #1 = No Tech Insert #2 = Yes Product Model = 1 Tech Insert #1 = Yes Tech Insert #2 = Yes Product Model = 2 Tech Insert #1 = No Tech Insert #2 = No Product Model = 2 Tech Insert #1 = Yes Tech Insert #2 = No Product Model = 2 Tech Insert #1 = No Tech Insert #2 = Yes Product Model = 2 Tech Insert #1 = Yes Tech Insert #2 = Yes The goal is to store all 8 configurations Without storing 8 different files
14
Way Forward Enhanced modeling of Use Cases/Operational Scenarios
Functions/Activities Networks Abstract Flows/Invocations/Signals Connections Item Flows/Messages Ports Port Sets (Interfaces) Behaviors Diagram Typing Allocations: Functions to Abstract Physical models Functions & Abstract Physical models to 2D and 3D designs Algorithms Configuration Validation and Solves Rules Solving Diagram Auto-Layouts Equivalence Transition Tool Integrations to this new model
15
What Can the Industry Do?
Push current modeling techniques to their limits of scale Document where the processes and tools break down Share these stress points with PLM vendors
16
Summary Siemens PLM Software has a long-term mandate to: Manage systems models of arbitrary scale and complexity Plants Products Infrastructure Apply engineering rules and product configuration variables to these models Support collaboration across large models Scale from single-user, local-domain models to full-system models at any level of detail Integrate systems models with Portfolio management and product planning Product configuration Engineering rules modeling Manufacturing process models MCAD and ECAD Software Development CAE (Functional and Physics-based)
Similar presentations
