Attachment_7_-_Section_L_(21_August_2014).pdf

PDF 114 KB Posted

Attached to
AN/FMQ-22 Automatic Meteorological Station (AMS) Contractor Logistics Support (CLS)
Solicitation number
FA8730-14-R-0017
Issued by

About this file

Attachment 7 - Section L (21 August 2014)

View the file

Other files

File Type Posted
FMQ-22_CLS_RFP_QA_Responses_(7_Oct_14).pdf PDF
Update_to_Attachment_9_(24_September_2014).pdf PDF
Attachment_5_-_Total_Evaluated_Price_Worksheet_(23_September_2014).xlsx XLSX spreadsheet
FMQ-22_CLS_RFP_Q A_Responses_(23_September_2014).pdf PDF
FMQ-22_CLS_RFP_Q A_Responses_(17_September_2014).pdf PDF
FA8730-14-R-0017_Rev_1_September_2014.pdf PDF
Attachment_7_-_Section_L_(17_September_2014).pdf PDF
Attachment_7_-_Section_L_(11_September_2014).pdf PDF
FMQ-22_CLS_RFP_Q A_Responses_(11_September_2014).pdf PDF
FMQ-22_CLS_RFP_Q A_Responses_(8_September_2014).pdf PDF
Exhibit_B_-_Separately_Priced_CDRL's_(Rev_2 _Sep_2014).pdf PDF
Exhibit_A_-_Not_Separately_Priced_CDRL's_(Rev_2_Sep_2014).pdf PDF
FMQ-22_CLS_RFP_QA_Responses_(21_August_2014).pdf PDF
FMQ-22_Spares_Warranty_Status.pdf PDF
FMQ-22_CLS_RFP_QA_Responses_(26_August_2014).pdf PDF
FMQ-22_CLS_RFP_QA_Responses_(18_August_2014).pdf PDF
Attachment_3_-_Client_Authorization_Letter_(17_April_2014).docx DOCX document
Attachment_6_-_Performance_Work_Statement_(19_August_2014).pdf PDF
Attachment_10_-_Government_Furnished_Property_List_(26_Aug_2014).pdf PDF
Attachment_2_-_Subcontractor_Teaming_Partner_Consent_Letter_(17_April_2014).docx DOCX document
Attachment_8_-_Section_M_(21_August_2014).pdf PDF
Exhibit_A_-_Not_Separately_Priced_CDRL's_(19_August_2014).pdf PDF
Exhibit_B_-_Not_Separately_Priced_CDRL's_(19_August_2014).pdf PDF
Attachment_5_-_Total_Evaluated_Price_Worksheet_(21_August_2014).xlsx XLSX spreadsheet
Amendment_Change_Log_(27_August_2014).pdf PDF
FA8730-14-R-0017_Revision_1.pdf PDF
Attachment_11_-_Cross_Reference_Matrix_(22_August_2014).xlsx XLSX spreadsheet
Attachment_1_-_Past_Performance_Information_Sheet_(15_August_2014).docx DOCX document
Attachment_15_-_PSE_and_LRU_List_(22_August_2014).pdf PDF
Attachment_4_-_Roles_and_Responsibilities_Worksheet_(17_April_2014).xlsx XLSX spreadsheet
FMQ22_Spares_Usage__July_2013_-__June_2014_(15_August_2014).xlsx XLSX spreadsheet
Attachment_1_-_Past_Performance_Information_Sheet_(15_August_2014).pdf PDF
FMQ-22_CLS_RFP_Q A_Responses_(15_August_2014).pdf PDF
FMQ-22_CLS_RFP_Q A_Responses_(12_August_2014).pdf PDF
Attachment_6_-_Performance_Work_Statement_(12_August_2014).pdf PDF
Attachment_6_-_Performance_Work_Statement_(11_Apr_14).pdf PDF
Attachment_7_-_Section_L_(5_August_2014).pdf PDF
Attachment_11_-_Cross_Reference_Matrix_(17_April_2014).xlsx XLSX spreadsheet
Attachment_1_-_Past_Performance_Information_Sheet_(5_August_2014).pdf PDF
Exhibit_B_-_Separately_Priced_CDRL's_(30_July_2014).pdf PDF
Attachment_4_-_Roles_and_Responsibilities_Worksheet_(17_April_2014).xlsx XLSX spreadsheet
Attachment_10_-_Government_Furnished_Property_List_(20_June_2014).pdf PDF
Attachment_3_-_Client_Authorization_Letter_(17_April_2014).pdf PDF
Attachment_2_-_Subcontractor_Teaming_Partner_Consent_Letter_(17_April_2014).pdf PDF
FA8730-14-R-0017_RFP_Without_Attachments_(7_August_2014).pdf PDF
Exhibit_A_-_Not_Separately_Priced_CDRL's_(30_July_2014).pdf PDF
Attachment_8_-_Section_M_(5_August_2014).pdf PDF
Attachment_5_-_Total_Evaluated_Price_Worksheet_(5_August_2014).xlsx XLSX spreadsheet
Attachment_14_-_Min_Max_purchase_quantities_(22_July_2014).pdf PDF
FBO_Presolicitation_Posting_(1_August_2014).pdf PDF
Show 40 more

