Submittal of Well Data Required by Xxxxx Sample Clauses

Submittal of Well Data Required by Xxxxx. Data shall be submitted to the Division via an operator-run, secure FTP site or to the Division’s data submittal email address, XXX.XXxxxx@xxxxxx.xxx. Email attachment size is limited to 20 MB. Files larger than 20 MB may need to be sent via FTP. Instructions for accessing the operator-run FTP site should be sent before submitting data. Data shall be submitted to the Arctic Slope Regional Corporation (ASRC) via an operator-run, secure FTP site or an ASRC email address. Contact ASRC at 0000 X Xxxxxx, Xxxxx 0000, Xxxxxxxxx, XX 00000 or (000)000-0000 for additional instructions. For spreadsheets, include the original Excel document. For images such as maps or charts, include a high-resolution TIFF or JPEG. For logs, see formats specified below, but include a graphical image file of logs as a PDF or TIFF in addition to the final merged data file of the log curves. Provide data for each well, pilot hole, and plugged back wellbore. Required data include:
AutoNDA by SimpleDocs
Submittal of Well Data Required by Xxxxx. Data shall be submitted to the Division via an operator-run, secure FTP site or to the Division’s data submittal email address, XXX.XXxxxx@xxxxxx.xxx. Email attachment size is limited to 20 MB. Files larger than 20 MB may need to be sent via FTP. Instructions for accessing the operator-run FTP site should be sent before submitting data. For spreadsheets, include the original Excel document. For images such as maps or charts, include a high- resolution TIFF or JPEG. For logs, see formats specified below, but include a graphical image file of logs as a PDF or TIFF in addition to the final merged data file of the log curves. Provide data for each well, pilot hole, and plugged back wellbore. Required data include:

Related to Submittal of Well Data Required by Xxxxx

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

  • 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.

  • Delivery Schedule The Goods specified in the List of Goods are required to be delivered within the acceptable time range (after the earliest and before the final date, both dates inclusive) specified in Section V, Schedule of Requirements. No credit will be given to deliveries before the earliest date, and Tenders offering delivery after the final date shall be treated as non-responsive. Within this acceptable period, an adjustment of [insert the adjustment factor], will be added, for evaluation purposes only, to the Tender price of Tenders offering deliveries later than the “Earliest Delivery Date” specified in Section V, Schedule of Requirements.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information.

  • DELIVERY: FOB DESTINATION, INSIDE DELIVERY, FREIGHT PAID Whenever possible, contractors should give the ordering entities 3 working days prior notice of any deliveries and/or installations. Furniture contractors will not be responsible for the removal/moving of existing furnishings unless requested by the ordering entity. Contractors should verify site readiness prior to delivery. All deliveries will be made during normal working hours unless otherwise arranged with the ordering entity. Contractor will communicate any scheduling delays and/or changes immediately. Agencies will not be responsible for any freight damage, concealed or otherwise.

  • DATA REQUESTS Upon the written request of the District, the State Auditor’s Office, the Appraisal District, or the Comptroller during the term of this Agreement, the Applicant, the District or any other entity on behalf of the District shall provide the requesting party with all information reasonably necessary for the requesting party to determine whether the Applicant is in compliance with its rights, obligations or responsibilities, including, but not limited to, any employment obligations which may arise under this Agreement.

  • Auction Schedule; Method of Submission of Orders (a) The Funds and the Auction Agent shall conduct Auctions for each series of Preferred Shares in accordance with the schedule set forth below. Such schedule may be changed at any time by the Auction Agent with the consent of the Fund, which consent shall not be withheld unreasonably. The Auction Agent shall give notice of any such change to BD. Such notice shall be received prior to the first Auction Date on which any such change shall be effective. Time Event ---- ----- By 9:30 A.M. Auction Agent advises the Funds and the Broker-Dealers of the Maximum Rate as set forth in Section 3.2(a) hereof.

  • Submittals Submittals required by the Contract Documents shall be prepared specifically for the Work by the Contractor to illustrate some portion of the Work. Submittals are not Contract Documents.

  • DELIVERY SCHEDULES In accordance with the "Non-State Agencies Participation in Centralized Contracts” and “Extension of Use” clauses herein, this Contract is extended to local governments, political subdivisions and others authorized by law as well as State agencies. The Delivery Schedules (based on Requirement Letter RL182) are available as a guide to indicate proposed delivery points and estimated annual requirements. Delivery Schedules may be revised or clarified as necessary. Any specific questions regarding the site conditions should be directed to the end-user at the telephone number shown on the Delivery Schedule. The Delivery Schedules are available upon request. Contractors shall be obligated to deliver under the Contract to any State agency which places a purchase order under the Contract, whether or not such delivery location is identified in the Delivery Schedules. Any political subdivision or other non-State entity which has not filed a requirement with OGS as of the date of the bid opening shall be eligible to receive deliveries at Contractor's option only, upon placement of a valid purchase order to the Contractor's address as indicated in the award. Contracts created by OGS in response to receipt of Filed Requirements are considered to be binding. At Contractor's request, Contractor will be advised in writing regarding political subdivisions or other Non-State entities which have filed on a timely basis but do not appear on the Delivery Schedule. Where “Standby” is indicated in the Delivery Schedule, this reflects those facilities which normally use a fuel supply (i.e. natural gas) other than fuel oil and will only use fuel oil when alternate fuel is unavailable.

  • Drug-Free Workplace Certification As required by Executive Order No. 90-5 dated April 12, 1990, issued by the Governor of Indiana, the Company hereby covenants and agrees to make a good faith effort to provide and maintain a drug-free workplace at the Project Location. The Company will give written notice to the IEDC within ten (10) days after receiving actual notice that the Company, or an employee of the Company in the State of Indiana, has been convicted of a criminal drug violation occurring in the workplace. False certification or violation of this certification may result in sanctions including, but not limited to, suspension of payments under the Agreement, termination of the Agreement and/or debarment of contracting opportunities with the State for up to three (3) years. In addition to the provisions of the above paragraph, if the total amount set forth in the Agreement is in excess of $25,000.00, the Company agrees that it will provide a drug-free workplace by: A. Publishing and providing to all of its employees a statement notifying them that the unlawful manufacture, distribution, dispensing, possession or use of a controlled substance is prohibited in the Company’s workplace, and specifying the actions that will be taken against employees for violations of such prohibition;

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