DRAFT - RPA Sections L M.pdf

FA4890-10-R-0009

RPA DRAFT Sections L&M

52.216-1 Type of Contract. The Government contemplates award of a Indefinite Delivery Indefinite Quantity

(IDIQ) contract resulting from this solicitation.

L-1 SPECIAL NOTICE TO OFFERORS

L-1.1 Harris IT Services, Inc. will provide software and hardware support during the proposal evaluation process.

The exclusive responsibility for Source Selection will reside with the Government. Any objection shall be provided in writing to the Contracting Officer (CO) no later than XX XXX 2011 and shall include a detailed statement of the basis for objection. Harris IT Services, Inc. is bound contractually by Organizational Conflict of Interest and

Disclosure clauses with respect to proprietary information. Each individual involved in this acquisition has executed a Non-Disclosure Agreement with ACC AMIC.

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/SITE VISIT

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

ACC AMIC/PKC

ATTN: Ms. Sharon Potter or Ms. Donna Rankin

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

Phone: 757-764-9371

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 "Computer 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 will be available by appointment only from XX XXX 2011 through the proposal closing date. E-mail the ACC AMIC

CO and ACC AMIC Contract Manager 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 XX XXX 2011, 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). To arrange attendance, send an email to the ACC AMIC CO and

ACC AMIC Contract Manager at RPARecomp@langley.af.mil no later than XX XXX 2011. 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

Contract Manager, as identified in Block 10 of the SF 33 and paragraph L-3, by XX XXX 2011 to allow their

RPA DRAFT Sections L&M 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 submittal 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 300 calendar days. Block 12 of Standard Form 33, is completed to read 300 calendar days.

L-3.3 Contact Information. Offeror shall provide:

L-3.3.1 Names, titles, addresses, telephone and facsimile numbers, 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

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. A complete proposal consists of five (5) separate volumes submitted in two phases. Phase

I submittals consist of: Volume I - Technical , Volume II - Past Performance, and Volume III - Price; Phase II submittals consists of: Volume IV - Task Order Technical and Volume V - Task Order Price.

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

RPA DRAFT Sections L&M submission shall be white or ivory. This does not apply to the Past Performance Information (PPI) data entered in the PPI tool, as described in paragraph L-8.1.2.

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 are copied as images. Offerors may use

JPEG images for charts or screen shots. See paragraph L-8.1.2.3 regarding electronic copies of Past Performance

Information Sheets. Volume III Cost/Price – Contract Level Price Matrix located in Section B, Table B, Pricing

Table, and Volume V, 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 and page limitations are as follows:

PHASE I, HARD CD-ROM PAGE CLOSING DATE AS

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

I – Technical Original + 5 1 75 pages 7 Nov 2011

II – Past Performance Original + 4 1 / See L-8.1.2 See L-8 7 Nov 2011

III – Price (See Note) Original + 3 1 None 7 Nov 2011

PHASE II, HARD CD-ROM/ PAGE CLOSING DATE AS

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

IV – Task Order Original + 5 1 To Be Announced To Be Announced

Technical

V – Task Order Original + 3 1 None To Be Announced

Price

NOTE: One original proposal, which includes a signature on the SF33 in Volume III, 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

L-5.3.4.1 No Cross-Referencing in Phase I. Offerors shall not cross reference between Volumes I, II, and III. Each

Volume in Phase I 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 in Phase I, which is not found in its designated Volume, will be assumed to have been omitted from the proposal. Each response to each subfactor shall be self-contained. No cross-referencing between subfactor responses is permitted.

L-5.3.4.2 Cross-Referencing in Phase II. Offerors are permitted to cross reference information from Volume I into

Volume IV. Offerors are permitted to cross reference information from Volume III into Volume V. No other cross referencing is permitted.

L-5.3.5 What Counts as a Page. A page shall be a 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.

RPA DRAFT Sections L&M

L-5.3.6 Pages Not Included in Page Count. Organizational chart, 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 within 15 calendar days after final solicitation release date. 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 applicable volume and the proposal will be evaluated as submitted.