50 files listed here. See the rest on GovTribe.

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

Addenda to FAR 52.212-1

Instructions, Conditions, and Notices to Offerors (ITO) for the

Acquisition of Commercial Items

For the

AN/FMQ-22 Automated Meteorological System (AMS)

21 August 2014

52.212-1 Addenda Page 1 of 18

Section Content:

1.0 - Program Structure Objectives

2.0 - General Instructions

3.0 - Volume I – Executive Summary

4.0 - Volume II – Technical Proposal

5.0 - Volume III – Price Proposal

6.0 - Volume IV – Performance Confidence

7.0 - Volume V – Contract Documentation

8.0 - Required Attachments

1.0 Program Structure and Objectives

The objective of this effort is to solicit contractor logistics support services to sustain the AN/FMQ-22 Automatic Meteorological Station in its current configuration worldwide, while maintaining Fully Mission Capable (FMC) availability rates for 70 AN/FMQ-22 Systems globally and to accomplish the work requirements specified within the Performance Work Statement (PWS).

2.0 General Instructions

(a) This section of the instructions provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror’s proposal must include all data and information requested by the instructions and must be submitted in accordance with these instructions.

The proposal must be complete, self-sufficient, and respond directly to the requirements of this solicitation. The proposal shall be compliant with and meet all of the Request for Proposal (RFP) requirements, such as terms and conditions, representations and certifications, technical requirements, requirements identified as evaluation factors and subfactors, requirement to return the provision FAR 52.212-3 (Offeror Representations and Certifications – Commercial Items) with the proposal and to complete and return the SF 1449 blocks 12, 17a, 30a, 30b, and 30c. Offerors are advised that submissions that DO NOT conform to the instructions provided herein may result in an unacceptable proposal evaluation, and/or exclusion from further consideration.

(b) Include Sufficient Detail: The proposal shall be clear, concise, and shall include sufficient detail for an effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements and objectives, but shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities, capabilities, and experience, and will base its evaluation on the information presented in the offeror’s proposal.

52.212-1 Addenda Page 2 of 18

(c) Embellishments Not Desired: Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

(d) Proposal Acceptance and Validity Dates: The proposal shall be valid for a period of 270 calendar days from the required submission date. The Offeror shall make a clear statement on the front page of the Contract Documentation Volume (Volume V) that the proposal is valid for a period of not less than 270 calendar days from the required submission date. Based on an anticipated award in February 2015, the Government contemplates the following periods of performance for each ordering period:

Base Period: February 2015* – January 2016 Option Year 1: February 2016 – January 2017 Option Year 2: February 2017 – January 2018 Option Year 3: February 2018 – January 2019 Option Year 4: February 2019 – January 2020 52.217-8 Option to Extend Services: February 2020 – July 2020

*The actual contract award date may differ from this notional date and is not a guarantee of performance. Each period of performance will be twelve (12) months in length, with the exception of the 52.217-8 period which will not exceed six (6) months in length.

(e) Disposition of Proposals: In accordance with FAR Subpart 4.803 (a), the Government will retain one copy of all proposals. Unless the offeror requests otherwise (in their proposal), the Government will destroy extra copies of the successful and unsuccessful proposals.

(f) Past Performance: For each contract identified, the offeror shall complete a Past Performance Information Sheet (PPIS), Attachment 1, in response to this RFP. The PCO will make a determination of acceptable past and current performance in accordance with FAR part 15.101-2 and FAR part 15.305(a)(2).

2.1 General Information

2.1.1 Contact Information: The Procurement Contracting Officer and the Contract Specialist are the sole points of contact for this acquisition. Written requests for clarification may be sent by mail or email to the Contracting Officer, with a copy to the Contract Specialist. Contact Information is below:

52.212-1 Addenda Page 3 of 18

AFLCMC/HBAK

