State of Texas ITS Architecture and Deployment Plans Permian Basin Region
|
|
Prepared by:  |
March 24, 2005
Copyright © 2005 by Texas Department of Transportation. All rights reserved.
Table of Contents
Executive Summary
Project
Approach..................................................................................................... 1
Overview of the Permian Basin Region......................................................... 2
Permian Basin Region Stakeholders.............................................................. 4
Permian Basin Regional ITS Architecture.................................................. 5
Inventory and Needs in the
Region................................................................................. 5
Market Packages............................................................................................................. 7
Interconnects, Interfaces, and
Standards........................................................................ 7
Operational Concept and
Scenarios.............................................................................. 12
Agreements.................................................................................................................... 12
ITS Architecture Documentation.................................................................................. 13
Permian Basin Regional ITS Deployment Plan........................................ 14
Prioritized Market Packages......................................................................................... 14
ITS Project Recommendations for
the Permian Basin Region..................................... 16
Maintaining the Regional ITS Architecture and Deployment Plan 21
Memorandum of Understanding.................................................................... 22
List of Figures
Figure 1 Permian Basin
Regional ITS Architecture and Deployment Plan Development
Process................................................................................................................. 1
Figure 2 Permian Basin Region Map..................................................................................... 3
Figure 3 Permian Basin Regional System Interconnect Diagram............................................. 8
Figure 4 TxDOT Odessa District Surface Street Control
Customized Market Package............ 9
Figure 5 TxDOT Odessa District Traffic Signals Interfaces.................................................. 11
Figure 6 TxDOT Odessa District TMC to Other TxDOT District
TMCs Architecture Flows.. 12
List of Tables
Table 1 Permian Basin
Region: Summary of ITS Needs......................................................... 6
Table 2 Summary of Prioritized Market Packages for the
Permian Basin Region................... 15
Table 3 Recommended ITS Projects for the Permian Basin
Region....................................... 17
Project Approach
The Federal Highway Administration (FHWA) issued a final rule to implement Section 5206(e) of the Transportation Equity Act for the 21st Century (TEA-21) in January of 2001. This final rule requires that Intelligent Transportation System (ITS) projects funded through the Highway Trust Fund conform to the National ITS Architecture and applicable standards. FHWA has further established a deadline of April 2005 for regions to have an ITS architecture in place.
To meet these requirements and ensure future federal funding
eligibility for ITS, the Texas Department of Transportation (TxDOT) initiated
the development of regional ITS architectures and deployment plans throughout
the State of
TxDOTs process for developing the regional ITS architectures
and deployment plans followed a consensus-based approach to meeting the
requirements in the FHWA Final Rule and supporting guidelines. This process was
further tailored to meet the specific multi-agency needs of these regional
plans, and was structured around stakeholder input and involvement. The
addition of an ITS deployment plan provides a tangible road map for regional
ITS deployment and integration. Figure 1
shows the development process for each of the State of
Figure 1
Development Process
Overview of the Permian Basin Region
The Permian Basin Region is bordered by the TxDOT Lubbock District to the north, the TxDOT Laredo District to the south, the TxDOT San Angelo and Abilene Districts to the east, and the TxDOT El Paso District to the west. For the Permian Basin Regional ITS Architecture and Deployment Plan, the study area included all 12 counties that comprise the TxDOT Odessa District. Figure 2 illustrates the Regional boundaries.
The Permian Basin Region has an extensive transportation infrastructure. The primary roadway facilities include I-10, I-20, US 67, US 285, and US 385.
I-10 and I-20 are east-west divided interstate highways.
Their effective operation is critical to the movement of goods and people
through the State of
Figure 2
Involving a range of perspectives in the development of a regional ITS architecture and deployment plan, and obtaining consensus on the vision and recommendations are key components to the process. Stakeholders from throughout the Permian Basin Region participated in the development of the Permian Basin Regional ITS Architecture and Deployment Plan. Key participants included representatives from TxDOT, cities, public safety, transit agencies, and planning organizations. These stakeholders provided input and review at key steps in the development process, including a project kick-off meeting, architecture development and review workshops, a deployment plan workshop, and review of the final project documentation.
The following is a list of stakeholders in the Permian Basin Region who have participated in the project workshops or provided input to the study team as to the needs and issues that should be considered as part of the Permian Basin Regional ITS Architecture and Deployment Plan:
- City of
- City of
- City of
- City of
- City of
- EZ Rider;
- Midland-Odessa Regional Transportation Study (MORTS);
- Midland-Odessa Transportation
- Texas Department of Public Safety;
- TxDOT El Paso District
- TxDOT Odessa District;
- TxDOT Traffic Operations Division (Austin); and
- West Texas Opportunities, Inc. - Permian Basin Rural Transit District.
The process for developing the Regional ITS Architecture for the Permian Basin Region included several key steps:
- Preparing an inventory of planned and existing systems in the Region;
- Identifying needs in the Region that could be addressed by ITS deployment or integration;
- Customizing and prioritizing market packages to address the specific needs and services identified by stakeholders;
- Developing interconnects and interfaces for system elements to map out data flows and agency links;
- Preparing an operational concept to illustrate how the systems, components, and agencies will be integrated and function as a result of the architecture framework;
- Identifying high-level functional requirements;
- Identifying standards that could be applicable to the Permian Basin Region; and
- Outlining potential agreements that would be needed to facilitate information or resource sharing as a result of ITS implementation.
Inventory and Needs in the Region
The Permian Basin Regional ITS Architecture began with a project kick-off meeting in January 2004. At that meeting, stakeholders provided information about existing and planned ITS elements in the Region. A diverse range of needs were identified by stakeholders who attended. The inventory of planned and existing ITS infrastructure provided the basis for the architecture development. Needs that could be addressed by ITS technologies guided the selection of market packages, data flows, and integration requirements.
The needs identified by the Permian Basin Region stakeholders were categorized into functional areas and are shown in Table 1.
Table 1
|
Table 1
Information Management Needs (Data Archiving)
None Identified Maintenance and Construction Management Needs
|
A 2-Day ITS Architecture Workshop was held in
The next step in developing the Permian Basin Regional ITS Architecture was to identify the services that would be needed to address the stakeholder needs. In the National ITS Architecture, services are referred to as market packages. Market packages can include several stakeholders and elements that work together to provide a service in the Region. Examples of market packages from the National ITS Architecture include Network Surveillance, Traffic Information Dissemination, and Transit Vehicle Tracking. There are a total of 75 market packages identified in Version 4.0 of the National ITS Architecture.
At the 2-Day ITS Architecture Workshop, stakeholders selected the market packages that corresponded to the desired services and functions identified for the Region, and then customized these market packages. They included services and functions such as Network Surveillance, Traffic Information Dissemination, and Emergency Response as well as market packages to address coordination needs, including an Incident Management System and Regional Traffic Control and Coordination. Because market packages are groups of services and functions, they can be deployed incrementally and over time. Of the 75 market packages in the National ITS Architecture Version 4.0, stakeholders identified 38 as being applicable to the Permian Basin Region.
Interconnects, Interfaces, and Standards
Stakeholders also began the process of mapping existing and planned ITS elements in the Permian Basin Region to the subsystems in the National ITS Architecture. These elements included agencies, systems, and essentially all of the ITS components in the Region. Subsystems are the highest level building blocks of the physical architecture, and the National ITS Architecture groups them into four major classes: Centers, Roadside, Vehicles, and Travelers. This mapping resulted in an interconnect diagram for the Permian Basin Region that is shown in Figure 3. This architecture diagram, also referred to as the sausage diagram shows the relationship of existing, planned, and future systems in the Permian Basin Region.
Figure 3
The market packages in the National ITS Architecture were customized to reflect the unique systems, subsystems, and terminators in the Permian Basin Region. Each market package was shown graphically, with the market package name, Permian Basin Region specific element, and the unique agency and system identifiers within the subsystems and terminators.
Figure 4 is an example of an advanced traffic management system (ATMS) market package for Surface Street Control that has been customized for the Permian Basin Region. This market package shows the three subsystems, Traffic Management, Roadway and Information Service Provider, as well as the associated entities (TxDOT Odessa District Traffic Signals, TxDOT Odessa District Field Sensors, etc.) for the TxDOT Odessa District signal system. The solid data flow lines in this market package indicate existing information flows. Future information flows are indicated by the dashed lines. All of the Permian Basin Region market package diagrams are included in the Regional ITS Architecture report.
Figure
More detailed interfaces were developed which identified the connectivity between the systems and elements. Each element identified in the ITS architecture for the Permian Basin Region was mapped to the other elements that it must interface with. These interfaces were further defined by architecture data flows between individual elements that specify the information to be exchanged. The data flows include requests for information, alerts and messages, status requests, confirmations, and other information requirements.
While it is important to identify the various systems and stakeholders as part of a regional ITS, a primary purpose of the architecture is to identify the connectivity between transportation systems in the Permian Basin Region. There are 137 different elements identified as part of the Permian Basin Regional ITS Architecture. These elements include local and state traffic management/operations centers, transit vehicles, dispatch systems, emergency management agencies, and others essentially all of the existing and planned physical components that contribute to a Regional ITS. Interfaces have been identified for each element in the Permian Basin Regional ITS Architecture, and each element has been mapped to those other elements with which it must interface.
An example of one of the system interfaces is included as Figure 5. This graphic shows the TxDOT Odessa District Traffic Signals and the existing and planned interfaces with other elements throughout the Region. These interfaces are shown as existing, planned, or future. Interfaces defined as planned have funding identified, while future interfaces are desired by stakeholders but funding has not yet been identified.
Architecture flows between the subsystems and terminators define the specific information (data) that is exchanged between subsystems and terminators. Each architecture flow has one or more data flows that specify what information is exchanged and the direction of the exchange.
An example of the architecture flows between two elements is shown in Figure 6. In this interface, the flows between the TxDOT Odessa District TMC and Other TxDOT District TMCs show information that must go from the Odessa District TMC to other Texas TMCs, as well as information that the District TMC needs from the other TMCs. Similar to the interfaces, architecture flows also are defined as existing, planned, or future. Diagrams of all of the architecture flows between elements have been included on the project website.
With the required interfaces and interconnections identified, standards that could potentially be applied to the Permian Basin Region were identified. Standards are an important tool that will allow efficient implementation of the elements in the Permian Basin Regional ITS Architecture over time. They facilitate deployment of interoperable systems at local, regional, and national levels without impeding innovation as technology advances, vendors change, and as new approaches evolve.
Figure 6 TxDOT Odessa District TMC to Other TxDOT District TMCs Architecture Flows
Operational Concept and Scenarios
An operational concept for the Permian Basin Region was
developed as part of the architecture process to illustrate how systems,
components, and agencies will be integrated and function as a result of the
framework provided by the Regional ITS Architecture. For the Permian Basin Region, two concepts
were illustrated. The first describes how ITS technologies could be used to
manage a multi-vehicle crash on I-20 between
Interfaces and data flows among public and private entities in the Permian Basin Region will require agreements among agencies that establish parameters for sharing agency information to support traffic and incident management, provide traveler information, and perform other functions identified in the Regional ITS Architecture. Recommended projects will result in systems and interfaces that will require inter-agency agreements, both public and private, to facilitate the exchange of information.
Currently, there are no formal agreements in place in the Region. With the implementation of ITS technologies, integration of systems from one or more agencies, and the anticipated level of information exchange identified in the architecture, it is likely that formal agreements will be needed in the future.
The following is a list of potential agreements for the Permian Basin Region based on the interfaces identified in the Regional ITS Architecture and recommended ITS projects in the Deployment Plan:
- Data sharing and usage agreements among public agencies;
- Data sharing and usage agreements among public agencies and private media and information service providers;
- Shared video monitoring agreements between TxDOT and public safety agencies;
- Mutual aid agreements among public sector agencies, primarily fire, police, emergency services, DPS, and TxDOT; and
- Joint operations/shared control agreements
between TxDOT, the City of
It is important to note that as ITS services and systems are implemented in the Region, part of the planning and review process for those projects should include a review of potential agreements that would be needed for implementation or operations.
ITS Architecture Documentation
The Regional ITS Architecture for the Permian Basin Region is documented in a final report. Stakeholders were brought together to review the Regional ITS Architecture and provide feedback. The final architecture report was not prepared until after completion of the Permian Basin Regional ITS Deployment Plan to allow for modifications based on information and input received for the ITS Deployment Plan recommendations.
A website with all
of the Regional ITS Architectures also was maintained. The website allowed stakeholders to review
the architecture and provide comments directly to the project team through the
website. At the time this report was
published, the Permian Basin Regional ITS Architecture website was being hosted at www.consystec.com. The site can be accessed by selecting the
link to Texas Regional, and then the link to
Permian Basin Regional ITS Deployment Plan
Although development of an ITS deployment plan was not required by the FHWA Final Rule for the architecture, the Final Rule does request a sequence of projects required for implementation. Capitalizing on the momentum and interagency dialogue established during the development of the Permian Basin Regional ITS Architecture, TxDOT chose to expand on the project sequence requirement to develop a formal ITS deployment plan for the Region.
The Permian Basin Regional ITS Architecture provided the framework and prioritized the key functions and services desired by stakeholders in the Region. The Permian Basin Regional ITS Deployment Plan builds on the architecture by prioritizing market packages, outlining specific ITS project recommendations and strategies for the Region, and identifying deployment timeframes so that the recommended projects and strategies can be implemented over time. Agency responsibilities for implementing and operating the systems also are a key component of the Regional ITS Deployment Plan.
Market packages for the Permian Basin Region previously identified as part of the architecture were categorized into high, medium, and low priorities by stakeholders. The market package prioritization was a key factor in developing recommendations for ITS deployment and integration in the Permian Basin Region. These priorities identified the key needs and services that are desired in the Region, as well as the interfaces that need to be established to provide integrated functionality and establish communication between elements.
It is important to note that the high, medium, and low priorities were not directly related to anticipated deployment timeframes (such as 5, 10, or 20 year deployment horizon). For example, a market package can be a high priority, but because of funding or prerequisite project requirements, it might not be feasible for deployment for several years. Maturity and availability of technology was another factor for prioritizing the market packages. Because market packages often represent groups of technologies or services to deliver a particular functionality, certain components of the market package could be identified as a high priority or existing capability, while other components would have a lower priority. Other considerations included whether or not the market package was better suited for deployment and operations by the private sector rather than public agencies in the Region.
Table 2 shows the prioritization of the selected market packages for the Permian Basin Region. The majority of these market packages fall into the high priority category. This category also includes market packages (or portions of market packages) that are already deployed in the Permian Basin Region, such as surface street control and traffic information dissemination.
Table 2
Summary of Prioritized Market Packages for the
|
High Priority |
Medium Priority |
Low Priority |
|
§ Network Surveillance § Surface Street Control § Traffic Information Dissemination § Regional Traffic Control § Incident Management System § Emergency Response § Evacuation and Reentry Management § Road Weather Data Collection § Weather Information Processing and Distribution § Maintenance and Construction Activity Coordination § Transit Vehicle Tracking § Transit Fixed-Route Operations § Demand Response Transit Operations § Transit Traveler Information § HAZMAT Management § Broadcast Traveler Information § ITS Data Mart |
§ Freeway Control § Standard Railroad Grade Crossing § Advanced Railroad Grade Crossing § Railroad Operations Coordination § Emergency Vehicle Routing § Roadway Maintenance and Construction § Work Zone Management § Transit Passenger and Fare Management § Transit Security § Weigh-in-Motion § ITS Data Warehouse |
§ Probe Surveillance § Maintenance and Construction Vehicle Tracking § Maintenance and Construction Vehicle Maintenance § Roadway Automated Treatment § Winter Maintenance § Work Zone Safety Monitoring § Transit Maintenance § Multi-modal Coordination § Electronic Clearance § ISP-Based Route Guidance |
Each of the prioritized market packages was assessed from the perspective of deployment status (which components, if any, were already existing in the Region), as well as any planned projects or additional new projects needed to fully implement the market package in the Permian Basin Region. Each market package analysis included:
- A brief definition of the market package (modified from the National ITS Architecture definitions);
- Any infrastructure or components from that market package that is already existing in the Permian Basin Region;
- Agencies currently operating or maintaining systems that apply to that market package;
- Planned projects that will address some or all of the services that are contained in the market package; and
- Any additional needs to bring the market package to the desired level of deployment or functionality.
ITS
Project Recommendations for the
Using the needs, market package priorities, and any planned projects identified by the stakeholders during the architecture process, a list of recommended ITS projects for the Permian Basin Region was developed. These projects were refined and additions and deletions were made by the Regional stakeholders at the ITS Deployment Plan Workshop in July 2004.
Recommended ITS projects for the Permian Basin Region were categorized into short-, medium-, and long-term timeframes for programming in the 5, 10, and 20 year horizons. This was done based on current status if the project had previously been identified and planned by the Region, market package priority, and dependency on other project completions. The majority of the short term or 5-year recommendations serve as foundation projects to implement basic functionality, infrastructure, and interfaces, with the intent of continuing to build out those foundation projects over the 10 and 20 year timeframes. Most projects for the Permian Basin Region are infrastructure based; however, there are some recommendations that focus more on institutional practices and interconnectivity to enhance coordination and communications.
Each recommended project for the Permian Basin Region was included in a short-, medium-, or long-term table. These tables provided the name of the project, primary operating/implementing agency, a planning level estimate of probable cost, an indication of whether or not funding had been identified for that specific project, and an estimated project duration. Following each table, detailed descriptions of each project were developed, which also included associated market packages and any pre-requisite project requirements.
Table 3 summarizes the ITS projects recommended for the Permian Basin Region. This summary is divided into the major program areas and subdivided by timeframe. As can be seen from this summary, the majority of the project recommendations focus on the Travel and Traffic Management category which would implement surface street traffic management, traveler information, and inter-agency coordination elements.
Table 3 Recommended ITS Projects for
the
|
Project Time Frame |
Project Name |
Funding Identified |
|
Travel and Traffic Management |
||
|
Short Term Projects |
TxDOT Odessa TMC |
No |
|
TxDOT ATMS Implementation |
N/A |
|
|
|
N/A |
|
|
TxDOT DMS on I-20 |
No |
|
|
TxDOT DMS on I-10 |
No |
|
|
TxDOT CCTV Camera Deployment Phase 1 |
No |
|
|
Detour Planning |
No |
|
|
TxDOT Rest Area Kiosks |
No |
|
|
TxDOT Closed |
Yes |
|
|
City of |
No |
|
|
City of |
Pending Approval |
|
|
City of Midland Closed |
Pending Approval |
|
|
City of |
No |
|
|
City of |
No |
|
|
City of |
No |
|
|
Mid Term Projects |
TxDOT Additional DMS Implementation |
No |
|
TxDOT CCTV Camera Deployment Phase 2 |
No |
|
|
TxDOT Web Page Customization and Enhancement |
No |
|
|
TxDOT Closed |
No |
|
|
Regional Telecommunications Master Plan |
No |
|
|
City of |
No |
|
|
City of |
No |
|
|
City of |
No |
|
|
City of Midland Closed |
No |
|
|
City of |
No |
|
|
City of |
No |
|
Table 3 Recommended
ITS Projects for the
|
Project Time Frame |
Project Name |
Funding Identified |
|
Travel and Traffic Management (continued) |
||
|
Mid Term Projects |
City of |
No |
|
City of |
No |
|
|
Regional 511 Advanced Traveler Information System Server |
No |
|
|
Media Liaison and Coordination |
N/A |
|
|
Long Term Projects |
TxDOT Advance Railroad Warning System |
No |
|
City of |
No |
|
|
City of |
No |
|
|
City of |
No |
|
|
City of |
No |
|
|
ISP-Based Route Guidance |
No |
|
|
Emergency Management |
||
|
Short Term Projects |
TxDOT Emergency Vehicle Traffic Signal Preemption Expansion |
No |
|
Municipal Emergency Vehicle Signal Preemption Vehicle Equipment |
No |
|
|
City of |
No |
|
|
City of |
No |
|
|
City of |
No |
|
|
City of |
No |
|
|
City of |
No |
|
|
City of |
No |
|
|
Mid Term Projects |
Midland County EOC/TxDOT |
No |
|
|
No |
|
|
911 PSAP/TxDOT |
No |
|
|
Municipal Emergency Management AVL and MDTs |
No |
|
|
Long Term Projects |
Municipal Emergency Vehicle Traffic Signal Preemption Implementation |
No |
Table 3 Recommended
ITS Projects for the
|
Project Time Frame |
Project Name |
Funding Identified |
|
Maintenance and Construction Management |
||
|
Short Term Projects |
TxDOT RWIS Stations Phase 1 |
No |
|
TxDOT High Wind/Low Visibility Detection |
No |
|
|
TxDOT Flood Detection Stations and Low Water Crossing Warning Beacon Implementation Phase 1 |
No |
|
|
TxDOT HCRS Enhancements |
Yes |
|
|
City of |
No |
|
|
Mid Term Projects |
TxDOT RWIS Stations Phase 2 |
No |
|
TxDOT Additional Portable DMS |
No |
|
|
TxDOT Flood Detection Stations and Low Water Crossing Warning Beacon Implementation Phase 2 |
No |
|
|
TxDOT Weigh-in-Motion for Pavement Management |
No |
|
|
City of |
No |
|
|
Long Term Projects |
TxDOT Work Zone Safety Monitoring |
No |
|
TxDOT Maintenance Vehicle AVL |
No |
|
|
TxDOT Maintenance and Construction Vehicle Maintenance Tracking System |
No |
|
|
TxDOT Anti-Icing Equipment Implementation |
No |
|
|
City of |
No |
|
|
City of |
No |
|
|
Public Transportation Management |
||
|
Short Term Projects |
EZ Rider AVL and Security System |
No |
|
EZ Rider Electronic Fare Collection |
No |
|
|
EZ Rider Paratransit Web-based Scheduling and Travel Data |
No |
|
|
Permian Basin Rural Transit AVL and MDTs |
No |
|
|
|
No |
|
|
Permian Basin Rural Transit/EZ Rider Communications Connection |
No |
|
|
EZ Rider/City of |
No |
|
|
EZ Rider/City of |
No |
|
Table 3 Recommended
ITS Projects for the
|
Project Time Frame |
Project Name |
Funding Identified |
|
Public Transportation Management (continued) |
||
|
Mid Term Projects |
EZ Rider Bus Stop Annunciation |
No |
|
EZ Rider/TxDOT |
No |
|
|
EZ Rider/Midland TOC Communications Connection |
No |
|
|
EZ Rider/Odessa TOC Communications Connection |
No |
|
|
EZ Rider/DPS Communications Connection |
No |
|
|
EZ Rider Transit Information Kiosks at Transfer Stations |
No |
|
|
Permian Basin Rural Transit Electronic Fare Collection |
No |
|
|
Permian Basin Rural Transit Video Surveillance |
No |
|
|
Permian Basin Rural Transit/TxDOT |
No |
|
|
Long Term Projects |
|
No |
|
Permian Basin Rural Transit Vehicle Maintenance Tracking System |
No |
|
|
Archived Data |
||
|
Short Term Projects |
None identified at this time |
N/A |
|
Mid Term Projects |
|
No |
|
Long Term Projects |
None identified at this time |
N/A |
Maintaining the Regional ITS Architecture and
Deployment Plan
The Permian Basin Regional ITS Deployment Plan is a living document. The recommended projects and their timeframes for implementation reflect the needs of the Region at the time the plan was developed. It is expected that the needs of the Region will change as ITS deployments are put into place, population and travel patterns change, and as new technology is developed. In order for the ITS Deployment Plan to remain a useful document for Regional stakeholders, the plan must be updated over time.
TxDOT will serve as the lead agency for maintaining both the Permian Basin Regional ITS Architecture and the ITS Deployment Plan; however, these plans will continue to be driven by stakeholder consensus rather than a single stakeholder.
At the ITS Deployment Plan Meeting in July 2004, stakeholders recommended that a meeting be held on an annual basis to review the existing Regional ITS Deployment Plan to update project status and include any new projects. These updates will be documented and included in the next formal revision of the plans. It was also recommended that the group meet on a two year basis to review the Regional ITS Architecture. Any new market packages that have been added to the National Architecture should be reviewed to see if they are applicable to the Permian Basin Region. Data flows in existing market packages should be reviewed to determine if any planned/future flows have been implemented. The Deployment Plan will also be updated at that time to reflect projects that have been deployed, new projects that are necessary, and to reprioritize projects currently shown in the plan. Projects that are added to the ITS Deployment Plan should also be reviewed closely to determine if they fit into the ITS Architecture for the Permian Basin Region. If a new project does not fit into the ITS Architecture, then the ITS Architecture will need to be revised to include the necessary links and data flows for the project. Any changes to the geographic scope of the Region should be agreed upon by the stakeholders. The complete revision of the plan on a two year basis will correspond with the Transportation Improvement Plan update process, which also occurs on a two year basis.
Both the Permian Basin Regional ITS Architecture and the ITS Deployment Plan were developed with a consensus approach from the stakeholders. In order for these documents to continue to reflect the needs of the Region, changes in the documents will need to be driven by consensus of all of the stakeholders.
As a final step in the development of the Permian Basin
Regional ITS Architecture and Deployment Plan, a Memorandum of Understanding
(MOU) was prepared for the participating stakeholder agencies. The MOU was
developed for stakeholders to acknowledge their participation and approval of
the plan, and pledge their support in the implementation and operation of ITS
in the Permian Basin Region. Also
included in the MOU was a pledge to provide TxDOT with the
Those stakeholders that were asked to sign the MOU represented agencies that participated in the planning process. In most cases these agencies will have the greatest impact in the Region in terms of ITS deployments and system operations. Stakeholder agencies that were asked to sign the MOU for the Permian Basin Regional ITS Architecture and Deployment Plan included the following:
- City of
- City of
- City of
- City of
- City of
- EZ Rider;
- MORTS;
- MOTRAN;
- Texas Department of Public Safety;
- Texas Department of Transportation; and
- West Texas Opportunities, Inc.