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.
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)
Technical changes The parties agree to make any technical changes that are mutually agreed prior to the going out for ratification. The parties on signing this document acknowledge, subject to any subsequent agreed editorial and technical changes, that this reflects the agreements reached in the settlement of the Primary Principals’ Collective Agreement 2019-2022. Signed in Wellington on 9 August 2019: Xxxxx Xxxxxx Advocate for NZEI Te Riu Roa Xxxx Xxxxxxxxxx Advocate for the Secretary for Education Witnessed: for NZSTA Annex 1
CONTRACTOR NAME CHANGE An amendment is required to change the Contractor's name as listed on this Agreement. Upon receipt of legal documentation of the name change the State will process the amendment. Payment of invoices presented with a new name cannot be paid prior to approval of said amendment.
Additional proposals If the Company at any time during the continuance of this Agreement desires to modify expand or otherwise vary its activities carried on pursuant to this Agreement beyond those specified in any approved proposal, it shall give notice of such desire to the Minister and within 2 months after giving such notice shall submit to the Minister detailed proposals in respect of such modifications expansions or variations and such other matters as the Minister may require. The provisions of clause 4 and 5 (including (for the avoidance of doubt) clause 5(9)) shall apply, the necessary changes being made, to proposals submitted pursuant to this clause.
TECHNICAL TASKS Products that require a draft version are indicated by marking “(draft and final)” after the product name in the “Products” section of the task/subtask. If “(draft and final)” does not appear after the product name, only a final version of the product is required. Subtask 1.1 (Products) describes the procedure for submitting products to the CAM.
Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
TECHNICAL GUIDANCE LETTERS In the sole discretion of the System Agency, and in conformance with federal and state law, the System Agency may issue instructions, clarifications, or interpretations as may be required during work performance in the form of a Technical Guidance Letter (TGL). A TGL must be in writing, and may be delivered by regular mail, electronic mail, or facsimile transmission. Any TGL issued by the System Agency will be incorporated into the Contract by reference for all purposes when it is issued.
Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.
