RFP Attachment 2 Section L-900.pdf

Section L- 900 Instructions, Conditions, and Notices to Offerors Section L

L-900. INSTRUCTIONS TO OFFERORS

I. Proposal Format

A. General: The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. Offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the Request for Proposal (RFP) may cause their proposal to be determined noncompliant and therefore not eligible for award. If a joint venture arrangement exists for this acquisition, the offeror shall provide a copy of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission. Offerors shall submit only one proposal for the On-Site Depot Support (OSDS) effort, as the Government will review only one proposal per offeror. No additional proposals (i.e., one (1) offeror submitting two (2) proposals based on differing approaches) shall be submitted. Proposals must be received by AFLCMC/WIUKA, Donna Casey, Contracting Officer, donna.casey.3@us.af.mil and Raquiel Shell, Contract Specialist, raquiel.shell@us.af.mil and Samantha Kirk, Contract Specialist, samantha.kirk.1@us.af.mil, via encrypted email or DoD SAFE (see paragraph L.II.A.7 below) no later than the date and time specified in Block 9 on the face page of the RFP. However, offerors are requested to submit Volume IV, Past Performance Information, so that it is received ten (10) calendar days prior to the required due date for proposals. Failure to submit Volume IV by the earlier date will not result in offeror disqualification.

B. Communications: Exchanges of source selection information after submission of the initial proposal packages between the Government and offerors will be controlled by the Contracting Officer. Email may be used to transmit such information, only if the email can be sent encrypted, and must include “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email. In order to facilitate the sending and receiving of encrypted emails, offerors must use MS Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption.

If you intend to submit your source selection information via encrypted email, you will need to contact the Contract Specialist/Contracting Officer indicated on the face page of the solicitation prior to that first submittal in order to exchange certificates used for encryption. To ensure the process is working correctly, send a test encrypted message first (without including any source selection information). When submitting source selection information via email, file suppression utilities, to include but not limited to zip files, will not be accepted.

The test encrypted message process is as follows:

(1) The offeror shall send a digitally signed “test” e-mail message containing no proprietary or source selection information to donna.casey.3@us.af.mil, raquiel.shell@us.af.mil, and samantha.kirk.1@us.af.mil. Please clearly identify the email as a “Test email for On-Site Depot Support for AFSOC C-130’s RFP FA8509-24-R-0026”.

(2) The PCO will open the test e-mail and add (or update) the sender’s e-mail address

(and corresponding encryption certificate) to their Outlook “Contacts List”.

(3) The PCO will send a digitally signed reply to the sender’s e-mail address.

(4) The sender must open the PCO’s digitally signed reply and add (or update) the PCO’s e-mail address in their “Contacts List” (For Outlook users - right-click the name in the “From” box, and then click” Add to Contacts” on the shortcut menu. Shortcut menu: a menu that shows a list of commands relevant to a particular item. To display a shortcut menu, right-click an item or press shift + F10. If you already have a contact entry for this person, select “Update New Information” mailto:donna.casey.3@us.af.mil mailto:raquiel.shell@us.af.mil mailto:samantha.kirk.1@us.af.mil mailto:donna.casey.3@us.af.mil mailto:raquiel.shell@us.af.mil mailto:samantha.kirk.1@us.af.mil from this contact to the existing one).

(5) When you are ready to send an encrypted email, ensure encryption is selected and include

“Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email.

NOTE: When sending files via encrypted email, please note there is a size limit of 20MB.

If an offeror’s computer system cannot support encryption technology, DoD Safe at https://safe.apps.mil is the preferred alternative method of electronic submissions. The offeror should send an unencrypted email, including “Source Selection Information – See FAR 2.101 and 3.104” in the subject line, requesting a Drop Link for transmission purposes. When submitting source selection information via email (to include DoD SAFE), file suppression utilities, to include but not limited to zip files, will not be accepted.

NOTE: When sending files via DoD SAFE, please note there is a size limit of 8GB, as well as a 25 files number limit. Offerors shall advise the PCO and buyer of any submissions that will be outside of these limitations so that multiple DoD SAFE drop-off request links can be sent. A formal notice must be sent to the PCO and buyer for a drop off link to be sent. Drop off request/links sent to companies by the Government are only valid for 14 days. Additionally, drop off request/links are only good for one submittal per use.

