ALE-47 Section L 7 May_.pdf

SOURCE SELECTION INFORMATION—SEE FAR 2.101 and 3.104

CONTROLLED UNCLASSIFIED INFORMATION

Section L

7 May 2024

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 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 AN/ALE-47 Production contract requirement as the Government will review only one proposal per offeror.

A joint venture is defined as a contractual agreement joining together two 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.

Proposals must be received by:

AFLCMC/WNKD

236 Milledgeville St, Ste F30

Robins AFB GA 31098

Attention: Mellissa Smith, Daniel Daniels, and Alex Katsekis

Proposals must be received no later than the date and time specified in Block 8 on the face page of the RFP. However, offerors are requested to submit Volume III, Past

Performance Information, so that it is received 10 calendar days prior to the date of receipt of proposals. Failure to submit Volume III by the earlier date will not result in offeror disqualification.

B. Communications: Exchanges of Source Selection information between Government and offerors will be controlled by the Procuring Contracting Officer (PCO). 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. Otherwise, Source Selection information will be transmitted via direct mailing or DoD SAFE. 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 Government Buyer/PCO 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). Otherwise, source selection information will be transmitted via direct mailing or DoD SAFE at https://safe.apps.mil/. When submitting source selection information via email, file compression utilities, to include but not limited to zip files, will not be accepted. If an offeror's computer system cannot support encryption technology, the offeror shall send the PCO correspondence at the time that it submits its proposal stating that it accepts the risk of sending and receiving unencrypted electronic mail if it chooses to utilize unencrypted email as a channel of communication.

II. Volume Organization

A. General: Proposals shall be submitted to the Government in five separate volumes as set forth:

VOLUME PAGE LIMITS NUMBER OF COPIES DESCRIPTION

I N/A* 1 Electronic Media/2 Paper* Completed RFP/Cross

Reference Matrix

II 50 1 Electronic Media/4 Paper* Written Technical Proposal

III N/A 1 Electronic Media/3 Paper** Past Performance

IV N/A 1 Electronic Media/2 Paper Small Business Participation

V N/A 1 Electronic Media/2 Paper Cost/Price Proposal

* Proposal information shall be submitted in written form (2 copies for Volumes I, IV, and V; 3 copies for Volume III, and 4 copies for Volume II) and CD-R or DVD-R (write once/read only) (1 copy for all Volumes) that is “closed” so that no further writes can be made to the media. CD-R/W or DVD-R/W media types are not acceptable. Media must be virus scanned by the offeror prior to submitting to the Government. Electronic media shall consist of one file per volume in PDF format, except for native files of MS Excel

(.xls) or MS Project (.mpp) format, and other similar files not readily convertible into

PDF without a significant loss of functionality. In the event of a disparity between the paper and the electronic versions of the proposals, the electronic version of the proposal will control. For paper copy submittal, offerors shall provide advance notification of submission to: Mellissa Smith, Daniel Daniels, and Alexander Katsekis. Advance notification should include tracking information for mailed proposals.

** Offerors shall use the instructions set forth in the RFP Attachment 1, Past

Performance Information (PPI) Tool, to electronically submit the Past Performance information. The offeror must submit an email request to the Buyer/PCO indicated on the face page of the solicitation to receive access to the PPI Tool via DoD Safe https://safe.apps.mil/. The offeror is also required to submit a hardcopy Past Performance https://safe.apps.mil/

Volume III that includes an Attachment 2, Relevancy Table. Line spacing, font size (etc.)

restrictions do not apply to the pages that are generated by the PPI Tool.

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

1. The sealed package used to submit the proposal package must show the time and date specified for receipt. 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, etc. Proposals shall be in the English language and all monies shall be proposed in United States dollars.

2. Print should be no smaller than a font size of 12, with 1.5 line spacing. Paper size shall be 8 1/2" X 11,'' excluding any drawings, diagrams, and/or supporting illustrations, spreadsheets, etc. Charts, graphs, drawings, diagrams, supporting illustrations, or spreadsheets shall not be greater than 11" x 17", and font size of no smaller than 9 will be allowable. 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. Each volume shall be submitted in a separate volume (i.e., 3-ring binder) and labeled. Elaborate formats, bindings, 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.

3. The page limitation for Volume II, Written Technical Proposal is 50 pages. The page limitations include any charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc., but excludes cover page, any table of contents, or list of acronyms (if utilized), and proof of certification. Charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets etc. may be on fold-out pages, but must fold within the page size specified, and shall not exceed 11 x 17 inches. Pages printed on one side shall count as one page, and pages printed on both sides shall count as two pages. Offerors are cautioned that any pages that exceed the page limitations shall not be read but shall be removed and either retained in the contract file without being considered in the evaluation or sent back to the offeror. Each technical subfactor must have a separate and clearly identified section within Volume II, Written Technical Proposal.

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

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

6. Each page should contain the following legend at the top and bottom of each sheet:

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

8. 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 IV 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 2016, MS Office Excel 2016, MS Office Project 2016, and MS Office Power Point

2016, as applicable.

B. Volume I, Completed RFP/Cross Reference Matrix

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. The proposal shall include a certificate or letter from an accredited organization demonstrating a quality program meeting AS9100D (Quality Management Systems - Requirements for Aviation, Space and Defense Organizations) requirements. The Government reserves the right to independently identify exceptions taken to the terms and conditions of the RFP outside of those identified in the offeror’s cover letter. 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. Offerors who meet the requirement to have First Article Testing waived, as described in RFP Part IV (First Article Applicability), will be considered a ‘proven’, ‘first-article qualified’, or simply a ‘qualified’ source. Offers who must complete First

Article Testing will be considered an ‘unproven’, ‘not first-article qualified’, or an

‘unqualified’ source. These terms may be used interchangeably within the RFP and file:///C:/Users/Brandi.Moody/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/Content.Outlook/AppData/Roaming/Microsoft/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/Content.Outlook/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Fil%23b522151 file:///C:/Users/Brandi.Moody/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/Content.Outlook/AppData/Roaming/Microsoft/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/Content.Outlook/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Fil%23b31044 associated documents/attachments. These terms may be used interchangeably within the

RFP and associated documents/attachments.

1. Cross Reference Matrix: The offeror shall fill out the cross-reference matrix at

Attachment 3 indicating where in its proposal the information can be found as it relates to the RFP. The cross-reference matrix will be utilized as a tool to show critical interrelationships and dependencies among the technical requirements documents including the Statement of Work (SOW), the Contract Data Requirements

List (CDRL), Section L (Instructions to Offerors) and Section M (Evaluation Basis for Award). The cross-reference matrix will help offerors ensure they have responded to all the evaluation criteria and proposal submittal requirements identified in the solicitation. If the matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over this matrix. Section

M references in the matrix are for informational purposes only, and the Government shall be obligated to evaluate proposals solely in conformance with the provisions of

Section M of the solicitation.

2. Small Business Subcontracting Plan: The small business subcontracting plan required by FAR 52.219-9, as supplemented by the DFARS and DAFFARS, shall be submitted by large business offerors. The plan shall set forth the offeror’s plan for subcontracting with small businesses to the maximum extent practicable, in accordance with FAR 52.219-9 as supplemented by the DFARS. The small business subcontracting plan shall include the information required by FAR 19.7, DFARS

219.7, and all associated clauses within this RFP. NOTE: The small business subcontracting plan is required by large business offerors only.)

3. Supplier Performance Risk System: If available, offerors shall have a current assessment in the Supplier Performance Risk System (SPRS) as required by DFARS

252.204-7019 and DFARS 252.204-7020. An assessment date is considered current within the last three years of this solicitation issuance. The Government will consider the offeror’s risk assessment for item, price, and supplier risk, as applicable. Offerors are able to access their risk assessments by following the access instructions in the

SPRS users guide available at https://www.sprs.csd.disa.mil/reference.htm.

C. Volume II, Written Technical Proposal

1. General: The written technical proposal shall be clear, concise, and include all the information required by this provision in sufficient detail for effective evaluation.

