Find out how these two Homeland Security agencies embraced cloud and are moving into third-generation cloud tactics to gain operational IT efficiencies and serve...
At least two large components of the Homeland Security Department are leading the way on what might best be described as third-generation cloud computing.
If initial cloud usage took email and other office tools off federal servers, and the second generation pulled in mission and operational support applications, the third generation of cloud will fully optimize code development, communications and data management for commercial cloud computing.
A case in point: the U.S Immigration and Customs Enforcement. ICE is completely in the cloud, said Richard Clark, the DHS agency’s chief technology officer. Speaking at a panel said during a panel at the Federal News Network Cloud Exchange 2023, he said ICE has “fully exited DHS data centers.”
It was a years-ago effort by DHS headquarters to consolidate components in departmental data centers that prompted ICE to explore cloud adoption.
“We saw [the consolidation] as a huge opportunity to exit from the data centers,” Clark said, “because moving from one zone to another was not going to provide us any real benefit.”
He added: “We may not quite have been ready for it. But we took it on with gusto, and we’re very happy that we are 100% in the cloud.”
At sister component Customs and Border Protection, the sheer scale of its transactions and their value prompted a steady move to the cloud, said Edward J. Mays, CBP’s deputy assistant commission for infrastructure and support services and its chief of enterprise infrastructure.
Mays pointed out that $2.7 trillion a year in exports — coupled with duty collections in excess of $100 billion — produces 40 billion transactions daily. The result? Multiple petabytes of data crossing CBP networks, he said.
As it continues its broad use of cloud, Mays’ group is also transitioning CBP’s communications infrastructure from traditional proprietary circuits to public broadband, brought together in the agency’s internet connection points.
“We think we’re about a year out, maybe a little more,” he said. That new infrastructure will unify how data from edge collection points get to cloud applications and vice versa, so that data is available to analysts, say, on the Southwest border, Mays explained.
The next iteration of cloud architecture will unite “hardware, software and cloud to securely connect sensors and systems in complex operational environments,” said Mathieu Guillebaud, product development director for the global security products at Leidos.
He cited scanning equipment Leidos deployed at the border that will generate a lot of data needed for support analysis and decision-making.
“We think in terms of extending the cloud out to the edge, bridging that gap,” Guillebaud said. “We call that edge-to-cloud.” In this scenario, edge sensors and other data gathering devices stage data in “some sort of on-premises rack, perhaps at a port of entry or in a regional command center … and then share it up to the traditional cloud, the enterprise.”
With cloud a given, what’s next? Guillebaud said he expects agencies to continue updating applications that they might have simply slid into the cloud initially. The idea is to render them more cloud-native and therefore easier to keep up to date.
“From our perspective, the concept of continuing to adopt cloud-native architectures and microservices-based approaches lends itself well to future-proofing,” he said. “And that goes along with continuing to leverage containerization technologies that allow deployment and management of services across geographic areas from the edge to the cloud.”
Clark noted that ICE has numerous active projects in containerizing applications.
“As I tell our teams: If you’re going to do all of the work to have a well-contained application, you should consider just going that extra flight of stairs and go serverless because that that will give you even more benefits than just going to containers,” he said.
Going serverless lets the agency rely on a cloud services provider to manage infrastructure capacity in response to demand for a particular application at a given time, which helps manage cost.
“A big part of that is breaking down the application into some of the component services, making certain that those can run the way they want to,” Clark said. “So that you know at 3 a.m. on Christmas Eve, when you know there’s only one guy logged into the system, we’re not running infrastructure that’s designed to support 6,000 users or whatever.”
Agencies also expect the capability of mixing and matching containerized software functions in an agile manner to create new applications, he said.
Like any technology, cloud computing requires an investment in times and resources. Initial lift and shift of applications to the cloud didn’t always lead to cost savings, but rather a change from managing equipment on premises to managing services. Mays said that as CBP continues its cloud journey, it will look for efficiency and savings. He agreed that a model of moment-by-moment consumption, coupled with the ability to scale up rapidly if needed, offers a pathway to that efficiency.
Better customer service and more extensive use of artificial intelligence also are part of CBP’s cloud goals, he said.
To improve customer experience, “it’s absolutely critical to ensure that you get that crosscutting thread that allows your customer base, your users, to actually access the services they need in a very easy manner.”
CX and A both focus on getting cloud services to the edge — the command centers and control centers where CBP agents and other employees interact with people and business entities.
“We’ve got at least 40 AI programs underway and probably another 140 or so robotics process automation efforts as well. So that’s a big thing for us,” Mays said.
Because managing clouds differs from managing data centers, he said his team has created a cloud services brokerage to help with cost-benefit analyses, architecture evaluation and application development.
“These are things that we’re doing differently now that I think will change the value proposition for our trusted partners and our stakeholders,” Mays said.
To read or watch other sessions on demand, go to our 2023 Cloud Exchange event page.
Copyright © 2024 Federal News Network. All rights reserved. This website is not intended for users located within the European Economic Area.
Deputy Assistant Commissioner for ISS and Chief of Enterprise Infrastructure, Customs and Border Protection
Chief Technology Officer, U.S. Immigration and Customs Enforcement
Product Development Director, Global Security Products Division, Leidos
Host, Federal Drive, Federal News Network
Deputy Assistant Commissioner for ISS and Chief of Enterprise Infrastructure, Customs and Border Protection
Dr. Edward J. Mays currently serves as the Deputy Assistant Commissioner (DAC) Infrastructure and Support Services (ISS), and Chief Enterprise Infrastructure (SES position) for United States Customs and Border Protection, Department of Homeland Security.
During his career, Dr. Mays (Colonel USMC, Ret.) served many years working with Information Technology (IT) and Software Development for logistics and Intelligence programs supporting the U.S. Marine Corps operational forces. He created a major Marine Corps logistic system used in the Marine Corps for over 25 years. He is a veteran numerous combat actions across the globe. In 2008, Dr. Mays became the Operations Assessment for Multinational Forces, Al Anbar, Iraq, where he played a substantive role in the return of Anbar Province to the government of Iraq. He also served in the US operations in Afghanistan, delivering IT capability and supporting the Afghan National Acquisition Agency.
Dr. Mays earned a Bachelor of Science from University of Florida, and a Master’s in IT from the University of Southern California. He attended the Naval Postgraduate School completed a Master’s degree in Computer Science, focusing on artificial intelligence and robotics. He also obtained a Doctor of Information Technology from Capella University in 2020.
Since 2016, Dr. Mays was selected as the Executive Director for the Enterprise Data Management and Engineering Division in OIT. In this role, he engineered cost effective, secure, and reliable IT solutions, and built the framework for Cloud computing at CBP.
In March 2022, Dr. Mays was appointed as the Deputy Assistant Commissioner for OIT’s Infrastructure and Support Services organization which combined three infrastructure organizations under his purview. The organizations have an enterprise focus: Field Support Directorate (FSD), Enterprise Infrastructure Operations Directorate (EIOD), and Enterprise Cloud Services Division (ECSD). The new organizational structure has created internal efficiencies executed the new Enterprise Cloud Services Directorate to complete CBP’s migration to the Cloud more affordably, effectively, and securely. Ultimately providing a modern, reliable IT infrastructure (Cloud, Networks, Mobility, etc.) and 24/7 year-round support services serve as the backbone for technology solutions that deliver critical capabilities at the speed of mission.
Chief Technology Officer, U.S. Immigration and Customs Enforcement
Product Development Director, Global Security Products Division, Leidos
Mathieu Guillebaud is a Product Development Director within Leidos” Global Security Products Division, where he manages Leidos”s non-intrusive imaging products, nuclear detection products, and software integration solutions. He has two decades of technology industry experience, having served in product and program management, engineering, and operations roles at detection technology companies. Before he joined Leidos in May 2020, Guillebaud was Product Line Director at L3Harris within the Security & Detection Systems business.
Mr. Guillebaud holds a Master of Engineering degree from the Rensselaer Polytechnic Institute and a Bachelor of Engineering degree from the Colorado School of Mines.
Host, Federal Drive, Federal News Network
Tom Temin has been the host of the Federal Drive since 2006 and has been reporting on technology markets for more than 30 years. Prior to joining Federal News Network, Tom was a long-serving editor-in-chief of Government Computer News and Washington Technology magazines. Tom also contributes a regular column on government information technology.