If the offeror chooses not to utilize encrypted email or DoD Safe, the offeror shall send the PCO correspondence at the time that it submits the proposal stating that it accepts the risk of sending and receiving unencrypted electronic mail.

II. Volume Organization

A. General: Proposals shall be submitted to the Government in four (4) separate volumes as set forth below:

VOLUME PAGE

LIMITS

NUMBER OF

COPIES*

DESCRIPTION

I N/A 1 Electronic Completed RFP (Excluding Section B of the Schedule, Includes Cross Reference Matrix and Joint Venture Agreement, if applicable)

II 40 1 Electronic Written Technical Proposal (excludes PWS Attachments G & I)

III N/A 1 Electronic Cost/Price Volume (Cost/Price proposal with completed RFP Attachment C)

IV N/A 1 Electronic Past Performance (Complete RFP Attachment A-FACTS Sheet)

*All proposal information shall be submitted in electronic form via encrypted email or DoD SAFE (see paragraph L.II.A.8. below). Media must be virus scanned by the offeror prior to submitting to the Government. The electronic version of RFP Attachment C (Excel Cost/Price model) shall be in .xlsx file format (Microsoft Excel 2016 or earlier version) with live working formulas; no other type of format will be accepted. Electronic media shall be accessible by a computer running Microsoft Windows 10 and above and Adobe Acrobat Portable Document Format (PDF) must be fully searchable in Adobe.

In addition to the page limitations set forth above, proposal volumes shall comply with the following format:

https://safe.apps.mil/

1. Each volume shall be marked with the RFP number and the offeror’s name and address, and the number of the Volume, i.e. I, II, III, and IV. Proposals shall be in the English language and all monies shall be proposed in United States dollars.

2. Print shall be no smaller than a font size of 12 and in Times New Roman. Paper size should be 8 1/2 x 11 inch, excluding any charts, graphs, drawings, diagrams, supporting illustrations, or spreadsheets, etc.

Charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc. shall not be greater than 11” x 17”. Each volume within the proposal notebook shall be separately tabbed and identified. Margins shall be no smaller than 1 inch and each page within a volume shall be numbered consecutively. Elaborate formats, bindings, or color presentations are not desired or required. In order to verify the font size and margins utilized, the offeror shall provide an electronic copy of the technical proposal in Word format and searchable PDF format.

3. 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.)

4. The page limitation for Volume II, Written Technical Proposal, is 40 pages (excludes PWS attachments G and I). The page limitation includes any charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc., but excludes any cover page, table of contents or list of acronyms (if utilized). Offerors are cautioned that any pages that exceed the page limitations shall not be read but shall be removed and retained in the contract file without being considered in the evaluation.

5. Page limitations may be placed on Evaluation Notices (ENs), if issued. The specified limits for EN responses will be identified in the letters forwarding the ENs to the offerors or on the EN form itself.

6. Each page containing proprietary information should be so marked.

7. Each page should contain the following legend at the bottom of each sheet:

SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104

CONTROLLED UNCLASSIFIED INFORMATION

8. Mailed or hand-delivered proposal packages will not be accepted. Proposal packages must be submitted via encrypted email or by DoD SAFE at https://safe.apps.mil. In order to submit the proposal package via DoD SAFE, the offeror shall send an email to the Contracting Officer (Donna Casey, donna.casey.3@us.af.mil) and Contract Specialist (Raquiel Shell, raquiel.shell@us.af.mil, and Samatha Kirk, samantha.kirk.1@us.af.mil) identified above and request a DoD SAFE drop-off link. Once the Contracting Officer and/or Contract Specialist receive the request, a drop-off link will be sent to the offeror to upload and send the proposal submittal. It must be noted that the proposal submittal, and not the request for drop off link, must be received by either the Contracting Officer and/or Contract Specialist by the proposal due date and time. Should the DoD SAFE proposal submittal be received after the proposal due date and time, the proposal will be considered late in accordance with FAR 15.208(b).

B. Volume I, Completed RFP

1. General: Volume I, Completed RFP shall consist of the completed and signed RFP, to include any amendments issued, with a cover letter delineating any exceptions taken to the RFP terms and conditions with accompanying rationale. However, offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined not eligible for award. Offerors shall ensure that all clauses and provisions that require “fill-in” information are appropriately completed, including the proposed prices associated with the contract line items in the Schedule of the RFP.

