Data Collection The grant recipient will be required to provide performance data reports on a schedule delineated within Section A of this contract, Specific Terms and Conditions.
DATA COLLECTION AND ANALYSIS The goal of this task is to collect operational data from the project, to analyze that data for economic and environmental impacts, and to include the data and analysis in the Final Report. The Recipient shall: • Develop a data collection plan. • Troubleshoot any issues identified. • Collect at least six months of data, including: o Throughput, usage, and operations data o Normal operating hours, up time, down time, and explanations of variations o Feedstock supply summary o Maximum capacity of the new fuel production system in diesel gallon equivalents (DGE) and ordinary units o Gallons of gasoline and/or diesel fuel displaced (with associated mileage information), along with value converted into DGE o Record of wastes from production processes (wastewater, solid waste, criteria emissions, etc.) o Expected air emissions reduction, for example: Non-methane hydrocarbons Oxides of nitrogen Non-methane hydrocarbons plus oxides of nitrogen Particulate Matter Formaldehyde o Duty cycle of the current fleet and the expected duty cycle of future vehicle acquisitions, if applicable o Specific jobs and economic development resulting from this project o Levelized cost of fuel and finished fuel price o Analysis of total facility costs, operation and maintenance costs, marginal abatement costs • Comply with the Petroleum Industry Information Reporting Act (PIIRA) and complete CEC Form M810E and CEC Form M13 on a monthly basis for submission to the California Energy Commission’s PIIRA Data Collection Unit. • Provide a written record of registering with the Low Carbon Fuel Standard and Renewable Fuel Standard programs. • Identify any current and planned use of renewable energy at the facility. • Describe any energy efficiency measures used in the facility that may exceed Title 24 standards in Part 6 of the California Code Regulations. • Provide data on potential job creation, economic development, and increased state revenue as a result of expected future expansion. • Provide a quantified estimate of the project’s carbon intensity values or provide an Air Resources Board approved pathway carbon intensity. • Estimate annual life-cycle greenhouse gas emission reduction. • Compare any project performance and expectations provided in the proposal to Energy Commission with actual project performance and accomplishments. • Collect data, information, and analysis described above and include in the Final Report.
Program Components Activities and services delivered under this Program Element align with Foundational Programs and Foundational Capabilities, as defined in Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf) as well as with public health accountability outcome and process metrics (if applicable) as follows:
Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Cellutell Communications, Inc.’s data from BellSouth’s data, the following shall apply:
Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.
Unbundled Sub-Loop Concentration System (USLC 2.9.1 Where facilities permit and where necessary to comply with an effective Commission order, BellSouth will provide <<customer_name>> with the ability to concentrate its sub-loops onto multiple DS1s back to the BellSouth Central Office. The DS1s will then be terminated into <<customer_name>>’s collocation space. TR-008 and TR303 interface standards are available.
