Root Sample Clauses

Root cause analysis - Analysis of the root causes of problems. Problems will be reviewed to determine their root causes, measures will be taken to correct the sources of the problems, and reports will be prepared and distributed in a timely fashion.
Sample 1Sample 2Sample 3See All (7)
AutoNDA by SimpleDocs
Root. Cause Analysis and Resolution Within 6 business days of receipt of a notice from AMEX in respect of (l) TM VENDORS' material failure to provide the Services or (2) TM VENDORS' repeated failure to provide any of the Services in accordance with the Service Levels, CREDITCOMM shall (a) perform a root-cause analysis to identify the cause of such failure, (b) correct such failure, provided, however, if the failure cannot be cured within 6 business days, the vendor shall commence the cure within such six (6) business day period and diligently pursue the cure until completed within twenty-one (21) business day period from the date of original failure, (c) provide AMEX with a report detailing the cause of, and procedure for correcting, such failure and (d) provide AMEX with reasonable evidence that such failure will not reoccur.
Sample 1Sample 2
Root. A root will mean either the highest S in a tree, an S immediately dominated by the highest S or the reported S in direct discourse. (Emonds 1969: 6) In these contexts, a non-structure preserving transformation such as Negative Constituent Preposing (NCP) may apply, but not in a non-root clause, which requires all transformations to be structure-preserving (see also Emonds 1976, 2004, 2012).
Sample 1
Root. The root of a METS document can contain a number of optional attributes, namespaces (xmlns:) and schema instance locations (xsi:) of the external standards referenced in the METS record and a number of other elements as seen in Table 1. Table 1: METS root Element Definition Explanation Card. METS Identity Identification of the package A code that uniquely identifies the whole SIP and the digital object/objects being submitted. A UUID or GUID should be used to create globally unique identifiers. Example: “UUID:550e8400-e29b-41d4-a716- 446655440004" 1 <mets: OBJID=”[Identity]” > Description Description of the package Short text describing the package. Example: "Example of SIP for delivery of personnel information" 0..1 <mets: LABEL=”[Descripti on]”> Content type The content type being submitted with this package Describes the content type the information being submitted in the package belongs to. It is recommended to use the pattern [OAIS_Type]:[Standard_Name]. Example: ”SIP:SIARD2” 1 <mets: TYPE=”[Content type]” Element Definition Explanation Card. METS Profile23 Profile name Describes the METS-profile being used. The name should contain the version number and the version may be captured in the profile file path. Example: ” xxxx://xxxx- xxxxxxx.xxx/xxxxxxxxx/XXXX/x00/XX TS.xml” 1 <mets: PROFILE="[Profile] " Example: <mets xmlns:xsi="xxxx://xxx.x0.xxx/2001/XMLSchema-instance" xmlns:xlink="xxxx://xxx.x0.xxx/1999/xlink" xmlns="xxxx://xxx.xxx.xxx/METS/" PROFILE="xxxx://xxx.xx.xx/METS/v02/METS.xml" TYPE="SIP:SIARD2" OBJID="5d378f86-28a1-41d8-a2b9- 264b10fbd511" LABEL="METS file describing the SIP." xsi:schemaLocation="xxxx://xxx.xxx.xxx/METS/ schemas/METS.xsd xxxx://xxx.x0.xxx/1999/xlink schemas/xlink.xsd">
Sample 1
Root. A root will mean either the highest S in a tree, an S immediately dominated by the highest S or the reported S in direct discourse. (Emonds 1969: 6) The following taken from Emonds (1969) exemplifies the three three root environments where the root transformation of Negative Constituent Preposing may occur; the fourth example shows a non-root environment that does not allow this operation.
Sample 1
Root. Rooting gives the user administrator rights to alter the OS, tweak the hardware and unlock the phone from its carrier.
Sample 1

