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)
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. Rooting gives the user administrator rights to alter the OS, tweak the hardware and unlock the phone from its carrier.
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

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.

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

  • Stability Trubion or its designee shall be responsible for conducting all necessary stability testing to comply with cGMP and other applicable regulatory guidelines. Such stability testing shall include testing to validate the lead times for shipment, the shelf life of Bulk Drug, and the Bulk Drug Specifications applicable to shipment, storage and handling of Bulk Drug. Lonza shall prepare all stability samples, and shall sublot stability samples and package and ship stability samples to Trubion, all in accordance with timelines, protocols and procedures agreed upon by Lonza and Trubion and as set forth in the Quality Agreement.

  • RE-WEIGHING PRODUCT Deliveries are subject to re- weighing at the point of destination by the Authorized User. If shrinkage occurs which exceeds that normally allowable in the trade, the Authorized User shall have the option to require delivery of the difference in quantity or to reduce the payment accordingly. Such option shall be exercised in writing by the Authorized User.

  • Downtime Due to the nature of server provision, downtime and lost transmissions may occur as part of routine maintenance. You are advised to maintain a copy of your account status and details of Content purchased.

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

  • Diagnosis For a condition to be considered a covered illness or disorder, copies of laboratory tests results, X-rays, or any other report or result of clinical examinations on which the diagnosis was based, are required as part of the positive diagnosis by a physician.

  • Progressive Discipline The Employer will follow the principles of progressive discipline. Disciplinary action shall be commensurate with the offense. Disciplinary action shall include:

  • Right to Grieve Disciplinary Action Disciplinary action grievable by the employee shall include written appraisals (if utilized), written censures, and warnings. An employee shall be given a copy of any such document placed on the employee's file which might be the basis of disciplinary action. Should any employee dispute any such entry in their file they shall be entitled to recourse through the grievance procedure. The Employer agrees not to introduce as evidence in any hearing any document from the file of an employee, the existence of which the employee was not aware at the time of filing.

  • Outages 9.7.1.1 Outage Authority and Coordination. Interconnection Customer and Transmission Owner may each in accordance with Good Utility Practice in coordination with the other Party and Transmission Provider remove from service any of its respective Interconnection Facilities, System Protection Facilities, Network Upgrades, System Protection Facilities or Distribution Upgrades that may impact the other Party’s facilities as necessary to perform maintenance or testing or to install or replace equipment. Absent an Emergency Condition, the Party scheduling a removal of such facility(ies) from service will use Reasonable Efforts to notify one another and schedule such removal on a date and time mutually acceptable to the Parties. In all circumstances, any Party planning to remove such facility(ies) from service shall use Reasonable Efforts to minimize the effect on the other Parties of such removal.