Reporting INCSEA Incidents and DMAs Sample Clauses

Reporting INCSEA Incidents and DMAs. (1) Operational Report (OPREP)-3 NAVY BLUE series messages from reference (e) are appropriate for promptly reporting INCSEA incidents and DMAs, except in cases of national level interest, when OPREP-3 PINNACLE series messages will be used. Amplifying message reports will be submitted as additional information becomes available, including an amplifying report within 72 hours that includes the NCC’s evaluation whether any actions violated reference (a) or (b). (2) Detailed written reports must be submitted within 15 days to CNO (Attn: Deputy Chief of Naval Operations for Operations, Plans and Strategy (N3/N5)) with a copy to the operational chain of command. This detailed written report is separate from operational chain of command reporting requirements for other purposes, such as public affairs guidance or communications with the Russian Federation in other channels (e.g., CJCS, Defense Attaché or Department of State). See enclosure (3) for the reporting flow chart. (3) When the Russian Federation provides information to the American Legation United States Naval Attaché (ALUSNA) Moscow concerning an alleged U.S. violation of reference (a) or (b), ALUSNA Moscow's process is to notify the appropriate NCC and CNO (N3/N5) immediately. The appropriate NCC will collect information from the units involved and forward the required written report to CNO (N3/N5) within 15 days. (4) The following documentation has proven effective in presenting the U.S. view of an INCSEA incident or DMA, and should be forwarded with the detailed written report where available: (a) A written chronology of events. Include when and where communications (radio or signals) were used during the interaction or DMA and whether or not both sides acknowledged communication. Provide appropriate position, course, speed, bearing, and range data. A voice narrative recording is an effective tool for use in constructing an accurate chronology.
Sample 1
AutoNDA by SimpleDocs

Related to Reporting INCSEA Incidents and DMAs

  • Reporting Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.

  • Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include: (a) accident, death or severe injury to any person; (b) damaged or dislodged fixed equipment; (c) flooding of Project Highway; and (d) any other unusual occurrence.

  • Accidents and Dangerous Occurrences The Hirer must report all accidents involving injury to the public to a member of the Village Hall management committee as soon as possible and complete the relevant section in the Village Hall’s accident book. Any failure of equipment belonging to the Village Hall or brought in by the Hirer must also be reported as soon as possible. Certain types of accident or injury must be reported on a special form to the local authority. The Hall Secretary will give assistance in completing this form. This is in accordance with the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 1995 (RIDDOR).

  • Technical and Organizational Measures The following sections define SAP’s current technical and organizational measures. SAP may change these at any time without notice so long as it maintains a comparable or better level of security. Individual measures may be replaced by new measures that serve the same purpose without diminishing the security level protecting Personal Data.

  • Reporting on Utilization of Subject Inventions 1. The Performer agrees to submit, during the term of the Agreement, an annual report on the utilization of a subject invention or on efforts at obtaining such utilization that are being made by the Performer or its licensees or assignees. Such reports shall include information regarding the status of development, date of first commercial sale or use, gross royalties received by the Performer, and such other data and information as the agency may reasonably specify. The Performer also agrees to provide additional reports as may be requested by DARPA in connection with any march-in proceedings undertaken by DARPA in accordance with Paragraph I of this Article. DARPA agrees it shall not disclose such information to persons outside the Government without permission of the Performer, unless required by law. 2. All required reporting shall be accomplished, to the extent possible, using the i-Edison reporting website: xxxxx://x-xxxxxx.xxxx.xxx.xxx/iEdison/. To the extent any such reporting cannot be carried out by use of i-Edison, reports and communications shall be submitted to the Agreements Officer and Administrative Agreements Officer.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Failure to Maintain Financial Viability The System Agency may terminate the Grant Agreement if the System Agency, in its sole discretion, determines that Grantee no longer maintains the financial viability required to complete the services and deliverables, or otherwise fully perform its responsibilities under the Grant Agreement.

  • Professional Development; Adverse Consequences of School Exclusion; Student Behavior The Board President or Superintendent, or their designees, will make reasonable efforts to provide ongoing professional development to Board members about the adverse consequences of school exclusion and justice-system involvement, effective classroom management strategies, culturally responsive discipline, appropriate and available supportive services for the promotion of student attendance and engagement, and developmentally appropriate disciplinary methods that promote positive and healthy school climates, i.e., Senate Bill 100 training topics. The Board will conduct periodic self-evaluations with the goal of continuous improvement. New Board Member Orientation The orientation process for newly elected or appointed Board members includes:

  • Technical and Organisational Measures (1) Before the commencement of processing, the Supplier shall document the execution of the necessary Technical and Organisational Measures, set out in advance of the awarding of the Order or Contract, specifically with regard to the detailed execution of the contract, and shall present these documented measures to the Client for inspection. Upon acceptance by the Client, the documented measures become the foundation of the contract. Insofar as the inspection/audit by the Client shows the need for amendments, such amendments shall be implemented by mutual agreement. (2) The Supplier shall establish the security in accordance with Article 28 Paragraph 3 Point c, and Article 32 GDPR in particular in conjunction with Article 5 Paragraph 1, and Paragraph 2 GDPR. The measures to be taken are measures of data security and measures that guarantee a protection level appropriate to the risk concerning confidentiality, integrity, availability and resilience of the systems. The state of the art, implementation costs, the nature, scope and purposes of processing as well as the probability of occurrence and the severity of the risk to the rights and freedoms of natural persons within the meaning of Article 32 Paragraph 1 GDPR must be taken into account. [Details in Appendix 1] (3) The Technical and Organisational Measures are subject to technical progress and further development. In this respect, it is permissible for the Supplier to implement alternative adequate measures. In so doing, the security level of the defined measures must not be reduced. Substantial changes must be documented.

  • Breaches and Security Incidents During the term of the Agreement, CONTRACTOR 27 agrees to implement reasonable systems for the discovery of any Breach of unsecured DHCS PI and PII 28 or security incident. CONTRACTOR agrees to give notification of any beach of unsecured DHCS PI 29 and PII or security incident in accordance with subparagraph F, of the Business Associate Contract, 30 Exhibit B to the Agreement.

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