Problem establishing project org structure correctly

[Eddie K]

I am creating a project org structure with different work package groups
doing differient pieces of work...

In some instances i have work package managers with subordinates that are
themselves managers in other project areas with that original manger being a
subordinate to them and this i think is causing confusion....

Each area has a work package number

So for example,

WP 01
Eddie Keating - Manager
Fred Perry - Subordinate
Lester Piggot - Subordinate

WP02
Fred Perry - Manager
Eddie Keating - Subordinate
Lester Piggot - Subordinate

Is there a way that Visio can use the work package number as a kind of
"Primary Key" that can be used to differentiate between the different work
package areas and so reflect the project reporting lines even though there
are apparant paradoxes?

 

[Chris]

I'm pretty sure that the Org Chart, especially the automated stuff, only
supports one superior per object. There's a "dotted line relationship"
connector, but I think you add that manually, I'm not sure if that can be
configured with imported data. The sample data file shows:

Name Title Reports_To Department Telephone E-Mail Office_Number
Master_Shape

which doesn't look too good for "multiple-parents".

Can you make two different pages somehow? The WPS as one view that "obeys
the rules", and the real people on a different page? If you can somehow
massage the data to eliminate the mutliple-parents, then you'll be able to
get it to work. Otherwise you'll have to create a flowchart that just looks
like an Orgchart, and then you lose the automatic-ness of it all. Bummer.

Chris Roth
Visio MVP