CONTRACT REQUIREMENTS A. Project area boundaries are marked with two blue paint slashes and block boundaries are designated with one blue paint slash.
B. All blocks are accessible by foot only. Xxxxxx’x Creek must be crossed on foot from the PGC railroad grade.
C. Block 1, All trees 1” DBH and over, except for red and blue paint marked trees are to be cut. All conifers are reserved. Block 1 will be cut during the dormant season; October 15 through March 15.
D. Block 2, All American beech, sweet birch, aspen, stripped maple, and ironwood 1” DBH and greater will be cut. All yellow marked trees will be cut. Block 2 will be cut during the dormant season; October 15 through March 15.
E. Block 3, All trees 1” DBH and over, except for red and blue paint marked trees are to be cut. All conifers are reserved. Block 3 will be cut during the dormant season; October 15 through March 15.
F. All employees must be able to identify species.
G. Usable material may not be removed from site.
X. Xxxxx material felled with clean cuts must have stumps that are parallel to the ground surface and shall not exceed six (6) inches in height measured on the side next to the highest ground or the diameter of the xxxxx, whichever is smaller, except when in the opinion of the Field Contract Coordinator, said height is impractical.
I. Cut trees must be removed from trails, roads, tail drains, streams, and utility rights-of- way.
J. All trees shall be felled so tops do not pile on one another but lie singly on the ground.
K. Slash shall be lopped to no higher than 4’ and pulled apart as directed by the Regional Forester.
L. Operator shall exercise care and caution in all operations to prevent damage to all trees not specified for treatment.
M. All tops must be pulled back 25 feet from the State Game Land boundary, (blazed & painted white), all roads, parking lots, herbaceous openings, utility Right of Ways and deer exclosures. Tops, branches, and slash will be removed from all ponds, lakes, and streams.
N. Damage to trails, roads, streams, or utility rights-of-way caused by the Operator’s equipment must be repaired by the Operator at their expense.
O. Any trash resulting from the Operator’s operations must be removed from the area and properly disposed.
P. The Operator shall not block any roads or trails in the area during performance of this contract. The Operator shall not in any way hinder the progress of any Timber Sale Contracts in these areas.
Q. All labor, equipment, tools, etc., needed to complete contracted projects are to be provided by the Operator.
R. Timber Damages – when in the opinion of Field Contract Coordinator, damage to the residual stand becomes excessive, the Operator shall pay the Commission a fair base current value determined by the Field Contract Coordinator per unit of volume. If this value for damage due to Operator’s carelessness or negligence is less than $10.00 per tree, then a minimum charge of $10.00 per tree will be made whether the tree is commercial, non-commercial, merchantable, or non-merchantable.
Subcontract Requirements As required by Section 6.22(e)(5) of the Administrative Code, Contractor shall insert in every subcontract or other arrangement, which it may make for the performance of Covered Services under this Agreement, a provision that said subcontractor shall pay to all persons performing labor in connection with Covered Services under said subcontract or other arrangement not less than the highest general prevailing rate of wages as fixed and determined by the Board of Supervisors for such labor or services.
Export Requirements The Program, Documentation and all related technical information or materials are subject to export controls and U.S. Government export regulations. You will comply strictly with all legal requirements established under these controls and will not, in connection with its limited evaluation rights hereunder, export, re-export, divert, transfer or disclose, directly or indirectly the Program, Documentation and any related technical information or materials without the prior approval of the U.S.
Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.
Compliance with Xxxxxxxx Act requirements The contractor shall comply with the requirements of 29 CFR part 3, which are incorporated by reference in this contract.
Minimum Site Requirements for TIPS Sales (when applicable to TIPS Sale). Cleanup: When performing work on site at a TIPS Member’s property, Vendor shall clean up and remove all debris and rubbish resulting from their work as required or directed by the TIPS Member or as agreed by the parties. Upon completion of work, the premises shall be left in good repair and an orderly, neat, clean and unobstructed condition. Preparation: Vendor shall not begin a project for which a TIPS Member has not prepared the site, unless Vendor does the preparation work at no cost, or until TIPS Member includes the cost of site preparation in the TIPS Sale Site preparation includes, but is not limited to: moving furniture, installing wiring for networks or power, and similar pre‐installation requirements. Registered Sex Offender Restrictions: For work to be performed at schools, Vendor agrees that no employee of Vendor or a subcontractor who has been adjudicated to be a registered sex offender will perform work at any time when students are, or reasonably expected to be, present unless otherwise agreed by the TIPS Member. Vendor agrees that a violation of this condition shall be considered a material breach and may result in the cancellation of the TIPS Sale at the TIPS Member’s discretion. Vendor must identify any additional costs associated with compliance of this term. If no costs are specified, compliance with this term will be provided at no additional charge. Safety Measures: Vendor shall take all reasonable precautions for the safety of employees on the worksite, and shall erect and properly maintain all necessary safeguards for protection of workers and the public. Vendor shall post warning signs against all hazards created by the operation and work in progress. Proper precautions shall be taken pursuant to state law and standard practices to protect workers, general public and existing structures from injury or damage. Smoking: Persons working under Agreement shall adhere to the TIPS Member’s or local smoking statutes, codes, ordinances, and policies.
Support Requirements If there is a dispute between the awarded vendor and TIPS Member, TIPS or its representatives may assist, at TIPS sole discretion, in conflict resolution or third party (mandatory mediation), if requested by either party. TIPS, or its representatives, reserves the right to inspect any project and audit the awarded vendors TIPS project files, documentation and correspondence. TIPS Members stand in the place of TIPS as related to this agreement and have the same access to the proposal information and all related documents. TIPS Members have all the same rights under the awarded Agreement as TIPS.
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.
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.
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
