Audit of Existing Content and Functionality By September 1, 2017, the Recipient will propose for OCR’s review and approval the identity and bona fides of an Auditor (corporation or individual) to audit all content and functionality on its website, including, but not limited to, the home page, all subordinate pages, and intranet pages and sites, to identify any online content or functionality that is inaccessible to persons with disabilities, including online content and functionality developed by, maintained by, or offered through a third party vendor or an open source. The Auditor will have sufficient knowledge and experience in website accessibility for people with disabilities to carry out all related tasks, including developing a Proposed Corrective Action Plan. The Audit will use the Benchmarks for Measuring Accessibility set out above, unless the Recipient receives prior permission from OCR to use a different standard as a benchmark. During the Audit, the Recipient will also seek input from members of the public with disabilities, including parents, students, employees, and others associated with the Recipient, and other persons knowledgeable about website accessibility, regarding the accessibility of its online content and functionality.
Publication of Procurement Contract 48.1 Within fourteen days after signing the contract, the Procuring Entity shall publish and publicize the awarded contract at its notice boards, entity website; and on the Website of the Authority in manner and format prescribed by the Authority. At the minimum, the notice shall contain the following information: a) name and address of the Procuring Entity; b) name and reference number of the contract being awarded, a summary of its scope and the selection method used; c) the name of the successful Tenderer, the final total contract price, the contract duration. d) dates of signature, commencement and completion of contract; e) names of all Tenderers that submitted Tenders, and their Tender prices as read out at Tender opening;
Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information.
Confidentiality of Vendor Data Vendor understands and agrees that by signing this Agreement, all Vendor Data is hereby released to TIPS, TIPS Members, and TIPS third-party administrators to effectuate Vendor’s TIPS Contract except as provided for herein. The Parties agree that Vendor Data is accessible by all TIPS Members as if submitted directly to that TIPS Member Customer for purchase consideration. If Vendor otherwise considers any portion of Vendor’s Data to be confidential and not subject to public disclosure pursuant to Chapter 552 Texas Gov’t Code (the “Public Information Act”) or other law(s) and orders, Vendor must have identified the claimed confidential materials through proper execution of the Confidentiality Claim Form which is required to be submitted as part of Vendor’s proposal resulting in this Agreement and incorporated by reference. The Confidentiality Claim Form included in Vendor’s proposal and incorporated herein by reference is the sole indicator of whether Vendor considers any Vendor Data confidential in the event TIPS receives a Public Information Request. If TIPS receives a request, any responsive documentation not deemed confidential by you in this manner will be automatically released. For Vendor Data deemed confidential by you in this manner, TIPS will follow procedures of controlling statute(s) regarding any claim of confidentiality and shall not be liable for any release of information required by law, including Attorney General determination and opinion. In the event that TIPS receives a written request for information pursuant to the Public Information Act that affects Vendor’s interest in any information or data furnished to TIPS by Vendor, and TIPS requests an opinion from the Attorney General, Vendor may, at its own option and expense, prepare comments and submit information directly to the Attorney General stating why the requested information is exempt from disclosure pursuant to the requirements of the Public Information Act. Vendor is solely responsible for submitting the memorandum brief and information to the Attorney General
End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).
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.
Proposed Policies and Procedures Regarding New Online Content and Functionality By October 31, 2017, the School will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the School to provide equally effective alternative access. The Plan for New Content will require the School, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternates are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the School’s online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the School will officially adopt, and fully implement the amended policies and procedures.
MONITORING FOR MATERIAL IRRECONCILABLE CONFLICTS AVIF agrees that its Board of Directors will monitor for the existence of any material irreconcilable conflict between the interests of the Participants in all separate accounts of life insurance companies utilizing AVIF ("Participating Insurance Companies"), including each Account, and participants in all qualified retirement and pension plans investing in AVIF ("Participating Plans"). LIFE COMPANY agrees to inform the Board of Directors of AVIF of the existence of or any potential for any such material irreconcilable conflict of which it is aware. The concept of a "material irreconcilable conflict" is not defined by the 1940 Act or the rules thereunder, but the Parties recognize that such a conflict may arise for a variety of reasons, including, without limitation: (a) an action by any state insurance or other regulatory authority; (b) a change in applicable federal or state insurance, tax or securities laws or regulations, or a public ruling, private letter ruling, no-action or interpretative letter, or any similar action by insurance, tax or securities regulatory authorities; (c) an administrative or judicial decision in any relevant proceeding; (d) the manner in which the investments of any Fund are being managed; (e) a difference in voting instructions given by variable annuity contract and variable life insurance contract Participants or by Participants of different Participating Insurance Companies; (f) a decision by a Participating Insurance Company to disregard the voting instructions of Participants; or (g) a decision by a Participating Plan to disregard the voting instructions of Plan participants. Consistent with the SEC's requirements in connection with exemptive orders of the type referred to in Section 5.1 hereof, LIFE COMPANY will assist the Board of Directors in carrying out its responsibilities by providing the Board of Directors with all information reasonably necessary for the Board of Directors to consider any issue raised, including information as to a decision by LIFE COMPANY to disregard voting instructions of Participants. LIFE COMPANY's responsibilities in connection with the foregoing shall be carried out with a view only to the interests of Participants.
Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient. (b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program. (c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only. (d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use. (e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient. (f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor. (g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient. (h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes. (i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5. (j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.
Breach by Authorized User An Authorized User’s breach shall not be deemed a breach of the Centralized Contract; rather, it shall be deemed a breach of the Authorized User’s performance under the terms and conditions of the Centralized Contract.
