Software and Format Requirements Sample Clauses

Software and Format Requirements. Software standards and formats include but are not limited to the following: • Each draft and final text-based or spreadsheet-based deliverable shall be provided in MS Office file formats (i.e., MS Word, Excel, etc.) and must be fully compatible with version used by Agency. • Consultant shall submit draft and final deliverables in electronic format via e-mail (and hard copy if requested). • Consultant shall also submit any graphic files accompanying reports separately in .jpg or .tif formats unless specified differently by Agency. Consultant’s software shall produce deliverables that are fully compatible, readable and useable by Agency software, requiring no modification or translation of Consultant’s deliverables. No loss of data integrity or accuracy shall result from any transfer of data. Compressed data shall be in a "self- expanding executable" format. Additional format requirements may be listed elsewhere in the Statement of Work or in the Contract.
AutoNDA by SimpleDocs

Related to Software and Format Requirements

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Equipment and Software Requirements In order to view and retain electronic communications that we make available to you, you must have: • A PC or other device with an Internet browser that has “cookies” enabled and supports 128 bit encryption • An Internet connection • An email address • A PDF viewer (such as Adobe Reader) • A printer or computer with sufficient electronic storage space All communications shall be delivered to the last address we have on file for you. These notices will be sent through electronic delivery (email) and will be considered delivered the same day as sent. If you have opted out of electronic delivery, communications sent to you through the United States Postal Service are considered delivered 5 business days after the postmark date. It is your responsibility to notify the Custodian of any email address change or residential address change. We will not be held liable for any losses or damages if you have not provided Custodian with the most current address information. The electronically signed copy of this document should be considered equivalent to a printed hard copy form. It is considered a true and complete record of the document, admissible in arbitration and/or administrative hearings or proceedings. Your electronic signature on the Application and other electronic forms such as the Investment Direction are considered valid and the same as if the paper form or Application were signed.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Software and Documentation Licensee may make as many copies of the Software necessary for it to use the Software as licensed. Each copy of the Software made by Licensee must contain the same copyright and other notices that appear on the original copy. Licensee will not modify the Documentation. Documentation may: (a) only be used to support Licensee’s use of the Software; (b) not be republished or redistributed to any unauthorized third party; and (c) not be distributed or used to conduct training for which Licensee, or any other party, receives a fee. Licensee will not copy any system schema reference document related to the Software.

  • Hardware and Software In order to use the Services, you must obtain and maintain, at your expense, compatible mobile hardware and software as specified by Credit Union from time to time. Credit Union is not responsible for any third party software you may need to use the Services. Any such software is accepted by you as is and is subject to the terms and conditions of the software agreement you enter into directly with the third party software provider at time of download and installation.

  • Software compliance Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive license (like MIT, BSD, Apache 2.0,...). ● The license should provide unlimited access rights to the EGI community. ● Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the EGI organisation in GitHub13.) All releases should be appropriately tagged. ● Adopt best practices: ○ Defining and enforcing code style guidelines. ○ Using Semantic Versioning. ○ Using a Configuration Management frameworks such as Ansible. ○ Taking security aspects into consideration through at every point in time. ○ Having automated testing in place. ○ Using code reviewing. 9 xxxxx://xxx.xxx.xx/about/policy/policies_procedures.html 10 xxxxx://xxxx.xxx.xx/wiki/OMB 11 xxxx://xxx.xxx.xx/ 12 xxxxx://xxx.xxx.xx/portal/index.php?Page_Type=NGI&id=4 13 xxxxx://xxxxxx.xxx/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.

  • Access to Software Access Rights to Software which is Results shall comprise: Access to the Object Code; and, where normal use of such an Object Code requires an Application Programming Interface (hereafter API), Access to the Object Code and such an API; and, if a Party can show that the execution of its tasks under the Project or the Exploitation of its own Results is technically or legally impossible without Access to the Source Code, Access to the Source Code to the extent necessary. Background shall only be provided in Object Code unless otherwise agreed between the Parties concerned.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • Required hardware and software The minimum system requirements for using the DocuSign system may change over time. The current system requirements are found here: xxxxx://xxxxxxx.xxxxxxxx.xxx/guides/signer-guide- signing-system-requirements. Acknowledging your access and consent to receive and sign documents electronically To confirm to us that you can access this information electronically, which will be similar to other electronic notices and disclosures that we will provide to you, please confirm that you have read this ERSD, and (i) that you are able to print on paper or electronically save this ERSD for your future reference and access; or (ii) that you are able to email this ERSD to an email address where you will be able to print on paper or save it for your future reference and access. Further, if you consent to receiving notices and disclosures exclusively in electronic format as described herein, then select the check-box next to ‘I agree to use electronic records and signatures’ before clicking ‘CONTINUE’ within the DocuSign system. By selecting the check-box next to ‘I agree to use electronic records and signatures’, you confirm that: • You can access and read this Electronic Record and Signature Disclosure; and • You can print on paper this Electronic Record and Signature Disclosure, or save or send this Electronic Record and Disclosure to a location where you can print it, for future reference and access; and

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