Student Evaluations Student evaluations shall be completed by the end of the 12th week of the Fall semester.
TECHNICAL EVALUATION (a) Detailed technical evaluation shall be carried out by Purchase Committee pursuant to conditions in the tender document to determine the substantial responsiveness of each tender. For this clause, the substantially responsive bid is one that conforms to all the eligibility and terms and condition of the tender without any material deviation. The Institute’s determination of bid’s responsiveness is to be based on the contents of the bid itself without recourse to extrinsic evidence. The Institute shall evaluate the technical bids also to determine whether they are complete, whether required sureties have been furnished, whether the documents have been properly signed and whether the bids are in order.
(b) The technical evaluation committee may call the responsive bidders for discussion or presentation to facilitate and assess their understanding of the scope of work and its execution. However, the committee shall have sole discretion to call for discussion / presentation.
(c) Financial bids of only those bidders who qualify the technical criteria will be opened provided all other requirements are fulfilled.
(d) AIIMS Jodhpur shall have right to accept or reject any or all tenders without assigning any reasons thereof.
Incident Event and Communications Management a. Incident Management/Notification of Breach - DST shall develop, implement and maintain an incident response plan that specifies actions to be taken when DST or one of its subcontractors suspects or detects that a party has gained material unauthorized access to Fund Data or systems or applications containing any Fund Data (the “Response Plan”). Such Response Plan shall include the following:
i. Escalation Procedures - An escalation procedure that includes notification to senior managers and appropriate reporting to regulatory and law enforcement agencies. This procedure shall provide for reporting of incidents that compromise the confidentiality of Fund Data (including backed up data) to Fund via telephone or email (and provide a confirmatory notice in writing as soon as practicable); provided that the foregoing notice obligation is excused for such period of time as DST is prohibited by law, rule, regulation or other governmental authority from notifying Fund.
ii. Incident Reporting - DST will use commercially reasonable efforts to promptly furnish to Fund information that DST has regarding the general circumstances and extent of such unauthorized access to the Fund Data.
Student Evaluation a. The President of the College or the President’s designee shall be responsible for administering the student evaluation process.
b. Student evaluation packets for each class containing instruments and instructions shall be distributed to each faculty member by the first week of December during the fall semester and by the last week in April during the spring semester.
c. It is expressly agreed that the faculty member being evaluated shall not be present in the classroom when the student evaluation is being administered and that all instruction to students with regard to such student evaluation shall be included in writing on the instrument, provided further that the designated unit or non-unit professional shall return the student evaluation directly to the President of the College or the President’s designee. The administering of the student evaluation shall be the responsibility of the President of the College or the President’s designee who shall determine who among unit or non-unit professionals shall administer such student evaluation. Student evaluations shall be valid only if signed by the student; provided, however, that faculty members shall not be entitled to the identity of the student responding unless such student evaluation is used as a basis for dismissal or other disciplinary action and such will be communicated to the students.
d. The data from the student evaluation shall be tabulated and copies sent to the President of the College or the President’s designee. The raw data shall be retained by the College for a period of one (1) year during which time the faculty member shall have access thereto upon written request.
e. The President of the College or the President’s designee shall review the tabulated data and shall forward a data summary to the faculty member by January 23 for the fall semester and by June 15 for the spring semester.
f. The faculty member shall have seven (7) working days in which to respond to such data.
Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan.
9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan.
9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work.
9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right
9.2.4.1 Issue Directive Letters to Developer regarding traffic management
9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.
LABOUR MANAGEMENT RELATIONS 9:01 No employee or group of employees shall undertake to represent the Union at meetings with the Employer without the proper authorization of the Union. The Employer shall not meet with any employee or group of employees undertaking to represent the Union without the proper authorization of the Union. In representing an employee or group of employees, a representative of the Union shall be the spokesperson. In order that this may be carried out, the Union shall supply the Employer with the names of its Officers and representatives. Likewise the Employer shall supply the Union with a list of its Designated Authorities and Chairs where the Chair is not the Designated Authority. Neither the Union nor the Employer shall be required to recognize such representatives until written notification has been received.
9:02 The Union and the Employer acknowledge the mutual benefit of joint consultation and agree, therefore, that there shall be a joint labour/management committee consisting of three (3) representatives from and selected by each party. There shall be one (1) regularly scheduled Labour/Management Committee meeting in each four (4) month term or semester (January to April, May to August, September to December). In addition, meetings shall be arranged at the request of either party through the Labour Relations Department, by submitting in writing the topics to be discussed. Such meetings shall take place, at a mutually-agreeable time, within ten (10) working days of the receipt of the request for the meeting. Meetings shall not be used to discuss matters which are the subject of a grievance nor to discuss any matters which are, at the time, the subject of collective bargaining. The committee shall function in an advisory capacity only, making recommendations to the Union and/or the Employer with respect to its discussions and conclusions, and shall not have the power to add to or modify the terms of this agreement. A representative of each party shall be designated Co-Chairperson, and the two persons so designated shall alternate in presiding over meetings.
DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK
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.
Technical and Organisational Measures (1) Before the commencement of processing, the Supplier shall document the execution of the necessary Technical and Organisational Measures, set out in advance of the awarding of the Order or Contract, specifically with regard to the detailed execution of the contract, and shall present these documented measures to the Client for inspection. Upon acceptance by the Client, the documented measures become the foundation of the contract. Insofar as the inspection/audit by the Client shows the need for amendments, such amendments shall be implemented by mutual agreement.
(2) The Supplier shall establish the security in accordance with Article 28 Paragraph 3 Point c, and Article 32 GDPR in particular in conjunction with Article 5 Paragraph 1, and Paragraph 2 GDPR. The measures to be taken are measures of data security and measures that guarantee a protection level appropriate to the risk concerning confidentiality, integrity, availability and resilience of the systems. The state of the art, implementation costs, the nature, scope and purposes of processing as well as the probability of occurrence and the severity of the risk to the rights and freedoms of natural persons within the meaning of Article 32 Paragraph 1 GDPR must be taken into account. [Details in Appendix 1]
(3) The Technical and Organisational Measures are subject to technical progress and further development. In this respect, it is permissible for the Supplier to implement alternative adequate measures. In so doing, the security level of the defined measures must not be reduced. Substantial changes must be documented.
Banking Operations Enter into any new material line of business; change its material lending, investment, underwriting, risk and asset liability management and other material banking and operating policies, except as required by applicable law, regulation or policies imposed by any Governmental Authority; or file any application or make any contract with respect to branching or site location or branching or site relocation.
