Specific Requirement Sample Clauses

Specific Requirement. Contractor shall submit copies of the following documents immediately on award of work and as and when demanded by Engineer In-charge: ❖ Suitable / Valid Driving licenses for JCB operator and open truck (tipper) driver(s) (of HMV / HCV category). ❖ R.C. book of Vehicles deployed at site. ❖ Valid Insurance coverage of Vehicles deployed at site. ❖ Valid Fitness certificates of Trucks / Dumpers ❖ Valid P.U.C of Trucks / Dumpers ❖ Vocational Training certificate if issued under VT rule ❖ Medical of Driver/ Dumper Operator - as per Mine Rule 1955 Under-performance of work: The daily operating hours shall be from 07.00 am to 09:00 pm. Contractor shall have to empty the silos for the day, as and when required, as directed by Engineer In-charge by 9:00 pm of the respective day. If the Contractor shall not be able to empty the Fly Ash and / or Bed Ash silos as per requirement, by 9.00 pm of the particular day and if Ash level in Silo becomes critical, it will be considered as Under performance and GIPCL shall be free to deploy any other party to get the work done at the risk and cost of Contractor. In case of such urgency, Contractor shall be prepared with the required / additional resources for the Ash Disposal up to 1,500 to 2000 MT per day. If Contractor under performs as above for three (3) times in a Fortnight period, GIPCL reserves the authority to terminate the Contract immediately and forfeit the Security deposit of the Contractor.
Sample 1Sample 2
AutoNDA by SimpleDocs
Specific Requirement. 7.3.1 The MOD has specific local requirements that will be determined during the Call Off stage.
Sample 1
Specific Requirement. 9.9.1 The Supplier must be aware that the MOD has specific local requirements that will be determined during the Call Off stage.
Sample 1
Specific Requirement. Contractor shall submit copies of the following documents immediately on award of work and as and when demanded by Engineer In-charge: ❖ Suitable / valid driving licenses of dumper (tipper) drivers (of HMV / HCV category). ❖ R.C. book of dumpers deployed at site. ❖ Valid Insurance coverage of dumpers deployed at site. ❖ Valid Fitness certificates of dumpers ❖ Valid P.U.C of dumpers ❖ Vocational Training certificate issued under VT rule ❖ Medical of Driver/ Dumper Operator - as per Mine Rule 1955 PACKAGE B: Cleaning of Areas underneath and surrounding Fly Ash & Bed Ash Silos and connecting roads The evacuation of Fly Ash from ESP & Bed Ash from Boiler is being carried out through pneumatic conveying system in all four (4) Units of Surat Lignite Power Plant. Finally, ash is respectively collected in the Fly Ash & Bed Ash Silos. At Ash Handling System (AHS) of GIPCL-SLPP, there are 4 nos. of Fly Ash & 4 nos. of Bed Ash silos. GIPCL is disposing ash in dry form by means of trucks. The trucks are being loaded underneath the Silos for sale to external Ash customers or for disposal to mines During truck loading and transportation, there is spillage of ash underneath and surrounding area of silos including connecting roads. Further overloaded truck need to be emptied at predefined location. All such spillage Ash has to be collected and should be disposed immediately to keep the area clean. The scope of work here, as per this Contract, includes accumulating the spillage fly ash & bed ash, from beneath silos and surrounding areas including connecting roads [total four (4) fly ash silos and total four (4) bed ash silos exists at GIPCL-SLPP],. Further, this accumulated/ collected ash shall be loaded in the Multi axle open truck / dumper (tipper) and shall be transported without emitting dust in environment at the following Ash disposal locations (distance ranges):
Sample 1
Specific Requirement. As per requirement of concern department.
Sample 1
Specific Requirement. 3.1.0 The main components of a Pre-fabricated Sub-station (PSS) are Transformer, High- voltage switchgear-control gear, Low-voltage switchgear-control gear and corresponding interconnections (cable, flexible, busbars) & auxiliary equipment. The components shall be enclosed, by either common enclosure or by an assembly of enclosure. All the components shall comply with their relevant IEC standards.
Sample 1
Specific Requirement. Contractor shall submit copies of the following documents immediately on Award of Contract: ❖ Suitable / Valid Driving licenses for Dozer Operators (suitable Earth mover category). ❖ R.C. book of Vehicles deployed at site. ❖ Valid Insurance coverage of Vehicles deployed at site. ❖ Valid Fitness certificates, if applicable, of Dozer(s) ❖ Valid P.U.C, if applicable, of Dozer(s). ❖ Vocational Training certificate issued under VT rule ❖ Medical of Driver/ Dumper Operator - as per Mine Rule 1955 • Under - performance of work: The daily operating hours may be from 07.00 am to 09:00 pm in critical times. Contractor shall have to doze / compact / level the dumped Ash or push / lift / compact Lignite, as and when required, as directed by Engineer In-charge, by 9:00 pm of the respective day. If the Contractor shall not be able to achieve the above, as per requirement, by 9.00 pm of the particular day, and especially for Package – (A), if Ash dumping shall be hampered, it will be considered as Under performance and GIPCL shall be free to deploy any other party to get the work done at the risk and cost of Contractor. In case of such urgency, Contractor shall be prepared with the required resources for the Dozing / compacting / leveling of up to 1,500 to 2,000 MT of Ash per day. If Contractor Under performs as above for more than five (5) times in a Fortnight period, GIPCL reserves the authority to terminate the Contract immediately and forfeit the Security deposit of the Contractor.
Sample 1
AutoNDA by SimpleDocs
Specific Requirement 
Sample 1