ATTN: Mr. Matthew Smith Contract Specialist 75 Vandenberg Drive, Bldg 1630 Hanscom AFB, MA 01731-2103 matthew.smith.96@us.af.mil 781-225-5420

AFLCMC/HBAK

ATTN: Captain Kenneth Haile Procurement Contracting Officer 75 Vandenberg Drive, Bldg 1630 Hanscom AFB, MA 01731-2103 Kenneth.haile.1@us.af.mil 781-225-5075

All questions and answers shall be sent through the prime offeror.

2.1.2 Debriefings: The PCO will promptly notify offerors of any decision to exclude them from the competitive range or otherwise eliminate them from the competition in accordance with FAR 15.503; whereupon they may request and receive a debriefing in accordance with FAR 15.505 and/or FAR 15.506.

Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 and/or FAR 15.506 procedures, as applicable.

2.1.3 Discrepancies: If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the PCO in writing with supporting rationale. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussions.

2.1.4 Electronic Reference Documents: All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOps), web site at https://www.fbo.gov/. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.1.5 Oral Presentations: Oral presentations will not be allowed.

2.1.6 Communications: Exchanges of source selection information between Government and offerors will be controlled by the Contracting Officer. Email may be used to transmit such information to offerors. The PCO may determine to conduct telephone exchanges when deemed appropriate by the Government.

52.212-1 Addenda Page 4 of 18 mailto:matthew.smith.96@us.af.mil mailto:Kenneth.haile.1@us.af.mil https://www.fbo.gov/

2.2 Organization/Number of Copies/Page Limits

The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.1) below. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified. The technical proposal, price proposal, and performance confidence volumes identified in the table shall be separately bound in three-ring, loose-leaf binders; the remaining volumes can be in one binder with a clear tab for each volume. However, for the electronic copy requested below, every volume shall be on a different CD-R. The paper and electronic copies shall be clearly identified.

The contents of each proposal volume are described in this section and summarized in the table below. Offerors shall include a Table of Contents in the proposal. In addition to the “Hard Copies” requested in Table 2.1 below, please submit one CD-R for each volume of the offeror’s proposal (not on CD-RW).

Table 2.1 - Proposal Organization

Volume Instruction Paragraph Number

Title Hard Copies

Electronic Copies

Page Limit

I 3.0 Executive Summary 2 1 5 II 4.0 Technical Proposal 5 1 150 III 5.0 Price Proposal 3 1 Unlimited IV 6.0 Performance Confidence 3 1 25 V 7.0 Contract Documentation 2 1 Unlimited

2.2.1 Page Limitations: Page limitations are identified in Table 2.1 – Proposal Organization, and explained below. Offerors are advised that the limitations shall be treated as maximums. If exceeded, the excess pages will not be evaluated or considered for award purposes; rather, they will be returned to the offeror as soon as practical. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarded. When both sides of a sheet display printed material, it shall be counted as 2 pages. In the event that an offeror includes fold-out pages, the folded-out portion shall be counted the same as an 8.5 x 11 sheet. Each page shall be counted except cover/title pages, tables of contents, tabbed dividers, acronym lists and glossaries.

2.2.1.1 Page Size and Format

(a) A page is defined as each face of a sheet of paper containing information.

When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 by 11 inches (foldouts must fold into no larger than 8.5 by 11 inches). Pages shall be typed using 1.5 line spacing, except for the reproduced sections of the solicitation document; the text size shall be no less than 12 point in Times New Roman typeface. Use at least 1 inch margins on

52.212-1 Addenda Page 5 of 18 the top and bottom and 3/4 inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall also apply to responses to ENs. These limitations shall apply to both electronic and hard copy format.

(b) Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc.

These displays shall be uncomplicated, legible and shall not exceed 8.5 by 11 inches in size. For tables, charts, graphs and figures, the text shall be no smaller than 8 point font. These limitations shall apply to both electronic and hard copy proposals.

2.2.2 Cross Referencing: Each Volume (I – V) of the proposal shall be submitted, evaluated, and considered based solely on the information contained therein (i.e. each volume “stands-alone”). Cross referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal.

2.2.3. Pricing Information: All cost or pricing information shall be addressed ONLY within the Pricing and Contract Documentation Volumes.

2.2.4. Classified Information: Classified information SHALL NOT be provided in the offeror’s response to this RFP.

2.2.5. Indexing: Each volume shall contain a detailed table of contents delineating the subparagraphs within that volume. Tab indexing shall be used to identify sections.

