This quantity will keep you busy with administrative tasks, time youll need for your main work: Planning&Scheduling.
Quite a different idea: Youll grant access to your database for your main partners - e.g. via Citrix? By security profiles you can reduce them to see/edit just what they need. I know a German administration (your branch), who does it. We do this as well.
This is exactly the type of info I am looking for. We are using one database for each of the program management clients. These are not detailed schedules but more of a program level. At the EPS level, we have major programs (Utility, road, parks) then the type of projects (signal, intersections, widening) followed by the actual projects. For each of these projects, we need to send certain information, such as permits, to the client so that they can incorporate into their system (P5).
Right now, because each project is a single xls file, it must be done 120 times. Very time consuming.
As I set up the new client, I am trying to avoid that, but there is a very similar format. A large program with a dozen type of projects and five to twenty projects for each of those types. We will need to provide another agency with a file that they can upload to their system that has a couple of activities from each of the projects.
There is no golden bridge to decide on how many projects youll create for a programme. But there are some characteristics which may lead you:
- Co-operation: Are there subcontractors who will do their own detail-planning and reporting of progress as a part of the master schedule? --> Dedicated project, because just complete projects to be exported (different for xls-format due to filters)
- Access rights: Are there parts of the master schedule persons who are allowed to read and/or write other parts shouldnt see? --> Must be different project.
- Different access right within the master schedule? Easier to control with different projects.
- Slow network: may lead to more projects due to smaller portions of data.
- ...
There are some more characteristics.
120 projects for one master schedule might be a little exaggerated.
If you have a special question for this answer, dont hesitate to ask.
Spider Project is most functional and powerful professional project management software.
The first SP version was launched in 1993 and since then it has been constantly improved. Today is used in 34 countries though most Spider Project customers are in Russia. Spider Project offers numerous unique functional features and is the only PM software that optimizes resource, cost, and material constrained schedules and budgets for projects and portfolios.
The unique features of Spider Project include Quantity Based Scheduling, Conditional Scheduling, Skill Scheduling, Optimal Resource, Cost and Material Leveling, Resource Critical Path Calculation, Cash and Material Flows Calculation and Management, Trend Analysis, Advanced Risk Simulation and Analysis, Calculation of Success Probability Trends, Calculation and Management of required Project Time and Cost Buffers, Application of Corporate Norms, Management of many Parallel Budgets, Multiple WBS and many others.
Spider Project was and is used for management of many large scale programs in Russia, including $51bln construction program for 2014 Winter Olympic Games preparation.
The application areas where Spider Project is successfully used include Aerospace, Banking, Construction, Defense, Energy, Engineering, Infrastructure, Manufacturing, Metallurgy, Mining, Oil & Gas, Railways, Retail, Shipbuilding, Software Development, Telecommunications, Utilities, etc.
P6-Auditor - Display information from Primavera P6 audit tables in a user-friendly format
Unifier-Archiver - Extract and archive important documents and attachments from Primavera Unifier
Unifier-Loader - Load data into and out of Unifier via Excel
PCM-Loader - Import data into Primavera Contract Management with flexible and secure, template-driven Excel spreadsheets
PCM-Archiver - Extract and archive important documents and attachments from Primavera Contract Management
PCM-Unifier Migrator - Automatically transfer live and historical data from Primavera Contract Management to Primavera Unifier with ease
Create Radically Better Construction Schedules with ALICE Technologies
Use the power of AI to create construction schedules that reduce risk while cutting costs and build time. With ALICE, develop the ideal schedule during preconstruction -- or recover projects that are off schedule and over budget.
Donna
How many partners do you have for co-operation?
This quantity will keep you busy with administrative tasks, time youll need for your main work: Planning&Scheduling.
Quite a different idea: Youll grant access to your database for your main partners - e.g. via Citrix? By security profiles you can reduce them to see/edit just what they need. I know a German administration (your branch), who does it. We do this as well.
Regards
Dieter
Dieter, thanks for your prompt response.
This is exactly the type of info I am looking for. We are using one database for each of the program management clients. These are not detailed schedules but more of a program level. At the EPS level, we have major programs (Utility, road, parks) then the type of projects (signal, intersections, widening) followed by the actual projects. For each of these projects, we need to send certain information, such as permits, to the client so that they can incorporate into their system (P5).
Right now, because each project is a single xls file, it must be done 120 times. Very time consuming.
As I set up the new client, I am trying to avoid that, but there is a very similar format. A large program with a dozen type of projects and five to twenty projects for each of those types. We will need to provide another agency with a file that they can upload to their system that has a couple of activities from each of the projects.
Your thoughts are greatly appreciated.
Donna
Donna
Welcome to PP!
There is no golden bridge to decide on how many projects youll create for a programme. But there are some characteristics which may lead you:
- Co-operation: Are there subcontractors who will do their own detail-planning and reporting of progress as a part of the master schedule? --> Dedicated project, because just complete projects to be exported (different for xls-format due to filters)
- Access rights: Are there parts of the master schedule persons who are allowed to read and/or write other parts shouldnt see? --> Must be different project.
- Different access right within the master schedule? Easier to control with different projects.
- Slow network: may lead to more projects due to smaller portions of data.
- ...
There are some more characteristics.
120 projects for one master schedule might be a little exaggerated.
If you have a special question for this answer, dont hesitate to ask.
Regards
Dieter