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

APPENDIX E Sample Report Cover Page _________________________________________________________________________________ PMOC Contract Number DTFT__-__-_-_____ Task Order Number ___ Project Number DC-__-____ Work Order Number ___ OPs Referenced ___ CAPITAL COST ESTIMATE REVIEW Great City Light Rail Subway Project Great City Transportation Authority Region or City, State May 1, 2008 May 22, 2008, Rev. 1 PMOC firm name, address PMOC lead person’s name, affiliation if different from PMOC firm, phone, email Length of time PMOC firm and person have been assigned to this project _________________________________________________________________________________ OP 01 Administrative Conditions and Requirements Revision 0, June 2008 Page E-1

U.S. DOT Federal Transit Administration TPM-20 Office of Engineering Project Management Oversight Oversight Procedure 02 – PMOC Implementation, Transition Plans, and Project Status Reporting ______________________________________________________________________________ 1.0 PURPOSE The purpose of this Oversight Procedure is to describe the review, analysis and recommendation procedures and reporting requirements expected by Federal Transit Administration (FTA) from the Project Management Oversight Contractor (PMOC) with regard to two types of administrative tasks: Implementation / Transition Plans and Project Status Reporting. 2.0 BACKGROUND 2.1 Implementation and Transition Plans 2.1.1 Implementation Plans The PMOC is required to develop and submit for review, comment and approval an Implementation Plan at the contract, task order, and work order levels. These Contract, Task Order, or work order level Implementation Plans play a key part in demonstrating to FTA that the PMOC has achieved and maintains a readiness to perform services and produce deliverables and outcomes in a satisfactory manner that meet FTA’s requirements. Implementation Plans define how the PMOCs’ services, products, deliverables, etc. will be accomplished in a manner and quality that meets FTA’s requirements. Unless otherwise directed by the COTR, PMOC services, products and outcomes will be performed in conformance with the then current version of the FTA approved Implementation Plan. The Contract Level Implementation Plan defines how multiple task orders or a combination of Regional and Headquarters task orders will be accomplished. The Task Order Level Implementation Plan defines how task order level services, products, deliverables will be accomplished. Minimize duplication between the Task Order and Contract implementation plans. Identify and explain inconsistencies. The Work Order Level Implementation Plans may be required if the work is to be performed over many months, the work is particularly complex, or if FTA has concerns regarding the PMOC’s technical approach, staffing, schedule, etc. 2.1.2 Transition Plans Transition Plans are required for Task Orders when changes in PMOC assignment necessitate. For Work Orders, Transition Plans may be required if the work is particularly complex or for other reasons indicated by FTA. FTA may require new PMOCs to replace or supplement the staff of current PMOCs when the current/resident/outgoing PMOC develops a conflict of interest with the subject project or FTA determines that it is in FTA’s interests to assign a replacement or supplemental PMOC. OP 2 PMOC Implementation, Transition Plans, and Project Status Reporting Revision 0, June 2008 Page 1 of 9

U.S. DOT <strong>Federal</strong> <strong>Transit</strong> <strong>Administration</strong><br />

TPM-20 Office of Engineering<br />

Project Management <strong>Oversight</strong><br />

<strong>Oversight</strong> Procedure 02 – PMOC Implementation, <strong>Transit</strong>ion Plans, and Project<br />

Status Reporting<br />

______________________________________________________________________________<br />

1.0 PURPOSE<br />

The purpose of this <strong>Oversight</strong> Procedure is to describe the review, analysis and recommendation<br />

procedures and reporting requirements expected by <strong>Federal</strong> <strong>Transit</strong> <strong>Administration</strong> (<strong>FTA</strong>) from the<br />

Project Management <strong>Oversight</strong> Contractor (PMOC) with regard to two types of administrative tasks:<br />

Implementation / <strong>Transit</strong>ion Plans and Project Status Reporting.<br />

2.0 BACKGROUND<br />

2.1 Implementation and <strong>Transit</strong>ion Plans<br />

2.1.1 Implementation Plans<br />

The PMOC is required to develop and submit for review, comment and approval an Implementation<br />

Plan at the contract, task order, and work order levels. These Contract, Task Order, or work order<br />

level Implementation Plans play a key part in demonstrating to <strong>FTA</strong> that the PMOC has achieved and<br />

maintains a readiness to perform services and produce deliverables and outcomes in a satisfactory<br />

manner that meet <strong>FTA</strong>’s requirements.<br />

Implementation Plans define how the PMOCs’ services, products, deliverables, etc. will be<br />

accomplished in a manner and quality that meets <strong>FTA</strong>’s requirements. Unless otherwise directed by<br />

the COTR, PMOC services, products and outcomes will be performed in conformance with the then<br />

current version of the <strong>FTA</strong> approved Implementation Plan.<br />

The Contract Level Implementation Plan defines how multiple task orders or a combination of<br />

Regional and Headquarters task orders will be accomplished. The Task Order Level Implementation<br />

Plan defines how task order level services, products, deliverables will be accomplished. Minimize<br />

duplication between the Task Order and Contract implementation plans. Identify and explain<br />

inconsistencies. The Work Order Level Implementation Plans may be required if the work is to be<br />

performed over many months, the work is particularly complex, or if <strong>FTA</strong> has concerns regarding the<br />

PMOC’s technical approach, staffing, schedule, etc.<br />

2.1.2 <strong>Transit</strong>ion Plans<br />

<strong>Transit</strong>ion Plans are required for Task Orders when changes in PMOC assignment necessitate. For<br />

Work Orders, <strong>Transit</strong>ion Plans may be required if the work is particularly complex or for other reasons<br />

indicated by <strong>FTA</strong>. <strong>FTA</strong> may require new PMOCs to replace or supplement the staff of current PMOCs<br />

when the current/resident/outgoing PMOC develops a conflict of interest with the subject project or<br />

<strong>FTA</strong> determines that it is in <strong>FTA</strong>’s interests to assign a replacement or supplemental PMOC.<br />

OP 2 PMOC Implementation, <strong>Transit</strong>ion Plans, and Project Status Reporting<br />

Revision 0, June 2008<br />

Page 1 of 9

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

Saved successfully!

Ooh no, something went wrong!