MICHIGAN MDOT TRAFFIC MANUAL
MICHIGAN MDOT TRAFFIC SOFTWARE

This Policy is incorporated into our Terms of Use. (DBA “NEOGOV”), including our related brands, ,, , and our mobile app(s) (collectively referred to as the “Services”), or affiliated companies (collectively referred to herein as “Governmentjobs”,“Schooljobs” ,“NEOGOV”, “NEOED”, “we”, “us”, or “our”).īy using any part of the Services you agree that you have read this policy, your personal data will be processed as described herein, and you agree to be bound by this Policy.

This Policy applies to personal data we collect or use, and applications owned or controlled by, Inc. Ultimately, the fact that a redesigned database 'could reduce accidents and maybe save some lives resulted in a level of commitment that I haven't seen in other projects,' Couto says.The purpose of this Privacy Policy (the “Policy”) is to describe how we collect, use, store, protect, and disclose personal data online and offline.

MICHIGAN MDOT TRAFFIC SOFTWARE

using Capability Maturity Model Level 5 from Carnegie Mellon University's Software Engineering Institute. A joint governance structure that included representatives from each of the three major project owners provided daily oversight and served as an approval mechanism for ongoing budgeting and scheduling.ĭevelopment work was done with the help of Electronic Data Systems Corp. It took nearly a year to gather business and technology requirements from multiple agencies, local governments, insurance companies, educational institutions and other users of the database. Key to the success of the project was the extensive collaboration that took place among the three principal stakeholders and others involved in the project, Couto says. The revised database allows Winslow to quickly look for accident data using parameters such as location, time of day or number of accidents. The process, which used to take five to six business days, was instead accomplished immediately, he says. 'Prior to having this in place, I would have had to contact the local county road commissioner and the Michigan State Police to get the information,' Winslow says. Winslow recently used the database to access information needed to apply for two road-improvement grants. 'The real return here is the reduced loss of life, which, to paraphrase a commercial, is priceless,' Couto says.īut the upgraded database has also made it a lot easier for law enforcement officials to retrieve accident information, says Chief Arlan Winslow of the Imlay City Police Department. More importantly, the redesigned Crash system will help improve traffic safety and road design by identifying accident risks and potential causes of traffic crashes and deaths, which cost the state $9.4 billion last year, he says.Ĭontributors to Michigan's redesigned Crash system include, from left to right, Mary Wichman, manager Jack Benac, project manager and Douglass Couto, information officer.Image Credit: Michelle Andonian 'We have identified about $4 million in savings over the next three years in decreased cycle times and improved quality,' says Jack Benac, project manager of the Crash redesign. Processing and hardware costs have been reduced, as have data errors. The gap between a traffic accident and data availability has been cut to 60 days. The results have been gratifying, says Douglass Couto, information officer at MDOT.

Instead of retrieving data from mainframe magnetic tapes and storage cartridges, users can now access data via a browser-based interface.

MICHIGAN MDOT TRAFFIC MANUAL

The heavily manual processes of the older system have been streamlined to a single process. Under the project, the Crash database has been migrated to a new setting based on Oracle Corp.'s technology and Sybase Inc.'s PowerBuilder environment. The project involved representatives from the Michigan Department of Transportation (MDOT), the Michigan State Police and the Michigan Department of State - the principal users of the Crash database. However, a recently completed multiagency project, called Crash Process Redesign, has changed much of that. And outdated data input methods often resulted in high error rates. Traffic accident data sometimes took two years to wend its way into the system, known as Crash. As a state that averages more than 450,000 traffic accidents annually, Michigan maintains a mountain of crash-related data.īut the 650,000 or so documents generated each year as a result of those accidents were maintained in an archaic 1970s-era mainframe, and it was hard for users to access the information for legal purposes or safety research, for example.

Michigan mdot traffic