What does the ideal TcUnified organization structure look like?

Session Number: 644
Connection/Track: Roundtable
Session Type: Roundtable
Primary Presenter: Round Table [Moderator]
Time: May 10, 2012 (01:00 PM - 03:10 PM)
Room: Tropical GH

Presentation Level: All of the above
Connection: None
Length: 85
User Role: End User of Siemens PLM Products at Company I work for (Not Siemens PLM)
Industry Presentation is Most Applicable Towards: Other
Primary Presenter Biography: Analyst Rep
Siemens Rep
User Rep - Moderator, Mark Hoover, Hoover & Nebrig, Inc.

Abstract:  The only more foundational element in TcUnified than organization is data model.  Significant system behavior builds off the organization structure.  A poorly thought out org structure can cause significant problems with modeling PLM in support of your business practices

Has anyone had an experience with an org structure that you regretted?

What do some of your org structure look like? (Draw on paper pads or white boards)

Have you modeled aspects of your org structure to enable other functionalities in the system (workflow filters, ACLs, command suppression, etc.)?

Have you considered the Aerospace and Defense Program Organization (or other industry solution) implications in how you define your org structure?

What issues have you had in changing an organization after it has been in use?