W909MY17R0016-Amendment_0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing items 8 and 15, and returning ____________ copies of the amendments: (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. Accounting And Appropriation Data (If required)

13. THIS ITEM ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: The Changes Set Forth In Item 14 Are Made In

The Contract/Order No. In Item 10A.

B. The Above Numbered Contract/Order Is Modified To Reflect The Administrative Changes (such as changes in paying office, appropriation data, etc.) Set

Forth In Item 14, Pursuant To The Authority of FAR 43.103(b).

C. This Supplemental Agreement Is Entered Into Pursuant To Authority Of:

D. Other (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return _______________ copies to the Issuing Office.

14. Description Of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. Name And Title Of Signer (Type or print)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

By (Signature of person authorized to sign) (Signature of Contracting Officer)

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Firm Fixed Price

W909MY

ARMY CONTRACTING CMD-APG

10205 BURBECK RD

FORT BELVOIR, VA 22060-5863

TAMARA JENKINS

EMAIL: TAMARA.N.JENKINS.CIV@MAIL.MIL

W909MY-17-R-0016

2017DEC13

X

X

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 10

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: TAMARA JENKINS

Buyer Office Symbol/Telephone Number: CCAP-CCV-A/(703)704-0827

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

The purpose of Amendment 0001 is to extend the due date for the AWR package from 22 December 2017 to 10 January 2018. This change has been made to Section L, Volume II Technical Proposal, Paragraph a., Section 1 Subfactor 1.1: Payload Performance (see below). In addition, the AWR date specified in Attachment 0006 YPG Demonstration Plan, Section J is also updated from 22 December 2017 to 10

January 2018.

All other terms and conditions remain unchanged and in full force and effect.

*** END OF NARRATIVE A0001 ***

2 10

W909MY-17-R-0016 0001

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L-15 PROPOSAL SUBMISSION (Section L)

1. Introduction. The Offerors proposal shall be submitted electronically through Federal Business Opportunity (FedBizOpps).

The Offerors submission shall consist of seven (7) volumes as follows:

Volume I Executive Summary

Volume II Technical

Volume III Price

Volume IV Past Performance

Volume V Technical Support Data

Volume VI Small Business Participation Plan

Volume VII - Solicitation, Offer and Award Documents

The content for each file is discussed in the paragraphs below. Offerors will need to be registered users of FedBizOpps in order to submit proposals. Files uploaded to FedBizOpps shall not contain classified data. WARNING: Please do not wait until the last minute to submit your proposals! To avoid submission of late proposals, we recommend the transmission of your proposal file 24 hours prior to the required proposal due date and time. Proposals shall remain valid for a minimum of 180 days from the closing date for receipt of proposals.

a. The United States Government (hereinafter the Government) intends to award without discussions, however, if discussions are conducted, the Government intends to conduct them using the Acquisition Source Selection Interactive Support Tool

(ASSIST). ASSIST will allow Offerors to receive and respond to Evaluation Notices (ENs) securely on-line. Offerors are required to provide two (2) company agents whose responsibilities will include reading and responding to ENs through ASSIST. For example, the

Offeror's Contract Manager, as an agent of the company, may be the main agent responsible, but a second agent must be available in case of the main agent's unavailability. The two (2) agents' names, company titles, telephone numbers, facsimile numbers, and e-mail addresses shall be provided. This required information shall be submitted with proposals under Volume VII - Solicitation, Offer and

Award Documents. In order to access ASSIST, the agents will need usernames and passwords. Once the company agents are provided access to ASSIST, your company will be informed of the specific website where your agents will receive and respond to the ENs. Offerors are cautioned that receipt of the website does NOT constitute official notice that a competitive range determination has been made or that a particular Offeror remains in the competitive range. The intent of this section is to advise Offerors that they may be receiving EN questions on-line if they remain in the competitive range and the Government decides to conduct discussions. Detailed instructions will be provided during the proposal evaluation phase. The ASSIST software program will allow Offerors to receive and respond to ENs securely on-line.

b. Offerors are cautioned that "parroting" of the Technical requirements or the PWS with a statement of intent to perform does not reflect an understanding of the requirement or capability to perform. Offerors are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal.

c. All proposals will be subjected to evaluation by a team of Government personnel and non-Government advisors from

Radiance Technologies.

The non-Government Subject Matter Experts (SME) will have access to all the necessary parts of the Offerors proposal pertinent to the

SMEs area of expertise. Non-Government SMEs will not have access to either past performance information or price data. As such, the above listed Government contractor company is precluded from being a prime contractor or participating in any teaming arrangement with potential Offerors due to Organizational Conflict of Interest (OCI) concerns. Offerors must advise the Contracting Officer as soon as possible of any concerns/questions with regard to the use of the non-Government SMEs from the company listed above. Any Offeror that is affiliated with, or is contemplating a contractual relationship with the above listed company, must notify the Contracting Officer for the solicitation as soon as possible. Offerors are required to execute non-disclosure agreements with the above company and provide copies with submitted proposals (See paragraph 2.c(7) below for further details).

2. Proposal Files

a. Format. The submission shall be clearly indexed and logically assembled. Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date and solicitation number in the header and/or footer. A Table of Contents must be created using the Table of Contents feature in MS Word Version 2007 or later. MS Word (.doc) files shall use the following Page Setup parameters:

Margins Top, Bottom, Left, Right - 1

Gutter 0

3 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

From Edge Header, Footer - 0.5

Page Size, Width 8.5

Page Size, Height 11

The following additional restrictions apply:

(1) Each paragraph shall be separated by at least one blank line. A standard, 12-point minimum font size applies. Arial is the only font authorized. Tables and illustrations may use a reduced font size not less than eight (8) point and may be landscape.

(2) All pages shall be sequentially numbered within each individual volume. The page limits are exclusive of a title page, table of contents, the list of illustrations, the acronym list or cross reference index, glossary and the one page Summary

Section.

(3) Those pages that exceed the page counts in Table 7 for each volume or attachment will not be evaluated.

Only page numbers, headers, and footers may be within the page margins, and are not bound by the font requirements. Company logos are prohibited with the exception of the Title Page. Pages that exceed the margin, font, or total page limit will not be evaluated. Pages deleted due to violation of the margin or font restrictions will not count against the page limitation. Page count will NOT be based upon the numbers of pages printed, but rather dictated by the number of pages in a print layout view in the application based upon the above-prescribed document settings. Counting pages in the order they appear for viewing will make up the page count. The page limits are applicable to graphs, tables, drawings and any annexes or other attachments submitted with the proposals and not specifically excluded by these solicitation instructions. PLEASE NOTE: No price information shall be presented in Volumes I, II, IV or V.

Table 7 Page Counts

VOLUME/SECTION TITLE PAGE LIMIT

I Executive Summary 10

II Technical Proposal 60

III Price Proposal No Limit

Proposal Spreadsheets

IV Past Performance Proposal No Limit*

V Test Data No Limit

VI Small Business Participation Plan No Limit

VII Solicitation, Offer and Award Documents, Certifications & Representations No Limit

* Each instance identified for relevant past performance shall be limited to no more than three pages.

b. File Packaging. Each Offeror shall submit its electronic proposal in seven (7) separate Volumes with ten (10) separate files, as depicted in Table 8, Assigned File Names. Microsoft Office products shall be used to create the required .XLS, and

.DOC files. Adobe Acrobat shall be used to create .PDF files. PLEASE NOTE: Self extracting .exe files will not be accepted.

Hyperlinks to documents, files or information external to the proposal are not permitted.

Table 8 - Assigned File Names

Volume Title File Name

I Executive Summary EXECSUM.PDF

II Technical Proposal TECH.PDF

III Price Completed Attachment 0008, Price Model TOTALPRICE.XLS

IV Past Performance Summary of Relevant

Contract Experience EXPER.XLS

IV Past Performance Performance PERF.PDF

IV Past Performance Subcontracts SUBCONT.PDF

V Test Data TEST.PDF

V Reliability Test Data REL.PDF

VI Small Business Participation Plan SBP.PDF

VII Solicitation, Offer and Award Documents And

Certifications/Representations FRREP.PDF

The contents of Volume V shall be limited to Government, independent, or contractor test data supporting the Offerors ability to meet the requirements as set forth below and in Section M. No other information or data shall be included in this volume. No price information shall be presented in any part of the proposal except the Price Volume, Small Business Participation Plan and the

Solicitation, Offer and Award Documents Volume. If the Offeror includes its own annexes or attachments, those annexes or attachments must be clearly identified. Proprietary markings are permitted and all proprietary data must be clearly marked. Classified data, if proposed, shall be contained in a separate Appendix to the Technical files. No classified material shall appear elsewhere in the

4 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

proposal and shall not be submitted electronically. Contact the Procuring Contracting Officer (PCO) for information on submitting any classified data. Use of URLs with hyperlinks in proposals is prohibited.

c. Content Requirements. All information shall be confined to the appropriate volume/file. The Offeror shall confine submissions to essential information, sufficient to define the proposal and provide adequate basis for evaluation. Offerors are responsible for including sufficient details, in a concise manner, to permit a complete and accurate evaluation of each proposal. Each volume/file of the proposal, at a minimum, must include a title page, table of contents, summary section, and the narrative discussion.

The Summary Section should contain a brief abstract of the file. The narrative discussion for each volume/file must include the following:

(1) VOLUME I EXECUTIVE SUMMARY. The Executive Summary Volume should contain a synopsis of the information contained in Volumes II, IV, V and VI. Pricing information shall not be included.

Offerors are reminded that the Executive Summary is an introductory summation of the proposal. No information should be in the

Executive Summary that does not appear elsewhere in the proposal. The Executive Summary is for information purposes only and WILL NOT be evaluated.

(2) VOLUME II TECHNICAL PROPOSAL. Offerors must submit information and substantiating data supporting their approach for the technical requirements listed below. The volume must be formatted such that all information is in the order listed below. Information applicable to a particular subfactor must be contained within that subfactor or references provided to specify where the information is located. NOTE: Test data is required to support compliance with certain subfactors. This test data must be for the proposed payload configuration(s), and certified as authentic. Test data pages will not be included as part of the

Technical Proposal. Test data will be provided in Volume V, Technical Support Data (See Volume V instructions below). However, the

Offeror must provide identifying information for any test results mentioned in the technical volume (i.e. Test Report Name, page number for location in Volume V, and paragraph number). Examples of acceptable certification include a local Defense Contract Management

Agency (DCMA) signature, or other form(s) of Government or independent commercial witness, or independent company statement.

The Offeror must provide an affirmative statement at the beginning of the technical proposal of Offerors ability and intent to comply with all requirements of the PWS, PBS and ICD.

The volume shall be organized in the following sections:

a) Section 1 Subfactor 1.1: Payload Performance

The Offeror must provide two (2) (one demonstration payload and one spare payload) production representative EO/IR/LD Payloads for RQ-

7Bv2 during the source selection evaluation for demonstration. The Offeror's Payload must demonstrate compliance with PBS Sections

3.4.2.4.1 (EO Sensor Recognition), 3.4.2.5.1 (IR Sensor Recognition), 3.4.2.6.3 (LTM Wavelength), 3.4.2.7.2 (LRF Accuracy), 3.4.2.8.1

(LD Range), 3.5.1 (Target Location Error), 3.6.2 (Payload Dimensions and Weight), and the maximum power requirement of 3.6.3

(Electrical Interface). Parameters to be measured and analyzed are outlined in Attachment 0006, Yuma Proving Ground Demonstration Plan.

Only those requirements specified in the Demonstration Plan will be assessed, the remaining requirements will be evaluated as set forth in Section M. The Demonstration payload must include the hardware, software accessories and tooling necessary to install the payload, conduct the Demonstration, and un-install the system. Offeror attendance at YPG is limited to no more than fifteen (15) individuals

(including payload operator and alternate payload operator) at the technical demonstration. All individuals other than the payload operator will remain in a room provided at mission control during all flight operations.

OFFERORS MUST ENSURE THEY HAVE COMPLETED AND SUBMITTED ALL INFORMATION NECESSARY TO MEET DEMONSTRATION ACCESS AND FLIGHT READINESS

REQUIREMENTS SET FORTH IN ATTACHMENT 0006, YUMA PROVING GROUND DEMONSTRATION PLAN. THIS INFORMATION MUST BE SUBMITTED TO THE CONTRACTING

OFFICER NLT 2PM ET 10 JANUARY 2018.

THE GOVERNMENT ASSUMES NO LIABILITY FOR ANY EQUIPMENT AND PERSONNEL PROVIDED.

b) Section 2 - Subfactor 1.2: Platform Elements. The Offeror must provide a full and detailed discussion of how the