2.2.6. Glossary of Abbreviations and Acronyms: Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each.

Glossaries do not count against the page limitations for their respective volumes.

2.2.7. Binding and Labeling: The three-ring loose leaf binders used to contain the proposal information shall permit the volumes to lie flat when open. Staples shall not be used. A cover sheet should preface each volume, clearly marked as to volume number, title, copy number, solicitation identification and the offeror's name. The same identifying data should be placed on the spine of each binder.

Since classified information shall not be provided in the proposal, all document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-5, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information. Each page that contains proprietary information shall be marked inside the header and footer of each

52.212-1 Addenda Page 6 of 18 page with the following statement “SOURCE SELECTION INFORMATION (FAR

3.104) FOR OFFICIAL USE ONLY.”

2.3 Electronic Offers: The content and page size of the electronic copies must be identical to the hard copies in all respects. The electronic copies shall be submitted on a single, virus free, ISO formatted read-only CD-R. Indicate on each “CD-R” the volume number and title (NOTE THAT “CD-RWs” CANNOT BE READ, EVALUATED, OR CONSIDERED). Each volume shall be in a different “CD-R”. File compression will not be used. Each disk will be clearly labeled.

Paper and electronic copies must be identical in all respects. In the event that there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation. The electronic copy of the proposal shall be submitted in a format readable by Microsoft (MS) Office 2010 Suite of Applications (Word, Excel, and Power Point) as applicable. PDF files are not acceptable. To facilitate evaluation electronic copies of the Pricing Volume (Volume III) of the proposal shall be submitted using Microsoft’s Excel format. Please do not “read protect” submitted Excel worksheets. Provide all formulas (evident within the spreadsheet) and links used. Do not embed electronic files within other electronic files. Word documents and Excel spreadsheets must be editable and not password protected.

2.4 Distribution: The "original" proposal shall be so designated and signed by the offeror’s authorized representative, and the “copies” should be identified appropriately. All requested copies must be received by the due date identified on the front page of the RFP. Proposals shall be addressed to the PCO and delivered to:

AFLCMC/HBAK

Captain Kenneth Haile, PCO c/o Matthew Smith, Contract Specialist 75 Vandenberg Drive, Bldg 1630 Hanscom AFB, MA 01731-2103

781-225-5420 / DSN 845-5420

FAX: 781-225-2431

matthew.smith.96@us.af.mil

Include Solicitation Number FA8730-14-R-0017 on the address label.

3.0 Volume I - Executive Summary

In the Executive Summary Volume (Volume I), the offeror shall provide the following information:

3.1 Table of Contents: Provide a master table of contents for the entire proposal, by ITO and Government PWS paragraph number and the

52.212-1 Addenda Page 7 of 18 mailto:matthew.smith.96@us.af.mil corresponding paragraph that addresses the referenced item. The table of contents will not count against the page limitation for this volume.

3.2 Other Information Required

3.2.1 Authorized Offeror Personnel: Provide the name, title, telephone number, and email address of the company/division point of contact regarding decisions made with respect to the offeror’s proposal and who can obligate (as to this proposal) the offeror’s company/firm contractually. Also identify those individuals authorized to negotiate with the Government.

3.2.2 Government Offices: Provide the mailing address, telephone number, email address, and facility code for the cognizant DCMA Contract Management Office, DCAA, and Government Paying Office for the offeror’s company/firm. Also provide this information for the Administrative Contracting Officer (ACO).

3.2.3 Company/Division Address, Identifying Codes, and Applicable Designations:

• Offeror shall provide company/division's street address, county and facility code; CAGE code; DUNS code; size of business (large or small); and labor surplus area designation. This same information must be provided if the work (for completing what is proposed) will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

• Offeror shall provide verification that at least 51 percent of the cost of contract performance incurred for personnel would be expended for employees of the prime contractor performing the key and vital areas of the work in this contract. Additionally, offeror shall provide verification that at least 51 percent of the cost for the “repair and maintenance of system components/spares” portion of contract performance, incurred for personnel, will be expended for employees of the prime contractor.

3.3 Volume Organization: The Executive Summary shall be organized according to the following general outline:

1. Table of Contents*

2. Authorized Offeror Personnel POCs

3. Government Offices POCs

4. Company Address, Cage Codes and Applicable Designations

5. Certification Statement*

6. Partnership/Joint Venture Agreement(s)

*Not included in page count

52.212-1 Addenda Page 8 of 18

4.0 Volume II Technical Proposal

