Cape H Preproposal Conf Slides.pptx
PPTX presentation 105 KB Posted
- Attached to
- Ship Management Services for Three RRF Vessels
- Solicitation number
- DTMA98R20120001
About this file
PowerPoint Slide Presentation given at Pre-proposal Conference Feb 22 2012
View the file
Other files
Show all 31
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
Maritime Administration (MARAD) Cape H Ship Manager RFP Pre-Proposal Conference
February 22, 2012
Agenda Welcome & opening remarks – Mr. Bill Cahill Summary of Requirement – Mr. Jim Fox Proposal Submissions & timelines – Melinda Simmons-Healy Open discussion Q&A – panel (Ops, Acq) Closing
Overview 2011 FSS/MDA contract was used as a baseline References to MAR Codes were minimized by substituting Office Name nomenclature Many references to RMS were changed to NS5 to be more specific Current term for COTR – now COR – was introduced as COR/COTR
Overview, cont.
Many language revisions have been made to clarify and enhance the readability Effort has been made to minimize duplicative or redundant language Specific requirements have been relocated appropriately to reduce fragmentation
Summary of Revisions
| C.1 | Introduction | Minor tailoring implemented for the current requirement. |
| C.2.1 | Maintenance Management – Logistics | Hierarchy of Alternative Compliance Program was changed to be under Classification Surveys along with Machinery Surveys, PM/CM and Hull Surveys |
| C.2.2 | Readiness | Minor tailoring |
| C.2.3 | PMP | Simplified narrative |
| C.2.4 | Corrective Maintenance & Repairs | Rearranged process steps in a more logical progression; introduced emphasis on ESL vs. M&R work items. |
| C.2.5 & C.2.6 | Management Transition of RRF Vessels | New section to better clarify roles and responsibilities of Ship Manager during both Phase-in and Phase-out at beginning and end of contracts replacing former Section 2.7 Turnover of RRF Vessels; former Sections 2.5 Business Plan Development & 2.6 Business Plan Execution were merged into Sections C.6.4 Business Plan Development and C.6.5. Business Plan Execution and Update |
| C.2.6 | Logistics | Formerly Section 2.8; language pertaining specifically to turnover was moved to new Section 2.5 Management Transition of RRF Vessels; requirements for maintenance of spare parts were substantially simplified. |
Summary of Revisions, cont.
| C.3.2 | Activation | Five specific categories of activations; introduced “proof of readiness sea trial” terminology; rearranged process steps to clarify logic path; added definitive language addressing Turbo Activations and Other Activations; added bullet lists to clarify reporting requirements |
| C.3.3 | Operations | Minor tailoring; clarified activations leading to MSC OPCON; clarified that commercial bunkers require specific COR/COTR authorization; |
| C.3.4 | Deactivation | Re-written for improved process description, more defined cost estimating expectations, and improved reporting. |
| C.4.1 | Safety | Minor edits |
| C.4.2 | Environmental | Minor edits; removed HQ individual names and emphasis on adherence to instructions in SOPEP |
| C.4.3 | Security | Minor edits |
| C.5.1 | Staffing | Minor edits |
| C.5.3 | Shipboard Crewing | Minor edits and rearranging; added new Section 5.2 Shoreside Staffing separate from Shipboard Crewing |
| C.5.4 | Labor Disruption | No edits; formerly C.5.3 |
| C.5.5 | Mariner Vetting | Minor edits and rearranging |
| C.5.6 | Medical | Formerly C.5.5; deleted C.5.5.4 Medical Screening/Consultative Service since it is covered in J.3; deleted C.5.5.10 CBR-D medicinal pertaining to controlled substances. |
| C.5.7 | Training | Formerly C.5.6; former C.5.6.2 Military Training moved to new Section C.9 SUPPORT NON-CORE RRF FUNCTIONS |
| C.5.8 | ROS | Formerly C.5.7; minor edits only |
| C.5.9 | General ROS Duties and Responsibilities | Formerly C.5.8; minor edits only; former C.5.9 Voluntary Program Support moved to new Section C.9 SUPPORT NON-CORE RRF FUNCTIONS |
| C.5.10 | FOS Crew | Merged C.5.10.4.5 ROS Telephone Service and C.6.8 Phone Lines on ROS Vessels into new C.5.9.13 ROS Telephone Service to reduce duplication; removed former C.5.10.5.2 Code of Conduct for Central Command Area of Responsibility. |
| C.5.11 | Requirement Unique to Designated Shipboard Positions | Minor edits only |
| C.5.12 | Force Protection/Security Teams | No edits |
| C.5.13 | Security Clearances for ROS Crew | Moved to Section 5.9 General ROS Duties and Responsibilities |
| C.6.4 | Business Plan Development | Consolidated related requirements here from C.3.2; re-wrote BP development language to better define both process milestones and objectives |
| C.6.5 | Business Plan Execution and Update | Re-wrote BP execution and update language to better define both process milestones and objectives |
| C.6.6 | IT Requirements | Consolidated requirements from former Sections 6.6.5 and 6.6.6 pertaining to software systems into one section; updated computer requirements definition. |
| C.6.7 | Subcontractor Management | No edits |
| C.7 | Financial Management | No edits |
| C.8 | Government Furnished Items | No edits |
| C.9 | Support Non-Core RRF Functions | New Section; clarifies previous requirements |
| C.9.1 | Support of 3rd Party Training on MARAD Vessels | Brought in from C.5.6.2 Military Training |
| C.9.2 | Voluntary Program Support | Brought from C.5.9 Voluntary Program Support |
The Ship Manager (SMC)/Ready Reserve Force (RRF) Program
Schedule
| Final RFP Posted | 15 Feb 2012 | |||
| Preproposal Conference | 22 Feb 2012 | |||
| Proposals Due | 15 Mar 2012 | |||
| Competitive Range Determination (if necessary) | 27 Apr 2012 | |||
| Discussions/Negotiations (if necessary) | 04 May 2012 | |||
| Contract Award | 12 Jun 2012 | |||
| Notice to Proceed | 02 Jul 2012 |
Source Selection All evaluations will be conducted by the following teams:
E-Review Team Ascertains completeness of the submission & adherence to electronic proposal submission instructions Mandatory Requirements Team Determines whether the submissions satisfy the mandatory requirements in the areas of U.S. Citizenship, Operating Qualifications, and Minimum Working Capital Technical & Management Evaluation Team (TET) Evaluates the technical/management submission against the factors outlined in Section L of the RFP
Source Selection (continued) All evaluations will be conducted by the following teams:
Past Performance Evaluation Team (PPET) Evaluates the offeror’s recent and relevant past performance and corporate experience Ascertains the degree of performance risk associated with each offeror Price Evaluation Team (PET) Evaluates the prices proposed for Section B, inclusive of all priced items
Source Selection (continued) Competitive Range Determination (if necessary) Only those offerors who meet the mandatory requirements will be considered for inclusion in the competitive range The Procuring Contracting Officer (PCO) makes the competitive range determination consisting a) of those proposals most likely to be considered for award and b) considering the results of the technical/management, past performance and price evaluations The PCO may further reduce the number of offers in the competitive range per FAR Part 15.305(a)(2)(iv) to ensure the efficiency of the source selection process
Source Selection (continued) Basis for Award MARAD will award a contract To an offeror meeting the Special Standards/Mandatory Requirements Proposing ship management approaches responsive to the solicitation Offering the Best Value to the Government for management of Ship Group 28 (by amendment, adding Ship Group 29)
Source Selection (continued) Best Value Award will be made on a “best value” basis considering Technical/management Relevant Corporate Experience Past Performance Price 12-Vessel Limitation (inclusive of awards under 2005 & 2011 Ship Manager Contracts)
Source Selection (continued) Best Value – Trade-offs MARAD reserves the right to award to a lower ranked offeror where the prices of the higher ranked offeror are so high as to no longer constitute best value to the agency Conversely, MARAD reserves the right to award to the higher ranked offeror at a higher price to acquire technical superiority MARAD will use a cost/technical trade-off analysis to assess the value the Government will receive against the cost of the contract.
Things to Watch The “Incumbent Trap” Proposal basically states that “I have done a good job and MARAD knows that” Evaluators can only evaluate what is being proposed, not what “they know” Submissions to Other MARAD Offices Just because you may have submitted i.e. Citizenship documentation to other offices within MARAD, doesn’t mean you don’t have to submit it for this solicitation again Non-submission makes an offeror non-responsive
Questions?
image1.png image2.wmf
File details come from the government source that posted it. Updated .