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. 3.1. Sensors external to the controller
Component Description. TECHNOLOGICAL CHARACTERISTICS AND COMPONENT SPECIFICATIONS
Component Description. The Account Management Provider is a privately owned component that can provide invoicing and payment tracking services for private companies or public agencies. Examples of the Account Management Provider component include:
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 Centralized Control Signal Center is a public controlled component that is used to manage Centralized Roadside Equipment components and communicate traffic related data to other Traffic Management Centers. Centralized roadside equipment components are connected to and operated by the Centralized Control Signal Center. Centralized Control Signal Center functional operation includes data collection and data sharing with other traffic management centers and roadside equipment. This is achieved via dedicated communication lines that perform real time or near real time control and data collection on the individual devices. Examples of the Centralized Control Signal Center component include:
Component Description. The Centralized Roadside Equipment is a public controlled component that consists of signs, signals and surveillance equipment used for the control and management of traffic. Detecting and collecting data about traffic conditions is also performed by this component. Centralized Roadside Equipment is connected to and operated by Centralized Control Signal Centers or Inter-Jurisdictional Traffic Systems. Operation of Centralized Roadside Equipment is achieved via dedicated communication lines that perform real time or near real time control and data collection on the individual devices. Examples of the Centralized Roadside Equipment component include: Traffic Signals Loop Detectors Surveillance Cameras Local Intersection Controllers Signal Priority/Pre-emption Equipment Portable Workzone System Portable Traffic Management System Railroad Crossing Detectors Changeable Message Signs, Variable Message Signs 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 Centralized/Decentralized Roadside Equipment (Group) is a collection of individual roadside equipment components consisting of: Centralized Roadside Equipment Decentralized Roadside Equipment Each item associated within this group is individually described in this Component Specification.
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 Decentralized Roadside Equipment is a publicly controlled component that is used to manage traffic flow and provide appropriate information to the traveler. Detecting and collecting data about traffic conditions is also performed by this component. Decentralized Roadside Equipment is connected to and operated individually by Decentralized Control Signal Centers. Examples of the Decentralized Roadside Equipment component include: Traffic Signals Loop Detectors Surveillance Cameras Master Intersection Controller Local Intersection Controllers Signal Priority/Pre-emption Equipment Portable Workzone System Portable Traffic Management System Railroad Crossing Detectors Changeable Message Signs, Variable Message Signs This component supports multiple Minnesota ITS services. The following list summarizes the Minnesota ITS service functions that are supported by this component.
