W91CRB21R0012 Amendment 6.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

1. Section L has been updated based on addtional clarif ication questions received.

2. Attached 30 FWS-I Q and A Tracker - 23 Feb 2021 has been updated to address addional clarification questions received.

1. CONTRACT ID CODE PAGE OF PAGES

U 1 19

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 24-Feb-2021

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

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

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W91CRB21R0012

X 9B. DATED (SEE ITEM 11)

11-Jan-2021

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offer 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 amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) 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 date, 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.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

24-Feb-2021

CODE

ACC - APG - W91CRB

BLDG 4310

6515 INTEGRITY COURT

ABERDEEN PROVING GROUND MD 21005-3013

W91CRB 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W91CRB21R0012

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

LIST OF ATTACHMENTS

The following documents are attahced hereto and incorprated by reference:

Attachment Number

Title

1 FWS-I Performance Specification FRP-PRF-FWSI (2 FEB 2021)

2 FWS-I ISW ICD 1.6

3 ISW Protocol Specification 4.4

4 I-MILES IWS 2 Performance Specification PRF-PT-00543, Rev B

5 Manworn HALO Assembly, Drawing 184100, Rev C

6 Mount Assembly, Drawing A3301511, Rev B

7 M16A1/A2 & M4 Bracket Assembly, Drawing A3170580, Rev B

8 ISW SolNet Property Descriptor Specification V1.4

9 ISW SolNet Protocol V1.4

10 FWS-I Security Classification Guide 13 Mar 2013

11 DD254 Contract Security Classification Specification

12 ISW Embedment Guide V1.4

13 FWS-I Failure Definition and Scoring Criteria (FDSC) 24 May 2013

14 Tool Kit, Electronic Equipment TK-105A/G

15 Modular TMDE Tech Manual

16 NVThermIP Modeling Guidance

17 NV ImageJ Instructions

18 NV 2009 Model Files

19 LSA 036 Card Block Preparation Guide

20 DD1494 Preparation Guide

21 Requisitioned Government Furnished Property- VERSION 1.3

22 Scheduled Government Furnished Property- VERSION 1.4

23 Total Evaluated Price (TEP) Matrix (29 JAN 2021)

24 TM 11-5855-343-10 Operator_2020-7-01

25 Past Performance Questionnaire

26 Small Arms Tool Kit, NSN 5180-01-559-5981

27 Army’s Automated System Safety Engineering Tool (ASSET) and electronic Hazard Tracking System (eHTS)

28 Guidance for Army’s Computerized Optimization Model for Predicting and Analyzing Support Structures (COMPASS) model

29 Quality Assurance Surveillance Plan (QASP)

30 FWS-I Q&A Tracker 23 FEB 2021

Exhibit Document Title

A Contract Data Requirements List (CDRL) 2 FEB 2021

B Data Item Descriptions (DIDs)

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS TO OFFERORS

2.1 Instructions, Conditions and Notice to Offerors (Section L)

2.1.1 Proposal Submission

2.1.1.1 General Instructions

In order to be considered for award, each Offeror shall submit its proposal IAW the following instructions which will be provided within the Request for Proposal (RFP).

Each Offeror shall submit a single, complete proposal that contains the Offeror’s best terms. Failure to adhere to these instructions may result in rejection of the offer without evaluation or consideration for award.

Offerors are cautioned that “parroting” of the technical requirements or the Statement of Work (SOW) 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.

Offerors are advised to submit any questions for clarification or explanation via email to both Peter P. Buckless, peter.p.buckless.civ@mail.mil, and Jerry Simmons, gerald.a.simmons2.civ@mail.mil.

The cutoff date for submitting questions is ten (10) calendar days after the solicitation has been posted on betaSAMgov. Note: If the 10th calendar day falls on a holiday or weekend, then it will be the first working day after the 10th calendar day. Offerors shall use Attachment 30 FWS-I Q&A Tracker for submitting questions.

The Offeror’s proposal shall remain valid for a period of 180 days from the closing date of the solicitation.

Offerors shall NOT submit any CLASSIFIED information as part of this proposal.

Offerors shall NOT include any pricing information in any section of their proposals except within Volume 1: Section B of the Standard Form 33 and Volume 3: Cost/Price.

Proposals shall be submitted in digital format as specified herein. The proposals shall be divided into five (5) volumes. Table 1 - Proposal Volumes lists the title for each volume and specifies the page limit for each volume.

Table 1 - Proposal Volumes

Volume Title Page Limit

Volume 1: Offer 45

Volume 2: Technical 100*

Volume 3†: Cost/Price NA

Volume 4: Past Performance 30*

Volume 5: Small Business 15

* Excluding annexes (see 2.1.2.2, 2.1.2.2.4, and 2.1.2.5 below) † The offer shall submit both locked and unlocked copies of CLI

2.1.1.1.1 Page Limits

