Critical Functions Sample Clauses

Critical Functions. Notwithstanding anything in this Section 18.8 to the contrary, upon the occurrence of an event described in Section 18.8.1 that substantially prevents, hinders or delays performance of services necessary for the performance of "critical functions" of such Party for more than seven (7) consecutive days, such Party to whom such affected or delayed performance is due will have the right to immediately terminate this Agreement. For the purposes of this Section 18.8.3, "critical functions" means with respect to a Party, those business functions that are essential and critical to its business operations or the business operations of its Members.
AutoNDA by SimpleDocs
Critical Functions. Notwithstanding anything in this Section 18.8 to the contrary, upon the occurrence of an event described in Section 18.8.1 that substantially prevents, hinders or delays performance of services necessary for the performance of “critical functions” of such Party for more than seven (7) consecutive days, such Party to whom such affected or delayed performance is due will have the right to immediately terminate this Agreement. For the purposes of this Section 18.8.3, “critical
Critical Functions. 7.1 Functions that are fundamental to carrying out Abacus’ core business are considered to be critical functions. A Critical Function is defined as a function that is fundamental to carrying out Abacus’ core business; the failure of which would result in one or more of the following: 7.1.1 A financial loss of sufficient magnitude to require a draw-down of the capital adequacy requirement 7.1.2 Failure to meet the contractual obligations to policyholders 7.1.3 A potential loss of license or penalty being imposed by the Regulator; financial or otherwise 7.2 The Control Functions in the business shall automatically be deemed to be critical functions. 7.3 The RC shall determine whether or not a function, activity or service is Critical. 7.4 The following must not be considered Critical Functions: 7.4.1 The provision to the Company of advisory services and other services, which do not form part of the core insurance activities, such as legal advice, the training of personnel, billing services and the security of premises and personnel; 7.4.2 The purchase of standardised services, including market information services and the provision of price feeds; 7.4.3 The provision of logistical support, for example, cleaning or catering; 7.4.4 The provision of elements of human resources support, for example, sourcing temporary employees and processing payroll.
Critical Functions. For purposes of this sec- tion, critical functions include, at a minimum, the fol- lowing: (1) Private security functions, as that term is de- fined in section 864(a)(6) of the National Defense Au- thorization Act for Fiscal Year 2008 [Pub. L. 110–181] (10 U.S.C. 2302 note) [now 10 U.S.C. 4571 note prec.]. (2) Training and advising Government personnel, including military and security personnel, of a host nation. (3) Conducting intelligence or information oper- ations. (4) Any other functions that are closely associated with inherently governmental functions, including the functions set forth in section 7.503(d) of the Fed- eral Acquisition Regulation. (5) Any other functions that are deemed critical to the success of the operation.

Related to Critical Functions

  • Review Systems; Personnel It will maintain business process management and/or other systems necessary to ensure that it can perform each Test and, on execution of this Agreement, will load each Test into these systems. The Asset Representations Reviewer will ensure that these systems allow for each Review Receivable and the related Review Materials to be individually tracked and stored as contemplated by this Agreement. The Asset Representations Reviewer will maintain adequate staff that is properly trained to conduct Reviews as required by this Agreement.

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

  • Statistical, Demographic or Market-Related Data All statistical, demographic or market-related data included in the Registration Statement, the Disclosure Package or the Prospectus are based on or derived from sources that the Company believes to be reliable and accurate and all such data included in the Registration Statement, the Disclosure Package or the Prospectus accurately reflects the materials upon which it is based or from which it was derived.

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