4.1 General: The technical proposal shall be clear, concise, complete, and include sufficient detail for effective evaluation. Legibility, clarity, and coherence are very important. The proposal shall not simply rephrase or restate the Government’s requirements, but rather shall provide convincing documentation to address how the offeror will meet these requirements. There will be no reference to rates or price in this volume. Offerors shall assume that the Government has no prior knowledge of their certifications, facilities and/or structural, mechanical, and electronics capabilities, and will base its evaluation on the information presented in the offeror’s proposal. Offerors’ responses will be evaluated against the factors and sub-factors defined in addenda to FAR 52.212-2 (Evaluation—Commercial Items). Using the instructions provided below, provide as specifically as possible the actual methodology the offeror would use for accomplishing/satisfying these sub-factors. All the requirements specified in the solicitation are mandatory. By the offeror’s proposal submission, the offeror is representing that the company/firm will perform ALL the requirements specified in the solicitation (including PWS and Sensor Specification Package); it is not necessary or desirable to tell us so in the proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

4.1.1 Adequate Responses: Cursory responses or content which merely reiterates or reformulates FAR 52.212-1 (or its addenda), FAR 52.212-2 (or its addenda), or the PWS will not be considered as being responsive to the requirements of the solicitation. Evidence (which clearly demonstrates and supports the offeror’s claims) is essential. The absence of such evidence may result in a technically unacceptable proposal.

4.2 Volume Organization: The Technical Proposal shall be organized according to the following general outline:

2. List of Table and Drawings*

3. Glossary*

4. Technical Approach

5. Management Approach

a. Program Management Plan

b. Transition Plan

c. Configuration Management Plan

d. Quality Assurance Program Plan

6. Experience

4.3 Technical Acceptability Factor

52.212-1 Addenda Page 9 of 18

4.3.1 Sub-Factor A: Technical Approach – Logistical Support and Computer Resource Support (PWS Sections 4, 5, 6, & 7)

4.3.1.1 The proposal shall describe in detail the offeror’s technical approach for meeting the PWS Section 4, 5, 6, and 7 requirements identified in the following paragraph. For those requirements, the proposal shall mirror the outline of the PWS; thus, paragraph 4.2 of the offeror’s proposal shall address requirements set forth in paragraph 4.2 of the PWS, etc. If the technical approach utilizes subcontractor(s), identify how the prime contractor will be responsible for performing the primary and vital requirements.

Specifically, the offeror shall provide detailed strategies of how they will accomplish and satisfy the following key requirements IAW the PWS:

• Contractor Performance – ability to meet Operational Availability (AO) requirements (PWS para 6.2)

• Helpdesk (PWS para 6.1)

• Reliability and Maintainability – including, but not limited to, Obsolescence and System Designs, Enhancements, and Upgrades (PWS para 7.2) o Include rationale for how the resolution proposed for obsolescence will be fully completed while still continuously meeting all CLS requirements

• Spares Management (PWS para 6.3)

• Support Equipment (PWS para 6.3.1)

• Configuration Management (PWS para 6.6)

• System Manuals/TOs (PWS para 6.7)

• Government Furnished Property Management (PWS para 6.9)

• Engineering Change Proposals/Special Projects (PWS para 7.2)

• Training/Training Materials (PWS para 6.8)

• Packaging, Handling, Storage, and Transportation (PWS para 6.4)

• Computer Resource Support (PWS para 5.1)

• Security Accreditation (PWS para 5.2)

• Time Compliance Network Orders (PWS para 5.2.7, 5.3)

• Laptop Option (PWS para 5.3)

4.3.2 Sub-Factor B: Management Approach – Program Management, System Sustainment Management and Configuration Management (PWS Sections 3, 6, & 7)

4.3.2.1 The proposal shall describe the offeror’s program management approach toward accomplishing the requirements of the PWS. The offeror shall submit four (4) plans entitled: (a) Program Management Plan; (b) Transition Plan; (c) Configuration Management Plan; and (d) Quality Assurance Program Plan.

52.212-1 Addenda Page 10 of 18

The proposal shall contain all of the following plans:

(a) Program Management Plan (PMP). A PMP shall be provided in the same format as CDRL A013 (PWS Section 3.1).

The offeror shall describe their approach that outlines all processes and programs by which the offeror will effectively execute the requirements of the PWS. The plan shall include an organizational chart of all key contractor employees, consultants and subcontractors that contains the appropriate level of expertise and skill mix for the successful performance of the AN/FMQ- 22 program. The plan shall address the performance of special projects, how the offeror will obtain required parts from AN/FMQ-22 OEMs, and the offeror’s approach to contractually required communication with the Government (e.g.

IPTs, PMRs, TIMs).

