Teamcenter Systems Engineering
Barbara Sheeley
Matthew McEmberSystems Engineer
The Boeing CompanyJuly 29, 2009
Teamcenter System Engineering
• Tailored Systems Engineering Tool Suite
• Manage Artifacts• Integrated
Single Source of Data
• Scalable• Customizable
Requirements
Functional Architecture(What Has to Be
Done)
Logical Architecture(How It Is Done)
Physical Architecture
(How It Is Implemented)
Product Definition
Verification and Validation
DevelopmentRequirements
Functional Architecture(What Has to Be
Done)
Logical Architecture(How It Is Done)
Physical Architecture
(How It Is Implemented)
Product Definition
Verification and Validation
Development
Teamcenter Systems
Engineering
Systems Engineerin
g
Features & UI
Live Demo
TcSE
Features
Intuitive MS Window
Explorer like web based
user interface
“Live” Microsoft
Office integrations for both data input and generation
of artifacts
All objects in Teamcenter
accessible via unique web addresses
Allows the user to capture
product decomposition
s and interrelate the
views
A natural-language
report writer and robust document generator
Security protections control user
access, information access and modification
privileges
Change management
and configuration
control
DoDAF module with tailored schema and
OV/AV/SV view generation
Content PaneContent Pane
Notebook PaneNotebook Pane
Navigation Pane
Navigation Pane
User Interface
Basic TcSE Entities
Project – Root collection of FoldersBuilding Block – Basic object used to decompose designRequirement – Uniquely identifiable RequirementParagraph – Type of Requirement for preserving document
structure as a placeholderLink – 1 to 1 directional relationship between two entitiesConnection – Physical connection between two physical objectsFolder – Container for other objectsDocument – Type of folder that may contain Requirements,
Paragraphs, and Building BlocksProperty – Attribute of an entity (color, bit rate, prime engineer,
etc)Diagram – Visio Diagram attached to an object
Sharing a Single Source of Data
Document
DocumentDocument
Document
TcS
E
Integrated Single Source of DataOffice Documents, local copies, emails, etc
Focus on Data, Generate Views
TcS
E
Manually Generate Views as Documents Integrate Data, Generate Views
@#%!!!
Great Potential for Entity Reuse
Source: Siemens DoDAF Module User Manual
Physical models
Requirements
Functional Architecture(What Has to Be
Done)
Physical Architecture
(How It Is Implemented)
One Architecture – multiple views captured
and linked
Logical Architecture(How It Is Done)
Systems Engineering
Which Data Would You Prefer to Work With?
B: Partitioned, Integrated Architectures?
A: Mixed, Integrated Architectures?
Horizontal Integration Across Architectures
Vertical Integration
Within A
rchitectures
Requirements Allocation
Integrated Requirements
Search Result: Requirements Allocation to Functions and Logical Systems
DoDAF – Operational-System Architectures
OV-2
Operational Node Architecture
OV-5Activity Architecture
System Function ArchitectureSV-4a
DoDAF – Software Architectures
DoDAF Activity Architecture
Rhapsody Use Case Architecture (in TcSE)
Use Case Diagram(Rhapsody / Sparx EA)
Functional DecompositionIDEF 0
Diagram
Activity Diagram(Rhapsody / Sparx EA)
Create Ancillary Architectural Views
•Spatial•Environmental Threats•Manufacturing Cells•Suppliers•Countries of Origin•etc
System Verification
Spec. Search ResultsSpec. Search ResultsExcel Live Test VerificationExcel Live Test Verification
Live-link back to problem RequirementLive-link back to problem Requirement
Enter Verification
Status
Enter Verification
Status
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
Live Demo
Acknowledgements
• This presentation would not have been possible without the contributions of:– John Herrold– Robert Malone