The number of pages specified in the above table is the firm page limit for that volume. The Cover Page, Table of Contents, List of Figures, and Acronyms pages are not included in the page count. Any pages in excess of the limits specified will be removed and not considered part of the proposal; information contained on any excess pages will not be evaluated. Supporting documentation will not be considered in the page limits and its applicability is denoted in the paragraphs below. Supporting documentation shall be submitted as annexes to the applicable Volume. The Government will accept 11”x 17" pages to support tables, charts, and graphics: each such page will be counted as one (1) page.

2.1.1.1.2 Acquisition Source Selection Interactive Support Tool (ASSIST)

During the conduct of this acquisition, ASSIST will be used by the Government to support the proposal evaluation and source selection process. A separate tool, the ASSIST2Industry (A2I), will be used in conjunction with ASSIST to accomplish all exchanges with Offerors after receipt of proposals pursuant to Federal Acquisition Regulation (FAR) 15.306. A2I provides the ability for the Government to issue, and the Offerors to receive and respond to, all Evaluation Notices (ENs) in a secure online environment. In order to initiate the use of A2I, the Government requires the names, company titles, telephone numbers, and email addresses of two individuals that the Offeror has designated as responsible for receiving and responding to Government ENs through A2I. The designation of two individuals is for the purpose of insuring availability of one individual if the other individual is not available. The required information regarding these two individuals must be submitted with the Offeror’s proposal and included in the cover letter.

After the solicitation's closing date, the Government will establish an account in A2I for each individual identified by the Offeror that has submitted a proposal in response to this solicitation. The two individuals named by the Offeror will be authorized access to that account. Two separate, system-generated emails will be sent to each individual. One of the emails will contain the individual's A2I username. The other email will contain the individual's temporary password. Using the provided username and temporary password, each individual can then go to https://ASSIST2Industry.army.mil to access the account.

Note: The first time a user logs in, the user will be required to change the temporary password before the user can proceed to use the site.

Whenever the Government issues ENs to the Offeror through A2I, the Government's Contracting Officer will notify the Offeror through a medium independent of A2I (e.g., e-mail) that the Offeror has ENs in A2I waiting for a response. There will be no ENs in A2I until such notice is issued by the Contracting Officer.

Offerors can contact the A2I helpdesk by logging on to https://ASSIST2Industry.army.mil for any technical assistance that may be needed. The Offeror will need to have the following available:

Contractor POC Name

Telephone Number

Email Address

Procuring Contracting Officer and/or Contract Specialist name and Telephone Number

ASSIST Source Selection/Program Name

Solicitation Number

Offerors are cautioned that the system generated emails referred to above are intended for administrative purposes only. Receipt of these emails does NOT constitute the commencement of any type of exchange with the Offeror IAW FAR 15.306(a), (b), or (d) (i.e., clarifications, communications, or discussions). Also, receipt of these emails does not signify that a competitive range determination IAW FAR 15.306(c) has been made or that the Offeror’s proposal will be included in the competitive range when that determination is made. All notifications that any type of exchange with the Offeror has commenced and the Offeror has ENs available to respond to or that any notification that the Offeror’s proposal has been included in or excluded from the competitive range will be sent to the Offeror by the contracting officer independently of the A2I.

2.1.1.1.3 Digital Copies

The Government will host the digital files within ASSIST, a secure online environment. The files will be available to authorized members of the Source Selection Evaluation Board (SSEB) only. The intent is to facilitate the Government evaluation and report preparation within a protected environment.

2.1.1.1.4 File Format

Below are the acceptable file formats. Only the file formats specified are to be used.

Narrative Microsoft Word (.docx) Spreadsheets Microsoft Excel (.xlsx) Presentations Microsoft Power Point (.pptx) Project Schedule Microsoft Project (.mpp) Pictures JPEG Code V or Zemax See Par 2.1.2.2.1.1.1 NVThermIP See attachment #16 of the RFP

Note: The Offeror may opt to include an Adobe Portable Document Format (PDF) version of its proposal in addition to the formats specified above. A PDF only proposal submission is NOT acceptable and will be rejected. The only exception to this rule is Volume 1 may be in PDF format. Do not convert Section B, G, I into Word documents. Do not embed Section B, G, I into Word Documents. Volume 1 may be submitted as single PDF file if the vendor chooses.

2.1.1.1.5 Printed Bound Volumes

No printed volumes shall be accepted.

2.1.1.1.6 General Appearance

Below are parameters for formatting Microsoft Office products. The specified parameters shall be adhered

to. The intent is to facilitate the Government evaluation by having a uniform, easy to read, easy to display, and uncluttered proposal to evaluate.

Font: Arial or MS Sans Serif (All Text) Minimum Size (Narrative) 12pt Minimum Size (Spreadsheet) 10pt Minimum Size (Figures & Tables) 8pt Font Color Automatic (Body Text & Headings) Line Spacing (minimum) Single (1.0) Page Size (Narrative) 8.5” x 11” Page Size (Figures/Tables/Graphics) 8.5” x 11” or 11” x 17”

Page Margin (Word) 1” Left, fight, top, bottom Page Number Location Bottom Center Page Background Backgrounds/Themes not allowed Table Heading Shading None/ No Fill Table Cell/Row Shading None/ No Fill Table Line color Automatic Table Line Size 1 (minimum)

