UPDATE AS OF 09/16/2020: An update is being provided to inform that more than one award may be made. Proposal revisions are not being requested as a result of this update. UPDATE AS OF 09/11/2020: A response is being provided to the following question: Question: One piece of information that seems to be missing is the potential size of the list of recipients who will receive an IPAWS alert from the requested offering. Is that information available? Response: IPAWS only uses broadcast technologies (i.e. WEA and EAS) and therefore the population reached by an alert sent via IPAWS is not known or relevant to system performance. The tool will be used to send alerts for state or local authorities only in emergency circumstances when the state or local agency is not able to send an alert using their own systems. The tool will only be used in a state or local agency emergency support function, therefore the largest area that an alert will be broadcast to will not exceed the area of one state / alert. UPDATE AS OF 09/09/2020: The RFP has been amended to revise the original evaluation criteria to now include inadvertently omitted intended criteria. The proposal due date is now 09/14/2020 and the page limit is increased to 10 pages total. Offerors who have already submitted a response may submit a new offer prior to the revised due date. See below for the amended solicitation. This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued. Request for Proposal (RFP) WX06401Y2020T is for the Public Alert and Warning Messaging Tool for IPAWS 24/7 Lab as defined in the attached Statement of Objectives. This solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 2020-04. It is anticipated that a firm-fixed-price purchase order will be awarded. To assist in your acquisition planning on whether to submit a response, the Government estimates this effort not to exceed $100,000.00. The solicitation document and incorporated provisions and clauses are those in effect thru Federal Acquisition Regulations (FAR). More than one award may result from this solicitation via the issuance of a purchase order for commercial items, applies to this acquisition. The provision at FAR 52.212-2, Evaluation-commercial items, applies to this acquisition. Proposals shall not exceed 10 pages. Proposals shall address the ability to meet the technical criteria as listed below as it relates to the attached Statement of Objectives. Basis of Award: The Government will award a contract resulting from this solicitation to the responsible offeror whose offer conforming to the solicitation will be most advantageous to the Government, price and other factors considered. The functional technical factor is more important than the non-functional technical factor. All non-price evaluation criteria, when combined, are significantly more important than price. Functional Technical Factor - The following criteria shall be used to evaluate offers which are stated in descending order of importance. The Government will evaluate the offeror's submission in meeting the following: 1. User can access the alerting tool through the internet via web browser (Internet Explorer, Firefox, Chrome) 2. User can install live COG and test COG digital certificates (alerting tool supports both IPAWS live and IPAWS lab environments) 3. User alerting permissions (event codes, geocodes, etc.) are constrained through the IPAWS getCogProfile function (e.g. system does not present event code or geocode selections for which they are not authorized per getCogProfile result). 4. User can send alert, update, and cancel messages. 4.1 User can blockchannel (or “select channel”) to prevent a message from reaching WEA, EAS, and/or NWEM 4.2 User can select FIPS codes from the COG’s list of permissions (implemented by getCogProfile function) 4.3 User can select event code from the COG’s list of permissions (implemented by getCogProfile function) 5. User can view a list of messages sent based on IPAWS getMessageList function 5.1 The results are presented based on the COG digital certificate that is loaded 5.2 The full CAP xml for each message in the results can be viewed based on IPAWS getMessage function 5.3 User can “update” or “cancel” active messages displayed in the results 5.3.1 When selecting a previous message to update or cancel, the previous message content will be pre-populated and can be edited 5.3.2 Required fields necessary to update or cancel will be pre-populated (i.e. reference field, msgType field) 6. User can open a map view when creating a message 6.1 User can create polygon(s) and circle(s) on a map 6.2 User can view and edit the polygon(s) and circle(s) on a map when updating a sent message 7. User can include a URI link to an mp3 file for EAS alerting (system will provide a file hosting service to store the mp3 for retrieval by external entities). 8. User can preview the message before sending. 9. User can view status codes for sent messages (implemented by getMessageStatus function). 10. Alerting tool will support at least 10 user accounts and at least 5 concurrent users. 11. Alerting tool has 99.9% availability (8.76 hours downtime per year permitted) Each of the above 11 criteria will be rated one of the following: Outstanding, Good, Acceptable, Unacceptable. Non-Functional Technical Factor - The following criteria shall be used to evaluate offers which are stated in descending order of importance. The Government will evaluate the offeror's submission in meeting the following: 1. Usability: The alerting tool must have an intuitive user interface such that sending alerts, updates, cancels can be accomplished through a workflow versus manually entering parameters and values. Note: manually entering free-form textual alert messages (e.g. headline, instruction, description, CMAMtext) is considered part of the workflow and is acceptable and necessary. 2. Features: The alerting tool must support all IPAWS features listed in the IPAWS-OPEN Interface Design Guide including but not limited to getCogProfile, getMessageStatus, getMessageList, getMessage. These features must be present in order to support functions such as alert cancellation and update, COG permissions, and for the review of alerts previously sent using the COG ID and digital certificate loaded into the alerting tool. 3. Compatibility: In order to ensure the preservation of life and property, the alerting tool vendor must be capable of sending IPAWS alerts and be compatible with the IPAWS features and functions. Therefore, the alerting tool must make updates to support IPAWS changes (IPAWS features, IPAWS capabilities, and IPAWS bug fixes) once they are available in the FEMA production environment. 4. Mass Notification: FEMA does NOT require a subscription-based mass notification feature (e.g. send email notifications to the public, send text messages to the public, automatic dialing public phone numbers), only IPAWS capabilities. Each of the above 4 criteria will be rated one of the following: Outstanding, Good, Acceptable, Unacceptable. A rating will not be assigned to the overall factors. PRICE: Offerors shall submit a Firm Fixed Price Quote for meeting the requirements of the SOO. Tentative CLIN schedule: CLIN 0001; CLIN Description: Messaging Tool as described in Statement of objectives; Delivery: 30 days after award. Price proposals will be evaluated for price reasonableness. Offerors are to include a completed copy of the provision at FAR 52.212-3, Offeror Representations and Certifications-Commercial items, with their response unless that information is current in their System from Award Management (SAM) registration. (Not included in page count) If registered in SAM please state such in your submission and provide your DUNS number. Note: SAM registration: a prospective awardee shall be registered in the SAM database prior to award. The Clause at FAR 52.212-4, Contract Terms and Conditions-Commercial items, applies to this acquisition. (NOTE: all referenced FAR provisions may be accessed electronically at http://acquisition.gov/far.) FAR 52.212-5, Contract Terms and Conditions Required to Implement States or Executive Orders-Commercial items, applies to this acquisition and the following additional FAR clauses apply: 52.212-1, 52.216-24, 52.216-25, 52.222-21, 52.222-26, 52.222-35, 52.222-36, 52.222-37, 52,222-41, 52.223-18,52.225-13, 52-225-25 and 52.233-04. Written responses to this RFP must be received no later than 4:00 PM EST, 09/14/2020 and shall be sent electronically to
[email protected]. Technical questions must be received no later than 4:00 PM/EST on 08/27/2020 and must be emailed to
[email protected]. Amendments to this RFP will be published in the same manner as the initial synopsis/solicitation. No set-aside being utilized; this is a full and open competition.