DHS Seal, Logo, and Flags The Contractor shall not use the Department of Homeland Security (DHS) seal(s), logos, crests, or reproductions of flags or likeness of DHS agency officials without specific FEMA pre-approval.
Articles of Organization This Company is organized pursuant to the provisions of the COLORADO LIMITED LIABILITY COMPANY ACT (the “Act”, codified in Colorado Revised Statues §7-80-100 et seq. as it may be amended from time to time) and pursuant to Articles of Organization filed with the Secretary of State on January 24, 2014. The rights and obligations of the Company and the Members shall be provided in this Operating Agreement.
Partnership Name The name of the Partnership is “OZ Management LP.” The name of the Partnership may be changed from time to time by the General Partner.
Principal Place of Business; State of Organization Borrower will not cause or permit any change to be made in its name, identity (including its trade name or names), place of organization or formation (as set forth in Section 4.1.36 hereof) or Borrower’s corporate or partnership or other structure unless Borrower shall have first notified Lender in writing of such change at least thirty (30) days prior to the effective date of such change, and shall have first taken all action required by Lender for the purpose of perfecting or protecting the lien and security interests of Lender pursuant to this Agreement, and the other Loan Documents and, in the case of a change in Borrower’s structure, without first obtaining the prior written consent of Lender, which consent may given or denied in Lender’s sole discretion. Upon Lender’s request, Borrower shall, at Borrower’s sole cost and expense, execute and deliver additional security agreements and other instruments which may be necessary to effectively evidence or perfect Lender’s security interest in the Property as a result of such change of principal place of business or place of organization. Borrower’s principal place of business and chief executive office, and the place where Borrower keeps its books and records, including recorded data of any kind or nature, regardless of the medium or recording, including software, writings, plans, specifications and schematics, has been for the preceding four months (or, if less, the entire period of the existence of Borrower) and will continue to be the address of Borrower set forth at the introductory paragraph of this Agreement (unless Borrower notifies Lender in writing at least thirty (30) days prior to the date of such change). Borrower shall promptly notify Lender of any change in its organizational identification number. If Borrower does not now have an organizational identification number and later obtains one, Borrower promptly shall notify Lender of such organizational identification number.
Partnerships and Joint Ventures No Loan Party shall become a general partner in any general or limited partnership or a joint venturer in any joint venture.
Delivery of Organizational Documents On or before the Closing Date, Borrower shall deliver or cause to be delivered to Lender copies certified by Borrower of all organizational documentation related to Borrower and/or the formation, structure, existence, good standing and/or qualification to do business, as Lender may request in its sole discretion, including, without limitation, good standing certificates, qualifications to do business in the appropriate jurisdictions, resolutions authorizing the entering into of the Loan and incumbency certificates as may be requested by Lender.
Mobile Gas Service Corp 350 U.S. 332 (1956) and Federal Power Commission v. Sierra Pacific Power Co., 350 U.S. 348 (1956) , and clarified by Xxxxxx Xxxxxxx Capital Group, Inc. v.
File Naming Conventions Files will be named according to the following convention: {gTLD}_{YYYY-MM-DD}_{type}_S{#}_R{rev}.{ext} where: {gTLD} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII-compatible form (A-Label) must be used; {YYYY-MM-DD} is replaced by the date corresponding to the time used as a timeline watermark for the transactions; i.e. for the Full Deposit corresponding to 2009-08-02T00:00Z, the string to be used would be “2009-08-02”; {type} is replaced by: “full”, if the data represents a Full Deposit; “diff”, if the data represents a Differential Deposit; “thin”, if the data represents a Bulk Registration Data Access file, as specified in Section 3 of Specification 4; {#} is replaced by the position of the file in a series of files, beginning with “1”; in case of a lone file, this must be replaced by “1”. {rev} is replaced by the number of revision (or resend) of the file beginning with “0”: {ext} is replaced by “sig” if it is a digital signature file of the quasi-homonymous file. Otherwise it is replaced by “ryde”.
Cloud storage DSHS Confidential Information requires protections equal to or greater than those specified elsewhere within this exhibit. Cloud storage of Data is problematic as neither DSHS nor the Contractor has control of the environment in which the Data is stored. For this reason: (1) DSHS Data will not be stored in any consumer grade Cloud solution, unless all of the following conditions are met: (a) Contractor has written procedures in place governing use of the Cloud storage and Contractor attests in writing that all such procedures will be uniformly followed. (b) The Data will be Encrypted while within the Contractor network. (c) The Data will remain Encrypted during transmission to the Cloud. (d) The Data will remain Encrypted at all times while residing within the Cloud storage solution. (e) The Contractor will possess a decryption key for the Data, and the decryption key will be possessed only by the Contractor and/or DSHS. (f) The Data will not be downloaded to non-authorized systems, meaning systems that are not on either the DSHS or Contractor networks. (g) The Data will not be decrypted until downloaded onto a computer within the control of an Authorized User and within either the DSHS or Contractor’s network. (2) Data will not be stored on an Enterprise Cloud storage solution unless either: (a) The Cloud storage provider is treated as any other Sub-Contractor, and agrees in writing to all of the requirements within this exhibit; or, (b) The Cloud storage solution used is FedRAMP certified. (3) If the Data includes protected health information covered by the Health Insurance Portability and Accountability Act (HIPAA), the Cloud provider must sign a Business Associate Agreement prior to Data being stored in their Cloud solution.
Notice of Organizational Change Grantee will submit notice to the SUD email box, XxxxxxxxxXxxxx.Xxxxxxxxx@xxxx.xxxxx.xx.xx and Substance Use Xxxxxxxx@xxxx.xxxxx.xx.xx within ten (10) business days of any change to Xxxxxxx's name, contact information, organizational structure, such as merger, acquisition, or change in form of business, legal standing, or authority to do business in Texas.