Annex B Structure Sample Clauses

Annex B Structure. Annex B provides a top level description of interoperability objectives and the approach taken to achieve UAV systems interoperability through standardising the interfaces between the CUCS and the air vehicle, the CUCS and external C4I systems, and the CUCS to the UAV system operator. It describes the requirement for a standard functional UCS architecture to accommodate those interfaces and refers to the Appendices B1 – B3 that contain the details of the standards required by STANAG 4586. It also lists other STANAGs, standards and protocols that are required for achieving UAV systems interoperability and offers some considerations for their implementation. The following Appendices are elements of Xxxxx X. • Appendix B1 explains the approach to standardising the DLI and the functionality of the VSM. It contains the standard messages and protocols required at the DLI that enable the CUCS to communicate with and exploit different UAVs and payloads and to support the required UAV System operator(s) interface as specified in the Human Computer Interface (HCI), Appendix B3. • Appendix B2 shows the approach selected to standardise the CCI and the application of the Command and Control Interface Specific Module (CCISM). The appendix contains the Information Exchange Requirements (IER), Attachment B2 - 1 and lists the UCS ADatP-3 Message Implementation Requirements, Attachment B2 - 2, to satisfy the IER requirements and to support the required UAV System operator(s) interface as specified in the Human Computer Interface (HCI), Appendix B3. • Appendix B3 describes the Human Computer Interface (HCI) requirements and services that the CUCS will provide to the UAV System operator(s).
AutoNDA by SimpleDocs

Related to Annex B Structure

  • Organizational Structure The ISO will be governed by a ten (10) person unaffiliated Board of Directors, as per Article 5 herein. The day-to-day operation of the ISO will be managed by a President, who will serve as an ex-officio member of the ISO Board, in accordance with Article 5 herein. There shall be a Management Committee as per Article 7 herein, which shall report to the ISO Board, and shall be comprised of all Parties to the Agreement. There shall be at least two additional standing committees, the Operating Committee, as provided for in Article 8, and the Business Issues Committee, as provided for in Article 9, both of which shall report to the Management Committee. A Dispute Resolution Process will be established and administered by the ISO Board in accordance with Article 10.

  • Report Structure Provides an analysis of each error type (by error code). The report is in descending order by count of each error code and provides the following: • Error Type (by error code) • Count of each error type • Percent of each error type • Cumulative percent • Error Description • CLEC Caused Count of each error code • Percent of aggregate by CLEC caused count • Percent of CLEC caused count • BellSouth Caused Count of each error code • Percent of aggregate by BellSouth caused count • Percent of BellSouth by BellSouth caused count. Data Retained Relating to CLEC Experience Relating to BellSouth Performance • Report Month • Total Number of Lsrs Received • Total Number of Errors by Type (by Error Code) - CLEC caused error • Report Month • Total Number of Errors by Type (by Error Code) - BellSouth System Error SQM Disaggregation - Analog/Benchmark SQM Level of Disaggregation SQM Analog/Benchmark • Not Applicable • Not Applicable SEEM Measure SEEM Measure No Tier I Tier II O-5: Flow-Through Error Analysis SEEM Disaggregation - Analog/Benchmark SEEM Disaggregation SEEM Analog/Benchmark • Not Applicable • Not Applicable O-6: CLEC LSR Information O-6: CLEC LSR Information Definition A list with the flow through activity of LSRs by CC, PON and Ver, issued by each CLEC during the report period. Exclusions • Fatal Rejects • LSRs submitted manually Business Rules The CLEC mechanized ordering process includes all LSRs, including supplements (subsequent versions) which are submitted through one of the three gateway interfaces (TAG, EDI, and LENS), that flow through and reach a status for a FOC to be issued. The CLEC mechanized ordering process does not include LSRs which are submitted manually (for example, fax and courier). Calculation Not Applicable

  • Agreement Structure 2.1 An “Agreement” hereunder shall consist of this Master Agreement, the Schedule, and their applicable attachments and represents the complete and exclusive agreement between the Parties regarding the subject matter of the Schedule, and replaces any prior oral or written communications between the Parties relating thereto. Each Lease is effective when the Schedule containing such Lease is executed by the Parties thereto.

  • PRICING STRUCTURES Licenses and Support Services for the Licensed Programs to which this OST applies are granted according to the pricing structures mentioned in the related Transaction Document. Standard pricing structures are defined in the section “DEFINITIONS” of this OST, even though those pricing structures may not be applicable to the DS Offerings to which this OST applies. Other pricing structures may be made available on a case-by-case basis.

  • General structure The General Assembly is the decision-making body of the consortium The Coordinator is the legal entity acting as the intermediary between the Parties and the Funding Authority. The Coordinator shall, in addition to its responsibilities as a Party, perform the tasks assigned to it as described in the Grant Agreement and this Consortium Agreement. [Option: The Management Support Team assists the General Assembly and the Coordinator.]

  • Classification Structure All employees working under this Agreement shall be classified according to the skill based classification structure set out in Appendix A.

  • FEE STRUCTURE In consideration of Consultant providing services, Municipality shall pay Consultant for Services performed in accordance with Exhibit A – List of Services and Fee Schedule.

  • Emergency Schedule Changes The Employer may adjust an overtime-eligible employee’s workweek and work schedule without prior notice in emergencies or unforeseen operational needs.

  • Credit Structure To obtain a credit, Customer must open a Trouble Ticket in accordance with the “Process for Customer to Apply for SLA Credits” section below. Verizon will work with Customer to confirm that a DDR issue exists with the Core Network and repair the problem(s), as applicable. Once Verizon confirms that the DDR on the Core Network for a specific Customer E-Line EVC connection does not comply with this Service Level Standard, Verizon will have thirty (30) calendar days from the opening of the Trouble Ticket to address the Service Issue and close the applicable Trouble Ticket before Customer may be eligible for SLA credits. If, after thirty (30) calendar days of opening the Trouble Ticket, the DDR Service Level Standard issue is not corrected, but has been agreed to as a Service Issue, Customer may qualify for credits.

  • Governance Structure The Academy shall be organized and administered as a Michigan nonprofit corporation under the direction of the Academy Board and pursuant to the governance structure as set forth in the Bylaws. The Academy’s Board of Directors shall meet monthly unless another schedule is mutually agreed upon by the President and the Academy. The Academy shall not delegate this duty of organization and administration of the Academy without the express affirmative consent of the University.

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