Sidebar

Katrina and On Demand e-Government

Commentary
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

IBM has staked a lot on the computing model called On Demand and, over the last five years, it has invested heavily in developing the tools and services necessary to propel the architecture. One of IBM's more crucial business strategies is to engage government entities at both the federal and the local levels in expanding the expertise and services of their e-government offerings. In the United States, this e-government initiative stretches back to the Clinton administration, but it has been more fully embraced recently, in the aftermath of 9/11, by the Bush administration.

However, if there were flaws in the On Demand model, they were certainly exposed in the recent hurricane disaster that has devastated the coastal cities of Mississippi and Louisiana. And there are lessons to be learned. These lessons address a number of key questions: What happens when the underlying infrastructure for electronic technology fails? What happens to the delivery of services? What happens to the structure and efficiency of centralized control and command?

On Demand in a Disaster Recovery Scenario

In a business environment, an infrastructure failure in an On Demand environment merely causes a loss of business. In severe situations, it may even result in the ultimate failure of the enterprise. In the recent natural disaster, however, when the government relied upon On Demand technologies for collaboration and coordination, Katrina demonstrated that an infrastructure failure can and will cause loss of life, the demise of law and order, and the suffering of untold thousands. By comparison to the tasks facing FEMA in the aftermath of Katrina, IT disaster recovery planning seems terribly trivial. Yet, when we witness the result of FEMA, it's hard not to think that IT would have handled it all very differently.

This is not to criticize the On Demand computing model, nor to pretend that the physical disaster caused by Katrina might have been avoided. Such terrible disasters will occur regardless of the computing model that has been chosen to deliver disaster services.

But Katrina and its aftermath should be wake-up calls to remind FEMA administration that it must plant its feet back in the real world, and IT's experience with disaster recovery contingency planning may be an interesting starting point. Sure, the scope is significantly different, the stakes infinitely more important, and the tools needed more diverse. Still, every IT manager knows that it's the outcome that measures the success of a disaster recovery contingency plan, not how well the management is informed of the costs.

Centralized Control and Command

In Katrina's case, too often the centralized command and control of rescue operations actually prevented workers on the ground from accomplishing their missions. Too often, the On Demand services delivered did not meet the needs of the victims.

The media has, for better or worse, portrayed the resulting problems of New Orleans as simple bureaucratic mismanagement. Indeed, one cannot dismiss this conclusion. And yet, in many cases, it was the underlying goals of the government's On Demand model that also failed.

Why did it fail? Because their On Demand model never met the requirement of delivering positive outcomes for the victims. Instead, it was focused upon delivering information to the FEMA controllers--the "management" administrator--enabling them to exert micro-control over the delivery of services, despite the needs of rescue workers on the ground.

Controlling the Intelligence

Consider the fact that rescue workers at the state and local levels were never fully coordinated into a master disaster plan of action. Such contingency plans had been in place for the city of New Orleans in previous years. Unfortunately, funding for updating those contingencies was eliminated during the aftermath of 9/11 in the first years of the Bush administration. This lack of an up-to-date, comprehensive, regional contingency plan meant that rescue workers were forced to rely upon outdated instructions that were often geared to previous generations of electronic technology. Meanwhile, the federal government had implemented newer technologies to gather intelligence that no longer meshed with the older contingency plans.

Furthermore, consider that the new On Demand model implemented by FEMA did not integrate with the mechanisms of the Red Cross and local and municipal rescue teams. Instead, the services that were to be delivered were focused on obtaining information about the disaster while often merely delivering tokens of service to the victims.

In other words, they had centralized the model of delivering services but had not provided a redundant method for local officials to use those services.

Failing Delivery Services

Consider, as an example, that FEMA's centralized control of the emergency actually blockaded rescue workers in one parish from delivering water, food, and diesel fuel for runing generators because those resources were not registered in their information system.

Consider, as another example, that rescue workers were instructed to chart the coordinates of corpses floating in the streets of New Orleans with handheld radio GPS devices--devices that sent the information to a centralized FEMA database--but that these same rescue workers were prevented by FEMA from actually recovering the bodies. FEMA could find the bodies, but it could not deliver the vehicles or the personnel to recover them.

Consider that, despite the overwhelming amount of information that FEMA had about the risk of a storm like Katrina, about the certain knowledge that the levees would fail in the aftermath, about the estimated numbers of citizens who would have no transportation out of New Orleans, and about the masses of evacuees who were still seeking shelter at the New Orleans Convention Center, still no means seems to have existed for FEMA to actually effect a rapid and coordinated rescue.

