FA8620-15-R-4005-02.docx

NSN

7540-01-152-8070 30-105

STANDARD

FORM

(REV.10-83)

PREVIOUS

EDITION

UNUSABLE

ConWrite

Version

6.14.5 Created

May

3:49

PM

Prescribed by GSA

FAR

(48

CFR)

53.243

See Block #2

PAGE OF PAGES

2. AMENDMENT/MODIFICATION NO.

3. EFFECTIVE DATE

18 MAY 2015

stephanie.sanchez.5@us.af.mil

FA8620-15-R-4005

X

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

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 Offers

Offers 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 MODIFICATION OF CONTRACTS/ORDERS, IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

(X )

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

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, 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.)

Pilot and Sensor Operators

See Schedule of Changes for detailed list.

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.

JOHN A. PURCELL

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

BY

(Signature of Contracting Officer)

16C. DATE SIGNED

SCHEDULE OF CHANGES

Changes incorporated on this modification:

1. Section L, Information to Offerors and Instructions for Proposal Preparation, Section 2.2, Table 2.2, Volume V, Contract Documentation, page limit was increased to 257 pages.

2. Section L, Information to Offerors and Instructions for Proposal Preparation, Section 7.1.3, Deliveries or Performance, was corrected.

FA8620-15-R-4005 0002

PAGE

OF

LIST OF ATTACHMENTS

DOCUMENT PGS DATE TITLE

ATTACHMENT 2 32 18 MAY 2015 SECTION L- INSTRUCTIONS, CONDITIONS, AND

NOTICES TO OFFERORS

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS L-III - INFORMATION TO OFFERORS (ITO) AND INSTRUCTIONS FOR

PROPOSAL PREPARATION

1.0 Program Structure and Objectives

The Medium Altitude Unmanned Air System (Medium Altitude UAS) program is comprised of the MQ-1 and MQ-9 aircraft, Ground Control Station (GCS), and support equipment that has been specially configured to meet mission requirements of Air Combat Command (ACC), US Special Operations Command (USSOCOM) and Air Force Special Operations Command (AFSOC). This Unmanned Air System (UAS) is employed around the globe and works in a range of environments from established bases to austere runways. The MQ-1/9 program develops cutting-edge equipment to meet the emerging requirements of ACC, USSOCOM, AFSOC, and various other government agencies.

The Production Acceptance and Developmental Test Support Services acquisition effort is to obtain the contracted services of MQ-1/9 Pilots, Test Pilots, and Sensor Operators (aircrew) to get the best value test support for the United States Air Force. The contract period of performance (POP) will be for 1 year plus 3 option years. In addition to providing aircrew, the Contractor shall provide MQ-9 Flight Manual Program support, Squadron Aviation Resource Management (SARM) Operations Administrators, Standards/Evaluation support, and Flight Scheduling support.

Baseline contract requires enough aircrew to support, on average, three (3) four (4)-hour sorties (flights) and three (3) four (4)-hour ground test events per day, five (5) days per week given the AFI11-202 Volume 3 12-hour crew rest and duty day limitations. Generally, this effort is 75% Developmental Test Services, 23% Production Acceptance, and 2% Foreign Military Sales (FMS) Production Acceptance. This level of effort has historically been supported by 17 MQ- 1/9 Pilots, two of which are Test Pilots, and 12 MQ-1/9 Sensor Operators. The historical unit level support also included two (2) aircrew schedulers, two (2) SARM Operations Administrators, one (1) Flight Manual Manager (works in Poway, CA at AFLCMC Det 3) and three (3) part time UAS Operator Subject Matter Experts to support the normal operations tempo at AFLCMC Det 3 OL.

2.1 General Instructions

(a) The offeror's proposal must include all data and information requested by this ITO and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

(b) The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but rather 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 and experience and will base its evaluation on the information presented in the offeror's proposal.

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

(d) The proposal acceptance period is specified in Section A of the model contract/solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.

(e) In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

2.2 General Information

2.1.1. Point of Contact

The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address located in Section A of the model contract/solicitation.

2.1.2. Debriefings

The CO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a preaward debriefing or they may choose to wait until after the source selection decision to request a postaward debriefing.

However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, 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 CO in writing with supporting rationale as well as the remedies the offeror is asking the CO to consider as related to the omission or error. The offeror is reminded that the Government reserves the right to award this effort based

Page of on the initial proposal, as received, without discussion. This reservation includes matters of additional or substitute pages of the initial proposal.