Proprietary information shall be clearly marked and, proposal submission documentation shall be marked

UNCLASSIFIED.

2.1.1.1.7 Compliance with Instructions

The Government will consider how well the Offeror complied with these instructions when evaluating the Offeror's capability to perform the prospective contract. The Government will consider an Offeror's noncompliance with these instructions or any attempt to take advantage of loopholes in these instructions to be indicative of the type of conduct that it may expect from the Offeror during contract performance. The Government will evaluate the Offeror's capability accordingly. Offerors are advised to ask the Contracting Officer for clarification or explanation of any part of these instructions that they do not understand.

The Government reserves the right to make an award without conducting discussions. Accordingly, initial proposals should contain the Offeror’s best terms.

2.1.1.1.8 RFP Submissions Instructions

After compiling all required information, Offerors shall submit all volumes via email to both Peter P. Buckless, peter.p.buckless.civ@mail.mil, and Jerry Simmons, gerald.a.simmons2.civ@mail.mil by the due date and time specified on betaSAM.gov. Our size limit for the email and combined attachments cannot exceed 30 MBs. As such you may need to send multiple emails that must be labeled 1 of 3, 2 of 3 etc., and include a list of documents included for each email. A reply email confirming receipt will be provided for each email received.

The subject line shall follow this example: W91CRB-21-R-0012 FWS-I Proposal / Email 1 of __ / “Your Company Name”

Proposal are required to be received by the date and time specified in betaSAM.gov. Late receipt of proposals due to issue not attributable to the Government could be deemed inexcusable. The Contracting Officer may declare the proposal late and remove it from consideration. Please leave enough time to allow for potential delays with internet speeds and reliability.

Note: Subsequent submissions, for example exchanges or updated proposals, shall be through ASSIST (see paragraph 2.1.1.1.2).

2.1.2 Specific Requirements per Volume

2.1.2.1 Volume 1 – Offer

The Offeror shall name the Volume 1 file as follows: B01_Abbreviated Company Name_Offer_FWS-I_21R0012.

Offerors shall include the following:

Standard Form 33, "Solicitation, Offer and Award," with blocks 12 through 18 completed and signed by the Offeror;

o RFP Section B, "Supplies or Services and Prices/Costs," with the Offeror’s proposed line item prices inserted in the appropriate spaces;

o RFP Section G, "Contract Administrative Data", completed by the Offeror;

o RFP Section I, "52.204-24 REPRESENTATION REGARDING CERTAIN

TELECOMMUNICATIONS AND VIDEO SURVEILLANCE SERVICES OR

EQUIPMENT (OCT 2020)," completed by the Offeror.

A statement specifying agreement with all terms, conditions, and provisions included in the RFP or any exceptions. Any exceptions or assumptions taken to the attachments, exhibits, enclosures, or other RFP terms, conditions, or documents shall be fully explained; however, any such exceptions may be grounds for the Contracting Officer to reject the proposal from further consideration in the source selection process before initial evaluation.

Identification and assertion of any and all restrictions on the Government's Use, Release, or Disclosure of technical data and computer software rights IAW DFAR 252.227-7013 and DFAR 252.227-7014.

Points of Contact information for the ASSIST tool.

A statement that the Offeror has ensured the Representations and Certifications in the System for Award Management (SAM) are current and complete. FAR 52.204-19 is incorporated by reference.

Offerors are advised that employee(s) of CACI, and NCI Information Systems may serve as advisors in the source selection process. This/these individual(s) will be authorized access only to those portions of the proposal data and discussions that are necessary to enable them to perform their respective duties. The named companies/corporations are expressly prohibited from competing on the subject solicitation. The contact information is as follows:

Company Name: CACI Technologies, Inc.

Company Address: 14370 Newbrook Drive, Chantilly, VA 20151 POC:

Ms. Elyse Wise Phone: (443) 360-6642 Email: elyse.wise@caci.com

Company Name: NCI Information Systems Company Address: 11730 Plaza America Dr, Reston, VA 20190 POC:

Mrs. Deborah Stephens Phone: 703-704-2240 Phone (c): 703-298-5768 Email: deborah.l.stephens6.ctr@usa.army.mil

In accomplishing their duties related to the source selection process, each of the above stated companies/corporations may require access to proprietary information contained in the Offerors’ proposals.

Submission of proposals without objections to the use of non-government employees from the companies referenced above shall serve as evidence of consent from Offerors for the stated employees to serve as advisors in the source selection process.

2.1.2.2 Volume 2 – Technical (Factor 1)

The Offeror shall name the Volume 2 file as follows: B01_Abbreviated Company Name_Technical_FWS-I_21R0012. The Offeror shall NOT include any pricing or cost information in this volume.

The Statement of Work (SOW) provides the Government’s overall objectives for the solicitation. Offerors shall use the SOW, the FWS-I Performance Specification and all other applicable portions of the RFP as the basis for preparing their proposals. Offerors shall ensure all requirements in these documents are addressed;

