CP Risks and Contingency Plans Sample Clauses

CP Risks and Contingency Plans. The Project Management Team will maintain a Risk Management plan as part of its periodic meetings. Risk Management is described in section 2.1.7. The Risk Management Plan aims to: - identify those risks which might impact the project; - ensure that each risk is analysed for probability and impact; - ensure that there is an agreed containment plan for each risk (the proposed plan may also be to do anything for an identified risk); - identify an appropriate contingency plan (as part of the containment plan) for high risks; - allocate ownership for the risks and its containment plan typically to a Work Package leader. Below the very first Risk Management Plan for the CP part of the project is presented. It will be brought up-to-date at the start of the project and also reported in new versions in the Annual reports) and in the Final Report. Failure to set up a technical environment that can in a trustful way test the tools and 2 4 8 Ensure adequate resourcing. Ensure clear ownership of responsibility between the consortium services developed by suppliers (Task 2.5 and the suppliers Task 7.1) The quality of the work done by the subcontractors is not satisfactory 2 5 10 The contract with the suppliers will foresee the possibility to ask for the reimbursement of the money in the case that the quality of the results does not respect the criteria established by the procurers in the contract itself. The contract will include periodic technical reviews that will be run as part of the monitoring activities of WP8. In the case of total failure, the following options will be considered by the General Assembly for decision: - to renounce the tools for the failing media type; - to negotiate with the supplier(s) in the reserve list Concerning the financial capability of the suppliers, a legal and financial assessment of the subcontractors will be run at the negotiation phase, before signing the contracts. Failure to establish agreement over IPR issues 1 4 4 Ensure IPR is clearly addressed within the tender. Serious disputes between consortium members 2 4 8 Aim to minimise the chances of disputes occurring by ensuring regular and clear communication between consortium members. Lead member and directors of work package should aim to build and nurture a culture of openness and trust, wherever possible. Where pre-dispute areas are suspected, offline discussions should be initiated. Where disputes become unavoidable, ensure a clearly agreed dispute management process is built ...
AutoNDA by SimpleDocs

