We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Group Settings Sample Clauses

Group Settings. For the selected Group Level, the Bank assigns the parameters of the rights or permissions that are available to customers and the associated limits within them. For example, the transaction rights or permissions may include various component parts of the Services (e.g., Xxxx Payment, External Funds Transfer, Mobile Banking, mRDC, Text Banking, etc.). While the associated aggregate limits on those rights could pertain to numbers or dollar amounts, per day, per transaction, per month, etc. The types of Security Alerts available to Users can also be set at the Group level.
Group Settings. If you belong to several groups and have the full control authority, you can select a default group to scan and add contacts into the group. As the right side of picture, the user has the full control authority for two groups. The user can select one of them as a default group.

Related to Group Settings

  • Interconnection Service Interconnection Service allows the Interconnection Customer to connect the Large Generating Facility to the Participating TO’s Transmission System and be eligible to deliver the Large Generating Facility’s output using the available capacity of the CAISO Controlled Grid. To the extent the Interconnection Customer wants to receive Interconnection Service, the Participating TO shall construct facilities identified in Appendices A and C that the Participating TO is responsible to construct.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Onvoy’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • Network Interconnection Methods 3.1 The Interconnection provided herein may not be used solely for the purpose of originating a Party’s own interexchange traffic.

  • Shift Rotation Routine shift rotation is not an approach to staffing endorsed by the Employer. Except for emergency situations where it may be necessary to provide safe patient care, shift rotation will not be utilized without mutual consent. If such an occasion should ever occur, volunteers will be sought first. If no one volunteers, the Employer will rotate shifts on an inverse seniority basis until the staff vacancies are filled.

  • Fund/SERV Transactions If the parties choose to use the National Securities Clearing Corporation’s Mutual Fund Settlement, Entry and Registration Verification (“Fund/SERV”) or any other NSCC service, the following provisions shall apply: The Company and the Fund or its designee will each be bound by the rules of the National Securities Clearing Corporation (“NSCC”) and the terms of any NSCC agreement filed by it or its designee with the NSCC. Without limiting the generality of the following provisions of this section, the Company and the Fund or its designee will each perform any and all duties, functions, procedures and responsibilities assigned to it and as otherwise established by the NSCC applicable to Fund/SERV, the Mutual Fund Profile Service, the Networking Matrix Level utilized and any other relevant NSCC service or system (collectively, the “NSCC Systems”). Any information transmitted through the NSCC Systems by any party or its designee to the other or its designee and pursuant to this Agreement will be accurate, complete, and in the format prescribed by the NSCC. Each party or its designee will adopt, implement and maintain procedures reasonably designed to ensure the accuracy of all transmissions through the NSCC Systems and to limit the access to, and the inputting of data into, the NSCC Systems to persons specifically authorized by such party. On each day on which the New York Stock Exchange is open for trading and on which the Fund calculates its net asset value pursuant to the rules of the SEC (“Business Day”), the Company shall aggregate and calculate the net purchase and redemption orders for each Account received by the Company by the close of the New York Stock Exchange (generally, 4:00 p.m. Eastern Time) (the “Close of Trading”) on the Business Day. The Company shall communicate to the Fund or its designee for that Business Day, by Fund/SERV, the net aggregate purchase or redemption orders (if any) for each Account received by the Close of Trading on such Business Day (the “Trade Date”) no later than 7:00 a.m. Eastern Time (or such other time as may be agreed by the parties from time to time) (the “Fund/SERV Transactions Deadline”) on the Business Day following the Trade Date. All such aggregated orders communicated to the Fund or its designee by the Fund/SERV Transactions Deadline on the Business Day following the Trade Date shall be treated by the Fund or its designee as if received prior to the Close of Trading on the Trade Date. All orders received by the Company after the Close of Trading on a Business Day shall not be aggregated with Orders received by the Company prior to the Close of Trading on such Business Day and shall be communicated to BRIL or its designee as part of an aggregated order no sooner than after the FUND/SERV Transactions Deadline or such other time as may be agreed by the parties from time to time) the following Business Day. Cash settlement shall be transmitted pursuant to the normal NSCC settlement process. In the case of delayed settlement, the Fund or its designee shall make arrangements for the settlement of redemptions by wire no later than the time permitted for settlement of redemption orders by the 1940 Act. Unless otherwise informed in writing, such redemption wires should be sent to an account specified by the Company and agreed to by Fund Parties.

  • Special Services Should the Trust have occasion to request the Adviser to perform services not herein contemplated or to request the Adviser to arrange for the services of others, the Adviser will act for the Trust on behalf of the Fund upon request to the best of its ability, with compensation for the Adviser's services to be agreed upon with respect to each such occasion as it arises.

  • Processing Transactions 2 2.1 Timely Pricing and Orders.................................... 2 2.2

  • Funding Arrangements Minimum amounts/increments for Japan Local Currency Borrowings, repayments and prepayments: Same as Credit Agreement.

  • Loop Makeup Response Time - Electronic Exclusions Business Rules

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ymax, Ymax, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ymax, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Ymax shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Ymax shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Ymax anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Ymax and Verizon. Ymax’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx- Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and Xxxx shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Ymax shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Ymax shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Ymax shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Ymax has not notified Verizon that it has corrected such blocking, Verizon may submit to Ymax a Trunk Group Service Request directing Ymax to remedy the blocking. Upon receipt of a Trunk Group Service Request, Ymax will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Ymax will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Ymax will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Ymax fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or bill (and Ymax shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Ymax’s network, Verizon’s performance in connection with these Two- Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Ymax will route its traffic to Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Ymax to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Ymax and the Verizon End Office.