EO/IR/LD Payload meets the requirements in the Performance Based Specification, see Attachment 0002. Specifically, the Offeror must provide a full and detailed discussion of how their system meets or exceeds threshold requirements in PBS Sections: 3.9.1.1 (Temperature

Non-Operating and Operating) and 3.9.2.1 (Operational Flight Environments - Temperature); 3.9.3.3.1 (Air Vehicle Vibration); 3.9.3.4.4

(Catapult Launch, Touch Down, and Arrested Landing); and 3.9.5.3 (EMI). In addition, the Offeror may provide a full and detailed description of how the presented Payload provides the potential for early fielding to the Warfighter of the EO/IR/LD Payload integration schedule events, as it relates to the Attachment 0007, Integration Schedule Events.

In order to establish the ability to provide early fielding, the Offeror must also provide supporting evidence that demonstrates the proposed payload meets the Standards as shown in Attachment 0007, Integration Schedule Events. Evidence may be in the form of test reports, product specification sheets, drawings, ICDs, or functional design documentation (user manuals, UML use cases, logic trees, and/or functional flow diagrams).

The Offerors proposal must include test results to support claims that the proposed EO/IR/LD payload meets or exceeds threshold

5 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

requirements for the above ICD and PBS requirements. The test data must be fully detailed Government, independent, or contractor test data. In addition, the Offeror will provide integration test data IAW Attachment 0007, Integration Schedule Events. The Offeror must support each claim of integration events completed, with fully detailed Government test data (or equivalent independent test data) verifying test completion on the EO/IR/LD Payload. This data must include documented test methodology and approach to attaining the requirements.