The proposal shall 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 the Government has no prior knowledge of their capabilities, work processes, facilities, and experience and https://www.sprs.csd.disa.mil/reference.htm will base its evaluation solely on the information presented in the offeror’s technical proposal.

2. Format and Specific Content: The following information shall be provided in the written technical proposal and will be evaluated to assess the proposed technical approach and associated technical risk in accordance with Section M-900, Evaluation

Basis for Award. The written technical proposal shall address the following technical subfactors to describe the offeror’s proposed approach to performing the requirements set forth in the SOW dated 18 Jan 2024 and Request For Proposal Part I - Schedule, Section B. For each subfactor, the offeror shall identify risks, if any, associated with the proposed approach and actions the offeror will 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.

In order to assist with streamlining the evaluation, offerors shall address only one subfactor per section in the technical proposal, avoid including subfactor discussions in multiple sections, and use the same headings/subfactor numbers/SOW paragraph numbers/etc. as used in this paragraph.

3. Subfactor 1: Engineering Expertise: The proposal shall include a detailed narrative of the offeror's current and planned capability for and approach to the following:

3.1 Engineering and reverse engineering to accomplish parts replacement and redesign associated with diminishing manufacturing resources and parts obsolescence, including reverse engineering associated with Field Programmable

Gate Arrays (FPGAs) and Programmable Array Logic (PAL) devices, timing, code / firmware, and programming. (SOW paragraphs 2.8.2, 2.8.3)

3.2 Engineering and reverse engineering to develop, verify, and validate acceptance test procedures, including test software and test equipment. (SOW paragraphs 2.1.1., 2.1.2, 2.1.3, including all sub-paragraphs for unproven sources. SOW paragraphs 2.2.1, 2.2.2, 2.2.3, including all sub-paragraphs for proven sources)

3.3 Engineering and reverse engineering to create, update, and provide configuration control of Technical Data Package (TDP) contents, including incorporation of Government submitted Notice Of Revisions (NORs) and

Engineering Orders (EOs). (SOW paragraph 2.8.5, including sub-paragraphs)

4. Subfactor 2: Fabrication, Integration, and Personnel: The proposal shall include a detailed narrative of the offeror's current and planned capability for and approach to the following:

4.1 Fabrication, integration, and test, to include test failure analysis and correction.

(SOW paragraph 2.1, 2.1.1, 2.1.2 including sub-paragraphs, 2.1.3, and 2.2 including sub-paragraphs)

4.2 Staffing to include key personnel and experience levels in the areas of

Security, Quality, Test, Engineering, Counterfeit Parts, Configuration

Management, and Operations/Manufacturing.

4.3 Manufacturing personnel training / qualification and staff levels, to include certifications (IPC or equivalent) in the following areas: (Attachment 3 –

Capability Table)

4.3.1 Requirements for Soldered Electrical and Electronic Assemblies, IPC J-STD-001.

4.3.2 Acceptability of Electronic Assemblies, IPC-A-610.

4.3.3 Rework of Electronic Assemblies/Repair and Modification of Printed

Boards and Electronic Assemblies, IPC-7711C/7721C.

4.3.4 Requirements and Acceptance for Cable and Wire Harness Assemblies, IPC/WHMA-A-620.

4.4 An effective system, such as an Enterprise Resource Planning type system, that automates the integration of internal and external management information across your entire organization, encompassing finance / accounting, manufacturing, sales and service, and customer relationship management. The narrative shall describe how the functional areas are linked, the extent to which they are linked, and the approach for how they shall share and exchange information. The narrative shall describe the medium (i.e., Aegis CircuitCam, paper copy, etc.) in which Bill of Materials and

Manufacturing instructions are provided to shop floor personnel.

5. Subfactor 3: Delivery Schedule/Requirements: The proposal shall include a detailed narrative of the offeror’s current and planned capability for and approach to the following:

5.1 Deliver LRUs/SRUs (at a minimum) within the stated timeframes (shown in

Table A), after contractor’s receipt of order. Note: an offeror’s proposed and substantiated technical approach that exceeds the USG requirements (i.e. less than the stated delivery schedule) may be deemed beneficial to the

