INTEROPERABILITY REQUIREMENTS Sample Clauses

INTEROPERABILITY REQUIREMENTS. Subscriber is responsible for obtaining and maintaining any equipment, software, and other services needed to connect to, access, and use the Digital Properties, including, without limitation, hardware, software, and Internet service. Subscriber shall be solely responsible for ensuring that such equipment, software, and ancillary services are compatible with the Digital Properties.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
INTEROPERABILITY REQUIREMENTS. 3.11.1 Except as provided in 3.10.2, a Licensed Copier that is capable of making a Managed Copy, using the MCOT (or MCOTs) that such Licensed Copier implements, must be capable of making any Managed Copy (again, using the MCOT or MCOTs that such Licensed Copier implements) that is authorized by the AACS MCAS, or by any MCAS that is designed and deployed in a manner consistent with the AACS MCAS implementation of the Specifications. 3.11.2 A Licensed Copier that is capable of making a Managed Copy shall be designed and produced to communicate with the AACS MCAS only in accordance with established protocols as set forth in the Specifications. A Licensed Copier shall be designed and produced using reasonable measures, at a minimum in accordance with standard industry practices, to prevent it from engaging in communications that cause harm to the systems or operations of the AACS MCAS. By way of example, Licensed Clients may not contain secret menus, or residual test or debug codes that could facilitate such harmful communications. 3.11.3 Licensee acknowledges and agrees that AACS LA may authorize the AACS MCAS to refuse access to the AACS MCAS for one or more units of products (whether Licensed Copiers or otherwise) that are causing, has caused, or is threatening to cause, or that are known to be capable of causing, imminent material harm to the systems or operations of the AACS MCAS.
Sample 1Sample 2
INTEROPERABILITY REQUIREMENTS. The NIMS requires that preparedness organizations at all jurisdictional levels establish standards, guidelines, and protocols necessary to promote interoperability among member jurisdictions and agencies. JBSA and City authorities will act in accordance with the interoperability standards established by the National Integration Center.
Sample 1
INTEROPERABILITY REQUIREMENTS. If required by law, Cisco will promptly provide the information You request to achieve interoperability between applicable Cisco Offers and another independently created program on terms that reasonably protect Cisco’s proprietary interests.
Sample 1
INTEROPERABILITY REQUIREMENTS. Service Provider understands the importance of ensuring its products and services support the delivery of Content Services to Subscribers. To this end, the Service Provider agrees that during the term of the Initial Agreement, its hardware, products, services, middleware, and software will function and interoperate with the Network. Service Provider will remain interoperable with the Network, and will cooperate and use its best efforts to resolve interoperability issues resulting from third party issues. Service Provider agrees that prior to the deliver of new releases, software patches, remedies, or fixes, Service Provider shall conduct tests and interoperability scenarios within its lab and engineering facility. Provo shall implement a pre-production Network test environment and will test all vendors' new releases and updates prior to deployment in the production network. When Service Provider adds new equipment or changes equipment to interface or integrate with the Network, Service Provider will be responsible for any interoperability issues with third party equipment vendors and Provo on the Network. Service Provider agrees to a) make its products and/or software available for testing in third party vendor/manufacturers SQA labs at no charge, and b) use its best efforts to modify applicable Service Provider products/software to achieve interoperability with third party products and software.
Sample 1
INTEROPERABILITY REQUIREMENTS. 357 In addition to this MAA acquisition, the Government has acquired, or is acquiring, 358 services and equipment to meet a range of telecommunications requirements, including local 359 service, intra-Local Access and Transport Area (LATA) toll, inter-LATA access, data 360 networking (local and wide area), inter-LATA transport, international voice/data transport, 361 wireless, electronic commerce, Internet, and electronic messaging. The MAA services shall, 362 when required by the Government, interface and interoperate with the systems and services 363 provided under these acquisitions. The interface requirements for interoperability for each of 364 the above acquisitions will be available from the Government. When interconnectivity and 365 interoperability are required at an SDP located at another vendor’s network, the contractor 366 shall conform to commercial standard interfaces for interconnectivity and interoperability. If 367 there are non-commercial standard interfaces used by the other vendor's network, the 368 contractor shall coordinate and negotiate with the Government on a case-by-case basis.
Sample 1