c) Section 3 - Subfactor 1.3: Sustainability. The Offer must provide a full and detailed discussion of their proposed approach to sustainability, specifically addressing:

Reliability, Availability and Maintainability (PWS Paragraph 3.3.5 and 3.6.7.1.1);

Technology Insertions (PWS paragraph 3.4.1);

Depot Analysis (PWS paragraph 3.6.1.2);

Operator and FSR training (PWS Paragraph 3.6.7.2.5);

Warranty Provisions (PWS App B, paragraph B-6.0); and

Repair Turn Around Time (RTAT) (PWS Table 3.6.7.1.1.1-1, Maintenance Requirements).

In addition to a full and complete description of the Offeror's approach to meeting the PWS sections above, the Offeror's proposal must describe an effective process for capturing RAM data in an integrated data environment. The Offeror must also provide a listing of the top 20 high failure rate items for their proposed system, the associated maintenance categories for these failures based on PWS

3.6.7.1.1, Repairs and the subparagraphs, and the associated Mean Time Between Failure (MTBF) for each item, to include supporting data and the conditions under which reliability was measured.

The Offerors proposed approach for technology insertions must include, at a minimum, a top level schematic supporting any claims of modularity, open architecture, plug-and-play, and use of standard interfaces. The Offeror must provide a full description of its systems upgrade potential and the flexibility of its systems design to adapt and incorporate future technologies beyond the threshold requirements for this procurement (e.g. weight/size reductions, range improvements, Target Location Error (TLE) improvements, image processing, software upgrades, and firmware upgrades, etc). The Offeror must describe if and how Modular Open System Architecture (MOSA) principles have been incorporated into the design of the proposed product to support maintenance and future upgrades.