2.1.4. Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) website at http://www.fedbizopps.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 Communications

Exchanges of source selection information between Government and offerors will be controlled by the CO. Email may be used to transmit such information to offerors only if the email can be sent and received encrypted or sent via Army Aviation and Missile Research Development and Engineering Center Safe Access File Exchange (AMERDEC SAFE) at https://safe.amrdec.army.mil/safe/ and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. Otherwise, source selection information will be transmitted via USPS, FedEx, UPS, or pick-up by local representative.

2.2 Organization/Number of Copies/Page Limits

The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2 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 in Table 2.2. The attachments identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

Table 2.2 - Proposal Organization

2.2.1 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and excess paper copies will be returned to the offeror as soon as practicable. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Each page shall be counted except the following: Cover page, table of contents, tabs, letters of intent 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 x 11 inches, not including foldouts. Pages shall be single spaced typed. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12 point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and ¾- inch side margins. Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

(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 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 10 point. These limitations shall apply to both electronic and hard copy proposals.

2.2.2 Cost or Pricing Related Data

All cost or pricing data shall be addressed ONLY in the Cost/Price Proposal and Contract Documentation Volumes. Cost trade-off information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions.

All pricing information shall be addressed in the Contract Documentation volume, in Section B of the RFP. Information shall be limited to Contract Line Item Number (CLIN), SubCLIN, or ELIN-level pricing, including unit and extended pricing, as specified in Section B of the RFP.

2.2.3 Cross-Referencing

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of 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.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

The offeror shall provide a Solicitation Cross Reference Matrix indicating by ITO and/or PWS, the corresponding proposal paragraph in that section which addresses the referenced item.

2.2.4 Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

2.2.5 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

2.2.6 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, 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. All unclassified 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-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

2.3 Electronic Offers

The content and page size of electronic copies must be identical to the hard copies. For electronic copies, indicate on each CD the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any.

The offeror shall submit volumes I through V in electronic format, using recordable CDs. Each volume shall be in a different directory on a CD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2010, MS Office Excel 2010, MS Office Project 2010, and MS Office Power Point 2010, as applicable. In the event that hard copies and electronic copies of a proposal are submitted and if there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

2.4 Distribution

The "original" proposal shall be identified. Proposals shall be addressed to the CO and mailed or hand carried to:

USAF/AFMC/AFLCMC

AF Life Cycle Management Center 2530 loop Rd West, Room 144 Wright-Patterson AFB, OH 45433-7101 John Purcell 937-255-5908 John.Purcell.3@us.af.mil

Be sure to advise the Administrative Contracting Officer (ACO) and the Defense Contract Audit Agency (DCAA) for prime and subcontractors that the proposal is "For Official Use Only" and "Source Selection Information--See FAR 2.101 and FAR 3.104".

3.1 Volume I - Executive Summary

In the executive summary volume, the offeror shall provide the following information:

3.2 Narrative Summary

The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

3.3 Table of Contents

Include a master table of contents of the entire proposal.

3.4 Cross-Referencing

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of 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. The offeror shall fill out the Solicitation Cross Reference Matrix at Attachment 1, indicating the proposal reference information as it relates to the PWS, Section L & M, CLIN numbers, and Past Performance references found therein.

4.1 Volume II - Technical Volume

4.2 General

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

4.3 Format and Specific Content

Volume II: Technical Factors Subfactor 1: Program Execution Subfactor 2: Program Management Subfactor 3: Transition Plan

Volume III: Past Performance Volume IV: Cost/Price

4.3.1 Technical

In the technical volume, address your technical solution for meeting the Government’s minimum performance or capability requirements of each technical subfactor.

4.3.2 Volume Organization

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

(1) Table of Contents

(2) List of Tables and Drawings

(3) Glossary

(4) Cross Reference Matrix

(5) Subfactor One

(6) Subfactor Two

(7) Subfactor Three

4.3.3 Subfactor One, Two, And Three:

4.2.3.1 Subfactor 1: Program Execution

Description: The offerors’ proposal shall describe their company’s Program Execution plan which includes:

a. The proposed approach for manning levels and skillsets required to support PWS Sections 3.1 -- 3.4 by filling in the Manning, Skills, Qualifications and Certifications (MSQC) Matrix in Attachment 2.

b. The proposed approach for manning given:

1. Temporary increases in Operations Tempo due to programmatic deadlines.

2. Surges in Operations Tempo due to Joint Urgent Operational Needs (JUONs), Urgent Operational Needs (UONs), and Quick Reaction Capabilities (QRCs) test efforts.

c. The proposed plan for maintaining pilots’ Federal Aviation Administration (FAA) Commercial/Instrument Pilots’ Licenses.

4.2.3.2 Subfactor 2: Program Management

Description: The offeror’s proposal shall describe how their company is organized to fulfill the contract requirements to include:

a. An Organization Chart which depicts the offeror’s company organizational structure describing lines of authority and communication; functional relationships and geographical locations; and roles and responsibilities of key personnel.

b. Three representative One-page Résumés of Key Personnel (include one each, On-site Contractor Program Manager, Chief Pilot, and Chief Sensor Operator).

c. The proposed processes for personnel management (includes managing vacancies and Government notification of imminent vacancies).

4.2.3.3 Subfactor 3: Transition Plan

Description: The offeror’s proposal shall include a Transition Plan which:

a. Describes the offeror’s proposed approach to meet the timeline and checkpoints as prescribed in PWS Section 4.2.

b. Captures associated transition risk assessment and accompanying mitigation strategies.

c. Describes the offeror’s approach to recruiting/attracting and hiring target aircrew and Unit Level Support personnel with the requisite experience.

5.1 Volume III - Past Performance

5.2 General

Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Attachment 3. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 25 percent or more of the proposed effort based on the total proposed price or perform aspects of the effort the offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance.

Along with the information required in this paragraph, the offeror shall submit a consent letter executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. For each identified effort for a commercial customer, the offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the offeror's performance.

Offerors are encouraged to send the Past Performance Questionnaire Section L, Attachment 4, to any current or previous customers to aide in a more through past performance evaluation.

5.3 Early Proposal Information

Each offeror is requested to submit the information shown in Attachment 3 for each relevant contract 10 days prior to the date set for receipt of proposals.

5.4 Relevant Contracts

Submit information in accordance with Attachment 3: Past Performance Information on 3 recent contracts that you consider most relevant in demonstrating your ability to perform the proposed effort. Also include information on 3 recent contracts performed by each of your teaming partners and significant subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. Include rationale supporting your assertion of relevance.

5.4.1 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, at minimum include contract number, period of performance, Government POC (name, email, and phone number), and CPAR rating. 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 a limited or no confidence 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. This may allow the offeror to be considered a higher confidence candidate. 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 Cost/Price factor used to evaluate the proposal.

5.4.2 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 your company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes impact the relevance of any efforts you identify 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), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