L-7 INSTRUCTIONS FOR PHASE I, 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 the Phase I, Volume I - Technical and with the Phase II, Volume IV - Task

Order/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. The purpose of this section is to set forth, in the most comprehensive manner, 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 Technical Subfactors

L-7.4.1.1 Subfactor A: Program Management

L-7.4.1.1.1 Aspect I: Management and Integration. Describe proposed manning levels and skill mix, and why it is adequate and sufficient to execute the program. Provide an organizational chart and staffing process/procedure necessary to ensure all needed personnel resources are provided to successfully accomplish program requirements.

Describe your process for supporting deployed requirements to include staffing, scheduling, and personnel deployment preparation. Identify responsibilities and functional relationships. Complete the manning matrix tab

RPA DRAFT Sections L&M located in Section B, Table B, Pricing Table. Include labor categories, skill level, and incremental number of personnel required to support RPA requirements. Labor category titles must be conformed to the Service Contract

Act (SCA) Directory of Occupations 5th Edition, where applicable. Describe your approach to create a quality culture to effectively integrate all aspects of the Quality Management System (QMS) into corporate management, maintenance, and routine business processes.

L-7.4.1.1.2 Aspect II: Human Resources. Describe your approach for providing initial training and maintaining training currency and certifications. Describe your approach for retaining qualified management and technical personnel. Identify your key positions, their minimum qualifications, certifications, and credentials. Describe why you selected these positions.

L-7.4.1.2 Subfactor B: Operations and Maintenance

L-7.4.1.2.1 Aspect I: Sortie and Support Requirements. Describe your approach for providing an effective and efficient organizational-level aircraft and equipment maintenance program; address scheduled and unscheduled maintenance, launch and recovery, aircraft weapons loading, configuration control, maintenance documentation, and associated flight line activities.

L-7.4.1.2.2 Aspect II: Munitions. Describe your approach for providing an effective munitions management and maintenance program that addresses inspection, storage, maintenance, buildup, delivery, and accountability of MQ-

1/MQ-9 munitions.

L-7.4.1.2.3. Aspect III: Reachback Facilities. Describe your approach for providing an effective and efficient organizational-level C4ISR equipment maintenance program; address scheduled and unscheduled maintenance, configuration control, maintenance documentation, and maintenance activities.

L-7.4.1.3 Subfactor C: Mission Support

L-7.4.1.3.1 Aspect I: Logistics. Describe your approach for providing responsive and effective supply and equipment management at all sites. Describe your approach for achieving prime mission equipment readiness, sustained mission support, and equipment and property accountability, maintainability and disposition.

L-8 INSTRUCTIONS FOR PHASE I, 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) Sheet: Content of Program Details Tab is limited to five (5) pages. See paragraph L-8.3 and Section L, Attachment 1, paragraph A.2

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

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

L-8. 3 PPI Sheet (Attachment 1).

L-8.3.1 Number of PPI References. Offerors shall submit information on contracts considered most relevant in demonstrating the ability to perform Remotely Piloted Aircraft 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 maximum of three (3) contract references, each with a

PPI Sheet identifying active or completed contracts, either Government or commercial, for each prime, teaming partner, or joint venture partner. The offeror shall also submit, for each major or critical subcontractor, a maximum of three (3) Past Performance contracts, each with a PPI Sheet. Each contract reference shall be submitted on a separate PPI Sheet (Attachment 1).

L-8.3.2 PPI Submission. Offerors shall submit their PPI Sheets using the past performance information tool, which offerors shall download from the RPA RFP posting to Federal Business Opportunities (FedBizOpps) at https://www.fbo.gov. Offerors shall provide hard copies of the pages generated from this tool as part of their Past

Performance Volume. Offerors shall save the PPI database file as offeror name-volume name (PPI).mdb (e.g., XYZ

Company-Past Performance Volume (PPI).mdb) to submit as part of the electronic copy of the Past Performance

Volume. Once complete, PPI sheets will be treated as source selection information in accordance with FAR Part

