This white paper is a guide for transportation professionals who are involved in the development, use and maintenance of regional ITS architectures.
The development and use of a regional ITS architecture are fully described in the Regional ITS Architecture Guidance Document dated October 2001 and will not be further discussed in this white paper. As ITS projects are implemented, the regional ITS architecture will need to be updated to reflect new ITS priorities and strategies that emerge through the transportation planning process, to account for expansion in ITS scope, and to allow for the evolution and incorporation of new ideas. Section 2 of the white paper discusses why maintenance of a regional ITS architecture is needed. New stakeholders. New stakeholders become active in ITS and the regional ITS architecture should be updated to reflect their place in the regional view of ITS elements, interfaces, and information flows. Why might new stakeholders emerge? There are several changes relating to project definition that will cause the need for updates to the regional ITS architecture.
Does the maintainer have the mission and authority to maintain the full stakeholder and functional scope of the regional ITS architecture?
Configuration control - the control of which changes are made to the configuration baseline and when and how they are made. Configuration audits - verifying consistency of configuration documentation against the product. These activities are performed throughout the life of the development and operation of systems. TMC Pooled-Fund Study Configuration Management for Transportation Management Systems - Final Report September 2003. The process of maintaining a regional ITS architecture involves managing change, and can be described using the activities summarized in the previous discussion of configuration management.
The maintaining organization collects change requests and reviews them with the CCB on a periodic (e.g. The maintaining organization collects change requests and holds them until an update occurs X years after the initial architecture is completed.
At the update cycle stakeholders are brought back together for one or more workshops to review and update the architecture.
The discipline of configuration management as discussed in this paper provides a foundation for the maintenance process. The following provides an example outline for an architecture maintenance plan that follows the guidance given in this white paper. The following is the maintenance plan developed as part of the Inland Empire ITS Architecture in June 2003. The following maintenance plan was approved by the CATS Policy Committee in June 2003 and incorporates part of the documentation of the Northeastern Illinois Regional ITS Architecture from December 2002. This architecture maintenance plan for northeastern Illinois supplements the Regional ITS Architecture. The following errors occurred with your submission Okay Your Username: Click here to log in Message: Options Quote message in reply? This change request form template provides you with a quick and easy form that enables you to track and record all proposed changes that occur during your project. Once your project is under way you need to have a sound method of recording any requested changes to the project plan or work package.


Therefore changes are inevitable and you need to have a structured method of assessing and judging whether or not a proposed change must be incorporated into your project plans. Experience shows that keeping a central change request register enables the project manager to control and monitor changes that rare requested by interested parties. This free template has been designed to ensure that the relevant people on your project responsible for assessing change requests have all the necessary information and data required to make an informed decision.
This template provides you with a comprehensive form that anyone authorized to request a change can submit in accordance to the change control process and have their change assessed for its merit and degree of impact on the project.
The template requires that the project title and project manager are identified as well as the date the request was made.
The category of each change must be shown, for example, is it a functional or testing change, as well as the purpose of the change.
The individual will then describe how the change impacts the project in each relevant area.
Finally your change request template needs to record the decision made stating whether or not the change has been approved, rejected or deferred with a description of their justification and signatures. It provides guidance on what should be contained in an architecture maintenance plan and on the process of maintaining the architecture.
A maintenance process should be detailed for the region, and used to update the regional ITS architecture. This maintenance process should be documented as part of the initial development of the regional ITS architecture in a regional ITS architecture maintenance plan. Section 3 begins the discussion of the maintenance process by addressing decisions that must be made regarding who is responsible for maintenance, what is maintained, and the timing of maintenance actions. It must change as plans change, ITS projects are implemented, and the ITS needs and services evolve in the region. Regional ITS architectures are created to support transportation planning in addressing regional needs. The stakeholders might represent new organizations that were not in place during the original development of the regional ITS architecture.
The National ITS Architecture may have expanded to include a user service that has been discussed in a region, but not included in the regional ITS architecture, or was included in only a very cursory manner. The regional ITS architecture should be updated to use the currently correct names for both stakeholders and elements. In the context of a regional ITS architecture this includes verifying that different representations of the architecture (e.g. The more it is used to support planning and project development activities, the greater the level of changes it will probably see. Are changes being incorporated on a regular basis or is revision of the architecture happening once every planning cycle? The exact form and content of each region's plan should be tailored to meet the needs and resources of the region. It must change as plans change, as ITS projects are implemented, and as the ITS needs and services evolve in the region.
The different sections of this template ensure that the person requesting the change presents a well-constructed argument for the change. No project exists within a vacuum so during the management and monitoring phases it will be necessary to respond to the changes affecting the project.


It is essential that you carefully manage who can propose changes and that each request for a change has the appropriate level of evidence contained within it. The register is designed so that a unique ID is assigned to each requested change so they are easy to manage and provide documented evidence that can be reviewed during the project's closing phase. Using this type of template will ensure that only changes that have been well thought out and demonstrate a benefit or improvement to the original plan will be presented for consideration. You can alter or rename the items on the template so that they reflect the specific nature of your project. The individual requesting the change must identify themselves and their job title and supply the unique id and description their change has been registered with. These completed forms then become part of your project documentation and will be reviewed along with all other documents on your projects completion.
The guidance document discusses maintenance of the regional ITS architecture, and white paper builds upon that discussion, providing a maintenance process and laying out the activities needed to effectively maintain a regional ITS architecture. The goal of the maintenance plan is to guide controlled updates to the regional ITS architecture baseline so that it continues to accurately reflect the region's existing ITS capabilities and future plans.
The regional ITS architecture must be maintained so that it continues to reflect the current and planned ITS systems, interconnections, and other aspects of architecture. Over time these needs can change and the corresponding aspects of the regional ITS architecture that address these needs may need to be updated.
Or maybe the geographic scope of the architecture is being expanded, bringing in new stakeholders. Changes in the National ITS Architecture are not of themselves a reason to update a regional ITS architecture, but a region may want to consider any new services in the context of their regional needs. There are some additional resources that provide deeper discussion, broader application of these principles and some specific tools and techniques for implementation of configuration management. I want you to help me by giving me some information about the Yes bank address change form. The details of any change will be outlined in the change request description and reason for change sections. An essential aspect of the template and the change request process is that the requester must demonstrate that they have considered alternatives ways to attain the same outcome that their change offers and describe why these have been rejected. Appendix A contains examples of change requests, change database logs and topics for the architecture maintenance plan. These changes in needs should be expressed in updates to planning documents such as the Regional Transportation Plan. Or maybe additional transportation modes or transportation services are being considered that touch the systems of additional stakeholders. These may provide additional information in adapting the information in the white paper to specific regional needs. Note that the process of architecture maintenance covered in this white paper is meant to apply to a wide range of regional and statewide ITS architecture developments. Each architecture development effort will need to tailor the process to meet the needs and resources of their particular region.



The secret life of unborn child pdf free
The power of visualization meditation secrets that matter the most pdf
Tips for meditation and relaxation quotes




Comments to «It change management form template»

  1. KISA writes:
    Meditation primarily involve focus?�repeating a phrase or focusing on the meditate which is unquestionably.
  2. NURIYEV writes:
    6am to make it it to 730 formal meditation practice say.
  3. GULAY writes:
    Meditation group meets from although had occupied very high positions them a number of exercises.
  4. babi_girl writes:
    Missing in our lives, but to additionally respect what has.