M67854-13-R-2410_Amendment_3.pdf

PDF 465 KB Posted

Attached to
Rugged Mobile Non-Intrusive Inspection System (RMNIIS)
Solicitation number
M67854-13-R-2410
Issued by

About this file

M67854-13-R-2410 Amendment 3 - Update Section L and M and QASP

View the file

Other files

Show all 17

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

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purposes of this amendment is to 1) update Section L Instructions to Offerors w ith the Quality Assurance Surveillance Plan (QASP); 2) update Section M - Evaluation w ith the QASP language; and 3) update Section J-1 Attachments. All other terms and conditions remain the same.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 30

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 30-Jan-2013

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X M67854-13-R-2410

X 9B. DATED (SEE ITEM 11)

11-Jan-2013

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

29-Jan-2013

CODE

MARCORSYSCOM PDM-MC3

ATTN:ANN PENNINGTON

2200 LESTER STREET

QUANTICO VA 22134

M67854 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

M67854-13-R-2410

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been modified:

SECTION L INSTRUCTIONS

IN SUMMARY- CHANGES MADE FOR AMENDMENT 2 OF REQUEST FOR PROPOSAL

M67854-13-R-2410:

Section L-1 – PRE-PROPOSAL INSTRUCTIONS deleted in full and adjusted numbering accordingly.

Section L-3 (4) Proposal Topics and Page Limitations: add Part F: Addendum to Performance Work Statement – Quality Assurance Surveillance Plan (QASP)

Section L-4 Proposal Content Volume III Technical Part A. Technical: add Quality Assurance

Surveillance Plan (QASP).

Section M- 3.1 Technical – Part A. Technical Approach: added Quality Assurance Surveillance

Plan (QASP).

Section L: Instructions, Conditions, and Notices to Offerors

Section L-1 PROPOSAL SUBMISSION

1. Introduction

a. The Government intends to award a Firm Fixed Price contract with CLINs for FSR CONUS Support, FSR OCONUS Support, ODC’s, Spares and Consumables, Manuals, CDRLs, and Training, and with a

Cost type CLIN for Travel resulting from this solicitation to the responsible Offeror whose proposal represents the best value to the Government in accordance with Section M.

2. General

a. Offerors shall be limited to one proposal for this Solicitation. The proposal shall be complete and clear in all respects without the need for additional explanation or information. The proposal shall be in sufficient detail and scope to permit the Government to evaluate it with respect to the non-price and price factors specified under Section M of this solicitation.

b. Offerors are cautioned against general, vague or unsubstantiated statements which prevent or render difficult the Government’s evaluation of the proposal. Mere statements by the Offeror that it understands a problem and/or can comply with the requirements, and statements paraphrasing the requirements or parts thereof, may be considered inadequate. Communications conducted to resolve minor or clerical errors do not constitute discussions and the contracting officer reserves the right to award a contract without the opportunity for proposal revision.

c. Data, even though previously submitted or presumed known by the Government, cannot be considered as part of the Offeror’s proposal unless submitted with and incorporated into the proposal.

d. Any inconsistency, whether real or apparent, between projected performance and price, should be explained in detail by the Offeror. The burden of demonstrating technical merit rests with the Offeror.

e. Proposals submitted for consideration for award shall address the full scope of the solicitation.

Proposals that address only part of the solicitation will be considered unacceptable.

f. A ceiling on the number of pages in the proposal has been imposed, as indicated in the sections below. All pages, or any other material, in excess of the maximum number of pages stated will not be evaluated.

g. The Government intends to evaluate proposals and award a contract without discussion in accordance with FAR 52.215-1. Therefore, each initial offer should contain the Offeror’s best terms from a price and technical standpoint.

SECTION L-2 - OFFEROR'S PROPOSAL REQUIREMENTS

1. Proposal Requirements

Proposals shall consist of the following:

a. One signed solicitation document, signed by a person authorized to enter into the proposed contract on behalf of the Offeror. All amendments issued shall be acknowledged in block 14.

b. Proposals shall be valid for a period of at least 180 days from the proposal due date.

c. Four (4) copies of Volumes II through VI and two (2) copies of Volumes I and VII. Submit the proposals in separable parts as indicated in paragraph L-3, section 4.

d. One electronic “soft” copy of the full proposal (Volumes I through VII, separable parts) using a Microsoft Office 2003 for Windows suite of applications. Price breakdown will include MS Excel spreadsheets with formulae intact. Schedules will be in MS Project or compatible format.

e. Each page shall contain the following legend at the bottom of each sheet; Source Selection

Information – See FAR 2.101 and 3.104.

f. The following notes apply to all hard copy proposal volumes submitted. Submit the proposals in separable parts following the proposal outline indicated in paragraph L-3, section 4.

NOTE 1: The definition of a page is a single side of paper with text, drawings, data, or similar content.

