ROSS Ready for Primetime

 
 
By Larry Dignan  |  Posted 2003-12-04 Email Print this article Print
 
 
 
 
 
 
 


?">

The biggest question for the California fire defense team: Is ROSS ready for primetime? MIRPS project manager John King says its unlikely that the CDF will use ROSS next fire season, but 2005 is a possibility.

ROSS was developed by Lockheed Martin for the National Wildfire Coordination Group and designed to accommodate multiple federal agencies and all 50 states, most of which had paper systems to route resources.

This year represented the first real test of the national system. When a long fire season ended last month, ROSS had allocated and managed more than 150,000 resources such as people, engines and machines across 50 states, says ROSS project manager Jon Skeels.

According to Skeels, ROSS relies heavily on the Java programming language to tie together a wide range of applications—Oracle databases, IBM Websphere and Hyperions Brio business intelligence software—found in corporate systems.

Skeels, however, is hostage to the machinations of Congressional funding. When federal budget deliberations dragged on, Skeels had to postpone a migration to the 9i edition of Oracles database system as well as plans to add storage area networking and processing power. Those upgrades will occur before the 2004 fire season.

ROSS users paid the price over the summer when the existing system crashed for 3.5 hours in June, from a database overload. Meanwhile, network performance was abysmally slow in June because there was "too much stress on too-small servers," says Skeels. That fact prompted many dispatchers to go back to the friendly confines of faxes and paper forms.

The culprit for the poor performance: an incorrect configuration setting in an Oracle database that keeps a running diary of requests. "There were a few days where ROSS was a four-letter word around here," says DeneenCone, dispatch center manager for the state of Arizona, which was dealing with a slew of wildfires as performance lagged. "We were using a dual system of ROSS and paper to be fail-safe, so it still worked out."

In Oregon, the slow performance led Randall Baley, dispatch coordinator for the Oregon Department of Forestry, to revert to "slow-time" from real-time. "We were just more comfortable with paper in the heat of battle," he says. "ROSS has potential, but the speed of the system wasnt enough.

So how slow is ROSS? In theory, with ROSS, dispatchers take reports from the scene, check availability of resources, place orders for new equipment and personnel, and thats it.

By contrast, Baleys paper system involves filling out five different forms to request equipment, supplies and crews. These forms are then faxed or the contents read over the phone to a regional fire coordination center, where details are manually re-entered on forms. From there, details are again faxed or transcribed to a state coordination center.

Baley says the paper system can take at best a half hour to get an air tanker headed toward California. Requests for engines and supervisors could take "numerous hours" to fill. If running properly, ROSS can process that air tanker order in minutes because data is only entered once. The time frame for other resources depends on availability.

Skeels acknowledged the problems, which he contends have been corrected with additional hardware and a database fix. He also installed a plan of action to prevent future problems. "During that time [ROSS users]went back to paper," says Skeels. "No additional acres were lost."

Cone say ROSS functioned as promised after its June problems. Skeels is trying to quantify the returns from ROSS by tracking time and the number of orders moved.

Based on surveys with users, Skeels estimates ROSS led to better than a 50% decrease in the time needed to take and process orders. Skeels didnt have an average time for the paper system, but dispatchers like Baley say the time to fax something five times spans hours. Skeels says 2003 was largely a year to gather and create a baseline set of statistics for ROSS.

In the meantime, Skeels will continue to develop ROSS and fight a cultural war with champions of a slow, decades-old yet effective paper system.

"All ROSS is doing is taking what we were doing all along and automating it," says Cone. "Most people see it as all bells and whistles, but it really updates an archaic system. A lot of old fire dogs think itll fail for a while, though."

Discuss This in the eWEEK Forum



 
 
 
 
Business Editor
ldignan@ziffdavisenterprise.com
Larry formerly served as the East Coast news editor and Finance Editor at CNET News.com. Prior to that, he was editor of Ziff Davis Inter@ctive Investor, which was, according to Barron's, a Top-10 financial site in the late 1990s. Larry has covered the technology and financial services industry since 1995, publishing articles in WallStreetWeek.com, Inter@ctive Week, The New York Times, and Financial Planning magazine. He's a graduate of the Columbia School of Journalism.
 
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Rocket Fuel