The Offeror's approach must include description of the Offerors current or proposed long-term sustainment strategy and what, if any, features the Offeror proposes to facilitate competitive procurement of sustainment services over the life of the EO/IR/LD product.

The Offeror must include a full and detailed description of the proposed approach to meeting the requirements for Operator and FSR training, PWS Paragraph 3.6.7.2.5.

The Offeror must provide a full and detailed discussion of their proposed Warranty provisions; and procedures and timeframes for warranty repairs. To support evaluation of the warranty provision the Offeror must provide its complete warranty agreement detailing warranty start date (e.g. shipment, delivery, integration, etc), warranty duration, failures covered under warranty, and all other applicable terms of the warranty. Offerors are advised that the proposed warranty agreement will be incorporated into the successful

Offerors contract.

The Offeror must provide a full description of their RTAT processes to meet the Major Repairs/Non-standard Depot maintenance requirements.

d) Section 4 - Subfactor 1.4: System Modifications. The Offeror must provide a full and detailed discussion of any modifications to the proposed Non-Developmental Item (NDI) EO/IR/LD Payload necessary to meet the PBS Sections: 3.4.2.4.3 (EO Sensor

FOV), 3.4.2.5.4 (IR Sensor FOV), 3.4.2.8 (LD), 3.4.2.9 (Image Fusion), 3.5.1 (Target Location Error), 3.6.1 (Mechanical Interface),