failure to do so may result in an Offeror’s removal from the competitive range.

Offerors shall organize Volume 2 – Technical into the following four (4) subfactors:

2.1.2.2.1 Subfactor 1- FWS-I Performance

The Offeror shall provide a narrative regarding the proposed system design, features, and performance of its FWS-I system. The narrative shall describe the Offeror's proposed approach to providing a product that meets or exceeds all threshold requirements identified in the FWS-I Performance Specification (PS). The narrative shall specifically address and clearly describe the Offeror's proposed approach to meeting or exceeding all Key Performance Parameters (KPPs) thresholds and any other objective requirements identified in the FWS-I PS, and shall cross- reference to the Offeror's proposed FWS-I PS (see paragraph below). Additionally, the Offeror shall provide detailed narrative regarding its design methodology, technical approach and implementation plan for the development and manufacture of the FWS-I systems, with a focus on the Offeror's approach to implementing the required user and Intra Soldier Wireless (ISW) Interfaces IAW the requirements specified in the PS. The Offeror shall describe how Modular Open Systems Architecture (MOSA) principles are incorporated in the FWS-I design to support technology updates. The Offeror shall identify any technical data that the Offeror asserts should be furnished to the Government with restrictions on use, release, or disclosure. The following FWS-I Performance elements shall be included as separate files on the Offeror’s Volume 2:

Element 1 – FWS-I Contractor’s Performance Specification (PS) The Offeror shall prepare and submit a proposed FWS-I PS with its proposal in the form of a red-lined version of the FWS-I PS provided in the RFP with all Offeror proposed revisions captured using track changes. The Offeror's changes shall be explained in the narrative (see paragraph above) and the Offeror shall not include comments embedded within the red-lined document to explain the changes. Upon Government acceptance, the proposed FWS-I PS will be incorporated into the awarded contract and shall become the governing document for contract performance (superseding the RFP version of the FWS-I PS). The proposed FWS-I PS shall be submitted as Annex A and will not be counted against the page count for the Technical Integration Volume.

Element 2 – FWS-I Optical Prescriptions to Support Performance Specification The Offeror shall prepare and submit with its proposal the complete optical prescriptions for the eyepiece lenses and objective lenses that support the Offeror’s proposed PS. The data shall be in a format (i.e., .len, .seq, .zmx) compatible with the current version of Code V or Zemax, including any associated glass catalogs required to properly analyze the file. If Code V or Zemax is not used to generate the raytrace file, a prescription listing is acceptable only if all the required data is present to accurately recreate the file in Zemax or Code V for analysis. "Black box" type files, where access to the prescription data is not permitted, are not acceptable. Files should include and be clearly labeled as "FWS-I eyepiece" and "FWS-I objective." The Offeror’s FWS-I Optical Prescriptions that support the Offeror’s proposed PS shall be submitted as Annex B and will not be counted against

Element 3 – FWS-I Range Modeling Data to Support Performance Specification The Offeror shall also submit completed NVThermIP 2009 input and output decks that support the Offeror’s proposed PS. The Offeror shall provide a narrative summarizing the results of its own range performance modeling along with supporting evidence to address the validity of values input into the models. The Offeror’s FWS-I NVThermIP 2009 input and output decks that support the Offeror’s proposed PS shall be completed IAW instructions provided in the NVThermIP Modeling Guidance, Attachment #16 of the RFP. The Offeror’s FWS-I Range Modeling Data to support the PS shall be submitted as Annex C and will not be counted against

Element 4 - FWS-I Frequency Allocation Application The Offeror shall submit for informational purposes a preliminary stage two DD1494 application for equipment frequency allocation for spectrum certification for the FWS-I as part of the Offeror’s proposal.

If the offeror's proposed wireless chipset and antenna already have approved spectrum certification, the vendor shall include the model and part number for both the ISW module and antenna in lieu of a new DD1494. If there is a discrepancy in Part Number/model compared to PdM SMS records, the Government will require the vendor to submit a DD1494 for clarification. If required, the Offeror’s FWS-I preliminary stage two DD1494 shall be submitted as Annex D and will not be counted against the page count for the Technical Integration Volume.

Element 5 - Contractor Test Results The Offeror may submit results from contractor or independent testing to support its product performance claims. The contractor test results shall be submitted as Annex E and will not be counted against the page count for the Technical Integration Volume.

2.1.2.2.2 Sub-Factor 2 - Integrated Logistics

The Offeror shall provide a narrative regarding the approach and methodology for assuring all FWS-I logistics efforts and deliverables meet contractual and program schedule requirements, with the purpose of ensuring that the FWS-I can be safely operated, trained, provisioned, transported, supported, and disposed of as necessary. The narrative shall discuss in detail the integration of logistics into the design, development, and production of the FWS-I systems and the delivery and review activity cycles for all deliverables.

