Documents (other)

In January 1999 the Minnesota Department of Transportation (Mn/DOT) presented the results of the Twin Cities Metropolitan Commuter Rail Feasibility Study to the Minnesota Legislature. After hearing those results the legislature passed M.S. 174.80 to 1 74.90 which gave the Commissioner of Mn/DOT the authority to plan, design, construct, and operate commuter rail in the State of Minnesota. Further, the Commissioner was charged with the responsibility of developing a commuter rail system plan that would ensure that, if built, commuter rail would be part of an integrated transportation system that would interface with all other forms of transportation including Light Rail Transit (LRT), buses, park and ride, bicycles, and pedestrians. In developing the Commuter Rail System Plan Mn/DOT has built on the results from the Twin Cities Metropolitan Commuter Rail Feasibility Study and in particular the implementation strategy presented in the final report.

The purpose of this document is to show how Mn/DOT, guided by our strategic vision and directions, is delivering a sustainable transportation system through wise stewardship of financial resources, a commitment to critical products and services, a promise to meet customer needs, and an ability to address key issues, policies and initiatives with strong leadership and innovation.

This report goes over the performance of various departments within the Minnesota Department of Transportation during the year 1996.

Partnerships are not new to the Minnesota Department of Transportation (Mn/DOT). In fact, Mn/DOT's involvement with other agencies and jurisdictions goes back many years -- long before the term "partnership" became popular. Cooperation is really the only way that Mn/DOT is able to effectively and expediently conduct its business. This has been particularly true since the mid-1960s when public awareness, local approval and environmental protection became a way of life. Partnerships run the gamut from multi-million dollar, multi-agency, international activities to small handshake arrangements between local, state and county employees. What they have in common is a government that provides better value for the customer. This inventory is merely a snapshot of existing partnerships. It would be nearly impossible to list them all, so in some cases a single example represents dozens of similar partnerships across the state. In short, this inventory illustrates the leadership role Mn/DOT has played in forming partnerships in and beyond the transportation community.

This is the MnDOT Office of Railroads and Waterways Strategic Plan for 1992-1997.

This report goes over the trends in the ethanol fuel industry in 1985.

The objective is to develop a model that defines the objects necessary for describing locations and the relationships between these objects. Objects include real-world and theoretical "anchors" of Mn/DOT's standard location reference systems (e.g., geodetic monuments, Public Land Survey corners, routes, mileposts, stations), geometric and topological representations of the transportation network (e.g., digitized line strings, topological links, nodes), and typical abstract or aggregated views of the network (e.g., pavement management segments, snow plow routes). [Mn/DOT 1993b] Individual end users of systems which reference spatial locations each have their own "external" view of how to locate objects. Roadway inventory may use route/reference point, construction surveying may use alignment station/offset, cartographers may use coordinates, traffic forecasting may use link/node, and traffic accident reporting street addresses. At the other end of the spectrum, different automated systems may each use different "internal" representation schemes for storing information in the computer. A CAD system, like Mn/DOT's Intergraph system represents roads as vectors on a drawing layer. ARC/Info approximates them as arcs (actually chords) on a map coverage. ORACLE Highways represents roads as rows in relational tables. An object based graphic data system like ODS models roads as individual objects with data and behavior consistent with a particular end user's view of the road. The objective of this project is to develop a single, comprehensive, conceptual model of location information. This model fits between the various external and internal views (see Figure 1). As such, it must support all of the identified external views. The internal views can be thought of as individual vendors' interpretation of that part ( or all) of the conceptual model necessary to support their delivered functionality, internally represented in the manner which best supports, in their opinion, that functionality.

The purpose of this document is twofold; To inform transportation oriented readers about existing systems that have been developed in other state agencies that may be of interest to them, and to provide an awareness of the State Information Systems Project (SISP), and encourage everyone to make use of this valuable resource. This directory contains information on many of the systems currently inventoried on the SISP. They were selected somewhat subjectively based on possible interest to users, planners, and systems developers. They are sorted and indexed by system name within agency. A second index in the back is sorted by system name only. Description, sources, produced materials, contact and record number are shown exactly as they appear in the SISP system. The SISP can provide additional information about these and other systems of other state agencies. Subject indexes are available and other methods of selecting and sorting are possible. Information is available in printed form or on floppy disks. All state agencies are required by law to keep their data in the SISP current.

This document represents Mn/DOT's commitment and successes in, the area of automated systems. It will serve as a valuable resource for legislators, state agencies and others as well as for our own use. The continued success of this document depends on the quality of the information it contains. Therefore all of us who are related to these systems in any way should be concerned with the accuracy of the information about the systems we are familiar with. Please browse the document for, inaccuracies and omissions. Changes and suggestions should be reported in the. manner described in the Introduction. Also please take the time just to see what types of data processing projects currently exist in our department. We should take pride in these accomplishments. Thank you in advance for your usual effort and cooperation in making this a success.

This Document recognizes the achievements of the Seeds program and MnDOT's Office of Workforce Equity and Diversity (O/WED). It was created after the Seeds program was nationally recognized for excellent by the Public Employees Roundtable, the Washington Times, and USA.