We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Add Template Sample Clauses

Add Template. User can click on ‘+’ in CG Template window to create a new template providing details, properties and data. Details like Path, Name, Type, Layer, Offset, Duration and Loop count. There is no limitation of the number of layers in the system and the users can add multiple layers.

Related to Add Template

  • TEMPLATE That certain three well drilling template acquired, inter alia, by Seller for use in connection with the drilling of the OCS-G 7049 #5 Well.

  • Implementation Report Within 150 days after the Effective Date, Ensign Group shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include: 1. the name, address, phone number, and position description of the Compliance Officer required by Section III.A, and a summary of other noncompliance job responsibilities the Compliance Officer may have; 2. the names and positions of the members of the Compliance Committee required by Section III.A; 3. the names and positions of the members of the Board of Directors who are responsible for satisfying the Board of Directors compliance obligations described in Section III.A.3; 4. a copy of Ensign Group’s Code of Conduct required by Section III.B.1; 5. the number of individuals required to complete the Code of Conduct certification required by Section III.B.1, the percentage of individuals who have completed such certification, and an explanation of any exceptions (the documentation supporting this information shall be available to OIG upon request); 6. a summary of all Policies and Procedures required by Section III.B (copies of the Policies and Procedures shall be made available to OIG upon request); 7. the following information regarding each type of training required by Section III.C: a. a description of such training, including a summary of the topics covered, the length of sessions, and a schedule of training sessions; b. the number of individuals required to be trained, percentage of individuals actually trained, and an explanation of any exceptions. A copy of all training materials and the documentation supporting this information shall be made available to OIG upon request. 8. a description of the Disclosure Program required by Section III.E; 9. the following information regarding the IRO(s): (a) identity, address, and phone number; (b) a copy of the engagement letter; (c) information to demonstrate that the IRO has the qualifications outlined in Appendix A to this CIA; (d) a summary and description of any and all current and prior engagements and agreements between Ensign Group and the IRO; and (e) a certification from the IRO regarding its professional independence and objectivity with respect to Ensign Group; 10. a description of the process by which Ensign Group fulfills the requirements of Section III.F regarding Ineligible Persons; 11. a list of all of Ensign Group’s locations (including locations and mailing addresses); the corresponding name under which each location is doing business; the corresponding phone numbers and fax numbers; each location’s Medicare and state Medicaid program provider number and/or supplier number(s); and the name and address of each Medicare and state Medicaid program contractor to which Ensign Group currently submits claims; 12. a description of Ensign Group’s corporate structure, including identification of any parent and sister companies, subsidiaries, and their respective lines of business; and

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Proposed Policies and Procedures Regarding New Online Content and Functionality By October 31, 2017, the School will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the School to provide equally effective alternative access. The Plan for New Content will require the School, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternates are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the School’s online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the School will officially adopt, and fully implement the amended policies and procedures.

  • Policies and Temporary Policies Registry Operator shall comply with and implement all Consensus Policies and Temporary Policies found at <xxxx://xxx.xxxxx.xxx/general/consensus-policies.htm>, as of the Effective Date and as may in the future be developed and adopted in accordance with the ICANN Bylaws, provided such future Consensus Polices and Temporary Policies are adopted in accordance with the procedure and relate to those topics and subject to those limitations set forth in Specification 1 attached hereto (“Specification 1”). Data Escrow. Registry Operator shall comply with the registry data escrow procedures set forth in Specification 2 attached hereto (“Specification 2”).

  • Formatted Font: 12

  • Training Plan 19.6.1 An apprentice shall be a party to an individual Training Plan. 19.6.2 The Training Plan sets out the training that the apprentice will do both on – the – job and off – the – job. The Training Plan also sets out how the Registered Training Organisation (RTO) will ensure the apprentice will receive quality training – both on – the – job and off – the – job. 19.6.3 The Training Plan reflects the choices made by the employer and the apprentice in relation to:-

  • Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.