SF30 - Amendment 0003

141 KB Posted

Attached to
Remotely Piloted Aircraft (RPA) Federal contract opportunity
Solicitation number
FA4890-10-R-0009
Issued by
Department of the Air Force Air Combat Command

About this file

SF30 - Amendment 0003 (1May12)

Text of this file

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

Paragraph L-8.1 has been changed to add a requirement for an authorization letter.

Paragraph L-8.11 provides the requirement for w ritten authorization for the Government to contact the prime contractor w hen an offeror submits past performance references as a subcontractor.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 11

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

16C. DATE SIGNED

BY 01-May-2012

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 FA4890-10-R-0009

X 9B. DATED (SEE ITEM 11)

14-Mar-2012

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 1 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

01-May-2012

CODE

ACC AMIC/PKC

11817 CANON BLVD, SUITE 306

NEWPORT NEWS VA 23606-4516

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

FA4890-10-R-0009

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been added by full text:

INSTRUCTIONS TO OFFERORS

L-1 SPECIAL NOTICE TO OFFERORS

L-1.1 The exclusive responsibility for Source Selection will reside with the Government. Each individual involved in this acquisition will execute a Non-Disclosure Agreement with ACC AMIC prior to having access to any proposals.

L-1.2 Proprietary information submitted in response to this solicitation shall be clearly marked as such and will be protected from unauthorized disclosure as required by Subsection 27 of the Office of Procurement Policy Act as amended (41 U.S.C.423) (hereinafter referred to as “the Act”) as implemented in the FAR. Any unmarked proprietary information will be considered releasable under the restrictions of the Freedom of Information Act.

L-2 FORMAL COMMUNICATIONS, BIDDERS’ LIBRARY, PRE-PROPOSAL CONFERENCE

L-2.1 Any formal communication such as requests for clarification, discussions, and information concerning this solicitation shall be submitted in writing to the Contracting Officer (CO) and Contract Manager (CM) at the email address below:

ACC AMIC/PKC

ATTN: Ms. Sharon Potter or Ms. Donna Rankin

Reference: Solicitation No. FA4890-10-R-0009, RPA

E-mail: RPARecomp@langley.af.mil

L-2.2 Access To Bidders’ Library

L-2.2.1 None of the forms, regulations, manuals, Technical Orders, or other publications referenced in the solicitation will be issued with the solicitation. Documents cited within PWS, Appendix C – Publications and

Forms, annotated as being available electronically, with the exception of documents labeled "For Official Use Only

(FOUO)" or "Communications Security (COMSEC)" in the title or publication description, are available via public domain at http://www.e-publishing.af.mil/. Documents cited as FOUO or COMSEC as well as other documents (i.e.

manuals, workload data), will be made available in the bidder's library at the location listed below. The library is available by appointment only from 29 August 2011 through the proposal closing date. E-mail the CO and CM at

RPARecomp@langley.af.mil at least five (5) business days in advance to arrange access. Title the e-mail “Bidders

Library Appointment – Company Name” (example: “Bidders Library Appointment – ABC Company”). Offerors will not be allowed to remove any documents from this area that are labeled FOUO or COMSEC. Hours of availability will be determined at the time of request. One computer will be available in the Bidders’ Library. Only one offeror with no more than two (2) representatives per offeror may use the library at any given time. The