3.6.2 (Payload Dimensions and Weight), and 3.6.3 (Electrical Interface). This discussion shall include details of how the Offeror will ensure production readiness of the proposed payload. In addition, the Offeror shall discuss each modification or change being made to their NDI EO/IR/LD Payload to meet Government requirements. This discussion shall include the Offerors assessment of the magnitude of the change and the associated risk and risk mitigation proposed.

If an Offeror's proposal states that no modification is necessary to the proposed NDI EO/IR/LD Payload to meet one or more of the above requirements, the claim shall be supported with Government, independent or contractor design schematics, product specification sheets, or other correlating data.

(3) VOLUME III PRICE. The Offeror must complete Section B of the Solicitation and the Attachment 0008, Price Model.

Prices for FFP CLINs should be input directly into the space allotted in the Price Model and Section B. Section B Pricing should be based on the Price Model and Pricing Model Notes and Instructions included in Attachment 0008.

If any CLIN/SLIN is proposed without a unit price (e.g. NSP, N/A, $-0-, blank, TBD, etc.), the Offeror must explain in detail why it is not priced. If the price is "NSP" (Not Separately Priced), it must be clearly indicated as to which CLIN/SLIN(s) must be exercised to obtain the item(s). If "N/A" (Not Available or obsolete item), the Offeror must provide a similar substitute item with all the required information (e.g. part number, description, price, etc.). If priced as $0.00, explain whether the Government can order this item at no cost and if the cost is included in other CLIN/SLIN(s). This information may be submitted in a separate Text (*.pdf) file.

6 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The Offeror must price all travel costs using the standard CONUS per diem rate as identified in .

(4) VOLUME IV PAST PERFORMANCE. This volume contains past performance information regarding similar contracts. This volume must not exceed 20 pages plus five (5) pages for each major subcontractor, excluding Past Performance Questionnaire Forms.

Offerors must submit all relevant Government and/or commercial contracts for the prime Offeror and each major subcontractor in performance or awarded during the past three years, from the issue date of this RFP, which are relevant to the efforts required by this solicitation. Relevant efforts are defined as manufacturing, production, and development and/or sustainment (e.g. FSR service/support, training OCONUS support, maintenance support planning) of Airborne EO/IR payloads of a similar size and complexity to the payload required by the RFP. An airborne EO/IR payload of a similar size and complexity to the payload required by the RFP that includes a LD will be considered more relevant than a payload without an LD. Data concerning the Offeror must be provided first, followed by each proposed major subcontractor, in alphabetical order. The Offeror must also submit the written consent of its major subcontractors to allow the disclosure of its subcontractors past performance information to the Offeror. In addition, letters of commitment must be included for all major subcontractors for their past performance to be considered. This volume must be organized into the following sections:

a) Section 1 Contract Descriptions. This section includes the following information in the following format:

i) Contractor/Subcontractor place of performance, Contractor and Government Entity (CAGE) Code and the Data