Government.

5.2 In accordance with the H-901 clause, Delivery Requirements, the

Government's required quantities per monthly delivery is up to 150 each

Category 1 items and 120 each Category 2 items (see Table A). Offerors may propose delivery quantities that are higher in volume than the Government's required quantities, and such may be deemed beneficial to the Government.

5.3 Should the offeror propose a shorter delivery schedule and/or higher quantities in Technical Subfactor 3, Delivery Schedule/Requirements, the offeror shall also provide this same proposed schedule and/or quantities within the allotted area within the H-901 clause, Delivery Requirements. Failure to do so shall be deemed a proposal inconsistency and may render the proposal ineligible for award.

Table A

NSN Noun CLIN

Delivery (Number of months after receipt of order)

Category

5930-01-333-2196 EW Safety Switch X001 6 months Category 1

5865-01-334-8349 EW Dispenser, Countermeasure X002 6 months Category 1

5865-01-380-8046 EW Control Display Unit X003 10 months Category 2

5865-01-437-3371 EW Programmer (Air Force -0005) X004 12 months Category 2

5865-01-437-3373 EW Programmer (Navy - 0006) X005 12 months Category 2

5865-01-687-1948 EW Programmer (Navy -0010) X006 12 months Category 2

5865-01-451-2868 EW Sequencer X007 12 months Category 1

5865-01-527-2187 EW Sequencer (Army) X008 12 months Category 1

5998-01-357-0599 EW

Circuit Card Assembly Sequencer Fire Select CCA

X009 12 months Category 2

5998-01-357-0600 EW

Circuit Card Assembly Sequencer Signal Conditioner CCA

X010 12 months Category 2

5998-01-357-0601 EW

Circuit Card Assembly Sequencer Control Logic CCA

X011 12 months Category 2

5998-01-357-0602 EW

Circuit Card Assembly Interconnect, J1/J2 CCA 8A2A3A1

X012 12 months Category 2

5998-01-357-0603 EW

Circuit Card Assembly Sequencer J3 Interconnect CCA

X013 12 months Category 2

5998-01-388-7062 EW

Circuit Card Assembly CDU Power Supply Module CCA

X014 12 months Category 1

5998-01-333-1980 EW

Circuit Card Assembly

CDU CPU CCA

X015 12 months Category 2

5895-01-335-6069 EW Panel, Control, Elect X016 12 months Category 2

5998-01-414-1387 EW

Circuit Card Assembly CDU Front Panel I/O CCA

X017 12 months Category 2

5998-01-580-9469 EW

Circuit Card Assembly CDU Power Supply/Connector

Interface CCA X018 12 months Category 2

5998-01-383-8263 EW

Circuit Card Assembly CDU Discrete I/O CCA

X019 12 months Category 2

5998-01-580-7506 EW

Circuit Card Assembly Programmer Power Supply CCA

X020 12 months Category 2

5998-01-439-9525 EW

Circuit Card Assembly (-0009) Programmer CPU CCA

X021 12 months Category 2

5998-01-702-8446 EW

Circuit Card Assembly (-0020) Programmer CPU CCA

X022 12 months Category 2

5998-01-603-6648 EW

Circuit Card Assembly Programmer Discrete I/O CCA

X023 12 months Category 1

5998-01-334-2219 EW

Electronic Component CDU Electronic Indicating Panel

Assembly X024 12 months Category 2

5998-01-337-7526 EW

Circuit Card Assembly CDU Switch Panel CCA

X025 12 months Category 2

5998-01-335-3197 EW

Circuit Card Assembly CDU Discrete I/O Module Assembly

X026 12 months Category 1

5998-01-335-3198 EW

Circuit Card Assembly CDU CPU Module Assembly

X027 12 months Category 2

5865-01-333-4735 EW

Housing, Countermeasures Programmer Electronic Enclosure

Assembly X028 12 months Category 2

5998-01-336-3867 EW

Circuit Card Assembly Programmer Motherboard

X029 12 months Category 2

5998-01-336-9190 EW

