Context Sensitive Solutions

A new approach to transportation planning
Context Sensitive Solutions (CSS) is an effective approach to planning and implementing transportation projects that are sensitive to community values — without compromising functionality or safety and without adding cost. CSS incorporates community values with sound engineering practices, resulting in projects that enhance quality of life.

What are CSS principles?
CSS principles are rooted in the federal transportation funding bill. This 1991 landmark legislation made a commitment to preserving and protecting the environment and cultural values affected by transportation. In response, the United States Department of Transportation examined its policies and now emphasizes a balance between scenic, historic, aesthetic, and cultural values with safety and mobility. Here at home, the Michigan Department of Transportation (MDOT) has also developed a set of CSS principles and is committed to incorporating these principles into its own projects and assisting local agencies to do the same.

Why should we use CSS principles? 
It makes good planning sense to use CSS principles. Collaborative interaction with stakeholders helps establish the context — not just in physical engineering terms, but the social context aspect — in which the project will move forward to completion with fewer objections and obstacles from the community. The project will be better. Faster implementation and better results is smart planning.

CSS principles make a difference
CSS principles do make a difference. Just take a look in Southeast Michigan and it’s easy to see projects reflecting community values without compromising safety or mobility. A prime example is the I-94/US-24 interchange in the City of Taylor. If conventional planning methods were used, the existing interchange and bridges would have simply been rehabilitated. MDOT took a different approach and worked with the City of Taylor, Telegraph Tomorrow, and the Detroit Regional Gateway Advisory Group to address local concerns, including safety, noise, economic development, and aesthetics. The end result was a “single point urban” interchange. The new geometrics and design eliminated the left entrances and exits, met the underclearance requirements on US-24, reduced noise, made over 80 acres of land available for development, and crafted a unique, tied-arch bridge.

CSS and the National Environmental Policy Act (NEPA)
CSS and NEPA work well together. Their processes are almost identical, and they share the same aim — selecting the best alternative. Both programs provide an interdisciplinary framework for considering the impacts of transportation programs and projects on the natural, built, and human environment. CSS does differ from NEPA in that it requires a broader based collaboration among stakeholders and seeks to incorporate the public’s involvement from the very earliest states of project development; whereas NEPA relies more heavily on various agencies to conduct the early conversations.

What’s the first step in implementing CSS principles?
Before incorporating CSS principles into planning, learn more about the process. A good place to start is the FHWA Web site. Here in Michigan, MDOT’s interdepartmental team has publications and maintains a clearinghouse of CSS projects. Lynn Lynwood is a good contact and can be reached at lynwoodl@michigan.gov or 517-373-0026. 

Don’t overlook SEMCOG. SEMCOG is committed to incorporating CSS in transportation planning and is available to answer questions and provide assistance to local communities and agencies.