Bidders’ Library will be located at ACC AMIC (11817 Canon Blvd, SunTrust Bank Building, 5th Floor, DRF, Suite

510, Newport News, VA 23606.

L-2.3 Pre-Proposal Conference

L-2.3.1 A pre-proposal conference will be held on 28 March 2012, at ACC AMIC (11817 Canon Blvd, SunTrust

Bank Building - 3rd Floor Conference Room, Newport News, VA 23606) to explain the requirements of this solicitation and to respond to questions raised by offerors. As space is limited, we request that you limit the number of individuals attending to a maximum of two (2) per company. To arrange attendance, send an email to the CO and

CM at RPARecomp@langley.af.mil no later than 23 March 2012. Title the e-mail "Pre-Proposal Conference -

Company Name" (example "Pre-Proposal Conference - ABC Company").

L-2.3.2 Offerors are requested to submit questions regarding the solicitation in writing via e-mail to the CO or CM as identified in Block 10 of the SF 33 and paragraph L-3, by 23 March 2012 to allow their inclusion in the agenda.

Questions will be considered at any time prior to or during the conference, however, official answers will be provided to written questions only.

L-2.3.3 The Government will not be liable for expenses incurred by offerors prior to contract award.

L-3 SUBMISSION OF PROPOSALS

L-3.1 The original and copies (specified below) shall be sent or hand delivered to the issuing office listed in Block 7 of the Standard Form 33 on or before the date/time specified on the front page. Mark the front of the envelope/box with the following: “Proposal No. FA4890-10-R-0009, ATTN: Sharon Potter/Donna Rankin, ACC AMIC/PKC, "DO NOT OPEN IN MAIL ROOM." If proposals are hand delivered, offerors shall contact the CO or CM via the email listed above to schedule delivery. Offerors are cautioned to strictly comply with all instructions within this solicitation to ensure submission of a complete proposal. All Offeror and team member/subcontractor information must be incorporated into one coherent proposal to be considered complete. Failure to furnish a complete proposal at the time of proposal submission may result in an unacceptable proposal that the Government eliminates from consideration for award. The Government will not accept any changes to offerors’ proposals after the closing date of this solicitation (see FAR 15.208 for further information regarding late proposals).

L-3.2 Proposals in response to this solicitation will be valid for 275 calendar days. Block 12 of Standard Form 33 is completed to read 275 calendar days.

L-3.3 Contact Information. Offeror shall provide:

L-3.3.1 Names, titles, addresses, telephone and facsimile numbers, and email addresses of persons authorized to negotiate on the offeror’s behalf with the Government in connection with this solicitation.

L-3.3.2 Name, title, and signature of person authorized to sign the proposal. Proposals signed by an agent shall be accompanied by evidence of that agent’s authority, unless that evidence has been previously furnished to the issuing office.

L-4 DISPOSITION OF UNSUCCESSFUL PROPOSALS

L-4.1 In compliance with FAR Subpart 4.8, the Government will retain one copy of all unsuccessful proposals.

Extra copies of unsuccessful proposals will be destroyed. No destruction certificate will be provided.

L-5 PROPOSAL PREPARATION INSTRUCTIONS. A complete proposal consists of three (3) separate volumes:

Volume I - Technical, Volume II - Past Performance, and Volume III - Price.

L-5.1 The instructions below prescribe the format of proposals. Proposals shall include all of the information requested in the specific instructions. Failure to include all information requested may adversely affect the evaluation.

L-5.2 A proposal that is orderly and sufficiently documented will enable the Government to easily understand and perform a thorough and fair evaluation. The Government may incorporate into this contract, by reference or full text, portions of the successful offeror’s proposal submitted in response to this solicitation as revised and supplemented through the final proposal revision.

L-5.3 Proposal Format.

L-5.3.1 Page Format. The proposal text shall be printed single-sided versus duplex. Type size for text shall not be smaller than Microsoft Word Times New Roman 12 point font, single column, normal proportional spacing and one inch (1”) margins (top, bottom, left and right). The text for charts, tables, graphs, and figures shall be no smaller than Microsoft Word, Times New Roman or Arial Narrow, 8 point font, and used only when absolutely necessary.

Text lines and table lines of text shall be single-spaced. Page color for each page of the original proposal submission shall be white or ivory.

L-5.3.2 Electronic Copies. Electronic copies of all proposal information for each volume shall be submitted on a

CD-ROM or CD-R using Microsoft Office 2003, Microsoft Office 2007 or Portable Document Format (PDF) using

Acrobat Adobe 9.0. Offerors shall NOT submit any documents in PDF that cannot be electronically searched.

Offerors may use JPEG images for charts or screen shots. Volume III IDIQ price matrix located in Section B, attachment Table B - Pricing Table, and Task Order pricing, shall be submitted in Microsoft Excel 2003 or 2007.

Offerors shall name files in an unambiguous manner, using plain language text, which facilitates the evaluator’s ease of accessing the files for evaluation, using standard naming conventions (e.g., offeror name-volume name). Each volume shall be in a single searchable file, with copy/paste capability, and stored in a folder that corresponds to the proposal volume it represents. Offerors shall insert the file name in the header of each document. All disks shall be virus checked prior to submission. Replacement disks (CD ROM/CD-R) shall be required to update the final proposal resulting from any discussions, should they occur. It is the Offeror's responsibility to ensure that electronic copies and hard copies are an exact match. If there is a discrepancy between electronic copies and hard copies referenced in L-5.3.3 below, the hard copy submission will be used to conduct evaluations.

L-5.3.3 Organization/Copies/Page Limit. Information submitted shall not exceed the page limits stated below for each volume. Evaluators will only read up to the maximum number of pages specified. If the page limit is exceeded, the pages in excess of the limit will be removed from the applicable volume and will not be considered as part of the evaluation. Copy requirements, page limitations and submission dates are as follows:

HARD CD-ROM PAGE CLOSING DATE AS

VOLUMES: COPIES CD-R LIMIT OF 12 NOON, EDT

I – Technical Original + 5 1 100 pages 27 Apr 2012

Part A – IDIQ Subfactors

Part B – Task Order Subfactors

II – Past Performance Original + 4 1/See L-8.1 See L-8 12 Apr 2012

III – Price (See Note) Original + 3 1 None 27 Apr 2012

Part A – IDIQ Price Matrix

Part B – Task Order Pricing

Part C – Proposal Documentation

NOTE: One original proposal, which includes a signature on the SF33 in Volume III Part C, shall be submitted.

The remaining copies, plus original, shall be submitted in accordance with the instructions provided in Section L-3 for evaluation.

L-5.3.4 Cross-Referencing. Offerors shall not cross reference between Volumes I, II, and III. Each Volume shall be written on a stand alone basis so that its contents may be evaluated without cross-referencing to other Volumes of the proposal. Information required for proposal evaluation, which is not found in its designated Volume, will be assumed to have been omitted from the proposal.

L-5.3.5 What Counts as a Page. A page shall be an 8 1/2” x 11” sheet of paper. Fold-outs shall not exceed (11” x

17”), and shall count as two pages. All material shall be contained within the page limit identified for each volume, and all appendices, charts, graphs, diagrams, tables, photographs, drawings, etc., are included in the page count, with exception of items stated in L-5.3.6.

L-5.3.6 Pages Not Included in Page Count. Organizational charts, acronym list, cross-reference matrix, manning matrix, and overview section (for exceptions) will not be included in the page count. Covers for volumes, tables of contents, indices, title pages, and section dividers/tables will not be included in the page count if they are inserted solely to provide ease to the reader in locating parts/sections of the proposal. They will be counted if they contain any other information, e.g., diagrams, extraneous data, etc. Pages marked “This page intentionally left blank” will not be counted.

L-6 EXCEPTIONS. The Government reserves the right to award without discussions; therefore, offerors are advised that taking exception to any requirements specified in this solicitation may result in the Government finding the proposal unacceptable. Clarification of Government requirements shall be handled by submitting questions/recommendations prior to submission of proposals. If offerors still find it necessary to take exception to any of the requirements specified in this solicitation (Sections A through M, to include the PWS and attachments), clearly identify each exception in the overview section of the appropriate volume along with a complete explanation of why the exception was taken and the resulting benefit to the Government. Exception to solicitation requirements may require the Government to amend the solicitation to reflect a changed requirement. The Government will consider the absence of a stated exception to mean the offeror takes no exception to the solicitation and the proposal will be evaluated as submitted.

L-7 INSTRUCTIONS FOR VOLUME I, TECHNICAL (FACTOR 1)

L-7.1 To facilitate evaluation, the Technical Volume shall be specific, detailed, and complete to clearly and fully demonstrate that offerors have a thorough understanding of RPA requirements. Statements that offerors understand, can, or will comply with the PWS (including referenced AF publications, etc.); statements paraphrasing the PWS or parts thereof (including applicable AF publications, etc.); and phrases such as “standard procedures will be employed” or “well known techniques will be used,” etc., will be considered “Unacceptable”. Offerors should note that data submitted prior to the proposal submission will not be considered in the Government’s evaluation;

therefore, such data should not be relied upon or incorporated in the Technical proposal by reference.

L-7.2 Cross-Reference Matrix (Attachment 4). As part of offerors’ proposals, a separate cross-reference matrix shall be completed and submitted with Volume I - Technical. See Attachment 4 for the format. All referenced paragraphs include all subsequent subparagraphs (for example, 5.0 includes 5.1, 5.2, 5.2.1, etc.). This is only a tool to assist in the proposal preparation process. Offerors are ultimately responsible for ensuring that their proposal fully addresses all areas and that all requested information is completed in accordance with Sections L and M of this solicitation. Offerors shall complete the last column of Attachment 4 with paragraph number references from their

Technical Volume. Offerors may provide additional references to the other columns as deemed necessary.

L-7.3 Acronym List. An acronym list shall be provided as an attachment within the Technical Volume.

L-7.4 Technical Factor. The purpose of this section is to set forth, in the most comprehensive manner, the Offerors' understanding of the program requirements and to demonstrate their ability to meet the evaluation requirements of

Section M, Factor 1, Technical. This section shall present a clear, concise description of how Offerors plan to meet award requirements. This section shall not contain any pricing data.

L-7.4.1 Part A - IDIQ Subfactors

L-7.4.1.1 Subfactor A: Program Management.

L-7.4.1.1.1 Aspect I: Management and Integration. Provide an organizational structure and explanation of the proposed program management approach to meet PWS requirements. At a minimum:

• Identify and explain all resources required to successfully accomplish program requirements

• Identify management hierarchy responsible for program management, operations and maintenance, deployments, training and explain their responsibilities

• Include labor categories, skill level, and number of personnel required to support various RPA mission requirements consistent with the following manning matrices:

• Single deployed location supporting one stand alone Combat Air Patrol (CAP) and up to 12 collocated CAPs (IAW Appendices N and O):

Deployed RPA Manning Matrix

Stand Alone Stand Alone

Labor Special Certs Shift Stand Alone Plus 1 THRU Plus 12

Category (PWS 3.7) CAP CAP CAP

Labor Cat 1

Labor Cat 2

Labor Cat 3

Labor Cat ##

Total

• Five (5) Reachback locations (IAW Appendices N and O):

Reachback RPA Manning Matrix

Labor Category Special Certs (PWS 3.7) Eur-1A Eur-1B Eur-2 PAC-1 PAC-2

Labor Cat 1

Labor Cat 2

Labor Cat 3

• CONUS locations (IAW Appendices N and O):

CONUS RPA Manning Matrix

Labor Category Special Certs (PWS 3.7) Shift Creech Nellis (See PWS APP N for all site locations)

Labor Cat 1

Labor Cat 2

Labor Cat 3

L-7.4.1.1.2 Aspect II: Human Resources. Describe your process to ensure personnel are qualified, trained and certified. At a minimum provide an outline of on-going / cyclical process for conducting initial training and maintaining training currency and certifications.

L-7.4.1.1.3 Aspect III: Quality Management System (QMS). Describe your QMS controls to successfully accomplish PWS requirements. At a minimum address:

• Provide current International Organizational for Standardization (ISO) 9001:2008, AS9100:2008, AS9110:2008, or AS9120:2008 registration certificate for offeror or for at least one entity in the offeror’s contractor teaming arrangement as defined in FAR 9.6

• Number and distribution of quality control personnel across the RPA Program

• Methods to enforce compliance with technical data

• Deficiency Resolution procedures

• Continual Process Improvement procedures

L-7.4.1.2 Subfactor B: Operations and Maintenance.

L-7.4.1.2.1 Aspect I: RPA Organizational-Level Maintenance. Describe your process to ensure an effective and efficient organizational-level RPA weapons systems and equipment maintenance program. At a minimum address procedures for:

• Scheduled and Unscheduled Maintenance

• Weapons buildup and loading

• Maintenance Documentation

L-7.4.1.2.2. Aspect II: Reachback Facilities. Identify and explain your process to ensure an effective organizational-level C4ISR equipment maintenance program. At a minimum address procedures for:

• Maintenance

• Troubleshooting

• Repair

• Modifications

• Documentation

L-7.4.1.2.3 Aspect III: Property Control and Accountability. Describe your process to ensure an effective property control and accountability program. At a minimum, address procedures to account for, maintain, and control government furnished property from receipt to proper disposition.

L-7.4.2 Part B - Task Order Subfactors. (See Section L, Attachment 6 - Technical Task Order Requirements)

L-7.4.2.1 Subfactor A: Manning. (applies to Technical Task Order 2 – Combined CONUS Sites, Technical Task

Order 3 – Combined Deployed Sites and Technical Task Order 4 - Reachback Site) Identify manning levels for each location contained in each task order based on your Part A proposal. At a minimum address:

• Two week shift schedule for CONUS and OCONUS locations providing labor categories, skill level and total manning required for each task order

• Any deviations to the technical solutions provided in Part A; include justification and support based on unique task order requirement(s)

L-7.4.2.2 Subfactor B: Deployment process. (applies to Technical Task Order 3 – Combined Deployed Sites)

Describe your process for supporting deployed locations to ensure uninterrupted mission support. At a minimum, address:

• A timeline that depicts all completed training and certifications required to support on site performance not later than 45 days after issuance of task order

• Maintaining manning levels through personnel rotations

L-7.4.2.3 Subfactor C: Transition. (applies to Technical Task Order 1 – Transition) Provide your executable transition plan for all CONUS, OCONUS and Reachback task order locations. At a minimum:

• Identify and explain key transition/phase-in period milestones

• Identify personnel required for interfacing with the incumbent contractor at each location

• Provide your plan for transitioning/phasing-in all existing work (e.g. open maintenance and requisition actions) from the incumbent at each site to ensure uninterrupted mission support and execution

• Provide your plan to hire, train and certify new personnel in the event you are not able to meet hiring goals of trained and certified incumbent personnel

L-8 INSTRUCTIONS FOR VOLUME II, PAST PERFORMANCE (FACTOR 2)

L-8.1 Contents. Offerors shall submit a Past Performance Volume containing the following:

1. Table of Contents: Not to exceed one (1) page

2. Past Performance Summary: Not to exceed two (2) pages, See paragraph L-8.2

3. Past Performance Information (PPI) Contract Reference Sheet: Contents of PPI Reference Sheet is limited to five (5) pages. See paragraph L-8.3 and Section L, Attachment 1

4. Subcontractor/Teaming Partner Consent Letter: See paragraph L-8.6

5. Organization Structure Change History: Not to exceed two (2) pages (bullet format, narrative not required). See paragraph L-8.7

6. Authorization Letter: Not to exceed one (1) page. See paragraph L-8.11.

L-8.2 Summary. Describe roles of offerors and all subcontractors, teaming partners, or joint venture partners.

Provide a detailed matrix that depicts how each PPI contract reference provided meets the criteria (#1 though #5) defined at M-3.3.3. Also include an explanation of how the combination of PPI contract references provided meet the relevancy criteria defined at M-.3.3.3.

L-8.3 PPI Contract Reference Sheet (Attachment 1). Offerors shall submit information on contracts considered most relevant in demonstrating the ability to perform RPA Operations and Maintenance services. This information is required on offerors, subcontractors, teaming partners, or joint venture partners considered critical to overall successful performance. The offeror shall submit a minimum of two (2) and maximum of five (5) contract references. The offeror shall also submit a minimum of two (2) and maximum of five (5) contract references for each teaming partner, joint venture partner, major or critical subcontractor. Offeror shall provide a separate PPI

Sheet (Attachment 1) for each contract reference identifying active (minimum of 12 months performance) or completed contracts, either Government or commercial.

L-8.4 Recency Determination. Each PPI contract reference shall have active work/services (minimum of 12 months performance) that was/were performed during the last three (3) years from the final solicitation release date. This includes contracts that were awarded prior to this period, but still had active performance (minimum of 12 months) during the last three years.

L-8.5 Relevant Contracts. Offerors shall submit information on contracts deemed relevant in demonstrating the ability to perform the full range of RPA capabilities IAW PWS requirements, and explain how/why the referenced contracts are relevant IAW paragraph M-3.3.3. Relevancy shall be detailed in the PPI Contract Reference Sheet

(Attachment 1).

L-8.6 Subcontractor/Teaming Partner Consent Letter (Attachment 2). PPI contract reference concerning subcontractor and teaming partners cannot be disclosed to a private party without the subcontractor’s or teaming partner’s consent. Because a prime contractor is a private party, the Government will need that consent before disclosing subcontractor/teaming partner PPI contract reference to the Prime during exchanges. These letters are only required for subcontractors and teaming/joint venture partners for which the Prime submits past performance information as part of the Past Performance Volume. Completed consent forms shall be submitted as part of the

Past Performance Volume.

L-8.7 Organizational Structure Change History. Many companies have acquired, have been acquired by, or have 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 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 the Government’s past performance evaluation, offerors shall include in this proposal volume a detailed "roadmap" describing all such organizational changes (if applicable), to include specific names and dates.

L-8.8 Past Performance Questionnaires (PPQ) (Attachment 3). The Government will use the attached PPQ as a tool for conducting Past Performance telephonic or email interviews. The PPQ is provided as a point of information to offerors and is for Government use only. In the event a PPQ is used, it will be treated as source selection information in accordance with FAR Part 3.104. Offerors shall not complete and submit the PPQ. Any PPQs submitted by offerors will not be considered as part of the evaluation.

L-8.9 Other Sources. The Government may utilize references other than those identified by offerors in evaluation of the offerors’ Past Performance. While the Government may elect to consider data obtained from other sources, the burden of providing accurate and complete, recent and relevant PPI contract references that demonstrates the ability to perform this requirement rests with each offeror.

L-8.10 Determination of Responsibility. Even though the assessment of Past Performance is separate and distinct from Determination of Responsibility required by FAR Part 9, PPI contract references contained herein may be used to support the Determination of Responsibility for successful offerors.

L-8.11 Authorization Letter. In order to validate an offeror's past performance as a subcontractor on PPI contract references, offerors are required to provide written authorization for the Government to contact the prime contractor.

L-9 INSTRUCTIONS FOR VOLUME III, PRICE (FACTOR 3)

L-9.1 Part A – IDIQ Price Matrix

L-9.1.1 IDIQ Price Matrix. Offerors shall provide pricing per RFP Section B and format consistent with Section B, Attachment Table B - Pricing Table. The burden of providing mathematically accurate and complete pricing proposals using a format consistent with Section B, Attachment Table B - Pricing Table rests with each offeror and shall reflect the manning requirements/labor categories contained in the manning matrix (format provided in L-

7.4.1.1.1) submitted with Volume I - Technical (Factor 1) Part A.

L-9.1.2 Labor Rates. Offerors shall provide fully loaded labor rates for CONUS and OCONUS locations in the

IDIQ price matrix located in Section B, Attachment Table B - Pricing Table and will be incorporated into the contract. Proposed fully loaded labor rates will be used to price task order requirements at contract award and serve as the ceiling rate for additional task orders throughout the life of this contract. Pricing table for CONUS locations will serve as the baseline for negotiations for adding sites that were not included in the price matrix at contract award. Identify each labor category, to include subcontracted personnel, as exempt or non-exempt, and if classified as a Service Contract Act (SCA) position. Proposed labor category titles must be cross referenced to the SCA

Directory of Occupations 5th Edition, where applicable. Labor rates identified as SCA will be adjusted IAW FAR

52.222-43.

L-9.1.3 Supporting Price Backup Data. Certified cost or pricing data is not required; however, supporting data is requested. Supporting data should explain the methodology used in developing proposed labor rates. Supporting data may be submitted in a format selected by the offeror.

L-9.2 Part B – Task Order Pricing

L-9.2.1 Submit complete and accurate price proposals for the Task Order requirements. Labor categories and rates shall be based on the prices contained in the IDIQ price matrix located in Part A, Section B, attachment Table B -

Pricing Table. Adjustments to the manpower requirements identified in the manning matrix provided in Volume I, Part A are permitted but shall be justified based on your technical solution for the unique task order requirements in

Volume I, Part B and must be clearly identified in the proposed price. Offerors shall submit proposed cost estimates and rationale for travel, Defense Base Act (DBA) insurance, and Department of State Standardized Rates for differential pay required to support the Task Order requirements to include any applicable indirect rates. This information will be used to assess whether prices proposed are fair and reasonable for the work to be performed, and are consistent with the offeror’s proposed technical approach.

L-9.2.2 Supporting Price Backup Data. Certified cost or pricing data is not required; however, supporting data is requested. Supporting data should explain the methodology used in developing proposed labor rates. Supporting data may be submitted in a format selected by the offeror.

L-9.3 Part C – Proposal Documentation. Provide the following:

L-9.3.1 Offeror’s response to the solicitation Sections A through K as follows:

L-9.3.1.1 Section A. Complete in its entirety the “Offeror” portion of the SF 33; an official having the authority to bind your company contractually must sign the SF 33 IAW FAR 4.102. In doing so, the offeror accedes to the contract terms and conditions as written in the RFP Sections A through K. These sections constitute the model contract. One copy of the SF 33 must bear an original signature.

L-9.3.1.2 Sections C through K. Complete the necessary fill-ins and certifications, and provide any information requested in Sections C through K. For Sections C through I, the offeror shall submit only those pages that require a fill-in. For Section K: complete Section K, Representations, Certifications and Other Statements of Offerors, or provide a copy of completed Online Representations and Certifications (ORCA) located at https://orca.bpn.gov.

L-9.3.1.3 Amendments. Offerors shall acknowledge any and all amendments per the directions on the amendment cover page (Standard Form 30). Failure to acknowledge any amendments to the solicitation may result in the offeror being deemed nonresponsive. Award CANNOT be made to a nonresponsive offeror.

L-9.3.1.4 Description of any exceptions and deviations to the RFP even if noted in any other volume. See paragraph L-6.

L-9.3.1.5 Information Other Than Cost or Pricing Data. Offeror shall identify the cognizant Defense Contract

Audit Agency (DCAA) and Defense Contract Management Agency (DCMA) field offices that have oversight to the offeror’s organization. Provide information concerning the adequacy of your accounting system pertaining to accumulation of costs for the cost reimbursable CLINs. If DCAA has already determined the offeror’s accounting system adequate, the offeror shall provide the referenced DCAA audit report number and report date. In addition, provide the most recent review date of your estimating system and identify any deficiencies identified by DCAA and the resolution of the deficiencies. If an offeror has never dealt with DCAA, offerors shall review the website at www.dcaa.mil and identify the cognizant DCAA office. Offerors shall also provide any information that pertains to a recent DCMA or DCAA financial capability assessment. Offeror shall provide evidence of indirect rates and factors used in the price schedule have been audited/approved by DCAA/DCMA.

L-9.3.1.5.1 Provide your previous three (3) fiscal year-end financial statements for use in the Government determining the apparent low offeror's responsibility IAW FAR 9.104-1. Also include documentation to show capability to access credit markets if necessary.

L-9.3.1.5.2 Supplemental Responsibility Determination IAW FAR Part 9 - DoD Contract Security Classification

Specification (DD Form 254).

L-9.3.1.5.2.1 Offeror shall provide information from DD Form 254, items 6a through 6c for offeror and 7a through

7c for each subcontractor, with proposal submission.

L-9.3.1.5.2.2 Facility Clearance. The offeror, and subcontractors as required, must possess or acquire prior to

Source Selection Authority Decision Brief, a facility clearance equal to the highest classification specified on the

DD Form 254 attached to this solicitation and be entitled to COMSEC information without additional authorization

(i.e. National Interest Determination (NID)). Therefore, all facility clearances must be approved and Foreign

Ownership Control or Influence (FOCI) issues in accordance with DoD 5220.22-M, must be mitigated prior to the

Source Selection Authority Decision Brief.

L-9.3.1.5.2.3 Subcontracting Classified COMSEC Work. If the offeror plans to subcontract COMSEC work to a subcontractor, they must comply with NISPOM 9-407, Subcontracting COMSEC Work, which states “Subcontracts requiring the disclosure of classified COMSEC information shall be awarded only upon the written approval of the

Government Contracting Activity (GCA).” Offeror's request for authorization to subcontract classified COMSEC work shall be included in the proposal.

L-9.3.1.6 Small Business Subcontracting Plan (Required from large businesses only). Provide a Subcontracting

Plan that complies with FAR Part 19, Small Business Programs, and its supplements. Identify the percentage of intended business with each of the following small business socioeconomic categories: Veteran-Owned Small

Business, Service-Disabled Veteran-Owned Small Business, HUB-Zone Small Business, Small Disadvantaged

Business (to include subcontracts with historically black colleges and universities and minority institutions), and

Women-Owned Small Business. Pursuant to AFFARS 5319.704, all small business subcontracting goals shall be expressed in terms of percent of contract value at the IDIQ contract level, in addition to percent of subcontracted amount. Each offeror shall complete and submit the Small Business Subcontracting Plan Checklist (Attachment 5) with the plan. Per FAR 19.702(a)(1), if the apparently successful offeror fails to negotiate a subcontracting plan acceptable to the CO within the time limit prescribed by the CO, the offeror will be ineligible for award. Reference minimum requirements at M-3.4.4.2.

L-9.3.1.7 Department of Labor Equal Employment Opportunity (EEO) Clearance. In accordance with FAR Part

22.805, the CO must request pre-award clearance on Prime contractors or Teaming Partners (not subcontractors) from the appropriate Office of Federal Contract Compliance Programs (OFCCP) regional office. If an offeror is listed in OFCCP’s National Pre-award Registry (http://www.dol-esa.gov/preaward/pa_reg.html), offerors shall provide the CO a copy of the database registration for Government verification as part of the proposal submission. If an offeror is not listed in the registry, the CO will request an EEO clearance review.

L-10 DEBRIEFING OF OFFERORS. Successful or unsuccessful offerors may request debriefings by providing a written request to the Procuring CO. Debriefings shall be conducted in accordance with FAR 15.505 for pre-award debriefings and FAR 15.506 for post-award debriefings.

L-11 CHANGES RESULTING FROM DISCUSSIONS. In the event any adjustment of price becomes necessary to reflect changes made to technical proposals resulting from discussions, if discussions are held, a complete traceable trail shall be provided to show how the changes took place.

The following have been deleted:

INSTRUCTIONS TO OFFERORS

(End of Summary of Changes)

Other files for this federal contract opportunity

Other files attached to Remotely Piloted Aircraft (RPA), newest first.
File Type Posted
SF30 - Amendment 0006 —
RPA RFP - Amendment 0005 —
Section L Atch 6 Tech TO Rqmts —
SF 30 - Amendment 0004 —
RPA PWS —
Appendix D-Publications Forms and Websites —
WD 2005-2485 rev 11 - Ellsworth.pdf PDF
Appendix I-Special Requirements for Deployment —
RPA RFP - Amendment 0003 —
SF30 - Amendment 0002 —
App D-Publications Forms and Websites —
Section L Atch 6 Tech TO Rqmts —
Notice to Potential Offerors —
Section B Table B-Pricing Tables —
L Atch 6 Tech TO Rqmts —
App G-Incentive and Award Fee Plan —
SF 30 - Amendment 0001 —
Notice to Potential Offerors —
RPA Pre-Proposal Attendance Roster.pdf PDF
L Atch 4 Cross Ref Matrix —
Appendix D-Publications Forms and Websites —
Appendix I-Special Rqmts for Deployment —
Appendix M-Certs Training and Qualifications —
WD 2005-2331 Rev 11 - Creech.Nellis.pdf PDF
WD 2005-2307 Rev 12 - Whiteman.pdf PDF
RPA PWS —
CDRL A002 —
CDRL A003 —
Appendix G-Incentive and Award Fee Plan —
Appendix H-RPA Service Summary —
FA4890-10-R-0009 —
L Atch 1 PPI —
RPA Government Responses to Industry Questions —
Draft RPA RFP Section B —
RPA Government Responses to Industry Questions —
RPA Creech Site Visit Attendance Roster.pdf PDF
DRAFT - Appendix I - Special Requirements for Deployment Support.pdf PDF
DRAFT - Appendix C - AFI 21-101_201_200 Compliance Matrix.xls XLS spreadsheet
DRAFT - CDRL A001 - Property Plan-RPA.pdf PDF
DRAFT - CDRL A005 - Safety and Health Plan-RPA.pdf PDF
DRAFT - Appendix K -C4ISR Demarcation Points.pdf PDF
RPA Site Visit Registration Update 12 July 2011.docx DOCX document
DRAFT - RPA Section B.pdf PDF
RPA Site Visit Announcement.docx DOCX document
DRAFT - Appendix K - C4ISR Demarcation Points —
DRAFT - Appendix N - Operational Requirements —
DRAFT - Appendix F - Quality Management Systems —
Potential offerors.docx DOCX document
DRAFT - Appendix M - Certifications Training and Qualifications —
DRAFT - CDRL A001 - Property Plan-RPA —
Show all 50

Remotely Piloted Aircraft (RPA) has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

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