Laserfiche WebLink
Crossing Wires <br /> <br />federal government. For this proj- <br />ect, the governments are not focus- <br />ing on getting radios to talk to one <br />another. Instead, they are using a <br />Web browser that first responders <br />will have on their mobile comput- <br />ers, personal digital assistants or <br />data-enabled mobile phones. Those <br />with existing mobile data systems <br />will go through an electronic bridge <br />to get connected to other systems <br />they couldn't communicate with <br />before. (Those without mobile <br />computers, such as the Maryland <br />State Police, will be getting them.) <br /> The Alexandria, Virginia, po- <br />lice department, for instance, has a <br />good mobile data system for its <br />force. But it can't connect with <br />neighboring jurisdictions. In a few <br />months, if all goes well, the Alexandria <br />system will be able to communicate with <br />the rest of the systems in the region, via a <br />set of computers housed in Greenbelt, <br />Maryland. Essentially what's happening is <br />that equipment in Greenbelt is being used <br />as a gateway to "translate French into <br />German," says George Ake, the project <br />coordinator. That is, Alexandria-speak is <br />being translated into other neighboring <br />government-speak without any of those <br />governments having to buy new systems. <br />The software is off the shelf and standards <br />based. "People can't afford to buy new sys- <br /> <br />Ability of public safety officials to communicate by radio <br />across different wireless systems on demand and in real <br />time, 2003. This assessment found a 41 percent increase <br />in national wireless interoperability scores since 2001. <br /> <br /> ~ Developing <br />Source: Public Safely Wireless Network Program ~ Established <br /> <br /> tems," AEe says. "if they already spent <br /> millions for a new system, they're not <br /> going to be really happy throwing it out <br /> and starting all over again." <br /> When there is a disaster that requires <br /> the cooperation of police, fire and medical <br /> units, first responders will be able to sit in <br /> their various vehicles or offices and log on <br /> to a computer chat room to discuss who <br /> should do what next. Or they can use <br /> instant messaging. They will get informa- <br /> tion from the FBI or a transportation <br /> department or a criminal database. The <br /> first governments had been expected to <br /> start using the system in March but that <br /> <br /> was delayed and they anticipate <br /> having the system ready for use <br /> within the next few weeks. <br /> <br /> DOUBLE WHAMMY <br /> While homeland security may <br />be a new term that will foster a <br />new thinking process, the equip- <br />ment that is purchased and the <br />partnerships formed can serve a <br />dual purpose, and "regular" invest- <br />ments can do double duty for <br />homeland security. Virginia area <br />fire fighters and emergency med- <br />ical technicians, for instance, <br />might tap into the CapWIN wire- <br />less interoperability system when <br />a truck with hazardous materials <br />tums over on the Capital Beltway. <br />Cook County, Illinois, is doing an aerial <br />flyover for its GIS system that will provide <br />location information that can be used for <br />crime, natural disasters or terrorism- <br />related incidents. <br /> While interoperability is useful, the <br />ability to communicate from system to sys- <br />tem presents a fundamental challenge for <br />any technology environment. The tools <br />exist to connect up those who want to be <br />connected, but connectivity can mean the <br />opposite of security. A connected system <br />becomes only as strong as its weakest link. <br />The more hands and eyes on data, from <br />various departments with different levels <br />of management and differing policies on <br />protecting data, the more the risk level <br />rises. The result, says Kirk Bailey, Seattle's <br />CIO, is a "never ending litany of poten- <br />tial liability." <br /> Most operating systems were developed <br />without security in mind, so enabling <br />them to speak to one another creates <br />additional risks. And that problem, Bai- <br />ley suggests, is almost unsolvable. <br /> That doesn't mean that governments <br />should back off from their goal of sharing <br />information. What's needed is a business <br />and technology evaluation on how much <br />risk to take, and that's not a new concept. <br />Federal regulations for the banking indus- <br />try and health regulations under <br />HIPAA the health care privacy law that <br />mandates electronic transfer of informa- <br />tion-speak to standards and rules on pri- <br />vacy and security. At the same time, state <br />and local agencies are looking for the most <br />affordable, best bang for the buck option. <br />"The information age has wrought upon <br />us a unique challenge," Bailey says. "It's <br />very hard to do." [] <br /> <br />Governing.corn <br /> <br /> <br />