The Offeror shall provide a narrative description of the proposed maintenance concept. The narrative shall describe the Offeror’s approach and methodology for organic field and sustainment-level maintenance which may include the use of the CECOM Regional Support Centers. The narrative shall identify the parts/assemblies that will be provisioned as spares and the level (field or sustainment) at which each part/assembly will be replaceable. The narrative shall also explain the rationale and analysis that led to selection of the proposed maintenance concept.

The Offeror shall include a narrative discussion for the establishment of a configuration management program, explaining how the program, when implemented, will establish, confirm, and ensure positive control of the product baseline, and the development and the delivery of Interface Control Drawings (ICDs) for the system and all spare/repair components.

The Offeror shall include narrative describing the warranty offered for FWS-I systems and its approach, during the warranty period, to repair or replace, at no cost to the Government, any FWS-I system, and related spare parts that fails under normal operations, while in storage, or during transportation. The Offeror shall discuss its approach and methodology to providing a replacement system no later than 10 business days upon receipt of the failed unit.

2.1.2.2.3 Sub-Factor 3 - Quality Assurance (QA)

The Offeror shall provide a narrative describing its overall QA organization and process, as well as its process for quality validation. Quality validation is comprised of the Offeror's overall quality program for this effort to include QA structure and its integration into the organization. The Offeror shall address all aspects of the QA section of the SOW in its proposal. The following QA elements shall be included as separate files on the Offeror’s Volume 2:

Element 1 - Test Plans The Offeror shall prepare and submit draft test plan(s) for Contractor Production Qualification Test (PQT-C) with its proposal IAW the SOW that provides the approach for assuring the FWS-I meets the product requirements. The Offeror shall use the Qualification Validation Matrix (QVM) provided in Section 4 of the FWS-I PS as the baseline for establishing the sample plan, sample size, and test method. The Offeror shall also include a proposed Environmental Stress Screening (ESS) profile designed to effectively reduce/eliminate workmanship and infant mortality type defects of the system. The test plans shall be submitted as Annex F and will not be counted against the page count for the Technical Integration Volume.

Element 2 - Reliability Program Plans (RPPs) The Offeror shall prepare and submit draft RPPs for FWS-I with its proposal IAW with the SOW which shall identify the planned activities to ensure the reliability requirements are achieved. The RPP shall address the management and organizational structure of personnel responsible for conduct of reliability activities, resources required to implement the plan, detailed descriptions of all planned reliability activities and schedule for completion, process for documentation and coordination with the customer, the plan to flow reliability down to subcontractors and suppliers, and how the Offeror ensures that reliability activities are an integral part of systems engineering. The Offeror shall identify the primary drivers of the overall system reliability and describe plans to mitigate the reliability risks. The Offeror shall describe how it proposes to monitor, assess, and report reliability data and findings during the program. The Offeror shall provide a reliability prediction/allocation to the Line-Replacement-Unit level for the FWS-I. The Offeror shall address the planned reliability demonstration, to include sample size, number of planned test hours, description of the test profile and environments, operational checks to be performed, and facilities required. The draft RPPs shall be submitted as Annex G and will not be counted against the page count for the Technical Integration Volume.

2.1.2.2.4 Sub-Factor 4 - Program Management

The Offeror shall provide a narrative regarding its proposed approach towards managing the effort defined in the RFP. The narrative shall discuss organization and efforts towards planning, monitoring and controlling program costs, schedule and adherence to SOW and technical performance requirements. The narrative should address the proposed program management structure, to include providing a single point of contact for program oversight, teaming arrangements and key subcontractors, key leadership, roles and responsibilities. The Offeror shall discuss plans to provide personnel with the required skills and expertise to execute the contract, to include required security clearances IAW the DD254 Contract Security Classification Specification, Attachment #11 provided with this RFP. The Offeror shall discuss its strategy for producing the FWS-I, to include manufacturing and testing capabilities and capacity to meet the contract requirements. The Offeror shall discuss its safety program for ensuring that all potential personnel and environmental hazards associated with operation, maintenance and disposal of the FWS-I are identified, assessed and mitigated to a level acceptable to the Government. The following Program Management elements shall be included as separate files on the Offeror’s Volume 2:

Statement of Work (SOW) to Work Breakdown Structure (WBS) Cross-reference The Offeror shall provide a cross-reference between the SOW and the Offeror’s WBS. For guidance on WBS content and format, Offerors may refer to MIL-STD-881. This cross reference for the FWS-I shall match the cross-reference provided in the Cost Volume, but shall NOT contain any cost information. The cross-reference shall be submitted as Annex H and will not be counted against the page count for the Technical Integration Volume.

Integrated Program Master Schedule (IPMS) The Offeror shall prepare and submit an initial IPMS with its proposal IAW the SOW. For guidance on IPMS content and format, Offerors may refer to the description of Format 6 within DI-MGMT- 81861. The activities and tasks defined should be sufficient to account for the entire program under contract, and as a minimum, integrate all required data items, testing, hardware deliverables, and major contract program events/reviews, and program events requiring Government participation.

