Bookmark this page

Work Plan & Schedule

The key activities of the project are as follows:

Step 1 – Coalition Building

In this task the project team will identify key stakeholders and define an outreach program.

Expected Completion: late January 2005

For strategic planning on a regional basis, all stakeholders, including the transportation agencies, decision makers, large employers as well as the public must buy-in to the ITS process, and work together as a coalition. They must be afforded the opportunity to provide input into the planning and system design process. Tasks in this step of the planning process will allow us to identify key stakeholders and define an appropriate outreach program.

Step 2 – Environmental Scan

The purpose of this task will be to contact the key stakeholders and engage them about ITS initiatives and goals. The input gathered will be used to define the direction of the ITS Strategic Plan.

Expected Completion: early March 2005

In this step, we will utilize the Coalition Building Plan developed under Step 1 to solicit the necessary information and develop an understanding of the current state of the regional transportation system from a multi-modal perspective. The perspective will include current issues, concerns and problem areas as well as projects, proposals, strategic plans and inter-governmental agreements pertinent to transportation within the Region of Durham.

By identifying problems as well as prioritized needs of the transportation network, we will establish a set of goals and measurable objectives for the Region’s ITS Strategic Plan. These goals and objectives will then help us define a clear and concise vision which in turn will help to shape the ITS Strategic Plan through consensus building.

Based on the vision for the ITS Strategic Plan and the specific needs of the Region of Durham, we will identify all applicable ITS user services and map them against each identified need, goal and objective. We will also identify both quantitative and qualitative performance criteria to objectively evaluate the effectiveness of individual user services.

Step 3 – Opportunities Analysis

The Opportunities Analysis will utilize the ITS Architecture for Canada to determine priorities throughout the Region of Durham and define the deployment program, recognizing funding opportunities.

Expected Completion: late April 2005

The purpose of this analysis is to review the user services and their relative priorities from an operational perspective to determine how the ITS Strategic Plan is to be deployed, operated and maintained in the short, medium and long terms. The analysis will take into consideration the constraints of the Region of Durham’s jurisdictions and related boundaries. We will develop an operations plan with recommendations on the mechanism necessary to operate the services, as well as the required institutional arrangement and the respective roles and responsibilities of each agency involved. The analysis will also address funding issues (identifying potential funding options / sources) and examine partnership opportunities to permit innovative joint arrangements for ITS deployment.

This analysis will help us to refine the User Service Plan and related priorities developed under Step 2.

Step 4 – Define ITS Program

The purpose of this task is to refine the priorities identified in the Opportunities Analysis phase and identify the various ITS components and elements for each initiative.

Expected Completion: late June 2005

In this step, we will define the functional areas required for the provision of each user service identified under the User Service Plan. Within each functional area, there is a set of ITS components and for each component there are various technologies that can be used to deliver the functionality required. We will then define the various ITS components associated with each of the functional areas and those that are common to each of the functional areas identified, focusing especially on enabling technologies that are common to several user services and compatible from a systems perspective.

Based on the identification of functional areas, ITS components and technologies, we will define the necessary sub-services (i.e., combinations of hardware, software and services) which become a building block in the implementation of a set of related functional requirements.

Step 5 – Develop the Architecture to Support the ITS Program

The ITS Architecture for Canada is used to develop the framework to guide the co-ordinated development of ITS programs. In this task, the functionality of each ITS component will be defined.

Expected Completion: late July 2005

The Canadian ITS Architecture provides a unified framework to guide the co-ordinated deployment of ITS programs within the public and private sectors. It offers a starting point from which stakeholders can work together to achieve compatibility among ITS elements to ensure unified ITS deployment for a given region. The Architecture describes interaction among physical components of the transportation systems including travellers, vehicles, roadside devices, and control centres. It also describes the information and communications system requirements, how data should be shared and used, and the standards required to facilitate information sharing. Overall, the Canadian ITS Architecture defines the functionality of ITS components and the information flows among ITS elements to achieve total system goals.

In this step, we will develop the physical architecture that will support the initiatives outlined in Step 4, and map the ITS program user service requirements to the ITS Architecture for Canada . This architecture (with its communications, transportation and institutional layers) will help to ensure interoperability between the stakeholder agencies as well as provincially and nationally.

Step 6 – Define Deployment Program

Based on the ITS components defined in the earlier tasks, we will define the projects identified in the short, medium and long terms. The phased approached will ensure budget concerns are recognized and that the existing systems infrastructure will be fully utilized.

Expected Completion: November 2005