Electronic Files and Developing Software Sample Clauses

The 'Electronic Files and Developing Software' clause governs the handling, ownership, and use of digital files and software that are created or modified during the course of a project or contractual relationship. It typically outlines who retains rights to source code, design files, or other digital assets, and may specify requirements for delivery formats, access, or ongoing support. This clause ensures that both parties have a clear understanding of their rights and responsibilities regarding electronic deliverables, reducing the risk of disputes over intellectual property or access to essential project materials.
Electronic Files and Developing Software o Electronic File Format  Submit all data and documents required as products under this Agreement in an electronic file format that is fully editable and compatible with the Energy Commission’s software and Microsoft (MS)-operating computing platforms, or with any other format approved by the CAM. Deliver an electronic copy of the full text of any Agreement data and documents in a format specified by the CAM, such as memory stick or CD-ROM. The following describes the accepted formats for electronic data and documents provided to the Energy Commission as products under this Agreement, and establishes the software versions that will be required to review and approve all software products:  Data sets will be in MS Access or MS Excel file format (version 2007 or later), or any other format approved by the CAM.  Text documents will be in MS Word file format, version 2007 or later.  Documents intended for public distribution will be in PDF file format.  The Recipient must also provide the native Microsoft file format.  Project management documents will be in Microsoft Project file format, version 2007 or later.
View SourceView Similar (4)
Electronic Files and Developing Software o Electronic File Format ▪ Submit all data and documents required as products under this Agreement in an electronic file format that is fully editable and compatible with the California Energy Commission’s (CEC) software and Microsoft (MS)- operating computing platforms, or with any other format approved by the CAM. Deliver an electronic copy of the full text of any Agreement data and documents in a format specified by the CAM, such as memory stick. The following describes the accepted formats for electronic data and documents provided to the CEC as products under this Agreement, and establishes the software versions that will be required to review and approve all software products: ▪ Data sets will be in MS Access or MS Excel file format (version 2007 or later), or any other format approved by the CAM. ▪ Text documents will be in MS Word file format, version 2007 or later. ▪ Project management documents will be in Microsoft Project file format, version 2007 or later.
View SourceView Similar (3)

Related to Electronic Files and Developing Software

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

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Electronic Files a. It is the Buyer's responsibility to maintain a copy of any original Electronic File provided by the Buyer. b. The Seller shall not be responsible for checking the accuracy of supplied input from an electronic file unless otherwise agreed in writing. c. Without prejudice to clause 5.2(b), if an electronic file is not suitable for outputting on equipment normally adequate for such purposes without adjustment or other corrective action the Seller may make a charge for any resulting additional cost incurred or may reject the file without prejudice to his rights to payment for work done/material purchased.

  • Electronic Records You acknowledge and agree that we may in our discretion store all records electronically; and that we will not retain and have no obligation to retain any original documents for any period of time. This applies to all documentation including but not limited to checks, transaction records, notes, mortgages, deeds of trust and other loan and/or security documentation. We will routinely destroy all original documentation. We may store records electronically via imaging, scanning, filming or other technology used in the financial services industry for the storage of documentation via internal processes or third-party processors that we approve for these services. You agree that such storage shall be secure, and further agree that such records shall for all purposes be recognized and admissible in evidence or otherwise to prove the agreements, rights and obligations of the parties pursuant to any such records.

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