(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?
(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.
Let’s consider the simple case:
There is a project model with multiple users. Some of them are responsible for planning, change management, coordinating some subprojects, others can enter and change resource costs or just get their plans and enter actual data.
I have an experience of organizing group work with Spider Project software but am interested in the ways it is done with other tools, in particular with P6.
Let’s suppose that somebody entered actual data for certain date and others did not do the same. What happens if data dates in different subprojects are different? What if in one subproject it is necessary to update the schedule every day and for other subprojects weekly updates are sufficient?
What if some of subproject managers want to make what if analysis and to create several versions of their subproject schedules and compare them for selecting the best one?
Let’s start with these simple questions.
Printer-friendly version
Send to friend
Vladimir,
could you elaborate on how Group work is managed in Spider Project? This way we have a comparision between Spider and P6. This is a very interesting topic.
Best regards,
Bogdan
The setting is depending on the complexity of the Project (Size and Locations i.e. mega project). Overall is ONE (1) big project schedule sitting on different level of EPS. Level 1, 2, 3, 4 & 5 are overseeing by the Management Lead Planner and Area Senior Planner.
What if scenario is usually done on level 4 & level 5 Project/ sub-project level which is being reflected on control schedule. Copying, updating and changing of the Project/sub-project shall be in accordance to the procedure to avoid duplication of works and effort. As mentioned, there is schedule log accessible and updated by each user including the request for above their level of access which being monitored and managed by Lead Planner of each Project/ sub-project.
Rodel,
do you mean that Level 1 & Level 2, Level 3, Level 4 & Level 5 are different schedules?
If yes then how are they linked?
Any change at the Level 5 must be seen on upper levels, isn't it?
The scheduler works with the copy of the whole project or with the copy of his subproject?
If the whole project must be copied then there is a problem if several schedulers created several copies simultaneously changing their parts.
If subprojects are copied then the group work means that each responsible scheduler is authorised to make changes in his/her area only. The whole model must be divided into responsibility areas and it is not permited for several persons to edit the same parameters.
Is this right?
Depending on users responsibilties and security limitation on the project/ subproject they are working and where the user share the projects.
For Example :
Level 1 & Level 2 - Management Schedule - Head Office (Master Project - Overall all integrated Project schedule)
- being manage by Management Lead Planner, Senior Area Planner, Area Planner
Level 3 - Project Controls Area Schedule (Main Projects - Integrated Project)
- being manage by Project Controls Lead Planner, Senior Planner, Planner
Level 4 & Level 5 - Projects/ Sub-projects - (Integrated sub-projects per locations)
- Being manage by Project Lead Planner, Senior Planner, Planner
- As they running different Calendars cut-off per location - as per Calendar reporting cycle date stated on the Procedures per project requirements.
"I don't understand the way to make changes in the initial subproject after playing what if and creating new version with changed activities, dependencies and resources. You wrote that "Importing a copied version of project is not allowed". Does it mean that the planner must repeat all changes that were made manually in the original subproject model?"
Yes - importing a copied version of project is not allowed. It means that the planner must work on the copy of the project on same P6 database and not on external database (this is to ensure the integrity of the data). The planner does not need to repeat all changes as it was on the same database and put the request on re-link and de-link the active replacing current active as I mentioned as part of the procedure.
Delete
Thank you Rodel!
It looks like the full scale group work with the project model can be organized by dividing it in accordance with responsibility structure to a set of subproject models with master project where inter-subproject dependencies were defined and stored.
Each user works with designated model and master project collects all information.
One of known P6 advantages is an ability of multiple users to work with the same project model. But it looks like each user must have special model to work with.
Is this right?
I don't understand the way to make changes in the initial subproject after playing what if and creating new version with changed activities, dependencies and resources. You wrote that "Importing a copied version of project is not allowed". Does it mean that the planner must repeat all changes that were made manually in the original subproject model?
Please delete
Please delete
Delete. I have problems with saving posts
I also have a wide experience in running group work in P6 Environment composed of different countries and different time zone and different resources. It can only be done on Enterprise version and not standalone. A proper planning procedure and documentation is a must and educate all the user within the group. The setup is using a Enterprise level to integrate all the projects and sub-projects. A high-level master project will integrate all the project and sub-project within different EPS level. An OBS structure will be properly define and setup to different level of security profile for each users profile of each project and depending on category of the user functions. A global Activity code will be used with limited access to each level of users. Global resources are also limited access to each level of users and countries they are being shared. Each project and sub-project can be updated with different timing, data date on each location as long as the Master will be schedule with the same data date on each month. The naming convention of each project is properly defined in accordance to the procedure. The active project will have standard naming convention and have a designated place holder on the each EPS level to ensure that the main administrator will be aware on which is the active project to call for each cut-off when running the Master Project report. A project / sub-project can be copied and create a several versions and run a different what if scenario as long as it follows the procedure when copying the project/ sub-project to ensure that the integrity of the data was maintained such as external link to each project and master project including the global activity code. Importing a copied version of project is not allowed to ensure the validity and integrity of all data are maintained in accordance to procedure but exporting is allowed anytime. A log register is maintained, accessible to all users including all the changes and request for changes that beyond their access. This includes the request of data validation, link and del-link of new active projects/ subproject when replacing the project/ subporoject in the active place holder. All of these are clearly discussed on the procedure.
Email: PPadmin@planningplanet.com
It is interesting that I did not see posts in this discussion for quite a long time and so I missed Bogdan's post.
In Spider Project senior planner creates project Responsibility Structure - one of multiple WBSs that can be created in Spider Project for the same project. He/She also assigns project users responsible for project phases (elements of Responsibility WBS).
Project can be linked with different reference-books (databases), including databases of project resources, materials, etc. and changes in these databases can be transfered into all projects linked with them.
Senior planner (scheduler) can select project menu option Distribute subprojects and all responsible users will get the models of their subprojects as separate files. They can work with them as they want (add or delete activities, play what if, enter actual data, send subprojects to their subordinates for editing, etc.) until the predefined moment when senior planner will select Consolidate subprojects. To that moment every responsible user must update his/her model to predefined date/time. Consolidation means that all changes that were made in all subprojects will be incorporated in the project model.
Those who are responsible not for subproject management but for updates of resource and material costs, different kinds of norms, etc. can use free Spider Project Viewer and make changes in corresponding reference-books at any moment but project will be updated with reference-books information together with subproject consolidation before scheduling and creating its next version.
After project consolidation and scheduling this process is repeated.
There is an option to send not project phases but whole project to responsible persons but in any case only changes made in corresponding responsibility areas will be consolidated.
This is very brief description, I can explain Spider Project group work processes in more details if necessary.