Root Clause Samples

The "Root" clause typically serves as the foundational or introductory provision in a contract or legal document, establishing the basis for the agreement. It may outline the parties involved, the general purpose of the contract, and reference the scope of the agreement. For example, it might specify the effective date and the overall intent behind the document. Its core practical function is to provide context and clarity, ensuring that all subsequent clauses are interpreted within the correct framework and that the parties are clearly identified from the outset.
POPULAR SAMPLE Copied 1 times
Root cause analysis—A class of problem-solving methods aimed at identifying the ultimate/root causes of problems or events. The practice of root cause analysis is predicated on the belief that problems are best solved by attempting to correct or eliminate root causes, as opposed to merely addressing the immediately obvious symptoms of which there could be many and may overshadow underlying issues. 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.
View SourceView Similar (3)
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.
View SourceView Similar (7)
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.
View SourceView Similar (3)
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.
View SourceView Similar (2)
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. 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]” 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: ” ▇▇▇▇://▇▇▇▇- ▇▇▇▇▇▇▇.▇▇▇/▇▇▇▇▇▇▇▇▇/▇▇▇▇/▇▇▇/▇▇ TS.xml” 1 <mets: PROFILE="[Profile] " <mets xmlns:xsi="▇▇▇▇://▇▇▇.▇▇.▇▇▇/2001/XMLSchema-instance" xmlns:xlink="▇▇▇▇://▇▇▇.▇▇.▇▇▇/1999/xlink" xmlns="▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/METS/" PROFILE="▇▇▇▇://▇▇▇.▇▇.▇▇/METS/v02/METS.xml" TYPE="SIP:SIARD2" OBJID="5d378f86-28a1-41d8-a2b9- 264b10fbd511" LABEL="METS file describing the SIP." xsi:schemaLocation="▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/METS/ schemas/METS.xsd ▇▇▇▇://▇▇▇.▇▇.▇▇▇/1999/xlink schemas/xlink.xsd">
View Source
Root. Rooting gives the user administrator rights to alter the OS, tweak the hardware and unlock the phone from its carrier.
View Source
Root. Rooting gives the user administrator rights to alter the OS, tweak the hardware and unlock the phone from its carrier.
View Source

Related to Root

  • Solution The Supplier’s contractually committed technical approach for solving an information technology business objective and associated Requirements as defined and authorized by the scope of the Contract or any order or Statement of Work issued under the Contract. Solution means all Supplier and Supplier’s third-party providers’ components making up the Solution, including but not limited to Software, Product, configuration design, implementation, Supplier-developed interfaces, Services and Work Product.

  • Downtime Each of Zero Hash and ZHLS uses commercially reasonable efforts to provide the Services in a reliable and secure manner. From time to time, interruptions, errors, delays, or other deficiencies in providing the Services may occur due to a variety of factors, some of which are outside of Zero Hash’s and/or ZHLS’ control, and some which may require or result in scheduled maintenance or unscheduled downtime of the Services (collectively, “Downtime”). You understand and acknowledge that part or all of the Services may be unavailable during any such period of Downtime, and you acknowledge that Zero Hash and ZHLS are not liable or responsible to you for any inconvenience or losses to you as a result of Downtime. Following Downtime, you further understand and acknowledge that the prevailing market prices of cryptocurrency may differ significantly from the prices prior to such Downtime.

  • Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.