6.1 Volume IV - Cost/Price

6.2 General Instructions

6.2.1 Price Reasonableness

This section is to assist you in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness of your proposed cost/price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal.

Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness. The burden of proof for credibility of proposed costs/prices rests with the offeror.

6.2.2 Price Data

Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Cost/Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

6.2.3 Cost or Pricing Data Requirements

In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit additional cost or pricing data.

6.2.4 Rounding

All dollar amounts provided shall be rounded to the nearest dollar. All loaded labor rates shall be rounded to the nearest penny.

6.2 Volume Organization

The Price volume shall consist of the following section:

SECTION 1 - Table of Contents; CLIN pricing on provided Attachment 5, Total Evaluated Price Matrix and section B of the RFP.

7.1 Volume V - Contract Documentation

7.2 Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The offeror's proposal shall include a signed copy of the Model Contract, and Sections A through K.

7.2.1 Section A - Solicitation/Contract Form

Completion of blocks 12 through 15 and signature and date for blocks 17 and 18 of the SF33. Signature by the offeror on the SF33 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes.

7.2.2 Section B - Supplies or Services and Costs/Prices

Completed pricing information in Section B of the model contract.

7.2.3 Section F - Deliveries or Performance

7.2 Exceptions to Solicitation Requirements

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, cost, 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

SOO, SOW, SPEC,

Model Contract, ITO, etc.

can/will not be met

7.3 Other Information Required

7.3.1 Authorized Offeror Personnel

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

7.3.2 Government Offices

Provide the mailing address, telephone and fax numbers, and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).

7.3.3 Company/Division Address, Identifying Codes, and Applicable Designations

Provide company/division's street address, county and facility code; CAGE code; DUNS code; TIN; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract 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.

7.3.4 Attachments to the Model Contract

The offeror shall provide the following as attachments to the model contract:

7.3.4.1 Government Furnished Property (GFP) and/or Base Support Requirements