3.104. In accordance with FAR Part 15.305(a)(2)(iii), the Government will allow consideration of offeror-defined key personnel who have relevant experience, including current employees and new hires proposed, to be evaluated as part of Past Performance.

L-8.4 Recency Determination. Each contract shall have active work/services 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 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 RPA PWS requirements, and explain how/why the referenced contracts are relevant IAW paragraph M-3.3.3. As applicable, address how the proposed reference provided on each PPI relates to Technical Subfactors A, B and C in Phase I and in Phase II Task-Order/Technical

Subfactors B and C.

L-8.6 Subcontractor/Teaming Partner Consent Letter (Attachment 2). PPI 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 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 only utilize the attached PPQ if they are unable to validate and analyze past performance via any other means (ex. CPARs). In the event no past performance can be retrieved via PPIRS, the Government may 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 are not expected to complete and submit the PPQ. Any PPQs submitted by offerors will be ignored and 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 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 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 contained herein may be used to support the

Determination of Responsibility for successful offerors.

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

RPA DRAFT Sections L&M

L-9.1 Contract Level Price Matrix - Section B, Table B, Pricing Table. Offerors shall provide pricing per RFP

Section B, Pricing Table paragraph B-7 and format specified in Section B, Table B-1. The burden of providing mathematically accurate and complete pricing proposals using the format provided in Section B, Table B-1 rests with each offeror. Volume III, Pricing Schedule shall reflect the manning requirements/labor categories contained in the manning matrix submitted with Phase I, Volume I - Technical (Factor 1).

L-9.1.1 Labor Rates. Offerors shall provide loaded labor rates and associated cost elements for each labor category for CONUS and OCONUS locations in the contract level price matrix located in Section B, Table B, Pricing Table.

Proposed loaded labor rates will be the maximum allowable rates used to price Task Order requirements 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. Labor category titles must be conformed to the Service Contract

Act (SCA) Directory of Occupations 5th Edition, where applicable. Labor rates identified as SCA will be adjusted

IAW FAR 52.222-43.

L-9.2 Supporting Price Backup Data. Certified cost or pricing data is not required; however, supporting data is requested. This information will be used to assess whether prices proposed are logical for the work to be performed, and are supported by the offeror‟s proposed technical approach. 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 Any inconsistency, whether real or apparent between promised price and performance, shall be explained in the proposal. For example, if the intended use of new and innovative techniques is the basis for an abnormally low price, the nature of these techniques and their impact on the cost or price shall be explained. Any significant inconsistency, if unexplained, raises a fundamental issue of the offeror‟s understanding of the nature and scope of the work required and its financial ability to perform the contract, and may be grounds for exclusion from the competitive range. The burden of proof as to price credibility rests with the offeror.

L-9.4 Proposal Documentation. The following shall be provided in Phase I, Volume III, Price (Factor 3) in a separate section. It shall be completed as follows:

L-9.4.1 Offeror‟s response to the solicitation Sections A through K as follows:

L-9.4.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.4.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: provide requested information on accounting systems and EEOC; complete all required certifications and representations or indicate if information is contained in Online Representations and

Certifications (ORCA) located at https://orca.bpn.gov.

L-9.4.1.3 AMENDMENTS. Offerors are required to acknowledge any and all amendments per the directions on the amendment cover page (Standard Form 30). Failure to acknowledge any amendments to the solicitation results in the offeror being deemed nonresponsive. Award CANNOT be made to a nonresponsive offeror.

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

L-9.4.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 determinations of 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.

Also, document adequacy and compliance determinations relating to your Disclosure Statement. If an offeror has

RPA DRAFT Sections L&M never dealt with DCAA, offerors shall review the website at www.dcaa.mil and identify the cognizant DCAA office.

Provide supporting documentation of your adequate purchasing system (if applicable) which is in compliance with your Disclosure Statement. Offerors shall also provide any information that pertains to a recent DCMA or DCAA financial capability assessment.