Circuit Card Assembly Programmer 1553 Max Bus CCA

X030 12 months Category 2

5935-01-334-3230 EW

Bracket, Electrical Breechplate Assembly

X031 12 months Category 2

5998-01-357-8993 EW Circuit Card Assembly X032 12 months Category 2

D. Volume III, Past Performance

General: The offeror shall utilize the Past Performance Information (PPI) Tool in order to submit Volume III, Past Performance. The offeror shall utilize the Past Performance

Information (PPI) Tool in order to submit Volume III, Past Performance. The offeror shall submit Present and Past Performance Information for itself and any joint venture member, as well as each proposed critical subcontractor in accordance with the format contained in the PPI Tool (RFP Attachment 1), RFP Attachment 2, Relevancy

Assessment, and the following paragraphs. A critical subcontractor is defined as an entity (subcontractor and/or teaming contractor), other than the offeror itself that will perform testing and/or populating of multi-layered circuit card assemblies and/or assembly of final units or those entities expected to conduct greater than or equal to

30% of the overall effort, based on the offeror’s proposed price.

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.

1. Past Performance Format: The requested present and past performance information shall be provided in a separate volume (i.e., 3-ring binder) labeled "Volume III - 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 and critical subcontractor shall utilize the PPI Tool to complete information for three (3) active or completed contracts in the past five (5) years (with at least one year of performance history) from the issuance date of the RFP that the offeror/joint venture member considers relevant in demonstrating its ability to perform the proposed effort. If the total number of such contracts exceeds three (3), each offeror/joint venture member shall address its three

(3) most recent and relevant contracts. Please note that the offeror/joint venture member shall be the party to submit all performance information in the PPI Tool. 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 divisions 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 information in the PPI Tool shall clearly indicate the division or corporate organization that performed or is presently performing the contract. Contracts listed may include those with the 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.

2. 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 hereby cautioned that the Government will not evaluate basic ordering contracts without associated orders identified.

When determining what order (or series of orders) to submit for evaluation, please reference Section M, Volume III, Past Performance for details on how the

Government will evaluate each effort for recency, relevancy, and quality. In order to achieve optimal programmatic/logistical/scope and magnitude of effort and complexities, as described in Section M , Volume III, Past Performance, the offeror should consider submitting a series of orders, if possible, to provide the longest length and the highest quantity orders that are relevant to this instant acquisition. However, a series of orders should only be submitted if the series of orders is for continuous technical scope demonstrating relevancy to this particular effort. Not all ordering type contractual vehicles will have series of orders that meet this criteria. If this is the case, only the single order demonstrating relevant technical scope should be submitted for evaluation.

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 accurate, complete, and in the correct format. If the information is not submitted in the correct format, the Government will not be able to evaluate the effort for recency, relevancy, and quality. 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. There are specific places for submission of this information in the PPI Tool (RFP Attachment 1) and the RFP

Attachment 2, Relevancy Assessment. Please ensure the information submitted, in the

PPI Tool (RFP Attachment 1) and the RFP Attachment 2, Relevancy Assessment, 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, quantity produced/managed, and type and complexity of data deliverables, for each order or series of orders. See paragraph 2.1 below for further information on how to submit series of orders.

2.1 Series of Orders: When submitting a series of orders for evaluation, the offeror should list the orders under the basic ordering type contractual vehicle that demonstrate relevancy, as defined in the Relevancy Definitions in Section M paragraph Volume III, Past Performance, paragraph 3. Relevancy consists of scope and magnitude (i.e. period of performance and quantity produced) and the complexities (body of work). If an offeror submits a series of orders for evaluation, the period of performance dates of each order (in the series of orders), shall be submitted. The total period of performance of each order (in the series of orders) shall be added up to calculate the Total Period of Performance to be used in the evaluation, for the submitted effort. The total quantity produced on each order (in the series of orders) shall be added up to calculate the Total Quantity

Produced to be used in the evaluation, for the submitted effort. The type and complexity of data deliverables provided on each order (in the series of orders) shall be evaluated as a whole for the series of orders.

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.

