Lobbying Activities - Standard Form - LLL No response Do not upload this form unless Vendor has reportable lobbying activities. There are Attributes entitled, “2 CFR Part 200 or Federal Provision - Xxxx Anti-Lobbying Amendment – Continued.” Properly respond to those Attributes and only upload this form if applicable/instructed. If upload is required based on your response to those Attributes, the Disclosure of Lobbying Activities – Standard Form - LLL must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, properly completed, and uploaded to this location.
Events Beyond Our Control If an Event Beyond Our Control occurs and prevents Us from performing any of Our obligations under this Contract to any extent, then We are not required to perform that obligation to the extent and for as long as We are prevented by that Event Beyond Our Control. If such an Event Beyond Our Control occurs and We consider it appropriate to do so, We may notify You of the Event Beyond Our Control by any reasonable means, including by a public announcement.
Co-Curricular Activities G. The enrollment of the student of employees who reside outside the District shall be subject to School Board Policy 3.02(3)f, Out-of-County Students.
Collocation Transfer of Responsibility Without Working Circuits The Collocation is not serving any End User Customers and does not have active service terminations (e.g., Interconnection trunks or UNE Loops) or 2) Collocation Transfer of Responsibility With Working Circuits – The Collocation has active service terminations, such as Interconnection trunks or is serving End User Customers.
Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: Field # Field Name Description 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES
Business Continuity Planning Supplier shall prepare and maintain at no additional cost to Buyer a Business Continuity Plan (“BCP”). Upon written request of Buyer, Supplier shall provide a copy of Supplier’s BCP. The BCP shall be designed to ensure that Supplier can continue to provide the goods and/or services in accordance with this Order in the event of a disaster or other BCP-triggering event (as such events are defined in the applicable BCP). Supplier’s BCP shall, at a minimum, provide for: (a) the retention and retrieval of data and files; (b) obtaining resources necessary for recovery, (c) appropriate continuity plans to maintain adequate levels of staffing required to provide the goods and services during a disruptive event; (d) procedures to activate an immediate, orderly response to emergency situations; (e) procedures to address potential disruptions to Supplier’s supply chain; (f) a defined escalation process for notification of Buyer, within two (2) business days, in the event of a BCP-triggering event; and (g) training for key Supplier Personnel who are responsible for monitoring and maintaining Supplier’s continuity plans and records. Supplier shall maintain the BCP and test it at least annually or whenever there are material changes in Supplier’s operations, risks or business practices. Upon Xxxxx’s written and reasonable request, Supplier shall provide Buyer an executive summary of test results and a report of corrective actions (including the timing for implementation) to be taken to remedy any deficiencies identified by such testing. Upon Xxxxx’s request and with reasonable advance notice and conducted in such a manner as not to unduly interfere with Supplier’s operations, Supplier shall give Buyer and its designated agents access to Supplier’s designated representative(s) with detailed functional knowledge of Supplier’s BCP and relevant subject matter.
CONTRACT SALES ACTIVITY REPORT Each calendar quarter, Vendor must provide a contract sales activity report (Report) to the Sourcewell Contract Administrator assigned to this Contract. A Report must be provided regardless of the number or amount of sales during that quarter (i.e., if there are no sales, Vendor must submit a report indicating no sales were made). The Report must contain the following fields: • Customer Name (e.g., City of Staples Highway Department); • Customer Physical Street Address; • Customer City; • Customer State/Province; • Customer Zip Code; • Customer Contact Name; • Customer Contact Email Address; • Customer Contact Telephone Number; • Sourcewell Assigned Entity/Participating Entity Number; • Item Purchased Description; • Item Purchased Price; • Sourcewell Administrative Fee Applied; and • Date Purchase was invoiced/sale was recognized as revenue by Vendor.
How Do I Get More Information? For more information, including the full Notice, Claim Forms and Settlement Agreement go to xxx.xxxxxxxxxxxxxxxxxxxx.xxx, contact the settlement administrator at 0-000-000-0000, or call Class Counsel at 1-866-354-3015. Exhibit E UNITED STATES DISTRICT COURT FOR THE SOUTHERN DISTRICT OF FLORIDA Xxxxx v. AvMed, Inc., Case No. 10-cv-24513 If You Paid for or Received Insurance from AvMed, Inc. at Any Time Through December of 2009, You May Be Part of a Class Action Settlement. IMPORTANT: PLEASE READ THIS NOTICE CAREFULLY. THIS NOTICE RELATES TO THE PENDENCY OF A CLASS ACTION LAWSUIT AND, IF YOU ARE A MEMBER OF THE SETTLEMENT CLASSES, CONTAINS IMPORTANT INFORMATION ABOUT YOUR RIGHTS TO MAKE A CLAIM UNDER THE SETTLEMENT OR TO OBJECT TO THE SETTLEMENT (A federal court authorized this notice. It is not a solicitation from a lawyer.) Your legal rights are affected whether or not you act. Please read this notice carefully. YOUR LEGAL RIGHTS AND OPTIONS IN THIS SETTLEMENT SUBMIT A CLAIM FORM This is the only way to receive a payment. EXCLUDE YOURSELF You will receive no benefits, but you will retain any rights you currently have to xxx the Defendant about the claims in this case. OBJECT Write to the Court explaining why you don’t like the Settlement. GO TO THE HEARING Ask to speak in Court about your opinion of the Settlement. DO NOTHING You won’t get a share of the Settlement benefits and will give up your rights to xxx the Defendant about the claims in this case. These rights and options – and the deadlines to exercise them – are explained in this Notice. QUESTIONS? CALL 0-000-000-0000 TOLL FREE, OR VISIT XXX.XXXXXXXXXXXXXXXXXXXX.XXX PARA UNA NOTIFICACIÓN EN ESPAÑOL, LLAMAR O VISITAR NUESTRO WEBSITE BASIC INFORMATION
Vendor Logo (Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Bid Attributes Disadvantaged/Minority/Women Business & Federal HUBZone Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Historically Underutilized Business (HUB) Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No National Coverage Can the Vendor provide its proposed goods and services to all 50 US States? Yes
Requester and Approved User Responsibilities The Requester agrees through the submission of the DAR that the PI named has reviewed and understands the principles for responsible research use and data management of the genomic datasets as defined in the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. The Requester and Approved Users further acknowledge that they are responsible for ensuring that all uses of the data are consistent with national, tribal, and state laws and regulations, as appropriate, as well as relevant institutional policies and procedures for managing sensitive genomic and phenotypic data. The Requester certifies that the PI is in good standing (i.e., no known sanctions) with the institution, relevant funding agencies, and regulatory agencies and is eligible to conduct independent research (i.e., is not a postdoctoral fellow, student, or trainee). The Requester and any Approved Users may use the dataset(s) only in accordance with the parameters described on the study page and in the 1 If contractor services are to be utilized, PI requesting the data must provide a brief description of the services that the contractor will perform for the PI (e.g., data cleaning services) in the research use statement of the DAR. Additionally, the Key Personnel section of the DAR must include the name of the contractor’s employee(s) who will conduct the work. These requirements apply whether the contractor carries out the work at the PI’s facility or at the contractor’s facility. In addition, the PI is expected to include in any contract agreement requirements to ensure that any of the contractor’s employees who have access to the data adhere to the NIH GDS Policy, this Data Use Certification Agreement, and the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. Note that any scientific collaborators, including contractors, who are not at the Requester must submit their own DAR. Addendum to this Agreement for the appropriate research use, as well as any limitations on such use, of the dataset(s), as described in the DAR, and as required by law. Through the submission of this DAR, the Requester and Approved Users acknowledge receiving and reviewing a copy of the Addendum which includes Data Use Limitation(s) for each dataset requested. The Requester and Approved Users agree to comply with the terms listed in the Addendum. Through submission of the DAR, the PI and Requester agree to submit a Project Renewal or Project Close-out prior to the expiration date of the one (1) year data access period. The PI also agrees to submit an annual Progress Update prior to the one (1) year anniversary2 of the project, as described under Research Use Reporting (Term 10) below. By approving and submitting the attached DAR, the Institutional Signing Official provides assurance that relevant institutional policies and applicable local, state, tribal, and federal laws and regulations, as applicable, have been followed, including IRB approval, if required. Approved Users may be required to have IRB approval if they have access to personal identifying information for research participants in the original study at their institution, or through their collaborators. The Institutional Signing Official also assures, through the approval of the DAR, that other institutional departments with relevant authorities (e.g., those overseeing human subjects research, information technology, technology transfer) have reviewed the relevant sections of the NIH GDS Policy and the associated procedures and are in agreement with the principles defined. The Requester acknowledges that controlled-access datasets subject to the NIH GDS Policy may be updated to exclude or include additional information. Unless otherwise indicated, all statements herein are presumed to be true and applicable to the access and use of all versions of these datasets.