https://safe.apps.mil/ mailto:donna.casey.3@us.af.mil

C. Volume II, Written Technical Proposal

1. General: The technical proposal shall be clear, concise, and include all the information required by this provision in sufficient detail for effective evaluation. Work product attachments in the PWS shall be utilized as applicable to the task scenarios below. 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. The offeror will demonstrate task understanding and their ability to meet the PWS requirements. To merely paraphrase the specification, instructions or parts thereof is considered inadequate. Offerors shall assume the Government has no prior knowledge of their capabilities, work processes, and experience and will base its evaluation on the information presented in the offeror’s technical proposal.

2. Mission Essential Services: A Mission Essential Plan from the contractor has been deemed required for this effort. The contractor’s plan shall be IAW CDRL A00H, DI-MGMT-80004A, Mission Essential Plan, attached to the RFP. The contractor's written plan, including any prices/cost, shall be considered, and evaluated in conjunction with the technical evaluation of offers.

3. Format and Specific Content: The following information shall be provided in the technical proposal and will be evaluated to assess technical acceptability (which includes the consideration of technical risk) in accordance with Section M-900, Evaluation Basis for Award. The offeror’s technical proposal will be evaluated based on the four subfactors to determine if the offeror provides a sound, compliant approach that meets the requirements of the solicitation and demonstrates a thorough knowledge and understanding of requirements as outlined in the Performance Work Statement (PWS).

For each subfactor, the offeror shall identify risks, if any, associated with the proposed approach and actions the offeror will be prepared to take to mitigate the identified risks. If no risks/mitigations are identified in the offeror’s proposal, it indicates the offeror does not consider there to be any risk associated with their proposed approach. The Government reserves the right to independently identify risks with the proposed approach outside of those risks identified by the offerors themselves.

a. The technical proposal shall make no reference to price. Only one technical proposal from each offeror will be considered. Each of the two scenarios will be utilized to evaluate two each of the four subfactors.

b. The technical proposal, being complete in every way, but not overly elaborate, shall describe the offerors capability of and proposed approach to performing the requirements for each of the scenarios identified with the subfactors below.

c. The technical proposal encompassing the two task scenarios and four subfactors shall not exceed 40 pages total, with the exception of Performance Work Statement (PWS) Attachments G and I.

Scenario 1, UDLM REPAIR

UDLM 2024-XXXXX, AC-130J XX-XXXX HAIL DAMAGE INSPECTION AND EVALUATION

Note: Xs above represent the ending tracking number for the UDLM and aircraft tail number...both simulated for the purpose of this document.

• AC-130J XX-XXXX sustained hail damage and requires inspection and evaluation to determine the extent of damage.

• A UDLM (Unscheduled Depot Level Maintenance) was submitted by AFSOC requesting OSDS personnel be dispatched to Cannon AFB to meet the requirement. A SOW (Statement of Work) titled UDLM 2024-XXXXX, AC-130J XX-XXXX HAIL DAMAGE INSPECTION AND EVALUATION was developed by engineering and OSDS was tasked to travel to Cannon AFB to perform the Hail Damage Inspection and Evaluation.

• Subfactor One, UDLM Planning. Using UDLM Repair, Scenario 1 and PWS UDLM Planning attachments A and G (para 4.2.5 and 4.3.4.1), (No WFP required for this scenario) provide a technical proposal that includes a detailed narrative that demonstrates the Offeror’s understanding of the repair issues involved, and depot maintenance and modification processes to recommend repairs or methods which may be outside the scope of 1C-130A-3 (Structural Repair Instructions USAF Series ALL C-130 Aircraft). The narrative and completion of PWS Attachments A and G (para 4.2.5 and 4.3.4.1) shall provide a logical workflow execution plan that maximizes quality, safety, and work efficiency (para 4.3.3). Identify and describe your assumptions and any risks associated with your approach. Include all applicable technical orders (figure and indexes), inspection, material and process specifications used for the repairs. Consider all aspects of making the aircraft safe and ready to accomplish the task. Identify any part-specific (or otherwise special) tooling and/or processes required. The narrative and PWS Attachment G should identify all items required to complete the task. Any and all required preparatory subtasks shall be included. All disturbed systems shall be identified. All required materials shall be identified. All fabrication requirements shall be identified. All manpower support shall be identified. All preparation requirements shall be identified. All equipment support requirements shall be identified. The UDLM worker shift coverage shall be identified.