Pages shall be 8.5 by 11 inches in size except for foldouts. Text font shall be in Times New Roman 12 point. Font for tables, figures, and other graphics shall be no smaller than 8 point Arial. Foldouts count as two pages. Limit use of foldout pages to non-textual matter. Where a proposal requirement dictates information in Contract Data Requirements List (CDRL) format, that information will not count against maximum page limitations. Attempts to circumvent the intent of these limitations (condensed printing, oversize paper, extensive or unnecessary use of large foldouts, or other similar actions) may result in removal of such material from the proposal or its exclusion from the evaluation.

NOTE 2: Bind each proposal volume in three-ring binders. Individual sections should be removable and replaceable to the volumes. Each volume shall contain a title page, table of contents, and list of tables and figures for that volume. Include a Cross Reference Matrix, in Volume III Technical and IV Program

Management, showing the location where the evaluator should look in that volume for a discussion of a particular requirement (excluding price information). Pages only used specifically for Cross Matrix, title page, table of contents, list of tables and figures information, and glossaries of acronyms and abbreviations will not count against volume page limitations. Use tab separators to separate required sections within a volume. Tab separators do not count against page count. Number all pages sequentially. Only material allocated to a specific section shall be in that section.

2. Proposal Submission Location, Time, and Date

Proposals shall be submitted by 1400 (2:00 PM local time Quantico, VA) on 15 February 2013. No exceptions.

Offeror’s shall prominently mark all containers used for delivery of proposals with the following statement:

“REQUEST FOR PROPOSAL – SOLICITATION M67854-13-R-2410”

For FEDEX, Hand-Carry, UPS, etc:

Commander

Marine Corps Systems Command

2201A Willis Street

Quantico, VA 22134-6050

Attn: Ms. Christine Kuney

(703) 432-9916

For US Postal Service:

Commander

Marine Corps Systems Command

2200 Lester Street

Quantico, VA 22134-6050

Attn: Ms. Christine Kuney

(703) 432-9916

3. Proposal Outline

All proposals shall conform to the following outline. Confine all information pertaining to each indicated topic to the appropriate volume and section. Section 4, below indicates specific topics for inclusion in each volume.

4. Proposal Topics and Page Limitations

Proposal volumes shall not exceed the following page limits:

Volume Title Max Pages

I Model Contract N/A

II Executive Summary/ Exceptions, Deviations, Assumptions and Waivers 5

III Technical (page count distributed among subsections as follows:) 75

Part A: Technical Approach

Part B: Training

Part C: Contractor Logistics Support (CLS)

Part D: Maintenance Planning

Volume Title Max Pages

Part E: Manuals

Part F: Addendum to Performance Work Statement (PWS) – Quality Assurance Surveillance Plan (QASP)

N/A

IV Program Management (page count distribution among subsections as follows:)

Part A: Management Approach

Part B: Personnel

Part C: Data Management

Part D: Integrated Logistics Support

Part E: Meetings, Formal Reviews, Conferences, and Audits

Part F: Teaming Arrangements

V Contract Data Requirements Lists (CDRLs) N/A

VI Past Performance 26

Part A: Previous Contract Efforts/Experience

Part B: Customer Assessment/Past Performance

VII Price (page count distributed among volume subsections as follows:) 10

Part A: Fixed Price CLINs

Part B: Cost Reimbursable CLIN

Part C: Attachment 3

SECTION L-3 PROPOSAL CONTENT

The Government will evaluate proposals using the evaluation criteria contained in Section M of this solicitation. Offerors are responsible for generating their best proposal efforts. Ensure each section of the proposal adequately contains all the information necessary for evaluation. Proposal volumes should, at a minimum, address the following information:

VOLUME I. MODEL CONTRACT

1. Solicitation/Model Contract and Representations and Certifications. The purpose of this volume is to provide information to the Government for preparing the contract document and supporting files. The

Offeror’s proposal shall include a signed copy of the offer and Sections A through K. This includes:

a. Section A- Completed and signed with all Amendments acknowledged

b. Section B - Supplies or Services and Costs/Prices. Completed pricing information in Section B of the solicitation. Insert the price for each line item (base CLINs and option CLINs).

c. Section G - Contract Administrative Data. Complete the "fill-in" required in Contractor’s

Contract Administration, in Section G. If not applicable, state so.

d. Section K- Filled-in and Completed Provisions

e. Representation and Certifications- Any applicable certifications submitted as “will submit with individual offers/proposals” within Online Representations and Certifications.

f. Statement of the period for which the proposal is valid (not less than 180 calendar days).

g. Evidence of required facility and/or personnel clearances.

h. Authorized Offeror Personnel. Provide the name, title and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the

Government. Finally, please provide the name, title, and telephone number of the CEO, Division

President, or Vice President of the Offeror.

j. Completed copy of Attachment (2) DD254.

2. Offerors are cautioned that any non-compliance with the terms and conditions of the RFP may cause their proposal to be determined unacceptable. The Government intends to make an award without discussions. Discussions, if necessary, will be conducted in accordance with FAR 15.306. The

Contracting Officer has determined that Certified Cost or Pricing Data is not required for this solicitation.

The Government reserves the right to request other than certified cost or pricing data for the remainder of the proposal should it be required to assess an Offeror’s price reasonableness.