3. Key Personnel: In considering past performance, The Government WILL NOT consider “Key Personnel” of the offeror/joint venture member even though they may perform major or critical aspects of this requirement.

4. Subcontractor/Teaming Member Consent Form: In addition to the information provided in the PPI Tool, Instructions available in Attachment 8 and the Relevancy

Table (Attachment 2) 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 Attachment

4). The consent form should 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 III.

5. Small Business Compliance in Past Performance Efforts: On the three (3) contracts submitted in Volume III, Past Performance, include relevant information in PPI Tool concerning the offeror’s/joint venture member’s and critical subcontractor’s compliance with FAR 52.219-8, Utilization of Small Business Concerns or FAR

52.219-9, Small Business Subcontracting Plan, if these clauses are or were contained in the contract. Please note that FAR 52.219-8 does apply to ALL businesses, whereas

FAR 52.219-9 only applies to large businesses.* When subcontracting possibilities existed on the contracts submitted by the offeror/joint venture member and critical subcontractor, address whether or not the offeror/joint venture member and critical subcontractor awarded subcontracts to small business concerns** to the fullest extent consistent with efficient contract performance. If none of the submitted contracts included these clauses, whenever subcontracting possibilities existed in the performance of these contracts, address whether or not it was the offeror/joint venture member and critical subcontractor’s policy to utilize small business concerns** to the fullest extent consistent with efficient contract performance.

*Small business offerors shall not simply identify themselves as a small business, as that does not address how the offeror utilized small business concerns** in the performance of the submitted effort

**Small business concerns include small business categories of veteran-owned small business concerns, service-disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and women-owned small business concerns.

6. PPI Tool and Relevancy Assessment Attachment: The offeror/joint venture member or critical subcontractor (if applicable) must submit information for each past performance effort in the PPI Tool (RFP Attachment 1) and the RFP Attachment 2, Relevancy Assessment. The offeror/joint venture member or critical subcontractor (if applicable) shall focus its responses in the PPI Tool (RFP Attachment 1) and RFP

Attachment 2, Relevancy Assessment so that they clearly correlate present and past performance with the requirements of this RFP. The information must clearly describe the relevance of the effort to the work proposed. Provide the most current information for the Points of Contact (POCs) identified in the PPI Tool. At least two of the following (in descending order of availability) should be identified as current POCs in the PPI Tool:

(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 actions taken to resolve those causes in the information provided in the PPI Tool for each contract identified for evaluation. Problems not addressed in the PPI Tool, 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.

7. Past Performance Questionnaire: The Present/Past Performance Questionnaire (see

RFP Attachment 5) 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 5) 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 PPI Tool.

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 6) 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 may submit their completed Present/Past

Performance Questionnaire either electronically or by mail. If sending electronically, follow the procedures outlined in paragraph I.B. Communications above, and email to:

mellissa.smith@us.af.mil. If mailing, the POCs may return the completed questionnaires via mail directly to:

236 Milledgeville St, Ste F30

If mailing, the outside envelope must be marked as follows:

NOTE: TO BE OPENED BY ADDRESSEE ONLY

The completed questionnaires should be contained in a second envelope marked with the mailing address and the following legend:

SOURCE SELECTION INFORMATION - See FAR 2.101 and 3.104

CUI

8. 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 7). The offeror is required to send the client authorization letter(s) with the Present/Past Performance Questionnaire(s) to each POC on 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.

9. Follow-up Discussions: The Government may conduct follow-up discussions with any of the people identified in the PPI Tool 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 through other sources, other than those listed within the PPI Tool.

