N00024-18-R-4201_Amendment_0001_11_27_17.pdf

N0002416NR63012

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

See Page 2.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 6

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

16C. DATE SIGNED

BY 27-Nov-2017

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 N0002418R4201

X 9B. DATED (SEE ITEM 11)

02-Nov-2017

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

27-Nov-2017

CODE

NAVAL SEA SYSTEMS COMMAND

1333 ISAAC HULL AVE SE - MAIL STOP 2030

WASHINGTON NAVY YARD DC 20376-2030

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0002418R4201

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

The following items are applicable to this Amendment 0001 to solicitation N00024-17-R-4201.

1. SECTION C – Descriptions and Specifications the following have been modified:

a) paragraph 1.4 Applicable Documents the following is modified:

From: MIL-STD-1472F, Human Engineering

To: MIL-STD-1472 Rev G, Human Engineering

b) all references in the RFP to “training sets” are changed to “FF and BF Lab Equipment Suite” including the following paragraphs:

3.4 COTS Software

3.7.10 Vulnerability Scan Compliance (VSC) Report

5.1 Configuration Management Plan

c) Paragraph 11.0 CYBERSECURITY- the following is deleted:

“The Contractor shall also develop and deliver cybersecurity information per the following CDRLs:

a) Cybersecurity Defense-in-Depth (DID) Architecture Diagrams for the system, the sub-network, or platform network into which the system will be integrated”

2. SECTION J - List of Documents, Exhibits and Other Attachments he following documents have been updated and are provided as attachments to this amendment.

Exhibit A - Contract Date Requirements List, DD Form 1423

Attachment A - IBNS Performance Specification; Revision C

Attachment G - Government Furnished Information (GFI) and Government Furnished Equipment (GFE)

List

3. SECTION L - Instructions, Conditions and Notices to Bidders

a) the following has been deleted:

252.246-7005 Notice of Warranty Tracking of Serialized Items (MAR 2016)

b) A. PHYSICAL FORMAT table is modified as follows:

VOLUME

TITLE

PAGE LIMIT

ORIGINALS

PAPER

COPIES

CD ROMs

I Technical 75 1 4 6

Prior EQT 20 additional pages 1 4 6 approval justification allowed

Vendor Hardware

Interface

Requirements

35 additional pages allowed

1 4 6

Data Rights 10 additional pages allowed

1 4 6

II Management 75 1 4 6

CMMI Level III

Experience

Included within the

Management proposal page limit but not exceeding 5 pages

1 4 6

Software

Development

Plan(SDP)

No specific page limit as long as it fits within the

Management proposal total page limitation

1 4 6

III Past Performance 10 1 4 6

IV Pricing N/A 1 4 6

c) All references in the Section L to “training sets” are changed to “FF and BF Lab Equipment Suite” including the following paragraphs:

Element 2.3 – Program Plan

d) Volume III – Past Performance, the following paragraph has been modified as follows:

Volume III – Past Performance:

“The Offeror shall forward the Past Performance Information (PPI) Questionnaire (Attachment L-4) to the points of contact for each of the listed contracts and request such contacts to complete the required form. The completed questionnaire shall be submitted by the point of contact who completed the form directly to the POC for the Navy, Tara Borntreger at tara.borntreger@navy.mil by the solicitation closing date. No completed questionnaire shall be forwarded by the offeror.

The Offeror may request the status of the receipt of these questionnaires by contacting the POC by email at tara.borntreger@navy.mil.”

The following questions are answered:

Question #1 - The RFP Section L requirements for the initial Software Development Plan (SDP) submission in the

"Physical Format" table at the top of page 164 conflicts with Section L page 172, which states that the initial SDP shall be provided in Volume II - Management Proposal, as Element 2.6.

Answer #1 – Section L Physical Format table on page 164 has been modified as part of this amendment. The SDP should be submitted as part of the Management Proposal vice the Technical Proposal.

Question #2 - Please consider increasing the page limit of the Volume II Management Proposal.

Answer #2 - Section L has modified to increase the page count limitations for the Volume II Management Proposal from 30 pages to 75 pages. The 75 page count limitation now includes the SDP document submission. There is no mailto:tara.borntreger@navy.mil mailto:tara.borntreger@navy.mil longer a page limitation on the SDP document other than it is now part of the Volume II Management Proposal which has a 75 page count limitation.

Question #3 - Section C.11.0 (Cybersecurity), page 51, requires Defense-in-Depth (DID) Architecture Diagrams

"per the following CDRLs," but no CDRL is listed. Please clarify.

Answer #3 - This requirement has been deleted from the RFP.

Questions #4 - Sections 12.2 and 16.8 of Attachment A are in conflict as to the Portable Computer programmed configurations. Section 12.2 states that the four configurations are NAV 2/VMS, C.O., Emergency Navigation

Laptop (ENL), and IBNS Administrator. Section 16.8 lists only three configurations for the four deliverable items:

