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.
Sample 1Sample 2
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
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

Related to INTEROPERABILITY REQUIREMENTS

  • Quality Requirements Performance Indicator Heading Indicator (specific) Threshold Method of Measurement Frequency of monitoring Consequence of Breach QUALITY Patient Safety - Incidents I1 Number of incidents Adverse incidents include the following: clinical or non clinical adverse events that have potential to cause avoidable harm to a patient, including medical errors or adverse events related to medical devices or other equipment. Clinical or non- clinical accidents, accidental injuries to staff and members of the public, verbal, physical or psychological abuse or harassment, unusual or dangerous occurrences, damage to trust property, plant or equipment, fire or flood, security, theft or loss, near misses are identified as any event where under different circumstances significant injury or loss may have occurred Number of recorded incidents in the contract month Monthly Remedial Action Plan brought to Performance Meeting following breach; action under Module C Clause 32 if needed I2 Number of Sis Definition of SUI according to trust policy and national guidance Number of Serious Untoward Incidents reported in contract month Monthly Remedial Action Plan brought to Performance Meeting following breach; action under Module C Clause 32 if needed S1 Percentage of eligible staff received child safeguarding training at level 2 (as identified in LSCB training strategy) 95% Number received training/ Number of identified staff requiring training Monthly S2 Percentage of eligible staff received adult safeguarding awareness training at level 2 ( as identified in K&M Safeguarding Vulnerable Adults training strategy) 95% Number of staff trained/ Number of identified staff requiring training Monthly

  • Technical Requirements 2.7.4.1 The NID shall provide an accessible point of interconnection and shall maintain a connection to ground.

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

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Encryption Requirements Transfer Agent will not locally store Fund Data on any laptops or mobile devices (e.g., Blackberries, PDAs) managed by Transfer Agent.

  • Security Requirements 11.1 The Supplier shall comply, and shall procure the compliance of the Suppliers Personnel, with the Security Policy and the Security Plan and the Supplier shall ensure that the Security Plan produced by the Supplier fully complies with the Security Policy.

  • Maintenance Requirements The Contractor shall ensure and procure that at all times during the Maintenance Period, the Project Highway conforms to the maintenance requirements set forth in Schedule-E (the “Maintenance Requirements”).

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

Time is Money Join Law Insider Premium to draft better contracts faster.