36C10A18R0043-A00003000.docx
DOCX document 32 KB Posted
- Solicitation number
- 36C10A18R0043
About this file
36C10A18R0043 A00003 36C10A18R0043 A00003.docx
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 36C10A18C0067-000.docx | DOCX document | |
| 36C10A18R0043-A00004000.docx | DOCX document | |
| 36C10A18R0043-A00002000.docx | DOCX document | |
| 36C10A18R0043-A00002002.docx | DOCX document | |
| 36C10A18R0043-A00002001.docx | DOCX document | |
| 36C10A18R0043-A00001000.docx | DOCX document | |
| 36C10A18R0043-A00001001.docx | DOCX document | |
| 36C10A18R0043-A00001002.docx | DOCX document | |
| 36C10A18R0043-003.docx | DOCX document | |
| 36C10A18R0043-002.docx | DOCX document | |
| 36C10A18R0043-001.docx | DOCX document | |
| 36C10A18R0043-004.xlsx | XLSX spreadsheet | |
| 36C10A18R0043-000.docx | DOCX document |
Show all 13
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
Solicitation 36C10A18R0043 Amendment A00003
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 ITE
M 10A.
15C. DATE
SIGNED
B. THE ABOVE NUMBERED 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 r eference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER
BY
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) TAC-Austin A00003 01-04-2018 Department of Veterans Affairs Office of Acquisition Operations Technology Acquisition Center - Austin 1701 Directors Blvd, Suite 600 Austin TX 78744 Y Department of Veterans Affairs Office of Acquisition Operations Technology Acquisition Center - Austin 1701 Directors Blvd, Suite 600 Austin TX 78744 To all Offerors/Bidders
36C10A18R0043 12-11-2017
X X X The purpose of this amendment is to provide answers to questions recieved.
See continuation pages.
Kari L. Cozzens 1/4/2018
Solicitation 36C10A18R0043 Amendment A00003
CONTINUATION PAGES
The following are questions and the Government responses:
1. Question: PWS Section 6.6 states that "As is Source code and technical documentation for existing apps to be enhanced under this TO" will be provided as a part of GFP.
Clarification:
Government Furnished Information specifically related to “as is source code and technical documentation for existing apps” does not apply since no existing apps will be enhanced under this contract.
1. Question: Can VA please provide information about the technology platform on which the mobile app and web app are developed? For example was it native iOS, native Android, Apache Cordova or some other Hybrid platform for the mobile app?
Answer:
VA’s Mobile Application Environment (MAE) is where the app shall be developed, see section 5.1.3.1 of the Performance Work Statement. The offeror shall provide a detailed description of the SUD digital mobile application development approach, including the technology platform on which the mobile app and web app will be developed.
1. Question: Was the source code ever released to production and/or to app store? If it was released to production/ app store, did it achieve Section 508 compliance? If it was not released to production, can the source code be built into a working Mobile and web application with the existing build script?
Answer:
No prior VA owned application or source code was released into production or to an app store. Further, no section 508 compliance was achieved, and there is no existing build script available for VA to provide.
1. Question: What percentage of functional requirements are met by the existing source code base?
Answer:
There is no existing source code base.
1. Question: Does the existing digital app source include integrations for VA systems including VistA/EHR, CPRS, CDW, and VAMF?
Answer:
There is no existing digital app source.
File details come from the government source that posted it.