Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF MAY 02, 2013 FBO #4177
DOCUMENT

70 -- Wi-Fi internet access for Veteran Patients at the VA Medical Center in Milwaukee, WI. - Attachment

Notice Date

4/30/2013
 

Notice Type

Attachment
 

NAICS

541519 — Other Computer Related Services
 

Contracting Office

Great Lakes Acquisition Center (GLAC);Department of Veterans Affairs;115 S 84th Street, Suite 101;Milwaukee WI 53214-1476
 

ZIP Code

53214-1476
 

Solicitation Number

VA69D13Q0789
 

Response Due

5/3/2013
 

Archive Date

5/6/2013
 

Point of Contact

Antonio Reyes
 

Small Business Set-Aside

N/A
 

Description

Questions MX 1. What types of WAN connections are currently servicing your network (DSL, Frame Relay, MPLS etc)? Is there a requirement for fiber ports? 2. What is the current bandwidth your ISP is providing? Do you see the need for an increase in bandwidth in the next 3-5 years? 3. What is your desired throughput (LAN __ WAN and LAN __ LAN)? 4. Is there a requirement for any special Firewall capabilities? Will the MX serve as a NAT device and is there a need for port forwarding? 5. What is the maximum number of connected devices? 6. Is there a desire for layer 3 functionality? If so, are you running any routing protocols have any static routes in place? 7. What type of High Availability/redundancy features are you looking for? 8. What type of traffic is running on your VPN? Are a majority of your servers located at a central site? 9. Are you looking for a remote client VPN solution? Details? 10. Is there a need for IPSec interoperability with other existing equipment? 11. Is Content Filtering with AD integration a desirable feature? 12. Are there any additional requirements? 13. Please provide: o Topology diagrams outlining existing infrastructure o Subnetting scopes o Public IP information o Interoperability requirements for LAN MS 1. Do you currently have managed or unmanaged switches? 2. Is there a need for Layer 3 functionality? 3. What are your requirements around port density? Is there a requirement for Fiber ports? 4. Would you like PoE on your switches? Are there any wireless AP's or phones hanging off these switches? 5. Who is your current switch vendor? How large is the existing switching infrastructure (switch count)? 6. What vendor/model is your core switch today? Are you running any type of routing protocols? 7. What are your throughput requirements? 8. What type of uplink ports do you require (1G or 10G)? 9. Are you looking for any type of security features, say, 802.1x? 10. Is your network segmented using VLAN's? 11. Are you currently running spanning tree (STP) in your network? If not, are you planning on implementing spanning tree moving forward? 12. Is there a need for stackable switches? How many IDFs are currently in your campus? 13. Please provide: o Topology diagrams outlining existing infrastructure o Subnetting scopes o Interoperability requirements for LAN MR Indoor: 1. What is the client density per building? 2. What is the total number of wireless clients connecting to the AP one time? 3. What is the building material inside (sheet rock, stucco, concrete, rebar or brick)? 4. How many floors are in each building? Are the floors concrete? 5. Are there any limitations to where you can run power and Ethernet cable? 6. Is there a requirement for outdoor coverage? 7. Are there any specific high density areas? 8. What is the expected throughput for a wireless client? 9. What is the bandwidth provided by your ISP? 10. What is the total coverage area? 11. Are there any high bandwidth or business critical applications running on the wireless network? 12. Is VOIP being implemented in this deployment? 13. Please provide floor plans. Outdoor 1. Where will the AP's be placed? 2. Will there be power to bring up the AP's? 3. Where will there be Ethernet uplinks? 4. Will the Omni antenna provide coverage on 2.4 Ghz, 5 Ghz or both? 5. What is the expected throughput for wireless clients? 6. Will the wireless infrastructure provide Internet/guest access only or is there a need for private data user access (corporate)? 7. Is there a need for Video Cameras communicating with the wired LAN? 8. Is this a Pro or Enterprise Deployment? 9. Is the customer using Meraki currently? 10. What is the bandwidth of the main WAN link? 11. Are all the AP's going to be in gateway mode or is there a need to mesh the AP's? 12. What type of traffic is expected to traverse the WLAN? 13. How many wireless clients are connecting to the AP at any one time? 14. Are there any specific high density areas? ? Answers MX 1. No current, air gapped WAN connections into the hospital. No requirement for fiber ports. 2. No current ISP contracts. Bandwidth growth for VGIA can be expected to grow in next 3-5 years. 3. No desired throughput. We're looking for the market to tell us what the best solution is for this type of service. 4. Basic firewall services will be required, to minimize malware and virus infections to patient devices. The requirement is to protect the users from the most common risks of such infections. We're looking for the market to tell us what the best solution is for this type of service. 5. This will be provided in the solicitation. 6. No layered switching requirement. We're looking for the market to tell us what the best solution is for this type of service. 7. This is an important, but non-critical system. This is a turnkey service, where were expect contractor to maintain uptime of the system. Design as you see fit; it will be your system to manage. 8. Not relevant. 9. No. 10. No. 11. Yes. 12. This will be provided in the solicitation. 13. Not relevant. VGIA will be an air gapped infrastructure designed, installed, and maintained by the contractor. We're looking for the market to tell us what the best solution is for this type of service. MS 1. Not relevant. Contractor will provide all infrastructure, with the exception of existing fiber if available. 2. No layered switching requirement. We're looking for the market to tell us what the best solution is for this type of service. 3. VA has no port density requirement. Contractor will provide designs for port density requirement. No requirement for fiber ports. 4. PoE is fine. Not relevant. VGIA will be an air gapped infrastructure used only to provide wireless internet services to patients and family members. 5. Cisco. Not relevant. VGIA will be an air gapped infrastructure designed, installed, and maintained by the contractor. 6. Cisco. Not relevant. VGIA will be an air gapped infrastructure designed, installed, and maintained by the contractor. 7. No desired throughput. We're looking for the market to tell us what the best solution is for this type of service. 8. 10G is not required. 9. The requirement is to protect the users from the most common risks of malware and virus infections. Apply security features to design as you see fit. 10. Not relevant. VGIA will be an air gapped infrastructure designed, installed, and maintained by the contractor. 11. Not relevant. VGIA will be an air gapped infrastructure designed, installed, and maintained by the contractor. 12. Not required. We're looking for the market to tell us what the best solution is for this type of system design. Do not understand "IDF." 13. Not relevant. VGIA will be an air gapped infrastructure designed, installed, and maintained by the contractor. We're looking for the market to tell us what the best solution is for this type of service. MR Indoor: 1. Anticipated users/devices per area will be included in SOW. 2. Anticipated users/devices per area will be included in SOW. 3. Various. Contracts will have option to visit site prior to submitting proposal. 4. 10, 2, and 2. 5. Cable installation must meet applicable code. 6. No. 7. Anticipated users/devices per area will be included in SOW. 8. No desired throughput. We're looking for the market to tell us what the best solution is for this type of service. 9. No current ISP contract in place. Contractor shall provide ISP service. 10. Approximate square footage will be included in SOW. 11. No. 12. No. 13. Floor plans will be included in SOW. Outdoor 1. - 14. Not relevant. (No outdoor coverage is included in SOW.)
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/spg/VA/VAGLHS/VAGLHCS/VA69D13Q0789/listing.html)
 

Document(s)

Attachment
 

File Name: VA69D-13-Q-0789 VA69D-13-Q-0789_1.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=731837&FileName=VA69D-13-Q-0789-002.docx)

Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=731837&FileName=VA69D-13-Q-0789-002.docx

 

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

Record

SN03048529-W 20130502/130430234539-eb3dd3797c8efd40675bd31ee34eeef8 (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 |