DOCUMENT VERSION CONTROL Sample Clauses

DOCUMENT VERSION CONTROL. Version Description Date
AutoNDA by SimpleDocs

Related to DOCUMENT VERSION CONTROL

  • Documentation control Specify how documentation will be identified with an alpha numeric which indicates source, recipient, communication number etc. Provide details of any particular format or other constraints; for example that all contractual communications will be in the form of properly compiled letters or forms attached to e mails and not as a message in the e mail itself. State any particular routing requirements but note from TSC3 who issues what to whom.

  • Infection Control Consistent with the Centers for Disease Control and Prevention Guideline for Infection Control in Health Care Personnel, and University Policy 3364-109-EH-603, the parties agree that all bargaining unit employees who come in contact with patients in the hospital or ambulatory care clinics will need to be vaccinated against influenza when flu season begins each fall. The influenza vaccine will be offered to all health care workers, including pregnant women, before the influenza season, unless otherwise medically contraindicated or it compromises sincerely held religious beliefs.

  • Erosion Control a. The Purchaser shall construct slash and debris erosion barriers, dips, water bars or ditches in skid trails and landings as directed by the Forest Officer.

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • Document Management The Contractor must retain sufficient documentation to substantiate claims for payment under the Contract and all other records, electronic files, papers, and documents that were made in relation to this Contract. The Contractor must retain all documents related to the Contract for five (5) years after expiration of the Contract or, if longer, the period required by the General Records Schedules maintained by the Florida Department of State available at the Department of State’s Records Management website.

  • OGS Centralized Contract Terms and Conditions have been renumbered as depicted in the following chart: Current Amended Section Title 4.25 4.26 Severability 4.26 4.27 Entire Agreement

  • Separation control Where legally required, Provider will ensure that Personal Data collected for different purposes can be Processed separately. Provider shall also ensure there is separation between test and production systems. AVAILABILITY CONTROL. Provider protects Personal Data against accidental destruction or loss by following these controls:

  • State Approval of Replacement Personnel The Engineer may not replace the project manager or key personnel without prior consent of the State. The State must be satisfied that the new project manager or other key personnel is qualified to provide the authorized services. If the State determines that the new project manager or key personnel is not acceptable, the Engineer may not use that person in that capacity and shall replace him or her with one satisfactory to the State within forty-five (45) days.

  • Document routing The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system. Routing Data Table* Field Name in WAWF Data to be entered in WAWF Pay Official DoDAAC "To be cited in each individual task order" Issue By XxXXXX "To be cited in each individual task order" Admin DoDAAC "To be cited in each individual task order" Inspect By XxXXXX "To be cited in each individual task order" Ship To Code "To be cited in each individual task order" Ship From Code "To be cited in each individual task order" Mark For Code "To be cited in each individual task order" Service Approver (DoDAAC) "To be cited in each individual task order" Service Acceptor (DoDAAC) "To be cited in each individual task order" Accept at Other DoDAAC "To be cited in each individual task order" LPO DoDAAC "To be cited in each individual task order" DCAA Auditor DoDAAC "To be cited in each individual task order" Other DoDAAC(s) "To be cited in each individual task order" (*Contracting Officer: Insert applicable DoDAAC information or “See schedule” if multiple ship to/acceptance locations apply, or “Not applicable.”)

  • Documentation License Subject to the terms of this Agreement, Flock hereby grants to Customer a non-exclusive, non-transferable right and license to use the Documentation during the Service Term for Customer’s internal purposes in connection with its use of the Flock Services as contemplated herein.

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