Upromise Restaurants Category Integration Sample Clauses

Upromise Restaurants Category Integration. Upromise intends to expand the Upromise Restaurants Category to include additional dining programs and/or restaurants not participating in the Upromise Dining Program by RN. In order to facilitate an integrated Restaurants Category, RN will allow Upromise to host features or functionality for the Upromise Dining Program by RN in a manner approved by RN, such approval not to be unreasonably withheld so that such features and functionality may be integrated into the Upromise Restaurant Category generally, and RN will provide the necessary data and information for such integration.
AutoNDA by SimpleDocs

Related to Upromise Restaurants Category Integration

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where EveryCall has requested an Unbundled Loop and BellSouth uses Integrated Digital Loop Carrier (IDLC) systems to provide the local service to the end user and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to EveryCall. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for EveryCall (e.g. hairpinning):

  • Supplier Diversity Seller shall comply with Xxxxx’s Supplier Diversity Program in accordance with Appendix V.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Training Program It is agreed that there shall be an Apprenticeship Training Program, the provisions of which are set forth in Exhibit "C", which is attached hereto and forms part of this Agreement.

  • Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing iNetworks traffic to Verizon, the subtending arrangements between Verizon Tandems and Verizon End Offices shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to iNetworks, the subtending arrangements between iNetworks Tandems and iNetworks End Offices shall be the same as the Tandem/End Office subtending arrangements that iNetworks maintains for the routing of its own or other carriers’ traffic.

  • Changes in Equipment, Systems, Etc USBFS reserves the right to make changes from time to time, as it deems advisable, relating to its systems, programs, rules, operating schedules and equipment, so long as such changes do not adversely affect the services provided to the Trust under this Agreement.

Time is Money Join Law Insider Premium to draft better contracts faster.