Project Controls International

FPSO and Topsides

West African Costs

Basis of Estimate

(procedures)
(analyses)
(white papers)

 

         Project Knowledge = Success

                    

www.projectcontrolsinternational.com

Que$tor Estimates

(white papers)

www.projectcontrolsinternational.com    |   contact: jorge.alberch@gmail.com   |   check me out at

Home

 

Analysis

- Construction Unit Costs

- FPSO and Topside Costs

- Offshore Fabrication Costs

- Welding Consumables

 

B.Dev./ Contracts

- Contracts: Quantum Meruit

- Guide to Business Acquisition

- Proposal Development

- Relationship Building

- Video: LATTE (Starbucks)

Mind Maps

- Estimating

- Planning

- Schedule Development

- Schedule Maintenance

- Risk Management

 

Procedures

- Constructability

- Document Management

- Estimating Process

- Project Claims and COs

- Project Controls

- Project Execution Plan

- Project Execution Strategy

- Contract Synopsis

Scheduling

- Basis of Schedule

- Number of Schedule Activities

- MS Project vs. Primavera P6

- Planning and Scheduling

- Schedule Extension of  Time

- Typical Primavera P6 Settings

- Updating a P6 Schedule

- Video: Liquidated Damages

- Why Your Project will be Late

 

Courses

- Construction Estimating

- Estimating Course

- Planning and Scheduling

White Papers

- Basis of Estimate

- Communicating Effectively

- Construction Escalation

- Earned Value Management

- Estimating Productivity

- Evaluating Change Orders

- International Multipliers

- Nigerian Content Development

- Project Execution Plan

- Project Risk Contingency

- Project Variables

- Que$tor Estimates

- Risk Analysis Spreadsheet

- Risk Breakdown Structure

- Risk Management

- Spreadsheets vs Databases

- Starting the Project

- Why Project Controls

- Work Breakdown Structure

Interesting Stuff

- Programmable Robot

- Pipe Dimensions and Weights

- Concurrent Database

- LibreOffice Base vs. MS Access

- SharePoint Database

- SAP vs Oracle ERP

- Free Unit Converter

- Motivational Food for Thought

- Passionate about Meetings?

- Video: Project Controls

 

 

Contact Us

- Bio

- PMC Consultancy

Introduction

 

The answer to this question will depend on the particular purpose of the schedule. Is the schedule schematic for presentation purposes, executive summary schedule, look ahead schedule, complete detailed schedule, etc.

 

Additionally of course the number of activities to be represented on the schedule will vary with the complexity of the project.

 

For example a fabricator's schedule to the Client for the manufacture of some pipe spools could have say 50 activities only and still provide sufficient granularity for the Client to have an adequate understanding and feel for the project's activities and progress based on this schedule. On the other hand if the schedule was to be for a large multi-train dual fuel generator system created by the manufacturer for distribution to the Client for communicating the execution plan and progress, then many more activities would be required say a minimum of 200 activities to show some basic level of granularity.

 

The above examples are for schedules by the Fabricator/ Manufacturer for distribution to the Client. However internal schedules clearly road-mapping the execution plan could for both of these referenced cases could easily contain more activities (and therefore more definition) by an order of magnitude.

 

Therefore, the question of how many activities should a schedule have does *not* have any fixed answer. However as a rough rule of thumb, one could *consider as a starting point* the following:

 

Schedules to senior management

- For presentation purposes: 25 to 50 activities.

- For high level discussions: 100 to 300 activities.

 

Schedules to Client

- Simple fabrication projects: 50 to 150 activities.

- More complex manufacturing projects: 200 to 400 activities.

- EPC projects: 250 to 500 activities.

 

Internal Company Schedules

- Simple fabrication projects: 200 to 500 activities.

- More complex manufacturing projects: 400 to 2,000 activities.

- EPC projects: 1,000 to 5,000 activities.

 

 

Conclusion and Notes

 

Ultimately, when considering the amount of detail to be provided in the schedule (number of activities) one must think of the primary function of the schedule: that is to communicate both the execution plan and its timeframe. Therefore the number of activities in the schedule shall be according to the necessary amount of detail needed to convey the pertinent information to the intended audience.

 

Also it's very important for any schedule containing more than a 100 activities to have a summary milestone section in the schedule. This will help any incumbent party to quickly read and understand the important dates in the schedule. Without this the reader is left to repeatedly flip back and forth through the pages in an attempt to form a picture of the critical dates. Schedule readability is of extreme importance, since lack of readership by the incumbent parties effectively renders the schedule mute.

How Many Activities Should a Schedule Have?

Meetings

Love them or hate them. How to conduct successful productive meetings.

Funny, but true. Video on the functions of Project Controls.

Enjoy!

Settings do matter: pick the wrong settings and your schedule’s output will be meaningless.

What the text books didn’t tell you
Primavera P6 Settings
Video - Project Controls

Selected Articles

Tips on Scheduling

50% Science, 50% Art, 100% Communication

Why Project Controls?

Email: Friend/colleague?subject=Interesting link - How Many Activities Should a Schedule Have%3F&body=Interesting link from Project Controls International:        http://www.projectcontrolsinternational.com/how-many-activities-should-a-schedule-have.html