W91CRB-15-R-0024-0003.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

A. Amendment 0003 updates the proposal due date, updates solicitation documentation, and provides Government responses to industry questions received as of 16 September 2015. Questions received after 16 September 2015 shall be addressed in a subsequent amendment.

B. Army Contracting Command Aberdeen Proving Ground (ACC APG) POC is Andrew Mitchell: phone (410) 306-2765 or e-mail Andrew .C.Mitchell1.civ@mail.mil.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 83

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

16C. DATE SIGNED

BY 17-Sep-2015

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 W91CRB-15-R-0024

X 9B. DATED (SEE ITEM 11)

31-Aug-2015

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

17-Sep-2015

CODE

ACC - APG - W91CRB

4310 BOOTHBY HILL AVENUE

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:

W91CRB-15-R-00240003 17 September 2015

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

Q AND A: AMENDMENT 0003

W91CRB-15-R-0024 Amendment 0003: QUESTIONS AND ANSWERS Question #1 Reference Family of Weapon Sights-Crew Served (FWS-CS) Variant Product Description Final RFP Release, paragraphs 3.2.2 Ancillary Items and 3.3.8.9.1 Electromagnetic Interference (EMI) Requirements. All "conducted" EMI requirements have been removed from the requirement even though systems may be expected to operate on vehicle power. Many "conducted" test are specifically oriented for power cable installations; we are unsure how the optional need for vehicle power should be interpreted. Are cabled systems not required to pass "conducted" testing?

Please clarify how the optional need or use of vehicle power impacts the FWS-CS. Please clarify where cabled systems do not require "conducted" testing.

Government Response to Question #1 The PD paragraph that governs the sight's vehicle power requirements is 3.3.5.4 External Power (see Question #2 for additional information). PD Paragraph 3.3.8.9.1 Electromagnetic Interference (EMI) Requirements has been updated for this amendment to include the following requirement when connected to vehicle power:

"Additionally, the FWS-CS shall exhibit neither damage nor degradation of performance, nor susceptibility and shall comply with CE102, CS101, CS114, CS115, CS116 of MIL-STD-461F when powered through the vehicle power cabling."

Question #2 Reference Family of Weapon Sights-Crew Served (FWS-CS) Variant Product Description Final RFP Release, paragraph 3.2.2 Ancillary Items. It is unclear what the requirements are that specifically require vendors to submit vehicular cables and/or the characteristics of these cables (e.g. length). Our interpretation is that any system that can handle "dirty" vehicle power as an input via IO cable does not require a cable. Is this correct? Please confirm that a cable is only required if the weapon sight can not use the direct vehicle "dirty" power.

Government Response to Question #2 The PD paragraph that governs the sight's vehicle power requirements is 3.3.5.4 External Power. It requires that the sight be able to accept vehicle power through either the battery compartment or I/O port and power the remote simultaneously. If the offeror's solution includes power conditioning in the sight to accept 'dirty' vehicle power directly through the I/O, a vehicle cable does not need to be offered, provided the remote can be used simultaneously. If the offeror chooses to include power conditioning in a cable to the I/O or through the battery compartment, or if the offerer requires a y-split in order to simultaneously connect the wired remote and the vehicle cable, then these cables (referred to as "Vehicle power cabling" in 3.2.2) shall be provided as part of the FWS-CS kit.

Question #3 Reference Family of Weapon Sights-Crew Served (FWS-CS) Variant Product Description Final RFP Release, paragraph 3.3.1.3.7 I-LRFAlignment, Table 4.6-1. Inspection Matrix for FWS-CS. No entry in Table 4.6-1 exists for the I-LRFAlignment paragraph that states test frequency/method. Where should an offeror detail this activity?

Please update Table 4.6-1 and add a line that directs the necessary test methods, frequency, etc.

Government Response to Question #3 The omission was an error. A line has been added to the PD in Tables 4.6-1 and 4.6-3 for 3.3.1.3.7 I-LRF Alignment to specify test method and frequency.

Question #4 Reference Family of Weapon Sights-Crew Served (FWS-CS) Variant Product Description Final RFP Release, paragraph 3.3.3.14 Carrying Case and others dependent on this requirement. This paragraph states, “The FWS-CS shall have a soft, water resistant carrying case that keeps the FWS-CS secure and protected. The case shall provide storage space for the FWS-CS (with objective lens cover, eyecup, and mount assembly), one spare loaded battery cassette and cover, remote (including base cable and cable extension, if wired), the vehicle power cabling (if required), HMD, operator’s manual, lens cleaning material, and quick reference card.” The carrying case is required to have room for the cable but it is unclear how large (length) this cable is required to be. Does the Government have a required cable length? Please update the specification and identify the required cable length.

Government Response to Question #4 The wired remote cable, including base cable and cable extension, has a specified length in paragraph 3.3.3.7.11.

