SECURITISATIONS Sample Clauses

SECURITISATIONS. So far as it is aware, having made all due and careful enquiries as at the date of the KPMG Securitisation Paper, no member of the Group had any rights, obligations or liabilities in respect of the Securitisations or the Securitisation Group other than as set out in the KPMG Securitisation Paper, the Accountants Report, the Legal Reports, the Information Pack and Securitisation Documents.
AutoNDA by SimpleDocs
SECURITISATIONS except for ABCP programmes and transactions, that meet the requirements set out in Articles 20, 21 and 22 ▌shall be considered ▌STS ▌.

Related to SECURITISATIONS

  • Securitization In addition to any other assignment permitted pursuant to this Section, Loan Parties hereby acknowledge that (x) the Lenders, their Affiliates and Approved Funds (“Lender Parties”) may sell or securitize the Loans (a “Securitization”) through the pledge of the Loans as collateral security for loans to a Lender Party or the assignment or issuance of direct or indirect interests in the Loans (such as, for instance, collateralized loan obligations), and (y) such Securitization may be rated by a rating agency. The Loan Parties shall reasonably cooperate with the Lender Parties to effect the Securitization including, without limitation, by (a) amending this Agreement and the other Loan Documents, and executing such additional documents, as reasonably requested by the Lenders in connection with the Securitization; provided that (i) any such amendment or additional documentation does not impose material additional costs on Borrower and (ii) any such amendment or additional documentation does not materially adversely affect the rights, or materially increase the obligations, of Borrower under the Loan Documents or change or affect in a manner adverse to Borrower the financial terms of the Loans, (b) providing such information as may be reasonably requested by the Lenders or rating agencies in connection with the rating of the Loans or the Securitization, and (c) providing a certificate (i) agreeing to indemnify the Lender Parties, or any party providing credit support or otherwise participating in the Securitization, including any investors in a securitization entity (collectively, the “Securitization Parties”) for any losses, claims, damages or liabilities (the “Securitization Liabilities”) to which the Lender Parties or such Securitization Parties may become subject insofar as the Securitization Liabilities arise out of or are based upon any untrue statement or alleged untrue statement of any material fact contained in any Loan Document or in any writing delivered by or on behalf of any Loan Party to the Lender Partiers in connection with any Loan Document or arise out of or are based upon the omission or alleged omission to state therein a material fact required to be stated therein, or necessary in order to make the statements therein, in light of the circumstances under which they were made, not misleading, and such indemnity shall survive any transfer by the Lenders or their successors or assigns of the Loans, and (ii) agreeing to reimburse the Lender Parties and the other Securitization Parties for any legal or other expenses reasonably incurred by such Persons in connection with defending the Securitization Liabilities.

  • Special Situations XXXXXXX BENEFICIARY agrees to inform AGENCY within one (1) business day of any circumstances or events which may reasonably be considered to jeopardize its capability to continue to meet its obligations under the terms of this Agreement. Incidents may include, but are not limited to, those resulting in injury, media coverage or public reaction that may have an impact on the AGENCY’S or GRANTEE BENEFICIARY’S ability to protect and serve its participants, or other significant effect on the AGENCY or GRANTEE BENEFICIARY. Incidents shall be reported to the designated AGENCY contact below by phone or email only. Incident report information shall not include any identifying information of the participant.

  • Finance 3.1 This contract is conditional on the Buyer obtaining approval of a loan for the Finance Amount from the Financier by the Finance Date on terms satisfactory to the Buyer. The Buyer must take all reasonable steps to obtain approval. 3.2 The Buyer must give notice to the Seller that: (1) approval has not been obtained by the Finance Date and the Buyer terminates this contract; or (2) the finance condition has been either satisfied or waived by the Buyer. 3.3 The Seller may terminate this contract by notice to the Buyer if notice is not given under clause 3.2 by 5pm on the Finance Date. This is the Seller’s only remedy for the Buyer’s failure to give notice. 3.4 The Seller’s right under clause 3.3 is subject to the Buyer’s continuing right to give written notice to the Seller of satisfaction, termination or waiver pursuant to clause 3.2.

  • Tourism In this field, the objective of the cooperation will be to strengthen the promotion of the tourist potentialities of the Parties, as well as to facilitate the information exchange and the conservation of natural and cultural attractions.

  • 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.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • 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.

  • Security Management The Contractor shall comply with the requirements of the DOD 5200.1-M and the DD Form 254. Security of the Contractor’s electronic media shall be in accordance with the above documents. Effective Program Security shall require the Contractor to address Information Security and Operations Security enabled by the Security Classification Guides. The Contractor’s facility must be able to handle and store material up to the Classification Level as referenced in Attachment J-01, DD Form 254.

  • Workload Management 11.1 The parties to this Agreement acknowledge that employees and management have a responsibility to maintain a balanced workload and recognise the adverse affects that excessive workloads may have on employee/s and the quality of resident/client care. 11.2 To ensure that employee concerns involving excessive workloads are effectively dealt with by Management the following procedures should be applied: (a) Step 1: In the first instance, employee/s should discuss the issue with their immediate supervisor and, where appropriate, explore solutions. (b) Step 2: If a solution cannot be identified and implemented, the matter should be referred to an appropriate senior manager for further discussion. (c) Step 3: If a solution still cannot be identified and implemented, the matter should be referred to the Facility Manager for further discussion. (d) Step 4: The outcome of the discussions at each level and any proposed solutions should be recorded in writing and fed back to the effected employees. 11.3 Workload management must be an agenda item at staff meetings on at least a quarterly basis. Items in relation to workloads must be recorded in the minutes of the staff meeting, as well as actions to be taken to resolve the workloads issue/s. Resolution of workload issues should be based on the following criteria including but not limited to: (a) Clinical assessment of residents’ needs; (b) The demand of the environment such as facility layout; (c) Statutory obligation, (including, but not limited to, work health and safety legislation); (d) The requirements of nurse regulatory legislation; (e) Reasonable workloads (such as roster arrangements); (f) Accreditation standards; and (g) Budgetary considerations. 11.4 If the issue is still unresolved, the employee/s may advance the matter through Clause 9 Dispute Resolution Procedure. Arbitration of workload management issues may only occur by agreement of the employer and the employee representative, which may include the union/s.

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

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