Requirements for Results of the Project Implementation Sample Clauses

Requirements for Results of the Project Implementation. 53. The obligatory result on the results of realization of the Project should be the activity connected with practical application of RSSTA, including results of intellectual activity, bringing new or improved goods, processes or services to the market and receipt of income from their realization.
AutoNDA by SimpleDocs

Related to Requirements for Results of the Project Implementation

  • Project Monitoring Reporting Evaluation A. The Project Implementing Entity shall monitor and evaluate the progress of its activities under the Project and prepare Project Reports in accordance with the provisions of Section 5.08(b) of the General Conditions and on the basis of indicators agreed with the Bank. Each such report shall cover the period of one

  • Project Implementation 2. The Borrower shall:

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • Implementation of and Reporting on the Project A. The Grantee shall implement and complete the Project in accordance with Exhibit A and with the plans and specifications contained in its Grant Application, which is on file with the State and is incorporated by reference. Modification of the Project shall require prior written approval of the State.

  • Implementation Report Within 150 days after the Effective Date, Extendicare shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include:

  • Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).

  • RETENTION AND ACCESS REQUIREMENTS FOR RECORDS ADOF shall retain all records pertinent to this agreement for a period of no less than 3 years from the expiration or termination date. As used in this provision, records includes books, documents, accounting procedures and practice, and other data, regardless of the type or format. ADOF shall provide access and the right to examine all records related to this agreement to the U.S. Forest Service Inspector General, or Comptroller General or their authorized representative. The rights of access in this section must not be limited to the required retention period but must last as long as the records are kept. If any litigation, claim, negotiation, audit, or other action involving the records has been started before the end of the 3-year period, the records must be kept until all issues are resolved, or until the end of the regular 3-year period, whichever is later. Records for nonexpendable property acquired in whole or in part, with Federal funds must be retained for 3 years after its final disposition.

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • EDD Independent Contractor Reporting Requirements Effective January 1, 2001, the County of Orange is required to file in accordance with subdivision (a) of Section 6041A of the Internal Revenue Code for services received from a “service provider” to whom the County pays $600 or more or with whom the County enters into a contract for $600 or more within a single calendar year. The purpose of this reporting requirement is to increase child support collection by helping to locate parents who are delinquent in their child support obligations. The term “service provider” is defined in California Unemployment Insurance Code Section 1088.8, subparagraph B.2 as “an individual who is not an employee of the service recipient for California purposes and who received compensation or executes a contract for services performed for that service recipient within or without the state.” The term is further defined by the California Employment Development Department to refer specifically to independent Contractors. An independent Contractor is defined as “an individual who is not an employee of the ... government entity for California purposes and who receives compensation or executes a contract for services performed for that ... government entity either in or outside of California.” The reporting requirement does not apply to corporations, general partnerships, limited liability partnerships, and limited liability companies. Additional information on this reporting requirement can be found at the California Employment Development Department web site located at xxxx://xxx.xxx.xx.xxx/Employer_Services.htm

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

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