VOLUME II. EXECUTIVE SUMMARY/ CONDITIONS, EXCEPTIONS, DEVIATIONS,

ASSUMPTIONS, AND WAIVERS

1. Offerors shall provide a top-level summary of the entire proposal in an Executive Summary.

2. General. This volume must include a certification that it contains all exceptions, deviations, and waivers that the Offeror takes from the provisions of the RFP and its applicable documents. A condition is when the contractors obligation to perform as described in the requirement is dependent upon another set of circumstances. An exception is where an Offeror states it will not comply with a requirement, usually involving contract terms and conditions. A deviation is where an Offeror states it will not comply with a requirement but proposes an alternative to meet the intent of the requirement, usually involving a specification. A waiver is where an Offeror requests authorization for the Government to accept an item that will depart from specified requirements, but would nevertheless be considered suitable. An assumption is any presupposition made by the Offeror about the Government’s requirements that is not explicitly stated within the requirement that has an effect on the proposal.

3. Description. Provide a detailed description of each exception, deviation or request for waiver.

Indicate the Offeror’s difficulty with the applicable requirement and the Offeror’s proposed solution.

Specifically identify the portion of the RFP and the Offeror’s proposal that are affected. Proposing conditions, exceptions, deviations, assumptions or waivers may render the offerors proposal unacceptable.

VOLUMES III THROUGH V. CONTRACTOR PERFORMANCE WORK STATEMENT

(CPWS)

1. The Statement of Objectives (SOO), which is located in Section C of the DRAFT solicitation, provides the Government’s overall objectives and performance requirements for this solicitation. The Offeror shall use the SOO together with applicable portions of this RFP, as the basis for preparing the Contractor

Performance Work Statement (CPWS) in Volumes III through V. The Offeror shall ensure all aspects of the SOO and Government requirements documents referenced in the RFP package are addressed in the proposed CPWS. The CPWS should specify in clear, understandable terms the work to be done in developing or producing the goods to be delivered or services to be performed by the Offeror. Preparation of an effective CPWS requires both the understanding of the goods and services that are needed to satisfy a particular requirement and an ability to define what is required in specific, quantitative terms.

2. The Offeror should respond in sufficient technical detail to demonstrate a clear understanding of the processes and procedures required to perform the work required by the SOO. The CPWS must be specific and complete. Readability, clarity and coherence are very important. Your CPWS proposed must describe the capability of your organization to perform this contract including pertinent aspects of the proposed approach. Offerors shall assume that the Government has no prior knowledge of their facilities and experience, as the evaluation will be based on the information presented in the Offeror’s

CPWS proposed. Proposals should provide, as specifically as possible, the actual methodology/approaches that will be used for accomplishing and satisfying these objectives.

3. By your proposal submission, you are representing that your company will perform all the objectives and requirements specified in the solicitation. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. It is your responsibility to ensure the completeness of your proposal. The Government evaluation team has been instructed to evaluate on the basis of the information provided in the proposal. The Government shall not assume that an Offeror possesses any capability unless identified in the proposal.

VOLUME III. TECHNICAL

The Technical volume shall include a Requirements Cross-Reference Matrix (Matrix shall not count against the page count limitation) showing the proposal paragraph number where an evaluator will find the detailed discussion of a particular requirement.

Part A. Technical Approach.

This section shall demonstrate in detail the Offerors capabilities to fulfill the requirements addressed in the SOO.

Contractor Performance Work Statement (CPWS). Submit a complete CPWS that describes the proposed approach to meeting the objectives stated in the SOO. The CPWS should be detailed enough to evaluate the Offeror’s understanding of the work to be performed based on the stated objectives.

Quality Assurance Surveillance Plan (QASP). Submit a completed Quality Assurance Surveillance Plan in the format provided, see RFP Attachment 4 – Quality Assurance Surveillance Plan. The QASP will not be counted against proposal page count limitations for Volume III.

Part B. Training.

Offerors shall propose OCONUS and CONUS operator training courses and maintainer training courses.

Training must include radiation, safety, warning, and cautions training associated with this system. All

OCONUS training shall be provided by the deployed FSRs.

Part C. Contractor Logistics Support (CLS).

Offerors shall propose logistics support services for system unique items necessary to maintain the operational readiness of the RMNIIS. Offerors’ CLS shall address and describe the technical approach and identify any and all capabilities and limitations to obtain and accomplish the key elements below:

Maintenance

Supply chain management

Parts Procurement/Sustainment

Component Exchange

Calibration (if required)

Technical Assistance

Failure Reporting Analysis and Corrective Action (FRACAS) and Failure Matrix’s (MTBF, MTTR, MTBR, TTR, etc)

Operator and Maintainer Training (to include radiation safety)

Part D. Maintenance Planning.

1. Offerors shall propose maintenance planning to define optimal maintenance activities in accordance with their PWS. All Levels of Maintenance (LOM) whether Operator/Crew, Field, or Sustainment will be performed by the Contractor’s FSRs. FSRs and trained USMC operators/maintainers can perform

Operator/Crew LOM. As there is no USMC Military Occupational Specialty (MOS) assigned to this project, Offerors shall propose specially trained mechanics and technicians to sustain the RMNIIS in all