L-9.4.1.5.1 Offerors shall provide an overview of their accounting system that demonstrates the system can adequately track, segregate, accumulate and report incurred costs for each CLIN, for government cost type contracts, as applicable. Include information regarding the general financial condition of your firm and specific plans for financing the proposed contract.

L-9.4.1.5.2 Since a portion of the contract requirements will be included on a cost reimbursable basis, provide a copy of your Disclosure Statement with the proposal, as well as identification of compliance with Cost Accounting

Standards (CAS), if applicable, and any CAS violations and subsequent corrections.

L-9.4.1.5.3 Offeror shall provide evidence indirect rates and factors used in the price schedule have been audited/approved by DCAA/DCMA.

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

L-9.4.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. All small business subcontracting goals shall be expressed in terms of percent of contract value. Pursuant to DFARS 215.305(a)(2), provide evidence to the extent to which the offeror‟s evaluated past performance demonstrates compliance with FAR 52.219-8, Utilization of Small Business

Concerns and FAR 52.219-9, Small Business Subcontracting 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.5.

L-9.4.1.7 Department of Labor Equal Employment Opportunity Clearance (EEOC). 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 EEOC review.

L-10 INSTRUCTIONS FOR PHASE II, VOLUME IV, TASK ORDER - TECHNICAL (FACTOR 4)

L-10.1 Paragraph L-7.1 applies to this section. Phase II, Volume IV – Task Order Technical proposals shall be consistent with Phase I, Volume I – Technical approach and as revised through discussions, if discussions are held.

L-10. 2 Subfactor A: Manning. Provide manning levels for each task order. Exceptions or deviations to the technical solutions provided in Phase I are permitted but shall be justified and supported based on the task order requirement. Provide a two-week work schedule for CONUS and OCONUS locations for each manning requirement/labor category for each task order.

L-10. 3 Subfactor B: Deployments. Describe your approach for providing aircraft and equipment organizational-level maintenance at OCONUS locations. Describe your process for deploying personnel to task order locations and effectively managing this process. Describe how you will sustain these operations through personnel rotations, schedules, and staffing to ensure uninterrupted mission support.

RPA DRAFT Sections L&M

L-10. 4 Subfactor C: Transition Plan. Provide a transition plan that will efficiently transition/phase-in resources and personnel at CONUS and OCONUS locations. At a minimum, address the following: key milestones that reflect how you will use the transition/phase-in period; and your plan for interfacing with the incumbent at each location to transition/phase-in all existing work (ex. open maintenance and requisition actions).

L-11 INSTRUCTIONS FOR PHASE II, VOLUME V, TASK ORDER – PRICE (FACTOR 5)

L-11.1 Submit complete and accurate price proposals for the Task Order requirements provided during Phase II.

Labor categories and rates shall be based on the prices contained in the contract level price matrix located in Section

B, Table B, Pricing Table submitted in Phase I and as revised through discussions, if discussions are held.

Exceptions or deviations to the manning matrix provided in Phase I are permitted but must be justified based on your technical solution for the task order requirements. Offerors are required to submit costs for travel, DBA insurance and Department of State differential pay amount required to support the task order requirements to include any applicable handling rates identified in the contract level price matrix located in Section B, Table B, Pricing

Table submitted in Phase I and as revised through discussions, if discussions are held.

L-11.2 Any inconsistency, whether real or apparent between promised price and performance, shall be explained in the proposal. For example, if the intended use of new and innovative techniques is the basis for an abnormally low price, the nature of these techniques and their impact on the cost or price shall be explained. Any significant inconsistency, if unexplained, raises a fundamental issue of the offeror‟s understanding of the nature and scope of the work required and its financial ability to perform the contract, and may be grounds for exclusion from the competitive range. The burden of proof as to price credibility rests with the offeror.

L-12 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-13 CHANGES RESULTING FROM DISCUSSIONS. In the event any adjustment of price becomes necessary to reflect changes resulting from discussions, if discussions are held, a complete traceable trail shall be provided to show how the changes took place.

RPA DRAFT Sections L&M

ATTACHMENT 1

SECTION L

PAST PERFORMANCE INFORMATION