The IPMS shall reflect all deliveries being made on a business day. The schedule shall integrate all efforts, to include major subcontracts. The IPMS shall be submitted as Annex I and will not be counted against the page count for the Technical Integration Volume and is not limited in the page size.

Risk Management/Mitigation Plan The Offeror shall prepare and submit an initial integrated Risk Management/Mitigation Plan with its proposal IAW the SOW. For guidance on the content and format of the Risk Management/Mitigation Plan, Offerors may refer to DI-MGMT-81808 paragraph 2.3.a through 2.3.f. The plan should describe the Offeror’s approach to documenting, tracking, and managing areas of program risk during the life of the contract. The plan shall be submitted as Annex J and will not be counted against the page count for the Technical Integration Volume.

Production Manufacturing Plan (PMP) The Offeror shall prepare and submit an initial FWS-I PMP with its proposal IAW the SOW. The plan should cover proposed manufacturing layout, methods, tools, instrumentation, test equipment, material, processes, and manpower required. The plan shall include discussion of initial monthly production rate, normal monthly production rate (based on one shift, operating eight hours a day, and five days a week), minimum monthly economical rate, and maximum sustainable monthly production capacity, maximum surge production capacity, and maximum duration of surge production. The plan shall discuss ramp up activities and lead times required to achieve normal, maximum, and surge production rates. The plan shall discuss the contractor's existing manufacturing facilities and detail plans to increase capacity if required. The plan shall discuss the use of subcontractors to provide components and/or subassemblies if applicable. The Offeror must provide sufficient narrative to enable an evaluation of the contractor's ability to produce the proposed FWS-I designs at the production rates proposed. The PMP shall be submitted as Annex K and will not be counted against the page count for the Technical Integration Volume.

Each subfactor has specific content requirements. Offerors may add additional information in the proposal, but to be fully compliant with the solicitation instructions, proposals shall fully address the specific requirement for each subfactor as specified herein.

As a whole, the technical volume must address all requirements of the SOW, the FWS-I Performance Specification, and all applicable portions of the RFP.

Annexes to the Technical Volume (not counted towards the page limit) are listed in Table 2:

Table 2 - Section /Annex List

Sub-Factor 1 FWS-I Performance

Sub-Factor 2 Logistics

Sub-Factor 3 Quality Assurance (QA)

Sub-Factor 4 Program Management

Annex A Performance Specification

Annex B Optical Prescriptions to Support Performance Specification

Annex C Range Modeling Data to Support Performance Specification

Annex D Frequency Allocation Application

Annex E Contractor Test Results

Annex F Test Plans

Annex G Reliability Program Plan

Annex H SOW to WBS Cross-reference

Annex I Integrated Program Master Schedule

Annex J Risk Management/Mitigation Plan

Annex K Production Manufacturing Plan

2.1.2.3 Volume 3 – Cost/Price (Factor 2)

The Offeror shall name the Volume 3 file as follows: B01_Abbreviated company name_Price_FWS-I_21R0012.

Price proposal information shall only be included in Volume 1 Section B and Volume 3 and not within any other volume of the proposal.

Offerors shall submit the following for this Volume:

1) Each Offeror shall submit a signed SF Form 33, a completed and totaled Section B, and a completed

Attachment #23 "Total Evaluated Price (TEP) Matrix" as part of its cost/price proposal, Volume 3.

The Offeror’s proposed step ladder unit prices will be incorporated as ‘Not to Exceed’ ceiling prices in the awarded contract.

2) In accordance with FAR 9.104-1 (a), offerors shall provide documentary evidence supporting the offeror’s possession of, or ability to obtain, adequate financial resources in order to perform a potential contract borne from this solicitation.

3) Offeror shall provide documentary evidence which supports the adequacy of its purchasing system in accordance with DFARS 252.244-7001.

4) Offeror shall submit sufficient detail to demonstrate the balance, reasonableness/realism for their proposed costs. If an offeror’s unit prices appear unbalanced, when comparing them from quantity range to quantity range or ordering period to ordering period, the offeror will be requested to provide documentation, including calculations and supporting rationale, explaining the apparent unbalanced pricing.

5) The Section B shall contain a bottom line total. Offerors are highly encouraged to show and explain the build-up of costs including build rate tables and estimating formulas used, in their submissions of spreadsheets. Spreadsheets shall not be linked unless the linked data is provided with the spreadsheets. Excel spreadsheets shall be submitted in both a locked and unlocked format

6) In addition to providing the above information, each Offeror is to propose its unit prices for

CLINs 0003-0012 in the step-ladder weighted average pricing format shown in Attachment #23 of this solicitation in electronic formats. Each Offeror is to enter the appropriate ranges up to the maximum order quantity and enter the appropriate corresponding unit prices for the respective ranges. The computed weighted average price for CLINs 0003-0012 each year, and in total, will be the evaluated price for price reasonableness.

7) Offerors shall not propose prices for the Not Separately Priced (NSP) CLINs 0014, 0015, 0019, 0020, 0022, and 0032 (or Reserved NSP CLINs 0033, and 0040). The cost of these CLINs shall be amortized in the pricing provided under CLINs 0001-0013.

