Component Description. Human Resources § The Parties shall jointly formulate and implement a communication plan associated with any human resources aspects of the Integration Plan including the transfer of certain Persons from employees of Company to employees of Servicer as contemplated by this transaction. Transition Risk Mitigation § The Parties shall jointly identify and develop a mitigation plan for major risks associated with the Integration Plan (systems, data feeds, training, testing periods, etc.) Customer Impact Analysis and Communication Plan § The Parties shall jointly identify major implications for Cardholders and how the Integration Plan will mitigate risk to customers and Cardholders (e.g., any POS impact, etc.) § The Parties shall jointly develop a comprehensive Cardholder communication plan (notifications, documentation, etc.) § The Servicer shall have prepared, and the Parties shall have approved in accordance with the Agreement, all Cardholder communications to be used commencing on or prior to the Conversion Date, as applicable. Store Impact Analysis and Communication Plan § The Parties shall jointly identify major implications for Company stores and how the Integration Plan will mitigate risk to the stores (e.g., any POS impact, etc.) § The Parties shall jointly develop a comprehensive communication plan for store associates (documentation, training, etc.) Physical Premises § The Servicer and Company respectively shall, subject to and consistent with the terms of the Sublease, complete site improvements, and technology updates to transition the Leased Premises into a Servicer customer service center site Key Program Systems (Instant Credit Originations, Sale Authorization, Daily Settlement, System Conversion) § (****). § Each Party shall have taken the actions required of it and necessary for completion of the Conversion in compliance with the requirements of Section 2.03 of the Agreement such that the other Party shall be reasonably confident that the Conversion shall be capable of being timely implemented in accordance with such Section, in each case without undue disruption to the Parties’ operations. § Each Party shall have given the other Party the opportunity to conduct such testing of the granting Party’s systems and procedures in relation to the Program as such other Party shall have reasonably requested. § (****). § The Parties shall have developed secure data protocols and a disaster recovery plan. Information § The Servicer shall have taken such ...
Component Description. The Broadcast Information Provider is a privately owned component that collects travel-related information from the public sector and private information sources, and broadcasts that information to its customers via a variety of user interface equipment (e.g.; radio, television). Examples of the Broadcast Information Provider component include: AM/FM Radio Stations (KTSP) Television Stations (WCCO) Metro Traffic Cable Companies Paging Companies This component may support multiple Minnesota ITS services. The following list summarizes the Minnesota ITS service functions that are supported by this component.
Component Description. The Decentralized Control Signal Center is a public controlled component that is used to manage Decentralized Roadside Equipment components and communicate traffic related data to other Traffic Management Centers. Decentralized roadside equipment components are connected to and operated by the Decentralized Control Signal Center. Decentralized Control Signal Center functional operation includes data collection and data sharing with other traffic management centers and is performed as negotiated between agencies. Decentralized Roadside Equipment is controlled and managed at the center, but the frequency of control is not a real-time operation.
Component Description. The Incident Dispatch Center(s) are public and private controlled components that are used to during incidents and emergencies. They provide the necessary resources required to resolve an incident. These centers communicate with various vehicle components which are utilized to assist in the resolution of incidents. Examples of the Incident Dispatch Center component include: Towing Medical Fire City/County/Transit Police HAZMAT Private Security Public Safety This component may support multiple Minnesota ITS services. The following list summarizes the Minnesota ITS service functions that are supported by this component.
Component Description. The Inter-Jurisdictional Traffic System is a public controlled component that is used to a) manage Centralized Roadside Equipment components and Freeway Roadside Equipment components, and b) distribute traffic related data to other Traffic Management Centers. Centralized roadside equipment components and freeway roadside components are connected to, and operated by, the Inter-Jurisdictional Traffic System. It may be located within a centralized or decentralized control signal center, the freeway traffic management center, a separate location, or distributed at multiple locations. Examples of the Inter-Jurisdictional Traffic System component include: Integrated Corridor Traffic Management System (ICTM) This component may support multiple Minnesota ITS services. The following list summarizes the Minnesota ITS service functions that are supported by this component.
Component Description. The Inter-Jurisdictional Transit System is a publicly controlled component that is used to manage passenger transfers and coordinate operations between transit systems that span transit agency jurisdictions. This component supports multiple Minnesota ITS services. The following list summarizes the Minnesota ITS service functions that are supported by this component.
Component Description. The Maintenance Dispatch Center(s) are public controlled components that are used for planned incidents (i.e.; road maintenance, snow plowing) and unplanned incidents (i.e., inoperable signal equipment). They provide plans and resources required to resolve an incident where traffic is involved. Also, they provide an incident detection service by using some of the equipment used for their normal operations. These centers communicate with various vehicle components and equipment components utilized in the resolution of incidents. Examples of the Maintenance Dispatch Center component include: Waters Edge (MnDOT Metro Region) Other Regional Maintenance Dispatch Centers This component may support multiple Minnesota ITS services. The following list summarizes the Minnesota ITS service functions that are supported by this component.
Component Description. The Maintenance Garage(s) are public and privately controlled components that are used for maintenance and repair of vehicles and equipment utilized to resolve incidents and emergencies. Maintenance notices are generated to notify agencies of required maintenance to vehicles and equipment and completion notices are generated to notify the agencies that the vehicles and equipment are ready to be re-assigned. Examples of the Maintenance Garage component include: State Patrol Maintenance Garage MnDOT Maintenance Garage This component may support multiple Minnesota ITS services. The following list summarizes the Minnesota ITS service functions that are supported by this component.
Component Description. The Mayday Service Provider is a private controlled component that is used to detect incidents and emergencies. It provides a fee paid service that receives incident data from clients, identifying incidents or emergencies that require some type of resource to resolve the problem. The Mayday Service Provider contacts the appropriate public or private agency to request a resource assignment such that the incident is resolved in a timely fashion. Examples of the Mayday Service Provider component include: Mayday Service Companies This component may support multiple Minnesota ITS services. The following list summarizes the Minnesota ITS service functions that are supported by this component.
Component Description. The Probe Vehicle(s) is a vehicle that measures and reports traffic flow conditions to roadside devices for relay to a traffic control center. A probe vehicle is used when real-time data is required for traffic flow analysis and there are no other methods of measurement. Examples of the Probe Vehicle component include: Personal Vehicles Buses This component may support multiple Minnesota ITS services. The following list summarizes the Minnesota ITS service functions that are supported by this component.
