H98210-17-R-0007-01.pdf

OMB Approval 2700-0042

1. CONTRACT ID CODE PAGE OF PAGES

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1 7

2. AMENDMENT/MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicable)

01 8 Aug 17

6. ISSUED BY CODE H98210 7. ADMINISTERED BY (If other than Item 6)

CODE

H98210- Defense Human Resources Activity 4800 Mark Center Drive, Suite 06J25-01 Alexandria, VA 22350-4000

SAME AS BLOCK 6

8. NAME AND ADDRESS OF CONTRACTOR (No. Street, county, State and ZIP: Code) () 9A. AMENDMENT OF SOLICITATION NO.

X H98210-17-R-0007

9B. DATED (SEE ITEM 11)

14 Jul 17

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

(a) By completing Items 8 and 15, and returning one (1) copy 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 DATA 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 data 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 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.)

SEE CONTINUATION

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

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

MELISSA TAMAYO, CONTRACTING OFFICER

571-372-1981 melissa.s.tamayo.civ@mail.mil

15B. CONTRACTOR/OFFEROR 15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 16C. DATE SIGNED

(Signature of person authorized to sign)

BY _____________________________________________

(Signature of Contracting Officer)

NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (REV. 10-83)

PREVIOUS EDITION UNUSABLE Computer Generated Prescribed by GSA

FAR (48 CFR) 53.243

OMB Approval 2700-004

H98210-17-R-0007-01

SF30 Continuation

The purpose of this amendment is to:

A. Change the Offer Due Date and Time To 11:00AM Local Time on 17 Aug 2017.

B. Provide Questions, Answers and RFQ changes as follows:

Question 1. The solicitation mentions getting access to MLA data. But from my understanding this is different from SCRA. Will this integration be able to provide the certificate that is downloadable from the SCRA site based on service member details?

Answer: This solicitation is only for MLA data. SCRA data is different and is not part of this solicitation.

RFQ Change: None

Question 2. Are extensions beyond the 8/8/17 deadline for contract completion available?

Answer: 8/8/17 was the proposal due deadline. It is being extended.

RFQ Change: The proposal due date has been changed.

Question 3. Can [the offeror] provide a "redline" contract version for discussion and will the DoD entertain suggested revisions to the contract?

Answer: No, but you can provide this for consideration for any potential follow-on effort.

RFQ Change: None

Question 4. What happens to the current AtO once [the offeror] signs the new contract?

Answer: The offeror shall provide a copy of its current and valid NUSGATO in accordance with PWS paragraph 4.3, RFQ Subfactor 2 (page 47) and RFQ Appendix A.

RFQ Change: None

Question 5. (b)(4) Factor 1 – Technical (p.47) Within the technical portion of the proposal, can [the offeror] define how [it] would satisfy the four requirements listed on p.13 of Solicitation (PWS Attachment A; Performance

Requirements Summary)?

Answer: Technical proposals must address the Technical Subfactors in accordance with (b)(4) Factor 1 – Technical

(p.47)

RFQ Change: None

Question 6. (b)(4) Factor 1 – Technical (p.47) Subfactor 2. Assessment & Authorization

What is an example of an Assessment and Authorization (A&A) that must be provided?

Answer: It is the NUSGATO

RFQ Change: Revised Subfactor 2 to read, “ The offeror must provide an assessment and authorization (A&A) by submitting a Non-United States Government Authority to Operate (NUSGATO). (See Appendix A)”

Question 7. (b)(4) Factor 1 – Technical (p.47) Subfactor 3. Encryption

Does the encryption requirement stop when the DoD has handed off data to [the offeror]?

Answer: No; per PWS requirements 4.3.1, 4.3.2, and 4.3.4, encryption of MLA data received by Contractor must be maintained in both transmission and storage.

RFQ Change: None

Question 8. Request the requirement to "consume quarterly maintenance updates" be removed as the requirement is undefined and may require IT/technological changes that were not previously known, budgeted for, and/or may not be technologically feasible to accommodate.

Answer: No; offerors that cannot consume quarterly maintenance updates to the direct connection will be deemed technically unacceptable, system access will be terminated and contract termination procedures may follow.

RFQ Change: None

Question 9. Request the requirement to submit to "periodic surveillance" be removed as the scope and manner of the audit is not defined.

Answer: Reference PWS Attachment A, 4.1.1 and the Quality Assurance Surveillance Plan (QASP). The

Government may conduct surveillance on any of the contract requirements. The Performance Requirements

Summary merely captures the ones that will be measured and reported on consistently. The surveillance will be unannounced (and via observation, system access issues or customer complaint) in order to ensure contract requirements are being followed, however the contractor will be notified/present as it would be conducted at the contractor’s site or via phone or electronic commerce.

RFQ Change: None

Question 10. Reference PWS paragraph 4.1.1 - What types of maintenance items would [the offeror] expect to see included in the quarterly updates?

Answer: Quarterly maintenance of the interface may include but not be limited to changes to required fields in interface request messages, changes to encryption standards, changes to response message contents, or other maintenance changes necessary to provide for the secure and accurate transmission of MLA data.

RFQ Change: None

Question 11. Reference PWS paragraph 4.1.1 - Will the DoD perform Systems & User Acceptance testing with

[the offeror] prior to distributing updates to ensure the updates don't create additional risk exposure to bank systems, customer data, encryption methodology or networks?

Answer: Yes; a testing environment and testing periods will be available prior to all required maintenance releases.

RFQ Change: None

Question 12. Reference PWS paragraph 4.1.1 - If [the offeror] fails to consume a quarterly release, would those changes be forced upon [the offeror] by the DoD during the next quarterly release.

