UCS Functional Architecture Sample Clauses

UCS Functional Architecture. ‌ The UCS Functional Architecture required to support interoperability among future and legacy UAV systems is illustrated in Figure B - 4, UCS Functional Architecture. AV AV LAUNCH & RECOVERY SYSTEM UCS VSM DLI CORE OPERATOR UCS HCI CCI CCI CCISM C4I C4I SYSTEM SYSTEM VSM LAUNCH & RECOVERY SYSTEM UCS DLI CORE UCS HCI OPERATOR CCI CCI CCISM C4I SYSTEM C4I SYSTEM Figure B - 4. UCS Functional Architecture This architecture establishes the following functional elements and interfaces: • Core UCS (CUCS) • Data Link Interface (DLI) • Command and Control Interface (CCI) • Vehicle Specific Module (VSM) • Command and Control Interface Specific Module (CCISM) This STANAG is not an attempt to define a detailed design or implementation for the CUCS other than specifying that the functional architecture accommodate the integration of the DLI and CCI and recommending that it follow applicable NATO STANAGS and guidelines for software. Lastly, because of changing technology, this STANAG does not define a specific Common Operating Environment (XXX) but only specifies that the Operating Environment supports/integrates the specified network/transport protocols and supports the specified user applications. Future, as well as legacy UAV systems, will be enabled for interoperability through compliance with this architecture and the relevant STANAGs. The DLI shall support legacy as well as future UAVs and all air vehicle technologies (e.g., fixed wing, rotary wing, etc.), and all UAV operational purposes (surveillance, reconnaissance, and combat). Future UAV systems should utilize a STANAG 7085 compliant data link system. For those that do not (future as well as legacy systems), an ADT compatible GDT shall be provided in order to achieve Level 2 and above interoperability. In similar fashion, the CCI interface shall support legacy as well as future C4I systems (e.g., Allied Command and Control System (ACCS)). Thus, the interface between the Core UCS and the External C4I nodes shall be compatible with the communication system infrastructure utilized to support the external tasking and sensor data dissemination. This will be accomplished by using the communication standards identified by the NATO C3 Technical Architecture’s (NC3TA's) NC3 Common Standards Profile (NCSP) as specified in Section 4. The NC3TA is intended to provide an overall framework for NATO communications. All future communications and information systems used in NATO are to conform to these standards. The concept...
Sample 1
AutoNDA by SimpleDocs
UCS Functional Architecture. AV LAUNCH & RECOVERY SYSTEM UCS VSM DLI CORE I OPERATOR UCS HC CCI CCI CCISM C4I C4I SYSTEM SYSTEM UCS VSM DLI OPERATOR CCI CCI C4I SYSTEM C4I SYSTEM CCISM CORE UCS LAUNCH & RECOVERY SYSTEM AV HCI The UCS Functional Architecture required to support interoperability among future and legacy UAV systems is illustrated in Figure B - 4, UCS Functional Architecture.
Sample 1

Related to UCS Functional Architecture

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Physical Architecture 59.2.1 CenturyLink's network architecture in any given local exchange area and/or LATA can vary markedly from another local exchange area/LATA. Using one or more of the NIMs herein, the Parties will agree to a physical architecture plan for a specific LATA, or if appropriate based on other requirements in Section 59, Local Calling Area. The physical architecture plan, as described in the Local Interconnection POI Profile, will be discussed during joint implementation planning. CLEC and CenturyLink agree to Interconnect their networks through existing and/or new Interconnection Facilities between CLEC switch(es) and CenturyLink's End Office Switch(es) and/or Tandem Switch(es). The physical architecture plan will be in accordance with Forecasting and Planning requirements in Article IV.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Operations Support Systems Functions CBT shall provide CLEC, upon CLEC's request, nondiscriminatory access to CBT's Operations Support Systems functions for pre-ordering, ordering, provisioning, maintenance and repair and billing, in accordance with the terms and schedules established in the Commission’s Arbitration Award in Case No. 97-152-TP-ARB, August 14, 1997 (“Arbitration Award”). CBT shall provide CLEC advance written notice of any material changes to CBT operating support systems functions.

  • Primary Function (a) The primary function of the troubleshooter shall be to address concerns of bargaining unit employees who seek a determination of their employment status (an employee of regular status or an employee of auxiliary status) pursuant to the terms of this Collective Agreement.

  • Additional Functionality Microsoft may provide additional functionality for the software. Other license terms and fees may apply.

  • Mixed Functions An employee engaged for more than two hours during one day or shift on duties carrying a higher rate than his or her ordinary classification shall be paid the higher rate for such day or shift. If for two hours or less during one day or shift he or she shall be paid the higher rate for the time so worked.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

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