Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.
BILLING PROCEDURE a. The Contractor shall submit, not more than semi-monthly, properly completed A-19 vouchers (the "voucher") to one of the following: The Department of Children, Youth, and Families Attn: Xxxxx Xxxx PO Box 40972 Olympia WA 98504-0972 Or, email a scan of an original, signed A-19 voucher directly to the DCYF Contract Manager at Xxxxx.xxxx@xxxx.xx.xxx
b. Payment to the Contractor for approved and completed work shall be made by warrant or Electronic Funds Transfer by DCYF and considered timely if made within 30 days of receipt of a properly completed voucher. Payment shall be sent to the address designated by the Contractor and set forth in this Contract.
c. Each voucher must clearly reference the DCYF Contract Number and the Contractor's Statewide Payee Registration number assigned by the Office of Financial Management (OFM).
d. Properly completed vouchers and attachments completed by the Contractor must contain the information described in Exhibit A under the Section titled "Compensation and Voucher Payment".
Protocol The attached Protocol shall be an integral part of this Agreement.
Billing Procedures The Supporting Party will xxxx the Protecting Party for actual costs incurred for Assistance by Hire. Reimbursements will be limited to the provisions of the Agreement and the applicable OP, regardless of whether or not it is authorized on the Resource Order or other documentation produced by the incident. Reimbursable costs may include transportation, salary, overtime, per diem and other approved expenses of Supporting agency personnel. Rates and conditions of use for the equipment and personnel are documented in the OP. Parties shall submit a xxxx within 90 days of the incident. Parties must use their own invoice form for billing under this Agreement to avoid any confusion with other services that may have been ordered under other agreements. Invoices must identify Supporting Party’s name, address, and Taxpayer Identification Number (Department only), fire name, order and request number, and xxxx number and amount. Invoice supporting documentation must include description of services performed, period of services performed, and any applicable cost share agreements. Supporting documentation will itemize details of billing, listing personnel, equipment, travel and per diem, aircraft, supplies and purchases as approved in the attached AOP. It will also include itemized deductions for maintenance and repair of equipment. Department invoices will include “Record of Activities” (FSLA-5) and U.S. Forest Service invoices will include transaction register. Invoices for services under this agreement must be sent to: Name: Xxxx Xxxxxx-Xxxxx, ECC Manager Address: 0000 Xxxxxxxxx Xxxxx Xxxx, Xxxxx, Xxx: Xxxxxxxxxx, XX 00000 Telephone: (000) 000-0000 FAX: (000) 000-0000 Email: xxxxxxxxxxxx@xx.xxx.xx Name: Spalding Community Service District Address: 000-000 Xxxxxxxx Xxx Xxxx, Xxxxx, Xxx: Xxxxxxxxxx, XX 00000 Telephone: (000) 000-0000 FAX: (000) 000-0000 Email: xxxxxxxxxxxxx@xxxxxxx.xxx All bills will have a payment due date 30 days upon receipt. Contested Xxxxxxxx: Written notice that a xxxx is contested will be mailed to the Party within 30 days of receipt of the invoice and will fully explain the contested items. Contested items should be resolved no later than 60 days following receipt of the written notice. Parties are responsible for facilitating resolution of contested xxxxxxxx. Billing requirements and rates are documented in the attached OP.
Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.
Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.50 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0150. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. The sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Master Contract Sales Report. Upon request, Contractor shall provide to Enterprise Services a detailed annual Master Contract sales report. Such report shall include, at a minimum: Product description, part number or other Product identifier, per unit quantities sold, and Master Contract price. This report must be provided in an electronic format that can be read by compatible with MS Excel. Small Business Inclusion. Upon Request by Enterprise Services, Contractor shall provide, within thirty (30) days, an Affidavit of Amounts Paid. Such Affidavit of Amounts Paid either shall state, if applicable, that Contractor still maintains its MWBE certification or state that its subcontractor(s) still maintain(s) its/their MWBE certification(s) and specify the amounts paid to each certified MWBE subcontractor under this Master Contract. Contractor shall maintain records supporting the Affidavit of Amounts Paid in accordance with this Master Contract’s records retention requirements.
Billing Unless otherwise provided in the Grant Agreement, Grantee shall bill the System Agency in accordance with the Grant Agreement. Unless otherwise specified in the Grant Agreement, Grantee shall submit requests for reimbursement or payment monthly by the last business day of the month following the month in which expenses were incurred or services provided. Grantee shall maintain all documentation that substantiates invoices and make the documentation available to the System Agency upon request.
Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.
Contract Database Metadata Elements Title: Great Neck Union Free School District and Great Neck Paraprofessionals Association (2011) Employer Name: Great Neck Union Free School District Union: Great Neck Paraprofessionals Association Local: Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 5132 Unit Size: Number of Pages: 28 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ ARTICLE# TITLE PAGE# Preamble 2 Article 1 Association Rights 2 Article 2 Board-Administration-Association Relationship and Procedures 4 Article 3 Exchange of Proposals 6 Article 4 Professionals Duties and Responsibilities of Paraprofessionals 7 Article 5 Work Assignments 8 Article 6 Annual Appointment 10 Article 7 Selection and Promotion 10 Article 8 Evaluations and Standards 11 Article 9 Procedures for Termination of Employment 11 Article 10 Conferences 12 Article 11 Human Resource File 12 Article 12 Professional Growth 13 Article 13 Sick Leave 14 Article 14 Personal Leave 16 Article 15 Other Leaves 17 Article 16 Grievance Procedures 18 Article 17 Legal Assistance 19 Article 18 Conformity to Law 19 Article 19 Health Insurance 20 Article 20 Retirement Plan 20 Article 21 Salary Schedule 21 Article 22 Seniority Policy 23 Article 23 Compensation for Financial Loss 24 Article 24 Duration of Agreement 25 Appendix A Determination of Negotiating Unit 25 Appendix B Payroll Deduction Authorization 26 Appendix C Bus Aides 26 Appendix D Salary Schedules 27
Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.
