Mobile Data Terminal compatibility Sample Clauses

Mobile Data Terminal compatibility the vendor must provide in-vehicle software that is able to operate on a wide range of Android tablet models currently offered from standard consumer electronics suppliers. J1.1 Once the MDT unit is powered up, it will automatically display a driver log-on form screen requesting the driver’s identification number and the vehicle’s odometer reading J1.2 Drivers must be able to log-on to the MDT unit by entering their employee identification, and the vehicle’s odometer reading into the MDT unit J1.3 The MDT unit will validate the log-on information with the scheduling software J1.4 Upon successful logon, prior to the manifest being displayed, the MDT software shall display pre-trip inspection screen that shall be filled in by the vehicle operator after conducting their pre-trip inspection of the vehicle J1.5 Each vehicle must be assigned specific checklist types that contain sets of questions relative to the vehicle J1.6 If the checklist login question is answered incorrectly, the system will deny the login J1.7 The dispatcher must be able to view the check list information within the system for a given run J1.8 The system must be able to set required questions whereas the driver will not be allowed to log on to the vehicle if not answered correctly J2 MDT Communication J2.1 MDT and driver application must be capable of visual and audible alerts to indicate incoming messages J2.2 The system must have the ability to send overt emergency notifications J2.3 After the driver acknowledges an incoming message it should be displayed on the MDT unit J2.4 The MDT unit should also be capable of allowing the driver to respond to a message J2.5 The dispatcher must be able to send a question that requires a yes/no answer from the driver J2.6 The MDT unit should be capable of sending a message and notifying the driver of the success or failure of the transaction J2.7 The MDT should allow the driver to select from a list of canned messages to send to the dispatcher. The canned message list should be configurable. J2.6 The MDT unit should be capable of queuing messages in a buffer and repeatedly attempting to deliver them to the host application. Each message should be configured to attempt delivery indefinitely or to attempt delivery only for a fixed period of time after which the message will be discarded J3 Standard Paratransit Functionality J3.1 The system should provide the paratransit operator with the option of downloading an entire day’s manifest to the MDT or a rol...
AutoNDA by SimpleDocs

Related to Mobile Data Terminal compatibility

  • MOBILE DATA COMPUTERS 20 1. As part of the law enforcement services to be provided to CITY, COUNTY 21 has provided, or will provide, mobile data computers (hereinafter called 22 “MDCs”) that are or will be mounted in patrol vehicles and motorcycles, 23 designated by COUNTY for use within CITY limits.

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • CUSTOMER SERVICE ACCESS The Competitive Supplier agrees to provide, or cause to be provided, certain customer services to Participating Consumers. Such services shall be reasonably accessible to all Participating Consumers, shall be available during normal working hours, shall allow Participating Consumers to transact business they may have with the Competitive Supplier, and shall serve as a communications liaison among the Competitive Supplier, the Town, and the Local Distributor. A toll-free telephone number will be established by Competitive Supplier and be available for Participating Consumers to contact Competitive Supplier during normal business hours (9:00 A.M. - 5:00 P.M. Eastern Standard Time, Monday through Friday) to resolve concerns, answer questions and transact business with respect to the service received from Competitive Supplier. The Town will post program-related information on the Town’s website which will be available to Participating Consumers for general information, product and service information, and other purposes.

  • Customer Service Standards The Franchising Authority hereby adopts the customer service standards set forth in Part 76, §76.309 of the FCC’s rules and regulations, as amended. The Grantee shall comply in all respects with the customer service requirements established by the FCC.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • COMMERCIAL COMPUTER SOFTWARE If performance involves acquisition of existing computer software, the following Company Exhibit is incorporated by reference: CCS Commercial Computer Software License (Company – July 2010).

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!