• Subfactor Two, UDLM Execution Schedule Development. Using the PWS (para 4.3.4.1.7) and Attachments A and G, break the task down into discrete sub steps with estimated execution hours for each sub step, then apply manpower loading based on the requirements of each sub step.

Identify the labor skills found in the PWS Attachment A to identify your task team composition.

Based on a 5-day per week, three shift (24-hour) work coverage (no overtime), provide the Government with a total direct labor hour estimate and a calendar day, start-to finish estimate, for task completion.

Scenario 2, Aircraft Modification

Comply with Time Compliance Technical Orders (TCTO) 1C-130(AHM)J-612 and subsequent

TCTO changes on all MC-130J aircraft.

• OSDS CDMT has been tasked to complete subject TCTO on AFSOC C-130s. The aircraft, an MC-130J, will be turned over to OSDS for TCTO completion. The aircraft will be turned over to OSDS on the flight line parking ramp for completion of the TCTO. In addition to the TCTO, OSDS is responsible for all aircraft ground handling and parts fabrication. Based on the TCTO provided and Attachments A. and I. in the PWS provide your Workflow Package (WFP) for execution (para.4.3.4.1).

• Since this TCTO will be completed on all MC-130J aircraft, the offerors WFP will be reviewed and revised, as needed, then issued by the Aircraft Mechanic III, Technical Point of Contact (TPoC), for team execution on each subsequent MC-130J aircraft (para 4.3.4.1.4).

• Subfactor Three, Workflow Package (WFP) Development. The offeror shall fully develop a WFP IAW PWS (para 4.3.4.1) instructions and in the format found in PWS Attachment I. and provide a narrative to comply with TCTOs on MC-130J aircraft. The WFP and narrative shall capture all aspects of the task including, team composition, ground handling, aircraft preparation for modification maintenance, documentation, and discrete work breakdown that supports a reasonable total man-hour and work-day estimate. Technical Order required Notes, Cautions or Warnings shall be included in the WFP (para 4.3.4.1.1). In-Process Inspections required by technical data are considered essential and shall be included in the WFP (para 4.3.4.1.3).

• Subfactor Four, WFP Update/Control. The offeror shall provide a detailed narrative describing their processes and controls to ensure WFPs for repetitive tasks have a review, revision, and issue control process IAW the PWS (para 4.3.4), their standard operating procedures (SOP) and their proposed local operating instruction to ensure an AS9001 compliant process is realized. This process shall ensure new updates are incorporated into the master WFP document prior to release for the next scheduled modification. This shall not be a restatement of Government requirements from the PWS but describe your technical approach to ensure quality WFPs for every task.

D. Volume III, Cost/Price Proposal

1. General: The Offeror shall complete and submit Attachment: OSDS Vol 3 Price Summary as its Volume III, Cost/Price Factor Proposal Submission:

OSDS Vol 3 Price Summary (Attachment to the RFP Attachment C- Excel Cost_Price Volume)

a. The contractor shall review, complete, and submit the above attachment. Instructions on what information to include is included on the form. Do not adjust or alter any of the pre-populated information, such as labor categories, hours, CLINs, etc. Labor rates shall be rounded to two decimal places.

b. Data beyond what is required by this instruction and form shall not be submitted.

Under no circumstances shall this data be included within the Price Summary volume.

E. Volume IV, Past Performance

1. General: The offeror shall submit Present and Past Performance Information for itself and any join venture member, as well as each proposed critical subcontractor in accordance with the format contained in the “FACTS Sheet” (See Attachment A) and the following paragraphs. A joint venture is defined as a contractual agreement joining together two (2) or more parties to undertake a particular business transaction or project and is intended to exist for a limited time period. The individual entities may retain their individuality and operate under a joint venture agreement, or the joint venture creates a separate corporation, limited liability company, or membership. A critical subcontractor is defined as an entity (subcontractor and/or teaming contractor), other than the offeror itself that will perform modification, maintenance, fabrications, inspections, and technical evaluations in direct support of specialized C-130 weapons systems, subsystems, and support systems. If subcontractor experience is submitted for consideration as part of the proposal, the offeror shall include a commitment signed by offeror and subcontractor certifying that if a contract is awarded resulting from the proposal, the parties commit to joint performance as proposed. If the signed commitment is not fully executed by both parties and provided with the Past Performance Proposal, subcontractor references will not be evaluated or considered. The evaluation of the offeror’s/joint venture member’s present/past performance WILL NOT include the present/past performance of any key personnel.

2. Past Performance Format: The requested present and past performance information shall be provided in a separate volume labeled "Volume IV - Past Performance". A summary page shall be provided for this acquisition, describing the proposed role of the offeror, any joint venture member and critical subcontractor (nature of work and percentage of overall work). Summary page information must clearly communicate how each proposed critical subcontractor meets the definition of a critical subcontractor established above. Efforts submitted for proposed critical subcontractors not meeting the established definition will not be evaluated. Efforts submitted for proposed critical subcontractors in which a signed commitment is not fully executed by both parties or is not provided with the proposal will not be evaluated. Each offeror/joint venture member shall complete a separate FACTS Sheet for no more than a total of four (4) active or completed contracts (with at least three years of performance history) in the past seven (7) years from the issuance date of the RFP, that the offeror/joint venture member considers relevant in demonstrating its ability to perform the proposed effort. For each critical subcontractor included in the offeror’s proposal, a FACTS Sheet for four (4) of the most recent and relevant contracts shall also be included. If the total number of such contracts exceeds four (4), the offeror/joint venture member/critical subcontractor shall address no more than a total of four (4) of the most recent and relevant contracts. The Government reserves the right to independently identify recent and relevant efforts outside of those summited by the offerors themselves. The offeror’s/joint venture member’s or critical subcontractor’s present and past performance information may include data on efforts performed by other predecessor companies, affiliates, other division or corporate management if such was provided for evaluation AND if the offeror’s past performance volume demonstrates the company, affiliate, or division will provide the offeror with resources for the instant proposed effort, such as workforce, management, facilities, or other capabilities demonstrating direct and meaningful involvement in the performance of the instant proposed effort. The FACTS Sheet shall clearly indicate the division or corporate organization that performed or is presently performing the contract. Contracts listed may include those with Federal Government, state and local governments or their agencies, and commercial customers.

Offerors/joint venture members/critical subcontractors shall furnish all available CPARS for the efforts submitted for evaluation, as applicable. Submittal of any CPARS for the efforts submitted for evaluation are not included in the page limitations.

3. Ordering Type Contracts Submission: If the contract you are submitting is an ordering type contractual vehicle (for example, including but not limited to an Indefinite Delivery “D” type contract per FAR 16.5), only after issuance of a delivery/task order does performance occur. Given this, an individual order (or series of orders) under the basic ordering contract shall be submitted, in lieu of just the basic ordering contract itself. All information provided to the Government, for an ordering type contractual vehicle, shall be at the order level (i.e. a delivery/task order). Offerors are cautioned that submitting an ordering-type contract without specific order identification will result in the effort not being evaluated.

When submitting an individual order (or series of orders) under an ordering type contractual vehicle, it is important that the offeror’s past performance information be submitted in the correct format. Please ensure the information submitted, using FACTS Sheet, is for each order (or series of orders), in lieu of just the basic ordering contract itself. This includes but is not limited to information such as the Dollar Value, Period of Performance, and type and complexity of data deliverables for each order in the series.

When determining what order (or series of orders) to submit for evaluation, please reference Section M, paragraph 2.d. for details on how the Government will evaluate each effort for recency, relevancy, and quality. If the information is not submitted in the correct format, the Government will not be able to evaluate the recency, relevancy, and quality for the effort.

Caution: All orders within the series of orders, being submitted, should be for the same continuous technical scope demonstrating relevancy to the instant acquisition. The Government reserves the right to request additional information from the offeror or Points of Contacts provided to verify that the series of orders is for the same continuous technical scope.

4. Subcontractor/Teaming Member Consent Form: In addition to the information provided in the FACTS Sheet (RFP Attachment A) for each entity as required above, the offeror must submit a consent letter executed by each of its proposed teaming member(s) and/or critical subcontractors authorizing release of adverse past performance information to the prime offeror to allow the prime offeror an opportunity to respond. A sample Subcontractor/Teaming Partner Consent Form is attached to this RFP (see RFP Attachment D). The consent form shall be completed by the team member(s) and/or critical subcontractors identified in your proposal. The completed consent forms shall be submitted as part of your Past Performance Volume IV.

5. FACTS Sheet: The offeror/joint venture member and critical subcontractor, if applicable, shall focus its FACTS Sheet responses so that they clearly correlate present and past performance with the requirements of this RFP. The FACTS Sheet responses must clearly describe the relevance of the effort to the work proposed. The answering space on the FACTS Sheet may be expanded so that the filled-in FACTS Sheet for each relevant contract covers no more than both sides of three (3) 8 ½ x 11inch pages.

(See paragraph 2, Relevancy Table and N. of the FACTS Sheet.) Provide the most current information for the Points of Contact (POCs) identified on the FACTS Sheets. At least two of the following (in descending order of availability) should be identified as current POCs on the FACTS Sheets:

(a) Procuring Contracting Officer/Contract Negotiator or equivalent

(b) Program/Project Manager, or equivalent

(c) Administrative Contracting Officer/Contract Administrator or equivalent

(d) Other (As specified in your FACTS Sheet)

If problems were encountered during the performance of the identified contracts, provide evidence of the ability to isolate the root causes of problems and include in the FACTS Sheet a description of programs or actions taken to resolve those causes. Problems not addressed in the FACTS Sheet but found by the Government during the evaluation of the information in this volume, will be assumed to still exist. Note:

In the case of Contractor Performance Assessment Report System (CPARS), if your input has already been provided and the rationale/circumstances have not changed, DO NOT repeat them here.

6. Past Performance Questionnaire: The Present/Past Performance Questionnaire (see RFP Attachment E) will be one means used by the Government to obtain present/past performance information. The Government reserves the right to change, alter, and/or supplement the questionnaire without further notice to the offeror(s). The offeror shall send out – and track the completion of - the Present/Past Performance Questionnaires (See RFP Attachment E) to each of the offeror’s, joint venture member’s and/or critical subcontractors’ (i.e., each entity’s) Points of Contact (POCs) identified in each FACTS Sheet. The responsibility to send out and track the completion of the Present/Past Performance Questionnaires rests solely with the offeror - i.e., it shall not be delegated to any other entity. The Transmittal Letter (see RFP Attachment B) shall be used by the offeror in sending out the Present/Past Performance Questionnaires. Exert your best effort to ensure that at least two POCs per relevant contract submit a completed Present/Past Performance Questionnaire directly to the Government not later than the date established in the RFP for receipt of proposals. POCs must submit their completed Present/Past Performance Questionnaire electronically. Follow the communication procedures outlined in Section L, Paragraph I. B, and email to: Contracting Officer (Donna Casey, donna.casey.3@us.af.mil), Contract Specialist (Raquiel Shell, raquiel.shell@us.af.mil, and Samantha Kirk, samantha.kirk.1@us.af.mil).

Once the Present/Past Performance Questionnaires are completed by your POCs, the information contained therein shall be considered source selection sensitive and shall not be released to you, the offeror. Therefore, any exchange/contact between the offeror/joint venture member and/or critical subcontractor and its own POCs in regard to comments made on the questionnaire is not permitted.

7. Client Authorization Letter: In the event that commercial contracts are presented as present/past performance sources of information, a client authorization letter shall be issued to those commercial POCs requesting/authorizing them to complete a Present/Past Performance Questionnaire. A sample client authorization letter is attached to this RFP (see RFP Attachment F). The offeror is required to send the client authorization letter(s) with the Present/Past Performance Questionnaire(s) to each POC on mailto:donna.casey.3@us.af.mil commercial contracts. A separate copy of client authorization letter(s) for each commercial contract shall be included in the offeror’s Present/Past Performance submission for the Government’s use in case additional questionnaires need to be sent by the Government after the RFP due date.

8. Follow-up Discussions: The Government may conduct follow-up discussions with any of the people identified in the FACTS Sheets or in the offeror’s Present/Past Performance Volume. Pursuant to FAR 15.305(a)(2)(ii), the Government may obtain other information by sending out additional questionnaires and/or through other sources, other than those listed within the FACTS Sheets.

9. RFP Attachment Legend: RFP Attachments A and E, FACTS Sheet and Present/Past Performance Questionnaire must include the following legend at the top and bottom of the page:

SOURCE SELECTION INFORMATION - See FAR 2.101 and 3.104

CUI