LOMs.

2. Offerors shall propose all labor, services, parts, supplies, packaging, and shipment of items necessary to maintain, diagnose, and correct malfunctions or failures in regards to overall RMNIIS operation and to accomplish all maintenance required. Offerors shall propose their approach to coordinate with each FOB point of contact to assure access to the systems.

3. Offerors shall propose their approach to Operator/Crew Level Maintenance, Field Level Maintenance, and Sustainment Level Maintenance.

Part E. Manuals.

Offerors shall propose their approach to develop and maintain operator and maintenance manuals for the

RMNIIS, to include any necessary supplemental documentation in accordance with Exhibit C (MIL-DTL-

24784-4C). Manuals must be of sufficient quality to enable the USMC to operate and maintain the

RMNIIS organically. Offerors shall provide, at a minimum, the Government with Government Purpose

Rights in all manuals and other documentation delivered.

VOLUME IV. PROGRAM MANAGEMENT

The Program Management volume shall include a Requirements Cross-Reference Matrix (Matrix shall not count against the page count limitation) showing the proposal paragraph number where an evaluator will find the detailed discussion of a particular requirement.

Part A. Management Approach.

1. Offerors shall propose their approach to establish and maintain project management practices throughout the period of performance. Program Management practices shall provide visibility into the

Contractors’ organization and techniques used in managing the project.

2. Offerors shall provide a detailed transition plan that demonstrates their plan for ensuring continuity of operations without interruption of service. The transition plan shall demonstrate start-up priorities, methods for minimizing transition risks, transitioning incumbent personnel, and example of experience in transitioning in-service contracts.

Part B. Personnel.

1. Offerors shall describe the Offeror’s program organizational structure. The Offeror must clearly portray the organizational structure and show how this organization will support the RMNIIS team.

Offerors must clearly define the relationship between the program and the overall corporate structure, the reporting responsibilities, lines of authority, the role of upper and functional management, the role of subcontractor’s decision making authority, and the communication processes.

2. Offerors shall include a staffing plan showing the personnel necessary to meet the requirements of their PWS. The staffing plan shall depict staffing levels and requisite skills and characterize the availability and location of these skills, current and anticipated. The Offeror shall demonstrate the availability of Key Personnel (Program Manager and Theater Lead FSR) from contract Period of

Performance. The offer shall provide copies of any key personnel agreements for this contract. The offer shall identify the role and authority of the Program Manager and Theater Lead FSR. The Offer shall include information showing that proposed personnel are qualified and experienced. Information shall include the following:

Professional Experience (i.e. years of experience, level of responsibility, accomplishments), Education (degree and appropriateness to this work effort), Any certifications.

Part C. Data Management.

1. Offerors shall establish a process for management of all data required under this contract. Offerors, in developing information that will be furnished to the Government, shall make the maximum use of existing data and provide maximum multiple use of technical information. Any electronic databases or applications used to store, track, share, transmit or display information pertaining to this contract shall be web-based. Government use of any data management system shall not require installation of client software on Government computer systems (with the exception of Internet Explorer and Microsoft

Office). Specific data management functions shall include schedule control for deliverables, maintenance of deliverables, approval of deliverable format, distribution, and delivery of data products. The system shall include facilities for storage of all data developed or utilized for this contract, and shall provide equal access to data by the Government. Offerors shall ensure all data is centrally available for

Government review.

Part D. Integrated Logistics Support (ILS)

1. Offerors shall have a documented ILS process for the RMNIIS. The ILS process shall also assign responsibilities and establish milestones for executing the ILS program. The ILS process shall ensure the

RMNIIS satisfies all supportability criteria. The Contractor's program/process shall be available for

Government review, upon request.

2. Offerors shall propose a Joint Government/Contractor Integrated Logistics Support Management

Team/ Integrated Product Team (ILSMT/IPT). The ILSMT/IPT shall be established to monitor the status of the ILS program implementation. The ILSMT/IPT shall provide a means for coordinating logistic matters, schedules, and SOO performance, ensuring adequacy and timeliness of Government inputs and action, and assisting the Government ILS manager in discharging their responsibilities. The Government will appoint the chairperson of the ILSMT/IPT.

Part E. Meetings, Formal Reviews, Conferences, and Audits.

1. Offerors shall propose to plan, host, attend, coordinate, support, and conduct meetings, formal reviews, conferences, and audits (hereinafter called "reviews"). All reviews shall be conducted at Government and

Contractor facilities. Reviews requiring demonstration and/or examination of equipment shall be conducted at the Contractor's facility. At a minimum, Offerors shall propose:

Post Award Conference

Quarterly In Process Review (IPR)

ILSMT/IPT

(Offerors are not limited to the above list.)

ILSMT/IPT meetings shall be in conjunction with the quarterly IPRs and shall be held at times and places mutually agreed to by the Government and Contractor.

Part F. Teaming Arrangements.

