Meal Breaks and Rest Pauses There will be a meal break and a rest pause for each shift or day where a minimum of eight hours are worked are worked Monday to Friday. The meal break shall be thirty minutes duration and will be unpaid. The rest pause will be twenty minutes duration and paid. An employee required to work overtime on a Saturday, Sunday or rostered day off shall be allowed a 20 minute paid crib break after each five hours worked if the work is scheduled to continue after the break. Payment for the crib break shall be at the prevailing overtime rate. A second meal break of 20 minutes shall be due if working 8 hours or more, and paid at the prevailing overtime rate. Subsequent paid meal breaks are due every 4 hours The times of taking the breaks will be as agreed between the employer and majority of employees affected.
The OCN, From XXX, and Invoice Number will control the invoice sequencing The From XXX will be used to identify to <<customer_name>> which BellSouth XXX is sending the message. BellSouth and <<customer_name>> will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> and resend the data as appropriate. THE DATA WILL BE PACKED USING ATIS EMI RECORDS.
Number Resources, Rate Center Areas and Routing Points 13.1 Nothing in this Agreement shall be construed to limit or otherwise adversely affect in any manner either Party’s right to employ or to request and be assigned any Central Office Codes (“NXX”) pursuant to the Central Office Code Assignment Guidelines and any relevant FCC or Commission orders, as may be amended from time to time, or to establish, by Tariff or otherwise, Rate Center Areas and Routing Points corresponding to such NXX codes.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Repayment of Amounts Advanced for Network Upgrades Upon the Commercial Operation Date, the Interconnection Customer shall be entitled to a repayment, equal to the total amount paid to the Participating TO for the cost of Network Upgrades. Such amount shall include any tax gross-up or other tax-related payments associated with Network Upgrades not refunded to the Interconnection Customer pursuant to Article 5.17.8 or otherwise, and shall be paid to the Interconnection Customer by the Participating TO on a dollar-for-dollar basis either through (1) direct payments made on a levelized basis over the five-year period commencing on the Commercial Operation Date; or (2) any alternative payment schedule that is mutually agreeable to the Interconnection Customer and Participating TO, provided that such amount is paid within five (5) years from the Commercial Operation Date. Notwithstanding the foregoing, if this LGIA terminates within five (5) years from the Commercial Operation Date, the Participating TO’s obligation to pay refunds to the Interconnection Customer shall cease as of the date of termination. Any repayment shall include interest calculated in accordance with the methodology set forth in FERC’s regulations at 18 C.F.R. §35.19a(a)(2)(iii) from the date of any payment for Network Upgrades through the date on which the Interconnection Customer receives a repayment of such payment. Interest shall continue to accrue on the repayment obligation so long as this LGIA is in effect. The Interconnection Customer may assign such repayment rights to any person. If the Large Generating Facility fails to achieve commercial operation, but it or another Generating Facility is later constructed and makes use of the Network Upgrades, the Participating TO shall at that time reimburse Interconnection Customer for the amounts advanced for the Network Upgrades. Before any such reimbursement can occur, the Interconnection Customer, or the entity that ultimately constructs the Generating Facility, if different, is responsible for identifying the entity to which reimbursement must be made.
User IDs and Password Controls All users must be issued a unique user name for accessing DHCS PHI or PI. Username must be promptly disabled, deleted, or the password changed upon the transfer or termination of an employee with knowledge of the password, at maximum within 24 hours. Passwords are not to be shared. Passwords must be at least eight characters and must be a non-dictionary word. Passwords must not be stored in readable format on the computer. Passwords must be changed every 90 days, preferably every 60 days. Passwords must be changed if revealed or compromised. Passwords must be composed of characters from at least three of the following four groups from the standard keyboard: • Upper case letters (A-Z) • Lower case letters (a-z) • Arabic numerals (0-9) • Non-alphanumeric characters (punctuation symbols)
Variable Registry-‐Level Fee If the ICANN accredited registrars (accounting, in the aggregate, for payment of two-thirds of all registrar-level fees (or such portion of ICANN accredited registrars necessary to approve variable accreditation fees under the then-current registrar accreditation agreement), do not approve, pursuant to the terms of their registrar accreditation agreements with ICANN, the variable accreditation fees established by the ICANN Board of Directors for any ICANN fiscal year, upon delivery of notice from ICANN, Registry Operator shall pay to ICANN a variable registry-level fee, which shall be paid on a fiscal quarter basis, and shall accrue as of the beginning of the first fiscal quarter of such ICANN fiscal year (the “Variable Registry-Level Fee”). The fee will be calculated and invoiced by ICANN on a quarterly basis, and shall be paid by Registry Operator within sixty (60) calendar days with respect to the first quarter of such ICANN fiscal year and within twenty (20) calendar days with respect to each remaining quarter of such ICANN fiscal year, of receipt of the invoiced amount by ICANN. The Registry Operator may invoice and collect the Variable Registry-Level Fees from the registrars that are party to a registry-registrar agreement with Registry Operator (which agreement may specifically provide for the reimbursement of Variable Registry-Level Fees paid by Registry Operator pursuant to this Section 6.3); provided, that the fees shall be invoiced to all ICANN accredited registrars if invoiced to any. The Variable Registry-Level Fee, if collectible by ICANN, shall be an obligation of Registry Operator and shall be due and payable as provided in this Section 6.3 irrespective of Registry Operator’s ability to seek and obtain reimbursement of such fee from registrars. In the event ICANN later collects variable accreditation fees for which Registry Operator has paid ICANN a Variable Registry-Level Fee, ICANN shall reimburse the Registry Operator an appropriate amount of the Variable Registry-Level Fee, as reasonably determined by ICANN. If the ICANN accredited registrars (as a group) do approve, pursuant to the terms of their registrar accreditation agreements with ICANN, the variable accreditation fees established by the ICANN Board of Directors for a fiscal year, ICANN shall not be entitled to a Variable-Level Fee hereunder for such fiscal year, irrespective of whether the ICANN accredited registrars comply with their payment obligations to ICANN during such fiscal year. The amount of the Variable Registry-Level Fee will be specified for each registrar, and may include both a per-registrar component and a transactional component. The per‑registrar component of the Variable Registry-Level Fee shall be specified by ICANN in accordance with the budget adopted by the ICANN Board of Directors for each ICANN fiscal year. The transactional component of the Variable Registry-Level Fee shall be specified by ICANN in accordance with the budget adopted by the ICANN Board of Directors for each ICANN fiscal year but shall not exceed US$0.25 per domain name registration (including renewals associated with transfers from one ICANN accredited registrar to another) per year.
Second and Lower Tier Subcontractor If a Subcontractor at any tier does all or part of the changed Work with its employees, the Subcontractor's markup on the Subcontractor’s work with its employees shall be twenty-five percent of the first $50,000 of the cost, and twenty percent of the remaining cost, if any. The management markup of a Subcontractor's work by the Contractor and all intervening tiers of Subcontractors shall not exceed seven and one half percent for the Contractor and any Subcontractor, or a total of fifteen percent for the changes to the Work.
Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.
Erosion Control Structure Maintenance During the period of this contract, Purchaser shall provide maintenance of soil erosion control structures constructed by Purchaser until they become stabilized, but not for more than 1 year after their construction. Contracting Of- ficer may agree to perform such structure maintenance under B4.218, if requested by Purchaser, subject to agreement on rates. Purchaser shall not be responsible for repair of such structures damaged by other National Forest users whose activities are not a part of Pur- chaser’s Operations.
