Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-‐level domain strings across the Internet, certain top-‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.
Implementation of Agreement Each Party must promptly execute all documents and do all such acts and things as is necessary or desirable to implement and give full effect to the provisions of this 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.
Technical Proposal The technical proposal may be presented in free format. It shall not exceed ten pages, not counting the CVs. It shall respect the following page limit and structure: • Technical methodology (max. 7 pages) • Quality management (max. 1 page) • Project management (max. 1 page) • Resource management (proposal (max. 1 page) + CVs of experts)
LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION AND DISASSEMBLY You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.
PURPOSE AND IMPLEMENTATION This Umbrella Agreement (hereinafter referred to as the "Agreement" or "Umbrella Agreement") shall be for the purpose of collaborative research, development, and testing opportunities on various topics of mutual interest to enable advanced understanding of aeronautics, science, and space systems research and development and to provide workforce development in Science, Technology, Engineering, and Mathematics (STEM) while furthering NASA’s research and development goals. The Parties shall execute one (1) Annex Agreement (hereinafter referred to as the "Annex") concurrently with this Umbrella Agreement. The Parties may execute subsequent Annexes under this Umbrella Agreement consistent with the purpose and terms of this Umbrella Agreement. This Umbrella Agreement shall govern all Annexes executed hereunder; no Annex shall amend this Umbrella Agreement. Each Annex will detail the specific purpose of the proposed activity, responsibilities, schedule and milestones, and any personnel, property, or facilities to be utilized under the task. This Umbrella Agreement takes precedence over any Annexes. In the event of a conflict between the Umbrella Agreement and any Annex concerning the meaning of its provisions, and the rights, obligations and remedies of the Parties, the Umbrella Agreement is controlling.
Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.
Innovative Scheduling Schedules which are inconsistent with the Collective Agreement provisions may be developed in order to improve quality of working life, support continuity of resident care, ensure adequate staffing resources, and support cost-efficiency. The parties agree that such innovative schedules may be determined locally by the Home and the Union subject to the following principles:
Technical Proposals Technical proposal information will be streamlined, e.g., the Government anticipates written proposals consisting of thirty (30) pages or less stating compliance or exception to requirements, risks, assumptions and conflict of interest issues. Proposals shall not merely restate PWS/SOO requirements. Written technical proposals shall normally address: * Technical Approach and descriptive narrative of the contractor's understanding of the requested effort * PWS in response to a SOO * Integrated Master Plan (if applicable) * Integrated Master Schedule (if applicable) * Key Personnel Assigned * Quantities/Hours of Personnel by Labor Categories and narrative justification (if applicable) * Other Direct Costs (ODCs) (materials and supplies, travel, training, etc.(quantities and types only)) * Period of Performance * Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI) * Security (including clearance level) * Teaming Arrangement (including subcontracting; identify new ACAs) * Small Business Plan (if a large business) * Other Pertinent Data, such as assumptions made.
VISIBILITY OF FUNDING FROM THE OFFICIAL DEVELOPMENT ASSISTANCE Unless the SAIDC requests or agrees otherwise, any communication or publication made by the Final Beneficiary that relates to the action, including at conferences, seminars or in any information or promotional materials (such as brochures, leaflets, posters, presentations in electronic form, etc.), including tangible assets acquired from the project must: (a) indicate that the action has received funding from the Official Development Assistance, SlovakAid and (b) display the SlovakAid logo. When displayed in association with another logo, the SlovakAid logo must have appropriate prominence. The obligation to display the SlovakAid logo does not confer on the Final Beneficiary a right of exclusive use. The Final Beneficiary may not appropriate the SlovakAid logo or any similar trademark or logo, either by registration or by any other means. For the purposes of the first, second and third subparagraphs and under the conditions specified therein, the Final Beneficiary may use the SlovakAid logo without first obtaining permission from the SAIDC.