(b) Transition Plan. A Transition Plan shall be provided IAW PWS Section 3.5.

The offeror shall submit a Staffing Sub-Plan as part of the Transition Plan, detailing how employees meet the technical requirements of the PWS. The Staffing Plan shall reflect strategy regarding personnel recruiting, retention, and clearances. If recruiting includes employees not currently employed by the offeror (or subcontractor), documentation shall be provided that supports the intent to hire. The Staffing Plan shall describe the offeror’s plan for staffing in the time frame required by the PWS with number of personnel identified and available in appropriate skill level categories; to include skill category, service monthly hours by category and all supporting documentation.

The offeror shall submit an Inventory Relocation and AN/FMQ-22 Sustainment Sub-Plan as part of the Transition Plan, detailing how the offeror plans to maintain the AN/FMQ-22 at an AO of 96% on day 1 after transition is complete. The transition plan shall also include a plan to receive and maintain current (and future) inventory of GFP

Note that the proposed transition plan from the successful offeror will be contractually incorporated into the contract.

The Associate Contractor Agreement (ACA) identified in PWS Section 3.5.3 shall not be submitted with the offeror’s proposal. The Contracting Officer will separately request the ACA submission if the offeror is selected for contract award.

(c) Configuration Management Plan (CMP). A CMP shall be provided in the same format as CDRL A011 (PWS Section 6.6).

52.212-1 Addenda Page 11 of 18

The offeror shall provide a CMP describing its methodology to maintain software and hardware configuration for 70 AN/FMQ-22 systems worldwide, and a strategy to identify, test, provide data, integrate and field modifications.

(d) Quality Assurance Program Plan (QAPP). A QAPP shall be provided in the same format as CDRL A011 (PWS Section 3.3.1).

The offeror shall provide a QAPP describing its methodology to address quality issues and risks with a cross-reference matrix of contract requirements to contractor operating instructions/work instructions, and a strategy to track corrective actions, analyze trends, and maintain quality assurance records and data.

4.3.3 Sub-Factor C: Experience

4.3.3.1 The proposal shall describe the offeror’s core experience in Contractor Logistics Support (CLS) services specifically related to weather systems, in accordance with the key elements listed in the PWS paragraphs identified below.

Offeror must identify at least one year of continuous experience within the past 5 years. Experience must apply to potential core personnel planned for this effort.

Core personnel meeting this experience requirement do not have to be current employees. Core personnel are defined as individuals who will have a primary responsibility in accomplishing the below key elements of the AN/FMQ-22 Weather System CLS, and who are anticipated to provide the stability necessary to ensure continuity during the contractual time period of the program. Offeror shall detail how it will address transition of core personnel to maintain expertise and continuity.

The proposal shall address the following key experience elements of what is required in sections 5, 6, and 7 of the PWS. Specifically, the offeror shall provide evidence of how they accomplished and satisfied the following key experience requirements:

• Meteorological System Logistics Support: IAW PWS Section 6

• Reliability and Maintainability (Obsolescence, System Design Changes, Enhancements, and Upgrades), Systems Engineering, and Configuration Management: IAW PWS Section 7

• Computer Resource Support IAW PWS para 5.1

• Time Compliance Network Orders: IAW PWS para 5.3.5

• Security Accreditation - DoD Information Assurance Certification and

Accreditation Process (DIACAP): IAW PWS para 5.2

5.0 Volume III - Price Proposal

52.212-1 Addenda Page 12 of 18

5.1 General: The primary purpose of the price proposal volume is to provide the contracting officer and the price team evaluators an understanding of how the price proposal was developed. The price evaluation criteria of reasonableness, balance, and Total Evaluated Price (TEP) as defined in the evaluation document of the RFP will be assessed from the offeror’s information provided in this volume.

5.1.1 Total Evaluated Price (TEP):

(a) Attachment 5 is the TEP worksheet and will be populated by the contractor in accordance with the worksheet’s instructions. Prices in the worksheet shall match pricing from information proposed in the line item schedule of the solicitation. The TEP is for award determination purposes only and will be a consideration in the best value award decision. The rates proposed on the fixed rates table worksheet will be incorporated into the contract at time of award.

(b) The TEP for this acquisition will be established by adding together the fixed-price CLINs as described below.

CLIN X001, AN/FMQ-22 Contractor Logistics Support (CLS) CLIN X002, Laptop Option CLIN 0003, Transition CLIN X004, Engineering Change Proposals (ECPs)/Special Projects

