Internship/Revature Readiness Program (RRP) Sample Clauses

Internship/Revature Readiness Program (RRP) a. Trainee Internship/RRP is for a minimum period of three (3) months. During this period, Xxxxxxx will receive a stipend of Rs.5,000/- (Rupees Five Thousand Only) per month. He/ She will be provided with a mentor during the Internship/RRP period b. This Program is a 12-week instructor-led training program designed to provide Trainees with skills and knowledge that can be built upon advance and acquire the skills of a software developer. The training program is a residential program, provided at no cost to eligible Trainees accepted into the training program. c. During the term, Trainee undertake to devote best efforts, knowledge and skill and devote substantially all their working time (at least 40 hours a week) and attention to the performance of duties. d. During Training, trainees will learn the skills that will set them on the career path, working on the most highly sought-after technologies in the tech industry. e. As part of our ongoing commitment to continued learning and development, Company has designed this Internship/RRP to be a mentor-led training program that enables trainees to get introduced to various emerging technologies. As they are entering the IT Industry, it is important to have a strong foundation in Programming languages, Databases and Operating Systems and Behavioral skills. f. Trainee performance will be tracked periodically and provide feedback when necessary. Upon successful completion of 12-week Internship/Revature Readiness Program, trainees will be required to clear the final review with Revature’ s Client(s) that includes an assessment and one to one interaction. g. Detailed description of training details is given in the Training Agreement. h. All Trainees will be required to agree to, abide by and adhere to the rules of use and policies in (or referenced in) Training Agreement. i. Attendance: Trainers will accurately report trainees training hours and Company will not encourage, require, or permit trainees to skip trainings or absence from trainings or falsify training hours.
Sample 1
AutoNDA by SimpleDocs

Related to Internship/Revature Readiness Program (RRP)

  • Scope of Interconnection Service 1.3.1 The NYISO will provide Energy Resource Interconnection Service and Capacity Resource Interconnection Service to Interconnection Customer at the Point of Interconnection. 1.3.2 This Agreement does not constitute an agreement to purchase or deliver the Interconnection Customer’s power. The purchase or delivery of power and other services that the Interconnection Customer may require will be covered under separate agreements, if any, or applicable provisions of NYISO’s or Connecting Transmission Owner’s tariffs. The Interconnection Customer will be responsible for separately making all necessary arrangements (including scheduling) for delivery of electricity in accordance with the applicable provisions of the ISO OATT and Connecting Transmission Owner’s tariff. The execution of this Agreement does not constitute a request for, nor agreement to, provide Energy, any Ancillary Services or Installed Capacity under the NYISO Services Tariff or any Connecting Transmission Owner’s tariff. If Interconnection Customer wishes to supply or purchase Energy, Installed Capacity or Ancillary Services, then Interconnection Customer will make application to do so in accordance with the NYISO Services Tariff or Connecting Transmission Owner’s tariff.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

  • Switching and Tagging Rules Each Party shall provide the other Parties a copy of its switching and tagging rules that are applicable to the other Parties’ activities. Such switching and tagging rules shall be developed on a non-discriminatory basis. The Parties shall comply with applicable switching and tagging rules, as amended from time to time, in obtaining clearances for work or for switching operations on equipment.

  • Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Interconnection Customer Authority Consistent with Good Utility Practice, this LGIA, and the CAISO Tariff, the Interconnection Customer may take actions or inactions with regard to the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities during an Emergency Condition in order to (i) preserve public health and safety, (ii) preserve the reliability of the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities,

  • Mail Order Catalog Warnings In the event that, the Settling Entity prints new catalogs and sells units of the Products via mail order through such catalogs to California consumers or through its customers, the Settling Entity shall provide a warning for each unit of such Product both on the label in accordance with subsection 2.4 above, and in the catalog in a manner that clearly associates the warning with the specific Product being purchased. Any warning provided in a mail order catalog shall be in the same type size or larger than other consumer information conveyed for such Product within the catalog and shall be located on the same display page of the item. The catalog warning may use the Short-Form Warning content described in subsection 2.3(b) if the language provided on the Product label also uses the Short-Form Warning.

  • Power Factor Design Criteria (Reactive Power A wind generating plant shall maintain a power factor within the range of 0.95 leading to 0.95 lagging, measured at the Point of Interconnection as defined in this LGIA, if the ISO’s System Reliability Impact Study shows that such a requirement is necessary to ensure safety or reliability. The power factor range standards can be met using, for example without limitation, power electronics designed to supply this level of reactive capability (taking into account any limitations due to voltage level, real power output, etc.) or fixed and switched capacitors if agreed to by the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, or a combination of the two. The Developer shall not disable power factor equipment while the wind plant is in operation. Wind plants shall also be able to provide sufficient dynamic voltage support in lieu of the power system stabilizer and automatic voltage regulation at the generator excitation system if the System Reliability Impact Study shows this to be required for system safety or reliability.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.50 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0150. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. The sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Master Contract Sales Report. Upon request, Contractor shall provide to Enterprise Services a detailed annual Master Contract sales report. Such report shall include, at a minimum: Product description, part number or other Product identifier, per unit quantities sold, and Master Contract price. This report must be provided in an electronic format that can be read by compatible with MS Excel. Small Business Inclusion. Upon Request by Enterprise Services, Contractor shall provide, within thirty (30) days, an Affidavit of Amounts Paid. Such Affidavit of Amounts Paid either shall state, if applicable, that Contractor still maintains its MWBE certification or state that its subcontractor(s) still maintain(s) its/their MWBE certification(s) and specify the amounts paid to each certified MWBE subcontractor under this Master Contract. Contractor shall maintain records supporting the Affidavit of Amounts Paid in accordance with this Master Contract’s records retention requirements.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!