Archiving of Projects and Data Sample Clauses

Archiving of Projects and Data. The Software performs periodic archiving of projects and data that have been idle for a certain period of days, which is currently forty (40) days subject to change. Project owners will be notified via e-mail in advance and can reject the archiving via the Software. Archived projects can be retrieved by the Designated User via the Software. Archived projects will be compatible with the Software for at least two (2) years from the archiving date. SCHEDULE 6
AutoNDA by SimpleDocs

Related to Archiving of Projects and Data

  • Project Website The State will develop and maintain a website that will be made available in advance of the first public meeting for this project. The Engineer shall provide project information for the project website to the State including documents related to project background, study area limits, study objectives, project photos, study area maps, material presented at public meetings, and contact information for requesting additional information. The project website will be updated with the documents and other information provided by the Engineer to the State after each set of public meetings and the final report in PDF format provided by the Engineer will be posted by the State to give the general public access to the document.

  • Customer Materials 12.1 The Supplier including any of its employees, agents, consultants, contractors and any third party shall:

  • Marking of Data Pursuant to Paragraph A above, any Data delivered under this Agreement shall be marked with the following legend: Use, duplication, or disclosure is subject to the restrictions as stated in Agreement HR0011-XX-9-XXXX between the Government and the Performer.

  • Information and Data 21.1 At all times during the subsistence of this Agreement the duly authorized representatives of each Participant shall, at its and their sole risk and expense and at reasonable intervals and times, have access to the Property and to all technical records and other factual engineering data and information relating to the Property which is in the possession of the Operator.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Access to Customer Data You agree that we may, for the purposes of providing Maintenance and Customer Support and/or for the purpose of otherwise protecting the integrity of the Software, access and/or download your Customer Data on a limited basis.

  • Audit of Existing Content and Functionality By May 1, 2017, the District will propose for OCR’s review and approval the identity and bona fides of an Auditor (corporation or individual) to audit all content and functionality on its website, including, but not limited to, the home page, all subordinate pages, and intranet pages and sites, to identify any online content or functionality that is inaccessible to persons with disabilities, including online content and functionality developed by, maintained by, or offered through a third party vendor or an open source. The Auditor will have sufficient knowledge and experience in website accessibility for people with disabilities to carry out all related tasks, including developing a Proposed Corrective Action Plan. The Audit will use the Benchmarks for Measuring Accessibility set out above, unless the District receives prior permission from OCR to use a different standard as a benchmark. During the Audit, the District will also seek input from members of the public with disabilities, including parents, students, employees, and others associated with the District, and other persons knowledgeable about website accessibility, regarding the accessibility of its online content and functionality.

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

  • Accessibility of Web-Based Information and Applications For State Agency Authorized User Acquisitions: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as follows: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08- 005, Accessibility of Web-Based Information and Applications as such policy may be amended, modified or superseded, which requires that state agency web-based information and applications are accessible to persons with disabilities. Web-based information and applications must conform to New York State Enterprise IT Policy NYS-P08-005 as determined by quality assurance testing. Such quality assurance testing will be conducted by the State Agency Authorized User and the results of such testing must be satisfactory to the Authorized User before web-based information and applications will be considered a qualified deliverable under the contract or procurement.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Interconnection Customer's data is materially different from what was originally provided to the Participating TO and the CAISO for the Interconnection Studies, then the Participating TO and the CAISO will conduct appropriate studies pursuant to the LGIP to determine the impact on the Participating TO’s Transmission System and affected portions of the CAISO Controlled Grid based on the actual data submitted pursuant to this Article 24.3. The Interconnection Customer shall not begin Trial Operation until such studies are completed and all other requirements of this LGIA are satisfied.

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