How to Obtain Warranty Service The Warranty Holder must inspect the Flooring for Manufacturing Defects caused by improper milling, grading, staining, and coating, and report any such defects to Cali Bamboo, prior to installation of the Flooring. To obtain warranty service, the Warranty Holder must contact Cali Bamboo’s Customer Experience Department: xxxxxxxxxxxxxxx@xxxxxxxxxx.xxx/ 000- 000-0000. Warranty claims must be received within 30 calendar days after the Warranty Holder identifies the Manufacturing Defect or other basis for a warranty claim. To be covered under this Cali Bamboo limited warranty, the Warranty Holder must provide documentation of sales order and proof that the Flooring was properly installed in accordance with the Installation Guide (defined below). Cali Bamboo reserves the right to retain a certified and independent National Wood Flooring Association inspector (“NWFA Inspector”) to verify the Warranty Holder’s warranty claims. The determination of the NWFA Inspector regarding the warranty claim is not binding on either Cali Bamboo or on the Warranty Holder. A determination that does not verify the warranty claim shall not affect the Warranty Holder’s right to submit its claim to arbitration in accordance with the terms of the Arbitration Agreement (as defined in Cali Bamboo’s Terms and Conditions of Purchase). The performance of the inspection, however, if requested by Xxxx Xxxxxx and assuming that Xxxx Xxxxxx advances the full cost of the inspection as described above, is a requirement for the Warranty Holder to submit a warranty claim to arbitration under the Arbitration Agreement. For specific instructions on how to obtain warranty service for defective Flooring, visit the Cali Bamboo website xxxxx://xxx.xxxxxxxxxx.xxx/flooring-warranty/. This limited warranty covers Flooring that is both (i) installed with strict adherence to Cali Bamboo’s Odyssey Engineered flooring installation guide found online at xxxxx://xxx.xxxxxxxxxx.xxx/flooring-installation/ (the “Installation Guide”) and
Data Return and Destruction of Data (a) Protecting PII from unauthorized access and disclosure is of the utmost importance to the EA, and Contractor agrees that it is prohibited from retaining PII or continued access to PII or any copy, summary or extract of PII, on any storage medium (including, without limitation, in secure data centers and/or cloud-based facilities) whatsoever beyond the period of providing Services to the EA, unless such retention is either expressly authorized for a prescribed period by the Service Agreement or other written agreement between the Parties, or expressly requested by the EA for purposes of facilitating the transfer of PII to the EA or expressly required by law. As applicable, upon expiration or termination of the Service Agreement, Contractor shall transfer PII, in a format agreed to by the Parties to the EA. (b) If applicable, once the transfer of PII has been accomplished in accordance with the EA’s written election to do so, Contractor agrees to return or destroy all PII when the purpose that necessitated its receipt by Contractor has been completed. Thereafter, with regard to all PII (including without limitation, all hard copies, archived copies, electronic versions, electronic imaging of hard copies) as well as any and all PII maintained on behalf of Contractor in a secure data center and/or cloud-based facilities that remain in the possession of Contractor or its Subcontractors, Contractor shall ensure that PII is securely deleted and/or destroyed in a manner that does not allow it to be retrieved or retrievable, read or reconstructed. Hard copy media must be shredded or destroyed such that PII cannot be read or otherwise reconstructed, and electronic media must be cleared, purged, or destroyed such that the PII cannot be retrieved. Only the destruction of paper PII, and not redaction, will satisfy the requirements for data destruction. Redaction is specifically excluded as a means of data destruction. (c) Contractor shall provide the EA with a written certification of the secure deletion and/or destruction of PII held by the Contractor or Subcontractors. (d) To the extent that Contractor and/or its subcontractors continue to be in possession of any de-identified data (i.e., data that has had all direct and indirect identifiers removed), they agree not to attempt to re-identify de-identified data and not to transfer de-identified data to any party.
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.
New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.
Geographic Area and Sector Specific Allowances, Conditions and Exceptions The following allowances and conditions shall apply where relevant. Where the Employer does work which falls under the following headings, the Employer agrees to pay and observe the relevant respective conditions and/or exceptions set out below in each case.
Usage for Voice Mail Message Service Rated Incollects (originated in BellSouth and from other companies) can also be on Optional Daily Usage File. Rated Incollects will be intermingled with BellSouth recorded rated and unrated usage. Rated Incollects will not be packed separately.
Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements
General Conditions Applicable to Option to Build If the Interconnection Customer assumes responsibility for the design, procurement and construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades, (1) the Interconnection Customer shall engineer, procure equipment, and construct the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades (or portions thereof) using Good Utility Practice and using standards and specifications provided in advance by the Participating TO; (2) The Interconnection Customer’s engineering, procurement and construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades shall comply with all requirements of law to which the Participating TO would be subject in the engineering, procurement or construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades; (3) the Participating TO shall review, and the Interconnection Customer shall obtain the Participating TO’s approval of, the engineering design, equipment acceptance tests, and the construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades, which approval shall not be unreasonably withheld, and the CAISO may, at its option, review the engineering design, equipment acceptance tests, and the construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades; (4) prior to commencement of construction, the Interconnection Customer shall provide to the Participating TO, with a copy to the CAISO for informational purposes, a schedule for construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades, and shall promptly respond to requests for information from the Participating TO; (5) at any time during construction, the Participating TO shall have the right to gain unrestricted access to the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades and to conduct inspections of the same; (6) at any time during construction, should any phase of the engineering, equipment procurement, or construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades not meet the standards and specifications provided by the Participating TO, the Interconnection Customer shall be obligated to remedy deficiencies in that portion of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades; (7) the Interconnection Customer shall indemnify the CAISO and Participating TO for claims arising from the Interconnection Customer's construction of the Participating TO's Interconnection Facilities and Stand Alone Network Upgrades under the terms and procedures applicable to Article 18.1
CERTIFICATION PROHIBITING DISCRIMINATION AGAINST FIREARM AND AMMUNITION INDUSTRIES (Texas law as of September 1, 2021) By submitting a proposal to this Solicitation, you certify that you agree, when it is applicable, to the following required by Texas law as of September 1, 2021: If (a) company is not a sole proprietorship; (b) company has at least ten (10) full-time employees; (c) this contract has a value of at least $100,000 that is paid wholly or partly from public funds; (d) the contract is not excepted under Tex. Gov’t Code § 2274.003 of SB 19 (87th leg.); and (e) governmental entity has determined that company is not a sole-source provider or governmental entity has not received any bids from a company that is able to provide this written verification, the following certification shall apply; otherwise, this certification is not required. Pursuant to Tex. Gov’t Code Ch. 2274 of SB 19 (87th session), the company hereby certifies and verifies that the company, or association, corporation, partnership, joint venture, limited partnership, limited liability partnership, or limited liability company, including a wholly owned subsidiary, majority-owned subsidiary parent company, or affiliate of these entities or associations, that exists to make a profit, does not have a practice, policy, guidance, or directive that discriminates against a firearm entity or firearm trade association and will not discriminate during the term of this contract against a firearm entity or firearm trade association. For purposes of this contract, “discriminate against a firearm entity or firearm trade association” shall mean, with respect to the entity or association, to: “ (1) refuse to engage in the trade of any goods or services with the entity or association based solely on its status as a firearm entity or firearm trade association; (2) refrain from continuing an existing business relationship with the entity or association based solely on its status as a firearm entity or firearm trade association; or (3) terminate an existing business relationship with the entity or association based solely on its status as a firearm entity or firearm trade association. See Tex. Gov’t Code § 2274.001(3) of SB 19. “Discrimination against a firearm entity or firearm trade association” does not include: “ (1) the established policies of a merchant, retail seller, or platform that restrict or prohibit the listing or selling of ammunition, firearms, or firearm accessories; and (2) a company’s refusal to engage in the trade of any goods or services, decision to refrain from continuing an existing business relationship, or decision to terminate an existing business relationship to comply with federal, state, or local law, policy, or regulations or a directive by a regulatory agency, or for any traditional business reason that is specific to the customer or potential customer and not based solely on an entity’s or association’s status as a firearm entity or firearm trade association.” See Tex. Gov’t Code § 2274.001(3) of SB 19.