The vehicle power cabling, if required (see answer to question #2), shall conform to paragraph 3.3.5.4. The PD paragraph 3.3.5.4 has been modified to include a vehicle cable length of 18 inches and a ruggedized, military standard end connector (e.g. the Fischer Core Series DBPU/DBPE 102 A059 or other connector as agreed upon by the IPPT) for the vehicle power cabling.

Question #5 Reference Family of Weapon Sights-Crew Served (FWS-CS) Variant Product Description Final RFP Release, paragraph 3.3.3.7.10.1 Weapon Sight Display Standby Mode. This paragraph states, “When the wireless radio is turned on and actively transmitting video to the HMD, the weapon sight display shall go into standby to conserve power. Upon activation of the eyecup while video is being transmitted to the HMD, the weapon sight display shall return to full-on (3.6.11) capability within 1.5 seconds. The display shall be returned at the same brightness setting prior to being placed into weapon sight display standby mode.” The existing requirements for standby and emergency modes imply depression sensing techniques that consequently require power. Other techniques proven through past Army qualified programs (17um LWTS, FWS-I) do not require depression sensors and instead enables the soldier to control display illumination via button presses on the keypad. This method also lowers the overall energy use and extends the battery lifetime. Is it acceptable to use other methods of standby and emergency mode controls as compared to eyecup depression? Please change the requirement to allow other methods along with eyecup depression as the method for enabling standby and emergency modes such as, "Upon activation of the eyecup or button manipulation by the user while video is being transmitted to the HMD, ..."

Government Response to Question #5 The other programs cited (FWS-I and 17um LWTS) were for clip-on systems. The intent for FWS-CS (a stand-alone system) is to have the weapon sight display standby mode operate as it did on the stand alone MWTS and HWTS, where activation of the eyecup brings the weapon sight out of standby.

Question #6 Reference Family of Weapon Sights-Crew Served (FWS-CS) Variant Product Description Final RFP Release, paragraph 3.3.5.3.2 Digital Display Video Interface. This paragraph states, “A wireless external interface shall be provided to access the digital data and provide a wired output of the video. The digital video output for display from the external interface shall be equivalent in content to the data presented in the display and use the High-Definition Multimedia Interface (HDMI).” In the past, digital output has been used for evaluating the performance of the camera system (noise, uniformity). The wireless interface definition allows lossy compression which will impact these measurements. Is this interface to be used only as a demonstration tool only and not used for performance measurement? Please confirm this interface is only used as a demonstration tool to replicate HMD video.

Government Response to Question #6 The paragraph cited, 3.3.5.3.2 Digital Display Video Interface, takes the place of the old analog video requirement for video out for demonstration and government alignment testing purposes over environmental conditions. It would be used for government tests, e.g. the GDT testing performed at WSMR, where video is used for alignment or for monitoring of the image quality during testing. The Digital video used for performance measurements (Noise, SITF, MTF, Uniformity, etc.) is governed by paragraph 3.3.5.3.1 Digital Measurement Video Interface.

Question #7 Family of Weapon Sights-Crew Served (FWS-CS) Variant Product Description Final RFP Release, paragraph

3.3.5.3.2 Digital Display Video Interface. This paragraph states, “A wireless external interface shall be provided to access the digital data and provide a wired output of the video. The digital video output for display from the external interface shall be equivalent in content to the data presented in the display and use the High-Definition Multimedia Interface (HDMI).” The external interface is not defined as part of the ancillary items (3.2.2) and therefore it is unclear how many are to be delivered. How many of these "digital display interface boxes" are required? Please clarify the delivery requirements for the "digital display interface boxes".

Government Response to Question #7 The external hardware interfaces outlined in Product Description paragraphs 3.3.5.3.1, 3.3.5.3.2 and Note 18 in Table 4.6-1 Inspection Matrix for FWS-CS are not ancillary items to the FWS-CS kit. These hardware interfaces (equipment or interface boxes), if required per PD paragraphs 3.3.5.3.1 and 3.3.5.3.2, are to facilitate receiving the required digital video to conduct lab measurements and perform Government testing during EMD and LRIP. SOW paragraph 3.3.2.2.2 Measurement Interface Equipment requires 5 sets of equipment to be delivered in EMD and 5 in

LRIP.

Question #8 Reference Family of Weapon Sights-Crew Served (FWS-CS) Variant Product Description Final RFP Release, paragraph 3.3.6.4.5 Multiple HMD Links. This paragraph states, “The HMD shall have a section leader mode that provides the ability to associate the section leader’s HMD with multiple FWS-CS weapon sight transmitters. The FWS-CS HMD shall be configured for section leader operation before a mission and the HMD shall only receive video from pre-associated FWS-CS systems. This operation shall be passive and shall not communicate with the weapon sight transmitter to resend packets if data loss occurs during transmission. The HMD shall automatically display the strongest signal among the associated weapon sights.” Does the Government intend for the section leader to be the only HMD linked to the FWS-CS systems or is the intent for the leader to be able to see the video already being received by another primary HMD associated with the sight? Is the intent for two HMD's to see the same weapon sight video? If the intent is to have the section leader see the same HMD video as the weapon sight operator's HMD video what is the procurement path for the section leaders HMD and what are the anticipated volumes? Please clarify if a section leader HMD with a different configuration is allowed? Please clarify that the section leader HMD is a 2nd HMD receiving the data of a previously paired Weapon Sight/HMD pair.

Government Response to Question #8 The intent is for the section leader to be able to view the same video seen by the Soldier through his HMD. The capability is intended to be provided on every HMD fielded as part of the FWS-CS kit. The capability is intended to be accessed through a section leader's mode available on every HMD. The procurement path for a separate HMD only for the section leader is still TBD.

Question #11 Reference Section C, paragraph 3.3.2.2.1 Thermal and Visible Color Camera Sensor. This paragraph states, “At the conclusion of FAT, the Contractor shall maintain not less than five (5) each Contractor-owned FWS-CS production configured systems as standards, one of which will be maintained at the Government’s location for the purpose of demonstrations.” For costing, which CLIN is this requirement associated with? Please update the RFP and identify the appropriate CLIN.

Government Response to Question #11 This requirement is not a separately priced line item and should be captured in the offeror's system production unit pricing.

Question #12 Reference Section J - Attachment 7 TEP, All Spares Worksheets, formula ' TEP Value =SUM(I24,I31)*('Step Ladder Pricing Worksheet'!C41/17). All of the spares TEP calculation include the amount divided by 17. As it impacts the TEP what is the Government's intent when dividing by 17? Please clarify the intent for the division by 17 for all the spares TEP in all PYs for CLIN0007.

Government Response to Question #12 The computation for Spares Step Ladder Pricing was derived based on historical spares procurement information from similar programs.

Question #16 Reference Section L - Instructions, Conditions and Notices to Bidders, paragraph 1.1.1.1.6 General Appearance.

The instructions for table formatting require:

Table Heading Shading None / No Fill Table Cell/Row Shading None / No Fill Section J Attachment 1 includes tables with shading. Should the offeror remove shading from all Annexes? Or is shading acceptable? As demonstrated with the attached word files with tables, black and white tables have proven difficult to read for evaluation with multiple columns of complex text. Will the Government please allow for shaded table headings and alternate table row shading to facilitate easier review? Please allow shading in tables in the proposal in 1.1.1.1.6, with the change, "Table Heading Shading allowed Table Cell/Row Shading allowed" Government Response to Question #16 Section L, paragraph 1.1.1.1.6 General Appearance has been updated as follows to allow shading only for table headings and alternate table rows/columns:

"Table Heading Shading Allowed Table Cell/Row Shading Allowed for Alternating Rows/Columns"

Question #17 Section L - Instructions, Conditions and Notices to Bidders, paragraph 1.1.2.2.1.1.1 FWS-CS Optical Prescriptions to Support Performance Specification. This paragraph states, “The offeror shall prepare and submit the complete optical prescriptions for the eyepiece and objective lenses that support the offeror’s proposed performance specification. 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.” Zemax as a ".zar" archive file has all inputs rolled into a single file. Is this an acceptable file for delivery for describing optical prescriptions.

http://www.zemax.com/products/opticstudio/user-interface/archive-files Please update 1.1.2.2.1.1.1 to enable submissions of ".zar" files, with the change, "The data shall be in a format (i.e., .len, .seq, .zmx, .zar) compatible with the current version of Code V or Zemax, …" Government Response to Question #17 Yes, a .zar file is acceptable for this submission provided it meets the remaining requirements of the paragraph, "current version of Code V or Zemax, including any associated glass catalogs required to properly analyze the file."

Section L has been amended to include .zar as an acceptable file format.

Question #18 Reference Section L - Instructions, Conditions and Notices to Bidders, paragraph 1.1.2.2.2 Section 2 – FWS-CS Sample Hardware. The RFP wording states (based on sample hardware evaluation), “…LWIR Camera/Sight with actual 12μm class or smaller (e.g., 10µm) FPA* (format, pixel size and supplier) proposed and approximate objective lens (HFOV ± 1 degree);…” Please change the HFOV +/-1 deg TO +/- 2 degrees.

Government Response to Question #18 The HFOV requirement in Section L and Section M on the sample hardware has been revised to +/- 2 degrees. Any differences between the sample hardware and the proposed system shall be described in the sample hardware narrative and "the Government verified sample hardware performance will support the Government's evaluation of the technical maturity of the sample hardware against the EMD performance goals", per Section M.

Question #19 Reference Section C, Appendix A, paragraph 6.2.4, which states, “The TMDE shall have alignment equipment including a minimum of two black bodies, calibrated cameras, a collimator, and LRF imaging to enable/verify thermal, visible and LRF alignment.” Since this requirement calls for a specific list of TMDE equipment; can alternative equipment be substituted if that substitute equipment satisfies the objective and are enable/verify thermal, visible and LRF alignment? Please modify the requirement to allow equipment that meets the requirement.

Government Response to Question #19 Paragraph 6.2.4 is specific to the alignment requirement. The other testing required is outlined in the other Appendix A paragraphs. Section C, Appendix A, 6.2.4 has been modified to read, "The TMDE shall have equipment to enable/verify thermal, visible and LRF alignment (e.g. black bodies, calibrated cameras, collimator, and LRF imaging)."

Question #23 Reference Section J, Attachment 5 - DD 254, Page 6, Item 6: Marking of FOUO information, which states, “An unclassified document containing FOUO information will be marked “FOR OFFICIAL USE ONLY” at the bottom of the front cover (if any), on the first page, on each page, on the back, and on the outside of the back cover (if any).

No portion marking will be shown.” This implies that every page of an unclassified document containing FOUO information shall be marked FOUO, irrespective of whether there is any FOUO information on a page. With reference to Army Regulation 380-5, Chapter 5, shouldn't the DD 254 phrase “on each page” be revised to state that:

'Pages of the document which contain FOUO information will be marked “FOR OFFICIAL USE ONLY” at the bottom of that page?' Government Response to Question #23 Army Regulation 380-5, paragraph 5-3 Marking requires the following:

a. Information which has been determined to qualify for FOUO status should be indicated, by markings, when included in documents and similar material. Markings should be applied at the time documents are drafted, whenever possible, to promote proper protection of the information.

b. Wholly unclassified documents and material containing FOUO information will be marked as follows:

(1) Documents will be marked "FOR OFFICIAL USE ONLY," in letters larger than the rest of the text, where practical, at the bottom of the front cover (if there is one), the title page (if there is one), the first page, and the outside of the back cover (if there is one).

(2) Pages of the document which contain FOUO information will be marked "FOR OFFICIAL USE ONLY" at the bottom.

(3) Material other than paper documents, for example, slides, computer media, films, etc., will bear markings which alert the holder or viewer that the material contains FOUO information.

(4) FOUO documents and material, transmitted outside the Department of Defense, must bear an expanded marking on the face of the document so that non-DOD holders understand the status of the information. A statement similar to this one should be used: This document contains information Exempt from mandatory disclosure under the FOIA.

Exemption(s) (indicate the exemption(s)) apply.

c. Classified documents and material containing FOUO information will be marked as required by chapter 4 of this regulation, with FOUO information identified as follows:

(1) Overall markings on the document will follow the procedures in chapter 4. No special markings are required on the face of the document because it contains FOUO information.

(2) Portions of the document will be marked with their classification as required by chapter 4. If there are unclassified portions which contain FOUO information, they can be marked with "FOUO" in parentheses at the beginning of the portion. Since FOUO information is, by definition, unclassified, the "FOUO" is an acceptable substitute for the normal "U."

(3) Pages of the document which contain classified information will be marked as required by chapter 4 of this regulation. Pages which contain FOUO information but no classified information will be marked "FOR OFFICIAL USE ONLY" at the top and bottom.

d. Transmittal documents which have no classified material attached, but do have FOUO attachments, will be marked with a statement similar to this one: "FOR OFFICIAL USE ONLY ATTACHMENT."

Question #25 Reference Section B, CLIN 0019, SOW 3.2.5.4.5, SOW 3.2.5.4.6. Section B CLIN 0019 references SOW paragraph 3.2.5.4.6 “FWS-CS First Article Test (FAT) Exit Criteria.” However, SOW section 3.2.5.4.6 is titled “FWS-CS PRR Exit Criteria,” while Section 3.2.5.4.5 is titled “FWS-CS First Article Test (FAT) Exit Criteria” Is it the Government's intent that CLIN 0019 refer to SOW paragraph 3.2.5.4.5 “FWS-CS First Article Test (FAT) Exit Criteria” instead of 3.2.5.4.6 “FWS-CS PRR Exit Criteria”?

Government Response to Question #25 Yes, CLIN 0019 should refer to SOW paragraph 3.2.5.4.5 "FWS-CS First Article Test (FAT) Exit Criteria" instead of 3.2.5.4.6. Section B has been revised to correct the paragraph number reference.

Question # 28 Reference Section I – Contract Clauses, pages 83 through 85, 52.209-5 Certification Regarding Responsibility Matters and 52.209-7 Information Regarding Responsibility Matters. These Section I FAR clauses appear to require fill-in and submittal by the Offeror; however, there is no requirement in Section L to include them in Volume 1 – Offer. Is it the Government’s intent that these clauses be completed and submitted with the proposal? If so, in what Volume/Section shall we include these items?

Government Response to Question #28 Yes, the Government's intent is for all clauses requiring a fill-in from offerors to be completed and submitted in Volume 1. RFP Section L, paragraph 1.1.2.1 Volume 1 - Offer has been revised to add the following: "RFP Sections, all clauses requiring offeror fill-in to be completed and submitted in Volume 1."

Question #29 Reference Section C, Table 3.1. This table provides the anticipated FWS-CS EMD Test Schedule and associated asset allocation. The column “No. of Systems Required” is interpreted as the number of assets allocated to each given event with some systems identified as new. It is unclear how “No. of Systems Required” column contributes to the “Cumulative Total No. of Systems Required” count in the last column.

For example, There are two (2) systems allocated to the Weapon Fit Check event, and the cumulative column is incremented by two (2). Next, in the 80% Op/Crew Technical Guide review event there are two (2) systems allocated and the cumulative column is further incremented by two (2), to a total of four (4). Note, neither of these systems are identified as new. Further down in the table there are eighteen (18) systems allocated to the CDT start event, however the cumulative column is not incremented by eighteen (18) it is set to eighteen (18). This implies there are fourteen (14) new assets allocated to this event, plus the four (4) previously used assets; however, this convention does not appear to apply to other events in the table. The anticipated FWS-CS LRIP Test Schedule, Table 3.2, is also not clear on the use of new systems.

Will the Government please clarify the information in Tables 3.1 and 3.2 regarding the required delivery and use of new systems and TMDE?

Government Response to Question #29 The intent is to show that for TM training that 2 reused systems for Weapon Fit Check and 2 additional reused systems for 80% TM review for a total of 4 systems would be needed for this phase.

For Table 3.1, the Government requires 18 new systems to start CDT. For GDT, 8 systems will be required, of those 8 systems, 5 will be new systems, thus a total cumulative of 23 new systems acquired from the vendor at that time. For RGT-1, 10 new systems will be needed for a new cumulative total of 33 systems acquired from the vendor. For I&KPT, 1 system would be reused from the previous 33 acquired systems and 8 systems with built-in malfunctions would be reused from the cumulative 33 systems for EAD. For NET and LUT, 1 each unit for each event from the cumulative 33 systems as long as the design/functionality hasn't changed for the LUT. The LUT requires 12 new systems for a cumulative total of 45 systems for EMD.

For LRIP, during the TM Training review, 1 system and 1 TMDE set will be required from the 45 LRIP systems to be acquired. Starting at PQT, 18 systems and 1 TMDE system will be required. For GDT, 8 systems will be required, of those 8 systems, 5 will be new systems, thus a total cumulative of 23 new systems, and 1 TMDE system acquired from the vendor at that time. For RGT-2, 10 new systems for a cumulative total of 33 and 1 TMDE system will be needed. For CBRN, 1 system from the 33 acquired systems will be used for CBRN testing at Dugway Proving Grounds. For the I&KPT and Log Demo, 8 systems with malfunctions will be used in conjunction with 3 TMDE systems (2 new) for a cumulative total of 33 systems and 4 TMDE systems acquired from the vendor at that point. For the Maintainer I&KPT Log Demo, there will be 8 systems reused from the 33 systems with built-in malfunctions that are diagnosed by 1 TMDE system from the 4 systems acquired from the vendor. The IOT&E will require 12 new systems and 1 reused TMDE system in case of repairs for any of the 12 systems are needed during IOT&E. Thus, the cumulative total for LRIP is 45 systems and 4 TMDE systems.

Question #30 Section L 1.1.2.1 (Volume 1 - Offer) and Section M 1.2.3 (Evaluation Approach). Section L 1.1.2.1 cites BANC3, Bevilacqua Research Corporation (BRC), CACI, and Jacobs Technology Inc. as serving as source selection advisors, while Section M 1.2.3 adds NCI to this list. Please clarify whether NCI will serve as source selection advisors, and if so, whether we are required to obtain a proprietary information agreement with them. If we are to provide such an agreement, please provide contact information.

Government Response to Question #30 Yes, NCI employees may serve as source selection advisors. Section L, paragraph 1.1.2.1 has been revised to add NCI and to provide their contact information:

Company Name: NCI Information Systems, Inc.

Company Address: 11730 Plaza America Dr Suite 700, Reston, VA 20190-4764 Contract: W91CRB-15-C-0035 Delivery Order: N/A POC: Gary Kirkland (Principal Contracts Administrator) Phone: 703-707-6713 Email: gmkirkland@nciinc.com

Question #31

Reference SOW Paragraph 3.2.2 (page 26), CDRL -BBB, CLIN 001 (page 108), and CLIN 0001 (Page 4). SOW Paragraph 3.2 calls for an Integrated Program Management Report (IPMR). CDRL BBB calls out the IPMR for EMD. According to DODI 5000.02, only cost type contracts or fixed price incentive programs greater than $20M require an IPMR. If an Offeror's cost-type CLINs total less than $20M, are IPMRs still required?

Government Response to Question #31

The Government intends to use the IPMR as stated.

Question #32

Reference SOW Paragraph 3.2.2 (page 26), CDRL -FFF, CLIN 011 (page 109), and CLIN 0011 (Page 15). SOW Paragraph 3.2 calls for an Integrated Program Management Report (IPMR). CDRL FFF calls out the IPMR for LRIP. According to DODI 5000.02, only cost type contracts or fixed price incentive programs greater than $20M require an IPMR. LRIP is Firm Fixed Price. Does the Government still require IPMRs for this Firm Fixed Price portion of the contract?

Government Response to Question #32

The Government will determine the amending the IPMR at the PAC.

Question #33

Reference CLIN 0019. RFP Wording:

PY5 FIRST ARTICLE TEST (FAT) REPORT

FFP

FWS-CS First Article Test (FAT) Report, IAW SOW paragraphs 3.3.8.7 “Test Reports” and 3.2.5.4.6 “FWS-CS First Article Test (FAT) Exit Criteria.”

Does CLIN 0019 “PY5 First Article Test (FAT) Report” only apply to the report generation or does it also include the conduct of the FAT?

Government Response to Question #33

Conduct of the FAT is not a separately priced event and should be captured in the offeror's system production unit pricing as the FAT is performed on a sample of the first production lot. The contractor should review all the CDRLs, DIDs, and PD that reference First Article Test. The report cannot be completed without conclusion of other related CDRLs and DIDs such as Test Plans, Test Reports, FIARs, etc in accordance with the PD table.

Question #34

Reference Section A regarding requests for proposal submission extension.

Government Response to Question #34

The Government has received multiple requests for a change to the proposal submission date with various lengths of extension requested. Amendment #3 provides an updated proposal due date of 12:00PM NOON 19 October 2015.

No additional extensions are planned based on current information.

Question #35

Reference SOW 3.3.2.2.2 and Attachment 1 (3.3.5.3.1 and 3.3.5.3.2). SOW paragraph 3.3.2.2.2. Measurement Interface Equipment states, “The Contractor shall provide five (5) sets of interface equipment for FWS-CS EMD, and five (5) sets of interface equipment for FWS-CS LRIP, to include deserializers to support Government measurement of required performance parameters identified in this SOW and the FWS-CS PD.” It is unclear what FWS-CS PD parameters are required to be checked with test equipment installed. For example, is the FWS-CS system required to pass EMI, immersion, weapon fire, sand and dust, and others when test equipment is installed?

Or is this only for room temperature lab based sensor testing of uniformity, noise, MTF, etc.? Please clarify which FWS-CS requirements are relevant to testing with interface equipment installed.

Government Response to Question #35

Please see responses to questions #6 and #7 for additional information on the parameters required to be checked with the measurement interface equipment installed. The equipment should be rated to operate at temperatures experienced in the lab (20-25 deg C) and at WSMR (~10 deg C to ~40 deg C ambient; -40 deg C to 49 deg C during testing). The equipment will be used to monitor video during a number of tests, but sufficient length cabling and/or the wireless video can be used in order to keep the equipment separate from the environment itself (e.g. in the antechamber at WSMR instead of the extreme temperature chamber, external from the rain chamber, etc.) if the equipment is not rated for the test conditions of the sight. Only the sight and its components are required to meet all of the environmental conditions listed in the PD.

Question #36

Reference SOW 3.3.2.2.2 and Attachment 1 (3.3.5.3.1 and 3.3.5.3.2). SOW paragraph 3.3.2.2.2. Measurement Interface Equipment states, “The Contractor shall provide five (5) sets of interface equipment for FWS-CS EMD, and five (5) sets of interface equipment for FWS-CS LRIP, to include deserializers to support Government measurement of required performance parameters identified in this SOW and the FWS-CS PD.” In addition to the above, the range of environments that the digital test equipment needs to work under (and after if applicable) is unclear. For example, does the test equipment need to survive weapon fire, immersion, etc. Operate at -40C and 49C + solar load? Or is this to be for laboratory use only (23C +/-5C, etc.)? Or TMDE based requirements? Please clarify the test equipment requirements (operational and storage/shipping) with regard to environmental exposure.

Government Response to Question #36

See response to question #35. The equipment should survive standard shipping methods to Government test locations (Ft. Belvoir, WSMR, Ft. Bragg and TBD locations for the Ground LUT and IOT&E) and will be stored in ambient conditions at those locations (e.g. lab, office or mobile trailer).

SUMMARY OF CHANGES, AMEND 0003

SUMMARY OF CHANGES, AMENDMENT 0003: 17 SEPTEMBER 2015

Amendment 0003 updates the proposal due date to 19 October 2015, provides updates to solicitation documentation, and provides Government responses to [open] Industry questions received as of 16 September 2015. Questions received after 16 September 2015 shall be addressed in a subsequent amendment.

Solicitation Documentation Changes:

a. Section A has been updated to reflect a proposal due date of 12:00PM NOON 19 October 2015.

b. Section B, CLIN 0019 has been updated to correct the SOW paragraph reference for “FWS-CS First Article Test (FAT) Exit Criteria” (see Question #25 below for details).

c. Section C, Appendix A, Paragraph 6.2.4 has been modified to clarify TMDE equipment requirements (see Question #19 below for details).

d. Section L, Paragraph 1.1.1.1.2 Acquisition Source Selection Interactive Support Tool (ASSIST)2Industry is amended to add the following:

“All Offerors are advised that ASSIST2Industry has been updated and it is now the responsibility of PRIME Contractors to establish accounts for their SUBCONTRACTORS to respond to Government ENs. A separate area within ASSIST2Industry has been created to allow authorized Subcontractor POCs to upload proposal files only. Subcontractors will not be able to access any other information on the ASSIST2Industry website (e.g.

Questions/Evaluation Notices, Responses, etc.). Once a Subcontractor has been added, they will receive a user ID (e.g. subcontractor0001) and password (an initial password) that will be sent via two separate system generated e-mails. A Subcontractor will have one user ID for all PRIMES and solicitation responses, i.e. if you are a Subcontractor to multiple Prime Contractors and multiple solicitation responses, you will only have one user ID.

Once an account has been established for the Subcontractor, go to https://ASSIST2Industry.army.mil access the account. Prime Contractors will only be able to see the number of files submitted by their Subcontractors; but, will be UNABLE TO VIEW the Subcontractor’s files.

NOTE: Both Prime Contractors and Subcontractors are instructed to review the ASSIST2Industry User’s Guide, located under the “Getting Started” tab on the website. The guide has been updated and provides step by step instructions on how to perform functions and navigate the website.

Offerors can contact the ASSIST2Industry Helpdesk via e-mail at usarmy.jbmdl.acc.list.vce-helpdesk@mail.mil or by telephone at (609) 562-5988 or (609) 562-7050 for any technical assistance that may be needed.”

e. Section L, Paragraph 1.1.1.1.6 General Appearance has been amended to allow shading only for table headings and alternate table rows/columns (see Question #16 below for details).

f. Section L, Paragraph 1.1.2.2.1.1.1 FWS-CS Optical Prescriptions to Support Performance Specification has been revised to clarify that a .zar file is acceptable for this submission provided it meets the remaining requirements of the paragraph (see Question #17 below for details).

g. Section L, Paragraph 1.1.2.2.2 Section 2 – FWS-CS Sample Hardware and Section M, Paragraph 1.2.3.1.2.2 Government Verified Sample Hardware Performance have been revised to allow +/- 2 degrees for Sample Hardware HFOV (see Question #18 below for details).

h. Section L, Paragraph 1.1.2.1 Volume 1 – Offer has been revised to clarify that all clauses requiring an offeror fill-in are to be completed and submitted in Volume 1 (see Question #28 below for details).

i. Section L, Paragraph 1.1.2.1 Volume 1 – Offer has been revised to add NCI along with their contact information (see Question #30 below for details).

j. Attachment #1, FWS-CS Purchase Description, Paragraph 3.3.8.9.1 Electromagnetic Interference (EMI) Requirements has been updated to clarify inclusion of conducted EMI requirements (see Question #1 below for details).

k. Attachment #1, FWS-CS Purchase Description, Tables 4.6-1 and 4.6-3 have been revised to include a line for I- LRF Alignment to specify test method and frequency (see Question #3 below for details).

l. Attachment #1, FWS-CS Purchase Description, Paragraph 3.3.5.4 External Power has been revised to include a vehicle cable length and a ruggedized, military standard end connector for the vehicle power cabling (see Question #4 below for details).

NOTE: The revised Attachment #1 – FWS-CS Product Description dated 16 September 2015 is a restricted distribution attachment. The revised FWS-CS PD shall be provided to offerors via AMRDEC SAFE distribution. Contact admin POC at jennifer.c.mccormick.ctr@mail.mil and cc contracting specialist at andrew.c.mitchell1.civ@mail.mil to request the updated FWS-CS Product Description.

The following have been deleted:

Q AND A: AMENDMENT 0002

SUMMARY OF CHANGES, AMEND 0002

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 30-Sep-2015 12:00 PM to 19-Oct-2015 12:00 PM.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0019

The CLIN extended description has changed from:

FWS-CS First Article Test (FAT) Report, IAW SOW paragraphs 3.3.8.7 "Test Reports" and 3.2.5.4.6 "FWS-CS First Article Test (FAT) Exit Criteria."

To:

FWS-CS First Article Test (FAT) Report, IAW SOW paragraphs 3.3.8.7 "Test Reports" and 3.2.5.4.5 "FWS-CS First Article Test (FAT) Exit Criteria." .

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK (SOW)

Following documentation is provided for the solicitation for W91CRB-15-R-0024.

Recipients shall:

i. Read and comply with distribution markings.

ii. Direct all requests for distribution to other parties to Andrew Mitchell at andrew.c.mitchell1.civ@mail.mil.

iii. Destroy the documents once they are no longer required to support this solicitation.

Recipients shall NOT: Redistribute the SOW outside of Distribution Statement D, of the program security classification guide, to include subsidiaries and subContractors within the corporate structure for this program.

In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

FAMILY OF WEAPON SIGHTS CREW SERVED (FWS-CS) STATEMENT OF WORK

1.0. Scope. This Statement of Work (SOW) establishes the performance, design, test, manufacture, and acceptance requirements for the Family of Weapon Sights – Crew Served (FWS-CS) variant. This SOW specifies the tasks the Contractor shall perform during the Engineering, Manufacturing and Development (EMD), Low Rate Initial Production (LRIP), and Production efforts for the FWS-CS. The FWS-CS system will be interoperable with the M240 Medium Machine Gun, M2 Heavy Machine Gun (HMG), and MK19 Automatic Grenade Launcher (AGL).

The FWS-CS is envisioned as a weapon mounted LWIR sensor used for surveillance and enhanced target engagement of crew served weapons during daylight, darkness, adverse weather, and dirty battlefield conditions in hot, basic, and cold environments. This will allow a single mounted or dismounted operator to detect and recognize targets at greater distances than their crew served weapon system’s maximum effective range. Note also that items in bold refer to requirements for Contract Line Item Numbers (CLINs) that become requirements if/when ordered.

1.1. Terminology.

1.1.1 Government. When the term “Government” is used throughout this document, it shall refer to the cognizant personnel within Product Manager, Soldier Maneuver Sensors as well as the Procuring Contracting Officer (PCO) and his/her representatives assigned to the FWS-CS program.

1.1.2 Days. When the term “days” is used throughout this document, it shall refer to calendar days, unless explicitly specified as business days. All deliveries shall be made on a business day and Close of Business (COB) is defined as 16:00 (Eastern Standard Time).

1.1.3 Weapon Sight. Basic term for the FWS-CS weapon sight containing the subcomponents of the thermal and visible color cameras, integrated laser range finder, display, objective lens assembly, eyepiece, and remote that can be mounted on the multiple weapon variants.

1.1.4 Contract Data Requirements List (CDRL). CDRLs have corresponding Data Item Descriptions (DID), which specify specific instructions on deliverables from the Contractor. The Contractor shall comply with the CDRLs and associated DID.

2.0. Applicable Documents. The contractor shall adhere to the following documents that form parts of this SOW to the extent specified herein. Unless otherwise specified, the latest revision of each document shall apply. The Government may tailor the required documentation as appropriate for the FWS-CS program in order to streamline and improve efficiencies as needed, without superseding applicable laws and regulations.

2.1 Government Documents. Unless otherwise specified, the following specifications, standards, and handbooks may be downloaded from the Army Publishing Directorate website at http://www.apd.army.mil/ and ASSIST (Acquisition Streamlining and Standardization Information System) website at: www.assistdocs.com.

AR 530-1 Operations Security (OPSEC) 20140926 or 26

September 2014 AR 700-37 Packaging of Army Materiel 20130222 or 22

February 2013 AR 700-127 Integrated Product Support 20141007 or 7

October 2014 AR 750-1 Army Materiel Maintenance Policy 20130912 or 12

September 2013 DA PAM 611-21_V1 MOS Smartbook

(Note: The link to the MOS Smartbook listed in pamphlet “https://smartbook.armyg1.pentagon.mil/” has been superseded effective 06/14/2015. DA Pam 611-21 is now located on milBook at the following link. Go to the link, join the group (button on the

20070122 or 22 January 2007 with Admin Change 20120426 or 26 April 2012 right), and then click on the “Content” tab to see the chapters.

CAC log-in required.

https://www.milsuite.mil/book/groups/smartbookdapam611-21)

DA PAM 700-127 Integrated Product Support Procedures 20141008 or 8 October 2014

DI-SESS-80858C Contractor’s Configuration Management Plan 20150407 or 7April 2015

DI-MGMT-81861 Integrated Program Management Report (IPMR) Data Item Description

20120620 or 20 June 2012

DI-MGMT-81808 Contractor’s Risk Management Plan 20100421 or 21 April 2010

DI-SESS-81758A Logistics Product Data (LPD) 20130522 or 22 May 2013

DI-SESS-81759A Logistics Product Data Summaries 20130521 or 21 May 2013

DI-NDTI-80566A Test Plan 20061114 or 14 November 2006

DI-NDTI-80603A Test Procedure 20061114 or 14 November 2006

DI-NDTI-80809B

Notice 1

Test/Inspection Report 20140827 or 27 August 2014

DoD 5220.22-M with Change 1

National Industrial Security Program Operating Manual 20130328 or 28 March 2013

FWS-S FDSC FWS-S Failure Definition and Scoring Criteria (FDSC) -- MIL-DTL-14072F Finishes for Ground Based Electronic Equipment 20130813 or 13

August 2013 MIL-HDBK-61A Configuration Management Guidance 20010207 or 7

February 2001 MIL-PRF-28800F General Specification Test Equipment for Use with Electrical and

Electronic Equipment 19960624 or 24 June 1996

MIL-STD-129R Military Marking for Shipment and Storage 20140218 or 18 February 204

MIL-STD-130N with Change 1

Identification Marking of US Military Property 20121116 or 16 November 2012

MIL-STD-461F DoD Interface Standard, Requirements for the Control of Electromagnetic Interface Characteristics of Subsystems and Equipment

20071210 or 10 December 2007

MIL-STD-2073-1E

with Change 1

DoD Standard Practice for Military Packaging 20110107 or 7 January 2011

MIL-STD-464C DoD Interface Standard, Electromagnetic Environmental Effects Requirements For Systems

20101201 or 1 December 2010

MIL-STD-1839D Standard Practice for Calibration and Measurement Requirements 20100512 or 12 May 2010

MIL-HDBK-2155

Notice 1

Failure Reporting, Analysis and Corrective Action Taken 20140910 or 10 September 2014

MIL-STD-40051-1B Preparation of Digital Technical Information for Interactive Electronic Technical Manuals (IETMs)

20121130 or 30 November 2012

MIL-STD-40051-2B Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)

20121130 or 30 November 2012

MIL-STD-810G with Change 1

DoD Test Method Standard - Environmental Engineering Considerations and Laboratory Tests

20140415 or 15 April 2014

MIL-STD-881C Work Breakdown Structures for Defense Materiel Items 20111103 or 3 October 2011

MIL-STD-882E System Safety 20120511 or 11 May 2012

MIL-STD-961E with Change 2

DoD Standard Practice for Defense Specifications - Defense and Program-Unique Specifications Format and Content

20140109 or 9 January 2014

PD-FWS-S Product Description- Family of Weapon Sight – Sniper (FWS-S) -- N/A DoD Guide for Achieving Reliability, Availability and

Maintainability 20050803 or 3 August 2005

Non-Government Documents. Are found on IEEE, ISO, SAE International, and IHS websites.

SAE GEIA-STD-

0007B

Logistics Product Data 20130501 or 1 May 2013

SAE GEIA HB-0007-B Logistics Product Data Handbook 20140201 or 1 February

SAE GEIA-STD-0009 Reliability Program Standard for Design, Development and Manufacturing

20080801 or 1 August

ANSI/NCSL-Z540.3-

2006 (R2013)

Requirements for the Calibration and Measurement of Test Equipment

20130326 or 26 March

ASME Y14.5-2009 Dimensioning and Tolerancing 20090327 or 27 March

SAE EIA-649-1 Configuration Management Requirements for Defense Contracts

20141101 or 1 Novembe

IEEE STD 15288.1-

IEEE Standard for Application of Systems Engineering on Defense Programs

20141210 or 10 December 2014

IEEE STD 315-1975

(R1993)

Graphic Symbols for Electrical and Electronics Diagrams 19931202 or 2 December

ISO 15288:2015 Systems and Software Engineering – System Life Cycle Processes

20140515 or 15 May

ISO/IEC/IEEE DIS

24748-4.2

Systems and Software Engineering Life Cycle Management – Part 4: Systems Engineering Planning

20140413 or 13 April

ISO 26702:2007 Systems Engineering – Application and Management of Systems Engineering Process

20070715 or 15 July 2015

ISO 9001:2008 Quality Management Systems – Requirements 20090715 or 15 July 2009 ISO 10012:2003 Measurement Management Systems - Requirements for

Measurement Processes and Measuring Equipment 20030415 or 15 April

3.0. Requirements and Description. The FWS-CS shall be a lightweight, battery operated, thermal and visible color imaging system for surveillance and target acquisition mounted on crew served weapons during daylight, darkness, limited visibility, adverse weather and dirty battlefield conditions. The FWS-CS shall include a wireless capability to stream and display information in real time from the weapon sensor to the HMD. The FWS-CS shall have a laser range finder (LRF) integrated into the weapon sight.