Transportation Framework

Progress Report to Framework Management Group - 11/10/99

Current Activity:  

Develop a plan for the next phase of the Transportation Framework development.  An interest group of potential Trans Framework users and data providers is in the process of developing a project charter for the next phase.  The charter is nearing completion with a draft copy ready for review after the next meeting (November 30).

Progress to Date:

Vision (DRAFT):  

The Washington State Transportation Framework is a seamless set of data that are consistent, connected, and continuous between segments of the transportation framework and with other framework layers. The transportation framework represents the best data available and includes mechanisms to improve over time. Framework data is accessible to the general public at the least cost with the least restrictions.

Approach (DRAFT): 

1. The approach to developing the framework is to start with an initial consensus of what the framework will consists of as defined by this charter. The next step will build on the understandings documented in the charter to further identify partners, their business needs, technology available, and a data model. A pilot project will then be undertaken for a limited geographic area (i.e. a few counties) and limited data contents (i.e. roads, railroads, bridges, and culverts) to show what it takes to do a framework and whether we can do a framework. Throughout, institutional arrangements necessary to facilitate the framework will be identified and implemented.
2. A project team will be formed to be responsible for scope, objectives, and overall success of the pilot project. A technical team reporting to the project team will make recommendations to the project team.
3. The data model to be developed will be inclusive. That is, the model will be developed to meet the business needs that are identified to the greatest extent possible while avoiding analysis paralysis. If the pilot determines full scope data modeling is not practical, the scope may be limited to allow the project to move forward. Data population of the database during the pilot will be limited in geographic area and contents in order to test the data model and framework processes at a lower cost.
4. It is anticipated that development of the transportation framework will be an iterative process that will result in changes to the charter and to requirements as we learn.

Objectives (DRAFT): 

1. Identify and recruit partners to develop, maintain, and distribute the transportation framework and framework data that meets a set of business and analytical needs defined by the partners.
2. Develop a transportation framework data model and standards based on business and analytical needs for the data, technology available to implement the model, and the ability to provide and maintain the data over time.
3. Define and implement institutional arrangements to facilitate data collection and maintenance partnerships, and to make the data accessible at the least cost with the least restrictions on use.
4. Implement interactive platform independent software, database, and processes to support integration of data received from data providers, maintenance of data by data stewards, and data accessibility by partners and the general public.

Scope (DRAFT): 

The project scope identifies the boundaries of the transportation framework development efforts. The scope defines elements of the transportation framework that will be considered for inclusion in the framework. Topics include contents, extent (geographic area), resolution (scale), datum (horizontal and vertical), metadata, linear referencing, feature attributes, institutional arrangements, data integration (within the transportation theme and between the transportation theme and other framework themes), data quality, technology, software, and tools. It is anticipated scope will be different for requirement definition, pilot, initial implementation, and future capabilities.

Critical Success Factors (DRAFT): 

1. Establish broad participation.
2. Establish standards which enhance the will and ability of partners to collect and maintain the data.
3. Provide the data needed to meet business and analytical needs.  Data must be accurate, complete, described, up-to-date, and not too complicated to use.
4. Define a model that partners agree meets their needs.
5. Identify the right standards needed to meet business needs, and that facilitate integration of data from multiple sources.
6. Identify standards that recognize the capabilities of existing technology to support the standards.
7. Phase development to allow delivery of a product within the biennium. Expect on-going growth and improvement.

IRICC

The Interorganizational Resources Information Coordinating Council (IRICC) Transportation Strike Team  is continuing to meet.  At the last meeting (10/6), a progress report the Washington planning effort was made.  There is interest in what we are developing and we will continue to share progress with them.  Bill Bogue, EPA, has resigned as chair of the group due to budget restrictions on travel and work load.  The scheduled 11/17 meeting will go on, hosted by the Region Ecosystem Office (REO).

Funding

Supplemental budget request by WSDOT for 2000 session was dropped.  WSDOT policy on supplemental budget funding requests is that an unfunded/failed request indicates the item is not a priority for the Legislature.  The result is that we don't proceed with the item even if other funding can be found.  Given some of the needed funding exists and addition is likely to be available through partners, the decision was made to not risk moving the project forward.

Impact of  I-695.  Voters approved reduction of the Motor Vehicle Excise Tax on November 2.  Media reports of the impact of the loss of revenue to state and local government are widespread.  WSDOT is in the process of developing an interim management plan for operating under the reduced funding through the 2000 legislative session.  Until the plan is completed (12/10/99) the WSDOT funding for the Transportation and Cadastral Framework projects is in doubt.  Also, the Legislature have other priorities from WSDOT's so it may be end of session before we know for sure.  It is likely that the ability of local government partners to participate will also be reduced.  Creativity is going to be required!

Future Meetings:

November 30, 1:00 - 4:00, Transportation Building, Shaman Conference Room, Olympia.

January 4, 9:15-Noon, same location, if needed.

Contact:

George Spencer, (360) 709-5515, spenceg@wsdot.wa.gov