FEDERAL EMERGENCY MANAGEMENT AGENCY USA Tender

Department Of Homeland Security (dhs) federal Emergency Management Agency (fema) office Of Response And Recovery (orr), Operations Integration Section (ois) request For Information (rfi) Crisis Management System (cms) department Of Homeland Security (dhs) federal Emergency Management Agency (fema) office Of Response And Recovery (orr), Operations Integration Section (ois) request For Information (rfi) Crisis Management System (cms) this Rfi Is Issued For Information And Planning Purposes Only And Does Not Constitute A Solicitation. All Information Received In Response To This Rfi That Is Marked As Proprietary Will Be Handled Accordingly. In Accordance With Far 15.201(e), Responses To This Notice Are Not Offers And Cannot Be Accepted By The Government To Form A Binding Contract. Responders Are Solely Responsible For All Expenses Associated With Responding To This Rfi. please Note That This Is Not A Request For Proposal, No Solicitation Exists At This Time. responses Should Include Your Company's Capability Statement. The Rfi Number 70fa3124i00000013 Shall Be In The Subject Line Of Submission. oral Communications Are Not Acceptable In Response To This Notice. However, Follow-up Discussions / Market Research May Be Performed. description: fema Is Interested In Obtaining Responses To This Request For Information (rfi) From Prospective Offerors That Will Provide An Application That Supports Fema Requirements. The Government Encourages The Responders To This Rfi And Prospective Offerors To Propose The Most Innovative And Cost-effective Methods To Achieve The Desired Objectives And Results. If The Proposed Application Meets Some, But Not All, Of Fema Requirements, Prospective Offerors Should Propose A Path To Meeting All Of Fema Requirements Including The Proposed Process, Application Implementation Schedule And Rough Cost To Achieve The Requirements. It Is Also Important That The Application Be Flexible, Adaptable, And Capable Of Being Updated Or Modified To Implement Additional Functional Capabilities To Meet The Agency’s Needs. agency Background: fema Is Part Of The U.s. Department Of Homeland Security And Is The Nation’s Preeminentemergency Management Agency. Fema’s Primary Mission Is To Reduce The Loss Of Life And Property And Protect The Nation From All Hazards, Including Natural Disasters, Acts Of Terrorism, And Other Man-made Disasters, By Leading And Supporting The Nation In A Risk-based, Comprehensive Emergency Management System Of Preparedness, Protection, Response, Recovery, And Mitigation. fema Operates Under Several Statutory Authorities Including The Robert T. Stafford Disaster Relief And Emergency Assistance Act, Pl 100-707, The Homeland Security Act Of 2002, Pl 107–296, And The Homeland Security Appropriations Act Of 2007, Pl 109-295. fema Prepares The Nation For All Hazards And Manages Federal Response And Recovery Efforts Following Any National Incident. Fema Works In Partnership With Other Organizations That Are Part Of The Nation's Emergency Management System. These Partners Include State And Local Emergency Management Agencies, 27 Federal Agencies And The American Red Cross. Fema Established The National Response Framework To Provide The Guiding Principles For Enabling All Response Partners To Prepare For And Provide A Unified National Response To Disasters And Emergencies – From The Smallest Incident To The Largest Catastrophe. general Requirements fema Requires Vendor-supported Cloud-based Commercial-off-the-shelf (cots) System As A Service (saas) Product That Is Compatible With The Existing Crisis Management System. Fema Requires This System To Be Hosted In A Fedramp High Certified Cloud-based Environment At The Time Of Award. the System Shall Have Mass Alerting And Workflow Notification Capabilities Via Multiple Modalities Including Email, Sms, Voice, And Mobile Application. Alerting Must Be Capable Of Being Fully Automated Based On Conditions And Workflows Within The System. the System Shall Provide For A Library Or Collection Of Readily Available Off-the-shelf Process Workflows And Features That Can Be Used Immediately, And/or Further Configured To Support Government Requirements. the System Must Support And Facilitate The Interoperability Among Other Incident Event Crisis Management Systems. platform Requirements fema Will Be Responsible For Providing Networking And Network Security Support Required To Facilitate Integrations, Data Migration, And End-user Access To Contractor Saas Software Components From The Fema Network. the System Must Provide Bi-directional Data Sharing Capabilities With Other Intra- And Inter-agency Offices. the System Must Provide Secure Chat, File Sharing, And Workflow Connectivity Across Agency Domains In A Fedramp High-hosted Platform, As Authorized To Facilitate The Flow Of Information. the System Must Be Available In Secure Single-tenant Structure, Not Multi-tenant, To Provide For Increased Security, Dependability, And Custom Configuration Potential. security: A Single Agency And A Dedicated Federal Server Set Contained On Secure Hardware Being Used By A Credential Group Of Government Employees And Contractors Eliminates The Risk Of Outside Breach. dependability: With An Entire Environment Dedicated To One Agency, Resources Are Abundant And Available Anytime. custom Configuration: Control Over The Entire Environment Allows For Configuration Customization And Added Functionality. the Platform Shall Utilize Open Application Programming Interfaces (api) To Provide The Maximum Flexibility And Adaptability To Integrate With Most Third-party Applications/systems. the System Administrators Must Have The Ability To Configure Custom Workflows Via Low-/no-code Tools Provided By The Vendor. system Administrators Must Have The Ability To Configure Custom Dashboards Tied To Workflows Using Via Low-/no-code Tools Provided By The Vendor. the System Must Be Able To Create Administrator-level Configurable Data Input Forms That Feed Into Existing Workflows And Processes Within The System. Data Input Forms Must Have Offline Capabilities Due To The Remote, Hard To Connect Disaster Locations. the System Must Comply With Federal Law, Executive Orders, And Other Policy. the System Must Be Capable Of Automated Scaling For Peak Users’ Access, Security Patches, Hardware Upgrades, And Seamless Modernization. the Offeror Shall Ensure Multi-factor Authentication (mfa), With Fema Users Accessing Via Personal Identification Verification (piv) And Username And Password For All Other Users Through Okta. fema May Request No-cost Technical Demonstrations Of The System. Please Indicate Whether You Can Provide A Capability Demonstration Of The Proposed Solution For An Enterprise-wide System. requested Information: interested Parties Are Encouraged To Respond To This Notice If They Have The Capability To Meet The System Functionalities Identified In This Document. Questions Related To This Rfi Are Due By Noon, March 25, 2024 , And Should Be Forwarded Via Email To Gene Garrett At Gene.garrett@fema.dhs.gov And Jimmy Nguyen Atjimmy.nguyen@associates.fema.dhs.gov. The Due Date And Time For Responses Is April 3, 2024, And Shall Be Submitted Via Email To Jgene Garrett At Gene.garrett@fema.dhs.gov And Jimmy Nguyen Atjimmy.nguyen@associates.fema.dhs.gov. responses Should Be Limited As Outlined In The Attached Technical Document. Each Response Section Shall Be Clearly Titled And Shall Begin At The Top Of Each Page (e.g., Corporate Profile, Previous Performance, Critical Business Requirements). The Response Shall Be No More Than Twenty (20) Pages. All Pages Of Each Response Section Shall Be Appropriately Numbered And Identified By The Complete Company Name, Date, And Reference Number Listed On The Notice In The Header And/or Footer. Page Size Shall Be No Greater Than 8 1/2" X 11." The Top, Bottom, Left And Right Margins Shall Be A Minimum Of One Inch Each. Font Size Shall Be No Smaller Than 12-point. Arial Or New Times Roman Fonts Are Required. Characters Shall Be Set At No Less Than Normal Spacing And 100% Scale. Tables And Illustrations May Use A Reduced Font Size Not Less Than 8-point And May Be Landscape. Line Spacing Shall Be Set At No Less Than Single Space. Each Paragraph Shall Be Separated By At Least One Blank Line. Page Numbers, Company Logos, And Headers And Footers May Be Within The Page Margins Only And Are Not Bound By The 12-point Font Requirement. Footnotes To Text Shall Not Be Used. Pages In Violation Of These Instructions, Either By Exceeding The Margin, Font, Or Spacing Restrictions Or By Exceeding The Total Page Limit, Will Not Be Reviewed. Pages More Than The Maximum Will Be Removed From The End Of The Response Without Being Reviewed. The Page Count Will Be Determined By Counting The Pages In The Order They Come Up In The Print Layout View. Pages Not Reviewed Due To Violation Of The Margin, Font Or Spacing Restrictions Will Not Count Against The Page Limitations. your Response May Be Releasable To The Public Under The Freedom Of Information Act (foia), 5 U.s.c. 552, And The Dhs Foia Regulation, 6 C.f.r. Chapter 1 And Part 5. If You Wish Fema To Consider Any Portion Of Your Response As "confidential Commercial Information", You Should Clearly Mark The Portion As "confidential Commercial Information". The Procedures For Identifying "confidential Commercial Information" Are Set Forth In The Dhs Foia Regulation Cited Above And Are Available On The Dhs Website, Http://www.dhs.gov/xfoia/editorial_0579.shtm. Fema, At Its Discretion, May Request Respondents To This Rfi To Elaborate On Information In Their Written Response. All Information Contained In This Rfi Is Preliminary And Is Subject To Revision And Is Not Binding On The Government. the Collection Of This Data Does Not Obligate The U.s. Government To The Incorporation Of The Solicited Comments In Any Future Procurement Action Nor Does It Obligate The Government To The Procurement Of Any Services Or Products Related To This Rfi. Responses To This Rfi Will Not Be Returned Nor Will Respondents Be Privy To Debriefings To Their Respective Submittals. Information Provided Will Be Used Solely By Fema As Market Research And Will Not Be Released Outside Of The Fema Operations Integration Section. requested Information respondents Are Requested To Provide Information About Solutions They Offer Or May Propose. Please Provide The Information You Deem Relevant To Respond To The Specific Inquiries Of The Rfi. Please Refer To The Following Items For Specific Questions/criteria That Fema Is Looking For Industry To Provide Answers To In Their Responses: corporate Information And Solution Context: Fema Requests Information About The Provider, Their Experience Providing Solutions Similar To The Requirements Of This Rfi Related To Ui/ux Developments, Highly Secured And Hardened Cloud Hosting With Fedramp High Authorization, Extensive Collaboration And Networking Capabilities, Emergency Management And Response, Mass Alerting, Customized Workflows, Interoperability, Predictive Analysis Which Offer Sophisticated Insights Into Outcomes Based On Historical Data And Statistical Modeling For Risk And Opportunity Assessments, Integrated Access To Other Federal And Defense Agencies For Data Sharing, Collaboration, And Common Operating Pictures (cop) Across Fema And All Of Its Stakeholders. critical Business Requirements: Fema Requests Information About The Offered Solution’s Ability To Perform Against A Non-exhaustive List Of High-level Agency Wide Technical Solution Requirements. to Support Budget And Planning Purposes You May Also Include Rough Cost Estimates Based Upon The Objectives Outlined In The Rfi. advise If Your Product Is Available Via Existing Contract Vehicles Or Special Procurement Authorities Such As Gsa Federal Supply Schedules (far 8.4), Far 19.8 8(a) Procedures, Small Business Innovation Research (sbir) Program, Etc.