Developing governance models for infrastructure integration Sample Clauses

Developing governance models for infrastructure integration. The agreement on governance models is a necessary condition for successful institutional participation in larger e-Infrastructure initiatives. This includes also aggregation and re-use of digital resources.
AutoNDA by SimpleDocs

Related to Developing governance models for infrastructure integration

  • Cost Responsibility for Interconnection Facilities and Distribution Upgrades 4.1 Interconnection Facilities 4.2 Distribution Upgrades

  • Additional Information for Product Development Projects Outcome of product development efforts, such copyrights and license agreements. • Units sold or projected to be sold in California and outside of California. • Total annual sales or projected annual sales (in dollars) of products developed under the Agreement. • Investment dollars/follow-on private funding as a result of Energy Commission funding. • Patent numbers and applications, along with dates and brief descriptions.  Additional Information for Product Demonstrations: • Outcome of demonstrations and status of technology. • Number of similar installations. • Jobs created/retained as a result of the Agreement.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Infrastructure (a) The Borrower has and will maintain a sufficient infrastructure to conduct its business as presently conducted and as contemplated to be conducted following its execution of this Agreement.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

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

  • For Product Development Projects and Project Demonstrations  Published documents, including date, title, and periodical name.  Estimated or actual energy and cost savings, and estimated statewide energy savings once market potential has been realized. Identify all assumptions used in the estimates.  Greenhouse gas and criteria emissions reductions.  Other non-energy benefits such as reliability, public safety, lower operational cost, environmental improvement, indoor environmental quality, and societal benefits.  Data on potential job creation, market potential, economic development, and increased state revenue as a result of the project.  A discussion of project product downloads from websites, and publications in technical journals.  A comparison of project expectations and performance. Discuss whether the goals and objectives of the Agreement have been met and what improvements are needed, if any.

  • Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

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