The two criteria we use for creating Projects within a Project Group are security access and speed.
1. Security Access – P3 allows you to set different access rights on each Project as well as at the Project Group level. This allows different people to maintain their project or part of the project without being able to alter activities that do not belong to them. If the project is being updated remotely (perhaps by a sub-contractor) you can backup the Project and only send that portion of the Project Group for them to update. It is a simple backup and restore process of the Project to move the updated data back and forth.
2. Speed – If you break a large project (the Project Group) into self contained sections (Projects) then the number of activities you need to process every time you filter, reorganize, schedule, etc is reduced to only those in the Project.
e.g. refurb of a submarine
approx 17,000 activities
broken into 125 Projects (ie each discrete system from air and water to weapons)
managed by 6 planners (updates came from an automated interface from the labor costing system (ERP) which used bar-coded job-cards and swipe readers to record times at the workface).
each planner had 20-30 Projects
each project had 100-300 activities
Working in the Projects of less 300 activities is a much better experience than working in the 17,000 activity Project Group. Remember you can have up to four Projects within the same Project Group open at a time if you need to multitask between Projects.
How you create them has been answered below. The other big advantage is that the Project Group provides an integrated view across multiple Projects when the Project Group is the view off all Projects within a Company/Department. It also enforces standards on all Projects within the Project Group as the dictionary items (calendars, activity codes, resources, etc) are common and predefined when you create a Project within the Group.
Member for
20 years 11 months
Member for20 years11 months
Submitted by Andrew Podolny on Tue, 2005-03-01 04:50
The most obvious advantage in creating project groups is ability to trace CP of each part of group independently. For example – you can create subprojects for Engineering, Procurement, Construction. So you may trace CP of each subproject as well as CP for whole group.
When I wish to extract some activities into new subproject:
1. Add new subproject into group. (Project -> Copy -> Project Group / Project Name / Project ID).
Lets assume Project ID=S1
2. Then I open newly created group in exclusive mode (or you can edit P3.ini to allow change Activity ID by users with non exclusive rights)
3. I change Activity ID for activities which are going into new subproject. All you have to do is to replace first 2 symbols in Activity ID by Project ID. For instance: AC8000 -> S1AC8000
Member for
24 years 6 monthsRE: Project Group
The two criteria we use for creating Projects within a Project Group are security access and speed.
1. Security Access – P3 allows you to set different access rights on each Project as well as at the Project Group level. This allows different people to maintain their project or part of the project without being able to alter activities that do not belong to them. If the project is being updated remotely (perhaps by a sub-contractor) you can backup the Project and only send that portion of the Project Group for them to update. It is a simple backup and restore process of the Project to move the updated data back and forth.
2. Speed – If you break a large project (the Project Group) into self contained sections (Projects) then the number of activities you need to process every time you filter, reorganize, schedule, etc is reduced to only those in the Project.
e.g. refurb of a submarine
approx 17,000 activities
broken into 125 Projects (ie each discrete system from air and water to weapons)
managed by 6 planners (updates came from an automated interface from the labor costing system (ERP) which used bar-coded job-cards and swipe readers to record times at the workface).
each planner had 20-30 Projects
each project had 100-300 activities
Working in the Projects of less 300 activities is a much better experience than working in the 17,000 activity Project Group. Remember you can have up to four Projects within the same Project Group open at a time if you need to multitask between Projects.
How you create them has been answered below. The other big advantage is that the Project Group provides an integrated view across multiple Projects when the Project Group is the view off all Projects within a Company/Department. It also enforces standards on all Projects within the Project Group as the dictionary items (calendars, activity codes, resources, etc) are common and predefined when you create a Project within the Group.
Member for
20 years 11 monthsRE: Project Group
Hi Thomas
The most obvious advantage in creating project groups is ability to trace CP of each part of group independently. For example – you can create subprojects for Engineering, Procurement, Construction. So you may trace CP of each subproject as well as CP for whole group.
When I wish to extract some activities into new subproject:
1. Add new subproject into group. (Project -> Copy -> Project Group / Project Name / Project ID).
Lets assume Project ID=S1
2. Then I open newly created group in exclusive mode (or you can edit P3.ini to allow change Activity ID by users with non exclusive rights)
3. I change Activity ID for activities which are going into new subproject. All you have to do is to replace first 2 symbols in Activity ID by Project ID. For instance: AC8000 -> S1AC8000