SOURCES SOUGHT
D -- EMERGENCY MESSAGING APPLICATION (EMA) - Requirements Matrix
- Notice Date
- 12/11/2013
- Notice Type
- Sources Sought
- NAICS
- 519190
— All Other Information Services
- Contracting Office
- United States Senate, Office of the Sergeant at Arms, Finance Division, United States Senate, Washington, District of Columbia, 20510-7207, United States
- ZIP Code
- 20510-7207
- Solicitation Number
- 2014-S-027
- Archive Date
- 1/11/2014
- Point of Contact
- Kathleen M. Haddow,
- E-Mail Address
-
Acquisitions2012@saa.senate.gov
(Acquisitions2012@saa.senate.gov)
- Small Business Set-Aside
- N/A
- Description
- Requirements Matrix DESC: MARKET SURVEY AND BIDDERS LIST DEVELOPMENT - SOURCES SOUGHT REQUEST FOR DEVELOPMENT OF AN EMERGENCY MESSAGING APPLICATION (EMA). The purpose of this sources sought synopsis is to gain knowledge of potential qualified industry sources or service providers of emergency messaging applications. The Office of the Senate Sergeant at Arms (SAA) is looking for a cross platform application that provides the ability to centrally manage and then distribute lists of individuals to Blackberry 10, IOS, Android, and Windows Phone "smartphones" allowing the smartphone users to then send messages to these lists. Administrators shall also be able to send messages to these lists from a web-based application. The SAA is currently conducting market research to determine the existence of viable organizations capable of providing this type of application and follow on support. This is not a request for proposal and in no way obligates the Senate in an award of a contract. This sources sought synopsis contains the most currently available information. This information is subject to change at any time. Requirements are stated in terms of minimum capabilities and characteristics required by the Senate. REQUIREMENTS: The key functional areas under consideration include, but are not limited to, the following: 1. An EMA administrator shall be able to create and uniquely name any number of lists that include any number of individuals that have been selected to receive messages. 2. The EMA administrator shall be able to deliver "push" these lists over-the-air to various individuals that have the EMA installed on their smartphone. 3. Individuals with the EMA on their smartphone shall be able to send a message to any of the lists that have been pushed to them. 4. At a minimum, e-mail addresses shall be associated with each member on a list so that when a message is initiated from the EMA, they are delivered to the recipients associate desktop and mobile e-mail inboxes. 5. Messages initiated from the EMA shall also be delivered to an associated EMA application residing on a recipient's smartphone, if installed. Messages delivered in this format should not rely on the Senate's e-mail infrastructure for transport, acknowledgments, or replies. 6. Messages should not be limited in length (number of characters). 7. Recipients shall be able to open the application to review messages. 8. Recipients shall be able to configure the smartphone application so that when messages are received, the application triggers a "new message" notification alert. 9. The sender of messages using EMA shall have the option to allow recipients to see who the message was sent to (similar to placing names in the "To:" field) or hide this information (similar to placing names in the "Bcc:" field). Message recipients shall have the option to REPLY ALL if the addresses are visible or just to the sender if the recipients were hidden (e.g. Bcc: field). The ability to reply to messages should be found both in the e-mail inbox and from within the EMA. 10. Individuals with EMA shall be able to view the members of each list present on his/her device but shall not be able to add or remove members that were pushed out by the EMA Administrator. 11. Individuals with EMA shall not be able to delete any lists pushed out by the EMA Administrator. 12. The EMA Administrator shall be able to send updates to the lists ad-hoc or as a regularly scheduled event. 13. Individuals with EMA shall be able to create their own lists directly from their device and add members to it from their personal contacts. These individuals should also be able to share and update these lists with any other EMA user. 14. The EMA Administrator shall be able to create an overriding custom alert/notification that can be assigned and pushed to an EMA user or list. The overriding custom alert may be triggered by sender name, words, or phrases in either the subject line or message body. When activated, the custom alert will trigger a unique device tone and vibration pattern. The tone and vibration shall override any notifications set by the user. The tone and vibration shall not stop until the message is acknowledged by the user. End users shall not be able to delete or disable EMA Administrator's overriding custom alerts. However, the EMA Administrator may send a command to delete any custom notifications pushed out by the Administrator. 15. Individuals with EMA shall be able to create their own custom alerts based on sender name, words, or phrases in the subject either line or message body. The EMA custom alert feature shall allow the end user to specify the type of notification to activate when it receives the message (e.g. specific ring tone to play, vibrate settings, etc...) 16. EMA users shall have the ability to request and view Delivery and Read acknowledgements for messages they initiate. 17. The EMA Administrator shall be able to create template messages and push those templates to select EMA users. Users of EMA shall be able to select a template message and update/edit it before use. EMA users shall also be able to create their own message templates. 18. The EMA shall directly integrate with Dialogic Communicator, Roam Secure, and ALERTUS mass notification systems. Example, when an e-mail message is initiated from Dialogic or Roam Secure to a specific list, the EMA backend shall have the ability to simultaneously deliver this message to the EMA application of those on the associated EMA lists. 19. The EMA Administrator shall be able to initiate messages from a Web-based application to any or all of the EMA lists. The Administrator shall be able to choose to send the message via 1) e-mail, 2) directly to the EMA application, or 3) via both options. Message templates shall be available to the EMA Administrator to utilize when sending out messages. Delivery and read confirmations should also be available for the Administrator to review. 20. The solution shall allow for all contact information to be hosted within the Legislative Branch environment. No contact information will be stored at the EMA vendor site. 21. The EMA client application shall be available for Blackberry 10, IOS, Android and Windows phones. 22. The EMA platform must offer scalable performance. Addressed recipients may range in numbers from one to several thousand for a single message. In all cases, the EMA will process and deliver each message to the appropriate network service in one minute or less. INSTRUCTIONS In responding to this SSN: 1) Complete the requirement matrix, TABLE 1. (See SSN Attachment Requirement Matrix, Table 1) 2) State your qualifications to perform each requirement, 1 through 22, your solution meets. Your response to each requirement you meet must include paragraph numbering identifiable to requirements; 3) Provide past performance experience and information for a minimum of three (3) contracts, less than two (2) years old that involve use of capabilities and products relevant to those necessary for the Senate's requirements, include the contract number, customer name and address, and brief synopsis of work performed relevant to requirements; and 4) Organizational information including your Dun and Bradstreet number and point of contact with telephone, fax, and e-mail address. This Sources Sought Notice (SSN) is not a request for proposal and in no way obligates the Senate in an award of a contract. This sources sought synopsis contains the currently available information. This information is subject to change at any time. The information contained in this notice will be the only information provided by the Senate during the Sources Sought process. All qualified sources should respond to this Sources Sought by submitting an information package in accordance with the instructions provided. Vendors responding to this sources sought notice and deemed qualified by the SAA may be requested to submit a proposal in response to a solicitation. Only firms deemed qualified will be permitted to submit proposals. If suitable responses are received from qualified sources, the SAA anticipates release of a solicitation in the second quarter of Fiscal Year 2014. Neither the SAA nor the Senate will be responsible for any costs for the preparation of responses to this request. Responses to this Sources Sought request are due to the SAA Procurement point of contact no later than January 11, 2013, at Noon EDT and shall be submitted electronically via email only to the attention of Kathleen M. Haddow to acquisitions2012@saa.senate.gov. The subject line of the email message shall be SSN 2014-D-027 EMERGENCY MESSAGING APPLICATION (EMA). No other method of transmittal will be accepted. The response shall not exceed twenty-five (25) pages. Unnecessarily elaborate submissions are discouraged. Pages over the page limitation may be discarded. Access by the SAA to information in any files attached to the response is the responsibility of the submitting party. Neither the SAA nor the Senate is responsible for any failure to access vendor's information. THIS IS NOT A REQUEST FOR PROPOSAL. THIS NOTICE CONSTITUTES THE ENTIRE SOURCES SOUGHT NOTICE AND IS THE ONLY INFORMATION THAT WILL BE PROVIDED BY THE SAA OR SENATE. REQUESTS FOR ADDITIONAL INFORMATION WILL NOT BE HONORED.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/Senate/SAA/SAAFD/2014-S-027/listing.html)
- Place of Performance
- Address: United States Senate, Washington, District of Columbia, United States
- Record
- SN03249455-W 20131213/131211234947-b17c7bc9e8abc25a14562c88cc9628b6 (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 |