Vehicle, Data Link, and CUCS Sample Clauses

Vehicle, Data Link, and CUCS. Identification (ID) Numbers. Each message shall contain fields that specify the identification (ID) numbers for the air vehicle and CUCS that are communicating with one another. Some messages also contain the Data Link ID and the VSM ID. The VSM ID is provided in those messages which may be required to be transmitted between a CUCS and a VSM in advance of a connection to an air vehicle, payload or a data link. The purpose of these numbers is to uniquely identify any entity in an arbitrarily formed system combining multiple CUCS, air vehicles, and data links all potentially interacting with VSMs which may control zero or more vehicles at a time. A VSM that controls zero air vehicles might require connection to a CUCS in advance of receiving an air vehicle handoff from another STANAG 4586 ground station. ID numbers shall be formed as 4-byte numbers. The first (most significant) byte shall be the standard NATO country code of the country of origin for that CUCS or air vehicle. NATO may assign additional country codes at its discretion. Country code 255 (hexadecimal FF) shall be reserved. The remaining three bytes shall be assigned statically according to procedures and protocols identified and maintained by the respective member countries. Each member country shall be responsible for establishing a system to assure unique ID numbers for each in-service device. The purpose of these numbers is to uniquely identify any entity in an arbitrarily formed system combining multiple CUCS and multiple vehicles with multiple interacting VSMs, each of which may control one or more vehicles at a time. STANAG 1059 Edition 8 provides the latest 3 letter country codes. The country codes are 3-letter character sets,
Sample 1
AutoNDA by SimpleDocs
Vehicle, Data Link, and CUCS. Identification (ID) Numbers Each message shall contain fields that specify the identification (ID) numbers for the air vehicle and CUCS that are communicating with one another. Some messages also contain the Data Link ID and the VSM ID. The VSM ID is provided in those messages which may be required to be transmitted between a CUCS and a VSM in advance of a connection to an air vehicle, payload or a data link. The purpose of these numbers is to uniquely identify any entity in an arbitrarily formed system combining multiple CUCS, air vehicles, and data links all potentially interacting with VSMs which may control zero or more vehicles at a time. A VSM that controls zero air vehicles might require connection to a CUCS in advance of receiving an air vehicle handoff from another STANAG 4586 ground station. ID numbers shall be formed as 4-byte numbers. The first (most significant) byte shall be the standard NATO country code, as defined in Table B1-1, NSIF Country Codes. NATO may assign additional country codes at its discretion. Country code 255 (hexadecimal FF) shall be reserved. The next three bits shall identify the type of component requiring identification. The remaining 21 bits shall be assigned and maintained by the individual countries in accordance with their specific procedures and protocols. It is the responsibility of the specific country to ensure uniqueness in these 21 bits to eliminate potential component conflicts. This numbering scheme and valid component codes are illustrated in Figure B1-7. Country Code Component Code 0 = AV 1 = CUCS 2 = DL 3 = VSM
Sample 1

Related to Vehicle, Data Link, and CUCS

  • Access to Customer Data You agree that we may, for the purposes of providing Maintenance and Customer Support and/or for the purpose of otherwise protecting the integrity of the Software, access and/or download your Customer Data on a limited basis.

  • Customer Data 5.1 The Customer shall own all right, title and interest in and to all of the Customer Data and shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data.

  • End User This agreement shall bind the ordering activity as end user but shall not operate to bind a Government employee or person acting on behalf of the Government in his or her personal capacity.

  • Workstation Encryption Supplier will require hard disk encryption of at least 256-bit Advanced Encryption Standard (AES) on all workstations and/or laptops used by Personnel where such Personnel are accessing or processing Accenture Data.

  • Customer Feedback WSP may from time to time request CUSTOMER to provide certain information or content by which the End User can be identified when using the SaaS Service including the control panel, and the registration functionality that are compatible with the WSP Software. WSP will only use and protect such information in accordance with the DPA. WSP shall have a royalty-free, worldwide, irrevocable, perpetual license to use and incorporate into the SaaS Services any suggestions, enhancement requests, recommendations or other feedback provided by Customer, including End Users, relating to the operation of the SaaS Services.

  • Customer Equipment Customer represents and warrants that it owns or has the legal right and authority, and will continue to own or maintain the legal right and authority during the term of this Agreement, to place and use the Customer Equipment as contemplated by this Agreement. Customer further represents and warrants that its placement, arrangement, and use of the Customer Equipment in the Internet Data Centers complies with the Customer Equipment Manufacturer's environmental and other specifications.

  • THIRD PARTY WEBSITES AND CONTENT The Website contains (or you may be sent through the Website or the Company Services) links to other websites ("Third Party Websites") as well as articles, photographs, text, graphics, pictures, designs, music, sound, video, information, applications, software and other content or items belonging to or originating from third parties (the "Third Party Content"). Such Third Party Websites and Third Party Content are not investigated, monitored or checked for accuracy, appropriateness, or completeness by us, and we are not responsible for any Third Party Websites accessed through the Website or any Third Party Content posted on, available through or installed from the Website, including the content, accuracy, offensiveness, opinions, reliability, privacy practices or other policies of or contained in the Third Party Websites or the Third Party Content. Inclusion of, linking to or permitting the use or installation of any Third Party Website or any Third Party Content does not imply approval or endorsement thereof by us. If you decide to leave the Website and access the Third Party Websites or to use or install any Third Party Content, you do so at your own risk and you should be aware that our terms and policies no longer govern. You should review the applicable terms and policies, including privacy and data gathering practices, of any website to which you navigate from the Website or relating to any applications you use or install from the Website. Any purchases you make through Third Party Websites will be through other websites and from other companies, and Company takes no responsibility whatsoever in relation to such purchases which are exclusively between you and the applicable third party. SITE MANAGEMENT Company reserves the right but does not have the obligation to:

  • End Users Customer will control access to and use of the Products by End Users and is responsible for any use of the Products that does not comply with this Agreement.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

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