Provide the information requested in this form for each contract/program being described. Provide frank, concise comments regarding your performance on the contracts you identify. Provide a separate completed form for each contract/program submitted. Limit the number of past efforts submitted and the length of each submission to the limitations set forth at paragraph L-8.1.2.

Past Performance Information Tool:

Step 1: Set up Business Relationships. Set up Prime and any company involved as subcontractor, teaming partner, joint venture partner, etc. as specified in the tool. Click New to enter information on the prime and any subcontractor(s), team partner(s) and/or joint venture partner(s). Select and delete any entries (samples) that do not pertain to the offeror. Percentage of work shall total 100% for all offeror business relationships.

Step 2: Enter Past Performance Information. Offerors shall download the tool provided as an attachment to the

RPA RFP on FedBizOpps and shall enter the information as instructed below (items in bold are fields requiring completion in the tool; to the right of/below each field title are instructions for that field).

a. Contract Information Tab:

*Contractor

Instructions: If the company or division referenced is different than the offeror, note those changes (see L-8.1.4)

DUNS Number Instructions: Although not marked with an asterisk in the tool, this is a required field.

CAGE Code

Instructions: Although not marked with an asterisk in the tool, this is a required field.

Delivery/Task

Order

Instructions: Enter the Task/Call/Delivery/Purchase

Order Number if the order is provided as a stand-alone reference

*Contract Number Instructions: Self-explanatory *Contract Type Instructions: Enter FFP, CPFF, ID/IQ, LH, etc.

*Program Title Instructions: Self-explanatory *Short Program

Title (i.e., acronym) Instructions: Enter abbreviated title for program.

Contracting

Agency/Customer Instructions: Enter the servicing contracting agency and customer (office symbols suffice).

Contract Dollar Value

*Original

Instructions: Input total contract dollar value, with all options, in the amount originally awarded on the referenced contract; if ID/IQ or BPA, provide total ceiling; if stand-alone task/call/delivery/purchase, provide amount of the individual contract.

*Current

Instructions: Input total contract dollar value, with all options, as the contract stands at time of PPI submission; if ID/IQ or BPA, provide total ceiling;

if stand-alone task/call/delivery/purchase, provide amount of the individual contract.

Explain the difference in contract values, if applicable

Instructions: Self-explanatory

Period of Performance (mm/dd/yy)

*Start

Date

Instructions:

Self-explanatory *Original End

Date

Instructions: Input original end date based on award *Current

End Date

Instructions: Input end date, as the contract stands at time of PPI submission

Explain the difference in Period of Performance, if applicable

Instructions: Self-explanatory

*Brief Description of

Effort as Instructions: Select Prime, Sub, Joint Venture or Other; if Other, provide explanation in text box below

b. Program Details Tab.

c. POC & Key Individuals Tab.

Step 3: Print Report

Step 4: Click “Submit” to upload information.

Instructions: Offerors shall:

1) Provide explanation if selected „Other‟ above.

2) Provide a brief description of the service provided and actual work performed under this contract reference.

3) If submitting a reference for a subcontractor, teaming partner, joint venture, or a corporate division related to the Prime, describe the nature and portion (percentage) of the work to be performed on RPA by the company referenced on the PPI sheet, and clearly define the relationship.

4) Indicate place(s) of performance:

a) State if performance was in multiple locations. If so, specify locations.

b) State if performance was CONUS, OCONUS or both, and provide details.

c) State if performance serviced state or federal Government, and provide details.

d) State if performance serviced the Department of Defense, and provide details.

*Explain how your experience on this program is relevant for each factor/subfactor under the Technical Factor in Section M, including any unique aspects that demonstrate relevancy in this effort.

Instructions: Provide evidence to support how the contract reference has relevant experience and demonstrates the ability to perform

RPA PWS requirements, and explain how the referenced contract is relevant IAW the relevancy definitions at M-3.3.1.2. As applicable, address how the proposed reference relates to each of the four (4) technical subfactors shown in paragraph L-7.4.1/M-3.2.