Related to INTEROPERABILITY REQUIREMENTS

  • Accessibility Requirements Under Tex. Gov’t Code Chapter 2054, Subchapter M, and implementing rules of the Texas Department of Information Resources, the System Agency must procure Products and services that comply with the Accessibility Standards when those Products are available in the commercial marketplace or when those Products are developed in response to a procurement solicitation. Accordingly, Grantee must provide electronic and information resources and associated Product documentation and technical support that comply with the Accessibility Standards.

  • Quality Requirements Performance Indicator Heading Indicator (specific) Threshold Method of Measurement Frequency of monitoring Consequence of Breach

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Interface Requirements 2.4.5.1 The NID shall be equal to or better than all of the requirements for NIDs set forth in the applicable industry standard technical references.

  • Specific Requirements compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Basic Requirements To be eligible for PayPal’s Seller Protection program, all of the following basic requirements must be met, as well as any applicable additional requirements: • The primary address for your PayPal account must be in the United States. • The item must be a physical, tangible good that can be shipped, except for items subject to the Intangible Goods Additional Requirements. Transactions involving items that you deliver in person in connection with payment made in your physical store, may also be eligible for PayPal’s Seller Protection program so long as the buyer paid for the transaction in person by using a PayPal goods and services QR code. • You must ship the item to the shipping address on the Transaction Details page in your PayPal account for the transaction. If you originally ship the item to the recipient’s shipping address on the Transaction Details page but the item is later redirected to a different address, you will not be eligible for PayPal’s Seller Protection program. We therefore recommend not using a shipping service that is arranged by the buyer, so that you will be able to provide valid proof of shipping and delivery. • The shipping requirement does not apply to eligible transactions involving items that you deliver in person; provided, however, that you agree to provide us with alternative evidence of delivery or such additional documentation or information relating to the transaction that we may request. • You must respond to PayPal’s requests for documentation and other information in a timely manner as requested in our email correspondence with you or in our correspondence with you through the Resolution Center. If you do not respond to PayPal’s request for documentation and other information in the time requested, you may not be eligible for PayPal’s Seller Protection program. • If the sale involves pre-ordered or made-to-order goods, you must ship within the timeframe you specified in the listing. Otherwise, it is recommended that you ship all items within 7 days after receipt of payment. • You provide us with valid proof of shipment or delivery. • The payment must be marked “eligible” or “partially eligible” in the case of Unauthorized Transaction claims, or “eligible” in the case of Item Not Received claims, for PayPal’s Seller Protection program on the Transaction Details page. • In the case of an Unauthorized Transaction claim, you must provide valid proof of shipment or proof of delivery that demonstrates that the item was shipped or provided to the buyer no later than two days after PayPal notified you of the dispute or reversal. For example, if PayPal notifies you of an Unauthorized Transaction claim on September 1, the valid proof of shipment must indicate that the item was shipped to the buyer no later than September 3 to be eligible for PayPal’s Seller Protection program. PayPal determines, in its sole discretion, whether your claim is eligible for PayPal’s Seller Protection program. PayPal will make a decision, in its sole discretion, based on the eligibility requirements, any information or documentation provided during the resolution process, or any other information PayPal deems relevant and appropriate under the circumstances. To be eligible for PayPal’s Seller Protection program for a buyer’s Item Not Received claim, you must meet both the basic requirements and the additional requirements listed below: • Where a buyer files a chargeback with the issuer for a card-funded transaction, the payment must be marked “eligible” for PayPal’s Seller Protection on the Transaction Details page. • You must provide proof of delivery as described below.

  • 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.

  • 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.

  • 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!