– Producer Declaration Sample Clauses

– Producer Declaration. Under the Agriculture Marketing Programs Act (AMPA), the Spring Credit Advance Program (SCAP), Enhanced Spring Credit Advance Program (ESCAP), Advance Payments Program (APP) and the New Advance Payments Program (NAPP), the Producer is responsible for ensuring that all individual producers, related producers, associates with interest in the Agricultural Product in question and associated advances are clearly identified. For the purposes of applying as an individual producer, I am not required by the Income Tax Act (Canada) to report income from other farming operations or other corporations carrying on a farm business, other than the one named in this Application. I certify the above to be true and correct. I agree to report any future changes in the Producer’s structure (as applicable). I am aware that to make a false statement is a criminal offence.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
– Producer Declaration. Under the Agriculture Marketing Programs Act (AMPA), the Spring Credit Advance Program (SCAP), Enhanced Spring Credit Advance Program (ESCAP), Advance Payments Program (APP) and the New Advance Payments Program (NAPP), the Producer is responsible for ensuring that all individual producers, related producers, associates with interest in the Agricultural Product in question and associated advances are clearly identified. Producer Signature Date
Sample 1
– Producer Declaration. I, the undersigned, declare that I have read and understand those relevant portions of the agreement between Antra Music Group, Inc. ("Antra") and Xxxxxxx Xxxxx (professionally known as "Crush" and referred to below as "Artist") dated as of October 1, 1999 ("Artist Agreement") that pertain to my record production endeavors. I hereby certify that I have produced or will have produced certain master recordings embodying Artist's featured performance ("Masters") pursuant to an agreement between Artist and me ("Producer Agreement") which provides for valuable consideration to be paid to me. As part of my material obligations pursuant to the Producer Agreement and for the express and direct benefit of Antra, I hereby:
Sample 1
– Producer Declaration. Under the Agriculture Marketing Programs Act (AMPA), the Spring Credit Advance Program (SCAP), Enhanced Spring Credit Advance Program (ESCAP), Advance Payments Program (APP) and the New Advance Payments Program (NAPP), the Producer is responsible for ensuring that all individual producers, related producers, associates with Interest in the Agricultural Product in question and associated advances are clearly identified. For the purposes of applying as an individual producer, I am not required by the Income Tax Act (Canada) to report income from other farming operations or other corporations carrying on a farm business, other than the one named in this Application. Producer Signature Date
Sample 1
– Producer Declaration. Under the Agriculture Marketing Programs Act (AMPA), the Spring Credit Advance Program (SCAP), Enhanced Spring Credit Advance Program (ESCAP), Advance Payments Program (APP) and the New Advance Payments Program (NAPP), the Producer is responsible for ensuring that all individual producers, related producers, associates with interest in the Agricultural Product in question and associated advances are clearly identified. For the purposes of applying as an individual producer, I am not required by the Income Tax Act (Canada) to report income from other farming operations or other corporations carrying on a farm business, other than the one named in this Application. I certify the above to be true and correct. I agree to report any future changes in the Producer’s structure (as applicable). I am aware that to make a false statement is a criminal offence. Producer Signature Date The personal and/or business information submitted on this form is collected under the authority of Section 10 of the Agricultural Marketing Programs Act. Any personal information collected by the Administrator will be used to administer the program in accordance with the Personal Information Protection and Electronic Documents Act (PIPEDA) or under legislation applicable within their jurisdiction. Any personal and/or business information may be disclosed to Agriculture and Agri-Food Canada (AAFC) and will be used to administer the program in accordance with the Privacy Act and Access to Information Act. The information may be used for the purposes consented to in the Declaration. Individuals have the right to request access to and correction of their personal information. Should you have any questions concerning your information and privacy, please contact: Agriculture and Agri-Food Canada’s Access to Information and Privacy Director, Floor 00, 0000 Xxxxxxxx Xxxx, Xxxxx 0, Xxxxxx XX X0X 0X0 or by email at XXXX.Xxxxxxx-xxxxxxxxx.XXX@XXX.XX.XX and reference AAFC’s personal information bank Agricultural Marketing Programs Act: Advance Payments Program, PPU 140. (2023).
Sample 1