Include relevant information concerning your compliance with FAR 52.219-8, Utilization of Small Business Concerns, on the contract you are submitting:

Instructions: Although not marked with an asterisk in the tool, this is a required field if applicable to the referenced contract.

Identify whether a subcontracting plan was required by the contract you are submitting. If one was required, identify in percentage terms the planned versus achieved goals during contract performance. Explain why goals were not met, if applicable:

Instructions: If a subcontracting plan was required, attach a copy of your most recently submitted ISR (formerly SF294). If goals were not met, explain why in this block. Only applies to RPA Primes.

Key Individuals

Click New to specify any key individual or individuals who participated in this program or who are proposed to support the instant acquisition. Also indicate their roles for both acquisitions. Double-click an item from the list to edit or delete an existing key individual.

Instructions: In accordance with FAR 15.305(a)(2)(iii), relevant experience from key personnel may be evaluated. If you wish to include the past performance of individual key personnel, include names of key personnel and their contractual roles for both acquisitions as identified above by selecting the „New‟ button for each individual. This box is optional.

Customer Points of Contact

Click the point of contact that you would like to add, edit or delete.

Instructions: For Government contracts, provide current information on Program Manager, Contracting Officer, and for Admin POC, provide information on Quality Assurance Evaluator. For commercial contracts, provide points of contact fulfilling these same roles.

Program/Site Manager Contracting Officer Admin POC

Instructions: Provide a minimum of the following for each reference: 1) Name, 2) office & office symbol, 3) telephone number,

4) address, 5) FAX number, and 6) e-mail address.

RPA DRAFT Sections L&M

ATTACHMENT 2

SAMPLE SUBCONTRACTOR/TEAMING PARTNER CONSENT LETTER

Date

MEMORANDUM FOR ACC AMIC/PKC

ATTN: Ms. Sharon Potter

11817 Canon Blvd, Suite 306

Newport News, VA 23606-4516

ATTN: Ms. Sharon Potter

SUBJECT: Consent Letter to Release Past Performance Information

We are currently participating as a (subcontractor/teaming partner) with (prime contractor) in response to the

Department of the Air Force solicitation number FA4890-10-R-0009, Request for Proposal for the Remotely Piloted

Aircraft (RPA) Program.

We understand that the Government is placing increased emphasis on Past Performance in order to obtain best value in source selections. In order to facilitate the Performance Evaluation process, we are signing this consent form to allow you to discuss our past performance information with the Prime Contractor during the source selection process.

Offeror Name:

Company (Teaming Partner/Subcontractor) Name:

Address:

CAGE Code:

Phone Number and FAX:

Insert signature and title of individual with authority to sign for and legally bind the company

RPA DRAFT Sections L&M

ATTACHMENT 3

PAST PERFORMANCE QUESTIONNAIRE

IAW L-8.8 the Government will only utilize this PPQ if they are unable to validate and analyze past performance via any other means (ex. CPARs). In the event no past performance can be retrieved via PPIRS, the Government may 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. Offerors are not expected to complete and submit the PPQ. Any PPQs submitted by offerors will be ignored and will not be considered as part of the evaluation.

**When completed, this document is Source Selection Information IAW FAR 3.104**

SECTION 1: CONTRACT IDENTIFICATION:

A. Contractor

B. Contractor Cage Code

C. Role (check): Prime Subcontractor Teaming Partner Joint Venture Partner

Other (specify)

If subcontractor, partner or other, who is the Prime?

D. Contract/Blanket Purchase Agreement (BPA) Number

Task/Call/Delivery/Purchase Order Number

Note: If the referenced contract is an overarching ID/IQ or BPA, the Government will only assess performance at the ID/IQ level and not performance on each individual underlying task/delivery order. If the offeror would like assessment of the single task/call/delivery/purchase order, the offeror shall submit that as a separate reference

E. Contract Type (FFP, CPFF, ID/IQ (include types), LH, etc.)__________________________________________

F. Period of Performance

G. Place(s) of Performance:

Multiple locations? Yes No

If yes, specify locations:

