Mail Count Data Report. The Employer shall provide the Union with the expanded mail count report as soon as possi- ble after the effective date of a mail count but no later than five pay periods after that date.
Mail Count Data Report Sample Clauses
Related to Mail Count Data Report
DATA REQUESTS Upon the written request of the District, the State Auditor’s Office, the Appraisal District, or the Comptroller during the term of this Agreement, the Applicant, the District or any other entity on behalf of the District shall provide the requesting party with all information reasonably necessary for the requesting party to determine whether the Applicant is in compliance with its rights, obligations or responsibilities, including, but not limited to, any employment obligations which may arise under this Agreement.
DATA REPORTING a) CONTRACTOR shall agree to provide all data related to student information and billing information with XXX. CONTRACTOR shall agree to provide all data related to any and all sections of this contract and requested by and in the format require by the LEA. CONTRACTOR shall provide the LEA with invoices, attendance reports and progress reports for LEA students enrolled in CONTRACTOR’s NPS/A. b) Using forms developed by the CDE or as otherwise mutually agreed upon by CONTRACTOR and XXX, CONTRACTOR shall provide LEA, on a monthly basis, a written report of all incidents in which a statutory offense is committed by any LEA student, regardless if it results in a disciplinary action of suspension or expulsion. This includes all statutory offenses as described in Education Code sections 48900 and 48915. CONTRACTOR shall also include, in this monthly report, incidents resulting in the use of a behavioral restraint and/or seclusion even if they were not a result of a violation of Education Code sections 48900 and 48915. c) The LEA shall provide the CONTRACTORS with approved forms and/or format for such data including but not limited to invoicing, attendance reports and progress reports. The LEA may approve use of CONTRACTORS-provided forms at their discretion.
Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)
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).
Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.
Electronic Visit Verification ("EVV A. To ensure: 1. the EVV system is used to verify the provision of services governed under 40 TAC, Chapter 68 or its successor; 2. only authorized people access the Contractor's EVV account; 3. all data elements required by HHSC or HHSC's designee are uploaded or entered and maintained in the EVV system completely, accurately, and prior to submitting the claim; 4. that each time services governed by 40 TAC Chapter 68 or its successor are delivered to an individual, the Contractor's staff uses an HHSC-approved EVV system; and 5. service delivery documentation is immediately available for review by HHSC when requested. B. Equipment provided to Contractor by HHSC, HHSC’s designee, or an HHSC-approved EVV vendor, must be returned in good condition when the equipment is no longer needed under this Contract. In the context of this agreement, “good condition” means Contractor must not place any marks or identifying information on the equipment and may not alter information on the equipment including logos and serial numbers. If the equipment is lost, stolen, marked, altered or damaged by Contractor, Contractor may be required to pay the replacement cost for each piece of equipment that is lost, stolen, marked or damaged. Replacement costs for lost, stolen, marked or damaged equipment may be assessed periodically. If Contractor recovers previously lost or stolen equipment for which Contractor paid the replacement cost in the prior 12 months, Contractor may return the equipment and be reimbursed for the replacement costs within 12 months of the date HHSC, HHSC’s designee or an HHSC-approved EVV vendor (as applicable) received payment in full from the Contractor. This is provided the equipment is returned in good condition as specified above. C. HHSC may perform EVV compliance oversight reviews to determine if Contractor has complied with EVV compliance requirements as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC EVV website or EVV Policy Handbook. D. If the Contractor determines an electronic record in the EVV system needs to be adjusted at any time, the Contractor will make the adjustment in the EVV system using the most appropriate EVV reason code number(s), EVV reason code description(s) and enter any required free text when completing visit maintenance in the EVV system, if applicable. E. Contractor must begin using an HHSC-approved EVV system prior to submitting an EVV relevant claim. F. All claims for services required to use EVV (EVV claims) must match to an accepted EVV visit transaction in the EVV Aggregator (the state’s centralized EVV database) prior to reimbursement of an EVV claim. Without a matching accepted EVV visit transaction, the claim will be denied. G. Contractor must submit all EVV related claims through the Texas Medicaid Claims Administrator, or as otherwise described in the EVV Policy posted on the HHSC EVV website or in the EVV Policy Handbook. H. Contractor must complete all required EVV training as outlined in the EVV Policy posted on the HHSC EVV website or EVV Policy Handbook: • Prior to using either an EVV vendor system or an EVV proprietary system and • Yearly thereafter. I. Contractor and, if applicable, the Contractor’s appointed EVV system administrator, must complete, sign and date the EVV Onboarding Form as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC website or EVV Policy Handbook.
Alerts via Text Message To stop Alerts via text message, text "STOP" to 99785 at anytime. Alerts sent to your primary email address will be unaffected by this action. To restore Alerts on your Mobile Device, just visit the Alerts tab in Online Banking and click the box next to your mobile number for the Alert(s) you would like to receive again. For help with SMS text alerts, text “HELP” to 99785. In case of questions, please contact Customer Care at 0-000-000-0000. Our participating carriers include (but are not limited to) AT&T® Wireless, T-Mobile®, U.S. Cellular®, Verizon Wireless.
Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
Usage for Voice Mail Message Service Rated Incollects (originated in BellSouth and from other companies) can also be on Optional Daily Usage File. Rated Incollects will be intermingled with BellSouth recorded rated and unrated usage. Rated Incollects will not be packed separately.
List of Operator’s Subprocessors [Box 26] [Box 27] [Box 28] [Box 29]
