Determining dependencies, assumptions and risk mitigations Sample Clauses

Determining dependencies, assumptions and risk mitigations. ‌ This step involves: • Determining in coordination with the affected SPs: the dependencies between the SPs, and where feasible with the affected AUs; • Determining in coordination with the affected SPs: the assumptions and risk mitigations that relate to more than one SP or AU; and • Only in case multiple SPs change their functional systems: developing an overarching safety argument (OASA). This step assures compliance with ATM/ANS.OR.A.045(e) and AMC1 ATM/ANS.OR.A.045(e). It eventually needs to result in agreed and aligned assumptions that can be used in the arguments of the involved parties for the change, such as the involved SPs safety cases and/or safety support cases (cf. Section 3.4). This way, each involved party should eventually be able to positively decide on the safety acceptability of the change. While it is recognized that mutual exchange with AUs is not always feasible, the change initiator should aim to inform and coordinate also with the AUs. If it is feasible to inform the AUs, they should also be involved in determining relevant assumptions and risk mitigations, and where possible dependencies. It is noted that for SPs performing a safety support assessment, formally, no risk mitigations can be identified, because there is no risk assessment. Nevertheless, improvements might be necessary to fulfil the service specification. Those may play a role in risk mitigations of another SP or AU involved. The development of an OASA is only required for situations in which two or more SPs change their functional system, unless they all perform safety support assessments 5. The OASA consists at least of: • an overall claim that each of the related SPs changing its functional system considers the overall change (i.e. including the interface and the part of the other SPs) acceptably safe; and • the necessary supporting arguments and evidence for this overall claim, including at least: o The coordination performed regarding dependencies, assumptions and risk mitigations, or a reference to that coordination; o The safety conclusions of the individual SPs, and/ or the unique references to these. The development of an OASA may well involve change developers and safety practitioners of the involved organizations: • Usually the change developers of involved organizations firstly need to agree on the modalities of a change, including dependencies, assumptions, and risk mitigations; and • Usually safety practitioners need to be involved in determining whether...
Sample 1
AutoNDA by SimpleDocs
Determining dependencies, assumptions and risk mitigations. In this step the SP and the airport determine the relevant dependencies, assumptions and risk mitigations. Examples of this are: o The entire AIP supplement with foreseen phases and workaround is a shared assumption. o A shared risk mitigation is that the airport will ensure that the works are stopped in time before low visibility procedures are started.
Sample 1

Related to Determining dependencies, assumptions and risk mitigations

  • ACCURACY OF CUSTOMER’S PLANS AND MEASUREMENTS a) The Company is entitled to rely on the accuracy of any plans, specifications and other information provided by the Customer. The Customer acknowledges and agrees that in the event that any of this information provided by the Customer is inaccurate the Company accepts no responsibility for any loss, damages or costs howsoever resulting from these inaccurate plans, specifications or other information.

  • Required Coverages For Generation Resources Of 20 Megawatts Or Less Each Constructing Entity shall maintain the types of insurance as described in section 11.1 paragraphs (a) through (e) above in an amount sufficient to insure against all reasonably foreseeable direct liabilities given the size and nature of the generating equipment being interconnected, the interconnection itself, and the characteristics of the system to which the interconnection is made. Additional insurance may be required by the Interconnection Customer, as a function of owning and operating a Generating Facility. All insurance shall be procured from insurance companies rated “A-,” VII or better by AM Best and authorized to do business in a state or states in which the Interconnection Facilities are located. Failure to maintain required insurance shall be a Breach of the Interconnection Construction Service Agreement.

  • Transition from Existing Evaluation System A) The parties may agree that 50% of more of Educators in the district will be evaluated under the new procedures at the outset of this Agreement, and 50% or fewer will be evaluated under the former evaluation procedures for the first year of implementation of the new procedures in this Agreement.

  • Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

  • OFFICE OF MANAGEMENT AND BUDGET (OMB) AUDIT REQUIREMENTS The parties shall comply with the requirements of the Single Audit Act of 1984, P.L. 98-502, ensuring that the single audit report includes the coverage stipulated in 2 CFR 200.

  • Testing Capabilities 7.2.2.10.2.1 LIS Acceptance Testing is provided where equipment is available, with the following test lines: seven-digit access to balance (100 type), milliwatt (102 type), nonsynchronous or synchronous, automatic transmission measuring (105 type), data transmission (107 type), loop-around, short circuit, open circuit, and non-inverting digital loop-back (108 type), and such other acceptance testing that may be needed to ensure that the service is operational and meets the applicable technical parameters.

  • DISASTER RECOVERY AND BUSINESS CONTINUITY The Parties shall comply with the provisions of Schedule 5 (Disaster Recovery and Business Continuity).

  • Skills and Abilities (i) Ability to communicate effectively both verbally and in writing.

  • Cost Responsibility for Interconnection Facilities and Distribution Upgrades 4.1 Interconnection Facilities 4.2 Distribution Upgrades

  • CHILD AND DEPENDENT ADULT/ELDER ABUSE REPORTING CONTRACTOR shall establish a procedure acceptable to ADMINISTRATOR to ensure that all employees, agents, subcontractors, and all other individuals performing services under this Agreement report child abuse or neglect to one of the agencies specified in Penal Code Section 11165.9 and dependent adult or elder abuse as defined in Section 15610.07 of the WIC to one of the agencies specified in WIC Section 15630. CONTRACTOR shall require such employees, agents, subcontractors, and all other individuals performing services under this Agreement to sign a statement acknowledging the child abuse reporting requirements set forth in Sections 11166 and 11166.05 of the Penal Code and the dependent adult and elder abuse reporting requirements, as set forth in Section 15630 of the WIC, and shall comply with the provisions of these code sections, as they now exist or as they may hereafter be amended.

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