Unacceptable Use I am aware that the school monitors the pupil’s activity on this device. I agree that my child will not carry out any activity that constitutes ‘unacceptable use’. This includes, but is not limited to the following: • Using ICT or the internet to bully or harass someone else, or to promote unlawful discrimination • Any illegal conduct, or statements which are deemed to be advocating illegal activity • Activity which defames or disparages the school, or risks bringing the school into disrepute • Causing intentional damage to ICT facilities or materials • Using inappropriate or offensive language I accept that the school will sanction the pupil, in line with our Behaviour Policy, if the pupil engages in any of the above at any time.
Floor Load Tenant shall not place a load upon any floor of the Premises that exceeds 50 pounds per square foot “live load”. Landlord reserves the right to reasonably designate the position of all Equipment which Tenant wishes to place within the Premises, and to place limitations on the weight thereof.
Purchase Order Duration Purchase orders issued pursuant to this State Term Contract must be received by the Contractor no later than close of business on the last day of the Contract’s term to be considered timely. The Contractor is obliged to fill those orders in accordance with the Contract’s terms and conditions. Purchase orders received by the Contractor after close of business on the last day of the State Term Contract’s term shall be considered void. Purchase orders for a one-time performance of contractual services shall be valid through the performance by the Contractor, and all terms and conditions of the State Term Contract shall apply to the single delivery/performance, and shall survive the termination of the Contract. Contractors are required to accept purchase orders specifying delivery schedules exceeding the contracted schedule even when such extended delivery will occur after expiration of the State Term Contract. For example, if a state term contract calls for delivery 30 days after receipt of order (ARO), and an order specifies delivery will occur both in excess of 30 days ARO and after expiration of the state term contract, the Contractor will accept the order. However, if the Contractor expressly and in writing notifies the ordering office within ten (10) calendar days of receipt of the purchase order that Contractor will not accept the extended delivery terms beyond the expiration of the state term contract, then the purchase order will either be amended in writing by the ordering entity within ten (10) calendar days of receipt of the contractor’s notice to reflect the state term contract delivery schedule, or it shall be considered withdrawn. The duration of purchase orders for recurring deliveries of commodities or performance of services shall not exceed the expiration of the State Term Contract by more than twelve months. However, if an extended pricing plan offered in the State Term Contract is selected by the Customer, the Contract terms on pricing plans shall govern the maximum duration of purchase orders reflecting such pricing plans. Timely purchase orders shall be valid through their specified term and performance by the Contractor, and all terms and conditions of the State Term Contract shall apply to the recurring delivery/performance as provided herein, and shall survive the termination of the Contract. Ordering offices shall not renew a purchase order issued pursuant to a State Term Contract if the underlying contract expires prior to the effective date of the renewal.
Interconnection Customer Drawings Within one hundred twenty (120) days after the date of Initial Operation, unless the Interconnection Parties agree on another mutually acceptable deadline, the Interconnection Customer shall deliver to the Transmission Provider and the Interconnected Transmission Owner final, “as-built” drawings, information and documents regarding the Customer Interconnection Facilities, including, as and to the extent applicable: a one-line diagram, a site plan showing the Customer Facility and the Customer Interconnection Facilities, plan and elevation drawings showing the layout of the Customer Interconnection Facilities, a relay functional diagram, relaying AC and DC schematic wiring diagrams and relay settings for all facilities associated with the Interconnection Customer's step-up transformers, the facilities connecting the Customer Facility to the step-up transformers and the Customer Interconnection Facilities, and the impedances (determined by factory tests) for the associated step-up transformers and the Customer Facility. As applicable, the Interconnection Customer shall provide Transmission Provider and the Interconnected Transmission Owner specifications for the excitation system, automatic voltage regulator, Customer Facility control and protection settings, transformer tap settings, and communications.
ODUF Pack Rejection 6.4.1 Image Access will notify BellSouth within one (1) business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI error codes will be used. Image Access will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to Image Access by BellSouth.
Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks.
6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order.
6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall xxxx the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information.
6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall xxxx the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic.
6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor
Pack Rejection 6.4.1 <<customer_name>> will notify BellSouth within one business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. <<customer_name>> will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to <<customer_name>> by BellSouth.
Order Acceptance Xxxxxxx’x acceptance of the Order and consequent agreement to the Contract by either: (a) delivering the Goods, Services, or Digital Services; or
Purchase Order Number NETAPP's purchase order number must appear on all invoices, packing lists and bills of lading and shall appear on each package, container or envelope on each shipment made pursuant to such purchase order.
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 Xxxxx’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.