Related to CP Risks and Contingency Plans

  • Contingency Plan Contractor is aware that unforeseen circumstances, Including damage to their Facility(ies), equipment breakdowns, weather-related emergencies and other Force Majeur events, may require their participation in non-scheduled operations in order to provide continuous service to the public. Contractor hereby acknowledges that, under this Agreement, they are prepared to commit to participation in training for such emergency scenarios and to provide vehicles and personnel to maintain uninterrupted service during impairment or breakdown of Contractor’s Facility or equipment, and in case of natural disaster or other emergency, Including the events described in Section 14.09.

  • Contingency Planning The Official Agency in conjunction with the Authority shall ensure that there are contingency plans in place at appropriate levels for dealing with food related crises and incidents. The contingency plan shall be in line with Article 115 of Regulation (EU) 2017/625 and include arrangements for activation of the plan, establishment of a crisis team, communication and information, out of hours contacts and on call services. As part of these plans, the Official Agency will provide the Authority with contact points for both office hours and out of office hours contact for emergency and crisis situations. The Official Agency shall facilitate training of personnel in the operation and exercise of the contingency plans. Periodic review of the plans shall take place in consultation with the Authority. The Official Agency shall implement the agreed Inter-Agency Protocol for the Management of a Food Crisis and guidance on Management of Outbreaks of Foodborne Illness as per Section 1.19.

  • Budget Contingency Clause A. It is mutually agreed that if the Budget Act of the current year and/or any subsequent years covered under this Agreement does not appropriate sufficient funds for the program, this Agreement shall be of no further force and effect. In this event, the State shall have no liability to pay any funds whatsoever to Contractor or to furnish any other considerations under this Agreement and Contractor shall not be obligated to perform any provisions of this Agreement. B. If funding for any fiscal year is reduced or deleted by the Budget Act for purposes of this program, the State shall have the option to either cancel this Agreement with no liability occurring to the State, or offer an agreement amendment to Contractor to reflect the reduced amount.

  • Clean Air Act and Federal Water Pollution Control Act The contractor agrees to comply with all applicable standards, orders or regulations issued pursuant to the Clean Air Act, as amended, 42 U.S.C. § 7401 et seq.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.

  • Management Plan The Management Plan is the description and definition of the phasing, sequencing and timing of the major Individual Project activities for design, construction procurement, construction and occupancy as described in the IPPA.

  • BUDGET CONTINGENCY If the Budget Act of the current year covered under this Grant Agreement does not appropriate sufficient funds for this program, this Grant Agreement shall be of no force and effect. This provision shall be construed as a condition precedent to the obligation of the State to make any payments under this Grant Agreement. In this event, the State shall have no liability to pay any funds whatsoever to the Grantee or to furnish any other considerations under this Grant Agreement and the Grantee shall not be obligated to perform any provisions of this Grant Agreement. Nothing in this Grant Agreement shall be construed to provide the Grantee with a right of priority for payment over any other Grantee. If funding for any fiscal year after the current year covered by this Grant Agreement is reduced or deleted by the Budget Act, by Executive Order, or by order of the Department of Finance, the State shall have the option to either cancel this Grant Agreement with no liability occurring to the State, or offer a Grant Agreement amendment to the Grantee to reflect the reduced amount.

  • CLEAN AIR ACT AND THE FEDERAL WATER POLLUTION CONTROL ACT (a) If the Sub-Recipient, with the funds authorized by this Agreement, enters into a contract that exceeds $150,000, then any such contract must include the following provision: Contractor agrees to comply with all applicable standards, orders or regulations issued pursuant to the Clean Air Act (42 U.S.C. 7401-7671q) and the Federal Water Pollution Control Act as amended (33 U.S.C. 1251-1387), and will report violations to FEMA and the Regional Office of the Environmental Protection Agency (EPA).

  • Fraud, Waste, and Abuse Contractor understands that HHS does not tolerate any type of fraud, waste, or abuse. Violations of law, agency policies, or standards of ethical conduct will be investigated, and appropriate actions will be taken. Pursuant to Texas Government Code, Section 321.022, if the administrative head of a department or entity that is subject to audit by the state auditor has reasonable cause to believe that money received from the state by the department or entity or by a client or contractor of the department or entity may have been lost, misappropriated, or misused, or that other fraudulent or unlawful conduct has occurred in relation to the operation of the department or entity, the administrative head shall report the reason and basis for the belief to the Texas State Auditor’s Office (SAO). All employees or contractors who have reasonable cause to believe that fraud, waste, or abuse has occurred (including misconduct by any HHS employee, Grantee officer, agent, employee, or subcontractor that would constitute fraud, waste, or abuse) are required to immediately report the questioned activity to the Health and Human Services Commission's Office of Inspector General. Contractor agrees to comply with all applicable laws, rules, regulations, and System Agency policies regarding fraud, waste, and abuse including, but not limited to, HHS Circular C-027. A report to the SAO must be made through one of the following avenues: ● SAO Toll Free Hotline: 1-800-TX-AUDIT ● SAO website: xxxx://xxx.xxxxx.xxxxx.xx.xx/ All reports made to the OIG must be made through one of the following avenues: ● OIG Toll Free Hotline 0-000-000-0000 ● OIG Website: XxxxxxXxxxxXxxxx.xxx ● Internal Affairs Email: XxxxxxxxXxxxxxxXxxxxxxx@xxxx.xxxxx.xx.xx ● OIG Hotline Email: XXXXxxxxXxxxxxx@xxxx.xxxxx.xx.xx. ● OIG Mailing Address: Office of Inspector General Attn: Fraud Hotline MC 1300 P.O. Box 85200 Austin, Texas 78708-5200

  • Standard Hazard and Flood Insurance Policies For each Mortgage Loan (other than a Cooperative Loan), the Master Servicer shall maintain, or cause to be maintained by each Servicer, standard fire and casualty insurance and, where applicable, flood insurance, all in accordance with the provisions of this Agreement and the related Servicing Agreement, as applicable. It is understood and agreed that such insurance shall be with insurers meeting the eligibility requirements set forth in the applicable Servicing Agreement and that no earthquake or other additional insurance is to be required of any Mortgagor or to be maintained on property acquired in respect of a defaulted loan, other than pursuant to such applicable laws and regulations as shall at any time be in force and as shall require such additional insurance. Pursuant to Section 4.01, any amounts collected by the Master Servicer, or by any Servicer, under any insurance policies maintained pursuant to this Section 9.16 or any Servicing Agreement (other than amounts to be applied to the restoration or repair of the property subject to the related Mortgage or released to the Mortgagor in accordance with the applicable Servicing Agreement) shall be deposited into the Collection Account, subject to withdrawal pursuant to Section 4.02. Any cost incurred by the Master Servicer or any Servicer in maintaining any such insurance if the Mortgagor defaults in its obligation to do so shall be added to the amount owing under the Mortgage Loan where the terms of the Mortgage Loan so permit; provided, however, that the addition of any such cost shall not be taken into account for purposes of calculating the distributions to be made to Certificateholders and shall be recoverable by the Master Servicer or such Servicer pursuant to Section 4.02.

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