Process Description. The purpose of the file process is to enable coordination of information about prescription drug benefit coverage between Medicare Part D plans and the PAPs. In order to coordinate benefit information, data must be collected from each PAP on each of its enrollees. Submission file formats have been created for the PAP to use. This input information from a PAP will be transmitted to the BCRC where it will be edit-checked, and matched against Medicare data in various eligibility databases. Once a match is found, the BCRC will be able to coordinate the beneficiary’s prescription drug information with the beneficiary’s Medicare Part D information, to create a record of the beneficiary’s prescription drug and Medicare drug benefit coverages. The combined drug benefit coverage information will be loaded into the Medicare Beneficiary Database (MBD). Data from the MBD will be transmitted to Part D plans. A Response File format has been created to be used to return information to the PAP. It will contain one status response record for each record initially submitted by the PAP to the BCRC. The response record will indicate if the enrollee is a Part D beneficiary, whether or not the BCRC applied the record to the MBD and if the record was not applied to the MBD, why not (e.g., the record contained errors or the record did not provide enough information about the enrollee); what Part D plan the beneficiary is in enrolled in; and other selected Part D enrollment information.
Process Description. The purpose of the file process is to enable coordination of information about prescription drug benefit coverage between Medicare Part D plans and the ADAPs. For ADAPs, this process will facilitate the tracking of TrOOP (“true out-of-pocket”) expenses incurred by each Medicare beneficiary. In order to coordinate benefit information, data must be collected from each ADAP on each of its enrollees. Submission file formats have been created for the partners to use. This input information from a partner will be transmitted to the BCRC where it will be edit-checked, and matched against Medicare data in various eligibility databases. Once a match is found, the BCRC will be able to coordinate the beneficiary’s prescription drug information with the beneficiary’s Medicare Part D information, to create a record of the beneficiary’s prescription drug and Medicare drug benefit coverages. The combined drug benefit coverage information will be loaded into the Medicare Beneficiary Database (MBD). Data from the MBD will be transmitted to Part D plans. A Response File format has been created to be used to return information to the ADAP. It will contain one status response record for each record initially submitted by the partner to the BCRC. The response record will indicate if the enrollee is a Part D beneficiary, the LIS status of the enrollee, whether or not the BCRC applied the record to the MBD and if the record was not applied to the MBD, why not (e.g., the record contained errors or the record did not provide enough information about the enrollee), what Part D plan the beneficiary is in enrolled in, and other selected Part D enrollment information.
Process Description. The purpose of the SPAP process is to coordinate the prescription drug benefits between Medicare Part D plans and the State Pharmaceutical Assistance Programs, which serve as supplemental payers. This collection of all prescription drug related benefits will facilitate the tracking of TrOOP (True Out-of- Pocket) expenses incurred by each Medicare beneficiary. In order to coordinate benefits information, data must be collected from each SPAP on each of its enrollees. New submission file formats have been created for use by an SPAP to deliver the pertinent information. This information will be transmitted to the BCRC where it will be edit-checked, and matched against the Medicare data in the Eligibility database. Once a match is found, the BCRC will be able to combine a beneficiary's SPAP information with their Medicare Part D specific information to create a complete record of the beneficiary's state and federal drug benefits. The combined drug benefits information will be loaded into the Master Beneficiary Database (the MBD). Data will be sent from the MBD to the TrOOP Facilitation contractor and Part D plans. An additional file format will be created to send back to the SPAP. This file will contain one status record for each record initially submitted by the SPAP to the BCRC. This response record will indicate if whether or not the SPAP enrollee is a Part D beneficiary; what the SPAP enrollee’s Low Income Subsidy status is; whether or not the BCRC applied the record to the Medicare Beneficiary Database; if the record was not applied to the Medicare Beneficiary Database, why, (e.g., the record contained errors or the record did not provide enough information about the enrollee); what Part D plan the beneficiary is in enrolled in; whether or not the beneficiary is receiving the Low Income Subsidy; and other Part D enrollment and Low Income Subsidy dates and levels.
Process Description. Seller will construct four (4) MHFs, including cyclones, located at Purchaser’s Site in Xxxxxxxxx, Louisiana. Purchaser, through the EPC Contractor, will install equipment to feed material to the MHFs, material handling equipment to remove product from the MHF outlets, and emissions control equipment downstream of the MHFs and cyclones. In addition, Purchaser will provide the Programmable Logic Controller (PLC)-based plant Distributed Control System (DCS), which interfaces with the Seller-provided PLC-based MHF control system. Lignite feedstock will be fed continuously to the MHFs, which are each guaranteed to produce a minimum of * of activated carbon. For the purposes of this test program, the unit will operate at this guaranteed rating. Supplemental fuel (natural gas), when required, will be provided on all even-numbered hearths and burned by two (2) MHF burners per hearth. Particulate emissions generated within the MHF will be controlled by a high-efficiency cyclone.
Process Description. Chart 4.1 in Section 4 is a block flow diagram showing the overall gas and liquid flows for Platform Xxxxx and LOGP. The gas which is not in solution in the oil is separated from the oil on Platform Xxxxx. The oil produced from the Tidelands xxxxx will be segregated from the oil produced from the existing Pt Ped production and metered by turbine meters and adjusted for sediments and water (hereinafter “S&W”) on Platform Xxxxx. Gravity samples will also be taken before commingling so that each area can receive the corresponding price adjustment for the purchaser’s gravity scale. Initially, two of the test separators will be dedicated to the Tidelands xxxxx. One of the test separators will be used as a gross separator. Once the production exceeds the capacity of the test separator which is being used as a gross separator, excess volume will be delivered to the three phase separator dedicated to the Tidelands xxxxx. All Tidelands oil produced will be combined before entering a three phase separator then metered (FT-250 & FT-251) separately and adjusted for temperature and S&W (TA-250 & OWD-250) before being commingled with Pt Ped production. The Pt Ped production will also be delivered through a three phase separator. Oil produced will be combined before entering a three phase separator then metered (FT-220 & FT-221) and adjusted for temperature and S&W (TA-220 & OWD-220) before being commingled with the Tidelands production. The oil production is then discharged into the shipping tank that moves through a common pipeline which ships the oil emulsion to the onshore LOGP facility. Once the oil emulsion is onshore, the oil is separated from remaining water and any gas which also evolves from the process is recovered via the vapor recovery system. Gasoline and condensate extracted from the process stream at LOGP are metered as they leave LOGP and may be blended with the dry oil prior to entering Lease Automatic Custody Transfer unit (hereinafter “LACT”) A and/or B (meters 556 and 557 respectively). The dry oil plus these additions is metered through LACT A and/or B at LOGP prior to entering the ConocoPhillips pipeline system. Oil may also be sent to storage on a limited basis. The actual Pt. Ped and Tidelands oil production is determined by allocating the total monthly shipments from LACT A and/or B at LOGP less blended condensate (meter 2469) and blended natural gasoline (meter 2468) and adjusted for changes in inventory (plus ending inventory, minus beginning ...
Process Description. The DGS Policy describes which bank accounts and parties must be reported on, as well as the data that must be reported. The DGS Manual addresses this in more detail. See the Manual and the Regulation.
Process Description. The RRE Reporting Manual describes which instruments and counterparties must be reported on, as well as the data that must be reported. The reporting population is also listed.
Process Description. Chart 4.1 in Section 4 is a block flow diagram showing the overall gas and liquid flows for Platform Xxxxx and the LOGP. The oil and gas production is allocated for royalty purposes as the production is commingled from both Pt Ped and Tidelands offshore. Each of the respective gas streams for Pt Ped gas and Tidelands gas are kept separate and a gas analysis is taken of each before commingling for transporting to LOGP. The gas is analyzed using gas chromatography by a state certified lab to determine BTU content and natural gas liquid content for each source of gas delivered to LOGP. This is used to determine the theoretical MMBTU and theoretical natural gas liquid products used for allocation purposes. Theoretical Pt Ped Gas and Theoretical Tidelands Gas, are adjusted each month by the gas lift gas volume so as to reflect net theoretical gas production. Gas lift gas is assumed to be the first gas recovered from gas lift xxxxx and is therefore deducted from the Theoretical Pt Ped Gas and Theoretical Tidelands Gas. Meters FE-101GL (“Pt Ped Gas Lift Gas”) and FE-201GL (“Tidelands Gas Lift Gas”) will meter the volume of gas sent into the respective areas of production and will be subtracted from Theoretical Pt Ped Gas and Theoretical Tidelands Gas, respectively. At LOGP, the crude oil is reheated, dewatered and shipped to ConocoPhillips Santa Xxxxx Refinery. Gas released from the crude oil during processing at LOGP is captured in the vapor recovery system and combined (via meter 2452) with gas from Platform Xxxxx (via meter 2453). This mixture passes through meter 2450 and mixes with gas from Lompoc Field (from meter 2675) along with gas recovered from injection ( (Purisima 73, meter 2451) before treatment in the gas processing unit. The gas processing unit removes heavy hydrocarbons (C3+) and waste products (water, H2S, and CO2) from the gas to be sold. Treated gas is normally compressed and sold into the SOCAL Pipeline (via meter 5811). During maintenance shutdowns or whenever the sales gas is “off specification,” the gas is injected into the Lompoc Field at Purisima well P- 73 (via meter 2462). Gas from Platform Xxxxx that is injected onshore, is metered, allocated and royalties are paid on the volume injected based on the weighted average sales price per Mcf for the month of injection. Gas recovered from storage (via meter 2451) is non-royalty bearing since the royalty was paid as the gas was injected. Natural Gas Liquids condense in the gas plant. Natural...
Process Description. 2.1 Prior to each delivery, the contracting parties shall agree on the recipients/addresses/place of delivery of the ... (subject of delivery), the types of equipment and the respective number of devices to be delivered.
Process Description. 65 8.3.1 Adding or Removing a Customer Site ..................... 66 8.3.2 Adding or Removing a System ............................ 66 8.3.3 Changing Service Level ................................. 67 8.3.4 Introducing or Eliminating a Service ................... 67 8.3.5