1. Offers shall outline any initial teaming arrangements or selected subcontractors that will perform any element of this contract, and define how teaming was decided, and what team member qualifications led to their selection. Additionally, the Offeror shall provide rationale if significant efforts on this program will be allocated to subcontractors. “Significant” means allocation of at least 60% of any task identified in the Offeror’s Proposal or any technical element of the subcontracted work critical to the whole. Relate these selections to their beneficial contribution to the program. Describe business arrangements and show direct lines of authority. Tie team member or subcontracted effort to a task. Define each of these interdivisional transfer or subcontracted efforts as a percentage of the total program effort.

2. Offerors shall submit a Small Business Subcontracting Plan in accordance with FAR 52.219-9 (Not counted against proposal page count limitations.)

VOLUME V. CONTRACT DATA REQUIREMENTS LISTS (CDRLs)

Below is a list of deliverables the Government anticipates might be needed in the course of any eventual contract to support the Technical and Program Management Volumes and Parts in accordance with

Section E of the contract. Each Offeror should review the list and provide DD1423’s for any report they deem would be necessary during performance of their proposed solution.

System Status Maintenance

Failure Report

FSR Status Reports

GFE report

Parts on Hand

Usage inventory

Overall Project Status/Management Reports

VOLUME VI. PAST PERFORMANCE

Part A. Recent and Relevant Experience.

1. Using the format in Exhibit A, identify three recent and relevant contracts. "Relevant" is defined as efforts worth at least $500,000/year, representative of the proposed technical solution from previous developed capability to demonstrate the Offeror’s ability to meet the program management, technical, and design requirements of the SOO. "Recent" is defined as work having been performed within the past 5 years. Within the Exhibit A, Offerors shall describe the significant achievements, challenges or obstacles that were encountered during contract performance and the measures taken to overcome them.

2. The contracts identified can be with Federal, commercial or other customers and should include experience with DoD systems of a similar nature as RMNIIS. These previous contracting efforts can be for work done by the prime or work done by a proposed team member. For each contract effort, identify two (2) customer Points of Contact (POCs) which should include either the Program Manager (PM), Contracting Officer (KO), Contracting Officer’s Representative (COR), or the Task Monitor. Provide the current address, phone number, email address for each customer POC.

NOTE: The Government reserves the right to use contract performance data provided in the Offeror’s proposal and contract performance data obtained from other sources, such as the Government’s Past

Performance Information Retrieval System (PPIRS) data base.

Part B. Customer Assessment.

1. The Offeror shall provide the Past Performance Questionnaire, Exhibit B, to each of the customer

POCs for their respective (identified in Volume VI, Part A) past performance efforts. In order to expedite the assessment process, the Offeror may complete Section 3, Organization/Agency & Respondent

Identification, of the Past Performance Questionnaire for the convenience of the customer POC. The

Offeror shall not, however, complete any other section of the Past Performance Questionnaire. The questionnaire shall be provided to the customer POCs with instructions to complete one per contract and submit directly to the MCSC Contracting Office, ann.pennington@usmc.mil .

2. The Offeror shall submit with its proposal a list of the customer POCs that received a Past

Performance Questionnaire.

VOLUME VII. PRICE

1. The Price Volume shall include the price proposal that includes a firm-fixed price or Cost for each separately priced CLIN in Section B in the format provided below for each CLIN. The Government intends to perform price analysis in accordance with FAR 15.404-1(b)(2). The contractor shall provide the necessary price information as required to support the appropriate CLINs.

2. The Offeror shall, at a minimum, provide supporting data that addresses the following areas in detail sufficient to provide the Government with the basis to accomplish its evaluation. All dollar amounts provided in a completed Section B shall be rounded to the nearest dollar. Pricing shall be provided on a spreadsheet that is compatible with Microsoft Excel 2007.

mailto:ann.pennington@usmc.mil

3. For bundled costs, the phrase “Not Separately Priced” (NSP) shall be indicated for the corresponding

CLIN. The term “N/A” or Not Applicable shall only be used when the described item in the applicable

CLIN are not being provided.

4. Price inconsistencies. The Government assumes a proposal represents the Offeror’s best effort to respond to the solicitation. Any inconsistency, whether real or apparent, between promised performance and price, should be explained in the proposal. Any significant inconsistencies, if unexplained, raise a fundamental issue of the Offeror’s understanding of the nature and scope of work required and financial ability to perform the contract. This may result in the proposal being determined unacceptable.

5. Instruction Assistance. The following instructions should assist the Offeror in developing and documenting adequate support for the price proposal. These instructions are not all-inclusive. The responsibility for providing price documentation rests with the Offeror. At a minimum, the Price Volume shall contain the following:

Part A. Fixed Price CLINs.

1. The Contract resulting from this solicitation will include Firm-Fixed Price CLINs for the FSR

CONUS, FSR OCONUS, Other Direct Costs, Spares and Consumables, Manuals, and Training.

Part B. Cost Reimbursable CLINs.

The contract resulting from this solicitation will include cost reimbursable CLIN Travel. This CLINs are non-fee bearing but may include G&A or other appropriate overhead charges consistent with the