Universal Numbering System (DUNS) Number. If the work was performed as a subcontractor, also provide the name of the prime contractor and Point of Contact (POC) within the prime contractor organization (name, and current address, e-mail address, and telephone and fax numbers).

ii) Government or commercial contracting activity, and current address, Procuring Contracting Officer's name, e-mail address, telephone and fax numbers.

iii) Government technical representative/COR and current email address, telephone and fax numbers.

iv) Government or commercial contract administration activity and the Administrative Contracting Officers name, and current e-mail address, telephone and fax number.

v) Government or commercial contract administration activities Pre-Award Monitors name, and current e-mail address, telephone and fax numbers.

vi) Contract Number and, in the case of Indefinite Delivery type contracts, GSA contracts, and Blanket

Purchase Agreements. Include recent and relevant Delivery Order Numbers, as defined herein.

vii) Contract Type (specific type such as Fixed-Price (FP), Cost Reimbursement (CR), Time & Material (T&M), etc.). In the case of Indefinite Delivery contracts, indicate specific type (Requirements, Definite Quantity, and Indefinite Quantity) and secondary contract type (FP, CR, T&M, etc.).

viii) Awarded price.

ix) Final or projected final price.

x) Original delivery schedule, including dates of start and completion or work.

xi) Final or projected final, delivery schedule, including dates of start and completion of work.

b) Section 2 Performance. Offerors must provide a specific narrative explanation of each contract listed in Section

1, Contract Description, describing the objectives achieved and detailing how the effort is relevant to the requirement of this RFP.

i) For any contracts not meeting the original schedule or technical performance requirements, provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. The Offerors must list each time the delivery schedule was revised and provide an explanation of why the revision was necessary. All Requests for Deviation and Requests for Waiver shall be addressed with respect to causes and corrective actions. The Offerors must also provide copy of any

Cure Notices or Show Cause Letters received on each contract listed and a description of any corrective action implemented by the

Offeror or proposed subcontractor. The Offerors must indicate if any of the contracts listed were terminated and the type and reasons for the termination.

ii) For all contracts, the Offeror must provide data on all manufacturing warranty returns. Data shall delineate total number of warranty returns, number of Could Not Duplicate (CND), number of failures attributable to GFE component failures, and number and nature of failures attributable to the Offerors delivered product.

c) Section 3 Subcontracts. Offerors must provide an outline of how the effort required by the RFP will be assigned

7 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

for performance within the Offeror's corporate entity and among the proposed subcontractors. The information provided for the prime

Offeror and each proposed major subcontractor must include the entire company name, company address, CAGE Code, DUNS Number and type of work to be performed by citing the applicable Government PWS subparagraph number. This includes all subcontractors that will be providing critical hardware/services or whose subcontract is 20% or more of the total proposed price. Critical Hardware/services is defined as any supplier of the spare parts listed at Attachment 0008 Price Model, or any supplier of FSR or training support. This section will further include written consent of major subcontractors to allow the disclosure of their subcontractors past performance information to the Offeror. In addition, letters of commitment must be included for all major subcontractors.

d) Section 4 New Corporate Entities. New corporate entities may submit data on prior contracts involving its officers and employees. However, in addition to the other requirements in this section, the Offeror must discuss in detail the role performed by such persons in the prior contracts cited. Information should be included in the files described in the sections above.

Letters of Commitment shall be included in the proposal for these employees in order to be considered.

e) Past Performance Questionnaire. For all contracts identified in Section 1, Contract Descriptions, a Past

Performance Questionnaire must be completed and submitted. The Offeror must complete Part I of the Past Performance Questionnaire and e-mail the questionnaire to both the Government contracting activity and technical representative responsible for the past/current contract. The POCs shall be instructed to electronically complete Part II of the questionnaire and e-mail the entire questionnaire to the Contracting Office no later than the proposal due date, to jean.p.davis2.civ@mail.mil. The Offeror must e-mail to the Contracting

Officer a list of all the POCs who were sent a questionnaire. The Government must receive this list no later than the proposal due date. The POC List must be submitted in Word for Windows Table Format to include the following fields: Solicitation Number; Company

Name; Contract Number; Government Agency; POC Last Name, First Name; POC Title; POC Telephone Number; POC E-mail Address; and Date E-

