Proposed Ways of Addressing Sample Clauses

Proposed Ways of Addressing. Issues‌ Table 2: Recommendations from SP12 data Protection and Privacy Opinion Number Recommendation Implementation 1 Create a coherent approach to data governance that covers all aspects of research, including data generated, data imported, and data exported by the HBP. Data protection should be one component of this data governance structure. It is likely that this will be achieved by: A Data Governance Working Group (DGWG) has been set up, and continues working on all aspects of data in the HBP. a Appointing a person who takes responsibility for privacy and data protection across the HBP. This person should be a senior leader and member of the Scientific and Infrastructure Board of the HBP. A proposal for a data protection officer role has been formulated by the DGWG and agreed to by HBP directorship. b Setting up a Data Governance Committee for the HBP comprised of representatives of all stakeholders involved in data collection and processing, and representatives of patient groups and of the general public to review privacy and data protection processes. The DGWG is working with SP representatives on these and related issues. Other activities concerning informed consent are underway (e.g. the creation of an SOP, and the formulation of a stakeholder forum). c Establishing a regular Privacy Impact Assessment (PIA) for the HBP, and a Research Audit structure that can identify, authorise and audit all users of the MIP. Ethics management is in regular contact with SP8 especially regarding the formulation of a PIA. The DGWG discusses related issues especially in anticipation of the GDPR. d Ensuring principles of data stewardship which will include finding ways of informing participants in a simple way of how their data has contributed to the public good. This may be achieved by public Some provision in this area is already expected by local ethics regulations, and some survey respondents were: “...unsure whether very *global* engagement and a dissemination programme for the results of the HBP dissemination program are actually informative for research participants.” In complement, “...short cycles that go from the acquired data to the actual results” might be preferable and be pursued on a broad agenda of ‘data stewardship’ exploration. See below (4.1) 2 As a general rule, adopt a privacy model when anonymising data in view of releasing them for secondary use. A privacy model specifies a precise privacy guarantee that can be explained to any interested party...
AutoNDA by SimpleDocs