The Government will provide adequate physical workspace and will furnish: desk, phone, computer equipment (to include all necessary hardware & software), an electronic mail (e-mail) account, use of the government telephone, facsimile machine, copier usage, and consumable office supplies as required by this effort. The workspace will include electricity, heating/air conditioning and water supply necessary to the functioning of such office space. Additionally, contractor aircrew will be provided headsets for flight operations, if necessary. GFP for this contract is shown in Table 7.3.

Table 7.3 – GFP

Quantity

Nomen- clature

Duration of Need

Reason for Need

If the offeror requires the use of Government furnished items other than those specified above, the offeror shall provide a listing including quantity, federal stock number, nomenclature, date needed and duration of availability, rental value per FAR 45.1 and 45.2, reason for need, and cross reference to cost/price volume paragraphs which pertain to GFP and/or base support. The offeror shall also provide the written authorization from the cognizant ACO, as applicable. The offeror shall supply this information in the format shown in Table 7.4.

Table 7.4 - Required Information for Using GFP/Base Support

Quantity

Federal Stock #

Nomen- clature

Duration of Need

Rental Value

Reason for Need Cross Ref. to Cost Prop

7.3.4.2 ciate Contractor Agreements

Include Associate Contractor Agreements, if applicable.

7.3.4.3 equired Attachments

7.3.4.3.1 Applicable Documents

A list of Applicable Documents has been provided to the offerors as an annex to the PWS attachment in the solicitation, which includes a minimum list of Government Compliance Documents. The offeror shall provide a list of any offeror, industry, commercial, and tailored Government standards, specifications, processes, and/or practices selected as compliance documents. The offeror shall also provide a list of all Government compliance documents intended to be used as compliance documents during the course of this contract. The offeror shall submit a list of these documents, including any tailoring instructions, as an annex to the proposed PWS. The offeror shall submit the completed Proposed Compliance Documents as a separately bound document.

Section L Attachments:

Attachment 1 – Solicitation Cross Reference Matrix Attachment 2 – Manning, Skills, Qualifications and Certification (MSQC) Matrix Attachment 3 – Past Performance Information Attachment 4 – Past Performance Questionnaire Attachment 5 – Total Evaluated Price Matrix

Attachment 1 –– Solicitation Cross Reference Matrix

Technical

Technical Risk

Past Performance

Attachment 2 –– Manning, Skills, Qualifications, and Certifications (MSQC) Matrix

Attachment 3 –– Past Performance Information (PPI) for Offerors

Offerors must use the PPI Tool (Use latest version from FBO.gov) in order to electronically submit the PPI portion of the Past Performance Volume in accordance with the RFP.

Downloading the PPI Tool The PPI Tool can be downloaded by performing the following steps (if you are unable to download the Tool, contact the contracting officer for assistance):