8) Each prime Offeror shall conduct the price and/or cost analysis necessary to determine the reasonableness of intercompany or subcontractor proposals IAW all the provisions of FAR 15.404-

3. If an Offeror is unable to conduct price/cost reasonableness of a subcontractor, the Offeror shall provide a statement why and ensure that the required data is provided to the Contracting Officer directly by the subcontractor.

9) Quantitative factors that impact cost shall be addressed in both the cost and technical volumes.

Specifically, proposed material quantities, labor hours, and other quantitative elements should be addressed in both the cost and technical volumes to allow for Government cost realism evaluation of material and labor IAW FAR 15.404-1(d)(3). However, any cost data, including proposed direct and indirect rates and factors, shall NOT be included in any other volume other than the cost volume. Cost data shall only be included in the cost volume and not any other volume.

10) As part of the technical and cost volumes each Offeror shall provide a cross-reference between the SOW and the Offeror's WBS. The cross-reference shall also include a cross- reference to the proposed CLIN/SLIN amounts in the cost volume.

11) Since this effort includes a potential CPFF requirement, each Offeror shall also provide documentation including any DCAA/DCMA reports as to the adequacy of its accounting system IAW FAR 16.301-3(a)(3). Each Offeror shall also provide documentary evidence as to the adequacy of its purchasing system IAW DFAR 252.244-7001. Each offer shall also provide a statement as to its financial capability as to the performance of this requirement IAW DFAR 253.209-1. For interdivisional subcontractor proposals exceeding $500,000.00 detailed support shall be provided showing the nature and extent of the work involved, proposed contract type (i.e. CP, CPFF, T&M, etc.), as well as the details necessary to enable the Government to evaluate the proposed costs. As stated above IAW FAR 15.404-3(b), the prime Offeror shall conduct and provide evidence of the reasonableness of proposed subcontractor costs. If a subcontractor declines to provide certain sensitive proprietary data (i.e. rates, etc.) directly to the prime to substantiate reasonableness and realism, the prime shall direct that the subcontractor provide the data to the Government. If interdivisional or subcontracts are awarded on a cost reimbursable basis evidence as to the FAR 16.301-3(a)(3) adequacy of the interdivisional/subcontractor accounting system and purchasing systems will also have to be provided for evaluation.

The following Normalized CLINs table identifies CLIN where the pricing has been normalized. Offerors shall not propose any amounts for these CLINs. Offerors shall include in Section B the Government provided normalized amounts. These CLINs are normalized for evaluation purposes, no cost analysis/cost realism will occur until after a basic award is made and a delivery order need is identified for work to be performed under those CLINs.

Table 3 – Normalized CLINs

0013 Foreign Military Sales

0037 Foreign Military Sales (FMS) Technical Manuals / (CDRL G001)

0038 Foreign Military Sales (FMS) Training Materials / (CDRL G002)

0039 Foreign Military Sales (FMS) Training Materials / (CDRL G003)

0041 FWS-I Software Updates

0042 FWS Technology Insertion

0043 FMS Maintenance Support

Adequate competition is anticipated in response to this solicitation therefore, IAW FAR 15.403- (1)(b)(1) certified cost or pricing data is not required. Further, IAW FAR 15.403-3, data other than certified cost or pricing data is required. However, if it is determined by the Contracting Officer that adequate competition does not exist, the Government reserves the right to request and evaluate certified cost or pricing data in a format prescribed in FAR 15.408, Table 15-2 prior to award. In accordance with FAR 15.403-5(b), the Contracting Officer may specify the format of cost or pricing data or data other than certified cost or pricing data.

2.1.2.4 Volume 4 - Past Performance (Factor 3)

The Offeror shall name the Volume 4 file as follows: B01_Abbreviated Company Name_Past Perf_FWS-I_21R0012

The information gathering process may include telephone interviews and questionnaires, sent to all Points of Contact (POCs) listed in the Offeror’s proposal.

Offerors are advised that the Government may utilize past performance information from sources other than those identified by the Offeror. Further, if an Offeror’s firm is divided into severable segments, the Government will only evaluate the past performance of those segments of the firm that that will actually perform the work.

The Offeror shall submit a description of a minimum of three (3) Government contracts for the prime and one (1) contract for major and/or critical subcontractors, with a per contract estimated dollar value of $5M or greater, in performance during the past three (3) years that are relevant to the efforts required by this solicitation. The SSEB will evaluate Past Performance relevancy first to establish that the Offeror demonstrates that it meets the relevancy requirements of the subject solicitation. Any Offeror that does not receive a rating of acceptable for relevancy will not be further considered for award. Relevant contracts are defined below:

Relevant: Present/past performance effort involved development and/or production contracts of man-portable electro-optical device(s) incorporating image intensification and/or thermal sensors with similar scope and magnitude of effort and complexities this solicitation requires.