Related to Specific Requirement

  • Specific Requirements 7.4.1 Workers’ compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.

  • W-9 Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a properly completed Internal Revenue Service (“IRS”) Form W-9. The purpose of the W-9 form is to document the SS# or FEIN# per the IRS. Note: W-9s submitted for any other entity name other than the Grantee’s will not be accepted.

  • Basic Requirements To be eligible for PayPal’s Seller Protection program, all of the following basic requirements must be met, as well as any applicable additional requirements: • The primary address for your PayPal account must be in the United States. • The item must be a physical, tangible good that can be shipped, except for items subject to the Intangible Goods Additional Requirements. Transactions involving items that you deliver in person in connection with payment made in your physical store, may also be eligible for PayPal’s Seller Protection program so long as the buyer paid for the transaction in person by using a PayPal goods and services QR code. • You must ship the item to the shipping address on the Transaction Details page in your PayPal account for the transaction. If you originally ship the item to the recipient’s shipping address on the Transaction Details page but the item is later redirected to a different address, you will not be eligible for PayPal’s Seller Protection program. We therefore recommend not using a shipping service that is arranged by the buyer, so that you will be able to provide valid proof of shipping and delivery. • The shipping requirement does not apply to eligible transactions involving items that you deliver in person; provided, however, that you agree to provide us with alternative evidence of delivery or such additional documentation or information relating to the transaction that we may request. • You must respond to PayPal’s requests for documentation and other information in a timely manner as requested in our email correspondence with you or in our correspondence with you through the Resolution Center. If you do not respond to PayPal’s request for documentation and other information in the time requested, you may not be eligible for PayPal’s Seller Protection program. • If the sale involves pre-ordered or made-to-order goods, you must ship within the timeframe you specified in the listing. Otherwise, it is recommended that you ship all items within 7 days after receipt of payment. • You provide us with valid proof of shipment or delivery. • The payment must be marked “eligible” or “partially eligible” in the case of Unauthorized Transaction claims, or “eligible” in the case of Item Not Received claims, for PayPal’s Seller Protection program on the Transaction Details page. • In the case of an Unauthorized Transaction claim, you must provide valid proof of shipment or proof of delivery that demonstrates that the item was shipped or provided to the buyer no later than two days after PayPal notified you of the dispute or reversal. For example, if PayPal notifies you of an Unauthorized Transaction claim on September 1, the valid proof of shipment must indicate that the item was shipped to the buyer no later than September 3 to be eligible for PayPal’s Seller Protection program. PayPal determines, in its sole discretion, whether your claim is eligible for PayPal’s Seller Protection program. PayPal will make a decision, in its sole discretion, based on the eligibility requirements, any information or documentation provided during the resolution process, or any other information PayPal deems relevant and appropriate under the circumstances. Item Not Received additional requirements To be eligible for PayPal’s Seller Protection program for a buyer’s Item Not Received claim, you must meet both the basic requirements and the additional requirements listed below: • Where a buyer files a chargeback with the issuer for a card-funded transaction, the payment must be marked “eligible” for PayPal’s Seller Protection on the Transaction Details page. • You must provide proof of delivery as described below.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Child Abuse Reporting Requirement Grantee will:

  • CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.

  • Age Requirement The employee must have reached the age of fifty-five (55) before reduction in workload.

  • Program Requirements A. The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • Data Requirements ‌ • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.

  • Reporting Requirement (1) In the event the Contractor identifies covered telecommunications equipment or services used as a substantial or essential component of any system, or as critical technology as part of any system, during contract performance, or the Contractor is notified of such by a subcontractor at any tier or by any other source, the Contractor shall report the information in paragraph (d)(2) of this clause to the Contracting Officer, unless elsewhere in this contract are established procedures for reporting the information; in the case of the Department of Defense, the Contractor shall report to the website at xxxxx://xxxxxx.xxx.xxx. For indefinite delivery contracts, the Contractor shall report to the Contracting Officer for the indefinite delivery contract and the Contracting Officer(s) for any affected order or, in the case of the Department of Defense, identify both the indefinite delivery contract and any affected orders in the report provided at xxxxx://xxxxxx.xxx.xxx.

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