Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(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.

Nebulous Specification interpretation arguments

2 replies [Last post]
John Reeves
User offline. Last seen 21 weeks 6 days ago. Offline
Joined: 10 May 2013
Posts: 343
Groups: None

"The Contractor mus provide a preliminary schedule reflecting the Contractor's planned activities during the first 45 calendar days after NTP0.  This preliminary schedule must be submitted within five (5) calendar days after NTP0."  - this is broad, the contractor turned in a copy and paste of just the dates, no float.  They said it is "a schedule", which it is but that does not mean that it is good.  What are some arguements to make with a vague, nebulous spec?  The float issue can be complicated, but also delays commonly occur early - part of the intent of the spec is to know if a delay effects the critical path early in the project etc...I can argue intent but that is also a grey area...does the word schedule in the AEC world have to have a float column?  a 5 week schedule does not.

Replies

Zoltan Palffy
User offline. Last seen 25 weeks 1 day ago. Offline
Joined: 13 Jul 2009
Posts: 3089
Groups: None

Why does it not have dates it should have dates the float may not be correct but the early dates should be good.

some of the reasons a preliminary schedule is to be submitted are the following

1. If it is a cost laoded schedule it becomes a vehicle by which you can get paid

2. Makes sure the initial work is properly planned such as submittals/approvals, which leads to procurement which leads to installation. This is especailly critical for long leadtime items. 

Rodel already mentioned the others

Rodel Marasigan
User offline. Last seen 15 weeks 5 days ago. Offline
Joined: 25 Oct 2006
Posts: 1699

This is a normal clause in the contract. The preliminary schedule usually a very high level (3 months plan or 45 days or 6 weeks whichever is mentioned in the contract) schedule to give the client a brief indication of what the contractor plan to do for the x? amount of weeks or months (as per contract requirement 45 days or ???) while baseline is being developed. It may presented as Gantt chart or a table. It usually prepared in Excel or PowerPoint with the list of high-level items such as:

1) Expected Mobilisation on Site - date and how many
2) Plant & equipment to be mobilise on Site - type, date and how many
3) Engineering deliverables - if part of the contract
4) Long Lead Items - procurement and strategy (date and lookahed plan) if part of the contract
5) Subcontractor - if any and what work
6) etc...