Common Use CUSS Kiosk Requirement Sample Clauses

Common Use CUSS Kiosk Requirement. The Common Use CUSS Kiosk Requirement includes the annual amortized capital cost, the allocated annual cost of operation and maintenance, including an allocation of telecom charges, and, for CUSS units placed in the Airport Terminal Building, 6 square feet of Class I space multiplied by the number of Common Use CUSS Kiosks in service in the Airport Terminal Building multiplied by the Class I terminal rental rate for the Fiscal Year. From time to time, the Department may receive requests or have a desire to install and operate CUTE equipment and devices at off-airport locations. As number and type of devices may vary, as well as the cost of the infrastructure at various locations, the pricing for such installations will be determined on a case by case basis. At a minimum, each installation will be completed and operated on a cost recovery basis and all such pricing will be approved by the MAAC. The off- airport Common Use CUSS Kiosk Requirement shall include any net expenses, fees, or rentals associated with placement of Common Use CUSS Kiosks outside the Airport terminal. Page 146 of 153 2. Common Use CUSS Kiosk Pricing. The Common Use CUSS Kiosk Requirement shall be divided by the projected number of common use CUSS kiosk transactions for the Fiscal Year. This per-transaction rate will be billed monthly to Airlines that elect to use the common use CUSS kiosks based upon the number of monthly transactions for each Airline user of common use CUSS kiosks. If the Department determines a maximum rate per transaction shall apply for the Fiscal Year, then this maximum rate per transaction multiplied by the number of Airline transactions shall be in effect replacing the methodology discussed immediately above in this Section II.
AutoNDA by SimpleDocs

Related to Common Use CUSS Kiosk Requirement

  • Network Requirements Customer shall be responsible for ensuring that all aspects of the applicable network environment(s) adhere to the applicable standards and requirements specified in the Documentation and are configured appropriately to its proposed use of Ordered SaaS Services.

  • W-9 Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a properly completed Internal Revenue Service (“IRS”) Form W-9. The purpose of the W-9 form is to document the SS# or FEIN# per the IRS. Note: W-9s submitted for any other entity name other than the Grantee’s will not be accepted.

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

  • Customer Requirements Customer will be required to maintain complex passwords for their User accounts where applicable. For any such passwords LightEdge will provide a secure URL that any User can access to change passwords. All User passwords are set to a ninety (90) day password expiration schedule by default. LightEdge is not responsible for unexpected use of Services whether by ex-employees, compromised User passwords or any other misuse of Customer accounts. Customer shall be responsible for all costs incurred by such unexpected use of Service. Customer shall be fully responsible for providing to LightEdge at Customer’s own expense and in a timely manner the following: - All security for its Services and systems used or accessible in connection with Service; - Cooperative testing of all Customer-provided hardware, software, and Services for compatibility with Service; - Designating an Authorized Contact(s) to be the point of contact to interface with LightEdge Technical Support; - All cabling necessary to support Service; and - Physical and remote management access to any and all Servers onto which Service is installed.

  • Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.

  • Work Requirements The following Partner(s) is/are required to work for the Partnership: (choose one) ☐ - No Partners. No Partners are required to work for the Partnership. ☐ - Specific Partners. The following Partner(s) are required to work for the Partnership: [PARTNER(S')] NAME(S)]. Compensation, if any, shall be agreed to in a separate document.

  • Minimum Vendor License Requirements Vendor shall maintain, in current status, all federal, state, and local licenses, bonds and permits required for the operation of the business conducted by Vendor. Vendor shall remain fully informed of and in compliance with all ordinances and regulations pertaining to the lawful provision of goods or services under the TIPS Agreement. TIPS and TIPS Members reserve the right to stop work and/or cancel a TIPS Sale or terminate this or any TIPS Sale Supplemental Agreement involving Vendor if Vendor’s license(s) required to perform under this Agreement or under the specific TIPS Sale have expired, lapsed, are suspended or terminated subject to a 30‐day cure period unless prohibited by applicable statue or regulation.

  • Design Criteria and Standards All Projects/Services shall be performed in accordance with instructions, criteria and standards set forth by the Director.

  • Applicable Standards The requirements and guidelines of NERC, the Applicable Regional Entity, and the Control Area in which the Customer Facility is electrically located; the PJM Manuals; and Applicable Technical Requirements and Standards.

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

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