Offeror’s accounting practices. Travel includes those costs, necessary for the direct support of this contract. Travel may be reimbursed provided such costs are specifically authorized and provided that the costs are reasonable, allowable, and allocable in accordance with the laws and regulations (e.g. FAR Part

31). Offerors shall be reimbursed for travel costs in accordance with the Federal Acquisition Regulations as limited by the Joint Travel Regulations, Volume II (available at http://www.dtic.mil/perdiem/jtr.pdf.)

and the following: (1) where official company travel can reasonably be planned in advance so as to take advantage of available discounted standard or coach airfares; (2) travel to and from work, shall not be reimbursed hereunder; and (3) the Offeror shall establish a primary place of performance in regards to any travel necessary to support the contract.

Part C. Attachment 3.

After contract award the winning offeror is responsible for providing a FFP proposal of

Attachment 3 Spares Parts List. Additionally the contractor may have to provide Cost and Pricing data depending on the threshold.

http://www.dtic.mil/perdiem/jtr.pdf

Exhibit A: Past Performance Statement

Offeror:

Program, Project Or Task Title:

Part I - REFERENCE INFORMATION

1 Customer Name:

2 Address:

Customer Info: Contractual Contact Client Program Manager

3 Name & Title:

4 Organization:

5 Address:

6 Phone No.:

7 Fax No.:

8 E-mail:

9 Task order Identification Number:

Task order Type (e.g. contract, BPA, task order) and pricing type (e.g. fixed price, cost reimbursement):

Original Dollar Value

Current Dollar Value

Explanation of Cost Growth (If applicable):

Project Start Date

Original Completion Date:

Estimated/Actual Completion Date:

Part II - PROGRAM DESCRIPTION AND RELEVANCE

Offeror:

Program, Project Or Task Title:

Description and relevance:

Exhibit B PAST PERFORMANCE QUESTIONNAIRE

I. NAME OF COMPANY QUESTIONNAIRE IS BEING SUBMITTED ON BEHALF OF :

(Offeror to complete item II A. and II B. prior to issuing this questionnaire to the Evaluator.)

In order to assess potential vendors under the Rugged Mobile Non-Intrusive Inspection System (RMNIIS)

Sustainment Support, Marine Corps Systems Command’s contracting office is obtaining past performance information with respect to each Offeror. In addition to this questionnaire, you may receive a follow-up phone call to confirm or clarify information. This is a critical acquisition being conducted by Marine Corps Systems Command and your support is sincerely appreciated. We thank you in advance for your time, effort, and cooperation in responding to this questionnaire. To be considered, the completed Questionnaire must be submitted directly via email from the customer reference to ann.pennington@usmc.mil by the due date established for receipt of offers.

The “subject” line in the submission email shall clearly indicate: “RMNIIS RFP Past Performance” and the message shall originate from the Evaluator’s corporate or government email system.

II. GENERAL GUIDANCE

Please use the following rating in scoring the performance elements below (assessments should reflect only contractor-liable performance):

RATING DESCRIPTION

Excellent The Offeror's past performance far exceeds the customer's expectations and contract requirements and provided significant, unusually worthwhile features or benefits.

Good The Offeror’s past performance exceeds the customer’s expectations and contract requirements and provided worthwhile features or benefits.

Satisfactory The Offeror's past performance clearly met the customer's expectations and contract requirements

Marginal The Offeror's past performance could have been improved but met most contract requirements.

Unsatisfactory The Offeror's past performance failed to meet customer expectations and one or more material contract requirements.

III. GENERAL INFORMATION

A. ORGANIZATION/AGENCY & RESPONDENT IDENTIFICATION:

1 Name & Title:

2 Organization:

3 Address:

4 Phone No.:

5 Fax No.:

6 E-mail:

7 Date:

8 Signature:

B. CONTRACT IDENTIFICATION:

Contractor

Name:

Name

Type of Instrument (e.g.

Contract/Order/Subcontract/Other):

3 Contract Identification Number:

4 Order Number (If applicable):

5 Project Title and Service Description (Add rows if needed):

Type of Contract (e.g. Negotiated, Sealed

Bid):

Pricing Type (e.g. fixed price, cost reimbursement, other):

8 Competitive (Y/N):

9 Follow-on (Y/N):

10 Date of Award:

11 Initial Contract Dollar Value (w/Options):

12 Final Contract Dollar Value (w/Options):

13 Period of Performance:

14 Place(s) of Performance:

15 Complexity of Work (e.g. difficult, routine):

16 Type and extent of subcontracting (add rows if needed):

C. GENERAL INFORMATION

Has the Contractor even been given a cure notice, show cause notice, suspension of progress payments, etc.? If yes, explain.

Has this contract been partially or completely terminated? If yes, explain and identify type of termination (e.g. default, convenience).

If this was an award or incentive fee contract, what percentage of the available fee did the Contractor usually receive?

Changes in contract dollar amounts throughout the life of the contract are/were generally attributable to customer-issued Change Orders, Contractor-submitted claims, other Customer actions (please explain):

IV. EVALUATION: How Would You Rate This Contractor With Respect To: (If you check Marginal below, please provide a comment as to why)

A. Compliance with the SOW and specifications; conformance to standards of good workmanship, and responsiveness to technical direction:

Rating Excellent Satisfactory Marginal Unsat

Check

Comment: __________________________________________________________________

B. Adherence to the contract delivery schedule:

Comment: __________________________________________________________________

C. Adherence to task order estimates; reasonableness of change order quotes; and completeness of billing:

Comment: ___________________________________________________________________

D. Working relationship with Contracting Officer, COTR, and other points of contact:

E. Relationship with and satisfaction level of agency end-user of product or service required:

In summary, if you care to, please give your overall assessment of this contractor.

SECTION M EVALUATION

M-1 BASIS FOR AWARD

1. Evaluation Summary

The Government will evaluate each Offeror’s proposal and use the results in the contracting source selection decision. The source selection process will determine the overall merits of each proposal in terms of its potential to best satisfy the needs of the Government. Proposals received before the RFP closing date and time established for this solicitation will be evaluated by a team of Government personnel. The employment and exercising of subjective judgment by the Government evaluators is implicit in the source selection process

2. Award

The Government intends to award a single contract resulting from solicitation M67854-13-R-2410 to the responsible Offeror on the basis of competitive source selection (FAR Subpart 15.3) using “Best Value” criteria per FAR 15.101. Award of the contract will be to the responsive and responsible Offeror;

- Whose proposal is technically acceptable;

- Whose proposal is deemed responsive to the solicitation requirements;

- Whose overall offer represents “Best Value” to the Government based on the Offeror’s overall technical merit, past performance, program management, and price.

Each Offeror’s proposal should contain the Offeror’s best price, and technical position. Any Offeror that is rated below “Marginal” in any evaluation Factor will not be considered for award.

The Government may award to other than the lowest-priced Offeror or to other than the Offeror with the highest technical rating if the Contracting Officer determines that to do so would result in the best value to the Government. Offerors, whether or not selected for task order award, will be eligible to bid on future contracts.

M-2 EVALUATION PROCESS

a. Pursuant to the criteria contained herein and the instructions provided in Section L, a combined technical/risk evaluation rating will be applied at the factor level for Technical and Program Management factors.

The Government will use the following proposal evaluation ratings:

Figure 1: Combined Technical/Risk Evaluation Rating for the Technical and Program

Management Factors

TECHNICAL and PROGRAM MANAGEMENT RATINGS

Color Rating Description

Blue Outstanding Proposal meets requirements and indicates an exceptional approach and understanding of the requirements. Strengths far outweigh any weaknesses. Risk of unsuccessful performance is very low.(Blue)

Purple Good Proposal meets requirements and indicates a thorough approach and understanding of the requirements. Proposal contains strengths which outweigh any weaknesses. Risk of unsuccessful performance is low. (Purple)

Green Acceptable Proposal meets requirements and indicates an adequate approach and understanding of the requirements. Strengths and weaknesses are offsetting or will have little or no impact on contract performance. Risk of unsuccessful performance is no worse than moderate. (Green)

Yellow Marginal Proposal does not clearly meet requirements and has not demonstrated an adequate approach and understanding of the requirements. The proposal has one or more weaknesses which are not offset by strengths. Risk of unsuccessful performance is high.

(Yellow)

Red Unacceptable Proposal does not meet requirements and contains one or more deficiencies. Proposal is unawardable. (Red)

Notes:

1) Strengths – That aspect of an Offeror's proposal that has merit or exceeds specified performance or capability requirements in a way that will be advantageous to the Government during contract performance.