Related to Root

  • Root Cause Analysis Upon Vendor's failure to provide the Services in accordance with the applicable Service Levels (for any reason other than a Force Majeure Event) Vendor will promptly (a) perform a root-cause analysis to identify the cause of such failure, (b) provide Prudential with a report detailing the cause of, and procedure for correcting, such failure, (c) obtain Prudential's written approval of the proposed procedure for correcting such failure, (d) correct such failure in accordance with the approved procedure, (e) provide weekly (or more frequent, if appropriate) reports on the status of the correction efforts, and (f) provide Prudential with assurances satisfactory to Prudential that such failure has been corrected and will not recur.

  • Stability 14.01 Maintain a documented, ongoing stability program to monitor the stability of the Product using stability indicating procedures. X 14.02 Data analysis and trending reporting will be performed. X

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case.

  • API If the Software offers integration capabilities via an API, your use of the API may be subject to additional costs or Sage specific policies and terms and conditions (which shall prevail in relation to your use of the API). You may not access or use the API in any way that could cause damage to us or the Software, or in contravention of any applicable laws. We reserve the right in our sole discretion, to: (i) update any API from time to time; (ii) place limitations around your use of any API; and (iii) deny you access to any API in the event of misuse by you or to otherwise protect our legitimate interests.

  • Testing Landlord shall have the right to conduct annual tests of the Premises to determine whether any contamination of the Premises or the Project has occurred as a result of Tenant’s use. Tenant shall be required to pay the cost of such annual test of the Premises; provided, however, that if Tenant conducts its own tests of the Premises using third party contractors and test procedures acceptable to Landlord which tests are certified to Landlord, Landlord shall accept such tests in lieu of the annual tests to be paid for by Tenant. In addition, at any time, and from time to time, prior to the expiration or earlier termination of the Term, Landlord shall have the right to conduct appropriate tests of the Premises and the Project to determine if contamination has occurred as a result of Tenant’s use of the Premises. In connection with such testing, upon the request of Landlord, Tenant shall deliver to Landlord or its consultant such non-proprietary information concerning the use of Hazardous Materials in or about the Premises by Tenant or any Tenant Party. If contamination has occurred for which Tenant is liable under this Section 30, Tenant shall pay all costs to conduct such tests. If no such contamination is found, Landlord shall pay the costs of such tests (which shall not constitute an Operating Expense). Landlord shall provide Tenant with a copy of all third party, non-confidential reports and tests of the Premises made by or on behalf of Landlord during the Term without representation or warranty and subject to a confidentiality agreement. Tenant shall, at its sole cost and expense, promptly and satisfactorily remediate any environmental conditions identified by such testing in accordance with all Environmental Requirements. Landlord’s receipt of or satisfaction with any environmental assessment in no way waives any rights which Landlord may have against Tenant.

  • Metering The Interconnection Customer shall be responsible for the Connecting Transmission Owner’s reasonable and necessary cost for the purchase, installation, operation, maintenance, testing, repair, and replacement of metering and data acquisition equipment specified in Attachments 2 and 3 of this Agreement. The Interconnection Customer’s metering (and data acquisition, as required) equipment shall conform to applicable industry rules and Operating Requirements.

  • Sampling The Licensee agrees that the Composition is purchased as a “Work Made for Hire” whereby the clearing of any sampled materials is the responsibility of Licensee.

  • Corrective Action Despite its right to terminate this Agreement pursuant to this Article, the LHIN may choose not to terminate this Agreement and may take whatever corrective action it considers necessary and appropriate, including suspending Funding for such period as the LHIN determines, to ensure the successful completion of the Services in accordance with the terms of this Agreement.

  • Commissioning Commissioning tests of the Interconnection Customer's installed equipment shall be performed pursuant to applicable codes and standards. If the Interconnection Customer is not proceeding under Section 2.3.2, the Utility must be given at least ten (10) Business Days written notice, or as otherwise mutually agreed to by the Parties, of the tests and may be present to witness the commissioning tests.

  • Virus Management Transfer Agent shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within the Transfer Agent environment.

Time is Money Join Law Insider Premium to draft better contracts faster.