1. Access the FedBizOpps (https://www.fbo.gov/) website.

2. Find the solicitation posting.

3. Locate the “ppi tool” link from the “All Files” column on the solicitation’s “Notice Details” tab .

4. Select the link and save the “ppi tool” to your computer. Name the file as the prime contractor + RFP number + file extension (e.g. XYZCompanyFA861710R6158.accdb).

Note: PPI Tools saved in Microsoft Office versions 2007 and greater will be saved with “.accdb” file extension.

Entering information in the PPI Tool After selecting and saving the tool, enter information by performing the following steps:

1. Open the saved PPI Tool.

2. Select the “Options” button from the “Security Warning” banner, if applicable .

3. The “Security Alert” pop-up screen displays.

Note:

Figure 1: Security Alert Pop-up

· Files saved using Microsoft Office 2010 will have the “Enable Content” button on the “Security Warning” banner and therefore will not get a Security Alert pop-up.

· If a "read only" file is opened, in order to populate data in the file, click "Save As" in the "Read-Only" message bar. Enter the filename as the prime contractor + RFP number + file extension (e.g. XYZCompanyFA861710R6158.accdb).

4. Select the radio button “Enable this content” and then click “OK.” A setup pop-up screen displays.

Figure 2: Setup Pop-Up

5. Select the “Start” button. The “Application Setup” screen displays.

Figure 3: Application Setup Screen

Note: Once the Offeror’s Name and RFP Number have been entered they can be edited by selecting the “Edit Offeror And RFP Number” button from the “Contractor’s Menu”

6. Enter the Offeror’s Name and RFP Number and then click the “Next” button. The application setup continues.

Figure 4: Continue the Application Setup

7. Choose the appropriate option by selecting the corresponding radio button and then click the “Next” button. The “Contractor’s Menu” displays.

Figure 5: Contractor’s Menu

8. Click the “Step 1: Set up Business Relationships” button to create a business relationship, if applicable, for each business entity before proceeding throughout the PPI Tool (refer to Section L of the RFP for detailed instructions). Identify all prime and sub-prime organizations and categorize them according to the appropriate role in the proposed acquisition. The “Business Relationships” screen displays.

Figure 6: Business Relationships

9. Click the “New” button to create a business relationship for the proposed acquisition. An additional “Business Relationships” screen displays.

Figure 7: Enter New Business Relationship

10. Complete the fields as follows (fields marked on the screen with an asterisk ‘*’ are required):

· Contractor’s Name: Self-explanatory

· Role in Proposed Acquisition: Choose one of the four options – Prime, Sub, Joint Venture, or Other (Explain). An explanation comment box will display when you select “Other.”

· Place of Work: Location where contractor will perform work.

· Percentage of Work: Identify percentage of work contributed by specified business entity

· Responsibilities: Detail proposed responsibilities of specified business entity.

11. Select one of the buttons at the bottom of the screen.

· Add – Saves the current business relationship and allows for the addition of a new one.

· Close – Cancels the current business relationship without saving.

Note: In order to edit or delete an existing business relationship in the list, double-click on it.

12. Select the “Close” button on the “Business Relationships” screen after all of the business relationships has been added.

13. Click the “Step 2: Enter Past Performance Information (PPI)” buttonto enter the Past Performance Information. The “Past Performance” screen displays.

Figure 8: Past Performance

14. Click the “New” button to enter Past Performance Information for the proposed acquisition. An additional “Past Performance” screen displays.

Figure 9: Enter Past Performance Information

15. Complete the fields on each of the tabs as follows (fields on the screen marked with an asterisk ‘*’ are required):

· Contract Information Tab

· Contractor: Select from the dropdown the appropriate business entity.

· Cage Code: Self-explanatory.

· Contract Number: If you don’t have a contract number, enter “N/A.”

· Program Title: Enter full name of program.

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

· DUNS Number: Self-explanatory

· Delivery Task/Order: If the order is provided as a stand-alone reference, enter the task/call/delivery/purchase order number.

· Contract Type: Enter Firm-Fixed-Price (FFP), Cost Plus Fixed-Fee (CPFF), Indefinite Delivery/Indefinite Quantity (ID/IQ), LH, Blanket Purchase Agreement (BPA), Cost Plus Incentive-Fee (CPIF), Cost Plus Award Fee (CPAF), etc. For additional clarification, click the question mark button.

· Short Program Title (i.e. Acronym): Enter abbreviated title for the program or enter “N/A.”

· Contract Dollar Value:

· Original: Input total contract dollar value, with all options if applicable, 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: Input total contract dollar value, with all options if applicable, 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 differences in Contract Value, if applicable: Enter an explanation of the difference between the original contract dollar value and the revised value as of the time of PPI submission.

· Period of Performance (mm/dd/yy)

· Start Date: Input start date of contract.

· Original End Date: Input original end date based on award.

· Current End Date: Input end date, as the contract stands at time of PPI submission.

· Explain the differences in Period of Performance, if applicable: Enter an explanation of the difference between “Original End Date” and “Current End Date.”

· Program Details Tab

· Brief Description of Effort as:

· Select Prime, Sub, Joint Venture, or Other (Explain). An explanation comment box will display when you select “Other.”

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

· ****If applicable: Provide information on performance problems encountered on the identified contracts. At a minimum, briefly describe the problem experienced, actions taken to alleviate the problem, and whether or not the problem was satisfactorily overcome.****

· Explain how your performance on this contract is relevant for each applicable factor or subfactor, as instructed under Past Performance in Section M of the RFP. Include any unique aspects that demonstrate relevancy in this effort. Provide evidence to support such relevance to the requirements as described in the RFP.

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

· Identify whether a subcontracting plan was required for 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:

· POC & Key Individuals Tab

· Key Individuals: Click the “New” button to specify any key individual or individuals who participated in this program or who may support the proposed acquisition. Also indicate their roles for both acquisitions, previous and current. To edit or delete an existing key individual, double-click an item from the list.

Note: In accordance with FAR 15.305(a)(2)(iii), relevant contract efforts performed by from key personnel may be evaluated. If you wish to include the past performance of individual key personnel, select the “New” button for each individual and fill out the necessary information.

· Customer Points of Contact: Click the “Program/Site Manager,” “Contracting Officer” or “Admin POC” button for the point of contact that you would like to add, edit, or delete.

Note: For government contracts provide current information on Program Manager, Contracting Officer, and Admin POC, if available.

For commercial contracts provide points of contact fulfilling these same roles, if available.

16. Select from the buttons at the bottom of the Past Performance screen:

· Save – Saves the Past Performance Information and displays the “Contract Information” tab on the Past Performance screen.

· Close – Closes the Past Performance screen. If there were any updates, a pop-up window displays asking to save before closing.

· Delete – Deletes the current PPI record. A pop-up window displays, select “Yes” to delete the record or “No” to close the window without deleting the record.

Note: In order to edit or delete an existing PPI record in the list, double-click on it.

17. Select the “Close” button on the “Past Performance Information” screen after all of the PPI records have been added.

Printing Reports and Submitting PPI Tool In order to print the Business Relationships and PPI reports, perform the following steps:

1. Click the “Step 3: Print Report” button . A pop-up displays asking which report to print.

Figure 10: Select Report to Print

2. Select separately each of the two options, “Business Relationships” or “Past Performance.” The Business Relationships and Past Performance documents will print separately; combine the two to create your Past Performance Volume.

In order to submit the Business Relationships and PPI, perform the following steps:

3. Click the “Step 4: Submit” button . The “Submission Instructions” screen displays.

Figure 11: Submission Instructions

4. Follow the submission instructions. Hard copies of the pages generated from this tool shall be used in the hard copy of the past performance volume subject to the limitations outlined in this RFP and should be Tab 1 of the past performance volume.

Note:

· Submit an electronic copy (e.g. CD) of the saved PPI database file with your proposal. If a prime contractor is submitting the file enter the filename as:

· prime contractor + RFP number + file extension (e.g.

XYZCompanyFA861710R6158.accdb) If a subcontractor is submitting the file enter the filename as:

· subcontractor + RFP number + file extension (e.g.

ABCCompanyFA861710R6158.accdb)

· Once the file is saved to a CD or any location that is marked as “Read-only,” it must first be saved to the desktop in order to read/edit the file.

Editing Offeror and RFP Number

In order to edit the Offeror name and/or the RFP number identified during start-up, perform the following steps:

1. Click the “Edit Offeror and RFP Number” button . The “Application Setup” screen displays.

Figure 12: Change Name and RFP Number - Application Setup

2. Update the Offeror’s name and/or RFP number.

3. Click the “Next” button twice to return to the “Contractor’s Menu”.

Attachment 4 –– Past Performance Questionnaire (PPQ)

The Medium Altitude Unmanned Aerial Surveillance Office is in the process of competitively selecting a source to provide Production Acceptance and Developmental Test aircrew and Unit Level support personnel to support ground and flight testing at AFLCMC/WII DET 3 OL.

One of the considerations in proposal evaluation is the verification of the offerors' past performance on contracts or other work efforts, which reflect the offeror's ability to perform on the proposed effort. We depend on information received from organizations such as yours, which have had first-hand experience with the offeror, for the evaluation of the offeror's performance on those contracts or work efforts.

Our areas of interest regarding the offeror are summarized in the enclosed questionnaire. Our schedule is extremely tight and we desire your written response no later than 15 calendar days after your receipt of this letter. This schedule will allow us sufficient time to analyze the data prior to the start of evaluations.

To assist you in preparing your response and expediting your reply, the questionnaire may be filled out electronically and e-mailed to john.purcell.3@us.af.mil or stephanie.sanchez.5@us.af.mil. Your completed questionnaire will become a part of the official Source Selection records.

Your assistance is greatly appreciated and your prompt response will be one of the keys to the successful and timely completion of this Source Selection.

John A. Purcell Contracting Officer

I. CONTRACT IDENTIFICATION

A. Contractor (Company/Division):

B. Cage Code:

C. Contract Number:

D. Contract Type (e.g., FFP, FPIF, CPIF, CPFF):

E. Program Title:

F. Brief Program Description:

G. Program Phase: (e.g., Engineering & Manufacturing Development (EMD))

H. Period of Performance:

II. RESPONDENT(S) TO QUESTIONNAIRE

A. Name(s):

B. Phone Number(s):

C. Position (e.g., Program Manager, PCO/ACO):

D. Other suggested points of contact:

III. GENERAL COMMENTS

IV. PERFORMANCE EVALUATION

Please indicate your performance rating for the contractor’s by circling or place an “X” over the appropriate code using the performance evaluation scale below. Ratings are defined as follows:

CODE PERFORMANCE RATING