Application Functionality Sample Clauses

Application Functionality. 9 1. Encryption; 10 a. Application is required to use encryption to protect sensitive data in both storage and 11 transit wherever technically possible 12 b. All encryption methods will be for storage and transit of data need to be defined by the 13 CONTRACTOR. 14 c. All data transmissions must be encrypted using a FIPS 140-2 certified algorithm, such 15 as Advanced Encryption Standard (AES), with a 128bit key or higher. Encryption can be end to end at 16 the network level. This requirement pertains to any regulated data in motion such as website access and 17 file transfers. 18 2. Network Communication: CONTRACTOR will provide information related to standards 19 and requirements for the deployment of the application including methods of secure implementation and 20 port requirements 21 3. Access Management; 22 a. Application/system controls access to and within the system at multiple levels (e.g. per 23 user, per user role, per area, per section of the chart) through a consistent mechanism of identification 24 and authentication of all users in accordance with the ‘Role Based Access Control’ (RBAC) standard. 25 b. Application will support measures to define, attach, modify and remove access rights 26 for all classes of users. 27 c. CONTRACTOR will work toward meeting the evolving standards for authentication as 28 they become available 29 d. Application will have the ability to create unique user accounts and passwords. 30 e. The application will disable or lock accounts after 90 days of inactivity or a date range 31 approved by COUNTY. 32 f. CONTRACTOR hosted solution will support client side certificates to restrict access to 33 known pc’s only.
Sample 1
AutoNDA by SimpleDocs
Application Functionality. Any modification of API Products must comply with the Governing Documents. Promptly upon request, you agree to provide us reasonable access to your Application, documents, information, employees, subcontractors, and your third-party agents. You will diligently and promptly correct any material bugs or faults in your Application that cause it to incorrectly access the API or display API Products. Regardless of how you use the API and API Products in your Application, you may not at any time, surviving termination of this Service Agreement to the maximum extent permitted by law, prevent or restrict us from any use, functionality, or display of our API and API Products in any manner, for any purpose, in any application, or in any medium, now known or later developed.
Sample 1
Application Functionality. The Application is designed to assist you to obtain information about Enercare’s product offers, services and information concerning energy cost savings and conservation measures, and to schedule and manage service appointments (the “Services”).
Sample 1
Application Functionality. 1.4.1. System shall support profiles for subcontract laboratories, each with lab-specific pricing per analysis. 1.4.2. System shall support cost tracking including, but not limited to: 1.4.2.1. Verify correct invoice totals based on the analyses performed, quantities and the lab; 1.4.2.2. Cost tracking is linked to specific sampling, events, programs, Entry Sets and lab report numbers; 1.4.2.3. Costs able to be tracked either in software or connected through ODBC to other business intelligence applications (e.g., R, Tableau, Power BI, etc.).
Sample 1
Application Functionality. Any modification of API Content/Services must comply with our Commercial Accounts API Specifications documents. Under no circumstances can you revise, change, modify or alter API Content/Services (or its appearance) to render the API Content/Services unfair, deceptive, abusive, false or misleading. If the API Content/Services includes hyperlinks to our website, the Application must use the complete, unaltered URL as the HREF or comparable functional link for proper tracking and functionality. Promptly upon request, you agree to provide us reasonable access to your Application, documents, information, employees, subcontractors, and your third party agents. You will diligently and promptly correct any material bugs or faults in your Application that cause it to incorrectly access the API or display API Content/Services.
Sample 1
Application Functionality. If you are using the UCA API as the UCA Interface, then, prior to launching a Licensee Application, you must submit all UCA-Related Pages to Licensor for review for compliance with Licensor’s requirements, including any required disclosures and legends, and, thereafter, you agree to not modify any UCA-Related Pages without Licensor’s prior written approval. Your Licensee Application may enhance the display of the UCA Content to best format the UCA Content. Any other modification of UCA Content must comply with the UCA Content License. If the UCA Content includes hyperlinks to a Licensor or Participating Program website, the Licensee Application must use the complete, unaltered URL as the HREF or comparable functional link given to the end user for proper tracking and functionality. Promptly upon request, you agree to provide Licensor reasonable access to any UCA-Related Pages for review of compliance with this Agreement and its requirements. You will diligently correct any material bugs or faults in your Licensee Application that cause it to incorrectly access the UCA API or display UCA Content. In addition, you will not, through your actions or omissions, cause the UCA API to fail to accurately deliver information, and you will be fully responsible for, and indemnify, defend and hold harmless the Licensor Indemnified Persons from, any Losses arising out of or relating to any failure of the UCA API to accurately deliver information as a result of your actions or omissions. Regardless of how you use the UCA API and UCA Content in your Licensee Application, you may not at any time, during and after the term of this Agreement, prevent or restrict Licensor from any use, functionality, or display of the UCA API or UCA Content in any manner, for any purpose, with any end user, in any application, or in any medium, now known or later developed.
Sample 1
Application Functionality. Any modification of API Content/Services must comply with the API Governing Documents. Under no circumstances can you revise, change, modify or alter API Content/Services (or its appearance) to render the API Content/Services unfair, deceptive, abusive, false or misleading. If the API Content/Services includes hyperlinks to Our website, the Application must use the complete, unaltered URL as the HREF or comparable functional link for proper tracking and functionality. Promptly upon request, you agree to provide Us reasonable access to your Application, documents, information, employees, subcontractors, and your third party agents. You will diligently and promptly correct any material bugs or faults in your Application that cause it to incorrectly access the API or display API Content/Services. Regardless of how you use the API and API Content/Services in your Application, you may not at any time, surviving termination of this Service Agreement to the maximum extent permitted by law, prevent or restrict Us from any use, functionality, or display of Our API or API Content/Services in any manner, for any purpose, with any user or End User, in any application, or in any medium, now known or later developed.
Sample 1
AutoNDA by SimpleDocs

