Results characterisation Sample Clauses

Results characterisation. The objective of the characterisation is to provide an assessment of the results in a way that their relevance in commercial terms can be understood. To characterize each Exploitable Result the partner(s) identified in Table 6.1 has (have) filled the predefined tables that were discussed during the ESS seminar held on 2011-02-01/02. The predefined table’s content is reported in this section mainly maintaining the original ESS seminar time-frame reference but specific adaptation has been applied in some cases in order to provide correct and updated information. Quantitative information (e.g. market size, price, time to market) has been considered of particular value, even when it is only approximate, or provided as a range of values (e.g. less than 10 M€, or 50 k€ -100 k€). In the cases where it has not been possible to provide quantitative estimations, qualitative information has been provided instead. It has also been considered very valuable to identify partners, potential customers and competitors (at least conceptually). For the latter, a rough prediction of the speed of reaction to the introduction of each result on the market has been provided in Deliverable D6.3b (Confidential). Non confidential information related to each individual exploitable result is reported in Table 6.2.
AutoNDA by SimpleDocs

Related to Results characterisation

  • Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.

  • Stability Testing Patheon may be requested to conduct stability testing on the Products in accordance with the protocols set out in the Specifications for the separate fees and during the time periods set out in Schedule C to a Product Agreement. Patheon will not make any changes to these testing protocols without prior written approval from Client. If a confirmed stability test failure occurs, Patheon will notify Client within one Business Day, after which Patheon and Client will jointly determine the proceedings and methods to be undertaken to investigate the cause of the failure, including which party will bear the cost of the investigation. Patheon will not be liable for these costs unless it has failed to perform the Manufacturing Services in accordance with the Specifications, cGMPs, and Applicable Laws. Patheon will give Client ail stability test data and results at Client’s request.

  • Narrative Results ‌‌ i. For the first Quarterly Claims Review Report only, a description of (a) Xxxxxxxx Clinic’s billing and coding system(s), including the identification, by position description, of the personnel involved in coding and billing, and (b) a description of controls in place to ensure that all items and services billed to Medicare or a state Medicaid program by Xxxxxxxx Clinic are medically necessary and appropriately documented. Subsequent Quarterly Claims Review Reports should describe any significant changes to items (a) and (b) or, if no significant changes were made, state that the systems and controls remain the same as described in the prior Quarterly Claims Review Report. ii. A narrative explanation of the results of the Quarterly Claims Sample, including reasons for errors, patterns noted, etc.

  • Status Report Recognizing that both parties may find it necessary to establish to third parties, such as accountants, banks, mortgagees, ground lessors, or the like, the then current status of performance hereunder, either party, on the request of the other made from time to time, will promptly furnish to Landlord, or the holder of any mortgage or ground lease encumbering the Premises, or to Tenant, as the case may be, a statement of the status of any matter pertaining to this Lease, including, without limitation, acknowledgment that (or the extent to which) each party is in compliance with its obligations under the terms of this Lease.

  • Status Reports The Grantee shall submit status reports quarterly, unless otherwise specified in the Attachments, on Exhibit A, Progress Report Form, to Department’s Grant Manager describing the work performed during the reporting period, problems encountered, problem resolutions, scheduled updates, and proposed work for the next reporting period. Quarterly status reports are due no later than twenty (20) days following the completion of the quarterly reporting period. For the purposes of this reporting requirement, the quarterly reporting periods end on March 31, June 30, September 30 and December 31. The Department will review the required reports submitted by Grantee within thirty (30) days.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Monthly MWBE Contractor Compliance Report A. In accordance with 5 NYCRR § 142.10, Contractor is required to report Monthly MWBE Contractor Compliance to OGS during the term of the Contract for the preceding month’s activity, documenting progress made towards achievement of the Contract MWBE goals. OGS requests that all Contractors use the New York State Contract System (“NYSCS”) to report subcontractor and supplier payments made by Contractor to MWBEs performing work under the Contract. The NYSCS may be accessed at xxxxx://xx.xxxxxxxxxxxxxx.xxx/. This is a New York State- based system that all State agencies and authorities will be implementing to ensure uniform contract compliance reporting throughout New York State. B. When a Contractor receives a payment from a State agency, it is the Contractor’s responsibility to pay its subcontractors and suppliers in a timely manner. On or after the first day of each month, the Contractor will receive an email or fax notification (“audit notice”) indicating that a representative of its company needs to log-in to the NYSCS to report the company’s MWBE subcontractor and supplier payments for the preceding month. The Contractor must also report when no payments have been made to a subcontractor or supplier in a particular month with entry of a zero dollar value in the NYSCS. Once subcontractor and supplier payments have been entered into the NYSCS, the subcontractor(s) and supplier(s) will receive an email or fax notification advising them to log into the NYSCS to confirm that they actually received the reported payments from the Contractor. It is the Contractor’s responsibility to educate its MWBE subcontractors and suppliers about the NYSCS and the need to confirm payments made to them in the NYSCS. C. To assist in the use of the NYSCS, OGS recommends that all Contractors and MWBE subcontractors and suppliers sign up for the following two webinar trainings offered through the NYSCS: “Introduction to the System – Vendor training” and “Contract Compliance Reporting - Vendor Training” to become familiar with the NYSCS. To view the training schedule and to register visit: xxxxx://xx.xxxxxxxxxxxxxx.xxx/events.asp D. As soon as possible after the Contract is approved, Contractor should visit xxxxx://xx.xxxxxxxxxxxxxx.xxx and click on “Account Lookup” to identify the Contractor’s account by company name. Contact information should be reviewed and updated if necessary by choosing “Change Info.” It is important that the staff member who is responsible for reporting payment information for the Contractor be listed as a user in the NYSCS. Users who are not already listed may be added through “Request New User.” When identifying the person responsible, please add “- MWBE Contact” after his or her last name (i.e., Xxxx Xxx – MWBE Contact) to ensure that the correct person receives audit notices from the NYSCS. NYSCS Technical Support should be contacted for any technical support questions by clicking on the links for “Contact Us & Support” then “Technical Support” on the NYSCS website. E. If Contractor is unable to report MWBE Contractor Compliance via the NYSCS, Contractor must submit a Monthly MWBE Contractor Compliance Report on Form MWBE 102 to OGS, by the 10th day of each month during the term of the Contract, for the preceding month’s activity to: OGS MWBE Office, 00xx Xxxxx Xxxxxxx Xxxxx, Xxxxxx Xxxxx Xxxxx, Xxxxxx, XX 00000. Phone: 000-000-0000; Fax: 000-000-0000. F. It is the Contractor’s responsibility to report subcontractor and supplier payments. Failure to respond to payment audits in a timely fashion through the NYSCS, or by paper to OGS, may jeopardize future payments pursuant to the MWBE liquidated damages provisions in clause IX below.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.

  • ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to TWTC via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. If AT&T determines the Secure FTP Mailbox is nearing capacity levels, AT&T may move the customer to CONNECT: Direct file delivery. 6.2.2 If the customer is moved, CONNECT: Direct data circuits (private line or dial-up) will be required between AT&T and TWTC for the purpose of data transmission. Where a dedicated line is required, TWTC will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with AT&T. TWTC will also be responsible for any charges associated with this line. Equipment required on the AT&T end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be TWTC's responsibility. Where a dial-up facility is required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to TWTC. Additionally, all message toll charges associated with the use of the dial circuit by TWTC will be the responsibility of TWTC. Associated equipment on the AT&T end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on TWTC end for the purpose of data transmission will be the responsibility of TWTC. 6.2.3 If TWTC utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of TWTC.

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