SF30_Amendment_0002_GSA_SP3_GS10F17LPP0003_03_03_2017.pdf
PDF 238 KB Posted
- Attached to
- GSA SmartPay 3
- Solicitation number
- GS10F17LPP0003
- Issued by
-
GSA Federal Acquisition Service
About this file
SF30 Amendment 0002 GSA SP3 GS10F17LPP0003 03_03_2017
View the file
Other files
Show all 11
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE PAGE OF PAGES
1 9
2. AMENDMENT/MODIFICATION NO.
3. EFFECTIVE DATE
03/03/2017
4. REQUISITION/PURCHASE REQ. NO.
5. PROJECT NO. (IF APPLICABLE)
6. Issued By Code QMAB 7. ADMINISTERED BY (If other than Item 6) Code
U.S. General Services Administration
Federal Acquisition Service
Center for Charge Card Acquisition
Division 1800F Street NW
Washington, DC 20405
SAME AS BLOCK 6
8. Name and Address of Contractor (No., street, county, State and ZIP Code (x) 9A. AMENDMENT OF SOLICITATION NO.
GS10F17LPP0003
X 9B. DATED (SEE ITEM 11)
02/01/2007
10A. MODIFICATION OF CONTRACT/ORDER NO.
10B. DATED (SEE ITEM 13)
CODE FACILITY CODE
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 Offers is extended X is not extended.
Offer's 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 ACKNOWLEDGEMENT 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)
N/A
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.)
Amendment 0002 to Solicitation GS10F17LPP0003 is amended as indicated on Pages 2-9.
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) 16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
15B. CONTRACTOR/OFFEROR 15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 16C. DATE SIGNED
________________________________________ BY ______________________________________________
(Signature of person authorized to sign) (Signature of Contracting Officer)
NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (REV. 10-83)
PREVIOUS EDITION UNUSABLE Prescribed by GSA, FAR (48 CFR) 53.243
Amendment 0002 Solicitation Number GS10F17LPP0003 Page 2 of 9
Amendment 0002 is hereby issued as follows:
A. Change Section C.7.1 Electronic Access System, Table of Requirements, Requirement 11 as follows:
DELETE:
The EAS shall treat locked accounts as follows:
a) Locked accounts shall only be unlocked by calling a Customer Service Security representative.
b) The system shall prompt the user when their account is locked.
c) The system shall generate a unique and secure incident ID number to include in the email to the account holder.
d) The system shall email instructions on how to unlock the account to the email addresses on file for the account holder.
e) The system shall verify the accountholder information before unlocking the account.
f) Customer Service Security representative shall verify the incident ID number provided before unlocking the account.
g) The system shall send a Notification of locked accounts to the A/OPC or authorizing official of the designated agency personnel the account belongs to.
REPLACE:
The EAS shall treat locked accounts as follows:
a) Locked accounts shall only be unlocked by calling a Customer Service Security representative. In the event a cardholder can't reach a Customer Service representative, the
A/OPC shall have the ability to unlock accounts as well without having to ask validation questions of the cardholder.
b) The system shall prompt the user when their account is locked.
c) The system shall generate a unique and secure incident ID number to include in the email to the account holder.
d) The system shall email instructions on how to unlock the account to the email addresses on file for the account holder.
e) The system shall verify the accountholder information before unlocking the account.
f) Customer Service Security representative shall verify the incident ID number provided before unlocking the account.
g) The system shall send a Notification of locked accounts to the A/OPC or authorizing official of the designated agency personnel the account belongs to. The A/OPC shall have a reset account protocol or process to unlock the account from the EAS without having to use customer service.
*The area highlighted herein are the only changes to the section.
Amendment 0002 Solicitation Number GS10F17LPP0003 Page 3 of 9
B. Change Section C.7.1.1 EAS Load Testing Results as follows:
The GSA SmartPay Program has over three (3) million account holders from customer agencies/organizations who shall have access to the EAS. The Contractor shall provide the GSA
COR an EAS that meets industry standards for web server bench-marking and provide the results and testing tool outputs across varying combinations of requests and loads per customer agency/organization to the GSA COR, in the following areas:
Load Size Testing at three (3) million concurrent users to report on system performance and noted reductions in response times/errors/etc.;
Scaled Load Testing from 3 million concurrent users to 2.5 million, 2 million, 1.5 million and from 1 million to 500 hundred thousand users. Each scaled group is representing concurrent users with 5-10 transactions at a time;
Scaled Load Testing results to be completed for 5 simulations in each area and results presented graphically and as reported from the testing tools used;
Average Response Times for each new connection or request;
Peak Response Times for each new connection or request;
Response Error Rates;
Number of requests that can be served per second;
Elapsed time from receiving a request to processing and sending responses (satisfying requests/completing processes or operations which require responses to the requestor);
Throughput in bytes per second (depending bandwidth, file size, etc.);
CPU Utilization for the transaction servers; Web Services; and memory utilization; and
Latency.
The GSA SmartPay Program has over three (3) million account holders from customer agencies/organizations who shall have access to the EAS. The Contractor shall provide the GSA
COR an EAS that meets industry standards for web server bench-marking and provide the results and testing tool outputs across varying combinations of requests and loads per customer agency/organization to the GSA COR, in the following areas:
Load Size Testing at 1.5 million concurrent users (50%) to report on system performance and noted reductions in response times/errors/etc.;
Scaled Load Testing from 1.5 million concurrent users to 1 million and from 1 million to
500 hundred thousand users. Each scaled group is representing concurrent users with 5-10 transactions at a time;
Scaled Load Testing results to be completed for 5 simulations in each area and results presented graphically and as reported from the testing tools used;
Average Response Times for each new connection or request;
Peak Response Times for each new connection or request;
Response Error Rates;
Number of requests that can be served per second;
Amendment 0002 Solicitation Number GS10F17LPP0003 Page 4 of 9
Elapsed time from receiving a request to processing and sending responses (satisfying requests/completing processes or operations which require responses to the requestor);
Throughput in bytes per second (depending bandwidth, file size, etc.);
CPU Utilization for the transaction servers; Web Services; and memory utilization; and
Latency.
C. Change Section J.16 Attachment 16: Program and Transaction Data Table as follows:
J.16 Attachment 16: Program and Transaction Data Table
J.16 Attachment 16: Program and Transaction Data Table - Attachment revised to add note to the fleet transaction data table to allow agency/bureau 4732 to nullify specific fleet data elements.
*The area highlighted herein is the only change to the attachment.
D. Change Section J.19 Attachment 19: Live Test Demonstration (LTD) Scripts as follows:
J.19 Attachment 19: Live Test Demonstration (LTD) Scripts
J.19 Attachment 19: Live Test Demonstration (LTD) Scripts – Attachment revised the step description/user action and/or expected results for Steps 2, 3, 5, 62, 63, 64, 65, 68, 76, 82, and
87.
*The area highlighted herein are the only changes to the attachment.
E. Change Section L.3.4.1.1 Sub-factor 1A, Technical Expertise, General Requirement
C.6.2 Risk Mitigation Assistance, Focus Item Bullet 2 For Proposal Options 1 and 3, Sub-bullet 1 Travel Business Line as follows:
For Proposal Options 1 and 3:
o Travel Business Line: Specific to the GSA SmartPay Tax Advantage Travel Card Accounts, provide the Offeror’s approach to delinquency controls for CBA and IBA transactions under a single card/account.
Amendment 0002 Solicitation Number GS10F17LPP0003 Page 5 of 9
For Proposal Options 1 and 3:
o Travel Business Line: Specific to the GSA SmartPay Tax Advantage Travel Card Accounts, provide the Offeror’s approach to risk mitigation assistance for CBA and IBA transactions under a single card/account.
*The area highlighted herein is the only change to the attachment.
F. Change Section L.3.4.3.1 LTD Package as follows:
Offerors must provide a copy of the LTD Package that shall include:
1) Points of Contract including name, position, and company affiliation.
2) Describe the electronic access and reporting system proposed.
3) Describe any known issues with the EAS being presented for LTD.
4) Describe any EAS requirements that were not implemented in the test environment being submitted for the LTD.
5) Describe and provide the Offeror’s test results based EAS LTD test criteria and test steps provided pursuant to J.19 Attachment 19: Live Test Demonstration (LTD) Scripts.
6) Describe how Section 508 testing was done and if the EAS conforms with all Section 508 standards; describe and show the certification of the testing if conformance is already achieved.
If EAS does not presently conform to Section 508 standards, the Offeror shall provide discussion on their approach to ensure their EAS will conform to Section 508 of the Rehabilitation Act of
1973 before competing for task order awards. NOTE: Offerors will not be eligible to compete for task orders under this contract unless they are determined to conform to Section 508 (see H.12.9
Ordering Process for details).
7) Describe the EAS test environment that has been established for the LTD, the test data, and how evaluators will access the EAS.
8) Include a detailed discussion of the types of data elements and levels of data that can be captured or obtained by the Offeror and provided to the Government at both the agency and GSA level with the proposed system.
9) Discuss the Offeror’s ability to provide or obtain the data elements specified in C.7.1
Electronic Access System.
10) Copies of EAS specific scripts that include detailed steps required to execute the actions outlined in the GSA provided action list. Refer to J.19 Attachment 19: Live Test Demonstration
(LTD) Scripts.
Offerors must provide a copy of the LTD Package that shall include:
1) Points of Contract including name, position, and company affiliation.
2) Describe the electronic access and reporting system proposed.
3) Describe any known issues with the EAS being presented for LTD.
4) Describe any EAS requirements that were not implemented in the test environment being submitted for the LTD.
Amendment 0002 Solicitation Number GS10F17LPP0003 Page 6 of 9
5) Describe and provide the Offeror’s test results based EAS LTD test criteria and test steps provided pursuant to J.19 Attachment 19: Live Test Demonstration (LTD) Scripts.
6) Describe how Section 508 testing was done and if the EAS conforms with all Section 508 standards; describe and show the certification of the testing if conformance is already achieved.
If EAS does not presently conform to Section 508 standards, the Offeror shall provide discussion on their approach to ensure their EAS will conform to Section 508 of the Rehabilitation Act of
1973 before competing for task order awards. NOTE: Offerors will not be eligible to compete for task orders under this contract unless they are determined to conform to Section 508 (see H.12.9
Ordering Process for details).
7) Describe the EAS test environment that has been established for the LTD, the test data, and how evaluators will access the EAS.
8) Include a detailed discussion of the types of data elements and levels of data that can be captured or obtained by the Offeror and provided to the Government at both the agency and GSA level with the proposed system.
9) Discuss the Offeror’s ability to provide or obtain the data elements specified in C.7.1
Electronic Access System.
10) Copies of EAS specific scripts that include detailed steps required to execute the actions outlined in the GSA provided action list. Refer to J.19 Attachment 19: Live Test Demonstration
(LTD) Scripts.
11) Provide at least one point of contact name and phone number for questions / support for testers accessing the EAS LTD test environment. POCs should be available Monday – Friday, 8:00am to 5:00pm Eastern Time to answer questions and provide support within a 2 hour turn-around period during the offer acceptance period (see L.2.10 for details).
For the purposes of the LTD, the email address spcard@gsa.gov will be utilized to establish test user accounts across authorized users as an "administrator" and as a test user for individual roles
(e.g. account holder user only, card manager only). All authorized user views (e.g. account holder, card manager, A/OPC, account manager, AO) should be accessible through this email address. Actual names or numbers of evaluators and/or real credentials will not be provided.
See C.7.1 for further information on access by authorized users by requirement number.
Some LTD scripts are date sensitive, specifically Scenario 2, Step 6 which requires a demonstration of password expiration and prompting 15 days prior to password change. Testers should be able to manually set the password expiration dates in a mmddyyyy format (example for March 2nd 2017 is 03022017) for users AND the number of days to prompt the user before a password expires (current requirement states 15 which should be the default value). The option to set the password expiration date and number of days to notify a user of an expiring password should only be available under the “administrator” test role in the LTD test environment.
Amendment 0002 Solicitation Number GS10F17LPP0003 Page 7 of 9
G. Change the language under Section M.1 FAR 52.212-2 Evaluation – Commercial Items as follows:
(a) The Government will award multiple contracts by proposal submission options resulting from this solicitation to the responsible offeror’s whose offer conforming to the solicitation will be most advantageous to the Government, price and other factors considered. The factors are described in M.3 Technical Evaluation and M.4 Price Evaluation Criteria.
Evaluation Factors
Factor 1 – Technical Excellence o Subfactor 1A – Technical Expertise o Subfactor 1B – Transition Plan
Factor 2 – Operational Quality Assurance
Factor 3 – Live Test Demonstration (LTD)
Factor 4 – Past Performance
Factor 5 – Small Business Participation
Factor 6 – Price
Factors 1, 2, and 3 are equal in importance. Factors 4 and 5 are less important than Factors 1, 2, and 3. Factors 4 and 5 are equal. Under Factor 1, Subfactors 1A and 1B are equal in importance.
Evaluations for Factors 1 through 5 will be combined to determine an overall adjectival rating for the technical proposal. Factor 6 will not be adjectivally rated.
(b) The Technical Factors 1 through 5, when combined, are more important than the Price
Factor. As proposals become more equal technically, price becomes a more important factor in the trade-off decision.
(c) Options. The Government will include option periods as part of the evaluation for award. The
Government may determine that an offer is unacceptable if pricing offered is significantly unbalanced. Evaluation of options shall not obligate the Government to exercise the option(s).
(d) A written notice of award or acceptance of an offer, mailed or otherwise furnished to the successful Offeror within the time for acceptance specified in the offer, shall result in a binding contract without further action by either party. Before the offer’s specified expiration time, the
Government may accept an offer whether or not there are negotiations after its receipt, unless a written notice of withdrawal is received before award.
(a) The Government will award multiple contracts by proposal submission resulting from this solicitation to the responsible offerors whose offer conforming to the solicitation will be most advantageous to the Government, price and other factors considered. The factors are described in
M.3 Technical Evaluation and M.4 Price Evaluation Criteria.
Amendment 0002 Solicitation Number GS10F17LPP0003 Page 8 of 9
Evaluation Factors
Factor 1 – Technical Excellence o Subfactor 1A – Technical Expertise o Subfactor 1B – Transition Plan
Factor 2 – Operational Quality Assurance
Factor 3 – Live Test Demonstration (LTD)
Factor 4 – Past Performance
Factor 5 – Small Business Participation
Factor 6 – Price
Factors 1, 2, and 3 are equal in importance. Factors 4 and 5 are less important than Factors 1, 2, and 3. Factors 4 and 5 are equal. Under Factor 1, Subfactors 1A and 1B are equal in importance.
Evaluations for Factors 1 through 5 will be combined to determine an overall adjectival rating for the technical proposal. Factor 6 will not be adjectivally rated.
(b) The Technical Factors 1 through 5, when combined, are significantly more important than the
Price Factor.
(c) Options. The Government will include option periods as part of the evaluation for award. The
Government may determine that an offer is unacceptable if pricing offered is significantly unbalanced. Evaluation of options shall not obligate the Government to exercise the option(s).
(d) A written notice of award or acceptance of an offer, mailed or otherwise furnished to the successful Offeror within the time for acceptance specified in the offer, shall result in a binding contract without further action by either party. Before the offer’s specified expiration time, the
Government may accept an offer whether or not there are negotiations after its receipt, unless a written notice of withdrawal is received before award.
H. Change the language under Section M.3.2 Factor 2 – Operational Quality Assurance
(paragraph 1) as follows:
In evaluating Operational Quality Assurance, the Government will look specifically of the
Offeror’s full understanding of the requirements to establish an operational structure to ensure high-quality, seamless operations.
In evaluating Operational Quality Assurance, the Government will look specifically at the
Offeror’s full understanding of the requirements to establish an operational structure to ensure high-quality, seamless operations.
*The area highlighted herein is the only change to the section.
Amendment 0002 Solicitation Number GS10F17LPP0003 Page 9 of 9
I. Change the language under Section M.4 Price Evaluation Criteria as follows:
The Offeror’s price proposal will be evaluated using one or more of the techniques defined in
FAR 15.404, in order to determine if it is reasonable and realistic. Pricing assumptions will also be evaluated to ascertain the level of understanding of the Government's requirements and the degree of risk the Offeror’s assumptions pose to the Government.
The Offeror’s price proposal will be evaluated using one or more of the techniques defined in
FAR 15.404, in order to determine if it is fair and reasonable. Pricing assumptions will also be evaluated to ascertain the level of understanding of the Government's requirements and the degree of risk the Offeror’s assumptions pose to the Government.
J. Change the language under Section M.5 Notice of Award as follows:
A written notice of award or acceptance of an offer mailed or otherwise furnished to the otherwise successful Offeror within the time for acceptance specified in the offer shall result in a binding contract without further action by either party. Before the offer's specified expiration time, the Government may accept an offer, whether or not there are negotiations after its receipt, unless a written notice of withdrawal is received before award.
A written notice of award or acceptance of an offer mailed or otherwise furnished to the successful Offeror within the time for acceptance specified in the offer shall result in a binding contract without further action by either party. Before the offer's specified expiration time, the Government may accept an offer, whether or not there are negotiations after its receipt, unless a written notice of withdrawal is received before award.
File details come from the government source that posted it. Updated .