FTA Oversight Procedures - Federal Transit Administration - U.S. ...

FTA Oversight Procedures - Federal Transit Administration - U.S. ... FTA Oversight Procedures - Federal Transit Administration - U.S. ...

25.10.2013 Views

activity durations. Critical path float is to be assessed. Data tables and histograms are to be provided. V) Conclusion • Summarized discussion of findings, • Recommendations and time frames for adjustments to the Project Management Plan, • Schedule Review checklists for design and construction reviews, • Summarize overall project risk. VI) Appendix: Sponsor Project Data • This section shall identify and characterize the sponsor’s structure and quality of the sponsor’s project data for this report. Examine the extent, nature, detail and quality of the sponsor’s project data and the steps the Contractor took to validate the information. The Contractor shall identify and discuss that Grantee or third party data it accepted without adjustment, • Detailed listing of identified risks, • Other Appendices as necessary or directed. 8.0 APPENDICES 8.1 Sample Section with Data Table 8.1.1 Technical Review Example This section reviews the preparation and presentation of the project schedule for its technical correctness and the completeness of its preparation as a critical path method based scheduling tool that can be successfully used to model and monitor the project. The schedule was generated and submitted in [software format] (example— Project Management, Release 5.0). [Software] is customarily used and accepted for project scheduling in the construction industry. A hard copy of the schedule and a written narrative titled “Basis of Schedule Development” were also submitted. There are two predominant calendars in use. The majority of the physical construction activities are based on a five day work week with non‐work days for holidays and weather delays. The design and other activities are on a calendar that is based on a five day work week with non‐ work days for holidays. Additional calendars are used in the schedule for other specific types of activities. Following is a listing of all the calendars, and the activity usage of each: Calendar Name Number of Activities Assigned Const. 5 Day w/Union Holiday & 30 2649 activities weather days Engineering/Procurement/Permit Calendar 1555 activities Number of Activities on Critical Path/ Total Duration Number of non-critical activities with less than 30 days float/avg. float OP 34 Project Schedule Review Revision 0, June 2008 Page 6 of 7

DTP/DTE Business Days 446 activities Standard 5 Day Work week 100 activities Winter Outage Calendar w/30 weather 21 activities days 5-Day Week, 2-shift 10 tunneling activities 7-day workweek 9 activities Test/Commission …Yard Modification Pre-Revenue Operation Start Revenue Operations 54 hour Outage calendar 5 activities Weekend Outage Calendar w/30 4 activities weather days NATM Tunneling w/Union Holiday & 2 activities 30 weather days TOTAL 4801 activities 8.2 Typical Construction Sequencing A typical transit project schedule should demonstrate the following broad sequencing; note that a full schedule will contain significantly more detail, and the chronological phases noted below may overlap in time: • acquire right-of-way • relocate utilities • construct roadway improvements • under-drains • duct banks and catenary pole foundations • construct station platforms and finishes • install trackwork • install systems components • communications, signals • traction electrification • fare collection. OP 34 Project Schedule Review Revision 0, June 2008 Page 7 of 7

activity durations. Critical path float is to be assessed. Data tables and histograms<br />

are to be provided.<br />

V) Conclusion<br />

• Summarized discussion of findings,<br />

• Recommendations and time frames for adjustments to the Project Management<br />

Plan,<br />

• Schedule Review checklists for design and construction reviews,<br />

• Summarize overall project risk.<br />

VI) Appendix: Sponsor Project Data<br />

• This section shall identify and characterize the sponsor’s structure and quality of the<br />

sponsor’s project data for this report. Examine the extent, nature, detail and quality<br />

of the sponsor’s project data and the steps the Contractor took to validate the<br />

information. The Contractor shall identify and discuss that Grantee or third party<br />

data it accepted without adjustment,<br />

• Detailed listing of identified risks,<br />

• Other Appendices as necessary or directed.<br />

8.0 APPENDICES<br />

8.1 Sample Section with Data Table<br />

8.1.1 Technical Review Example<br />

This section reviews the preparation and presentation of the project schedule for its technical<br />

correctness and the completeness of its preparation as a critical path method based scheduling<br />

tool that can be successfully used to model and monitor the project.<br />

The schedule was generated and submitted in [software format] (example— Project<br />

Management, Release 5.0). [Software] is customarily used and accepted for project scheduling in<br />

the construction industry. A hard copy of the schedule and a written narrative titled “Basis of<br />

Schedule Development” were also submitted.<br />

There are two predominant calendars in use. The majority of the physical construction activities<br />

are based on a five day work week with non‐work days for holidays and weather delays. The<br />

design and other activities are on a calendar that is based on a five day work week with non‐<br />

work days for holidays. Additional calendars are used in the schedule for other specific types of<br />

activities. Following is a listing of all the calendars, and the activity usage of each:<br />

Calendar Name Number of<br />

Activities<br />

Assigned<br />

Const. 5 Day w/Union Holiday & 30 2649 activities<br />

weather days<br />

Engineering/Procurement/Permit<br />

Calendar<br />

1555 activities<br />

Number of Activities<br />

on Critical Path/<br />

Total Duration<br />

Number of non-critical<br />

activities with less than<br />

30 days float/avg. float<br />

OP 34 Project Schedule Review<br />

Revision 0, June 2008<br />

Page 6 of 7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!