Event Notification Interface Sample Clauses

Event Notification Interface. Certain classes of systems may provide the capability for the addition or removal of system devices while the system unit is powered on, such as inserting a Notebook unit into a Docking Station. System BIOS support is necessary for providing Event Notification accessible to system software so that when devices are added or removed the system software will comprehend the use or release of system resources by those devices. Event Notification can be implemented as either a polled method or as asynchronous events.
AutoNDA by SimpleDocs

Related to Event Notification Interface

  • Incident Notification Google will notify Customer promptly and without undue delay after becoming aware of a Data Incident, and promptly take reasonable steps to minimize harm and secure Customer Data.

  • Union Notification The Union shall be notified of all appointments, hirings, layoffs, transfers, recalls and terminations of employment.

  • Instruction; Etc The Underwriters, for and on behalf of each of the Investors, hereby irrevocably instruct the Escrow Agent, and the Escrow Agent agrees: (a) to enter into the Deposit Agreement, and, if applicable, in accordance with Section 5 of the Note Purchase Agreement, to enter into a Replacement Deposit Agreement with the Replacement Depositary; (b) to appoint the Paying Agent as provided in this Agreement; (c) upon receipt at any time and from time to time prior to the Termination Date (as defined below) of a certificate substantially in the form of Exhibit B hereto (a “Withdrawal Certificate”) executed by the Pass Through Trustee, together with an attached Notice of Purchase Withdrawal in substantially the form of Exhibit A to the Deposit Agreement duly completed by the Pass Through Trustee (the “Applicable Notice of Purchase Withdrawal” and the withdrawal to which it relates, a “Purchase Withdrawal”), immediately to execute the Applicable Notice of Purchase Withdrawal as Escrow Agent and transmit it to the Depositary by facsimile transmission in accordance with the Deposit Agreement; provided that, upon the request of the Pass Through Trustee after such transmission, the Escrow Agent shall cancel such Applicable Notice of Purchase Withdrawal; (d) upon receipt of a Withdrawal Certificate executed by the Pass Through Trustee, together with an attached Notice of Replacement Withdrawal (as such term is defined in the Deposit Agreement) in substantially the form of Exhibit C to the Deposit Agreement duly completed by the Pass Through Trustee, to:

  • Required Acceptance of Daily Load Deliveries and Notification If the State is harmed by purchaser’s refusal to accept up to 10 truck deliveries of any one sort per day, Purchaser will be in breach of contract and subject to damages as per the D-026.2 and D-027.2 clauses. A truck delivery is all the wood delivered including sorts on super trucks, mule trains and pups brought to the delivery point by a single truck. The Purchaser shall notify the Contract Administrator at least 48 hours in advance if: 1. Purchaser intends to limit the number of truck deliveries accepted on any day to less than that listed above, or 2. Purchaser intends to limit the number of truck deliveries accepted on any day to the number listed above.

  • Recall Notification Notice of recall shall be sent to the bargaining unit member by certified mail. The City shall be deemed to have fulfilled its obligation by mailing the recall notice by certified mail, return receipt requested, to the last address provided by the bargaining unit member.

  • Implementation Report Within 150 days after the Effective Date, Ensign Group shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include: 1. the name, address, phone number, and position description of the Compliance Officer required by Section III.A, and a summary of other noncompliance job responsibilities the Compliance Officer may have; 2. the names and positions of the members of the Compliance Committee required by Section III.A; 3. the names and positions of the members of the Board of Directors who are responsible for satisfying the Board of Directors compliance obligations described in Section III.A.3; 4. a copy of Ensign Group’s Code of Conduct required by Section III.B.1; 5. the number of individuals required to complete the Code of Conduct certification required by Section III.B.1, the percentage of individuals who have completed such certification, and an explanation of any exceptions (the documentation supporting this information shall be available to OIG upon request); 6. a summary of all Policies and Procedures required by Section III.B (copies of the Policies and Procedures shall be made available to OIG upon request); 7. the following information regarding each type of training required by Section III.C: a. a description of such training, including a summary of the topics covered, the length of sessions, and a schedule of training sessions; b. the number of individuals required to be trained, percentage of individuals actually trained, and an explanation of any exceptions. A copy of all training materials and the documentation supporting this information shall be made available to OIG upon request. 8. a description of the Disclosure Program required by Section III.E; 9. the following information regarding the IRO(s): (a) identity, address, and phone number; (b) a copy of the engagement letter; (c) information to demonstrate that the IRO has the qualifications outlined in Appendix A to this CIA; (d) a summary and description of any and all current and prior engagements and agreements between Ensign Group and the IRO; and (e) a certification from the IRO regarding its professional independence and objectivity with respect to Ensign Group; 10. a description of the process by which Ensign Group fulfills the requirements of Section III.F regarding Ineligible Persons; 11. a list of all of Ensign Group’s locations (including locations and mailing addresses); the corresponding name under which each location is doing business; the corresponding phone numbers and fax numbers; each location’s Medicare and state Medicaid program provider number and/or supplier number(s); and the name and address of each Medicare and state Medicaid program contractor to which Ensign Group currently submits claims; 12. a description of Ensign Group’s corporate structure, including identification of any parent and sister companies, subsidiaries, and their respective lines of business; and

  • Customer Notification By executing this Agreement, the Advisor acknowledges that as required by the Advisers Act the Sub-Advisor has supplied to the Advisor and the Trust copies of the Sub-Advisor’s Form ADV with all exhibits and attachments (including the Sub-Advisor’s statement of financial condition) and will promptly supply to the Advisor copies of all amendments or restatements of such document. Otherwise, the Advisor’s rights under federal law allow termination of this contract without penalty within five business days after entering into this contract. U.S. law also requires the Sub-Advisor to obtain, verify, and record information that identifies each person or entity that opens an account. The Sub-Advisor will ask for the Trust’s legal name, principal place of business address, and Taxpayer Identification or other identification number, and may ask for other identifying information.

  • Project Completion Report At the completion of construction and once a Project is placed in service, the Subrecipient must submit a Project Completion Report that includes the total number of units built and leased, affordable units built and leased, DR-MHP units built and leased, an accomplishment narrative, and the tenants names, demographics and income for each DR-MHP unit.

  • 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.

  • REPORTING - NOTIFICATION A. Quarterly Reports In addition to any reports required pursuant to §19 or pursuant to any exhibit, for any contract having a term longer than 3 months, Local Agency shall submit, on a quarterly basis, a written report specifying progress made for each specified performance measure and standard in this Agreement. Such progress report shall be in accordance with the procedures developed and prescribed by the State. Progress reports shall be submitted to the State not later than five (5) Business Days following the end of each calendar quarter or at such time as otherwise specified by the State.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!