NAV 2/VMS, NAV 4 (C.O.)/VMS, and IOS (Instructor Operator Station). Based on the definition of an IBNS

Equipment Set in SOW Section 1.1, it appears that 12.2 is correct, and 16.8 is in error. Therefore, there are currently no software requirements defined for the ENL and IBNS Administrator configurations. Please revise

Section 16.8 to provide software requirements consistent with the Portable Computer configurations listed in Section

12.2.

Answer #4 – Attachment A, para 16.8 has been updated as follows:

The four laptops will be required to support the following software:

- The NAV2 laptop will run VMS or ECDIS software;

- The COLAPTOP/NAV4 will run VMS or Nay ECDIS software

- The ENL laptop will run VMS or NAVY ECDIS software

- The IBNS Administrator Laptop, shall include the necessary software to load Allen-Bradley/Rockwell

Automation Control Logic Programmable Logic Controller (PLC) Modules.

Question #5 - Attachment A states that "The Portable Computers shall use ATI GPUs." To our knowledge, none of the IBNS software applications to be hosted on the Portable Computers require a specific brand of GPU. Can this requirement be deleted?

Answer #5: No changes have been made to the RFP as a result of this question. ATI GPUs are needed for the radar overlay in the VMS software.

Question #6 - The IBNS Maintenance Kit is required to include a "Portable Computer power supply" and a "USB

Optical drive capable of reading and writing to BluRay." The Portable Computer included in the kit has an internal power supply and a BluRay read/write drive. Is the specified power supply an AC power adapter and cord for the

Portable Computer? Is the specified Optical Drive an external device, or is this requirement met by the Portable

Computer drive?

Answer #6 - No changes have been made to the RFP as a result of this question. An AC power adapter and cord will meet the Attachment A requirement for a power supply. An external optical drive is needed for use in the other workstations.

Question #7 - Attachment A, Section 16.7.1 states: "The LCUs shall run Government provided Steering and

Propulsion Control System (SPCS) Programmable Logic Controller module firmware and PLC ladder." Per

Attachment G, the current SPCS software is GFI. Please confirm that Contractor modification of GFI SPCS software to interface to the specified LCU is not within the scope of this contract.

Answer #7 - No changes have been made to the RFP as a result of this question. The SPCS software is not a deliverable as part of the RFP and contractor modification of GFI SPCS software to interface to the specified LCI is not a requirement of this RFP.

Question #8 - Section L includes DFARS 252.246-7005, Notice of Warranty Tracking of Serialized Items. The prescription for this clause states: “Use the provision at 252.246-7005, Notice of Warranty Tracking of Serialized

Items, in the solicitation if the Government does not specify a warranty and offerors will be required to enter data with the offer…” The IBNS RFP specifies a warranty, in SOW section 9.0 and elsewhere. To eliminate the conflict in warranty requirements, please remove DFARS 252.246-7005 from the solicitation.

Answer #8 - DFARS 252.246-7005 has been deleted.

Question #9 - Attachment A requires that various IBNS computers shall be loaded with Steering and Propulsion

Control System (SPCS) or Voyage Management System (VMS) software. SPCS is listed as GFI in Attachment G, but VMS is not. Please confirm if VMS will also be GFI.

Answer #9 - Attachment G GFI-GFE listing has been updated to reflect that VMS software will be provided as GFI

180 DACA.

Question #10 - Attachment A.11.12.2 states: "The MEM board shall only use components that do not require software programming." Is it acceptable to use an FPGA and its associated firmware in the MEM?

Answer #10 - The government will accept an FPGA with associated firmware.

Question #11 - Attachment L-4 states that the completed Past Performance Questionnaires shall be submitted to tara.borntreger@navy.mil. In Section L, the Volume III requirements state that these questionnaires shall be submitted to Emily Lonigro at 202-781-4132. Please clarify.

Answer #11 - Section L, Volume III has been revised to state that completed Past Performance Questionnaires shall be submitted to Tara Borntreger at tara.borntreger@navy.mil.

Question #12 - The SOW makes three references to a "Training Set." See Section C.3.4 (COTS Software), C.3.7.10

(Vulnerability Scan Compliance (VSC) Report), and C.5.1 (Configuration Management Plan). The Section L requirements for proposal Element 2.6 (Program Plan) state: "The Offeror shall demonstrate its ability to accomplish the production and delivery of two (2) Ship sets, one (1) First Article Testing set, and two (2) Training Site set of

IBNS equipment." However, there are no "Training Set" deliverables defined in the Section B CLINs, and there is no definition of the scope of a Training Set in the RFP. Please either delete the references to Training Sets, or revise the RFP to define the scope of a Training Set and the delivery and schedule requirements.

Answer #12 - All references to "Training Sets" will be changed to "FF and BF Lab Equipment Suites". Section

