91003119R0003_0010.pdf

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 or (c) By separate letter or electronic communication 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 letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

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

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

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.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

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

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

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, 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)

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.

15C. DATE SIGNED

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

16C. DATE SIGNED

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

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

Previous edition unusable

2. AMENDMENT/MODIFICATION NUMBER

91003119R00030010

FSA-FS1

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

See the attached Continuation Pages for changes to the solicitation.

United States Department of Education Federal Student Aid Business Support Group, 830 First St NE - Suite 91F3 Washington, DC 20202

See Block 6

NA

TBD

91003119R0003

NA

1 6

06/12/2019

04/15/2019

SF-30 Block 14 Continuation Pages 910031-19-R-0003_0010

The purpose of this amendment is to (1) change the page limit for Volume One, (2) replace EBC references with ESB, (3) update the transition-in requirements, (4) add two attachments to the RFP, and (5) update the list of existing ITA and ESB capabilities. As a result, the solicitation is hereby amended to incorporate the following changes:

1. Regarding Section VI (Instructions to Offerors), 4.1 (Proposal Organization, Formatting, and Page Limitations), the page limit in the table assigned to Volume One (Relevant Experience) is hereby modified as follows:

FROM

26 Pages

TO

30 Pages

2. Regarding Section VII (Evaluation Criteria), 3.0 (All-or-None Procurement Notifications), the second paragraph of this subsection is modified as follows:

FROM

The procurement of Task Orders 0001 (ITA) and 0002 (EBC) are all-or-none procurements; therefore, one vendor will be awarded a task order for each requirement.

TO

The procurement of Task Orders 0001 (ITA) and 0002 (ESB) are all-or-none procurements; therefore, one vendor will be awarded a task order for each requirement.

3. Regarding Section IX (ID/IQ Contract FSA IT Compliance and Other Work Requirements), subsection 43.1.1 (Support Transition-In Planning), the third and fourth paragraphs are hereby modified as follows:

FROM

The period between Contract award date and Contract start date will constitute the phase-in period. During the phase-in period, the Contractor shall prepare to assume full responsibility for all areas of operation in accordance with the terms and conditions of this contract. The Contractor shall take all actions necessary for a smooth transition of the contracted operations.

This period will be approximately 120 calendar days in duration. The Government will make all facilities and equipment accessible to the Contractor during the phase-in period.

During the last 60 days of the phase-in period, the Contractor's management personnel will be permitted to observe any on-going operations, as approved by the CO.

TO

The period between the effective Contract date and Contract start date will constitute the phase-in period. During the phase-in period, the Contractor shall prepare to assume full responsibility for all areas of operation in accordance with the terms and conditions of this contract. The Contractor shall take all actions necessary for a smooth transition of the contracted operations.

This period will be approximately two months in duration. The Government will make all facilities and equipment accessible to the Contractor during the phase-in period. During the phase-in period, the Contractor's management personnel will be permitted to observe any on-going operations, as approved by the CO.

4. Regarding RFP Section XI (Solicitation and Contract Attachments) the following attachments are added to the list of solicitation attachments and each is added by separate attachments to the solicitation (these attachments are added in response to a question regarding APIs to help clarify EMAS environments):

(8) Attachment 8 – ESB Interfaces (This attachment is for reference only and will not be included in any awards.)

(9) Attachment 9 – Approximate EMAS Environments (This attachment is for reference only and will not be included in any awards. The term “Approximate” is used as this document was sanitized to remove sensitive information.)

5. Regarding Attachment One (ITA Performance Work Statement), C.10.1 (1) is modified as follows:

FROM:

(1) Maintain, develop, deploy, customize, optimize, and manage the following for existing and added ITA products and tools, including associated APIs and product databases: (1) configuration, (2) application deployments, (3) existing and new capabilities and features for ITA products and tools; and (4) complete enhancements that add customizations for specific FSA applications. Automation (e.g., by means of scripts) and minimizing downtime to users shall be included to the maximum extent possible. Existing capabilities include the Reusable Common Services (RCS), including but not limited to: Audit Tracking Framework (ATF)

a. Authentication APIs

(a) Component Factory

(b) Email

(c) Exception

(d) IMAP

(e) Logging

(f) Persistence

(g) Search

(h) Tag Library

TO:

(1) Maintain, develop, deploy, customize, optimize, and manage the following for existing and added ITA products and tools, including associated APIs and product databases: (1) configuration, (2) application deployments, (3) existing and new capabilities and features for ITA products and tools; and (4) complete enhancements that add customizations for specific FSA applications. Automation (e.g., by means of scripts) and minimizing downtime to users shall be included to the maximum extent possible. Existing capabilities include the Reusable Common Services (RCS), including but not limited to:

(a) Audit Tracking Framework (ATF)

(b) Component Factory

(c) Email

(d) Exception

(e) IMAP

(f) Logging

(g) Persistence

(h) Search

(i) Tag Library

6. Regarding Attachment One (ITA Performance Work Statement), subsection F.4

(Deliverables Table), the “Description” column in the table for item 37 is modified as follows:

FROM:

This plan describes the Contractor’s approach to achieving a smooth transfer of all EBC activities during the Transition-Out Period.

TO:

This plan describes the Contractor’s approach to achieving a smooth transfer of all ITA activities during the Transition-Out Period.

7. Regarding Attachment Two (ESB Performance Work Statement), C.10.1 (1) is modified as follows:

FROM:

(1) Maintain, develop, deploy, customize, optimize, and manage the following for existing and added ESB products and tools, adapters, including associated APIs and product databases: (1) configuration, (2) application deployments, (3) existing and new capabilities and features for ESB products and tools; and (4) complete enhancements that add customizations for specific FSA applications. Automation (e.g., by means of scripts) and minimizing downtime to users shall be included to the maximum extent possible. Existing capabilities include the Reusable Common Services (RCS), including but not limited to:

(a) Audit Tracking Framework (ATF)

(b) Authentication APIs

(c) Component Factory

(d) Email

(e) Exception

(f) IMAP

(g) Logging

(h) Persistence

(i) Search

(j) Tag Library

TO:

(1) Maintain, develop, deploy, customize, optimize, and manage the following for existing and added ESB products and tools, adapters, including associated APIs and product databases: (1) configuration, (2) application deployments, (3) existing and new capabilities and features for ESB products and tools; and (4) complete enhancements that add customizations for specific FSA applications. Automation (e.g., by means of scripts) and minimizing downtime to users shall be included to the maximum extent possible. Existing capabilities include the Reusable Common Services (RCS), including but not limited to:

(a) Audit Tracking Framework (ATF)

(b) Component Factory

(c) Email

(d) Exception

(e) Logging

(f) Persistence

(g) Tag Library

8. Regarding Attachment Two (ESB Performance Work Statement), subsection F.4

(Deliverables Table), the “Description” column in the table for item 37 is modified as follows:

FROM:

This plan describes the Contractor’s approach to achieving a smooth transfer of all EBC activities during the Transition-Out Period.

TO:

This plan describes the Contractor’s approach to achieving a smooth transfer of all ESB activities during the Transition-Out Period.

9. A fully conformed document that shows all changes made by Amendments 0001-0010 to the original document entitled 910031-19-R-0003 is hereby added as part of this amendment and is titled “910031-19-R-0003 (Fully Conformed).” The formatting of this document is MS Word and therefore previously embedded documents may be more accessible in this document.