Process Overview. The City will offer and advertise the availability of the tax rebate program throughout the term of the Plan. Persons or businesses planning improvement projects may contact the Public Improvement Department at any time for a discussion of eligibility. The Neighborhood Revitalization Plan application will stipulate the type of improvement to be made, renderings, a timetable for completion and any supporting documents appropriate for the type of application. Prior to beginning the project, the owner shall apply for a building permit. Once the building permit has been issued the owner has 60 days to file a complete application. The county appraiser will determine the increase in improvement value for January 1st the year immediately following the completion of the project which shall be used to calculate the tax value increment added. At the customary time, the county treasurer shall mail tax statements based on the new appraised value. Upon payment of all taxes in full by the taxpayer, the county treasurer will initiate the tax rebate procedure. Only the increase in taxes will be rebated less any applicable administrative fees. The rebate must be made within 30 days after the next distribution date, unless there is an open appeal, then 30 days from issuance of the appeal result letter.
Process Overview. PG&E notified over 2,900 market participants when the Fifth RAM Solicitation was launched on May 30, 2014 and followed the timeline in the table below. Date/Time Event May 30, 2014 PG&E issued the Fifth RAM RFO June 11, 2014 Bidders’ Webinar for Fifth RAM RFO June 27, 2014 no later than 12:00 P.M.(PPT) Offers Due. Offer(s) must be submitted to the online platform at Power Advocate. All Projects must provide a completed Phase I or equivalent interconnection study with applicable appendices or showing that the project passed the WDAT/WDT or CAISO Fast Track screens. Projects must have a queue position and remain in the queue. Offer evaluation begins. August 12, 2014 PG&E met with members of the Procurement Review Group (“PRG”) concerning the Fifth RAM Solicitation. September 5, 2014 PG&E selected Participants. offers and notified Selected and Waitlist September 10, 2014 Deadline for Selected and Waitlisted Participants to return signed acceptance letters. Advice 4539-E - 4 - November 21, 2014 September 11, 2014 Waitlisted Participants were notified if they had been selected. September 16, 2014 no later than 1:00 P.M.(PPT) Submittal of Signed PPA. Selected Participants that wished to continue participation in the Fifth RAM RFO had to return a signed RAM PPA and required documentation as shown in Appendix VIII of the PPA to PG&E. September 23, 2014 no later than 1:00 P.M.(PPT) Selected Waitlisted Participants that wished to continue participation in the Fifth RAM RFO had to return a signed RAM PPA with required documentation as shown in Appendix VIII to the RAM PPA. October 21, 2014 PG&E executed three RAM PPAs November 12, 2014 PG&E executed the other five RAM PPAs Offer Overview PG&E received 103 offers for 69 unique facilities from 25 counterparties totaling 1,129 MW; or 3,222 gigawatt hours (“GWh”) annually. The offers were separated into the three product categories (procurement targets in parentheses): baseload (10 MW); as-available non-peaking (20 MW); and as-available peaking (78.2 MW). The existing RAM Program rules provide flexibility for PG&E to procure plus or minus 20 MW per product category and for total solicitation. Consistent with Resolution E-4489, entities (“Participants”) submitting bids into the RFO had the option to bid their project as either energy-only (“EO”) or with full capacity deliverability status (“FCDS”). Projects that elected FCDS were required to meet additional eligibility requirements which included having a completed Phase ...
Process Overview. Following the publication of the IOG, the NSSG produced the action plan with key milestones and resources required for implementation of the recommendations. The plan has been agreed by the Network Board, Commissioners and the Strategic Health Authority.
Process Overview. 5.1.1 The Spend Data Analysis service shall be delivered via web-enabled technology to facilitate the process of aggregating; classifying, analysing and leveraging spend data for the purpose of reducing costs, improving operational performance, and ensuring compliance. Spend Data Analysis provides a clear picture of buying patterns including who is buying what, from whom, when, how often, on what terms and the value of spend.
Process Overview. A. The City unit that administers the ULA permit system is the Right-of-Way Management Group. This group collects applications, distributes them to potentially affected City departments, agencies, and Utility Companies for review and feedback.
Process Overview. (a) The “IT Infrastructure Management” Core Function will require Supplier to support ***, ***, *** Infrastructure Administration. Supplier’s responsibilities includes: CORELOGIC / COGNIZANT CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES ACT OF 1933, AS AMENDED, AND RULE 24B-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH ASTERISKS.
Process Overview. An overview of the Process is attached to this Agreement as Exhibit H. Agilent acknowledges and agrees that Exhibit H does not contain any Agilent Proprietary Information and that Customer may disclose Exhibit H, or any information contained therein, to any Third Party to the extent such Third Party has a reasonable need to know such information.
Process Overview. (a) The “APG support” Core Function includes the following departments:
Process Overview. In order to meet the expedited timeline set forth in Senate Bill (“SB”) 859, PG&E contacted the five remaining market participants who bid into the BioRAM 1 solicitation but were not awarded bids on October 14, 2016. PG&E offered these projects the opportunity to submit refreshed offers to be considered as a bilateral transaction. PG&E also reached out to two market 2 See Attestation of Xxx Xxxxxx, December 12, 2016 (attached as Appendix G). Advice 4984-E - 3 - December 20, 2016 participants who had not submitted offers into BioRAM 1 to invite them to submit offers. Of the seven projects invited to bid, six offers were submitted. In this negotiation, PG&E used the terms and conditions of the CPUC approved BioRAM PPA and negotiated specific revisions to incorporate the following provisions required by Resolution E-4805 to be included in any such bilateral contract:3 • 5 year contract term only; • Feedstock requirements updated, with at least 80 percent of the feedstock of the facility, on an annual basis, required to be a byproduct of sustainable forest management, which includes removal of dead and dying trees from Tier 1 and Tier 2 high hazard zones (“HHZs”) and is not from lands that have been clear cut. Additionally, at least 60 percent of the total feedstock on an annual basis shall be from Tier 1 and Tier 2 HHZs; • Removal of the fuel switching option from BioRAM 1; and • The facility must be an existing bioenergy project that commenced operations prior to June 1, 2013.
Process Overview. A registered agency can map data from a custom user interface or a data repository to the data requirements set forth in this ICA, packaging it in appropriate Web service calls that are sent to the SAVE Agency Web Service over the Internet or the USCIS intranet. This interface follows the design paradigms established by Service Oriented Architecture (SOA). Service-oriented interfaces are based on principles of loose coupling, supporting a broad set of diverse clients (possibly using different technologies), and real-time message exchanges. This document describes the interface in a service-oriented manner. As such, only the services provided by this Web service are documented. The interface on the client side is not documented as it is not appropriate for this ICA to document them for a service-oriented interface. The SAVE Program provides verification of immigration status services to qualified government agencies. Specified data is provided by the user Agency and SAVE attempts to confirm a status response. If a status cannot be provided by the initial automated check, subsequent manual checks may be required. Exhibit 1: SAVE Processing Event Sequence Table Participant Action Potential Outcomes Initial Verification Query (Agency3InitVerif) Immigration Status Returned Prompt: Photo Confirmation Prompt: Institute (Manual) Additional Verification Prompt: Institute (Manual) Third Level Verification Additional Verification Request (Agency3SubmitAdditVerif) Immigration Status Returned Prompt: Resubmit with Photocopy of Original Documents Third level Verification Request (Agency3SubmitThirdVerif) Immigration Status Returned Final (non-status) Message The current timeline for implementing an Agency Web service integration can vary widely depending on the amount of development time required by an agency. There are a number of steps that must be followed once an agency has completed Web service client development.