Mail to POC (month/day).

f) Submissions. Offerors are discouraged from providing points of contact with another Offeror's facility in case an Offeror (or one of his/her team members) is in a subcontract with another contractor who has submitted a proposal on the same requirement. Offerors must provide and submit the prime contract number and all Governmental agency POCs in lieu of subcontract numbers or prime contract POCs in situations as described above.

g) Small Business Participation Past Performance. All Offerors must submit information substantiating the Offerors past performance in complying with FAR 52.219-8, Utilization of Small Business, maximizing opportunities for U.S. small business subcontractors. Offerors must also provide a statement indicating whether any negative information has been reported in the past six years concerning the Offerors past compliance with FAR 52.219-8. If any such negative information has been reported, the Offeror may submit explanations or comments responding to such negative information. Offerors with no prior contracts containing FAR 52.219-8 shall certify the same.

(5) VOLUME V TECHNICAL SUPPORT DATA - The Offeror must provide test data, drawings, Interface Control Document (ICDs), functional design documentation (user manuals, UML use cases, logic trees, and/or functional flow diagrams), design schematics, or product specification sheets in accordance with subfactors to be evaluated and the submission requirements set forth in Volume I, above.

The Offeror must provide a cross reference pointing to the relevant pages within the test data for each criteria being evaluated.

(6) VOLUME VI Small Business Participation Plan - All Offerors (both large and small businesses) must provide the following SBPP information and substantiating documentation to demonstrate how you will meet the proposed SBPP requirements. This required information will be used to evaluate the extent of your proposed participation/commitment to use U.S. small businesses in the performance of this acquisition (as small business prime offerors or small business subcontractors) relative to Section M, Factor 4, Small Business Participation. The proposed small business participation set forth in the Offerors SBPP will be incorporated into any resulting contract(s) as specified below.

a) The small business concerns (SBC) as defined in FAR Part 19 that are to be used in your proposed approach to satisfying the requirements of this solicitation for the entire performance period, including company name, business category(ies), description of products or services and NAICS code to be provided by each SBC and the nature of the commitment with the SBC (i.e., letter of commitment, joint ventures, mentor prot\'e9g\'e9 agreements, others). Use the table/format below in proposing this required information.

Company Small Business Product/ NAICS Nature of

Name Category Service Code Commitment

1.

2.

3.

4.

5.

6.

b) The SBCs (prime offerors and small business subcontractors) proposed quantitative participation in terms of the value of the total acquisition (total contract value). Offerors shall provide detailed explanations/ documentation to support quantitative small business participation. Use the table/format below in proposing this required information.

8 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Proposed Total Contract Value $ _______

Minimum Quantitative Requirement (MQR) Small Business Participation

Total Percentage planned for Large Business(es) _______% = $ _______

Total Percentage planned for Small Business(es) _______% = $ _______

Small Disadvantaged Business _______% = $ _______

Woman-Owned Small Business _______% = $ _______

HUBZone Small Business _______% = $ _______

Veteran-Owned Small Business _______% = $ _______

Service-Disabled Veteran-Owned Small Business _______% = $ _______

When Combined Large and Small Business Total must equal 100%

c) The work to be performed directly by a small business prime Offeror shall be evaluated as Small Business Participation. Small business prime Offerors shall include their information in the above requested Subparagraphs.

d) Offerors are reminded that proposed small business participation percentages will become enforceable, contractual requirements and will require periodic progress reporting to facilitate Government monitoring in the event of an award. Offerors are to propose monthly reporting for the requirements in Section L, subparagraphs a-c above (contractor format acceptable) in accordance with Section J, Exhibit B, CDRL B001, Small Business Participation.

e) Check the applicable size and categories for the PRIME Offeror only -- Check all applicable boxes:

{ } Large Prime

{ } Historically Black Colleges or Universities and Minority Institutions (HBCU) or

{ } Small Business Prime; also categorized as a

{ } Small Disadvantaged Business (SDB)

{ } Woman-Owned Small Business (WOSB)

{ } Historically Underutilized Business Zone (HUB Zone) Small Business