Not Relevant: Present/past performance effort involved little or none of the scope and magnitude of effort and complexities this solicitation requires. Contracts completed more than three (3) years prior to the RFP.

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 shall discuss, in detail, the role performed by such persons in the prior contracts cited. Information shall 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.

Volume 4 shall be organized into the following sections:

2.1.2.4.1 Section 1 - Relevant Contract Past Performance Information

For each contract that the Offeror claims as relevant past performance information, the Offeror shall include the following information in the following format:

Contract Description o Offerors shall make clear within the submitted reference whether their role in the performance of the contract was the Prime contractor or a Subcontractor;

o Contractor’s address, place of performance, CAGE Code and DUNS number;

o Subcontractors’ addresses, place of performance (if different from their address); CAGE Code and DUNS number.

o Name of the Government contracting activity and the name, telephone number; address and e-mail address for the Government Contracting Officer, Government Administrative Contracting Officer (if different than Government Contracting Officer), and Government technical representative;

o Contract Number (to include delivery order numbers) and Contract Type;

o Total Contract Amount (Total quantity ordered and total dollar value);

o Contract Awarded Price (initial and final) and Delivery Schedule (initial and final);

o Contract Performance Assessment Reporting System (CPARS) information shall be submitted for the contracts referenced (if available);

Relevance to Solicitation Requirements

The Offeror shall provide a narrative explanation describing the objectives achieved and detailing how the contract being described is relevant, as defined above, to the requirements of the solicitation.

Performance Confidence Assessment

The Offeror's narrative for each contract shall provide information that addresses all of the questions and information that is requested in the attached Past Performance Questionnaire, to include narrative addressing Items 1-7 in Part III of the Questionnaire:

o Conforming to specifications and standards of good workmanship o Adherence to contract schedules, including the administrative aspects of performance o Maintaining program execution within contract cost o Ability to resolve technical and manufacturing problems quickly and effectively o Establishing and maintaining adequate management of subcontractors o Business-like concern for the interest of its customers o Meeting program quality objectives (e.g. producibility, reliability, maintainability, inspectability, testability, system safety and controlled the overall manufacturing process)

For any contracts that did not or do not meet original cost, schedule or performance requirements, the Offeror shall provide a detailed explanation of the reason(s) for the shortcomings and any management actions taken to resolve the issues, as well as to actions to avoid recurrences. The Offeror shall list each time the delivery schedule was revised and provide rationale of why the revision was necessary. The Offeror shall also provide a copy of any cure notices or show-cause notices received on each contract listed and a description of any corrective action taken. The Offeror shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.

Offerors are cautioned that the Government may use data provided in the Offeror's proposal and data obtained from other sources, to include the Contractor Performance Assessment Reporting System (CPARS). Since the Government may not necessarily interview all of the sources provided by the Offerors, it is incumbent upon the Offeror to explain the relevance of the data provided. The Offerors are reminded that while the Government may elect to consider data obtained from other sources, the burden of proving acceptable past performance rests with the Offerors. The Offeror will provide documentation to demonstrate the lowest possible performance risk. The Offeror must explain the relevance of the data provided and whether the data is current, accurate and complete.

Note: CPARS data, Cure Notices, and Show-cause Notices do not count toward the Volume 4 page limit.

2.1.2.4.2 Section 2 – Subcontracts

The Offeror shall provide an outline of how the effort required by the solicitation will be assigned for performance within the contractor's corporate entity and among the proposed subcontractors. Offeror's shall provide the same information required in Section 1 above for any proposed major subcontractor.

The Government requires prospective subcontractor consent before disclosing past performance information for prospective subcontractors to the Offeror during a potential source selection exchange. Therefore, for any subcontractor cited as a reference POC, the Offeror shall discuss this requirement with the subcontractor and request consent, which, if granted, shall be submitted in the form of a letter which cites the solicitation number and reference contract number and, provides a written statement providing permission for the Government to discuss the company’s past performance information with the prime contractor, if necessary, during the source selection process.

In the event the Offeror does not submit a consent letter for a subcontractor or a subcontractor denies consent, the Government will only discuss past performance information directly with the subcontractor being reviewed. If a subcontractor has adverse past performance information, an Offeror may be notified of the situation but will not be provided details related to the issue.

2.1.2.4.3 Section 3 - Submission of Past Performance Questionnaire

The Past Performance Questionnaire, provided as Attachment #25 of the RFP, is required for evaluation.

The Offeror shall send the questionnaire electronically to the points of contact (POCs) for each contract/subcontract cited. Instructions are included with the questionnaire requesting that each respondent POC complete its response and send it electronically directly to the Procuring Contracting Officer (PCO) responsible for this acquisition no later than 30 days after release of the RFP. The questionnaire is NOT to be submitted back to the Offeror, either as an original or as a copy. Any response submitted back through the Offeror for submission to the PCO will not be evaluated. The POC should send completed questionnaires via electronic mail to gerald.a.simmons2.civ@mail.mil and peter.p.buckless.civ@mail.mil. For this section, the Offeror shall provide a list of the organizations and POCs, to include telephone numbers and e- mail addresses to whom the questionnaires were provided.