Related to Application Functionality

  • CUSTOMER SERVICE FUNCTIONS The Servicer shall handle all Customer inquiries and other Customer service matters according to the same procedures it uses to service Customers with respect to its own charges.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Mobile Application If Red Hat offers products and services through applications available on your wireless or other mobile Device (such as a mobile phone) (the "Mobile Application Services"), these Mobile Application Services are governed by the applicable additional terms governing such Mobile Application Service. Red Hat does not charge for these Mobile Application Services unless otherwise provided in the applicable additional terms. However, your wireless carrier's standard messaging rates and other messaging, data and other rates and charges will apply to certain Mobile Application Services. You should check with your carrier to find out what plans your carrier offers and how much the plans cost. In addition, the use or availability of certain Mobile Application Services may be prohibited or restricted by your wireless carrier, and not all Mobile Application Services may work with all wireless carriers or Devices. Therefore, you should check with your wireless carrier to find out if the Mobile Application Services are available for your wireless Device, and what restrictions, if any, may be applicable to your use of such Mobile Application Services.

  • Future Functionality You agree that Your purchases are not contingent on the delivery of any future functionality or features, or dependent on any oral or written public comments made by Us regarding future functionality or features.

  • Scope and Application This Appendix will apply to all work undertaken within the Employer’s Workshop(s) by employees mainly engaged at the Workshop.

  • Customization The listed products are licensed for Customer Manager Suite use and customization only. Use of these tools to develop or customize non-Customer Manager Suite applications is not permitted without the express written authorization of PFPC.

  • Contract Database Metadata Elements Title: Great Neck Union Free School District and Great Neck Paraprofessionals Association (2011) Employer Name: Great Neck Union Free School District Union: Great Neck Paraprofessionals Association Local: Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 5132 Unit Size: Number of Pages: 28 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ ARTICLE# TITLE PAGE# Preamble 2 Article 1 Association Rights 2 Article 2 Board-Administration-Association Relationship and Procedures 4 Article 3 Exchange of Proposals 6 Article 4 Professionals Duties and Responsibilities of Paraprofessionals 7 Article 5 Work Assignments 8 Article 6 Annual Appointment 10 Article 7 Selection and Promotion 10 Article 8 Evaluations and Standards 11 Article 9 Procedures for Termination of Employment 11 Article 10 Conferences 12 Article 11 Human Resource File 12 Article 12 Professional Growth 13 Article 13 Sick Leave 14 Article 14 Personal Leave 16 Article 15 Other Leaves 17 Article 16 Grievance Procedures 18 Article 17 Legal Assistance 19 Article 18 Conformity to Law 19 Article 19 Health Insurance 20 Article 20 Retirement Plan 20 Article 21 Salary Schedule 21 Article 22 Seniority Policy 23 Article 23 Compensation for Financial Loss 24 Article 24 Duration of Agreement 25 Appendix A Determination of Negotiating Unit 25 Appendix B Payroll Deduction Authorization 26 Appendix C Bus Aides 26 Appendix D Salary Schedules 27

  • Performance of Government Functions Nothing contained in this contract shall be deemed or construed so as to in any way estop, limit, or impair the City from exercising or performing any regulatory, policing, legislative, governmental, or other powers or functions.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.

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