(c) The total TEP will be the price factor in determining which offeror’s proposal represents the best value to the government. Consequently, the offeror submitting the “best value” proposal will be the successful contract awardee.

5.1.2 Estimating Techniques and Methods: When responding to the Pricing Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating Relationships (CERs), commercially available parametric cost models, in-house developed parametric cost models, etc.), to develop their estimates.

5.1.3 Price Information: Information beyond that required by this instruction shall not be submitted, unless offeror considers it essential to document or support their cost/price position. All information relating to the proposed price including all required supporting documentation must be included in the Price Proposal and Contract Document Volumes. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

5.1.4 Pricing Information Requirements: In accordance with FAR 15.403-1(b) and 15.403-3(a), information other than pricing data may be required to support price reasonableness. Information shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the CO determines that there is

52.212-1 Addenda Page 13 of 18 insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offer shall be required to submit pricing data.

The PCO has made a preliminary determination of “Adequate Price Competition” IAW FAR 15.403-1(c)(1). Therefore, a Certificate of Current Cost or Pricing Data per FAR 15.403-4 will not be required. In the event that adequate competition does not emerge in response to the solicitation, the PCO may require current cost or pricing data IAW FAR 15.403-4.

5.1.5 Rounding: All dollar amounts provided shall be rounded to the nearest dollar with the exception of loaded labor rates. Loaded labor rates shall be rounded to the nearest penny.

5.2 Volume Organization

The Pricing volume shall consist of the following sections:

SECTION 1 – Table of Contents; summary descriptions of estimating, and accounting systems; changes to estimating and accounting practices, if applicable.

SECTION 2 – Pricing information and supporting data, to include estimating methodology.

SECTION 3 – Other information such as Government Furnished Property/Government Furnished Equipment (GFP/GFE), base support, long lead costs, termination costs, inflation rate summary and explanation, and life cycle costs.

SECTION 4 – The offeror will complete the Excel file, Section J “TEP worksheet” IAW in the instructions. This completed worksheet will be utilized to develop the TEP. The TEP is for award determination purposes only and will be a consideration in the best value award decision.

6.0 Volume IV – Performance Confidence

6.1 General: Each offeror shall submit a performance confidence volume containing (i) completed PPIS’ in accordance with the format contained in Attachment 1, Past Performance Information Sheets. Offerors may submit a maximum of five (5) PPISs on the prime contractor and a maximum of three (3) for its proposed key subcontractors individually for recency and relevancy; and

(ii) a completed Roles and Responsibilities Worksheet in accordance with the format contained in Attachment 4, Roles and Responsibilities Worksheet, for all proposed subcontractors performing direct labor for this effort. The offeror has

52.212-1 Addenda Page 14 of 18 discretion in determining the most beneficial mix and quantity of contracts by prime offeror, key partners, or subcontractors covering as many of these elements as is practical.

The Offeror shall coordinate Attachment 1b, Past Performance Questionnaires, with each of the POCs identified in the Performance Confidence Volume, and provide evidence of transmission to those POCs. The Offeror may add its own transmittal letter to provide an Offeror representative name and telephone number; in case questions arise from the POC receiving the questionnaires. In your transmittal letter, direct the POCs to submit completed questionnaires directly to the USG POCs. The USG POCs are identified in Attachment 1b.

Once the Past Performance Questionnaires are completed by the POCs, the information contained therein shall be considered sensitive and shall not be released to you, the Offeror.

6.1.1 Consent Letter: The offeror shall also submit a consent letter (Attachment

2) executed by each key subcontractor, and/or teaming partners identified on Roles and Responsibilities Worksheet, Attachment 4, authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. A Consent Letter is provided because past performance information pertaining to a subcontractor cannot be disclosed to the prime offeror without the subcontractor’s consent. Provide with the proposal a letter from key subcontractors and/or teaming partners that will perform major or critical aspects of the requirement, consenting to the release of their past performance information to the prime contractor.

6.1.2 Client Authorization Letter: For each identified effort for a commercial customer, the offeror shall submit a client authorization letter (Attachment 3), authorizing release to the Government of requested information on the offeror’s performance.

6.1.3 Summary Table: The offeror shall submit a Summary Table (see format below). The purpose of the summary table is to capture the total scope of work that the offeror is presenting in this Performance Confidence Volume. The Government may obtain and use performance information on any or none of these programs. (This Section counts against the page count.) The table shall include (as a minimum) current information as follows:

