Service Log Sheet. The Contractor shall create a “Service Log Sheet” which will be maintained and checked daily for customer requests at each facility location. Items requiring completion will be so noted at the end of each shift.
Service Log Sheet Sample Clauses
Related to Service Log Sheet
Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.
Service Location The services shall be performed at all contracting and participating facilities of the Contractor.
Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A.
Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.
Time Schedule 4.1. A project schedule is included in Appendix A. 4.2. Any delay of services or change in sequence of tasks must be approved in writing by Delaware. 4.3. In the event that Vendor fails to complete the project or any phase thereof within the time specified in the Contract, or with such additional time as may be granted in writing by Delaware, or fails to prosecute the work, or any separable part thereof, with such diligence as will insure its completion within the time specified in this Agreement or any extensions thereof, Delaware shall suspend the payments scheduled as set forth in Appendix A.
Detailed Description of Services / Statement of Work Describe fully the services that Contractor will provide, or add and attach Exhibit B to this Agreement.
Service Locations X.X. Xxxxxx maintains various operational/service centers and locations through the United States and foreign jurisdictions. The services provided under this Agreement may be provided from one or more such locations. X.X. Xxxxxx may change the operational/service centers and locations as it deems necessary or appropriate for its business concerns.
Approved Services; Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at xxxx://xxx.xxxxx.xxx/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.
Contract Schedule The information set forth in the Contract Schedule is true and correct.
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.
