§ 66-22 Business Requirements – Cooperation with the Commission.
RCNY § 66-22
(a)The Technology System Provider must make commercially reasonable efforts, as described in this section, to cooperate with the Commission, its designees and any contractor(s) of the Commission, including the Accessible Taxi Dispatcher as defined in section 35 RCNY § 51-03: (1) in the development and support of any application(s) developed by the Commission or the Commission's designees, where such applications are developed specifically for the purpose of interoperating with the Technology System (including but not limited to smartphone applications); and 35 RCNY § 66-22(a)Penalty: $5,000 and suspension until complianceAppearance REQUIRED (b) The Technology System Provider must provide a data connection for TLC's Accessible Dispatch Program. The data connection will, at a minimum, provide the following functionality in the manner specified by the Accessible Taxi Dispatcher: (1) Automatically indicate the log on/off status of the Vehicle to the contractor's systems; (2) Automatically switch to the appropriate log on/off status in response to the Driver's use of the contractor's system; (3) Driver must be within 0.35 of a mile in order to indicate that the vehicle is at the pickup location; (4) Notify the Driver of a Dispatch using the Technology System's driver interface in a manner that identifies such dispatch as coming from the Accessible Taxi Dispatcher; and (5) Transmit all Trip Data to the Accessible Taxi Dispatcher's system as it is collected. 35 RCNY § 66-22(b)Penalty: $5,000 and suspension until complianceAppearance REQUIRED (c) The Technology System Provider may only charge the Accessible Taxi Dispatcher for the costs of labor, equipment, data, data connections, or any other expense resulting from the data connection to the Accessible Dispatch Program. All expenses charged to the Accessible Taxi Dispatcher must be clearly documented. 35 RCNY § 66-22(c)Penalty: Suspension until complianceAppearance REQUIRED (Added City Record 5/17/2018, eff. 6/16/2018; amended City Record 8/19/2019, eff. 9/18/2019; amended City Record 2/2/2023, eff. 3/4/2023)
