Use Case Enablement Sample Clauses

Use Case Enablement. Message Content may be used in other Use Cases only if Participant enters into other UCEs that require Message Content from that Use Case.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Use Case Enablement. The Reserve Banks have identified certain FedDetect Anomaly Notification use cases. Selected use cases will be enabled on behalf of your institution. Once established, management of the use cases remains with your institution, and you can modify or delete use cases at any time through FedACH Information Services on FedLine Web or by submitting a new Part 6H Request Form. NOC Monitoring Notifies your ODFI when the same correction or change (NOC) is received more than once outside of the prescribed Nacha change timeframe, indicating that your Originator may not be making required updates.
Sample 1
Use Case Enablement. Message Content may be used in other Use Cases only if PO enters into other UCEs that require Message Content from that Use Case.
Sample 1

Related to Use Case Enablement

  • Use Cases Subscription Services are provided for Software only when used for its supported purpose (“Use Case”). The Use Case determines which Subscription is required and what fees are charged. If you use or deploy the Software in a manner contrary to a supported Use Case, you are responsible for purchasing the appropriate Subscription(s) to cover such usage. For example, if you are using a Red Hat Enterprise Linux Desktop Subscription as a server, you are obligated to purchase a Red Hat Enterprise Linux Server Subscription.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Supported Use Cases Subscription Services are provided for Red Hat Satellite Server, Red Hat Satellite Capsule and Red Hat Satellite Proxy Management Subscriptions only when used for their supported purposes (“Use Case”) in accordance with the terms of this Exhibit and Table 2 below.

  • 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.

  • Early Construction of Base Case Facilities Developer may request Connecting Transmission Owner to construct, and Connecting Transmission Owner shall construct, subject to a binding cost allocation agreement reached in accordance with Attachment S to the ISO OATT, including Section 25.8.7 thereof, using Reasonable Efforts to accommodate Developer’s In-Service Date, all or any portion of any System Upgrade Facilities or System Deliverability Upgrades required for Developer to be interconnected to the New York State Transmission System which are included in the Base Case of the Class Year Study for the Developer, and which also are required to be constructed for another Developer, but where such construction is not scheduled to be completed in time to achieve Developer’s In-Service Date.

  • ACCESS TO OPERATIONS SUPPORT SYSTEMS 2.1 BellSouth shall provide Cellutell Communications, Inc. access to operations support systems (“OSS”) functions for pre-ordering, ordering and provisioning, maintenance and repair, and billing. BellSouth shall provide access to the OSS through manual and/or electronic interfaces as described in this Attachment. It is the sole responsibility of Cellutell Communications, Inc. to obtain the technical Version R4Q01: 12/01/01 capability to access and utilize BellSouth’s OSS interfaces. Specifications for Cellutell Communications, Inc.’s access and use of BellSouth’s electronic interfaces are set forth at xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx and are incorporated herein by reference.

  • Operational Support Systems <<customer_name>> shall pay charges for Operational Support Systems (OSS) as set forth in this Agreement in Attachment 1 and/or in Attachments 2, 3 and 5, as applicable.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Interconnection Facilities Engineering Procurement and Construction Interconnection Facilities, Network Upgrades, and Distribution Upgrades shall be studied, designed, and constructed pursuant to Good Utility Practice. Such studies, design and construction shall be based on the assumed accuracy and completeness of all technical information received by the Participating TO and the CAISO from the Interconnection Customer associated with interconnecting the Large Generating Facility.

  • Operational Support Systems (OSS The terms, conditions and rates for OSS are as set forth in Section 2.13 of this Attachment.

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