220 likes | 311 Views
Teamcenter Systems Engineering. Barbara Sheeley Matthew McEmber Systems Engineer The Boeing Company July 29, 2009. Tailored Systems Engineering Tool Suite Manage Artifacts Integrated Single Source of Data Scalable Customizable. Teamcenter System Engineering. Features & UI.
E N D
Teamcenter Systems Engineering Barbara Sheeley Matthew McEmber Systems Engineer The Boeing Company July 29, 2009
Tailored Systems Engineering Tool Suite Manage Artifacts Integrated Single Source of Data Scalable Customizable Teamcenter System Engineering
Features & UI Teamcenter Systems Engineering Systems Engineering Live Demo
Intuitive MS Window Explorer like web based user interface All objects in Teamcenter accessible via unique web addresses Change management and configuration control “Live” Microsoft Office integrations for both data input and generation of artifacts TcSE Features Security protections control user access, information access and modification privileges DoDAF module with tailored schema and OV/AV/SV view generation Allows the user to capture product decompositions and interrelate the views A natural-language report writer and robust document generator
User Interface Content Pane Navigation Pane Notebook Pane
Basic TcSE Entities Project – Root collection of Folders Building Block – Basic object used to decompose design Requirement – Uniquely identifiable Requirement Paragraph – Type of Requirement for preserving document structure as a placeholder Link – 1 to 1 directional relationship between two entities Connection – Physical connection between two physical objects Folder – Container for other objects Document – Type of folder that may contain Requirements, Paragraphs, and Building Blocks Property – Attribute of an entity (color, bit rate, prime engineer, etc) Diagram – Visio Diagram attached to an object
Great Potential for Entity Reuse Source: Siemens DoDAF Module User Manual
Systems Engineering One Architecture – multiple views captured and linked Requirements Functional Architecture ( What Has to Be Done ) Logical Architecture ( How It Is Done ) Physical Architecture (How It Is Implemented) Physical models
Which Data Would You Prefer to Work With? A: Mixed, Integrated Architectures? Vertical Integration Within Architectures B: Partitioned, Integrated Architectures? Horizontal Integration Across Architectures
Requirements Allocation Integrated Requirements Search Result: Requirements Allocation to Functions and Logical Systems
DoDAF – Operational-System Architectures OV-5 Activity Architecture OV-2 Operational Node Architecture System Function Architecture SV-4a
DoDAF – Software Architectures Activity Diagram (Rhapsody / Sparx EA) Use Case Diagram (Rhapsody / Sparx EA) DoDAF Activity Architecture Rhapsody Use Case Architecture (in TcSE) Functional Decomposition IDEF 0 Diagram
Create Ancillary Architectural Views • Spatial • Environmental Threats • Manufacturing Cells • Suppliers • Countries of Origin • etc
System Verification Spec. Search Results Enter Verification Status Excel Live Test Verification Live-link back to problem Requirement
Operational Connectivity Model with Product Overlay Source: Siemens DoDAF Module User Manual
System Connectivity Model with Product Overlay Source: Siemens DoDAF Module User Manual
Operational to System Connectivity Model with Product Overlay Source: Siemens DoDAF Module User Manual
Acknowledgements • This presentation would not have been possible without the contributions of: • John Herrold • Robert Malone