License Compliance HP may audit Customer compliance with the software license terms. Upon reasonable notice, HP may conduct an audit during normal business hours (with the auditor’s costs being at HP’s expense). If an audit reveals underpayments then Customer will pay to HP such underpayments. If underpayments discovered exceed five (5) percent of the contract price, Customer will reimburse HP for the auditor costs.
License Key 2.5. The Application Software may include an embedded security system which if provided must be used together with a license key. The license key may limit the use of the Application Software to the applicable Use Level and prevent a single User from using more than one workstation at the same time and is valid for a certain period of time following which the license key must be renewed. Customer is solely responsible for any cost or loss arising out of Customer’s failure or delay to renew the license key.
Software compliance Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive license (like MIT, BSD, Apache 2.0,...). ● The license should provide unlimited access rights to the EGI community. ● Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the EGI organisation in GitHub13.) All releases should be appropriately tagged. ● Adopt best practices: ○ Defining and enforcing code style guidelines. ○ Using Semantic Versioning. ○ Using a Configuration Management frameworks such as Ansible. ○ Taking security aspects into consideration through at every point in time. ○ Having automated testing in place. ○ Using code reviewing. 9 xxxxx://xxx.xxx.xx/about/policy/policies_procedures.html 10 xxxxx://xxxx.xxx.xx/wiki/OMB 11 xxxx://xxx.xxx.xx/ 12 xxxxx://xxx.xxx.xx/portal/index.php?Page_Type=NGI&id=4 13 xxxxx://xxxxxx.xxx/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.
FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:
License Scope Licensee is granted a non-exclusive, perpetual license to use, execute, reproduce, display, perform, or merge the Product within its business enterprise in the United States up to the maximum licensed capacity stated on the Purchase Order. Product may be accessed, used, executed, reproduced, displayed or performed up to the capacity measured by the applicable licensing unit stated on the Purchase Order (i.e., payroll size, number of employees, CPU, MIPS, MSU, concurrent user, workstation). Licensee shall have the right to use and distribute modifications or customizations of the Product to and for use by any Authorized Users otherwise licensed to use the Product, provided that any modifications, however extensive, shall not diminish Licensor’s proprietary title or interest. No license, right or interest in any trademark, trade name, or service xxxx is granted hereunder.
License Keys The Software, when used in production, requires a License Key to install or access it. You are responsible for the use of any License Key(s) assigned to you and must not share the License Key(s) with any third party. If your License Key is stolen, or if you suspect any improper or illegal usage of your License Key, you should promptly notify Acumatica of such occurrence. A replacement License Key will be issued to you and the compromised License Key will be disabled.
Program Compliance The School Board shall be responsible for monitoring the program to provide technical assistance and to ensure program compliance.
Sublicense (a) The license granted in Paragraph 2.1 includes the right of LICENSEE to grant Sublicenses to third parties during the Term but only for as long as the license to Patent Rights is exclusive.
CEQA Compliance The District has complied with all assessment requirements imposed upon it by the California Environmental Quality Act (Public Resource Code Section 21000 et seq. (“CEQA”) in connection with the Project, and no further environmental review of the Project is necessary pursuant to CEQA before the construction of the Project may commence.
Contractor Licensing, etc. Notwithstanding Section 14.c, District may terminate this Contract immediately by written notice to Contractor upon denial, suspension, revocation, or non-renewal of any license, permit, or certificate that Contractor must hold to provide services under this Contract.
