Sustainability Models Parties Involved: XXX Sample Clauses

Sustainability Models Parties Involved: XXX xx (Xxxxxx Xxxxxxxxx), XXXXXX (Xxxxxx Xxxxxxxx) Description of work: Through work supported by the EGI-InSPIRE project, which explores how the EGI ecosystem can ensure sustainability of services, this activity may include comparing sustainability strategies, ensuring alignment around the provided technology, better understanding of who uses the technology and opportunities for engaging business partners. Expected outcome: M5.1: Sustainability information documented and updated annually for inclusion in EGI’s strategic reports.
Sample 1Sample 2See All (4)
AutoNDA by SimpleDocs
Sustainability Models Parties Involved: XXX xx (Xxxxxx Xxxxxxxxx), XxxxxxxXxx (Xxxx-Xxxxx Xxxxx) Description of work: in work supported by EGI-InSPIRE explore how XXX.xx through its participants (NGIs and XXXXx) can help sustain the middleware provided by XxxxxxxXxx that it may rely on. This may include developing a joint strategy for engaging business partners, having a better understanding as to who uses the current middleware technology. Expected outcome: • M5.1: Explore joint sustainability strategies for the StratusLab middleware and EGI. Updated annually for inclusion in the deliverables related to EGI-InSPIRE and StratusLab Sustainability Plans
Sample 1
Sustainability Models Parties Involved: XXX xx (Xxxxxx Xxxxxxxxx), SAGA (Xxx Xxxxxxx) Description of work: in work supported by EGI-InSPIRE explore how XXX.xx through its participants (XXXx and XXXXx) can help sustain the software provided by SAGA that it relies on. This should include a periodic survey of which communities use the SAGA software, a survey of successful business models for sustaining open source projects and the identification of possible strategies to integrate the SAGA sustainability plan into the larger EGI sustainability plan. The possibility to develop joint strategy for engaging business partners should also be considered. Expected outcome: ▪ M5.1: Survey of user base for SAGA software in EGI. Updated annually. ▪ M5.2: Survey of sustainability strategies for open source projects. Explore joint sustainability strategies for the SAGA software and EGI. Updated annually for inclusion in the deliverables related to EGI-InSPIRE and SAGA Sustainability Plans, and their relation to SAGA's community activities
Sample 1
Sustainability Models Parties Involved: XXX xx (Xxxxxx Xxxxxxxxx, Xxxxxx Xxxxxxxx), IGE WP5 (Xxxxx Xxxxxxxx) 2 Party leading the activity is underlined. Description of work: in work supported by XXX-XxXXXXX, explore how XXX.xx through its participants (NGIs and EIROs) can help sustain the middleware provided by IGE that it relies on. This may include developing a joint strategy for engaging business partners, having a better understanding as to who uses the current middleware technology and how to account for its usage. Expected outcome:  M5.1: Make inventory of the existing software components to provide an initial assessment of usage and install base in EGI and opportunities for uptake and support outside of the EGI community  M5.2: Identify the services which may need extensions to their accounting mechanisms in order to record service usage  M5.3: Implement the accounting (defined in M5.2)
Sample 1

Related to Sustainability Models Parties Involved: XXX

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

  • Sustainability 49.1 The Contractor shall perform its obligations under the Call-off Contract in a manner so as to:

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.

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

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.

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

  • Sustainable Development 4.1 The Authority will review the Contractor’s Sustainable Development Policy Statement and Sustainable Development Plan submitted by the Contractor in accordance with the Schedule (Sustainable Development Requirements) and then at least annually thereafter.

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