2) Weaknesses – means a flaw in the proposal that increases the risk of unsuccessful contract performance. See FAR 15.001.

3) Significant Weaknesses – A flaw in a proposal that appreciably increases the risk of unsuccessful contract performance.

4) Deficiency – A material failure of a proposal to meet a Government requirement or a combination of significant weaknesses in a proposal that increases the risk of unsuccessful contract performance to an unacceptable level. See FAR 15.001.

b. A narrative past performance relevancy rating will be applied to the Past Performance Factor. The

Government will evaluate the Offeror’s Recent and Relevant Past Performance and provide an assignment of a past performance relevancy rating based on the Offeror’s past and present experience and performance, with efforts similar in size and scope.

The Government will use the following Past Performance Relevancy Ratings:

Figure 2: Past Performance Relevancy Ratings

RATING DEFINITION

Very

Relevant

Present/past performance effort involved essentially the same scope and magnitude of effort and complexities this solicitation requires.

Relevant Present/past performance effort involved similar scope and magnitude of effort and complexities this solicitation requires.

Somewhat

Relevant

Present/past performance effort involved some of the scope and magnitude of effort and complexities this solicitation requires.

Not

Relevant

Present/past performance effort involved little or none of the scope and magnitude of effort and complexities this solicitation requires.

c. A narrative Past Performance Confidence Assessment will be applied to the Past Performance Factor.

The Government will evaluate the Offeror’s Recent and Relevant Past Performance and provide a

Performance Confidence Assessment based on the Offeror’s past and present experience and performance with efforts similar in size and scope.