CONUS OCONUS Both

Provide details:

State Federal DOD Other

Provide details:

H. Total Contract or Task/Call/Delivery/Purchase Order $ Value (including options)

I. Has a CPAR (or more than one CPAR) been completed for this contract? Yes No

If Yes, provide dates covered by CPARs:

SECTION 2: CUSTOMER OR AGENCY IDENTIFICATION

A. Customer or Agency Name

B. Customer or Agency Description

C. Description of Service(s) provided (Provide details on type of work, locations worked, and organizations serviced, to include Department of Defense, Government, or commercial work)

SECTION 3: EVALUATOR IDENTIFICATION

A. Name _________________________________________ B. Title

C. Phone/Fax D. E-mail

E. Years worked on Subject Contract

SECTION 4: EVALUATION

Please indicate your satisfaction with the Contractor‟s performance by placing an “X” in the appropriate block using the scale provided to the right of each question. This scale is defined as follows:

CODE PERFORMANCE LEVEL

E

EXCEPTIONAL - The Contractor‟s performance meets contractual requirements and exceeds many

(requirements) to the Government‟s benefit. The contractual performance was accomplished with few minor problems for which corrective actions taken by the Contractor were highly effective.

VG

VERY GOOD- The Contractor‟s performance meets contractual requirements and exceeds some

(requirements) to the Government‟s benefit. The contractual performance was accomplished with some minor problems for which corrective actions taken by the Contractor were effective.

S

SATISFACTORY – The Contractor‟s performance meets contractual requirements. The contractual performance contained some minor problems for which corrective actions taken by the Contractor appear or was satisfactory.

M

MARGINAL – Performance does not meet some contractual requirements. The contractual performance reflects a serious problem for which the Contractor has not yet identified corrective actions or the Contractor‟s proposed actions appear only marginally effective or were not fully implemented.

U

UNSATISFACTORY – Performance does not meet most contractual requirements and recovery is not likely in a timely manner. The contractual performance contains serious problem(s) for which the

Contractor‟s corrective actions appear or were ineffective.

N/A NOT APPLICABLE - Unable to provide a score or item is not applicable to the referenced contract.

Please provide detailed narrative comments to support your ratings. At a minimum, please discuss each response for which you indicated E (Exceptional), M (Marginal) or U (Unsatisfactory) in response to the questions below (use additional sheets, if necessary).

Q1. Quality of Product or Service E VG S M U N/A

Ability of Contractor to: provide accurate deliverables/reports; meet service specifications of the contract; provide timely proposals; respond to short notice requirements; provide and adhere to quality control/management plan (when required)

Explanation:

RPA DRAFT Sections L&M

Q2. Schedule E VG S M U N/A

Ability of Contractor to provide deliverables/reports required by the contract on time

Q3. Cost/Price Control E VG S M U N/A

Ability of Contractor to: provide accurate contract costs/estimates; track and control costs; meet and perform within negotiated costs; provide current, accurate and complete invoices/billing; submit cost reporting information in a timely manner

Q4. Business Relations E VG S M U N/A

Ability of Contractor to: maintain effective relationship between key

Contractor personnel and key Government personnel; manage, resolve problems and respond to and/or integrate changes in mission-related requirements

Q5. Management of Personnel E VG S M U N/A

Ability of Contractor to: attract, recruit, hire, train and retain qualified management and technical personnel to accomplish mission requirements; manage subcontractors to include identification and resolution of subcontractor problems; ensure continuation of services during personnel absences or vacancies; replace/fill vacancies within timeframe specified; maintain training/certification currency

Q6. Utilization of Small Business E VG S M U N/A

Ability of Contractor to: comply with Small Business Subcontracting

Plan (Large Businesses only); meet Small Business subcontracting goal as stated in the contract (Large Businesses only); meet the Limitations on

Subcontracting in accordance with FAR 52.219-14

RPA DRAFT Sections L&M

Q7. Security E VG S M U N/A

Ability of Contractor to: obtain appropriate company and personnel security clearances in a timely manner;…