December 10-11 2021 tornado map. The areas that were affected by the tornado were: Arkansas, Illinois, Kentucky, Missouri, and Tennessee.
December 12, 2021
WASHINGTON — FEMA Administrator Deanne Criswell and Department of Homeland Security Sec. Alejandro Mayorkas traveled to Kentucky today where they were briefed by local and commonwealth officials and held a media briefing with Kentucky Gov. Andy Beshear.
The tour allowed Criswell and Mayorkas to see the tornado destruction firsthand and meet with first responders and emergency management officials conducting operations throughout the state. They toured areas of Graves and Marshall counties, also seeing the destroyed Mayfield Consumer Products factory.
“To all of the people of Kentucky, my heart goes out to each and every one of you who have experienced the tragic events from these tornadoes,” said Administrator Criswell. “I want you to know that the nation, your country, is praying with you. We’ve been seeing the pictures of this, but standing there in these communities, you don’t get that feeling from a picture. When you stand in one direction and look and see all of the devastations and then just turn to your right and all of the devastations around you, you can’t understand how this has impacted these communities until you’re there,” she continued. “That’s why it’s so important to be here to see it for myself, so we can make sure that we’re providing the right level of assistance to help with your response and your ongoing recovery.”
Criswell added that FEMA still will be working with the commonwealth on all their long-term recovery needs as these communities start to rebuild.
BENTON, Ky. — Kentucky Emergency Management Director Mike Dossett (center) briefs DHS Secretary Alejandro Mayorkas (left) and FEMA Administrator Deanne Criswell (right) as they begin touring damage throughout the area.
BENTON, Ky. — Local Marshall County incident commander briefs DHS Sec. Alejandro Mayorkas (center) and Administrator Criswell, showing a satellite image of the tornado’s path.
MAYFIELD, Ky. — Louisville Emergency Management Director E.J. Meiman and Administrator Criswell discuss response operations near the Mayfield Consumer Products factory that was destroyed by a tornado late Friday.
HQE Systems, Inc. is looking to partner with Fayette County, KY.
HQE’s partner should have a technical workforce that can operate hand tools, have an understanding of low voltage hardware, and be ready to provide customer support (telephonic, email, and customer support portal).
As a Minority-Owned, Service Disabled Veteran Owned Small Business, HQE is looking to partner with a certified Minority Woman Owned Small Business that is operating in Fayette County, KY.
If you qualify as one of the certified business entities below, please contact us.
From the client: OUR MISSION: The mission of the Minority Business Enterprise Program is to facilitate the full participation
of minority and women owned businesses in the procurement process and to promote economic inclusion as a
business imperative essential to the long term economic viability of Lexington-Fayette Urban County
Government. To that end the city council adopted and implemented Resolution 484-2017 – A Certified Minority, Women and
Disadvantaged Business Enterprise ten percent (10%) minimum goal and a three (3%) minimum goal for
Certified Veteran-Owned Small Businesses and Certified Service Disabled Veteran – Owned Businesses for
government contracts. The resolution states the following definitions shall be used for the purposes of reaching these goals (a full copy is available in Central Purchasing):
Certified Disadvantaged Business Enterprise (DBE) – a business in which at least fifty-one percent (51%) is owned, managed
and controlled by a person(s) who is socially and economically disadvantaged as define by 49 CFR subpart 26.
Certified Minority Business Enterprise (MBE) – a business in which at least fifty-one percent (51%) is owned, managed and
controlled by an ethnic minority (i.e. African American, Asian American/Pacific Islander, Hispanic Islander, Native American/Native Alaskan Indian) as defined in federal law or regulation as it may be amended from time-to-time.
Certified Women Business Enterprise (WBE) – a business in which at least fifty-one percent (51%) is owned, managed and
controlled by a woman.
Certified Veteran-Owned Small Business (VOSB) – a business in which at least fifty-one percent (51%) is owned, managed
and controlled by a veteran who served on active duty with the U.S. Army, Air Force, Navy, Marines or Coast Guard.
Certified Service Disabled Veteran Owned Small Business (SDVOSB) – a business in which at least fifty-one percent
(51%) is owned, managed and controlled by a disabled veteran who served on active duty with the U.S. Army, Air Force, Navy, Marines or Coast Guard.
The term “Certified” shall mean the business is appropriately certified, licensed, verified, or validated by an organization or entity recognized by the Division of Purchasing as having the appropriate credentials to make a determination as to the status of the business.
HQE Systems Inc. is a FEMA Certified, Service Disabled Veteran Owned Small Business (SDVOSB), Minority Business Enterprise (MBE), and a Disadvantaged Business Enterprise (DBE). HQE is a software and technology innovation company that can mitigate any pain points for clients of all sizes.
Every moment counts in an emergency, so getting help should be as simple as dialing 911. In Kari Hunt Dunn’s case, that phone call proved impossible — her hotel room didn’t allow guests to directly dial emergency services. As Dunn’s estranged husband attacked her in 2013, her young daughter made several attempts to call authorities for help. None went through because she didn’t first dial “9” for an outside line.
But a new federal law will make a difference for the next victim. Kari’s Law requires multi-line phone systems to have a default configuration that enables users to dial 911 directly. While the law doesn’t require mass notification, it highly recommends organizations deploy on-site notification – which automatically sends alerts to executives and on-site emergency responders – if the communications solution in place supports it.
As a result, government agencies, universities and K-12 schools need to be sure their communications solutions comply with the law. Although many legacy phone systems don’t have this functionality, today’s communications technology offers a robust and easily installed solution at a reasonable cost.
To help with your planning, here’s an overview of two technologies – on-site notification and mass notification – and how they can make your school community and government offices safer.
On-site notification keeps the people in your care safer by automatically notifying first responders of an emergency, getting trained assistance to the right people in less time.
Executives can notify staff and on-site police and security as soon as someone dials 911. Alerts include the name, extension number and exact location of the caller. This is especially important in large government buildings and school campuses. Simultaneous notification allows the right people to respond immediately in an appropriate and unified manner. The system’s built-in messaging even allows text communications to be sent from desktops, further enhancing a timely and coordinated response.
Currently only a recommendation, on-site notification will likely become required in the future. In fact, this technology is already available and affordable with new communications technology solutions. As legacy phone systems reach the end of their lifespans, more organizations are sure to adopt this feature.
Finally, integrating your emergency notification system with door locks removes the need to physically lock doors, providing increased protection in an instant. Staffers can initiate a lockdown or lockout from any type of phone.
The technology that underlies onsite notifications systems – intelligent mass notification – offers additional safety features. Most importantly, governments and schools can quickly deliver critical information to an entire community or relevant subgroup when emergencies arise. The technology is also versatile. For example, administrators can use a variety of channels and devices to send alerts.
If you’re in the financial services industry, you’re familiar with the dozens of whitepapers, trend reports, and news articles discussing the importance of legacy system modernization.
But “legacy modernization” as a buzzword doesn’t have to mean starting from scratch, rather it hints at the idea of bridging the divide between your existing legacy systems and the new ecosystem of apps that your customers demand connectivity to.
We’ve found that it’s helpful to think of this connectivity through a construction metaphor – an integration “bridge” that helps data move back and forth among your current infrastructure, your customers’ legacy (ERP) systems, and the “latest and greatest” apps that your users are consistently requesting from your CS team.
In theory, any skilled developer can build a brittle bridge of point-to-point connectivity between each business-critical application – whether it’s flexible, maintainable, and easy to adapt in the future is another question in and of itself.
According to BDO’s 2019 Middle Market Digital Transformation report, customers “will want to manage all their finances—not just one component—in one place, on the devices convenient to them. They will expect nothing less than real-time engagement when they need it. They will value simplicity, efficiency, and transparency.” But to achieve this reality, FIs need to offer myriad seamless integrations that connect to the applications customers need.
Banks’ widespread offerings (payments, lending, investment management, etc.) necessitate more. A better experience to retain customers, overcome fintech competition, and gain a future-ready technological edge.
PwC’s “Financial Services Technology 2020 and Beyond” report explains, “APIs require that financial institutions think differently about strategy… This is not just an issue for business strategists; it has clear technical implications for the teams who are responsible for doing the work.” As systems become more diverse and complex, FIs are forced to up their game via holistic data access.
Building More Bridges – Sustainably
You’re probably really happy with me at this point for telling you to do more with your integrations (sarcasm), but building better experiences for your customers doesn’t necessarily mean building one-off connections that require a large portion of your development team’s time to maintain. There’s another option – one-to-many integrations.
With one-to-many integrations, you map your data objects once to a canonical resource (such as our Finance Hub) and, via that multi-tenanted content, quickly connect to leading ERPs such as QuickBooks, NetSuite, & Microsoft Dynamics GP. One-to-many integrations offer both faster time-to-value and reduced LOE for your developers so your junior devs can take care of the integration work while others on the team focus on innovation.
The Maintenance Burden
But what happens when a bridge is broken and the data crossing the bridge (legacy <–> modern) can’t make it from one system to the other? Gaps in usability that necessitate hastened development work and hours on the phone assuring customers that a fix is ongoing.
You might have read about (or encountered) the very public dispute between Plaid and Capital One a couple of years ago. Using integration techniques that cause security concerns (screen-scraping vs API), or failing to offer robust, usable APIs are both characteristics of brittle bridges that make sharing data between legacy and modern systems difficult.
Not only did the collapse of this bridge eventually lead to integrations breaking (TurboTax couldn’t pull interest statements automatically for Capital One accounts this spring, frustrating my colleague on tax day…), but consider also the amount of rework needed behind the scenes to rebuild functionality customers have come to expect.
Sure, this FI vs. fintech battle is a public manifestation of how many banks feel about providing customer data access to fintech upstarts, but the public drama and backend hair-pulling & patching could have been avoided by building secure, multi-use integration ‘bridges’ (to our metaphor) from the start. Think about integration platforms as the people managing the bridge day-to-day to make sure nothing goes awry rather than the repair crew that comes in when cables start to snap.
Summing it Up
Financial institutions are in a unique position where one-to-many integrations can prove maximally beneficial in bridging the gap between existing and “new-to-them” systems. The need for connectivity to boost customer retention, gain a competitive edge, and provide a seamless experience is here to stay.
HQE Systems Inc. is a Service Disabled Veteran Owned Small Business (SDVOSB), Minority Business Enterprise (MBE), and a Disadvantaged Business Enterprise (DBE). HQE is a software and technology innovation company that can mitigate any pain points for clients of all sizes.