Confidence Risk Assessment ratings for Past Performance:

Figure 3: Past Performance Confidence Risk Assessment

RISK DEFINITION

Substantial

Confidence

Based on the Offeror’s recent/relevant performance record, the

Government has a high expectation that the Offeror will successfully perform the required effort.

Satisfactory

Confidence

Based on the Offeror’s recent/relevant performance record, the

Government has a reasonable expectation that the Offeror will successfully perform the required effort.

Limited

Confidence

Based on the Offeror’s recent/relevant performance record, the

Government has a low expectation that the Offeror will successfully perform the required effort.

No Confidence

Based on the Offeror’s recent/relevant performance record, the

Government has no expectation that the Offeror will be able to successfully perform the required effort.

Unknown

Confidence

(Neutral)

No recent/relevant performance record is available or the Offeror’s performance record is so sparse that no meaningful confidence assessment rating can be reasonably assigned.

d. Paragraph M 3.4 describes the Government methodology for evaluating price.

M-3 SPECIFIC EVALUATION CRITERIA

While the evaluated price to the Government is a substantial area to be taken into consideration in the integrated assessment of offers, the non-price factors, collectively, are of significantly greater importance.

Therefore, the Government may award to other than lowest price offer or to other than the Offeror with the highest technical rating if the Source Selection Authority determines that doing so would result in the best value to the Government. However, the Government will not make an award at a significantly higher price to achieve only slightly superior performance capability. The relative importance of the non-price factors are listed below in descending order of importance:

T: Technical

M: Program Management

PP: Past Performance

Technical is significantly more important than Program Management, which is more important than Past

Performance.

M-3.1 Technical

Part A. Technical Approach

The Government will evaluate the Offeror’s proposal for completeness and realism in regards to the FSRs in deployment locations and ability to accomplish the key elements below:

Maintain an operational availability greater than or equal to 90%. The RMNIIS’ Operational

Availability (Ao) equals Mission Capable Time (MCT) divided by the Total Time (TT). Ao shall be displayed as a percentage. Example: Ao = MCT ∕ TT

Work closely with the using units and the MCSC Liaison Officer (LNO)/FPS LNO in-theater who will notify FSRs to conduct any repairs or maintenance.

Provide training, and maintenance support systems located with the CONUS when necessary.

Ensure the responsible Program Analyst and Contracting Officer Representative (COR) are informed within twenty-four (24) hours of any issues involving systems and/or personnel.

Conduct scheduled and unscheduled preventative maintenance.

Conduct operational and maintenance training and mentoring of USMC personnel in the

CONUS and OCONUS locations as required.

Provide the necessary tools required to perform all maintenance activities.

Support inventory management and parts ordering.

Provide the Program Analyst and COR with weekly equipment status readiness reports and monthly parts inventory reports via an available secure or encrypted communication network.

Conduct repair of repairable.

Ability to deploy within sixty (60) days of contract award.

The Government will evaluate whether FSRs identified for OCONUS deployment are in compliance with

USCENTCOM deployment requirements per the USCENTCOM Individual Protection and Individual

Unit Deployment Policy, RFP Attachment5. The Government will evaluate the ability of FSRs of obtaining a National Agency Check with Inquiries (NACI) Background Investigation that has been verified in the Joint Personnel Adjudication System or possess an active Secret Security Clearance. Any proposal without the proper background investigations and clearances will be found unacceptable.

The Quality Assurance Surveillance Plan will not be evaluated as a separate factor. The QASP will be evaluated as part of the Contractor Performance Work Statement (CPWS).

Part B. Training

The Government will evaluate the Offer’s approach to OCONUS and CONUS locations operator training courses and maintainer training courses. The Government will evaluate training for radiation, safety, warning, and cautions training associated with this system.

Operator training course will be evaluated on completeness, comprehensiveness, and the ability to provide the operator with the knowledge and skills necessary to perform operator tasks. The maintainer training course will be evaluated on the ability to provide the maintainer with the knowledge and skills necessary to perform Operator/Crew level maintainer tasks.

Part C. Contractor Logistics Support (CLS).

The Government will evaluate the proposed logistics support services for completeness and realism for the system unique items necessary to maintain the operational readiness of the RMNIIS. The

Government will evaluate the technical approach and ability to accomplish the key elements below:

Maintenance

Supply chain management

Parts Procurement/Sustainment

Component Exchange

Calibration (if required)

Technical Assistance

Failure Reporting Analysis and Corrective Action (FRACAS)

Operator and Maintainer Training (to include radiation safety)

Part D. Maintenance Planning.

The Government will evaluate the Offeror’s maintenance planning for completeness and realism. The

Government will evaluate whether All Levels of Maintenance (LOM) whether Operator/Crew, Field, or

Sustainment will be performed by the Contractor’s FSRs.

The Government will evaluate whether the Offeror’s proposal provides all labor, services, parts

(consumables and non-consumables), supplies, packaging, and shipment of items necessary to maintain, diagnose, and correct malfunctions or failures in regards to overall RMNIIS operation and to accomplish all maintenance required.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .