DRAFT_SECTION_L_MTE_450V_PS_WORKING_DRAFT.pdf

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

L-I - SOLICITATION PROVISIONS INCORPORATED BY REFERENCE

NOTICE: Pursuant to FAR 52.252-1, "SOLICITATION PROVISIONS INCORPORATED BY

REFERENCE," the following provisions are incorporated herein by reference:

L-II - SOLICITATION PROVISIONS IN FULL TEXT

NOTICE: The following provisions are hereby incorporated in full text:

L-III - INFORMATION TO OFFERORS (ITO) AND INSTRUCTIONS FOR

PROPOSAL PREPARATION

1.0 Program Structure and Objectives

1.1The Governement intends to award a contract for an adjustable (200-450V), regulated power supply, with over-voltage over-current protection along; 1 first article, 21 power supplies, and the associated data package. As presently configured, the MTE is vulnerable to major system damage resulting from AC line voltage fluctuations. The new power supplies will correct this problem.

1.2 This requirement is being set aside for Small Businesses. The PCO has determined there is a high probability of adequate price competition in this acquistion. Upon examination of the intital offers, the PCO will review this determination and if, in the PCO’s opinion, adequate price competition exists, no additional cost information will be requested. However, if at any time during this competition, the PCO deteremines that adequate price competition no longer exists, offers may be required to submit information to the extent necessary for the PCO to determine the reasonableness and affordability of the price.

2.0 General Instructions

2.0.1 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 Statement of Work (SOW), System Specification, and Contract

Data Requirements List (CDRL). Non-conformance with the instructions provided in this

ITO may result in an unfavorable proposal evaluation.

2.0.2 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 or experience and will base its evaluation on the information presented in the offeror's proposal.

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

https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR52.246.doc#b522521

2.0.4 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.

2.0.5 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.1 General Information

2.1.1. Point of Contact

The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition.

Electronic exhanges of source selection information between the Government and offerors will be controlled by the PCO. Source selection information may also be transmitted via the mail system or in person. The PCO may determine to conduct telephone communications when deemed appropriate by the Government. Address any questions or concerns you may have to the PCO. Written requests for clarification may be sent to the PCO at the address below:

AFMC/PZZKC

Wade Pilcher

6039 Wardleigh Ave, Bldg 1206

Hill AFB UT 84056

E-mail: wade.pilcher@us.af.mil

801-586-1229

2.1.2. Debriefings

The PCO 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 pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing.

However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The PCO 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 PCO in writing with supporting rationale as well as the remedies the offeror is asking the PCO to consider as related to the omission or error. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

2.1.4. Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business

Opportunities (FedBizOpps) website at https://www.fbo.gov/. Potential offerors are encouraged mailto:wade.pilcher@us.af.mil https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b15505 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b15506 https://www.fbo.gov/ to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.2 Proposal 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

VOLUME ITO Paragraph

Number

VOLUME TITLE Hard

COPIES /

Disk

Copies

PAGE LIMIT

I Price Proposal 3/2

II Technical Proposal 3/2 15

III Past Performance 3/2 3 pages per

PPIS

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 pages and tables of contents.

2.2.1.1. Page Size and Format

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. Except for the reproduced sections of the solicitation document, the text size shall be no less than 10 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.

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 10point.

2.2.2 Pricing Related Data

All pricing information shall be addressed in the Contract Documentation volume, in Section B of the Schedule 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.4 Cross-Referencing

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, SOW, and specification paragraph number, the corresponding proposal paragraph in that section which addresses the referenced item

2.2.5 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.6 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.7 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

Electronic Offers – The content and page size of electronic copies must be identical to the hard copies. In the event there is a discrepancy between the hard copy and electronic copy, the hard https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR52.215.doc#b522151 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC#b31044 copy shall take precedence. For electronic copies, indicate on each CD the volume number and title. Use separate files for each volume to permit rapid location of all portions, including subfactor required plans, exhibits, annexes, and attachments, if any. The Offeror shall submit volumes I through III in electronic format, using read only CDs (i.e. CD-R). In no case, shall the Offeror use re-writable CDs (i.e. CD-RW). Each volume shall be on a separate 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) Word 2007, MS

Excel 2007, MS-Project 2003, and MS-Power Point 2007, as applicable and not in PDF format.

2.4 Distribution

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

AFMC/PZZKC

Wade Pilcher

6039 Wardleigh Ave, Bldg 1206

Hill AFB UT 84056

3.0 Factor 1– Price Proposal / Model Contract

3.1 Model Contract

The offeror shall complete the blocks of the RFP as required on the Standard Form (SF) 1447.

In doing so the offer accedes to the contract terms and conditions as written in the RFP sections

A through K. These sections constitute the model contract.

3.2 Section A Solicitation/Contract Form.

The offeror shall complete blocks 11,13,15,21,22, and 27 of the Standard Form (SF) 144.

Signature by the offeror on the SF 1447 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. This section shall be incorporated into the contract.

3.3 Supplies or Services and Prices

Offeror shall fill-in unit price and extened amount for each Contract Line Item Number (CLIN).

Insert proposed unit and exteneded prices in Section B for each CLIN or Sub CLIN in Schedule

B. The extended amount must equal the whole dollar unit price multiplied by the number of units.

The Cost/Price evaluation factors are Price Reasonableness and Balance. A Total Evaluated

Price (TEP), as defined in section M of this RFP, will be computed and provided to the Source

Selection Authority for award purposes only. It is the offeror’s responsibility to provide enough information in the Cost/Price proposal to support the evaluation factors.

3.3.1 Price Reasonableness

This section is to assist you in submitting information other than certified cost or pricing data that is required to evaluate the reasonableness and balance of your proposed cost/price.

Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low or high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has submitted an unrealistic 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 and balance. The burden of proof for credibility of proposed prices rests with the offeror.

3.1.2 Price Data

Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your 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 Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

3.1.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.

3.4 Section F - Deliveries

Deliveries will be required as shown in Section F of the solicitation.

3.5 Section H - Special Contract Requirements

The offeror shall comply with the clauses specified within Section H of the solicitation.

Furthermore, any reference of a clause and/or provision will be adhered to. All laws, regulations and statutory authorities will also be applied within the response to this RFP. This section shall be incorporated into the contract. The offeror shall complete the necessary fill-ins in the provisions identified in the solicitation in Sections I through K and return the RFP in its entirety to be evaluated for contract compliance acceptability

3.6 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, price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 3.6.

Table 3.6 - Solicitation Exceptions

Solicitation

Document

Page/

Paragraph

Requirement/

Portion Rationale

SOO, SOW, SPEC,

Model Contract, ITO, etc.

Applicable

Page and

Paragraph

Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

4.0 Other Information Required

4.1 GFP and/or Base Support Requirements

The Government plans to provide assistance in providing access to the relevant range(s) required for site visits.

4.2 Governement Furnished Equipment (GFE)/Government Furnished Information (GFI)

The Government intends to provide working prototype and relevant data as GFE/GFI to the contractor upon request.

5.0 Factor 2 - Technical Proposal

5.1 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. Note that technical risks assess the degree to which the offeror’s proposed technical approach for the requirements of the solicitation may cause disruption of schedule, increase costs, degrade performance, increase the need for Government oversight, or increase likelihood of unsuccessful contract performance. Risk will be treated as one aspect of the technical evaluation, inherent in the technical evaluation subfactors.

5.2 Format and Specific Content

5.2.1 Technical

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

5.2.2 Volume Organization

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

(1) Table of Contents

(2) List of Table and Drawings

(3) Glossary

(4) Cross Reference Matrix

(5) Subfactor One

(6) Subfactor Two (etc.)

(7) Risk Matrix

5.2.3 Subfactor 1, Program Management

5.2.3.1 Integrated Master Schedule (IMS)

The offeror shall provide a IMS that identifies proposed schedule dates for all events, reviews, accomplishments and criteria as outlined in SOW para 3.3.1.1. The offeror shall include a delivery schedule of the design Contractor Data Requirements List (CDRLs) and Technical Data

Package (TDP) as a part of the IMS. The offeror shall assume the contract award date of TBD for the IMS.

5.2.3.2 Data Management

The offeror shall describe how they will manage generatation, tracking, maintenance, DID compliance, and delivery of the data products described in Section 3.2, 3.3, and 4.3 of the SOW.

5.2.4 Subfactor 2, Technical Orders and Technical Data

5.2.4.1 Technical Orders

The offeror shall describe how they will meet the requirement to develop, prepare and deliver technical order (TO) change pages and commercial manuals as outlined in CDRL A013 and

A014. This description shall include how the offeror will meet the criteria described in SOW

3.2.3 and CDRL A013 and A014.

5.2.4.2 Technical Data

The Air Force projects that the end of life for the MTE will be 2040. Sustainment of legacy systems is a priority for the Air Force. As such, technical data that allows the Air Force, to the fullest extent possible, repair, re-procure and re-develop system assemblies is essential to their mission. Therefore, the offeror shall describe what data rights, relative to CDRL item A009 and as described in Section 3.1.1 & 3.2.1.1 of the SOW, they propose to satisfy the governments need for data suitable for manufacture or repair activites by other sources.

5.2.5 Subfactor 3, Testing

The offeror shall provide an approach that describes testing efforts necessary to validate all requirements described in Section 3 of the PS and described in the testing Section of the SOW para 3.2.1.8. The offeror’s approach shall include an explanation on how the offeror will meet the PS specifications, environmental requirements, and system reliability requirements. Tests shall comply with those defined is Section 3.2.1.7 of the SOW. The offeror shall use the sequence (not format) of Test Plan, Test Procedure and Test Report as outlined CDRLs A004 -

A008.

5.2.6 Subfactor 4, Engineering Design

In the design of the MTE 450 Volt Power Supply (VPS), the offeror shall convey to the

Government how several engineering aspects will or are incorporated into their product. The aspects shall include shielding, filtering, built-in-test, and obsolescence mitigation. The offeror shall describe how their design will meet the contract requirements for EMI, EMC, and electrical noise reduction, compliance with Section 3 of the MTE 450 VPS Performance

Specification, and thermal dissipation. The offeror shall prove to the Government how their design will be supportable for ten years. For example, this could be shown by designing in redundancy, identifying multiple sources for every component, or recommending a lifetime buy to the Government for sole source components. The lifetime buy is based on the offeror's reliability model and estimated allocation hours for each component. The offeror shall refer to

SOW 3.2.1 and ISO 9001:2015 (or an equivalent quality assurance prorgram).

For operation and maintenance (including installation, removal, and testing) only common tools shall be required; no special or unique tools will be required. The offeror shall include this while addressing the maintenance concept. The offeror shall describe all of the testing methods including qualification testing, built-in-test, and operational and maintenance testing. The offeror shall describe their complete technical data package to be delivered after completion of the contract. The offeror shall describe their maintenance concept to show how easily and safely the power supply can be restored to full operation.

6.0 Factor 3 - Past Performance

6.1 General

Each offeror shall submit a Past Performance Volume III as part of their proposal. Volume III shall contain completed Past Performance Information sheets (PPISs) (Section L, Attachment L-

1) containing the following:

Section 1: Table of Contents

Section 2: Past performance Information Sheet (PPIS) (IAW Section L, Attachment L-1)

Section 3: List of offeror’s contracts within the past three (3) years

Section 4: Consent Letters executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing the release o past performance information so the offeror can respond to such information. A sample consent letter is identified in Attachment L-2.

Section 5: Client Authorization Letters for each identified effort for a commercial customer authorizing release to the Government of requested information on the offerors performance.

As sample authorization letter is identified in Attachment L-3.

6.2 Past Performance Information Sheets

Offerors and their critical subcontractors shall complete a separate PPIS. The PPISs shall be used to submit information on no more than five (5) of the most relevant and recent contracts performed by eh prime offeror, key partners and subcontractors. Each PPIS shall be limited to three (3) pages, or a total of no more than 15 pages for all PPIS submitted.

6.3 List of Offerors’ Contracts

Each offeror shall submit a spreadsheet to identify quality and satisfaction rating for contracts awarded and/or completed in the past three years. The offeror shall provide information currently available (letters, metrics, customer, surveys, independent surveys, etc.) which demonstrates customer satisfaction with overall job performance and quality of competed products for same or similar type contract. In addition, explain corrective actions taken in the past, if any, for substandard performance and any current performance problems such as cost overruns, extended performance periods, numerous warranty calls, etc.

6.4 Past Performance Evaluation

The evaluation of past performance information will take into account past performance information regarding predecessor companies, key personnel who have relevant experience, or subcontractors that will perform major or critical aspects of the requirement when such information is relevant to the instant acquisition. Furnish the following information of reach contract listed:

(i) Company/Division name

(ii) Product/Service

(iii) Contracting Agency/Customer

(iv) Contract Number

(v) Contract Dollar Value

(vi) Period of Performance

(vii) Verified, up-to-date name, address, and telephone number of the contracting officer or primary point of contact. If current contract information is not provided, the referenced contract will not be included in the past performance evaluation.

(viii) Comments regarding compliance with contract terms and conditions.

(ix) Comments regarding any known performance deemed unacceptable to the customer, or not in accordance with the contract terms and conditions.

6.5 Consent Letters

If a teaming arrangement is contemplated, provide complete information as to the arrangement, including any relevant and recent past performance information on previous teaming arrangement s with same partner. If this is a first time joint effort, each party to the arrangement must provide a list of past and present relevant contracts.

6.6 Subcontractor Past Performance Information

Past performance information pertaining to a subcontractor cannot be disclosed to the prime offeror without the subcontractor’s consent. Provide with the proposal a letter from all subcontractors that will perform major or critical aspects of the requirement, consenting to the release of their past performance information to the prime contractor.

7.0 List of Attachments: Section L attachments listed below are provided as separate files.

Attachment L-1: Past Performance Information Sheet

Attachment L-2: Subcontractor Teaming/Partner Consent Letter

Attachment L-3: Client Authorization Letter

ATTACHMENT L-1: PAST PERFORMANCE INFORMATION SHEET (PPIS)

Provide the information requested in this sheet for each contract/program being described.

Provide frank, concise comments regarding your performance on the contract you identify.

Provide a separate completed form for each contract/program submitted.

Offeror Name:

Cage Code:

DUNS Number:

Program Title:

Contracting Agency or Customer:

Contract Number:

Contract Type: (FFP/CPFF/Other)

Period of Performance:

Original Dollar Value:

Current Contract Dollar Value: (If current value and original value differ please provide a brief explanation)

Key Point(s) of Contract Verified and up-to-date)

Customer Program Manager(s):

Office:

Address:

Phone:

Fax:

E-mail:

Discription of Work

A. Brief description of effort as Prime/Subcontractor: (Please indicate whether it was development and/or production, or other acquisition phase, and highlight portions portions considered most relevant to current acquisition)

B. Describe and adverse past performance and what actions where taken to mitigate the issue and result of that mitigation: (If there is no adverse past performance, indicate

“Not Applicable”)

ATTACHMENT L-2: SUBCONTRACTOR/TEAMING PARTNER CONSENT

LETTER FOR THE RELEASE OF PAST PERFORMANCE INFORMATION TO THE

PRIME CONTRACTOR

Past performance information concerning subcontractors 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 past and present performance information to the prime contractor during exchanges. In an effort to assist the Government’s Past Performance evaluation team in assessing your recent past performance relevancy and confidence, we request that the following consent letter be completed by the major subcontractors/teaming partners identified in your proposal. The completed consent letters should be submitted as part of your Past Performance

Volume.

SAMPLE

Dear “Contracting Officer:”

We are participating as a (insert “subcontractor” or “teaming partner”) with (prime contractor or name of entity providing proposal) in responding to the Department of the Air Force, Hill Air

Force), Request for Proposal TBD for Multiple Threat Emitter (MTE) 450 volt power supply contract.

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 confidence assessment process we are signing this consent letter to allow you to discuss our past performance information with the prime contractor during the source selection process.

(Signature and title of individual who has the authority to sign for and legally bind the company)

Company Name:

Address:

ATTACHMENT L-3: CLIENT AUTHORIZATION LETTER

Past performance information concerning private sector contractors, subcontractors and joint venture partners cannot be disclosed to the Government without their consent. Client authorization letters are required for each identified effort for a commercial customer. This letter will authorize release to the Government of requested information on the offeror's performance. The Government will need that consent before contacting commercial customers to assess the offeror’s past performance. In an effort to assist the Government's Past

Performance evaluation team in assessing your past performance, we request that the following client authorization letter be completed by any commercial customers identified in your proposal. The completed client authorization letters should be submitted as part of your

Present/Past Performance Volume.

Offerors should send with their list of references a letter similar to the following authorizing the reference to provide past performance information to the Government.

Dear “Client:”

We are responding to a Department of the Air Force, Hill Air Force Base, Request for Proposal

TBD for the Multiple Threat Emitter (MTE) 450 volt power supply contract.

In their acquisitions, the government is placing increased emphasis on past performance as a source selection factor. They are requiring those clients of entities responding to their solicitation to be identified, and their participation in the evaluation process is requested. In the event that you are contacted for information on work performed, you are hereby authorized to respond to those inquiries.

We have identified Mr./Ms.____________________________ of your organization as the point of contact based on his/her knowledge of our work. Your cooperation is appreciated. Any questions may be directed to .