Contractor Contract Number

Total Period of Performance

Maximum Total Estimated Dollars

Contracting Agency or Customer

Phone Number and E-Mail Addresses of at Least Two POCs (one being a “Contracts”

POC)

Brief Program Description (max 25 words)

Stage of the Program & Brief Status (max 25 words)

52.212-1 Addenda Page 15 of 18

6.2 Performance Confidence Volume Submission: It is requested that the offeror submit its Performance Confidence Volume 10 calendar days prior to the date set forth in block 8 of the SF 1449 for receipt of proposal; however offerors shall not submit it later than the proposal deadline.

6.3 Relevant Contracts: Submit information in accordance with Attachment 1, Past Performance Information Sheet. The offeror shall submit past performance information for a maximum of five recent contracts that are most relevant in demonstrating the offeror’s ability to perform the proposed effort. The offeror shall also include information for a maximum of three recent contracts performed by each of the teaming partners and significant subcontractors that are considered most relevant in demonstrating their ability to perform the proposed effort. Offeror shall include rationale supporting its assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining recency and relevancy, see FAR 52.212-2 Addenda, Evaluation Criteria for the Acquisition of Commercial Items.

6.4 Organizational Structure Change History: Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a “roadmap” describing all such changes in the organization of the offeror’s company. As part of this explanation, show how these changes impact the relevance of any efforts the offeror identifies for past performance evaluation/performance confidence assessment. Since the Government intends to consider past performance information provided by other sources as well as that provided by the offeror(s), the offeror’s “roadmap” should be both specifically applicable to the efforts identified and general enough to apply to efforts on which the Government receives information from other sources.

6.5 Contractor Relationships: Provide information regarding predecessor companies, key personnel who have relevant experience or subcontractors that will perform major or critical aspects of the requirement when such information is relevant to the acquisition and will be considered in the evaluation. If a teaming arrangement is contemplated, provide complete information as to the arrangement, including any relevant and recent past performance information on previous teaming arrangements with same partner. As with all past contracts identified in the proposal, use the PPIS (Attachment 1).

52.212-1 Addenda Page 16 of 18

6.6 Clarifying Submitted Past Performance: The Government may contact the points of contact provided by the offeror for the purpose of ascertaining and/or clarifying past performance information.

6.7 Specific Content: Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to an unacceptable past performance evaluation rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified.

For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required. Categorize the relevant information into the specific Technical subfactors and Price factor used to evaluate the proposal.

6.8 Volume Organization

The Performance Confidence volume shall be organized according to the following general outline:

2. Glossary*

3. Summary Table*

4. Past Performance Information Sheets (PPISs) (Attachment 1)

5. Consent Letters (Attachment 2)*

6. Client Authorization Letters (Attachment 3)*

7. Roles and Responsibilities Worksheet (Attachment 4)*

7.0 Volume V - Contract Documentation

7.1 Model Contract/Representations and Certifications: The purpose of this volume is for the offerors to provide the following:

7.2 Solicitation/Contract Form:

(a) Complete blocks 12, 17a, and 30a, b, and c of the SF1449. In doing so, the offeror accedes to the contract terms and conditions as written in the SOLICITATION, with attachments. The SOLICITATION constitutes the model contract.

52.212-1 Addenda Page 17 of 18

(b) Insert proposed unit and extended prices in the Pricing Schedule. The extended amount must equal the whole dollar unit price multiplied by the number of units. The proposal(s) must be submitted for five (5) years plus six (6) Option months (FAR 52.217-8, Option to Extend Services).

(c) Complete the necessary fill-ins and certifications in provisions. The provisions FAR 52.212-3, Offeror Representations and Certifications – Commercial Items, shall be returned along with the proposal.

(d) Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 7.2.

Table 7.2 - Solicitation Exceptions

Solicitation Document

Page/ Paragraph

Requirement/ Portion Rationale

SOO, SOW, SPEC,

Model Contract, ITO, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

7.3 Deliveries or Performance: Alternate delivery schedules are not acceptable as this is an Indefinite Delivery/Indefinite Quantity award. Failure to meet the solicitation’s required delivery will result in ineligibility for award. Specific delivery requirements shall be addressed in each resulting Task/Delivery order placed under the resulting contract.

52.212-1 Addenda Page 18 of 18

Section Content:
1.0 Program Structure and Objectives
2.0 General Instructions
3.0 Volume I - Executive Summary
4.0 Volume II Technical Proposal
5.0 Volume III - Price Proposal
7.0 Volume V - Contract Documentation

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