Levels of Interoperability Sample Clauses

Levels of Interoperability. The following list defines the Levels of Interoperability for STANAG compliant UAV systems: Level 1: Indirect receipt of UAV related data Level 2: Direct receipt of ISR/other data where “direct” covers reception of the UAV data by the UCS when it has direct communication with the UAV. Level 3: Control and monitoring of the UAV payload in addition to direct receipt of ISR/other data Level 4: Control and monitoring of the UAV, less launch and recovery Level 5: Control and monitoring of the UAV (Level 4), plus launch and recovery functions Level 2 monitoring and Level 3 controls are divisible by payload for an air vehicle where there is more than one payload located onboard the air vehicle. Level 4 interoperability is for the air vehicle alone, and does not include payload control that is specified as Level 3 control. A CUCS controlling both the air vehicle and its payload is exercising Level 3 and Level 4 control. The interoperability levels defined above can be enabled through the standardization of interfaces between the UAV system elements and between the UCS and external C4I Systems. This can be accomplished if the overall System Architecture is also standardised to the extent that it accommodates the implementation of these standard interfaces. In order to achieve interoperability, the UCS Architecture and interfaces shall support the appropriate communication protocols and message formats for legacy as well as new UAV systems. In addition, Level 2 and above (Level 2, 3, 4, and 5) interoperability requires the use of a Ground Data Terminal (GDT) that is interoperable with the Air Data Terminal (ADT), (e.g., connectivity between the GDT and ADT is prerequisite for Level 2,3,4 and 5 interoperability).
Sample 1
AutoNDA by SimpleDocs
Levels of Interoperability. Organisational interoperability Capable of organisational collaboration • Degree to which the use of COBACORE is aligned with standards, best practices and procedures of intended end- users. • Degree to which end-users and their organisations are willing and able to align their standards and procedures to effectively and efficiently use COBACORE. Technical interoperability Capable of technical interaction • Degree to which COBACORE technology (software, hardware, information formats) is compatible with technology of end-users and their organisations. Semantic interoperability Capable of shared understanding. • Degree to which the terminology and definitions in COBACORE’s information models are compatible with terminology and definitions of end-users and their organizations.
Sample 1
Levels of Interoperability 
Sample 1

Related to Levels of Interoperability

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

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

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • Service Levels All service level requirements will be set forth in Exhibit A (“XXXX.xxx Referral Service Level Requirements”). Recipient Xxxxxx agrees to adhere, and encourage Recipient Agent’s adherence, with the version of the XXXX.xxx Referral Service Level Requirements in effect at the time XXXX.xxx identifies the Referral to Recipient Broker/Agent.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing Ymax traffic to Verizon, the subtending arrangements between Verizon Tandems and Verizon End Offices shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to Ymax, the subtending arrangements between Ymax Tandems and Ymax End Offices shall be the same as the Tandem/End Office subtending arrangements that Ymax maintains for the routing of its own or other carriers’ traffic.

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