10. RFP Attachment Legend: RFP Attachments 2 and 5 (Relevancy Assessment 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

E. Volume IV, Small Business Participation

1. General: The Small Business Participation proposal is required from all offerors, including small businesses and companies with Master, Individual, commercial subcontracting plans and/or comprehensive subcontracting plans. The offeror/joint venture member and each proposed critical subcontractor shall include only the first tier of subcontractors for this effort. Offerors are advised that the Small Business

Participation proposal is not the same as the Small Business Subcontracting Plan required by FAR 52.219-9. Large business offerors shall not utilize the Small Business

Subcontracting Plan in the place of the Small Business Participation proposal.

2. Format and Specific Content: The offeror shall submit a Small Business

Participation proposal for itself and any joint venture member, as well as each proposed critical subcontractor in a separate volume (i.e., 3-ring binder) labeled “Volume IV –

Small Business Participation”. The Small Business Participation proposal shall address each of the following elements in the proposed performance of this resultant contract:

a. The extent of participation of proposed Small Businesses (SB) when subcontracting possibilities exist, including the company names with CAGE codes the offeror plans to use in the performance of this resultant contract; and,

b. The description of the subcontracted work these proposed firms are to perform;

and,

c. The associated goals expressed in terms of percentages of the expressed in terms of percentages of the total acquisition value. If limited or no subcontracting possibilities exist for these socio-economic entities, provide rationale for such.

Offerors are cautioned against only acknowledging a goal is not met, if applicable. Rather, adequate rationale includes specific reasons why a goal is unmet and any actions being taken to increase any unmet goals. Additionally, if the offeror/joint venture member/critical subcontractor is a small business concern, it should include the work it will be performing when calculating the goals for your Small Business Participation information.

F. Volume V, Price Factor

1. General Instructions: These instructions are to assist Offerors in submitting cost/price information that is required to evaluate the unit prices proposed and to calculate the Total Evaluated Price. Compliance with these instructions is mandatory and failure to comply may result in rejection of the proposal.

2. Offerors shall propose unit prices as described in Section M, paragraph II, F, 1.3, a.

and shall complete the RFP Attachment 4.

3. Proposed unit/CLIN prices shall be rounded to the nearest whole dollar. If any proposed unit/CLIN price does not meet the required rounding, the Government will round that unit/CLIN price to the nearest whole dollar. The Government-adjusted unit/CLIN price will become the offeror’s proposed amount.

4. Data beyond that required by this instruction shall not be submitted. 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.

5. Compliance with these requirements is mandatory and failure to comply may result in rejection of the proposal.

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

7. In accordance with DFARS 215.371-3, cost and pricing data may be required in the event only one offer is received. If no exception in FAR 15.403-1(b) applies, the cost and pricing data shall be certified.

8. The proposal completed by each offeror depends on whether the offeror is a proven or unproven source.

8.1 Unproven sources shall propose for the thirty-six (36) month base period

(CLINs 0001-0008, A001-A00Y, and D001-D00Y).

8.2 Proven sources shall propose for the twelve (12) month Ordering Period I

(CLINs 1001 – 1005, 1007 – 1021, and 1023 – 1032).

8.3 All offerors shall propose to the twelve (12) month Ordering Periods II, III, IV, and V; these periods include CLINs 2001 – 2032, 3001 – 3032, 4001 – 4032, and 5001 - 5032.

8.4 Failure of an offeror to propose to the five (5) appropriate periods may be result in the entire proposal being determined not eligible for award. The

Government will not accept Not Separately Priced (NSP), To Be

Negotiated (TBN), $0 (Zero Dollar), etc. on any line items other than those already designated as such in the schedule.

8.5 The offeror shall submit the information requested above no later than the date and time specified in Block 8 on the face page of the RFP.

236 Milledgeville St, Ste F30

Section L Attachment 1 Instructions to Offerors

Past Performance Information (PPI) for Offerors

Offerors must use the PPI Tool in order to electronically submit the PPI portion of the Past Performance Volume in accordance with the RFP.

PPI Tool (Access database) The Contracting Officer will send the PPI Tool to the offeror by using a secure government website. (e.g., DoDSAFE). Once the offeror receives the PPI Tool follow the below steps:

1. Click on the ppi tool (access database file) and save the “ppi tool” to your computer. Name the file as the prime contractor + RFP number + file extension (e.g.

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

Figure 1: Security Alert Pop-up Note:

• 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. XYZCompanyFA852325R0002.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)” button to 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:

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

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

o 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) o Start Date: Input start date of contract.

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

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

o Explain the differences in…