Loren Data's SAM Daily™

FBO DAILY ISSUE OF JULY 22, 2011 FBO #3527
DOCUMENT

D -- PTSD Treatment Monitoring Tool - Attachment

Notice Date

7/20/2011
 

Notice Type

Attachment
 

NAICS

541512 — Computer Systems Design Services
 

Contracting Office

Department of Veterans Affairs;VA Sierra Pacific Network (VISN 21);VA Palo Alto Health Care System (90/CCA);3801 Miranda Ave;Palo Alto CA 94304-1207
 

ZIP Code

94304-1207
 

Solicitation Number

VA26111RP0595
 

Response Due

7/25/2011
 

Archive Date

9/23/2011
 

Point of Contact

Helena Zhao
 

E-Mail Address

3-5000x65352<br
 

Small Business Set-Aside

Total Small Business
 

Description

The purpose of this amendment is to provide answer to the questions asked by vendors. All other terms and conditions remain the same. 1. Is the VA open to a COTS solution to augment the current COMMEND system? The scope of the project calls for modifying the current software and unlikely would need additional COTS. Any COTS solution would need to be specifically verified 2. For Development work that does not involve handling VA data, will the agency be open to off-site work (based at the vendor's premises in the continental US). As stated in the SOW "Place of performance for the work described within shall be at the Palo Alto VA Health Care System, including the Menlo Park VA Mental health Clinic and the Dissemination and Clinical Training division of the National Center for Posttraumatic Stress Disorder". Given security issues, the work needs to take place on site. This is due to as the work as listed in the SOW calls for either modifying the current software to work directly with VA clinical data bases (e.g., program administrator view, extraction of additional data, program note data extraction). 3. Will the agency be open to allowing additional hardware as part of the COTS solution? N0, the project needs to run on current VA hardware. a. Preference for operating systems. The project needs to run in conjunction with the VA specific software such as Veterans Health Information System and Technology Architecture (VistA), Primavera, Remedy, etc. b. Preference for databases that the COTS will utilize - MS SQL, Oracle, etc. SQLServer database 4. Does the agency currently work with an incumbent Business partner? Was previously developed with a business partner. The current contact does not have an assigned business partner. 5. Does the agency have a proposed organization for the project, from the agency's side? Or does the agency wish the Vendor/Contractor to provide this? A preliminary project plan is outlined in the SOW that we would want to follow. 6. Does the agency need any NON production environment at all? Yes. Modifications need to run in a test environment before being deployed. 7. Has a detailed business analysis already been done for the environment, Dashboards and reporting requirements? If so, can VA share the documents at a later stage? One has not been formally developed. 8. If a data warehouse (EDW) is not available, has any kind of data modeling or business analysis has been done creating a database for reporting and dash boarding purpose? The VA does have regional data warehouses which COMMEND currently works with. 9. How big is the user base for this application? The projected current user base in 100-200 providers and administrators at the VA Palo Alto. Future wide spread use by the VA is possible but uncertain at this time. 10. How big is the current database ( size in GB and number of major tables)- Exact size unknown but the RDW is huge-measured in terabytes. 11. How many major user access levels are envisioned in this environment? ( Ex: Refresh Users, Read Only Users,Power Users etc ¦). Of the 100-200 initial users, 10 would be power users. 12. Are the dashboards intended to be public facing or should the access to these dashboards be restricted for different internal users only? Access is restricted to only specified Users within the VA environment. 13. Is the agency expecting a heavy ad-hoc analysis usage? Yes, that is one of the greater potential strengths of this system 14. Is there any standard application server in the agency environment ( Websphere/Web Logic etc)? Will need to verified but do not think so. 15. Has the glossary or terms and meta data reporting templates already defined by the business? No 16. Is the Development environment will be available after Production release? Yes. 17. Does VA require ongoing continuous support after Production release / Go-live? Unknown, will be depended on the budget, budget has not committed past the current requirement. 18. Can the reporting environment be a standalone one or should it be integrated to an existing VA portal /system? Integrated with the current VA system 19. Is there any third part security tool (for example encryption/decryption) which the reporting tool need to comply with? Is there any security model requirement for VA ( like single sign on). The system needs to work within the VA encryption environment (which is not third party), COMMEND currently uses a Java background listener program to provider CPRS login's. Only those providers who have successfully logged in via CPRS are able to access COMMEND to ensure data security and privacy. 20. Is there any standard of Application Server, Portal and other infrastructure setup already in place which we need to comply with? If so can you give some more information about this? It needs to comply with the current VA infrastructure as above. 21. What should be the availability of the environment (eg: 24X7)? Yes 24/7 22. Is the VA open to the vendor providing hardware requirement specifications and the agency then procures the hardware through it's established sources, or is it mandatory for the vendor to specify. The project needs to function on current VA hardware.
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/spg/VA/VAPAHCS/VAPAHCS/VA26111RP0595/listing.html)
 

Document(s)

Attachment
 

File Name: VA-261-11-RP-0595 0002 VA-261-11-RP-0595 0002.doc (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=220798&FileName=VA-261-11-RP-0595-0002000.doc)

Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=220798&FileName=VA-261-11-RP-0595-0002000.doc

 

Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
 

Record

SN02504384-W 20110722/110721001930-5cc886d9b87208cfb6aff341bf3c53d0 (fbodaily.com)
 

Source

FedBizOpps Link to This Notice
(may not be valid after Archive Date)

---

| FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |