September 4, 2011
9/11 - A Lesson In Risky Business
November 16, 2010
Who Needs Airport Body Scanners? An Alternative Approach
Who Needs Airport Body Scanners? An Alternative Approach
August 7, 2010
No Real Solution Without Integration
Emergency Management Magazine (July/August 2010) has an article called “Life Savers” that describes how a convergence of new technologies will help protect and save first responder lives. These new technologies can track first responders’ location (“inside buildings, under rubble, and even below ground”) and monitor their vital signs and send alerts when their health is in danger.
There are numerous technologies involved in protecting our first responders and knowing where they are and that their vitals are holding up:
- For locating them—“It will likely take some combination of pedometers, altimeters, and Doppler velocimeters…along with the kinds of inertial measurement tools used in the aerospace industry.”
- For monitoring health—“We’ve got a heart monitor; we can measure respiration, temperature. We can measure how much work is being done, how much movement.”
The key is that none of the individual technologies alone can solve the problem of first responder safety. Instead, “All of those have to be pulled together in some form. It will have to be a cocktail solution,” according to the Department of Homeland Security (DHS), Science and Technology (S&T) Directorate that is leading the effort.
Aside from the number of technologies involved in protecting first responders, there is also the need to integrate the technologies so they work flawlessly together in “extreme real world conditions,” so for example, we are not just monitoring health and location at the scene of an emergency, but also providing vital alerts to those managing the first responders. This involves the need to integrate the ability to collect inputs from multiple sensors, transmit it, interpret it, and make it readily accessible to those monitoring the scene—and this is happening all under crisis situations.
While the first responder technology “for ruggedized vital-sign sensors could begin in two years and location tracking in less than a year,” the following lessons are clear:
- The most substantial progress to the end-user is not made from lone, isolated developments of technology and science, but rather from a convergence of multiple advances and findings that produce a greater synergistic effect. For example, it clearly takes the maturity of numerous technologies to enable the life saving first responder solution envisioned.
- Moreover, distinct technical advances from the R&D laboratory must be integrated into a solution set that performs in the real world for the end-user; this is when product commercialization becomes practical. In the case of the first responder, equipment must function in emergency, all hazard conditions.
- And finally, to bring the multiple technologies together into a coherent end-user solution, someone must lead and many parties must collaborate (often taking the form of a project sponsor and an integrated project team) to advance and harmonize the technologies, so that they can perform as required and work together seamlessly. In the case of the first responder technology, DHS S&T took the lead to come up with the vision and make it viable and that will save lives in the future.
No Real Solution Without Integration
August 18, 2009
DHS OIG Report on My User-centric EA Implementation at the Coast Guard
I am pleased at the recognized progress and at the terrific work that my team accomplished there--I am very proud of all of them!
Of course, there is more work to be done, but the right EA infrastructure has been put in place to accomplish the goals and objectives set out.
Here is the link to the report: http://sites.google.com/site/thetotalcio/Home/links/EAOIGReport-July2009.pdf?attredirects=0
"The Coast Guard has made progress in developing its enterprise architecture by defining its enterprise architecture framework [User-centric EA] in alignment with both federal and DHS architectures. In addition, its enterprise architecture is aligned with the Coast Guard's IT strategy. These achievements have been possible because of executive support for the enterprise architecture effort."
DHS OIG Report on My User-centric EA Implementation at the Coast Guard
July 13, 2008
Secure Border Initiative and Enterprise Architecture
The enterprise architecture change process starts with requirements generation and management. Requirements become business cases and business cases become decision requests for new or changes to IT projects, products, and standards that go before the enterprise architecture board (EAB) and ultimately to the IT investment review board (IRB). The decision requests get vetted against the architecture for business alignment and technical compliance by the EAB. The IRB takes the findings of the EAB and also looks at return on investment and risk management. Approved changes to the IT environment get added to the enterprise architecture.
So mission-business requirements from the program sponser/end user are the starting point for changes to the EA.
What happens though when requirements are unclear?
Obviously, if the requirements are unclear, then proposed changes to the enterprise are sort of like shooting in the dark, and the ability to develop viable technical solutions is a guessing game.
An article on Secure Border Initiative in National Defense Magazine, July 2008, demonstrated how the architecture does not add up, when the “Border Calculus” is a big question mark.
After 9/11, securing the border became a more publicized issue. With the formation of DHS, the Secure Boarder Initiative (SBI) was set up in 2005.
SBI is supposed to secure the border, okay. But secure it against what is the question. What are the requirements for securing it?
- Illegal immigrants—“For many Americans—especially these who don’t live near the border—illegal immigration is what prompts their calls for a beefed up border.” While some say that “the U.S. economy depends on cheap labor…others claim illegal immigrants are a drain on the economy.”
- Terrorism—“For the Department of Homeland Security, charged with protecting the nation, keeping weapons of mass destruction out of the United States is the priority.”
- Drugs—“for many who live north and south of the four states that border Mexico, the real threat is narcotics.”
Each of these purposes, changes the equation. If the primary purpose you are securing the border is to protect against a genuine threat of weapons of mass destruction, then some may argue for highly secure border, one that is truly non-porous, without regard to cost. However, if the goals are more for controlling illegal immigration, perhaps a less perfect and less costly border security solution is acceptable. And if drugs are the issue, then maybe the money is better spent going after the source, rather than building fences that can be circumvented.
So understanding and building consensus on the true requirements are critical to developing a business case and a technical solution.
As it stands now, SBI is going in two directions:
- Physical fence—“to stop those on foot or on vehicles.” Estimates by the Congressional Research Service “say that maintaining those fences may cost up to $49 billion.” While critics say that these physical barriers “only delay an illegal crosser three to four minutes,” so is this worth it?”
- Virtual fence—“Sensors, cameras, improved communication systems and unmanned aerial vehicles.” According to the article, “no one seems know how much it will cost to set up and maintain these high-tech systems throughout their lifespan.”
Additionally, “plans call for doubling the number of border patrol agents.”
I guess without a clear consensus on what we’re trying to accomplish, any solution will get us there or not. Isn’t this what an enterprise architecture is supposed to help with—establishing a clear roadmap or blueprint? Of course, but it’s got to start with the requirements generation process and with the business owners.
Secure Border Initiative and Enterprise Architecture
January 25, 2008
Big Brother is Watching and Enterprise Architecture
The intent is to use these screening technologies at airports, border crossings, as well as possibly in the private sector for building access control and candidate screening.
- Recognition of gestures and microfacial expressions
- Analysis of variations in speech (i.e. pitch, loudness)
- Measurement of physiological characteristics
- Currently, too many false positives
- Existing technologies, like the polygraph have “long been questioned by scientists…and remain inadmissible in court.”
- Ability of algorithms to “correctly interrupt” suspicious behavior or cues
- Profiling is continuously objected too based on discriminatory grounds
- Privacy concerns about the personal data collected
- Testing is limited by security concerns in the field
- Deployment will be limited due to cost, leaving soft targets potentially at risk
Big Brother is Watching and Enterprise Architecture