{ } Veteran Owned Small Business (VOSB)

{ } Service Disabled Veteran Owned Small Business (SDVOSB)

(7) VOLUME VII - SOLICITATION, OFFER, AND AWARD DOCUMENTS AND CERTIFICATIONS/REPRESENTATIONS - Certifications and

Representations Each Offeror must complete (fill-in and signatures) the solicitation sections indicated below using the file (without modification to the file) provided with the RFP. An authorized official of the firm shall sign the SF 33 and all certifications requiring original signature. An Acrobat PDF file shall be created to capture the signatures for submission.

(a) Section A Offer. The Offeror must include a cover letter providing the following information:

(1) Solicitation number;

(2) Name, address, electronic mail address, telephone and facsimile number of points of contact for the

Offeror;

(3) A statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation;

(4) Names, titles, electronic addresses, telephone and facsimile numbers of persons authorized to negotiate on the Offeror's behalf in connection with this solicitation;

(5) Name, title and signature of person authorized to sign the proposal (evidence of agents authority to sign shall be included within the proposal);

(6) Offerors DUNS Number, CAGE Code, and taxpayer ID; and

(7) Statement regarding the proposal acceptance period. The Government requires a minimum proposal acceptance period of 180 calendar days.

(b) Section B Standard Form 33 (SF 33), Solicitation, Offer and Award. The completed SF 33 shall include:

Section A Standard Form 33 (SF 33), Solicitation, Offer and Award

Section B Supplies or Services and Prices/Costs

Section G Contract Administration Data

Section K Representations, Certification and Other Statements of Offerors

9 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Section L = Instructions, Conditions, and Notices to Offerors

(c) Pursuant to the requirements set forth in DFARS 252.227-7017, Offerors are required to specifically identify Data/Software Rights

Assertions related to technical data and software deliverables. As indicated in DFARS 252.227-7017(e), an Offeror's failure to submit, complete, or sign the aforementioned Data and Software Rights Assertions with its offer may render the offer ineligible for award. In accordance with the content and formatting requirements for Data and Software Rights Assertions (set forth in DFARS 252.227-7017), the

Offeror's Data and Software Rights Assertions shall comply with the following requirements:

1) The Offeror shall not assert license restrictions on items, component, or processes themselves. The asserted license restrictions shall pertain to software or technical data that relates to items, components, or processes.

2) The Offeror's Assertions shall not include technical data or software that will not be furnished to the Government under this

Contract.

3) The Offeror shall provide a concise (but specific) description of the technical data and software deliverables that will be furnished to the Government with restrictions, rather than generically asserting license restrictions in "technical data" or "technology."

4) The Offeror is responsible for ensuring that Data and Software Rights Assertions from its subcontractors comply with the aforementioned content and formatting requirements (in accordance with DFARS 252.227-7017).

Offerors shall provide Data/Software Rights Assertions in a tabular format prescribed in DFARS 252.227-7017. However, in addition to the content and formatting requirements set forth in DFARS 252.227-7017, the Offerors Data/Software Rights Assertions table shall list technical data and software items that the Offeror intends to furnish to the Government with and without license restrictions. Thus, the Data/Software Rights Assertions table may include technical data and software items that are provided to the Government with an unlimited rights license. In the Offerors identification of technical data and software license rights, the Offeror shall use the prescribed categories of license rights referenced in DFARS 252.227-7014 and DFARS 252.227-7015 (e.g,. Limited Rights, Government

Purpose Rights, Unlimited Rights, Unrestricted Rights, or Commercial Software License Agreement).

(d) Non-Disclosure Agreements Each Offeror must submit copies of their completed non-disclosure agreements with

Radiance Technologies, as specified in paragraph D.1.c above. POC for the company is as follows:

Company POC/Email/Phone

Radiance Technologies Jennifer Dean

Jennifer.dean@radiancetech.com

256-489-8575

(e) Certification of compliance or registration of the Offerors quality system by an independent standards organization or auditor is not required. However, if the Offeror has a certified quality system, a copy of such certification may be attached with the offer in response to the solicitation as proof of system compliance.

*** END OF NARRATIVE L0001 ***

10 10