Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF MARCH 07, 2019 FBO #6313
SOURCES SOUGHT

L -- Sources Sought Notification Mass Notifciation System Wilmington VAMC

Notice Date
3/5/2019
 
Notice Type
Synopsis
 
NAICS
561421 — Telephone Answering Services
 
Contracting Office
Department of Veterans Affairs;Network Contracting Office 4;Lebanon VA Medical Center;1700 South Lincoln Avenue;Lebanon, PA 17042
 
ZIP Code
17042
 
Solicitation Number
36C24419Q0402
 
Response Due
3/8/2019
 
Archive Date
4/7/2019
 
Point of Contact
daniel.johnson44@va.gov
 
Small Business Set-Aside
N/A
 
Description
Purpose and Objectives: The intent of this Sources Sought Notice is to identify potential offerors capable of providing Mass Notification System. These are for the Wilmington VA Medical Center in Wilmington, DE 19805. Responses to this Sources Sought Notice should demonstrate the firm's ability, capability, and responsibility to provide the principal components of supplies listed in the attached document. Responses should include the following information: Verify that the business is under 5614219 of the North American Industry Classification System (NAICS), V1erification of Size Standard under the NAICS, Business name, address, Point-of-Contact, if in possession of a Federal Supply Schedule contract, and if the business has verification as a Service Disabled Veteran Owned Small Business or Veteran Owned Small Business. All information is to be submitted via e-mail at Daniel.Johnson44@va.gov. Information provided will not be returned. All responses shall be in the English Language. Responses are due by 12:00 P.M. (EST) on Friday, March 08, 2019. No submissions will be accepted after this date and time. Questions can be submitted electronically to Daniel.Johnson44@va.gov. This is a Sources Sought Notice and submissions will be used for informational and planning purposes only. This notice does not constitute a formal Request for Quote (RFQ), nor is the government obligated to issue an RFQ. In addition, the Government does not intend to pay for any information provided under this notice. The Government is not obligated to notify respondents of the results of this survey. STATEMENT OF WORK Wilmington VA Medical Center Title of Project: Emergency Mass Notification System Scope of Work: The vendor shall provide all resources necessary to accomplish the deliverables described in this Statement of Work (SOW), except as may otherwise be specified and deliver to the desired location within the timeframe specified. Type of Contract: Firm Fixed Price Period of Performance: Delivery Date within 30 days of Date of Award unless otherwise coordinated with the Point of Contact (POC). Base Year and Four (4) Option Years: Base: 04/01/2019 03/31/2020 Option Year One (1): 04/01/2020 03/31/2021 Option Year Two (2): 04/01/2021 03/31/2022 Option Year Three (3): 04/01/2022 03/31/2023 Option Year Four (4): 04/01/2023 03/31/2024 General Requirement: The Wilmington VA Medical Center has a need for a Mass Notification System outside of the Wilmington VA Network with the following requirements. Delivery: I. ARCHITECTURE 1. Solution must only be delivered as a Software as a Service (SaaS) platform with all maintenance and upgrades being provided by the vendor during the term of the subscription. Please specify how many years the solution has been offered as a SaaS product. 2. Solution must consist of a multi-tier security infrastructure. 3. Solution must be FedRAMP & SOC3 compliant. 4. SaaS offering must be completely redundant at all levels with no single point of failure. 5. Solution must not require any hardware or software special permissions to be installed or managed. No add-ons should be required to operate the system. II. AVAILABILITY 1. Solution must meet a 99.99% system uptime. 2. Vendor must provide a Service Level Agreement that stipulates a minimum number of notifications per hour for voice-based and text-based messages. 3. Solution must consist of geographically dispersed, top tier data centers that reside in separate FEMA regions. 4. Solution must utilize datacenter locations that have undergone SOC 2 audit or higher. Solution provider must provide a publicly available SOC 3 report. 5. The proposed solution has been granted access to the Telecommunications Service Priority (TSP - http://www.dhs.gov/telecommunications-service-priority-tsp) which allows organizations to receive priority treatment for vital voice and data circuits or other telecommunications services. Please provide Level/Category and proof of certification. 6. The proposed solution is Department of Homeland Security (DHS) Safety Act certified (https://www.safetyact.gov/pages/homepages/Home.do) as a Qualified Anti-Terrorism Technology (QATT) and provide proof of certification. III. DATA MANAGEMENT CAPABILITIES 1. Solution must not require vendor intervention or support to manage message recipient or group information in any way, at any time. 2. Solution must support the ability for administrators to manually add, edit, and delete message recipients from the system. 3. Solution must support automatically adding and removing message recipients from static and dynamic groups. 4. Solution must support the ability to establish a Profile Management Portal where contacts may be invited/opt-in for notifications and manage or augment personal contact data. a. Solution must support the ability to expose the Profile Management Portal to internal personnel (invitation only) or to external stakeholders (opt-in). b. Solution must support the ability for administrators to customize the information presented to the end user through the portal, including but not limited to contact fields, custom fields, subscriptions, and delivery methods (contact information). c. Administrators have the ability to set any of the data elements in the portal to Exposed, Editable, and/or Mandatory d. Profile Management Portal must support SAML 2.0 compatible Single Sign-On e. Portal must support any language via Google Translate. f. Portal must allow for contacts to send a test notification 5. All contacts must be maintained and displayed in single directory that supports quick sorting. a. Contact directory must support advanced search capabilities including multiple field value conditions using all contact information fields. For example, Contact Type equals Employee and City does not equal Minneapolis. b. Solution must allow for an unlimited number of dynamic groups that are built from an advanced search. c. Solution must allow for a dynamic group to be built on the fly during a notification. d. Solution must support a hierarchy of unlimited groups and sub-groups. Groups must be maintained in a single directory. 6. Solution must graphically display the number of uploaded contacts by record type for informative reference and data management. 7. Solution must allow for administrators to recover contacts that have been deleted within the last 30 days. IV. MESSAGE DEPLOYMENT 1. Solution must provide a configurable and interactive dashboard that displays an overview of contacts, notifications and incidents. This dashboard must have the ability to launch a message quickly as a new message or be directed to system templates. 2. Solution must support the creation of a new message or template from a single web page to ensure efficiency. 3. Solution must be capable of tracking message deployment and confirmation in real time for all delivery methods including phone, SMS, and email. 4. Solution must enable message recipients to acknowledge receipt of messages and will continue trying to reach the recipient until receipt is received. 5. Solution must be able to send a follow up message that targets recipients that confirmed, did not confirm, or responded with a specific response from a previous message. This must be based on real-time confirmation status. 6. Solution must be able to stop a message in progress. 7. Solution must be able to disable message confirmation when desired for individual broadcasts. 8. Solution must support the ability to require a pin code/passcode prior to delivering a voice message. 9. Solution must be able to support live voice recordings via web application, telephone, file upload, and mobile application recorder as part of the single page message construction. 10. Solution must support text to speech in multiple languages. 11. Solution must allow a message initiator to preview the Text to Speech before sending the Message 12. Solution must be able to store message content for future use with a new notification. The templates must be maintained in a single message library that is searchable within the user interface as part of the single page message construction. a. Solution must allow administrator to categorize message templates for quick sorting and enhanced search capabilities within the user interface. 13. Solution must be able to store notification templates which include any/all of the required elements (message content, target audience, and deployment options) to send the notification for immediate or later deployment. The templates must be maintained in a single message library. a. Solution must support the ability to edit/update notification templates prior to launch, if desired. 14. Solution must allow administrators to establish default delivery settings which can be edited on-the-fly for individual notifications. a. Solution must be able to configure time intervals between message attempts between devices as well as between message cycles. b. Solution must support a default customizable Caller ID used for telephone messages as well as a custom email sender address. c. Solution must provide the ability for a custom reply to email address d. Solution must support delivery throttling settings. e. Solution must be able to deliver a voice mail if a contact is not reached. f. Solution administrator must be able to edit delivery methods when creating a message. 15. Solution must support the ability to include file attachments. 16. Solution must be capable of delivering an invitation to join a conference call that does not require the recipient to hang up and dial a separate number to join. a. Message sender must be able to determine which conference bridge is used. b. Product must include conference bridge numbers that are usable without activation of a notification c. Solution must allow clients to add their own existing conference bridges to the system, and allow the system to directly connect them 17. Solution must be able to support at least six (6) Phones, five (5) SMS numbers, five (5) Email addresses, three (3) Text Telephone (TTY), three (3) Faxes, and other pagers and plain-text devices per single profile. V. GIS 1. Solution must be able to target geographically located contacts as part of the single page notification process used for all other notifications. 2. Solution must support the ability to import ESRI Shape and KML files. This functionality must be directly accessible to a client administrator without vendor intervention. 3. Solution must support all notification types as part of geographic notification. 4. Geographic Targeting a. Solution must support the ability to search for a geographic location using a contact name, address, street segments, zip code, intersection, landmark, and Latitude/Longitude. b. Solution must support the ability to target a region defined by a combination of a contact location, an address point or a landmark, and a radius around that address. c. Created polygons must include a pin drop of the targeted point of interest. d. If the solution is not able to find an address, it must present a list of alternative addresses for the user to choose from. The system shall be activated from the Wilmington VA Medical Center and cover the following locations: Wilmington VA Medical Center, 1601 Kirkwood Highway, Wilmington, DE 19805. Wilmington Vet Center, 2710 Centerville, Rd, Suite 103, Wilmington, DE 19808 Kent County CBOC, 1198 S. Governors Ave, Suite 201, Dover, DE 19901 Sussex County CBOC, 21748 Roth Ave., Georgetown, DE 19947 Sussex County Vet Center, 20653 DuPont Blvd., Suite 1, Georgetown, DE 19947 Cape May County CBOC, 1 Monro Ave., Cape May, NJ 08204 Atlantic County CBOC, 1909 New Road, Northfield, NJ 08225 Cumberland County, CBOC, 79 W. Landis Ave., Vineland, NJ 08360 Southern New Jersey Vet Center, 2900 Fire Road, Suite 101, Egg Harbor Township, NJ 08234 e. The system must include the ability to select a geographic area using polygons/drawing tools. f. Message initiator must be able to exclude an address or contact from the notification 5. Drawing Tools a. Solution must include the ability to resize the shapes after initial drawing or placement. b. Solution must include the ability to modify the shapes after initial drawing or placement. c. Solution must include the ability to rotate the shapes after initial drawing or placement. d. Solution must include the ability to drag and drop the shapes to a different location on the map. e. Solution must include the ability to create both inclusion and exclusion polygons 6. Solution must display the number of recipients included within a selected region. 7. Shape Library a. Solution must allow saved shapes to automatically select contacts when recalled, no additional drawing is required. b. Solution must include the ability to save polygons in a library for later use. c. Solution must support the ability to upload existing GIS shapefiles from other systems for later use d. Shapes in the library must be fully manageable without vendor assistance. 8. Solution must allow for an agency to create a polygon for an event with a set expiration time. When a contact enters that zone with their mobile application they shall receive the notification. VI. REPORTING 1. Solution must provide a configurable and interactive dashboard that displays an overview of contacts, notifications and incidents. This dashboard must provide links to common features and recent notifications. 2. Solution must provide a real-time graphical dashboard for with a summary of each broadcast. Results that update after all notifications are sent will not be acceptable. Results must be presented in real-time. 3. Broadcast results reports must comprehensively contain the following information in a single screen: a. Date and time of the message. b. Name of the person who initiated the message. c. Message content including title. d. Settings used to deliver the broadcast including delivery methods, broadcast duration, language, throttling rules, etc. e. Graphical summarized statistics including confirmation status and confirmation by delivery paths. f. Option to view detailed calling information per member including call-result of each attempt. g. Solution must be able to sort results based on contact name, confirmation, or response. 4. Solution must organize previously sent and active broadcast in a single directory. a. Solution must allow administrators to search the broadcasts history b. Solutions must allow administrators to sort broadcasts based on sent date or title. 5. Solution must have the ability to produce custom reports using all application data. a. This includes recipient information, distribution group information, call summary, message information and all other fields available in the database. b. The report should allow the user to choose the fields for the report. c. Exporting into an Excel or.csv file in order to customize the report is NOT acceptable. You must be able to customize within the web interface. d. Solution must support a customized report library where users can save an unlimited number of reports. e. Solution must have the ability to export report data in CSV or PDF format. 6. Solution must store at least eighteen (18) months of historical message data. 7. Solution must have the capability to produce an aggregated broadcast report for regulatory purposes. 8. Solution must provide an API for custom reporting VII. CAPACITY 1. Solution telephony must use a combination of dedicated PSTN telephony and on-demand VOIP for enhanced scalability. All PSTN lines must be owned by the vendor to ensure control and capacity. 2. Solution vendor must provide a delivery SLA stipulating a minimum of 300,000 voice-based and 600,000 text-based messages per hour. 3. Solution must allow an administrator to adjust and align message delivery to the capacity of the target phone networks to prevent system wide disruption during a large notification. a. Preferences must support the ability to define maximum number of simultaneous calls for multiple telephone networks within the same broadcast (i.e. 50 calls per minute to 555-123-xxxx and 100 calls per minute to 555-999-xxxx) b. Preferences are easily accessible from within the system s web user interface and require no vendor intervention for quick adjustments. 4. If vendor is proposing an auto call throttling capability, at a minimum, vendor must provide a real-time demonstration of the technology accompanied by reports that prove how the system automatically adjusts calls during network congestion, the success rates, retries to unsuccessful calls, network capacity reports, and final call completion success rates. 5. Solution vendor must be capable of monitoring delivery performance and automatically increase system capacity on demand to avoid long broadcast delays. a. Clients must experience no downtime impact during capacity enhancements. 6. Solution vendor must be capable of simulating system performance tests for hundred thousands of calls. a. Performance tests must support real life simulations including, but not limited to, percentage of confirmed calls in the first attempt, and the ability to customize broadcast setting and delivery contact paths. VIII. SUPPORT SERVICES 1. Implementation a. Prospective vendors must be able to fully implement the proposed solution within 30 days. b. Prospective vendors must provide a dedicated implementation contact and a dedicated account manager. 2. Technical Support a. Prospective vendors must provide employee staffed technical support 24/7/365. b. Vendor s 24/7/365 support must be three tiered: General Technical Support, Tier 2 Support, and NOC level engineering support. This support must be staffed 24/7/365 and not consist of employees on-call or make use of 3rd party vendors. c. Prospective vendors must provide their technical support service level agreement for problem resolution. Please include incident categories and time frames for resolution. d. Support must be located within at least 2 regions in case one location is in an area affected by a large-scale disaster. An employee living remote will NOT be accepted. Please provide the amount of dedicated Customer Service staff in each location. 3. Training a. Prospective vendors must be able to provide online training accessible 24/7 that requires NO human/vendor intervention. Please provide costs for this training option. b. On-line training must be interactive and be available 24/7. Scheduled webinars will NOT meet this requirement. c. Prospective vendors must be able to provide onsite training. Please provide costs for this training option(s). d. Prospective vendors must provide an on-demand video training library. e. Prospective vendors must provide a Help file that is accessible within the User Interface. f. The User Interface must include Help links throughout the user interface that links for instructions on that specific page, so no searching is required to find the necessary Help topic. Point of Contact: COR: Marshall Murdaugh Phone: (302) 633-5518 Email: marshall.murdaugh@va.gov NOTE: THIS NOTICE WAS NOT POSTED TO FEDBIZOPPS ON THE DATE INDICATED IN THE NOTICE ITSELF (05-MAR-2019); HOWEVER, IT DID APPEAR IN THE FEDBIZOPPS FTP FEED ON THIS DATE. PLEASE CONTACT 877-472-3779 or fbo.support@gsa.gov REGARDING THIS ISSUE.
 
Web Link
Link To Document
(https://www.fbo.gov/spg/VA/PiVAMC646/PiVAMC646/36C24419Q0402/listing.html)
 
Place of Performance
Address: Department of Veterans Affairs;Wilmington VA Medical Center;Main Facility and CBOCs;1601 Kirkwood Highway;Wilmington, DE
Zip Code: 19805
Country: U.S.A.
 
Record
SN05239846-F 20190307/190305230021 (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 |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.