VOIDING A DMR. Steps to take in order to put material back into production after a DMR has been written.
VOIDING A DMR Sample Clauses
Related to VOIDING A DMR
Undue Burden and Fundamental Alteration For any technology-related requirement in this Agreement for which the Recipient asserts an undue burden or fundamental alteration defense, such assertion may only be made by the Superintendent or by an individual designated by the Superintendent and who has budgetary authority after considering all resources available for use in the funding and operation of the service, program, or activity, and must be accompanied by a written statement of the reasons for reaching that conclusion, including the cost of meeting the requirement and the available funding and other resources. The written statement will be certified by the determining official. If such a determination is made, the certifying official will describe in the written statement how it will provide equally effective alternate access, i.e., other action that would not result in such an alteration or such burdens but would nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services provided by the Recipient as their nondisabled peers.
Private Letter Ruling or Change or Clarification of Law At Developer’s request and expense, Connecting Transmission Owner shall file with the IRS a request for a private letter ruling as to whether any property transferred or sums paid, or to be paid, by Developer to Connecting Transmission Owner under this Agreement are subject to federal income taxation. Developer will prepare the initial draft of the request for a private letter ruling, and will certify under penalties of perjury that all facts represented in such request are true and accurate to the best of Developer’s knowledge. Connecting Transmission Owner and Developer shall cooperate in good faith with respect to the submission of such request. Connecting Transmission Owner shall keep Developer fully informed of the status of such request for a private letter ruling and shall execute either a privacy act waiver or a limited power of attorney, in a form acceptable to the IRS, that authorizes Developer to participate in all discussions with the IRS regarding such request for a private letter ruling. Connecting Transmission Owner shall allow Developer to attend all meetings with IRS officials about the request and shall permit Developer to prepare the initial drafts of any follow-up letters in connection with the request.
Interconnection Customer Payments Not Taxable The Parties intend that all payments or property transfers made by the Interconnection Customer to the Participating TO for the installation of the Participating TO's Interconnection Facilities and the Network Upgrades shall be non-taxable, either as contributions to capital, or as a refundable advance, in accordance with the Internal Revenue Code and any applicable state income tax laws and shall not be taxable as contributions in aid of construction or otherwise under the Internal Revenue Code and any applicable state income tax laws.
Network Upgrades and Distribution Upgrades The Participating TO shall design, procure, construct, install, and own the Network Upgrades and Distribution Upgrades described in Appendix A. The Interconnection Customer shall be responsible for all costs related to Distribution Upgrades. Unless the Participating TO elects to fund the capital for the Distribution Upgrades and Network Upgrades, they shall be solely funded by the Interconnection Customer.
Unbundled Network Terminating Wire (UNTW) 2.8.3.1 UNTW is unshielded twisted copper wiring that is used to extend circuits from an intra-building network cable terminal or from a building entrance terminal to an individual End User’s point of demarcation. It is the final portion of the Loop that in multi-subscriber configurations represents the point at which the network branches out to serve individual subscribers. 2.8.3.2 This element will be provided in MDUs and/or Multi-Tenants Units (MTUs) where either Party owns wiring all the way to the End User’s premises. Neither Party will provide this element in locations where the property owner provides its own wiring to the End User’s premises, where a third party owns the wiring to the End User’s premises.
Termination and Data Destruction Upon Project Close-out, the Requester and Approved Users agree to destroy all copies, versions, and Data Derivatives of the dataset(s) retrieved from NIH-designated controlled-access databases, on both local servers and hardware, and if cloud computing was used, delete the data and cloud images from cloud computing provider storage, virtual and physical machines, databases, and random access archives, in accord with the NIH Security Best Practices for Controlled-Access Data Subject to the NIH Genomic Data Sharing (GDS) Policy. However, the Requester may retain these data as necessary to comply with any institutional policies (e.g., scientific data retention policy), law, and scientific transparency expectations for disseminated research results, and/or journal policies. A Requester who retains data for any of these purposes continues to be a xxxxxxx of the data and is responsible for the management of the retained data in accordance with the NIH Security Best Practices for ControlledAccess Data Subject to the NIH Genomic Data Sharing (GDS) Policy, and any institutional policies. Any retained data may only be used by the PI and Requester to support the findings (e.g., validation) resulting from the research described in the DAR that was submitted by the Requester and approved by NIH. The data may not be used to answer any additional research questions, even if they are within the scope of the approved Data Access Request, unless the Requester submits a new DAR and is approved by NIH to conduct the additional research. If a Requester retains data for any of these purposes, the relevant portions of Terms 4, 5, 6, 7, 8, and 12 remain in effect after termination of this Data Use Certification Agreement. These terms remain in effect until the data is destroyed.
Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.
Other Methods of Procurement of Consultants’ Services The following table specifies the methods of procurement, other than Quality and Cost-based Selection, which may be used for consultants’ services. The Procurement Plan shall specify the circumstances under which such methods may be used. (a) Quality-based Selection (b) Selection under a Fixed Budget
Alternative Work Schedule An alternate forty (40) hour work schedule (other than five (5) uniform and consecutive eight (8) hour days in a seven (7) day period), or for hospital personnel an eighty (80) hour workweek in a fourteen (14) day period and other mutually agreed upon schedules that comply with applicable federal and state law. Employee work schedules normally include two (2) consecutive days off.
Sub-processing 11.1 The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the sub-processor which imposes the same obligations on the sub- processor as are imposed on the data importer under the Clauses. Where the sub-processor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the sub-processor’s obligations under such agreement. 11.2 The prior written contract between the data importer and the sub-processor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the sub-processor shall be limited to its own processing operations under the Clauses. 11.3 The provisions relating to data protection aspects for sub-processing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established, namely ........................................ 11.4 The data exporter shall keep a list of sub-processing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5(j), which shall be updated at least once a year. The list shall be available to the data exporter’s data protection supervisory authority.
