Requirements for proposed Relevant Applications. (a) The Developer must give a notice with any Relevant Application, to the State, as applicable. The notice must:
Requirements for proposed Relevant Applications Sample Clauses
Related to Requirements for proposed Relevant Applications
Request for Proposals A State request inviting proposals for Goods or Services. This Contract shall be governed by the statutes, regulations and procedures of the State of Connecticut, Department of Administrative Services.
Request for Proposal Once the project development stage and joint scope meeting have produced a County approved Detailed Scope of Work, the County will issue a Request for Proposal (RFP) to the Contractor. The RFP will include the Scope of Work approved by the County and other pertinent information with regards to scheduling, submittals, shop drawings and sketch requirements. The Contractor agrees to prepare and submit a JOC Task Order Proposal of Work.
Application for Promotion Employees who have successfully completed their initial probationary period may make application for any Job Posting provided they meet the minimum, stated qualifications for the involved position; provided, however, that employees who have failed a promotional probationary period in a classification shall not be permitted to take an examination for promotion to that classification within twelve (12) months of the date of such failure.
Accurate and Timely Submission of Reports a) The reports and administrative fees shall be accurate and timely and submitted in accordance with the due dates specified in this section. Vendor shall correct any inaccurate reports or administrative fee payments within three (3) business days upon written notification by DIR. Vendor shall deliver any late reports or late administrative fee payments within three (3) business days upon written notification by DIR. If Vendor is unable to correct inaccurate reports or administrative fee payments or deliver late reports and fee payments within three
Invoice Submission The Contractor shall accept payment of invoices via EFT. Invoice submission information shall be contained in each individual Order. Payment of invoices will be made by the payment office designated in each individual Order.
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.
Third-Party Applications Oracle or third party providers may offer Third Party Applications. Except as expressly set forth in the Estimate/Order Form, Oracle does not warrant any such Third Party Applications, regardless of whether or not such Third Party Applications are provided by a third party that is a member of an Oracle partner program or otherwise designated by Oracle as “Built For NetSuite,” "certified," "approved" or “recommended.” Any procurement by Customer of such Third Party Applications or services is solely between Customer and the applicable third party provider. Customer may not use Third Party Applications to enter and/or submit transactions to be processed and/or stored in the NetSuite CPQ, unless Customer has procured the applicable subscription to the NetSuite CPQ for such use and access. Oracle is not responsible for any aspect of such Third Party Applications that Customer may procure or connect to through the NetSuite CPQ, or any interoperation, descriptions, promises, or other information related to the foregoing. If Customer installs or enables Third Party Applications for use with the NetSuite CPQ, Customer agrees that Oracle may enable such third party providers to access Customer Data for the interoperation of such Third Party Applications with the NetSuite CPQ, and any exchange of data or other interaction between Customer and a third party provider is solely between Customer and such third party provider pursuant to a separate privacy policy or other terms governing Customer’s access to or use of the Third Party Applications. Oracle shall not be responsible for any disclosure, modification or deletion of Customer Data resulting from any such access by Third Party Applications or third party providers. No procurement of such Third Party Applications is required to use the NetSuite CPQ. If Customer was referred to Oracle by a member of one of Oracle’s partner programs, Customer hereby authorizes Oracle to provide such member or its successor entity with access to Customer’s business information related to the procurement and use of the NetSuite CPQ pursuant to this Agreement, including but not limited to User names and email addresses, support cases and billing/payment information.
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.
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.
