36C25520Q0439 0001 Amendment.docx

36C25520Q0439_0001

5. PROJECT NUMBER (if applicable)

CODE

7.

ADMINISTERED BY

2. AMENDMENT/MODIFICATION NUMBER

CODE

6. ISSUED BY

8. NAME AND ADDRESS OF CONTRACTOR

4. REQUISITION/PURCHASE REQ. NUMBER

3. EFFECTIVE DATE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED

PAGE OF

PAGES

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED

BPA NO.

1. CONTRACT ID CODE

FACILITY CODE

CODE

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:

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

E. IMPORTANT:

is extended,

(a) By completing Items 8 and 15, and returning __________ copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; 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 is not extended.

12. ACCOUNTING AND APPROPRIATION DATA

(REV. 11/2016)

is required to sign this document and return ___________ copies to the issuing office.

is not, 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.

15C. DATE SIGNED

B. THE ABOVE NUMBERE

D CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES

SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

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 amendmen t, and is received prior to the opening hour and date specified.

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER

Contractor

16C. DATE SIGNED

14. DESCRIPTION OF AMENDMENT/MODIFICATION

16B. UNITED

STATES OF AMERICA

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

16A. NAME AND TITLE OF

CONTRACTING OFFICER

15B. CONTRACTOR/OFFEROR

STANDARD FORM 30

PREVIOUS EDITION NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.243 (Type or print) (Type or print) (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

(Number, street, county, State and ZIP Code) (If other than Item 6) (Specify type of modification and authority) (such as changes in paying office, appropriation date, etc.)

(If required)

(SEE ITEM 11)

(SEE ITEM 13)

(X)

CHECK

ONE

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

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

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF

SOLICITATIONS

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

(Signature of person authorized to sign) (Signature of Contracting Officer) 07-21-2020 None 36C255 Department of Veterans Affairs Network Contracting Office (NCO) 15 3450 S 4th Street Trafficway Leavenworth KS 66048 36C255 Department of Veterans Affairs Network Contracting Office (NCO) 15 3450 S 4th Street Trafficway Leavenworth KS 66048 To all Offerors/Bidders

36C25520Q0439 07-16-2020

X X X

See CONTINUATION Page X 1 (One) St. Louis VA Healthcare System - St. Louis, MO 63106 Secure Text Message Service

1. See page s and 3 for technical questions and answer s.

2. All other terms and conditions remain the same in the RFQ.

Khamoy Sysengchanh Contracting Officer

VA-VHA-2020-6F87AD73

St. Louis VA Healthcare System Secure Text Messaging Service Questions and Answers

1. The recent carrier rules regarding outbound text messaging require a cost for sending text messages from both short codes and long codes (10 digit). Your contract, however, calls for unlimited messaging. Based on this, is it possible to obtain an estimate of the amount of messages you intend to send or the number of consumers in your database?

We serve 60,000 Veterans in our cachement area – we do not anticipate all Veterans would participate, but that about ¼ (or 15,000) would.

2. Will any of the messages be broadcasting the same message to all consumers?

We do not anticipate sending out “broadcast messages”.

3. Will the messages be considered "P to P" (Peer to Peer messaging) meaning an individual message sent to each consumer and without an automated message system?

Yes. However, we do want the ability to have algorithms respond automatically – with our input on developing these algorithms.

4. Who will be responsible for text message charges? Vendor or VA? If Vendor is to cover the cost of sending text messages, then would the government please provide the estimated number of enrolled Veterans and the desired number of messages per Veteran?

Vendor will be responsible. We anticipate around 15,000 end users; anticipate around 1,200/month (estimate) users.

5. The facilities listed on the same page only included St. Louis’ medical centers and CBOCs. Can the Government please clarify the number of facilities? Is it just St. Louis or all of VISN 15?

Just St. Louis VAHCS (John Cochran, Jefferson Barracks) and the 7 CBOC’s listed in the SOW

6. Can the Government clarify expectations on 24/7 support? Is it acceptable for the Vendor to be able to receive issues without having someone manning the support desk 24/7? What’s the government’s expected response time to issues?

We expect some kind of response automatically/immediately (could be AI) – no more than one business day of response time – we prefer 24/7 actual response.

7. It seems that the Government expects the Contractor to be onsite. Is the government expecting the Contractor to provide staff onsite at VA facilities? If yes, at how many locations and how many days per week? No expectations for contractor to be onsite.

8. How does the Government expect the Vendor to handle undeliverable text messages and wrong phone numbers? Notify the COR

9. Can we get an approximate of how many end users there is expected to be?

We anticipate around 15,000 end users

10. Can we get an approximate of the amount of sms sent (eg, per user per month, etc.)

We anticipate around 1,200/month (estimate) users.