Answer: Failure to consume quarterly releases could result in termination of the direct connection or any contract remedy available in the Federal Acquisition Regulation (FAR), to include contract termination.

RFQ Change: None

Question 13. Reference PWS Attachment A, 4.1.1 If [the offeror] fails to consume two consecutive quarterly releases, what action will the DoD take against [it](financial, other)?

Answer: See the response to Question 12.

RFQ Change: None

Question 14. Reference PWS Attachment A, 4.3.1 Request the requirement to submit to "periodic surveillance" be removed as the scope and manner of the audit is not defined.

Answer: See the response to question 9

RFQ Change: None

Question 15. PWS paragraph 4.3.1 - What types of device Encryption does the DoD consider acceptable?

Answer: See the PWS and Applicable Documents Referenced in the PWS

RFQ Change: None

Question 16. PWS paragraph 4.3.1 - What types of network Encryption does the DoD consider acceptable?

Answer: See response to Question 15

RFQ Change: None

Question 17. PWS paragraph 4.3.1 - If [the offeror] fails to notify the DoD within 1 hour of a security failure, what action will the DoD take against [it](financial, other)?

Answer: See the answer to Question 12

RFQ Change: None

Question 18. PWS paragraph 4.3.1 - What does the DoD classify as a security failure?

Answer: Any instance of failure to maintain encryption of MLA data on all devices and networks used to obtain and transmit MLA data resulting from either periodic surveillance or customer complaint.

RFQ Change: None

Question 19. PWS paragraph 4.3.1 - What does the DoD classify as a customer complaint?

Answer: Any complaint received in regards to the contract.

RFQ Change: None

Question 20. Is [the offeror] permitted to challenge the veracity of a customer complaint?

Answer: The Government will investigate any customer complaint it receives and will solicit the Contractor’s input on such complaints as is necessary.

RFQ Change: None

Question 21. PWS paragraph 4.5 - Request the requirement to provide expected monthly volume be removed as business conditions are unpredictable and volume can be influenced by numerous factors including those external to [the offeror]. Additionally, the format and method of transmitting that information may not be viable given the method of transmission is not specified in the solicitation and could be technologically impossible to accommodate.

Answer: This requirement is critical to the optimal efficiency of the direct connect interface and will not be removed from the PWS.

RFQ Change: None

Question 22. Reference PWS Attachment A, 4.3.1 - Request the requirement to submit to "periodic surveillance" be removed as the scope and manner of the audit is not defined.

Answer: See the answer to Question 9

RFQ Change: None

Question 23. PWS paragraph 4.5 - If the 20th falls on a weekend or a federally recognized holiday, is [the offeror] expected to transmit schedule and volume information to the DoD?

Answer: The PWS states “no later than the 20th”

RFQ Change: None

Question 24. Reference PWS Attachment A, 4.5 - If [the offeror] fails to provide the DoD with schedule and volume information more than two instances during the year, what action will the DoD take against [it](financial, other)?

Answer: See the answer to Question 12

RFQ Change: None

Question 25. Reference PWS paragraph 4.5 - How does the DoD define a year, calendar of fiscal? If fiscal, what is considered the first month?

Answer: In reference to the Performance Requirements Summary at PWS Attachment A, a year is the period of performance of the contract. This is the year that the surveillance will be consolidated and reported in the

Contractor Performance Assessment Reporting System (CPARS) if we decide it is necessary (ie. poor performance/not meeting the requirements of the contract).

RFQ Change: None

Question 26. Reference PWS Attachment A, 4.5 - What does the DoD classify as a customer complaint?

Answer: See the response to Question 19

RFQ Change: None

Question 27. Reference PWS Attachment A, 4.5 - Is [the offeror] permitted to challenge the veracity of a customer complaint?

Answer: See the response to Question 20

RFQ Change: None

Question 28. PWS Paragraph 4.5.1 - Request the requirement to provide non-personally identifiable "financial well being" of covered borrowers as well as entire portfolio be removed as "financial well being" is undefined and may require submission of proprietary and/or confidential information. Additionally, the format and method of transmitting that information may not be viable given the method is not specified in the solicitation and could be technologically impossible to accommodate.

Answer: This information is no longer being requested

RFQ Change: Remove paragraph 4.5.1 from the PWS

Question 29. Reference PWS Attachment A, 4.5.1 - Request the requirement to submit to "periodic surveillance" be removed as the scope and manner of the audit is not defined.

Answer: This information is no longer being requested

RFQ Change: Remove 4.5.1 from PWS Attachment A

Question 30. If the 20th falls on a weekend or a federally recognized holiday, is [the offeror] expected to transmit financial well-being information to the DoD?

Answer: This information is no longer being requested

RFQ Change: Remove Deliverable for PWS 4.5.1 from the Table at PWS paragraph 5.0

Question 31. Reference PWS Attachment A, 4.5.1 - If [the offeror] fails to provide the DoD with financial well-being information more than 2 instances during the year, what action will the DoD take against [the offeror]

(financial, other)?

Answer: See the response to Question 29

RFQ Change: See Question 29

Question 32. Reference PWS paragraph 4.5.1 - How does the DoD define a year, calendar of fiscal? If fiscal, what is considered the first month?

Answer: See the response to Question 28

RFQ Change: See Question 28

Question 33. Reference PWS Attachment A, 4.5 - What does the DoD classify as a customer complaint?

Answer: See the response to Question 29

RFQ Change: See Question 29

Question 34. Reference PWS Attachment A, 4.5.1 -Is [redacted name] permitted to challenge the veracity of a customer complaint?

Answer: See the response to Question 29

RFQ Change: See Question 29

End of Amendment