Component Requirements and Verification. The following tools and features are used to capture component level require- ments and perform verification.
Component Requirements and Verification Sample Clauses
Related to Component Requirements and Verification
MEASUREMENT AND VERIFICATION The goal of this task is to report the benefits resulting from this project. Project team may use in- house expertise of the project demonstration site or use third party vendor for measurement and verification (M&V) of GHG and energy consumption reduction. The Recipient shall: • Enter into agreement with M&V subcontractor per Task 1.9 (if using outside vendor) • Coordinate site visits with the M&V subcontractor at the demonstration site(s) • Develop M&V protocol for pre-installation measurement (and calculations) following Section II.B.2 of the grant solicitation manual3: o Electric, natural gas and/or other fossil fuel consumption and greenhouse gas emissions (use appropriate emissions factor from Attachment 8 of the grant solicitation) of the equipment/process/system(s)/sub-system(s) that are be upgraded and/or replaced and/or modified; and o If necessary, ensure installation of sub-metering equipment and data loggers for pre/post data analysis. • Prepare and provide a detailed M&V Plan for each project demonstration site to include but not be limited to: o A description of the monitoring equipment and instrumentation which will be used; o A description of the key input parameters and output metrics which will be measured; o A description of the M&V protocol and analysis methods to be employed; and o A description of the independent, third-party measurement and verification services to be employed, if applicable. • Perform three months (or shorter period as approved in writing by the CAM) of pre- installation measurements (and calculations) based on the M&V protocol for pre- installation. • Prepare and provide a Pre-Installation M&V Findings Report that includes M&V protocol, pre-install measurements (and calculations), analysis, and results performed in this task. • Develop M&V protocol for post-installation measurements (and calculations) of: o Electric, natural gas and/or other fossil fuel consumption and greenhouse gas emissions (use appropriate emissions factor from Attachment 8 of the grant solicitation) of the equipment/process/system(s)/sub-system(s) that will be upgraded and/or replaced and/or modified. Perform 12 months (or shorter period as approved in writing by the CAM) of post- installation measurements based on M&V protocol for post-installation. • Provide a summary of post-installation M&V progress in Progress Report(s) (see subtask 1.5) which shall include but not be limited to: o A narrative on operational highlights from the reporting period, including any stoppages in operation and why; and o A summary of M&V findings from the reporting period. • Analyze post-installation electrical, natural gas and/or other fossil fuel consumption and GHG emissions. 3 GFO-18-903, Food Production Investment Program, California Energy Commission, November 2018. xxxxx://xxx.xxxxxx.xx.xxx/contracts/GFO-18-903/000_FPIP_Solicitation_Manual.docx • Prepare and provide a Post-installation M&V Findings Report that includes M&V protocol, pre and post install measurements (and calculations), analysis, and results performed in this task. Results should at a minimum report on the reduction of electricity, natural gas and/or other fossil fuel usage and reductions of GHG emissions that directly result from this project.
Project Requirements Failure to comply with the following requirements will result in a suspension of all other operations:
Divestment Requirements 34.1.1 Upon Termination, the Concessionaire shall comply with and conform to the following Divestment Requirements:
Agreement Requirements This agreement will be issued to cover the Janitorial Service requirements for all State Agencies and shall be accessible to any School District, Political Subdivision, or Volunteer Fire Company.
Procurement Requirements The below listed provisions of State Procurement requirements shall be complied with throughout the contract period:
Equipment Requirements No Equipment is provided to Customer as part of this Service.
Development Requirements The exterior wall standards set forth in this section shall apply to the structures located on the Property. At least ninety percent (90%) of the combined exterior surface area of all walls, including all stories of buildings / structures, shall consist of stone, brick, painted or tinted stucco, and factory tinted (not painted) split faced concrete masonry unit or similar material approved by the Director of Planning.
Test requirements 3.1. The limits apply throughout the frequency range 30 to 1,000 MHz for measurements performed in a semi anechoic chamber or an outdoor test site.
Payment Requirements If funding levels are significantly affected by state or federal budget and funds are not allocated and available for the continuance of the function performed by Subrecipient, the Contract may be terminated by the County at the end of the period for which funds are available. The County shall notify Subrecipient at the earliest possible time of any service, which will or may be affected by a shortage of funds. No penalty shall accrue to the County in the event this provision is exercised and the County shall not be obligated nor liable for any damages as a result of termination under this provision of this Contract, and nothing herein shall be construed as obligating the County to expend or as involving the County in any Contract or other obligation for future payment of money in excess of appropriations authorized by law.
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.