C.3.4 (COTS Software), C.3.7.10 (Vulnerability Scan Compliance (VSC) Report), and C.5.1 (Configuration

Management Plan) have been changed. Also, the Section L requirements for proposal Element 2.3 (Program Plan) has been changed from "The Offeror shall demonstrate its ability to accomplish the production and delivery of two

(2) Ship sets, one (1) First Article Testing set, and two (2) Training Site set of IBNS equipment." to "The Offeror shall demonstrate its ability to accomplish the production and delivery of one (1) ship set, one (1) First Article

Testing set, and one (1) FF or BF lab Equipment Suite of IBNS equipment."

Question #13 - Attachment G states that the "current" SPCS software will be Government-furnished 30 DACA. In

Attachment A, section 16.7.1 states: "The LCUs shall run Government provided Steering and Propulsion Control

System (SPCS) Programmable Logic Controller module firmware and PLC ladder." Will the SPCS software furnished 30 DACA include the LCU PLC ladder logic and firmware? If not, this may create dependency issues for the CLIN 0001 NRE, Qualification, and Test schedule -- when does the Government anticipate that the LCU portion will be provided?

Answer #13 - No changes have been made to the RFP as a result of this question. The SPCS software will include the necessary LCU PLC ladder logic and firmware.

Question #14 - In multiple Exhibit A CDRLs, the delivery date is defined in relation to an "FDR" (Functional

Design Review) event. For an example, please see Block 12 of CDRL A002 (Product Drawings and Associated

Lists). Per SOW Section 4.3.2 (Technical Design Reviews), FDR is not an IBNS program event. Please clarify.

Answer #14 - All references to a Functional Design Review (FDR) should be considered to be equal to a

Preliminary Design Review (PDR). The Exhibit "A" CDRLs have been revised to change all FDR references to

PDR.

Question #15 - Attachment A states: "The LCU shall contain a WeaselBoard Module from Sandia National

Laboratories." Sandia informs us that this module is currently in development under a Government contract, so they are unable to provide a firm price. Since this module is being developed under Government contract, please revise

RFP Attachment G to specify that it will be provided as GFE.

Answer #15 - Attachment A has been modified to state that the "The steering LCU shall be designed so that it will allow for capacity/space to accommodate the addition of a future Government installation of a WeaselBoard cybersecurity backplane monitoring module from Sandia National Laboratories." Each of the four LCUs in a shipset shall have the capacity to accommodate a future WeaselBoard. The vendor will not be required to acquire

WeaselBoards and the WeaselBoards will not be provided as GFE to be integrated by the vendor. The vendor shall only provide the capacity into the design to allow the Government to integrate the WeaselBoards at a later date.

Question #16 - In RFP Section C, SOW Section 1.1 (Equipment Sets) states that each equipment set includes "1

IBNS Administrator Portable Computer" among the "4 Portable Computers." It also states that each equipment set includes an "IBNS Maintenance Kit." In RFP Attachment A, section 14.3.1 states that one of the components of this kit is an "IBNS Administrator laptop." Does a complete equipment set include one or two IBNS Administrator

Portable Computers?

Answer #16 - No changes have been made to the RFP as a result of this question. As stated in section C of the RFP in sections 1.1.1, 1.1.2, 2.2.3, 1.1.4, and 1.1.5 the requirement is for four total laptops for each equipment suite delivery. The administration laptop discussed in Attachment A Section 14.3.1 is the same administration laptop described in Section C. There is only one administration laptop required per shipset.

Question #17 - FAR 52.209-3 FIRST ARTICLE APPROVAL -- CONTRACTOR TESTING (SEP 1989) -

ALTERNATE II (SEP 1989). Paragraph (g) states: "Before first article approval, the Contracting Officer may, by written authorization, authorize the Contractor to acquire specific materials or components or to commence production to the extent essential to meet the delivery schedules. Until first article approval is granted, only costs for the first article and costs incurred under this authorization are allocable to this contract for (1) progress payments."

The first shipset (CLIN 0002) is deliverable 16 months ADC. Per CLIN 0001, qualification/first article testing will not be complete until 10 months ADC, and the Government's review and approval process for first article test results may require several months. Even assuming immediate approval of those results, procurement of long-lead materials and production start prior to completion of first article testing will be necessary in order to meet the CLIN 0002 schedule. In order to meet CLIN 0002 delivery requirements, please confirm that the Contracting Officer will authorize costs to be incurred and made eligible for progress payments in advance of first article approval.

Answer #17 - No changes have been made to the RFP as a result of this question. FAR 52.209-3 will be implemented as stated and, if required, the Contracting Officer can authorize the procurement of long lead materials prior to first article approval which would be eligible for progress payments.

Question #18: Please provide the incumbent contract number and value, including per unit price?

Answer #18: The incumbent contract number is N00024-13-C-4205 and the total value at contract award (if all options were exercised) was $88,583,682. Per unit prices will not be provided. This information can be requested through the FOIA process.