Oklahoma Highway Safety Office

The Oklahoma Highway Safety Office (OHSO) is an agency of the State of Oklahoma responsible for promoting highway safety. The OHSO is responsible for developing an annual statewide Highway Safety Plan to decrease fatalities and injuries on Oklahoma roadways. The OHSO is a division of the Oklahoma Department of Public Safety.

Oklahoma Highway Safety Office
Agency overview
Formed1967
Headquarters3223 N. Lincoln
Oklahoma City, Oklahoma
Employees26 (part of DPS)
Annual budget$10.9 million (part of DPS)
Minister responsible
  • Chip Keating, Secretary of Safety and Security
Agency executive
  • Paul Harris, Director
Parent agencyOklahoma Department of Public Safety (DPS)
WebsiteOklahoma Highway Safety Office

The OHSO is supervised by the Oklahoma Secretary of Safety and Security, who is the Governor's Representative for Highway Safety, and under the direct administrative control of the Director of Highway Safety, who is a career civil servant of the State government. The current Highway Safety Representative is John Scully and the current Highway Safety Director is Paul Harris.

The Highway Safety Office was created in 1967 during the term of Governor Dewey F. Bartlett.

Leadership

The Highway Safety Office located within the Oklahoma Department of Public Safety. As such, the Office is under the supervision of the Secretary of Safety and Security, and the Commissioner of Public Safety.

Overview

The OHSO is funded through grants from the National Highway Traffic Safety Administration. Most programs and activities of the OHSO fall into the areas of traffic safety education, training, and enforcement enhancement.

Divisions

  • Governor's Representative for Highway Safety
    • Director of Highway Safety
      • Chief of Programs
      • Chief of Plans
      • Chief of Finances
        • Program Management Division
        • Communications/Marketing
        • Data Management Division
        • Financial Management Division

Communications/Marketing Efforts

A portion of the budget for the OHSO is set aside each federal fiscal year for public information and education campaigns.[1] These campaigns include the ENDUI Oklahoma program,[2] OkieMoto (motorcycle safety),[3] as well as support for various National Highway Traffic Safety Administration campaigns including, Click It or Ticket, Drive Sober or Get Pulled Over, and other campaigns.

All communications and marketing efforts are overseen by the Communications Manager for the OHSO. The Communications Manager is responsible for the research, planning, execution, and reporting of each campaign. The Communications Manager works closely with the OHSO's marketing services vendor. The marketing services vendor for the OHSO for FFY20 is VI Marketing and Branding, based in Oklahoma City.

Local Outreach

The OHSO issues many grants each federal fiscal year to local and state-wide agencies and organizations in Oklahoma. A large part of the overall local outreach plan for the OHSO is a grant with the Oklahoma County Sheriff's Office (OCSO).[4] The OCSO has two full-time deputy sheriff's assigned to work at the OHSO. These two Sergeants are responsible for setting up and executing public awareness events across Oklahoma each year. Tools and equipment used by the OCSO Highway Safety deputies include a rollover simulator, impaired driving simulators, distracted driving simulators, and other tools.

The OCSO Sergeants also participate in safety events across Oklahoma, presenting safety information and operating their various simulators. Events include college football games, safety fairs, Cops N Kids events,[5] and other events.

Events

Each year, the OHSO plans and puts on several training events and conferences across the state. In 2019, the idea to combine all of these events into one large event was created. In February 2020, the OHSO hosted the first Oklahoma Traffic Safety Summit (Summit). The Summit combined the annual Oklahoma Drug Recognition Expert Conference, the Fatality Crash Reporting Conference, the annual Stakeholders Meeting, the Traffic Safety Forum, and other events.[6]

gollark: Well, that should be easier, I can just pregenerate... 0.1 second blocks of various frequencies, or something.
gollark: Ah, hmm.
gollark: Also, recognizing frequency would probably be irritating, I'd need a... Fourier transform, or something, or just some really hacky thing for recognizing *one* frequency.
gollark: I see. Well, if you write/find DFPWM to/from... raw signed ints, or something... conversion, I'll look at implementing that.
gollark: Waaaait, wouldn't I need to implement a DFPWM encoder/decoder somehow?

See also

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.