Import File Sample Clauses

Import File. There are two ways to import files (PDF, BMP, JPG, TIFF) into WorldocScan X. One way is to directly import PDF, BMP, JPG, or TIFF file into WorldocScan X.
AutoNDA by SimpleDocs

Related to Import File

  • Regulatory Filing In the event that this Interconnection Construction Service Agreement contains any terms that deviate materially from the form included in Attachment P or from the standard terms and conditions in this Appendix 2, the Transmission Provider shall file the executed Interconnection Construction Service Agreement on behalf of itself and the Interconnected Transmission Owner with FERC as a service schedule under the Tariff. Interconnection Customer may request that any information so provided be subject to the confidentiality provisions of Section 17 of this Appendix

  • ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to Image Access via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one (1) dataset per workday per OCN. If BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.

  • Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.

  • PRICE LISTS AND PRODUCT INFORMATION Contractors should provide an electronic version of the proposed price list in an Excel format or pdf on a jump drive. Also provide a dealer list, if applicable in an Excel format with "read and write" capabilities on the same jump drive. No costs or expenses associated with providing this information in the required format shall be charged to the State of Arkansas. At the time of contract renewal contractor will furnish OSP with an updated dealer list and published price list.

  • Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.

  • Regulatory Filings NYISO and Connecting Transmission Owner shall file this Agreement (and any amendment hereto) with the appropriate Governmental Authority, if required. Any information related to studies for interconnection asserted by Developer to contain Confidential Information shall be treated in accordance with Article 22 of this Agreement and Attachment F to the ISO OATT. If the Developer has executed this Agreement, or any amendment thereto, the Developer shall reasonably cooperate with NYISO and Connecting Transmission Owner with respect to such filing and to provide any information reasonably requested by NYISO and Connecting Transmission Owner needed to comply with Applicable Laws and Regulations.

  • COMPUTER GRAPHICS FILES The Engineer agrees to comply with Attachment G, Computer Graphics Files for Document and Information Exchange, if determined by the State to be applicable to this contract.

  • Grievance File Records involving the processing of an employee's grievance, such as the grievance form, step appeals/responses, and settlement documents, will be kept in a file separate from the employee’s personnel file. It is not the intent of this section to exclude from the employee's personnel file final disciplinary action documents, including those that result from a settlement agreement.

  • Access to File 12.01 An employee shall upon written request, made a reasonable time before the time of viewing, have an opportunity to view their personnel file in the presence of the Director of Human Resources or their designate. The information the employee may review will be:

  • Personal File (a) The Corporation agrees that there shall be only one personal file for each employee and that no report relating to the employee's conduct or performance may be used against him or her in the grievance procedure nor at arbitration unless such report is part of the said file.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!