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

See Page 2.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 4

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

16C. DATE SIGNED

BY 17-Apr-2018

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 N0002418R4209

X 9B. DATED (SEE ITEM 11)

21-Mar-2018

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

17-Apr-2018

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:

N0002418R4209

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

Paragraph 1.21 is modified as follows:

1.21 CYBERSECURITY

The Contractor shall implement information assurance requirements in accordance with the Risk Management

Framework (RMF) process for all delivered hardware and software. The Contractor shall provide Risk Management

Framework (RMF) deliverable Data. The RMF deliverable Data shall be in accordance with 1.21, 1.21.1, 1.21.2, 1.21.3, 1.21.4. The RMF deliverable package shall document all efforts taken to achieve Cybersecurity for equipment delivered under this contract. The RMF deliverable package shall list all open ports, protocols, and services and document the reason for all open ports, protocols and services. Any use of mobile code shall be documented and its uses shall be demonstrated to comply with RMF requirements.

CDRL: C014

SECTION F - DELIVERIES OR PERFORMANCE

The following Delivery Schedule item for CLIN 0001 has been changed from:

DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

8 mths. ADC 1 N/A

FOB: Destination

To:

DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

12 mths. ADC 1 N/A

FOB: Destination

The following offeror’s questions are answered:

Question #1 - Per FAR 15.404-4 para. (c) (3), it states: Before applying profit or fee factors, the contracting officer shall exclude any facilities capital cost of money included in the cost objective amounts. Is it the Government’s intent to base the percentage of fee on total estimated cost including facilities capital cost of money as mentioned above?

Answer #1: Fee is applied to the total estimated cost, excluding facilities capital cost of money.

Question #2 - Based on the synopsis posted on 06-07-2017 and as referenced in the Solicitation posted on 03-21-

2018, it states: “The Navy Sea Systems Command intends to procure, through full and open competition, Engine

Controllers (EC) on a Firm Fixed Priced basis…” FAR 52.215-20 is included in Section L of the solicitation, which is inconsistent with full and open competitions. Please confirm the intent of invoking FAR 52.215-20 and that it is not a requirement for submission of this solicitation.

Answer #2: FAR 52.215-20 is included in this solicitation as cost or pricing data is required to be submitted for

CLINs 0013 and 0014.

Question #3 - Attachment A Performance Specification, Section 8, Paragraph 8.0 - Is the intent of the requirement listed to include the source code of the Real Time Engine Model?

Answer #3 - The Government requires the source code of the Real Time Engine Model.

Question #4 - Attachment A, Performance Specification, Section 3, Paragraph 3.1 - There are conflicting requirements in paragraph 3.1.2:

VXWorks 7.0 or higher compiler (fully supported through calendar year 2022) shall be used for EC software development.

The contractor shall provide a RTOS that is in conformance with the Portable Operating System Interface (POSIX)

1003.1 Standard in its entirety.

VxWorks 7.0 is currently conformant to POSIX 1003.13 (PSE52). Wind River does not currently have plans to support the more general purpose POSIX 1003.1 specification in their RTOS.

Should the Offerer plan to supply VxWorks 7.0 or higher in conformance to POSIX 1003.13 or investigate alternative RTOS supplier that meets POSIX 1003.1?

Answer #4 - To clarify the requirement, the offeror shall supply VxWorks 7.0 or higher in conformance to POSIX

1003.13.

Question #5 - Will the Navy consider extending the delivery schedule for CLIN 0001 to 12 MACA?

Answer #5 – See Section F changes in this amendment.

Question #6 - Section C, Paragraph 1.21 - From the SOW, Section 1.21, both DIACAP and RMF are indicated. The offeror believes DIACAP is being phased out for DoD systems and the prevailing requirement is now to use RMF.

Is it the government’s intent to pursue both DIACAP accreditation and RMF authorization?

Answer #6 - The requirement is only to support RMF information assurance accreditation. Section C is modified as part of this amendment to remove the references to DIACAP.

Question #7 - Exhibit C, DD-1423 form C014 - This CDRL references the Navy’s old information assurance system known as DIACAP which has been replaced by the RMF process. Is this CDRL still correct?

Answer #7 - Exhibit C, Cybersecurity CDRL DD-1423 requirements have been updated as part of this amendment to delete the DIACAP references in CDRL C014.

Question #8 - RFP Section C, para 1.21 RMF is required but there is no reference or mention of Step 1 for the RMF process; Categorization. What has the Navy categorized the system as?

Answer #8 - The details of the execution of the RMF Step 1 requirements will be discussed by the Government with the successful offeror after contract award and is not required for submission of an offer.

Question #9 - RFP Section C, para 1.21 RMF is required but there is no reference or mention of Step 2 for the RMF process; Select Controls. Has the Navy selected the controls for the system? What is the list of required overlays?

What is the list of inherited controls?

Answer #9 - The details of the execution of the RMF Step 2 requirements will be discussed by the Government with the successful offeror after contract award and is not required for submission of an offer.

(End of Summary of Changes)