In other words, the On Demand model delivered the information to FEMA very well; the agency was awash with information. Yet transforming that information into a multi-threaded response to achieve its primary mission of rescue seemed beyond its capabilities.

Acronyms for Failure

The acronym FEMA stands for Federal Emergency Management Agency. In the aftermath of Katrina, its name might well have been altered to Federal Emergency Information Management Agency, for certainly information management was the only task it achieved.

Yet every IT manager worth his salt knows that managing the information about a disaster--whether it be a DASD failure, a complete system meltdown, or a catastrophic collapse of the business infrastructure--is only the beginning of handling the calamity. In an IT disaster recovery scenario, delivering the means of recovering the environment is more important than knowing the extent of the damage. And here FEMA's On Demand service delivery model clearly failed.

Tokens of Service in a Disaster

For example, we have all heard of the pilot program that FEMA promoted during the initial days following Katrina: the distribution of ATM cards to the victims of the storm. The idea was that these citizens could each withdraw up to $2,000 from a government account to manage their immediate needs.

Although FEMA later acknowledged that this was only a pilot program not intended for every victim of the disaster, the more important point seems to have eluded the administrators. In a disaster of Katrina's magnitude, cash has little or no value, and ATM machines--if they are functioning at all--will quickly become emptied. Meanwhile, regardless of the availability of paper money or credit, food, water, shelter, and safety cannot be purchased at any price. A small piece of credit card plastic in such circumstances may be a flashy token of service, but it's certainly an absurdly fragile safety net.

The equivalent in the aftermath of an IT disaster might be restoring access to the Internet when the mission-critical applications are still down. It's a nice thing to have--maybe even important for some users--but it's not a measure of success. In the light of a real disaster, it's a measure of incompetence.

In Katrina's case, providing plastic credit to victims was a flashy service. But it wasn't the measure by which FEMA would be judged. Rescuing citizens in need and restoring a system of law and order along with basic mission-critical systems was!

The On Demand Delivery Mechanism

And yet, when one looks at the underlying service delivery model, delivering credit cards is exactly the sort of On Demand service mechanism IBM (and others) has pushed onto the federal government. After all, keeping people tied into the ether-economy through credit vouchers is what information technology companies are all about. Great concept in the abstract! Little value under the circumstances!

Don't get me wrong. I have the greatest respect for the brave teams of rescuers, admiration for the dedication of those attempting to manage the catastrophe on the ground, and even grudging respect for the long hours put in by administrators and workers on the FEMA team. However, there's an old adage: "When all you have is a hammer, all your problems look like nails." In this case, FEMA seemed reduced to relying completely upon the On Demand model for managing the disaster. As a result, though the agency and its administrators took a beating, it was the poor suffering victims of Katrina who got screwed.

Lessons of Contingency

By comparison, in our IT environments over the years, we have learned the lessons of disaster recovery through trial and error. Though individually we could never manage an event like the horrible aftermath of Katrina, it is still a wake-up call to examine our reliance upon new technologies in our contingency plans. What happens if they fail? What are the real outcomes that our management and our users require us to deliver? Is our contingency plan up to the challenge? Is it up-to-date with the technologies we are using? Can it withstand and deliver, even in the most critical of circumstances?

We long ago learned, by anticipating the unthinkable, that we should not rely solely upon a single technology to rescue us or to enable us to recover. We've learned that there is no substitute for a comprehensive disaster recovery plan, with trained people in place and alternate backup facilities available. And we expect to roll up our sleeves and get dirty in the process. Most importantly, we know we can't ignore the signs of impending disaster when we discover them, and we know we must think proactively about how we might recoup our losses after a disaster.

Because, without such a contingency plan, we in IT, like FEMA in New Orleans, will be reduced to praying for blue skies after Mother Earth has wrought her wrath.

Thomas M. Stockwell is Editor in Chief of MC Press Online, LP.

Thomas Stockwell

Thomas M. Stockwell is an independent IT analyst and writer. He is the former Editor in Chief of MC Press Online and Midrange Computing magazine and has over 20 years of experience as a programmer, systems engineer, IT director, industry analyst, author, speaker, consultant, and editor.  

 

Tom works from his home in the Napa Valley in California. He can be reached at ITincendiary.com.

 

 

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