Related to – Producer Declaration

  • Condominiums/Planned Unit Developments If the Mortgaged Property is a condominium unit or a planned unit development (other than a de minimis planned unit development) such condominium or planned unit development project such Mortgage Loan was originated in accordance with, and the Mortgaged Property meets the guidelines set forth in the Originator's Underwriting Guidelines;

  • Unbundled Copper Loop – Designed (UCL-D) 2.4.2.1 The UCL-D will be provisioned as a dry copper twisted pair (2- or 4-wire) Loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters). 2.4.2.2 A UCL-D will be 18,000 feet or less in length and is provisioned according to Resistance Design parameters, may have up to 6,000 feet of bridged tap and will have up to 1300 Ohms of resistance. 2.4.2.3 The UCL-D is a designed circuit, is provisioned with a test point, and comes standard with a DLR. OC is a chargeable option for a UCL-D; however, OC is always required on UCLs where a reuse of existing facilities has been requested by Telepak Networks. 2.4.2.4 These Loops are not intended to support any particular services and may be utilized by Telepak Networks to provide a wide-range of telecommunications services as long as those services do not adversely affect BellSouth’s network. This facility will include a Network Interface Device (NID) at the customer’s location for the purpose of connecting the Loop to the customer’s inside wire. 2.4.2.5 Upon the Effective Date of this Agreement, Unbundled Copper Loop – Long (UCL-L) elements will no longer be offered by BellSouth and no new orders for UCL-L will be accepted. Any existing UCL-Ls that were provisioned prior to the Effective Date of this Agreement will be grandfathered at the rates set forth in the Parties’ interconnection agreement that was in effect immediately prior to the Effective Date of this Agreement. Existing UCL-Ls that were provisioned prior to the Effective Date of this Agreement may remain connected, maintained and repaired according to BellSouth’s TR73600 and may remain connected until such time as they are disconnected by Telepak Networks or BellSouth provides ninety

  • Operating Agreement The Borrower will not amend, modify, waive or terminate any provision of its operating agreement without the prior written consent of the Administrative Agent.

  • Operating Partnership Agreement The Operating Partnership Agreement, in substantially the form attached hereto as Exhibit B, shall have been executed and delivered by the partners of the Operating Partnership and shall be in full force and effect and, except as contemplated by Section 2.03 or the other Formation Transaction Documents, shall not have been amended or modified.

  • Unbundled Copper Loop – Non-Designed (UCL-ND 2.4.3.1 The UCL–ND is provisioned as a dedicated 2-wire metallic transmission facility from BellSouth’s Main Distribution Frame to a customer’s premises (including the NID). The UCL-ND will be a “dry copper” facility in that it will not have any intervening equipment such as load coils, repeaters, or digital access main lines (“DAMLs”), and may have up to 6,000 feet of bridged tap between the end user’s premises and the serving wire center. The UCL-ND typically will be 1300 Ohms resistance and in most cases will not exceed 18,000 feet in length, although the UCL-ND will not have a specific length limitation. For loops less than 18,000 feet and with less than 1300 Ohms resistance, the loop will provide a voice grade transmission channel suitable for loop start signaling and the transport of analog voice grade signals. The UCL-ND will not be designed and will not be provisioned with either a DLR or a test point. 2.4.3.2 The UCL-ND facilities may be mechanically assigned using BellSouth’s assignment systems. Therefore, the Loop Make Up process is not required to order and provision the UCL-ND. However, Lightyear can request Loop Make Up for which additional charges would apply. 2.4.3.3 At an additional charge, BellSouth also will make available Loop Testing so that Lightyear may request further testing on the UCL-ND. Rates for Loop Testing are as set forth in Exhibit B of this Attachment. 2.4.3.4 UCL-ND loops are not intended to support any particular service and may be utilized by Lightyear to provide a wide-range of telecommunications services so long as those services do not adversely affect BellSouth’s network. The UCL-ND will include a Network Interface Device (NID) at the customer’s location for the purpose of connecting the loop to the customer’s inside wire. 2.4.3.5 Order Coordination (OC) will be provided as a chargeable option and may be utilized when the UCL-ND provisioning is associated with the reuse of BellSouth facilities. Order Coordination -Time Specific (OC-TS) does not apply to this product. 2.4.3.6 Lightyear may use BellSouth’s Unbundled Loop Modification (ULM) offering to remove bridge tap and/or load coils from any loop within the BellSouth network. Therefore, some loops that would not qualify as UCL-ND could be transformed into loops that do qualify, using the ULM process.

  • Partnership Agreements Each of the partnership agreements, declarations of trust or trust agreements, limited liability company agreements (or other similar agreements) and, if applicable, joint venture agreements to which the Company or any of its subsidiaries is a party has been duly authorized, executed and delivered by the Company or the relevant subsidiary, as the case may be, and constitutes the valid and binding agreement of the Company or such subsidiary, as the case may be, enforceable in accordance with its terms, except as the enforcement thereof may be limited by (A) the effect of bankruptcy, insolvency or other similar laws now or hereafter in effect relating to or affecting creditors’ rights generally or (B) the effect of general principles of equity, and the execution, delivery and performance of such agreements did not, at the time of execution and delivery, and does not constitute a breach of or default under the charter or bylaws, partnership agreement, declaration of trust or trust agreement, or limited liability company agreement (or other similar agreement), as the case may be, of the Company or any of its subsidiaries or any of the Agreements and Instruments or any law, administrative regulation or administrative or court order or decree.

  • Developer Attachment Facilities Developer shall design, procure, construct, install, own and/or control the Developer Attachment Facilities described in Appendix A hereto, at its sole expense.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • Interconnection Agreement Seller shall comply with the terms and conditions of the Interconnection Agreement.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

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