Teamcenter Systems Engineering
Barbara Sheeley
Matthew McEmber
Systems Engineer
The Boeing Company
July 29, 2009
Teamcenter System Engineering
• Tailored
Systems
Engineering Tool
Suite
• Manage Artifacts
• Integrated
Single Source of
Data
• Scalable
• Customizable
Requirements
Development
Pr
Functional
Architecture
(What Has to Be
Done)
Ve
ef
ini
t
ion
Logical
Architecture
rifi
ca
tio
na
nd
od
uc
tD
(How It Is Done)
Va
lid
ati
o
n
Physical
Architecture
(How It Is
Implemented)
Features
& UI
Teamcenter
Systems
Engineering
Systems
Engineerin
g
Live
Demo
Change
management
and
configuration
control
DoDAF module
with tailored
schema and
OV/AV/SV view
generation
Security
protections
control user
access,
information
access and
modification
privileges
Intuitive MS
Window
Explorer like
web based
user interface
TcSE
Features
A naturallanguage
report writer
and robust
document
generator
All objects in
Teamcenter
accessible via
unique web
addresses
“Live”
Microsoft
Office
integrations for
both data input
and generation
of artifacts
Allows the user
to capture
product
decomposition
s and
interrelate the
views
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
Sharing a Single Source of Data
TcSE
Document
Document
Document
Document
Office Documents, local copies, emails, etc
Integrated Single Source of Data
@#%!!!
Manually Generate Views as Documents
TcSE
Focus on Data, Generate Views
Integrate Data, Generate Views
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?
Horizontal Integration Across Architectures
Vertical Integration
Within Architectures
B: Partitioned,
Integrated
Architectures?
Requirements Allocation
Integrated Requirements
Search Result: Requirements Allocation to
Functions and Logical Systems
DoDAF – Operational-System
Architectures
OV-2
Activity Architecture
OV-5
Operational Node Architecture
SV-4a
System Function Architecture
DoDAF – Software Architectures
DoDAF Activity Architecture
Rhapsody Use Case
Architecture (in TcSE)
Use Case Diagram
(Rhapsody / Sparx EA)
Activity Diagram
(Rhapsody / Sparx EA)
Functional Decomposition
IDEF 0
Diagram
Create Ancillary Architectural Views
•Spatial
•Environmental Threats
•Manufacturing Cells
•Suppliers
•Countries of Origin
•etc
System Verification
Spec. Search Results
Excel Live Test Verification
Enter
Verification
Status
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
Live Demo
Acknowledgements
• This presentation would not have been
possible without the contributions of:
– John Herrold
– Robert Malone