RESOURCE CENTER

  • WHITE PAPERS

  • WEBCAST

  • TRIAL SOFTWARE

  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things


    Read Node.js for Enterprise IBM i Modernization Now!

     

  • Profound Logic Solution Guide

    SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation.
    Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects.
    The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the companyare not aligned with the current IT environment.

    Get your copy of this important guide today!

     

  • 2022 IBM i Marketplace Survey Results

    Fortra2022 marks the eighth edition of the IBM i Marketplace Survey Results. Each year, Fortra captures data on how businesses use the IBM i platform and the IT and cybersecurity initiatives it supports.

    Over the years, this survey has become a true industry benchmark, revealing to readers the trends that are shaping and driving the market and providing insight into what the future may bring for this technology.

  • Brunswick bowls a perfect 300 with LANSA!

    FortraBrunswick is the leader in bowling products, services, and industry expertise for the development and renovation of new and existing bowling centers and mixed-use recreation facilities across the entertainment industry. However, the lifeblood of Brunswick’s capital equipment business was running on a 15-year-old software application written in Visual Basic 6 (VB6) with a SQL Server back-end. The application was at the end of its life and needed to be replaced.
    With the help of Visual LANSA, they found an easy-to-use, long-term platform that enabled their team to collaborate, innovate, and integrate with existing systems and databases within a single platform.
    Read the case study to learn how they achieved success and increased the speed of development by 30% with Visual LANSA.

     

  • The Power of Coding in a Low-Code Solution

    LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks

     

     

  • Why Migrate When You Can Modernize?

    LANSABusiness users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
    In this white paper, you’ll learn how to think of these issues as opportunities rather than problems. We’ll explore motivations to migrate or modernize, their risks and considerations you should be aware of before embarking on a (migration or modernization) project.
    Lastly, we’ll discuss how modernizing IBM i applications with optimized business workflows, integration with other technologies and new mobile and web user interfaces will enable IT – and the business – to experience time-added value and much more.

     

  • UPDATED: Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    FortraIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact

     

  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using NodeRun.com as a pre-built development environment

     

     

  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.

     

     

  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.

     

     

  • Encryption on IBM i Simplified

    SB PowerTech WC GenericDB2 Field Procedures (FieldProcs) were introduced in IBM i 7.1 and have greatly simplified encryption, often without requiring any application changes. Now you can quickly encrypt sensitive data on the IBM i including PII, PCI, PHI data in your physical files and tables.
    Watch this webinar to learn how you can quickly implement encryption on the IBM i. During the webinar, security expert Robin Tatam will show you how to:

    • Use Field Procedures to automate encryption and decryption
    • Restrict and mask field level access by user or group
    • Meet compliance requirements with effective key management and audit trails

     

  • Lessons Learned from IBM i Cyber Attacks

    SB PowerTech WC GenericDespite the many options IBM has provided to protect your systems and data, many organizations still struggle to apply appropriate security controls.
    In this webinar, you'll get insight into how the criminals accessed these systems, the fallout from these attacks, and how the incidents could have been avoided by following security best practices.

    • Learn which security gaps cyber criminals love most
    • Find out how other IBM i organizations have fallen victim
    • Get the details on policies and processes you can implement to protect your organization, even when staff works from home

    You will learn the steps you can take to avoid the mistakes made in these examples, as well as other inadequate and misconfigured settings that put businesses at risk.

     

     

  • The Power of Coding in a Low-Code Solution

    SB PowerTech WC GenericWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks

     

     

  • The Biggest Mistakes in IBM i Security

    SB Profound WC Generic The Biggest Mistakes in IBM i Security
    Here’s the harsh reality: cybersecurity pros have to get their jobs right every single day, while an attacker only has to succeed once to do incredible damage.
    Whether that’s thousands of exposed records, millions of dollars in fines and legal fees, or diminished share value, it’s easy to judge organizations that fall victim. IBM i enjoys an enviable reputation for security, but no system is impervious to mistakes.
    Join this webinar to learn about the biggest errors made when securing a Power Systems server.
    This knowledge is critical for ensuring integrity of your application data and preventing you from becoming the next Equifax. It’s also essential for complying with all formal regulations, including SOX, PCI, GDPR, and HIPAA
    Watch Now.

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    TRY the one package that solves all your document design and printing challenges on all your platforms.

    Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    FortraRobot automates the routine tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. How can you be sure you won’t miss important system events?
    Automate your message center with the Robot Message Management Solution. Key features include:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    FortraRobot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing.
    Manage your reports with the Robot Report Management Solution. Key features include:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.