Related to Proposed Ways of Addressing

  • PROCEDURAL HISTORY On May 16, 2008, pursuant to 83 Illinois Administrative Code Part 763, Illinois Bell Telephone Company (“AT&T Illinois”) and Vertex Broadband, Corp. d/b/a AthenaTel d/b/a Reason to Switch d/b/a TownLink Communications d/b/a INT Connections (“Vertex”), filed a joint petition for approval of the 1st Amendment to the Interconnection Agreement dated May 6, 2008 under Section 252 of the Telecommunications Act of 1996 (47 U.S.C. § 252 et seq.) (“the Act”). The 1st Amendment to the Agreement was submitted with the petition. A statement in support of the petition was filed along with verifications sworn to by Xxxxx X. Xxxx, Xx. on behalf of AT&T Illinois and by Xxxxxx X. Xxxxx on behalf of Vertex, stating that the facts contained in the petition are true and correct to the best of their knowledge, information, and belief. Pursuant to notice as required by law and the rules and regulations of the Commission, this matter came on for hearing by the duly authorized Administrative Law Judge of the Commission at its offices in Chicago, Illinois, on June 9, 2008. Staff previously filed the Verified Statement of A. Xxxxxxxx Xxxxxxx of the Commission’s Telecommunications Division on June 6, 2008. At the hearing on June 9, 2008, AT&T Illinois, Vertex and Staff appeared and agreed that there were no unresolved issues in this proceeding. Subsequently Xx. Xxxxxxx’x Verified Statement was admitted into evidence and the record was marked “Heard and Taken.”

  • Dimensions Education: Bachelor’s or Master’s Degree in Computer Science, Information Systems, or other related field. Or equivalent work experience. A minimum of 10 years of IT (including Web/Internet, database applications and data warehousing) and business/industry work experience, with at least 3 years of leadership experience in managing multiple, large, cross-functional teams or project, and influencing senior level management and key stakeholders.

  • Parameters In calculating the MtM Exposure for each Transaction, the following parameters are set on the Transaction Date: ▪ On-Peak Initial Xxxx Xxxxx ▪ Off-Peak/On-Peak Price Ratio ▪ Off-Peak Initial Xxxx Xxxxx ▪ MW-Measure: initial Capacity PLC Per Tranche ▪ On-Peak Estimated Energy Quantity Per MW-Measure for each of the twelve calendar months ▪ Off-Peak Estimated Energy Quantity Per MW-Measure for each of the twelve calendar months ▪ Number of awarded Tranches In calculating the MtM Exposure for each Transaction, the following parameters are set each Business Day subsequent to the Transaction Date: ▪ On-Peak Forward Price ▪ Off-Peak Forward Price ▪ Current Capacity PLC Per Tranche ▪ On-Peak Estimated Energy Quantity ▪ Off-Peak Estimated Energy Quantity Process to Update the On-Peak Initial Mark Prices and Off-Peak Initial Mark Prices on a Daily Basis On each Business Day subsequent to the Transaction Date, the Pricing Agent will contact four Reference Market-Makers to obtain price quotes for on-peak and off-peak energy for PJM Western Hub. The Pricing Agent may not rely upon quotes from Seller or any Affiliate of Seller. The updated mark for a month will be equal to the average mark for that month over all sources from which a quote is available. If a monthly quote is available from any source, only the monthly quote or monthly quotes shall be used. Where quotes provide a bid and ask, the average shall be used. Where a quote for an individual month is unavailable, but the month is quoted as part of a “packaged” quote (e.g., January 2011 is only available in the form of a January/February 2011 “packaged” quote or an annual quote): ▪ If the other month/months of the package quote is/are also unavailable, then the marks for all months of the package will be calculated by multiplying the packaged quote by the ratio of the corresponding month to the corresponding calculated package quote from the previous day. Example: There are no On-Peak quotes available on day X during the contract for July 2011 or August 2011. However, there is an On-Peak July/August 2011 packaged quote of $73.00/MWh available. The On-Peak marks from day X-1 for July 2011 and August 2011 were $73.50/MWh and $76.50/MWh respectively. The day X On-Peak mark for July 2011 is set at 73.00 * [73.50] / [( (73.50 * 352) + (76.50 * 336) ) / (352+336) ] = 73 * (73.50/ 74.97) = $71.57/MWh. The day X On-Peak mark for August 2011 is set at 73.00 * [76.50] / [( (73.50 * 352) + (76.50*336) ) / (352+336) ] = 73 * (76.50 / 74.97) = $74.49/MWh. ▪ If the other month/months of the package quote is/are available, then the mark for the month will be set such that the average of the month and the other month(s) (weighted for either the On-Peak Hours or Off-Peak Hours as applicable) equals the packaged quote (see calculation example below).

  • Scaling “Scaling,” as used herein, involves:

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • NONPAYMENT AND PROCEDURES FOR DISCONNECTION 12.1 If a Party is furnished Interconnection Services under the terms of this Agreement in more than one (1) state, Section 12.2 below through Section 12.19 below, inclusive, shall be applied separately for each such state. 12.2 Failure to pay charges shall be grounds for disconnection of Interconnection Services furnished under this Agreement. If a Party fails to pay any charges billed to it under this Agreement, including but not limited to any Late Payment Charges or Unpaid Charges, and any portion of such Unpaid Charges remain unpaid after the Bill Due Date, the Billing Party will send a Discontinuance Notice to such Non-Paying Party. The Non-Paying Party must remit all Unpaid Charges to the Billing Party within fifteen (15) calendar days of the Discontinuance Notice. 12.3 AT&T-21STATE will also provide any written notification to any Commission as required by any State Order or Rule. 12.4 If the Non-Paying Party desires to dispute any portion of the Unpaid Charges, the Non-Paying Party must complete all of the following actions not later than fifteen (15) calendar days following receipt of the Billing Party’s notice of Unpaid Charges: 12.4.1 notify the Billing Party in writing which portion(s) of the Unpaid Charges it disputes, including the total Disputed Amounts and the specific details listed in Section 13.4 below of this Agreement, together with the reasons for its dispute; and 12.4.2 pay all undisputed Unpaid Charges to the Billing Party; and 12.4.3 pay all Disputed Amounts (other than Disputed Amounts arising from Intercarrier Compensation) into an interest bearing escrow account that complies with the requirements set forth in Section 11.10 above; and 12.4.4 furnish written evidence to the Billing Party that the Non-Paying Party has established an interest bearing escrow account that complies with all of the terms set forth in Section 11.10 above and deposited a sum equal to the Disputed Amounts into that account (other than Disputed Amounts arising from Intercarrier Compensation). Until evidence that the full amount of the Disputed Charges (other than Disputed Amounts arising from Intercarrier Compensation) has been deposited into an escrow account that complies with Section

  • MEASUREMENT AND VERIFICATION The goal of this task is to report the benefits resulting from this project by performing measurement and verification (M&V) of fossil fuel consumption and associated GHG reduction. • Enter into agreement with M&V subcontractor per Task 1.9 • Coordinate site visits with the M&V subcontractor at the demonstration site(s) • Develop M&V protocol for pre-installation measurements (and calculations): o Electric, natural gas and/or other fossil fuel consumption and GHG emissions (use appropriate emissions factor from Attachment 8 of the grant solicitation) of the equipment/process/system(s)/sub-system(s) that are to be upgraded and/or replaced and/or modified. o Ensure installation of sub-metering equipment and data loggers for pre/post data analysis. • Prepare and provide a detailed M&V Plan for each project demonstration site to include but not be limited to: o A description of the monitoring equipment and instrumentation which will be used. o A description of the key input parameters and output metrics which will be measured. o A description of the M&V protocol and analysis methods to be employed. o A description of the independent, third-party M&V services to be employed, if applicable. • Perform three months (or shorter period as approved in writing by the CAM) of pre- installation measurements (and calculations) based on the M&V protocol for pre- installation. • Prepare and provide a Pre-Installation M&V Findings Report for the demonstration site that includes M&V protocol, pre-install measurements (and calculations), analysis, and results performed in this task. • Develop M&V protocol for post-installation measurements (and calculations) of: o Electric, natural gas and/or other fossil fuel consumption and GHG emissions (use appropriate emissions factor from Attachment 8 of the grant solicitation) of the equipment/process/system(s)/sub-system(s) that will be upgraded and/or replaced and/or modified • Perform 12 months or two seasons, for seasonal facilities, (or shorter period as approved in writing by the CAM) of post-installation measurements based on M&V protocol for post-installation. • Provide a summary of post-installation M&V progress in Progress Report(s) (see subtask 1.5) which shall include but not be limited to:

  • Audit and Testing 4.1 The Contractor shall conduct tests of the processes and countermeasures contained in the Security Plan ("Security Tests") on an annual basis or as otherwise agreed by the Parties. The date, timing, content and conduct of such Security Tests shall be agreed in advance with the Authority. 4.2 The Authority shall be entitled to send a representative to witness the conduct of the Security Tests. The Contractor shall provide the Authority with the results of such tests (in a form approved by the Authority in advance) as soon as practicable after completion of each Security Test. 4.3 Without prejudice to any other right of audit or access granted to the Authority pursuant to this Contract, the Authority shall be entitled at any time and without giving notice to the Contractor to carry out such tests (including penetration tests) as it may deem necessary in relation to the Security Plan and the Contractor's compliance with and implementation of the Security Plan. The Authority may notify the Contractor of the results of such tests after completion of each such test. Security Tests shall be designed and implemented so as to minimise the impact on the delivery Services. If such tests impact adversely on its ability to deliver the Services to the agreed Service Levels, the Contractor shall be granted relief against any resultant under-performance for the period of the tests. 4.4 Where any Security Test carried out pursuant to paragraphs 4.2 or 4.3 above reveals any actual or potential security failure or weaknesses, the Contractor shall promptly notify the Authority of any changes to the Security Plan (and the implementation thereof) which the Contractor proposes to make in order to correct such failure or weakness. Subject to the Authority's approval in accordance with paragraph 3.12, the Contractor shall implement such changes to the Security Plan in accordance with the timetable agreed with the Authority or, otherwise, as soon as reasonably possible. For the avoidance of doubt, where the change to the Security Plan to address a non-compliance with the Security Policy or security requirements, the change to the Security Plan shall be at no additional cost to the Authority. For the purposes of this paragraph 4, a weakness means a vulnerability in security and a potential security failure means a possible breach of the Security Plan or security requirements.

  • 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.

  • Number Resources, Rate Center Areas and Routing Points 8.1 Nothing in this Agreement shall be construed to limit or otherwise adversely affect in any manner either Party’s right to employ or to request and be assigned any Central Office Codes (“NXX”) pursuant to the Central Office Code Assignment Guidelines and any relevant FCC or Commission orders, as may be amended from time to time, or to establish, by Tariff or otherwise, Rate Center Areas and Routing Points corresponding to such NXX codes. 8.2 It shall be the responsibility of each Party to program and update its own switches and network systems pursuant to information provided in the LERG in order to recognize and route traffic to the other Party’s assigned NXX codes. Except as expressly set forth in this Agreement, neither Party shall impose any fees or charges whatsoever on the other Party for such activities. 8.3 Unless otherwise required by Commission order, the Rate Center Areas will be the same for each Party. During the term of this Agreement, Onvoy shall adopt the Rate Center Area and Rate Center Points that the Commission has approved for Frontier within the LATA and Tandem serving area. Onvoy shall assign whole NPA-NXX codes to each Rate Center Area unless otherwise ordered by the FCC, the Commission or another governmental entity of appropriate jurisdiction, or the LEC industry adopts alternative methods of utilizing NXXs. 8.4 Onvoy will also designate a Routing Point for each assigned NXX code. Onvoy shall designate one location for each Rate Center Area in which the Onvoy has established NXX code(s) as the Routing Point for the NPA-NXXs associated with that Rate Center Area, and such Routing Point shall be within the same LATA as the Rate Center Area but not necessarily within the Rate Center Area itself. Unless specified otherwise, calls to subsequent NXXs of Onvoy will be routed in the same manner as calls to Xxxxx’s initial NXXs. 8.5 Notwithstanding anything to the contrary contained herein, nothing in this Agreement is intended, and nothing in this Agreement shall be construed, to in any way constrain Onvoy’s choices regarding the size of the local calling area(s) that Onvoy may establish for its Customers, which local calling areas may be larger than, smaller than, or identical to Frontier’s local calling areas.

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