Vendor Questions and Answers.docx
DOCX document 17 KB Posted
- Attached to
- 6515--Real Time Location System (RTLS) Asset Tracking Federal contract opportunity
- Solicitation number
- 36C26224Q1780
About this file
This document consists of Vendor Questions and Answers related to a federal contract opportunity for a Real Time Location System (RTLS) Asset Tracking System for the VA Greater Los Angeles Healthcare System (VAGLAHS).
The key details are:
- This is a Service-Disabled Veteran-Owned Small Business set-aside with a NAICS code of 541519 and a size standard of 150 employees.
- The solicitation is for a Brand Name or Equal RTLS Asset Tracking System, with a 12-month period of performance and a 180-day delivery requirement.
- The government confirmed there is no current VISN-level RTLS infrastructure in place, and stated the implemented system would need to be compatible with transitioning to a planned Juniper/MIST WiFi system in the future.
- The government indicated they are open to adjusting the CLIN quantities/pricing to provide a more efficient and economical solution, as well as modifying the payment terms to include milestone payments.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 36C26224Q1780 A0001.docx | DOCX document | |
| Solicitation A0001 Amended.pdf | ||
| 36C26224Q1780_2.docx | DOCX document | |
| S02 - 36C26224Q1780.pdf | ||
| 36C26224Q1780.docx | DOCX document | |
| 36C26224Q1780_1.docx | DOCX document |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
1. Can the government please confirm that VISN level RTLS infrastructure/Servers (upon which this project is dependent) are in place and can be used for GLAHCS RTLS implementation, including: Infor LBI, CenTrak Pulse, SSOi, Active Directory and VistA (AMES/MERS) interface.
ANSWER: There is no current VISN level RTLS infrastructure/Servers in place nor planned, as Long Beach’s implementation is standalone/local.
2. Re: page 9, User Interface & Configuration section. The government states, “The Contractor shall provide VA ATO-approved system interfaces, to include AEMS/MERS, Maximo, PIV/SSOI, and Vocera, as well as EHRM.” Are all of these interfaces required?
ANSWER: No, GLA uses AEMS/MERS(VISTA) and would only require compatibility with this, PIV/SSOi is also used.
3. e When is VA West LA scheduled to migrate from Cisco to Juniper/MIST WiFi? If Calendar Q4 2024, or Q1 2025, should we integrate with Juniper MIST instead of Cisco?
ANSWER: GLA is not currently expecting the Juniper/MIST transition in Q4 ‘24 or Q1 ‘25 but it is planned and funded, please connect to CISCO WiFi and ensure your solutions is compatible with Juniper. Any implemented systems would need to be able to support nextgen WiFi or have compatibility to transition to Juniper.
4. Can we use the exact CLINs provided in the RFP, but adjust the Quantities/CLIN to provide a more efficient and economical solution that meets the needs and requirements of RFP?
ANSWER: Quantities/CLIN can be adjusted to provide more efficient and economical solutions as long as it can provide a functional RTLS.
5. Page 6 says a 12-month PoP but page 19 says 180 days for delivery. 180 days does not seem feasible. Can the government confirm the PoP and delivery date are 12 months?
ANSWER: Yes, PoP can be adjusted to accommodate a 12 month implementation time.
6. Payment on full delivery is in conflict with preexisting terms with our subcontractors. Will the government consider modifying payment terms to include milestone payments for each of the individual services as listed in CLIN 2001 (to allow for partial/milestone billing).
ANSWER: Payment terms can be adjusted to partial payments.
END OF ANSWERS
File details come from the government source that posted it. Updated .