Attachment_14_-_Questions_and_Responses_Cont_0002.pdf
PDF 184 KB Posted
- Attached to
- MOD/MODE/US Bypass Canal Repairs
- Solicitation number
- 140R3026R0001
About this file
This is a Questions and Answers document for federal contract opportunity 140R3026R0001 MOD/MODE/US Bypass Canal Repairs, specifically addressing inquiries raised prior to a site visit.
The document contains a single question-and-answer entry (Question 4C) regarding Section L.13 Construction Schedule requirements. The contractor questioned whether a separate "float" column is mandatory in the proposal schedule, noting that MS Project software displays float information through precedence relationships and lag rather than as a discrete column. The Government's response clarifies that Section L.13(1)(d) requires the proposal schedule to include columns for activity name, plan duration, start, finish, float, and calendar ID to ensure visibility of schedule logic and flexibility. However, the Government will accept alternative presentations if float information is clearly identifiable through other means, such as through relationships and lag notation. The Government explicitly stated that a separate float column is not mandatory if the data is presented in another clear and accessible manner or if float can be removed entirely.
View the file
Other files
Show all 20
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
140R3026R0001 MOD/MODE/US Bypass Canal Repairs Questions Prior to Site Visit
Question # Question Response 4C Section L.13 Construction Schedule (1)(d): Per subparagraph (i) the proposal schedule shall have columns that display the following information in the following order: activity name, plan duration, start, finish, float, and calendar ID. Float is not easily created as a column if utilizing MS Project, but is shown within the precedence relationships (finish-to-start, start-to-start, etc) where “lag” is applied.
Will the Government confirm that a separate column for “float” is not a requirement for the proposal?
Section L.13(1)(d) specifies that the proposal schedule should include columns for activity name, plan duration, start, finish, float, and calendar ID. The intent is to ensure visibility of schedule logic and flexibility.
If your scheduling tool (e.g., MS Project) does not easily generate a separate “float” column but displays float through relationships and lag, the Government will accept that approach as long as float information is clearly identifiable. A separate column for float is not mandatory if the data is presented in another clear and accessible manner or float can be removed.
File details come from the government source that posted it. Updated .