RecordWell Data

City Council Meeting — Agenda Packet

City of Lynchburg · Lynchburg City County · City Council · meeting of Apr 23, 2024 · Agenda packets

Open the original document More from City of Lynchburg

Text

Extracted automatically from the original. Tables and formatting may not survive; the original document is authoritative.

CITY COUNCIL Tuesday, April 23, 2024 | 7:00 PM Council Chamber- City Hall 900 Church Street Lynchburg, VA 24504 AGENDA I. Invocation Vice Mayor Faraldi II. Recognitions II.1. Small Business Week Proclamation II.2. Economic Development Week Proclamation III. Consent Agenda IV. Public Hearing IV.3. Consideration of adopting Resolution #R-24-___ granting a non-exclusive interim license agreement to maintain and operate 1,670 linear feet of fiber optic cable between the City of Lynchburg and Sprint. IV.4. Consideration of adopting Ordinance #O-24-___ changing a certain area located at 717 & 725 Leesville Road from R-1, Low Density Residential District to R-4, High Density Residential District V. Public Comment V.5. Hear from a citizen regarding, "People that have inherited property forcing to sell demolished or $500 month [derelict] program property taxes with only 30 day time period." (Consulea Mosley). VI. General Business VI.6. Consideration of introducing Resolution #R-24-___ amending Lynchburg City Schools Major Classification Funding for FY 2024 and transferring $1,671,820 from Contingency Reserves to Instruction. VI.7. Consideration of introducing Resolution #R-24-___ amending the FY 2024 City/Federal/State Aid fund budget and appropriating $27,326 from the Library of Virginia to preserve several Circuit Court Records. VI.8. Consideration of adopting Resolution #R-24-___ approving the newly amended “Guidelines for Implementation of the Public-Private Transportation Act of 1995 and Public-Private Education Facilities & Infrastructure Act of 2002” for the City of Lynchburg. VI.9. Consideration of adopting Resolution #R-24-___ approving the Revised Emergency Operations Plan. VII. Closed Session Page 1 of 325 City Council Agenda Item IV.3. Action AGENDA ITEM SUMMARY MEETING DATE PRESENTED BY April 23, 2024 Lee Newland - City Engineer AGENDA ITEM # IV.3 Consideration of adopting Resolution #R-24-___ granting a non-exclusive interim license agreement to maintain and operate 1,670 linear feet of fiber optic cable between the City of Lynchburg and Sprint. RECOMMENDATION Consider approving the attached license agreement by adopting the attached proposed Resolution, that SPRINT COMMUNICATIONS COMPANY, L.P. (Sprint) is granted a non-exclusive interim license to maintain and operate fiber optic cable for telecommunications purposes. SUMMARY Sprint has asked to continue use and be granted a non-exclusive interim license to maintain and operate 1,670 linear feet of fiber optic cable for telecommunications purposes leaving the Norfolk Southern Railway corridor commencing at 12th Street and proceeding in a northerly direction along the westerly side of the abandoned railroad track (formerly Norfolk Western) within the corporate limits of the City of Lynchburg, Virginia (City), as more specifically described in that certain Interim License Agreement, dated January 9, 2024, between the City and Sprint Staff recommends authorization of the attached license agreement by adopting the attached proposed Resolution to permit the existing communications cable to remain, given that the encroachments cause no undue hardship to the City. PRIOR ACTION(S) Approved Ordinance on July 11, 1995. Approved Permit November 9, 2004. Physical Development Committee March 12, 2024 FISCAL IMPACT None CONTACT(S) Lee Newland - City Engineer Tom Williamson, Chief Information Officer Page 2 of 325 ATTACHMENT(S) 1. Proposed Resolution - Sprint & City Interim License Agreement (2024) 2. Sprint & City Interim License Agreement (2024) 3. Exhibit A - Sprint & City Interim License Agreement (2024) 4. Notice to Continue Franchise (2022) 5. Notice to Continue Franchise (2004) & #O-95-208 REVIEWED BY Date: March 19, 2024 Gaynelle Hart, Director of Public Works Date: April 04, 2024 Gregory Patrick, Deputy City Manager Date: April 18, 2024 Alicia Finney, Clerk of Council Page 3 of 325 RESOLUTION: #R-24-____ BE IT RESOLVED BY THE COUNCIL OF THE CITY OF LYNCHBURG: 1. That SPRINT COMMUNICATIONS COMPANY, L.P. (Sprint) is granted a non-exclusive interim license to maintain and operate 1,670 linear feet of fiber optic cable for telecommunications purposes leaving the Norfolk Southern Railway corridor commencing at 12 th Street and proceeding in a northerly direction along the westerly side of the abandoned railroad track (formerly Norfolk Western) within the corporate limits of the City of Lynchburg, Virginia (City), as more specifically described in that certain Interim License Agreement, dated January 9, 2024, between the City and Sprint. Such agreement is expressly incorporated herein by reference. 2. That the City Manager is authorized to execute the said Interim License Agreement on behalf of the City. 3. That this Resolution shall become effective upon its adoption. Adopted: Certified: ________________________________ Clerk of Council Page 4 of 325 Page 5 of 325 Page 6 of 325 Page 7 of 325 Page 8 of 325 Page 9 of 325 Page 10 of 325 Page 11 of 325 Page 12 of 325 Page 13 of 325 Page 14 of 325 Page 15 of 325 Page 16 of 325 Page 17 of 325 Page 18 of 325 Page 19 of 325 Page 20 of 325 Page 21 of 325 Page 22 of 325 Page 23 of 325 Page 24 of 325 Page 25 of 325 Page 26 of 325 City Council Agenda Item IV.4. Action AGENDA ITEM SUMMARY MEETING DATE PRESENTED BY April 23, 2024 Rachel Frischeisen, City Planner AGENDA ITEM # IV.4 Consideration of adopting Ordinance #O-24-___ changing a certain area located at 717 & 725 Leesville Road from R-1, Low Density Residential District to R-4, High Density Residential District RECOMMENDATION Approval of the petition to rezone 717 and 725 Leesville Road from R-1, Low Density Residential District to R-4, High Density Residential District. SUMMARY Abundant Life Estates, LLC, is petitioning to rezone approximately forty-eight hundredths (0.48) of an acre located at 717 & 725 Leesville Road from R-1, Low Density Residential District to R-4, High Density Residential District. The purpose of the rezoning petition is to allow the construction of an entrance to a twenty-six (26) unit residential development. The “duplex” style residential units and associated parking would be located in Campbell County and accessed via property in the City of Lynchburg. The portion of the project located in Campbell County was rezoned in 2023 from Business – General Commercial to Residential – Multi Family, and the County’s Future Land Use Map was amended from Urban Development Area Commercial to Medium to High Density Mixed. The proposed residential development would create a transition between the single household homes along Leesville Road and the more intense commercial development that may occur in Campbell County in the future. PRIOR ACTION(S) April 9, 2024: City Council Business Item Briefing. March 13, 2024: The Planning Commission recommended approval (6-0, with 1 absent; Gammon) of the rezoning petition. March 13, 2024: The Planning Division recommended approval of the petition. FISCAL IMPACT N/A CONTACT(S) Page 27 of 325 Rachel Frischeisen, City Planner ATTACHMENT(S) 1. Ordinance 2. Planning Commission Minutes, Report, and Attachments REVIEWED BY Date: April 15, 2024 William Martin, Community Development Director Date: April 15, 2024 Kent White, Assistant City Manager Date: April 18, 2024 Alicia Finney, Clerk of Council Page 28 of 325 UNCODIFIED ORDINANCE AN ORDINANCE CHANGING A CERTAIN AREA LOCATED AT 717 & 725 LEESVILLE ROAD FROM R-1, LOW DENSITY RESIDENTIAL DISTRICT TO R-4, HIGH DENSITY RESIDENTIAL DISTRICT. BE IT ORDAINED BY THE COUNCIL OF THE CITY OF LYNCHBURG that in order to promote the public necessity, convenience, welfare and good zoning practice that Chapter 35.2 of the Code of the City of Lynchburg, 1981, as amended, be and the same is hereby further amended by adding thereto Section 35.2- 54.__ which shall read as follows: Section 35.2-54.__. Change of a certain area located at 717 & 725 Leesville Road from R-1, Low Density Residential District to R-4, High Density Residential District. The area embraced within the following boundaries: BEGINNING AT A 1/2" REBAR FOUND ON THE EASTERN RIGHT OF WAY OF LEESVILLE RD; THENCE ALONG THE RIGHT OF WAY OF LEESVILLE RD N 17°44'27" E A DISTANCE OF 68.20' TO A 1/2" REBAR FOUND; THENCE S 72°50'03" E A DISTANCE OF 138.67' TO A 1/2" REBAR FOUND; THENCE N 17°07'00" E A DISTANCE OF 166.26' TO A 1/2" REBAR FOUND; THENCE S 72°37'52" E A DISTANCE OF 32.30' TO A POINT; THENCE S 17°34'32" W A DISTANCE OF 282.31' TO A POINT; THENCE N 57°01'59" E A DISTANCE OF 176.15' TO A 1/2" REBAR FOUND; WHICH IS THE POINT OF BEGINNING, HAVING AN AREA OF 0.480 ACRES …is hereby changed from R-1, Low Density Residential District to R-4, High Density Residential District. And the City Planner shall forthwith cause the “Official Zoning Map of Lynchburg, Virginia,” referred to in Section 35.2-30 of this chapter to be amended in accordance therewith. Adopted: Certified: _______________________ Clerk of Council Page 29 of 325 MINUTES OF THE MARCH 13, 2024 PLANNING COMMISSION MEETING (MINUTES HAVE BEEN APPROVED): Petition of Abundant Life Estates, LLC to rezone approximately forty-eight hundredths (0.48) of an acre located at 717 and 725 Leesville Road from R-1, Low Density Residential District to R-4, High Density Residential District to allow the construction of an entrance to a thirteen (13) duplex, twenty-six (26) unit, residential development. Ms. Rachel Frischeisen, City Planner, provided the following summary to the Commission. The subject property is comprised of two (2) parcels located at 717 and 725 Leesville Road totaling approximately forty-eight hundredths (0.48) of an acre. If the petition is approved, an entrance to a twenty-six (26) unit residential development would be constructed. The units would be “duplex” style, with two units in each building. The residential units and parking for the units would be located in Campbell County and accessed via property in the City of Lynchburg. The City’s Zoning Ordinance would consider these apartments, since the buildings will be on one common parcel, rather than individual lots. The property is recommended for Low Density Residential uses on the City’s Future Land Use Map (FLUM). These areas are dominated by single family detached housing at densities of up to four (4) dwelling units per acre. The portion of the project located in Campbell County was rezoned in 2023 from Business – General Commercial to Residential – Multi Family, and the County’s Future Land Use Map was amended from Urban Development Area Commercial to Medium to High Density Mixed. The City Traffic Engineer has requested a trip generation report to determine whether a turn lane and/or turn taper would be required, and noted that the entrance may need to be limited to right- in/right-out access only. The “duplex” style residential development would create a transition between the single household homes along Leesville Road and the more intense commercial development that would have occurred in Campbell County if the rezoning there had not been pursued, as well as the remaining commercial that surrounds the parcel. The Technical Review Committee (TRC) reviewed the petition on February 6, 2024. Comments were minor in nature and would be addressed prior to final plan approval. The Planning Division recommends approval of the petition. Chair Johnson asked if anyone was present to speak on behalf of the petition. Ms. Amy Seipp, PE, of Accupoint Surveying & Design, LLC, was present to represent the application. This project is on the City-County boundary. The structures would be in Campbell County. Access would be through the City. This project would keep a buffer between the single-family properties on Leesville Road in the City and the heavy commercial uses on Compson Way in Campbell County. The project would establish a transitional area and be consistent with Campbell County’s multi- family housing designation. The project would also go through the County’s Technical Review Committee to meet their regulations, such as stormwater, and the developers would coordinate with both the City and County, as needed. The project has no structures in the City, only an entrance. The project would include buffers along all boundaries in the City. The width of the proposed sidewalk has been updated from five (5) feet to six (6) feet. The traffic analysis was recently submitted to City staff for review. It does not appear to warrant a turn lane or taper. The proposed units mimic duplex structures in appearance – two units, side by side, under one roof. The units are all on one parcel. They are not for sale. The project would include sidewalks throughout and a dumpster on site. Sewer would be through Campbell County, constructed at the rear of the property; the owner has obtained an easement from the adjacent property owner for sewer. Water would be provided through the City but coordinated with Campbell County Utility and Service Authority (CCUSA) for billing purposes. Chair Johnson asked if there was anyone present to speak in favor or opposition of this petition. With there being none, Chair Johnson closed the public hearing. Commissioner Rogers asked if Bud Drive is a public road. Page 30 of 325 Ms. Seipp responded that research suggests it is City right-of-way. The title search was inconclusive. It has the appearance of a gravel driveway, but is shown on GIS as City right-of-way. Commissioner Marion asked if the petitioner would be improving the road. Ms. Seipp responded that the developer would be required to improve Bud Drive for fire safety purposes, so as not to dead-end the property. Bud Drive would be improved at least to the standard to be able to support the weight of a fire truck to traverse and enter the rear of the property. The fire department would have access through a fire gate on Bud Drive, if the main entrance were blocked. At this point, the road is treated as public, but neither the City nor the County is maintaining it. Commissioner Marion asked for confirmation that the residents would not be able to use the road to access the property. Ms. Seipp clarified that the gate to the property would block residents from accessing the property from Bud Drive. Access would only be for emergency/fire response purposes. Chair Johnson asked for more information about the proposed shared access drive with neighboring 727 Leesville Road. Ms. Seipp replied that portions of the driveway for 727 Leesville Road encroach on the subject property, 725 Leesville Road. All parties have agreed to the proposed commercial entrance, which includes a shared driveway, with an improved parking area for 727 Leesville Road, and safer egress for all. Chair Johnson asked the City Planner about the possibility of whether any units could be constructed in the proposed R-4 rezoned area within the City. Ms. Frischeisen said that constructing another building located in the small green space along the driveway within the City would be a tight fit, it is theoretically within the realm of possibility. Commissioners discussed the possibility. Commissioner Perault asked the City Planner to provide more information about review of the recently received traffic study. Ms. Frischeisen explained that the information was received after the Planning Commission report packet was distributed. The developer has indicated that the trip generation data does not indicate the need for a turn lane or taper. The City’s Traffic Engineer will review the data; any requirements would be enforced at the site plan phase and the developer would have to comply. (Note: After reviewing the submitted materials, the City’s Traffic Engineer concurred with the findings of the trip generation data. Neither a turn lane nor a taper is required in this case.) Commissioner Marion asked how the developer would handle a turn lane or taper, if required. Ms. Seipp explained that the developer would comply by configuring the entrance at their adjacent property. Commissioner Perault commented that if this project were in the City, there would be more discussion. Commissioners generally discussed traffic and development on Leesville Road. Page 31 of 325 Chair Johnson noted that this project takes away an R-1 zoned lot. Commissioner Perault noted that since the petition is only to grant access for a County development, he doesn’t want stand in the way of the County project. Commissioner Rogers remarked that there will eventually be a need for the Commission to revisit Leesville Road development. At some point, people will not want R-1 parcels along this section of the road, with the development that is currently happening there. Land use recommendations in the developing Comprehensive Plan will come into play. Commissioner Rogers indicated that he would support this petition. Commissioner Perault remarked that Leesville is in good shape, referencing the success of the Timberlake and Airport intersections. Commissioner Rogers made the following motion, seconded by Commissioner Bowden, and approved by the following vote: Based on the preceding Findings of Fact, the Planning Commission recommends to City Council approval of the request of Abundant Life Estates, LLC to rezone approximately forty-eight hundredths (0.48) acres at 717 and 725 Leesville Road from R-1, Low Density Residential District to R-4, High Density Residential District. AYES: Bowden, Henderson, Johnson, Marion, Perault, Rogers 6 NOES: 0 ABSTENTIONS: 0 ABSENT: Gammon 1 Page 32 of 325 The Department of Community Development City Hall, Lynchburg, VA 24504 434-455-3900 To: Planning Commission From: Planning Division Date: March 13, 2024 Re: Rezoning: R-1, Low Density Residential District to R-4, High Density Residential District – 717 & 725 Leesville Road. I. PETITIONER Abundant Life Estates, LLC, 7700 Timberlake Rd, Lynchburg, Virginia 24502 Representative: Amy Seipp, PE, Accupoint Surveying & Design, LLC, 6200 Fort Avenue, Lynchburg, Virginia 24502. Property Owner: Same as Petitioner. II. LOCATION The subject property is comprised of two (2) parcels located at 717 & 725 Leesville Road totaling approximately forty-eight hundredths (0.48) of an acre. III. PURPOSE The purpose of the rezoning petition is to allow the construction of an entrance to a twenty-six (26) unit residential development. The “duplex” style residential units and associated parking would be located in Campbell County and accessed via property in the City of Lynchburg. IV. SUMMARY • The portion of the project located in Campbell County was rezoned in July 2023 from Business – General Commercial to Residential – Multi Family, and the County’s Future Land Use Map was amended from Urban Development Area Commercial to Medium to High Density Mixed. • The property is recommended for Low Density Residential uses on the City’s Future Land Use Map (FLUM). • The “duplex” style residential development would create a transition between the single household homes along Leesville Road and the more intense commercial development that may occur in Campbell County in the future. The Planning Division recommends approval of the rezoning petition. V. FINDINGS OF FACT 1. Comprehensive Plan. The Comprehensive Plan 2013-2030 recommends a Low Density Residential use for the area. These areas are dominated by single family detached housing at densities of up to four dwelling units per acre. In addition to residential uses, they may include public and institutional uses compatible in scale with single family residential homes. Private recreation uses, including country clubs and swim and racquet clubs, and private open space are also appropriate for Low Density Residential areas. (p.72) 2. Zoning. The subject property was annexed into the City in 1976. The existing R-1, Low Density Residential District zoning was established in 1978. Page 33 of 325 Planning Commission: Rezoning: 717 & 725 Leesville Road – March 13, 2024 2 3. Proffers. The petitioner has not submitted proffers for this petition. 4. Board of Zoning Appeals (BZA). The Zoning Administrator has determined that no variances are needed for the development of the property as proposed. 5. Surrounding Area. There have been several items requiring City Council approval in the immediate area: • On May 22nd, 1979, City Council approved the Timberlake Road Study’s Proposed Zoning, rezoning 701 and 713 Leesville Road to B-1, Limited Business District. • On July 14th, 1981, City Council approved Phillip Coffey’s petition to rezone sixteen and eight tenths (16.8) acres at 762 Leesville Road from R-1, Low-Density Single-Family Residential District to R-4C, Medium-High Density, Multi-Family Residential District (Conditional) to allow the construction of twenty-seven (27) four (4) and six (6) unit apartments. • On May 14th, 1985, City Council approved Virginia Baptist Hospital’s CUP petition for the construction of a residential care center at Leesville Road and Del Ray Circle. • On August 13th, 1991, City Council approved Tree of Life Pentecostal Holiness Church’s CUP petition for the construction of a sanctuary and parking lot at 742 Leesville Road. • On June 13th, 1995, City Council approved Virginia Baptist Hospital’s CUP petition for the construction of a dining facility and building additions for Bridges Treatment Center at 693 Leesville Road. • On April 19th, 1996, City Council approved Virginia Baptist Hospital’s CUP petition for cottages and parking areas for Bridges Treatment Center at 693 Leesville Road. • On August 13th, 1996, City Council approved Tree of Life Ministry’s CUP petition for the expansion of existing church facilities at 742 Leesville Road. • On August 14th, 2001, City Council approved Centra Health’s CUP petition for the construction of modular classrooms, additional classrooms, residential cottages and parking for Bridges Treatment Center at 693 Leesville Road. • On December 11th, 2001, City Council approved Tree of Life Ministry’s CUP petition for Master Plan Development of a sanctuary, multi-purpose building, parking and athletic fields at 742 & 752 Leesville Road. • On December 10th, 2002, City Council approved Centra Health’s CUP petition to retain modular classrooms and construct additional classrooms/residential cottages and a nature walk for Bridges Treatment Center at 693 Leesville Road. • On February 10th, 2004, City Council approved Luther Shepard’s petition to rezone approximately three and eighty-nine hundredths (3.89) acres from R-1, Low-Density Single- Family Residential District to R-3C, Medium-Density, Two-Family Residential District (Conditional) at 800 Middle Street, to allow the construction of five (5) duplexes, in addition to three (3) existing duplexes. • On November 9th, 2004, City Council approved Joe Gantt’s petition to rezone approximately six and one tenth (6.1) acres from R-1, Low-Density Single-Family Residential District to R- 3C, Medium-Density, Two-Family Residential District (Conditional) and for a CUP at 716, 718 and 726 Leesville Road to allow the construction of fifty-nine (59) townhomes and associated parking. • On November 13th, 2007, City Council denied the petition of Lynchburg Renting, LLC to rezone approximately seven and thirteen hundredths (7.13) acres from R-1, Low-Density Single-Family Residential District to R-3C, Medium-Density, Two-Family Residential Page 34 of 325 Planning Commission: Rezoning: 717 & 725 Leesville Road – March 13, 2024 3 District (Conditional) and for a CUP at 714 Leesville Road disallowing the construction of seventy-six (76) townhomes and associated parking. • On April 13, 2010, City Council approved the Future Land Use Map (FLUM) amendment, Low Density Residential to Office and rezoning from R-1, Low Density Residential to B-2C, Neighborhood Business District (Conditional) (now B-1, Limited Business District) petitions of SFB, LLC at 623 Leesville Road to allow the construction of a business park. • On September 8, 2015, City Council denied the petition of Lynchburg Renting, LLC to rezone approximately seven and thirteen hundredths (7.13) acres from R-1, Low-Density Single-Family Residential to R-3C, Medium-Density, Two-Family Residential District (Conditional) and for a CUP at 714 Leesville Road disallowing the construction of a sixty- eight (68) unit townhomes and associated parking. • On September 13, 2016, City Council approved the petition of Kristie Napier to rezone approximately one (1) acre at 630 & 636 Leesville Road from R-3, Medium Density Residential District to B-1C, Limited Business District (Conditional) to allow the reuse of an existing building as a business. • On September 24, 2019, City Council approved the petition of Lynchburg Renting, LLC, for a CUP allow the construction of an eighty-seven (87) unit townhome development with one hundred fifty-seven (157) parking spaces and to rezone approximately eight (8) acres from R-1, Low Density Residential District and R-3, Medium Density Residential District to R- 3C, Medium Density Residential District (Conditional) at 710 and 714 Leesville Road. • On April 11, 2023, City Council approved the petition of Lynchburg Renting, LLC, for a CUP at 710 and 714 Leesville to allow the construction of eighty-seven (87) townhomes. (The CUP granted on September 24, 2019 had expired.) • On September 26, 2023, City Council approved the petition of Centra Health, Inc. to rezone approximately two and forty-seven hundredths (2.47) acres from R-1, Low Density Residential District to B-5C, General Business District (Conditional), and to amend the Future Land Use Map (FLUM) from Low Density Residential to Community Commercial at 759 Leesville Road to allow the construction of an entrance and parking area to serve the rehabilitation facility and behavioral health hospital that will be built on the portion of the property within Campbell County. 6. Site Description. The subject property is comprised of two (2) parcels located at 717 & 725 Leesville Road totaling approximately forty-eight hundredths (0.48) of an acre. 717 Leesville Road is currently vacant. 725 Leesville Road contains a mobile home and driveway. The property is bound to the north and south by single-household homes, to the east (across Leesville Road) by a cemetery and a townhouse development, and to the west by single- household homes and vacant land in Campbell County. 7. Proposed Use of Property. If the petition is approved, an entrance to a twenty-six (26) unit residential development would be constructed. The units would be “duplex” style, with two units in each building. The residential units and parking for the units would be located in Campbell County and accessed via property in the City of Lynchburg. The City’s Zoning Ordinance would consider these apartments, since the buildings will be on one common parcel, rather than individual lots. The entrance drive would also contain a small parking area to serve the property at 727 Leesville Road, which currently has a shared driveway with 725 Leesville Road. Page 35 of 325 Planning Commission: Rezoning: 717 & 725 Leesville Road – March 13, 2024 4 8. Traffic, Parking and Public Transit. The submitted concept plan indicates the construction of thirteen “duplex” style buildings, with a total of twenty-six (26) units and sixty (60) parking spaces. The number of parking spaces proposed is above the Zoning Ordinance requirement of one (1) space per unit, although the development would be subject to Campbell County’s development requirements since parking and residential units would be constructed within the County. The City Traffic Engineer has requested a trip generation report to determine whether a turn lane and/or turn taper will likely be required, and noted that the entrance would likely be limited to right-in/right-out access only. (Note: This data was submitted by the petitioner after this Planning Commission report was distributed. Upon reviewing the submitted materials, the City’s Traffic Engineer concurred with the findings of the trip generation data. Neither a turn lane nor taper is required in this case.) The area is served by the Greater Lynchburg Transit Company (GLTC) Route 7 with the nearest bus stop located about two hundred (200) feet away, across the street at the entrance to the Wyndsor Place townhouse development (716 Leesville Road). 9. Stormwater Management. An Erosion & Sediment Control Plan will be required prior to site plan approval. A stormwater management plan would be required if the disturbed area within the City exceeds five thousand (5,000) square feet. The submitted concept plan shows stormwater management facilities located at rear of the property in Campbell County. 10. Emergency Services. The City’s Fire Marshal and Police Department had no comments of concern regarding the proposal. 11. Impact. The proposed rezoning would facilitate the construction of a multifamily residential development in Campbell County. The property within the County was previously zoned for commercial use, which would likely have had a more significant negative impact on the adjoining residential area if it were to be developed as the previous zoning would have allowed. In July 2023, the portion within the County was rezoned from Business – General Commercial to Residential – Multi Family, and the Future Land Use Map was amended from Urban Development Area Commercial to Medium to High Density Mixed. The property surrounding the proposed development remains as Business – General Commercial zoning and Urban Development Area Commercial on the Future Land Use Map. The “duplex” style residential development would create a transition between the single household homes along Leesville Road and the more intense commercial development that may occur in Campbell County in the future. 12. Technical Review Committee. The Technical Review Committee (TRC) reviewed the petition on February 6, 2024. Comments were minor in nature and would be addressed prior to final plan approval. VI. PLANNING DIVISION RECOMMENDATION Based on the preceding Findings of Fact, the Planning Commission recommends to City Council approval of the request of Abundant Life Estates, LLC to rezone approximately forty-eight hundredths (0.48) acres at 717 and 725 Leesville Road from R-1, Low Density Residential District to R-4, High Density Residential District. Page 36 of 325 Planning Commission: Rezoning: 717 & 725 Leesville Road – March 13, 2024 5 This matter is respectfully offered for your consideration. Rachel Frischeisen City Planner pc: Wynter Benda, City Manager Greg Patrick, Deputy City Manager Kent White, Assistant City Manager Tom Martin, Director of Community Development Matthew Freedman, City Attorney J. Lee Newland, City Engineer Cynthia Kozerow, Lynchburg Police Department Thomas Goode, Fire Marshal Doug Saunders, Building Official Kevin Henry, Zoning Administrator Amy Seipp, PE, Representative Abundant Life Estates, LLC, Petitioner & Property Owner VII. ATTACHMENTS 1. Zoning Map with Adjoining Property Owners 2. Future Land Use Map 3. Watershed Map 4. Planimetric and Topographic Map 5. Narrative 6. Concept Plan 7. Property Photograph Page 37 of 325 ZoningZoning TRCTRC 75 83 95 83 80 83 176.3 144 83144 144 122.4 122.4 96.1 308 110 110 110 110 75 20 100.00 80.44 100.00 20 100 ~160.38 ~165.88 ~170.29 ~99.55 ~48.01 ~32.97 ~370.23Beyond City Limit ~353.87Beyond Ci ty 305 275 0 100 ~144.79 ~83.45 ~33.54 ~82.39 ~168.69 ~92.34 ~171.52 ~119.99 ~437.69 100.4 100.1 80.30 291.00 6 302.35 126.99 105.00 53.00 210.00 319.84 67.00 00 00 0 123.00 34.50 34.50 18.00 18 .00 18.00 195.00 195.00 67.00 67.0067.0067.0067.0067.0067.0067.0067 .00 50 34.50 34.50 18.00 18.00 18.00 18.00 18.0018.0018.00 18.0018.0018.00 18.00 18.00 18.00 18.00 200.89 708.00 708.00 34.5034.50 34.5034.50 34.50 34.50 34.5034.50 34.5034.50 0 18.00 18.00 18.00 18.00 18.00 18.00 18.0018.0018.00 18.0018.0018.00 00 18.0018.0018.00 18.0018.0018.00 8.00 18.00 18.00 18.00 18.00 18.00 18.00 67.0067.0067.0067.0067.0067.0067.0067.00 67.0067.0067.0067.0067.0067.0067.0067.0067.0067.0067 .00 60 60 (1) (1) (Part 13) (A) (2) (2) (1) (4) (B) (Part 14) (3A) (2) (3) (216) (3) (4) (Part 15) ! ! !! !!! ! ! ! ! ! 4 ! !1)) ! ! ! !! ! ! ! ! ! ! !8.698.69 !67.067.0!0 67.0067.00!18 67.0067.00!!!00 67.0067.00!!!18 67.0067.00!! 00 !00 67.0067.00!!!188 67.0067.00!!!67.067.0!67.067.0!0 67.0067.00!188 67.0067.00!!!0 67.0067.00!! 00!67.0067.00!!!00 67.0067.00!!!18 67.0067.00!!!67.067.0!67.067.0!67.067.0 !!00 !!0000 !! 00 !!0000 !67.007.00!67.0067.00 00 !! !67.0067.00 !! 7070!67.0067.00!! 6!67.0067.00 1 !! 6767!67.0067.00 0 !! ! 767.0067.00!! 66 !67.0067.00 ! ! 44 144 8080 82.39 80 82.3982.39 144 44 83 83 168. !8.6969 168.168.69 !!!.6969.6969 83 83 R-3C R-3C R-3C R-3C R-1R-1 B-1B-1 R-4R-4 R-1R-1 R-1R-1 R-3R-3 733733 730730 727727 710710 708708 714714 713A713A 308308 306306 304304 713713 701701 719719 721721 725725 305305 729729 735735 731731 734734 724724 716716 717717 716 100 716 100 716 101 716 101 716 102 716 102 716 103 716 103 716 104 716 104 716 105 716 105 716 106 716 106 716 107 716 107 716 200 716 200 716 201 716 201 716 202 716 202 716 203 716 203 716 204 716 204 716 205 716 205 716 206 716 206 716 207 716 207 716 300 716 300 67046704 716 801 716 801 716 802 716 802716 803 716 803 716 804 716 804 716 805 716 805716 806 716 806 716 807 716 807 716 808 716 808 307AͲB307AͲB 307307 BUD DR DEL RAY CIR LEESVILLE RD MAP SCALE:D ATE PRINTED: 1/24/2024 PROPERTY INFORMATIONPROPERTY INFORMATION LEGENDLEGEND qq PARCEL ID ADDRESS WEXFORD PL[PVT] MERIDIANST [PVT] BUD DR DALEAVE DALE AVE LINCOLNS WAY CAPSTONE DR ROTUNDA ST CORNERSTONEST BROOKVILLE CIR WALTONDR ALTA LN MIDDLE ST VISTA LN GROVERD KENBRIDGEPL MCVEIGH RD LAKEVIEW DR GATLINST LAKEVIEW DR WOODBINE DR MOREY PL MOREVIEW DR CEDAR HILL DR WINDSOR RD WOODLAND CIR LEESVILLERDLEESVILLERD SIMONSRUNSIMONSRUN ALTALNALTALN MELINDA DR MELINDA DR ALTALNALTALN LEESVILLE RD LEESVILLE RD ALTALNALTALN LEESVILLERDLEESVILLERD GREENVIEW DR GREENVIEW DR WARDSFERRY RD WARDSFERRY RD BUCKINGHAM DR BUCKINGHAM DR DEL RAY CIR DEL RAY CIR ALTA LNALTA LN GREENVIEW DR GREENVIEW DR LEESVILLE RD LEESVILLE RD ALTA LNALTA LN GREENVIEW DR GREENVIEW DR GREENVIEW DR GREENVIEW DR LEESVILLE RD LEESVILLE RD LEESVILLE RD LEESVILLE RD MELINDA DR MELINDA DRCHESTERFIELD RD CHESTERFIELD RD MOREVIEW DR MOREVIEW DR WARDS RD WARDS RD OVERVIEW MAPOVERVIEW MAP Subject PropertySubject Property BͲ1BͲ1 BͲ4BͲ4 BͲ5BͲ5 IͲ1IͲ1 IͲ2IͲ2 IͲ3IͲ3 RͲ1RͲ1 RͲ2RͲ2 RͲ3RͲ3 RͲ4RͲ4INͲ1INͲ1 INͲ2INͲ2 BͲ3BͲ3 RͲCRͲC 215 Foot Buffer215 Foot Buffer ABUNDANT LIFE ESTATES LLC 26202018 725 LEESVILLE RD 26202017 Parcel ID Address Parcel ID 725 LEESVILLE RD 717 LEESVILLE RD Address Address 1:1,529 Page 38 of 325 717 & 725 Leesville Road Parcel ID Address Owner 26202019 727 LEESVILLE RD HODGE, ERNEST G & SANDRA H 26202018 725 LEESVILLE RD ABUNDANT LIFE ESTATES LLC 26202016 721 LEESVILLE RD ABUNDANT LIFE ESTATES LLC 26202017 717 LEESVILLE RD ABUNDANT LIFE ESTATES LLC 26202015 719 LEESVILLE RD PICKING, BONNIE B & WILLIAM J 26202014 713 A LEESVILLE RD WIERINGO, KEVIN D 26202010 713 LEESVILLE RD RILEY, CLARENCE R JR 26202021 731 LEESVILLE RD SHERWOOD, DOUGLAS R & ANNETTE K 26202020 729 LEESVILLE RD 729 LEESVILLE RD LLC 26205004 716 LEESVILLE RD 101 WILLIAMSON, CHELSEA JO & NOORDSY, VICKI JO 26205002 716 LEESVILLE RD WYNDSOR PLACE TOWNHOMES ASSOC INC 26210003 730 LEESVILLE RD SELLERS, GENA L & JEFFREY R 26210001 724 LEESVILLE RD BEULAH BAPTIST CEMETERY 26205003 716 LEESVILLE RD 100 ROSS, DARREL LEE 1113200 21017 LEESVILLE RD 729 LEESVILLE RD LLC 384800 73 BUD DR ABUNDANT LIFE ESTATE LLC 1541300 45 BUD DR WIERINGO KEVIN 752800 96 BUD DR OAKS VILLAGE LLC 2259800 BUD DR ABUNDANT LIFE ESTATES LLC 1094600 ABUNDANT LIFE ESTATES LLC 1712600 RILEY CLARENCE R JR 963800 HODGE ERNEST G & SANDRA H CAMPBELL COUNTY ADMINISTRATOR FRANK ROGERS V D O T L Y N C H B U R G D I S T R I C T O F F I C E Page 39 of 325 FLUMFLUM TRCTRC ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! !!!!!!!!!!!!! !!!!!!!!!!!!!!! ! !!!!!!!!!!!!!!! !!!!!!!!!! !!!!!!!!! !!!!!!!!! !!!!!!!!! !!!!!!!!!! ! !! !! 733733 730730 727727 710710 714714 713A713A 308308 306306 304304 713713 719719 721721 725725 729729 735735 731731 734734 724724 716716 717717 716 100 716 100 716 101 716 101 716 102 716 102 716 103 716 103 716 104 716 104716105716105 716 106 716 106 716 107 716 107 716 200 716 200 716 201 716 201 716 202 716 202 716 203 716 203 716 204 716 204 716 205 716 205 716 206 716 206 716 207 716 207 716 300 716 300 716 301 716 301 701701 67026702 716 703 716 703 716 704 716 704 68006800716 801 716 801 716 802 716 802716 803 716 803 716 804 716 804 716 805 716 805716806716806716 807 716 807716808716808 307307 BUD DR DEL RAY CIR LEESVILLE RD MAP SCALE:D ATE PRINTED: 1/24/2024 PROPERTY INFORMATIONPROPERTY INFORMATION LEGENDLEGEND qq PARCEL ID ADDRESS WEXFORD PL[PVT] MERIDIANST [PVT] NOLANS WAY BUD DR DALE AVE CAPSTONE DR ROTUNDA ST CORNERSTONEST BROOKVILLE CIR WALTONDR ALTA LN GROVE RD MIDDLE ST VISTA LN KENBRIDGEPL MCVEIGH RD LAKEVIEW DR GATLINST LAKEVIEW DR WOODBINE DR MOREY PL MOREVIEW DR CEDARHILLDR WINDSOR RD WOODLAND CIR LEESVILLERDLEESVILLERD SIMONSRUNSIMONSRUN ALTALNALTALN MELINDA DR MELINDA DR ALTALNALTALN LEESVILLE RD LEESVILLE RD ALTALNALTALN LEESVILLERDLEESVILLERD GREENVIEW DR GREENVIEW DR WARDSFERRY RD WARDSFERRY RD BUCKINGHAM DR BUCKINGHAM DR DEL RAY CIR DEL RAY CIR ALTA LNALTA LN GREENVIEW DR GREENVIEW DR LEESVILLE RD LEESVILLE RD ALTA LNALTA LN GREENVIEW DR GREENVIEW DR GREENVIEW DR GREENVIEW DR LEESVILLE RD LEESVILLE RD LEESVILLE RD LEESVILLE RD MELINDA DR MELINDA DRCHESTERFIELD RD CHESTERFIELD RD MOREVIEW DR MOREVIEW DR WARDSRDWARDSRD WARDSRDWARDSRD OVERVIEW MAPOVERVIEW MAP 26202018 725 LEESVILLE RD 26202017 Parcel IDPPARCELARCEParcel IDParcel ID AddressDDAdAd ressress Parcel IDDDRESDDRESParcel IDParcel ID 725 LEESVILLE RD 717 LEESVILLE RD Address Address ABUNDANT LIFE ESTATES LLC Local Historic DistrictLocal Historic District Traditional ResidentialTraditional Residential Low Density ResidentialLow Density Residential Medium Density ResidentialMedium Density Residential High Density ResidentialHigh Density Residential Neighborhood CommercialNeighborhood Commercial Community CommercialCommunity Commercial Employment 2Employment 2 InstitutionInstitution DowntownDowntown Public UsePublic Use Public ParksPublic Parks Resource ConservationResource Conservation Employment 1Employment 1 Mixed UseMixed Use 1:1,529 Page 40 of 325 WatershedWatershed TRCTRC !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!! !!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!! !!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!! !!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!! !! 733733 730730 727727 710710 714714 713A713A 306306 304304 713713 719719 721721 725725 729729 735735 731731 734734 724724 716716 717717 716 100 716 100 716 101 716 101 716 102 716 102 716 103 716 103 716 104 716 104716105716105 716 106 716 106 716 107 716 107 716 200 716 200 716 201 716 201 716 202 716 202 716 203 716 203 716 204 716 204 716 205 716 205 716 206 716 206 716 207 716 207 716 300 716 300 716 301 716 301 716 302 716 302 63036303 716700716700 716701716701 716702716702 716703716703 716704716704 716 800 716 800 716 801 716 801 716 802 716 802716 803 716 803 716 804 716 804 716 805 716 805716806716806716 807 716 807716808716808 BUD DR DEL RAY CIR LEESVILLE RD MAP SCALE:D ATE PRINTED: 1/24/2024 PROPERTY INFORMATIONPROPERTY INFORMATION LEGENDLEGEND qq PARCEL ID ADDRESS Blackwater Creek MERIDIANST [PVT] WEXFORD PL[PVT] NOLANS WAY BUD DR DALE AVE CAPSTONE DR ROTUNDA ST CORNERSTONEST BROOKVILLE CIR WALTONDR ALTA LN MIDDLE ST GROVE RD VISTA LN KENBRIDGEPL MCVEIGH RD LAKEVIEW DR GATLINST LAKEVIEW DR WOODBINE DR MOREY PL MOREVIEW DR CEDARHILLDR WINDSOR RD WOODLAND CIR LEESVILLE RDLEESVILLERD SIMONSRUNSIMONSRUN ALTALNALTALN MELINDA DR MELINDA DR ALTALNALTALN ALTALNALTALN LEESVILLE RDLEESVILLERD GREENVIEW DR GREENVIEW DR WARDSFERRY RD WARDSFERRY RD BUCKINGHAM DR BUCKINGHAM DR DEL RAY CIR DEL RAY CIR ALTA LNALTA LN GREENVIEW DR GREENVIEW DR LEESVILLE RD LEESVILLE RD ALTA LNALTA LN GREENVIEW DR GREENVIEW DR GREENVIEW DR GREENVIEW DR LEESVILLE RD LEESVILLE RD LEESVILLERDLEESVILLERD MELINDA DR MELINDA DRCHESTERFIELD RD CHESTERFIELD RD MOREVIEW DR MOREVIEW DR WARDSRDWARDSRD WARDS RD WARDS RD OVERVIEW MAPOVERVIEW MAP ABUNDANT LIFE ESTATES LLC Base Flood ElevationBase Flood Elevation FloodwayFloodway FloodzoneFloodzone River / Lake / StreamRiver / Lake / Stream Subject PropertySubject Property26202018 725 LEESVILLE RD 26202017 Parcel IDPPARCELARCEParcel IDParcel ID AddressDDAdAd ressress Parcel IDDDRESDDRESParcel IDParcel ID 725 LEESVILLE RD 717 LEESVILLE RD Address Address 1:1,529 Page 41 of 325 Planimetric and Topographic-TRCPlanimetric and Topographic-TRC TRCTRC !! !! !! !! !! !! !! !! !! !! !! !! !! !! !! !! !! ! ! ! ! !!! ! ! ! ï ï ï ï ïï ïï ï ïï ïïïïï ïïï ïïïïïï ïï ïï ïï ïïï ï ïï ï ï ï ! ï ! ! ! ïïï ï ïï ï ï ïï ïïïï ïï ïï ï ïï ïï ï ïï ïï ï ï ïï ï ïïï ï ïï ï ïï ï ïï ïï ïï ï ïï ïï ï ï ï ïï ïïïïï ï ïïï ï ïïïï ï ïïï ï ïï ï ï ïï ïïï ïï ïï ïïïïï ïïï ïï ïïïïï ïï ïïï ïïï ïï ïï ïïïï ïï ïï ï ïï ïïïï ï ïï ïïïïï ï ï ï ïïï ï ïï ï ï ïï ï ï ïïï ïï ïï ï ï ï ïï ïïï ï ïï ï ï ï ïïï ï ïï ï ï ïï ï ï ïïï ïï ïï ïïïï ï ïïïï ï ï ï ïïïï ïï ïïï ï ïïïïï ï ï ï ï ïïï ï ïï ï ïï ïïïïï ï ïïï ï ïï ï ïïïïï ïï ïï ïï ï ïïïïï ï ï ïïï ïïïï ï ïïï ï ï ï ï ïïï ï ïï ï ï ïï ï ïï ï ï ïï ïï ïïï ïï ïïïï ï ï ï ï ïïïï ï ï ï ïï ï ï ïï ï ï ïï ï ïï ïï ïïïï ï ïïï ï ïï ïï ïï ï ïïïï ï ï ï ï ïï ï ï ïï ï ï ï ïï ï ï ï ï ï ïïïï ïïïï ï ï ï ï ï ïï ï ïï ï ï ï ï ïï ïï ï ï ï ï ï ï ïï ïï ï ï ï ï ï ï ï ï ï ï !! ! ! !!! !!!!!! ! !! ! !!!!!! !! !!!!!!!! !!! !!!!!!!!! !! !! !!!!!!!!!!! !!!!!!!! !! !!! !!!!!!! !!!!!!!!!! !!! !!!!!!!!!!!!!!! !!!!!!! !!!!! !!!!!! ! !! ! ! !! !!!!!!! !!!! ï ï ïïï ïïïïï ïïïï ï ï ïïïï ïïïï ï ï ïïï ï ï !!!!!!!!!! !!!!! !!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!! !!!!!!!!!!! !! !!! !!!!!!!!!!!!! !! !!!! !!!!!!!!!!!!! !!! !!!!! !!!!!!!!!!! !!!! !!!!!! !!!!!!! !!!!!!! ! !! !!!!!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!!!!!!! !!!! !! !! !!! !!!!! ! !!! !!!!!!!!!!!!!! !! !!! !!!!!!!!!!! !!! !!!! !!!!! ! !!!!! !!!!!!!!! !!!!!!!!!!!!!!!!! !!!! !!! !!!!!!!!! ! !!! !!!!!!!!!!!!! ! !!!!! !!!!!!!!!!!!! !!!! !!!!!!! !!!!!!!!! !! !!! !!!!!! !!!!!!! ! !!!!! !! !!!!!! !!! !!!!!! !!!!!!!!!!!!!!!!!! !!! !! ! !!! !! ! !!! !! !! 733733 739739 730730 727727 710710 714714 713A713A 308308 306306 713713 719719 721721 725725 3030 729729 735735 731731 734734 724724 716716 717717 716 100 716 100 716 101 716 101 716 102 716 102 716 103 716 103 716 104 716 104716105716105 716 106 716 106 716 107 716 107 716 200 716 200 716 201 716 201 716 202 716 202 716 203 716 203 716 204 716 204 716 205 716 205 716 206 716 206 716 207 716 207 63006300 716 802 716 802716 803 716 803 716 804 716 804 716 805 716 805716806716806716 807 716 807716808716808 BEULAHBAPTIST CEMETERY BUD DR DEL RAY CIR LEESVILLE RD 950 940 930 920 970 960 950 940 910 900 930 950 940 950 City of Lynchburg - GIS Office - 434.455.3961 - GIS@lynchburgva.gov MAP SCALE:D ATE PRINTED: 1/24/2024 PROPERTY INFORMATIONPROPERTY INFORMATION LEGENDLEGEND qq PARCEL ID ADDRESS WEXFORD PL[PVT] NOLANS WAY CUPOLA ST BUD DRCAPSTONEDR DALE AVE ROTUNDA ST RIDGELINE LN BROOKVILLE CIR WALTONDR ALTA LN GROVE RD MIDDLE ST VISTA LN KENBRIDGEPL MCVEIGH RD LAKEVIEW DR GATLINST LAKEVIEW DR WOODBINE DR MOREY PL MOREVIEW DR CEDARHILLDR WINDSOR RD WOODLAND CIR LEESVILLERDLEESVILLERD SIMONSRUNSIMONSRUN ALTA LNALTALN MELINDA DR MELINDA DR ALTALNALTALN LEESVILLE RD LEESVILLE RD ALTALNALTALN LEESVILLERDLEESVILLERD GREENVIEW DR GREENVIEW DR WARDSFERRY RD WARDSFERRY RD BUCKINGHAM DR BUCKINGHAM DR DEL RAY CIR DEL RAY CIR ALTA LNALTA LN GREENVIEW DR GREENVIEW DR LEESVILLE RD LEESVILLE RD ALTA LNALTA LN GREENVIEW DR GREENVIEW DR GREENVIEW DR GREENVIEW DR LEESVILLE RD LEESVILLE RD LEESVILLE RD LEESVILLE RD MELINDA DR MELINDA DRCHESTERFIELD RD CHESTERFIELD RD MOREVIEW DR MOREVIEW DR WARDSRDWARDSRD WARDS RD WARDS RD OVERVIEW MAPOVERVIEW MAP UtilitiesUtilities WaterWater ActiveActive ProposedProposed AbandonedAbandoned SanitarySanitary StormStorm Planimetrics Planimetrics PavedPaved UnpavedUnpaved OtherOther SidewalkSidewalk RoadwayRoadway ParkingParking DrivewayDriveway ͲͲ ͲͲ ͲͲ ͲͲStructureStructure ͲͲ ͲͲ ͲͲ ͲͲ TopographyTopography ContourContour 20'20' 10'10' 100'100' 50'50' 5'5' 1'1' ABUNDANT LIFE ESTATES LLC 725 LEESVILLE RD 717 LEESVILLE RD Address Address 26202018 725 LEESVILLE RD 26202017 Parcel IDPPARCELARCEParcel IDParcel ID AddressDDAdAd ressress Parcel IDDDRESDDRESParcel IDParcel ID 1:1,529 Page 42 of 325   ^hZszKZ^E'/EZ^^K/>s>hdKZ^ ϰϯϰ͘ϲϭϬ͘ϰϯϯϰ_ϲϮϬϬ&KZdsEhͮ>zE,hZ'͕sϮϰϱϬϮ ǁǁǁ͘ĂĐĐƵƉŽŝŶƚƐƵƌǀĞLJŝŶŐ͘ĐŽŵηϳϮϯϲϮϵ    DĂƌĐŚϭϮ͕ϮϬϮϰ  ĞƉĂƌƚŵĞŶƚŽĨŽŵŵƵŶŝƚLJĞǀĞůŽƉŵĞŶƚ ŝƚLJŽĨ>LJŶĐŚďƵƌŐ ϵϬϬŚƵƌĐŚ^ƚƌĞĞƚ >LJŶĐŚďƵƌŐ͕sϮϰϱϬϰ   Z͗ WƌŽũĞĐƚEĂƌƌĂƚŝǀĞ ϳϮϱ>ĞĞƐǀŝůůĞZŽĂĚ͕>LJŶĐŚďƵƌŐ͕sϮϰϱϬϮ WĂƌĐĞů/ηϮϲϮϬϮϬϭϴ  ĞĂƌŝƚLJŽĨ>LJŶĐŚďƵƌŐĞƉĂƌƚŵĞŶƚŽĨŽŵŵƵŶŝƚLJĞǀĞůŽƉŵĞŶƚ͕  ĐĐƵƉŽŝŶƚ ^ƵƌǀĞLJŝŶŐ Θ ĞƐŝŐŶ͕ >> ;^Ϳ ŝƐ ƌĞƋƵĞƐƚŝŶŐ͕ ŽŶ ďĞŚĂůĨ Ž Ĩ < Ă ƌ ů D ŝ ů ů Ğ ƌ Z Ğ Ă ů ƚ LJ > >  ͕ Ă  ƉĞƚŝƚŝŽŶƚŽƌĞnjŽŶĞWĂƌĐĞů/η͛Ɛ͗ϮϲϮϬϮϬϭϴΘϮϲϮϬϮϬϭϳ͘dŚĞƌĞƋƵĞ ƐƚŝƐĨŽƌƚŚĞƌĞnjŽŶŝŶŐŽĨƚŚĞƐĞ ƚǁŽ;ϮͿƉĂƌĐĞůƐĨƌŽŵ͞ZͲϭʹ>ŽǁĞŶƐŝƚLJZĞƐŝĚĞŶƚŝĂů͟ƚŽ͞ZͲϰʹ ,ŝŐŚĞŶƐŝƚLJZĞƐŝĚĞŶƚŝĂů͘͟dŚĞƐĞ ƉĂƌĐĞůƐƐĞƌǀĞĂƐƚŚĞĞŶƚƌĂŶĐĞĂĐĐĞƐƐĂŶĚǁĂƚĞƌƐĞƌǀŝĐĞĐŽŶŶĞĐƚŝ ŽŶƚŽƚŚĞĚƵƉůĞdžĚĞǀĞůŽƉŵĞŶƚ ŽŶůLJ͘  dŚĞ ďƵŝůĚŝŶŐ ƐƚƌƵĐƚƵƌĞƐ ĂƌĞ ƉƌŽƉŽƐĞĚ ŝŶ ĂŵƉďĞůů ŽƵŶƚLJ ĂŶĚ ǁĂƚĞƌ ƐĞƌǀŝĐĞ ǁŝůů ďĞ ĐŽŽƌĚŝŶĂƚĞĚďĞƚǁĞĞŶĂŵƉďĞůůŽƵŶƚLJhƚŝůŝƚŝĞƐĂŶĚ^ĞƌǀŝĐĞƵƚŚŽ ƌŝƚLJ;h^ͿĂŶĚƚŚĞŝƚLJŽĨ >LJŶĐŚďƵƌŐtĂƚĞƌZĞƐŽƵƌĐĞƐ͘ƌĞnjŽŶŝŶŐĂƉƉůŝĐĂƚŝŽŶǁĂƐƐƵďŵŝƚƚĞ ĚĂŶĚĂƉƉƌŽǀĞĚŝŶĂŵƉďĞůů ŽƵŶƚLJĨŽƌƚŚĞĂĚũŽŝŶŝŶŐƉƌŽƉĞƌƚŝĞƐƚŽŵĂŝŶƚĂŝŶƚŚĞŽǀĞƌĂůůĐŽŶ ƚŝŶƵŝƚLJŽĨƌĞƐŝĚĞŶƚŝĂůƵƐĞŝŶƚŚĞ ĂƌĞĂ ĂŶĚ ƚŚĞ ƌĞĐĞŶƚůLJ ĂĚŽƉƚĞĚ &ƵƚƵƌĞ >ĂŶĚ hƐĞ DĂƉ njŽŶŝŶŐ ŽĨ DĞĚ ŝƵŵ ƚŽ ,ŝŐŚͲĞŶƐŝƚLJ ZĞƐŝĚĞŶƚŝĂů͘  WůĞĂƐĞůĞƚƵƐŬŶŽǁŝĨLJŽƵŚĂǀĞĂŶLJƋƵĞƐƚŝŽŶƐŽƌĐŽŶĐĞƌŶƐ͕ƚŚĂŶŬLJŽƵĨŽƌLJŽƵƌƚŝŵĞ͘  ĞƐƚZĞŐĂƌĚƐ͕      ŵLJ<͘^ĞŝƉƉ͕W WĂƌƚŶĞƌ͕WƌŝŶĐŝƉĂůŶŐŝŶĞĞƌ ĐĐƵƉŽŝŶƚ^ƵƌǀĞLJŝŶŐΘĞƐŝŐŶ͕>> Page 43 of 325 OWNER INFORMATION: NAME: ABUNDANT LIFE ESTATES LLC ADDRESS: 7700 TIMBERLAKE ROAD LYNCHBURG, VA 24502 EMAIL: KARL@KARLMILLERTEAM.COM DESIGNER INFORMATION: NAME: ACCUPOINT SURVEYING & DESIGN, LLC ADDRESS: 6200 FORT AVENUE LYNCHBURG, VA 24502 PROJECT DESIGNER: AMY K. IGARTA-SEIPP, PE REGISTRATION NUMBER: 0402 036952 PHONE: 434-610-4334 E-MAIL ADDRESS: ASEIPP@ACCUPOINTSURVEYING.COM SOURCE OF SURVEY: ACCUPOINT SURVEYING & DESIGN, LLC SOURCE OF TOPOGRAPHY: ACCUPOINT SURVEYING & DESIGN, LLC COUNTY/CITY, STATE: CITY OF LYNCHBURG, VIRGINIA CAMPBELL COUNTY, VIRGINIA TAX MAP REFERENCES: CITY OF LYNCHBURG CAMPBELL COUNTY 26202018 13C-4-2 26202017 13C-4-4 13C-5-C EXISTING ZONING: CITY OF LYNCHBURG CAMPBELL COUNTY R-1 - LOW DENSITY RESIDENTIAL B-GC - BUSINESS, GENERAL COMMERCIAL PROPOSED ZONING CITY OF LYNCHBURG CAMPBELL COUNTY R-4 - HIGH DENSITY RESIDENTIAL R-MF - RESIDENTIAL MULTIFAMILY PROPOSED PROPERTY USE: TWO-UNIT RESIDENTIAL COMPLEX C-1 COVER SHEET C-2 CONCEPTUAL SITE PLAN C-3 FIRE TRUCK TURNAROUND TEMPLATE C-4 INTERSECTION SIGHT DISTANCE 1. THIS PLAN WAS PREPARED AT THE REQUEST OF KARL MILLER REALTY LLC. 2. NO DELINEATION OF WETLANDS WAS REQUESTED OR MADE AS PART OF THIS PLAN. 3. BY GRAPHIC SCALING ONLY, THIS PROPERTY AS PLATTED FALLS WITHIN THE FLOOD ZONE "X" AS DETERMINED BY FEMA AND SHOWN ON THEIR MAP NUMBER 5100930104D BEARING AN EFFECTIVE DATE OF JUNE 3, 2008 IN THE CITY OF LYNCHBURG AND MAP NUMBER 51031C0105D BEARING AN EFFECTIVE DATE OF AUGUST 28, 2008 IN CAMPBELL COUNTY. 4. THIS EXISTING CONDITIONS PLAN WAS PREPARED FROM AN ACTUAL AND CURRENT FIELD SURVEY MADE UNDER MY SUPERVISION AND COMPLIES WITH THE MINIMUM STANDARDS AND PROCEDURES ESTABLISHED BY THE VIRGINIA STATE BOARD OF ARCHITECTS, PROFESSIONAL ENGINEERS, LAND SURVEYORS, CERTIFIED INTERIOR DESIGNERS AND LANDSCAPE ARCHITECTS TO THE BEST OF MY KNOWLEDGE AND BELIEF. 5. THIS PROPERTY IS ZONED R-1 - LOW DENSITY RESIDENTIAL (CITY OF LYNCHBURG) & B-GC - BUSINESS, GENERAL COMMERCIAL (CAMPBELL COUNTY). 6. THIS PARCEL IS CURRENTLY SERVED BY CITY OF LYNCHBURG WATER. 7. EXISTING UTILITIES ARE SHOWN AT APPROXIMATE LOCATIONS. CONTRACTOR IS RESPONSIBLE FOR VERIFYING EXACT LOCATION AND DEPTHS PRIOR TO CONSTRUCTION. 8. THE CONTRACTOR SHALL CONTACT THE CITY ENVIRONMENTAL REVIEWER, THE CITY CONSTRUCTION COORDINATOR, CAMPBELL COUNTY, AND MISS UTILITY (811) AT LEAST 48 HOURS PRIOR TO ANY CONSTRUCTION OR EXCAVATION ACTIVITY AND ADVISE THE NATURE AND LOCATION OF WORK. 9. NO SITE WORK, LOGGING, GRUBBING OR GRADING IS PERMITTED PRIOR TO THE ISSUANCE OF A LAND DISTURBING PERMIT. 10. ALL CONSTRUCTION SHALL BE PERFORMED IN ACCORDANCE WITH THE CURRENT EDITION OF THE CITY OF LYNCHBURG MANUAL OF SPECIFICATIONS AND STANDARD DETAILS, AND CAMPBELL COUNTY REQUIREMENTS. 11. THE LIMITS OF CLEARING AND GRADING AND ALL CRITICAL AREAS SHOULD BE CLEARLY MARKED/FLAGGED IN THE FIELD PRIOR TO THE PRE-CONSTRUCTION CONFERENCE. 12. THE CONTRACTOR SHALL BE FULLY LIABLE FOR ANY DAMAGES TO PUBLIC OR PRIVATE PROPERTY CAUSED BY CONSTRUCTION OPERATION AND SHALL RESTORE DAMAGED PROPERTY TO EXISTING OR BETTER CONDITION AT NO ADDITIONAL COST TO THE OWNER. 13. ALL GRASSED AREAS DISTURBED BY CONSTRUCTION SHALL BE SEEDED AND PROTECTED WITH EROSION CONTROL PRACTICES AND AS SHOWN ON THE PLAN HEREIN. 14. VEGETATIVE AND STRUCTURAL EROSION AND SEDIMENT CONTROL DEVICES SHALL BE CONSTRUCTED AND MAINTAINED FOR ALL DISTURBED AREAS IN ACCORDANCE WITH ALL LOCAL REQUIREMENTS AND THE LATEST EDITION OF THE VIRGINIA EROSION AND SEDIMENT CONTROL HANDBOOK. ALL EROSION AND SEDIMENT CONTROL DEVICES SHALL BE INSTALLED BEFORE EXCAVATION BEGINS. 15. THE CONTRACTOR SHALL REPLACE ALL DISTURBED SURFACES IN KIND, INCLUDING PAVEMENT, STONE, DITCHES, MAILBOXES, SHRUBS, ETC. AND/OR AS SHOWN ON THIS PLAN. 16. ALL PROPERTY PINS DISTURBED DURING CONSTRUCTION SHALL BE REPLACED BY A LICENSED LAND SURVEYOR. 13. HORIZONTAL CONTROL IS BASED ON NAV 83 VA SOUTH ZONE. VERTICAL CONTROL IS BASED ON NAV88 GEOID 18. 14. MAINTAIN OVERHEAD AND UNDERGROUND ELECTRICAL, TELEPHONE, AND GAS SERVICES AND ALL OTHER UNDERGROUND UTILITIES DURING ENTIRE CONSTRUCTION PERIOD. OUTAGES WILL NOT BE ALLOWED. SHOULD OUTAGES BECOME NECESSARY, CONTACT THE ENGINEER OF RECORD IMMEDIATELY. 15. ANY SITEWORK AND DETAILS NOT COVERED BY THESE PLANS, CAMPBELL COUNTY, OR THE CITY OF LYNCHBURG MANUAL OF SPECIFICATIONS AND STANDARD DETAILS SHALL CONFORM TO THE VIRGINIA DEPARTMENT OF TRANSPORATION'S ROAD AND BRIDGE SPECIFICATIONS, CURRENT EDITIONS. 16. THIS ENGINEER AND/OR SURVEYOR TAKES NO RESPONSIBILITY FOR THE LOCATION OR ACCURACY OF THE UTILITIES AS SHOWN HEREIN. THE CONTRACTOR SHALL BE RESPONSIBLE FOR CONTACTING THE UTILITY COMPANIES TO SEE IF ANY UTILITIES EXIST WITHIN THE PROJECT AREA BEFORE CONSTRUCTION BEGINS. ANY COST INCURRED BY DAMAGING ANY UTILITY WITHIN THE PROJECT SHALL BE AT THE EXPENSE OF THE CONTRACTOR. 17. WATER SERVICE CONNECTIONS SHALL NOT BE USED FOR DEMOLITION, CONSTRUCTION, OR LANDSACPING PURPOSES UNTIL THE APPROPRIATE BACKFLOW PREVENTION ASSEMBLY HAS BEEN INSTALLED AND APPROVED AND A PASSING TEST HAS BEEN SUBMITTED TO THE DEPARTMENT OF WATER RESOURCES AND CAMPBELL COUNTY UTILITIES AND SERVICE AUTHORITY. THIS INCLUDES NEW AND EXISTING WATER SERVICE CONNECTIONS, AS WELL AS TEMPORARY AND PERMANENT WATER SERVICE CONNECTIONS. 18. ALL LIGHTING SHALL BE SHIELDED, NON-GLARE TYPE LIGHTING AND SHALL NOT EXCEED ZERO CANDLEPOWER AT THE PROPERTY LINES. 19. ALL CONNECTIONS TO PUBLIC WATER AND SANITARY SEWER SHALL BE PERFORMED IN ACCORDANCE WITH THE CITY OF LYNCHBURG MANUAL OF SPECIFICATIONS AND STANDARD DETAILS, LATEST EDITION. 20. ALL EXPOSED SOILS SHALL BE PERMANENTLY SEEDED AND STABLIZED IN ACCORDANCE WITH VIRGINIA E&S REGULATIONS IMMEDIATELY AFTER REACHING FINISHED GRADE. FINISHED GRADE IS FINAL GRADE OF THE SITE AFTER EXCAVATING OR FILLING WHICH CONFORMS TO THE APPROVAL FINAL GRADING PLAN. THE FINISH GRADE IS ALSO THE GRADE AT THE TOP OF A PAVED SURFACE. 21. APPROXIMATE EARTH QUANTITIES MAY DIFFER FROM ACTUAL CONDITIONS AND THE CONTRACTOR SHALL ENSURE PROPER SHRINK FACTORS. 22. SOIL MATERIALS SHALL BE FREE OF DEBRIS, ROOTS, WOOD, SCRAP MATERIAL, VEGETATION, REFUSE, SOFT UNSOUND PARTICLES, AND FROZEN DELETERIOUS OR OBJECTIONABLE MATERIALS. THE MAXIMUM PARTICLE DIAMETER SHALL BE ONE-HALF THE LIFT THICKNESS. COMMON FILL MATERIAL SHALL BE UNCLASSIFIED SOIL MATERIAL WITH THE CHARACTERISTICS REQUIRED TO COMPACT TO THE SOIL DENSITY SPECIFIED FOR THE INTENDED LOCATION. BACKFILL AND FILL MATERIAL: ASTM D 2487, CLASSIFICATION GW, GP, SW, SP WITH A MAXIMUM OF 10 PERCENT BY WEIGHT PASSING ASTM D 1140, NO. 200 SIEVE. ASD JOB #: FILE #: REVISION/DATE COVER SHEET C-1 DATE: PARCEL ID: 2022-664 2022-664 CONCEPT 26202018 GENERAL NOTES GENERAL INFORMATION DRAWING INDEX 725 LEESVILLE ROAD LYNCHBURG, VA 24502 DECEMBER 19, 2023 VICINITY MAP SCALE: NTS Know what's below. Call before you dig. R LEESVILLE ROAD BUD DRIVE SITESITE DECEMBER 19, 2023 MISS UTILITY TICKET NUMBER: TBD PRELIMINARY CITY OF LYNCHBURG, VIRGINIA CAMPBELL COUNTY, VIRGINIA CONCEPTUAL SITE PLAN FOR KARL MILLER DEL RAY CIRCLE ALTA LANE Page 44 of 325 PROPERTY LINE SETBACK PROPOSED BUILDING CONCRETE SWM FACILITY - APPROXIMATE SIZE EXISTING WATER LINE PROPOSED WATER LINE PROPOSED SEWER LINE PROPOSED MANHOLE CITY OF LYNCHBURG CAMPBELL COUNTY 24' LEESVILLE ROAD CAMPBELL COUNTY 13C-4-5 103 BUD DRIVE TAX ID# 000752700 OAKS VILLAGE LLC B-GC - BUSINESS, GENERAL COMMERCIAL PROPOSED DUMPSTER W/ 6' SOLID PRIVACY ENCLOSURE PROPOSED DUMPSTER W/ 6' SOLID PRIVACY ENCLOSURE PROPOSED NEW CONNECTION FOR SHARED ACCESS TO 727 LEESVILLE ROAD PROPOSED RESIDENTIAL ENTRANCE (24' WIDTH) W/ CURB & GUTTER PROPOSED STORMWATER MANAGEMENT FACILITY PROPOSED 6' WIDE SIDEWALK PROPOSED SANITARY SEWER EXTENSION (APPROXIMATELY 712 LF) SEE SHEET C-4 10' SIDE SETBACK 20' REAR SETBACK PROPOSED 20' SANITARY SEWER EASEMENT CITY OF LYNCHBURG HODGE, ERNEST G & SANDRA H 727 LEESVILLE ROAD PARCEL ID: 26202019 R-1 - LOW DENSITY RESIDENTIAL DB 691 PG 513 CITY OF LYNCHBURG ABUNDANT LIFE ESTATES LLC 721 LEESVILLE ROAD PARCEL ID: 26202016 R-1 - LOW DENSITY RESIDENTIAL DOCUMENT NO: 230006363 CITY OF LYNCHBURG PICKING, BONNIE B & WILLIAM J 719 LEESVILLE ROAD PARCEL ID: 26202015 R-1 - LOW DENSITY RESIDENTIAL DOCUMENT NO: 130006805 CITY OF LYNCHBURG WIERINGO, KEVIN D 713 A LEESVILLE ROAD PARCEL ID: 26202014 R-1 - LOW DENSITY RESIDENTIAL DOCUMENT NO: 200000125 CAMPBELL COUNTY 12K-1-15 21017 LEESVILLE RD TAX ID# 001113200 729 LEESVILLE RD LLC B-GC - BUSINESS, GENERAL COMMERCIAL CAMPBELL COUNTY 13C-4-4A (NO ADDRESS) TAX ID# 000963800 HODGE, ERNEST G & SANDRA H B-GC - BUSINESS, GENERAL COMMERCIAL CAMPBELL COUNTY 13C-4-2A 45 BUD DRIVE TAX ID# 001541300 WEIRINGO, KEVIN B-GC - BUSINESS, GENERAL COMMERCIAL DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX 24' FIRE ACCESS ROAD W/ SURFACE THAT SUPPORTS A FIRE APPARATUS WEIGHING 75,000 LBS & 25' FIRE ACCESS GATE W/ KNOX PADLOCK OR EQUIVALENT. FOR EMERGENCY ACCESS ONLY. PROPOSED REZONE OF CAMPBELL COUNTY PARCELS TO R-MF - RESIDENTIAL, MULTI-FAMILY PROPOSED PROPERTY LINE VACATION FOR COMBINATION INTO SINGLE PARCEL APPROXIMATE LOCATION OF EXISTING 24" WATERLINE TAP CONNECTION TO EXISTING 24" CITY OF LYNCHBURG WATERLINE EXISTING 10" WATERLINE TO BE ABANDONED BY THE CITY OF LYNCHBURG 24' 30' FRONT SETBACK PROPOSED STORMWATER MANAGEMENT FACILITY PROPOSED PUBLIC SANITARY SEWER MANHOLE EXISTING DRIVEWAY TO BE CLOSED PROPOSED 6"x2" MASTER METER AT CITY/COUNTY LINE (CoL/CCUSA COORDINATION FOR WATER SERVICE) PROPOSED RPZ IN ABOVE GROUND HOT BOX PROPOSED PRIVATE FIRE HYRANT PROPOSED PROPERTY LINE VACATION FOR COMBINATION INTO SINGLE PARCEL 20' PUBLIC UTILITY EASEMENT (CoL) 22' 22' 22' BUD DRIVE TO BE UPGRADEDTO SUPPORT FIRE APPARATUS 32'TYP 40' TYP BUD DRIVE BUD DRIVE TO BE UPGRADEDTO SUPPORT FIRE APPARATUS SCALE: ASD JOB #: 1" = 30' 2022-664 FILE #: 2022-664 CONCEPT REVISION/DATE DATE: CITY OF LYNCHBURG, VIRGINIA CAMPBELL COUNTY, VIRGINIA CONCEPTUAL SITE PLAN FOR KARL MILLER DECEMBER 19, 2023 CONCEPTUAL SITE PLAN C-2 04/25/2023 PRELIMINARY SIDEWALK CALCULATIONS (PER ARTICLE VI; SEC. 35.2-67.1): FRONTAGE: LEESVILLE RD = 70.28 LF X 1 = 70.28 LF OF SIDEWALK PROPOSED 70.28 LF OF SIDEWALK ALONG LEESVILLE RD MISS UTILITY TICKET NUMBER: SITE INFORMATION: CURRENT OWNER: ABUNDANT LIFE ESTATES LLC 7700 TIMBERLAKE ROAD LYNCHBURG, VA 24502 PROPERTY ADDRESS(ES): CITY OF LYNCHBURG: CAMPBELL COUNTY: 725 LEESVILLE ROAD 73 BUD DRIVE 717 LEESVILLE ROAD (2 LANDLOCKED PARCELS WITH NO ADDRESSES - SEE PARCEL IDS) PARCEL ID: CITY OF LYNCHBURG: CAMPBELL COUNTY: 26202018 13C-4-2 26202017 13C-4-4 13C-5-C PARCEL ACREAGE: 0.305 AC (26202018) 0.111 AC (26202017) 1.781 AC (13C-4-2) 0.160 AC (13C-4-4) - APPROXIMATE 0.298 AC (13C-5-C) 2.655 AC TOTAL EXISTING ZONING DISTRICT: CITY OF LYNCHBURG = R-1 - LOW DENSITY RESIDENTIAL DISTRICT CAMPBELL COUNTY = B-GC - BUSINESS, GENERAL COMMERCIAL PROPOSED ZONING DISTRICT: CITY OF LYNCHBURG = R-4 - HIGH DENSITY RESIDENTIAL CAMPBELL COUNTY = R-MF - RESIDENTIAL MULTIFAMILY EXISTING USE: SINGLE FAMILY RESIDENTIAL PROPOSED USE: TWO-UNIT RESIDENTIAL COMPLEX SETBACKS: CITY OF LYNCHBURG: CAMPBELL COUNTY: FRONT: 30' FRONT: 20' SIDE: 5' SIDE: 10' REAR: 25' REAR: 20' MAXIMUM BUILDING COVERAGE: 40% OF THE SUBJECT PROPERTY (CAMPBELL COUNTY) 2.239 TOTAL ACRES IN CAMPBELL COUNTY 2.239 x 40% = 0.896 ACRES 0.39 ACRES PROPOSED LEGEND Know what's below. Call before you dig. R 03 0 6 0 9 0 GRAPHIC SCALE: 1" = 30' TBD SCREENING/BUFFER LANDSCAPE TABULATION SYMBOL TYPE BOTANICAL NAME COMMON NAME SIZE CANOPY SF 113 40 X 113 = 4,520 SF QUANTITY 4079-113 SF AT 20 YR SPREAD QUANTITY & CANOPY TOTAL SF ILLEX x 'NELLIE R. STEVENS' NELLIE STEVENS HOLLY EVERGREEN SHRUB 36 41 X 36 = 1,476 SF4148" - 72" SPREAD RHODODENDRON 'NORTHERN HI-LIGHTS' NORTHERN HI-LIGHTS AZALEA EVERGREEN TREE BUILDING LEGEND BUILDING TYPE DUPLEX (1340 SF FOOTPRINT) # OF UNITS # OF BUILDINGS 13 26 Page 45 of 325 PROPERTY LINE SETBACK PROPOSED BUILDING CONCRETE FIRETRUCK TURNAROUND TEMPLATE CITY OF LYNCHBURG CAMPBELL COUNTY LEESVILLE ROAD 10' SIDE SETBACK 20' REAR SETBACK DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX 24' FIRE ACCESS ROAD W/ SURFACE THAT SUPPORTS A FIRE APPARATUS WEIGHING 75,000 LBS & 25' FIRE ACCESS GATE W/ KNOX PADLOCK OR EQUIVALENT. FOR EMERGENCY ACCESS ONLY. 30' FRONT SETBACK PROPOSED PRIVATE FIRE HYRANT BUD DRIVE TO BE UPGRADEDTO SUPPORT FIRE APPARATUS 32'TYP 40' TYP BUD DRIVE BUD DRIVE TO BE UPGRADEDTO SUPPORT FIRE APPARATUS SCALE: ASD JOB #: 1" = 30' 2022-664 FILE #: 2022-664 CONCEPT REVISION/DATE DATE: CITY OF LYNCHBURG, VIRGINIA CAMPBELL COUNTY, VIRGINIA CONCEPTUAL SITE PLAN FOR KARL MILLER DECEMBER 19, 2023 FIRE TRUCK TURNAROUND TEMPLATE C-3 04/25/2023 PRELIMINARY MISS UTILITY TICKET NUMBER: LEGEND Know what's below. Call before you dig. R 03 0 6 0 9 0 GRAPHIC SCALE: 1" = 30' TBD DEAD-END FIRE APPARATUS ACCESS ROAD TURNAROUND - ACCEPTABLE ALTERNATIVE TO 120-FOOT HAMMERHEAD 120' 20' 20' 20' 60' 28' R 28' R 70' Page 46 of 325 PROPERTY LINE SETBACK PROPOSED BUILDING CONCRETE CITY OF LYNCHBURG CAMPBELL COUNTY LEESVILLE ROAD 10' SIDE SETBACK 20' REAR SETBACK DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX DUPLEX 24' FIRE ACCESS ROAD W/ SURFACE THAT SUPPORTS A FIRE APPARATUS WEIGHING 75,000 LBS & 25' FIRE ACCESS GATE W/ KNOX PADLOCK OR EQUIVALENT. FOR EMERGENCY ACCESS ONLY. 30' FRONT SETBACK PROPOSED PRIVATE FIRE HYRANT BUD DRIVE TO BE UPGRADEDTO SUPPORT FIRE APPARATUS 32'TYP 40' TYP BUD DRIVE BUD DRIVE TO BE UPGRADEDTO SUPPORT FIRE APPARATUS 530' LINE OF SIGHTSIGHT DISTANCE LEFT 565' LINE OF SIGHT SIGHT DISTANCE RIGHT SCALE: ASD JOB #: 1" = 50' 2022-664 FILE #: 2022-664 CONCEPT REVISION/DATE DATE: CITY OF LYNCHBURG, VIRGINIA CAMPBELL COUNTY, VIRGINIA CONCEPTUAL SITE PLAN FOR KARL MILLER DECEMBER 19, 2023 INTERSECTION SIGHT DISTANCE C-4 04/25/2023 PRELIMINARY MISS UTILITY TICKET NUMBER: LEGEND Know what's below. Call before you dig. R 0 50 100 150 GRAPHIC SCALE: 1" = 50' TBD Page 47 of 325 Page 48 of 325 Page 49 of 325 1 Holt, Loryn From: Finney, Alicia Sent: Monday, April 22, 2024 7:14 AM To: Holt, Loryn Subject: Fwd: Public Comment April 9, 2024 For public comment tomorrow. Thank you!      From: cmosley5172@aol.com <cmosley5172@aol.com>  Sent: Friday, April 19, 2024 3:48:26 PM  To: Finney, Alicia <Alicia.Finney@lynchburgva.gov>  Subject: Re: Public Comment April 9, 2024      CAUTION: External Sender    People that have inherited property forcing to sell demolished or $500!month dureluc program property taxes with only  30 day time period. What is the city doing with all this money from these properties. Thank you!    Sent from the all new AOL app for iOS    On Friday, April 19, 2024, 11:59 AM, Finney, Alicia <Alicia.Finney@lynchburgva.gov> wrote:  Hi Ms. Mosley, we’re happy to help get you scheduled. Our meeting is on April 23, 2024, not April 24,  2024. Can you please help us by providing a brief topic of discussion that would best summarize all that  you’re hoping to talk about? A few words to one sentence should be enough. Thank you!          From: cmosley5172@aol.com <cmosley5172@aol.com>   Sent: Thursday, April 18, 2024 7:37 PM  Page 50 of 325 2 To: Finney, Alicia <Alicia.Finney@lynchburgva.gov>  Subject: Re: Public Comment April 9, 2024     CAUTION: External Sender     I  will like to put on City Council how they are taking over peoples property that was inherited down or  these ederly that doesn’t have funds if living with their children. City always complainining they don’t  have enough for this schools or certain other projects . I would to put n Agenda for public comment  April 24,2024. I be looking forward to hearing back from you.  Sent from the all new AOL app for iOS     On Tuesday, April 9, 2024, 1:25 PM, cmosley5172@aol.com <cmosley5172@aol.com> wrote:  I apologize for the late notice . My grandson sick and we been up since 5:30am. I would  like to know if you can reschedule me for the next agenda meeting please.  Sent from the all new AOL app for iOS     On Thursday, April 4, 2024, 3:45 PM, cmosley5172@aol.com  <cmosley5172@aol.com> wrote:  My topic!  Sent from the all new AOL app for iOS     On Thursday, April 4, 2024, 3:44 PM, Finney, Alicia  <Alicia.Finney@lynchburgva.gov> wrote:  Hi Ms. Mosley,     I am in receipt of your Public Comment request for April  9th; you noted that you were speaking on behalf of the  group “Parental Alienation Awareness”. Is this a  functioning group or your topic? Thank you for  confirming!           Page 51 of 325 City Council Agenda Item VI.6. Action AGENDA ITEM SUMMARY MEETING DATE PRESENTED BY April 23, 2024 Donna Witt, Chief Financial Officer AGENDA ITEM # VI.6 Consideration of introducing Resolution #R-24-___ amending Lynchburg City Schools Major Classification Funding for FY 2024 and transferring $1,671,820 from Contingency Reserves to Instruction. RECOMMENDATION Consideration of adopting a resolution to amend FY 2024 Schools Operating Budget by major classification. SUMMARY In a letter dated March 19, 2024 Lynchburg City Schools Superintendent reported, "On March 12, 2024, the Lynchburg City School Board voted to request that the City Council transfer the remaining $1,671,820 in the FY 2024 LCS Contingency Reserve to the Instruction category. This request is crucial for addressing several pressing financial challenges faced by our school division." If approved, the FY 2024 Adopted Schools Operating Budget would be amended by transferring $1,671,820 from Contingency Reserves to Instruction. This request does not change the total operating revenues appropriated by City Council but rather moves $1,671,820 from Contingency Reserves to Instruction. PRIOR ACTION(S) May 23, 2023: City Council, FY 2024 Schools Operating Budget adopted by major classification June 27, 2023: City Council, FY 2024 Schools Operating Budget amended by major classification September 12, 2023: City Council, FY 2024 Schools Operating Budget amended by major classification February 13, 2024: City Council, FY 2024 Schools Operating Budget amended by major classification April 9, 2024: City Council Worksession - Business Item Briefing, FY 2024 Schools Operating Budget request to amend by major classification FISCAL IMPACT This request does not change the total operating revenues appropriated by City Council but rather moves $1,671,820 from Contingency Reserves to Instruction. Page 52 of 325 CONTACT(S) Gregory Patrick, Deputy City Manager Donna Witt, Chief Financial Officer ATTACHMENT(S) 1. Contingency Reserve Request City Manager 03192024 2. Resolution to Amend FY 2024 Operating Budget - Schools 042324 REVIEWED BY Date: April 16, 2024 Donna Witt, Chief Financial Officer Date: April 18, 2024 Gregory Patrick, Deputy City Manager Date: April 18, 2024 Alicia Finney, Clerk of Council Page 53 of 325 Office of the Superintendent 915 Court Street P.O. Box 2497 Lynchburg, VA 24505 March 19, 2024 Wynter Benda, City Manager 900 Church Street Lynchburg, Virginia 24504 Dear Mr. Benda: On March 12, 2024, the Lynchburg City School Board voted to request that the City Council transfer the remaining $1,671,820 in the FY 2024 LCS Contingency Reserve to the Instruction category. This request is crucial for addressing several pressing financial challenges faced by our school division. Despite receiving additional FY 2024 revenue of $3.7 million from the state, it is imperative to note that this revenue is restricted exclusively to support the Governor’s All In program. The ALL In spending plans which can be found on the VDOE website, require that revenue be allocated and s pent as follows: 70% for tutoring, 20% for implementing the Virginia Literacy Act, and 10% for addressing chronic absenteeism. As such, this revenue cannot be utilized to meet our other operational needs that are expressed in this letter. The decision to seek a transfer of the remaining c ontingency funds stems from several mitigating factors outlined below: 1. The Governor’s recent budget amendment (Jan 2024) to the FY 2024 LCS sales tax revenue resulted in a reduction of $1,214,657. 2. The updated VDOE calc tool (Jan 2024) also indicates a reduction in the Grocery Tax Hold Harmless Funds by $81,565. 3. Given the rise of utilities costs, LCS estimates the FY 2024 expenditures associated with electric, water, and gas to be approximately $2.0 million over the current FY 2024 operating budget allocation. 4. Given the costs of monthly health insurance claims, LCS estimates that FY 2024 claims will exceed employee contributions by $1.5 million in the current year, despite an increase of employee contributions beginning in January 2024. To address the deficit caused by reduction in S tate revenue and the projected increases in healthcare and utilities during the current school year, the school division has canceled all purchase orders not directly associated with immediate and direct student learning or experiences, frozen all non -grant funded hiring and travel, implemented an overtime reduction plan, and instituted an electricity consumption reduction Page 54 of 325 Office of the Superintendent 915 Court Street P.O. Box 2497 Lynchburg, VA 24505 challenge for schools and facilities. We have also redirected some ESSER/CARES funds that were identified for important, but not as immediately critical needs. LCS believes that the successful completion of the current fiscal year relies on our combined efforts, encompassing both expenditure reductions by LCS and the transfer of the remaining contingency revenue by the City Council. Thank you for you r time, consideration, and support in this matter . Should you have any questions or require additional information, please do not hesitate to contact me. Sincerely, Crystal M. Edwards, EdD Superintendent cc: Members, Lynchburg City School Board Amy Pugh, Deputy Superintendent of Instruction and Programs Reid Wodicka, Deputy Superintendent of Operations & Strategic Planning Sonia Jammes, Chief Financial Officer Page 55 of 325 RESOLUTION: #R-24 -______________ BE IT RESOLVED that by majority vote of the Lynchburg City Council, the FY 2024 Adopted Schools Operating Budget is hereby amended by transferring $1,671,820 from Contingency Reserves to Instruction with the FY 2024 Adopted Schools Operating Budget, beginning July 1, 2023, through June 30, 2024, pursuant to Sections 22.1-94 and 22.1-115 of the Code of Virginia, 1950, as amended, being amended, readopted, and appropriated by major classification as follows: Introduced: Adopted: Certified: Clerk of Council SCHOOLS INCOME SCHOOLS EXPENDITURES BY MAJOR CLASSIFICATION State $68,137,129 Instruction $77,563,338 Federal 925,000 Administration, Attendance and Health 7,723,076 Local - Operating 39,375,355 Pupil Transportation 6,599,342 Miscellaneous 888,000 Operation and Maintenance 12,474,168 School Food Services and Other Noninstructional Operations 42,145 Facilities 25,210 Debt and Fund Transfers 0 Technology 4,898,205 Contingency Reserves 0 Total $109,325,484 Total $109,325,484 Page 56 of 325 City Council Agenda Item VI.7. Action AGENDA ITEM SUMMARY MEETING DATE PRESENTED BY April 23, 2024 K. Todd Swisher, Clerk of the Circuit Court AGENDA ITEM # VI.7 Consideration of introducing Resolution #R-24-___ amending the FY 2024 City/Federal/State Aid fund budget and appropriating $27,326 from the Library of Virginia to preserve several Circuit Court Records. RECOMMENDATION Adopt a resolution to amend the FY 2024 City/Federal/State Aid Fund budget and appropriate $27,326 with resources from a Library of Virginia Circuit Court Records Preservation Grant to preserve Deed Book 45 T-T 1891; Deed Book 46 U-U 1891-1892; Deed Book 47 V-V 1892-1893; Deed Book 48 W-W 1893; Deed Book 57 1898-1899; and Marriage Licenses 1864-1866. SUMMARY The Library of Virginia allows Circuit Court Clerks’ Offices to submit applications for grant funding. Staff submitted a grant application to The Library of Virginia to preserve records held at the Circuit Court Clerk’s Office. The approved grant funding of $27,326 will allow Deed Book 45 T-T 1891; Deed Book 46 U-U 1891-1892; Deed Book 47 V-V 1892-1893; Deed Book 48 W-W 1893; Deed Book 57 1898-1899; and Marriage Licenses 1864-1866 to be reformatted and preserved. The grant covers 100% of preservation work; no local match is required for this grant. PRIOR ACTION(S) April 23, 2024: Finance Committee FISCAL IMPACT None – no local match is required. CONTACT(S) K. Todd Swisher - Clerk of the Circuit Court ATTACHMENT(S) 1. RESOLUTION - CCRP Library of Virginia Conservation Grant 04232024 2. 2024 Library of VA Grant Approval - Lynchburg Page 57 of 325 REVIEWED BY Date: April 18, 2024 Mercedes Braun, Assistant to the City Manager Date: April 18, 2024 Wynter Benda, City Manager Date: April 18, 2024 Alicia Finney, Clerk of Council Page 58 of 325 RESOLUTION: BE IT RESOLVED that the FY 2024 City/Federal/State Aid Fund budget is amended and $27,326 is appropriated with resources from a Library of Virginia Circuit Court Records Preservation Grant to preserve Deed Book 45 T-T 1891; Deed Book 46 U-U 1891-1892; Deed Book 47 V-V 1892-1893; Deed Book 48 W-W 1893; Deed Book 57 1898-1899; and Marriage Licenses 1864-1866. Introduced: Adopted: Certified: Clerk of Council Page 59 of 325 Page 60 of 325 Page 61 of 325 Page 62 of 325 Page 63 of 325 Page 64 of 325 City Council Agenda Item VI.8. Action AGENDA ITEM SUMMARY MEETING DATE PRESENTED BY April 23, 2024 Donna Witt, Chief Financial Officer AGENDA ITEM # VI.8 Consideration of adopting Resolution #R-24-___ approving the newly amended “Guidelines for Implementation of the Public-Private Transportation Act of 1995 and Public-Private Education Facilities & Infrastructure Act of 2002” for the City of Lynchburg. RECOMMENDATION Adopt a Resolution which approves newly amended “Guidelines for Implementation of the Public- Private Transportation Act of 1995 and Public-Private Education Facilities & Infrastructure Act of 2002” for the City. SUMMARY City Council adopted guidelines for implementation of both the Public-Private Transportation Act (PPTA) and Public-Private Education Facilities & Infrastructure Act (PPEA) in 2004 and then amended both in 2006. Changes to the PPTA legislation over the years have resulted in procedural differences from the PPEA. An update to the guidelines is needed. PRIOR ACTION(S) January 27, 2004: Adopted January 10, 2006: Amended February 27, 2024: Council Worksession - Business Item Briefing March 12, 2024: Item tabled for Technical Corrections FISCAL IMPACT N/A CONTACT(S) Donna Witt, Chief Financial Officer Stephanie Suter ATTACHMENT(S) 1. Proposed Resolution - PPEA - PPTA Amended Guidelines (2024) 2. PPEA - PPTA Amended Guidelines (2024) 3. PPEA - PPTA Guidelines (2004 & 2006) Page 65 of 325 REVIEWED BY Date: April 15, 2024 Donna Witt, Chief Financial Officer Date: April 16, 2024 Matthew Freedman, City Attorney Date: April 18, 2024 Gregory Patrick, Deputy City Manager Date: April 18, 2024 Alicia Finney, Clerk of Council Page 66 of 325 RESOLUTION: #R-24-____ BE IT RESOLVED BY THE COUNCIL OF THE CITY OF LYNCHBURG: 1. That the City of Lynchburg’s implementation procedures and guidelines for the Public-Private Transportation Act of 1995 (PPTA), as amended, and the Public-Private Education Facilities and Infrastructure Act of 2002 (PPEA), as amended, also known as the Lynchburg PPTA/PPEA Procedures, are hereby amended, approved, and reenacted as provided in that certain document entitled “City of Lynchburg, Virginia, Guidelines for Implementation of the Public-Private Transportation Act of 1995 and Public-Private Education Facilities & Infrastructure Act of 2002”, as of the date of April 23, 2024, which is expressly incorporated herein by reference. 2. That this Resolution shall be effective upon its adoption. Adopted: Certified: _____________________________ Clerk of Council Page 67 of 325 Page 68 of 325 Page 69 of 325 Page 70 of 325 Page 71 of 325 Page 72 of 325 Page 73 of 325 Page 74 of 325 Page 75 of 325 Page 76 of 325 Page 77 of 325 Page 78 of 325 Page 79 of 325 Page 80 of 325 Page 81 of 325 Page 82 of 325 Page 83 of 325 Page 84 of 325 Page 85 of 325 Page 86 of 325 Page 87 of 325 Page 88 of 325 Page 89 of 325 Page 90 of 325 Page 91 of 325 Page 92 of 325 Page 93 of 325 Page 94 of 325 City of Lynchburg, Virginia Implementation Procedures and Guidelines for the Public-Private Transportation Act of 1995 and the Public-Private Education Facilities and Infrastructure Act of 2002, as amended Adopted January 27, 2004 Amended January 10, 2006 Page 95 of 325 2 TABLE OF CONTENTS CITY OF LYNCHBURG PPTA/PPEA IMPLEMENTATION PROCEDURES AND GUIDELINES I. INTRODUC TION............................................................................................... 4 A. Scope and App licability................................................................................ 4 B. Point of Contact for PPTA/PPEA Information and Submission of Proposals ...................................................................... 5 C. City Review Board ....................................................................................... 5 D. Reservation of Rights .................................................................................. 6 E. Timeline for Proposal Re view and Consideration ........................................ 7 II. GENERAL PROV ISIONS ................................................................................. 7 A. Proposal Subm ission ................................................................................... 7 B. General Administ rative Issues ..................................................................... 10 C. General Format for Submissi on of Conceptual Proposal............................. 10 D. General Format for Submissi on of Detailed Proposal.................................. 11 E. Proposal Revi ew Fee................................................................................... 12 F. Virginia Freedom of Information Act ............................................................ 13 G. Affected Local Juri sdiction Review .............................................................. 14 H. Applicability of Other Law ............................................................................ 14 I. Adoption of Certain Portions of the Virginia Public Procurement Act and Use of competitive Negotiation and Competitive Sealed Bidding Procedures....................................................................................................15 III. PROPOSAL EVALUAT ION AND SELECTION................................................ 16 A. Decision to Accept an Unsolicited Proposal................................................. 16 B. Initial Review by the City.............................................................................. 16 C. Written Determination of Qualification.......................................................... 17 D. Conclusion of an Agre ement on the Protection of Confidential Information............................................................................... 17 E. Publication for Co mpeting Proposals........................................................... 17 F. Receipt of Com peting Proposals ................................................................. 17 G. Determination and Agreement on Confidential Material for Competing Proposals ............................................................................. 18 H. Selection for Submission of Detailed Proposals .......................................... 18 I. Receipt and Review of Detailed Proposals.................................................. 18 J. Selection of Proposal(s) for Negot iation of Comprehensive Agreement ...... 19 K. Negotiation and Approval of Comprehensive Agreement ............................ 19 IV. FORMAT FOR CONC EPTUAL PROPOSALS ................................................. 19 A. Descrip tion................................................................................................... 19 B. Tab 1: Qualificat ion and Experience ........................................................... 20 C. Tab 2: Project Characteristics..................................................................... 21 D. Tab 3: Proj ect Financing............................................................................. 22 E. Tab 4: Public Support, Proj ect Benefit and Compatibility............................ 22 Page 96 of 325 3 V. FORMAT FOR DETA ILED PROPOSALS........................................................ 23 A. Description and Re quired Information ......................................................... 23 VI. PROPOSAL EVALUATION.............................................................................. 24 A. Manner of Evaluat ion and Use of Outside Professionals............................. 24 B. Evaluation and Sele ction Criteria................................................................. 24 VII. COMPREHENSIVE AGREEMENTS AND INTERIM AGREEMENTS.............. 24 A. Descripti on and Terms................................................................................. 24 B. Interim Ag reements ...................................................................................... 27 VIII. DISPUTES, CLAIMS AND OT HER MATTERS ARISING UNDER OR RELATING TO ANY COMPREHENSIVE AGREEMENT OR INTERIM AGREEMENT ................................................................................................... 27 IX. PROTESTS OF PPTA/PPE A PROCUREMENTS ............................................ 29 X. PARTICIPATION OF SMALL AND MINORITY-OWNED BUSINESS.............. 30 XI. PROPOSERS' AGREEMENT TO TERMS AND CONDITIONS OF THIS POLICY............................................................................................................. 30 Appendix A: The Public-Private Transportation Act of 1995 ............................... 31 Appendix B: The Public-Privat e Education Facilities and Infrastructure Act of 2002, as amended........................................... 44 Appendix C: Projected Procurement Timeline for PPTA/PPEA Procurement Initiated By Unso licited Proposal..................................................... 57 Appendix D: Projected Procurement Timeline for PPTA/PPEA Procurement Solicited By Request fo r Proposals (“RFP”) ................................... 58 Appendix E: Potential Proposal Eval uation and Selection Criteria..................... 59 Appendix F: Proposers' Certification .................................................................... 64 Page 97 of 325 4 CITY OF LYNCHBURG PPTA / PPEA IMPLEMENTATION PROCEDURES AND GUIDELINES I. INTRODUCTION. A. Scope and Applicability. This document presents the implementation procedures and guidelines (the “procedures") developed by the City of Lynchburg ("the City") to guide the selection of projects under the purview of the City as authorized by the Virginia Public- Private Transportation Act of 1995 (the "PPTA") (Virginia Code §56-556 et seq.), and the Virginia Public-Private Education Facilities and Infrastructure Act of 2002, as amended (the "PPEA") (Virginia Code §56-575.1 et seq.). The PPTA and PPEA are collectively referred to herein as "the Acts". Copies of the PPTA and PPEA are included as Appendices A and B, respectively, to these procedures. The City is a political subdivision of the Commonwealth of Virginia with the authority to acquire, design, construct, improve, renovate, expand, equip, maintain, operate, implement and install a wide range of projects for public use, and therefore is a "Responsible Public Entity" as that term is used in both the PPTA and PPEA. As discussed below, the PPTA authorizes public-private partnerships to develop "qualifying transportation facilities," and the PPEA authorizes such partnerships to develop "Qualifying Projects.” The term "qualifying transportation facility" is defined in the PPTA as follows: "Qualifying transportation facility" means one or more transportation facilities acquired, constructed, improved, maintained and/or operated by a private entity pursuant to this chapter. The PPTA further defines a "transportation facility" as follows: "Transportation facility" means any road, bridge, tunnel, overpass, ferry, airport, mass transit facility, vehicle parking facility, port facility or similar commercial facility used for the transportation of persons or goods, together with any other property that is needed to operate the transportation facility. The term "Qualifying Project" under the PPEA is defined as follows: "Qualifying project" means (i) any education facility, including, but not limited to a school building, any functionally related and subordinate facility and land to a school building (including any stadium or other facility primarily used for school events), and any depreciable property provided for use in a school facility that is operated as part of the public school system or as an institution of higher education; (ii) any building or facility that meets a public purpose and is developed or operated by or for any public entity; (iii) any improvements, together with equipment, necessary to enhance public safety and security of buildings to be principally used by a public entity; (iv) utility and telecommunications and Page 98 of 325 5 other communications infrastructure; (v) a recreational facility; or (vi) technology infrastructure, including, but not limited to, telecommunications, automated data processing, word processing and management information systems, and related information, equipment, goods and services. The terms "Proposal," "Qualifying Project" or "Project" will be used herein to apply to authorized projects under either the PPTA or PPEA, unless otherwise stated. These procedures apply to proposals submitted under the authority of either the PPTA or PPEA, or both. The City reserves the right to consider a proposal under either or both Acts. While the Acts are fundamentally similar, prospective proposers are cautioned to review them closely as there are significant differences between the PPEA and PPTA. The Acts allow both solicited and unsolicited proposals. The major steps involved in evaluating, selecting, and implementing the projects are similar for both solicited and unsolicited proposals. It is anticipated that the private sector will identify prospective projects, although the City may, from time to time, solicit proposals generally or for specific projects. Private entities may also propose innovative financing methods, including the imposition of user fees, lease payments, or other service payments under the provisions of the Acts. As explained more fully below, these procedures adopt a "two phase" proposal process for both solicited and unsolicited proposals. The first phase involves the submission of a "Conceptual Proposal" of limited scope, and the second phase requires the submission of a "Detailed Proposal" by one or more proposers selected by the City after review of the Conceptual Proposal. B. Point of Contact for PPTA/PP EA Information and Submission of Proposals. The City Manager has designated the City Purchasing Agent to serve as the point of contact for the implementation of these procedures, to receive proposals submitted under the PPTA/PPEA and to respond to inquiries regarding the PPTA/PPEA or these procedures. C. City Review Board. All proposals for a Qualifying Project will be reviewed and selections made by a City Review Board (CRB), which shall consist of: The City Manager The Director of Financial Services The City Attorney The Purchasing Agent Other members as the City Manager may determine The CRB may also employ outside advis ors and consultants to assist in its review of proposals. Page 99 of 325 6 D. Reservation of Rights. In connection with any proposal or Qualifying Project, the City shall have all rights available to it by law in administering these procedures, including without limitation, the right in its sole and unfettered discretion to: 1. Reject any or all proposal s at any time, for any reason, solely within the discretion of the City. Proposers shall have no recourse against the City for such rejection. Proposers will be notified in writ ing of such rejection in accordance with these procedures. 2. Terminate evaluation of any and all proposals at any time. 3. Suspend, discontinue and/ or terminate Comprehensive Agreement negotiations. 4. Negotiate with a proposer without being bound by any provision in its proposal. 5. Request or obtain additional information about any proposal. 6. Issue addenda to and/or cancel any request for proposals ("RFP") or invitation for bids ("IFB"). 7. Revise, supplement or withdr aw all or any part of these procedures at any time. 8. Modify any standard fee schedul e as stated herein for a specific proposal or for all future proposals. 9. Decline to return any and all fees required to be paid by proposers hereunder, except for initial fees paid by proposers with an unsolicited conceptual proposal where the City declines to accept the proposal for consideration. 10. Request revisions to Conceptual or Detailed Proposals. 11. Treat any proposal which may have certain characteristics in common yet differ in meaningful ways from a previously received proposal as either a competing proposal or a noncompeting unsolicited proposal and proceed accordingly. 12. Submit a proposal for review by outside consultants or advisors selected by the City without notice to the proposer. Such consultants or advisors shall be advised of and contractually required to agree to maintain the confidentiality of information that has been designated as confidential Page 100 of 325 7 pursuant to an agreement between the City and the proposer, and to refer all requests for such information to the City. 13. Modify the stated timeline fo r consideration, review or negotiation of proposals when deemed necessary by the City in its sole discretion. Written notice will be provided to any affected proposers when such departures from a stated timeline are deemed significant. Under no circumstances shall the City be liable for, or reimburse, the costs incurred by proposers, whether or not selected for negotiations, in developing proposals or in negotiating agreements. Any and all information the City makes available to proposers shall be as a convenience to the proposer and without representation or warranty of any kind. Proposers may not rely upon any oral responses to inquiries. If a proposer has a question regarding application of these procedures, the proposer must submit the question in writing to the City Purchasing Agent and the City will respond in writing as it determines appropriate. E. Timeline for Proposal Re view and Consideration. For solicited proposals, the City will include an anticipated timeline for submission and review of proposals. For unsolicited proposals, the City will attempt to review proposals in a timely manner and will discuss with the proposer an anticipated timeline for the full process should the City decide to proceed. Every attempt will be made to move through the process as expeditiously as possible. Normal expected timelines for selectin g proposals and negotiating an interim agreement or comprehensive agreement ar e set out at Appendices C and D hereto. Appendix C sets out the norma l expected timeline for a procurement initiated by an unsolicited proposal. Appendix D sets out the normal expected timeline for a procurement solicited by the City. For projects deemed a priority by the City , the portion of timelines related to selection, review, and documentation may be accelerated. The City should generally adhere to thes e timelines, but the City Manager may deviate from them when it is in the City’s interests to do so. II. GENERAL PROVISIONS . A. Proposal Submission. 1. Solicited Proposals From time to time, the City may issue RFPs or IFBs inviting proposals from private entities to acquire, design, construct, improve, renovate, expand, equip, Page 101 of 325 8 maintain, operate, implement and/or install Qualifying Projects. The RFP or IFB will outline minimum qualifications and project selection criteria, specify information and documents which must accompany the proposals, the factors which will be used in evaluating the proposals, and contain or incorporate by reference other applicable terms and conditions, including any unique capabilities or qualifications which will be required of private entities submitting proposals ("proposers"). Proposers are encouraged to be as innovative as possible in their proposals. Pre-proposal conferences may be held, as deemed appropriate, and notice of such will be provided in the RFP or IFB. Proposers will be instructed as to the format in which to submit proposals and what minimum information, materials, and fees must be submitted in order for the proposal to be considered complete. Public notice of the solicitation of proposals under the Acts will be posted at least 60 days prior to the date set for receipt of proposals by posting in a public area of City Hall normally used for the posting of City public notices, by posting on the Purchasing Division website, www.lynchburgva.gov/procurement, and other electronic posting sites, and by publication in one or more newspapers or other publications of general circulation within and/or outside the City of Lynchburg, including the Virginia Business Opportunities publication, so as to provide reasonable notice to the maximum number of proposers that can be reasonably anticipated to submit proposals. In addition, proposals may be solicited directly from potential proposers. 2. Unsolicited Proposals The Acts permit responsible public entities to receive, evaluate and select for negotiations unsolicited proposals from private entities to acquire, design, construct, improve, renovate, expand, equip, maintain, operate, implement and/or install Qualifying Projects. The City will receive such unsolicited proposals at any time pursuant to these procedures. The City will evaluate unsolicited proposals whenever received so long as the proposals meet the requirements of the Acts and these procedures and are determined to be in the City's best interest. Once a proposal is received and deemed by the City to meet all legal and policy requirements for initial review, as set out in relevant provisions of the Acts, and the proposer and the City have reached an agreement on the protection of confidential information as permitted under Virginia Code Section 2.2-3705.A.56, the City will publish a notice accepting such proposal for initial review and inviting other private entities to submit competing proposals, as follows: i. Post a notice for 45 calendar days, or such additional time as determined by the City, in a public area of City Hall normally designated for such public notices. ii. Publish the same notice in one or more newspapers or periodicals of general circulation, including the Virginia Business Opportunities publication, as appropriate to notify Page 102 of 325 9 potential proposers that might be interested. The notice will state that the City has received an unsolicited proposal under the Acts, that it intends to evaluate the proposal, that it may negotiate a Comprehensive Agreement with the proposer based on the proposal, and that it will accept for simultaneous consideration any competing and compliant proposals the City receives in accordance with these procedures within 45 calendar days, or more, of the initial posting of the notice. The notice will summarize the proposed Qualifying Project, including its location, and will generally contain a deadline, not less than 45 calendar days from posting of the notice, for receipt of competing proposals. iii. Post the notice on the City' s Purchasing Division website, www.lynchburgva.gov/procurement. The deadline for the City's receipt of any such competing proposals in writing will generally be 3:00 p.m. local, on the designated day after the City's initial publication of the notice unless otherwise stated by the City in the notice of acceptance and invitation for competing proposals. Only those competing, compliant proposals submitted and actually received in writing by the City at the location specified in the invitation for competing proposals by such deadline will be considered unless the City terminates consideration of, or negotiation on the original unsolicited proposal. The City may, in it sole discretion, ex tend the 45 day peri od, but otherwise will not accept competing proposals receiv ed after the designated period. The City recognizes that it may receive proposals, which have certain characteristics in common yet differ in meaningful ways. In such cases, the City reserves the right, in its sole discretion, to treat such a proposal or any portion of such proposal received after the original proposal, as either a competi ng proposal or a non- competing unsolicited proposal, and to proceed accordingly under these procedures. Because of the consequences to a proposer for failing to submit within the designated period a proposal which the City could later deem a competing proposal, prospective proposers are strongly urged to monitor the City notices of proposals received, and to be prepared to submit within such designated period if they perceive that a proposal they are considering or are preparing bears certain similarities to, or has characteristics in common with, a proposal which is the subject of a notice. In the event a proposer is unsure whether its planned proposal will be sufficiently similar to the proposal which was the subject of a notice to be deemed a competing proposal, such proposer may submit to the City a written request for a preliminary determination of whether its project would be deemed a competing proposal in whole or in part. The City will endeavor, no later than fourteen days thereafter, to respond to such request with a preliminary determination as to whether or not the proposal would be a competing proposal or that it has received insufficient information to make a determination. In the event the City Page 103 of 325 10 elects to treat a proposal, or part of a proposal, received within the designated period as a non-competing proposal, the City will follow the above notice procedure to permit competing proposals to be submitted, including from the proposer whose proposal triggered the original notice. If state or federal funds ar e anticipated in any proposal , the City may also notify the appropriate state or federal agencies. B. General Administrative Issues. Proposers shall deliver one (1) original, nine (9) copies, and one (1) electronic copy of their Conceptual Proposal and, if requested, Detailed Proposal to the City at the following address: Purchasing Agent City of Lynchburg Purchasing Division Third Floor Hall 900 Church Street Lynchburg, Va. 24504 Proposals are to be sealed in mailing envelopes or packages bearing the proposer's name, address and the words "PPTA / PPEA Project Proposal" clearly written on the outside. The cover page must include the title of the proposal, the name and address of the proposing entity, the person authorized to act on behalf of the proposer and his or her telephone and facsimile numbers, and email address. Also, pursuant to the Acts, copies of proposals must be provided directly to the governing body of each local jurisdiction (city, county, town etc.), if any, affected by a proposed project. A list of all local jurisdictions being provided a copy of the proposal must accompany the Conceptual Proposal with name and address of recipient and date delivered. In addition, in the case where the project is a highway or a bridge, a copy of the proposal should be delivered to the Commonwealth Transportation Commissioner on the same day it delivers its proposal to the City. The Commissioner will be asked to provide written comments to the City within 60 days of receipt of such proposal. C. General Format for Submi ssion of Conceptual Proposal. An authorized representative of the firm or consortium making the proposal must sign the proposal. All information requested under Section IV, "FORMAT FOR CONCEPTUAL PROPOSAL" should be submitted. Proposers failing to submit all information requested for Conceptual or Detailed Proposals may be given an opportunity to promptly submit missing information or may be given a lowered evaluation of the proposal. Conceptual Proposals that lack key information required may be rejected. Proposals should be prepared simply and economically, providing a straightforward, concise description of the proposer's capabilities to complete the Page 104 of 325 11 proposed project. Emphasis should be placed on completeness and clarity of content. Proposals submitted for consideration should include a comprehensive scope of work and provide enough information about the project to determine whether it meets the criteria stated herein. In addition, the financial plan for the project must contain enough detail so that an analysis will reveal whether the proposed project financing is feasible. Proposals should be organized in the order requested herein. All pages of the proposal should be consecutively numbered. Evaluation of proposals will be better facilitated if proposers will cross reference responses by citing the tab number, and sub letter, and repeating the text of the requirement, not the text of the proposal. If a response covers more than one page, the tab number and sub letter should be repeated at the top of the next page. The proposal should contain a table of contents, which cross references the requirements by category. Information that the proposer desires to present that does not fall within any of the requirements should be inserted at an appropriate place or be attached at the end of the proposal and designated as additional material. Proposals that are not organized in this manner risk elimination from consideration. Each copy of the proposal should be bound or otherwise contained in a single volume where practical. All documentation submitted with the proposal should be contained in that single volume, except that information for which a claim of confidentiality is made should be submitted in a separately bound document or volume for convenience of review by the City. Any such volume containing confidential information should be clearly marked on its cover as containing confidential information to reduce the potential for inadvertent disclosure. Proposers who submit a proposal may be required to give an oral presentation of their proposal to the City. Such presentations will provide opportunities to educate the City and/or clarify aspects of the proposed project. D. General Format for Submi ssion of Detailed Proposal. Once Conceptual Proposals have been reviewed, one or more such proposers may be selected for submission of Detailed Proposals. The required contents of a Detailed Proposal are as listed below in Section V, entitled "FORMAT FOR DETAILED PROPOSAL," but may be modified for specific projects in the notice of selection and request for Detailed Proposals. As with Conceptual Proposals, one (1) original, nine (9) copies, and one (1) electronic copy of each Detailed Proposal must be submitted and the required review fee increment paid. Each copy should be bound in one or more volumes with a detailed table of contents showing the location of the required information. The required items should be provided in individually tabbed sections marked in accordance with the contents listed herein. Pages should be numbered consecutively. As with Conceptual Proposals, confidential information should be segregated into a separate volume for ease of review and production in response to potential requests under the Virginia Freedom of Information Act (FOIA). Any such volume containing confidential information should be clearly marked on its Page 105 of 325 12 cover as containing confidential information to reduce the potential for inadvertent disclosure. E. Proposal Review Fee The PPEA permits the City to charge a reasonable fee for the review of all proposals for Qualifying Projects, whether solicited or unsolicited. The PPTA, however, only allows the City to charge a review fee for unsolicited proposals. When applicable, the fee will be payable in two increments: the first increment must accompany the submission of a Conceptual Proposal, and the second increment must accompany a Detailed Proposal requested by the City. Any proposal submitted without the required fee will be deemed noncompliant and will be rejected. 1. Proposal Review Fee for Solicited Projects. For solicited proposals, for qualifying projects as defined under the PPEA, the fee schedule will be set forth in the RFP or IFB. 2. Proposal Review Fee for Unsolicited Projects. The City has established a fee schedule for the review of unsolicited proposals for Qualifying Projects under these procedures. This fee schedule is subject to revision for specific projects, based on the complexity or details of the project, and upon the actual cost to the City to review the proposal. The fee schedule is based upon the estimated construction cost of the proposed Qualifying Project. If the proposal also includes maintenance and operation services to be provided by the private entity for a period longer than one year following construction, the required fee shall be increased by 50% to cover evaluation of the services components of the proposal. Proposals including only services and no construction component shall include a fee commensurate with a proposal with a construction cost under $20,000,000. a. Projects with Estimat ed Construction Cost under $20,000,000, and "services only" proposals. A total fee of $20,000, payable in two increments: (1) $5,000 with the Conceptual Proposal, and (2) $15,000 with the Detailed Proposal, if requested. b. Projects with Estimat ed Construction Cost between $20,000,000 and $50,000,000. A total fee of $30,000, payable in two increments: (1) $7,500 with the Conceptual Proposal, and (2) $22,500 with the Detailed Proposal, if requested. c. Projects with Estimated Construction Cost over $50,000,000. A total fee of $50,000, payable in tw o increments: (1) $10,000 with the Conceptual Proposal, and (2) $40,000 with the Detailed Proposal if requested. Page 106 of 325 13 3. Refunds of Fees. If an unsolicited Conceptual Proposal is determined upon initial review by the City to be not proper for consideration or is otherwise rejected without conclusion of an agreement on the protection of confidential information, the initial payment of the fee will be refunded. If an unsolicited Detailed Proposal is rejected without negotiations with the proposer, ninety per cent (90%) of the second incremental payment will be refunded to the proposer. F. Virginia Freedom of Information Act. Generally, proposal document s submitted by private ent ities are subject to the Virginia Freedom of Information Act ("VFOI A"). In accordance with § 2.2-3705 A 56 of VFOIA, such documents are releasabl e if requested, exc ept to the extent that they relate to (a) c onfidential proprietary inform ation submitted to the City under a promise of confident iality or (b) memoranda, wo rking papers or other records related to proposals if making pub lic such records would adversely affect the financial interest of the City or the pr ivate entity or the bargaining position of either party. Once a comprehensive ag reement has been entered into and the process of bargaining of all phases or aspects of the comprehensive agreement is complete, the City shall make the procurement records available upon request, in accordance with Virginia Code §§ 2.2-4342 and 56-575.16.5. However, proprietary, commercial or financial in formation, balance sheets, financial statements, or trade secrets provided by a privat e entity as evidence of its qualifications and properly designated under this paragraph as "Confidential-Not Releasable under VFOIA" are not considered procurement records. If requesting that the City not disclose information, the proposer must (i) invoke an exclusion when the data or materials ar e submitted to the City or before such submission, (ii) identify the data and materials for which protection from disclosure is sought, and (iii) state wh y the exclusion from disclosure is necessary. In addition, the proposer must clearly mark each page of its proposal that it contends not to be disclos eable under the VFOIA with the legend "Confidential – Not Releasable under VFOIA." The City may only protect confidential proprietary information and wi ll not protect any portion of a proposal from disclosure if the ent ire proposal has been desig nated confidential by the proposer without re asonably differentiating bet ween the proprietary and non- proprietary information contained therein. Except as reasonably necessary for the Cit y, staff, and consultants to review proposals, the City promises to mainta in the confidentialit y of confidential proprietary information that is provided to it by a private entity pursuant to a proposal for a procurement under these procedures if the private entity follows all the steps required by paragraph 4.4. of this policy to designate the information as confidential proprietary information excluded from disclosure under VFOIA, and if the information is, in fact, information t hat is properly exempt from release under VFOIA. The City Manager shall take r easonable precautions to protect the confidentiality of such information from any disclosure beyond whatever disclosure is reasonably necessary for t he City Council, staff, and consultants having a need to know the information to carry out the procurement. Despite the Page 107 of 325 14 City’s sincere intent to honor this promis e of confidentiality, nothing contained herein shall constitute a wa iver of sovereign immunity, a consent to suit, or a contractual undertaking, and it is a condi tion of submitting proposals that no cause of action, in contract or otherwise, shall arise against the City or its Mayor, council members, City Manager, officers, employees, attorneys, or agents for any failure to maintain confidentiality of information. Any information in a proposal that becom es incorporated into a Comprehensive Agreement or Interim Agreement with t he proposer submitting it, such as by becoming an exhibit, shall become a public record releasable under VFOIA upon execution of the agreement and its approval by the City. G. Affected Local Jurisdiction Review The Acts require that proposals be submitted to affected local jurisdictions for review. This requirement applies to both Conceptual Proposals and Detailed Proposals. While, normally, the City of Lynchburg will be the only affected locality, the City will notif y and solicit comment from any locality thought to be affected by a proposal and will respond to a request from any locality that feels it is affected. Affected localities will be provided with copies of accepted Conceptual and Detailed Prop osals and Confidentiality Agreements at the appropriate time in the process and will be given 60 days from the receipt of such documents to provide comment. Comment s received within the 60-day period will be given consideration by the City and no negative infer ence will be drawn from the absence of comment. Each proposer will be permitted to review any comments from affected jurisdictions applicable to its or other proposals, subject to limitations on the sharing of confidential information under a Confidentiality Agreement. H. Applicability of Other Law. 1. Use of Public Funds Virginia constitutional and statutory requi rements as they apply to appropriation and expenditure of public funds apply to any agreement entered into under the PPTA or PPEA. Accordingly, the pr ocesses and procedur al requirements associated with the expend iture or obligation of public funds should be incorporated into planning for any PPTA or PPEA projec t, and any PPTA/PPEA procurement should comply with City fiscal policies. Virginia constitutional and statutory restrictions that apply to the City regarding expenditures of public funds shall be deemed to be incorporated into any agreement into which the City enters pursuant to the PPTA/PPEA and to condition the City's obligations thereunder. Nothing in the Acts affects the duty of the City or any of its officers, employees or agents to comply with all other applicable law not in conflict with the Acts, and proposals for Qualifying Projects shall consider those requirements where applicable. However, the applicability of the Virginia Public Procurement Act (the VPPA) shall be as set forth in paragraph I of this policy. Page 108 of 325 15 I. Adoption of Certain Portions of the Virginia Public Procurement Act and Use of Competitive Negotiation and Competitive Sealed Bidding Procedures. The provisions of the Virg inia Public Procurement Ac t, Va. Code § 2.2-4300, et seq., shall not apply to procurements by the City under the PPTA/PPEA except as follows: 1. The definitions of "compet itive sealed bidding" and "competitive negotiation" of othe r than professional services in Va. Code § 2.2-4301 are hereby adopted. 2. The provisions of Va. C ode §2.2-4310 shall apply to all PPTA/PPEA procurements. 3. The provisions from the Ethics in Public Contracting Act, Va. Code § 2.2-4367 through 2.2-4377, shall apply to all PPTA/PPEA procurements. 4. The provisions of Va . Code §2.2-4343 are adopted as additional authority for parts of this policy. 5. The provisions of Virginia Code §2.2-4337 apply to bonds or letters of credit for any com ponents of a qualifying project involving construction. 6. Before accepting any unsolic ited proposal or before issuing any solicitation for proposals, the City will determine whether it will proceed to evaluate proposals using either: a. "Competitive sealed bidding" , as defined in Va. Code § 2.2-4301; or b. "Competitive negotiation" of other than professional services as defined in Va. Code § 2.2-4301. 7. The City may proceed using competitive negotiation procedures described in paragr aph 6.a. above only if the City Council first makes a written determination pursuant to Virginia Code § 56-575. 16.2 that doing so is likely to be advantageous to the public based upon either (i) the probable scope, complexity or priori ty of the project, or (ii) the risk sharing, including gu aranteed cost or completion guarantees, added value, or debt or equity investments proposed, or (iii) the increase in funding, dedicated revenue source or other economic benefit that would otherwise not be available. Page 109 of 325 16 III. PROPOSAL EVALUATION AND SELECTION. A. Decision to Accept an Unsolicited Proposal. The City must make several determinations in order to accept an unsolicited proposal for a Qualifying Project. Proposers are required to address all of the following criteria in their proposals to assist the City in making informed determinations. B. Initial Review by the City. 1. Determination if the proposal presents a "Qualifying Project" under the PPTA or the PPEA. The first determination that must be made by the City is whether the proposal constitutes a "Qualifying Project" under the PPEA, or a "qualified transportation facility" under the PPTA. The definitions of these terms are presented in the introduction to these procedures. 2. Determination of whether t he proposed project meets the public purposes of the Acts and the City. The Acts require that the City determine if the proposed project serves the public purpose as defined in the Acts by facilitating the timely acquisition, design, construction, improvement, renovation, expansion, equipping, maintenance, operation, implementation and/or installation of a Qualifying Project or facility. Specifically, in determining whether a proposed project meets this "public purpose" requirement, the City must determine if: a. There is a public need fo r or benefit derived from the Qualifying Project; b. The estimated cost of the Qualifying Project is reasonable in relation to similar facilities; and c. The private entity's plans will result in the timely acquisition, design, construction, improvement, renovation, expansion, equipping, maintenance, implementation, installation, and/or operation of the Qualifying Project. Each of these criteria should be addressed in the proposal. In addition, the City will determine if the proposed project is desirable and compatible with other City, regional or state plans. Proposers are cautioned that a proposal may be rejected on this basis alone even if it is an otherwise Qualifying Project under the Acts. 3. Determination to use "com petitive sealed bidding" or "competitive negotiation" procedures. The City will acquire a Qualifying Project through the use of "competitive sealed bidding" procedures unless a determination is made, in writing, that proceeding Page 110 of 325 17 through "competitive negotiation" procedures will be advantageous to the City and the public based on the (a) the probable scope, complexity or urgency of the project, or (b) risk sharing, added value, an increase in funding or economic benefit from the project that would not otherwise be available. Proposers should address these factors in their proposals. C. Written determination of qualification. The City will make a written determination that the above criteria are satisfied prior to proceeding with further consideration of Conceptual Proposals. D. Conclusion of an Agreement on the Protection of Confidential Information. Following a decision of the City to accept and consider a Conceptual Proposal, the City and the proposer will review the provisions of paragraph II.F., above, and, if necessary, execute a Confidentiality Agreement designating confidential information within the proposal that will be excluded from public availability under the Virginia FOIA. E. Publication for Competing Proposals. Following a decision by the City to accept a Conceptual Proposal and the conclusion of a Confidentiality Agreement, the City will publish a notice of its decision and an invitation for the submission of competing proposals ("the public notice"). If the City has determined it will proceed under competitive sealed bidding procedures, it will so state in the public notice, and advise that it will enter into negotiations to execute a Comprehensive Agreement for a Qualifying Project with the proposer presenting a Qualifying Project with the lowest evaluated cost to the City. If the City has determined it will proceed under competitive negotiation procedures, it will so state in the public notice and advise of any special evaluation criteria it will use in its evaluation in addition to those stated in these procedures or it will identify the person from whom such information can be obtained at the City. If the City uses these procedures, it is not required to select the proposal with the lowest price offer, but may consider price as one factor in evaluating the proposals received. The public notice will state the date, time and location for receipt of competing proposals in accordance with these Procedures. F. Receipt of Competing Proposals. After passage of the date for the receipt of competing proposals, the City will review and make the initial determinations required above for all competing proposals. The City may reject any or all proposals at any time. Page 111 of 325 18 G. Determination and Agreement on Confidential Material for Competing Proposals. Agreement must be reached on all competing proposals regarding protection of confidential information. Upon conclusion of Confidentiality Agreements, if any, with private entities submitting accepted proposals, the City may begin its review. H. Selection for Submission of Detailed Proposals. If no competing proposals are submitted after publication of the public notice, or only one Conceptual Proposal is received in response to an RFP or IFB, the City may proceed immediately to request a Detailed Proposal from the sole proposer. Otherwise, the City shall then evaluate all Conceptual Proposals according to the evaluation factors, and select two or more proposers deemed to be fully qualified and best suited for submission of Detailed Proposals, unless it makes a written determination that the original proposer was the only fully qualified proposer or was clearly more highly qualified than the others under consideration. The CRB will perform its review of each Conceptual Proposal to determine whether the proposer has, in the sole opinion of the CRB (i) submitted a complete proposal; (ii) assembled a team which is qualified and capable of completing the proposed facility; (iii) developed a conceptual plan which is technically feasible; and (iv) provided a financial plan which will allow access to the necessary capital to finance the facility. The CRB may consider the advice of outside consultants and advisors, federal and state agencies with appropriate technical expertise, and legal counsel in reaching its decision. The CRB may request oral presentations and/or additional documentation in order to assess project feasibility and proposer's qualifications. If any proposer makes an oral presentation, each proposer will be given that same opportunity. The City will request submission of Detailed Proposals in writing and state the date by which such submissions shall be required. The request for Detailed Proposals shall specify the deliverables that must be included in the Detailed Proposal. The City may also request that a proposer address in detail certain aspects of its proposal or respond to certain questions in its Detailed Proposal. Those private entities submitting proposals not selected for Detailed Proposals shall also be notified in writing. I. Receipt and Review of Detailed Proposals. Those Detailed proposals received in a timely manner and complying with the requirements of these procedures and the City's request for Detailed Proposals will be reviewed by the CRB. Before such review, however, the City will execute a Confidentiality Agreement, if necessary, with each proposer as to the protection of confidential information. A Detailed Proposal should not depart significantly from the technical approach or financing plan described in the Conceptual Proposal. If a proposer departs significantly in either respect, the City may reject the Detailed Proposal as non- Page 112 of 325 19 compliant. In particular, adoption of significant aspects or characteristics of a competing Conceptual Proposal will normally result in disqualification and rejection of a Detailed Proposal. Proposers may be required to make an oral presentation to the CRB to explain their proposals and respond to questions. The format of the presentation will include a formal presentation by the proposer, followed by any questions the CRB may have pertaining to the project proposal or the presentation. The CRB may also ask the proposer to address concerns expressed through the public comment process. These meetings will allow the City to seek clarification of project elements and complete deliverable requirements, and provide proposers with the opportunity to further explain their proposed projects. If there is an issue to which the proposer is unable to respond during the formal presentation, the City may, at its discretion, grant the proposer a reasonable period of time in which to submit a written response. The CRB may request clarifying or additional information from any proposer regarding its Detailed Proposal. J. Selection of Proposal(s) for Negotiation of Comprehensive Agreement. The CRB will consider comments from any affected local jurisdictions and any oral presentations of the proposers, and select one or more proposals for negotiations leading to the selection of one proposal for the negotiation of a Comprehensive Agreement. The selection by the CRB will be presented to the Lynchburg City Council for review and final approval. K. Negotiation and Approval of Comprehensive Agreement. Following approval of the selected proposal, the City and the private entity proposer will enter into negotiations to conclude a Comprehensive Agreement. If the City and the proposer cannot conclude a Comprehensive Agreement acceptable to both parties within a reasonable time, the City may terminate negotiations with the selected proposer and negotiate with another proposer, or it may terminate all negotiations or consideration of the proposed project. The Lynchburg City Council must approve the proposed Comprehensive Agreement before its execution. IV. FORMAT FOR CONCEPTUAL PROPOSALS. A. Description Proposals shall provide a straightforward, concise delineation of capabilities, experience and approach. Elaborate brochures and/or excessive promotional materials are not required or desirable. A Conceptual Proposal shall contain the following information: (i) proposer’s qualifications and experience, (ii) project characteristics, (iii) project financing and estimate of construction costs, (iv) anticipated public support or opposition, or both, (v) project benefit and Page 113 of 325 20 compatibility and (vi) any additional information as the City may reasonably request to comply with the requirements of the Acts. Information in Conceptual proposals should be organized into an Executive Summary, Introduction, and individually tabbed sections in accordance with the following format: Executive Summary A brief description of the project scope and characteristics, the general approach to financing the proposed project and the benefits. The Executive Summary may be used by the City in public notices and other short descriptions of the proposal. Introduction Among other information, the Introduction should address the criteria by which the City must evaluate the proposed project to determine if it is a "Qualifying Project" under the Acts, identify how the proposed project serves the public purposes of the Acts, and whether or not the use of competitive negotiation as a method of procurement can be authorized. B. TAB 1. Qualification and Experience a. Identify the legal struct ure of the firm or consortium of firms making the proposal. Identify the organizational structure for the project, the management approach and how each entity and major subcontractor in the structure fits into the overall team. b. Describe the experience of the firm or consortium of firms making the proposal and the key principals involved in the proposed project including the length of time in business, business experience, public sector experience, other engagements of the firm or consortium of firms and experience with projects of comparable size and complexity. Include the identity of any firms that will provide performance guarantees and warranties and a description of such guarantees and warranties. c. Provide the names, addresses, em ail addresses, and telephone numbers of persons within the firm or consortium of firms who may be contacted for further information. d. Provide the address, telephone nu mber, and the name of a specific contact person for an entity, or entities, for which the firm or consortium of firms, or primary members of the consortium, have completed a similar project or projects. These references should include: • Name and address of project owner/sponsor • Name, telephone number, fax number, and email address of the owner’s project manager • A summary of the projec t including budget and final cost • Project schedule (proposed and actual) Page 114 of 325 21 e. Provide the most recent audited fi nancial statement of the firm or firms, and each partner with an equity interest of twenty percent or greater. Such financial statements shall be for a period not more than one year before the date of the proposal. Submit the most recent Securities and Exchange Commission 10-K and 10-Q reports, if such reports have been filed. f. Identify any persons known to t he proposer who would be disqualified from participation in any transaction arising from or in connection to the project pursuant to The Virginia State and Local Government Conflict of Interest Act (Virginia Code § 2.2-3100 et seq.). g. Include any planned participation by small, women-owned, or minority- owned businesses during project development and implementation. C. TAB 2. Project Characteristics a. Provide a description of the proj ect, including the conceptual design. Describe the proposed project in sufficient detail so that the type and intent of the project, the location, and the communities that may be affected are clearly identified. Include a description of any components, planned initially or for the future, that are expected to generate revenue for the project or the proposer. b. Identify and fully describe any wo rk to be performed by the City. c. Provide a statement setting out the plans for securing all necessary property. The statement must include the names and addresses, if known, of the current owners of the subject property as well as a list of any property the proposer intends to request the City to condemn. d. Include a list of all federal, stat e and local permits and approvals required for the project and a schedule for obtaining such permits and approvals. Identify which, if any, permits or approvals are to be obtained by the City. e. Identify any anticipated adverse social, economic and environmental impacts of the project. Specify the strategies or actions to mitigate known impacts of the project. f. Identify the project ed positive social, economic and environmental impacts of the project. g. Identify the proposed schedule for wo rk on the project, including the estimated time for completion, and any extended or maintenance warranties. h. Propose allocation of risk and liability for work completed beyond the agreement's completion date, and assurances for timely completion of the project. Page 115 of 325 22 i. State assumptions related to owner ship, legal liability, law enforcement and operation of the project and the existence of any restrictions on the City's or the public's use of the project. j. Provide information relative to phas ed or partial openings of the proposed project prior to completion of the entire work. D. TAB 3. Project Financing a. Provide a preliminary estimate and estimating methodology of the cost of the work by phase and/or segment (e.g. planning, design, construction). b. Submit a plan for the developmen t, financing and operation of the project showing the anticipated schedule on which funds will be required. Describe the anticipated costs of and proposed sources and uses for such funds. c. Include a list and discussion of assump tions (user fees, tolls, usage rates) underlying all major elements of the plan. d. Identify the proposed risk factor s and methods for dealing with these factors. e. Identify any local, state or f ederal resources that the proposer contemplates requesting for the project. Describe the total commitment (financial, services, property, etc.), if any, expected from governmental sources and the timing of any anticipated commitment. f. Provide financial information whic h indicates the proposer’s financial stability and ability to finance the project. g. Include a description and analysis (c ost/benefit, tax, etc.) to demonstrate the project’s financial feasibility. E. TAB 4. Public Support, Project Benefit and Compatibility a. Identify who will benefit from the project, how they will benefit and how the project will benefit the overall community, region, or state. b. Identify any anticipated public sup port or opposition, as well as any anticipated government support or opposition for the project. c. Explain the strategy and plans to involve and inform the general public, business community, and governmental agencies in areas affected by the project. d. Describe the anticipated significant benefits to the community, region or state, including anticipated benefits to the economic condition of the City and whether the project is critical to attracting or maintaining competitive industries and businesses to the City or the surrounding region. Page 116 of 325 23 e. Address project compatibility with the City's master plan, local comprehensive plans, local infrastructure development plans, the capital improvements plan or other government spending plan. V. FORMAT FOR DETAILED PROPOSALS. A. Description and Required Information If the City decides to proceed to the detailed phase of review with one or more proposals, it shall specify any particular deliverables it will require in the Detailed Proposals. In addition, the following information should be provided by the proposer unless waived by the City: 1. A topographical map (1:2,000 or other appropriate scale) depicting the location of the proposed project; 2. A list of public or private utility facilities, if any, that will be crossed by the Qualifying Project and a statement of the plans of the proposer to accommodate such crossings; 3. A statement and strategy setti ng forth the plans for securing all necessary property. The statement must include the names and addresses, if known, of the current owners of the subject property as well as a list of any property the proposer intends to request the City to condemn; 4. A detailed listing of all firms that will provide specific design, construction and completion guarantees and warranties, and a brief description of such guarantees and warranties; 5. A total life-cycle cost specif ying methodology and assumptions of the project or projects and the proposed project start date. Include the anticipated commitment of all parties; equity, debt, and other financing mechanisms; and a schedule of project revenues and project costs. The life-cycle cost analysis should include, but not be limited to, a detailed analysis of the projected return, rate of return, or both, expected useful life of facility and estimated annual operating expenses. 6. A detailed discussion of assumpti ons about user fees or rates, and usage of the projects. 7. Identification of any known gov ernment support or opposition, or general public support or opposition for the project. Government or public support should be demonstrated through resolution of official bodies, minutes of meetings, letters, or other official communications. Page 117 of 325 24 8. Demonstration of consistency with appropriate local comprehensive or infrastructure development plans or indication of the steps required for acceptance into such plans. 9. Identification of any known conflicts of interest or other disabilities that may impact the City's consideration of the proposal, including the identification of any persons known to the proposer who would be disqualified from participation in any transaction arising from or in connection to the project pursuant to The Virginia State and Local Government Conflict of Interest Act (Code of Virginia § 2.2- 3100 et seq.). 10. Additional material and info rmation as the City may reasonably request. VI. PROPOSAL EVALUATION. A. Manner of Evaluat ion and Use of Outside Professionals Unless the City Council directs a differ ent manner of evaluat ion in writing, evaluations of proposals shall be by such persons or group or committee of persons as the City Manager may designate, subject to such review as the City Council or City Manager may direct. Eval uations of proposals shall include, without limitation, analysis of t he proposals’ specifics, advantages, disadvantages, long-term costs, and shor t-term costs, using the evaluation criteria specified for the procuremen t. The City Manager shall engage the services of qualified professionals not em ployed by the City, which may include, without limitation, an architect, profes sional engineer, or certified public accountant, to provide an independent analys is as part of the evaluation. Notwithstanding the preceding sentence, if the City Council determines that such analysis of proposals will be performed by City staff, the City Manager need not engage such an outside professional. B. Evaluation and Se lection Criteria The City will consider criteria it deems appropriate in the evaluation and selection of proposals at all phases of its review. Such criteria may include some or all of the criteria listed in Appendix E hereto but shall not be limited to those criteria alone. The City may, in its sole discretion, select other evaluation criteria that it deems appropriate to the specific project. VII. COMPREHENSIVE AGREEMEN TS and INTERIM AGREEMENTS. A. Description and Terms Prior to acquiring, designing, constructing, improving, renovating, expanding, equipping, operating, implementing and/or installing, a Qualifying Project the proposer(s) selected must enter into a comprehensive agreement with the City. Page 118 of 325 25 Each Comprehensive Agreement shall define the rights and obligations of the City and the selected proposer with regard to the project. The terms of the Comprehensive Agreement shall include but not be limited to: 1. The delivery of maintenance, performance and payment bonds or letters of credit in connection with any acquisition, design, construction, improvement, renovation, expansion, equipping, maintenance, operation, implementation or installation of the Qualifying Project, in the forms and amounts satisfactory to the City; 2. The performance milestones that will be required of the proposer. 3. The design, construction, operation and main tenance standards with which the proposer must comply. 4. The review and approval of plans and specifications for the Qualifying Project by the City if the plans and specifications conform to the City’s standard conditions; 5. The rights of the City to ins pect the Qualifying Project to ensure compliance with the Comprehensive Agreement; 6. The maintenance of a policy or policies of liability insurance, (copies of which shall be filed with the City accompanied by proofs of insurance), or self-insurance, in form and amount satisfactory to the City and reasonably sufficient to insure coverage of the project and the tort liability to the public and employees and to enable the continued operation of the Qualifying Project; 7. The right of the proposer to ac quire, design, construct, improve, renovate, expand, equip, maintain, operate, implement and/or install the facility, the duration of the operator’s rights to operate the facility, and the conditions under which the facility will be dedicated to the City. 8. The monitoring of the practices of the proposer and/or operator by the City to ensure proper maintenance and provisions for the City to take appropriate action to ensure the facility is properly maintained. 9. The procedures by and condit ions under which the City will exercise its power of eminent domain. 10. The terms under which the propos er and/or operator will reimburse the City for services provided; 11. The events that will constitu te default by the proposer, the proposer’s rights to notice and cure and the remedies available to the City. Page 119 of 325 26 12. The events that will constitute defaul t by the City, the City’s rights to notice and cure and the remedies available to the proposer. 13. The rights and remedies of any lender with respect to the proposer’s defaults and the City’s remedies. 14. The policy and procedures that will govern the rights and responsibilities of the City and the proposer and/or operator in the event that the Comprehensive Agreement is terminated or there is a material default by the proposer and/or operator including the conditions governing assumption of the duties and responsibilities of the proposer and/or operator by the City and the transfer or purchase of property or other interests of the proposer and/or operator to/by the City; 15. The events that will constitute force majeure and the remedies the parties will have in the event of such occurrence. 16. The terms under which the pr oposer and/or operat or will file appropriate financial statements on a periodic basis. 17 The mechanism by which user fees, lease payments, or service payments, if any, may be established from time to time upon agreement of the parties. Any payments or fees shall be set at a level that are the same for persons using the facility under like conditions and that will not materially discourage use of the Qualifying Project; a. A copy of any service contra ct shall be filed with the City. b. The proposer and/or operator shall make a schedule of the current user fees or lease payments available to any member of the public upon request. c. Classifications accordin g to reasonable categories for assessment of user fees may be made. 18. The terms and conditions unde r which the City may contribute financial, or other, resources, if any, for the Qualifying Project; and 19. The conditions under which th e proposer may assign its rights under the Comprehensive Agreement. 20. The obligation of t he operator to maintain records, to allow inspection and audit and to provide regular reports to the City. 21. Other requirem ents of the Acts Any changes in the terms of the Comprehensive Agreement as may be agreed upon by the parties from time to time shall be added to the Comprehensive Agreement by written amendment. Page 120 of 325 27 B. Interim Agreements In exceptional circumstances, the City may enter into an “Interim Agreement” within the meaning of the PPEA prior to or in connection with the negotiation of a comprehensive agreement for a qualifying project when doi ng so clearly is in the City’s best interests. As a matter of policy, the City does not favor entry into “Interim Agreements” with proposers because this technique tends to reduce competition and competitive negotiations. In particular, entry into an “Interim Agreement” with a proposer without firs t reaching an agreement as to the material terms of a comprehensive agr eement, particularly as to Guaranteed Maximum Price, scope of work, and qualit y of work, generally would tend to eliminate most of the Cit y’s ability to obtain the best value through competitive negotiations with two or more proposers. Accordingly, use of “Interim Agreements” is strongly disfavored by the City, and their use must be fully justified. Further, as a condition for entry into any interim agreement, the City must first obtain approval of such entry from the City Council. VIII. DISPUTES, CLAIMS AND OT HER MATTERS ARISING UNDER OR RELATING TO ANY COMPREHENSIVE AGREEMENT OR INTERIM AGREEMENT The following provisions apply to any disp utes, claims or other matters arising under or relating to any comprehensive ag reement or interim agreement entered into pursuant to the Acts by the City on the one hand ("Owner") , and any private entity ("Contractor"), on the other hand. Disputes, claims and other matters in question between the parties arising under or relating to any comprehensive agreement or any interim agreement shall only be resolved as follows: A. The Contractor shall give Owner written notice of any claim for any additional compensation, damages, delay or other relief within ten (10) days of the beginning of t he occurrence of the event leading to the claim being made and shall submit the actual claim and any supporting data within thirty (30) days after the occu rrence giving rise to the claim ends. The written notice shall be a docum ent addressed to the Owner that clearly states Contractor's intenti on to make a claim and the occurrence involved and shall be transmitted in a manner to ensure prompt receipt by Owner. The claim must be certifi ed under oath as true and correct by a principal of Contractor. The "occurrence" means the condition encountered in the field giving rise to the claim and not a later dispute about payment for that condition. Claims of time impacts will be resolved as they occur, and no claims of cumu lative impacts or deferral of claimed time impacts will be allowed. Complete satisfaction of this subparagraph 12.1 is an absolute prerequisi te for Contractor to pursue a claim, dispute, or other matter arising under or rela ting to the agreement. Failure by Contractor to satisfy this paragraph VIII.A. shall constitute a waiver by Contactor of the claim, dispute, or other matter for which such failure occurs. Page 121 of 325 28 B. The parties shall first endeavor to resolve any disputes, claims or other matters in question between them through direct negotiations, and if such direct negotiations fail, by non-binding mediati on conducted pursuant to the Rules of the American Arbitration Association, with the site of the mediation being Lynchburg, Vi rginia. Should the di spute, claim or other matter in question remain unresolved for the shorter of (i) following negotiation and mediation, or (ii) mo re than 90 days after mediation is requested by a party, either party ma y proceed in accordance with 12.1.3 below. However, nothing in this paragraph VIII.B. excuses Contractor from compliance with all the provisions of Section VIII. C. If the procedures of paragraph VIII.B. have been followed, but, more than 90 days have passed since a party has invoked mediation, and the dispute, claim or other matter in question remains unresolved, then either party may institute a lawsuit or chanc ery action, as appropriate, in the Lynchburg Circuit Court, Lynchburg, Virginia, or if the subject or amount in controversy is within its jurisdiction, the Lynchburg General District Court, Lynchburg, Virginia, and may thereafte r pursue all available appeals in Virginia state courts, to the extent they have jurisdiction. D. Nothing in paragraphs VIII.B. and VIII.C. shall prevent a party from seeking temporary injunctive or other temporary equitable relief in the Lynchburg Circuit Court if circumstances so warrant. E. In the event of any di spute, claim, or other matter in question arising, Contractor shall continue its performance diligently during its pendency as if no dispute, claim or other matte r in question had arisen. During the pendency of any claim, dispute or ot her matter in connection with the payments of moneys, Contractor sha ll be entitled to receive payments for non-disputed items, subject to any right of set-off by Owner. F. These procedures and the provisio ns of the interim agreement or comprehensive agreement, as applicable, supercede any right at common law by Contractor for a claim of mate rial breach or for rescission of such agreement. G. These procedures shall be deem ed automatically incorporated by reference into any agreement entered in to by the City pursuant to the Acts. H. For purposes of these procedur es, "Owner" means the City, and "Contractor" means the private entity or entit ies entering into the agreement with the Cit y, as well as Contractor's successors, assigns, sureties or others claiming through Contractor. I. The City Manager may further supplem ent Section VIII. of this policy with the terms and conditions of any agreements. Page 122 of 325 29 IX. PROTESTS OF PPTA/PPEA PROCUREMENTS The following are the exclusive proc edures for contesting or challenging (protesting) (a) the terms or conditions of any solicitation of proposals by the City pursuant to the Acts, (b) nonselection of a proposal for further consideration, and (c) the selection of any proposal for ent ry into a comprehensive agreement or interim agreement or the entry into a comprehensive agreement or interim agreement under the Acts: A. Any protest to any term or conditi on of a solicitation or any term or condition imposed by the City must be made in writing and delivered to the City Manager so it is received by the City Manager bef ore proposals are due. Otherwise, any such protest shall be deemed to be waived. B. A protest of a City decision not to select a proposal for further consideration may only be made by the entity w ho submitted the proposal at issue. A protest of a City decision to select a proposal for entry into an agreement or to enter into an agreement may only be made by an entity who submitted a proposal for the procurement at is sue and who was reasonably likely to have its proposal a ccepted but for the City's decision. Protests shall only be gr anted if (1) the proteste r has complied fully with this Section IX and there has been a viol ation of law, these guidelines, or mandatory terms of the solic itation that clearly prej udiced the protestor in a material way, or (2) a statute requires voiding of the decision. C. Any entity desiring to protest a City decision not to select a proposal for further consideration, to select a pr oposal for entry into an agreement, or to enter into an agreement shall submit the protest in writing and deliver it so that it is received by the Cit y Manager not later than 5 business days after announcement of the decision. Oth erwise any such protest shall be deemed to be waived. D. The City Manager shall issue a wri tten decision on a protest within 10 days of its receipt by the City Manager. E. If the protest is denied, the prot ester may only appeal the denial or otherwise contest or chal lenge the procurement by then filing suit in the Lynchburg Circuit Court, Lynchburg, Vi rginia, and serving the City with such suit within 10 days of such denial. Otherwise, the protester's right to appeal the denial or to ot herwise contest or cha llenge the procurement shall be deemed to be waived. F. The exclusive relief allowed if a prot est is granted is to void the decision being protested. Under no circum stances will any monetary relief be allowed. G. Strictly following these procedures shall be a mandatory prerequisite for any challenge of any nature to a decisi on by the City relating to terms and conditions of a PPTA/PPEA solicitati on or terms and conditions imposed by the City, nonselection of a proposal for further consideration, selection of a proposal, or entry into an agreement. A failure to follow all these Page 123 of 325 30 procedures strictly shall constitute a waiver of any right to challenge judicially a City decision (a) as to terms or conditions in a PPTA/PPEA solicitation or imposed by the City, (b) not to sele ct a proposal for further consideration, (c) to select a proposal, or (d) to enter into an agreement. X. PARTICIPATION OF SMALL AND MINORITY-OWNED BUSINESS The City's policy is to facilitate partic ipation of small businesses and businesses owned by women and minorit ies in its procurement transactions, including procurement transactions under the Acts. Persons making proposals to the City pursuant to the Acts should ensure that reasonable efforts are made to facilitate participation of small businesses and businesses owned by women and minorities as part of their proposals. Resort to lists of such businesses available from the Virginia Department of Minority Enterprise is encouraged. XI. PROPOSERS' AGREEMENT TO TERMS AND CONDITIONS OF THIS POLICY The City Manager shall require as a c ondition of accepting any proposal for consideration that its proposer agree to be bound by all the te rms and conditions of this policy. Proposers shall submit with any proposal the certification that is set out at Appendix F hereto. Page 124 of 325 31 Appendix A The Public-Private Transportation Act of 1995 Code of Virginia, 1950, As Amended § 56-556. Title. This chapter may be cited as the "Public-Private Transportation Act of 1995." (1994, c. 855; 1995, c. 647.) § 56-557. Definitions. As used in this chapter, unless the context requires a different meaning: "Affected local jurisdiction" means any county, city or town in which all or a portion of a qualifying transportation facility is located. "Asset management" means a systematic process of operating and maintaining the state system of highways by combining engineering practices and analyses with sound business practices and economic theory to achieve cost-effective outcomes. "Commission" means the State Corporation Commission. "Comprehensive agreement" means the comprehensive agreement between the operator and the responsible public entity required by § 56-566 of this chapter. "Maintenance" means that term as defined in § 33.1-23.02. "Material default" means any default by the operator in the performance of its duties under subsection F of § 56-565 of this chapter that jeopardizes adequate service to the public from a qualifying transportation facility and remains unremedied after the responsible public entity has provided notice to the operator and a reasonable cure period has elapsed. "Operator" means the private entity that is responsible for the acquisition, construction, improvement, maintenance and/or operation of a qualifying transportation facility. "Private entity" means any natural person, corporation, limited liability company, partnership, joint venture or other private business entity. "Public entity" means the Commonwealth and any agency or authority thereof, any county, city or town and any other political subdivision of any of the foregoing, but shall not include any public service company. "Qualifying transportation facility" means one or more transportation facilities acquired, constructed, improved, maintained and/or operated by a private entity pursuant to this chapter. "Responsible public entity" means a public entity that has the power to acquire, construct, improve, maintain and/or operate the applicable transportation facility. Page 125 of 325 32 "Revenues" means the user fees and/or service payments generated by a qualifying transportation facility. "Service contract" means a contract entered into between a public entity and the operator pursuant to § 56-561 of this chapter. "Service payments" means payments to the operator of a qualifying transportation facility pursuant to a service contract. "State" means the Commonwealth of Virginia. "Transportation facility" means any road, bridge, tunnel, overpass, ferry, airport, mass transit facility, vehicle parking facility, port facility or similar commercial facility used for the transportation of persons or goods, together with any other property that is needed to operate the transportation facility. "User fees" mean the rates, fees or other charges imposed by the operator of a qualifying transportation facility for use of all or a portion of such qualifying transportation facility pursuant to the comprehensive agreement. (1994, c. 855; 1995, c. 647; 2001, c. 286; 2002, cc. 570, 593.) § 56-558. Policy. A. The General Assembly finds that: 1. There is a public need for timely acquisition or construction of and improvements to transportation facilities within the Commonwealth that are compatible with state and local transportation plans; 2. Such public need may not be wholly satisfied by existing ways in which transportation facilities are acquired, constructed or improved; and 3. Authorizing private entities to acquire, construct, improve, maintain, and/or operate one or more transportation facilities may result in the availability of such transportation facilities to the public in a more timely or less costly fashion, thereby serving the public safety and welfare. B. An action, other than the approval of the responsible public entity under § 56-560 of this chapter, shall serve the public purpose of this chapter if such action facilitates the timely acquisition or construction of or improvement to a qualifying transportation facility or the continued operation of a qualifying transportation facility. C. It is the intent of this chapter, among other things, to facilitate to the greatest extent possible, the pooling and funding mechanisms of the Intermodal Surface Transportation Efficiency Act of 1991, and any successor legislation, to the end that transportation financing be expanded and accelerated to improve and add to the convenience of the public, and such that public and private entities may have the greatest possible flexibility in contracting with each other for the provision of the public services which are the subject of this chapter. Page 126 of 325 33 D. This chapter shall be liberally construed in conformity with the purposes hereof. (1994, c. 855; 1995, c. 647.) § 56-559. Prerequisite for operation. Any private entity seeking authorization under this chapter to acquire, construct, improve, maintain and/or operate a transportation facility shall first obtain approval of the responsible public entity under § 56-560. Such private entity may initiate the approval process by requesting approval pursuant to subsection A of § 56-560 or the responsible public entity may request proposals pursuant to subsection B of § 56-560. (1994, c. 855; 1995, c. 647.) § 56-560. Approval by the responsible public entity. A. The private entity may request approval by the responsible public entity. Any such request shall be accompanied by the following material and information unless waived by the responsible public entity with respect to the transportation facility or facilities that the private entity proposes to operate as a qualifying transportation facility: 1. A topographic map (1:2,000 or other appropriate scale) indicating the location of the transportation facility or facilities; 2. A description of the transportation facility or facilities, including the conceptual design of such facility or facilities and all proposed interconnections with other transportation facilities; 3. The projected total life-cycle cost of the transportation facility or facilities and the proposed date for acquisition of or the beginning of construction of, or improvements to the transportation facility or facilities; 4. A statement setting forth the method by which the operator proposes to secure all property interests required for the transportation facility or facilities. The statement shall include: (i) the names and addresses, if known, of the current owners of the property needed for the transportation facility or facilities, (ii) the nature of the property interests to be acquired, and (iii) any property that the responsible public entity is expected to be requested to condemn; 5. Information relating to the current transportation plans, if any, of each affected local jurisdiction; 6. A list of all permits and approvals required for acquisition or construction of or improvements to the transportation facility or facilities from local, state, or federal agencies and a projected schedule for obtaining such permits and approvals; 7. A list of public utility facilities, if any, that will be crossed by the transportation facility or facilities and a statement of the plans of the operator to accommodate such crossings; Page 127 of 325 34 8. A statement setting forth the operator's general plans for financing and operating the transportation facility or facilities; 9. The names and addresses of the persons who may be contacted for further information concerning the request; and 10. Such additional material and information as the responsible public entity may reasonably request. B. The responsible public entity may request proposals from private entities for the acquisition, construction, improvement and/or operation of transportation facilities. The responsible public entity shall not charge a fee to cover the costs of processing, reviewing, and evaluating proposals received in response to such requests. C. The responsible public entity may grant approval of the acquisition, construction, improvement and/or operation of the transportation facility or facilities as a qualifying transportation facility if the responsible public entity determines that it serves the public purpose of this chapter. The responsible public entity may determine that the acquisition, construction, improvement and/or operation of the transportation facility or facilities as a qualifying transportation facility serves such public purpose if: 1. There is a public need for the transportation facility or facilities of the type the private entity proposes to operate as a qualifying transportation facility; 2. The transportation facility or facilities and the proposed interconnections with existing transportation facilities, and the operator's plans for operation of the qualifying transportation facility or facilities, are reasonable and compatible with the state transportation plan and with the local comprehensive plan or plans; 3. The estimated cost of the transportation facility or facilities is reasonable in relation to similar facilities; and 4. The private entity's plans will result in the timely acquisition or construction of or improvements to the transportation facility or facilities or their more efficient operation. In evaluating any request, the responsible public entity may rely upon internal staff reports prepared by personnel familiar with the operation of similar facilities or the advice of outside advisors or consultants having relevant experience. D. The responsible public entity may charge a reasonable fee to cover the costs of processing, reviewing and evaluating the request submitted by a private entity pursuant to subsection A, including without limitation, reasonable attorney's fees and fees for financial and other necessary advisors or consultants. E. The approval of the responsible public entity shall be subject to the private entity's entering into a comprehensive agreement with the responsible public entity. F. In connection with its approval of the operation of the transportation facility or facilities as a qualifying transportation facility, the responsible public entity shall establish a date for the acquisition of or the beginning of construction of or improvements to the qualifying transportation facility. The responsible public entity may extend such date from time to time. Page 128 of 325 35 (1994, c. 855; 1995, c. 647; 2003, c. 289.) § 56-561. Service contracts. In addition to any authority otherwise conferred by law, any public entity may contract with an operator for transportation services to be provided by a qualifying transportation facility in exchange for such service payments and other consideration as such public entity may deem appropriate. (1994, c. 855; 1995, c. 647.) § 56-562. . Repealed by Acts 1995, c. 647. § 56-563. Affected local jurisdictions. A. Any private entity requesting approval from, or submitting a proposal to, a responsible public entity under § 56-560 shall notify each affected local jurisdiction by furnishing a copy of its request or proposal to each affected local jurisdiction. B. Each affected local jurisdiction that is not a responsible public entity for the respective qualifying transportation facility shall, within sixty days after receiving such notice, submit any comments it may have in writing on the proposed qualifying transportation facility to the responsible public entity and indicating whether the facility is compatible with the local comprehensive plan. (1994, c. 855; 1995, c. 647.) § 56-564. Dedication of public property. Any public entity may dedicate any property interest that it has for public use as a qualified transportation facility if it finds that so doing will serve the public purpose of this chapter. In connection with such dedication, a public entity may convey any property interest that it has, subject to the conditions imposed by general law, to the operator, subject to the provisions of this chapter, for such consideration as such public entity may determine. The aforementioned consideration may include, without limitation, the agreement of the operator to operate the qualifying transportation facility. (1994, c. 855; 1995, c. 647.) § 56-565. Powers and duties of the operator. A. The operator shall have all power allowed by law generally to a private entity having the same form of organization as the operator and shall have the power to acquire, construct, improve or operate the qualifying transportation facility and impose user fees and/or enter into service contracts in connection with the use thereof. No tolls or user fees may be imposed by the operator on any free road, bridge, tunnel or overpass unless such road, interstate highway, bridge, tunnel or overpass is reconstructed to provide for increased capacity. Page 129 of 325 36 B. The operator may own, lease or acquire any other right to use or operate the qualifying transportation facility. C. Any financing of the qualifying transportation facility may be in such amounts and upon such terms and conditions as may be determined by the operator. Without limiting the generality of the foregoing, the operator may issue debt, equity or other securities or obligations, enter into sale and leaseback transactions and secure any financing with a pledge of, security interest in, or lien on, any or all of its property, including all of its property interests in the qualifying transportation facility. D. Subject to applicable permit requirements, the operator shall have the authority to cross any canal or navigable watercourse so long as the crossing does not unreasonably interfere with then current navigation and use of the waterway. E. In operating the qualifying transportation facility, the operator may: 1. Make classifications according to reasonable categories for assessment of user fees; and 2. With the consent of the responsible public entity, make and enforce reasonable rules to the same extent that the responsible public entity may make and enforce rules with respect to a similar transportation facility. F. The operator shall: 1. Acquire, construct, improve, maintain and/or operate the qualifying transportation facility in a manner that meets the engineering standards of the responsible public entity for transportation facilities operated and maintained by such responsible public entity, all in accordance with the provisions of the comprehensive agreement; 2. Keep the qualifying transportation facility open for use by the members of the public at all times after its initial opening upon payment of the applicable user fees, except when exempted by § 33.1-252, and/or service payments; provided that the qualifying transportation facility may be temporarily closed because of emergencies or, with the consent of the responsible public entity, to protect the safety of the public or for reasonable construction or maintenance procedures; 3. Maintain, or provide by contract for the maintenance of, the qualifying transportation facility; 4. Cooperate with the responsible public entity in establishing any interconnection with the qualifying transportation facility requested by the responsible public entity; and 5. Comply with the provisions of the comprehensive agreement and any service contract. (1994, c. 855; 1995, c. 647; 2002, c. 593.) § 56-566. Comprehensive agreement. Page 130 of 325 37 A. Prior to acquiring, constructing, improving, maintaining, and/or operating the qualifying transportation facility, the operator shall enter into a comprehensive agreement with the responsible public entity. The comprehensive agreement shall provide for: 1. Delivery of performance and payment bonds in connection with the construction of or improvements to the qualifying transportation facility, in the forms and amounts satisfactory to the responsible public entity; 2. Review of plans and specifications for the qualifying transportation facility by the responsible public entity and approval by the responsible public entity if the plans and specifications conform to standard conditions of the responsible public entity; 3. Inspection of construction of or improvements to the qualifying transportation facility by the responsible public entity to ensure that they conform to the engineering standards acceptable to the responsible public entity; 4. Maintenance of a policy or policies of public liability insurance (copies of which shall be filed with the responsible public entity accompanied by proofs of coverage), self- insurance, in form and amount satisfactory to the responsible public entity and reasonably sufficient to insure coverage of tort liability to the public and employees and to enable the continued operation of the qualifying transportation facility; 5. Monitoring of the maintenance practices of the operator by the responsible public entity and the taking of such actions as the responsible public entity finds appropriate to ensure that the qualifying transportation facility is properly maintained; 6. Reimbursement to be paid to the responsible public entity for services provided by the responsible public entity; 7. Filing of appropriate financial statements on a periodic basis; 8. A reasonable maximum rate of return on investment for the operator; and 9. The date of termination of the operator's authority and duties under this chapter and dedication to the appropriate public entity. B. The comprehensive agreement shall provide for such user fees as may be established from time to time by agreement of the parties. Any user fees shall be set at a level that, taking into account any service payments, allows the operator the rate of return on investment specified in the comprehensive agreement. A copy of any service contract shall be filed with the responsible public entity. A schedule of the current user fees shall be made available by the operator to any member of the public on request. In negotiating user fees under this section, the parties shall establish fees that are the same for persons using the facility under like conditions and that will not materially discourage use of the qualifying transportation facility. The execution of the comprehensive agreement or any amendment thereto shall constitute conclusive evidence that the user fees provided for therein comply with this chapter. User fees established in the comprehensive agreement as a source of revenues may be in addition to, or in lieu of, service payments. Page 131 of 325 38 C. In the comprehensive agreement, the responsible public entity may agree to make grants or loans to the operator from time to time from amounts received from the federal government or any agency or instrumentality thereof. D. The comprehensive agreement shall incorporate the duties of the operator under this chapter and may contain such other terms and conditions that the responsible public entity determines serve the public purpose of this chapter. Without limitation, the comprehensive agreement may contain provisions under which the responsible public entity agrees to provide notice of default and cure rights for the benefit of the operator and the persons specified therein as providing financing for the qualifying transportation facility. The comprehensive agreement may contain such other lawful terms and conditions to which the operator and the responsible public entity mutually agree, including, without limitation, provisions regarding unavoidable delays or provisions providing for a loan of public funds to the operator to acquire, construct, improve, maintain and/or operate one or more qualifying transportation facilities. E. The comprehensive agreement shall provide for the distribution of any earnings in excess of the maximum rate of return as negotiated in the comprehensive agreement. Without limitation, excess earnings may be distributed to the Commonwealth's transportation trust fund, to the responsible public entity, or to the operator for debt reduction or they may be shared with affected local jurisdictions. F. Any changes in the terms of the comprehensive agreement, as may be agreed upon by the parties from time to time, shall be added to the comprehensive agreement by written amendment. (1994, c. 855; 1995, c. 647.) § 56-567. Federal, state and local assistance. The responsible public entity may take any action to obtain federal, state or local assistance for a qualifying transportation facility that serves the public purpose of this chapter and may enter into any contracts required to receive such federal assistance. If the responsible public entity is a state agency, any funds received from the state or federal government or any agency or instrumentality thereof shall be subject to appropriation by the General Assembly. The responsible public entity may determine that it serves the public purpose of this chapter for all or any portion of the costs of a qualifying transportation facility to be paid, directly or indirectly, from the proceeds of a grant or loan made by the local, state or federal government or any agency or instrumentality thereof. (1994, c. 855; 1995, c. 647.) § 56-568. Material default; remedies. A. Except upon agreement of the operator and any other parties identified in the comprehensive agreement, no responsible public entity shall exercise any of the remedies provided in this section or in subsection B or C of § 56-569 unless the Commission, after notice to the operator and the secured parties (as may appear in the operator's records) and an opportunity for hearing, shall first issue a declaratory judgment that a material default, as defined in § 56-557, has occurred and is continuing. Page 132 of 325 39 B. Upon entry by the Commission of a declaratory judgment order pursuant to subsection A above, unless such order is stayed pending appeal to the Virginia Supreme Court, the responsible public entity may exercise any or all of the following remedies: 1. The responsible public entity may elect to take over the transportation facility or facilities and in such case it shall succeed to all of the right, title and interest in such transportation facility or facilities, subject to any liens on revenues previously granted by the operator to any person providing financing therefor and the provisions of subsection C below. 2. Any responsible public entity having the power of condemnation under state law may exercise such power of condemnation to acquire the qualifying transportation facility or facilities. Nothing in this chapter shall be construed to limit the exercise of the power of condemnation by any responsible public entity against a qualifying transportation facility after the entry by the Commission of a final declaratory judgment order pursuant to subsection A above. Any person that has provided financing for the qualifying transportation facility, and the operator, to the extent of its capital investment, may participate in the condemnation proceedings with the standing of a property owner. 3. The responsible public entity may terminate the comprehensive agreement and exercise any other rights and remedies which may be available to it at law or in equity. 4. The responsible public entity may make or cause to be made any appropriate claims under the performance and/or payment bonds required by subsection A 1 of § 56-566. C. In the event the responsible public entity elects to take over a qualifying transportation facility pursuant to subsection B 1 of this section, the responsible public entity shall acquire, construct, improve, operate and maintain the transportation facility, impose user fees for the use thereof and comply with any service contracts as if it were the operator. Any revenues that are subject to a lien shall be collected for the benefit of, and paid to, secured parties, as their interests may appear, to the extent necessary to satisfy the operator's obligations to secured parties, including the maintenance of reserves and such liens shall be correspondingly reduced and, when paid off, released. Before any payments to, or for the benefit of, secured parties, the responsible public entity may use revenues to pay current operation and maintenance costs of the transportation facility or facilities, including compensation to the responsible public entity for its services in operating and maintaining the qualifying transportation facility. Remaining revenues, if any, after all payments for operation and maintenance of the transportation facility or facilities, and to, or for the benefit of, secured parties, have been made, shall be paid to the operator, subject to the negotiated maximum rate of return. The right to receive such payment, if any, shall be considered just compensation for the transportation facility or facilities. The full faith and credit of the responsible public entity shall not be pledged to secure any financing of the operator by the election to take over the qualifying transportation facility. Assumption of operation of the qualifying transportation facility shall not obligate the responsible public entity to pay any obligation of the operator from sources other than revenues. (1994, c. 855; 1995, c. 647.) Page 133 of 325 40 § 56-569. Condemnation. A. At the request of the operator, the responsible public entity may exercise any power of condemnation that it has under law for the purpose of acquiring any lands or estates or interests therein to the extent that the responsible public entity finds that such action serves the public purpose of this chapter. Any amounts to be paid in any such condemnation proceeding shall be paid by the operator. B. Except as provided in subsection A of this section, until the Commission has entered a final declaratory judgment order under subsection A of § 56-568, the power of condemnation may not be exercised against a qualifying transportation facility. C. After the entry of such final order by the Commission, any responsible public entity having the power of condemnation under law may exercise such power of condemnation as provided in subsection B 2 of § 56-568 in lieu of, or at any time after taking over the transportation facility pursuant to subsection B 1 of § 56-568. (1994, c. 855; 1995, c. 647.) § 56-570. Utility crossings. The operator and each public service company, public utility, railroad, and cable television provider, whose facilities are to be crossed or affected shall cooperate fully with the other in planning and arranging the manner of the crossing or relocation of the facilities. Any such entity possessing the power of condemnation is hereby expressly granted such powers in connection with the moving or relocation of facilities to be crossed by the qualifying transportation facility or that must be relocated to the extent that such moving or relocation is made necessary or desirable by construction of or improvements to the qualifying transportation facility, which shall be construed to include construction of or improvements to temporary facilities for the purpose of providing service during the period of construction or improvement. Any amount to be paid for such crossing, construction, moving or relocating of facilities shall be paid for by the operator. Should the operator and any such public service company, public utility, railroad, and cable television provider not be able to agree upon a plan for the crossing or relocation, the Commission may determine the manner in which the crossing or relocation is to be accomplished and any damages due arising out of the crossing or relocation. The Commission may employ expert engineers who shall examine the location and plans for such crossing or relocation, hear any objections and consider modifications, and make a recommendation to the Commission. In such a case, the cost of the experts is to be borne by the operator. (1994, c. 855; 1995, c. 647.) § 56-571. Police powers; violations of law. A. All police officers of the Commonwealth and of each affected local jurisdiction, shall have the same powers and jurisdiction within the limits of such qualifying transportation facility as they have in their respective areas of jurisdiction and such police officers shall have access to the qualifying transportation facility at any time for the purpose of exercising such powers and jurisdiction. This authority does not extend to the private Page 134 of 325 41 offices, buildings, garages and other improvements of the operator to any greater degree than the police power extends to any other private buildings and improvements. B. To the extent the transportation facility is a road, bridge, tunnel, overpass or similar transportation facility for motor vehicles, the traffic and motor vehicle laws of the Commonwealth or, if applicable, any local jurisdiction shall be the same as those applying to conduct on similar transportation facilities in the Commonwealth or such local jurisdiction. Punishment for offenses shall be as prescribed by law for conduct occurring on similar transportation facilities in the Commonwealth or such local jurisdiction. (1994, c. 855; 1995, c. 647.) § 56-572. Dedication of assets. The responsible public entity shall terminate the operator's authority and duties under this chapter on the date set forth in the comprehensive agreement. Upon termination, the authority and duties of the operator under this chapter shall cease, and the qualifying transportation facility shall be dedicated to the responsible public entity or, if the qualifying transportation facility was initially dedicated by an affected local jurisdiction, to such affected local jurisdiction for public use. (1994, c. 855; 1995, c. 647.) § 56-573. Sovereign immunity. Nothing in this chapter shall be construed as or deemed a waiver of the sovereign immunity of the Commonwealth, any responsible public entity or any affected local jurisdiction or any officer or employee thereof with respect to the participation in, or approval of all or any part of the qualifying transportation facility or its operation, including but not limited to interconnection of the qualifying transportation facility with any other transportation facility. Counties, cities and towns in which a qualifying transportation facility is located shall possess sovereign immunity with respect to its construction and operation. (1994, c. 855; 1995, c. 647.) § 56-573.1. Procurement. The Virginia Public Procurement Act (§ 2.2-4300 et seq.) shall not apply to this chapter; however, a responsible public entity may enter into a comprehensive agreement only in accordance with procedures adopted by it as follows: 1. A responsible public entity may enter into a comprehensive agreement in accordance with procedures adopted by it that are consistent with procurement through "competitive sealed bidding" as defined in § 2.2-4301 and subsection B of § 2.2-4310. 2. A responsible public entity may enter into a comprehensive agreement in accordance with procedures adopted by it that are consistent with the procurement of "other than professional services" through competitive negotiation as defined in § 2.2-4301 and subsection B of § 2.2-4310. Such responsible public entity shall not be required to select the proposal with the lowest price offer, but may consider price as one factor in Page 135 of 325 42 evaluating the proposals received. A responsible public entity shall proceed in accordance with the procedures adopted by it pursuant to subdivision 1 unless it determines that proceeding in accordance with the procedures adopted by it pursuant to this subdivision is likely to be advantageous to the responsible public entity and the public, based on (i) the probable scope, complexity, or urgency of a project or (ii) risk sharing, added value, an increase in funding, or economic benefit from the project that would not otherwise be available. When the responsible public entity determines to proceed according to the procedures adopted by it pursuant to this subdivision, it shall state the reasons for its determination in writing. If a state agency is the responsible public entity, the approval of the Secretary of Transportation shall be required before the comprehensive agreement is signed. 3. Comprehensive agreements for maintenance or asset management services for a transportation facility that is a highway, bridge, tunnel or overpass, and any amendment or change order thereto that increases the highway lane-miles receiving services under such an agreement shall be procured in accordance with procedures that are consistent with procurement through "competitive sealed bidding" as defined in § 2.2-4301 and subsection B of § 2.2-4310. Furthermore, such contracts shall be of a size and scope to encourage maximum competition and participation by agency prequalified contractors and otherwise qualified contractors. 4. The provisions of subdivision 3 shall not apply to maintenance or asset management services agreed to as part of the initial provisions of any comprehensive agreement entered into for the original construction, reconstruction, or improvement of any highway pursuant to Chapter 22 (§ 56-556 et seq.) of Title 56. 5. Once a comprehensive agreement has been entered into, and the process of bargaining of all phases or aspects of the comprehensive agreement is complete, a responsible public entity shall make available, upon request, procurement records in accordance with § 2.2- 4342. 6. Nothing in this section shall require that professional services be procured by any method other than competitive negotiation in accordance with the Virginia Public Procurement Act (§ 2.2-4300 et seq.). (1995, c. 647; 2002, cc. 570, 593; 2003, c. 968.) § 56-573.2. Jurisdiction. The Commission shall have exclusive jurisdiction to adjudicate all matters specifically committed to its jurisdiction by this chapter. (1995, c. 647.) § 56-574. Preservation of the Virginia Highway Corporation Act of 1988. Nothing in this chapter shall be construed to repeal or change in any manner the Virginia Highway Corporation Act of 1988, as amended (§ 56-535 et seq.). Nothing in the Page 136 of 325 43 Virginia Highway Corporation Act of 1988, as amended, shall apply to qualifying transportation facilities undertaken pursuant to the authority of this chapter. (1994, c. 855; 1995, c. 647.) Page 137 of 325 44 Appendix B The Public-Private Education Facilities and Infrastructure Act of 2002, as amended Code of Virginia, 1950, As Amended § 56-575.1. Definitions. As used in this chapter, unless the context requires a different meaning: "Affected local jurisdiction" means any county, city or town in which all or a portion of a qualifying project is located. "Commission" means the State Corporation Commission. "Comprehensive agreement" means the comprehensive agreement between the private entity and the responsible public entity required by § 56-575.9. "Develop" or "development" means to plan, design, develop, finance, lease, acquire, install, construct, or expand. "Interim agreement" means an agreement between a private entity and a responsible public entity that provides for phasing of the development or operation, or both, of a qualifying project. Such phases may include, but are not limited to, design, planning, engineering, environmental analysis and mitigation, financial and revenue analysis, or any other phase of the project that constitutes activity on any part of the qualifying project. "Lease payment" means any form of payment, including a land lease, by a public entity to the private entity for the use of a qualifying project. "Material default" means any default by the private entity in the performance of its duties under subsection E of § 56-575.8 that jeopardizes adequate service to the public from a qualifying project. "Operate" means to finance, maintain, improve, equip, modify, repair, or operate. "Private entity" means any natural person, corporation, general partnership, limited liability company, limited partnership, joint venture, business trust, public benefit corporation, non-profit entity, or other business entity. "Public entity" means the Commonwealth and any agency or authority thereof, any county, city or town and any other political subdivision of the Commonwealth, any public body politic and corporate, or any regional entity that serves a public purpose. "Qualifying project" means (i) any education facility, including, but not limited to a school building, any functionally related and subordinate facility and land to a school building (including any stadium or other facility primarily used for school events), and any depreciable property provided for use in a school facility that is operated as part of the public school system or as an institution of higher education; (ii) any building or facility that meets a public purpose and is developed or operated by or for any public entity; (iii) any improvements, together with equipment, necessary to enhance public safety and security of buildings to be principally used by a public entity; (iv) utility and telecommunications and other communications infrastructure; (v) a recreational facility; (vi) technology infrastructure, including, but not limited to, telecommunications, Page 138 of 325 45 automated data processing, word processing and management information systems, and related information, equipment, goods and services; or (vii) any improvements necessary or desirable to any unimproved locally- or state-owned real estate. "Responsible public entity" means a public entity that has the power to develop or operate the applicable qualifying project. "Revenues" means all revenues, income, earnings, user fees, lease payments, or other service payments arising out of or in connection with supporting the development or operation of a qualifying project, including without limitation, money received as grants or otherwise from the United States of America, from any public entity, or from any agency or instrumentality of the foregoing in aid of such facility. "Service contract" means a contract entered into between a public entity and the private entity pursuant to § 56-575.5. "Service payments" means payments to the private entity of a qualifying project pursuant to a service contract. "State" means the Commonwealth of Virginia. "User fees" mean the rates, fees or other charges imposed by the private entity of a qualifying project for use of all or a portion of such qualifying project pursuant to the comprehensive agreement pursuant to § 56-575.9. (2002, c. 571; 2003, c. 1034; 2005, cc. 618, 865.) § 56-575.2. Declaration of public purpose. A. The General Assembly finds that: 1. There is a public need for timely acquisition, design, construction, improvement, renovation, expansion, equipping, maintenance, operation, implementation, or installation of education facilities, technology infrastructure and other public infrastructure and government facilities within the Commonwealth that serve a public need and purpose; 2. Such public need may not be wholly satisfied by existing methods of procurement in which qualifying projects are acquired, designed, constructed, improved, renovated, expanded, equipped, maintained, operated, implemented, or installed; 3. There are inadequate resources to develop new education facilities, technology infrastructure and other public infrastructure and government facilities for the benefit of citizens of the Commonwealth, and there is demonstrated evidence that public-private partnerships can meet these needs by improving the schedule for delivery, lowering the cost, and providing other benefits to the public; 4. Financial incentives exist under state and federal tax provisions that promote public entities to enter into partnerships with private entities to develop qualifying projects; 5. Authorizing private entities to develop or operate one or more qualifying projects may result in the availability of such projects to the public in a more timely or less costly fashion, thereby serving the public safety, benefit, and welfare. B. An action under § 56-575.4 shall serve the public purpose of this chapter if such action facilitates the timely development or operation of qualifying projects. Page 139 of 325 46 C. It is the intent of this chapter, among other things, to encourage investment in the Commonwealth by private entities and facilitate the bond financing provisions of the Economic Growth and Tax Relief Reconciliation Act of 2001 or other similar financing mechanisms, private capital and other funding sources that support the development or operation of qualifying projects, to the end that financing for qualifying projects be expanded and accelerated to improve and add to the convenience of the public, and such that public and private entities may have the greatest possible flexibility in contracting with each other for the provision of the public services that are the subject of this chapter. D. This chapter shall be liberally construed in conformity with the purposes hereof. (2002, c. 571; 2003, c. 1034; 2005, c. 865.) § 56-575.3. Prerequisite for operation of a qualifying project. A. Any private entity seeking authorization under this chapter to develop or operate a qualifying project shall first obtain approval of the responsible public entity under § 56- 575.4. Such private entity may initiate the approval process by requesting approval pursuant to subsection A of § 56-575.4 or the responsible public entity may request proposals or invite bids pursuant to subsection B of § 56-575.4. B. Any facility, building, infrastructure or improvement included in a proposal as a part of a qualifying project shall be identified specifically or conceptually. C. Upon receipt by the responsible public entity of a proposal submitted by a private entity initiating the approval process pursuant to subsection A of § 56-575.4, the responsible public entity shall determine whether to accept such proposal for consideration in accordance with § 56-575.16. If the responsible public entity determines not to accept for consideration the proposal submitted by the private entity pursuant to subsection A of § 56-575.4, it shall return the proposal, together with all fees and accompanying documentation, to the private entity. D. The responsible public entity may reject any proposal initiated by a private entity pursuant to subsection A of § 56-575.4 at any time. (2002, c. 571; 2003, cc. 292, 1034; 2005, c. 865.) § 56-575.3:1. Adoption of guidelines by responsible public entities. A. Any responsible public entity requesting or considering a proposal for a qualifying facility shall adopt and make publicly available guidelines that are sufficient to enable the responsible public entity to comply with this chapter. Such guidelines shall guide the selection of projects under the purview of the responsible public entity and include, but not be limited to, reasonable criteria for choosing among competitive proposals and timelines for selecting proposals and negotiating an interim or comprehensive agreement. B. Such guidelines shall permit accelerated selection, review and documentation timelines for proposals involving a qualifying facility that the responsible public entity deems a priority. (2005, c. 865.) Page 140 of 325 47 § 56-575.4. Approval of qualifying projects by the responsible public entity. A. A private entity may request approval of a qualifying project by the responsible public entity. Any such request shall be accompanied by the following material and information unless waived by the responsible public entity: 1. A topographic map (1:2,000 or other appropriate scale) indicating the location of the qualifying project; 2. A description of the qualifying project, including the conceptual design of such facility or facilities or a conceptual plan for the provision of services or technology infrastructure, and a schedule for the initiation of and completion of the qualifying project to include the proposed major responsibilities and timeline for activities to be performed by both the public and private entity; 3. A statement setting forth the method by which the private entity proposes to secure necessary property interests required for the qualifying project; 4. Information relating to the current plans for development of facilities or technology infrastructure to be used by a public entity that are similar to the qualifying project being proposed by the private entity, if any, of each affected local jurisdiction; 5. A list of all permits and approvals required for the qualifying project from local, state, or federal agencies and a projected schedule for obtaining such permits and approvals; 6. A list of public utility facilities, if any, that will be crossed by the qualifying project and a statement of the plans of the private entity to accommodate such crossings; 7. A statement setting forth the private entity's general plans for financing the qualifying project including the sources of the private entity's funds and identification of any dedicated revenue source or proposed debt or equity investment on the behalf of the private entity; 8. The names and addresses of the persons who may be contacted for further information concerning the request; 9. User fees, lease payments, and other service payments over the term of the interim or comprehensive agreement pursuant to § 56-575.9 or 56-575.9:1 and the methodology and circumstances for changes to such user fees, lease payments, and other service payments over time; and 10. Such additional material and information as the responsible public entity may reasonably request. B. The responsible public entity may request proposals or invite bids from private entities for the development or operation of qualifying projects. C. The responsible public entity may grant approval of the development or operation of the education facility, technology infrastructure or other public infrastructure or government facility needed by a public entity as a qualifying project, or the design or equipping of a qualifying project so developed or operated, if the responsible public entity determines that the project serves the public purpose of this chapter. The responsible public entity may determine that the development or operation of the qualifying project as a qualifying project serves such public purpose if: Page 141 of 325 48 1. There is a public need for or benefit derived from the qualifying project of the type the private entity proposes as a qualifying project; 2. The estimated cost of the qualifying project is reasonable in relation to similar facilities; and 3. The private entity's plans will result in the timely development or operation of the qualifying project. In evaluating any request, the responsible public entity may rely upon internal staff reports prepared by personnel familiar with the operation of similar facilities or the advice of outside advisors or consultants having relevant experience. D. The responsible public entity may charge a reasonable fee to cover the costs of processing, reviewing and evaluating the request, including without limitation, reasonable attorney's fees and fees for financial, technical, and other necessary advisors or consultants. E. The approval of the responsible public entity shall be subject to the private entity's entering into an interim or comprehensive agreement pursuant to § 56-575.9 with the responsible public entity. F. In connection with its approval of the qualifying project, the responsible public entity shall establish a date for the commencement of activities related to the qualifying project. The responsible public entity may extend such date from time to time. G. The responsible public entity shall take appropriate action to protect confidential and proprietary information provided by the private entity pursuant to an agreement under subdivision 11 of § 2.2-3705.6. H. Nothing in this chapter or in an interim or comprehensive agreement entered into pursuant to this chapter shall be deemed to enlarge, diminish or affect the authority, if any, otherwise possessed by the responsible public entity to take action that would impact the debt capacity of the Commonwealth. (2002, c. 571; 2003, c. 1034; 2004, c. 690; 2005, c. 865.) § 56-575.5. Service contracts. In addition to any authority otherwise conferred by law, any public entity may contract with a private entity for the delivery of services to be provided as part of a qualifying project in exchange for such service payments and other consideration as such public entity may deem appropriate. (2002, c. 571; 2005, c. 865.) § 56-575.6. Affected local jurisdictions. A. Any private entity requesting approval from, or submitting a proposal to, a responsible public entity under § 56-575.4 shall notify each affected local jurisdiction by furnishing a copy of its request or proposal to each affected local jurisdiction. B. Each affected local jurisdiction that is not a responsible public entity for the respective qualifying project shall, within sixty days after receiving such notice, submit any comments it may have in writing on the proposed qualifying project to the responsible Page 142 of 325 49 public entity and indicate whether the facility is compatible with the local comprehensive plan, local infrastructure development plans, the capital improvements budget, or other government spending plan. Such comments shall be given consideration by the responsible public entity prior to entering a comprehensive agreement pursuant to § 56- 575.9 with a private entity. (2002, c. 571.) § 56-575.7. Dedication of public property. Any public entity may dedicate any property interest, including land, improvements, and tangible personal property, that it has for public use in a qualifying project if it finds that so doing will serve the public purpose of this chapter by minimizing the cost of a qualifying project to the public entity or reducing the delivery time of a qualifying project. In connection with such dedication, a public entity may convey any property interest that it has, subject to the conditions imposed by general law governing such conveyances, to the private entity subject to the provisions of this chapter, for such consideration as such public entity may determine. The aforementioned consideration may include, without limitation, the agreement of the private entity to develop or operate the qualifying project. The property interests that the public entity may convey to the private entity in connection with a dedication under this section may include licenses, franchises, easements, or any other right or interest the public entity deems appropriate. (2002, c. 571; 2005, c. 865.) § 56-575.8. Powers and duties of the private entity. A. The private entity shall have all power allowed by law generally to a private entity having the same form of organization as the private entity and shall have the power to develop or operate the qualifying project and collect lease payments, impose user fees or enter into service contracts in connection with the use thereof. B. The private entity may own, lease or acquire any other right to use or operate the qualifying project. C. Any financing of the qualifying project may be in such amounts and upon such terms and conditions as may be determined by the private entity. Without limiting the generality of the foregoing, the private entity may issue debt, equity or other securities or obligations, enter into sale and leaseback transactions and secure any financing with a pledge of, security interest in, or lien on, any or all of its property, including all of its property interests in the qualifying project. D. In operating the qualifying project, the private entity may: 1. Make classifications according to reasonable categories for assessment of user fees; and 2. With the consent of the responsible public entity, make and enforce reasonable rules to the same extent that the responsible public entity may make and enforce rules with respect to similar facilities. Page 143 of 325 50 E. The private entity shall: 1. Develop or operate the qualifying project in a manner that is acceptable to the responsible public entity, all in accordance with the provisions of the interim or comprehensive agreement pursuant to § 56-575.9 or 56-575.9:1; 2. Keep the qualifying project open for use by the members of the public at all times, or as appropriate based upon the use of the facility, after its initial opening upon payment of the applicable user fees, lease payments, or service payments; provided that the qualifying project may be temporarily closed because of emergencies or, with the consent of the responsible public entity, to protect the safety of the public or for reasonable construction or maintenance activities. In the event that a qualifying project is technology infrastructure, access may be limited as determined by the conditions of the interim or comprehensive agreement; 3. Maintain, or provide by contract for the maintenance or upgrade of the qualifying project, if required by the interim or comprehensive agreement; 4. Cooperate with the responsible public entity in making best efforts to establish any interconnection with the qualifying project requested by the responsible public entity; and 5. Comply with the provisions of the interim or comprehensive agreement and any lease or service contract. F. Nothing shall prohibit an private entity of a qualifying project from providing additional services for the qualifying project to public or private entities other than the responsible public entity so long as the provision of additional service does not impair the private entity's ability to meet its commitments to the responsible public entity pursuant to the interim or comprehensive agreement as provided for in § 56-575.9 or 56-575.9:1. (2002, c. 571; 2003, c. 1034; 2005, c. 865.) § 56-575.9. Comprehensive agreement. A. Prior to developing or operating the qualifying project, the private entity shall enter into a comprehensive agreement with the responsible public entity. The comprehensive agreement shall provide for: 1. Delivery of maintenance, performance and payment bonds, letters of credit in connection with the development or operation of the qualifying project, in the forms and amounts satisfactory to the responsible public entity and in compliance with § 2.2-4337 for those components of the qualifying project that involve construction; 2. Review of plans and specifications for the qualifying project by the responsible public entity and approval by the responsible public entity if the plans and specifications conform to standards acceptable to the responsible public entity. This shall not be construed as requiring the private entity to complete design of a qualifying project prior to the execution of a comprehensive agreement; 3. Inspection of the qualifying project by the responsible public entity to ensure that the private entity's activities are acceptable to the responsible public entity in accordance with the provisions of the comprehensive agreement; Page 144 of 325 51 4. Maintenance of a policy or policies of public liability insurance (copies of which shall be filed with the responsible public entity accompanied by proofs of coverage) or self- insurance, each in form and amount satisfactory to the responsible public entity and reasonably sufficient to insure coverage of tort liability to the public and employees and to enable the continued operation of the qualifying project; 5. Monitoring of the practices of the private entity by the responsible public entity to ensure that the qualifying project is properly maintained; 6. Reimbursement to be paid to the responsible public entity for services provided by the responsible public entity; 7. Filing of appropriate financial statements on a periodic basis; and 8. Policies and procedures governing the rights and responsibilities of the responsible public entity and the private entity in the event the comprehensive agreement is terminated or there is a material default by the private entity. Such policies and guidelines shall include conditions governing assumption of the duties and responsibilities of the private entity by the responsible public entity and the transfer or purchase of property or other interests of the private entity by the responsible public entity. B. The comprehensive agreement shall provide for such user fees, lease payments, or service payments as may be established from time to time by agreement of the parties. A copy of any service contract shall be filed with the responsible public entity. In negotiating user fees under this section, the parties shall establish payments or fees that are the same for persons using the facility under like conditions and that will not materially discourage use of the qualifying project. The execution of the comprehensive agreement or any amendment thereto shall constitute conclusive evidence that the user fees, lease payments, or service payments provided for comply with this chapter. User fees or lease payments established in the comprehensive agreement as a source of revenues may be in addition to, or in lieu of, service payments. C. In the comprehensive agreement, the responsible public entity may agree to make grants or loans to the private entity from time to time from amounts received from the federal, state, or local government or any agency or instrumentality thereof. D. The comprehensive agreement shall incorporate the duties of the private entity under this chapter and may contain such other terms and conditions that the responsible public entity determines serve the public purpose of this chapter. Without limitation, the comprehensive agreement may contain provisions under which the responsible public entity agrees to provide notice of default and cure rights for the benefit of the private entity and the persons specified therein as providing financing for the qualifying project. The comprehensive agreement may contain such other lawful terms and conditions to which the private entity and the responsible public entity mutually agree, including, without limitation, provisions regarding unavoidable delays or provisions providing for a loan of public funds to the private entity to develop or operate one or more qualifying projects. The comprehensive agreement may also contain provisions where the authority and duties of the private entity under this chapter shall cease, and the qualifying project is dedicated to the responsible public entity or, if the qualifying project was initially dedicated by an affected local jurisdiction, to such affected local jurisdiction for public use. Page 145 of 325 52 E. Any changes in the terms of the comprehensive agreement, as may be agreed upon by the parties from time to time, shall be added to the comprehensive agreement by written amendment. F. When a responsible public entity that is not an agency or authority of the Commonwealth enters into a comprehensive agreement pursuant to this chapter, it shall within 30 days thereafter submit a copy of the comprehensive agreement to the Auditor of Public Accounts. G. The comprehensive agreement may provide for the development or operation of phases or segments of the qualifying project. (2002, c. 571; 2003, c. 1034; 2004, c. 986; 2005, c. 865.) § 56-575.9:1. Interim agreement. Prior to or in connection with the negotiation of the comprehensive agreement, the responsible public entity may enter into an interim agreement with the private entity proposing the development or operation of the qualifying project. Such interim agreement may (i) permit the private entity to commence activities for which it may be compensated relating to the proposed qualifying project, including, but not limited to, project planning and development, design and engineering, environmental analysis and mitigation, survey, and ascertaining the availability of financing for the proposed facility or facilities; (ii) establish the process and timing of the negotiation of the comprehensive agreement; and (iii) contain any other provisions related to any aspect of the development or operation of a qualifying project that the parties may deem appropriate. (2005, c. 865.) § 56-575.10. Federal, state and local assistance. A. Any financing of a qualifying facility may be in such amounts and upon such terms and conditions as may be determined by the parties to the interim or comprehensive agreement. Without limiting the generality of the terms and conditions of the financing, the private entity and the responsible public entity may propose to utilize any and all funding resources that may be available to them and may, to the fullest extent permitted by applicable law, issue debt, equity, or other securities or obligations, enter into leases, access any designated trust funds, borrow or accept grants from any state infrastructure bank, and secure any financing with a pledge of, security interest in, or lien on, any or all of its property, including all of its property interests in the qualifying facility. B. The responsible public entity may take any action to obtain federal, state, or local assistance for a qualifying project that serves the public purpose of this chapter and may enter into any contracts required to receive such assistance. If the responsible public entity is a state agency, any funds received from the state or federal government or any agency or instrumentality thereof shall be subject to appropriation by the General Assembly. The responsible public entity may determine that it serves the public purpose of this chapter for all or any portion of the costs of a qualifying project to be paid, directly or indirectly, from the proceeds of a grant or loan made by the local, state, or federal government or any agency or instrumentality thereof. (2002, c. 571; 2005, c. 865.) Page 146 of 325 53 § 56-575.11. Material default; remedies. A. In the event of a material default by the private entity, the responsible public entity may elect to assume the responsibilities and duties of the private entity of the qualifying project, and in such case, it shall succeed to all of the right, title and interest in such qualifying project, subject to any liens on revenues previously granted by the private entity to any person providing financing thereof. B. Any responsible public entity having the power of condemnation under state law may exercise such power of condemnation to acquire the qualifying project in the event of a material default by the private entity. Any person who has provided financing for the qualifying project, and the private entity, to the extent of its capital investment, may participate in the condemnation proceedings with the standing of a property owner. C. The responsible public entity may terminate, with cause, the interim or comprehensive agreement and exercise any other rights and remedies that may be available to it at law or in equity. D. The responsible public entity may make or cause to be made any appropriate claims under the maintenance, performance, or payment bonds; or lines of credit required by subsection A 1 of § 56-575.9. E. In the event the responsible public entity elects to take over a qualifying project pursuant to subsection A, the responsible public entity may develop or operate the qualifying project, impose user fees, impose and collect lease payments for the use thereof and comply with any service contracts as if it were the private entity. Any revenues that are subject to a lien shall be collected for the benefit of and paid to secured parties, as their interests may appear, to the extent necessary to satisfy the private entity's obligations to secured parties, including the maintenance of reserves. Such liens shall be correspondingly reduced and, when paid off, released. Before any payments to, or for the benefit of, secured parties, the responsible public entity may use revenues to pay current operation and maintenance costs of the qualifying project, including compensation to the responsible public entity for its services in operating and maintaining the qualifying project. The right to receive such payment, if any, shall be considered just compensation for the qualifying project. The full faith and credit of the responsible public entity shall not be pledged to secure any financing of the private entity by the election to take over the qualifying project. Assumption of operation of the qualifying project shall not obligate the responsible public entity to pay any obligation of the private entity from sources other than revenues. (2002, c. 571; 2003, c. 1034; 2005, c. 865.) § 56-575.12. Condemnation. At the request of the private entity, the responsible public entity may exercise any power of condemnation that it has under law for the purpose of acquiring any lands or estates or interests therein to the extent that the responsible public entity finds that such action serves the public purpose of this chapter. Any amounts to be paid in any such condemnation proceeding shall be paid by the private entity. (2002, c. 571; 2005, c. 865.) Page 147 of 325 54 § 56-575.13. Utility crossing. The private entity and each public service company, public utility, railroad, and cable television provider, whose facilities are to be crossed or affected shall cooperate fully with the other entity in planning and arranging the manner of the crossing or relocation of the facilities. Any such entity possessing the power of condemnation is hereby expressly granted such powers in connection with the moving or relocation of facilities to be crossed by the qualifying project or that must be relocated to the extent that such moving or relocation is made necessary or desirable by construction of, renovation to, or improvements to the qualifying project, which shall be construed to include construction of, renovation to, or improvements to temporary facilities for the purpose of providing service during the period of construction or improvement. Any amount to be paid for such crossing, construction, moving or relocating of facilities shall be paid for by the private entity. Should the private entity and any such public service company, public utility, railroad, and cable television provider not be able to agree upon a plan for the crossing or relocation, the Commission may determine the manner in which the crossing or relocation is to be accomplished and any damages due arising out of the crossing or relocation. The Commission may employ expert engineers who shall examine the location and plans for such crossing or relocation, hear any objections and consider modifications, and make a recommendation to the Commission. In such a case, the cost of the experts is to be borne by the private entity. Such determination shall be made by the Commission within ninety days of notification by the private entity that the qualifying project will cross utilities subject to the Commission's jurisdiction. (2002, c. 571; 2005, c. 865.) § 56-575.14. Police powers; violations of law. All police officers of the Commonwealth and of each affected local jurisdiction shall have the same powers and jurisdiction within the limits of such qualifying project as they have in their respective areas of jurisdiction and such police officers shall have access to the qualifying project at any time for the purpose of exercising such powers and jurisdiction. (2002, c. 571.) § 56-575.15. Sovereign immunity. Nothing in this chapter shall be construed as or deemed a waiver of the sovereign immunity of the Commonwealth, any responsible public entity or any affected local jurisdiction or any officer or employee thereof with respect to the participation in, or approval of all or any part of the qualifying project or its operation, including but not limited to interconnection of the qualifying project with any other infrastructure or project. Counties, cities and towns in which a qualifying project is located shall possess sovereign immunity with respect to its design, construction, and operation. (2002, c. 571.) § 56-575.16. Procurement. The Virginia Public Procurement Act (§ 2.2-4300 et seq.) and any interpretations, regulations, or guidelines of the Division of Engineering and Buildings of the Department of General Services or the Virginia Information Technologies Agency, including the Page 148 of 325 55 Capital Outlay Manual and those interpretations, regulations or guidelines developed pursuant to §§ 2.2-1131, 2.2-1132, 2.2-1133, 2.2-1149, and 2.2-1502, except those developed by the Division or the Virginia Information Technologies Agency in accordance with this chapter when the Commonwealth is the responsible public entity, shall not apply to this chapter. However, a responsible public entity may enter into a comprehensive agreement only in accordance with guidelines adopted by it as follows: 1. A responsible public entity may enter into a comprehensive agreement in accordance with guidelines adopted by it that are consistent with procurement through competitive sealed bidding as defined in § 2.2-4301 and subsection B of § 2.2-4310. 2. A responsible public entity may enter into a comprehensive agreement in accordance with guidelines adopted by it that are consistent with the procurement of "other than professional services" through competitive negotiation as defined in § 2.2-4301 and subsection B of § 2.2-4310. Such responsible public entity shall not be required to select the proposal with the lowest price offer, but may consider price as one factor in evaluating the proposals received. Other factors that may be considered include (i) the proposed cost of the qualifying facility; (ii) the general reputation, industry experience, and financial capacity of the private entity; (iii) the proposed design of the qualifying project; (iv) the eligibility of the facility for accelerated selection, review, and documentation timelines under the responsible public entity's guidelines; (v) local citizen and government comments; (vi) benefits to the public; (vii) the private entity's compliance with a minority business enterprise participation plan or good faith effort to comply with the goals of such plan; (viii) the private entity's plans to employ local contractors and residents; and (ix) other criteria that the responsible public entity deems appropriate. A responsible public entity shall proceed in accordance with the guidelines adopted by it pursuant to subdivision 1 unless it determines that proceeding in accordance with the guidelines adopted by it pursuant to this subdivision is likely to be advantageous to the responsible public entity and the public, based on (i) the probable scope, complexity or priority of the project; (ii) risk sharing including guaranteed cost or completion guarantees, added value or debt or equity investments proposed by the private entity; or (iii) an increase in funding, dedicated revenue source or other economic benefit that would not otherwise be available. When the responsible public entity determines to proceed according to the guidelines adopted by it pursuant to this subdivision, it shall state the reasons for its determination in writing. If a state agency is the responsible public entity, the approval of the responsible Governor's Secretary, or the Governor, shall be required before the responsible public entity may enter into a comprehensive agreement pursuant to this subdivision. 3. Nothing in this chapter shall authorize or require that a responsible public entity obtain professional services through any process except in accordance with guidelines adopted by it that are consistent with the procurement of "professional services" through competitive negotiation as defined in § 2.2-4301 and subsection B of § 2.2-4310. 4. A responsible public entity shall not proceed to consider any request by a private entity for approval of a qualifying project pursuant to subsection A of § 56-575.4 until the responsible public entity has adopted and made publicly available guidelines that are sufficient to enable the responsible public entity to comply with this chapter. Such guidelines shall: Page 149 of 325 56 a. If the responsible public entity is not an agency or authority of the Commonwealth, require the responsible public entity to engage the services of qualified professionals, which may include an architect, professional engineer or certified public accountant, not employed by the responsible public entity to provide to the responsible public entity independent analysis regarding the specifics, advantages, disadvantages, and the long- and short-term costs of any request by a private entity for approval of a qualifying project, unless the governing body of the responsible public entity determines that such analysis of a request by a private entity for approval of a qualifying project shall be performed by employees of the responsible public entity. b. Provide for the posting and publishing of public notice of a private entity's request for approval of a qualifying project pursuant to subsection A of § 56-575.4 and a reasonable time period, determined by the responsible public entity to be appropriate to encourage competition and public-private partnerships pursuant to the goals of this chapter, such reasonable period not to be less than 45 days, during which the responsible public entity will receive competing proposals pursuant to that subsection. Such guidelines shall also require advertising the public notice in the Virginia Business Opportunities publication and posting a notice on the Commonwealth's electronic procurement website. 5. Once a comprehensive agreement has been entered into, and the process of bargaining of all phases or aspects of the comprehensive agreement is complete, a responsible public entity shall make available, upon request, procurement records in accordance with § 2.2- 4342. 6. A responsible public entity that is a school board or a county, city or town may enter into an interim or comprehensive agreement under this chapter only with the approval of the local governing body. (2002, c. 571; 2003, cc. 292, 968, 1034; 2004, c. 986; 2005, c. 865.) Page 150 of 325 57 APPENDIX C Projected Procurement Timeline for PPTA/PPEA Procurement Initiated By Unsolicited Proposal Activity Number Date Activity 1 D Receipt of Unsolicited Proposal 2 D+45 Decide whether to accept Unsolicited Proposal, whether to use competitive negotiation, and what conditions to impose 3 D+75 Prepare Notice of Unsolicited Proposal, Receipt of Unsolicited Proposal, and Post and Publish 4. D+135 Receive Competing Conceptual-Phase Proposals 5 D+195 Evaluate Conceptual-Phase Proposals, decide whether to proceed. If proceeding, select proposers to invite to submit, and invite submission of Detailed-Phase Proposals 6 D+225 Receive Detailed- Phase Proposals 7.6. D+270 Evaluate Detailed- Phase Proposals, conduct interviews, and select proposers for negotiation of Agreement 8.7 D+315 Negotiate Interim Agreement or Comprehensive Agreement 9 D+350 Obtain Approval by City Council Page 151 of 325 APPENDIX D Projected Procurement Timeline for PPTA/PPEA Procurement Solicited By Request for Proposals (“RFP”) Activity Number Date Activity 1 D Initiate procurement. Decide whether to use competitive negotiation and issue RFP. 2 D+45 Receive Conceptual-Phase Proposals 3 D+105 Evaluate Conceptual-Phase Proposals and decide whether to proceed. Select proposers to invite to submit, and invite submission of Detailed-Phase Proposals 4. D+135 Receive Detailed- Phase Proposals 5 D+180 Evaluate Detailed- Phase Proposals, conduct interviews, and select proposers for negotiation of Agreement 6 D+225 Negotiate Interim Agreement or Comprehensive Agreement 7 D+270 Obtain Approval by City Council Note: Considerable planning befor e Step 1 is required to determine the City's needs for a project and to state them in an RFP. Page 152 of 325 59 Appendix E Potential Proposal Evaluation and Selection Criteria A. Qualifications and Experience Does the proposer propose a team which is qualified, led, and structured in a manner which will clearly enable the team to complete the proposed project? 1. Experience with Similar Projects Have members of this team previously worked together in successfully constructing, improving or managing similar projects? Has the lead firm managed, or any of the member firms worked on, a similar privatization project? 2. Demonstration of Ability to Perform Work What commitments has the team made to carry out the project? Does the team possess the necessary financial, staffing, equipment, and technical resources to successfully complete the project? Does the team and/or member firms have competing financial or workforce commitments that may inhibit success and follow-through on this project? 3. Leadership Structure Is one firm designated as lead on the project? Does the organization of the team indicate a well thought out approach to managing the project? Is there an agreement/document in place between members? 4. Project Manager's Experience Is a Project Manager identified, and does this person work for the principal firm? If not, is there a clear definition of the role and responsibility of the Project Manager relative to the member firms? Does the Project Manager have experience leading this type and magnitude of project? 5. Management Approach Have the primary functions and responsibilities of the management team been identified? Have the members of the team developed an approach to facilitate communication among the project participants? Has the firm adequately described its approach to communicating with and meeting the expectations of the City? 6. Financial Condition Is the financial information submitted on the firms sufficient to determine the firms' capability to fulfill their obligations described in the project proposal? 7. Project Ownership Does the proposal identify the proposed ownership arrangements for each phase of the project and indicate assumptions on legal liabilities and responsibilities during each phase of the project? Page 153 of 325 60 8. Participation of Small Busi nesses and Businesses Owned by Women and Minorities What is the level of commitment by the proposers to use small, minority-, and women-owned business enterprises in developing and implementing the project? 9. Competitive Bidding To what extent have adequate and transparent procurement policies been adopted by the proposer to maximize competitive bidding opportunities for potential subcontractors and suppliers? B. Project Characteristics Does the proposed project serve a public purpose as required by the Acts? Is the project technically feasible? 1. Project Definition Is the project described in sufficient detail to determine the type and size of the project and its location? 2. Proposed Project Schedule Is the time frame for project completion clearly outlined? Is the proposed schedule reasonable given the scope and complexity of the project? Does the proposal contain adequate assurances that the project will be completed and will be completed on time? 3. Operation Does the proposer present a reasonable statement setting forth plans for operation of the facility? 4. Technology Is the proposal based on proven technology? What is the degree of technical innovation associated with the proposal? Will the knowledge or technology gained from the project benefit other areas of the state or nation, as well as the City? Does the technology proposed maximize interoperability with relevant local and statewide technology? Can the proposed project upgrade relevant local technology? 5. Conforms to Laws, Regulations, and Standards Is the proposed project consistent with applicable state and federal statutes and regulations, or reasonably anticipated modifications of state or federal statutes, regulations or standards? Does the proposed design meet appropriate state and federal standards? 6. Federal Permits Is the project outside the purview of federal oversight, or will it require some level of federal involvement or permitting? Page 154 of 325 61 7. Meets/Exceeds Environmental Standards Is the proposed project consistent with applicable state and federal environmental statutes and regulations? Does the proposed design meet applicable state environmental standards? Does the proposal adequately address or improve air quality conformity? 8. State and Local Permits Does the proposal list the required permits and a schedule to obtain them? Are there negative impacts known for the project? If so, is there a mitigation plan identified? Are alternatives to standards or regulations needed to avoid those impacts that cannot be mitigated? 9. Property Acquisition Does the proposal set forth the method by which the private operator proposes to secure all property interests required for the facility? Does the statement include: the names and addresses, if known, of the current owners of the property needed for the facility, the nature of the property to be acquired, and a listing of any property that the City is expected to be requested to condemn? 10. Maintenance Does the proposer have a plan to maintain the facility in conformance with City standards? Does the proposal clearly define assumptions or responsibilities during the operational phase? C. Project Financing Has the proposer provided a financial plan and financial guarantees which will allow for access to the necessary capital to finance the facility? 1. Financing Did the proposer demonstrate evidence of its ability and commitment to provide sufficient equity in the project as well as the ability to obtain the other necessary financing? 2. Financial Plan Does the financial plan demonstrate a reasonable basis for funding project development and operations? Are the assumptions on which the plan is based well defined and reasonable in nature? Are the plan's risk factors identified and dealt with sufficiently? Are the planned sources of funding and financing realistic? Does the proposer make a financial contribution to the project? 3. Estimated Cost Is the estimated cost of the facility reasonable in relation to the cost of similar projects? The final determination will depend, to a large extent, on a cost/benefit analysis. Page 155 of 325 62 4. Life Cycle Cost Analysis Does the proposal include an appropriately conducted analysis of projected rate of return and life-cycle cost estimate of the proposed project and/or facility? 5. Business Objective Does the proposer clearly outline its reason for pursuing this project? Do the proposer’s assumptions appear reasonable? D. Public Support Has the proposer garnered sufficient public support for the proposed project? 1. Community Benefits Will this project bring a significant benefit to the City, the region, and/or the state? Are there ancillary benefits to the City because of the project? 2. Community Support What is the extent of support or opposition for the project? Does the project proposal demonstrate an understanding of City and regional issues and needs, as well as the impacts the project may have on those needs? Is there a demonstrated ability to work with the City? Have all affected local jurisdictions provided a clear written statement of the extent of their support for the project? 3. Public Involvement Strategy What strategies are proposed to involve local and state elected officials in developing the project? What level of community involvement has been identified for the project? Is there a clear strategy for informing, educating and obtaining community input through the development and life of the project? E. Project Compatibility Is the proposed project compatible with the City's master plan, local comprehensive plans, local infrastructure development plans, the capital improvements budget or other government spending plans? 1. Compatibility with the Ex isting Transportation System Does the project propose improvements that are compatible with the present and planned transportation system? Does the project provide continuity with existing and planned state and local facilities? 2. Fulfills Po licies and Goals Does the proposed project help achieve performance, safety, mobility or transportation demand management goals? Does the project improve connections among the transportation modes? 3. Enhance Community-Wide Transportation System Are there identified project benefits to the affected community transportation system? Does this project enhance adjacent transportation facilities? Page 156 of 325 63 4. Consistency with Local, Regi onal and State Transportation Plans Is the project consistent with the City’s comprehensive plan and regional and state transportation plans? If not, are steps proposed that will achieve consistency with such plans? 5. Economic Development Will the proposed project enhance the City’s, the region’s and the state's economic development efforts? Is the project critical to attracting or maintaining competitive industries and businesses to the City or region, consistent with stated objectives? 6. Impacts on Other Facilities Have crossings or other impacts on facilit ies of public service companies, public or private utilities, railroads and cable television prov iders, that may be affected by the project, been addressed? If a tran sportation project, are all proposed interconnections with other transportation fa cilities, the communities that may be affected, and alternatives (e.g. alig nments) that may need to be evaluated identified? Page 157 of 325 64 Appendix F Proposer’s Certification Proposer’s Name: _______________________ _______________________ Proposer’s Address Proposer’s: ______________________________ Telephone No.: ________________ ______________________________ Facsimile No.: ________________ ______________________________ E-mail Addr ess: ________________ Proposer’s or Proposer’s Contractor’s Virginia Class A General Contractor’s License Number ____________________________ Proposer’s or Proposer’s Architects and Engineers Virginia Registration Numbers: _________________________________ After first being placed under oath, I hereby certify that I have authority to submit this proposal on behalf of the proposer whose name appears above, that I am a principal of the proposer, that the proposer hereby agrees to all of the terms and conditions in The City of Lynchburg, Virginia, Implementation Procedures and Guidelines for the Public-Private Transportation Act of 1995 and the Public-Private Education Facilities and Infrastructure Act of 2002, as amended, that neither the proposer nor any member of its team or their principals is currently suspended or debarred from public contracting by any federal, state or local government entity, that I have taken reasonable steps to ascertain the accuracy of all the information contained in this proposal and this certification, and that the information in this proposal and certification is accurate to the best of my knowledge or information and belief. ______ _____________________ Signature ______ ______________________ P r i n t e d / T y p e d N a m e ______ ______________________ Title (Principal of Proposer) Page 158 of 325 65 Commonwealth of Virginia : : T o w i t County/City of __________ : On ______________, 200_, ________________, (same name as above) appeared before me, and after satisfying me of his/her identity and after being placed under oath, swore to the truthfulness of the above statement. ______ _____________________ N o t a r y P u b l i c My commission expires: _______________________ (If applicable) the proposer acknowledges receipt of the following agenda: Addendum No.: ______ Dated: ____________ Addendum No.: ______ Dated: ____________ Addendum No.: ______ Dated: ____________ Addendum No.: ______ Dated: ____________ Page 159 of 325 City Council Agenda Item VI.9. Action AGENDA ITEM SUMMARY MEETING DATE PRESENTED BY April 23, 2024 Gregory Wormser, Fire Chief AGENDA ITEM # VI.9 Consideration of adopting Resolution #R-24-___ approving the Revised Emergency Operations Plan. RECOMMENDATION Adopt the revised Emergency Operations Plan SUMMARY The City’s current Emergency Operations Plan (EOP) was originally adopted by City Council on April 23, 2002. It was revised and adopted on February 14, 2012, January 26, 2016, and January 28, 2020. The City is required to revise and adopt the plan every four years. Overall, the plan has served the City well through numerous planned and unplanned events. The proposed EOP is an incorporation of best practices from the previous plan, input from the Emergency Policy Team, Emergency Support Functions (ESFs), and Fire Department staff. The most noteworthy changes include: • Transition of Emergency Management responsibilities from Emergency Services to Fire Department • Greater emphasis on provisions to ensure that the plan is applied equitably and that the needs of minority and vulnerable communities are met during emergencies • Greater emphasis on management of potential cybersecurity incidents • Additional policies and information as a result of lessons learned since update in 2020 PRIOR ACTION(S) April 23, 2002: City Council adopted the original EOP February 14, 2012: City Council adopted the revised EOP January 26, 2016: City Council adopted the revised EOP January 28, 2020: City Council adopted the revised EOP FISCAL IMPACT Adoption of the EOP is required for the City to be eligible for various grants and funding opportunities. Page 160 of 325 CONTACT(S) Gregory Wormser, Fire Chief Piper Vandeperre, Emergency Program Specialist ATTACHMENT(S) 1. 2024 EOP Update - Option A - with Special Meeting Language 2. 2024 EOP Update - Option B - without Special Meeting Language 3. Resolution to Adopt Revised EOP 2024 (Option A) 4. Resolution to Adopt Revised EOP 2024 (Option B) REVIEWED BY Date: April 18, 2024 Gregory Wormser, Fire Chief Date: April 18, 2024 Mercedes Braun, Assistant to the City Manager Date: April 18, 2024 Wynter Benda, City Manager Date: April 18, 2024 Alicia Finney, Clerk of Council Page 161 of 325 Page 162 of 325 ii | Page EMERGENCY OPERATIONS PLAN RECORD OF CHANGES DATE CHANGE DESCRIPTION February 14, 2012 City Council adopted the Emergency Operations Plan February 14, 2014 Kimball Payne, City Manager, approves administrative changes to the Emergency Operations Plan January 26, 2016 City Council adopted the revised Emergency Operations Plan January 28, 2020 City Council adopted the revised Emergency Operations Plan April 23, 2024 City Council adopted the revised Emergency Operations Plan Page 163 of 325 iii | Page The 2009 Session of the General Assembly introduced legislation amending Code of Virginia, § 44-146.18, which was signed into law with an effective date of July 1, 2009, which states: “… shall include the requirement for a provision that the Department of Criminal Justice Services (DCJS) and the Virginia Criminal Injuries Compensation Fund (VCICF) be contacted immediately to deploy assistance in the event of an emergency as defined in the emergency response plan when there are victims as defined in §19.2-11.01 [re.: Crime Victim and Witness Rights], as well as current contact information for both.” Contact information: Criminal Injury Compensation Fund (Virginia Victims Fund) P.O. Box 26927 Richmond, VA 23261 Phone: 1-800-552-4007 Email: info@virginiavictimsfund.org Website: http://www.cicf.state.va.us/content/victims-crime-virginia Virginia Department of Criminal Justice Services 1100 Bank Street Richmond, VA 23219 DCJS Main Line: (804) 786-4000 This document was prepared by the City of Lynchburg, Virginia Lynchburg Fire Department Division of Emergency Management Department of Communications and Public Engagement May be used with permission. Page 164 of 325 iv | Page TABLE OF CONTENTS EXECUTIVE SUMMARY 1 Introduction 1 Team Roles and Responsibilities 2 Activation of the Emergency Operations Plan (EOP) 4 Colleges and Universities 4 Incident Management Organizational Chart 5 Fair and Equal Support for all Persons and Communities 5 EMERGENCY OPERATIONS PLAN 7 Introduction 7 Roles, Responsibilities, and Authorities 8 City Manager and City Council Roles and Responsibilities 8 Emergency Policy Team 9 Emergency Operations Team and Emergency Operations Center 10 Emergency Operations Center Planning Team 12 Emergency Support Functions 12 Emergency Support Functions Chart 13 City of Lynchburg Departments Chart 13 Emergency Operations Center Plan 14 Operational Period Planning Cycle Chart 16 Additional Resources Coordinated by the EOC 17 INCIDENT MANAGEMENT 19 Unified Command 19 Transfer of Incident Authority 20 Strategic Management Team Staff Positions and Liaison Officers 20 Hazard Type/Lead Incident Command Agency Chart 21 On-Scene Incident Command General Staff Positions 22 Operational Period Planning Cycle 22 CITY OF LYNCHBURG DEPARTMENTS, AGENCIES, AND NON-GOVERNMENTAL ORGANIZATIONS 26 CITY OF LYNCHBURG ACTIVATION OF THE EMERGENCY OPERATIONS PLAN 27 CONSENT TO CITY MANAGER’S DECLARATION OF EMERGENCY FORM 29 EMERGENCY SUPPORT FUNCTIONS CHART 30 Page 165 of 325 v | Page TABLE OF CONTENTS #1 TRANSPORTATION 31 #2 COMMUNICATIONS 34 #3 PUBLIC WORKS AND WATER RESOURCES 36 #4 FIRE FIGHTING 40 #5 EMERGENCY MANAGEMENT 42 #6 MASS CARE, HOUSING, AND HUMAN SERVICES 44 #7 RESOURCE SUPPORT 47 #8 PUBLIC HEALTH AND MEDICAL SERVICES 49 #9 URBAN SEARCH AND RESCUE 52 #10 OIL AND HAZARDOUS MATERIALS 54 #11 AGRICULTURE AND NATURAL RESOURCES 56 #12 ENERGY 59 #13 PUBLIC SAFETY AND SECURITY 61 #14 LONG-TERM COMMUNITY RECOVERY AND MITIGATION 64 #15 EXTERNAL AFFAIRS 69 #16 EMPLOYEE SUPPORT 72 #17 VOLUNTEER AND DONATIONS MANAGEMENT 74 Page 166 of 325 Page 167 of 325 1 | Page EXECUTIVE SUMMARY INTRODUCTION To respond effectively to any emergency of a size or complexity beyond routine responsibilities, it is critical that all City of Lynchburg employees, public officials, departments, agencies, non-governmental emergency organizations and the public understand their roles and responsibilities. These additional responsibilities become particularly important as incident command organizes beyond the initial response phase. The foundation for this coordinated response is established through the City of Lynchburg Comprehensive Emergency Management Program and its component Emergency Operations Plan (EOP). The EOP identifies the departments and agencies that are responsible for providing command and coordination capabilities for large-scale or unusual events, and describes how the multiple command and response components are organized and managed. It provides the framework to mitigate, prepare for, respond to, and recover from any emergency or disaster. This EOP uses a multi-agency team approach and operates under a structure based upon the principles of the Incident Command System (ICS)/National Incident Management System (NIMS) to manage, coordinate and direct resources committed to an incident. The Incident Command System is the combination of facilities, equipment, personnel, procedures and communications systems operating within a common organizational structure. This system is commonly recognized among federal, state and local jurisdictions. The City Manager, as the Chief Administrative Officer and the senior management professional in the City of Lynchburg government, is designated as the Director of Emergency Management. The City Manager reports to the seven-member City Council. The Mayor of the Council serves as the City’s chief elected official. The following teams report directly to the City Manager and advise him/her in pre-emergency planning, emergency and incident command and recovery: • Emergency Policy Team • Emergency Operations Team • Strategic Management Team Page 168 of 325 2 | Page TEAM ROLES AND RESPONSIBILITIES The following briefly describes the roles and responsibilities of the City Manager and of each team during an emergency. For detailed information about each team’s duties, please see the appropriate sections following this summary. City Council The City Council holds authority over policy and political activities concerning emergencies. It bears the direct responsibility for approving an Emergency Declaration issued by the City Manager or their designee. While Council entrusts emergency management and oversight to the City Manager, Council is required to ratify the Emergency Declaration within a timeframe of fourteen days. Council also formally declares an end to the emergency. Mayor The Mayor of the City Council serves as the City’s chief elected official. During an emergency, the Mayor serves as spokesperson for the City and coordinates with other elected officials at the regional and state levels including the Congressional delegation. The Mayor also conducts any other activities required of the chief elected official. City Manager During an emergency the City Manager provides policy implementation and administration, monitors the response of City agencies for adequacy, delegates authority for management of the situation, fulfills all legal requirements of an emergency declaration, and addresses other issues at the City Manager level. Emergency Policy Team The Emergency Policy Team advises the City Manager in pre-emergency planning, and emergency and incident command and recovery, while focusing on policy and providing oversight advice to the City Manager. It operates within the City’s hierarchical structure as an independent subcommittee of the City Manager’s Leadership Team (LT). The Emergency Policy Team includes: • City Manager (Chair) • Deputy City Manager (Chair in the City Manager’s Absence) • Fire Chief (serves as the Emergency Policy Team Planning Leader) • Police Chief • Director, Emergency Communications Center • Director, Department of Human Services • Director, Department of Water Resources • Director, Department of Public Works • Director, Department of Communications and Public Engagement • Director, Department of Information Technology • Superintendent of City Schools/Designee Emergency Operations Team The Emergency Operations Team is the functional organization that manages the Emergency Operations Center (EOC) during an emergency. This team coordinates and manages City-wide assets beyond the incident and oversees the coordination of the Emergency Support Functions (ESF). The Fire Chief or designee serves as the EOC Director. Other Emergency Operations Team positions may include: • Deputy EOC Director • Safety Officer • Senior Liaison • Senior Advisors • EOC Watch Officer • Command and General Staff Aide(s) • Planning and Finance Team Leaders Page 169 of 325 3 | Page The Emergency Operations Team is responsible for all strategic emergency management operations away from the incident site. These responsibilities include: 1. Directly support the Strategic Management Team, providing resources that are not available through the established incident command system operating in the specific event. This includes coordinating assistance from outside resources (federal, state, and other local jurisdictions) that is not obtained through tactical mutual aid or other incident-level command processes. 2. Directly manage emergency issues related to the incident, but outside the defined scope of the incident as delineated by the Strategic Management Team. Usually, this will entail maintaining or restoring essential City services during an emergency, avoiding or minimizing casualties and property damage, and addressing financial and other major impacts as soon as possible following the onset of an emergency or disaster situation. 3. Provide information integration between the Strategic Management Team and the City Manager and City Council. The Emergency Operations Team raises policy questions and communicates decisions made by the City Manager to the appropriate Emergency Support Functions or other sections and the Strategic Management Team. Emergency Support Functions (ESF) Emergency Support Functions (ESF) operate out of the EOC and provide resources to support both the Strategic Management and the Emergency Operations Teams. The Emergency Operations Team monitors the activities of Emergency Support Functions. Emergency Operations Center Plan The Emergency Operations Center Plan designates command and support staff positions to operate the EOC. Procedures for these support operations are established and maintained in a separate Emergency Operations Center Standard Operation Procedures manual, located in the EOC. In an emergency, activation of the EOC is initiated by the on-duty Emergency Communications Center Supervisor who will notify the Director of the Emergency Communications Center (ECC). The Director of the ECC will notify the Fire Chief. The Fire Chief, or designee, will provide a briefing to the primary departments responsible for the Emergency Support Functions that are required to be activated. The Emergency Operations Team members will convene in the EOC, or virtually if appropriate, and assume their assigned roles. Strategic Management Team The Strategic Management Team leads the incident response and defines the scope of the incident. This includes assigning the appropriate command and general staff personnel to an incident and ensuring that Unified Command is established for incidents that cross functional or jurisdictional boundaries. The Strategic Management Team provides guidance to responders in field operations and to the support sections by establishing goals and objectives, and overseeing the development of incident strategy and overall tactics. There are a number of command and general staff positions that may be included as part of the Strategic Management Team. Those positions include: • Liaison Officers • Safety Officer • Scribes • Advisors • Incident Commander Page 170 of 325 4 | Page ACTIVATION OF THE EMERGENCY OPERATIONS PLAN (EOP) The Emergency Operations Plan (EOP) shall be activated and in effect when so ordered by the City Manager or designee or a member of the Emergency Policy Team. As the Director of Emergency Management, the City Manager shall assume overall responsibility for the City’s disaster response operations through the roles delineated in this EOP. A declaration of a local emergency will automatically activate the EOP and authorizes the provision of aid and assistance. The City of Lynchburg EOP may also be activated to manage significant requests for mutual aid and cooperative assistance to other jurisdictions that have requested appropriate assistance in response to a major event or incident. When emergency activities have resolved the emergency and ongoing demobilization and recovery actions may be adequately managed without continued emergency declaration powers, the City Manager shall recommend to the City Council a termination of the declared emergency. The EOP may continue in operation beyond the emergency declaration, allowing an orderly incident response demobilization and transition to the Recovery phase of the incident. COLLEGES AND UNIVERSITIES The City of Lynchburg acknowledges the benefits of incorporating emergency operations planning from local colleges and universities into our Comprehensive Emergency Management Program. To achieve this objective, the City will maintain its commitment to promoting integrated emergency planning efforts with these institutions through collaboration within the Local Emergency Planning Committee (LEPC), joint exercises, and other collaborative initiatives aimed at enhancing preparedness and response capabilities for all stakeholders involved. Page 171 of 325 5 | Page FAIR AND EQUAL SUPPORT FOR ALL PERSONS AND COMMUNITIES In accordance with § 44-146.19. E of the Code of Virginia, the City of Lynchburg is committed to ensuring fair and equal support for all persons and communities of the City of Lynchburg during emergencies. The following provisions are outlined to address these specific needs: 1. Community Engagement and Representation: Prior to and during emergencies, efforts will be made to engage all persons and communities, including, but not being limited to, ethnic and racial minorities, low-income persons, disabled persons, the elderly, and non-English speaking residents in emergency planning and decision-making processes. 2. Accessible Communication: Information regarding emergencies, shelter locations, and available resources will be disseminated through multiple channels to reach all persons and communities of the City of Lynchburg, including, but not being limited to, those with limited English proficiency, disabilities, or other communication barriers. Efforts will be made to use plain language messaging and accommodations where appropriate. 3. Access to Resources: Emergency shelters, food distribution points, medical services, and other essential resources will be established and operated in a manner that ensures fair and equal access for all members of the community, including, but not being limited to, ethnic and racial minorities, low-income persons, disabled persons, the elderly, and non-English speaking residents. Accommodations will be made to address specific needs where appropriate. 4. Cultural Competence and Sensitivity: Emergency responders and personnel involved in emergency management activities will receive training on how to interact with and support all communities of the City of Lynchburg during emergencies. 5. Collaboration with Community Partners: Collaborative partnerships will be fostered with community-based organizations, faith-based groups, social service agencies, and other stakeholders. These partnerships will facilitate the identification of needs, the coordination of resources, and the delivery of competent services to all persons and communities of the City of Lynchburg during emergencies. 6. Evaluation and Continuous Improvement: The effectiveness of strategies to address the needs of all persons and communities will be regularly evaluated, and adjustments will be made based on feedback and lessons learned from past emergencies. Continuous improvement efforts will ensure that our response remains responsive, inclusive, fair, and equal over time. By implementing these provisions, our Emergency Operations Plan reaffirms our commitment to serving all members of our community during times of crisis, in accordance with the requirements outlined in the Code of Virginia. Page 172 of 325 6 | Page Page 173 of 325 7 | Page EMERGENCY OPERATIONS PLAN INTRODUCTION To respond effectively to any emergency of a size or complexity beyond routine responsibilities it is critical that all City of Lynchburg public officials, departments and agencies, non-governmental emergency organizations and the public understand their roles and responsibilities. These additional responsibilities become particularly important as incident command organizes beyond the initial response phase. The foundation for this coordinated response is established through the City of Lynchburg Comprehensive Emergency Management Program (CEMP) and its component Emergency Operations Plan (EOP). The EOP delineates the entities that are responsible for providing command and coordination capabilities for large-scale or unusual events, and how the multiple command and response components are organized and managed. The City of Lynchburg EOP provides guidance across City of Lynchburg departments, agencies and response organizations by describing an overall emergency response system that state: • How City of Lynchburg agencies will be organized during response to an event, including command authorities. • Critical actions and interfaces during the response • How the interaction between City of Lynchburg and regional, state, and federal authorities is managed. • How the interaction between City of Lynchburg and its private partner organizations (hospitals, non-governmental emergency organizations and others) is managed. This document serves as an operational reference for the City of Lynchburg’s response to major emergencies. Other documents, such as field guides and operational checklists (job action sheets), may supplement the EOP by providing more detailed operational guidance at the City, agency, and individual asset levels. The EOP employs a multi-agency operational structure based upon the principles of the Incident Command System (ICS)/ National Incident Management System (NIMS) to manage, coordinate and direct resources committed to an incident. The City of Lynchburg is a practitioner of the National Incident Management System (NIMS). The City of Lynchburg also utilizes the Multi-agency Coordination (MAC) System to synchronize operations between the Incident Command System and the Emergency Operations Center. The Incident Command System is the combination of facilities, equipment, personnel, procedures and communication systems operating within a common organizational structure. The basic functional sections of the Incident Command System are: 1. Incident Command 2. Operations 3. Logistics 4. Safety These components are used to divide the incident into manageable tasks, while maintaining a coordinated focus. Task assignments are only established when a clear need exists to perform the task, to address span of control concerns, or to perform specific duties. Page 174 of 325 8 | Page The basic function teams in the Emergency Operations Center are: 1. Planning 2. Financial Services/Administration 3. Safety Officer These teams are used to coordinate tasks outside the scope of the Incident Command. These teams are only activated when a clear need exists to perform the task, to address span of control concerns, or to perform specific duties. The functional size and number of designated positions within the Incident Command System and the Multi-agency Coordination System can be expanded or contracted to meet requirements as an event progresses. Selective implementation of ICS/NIMS components through the activation and/or demobilization of additional positions allows maximum flexibility in meeting the unique operational requirements of each situation. ROLES, RESPONSIBILITIES, AND AUTHORITIES The primary management components of the City of Lynchburg Emergency Operations Plan and Comprehensive Emergency Management Program are: • City Council and City Manager • Emergency Policy Team • Emergency Operations Team • Strategic Management Team CITY COUNCIL AND CITY MANAGER ROLES AND RESPONSIBILITIES Lynchburg is governed by a seven-member City Council. The Mayor of the Council serves as the City’s chief elected official. The Vice Mayor serves in the Mayor’s absence. The City Council is responsible for policy and political activities related to an emergency. The City Council must formally act on the City Manager’s Declaration of an Emergency within fourteen days. The City Council also formally declares an end to the declared emergency. Other responsibilities of the Council, typically handled by the Mayor, include serving as overall spokesperson for the City and coordinating with other elected officials at the regional and state levels, including the Congressional delegation. The Mayor also conducts any other activities required of the chief elected official. The direct management of emergencies is delegated to the City Manager who is designated as the City’s Director of Emergency Management. The role of the City Manager during an emergency is to implement City Council policies, provide overall direction, monitor the response of City agencies for adequacy, delegate authority for command of the situation, fulfill legal requirements of an emergency declaration, and other issues that must be addressed at the City Manager level. The City Manager also serves as a critical link between the City of Lynchburg Emergency Operations Team and the City Council and political authorities from other levels of local, state and federal government. Functions of the City Manager during an incident or emergency include: 1. Empowering the Emergency Operations Team to manage emergencies, and the Strategic Management Team to manage the incident itself. 2. Meeting legal requirements, such as declarations of emergency or curfew. Page 175 of 325 9 | Page 3. Providing a liaison with political bodies, including members of the City Council, and, as necessary, regional, state, and federal political authorities. 4. Informing the Emergency Operations Team and Strategic Management Team of decisions and actions taken at the City, regional, state and federal political leadership levels. 5. Providing policy guidance to the Emergency Operations Team. 6. Providing guidance on sensitive issues such as community information. 7. Remaining available to the Emergency Operations Team for consultation and support. The City Manager, or designee, monitors emergency operations and guides the City response as needed. The City Manager or aforementioned parties may participate in any Emergency Operations Team, or Strategic Management Team meeting. City Manager participation is generally in the form of policy guidance to the Emergency Operations Team as well as directives or guidance issued to City agencies and other organizations, as appropriate. EMERGENCY POLICY TEAM The Emergency Policy Team, as the core group of senior managers knowledgeable in field emergency operations, and other officials as necessary, advise the City Manager in pre-emergency planning, emergency and incident command, and recovery. They operate within the City’s hierarchical structure as an independent subcommittee of the City Manager’s Leadership Team (LT). The core membership of the Emergency Policy Team consists of the following: • City Manager (Chair) • Deputy City Manager (Chair in the City Manager’s Absence) • Fire Chief (serves as the Emergency Policy Team Planning Leader) • Police Chief • Director, Emergency Communications Center • Director, Department of Human Services • Director, Department of Water Resources • Director, Department of Public Works • Director, Department of Communications and Public Engagement • Director, Department of Information Technology • Superintendent of City Schools/Designee The City Attorney shall act as a legal advisor to the Emergency Policy Team. Emergency Policy Team members focus on policy and oversight advice to the City Manager. Each member of the Emergency Policy Team will designate a staff member, who has executive decision-making authority, to serve as their “second.” The designation of a “second” allows flexibility for the core member to respond to other duties as needed. Emergency Policy Team members should develop lists of those capable of serving as seconds. These lists must include at least two (2) people. Assignment to the Emergency Policy Team does not preclude members from fulfilling other roles within the Comprehensive Emergency Management Program or in an incident response. The core member’s primary role, however, is to serve on the Emergency Policy Team and advise the City Manager on effective policy formation during an incident response. The City Manager may add additional members based upon the core members’ recommendations or as necessitated by a specific incident. The Fire Chief or designee may serve as the staff coordinator for the Emergency Policy Team during activations of the Emergency Policy Team. Page 176 of 325 10 | Page In the performance of response oversight duties, the City Manager may call upon the Emergency Policy Team to address issues related to an event. When convened, the Emergency Policy Team will receive an incident update briefing and will be tasked with providing policy recommendations to the City Manager. At the City Manager’s direction, the Emergency Policy Team may be convened physically or virtually at any time through the Fire Chief or designee. The Emergency Policy Team will establish and review broader issues facing those agencies responding to or recovering from an event or emergency, as well as those issues that impact the City. The Fire Chief or designee is generally charged with fulfilling the Planning Team Leader duties for the Emergency Policy Team. The Planning Leader’s duties include: • In consultation with the City Manager or designee, setting Emergency Policy • Determining team meeting time and agenda • Providing a policy-level briefing from Strategic Management Team and Emergency Operations Team action plans and from situation updates • Presenting policy issues/questions from the Emergency Operations Team and Strategic Management Team • Receiving policy direction to incorporate into the Emergency Operations Team and Strategic Management Team planning Information briefings may be provided by the Emergency Operations Center Director, the Emergency Operations Center Planning Team Leader, a Strategic Management Team member or an Incident Commander, outside experts being consulted for policy advice, or others as appropriate for the situation. EMERGENCY OPERATIONS TEAM & EMERGENCY OPERATIONS CENTER The Emergency Operations Team is the functional organization that manages the Emergency Operations Center (EOC) during an emergency. This team coordinates and manages citywide assets beyond the incident and oversees the coordination of the Emergency Support Functions. The Emergency Operations Team positions may include: • Fire Chief • Director, Emergency Communications Center • Safety Officer • Liaison • Advisors • EOC Watch Officer • Planning & Finance Team Leaders • Command and General Staff Aide(s) The Emergency Operations Team is responsible for all strategic emergency management operations away from the incident site. These responsibilities include: 1. Directly support the Strategic Management Team, providing resources that are not available through the established incident command system, operating in the specific event. This includes coordinating assistance from outside resources (federal, state, and other local jurisdictions) that is not obtained through tactical mutual aid or other incident-level command processes. 2. Directly manage emergency issues related to the incident, but outside the defined scope of the incident, as delineated by the Strategic Management Team. This may be determined geographically (outside a scene perimeter) or functionally (beyond the scope of the Strategic Management Team objectives when no single Page 177 of 325 11 | Page scene exists, or when the impact is widespread). Usually, this will entail maintaining or restoring essential City services during an emergency, avoiding or minimizing casualties and property damage, and addressing financial and other major impacts as soon as possible following the onset of an emergency or disaster situation. The Emergency Operations Team organizes the Citywide response with guidance provided to City of Lynchburg departments, agencies, non-governmental emergency organizations, and to the public, by establishing Citywide goals and strategic objectives. 3. Provide information integration between the Strategic Management Team and the City Manager and the City Council. More specifically, the Emergency Operations Team duties may include: • Strategic Management Team requests for assistance o The Emergency Operations Team coordinates administrative, material and personnel support to Field Operations and the Incident Commander as necessary for the duration of the incident. o When the Strategic Management Team has resource requests that cannot be directly addressed or obtained from within the agencies directly involved in the response, the Emergency Operations Center accepts the request and seeks solutions through the City of Lynchburg Emergency Support Functions. o If necessary, new task groups may be formed within the Emergency Operations Center to address complex issues that fall between the authorities of multiple Emergency Support Functions. Assistance from non-City resources will be arranged as needed to meet critical needs. o The Emergency Operations Center will coordinate (usually through the Virginia Emergency Operations Center) all assistance from the state and federal government. Emergency Operations Center personnel will manage these outside resources, both personnel and material, until they are assigned to the incident. Once an asset has been assigned to the incident, it is transferred to the Strategic Management Team. • Events outside the scope of the incident itself o The Emergency Operations Team, through the utilization of ESFs, manage other non-incident emergency issues, such as public communications. The Emergency Operations Center Planning Team Leader will oversee the planning efforts for contingencies, long-range issues and demobilization for each operational period. • Coordination with the State Government o The Emergency Operations Team is responsible for coordination between the City Emergency Operations Center and the Virginia Emergency Operations Center. o The Fire Chief (or designee) will notify the Virginia Department of Emergency Management immediately upon either the declaration of a local emergency or the activation of the Emergency Operations Center. o The Commonwealth of Virginia’s Emergency Operations Plan requires the submission of various reports by local government in times of emergency. The Emergency Operations Team will submit these and other reports and updates, after approval by the Fire Chief (or designee). • Coordination with the City Manager o The Emergency Operations Team will recommend to the City Manager when the Emergency Operations Center should be fully activated, and when the levels of an Emergency Operations Plan (response, demobilization, and transition to recovery) should be implemented. o The Emergency Operations Team will recommend to the City Manager when an emergency should be officially declared, and when other direct action is required by law or regulation. o The Emergency Operations Team will raise policy questions, and facilitates the application of policy decisions made by the City Manager, by incorporating the policy direction into Emergency Operations Center planning and conveying the instructions to the Strategic Management Team, as indicated. o The Emergency Operations Team will provide timely and accurate information to the members of the Emergency Policy Team and, at the City Manager’s direction, to other City government officials and/or to the public. Page 178 of 325 12 | Page EMERGENCY OPERATIONS CENTER PLANNING TEAM The Emergency Operations Center Planning Team supports the Emergency Operations Center Director during the Emergency Policy Team meetings, documenting policy decisions that are resolved. They also provide the agenda and supporting documents for subsequent meetings. The Emergency Operations Center Director receives the policy direction and other recommendations from the City Manager, conveying them to the Strategic Management Team for incident implementation, and overseeing their implementation through the Emergency Operations Center operations plan and Emergency Support Functions directives. The Planning Team is also responsible for the production and distribution of the Lynchburg City Incident Action Plan. EMERGENCY SUPPORT FUNCTIONS Emergency Support Functions (ESF) are organized as task groups and operate out of the Emergency Operations Center (EOC). These support functions provide resources to support both the Strategic Management Team for during incident response, and the Emergency Operations Team for incident- related issues that fall outside the Strategic Management Team’s scope. The Emergency Operations Team monitors the activities of Emergency Support Functions. When issues arise, which are difficult to manage within the pre-established Emergency Support Function structure, the Emergency Operations Team will assist in securing the resources necessary for the task group. During emergency operations, the Emergency Support Functions carry out assignments unique to each task group’s expertise that have been delegated to them from the Emergency Operations Team. Each Emergency Support Function is assigned a lead City department or office that is responsible for contacting their respective support agencies. Support agencies are entities with specific capabilities or resources that support the lead City department in executing the mission of the ESF and can include other City departments or non- governmental emergency organizations. Each lead agency’s response role includes: • The Department Director of the lead agency for each Emergency Support Function is responsible for designating that Emergency Support Function’s leader. • The leader is responsible for ensuring that their Emergency Support Function is fully operational for the emergency. Duties include: o Conducting necessary planning and training activities to ensure Emergency Support Function members understand their roles and responsibilities. o Preparing necessary information and technical resources to support the Emergency Support Function during activation. o Assuring that assigned tasks are completed and reported back to the appropriate Emergency Operations Center position. o Bringing difficult operational issues to the appropriate Emergency Operations Center position for resolution. o Evaluating the overall performance of the Emergency Support Function during the incident. The chart on the next page lists the Emergency Support Functions and indicates lead and support agencies assigned to each. Page 179 of 325 13 | Page ESF1 ESF2 ESF3 ESF4 ESF5 ESF6 ESF7 ESF8 ESF9 ESF10 ESF11 ESF12 ESF13 ESF14 ESF15 ESF16 ESF17 CA S CD S S S S L CPE S S L/C S CMO S L CR S ECC L S S S S FD S S L S S L L L S S FS L S HR L HS S S L S S IT S S S S S LCS S S S S S S OED S S S PD S S S S S S S S S S L L PR S S S L S L PM S PW L L/C S S S S S L S WR S L S S S S S S L: LEAD S: SUPPORT C: ESF COORDINATOR (if more than one lead) This table only shows the City agencies that are involved with each of the emergency support functions. There are also non-governmental and state participants involved in several of the ESFs. Emergency Support Functions (ESFs) City of Lynchburg Departments 1 Transportation CA City Assessor’s Office 2 Communications CD Community Development 3 Public Works & Water Resources CPE Communications & Public Engagement 4 Fire Fighting CMO City Manager’s Office 5 Emergency Management CR Commissioner of the Revenue 6 Mass Care, Housing & Human Services ECC Emergency Communications Center 7 Resource Support FD Fire Department 8 Public Health & Medical Services FS Financial Services 9 Urban Search & Rescue HR Human Resources 10 Oil & Hazardous Materials Response HS Human Services 11 Agriculture & Natural Resources IT Information Technology 12 Energy LCS Lynchburg City Schools 13 Public Safety & Security OED Office of Economic Development 14 Long Term Community Recovery & Mitigation PM Parking Management 15 External Affairs PR Parks and Recreation 16 Employee Support PD Police Department 17 Volunteer & Donations Management PW Public Works WR Water Resources Page 180 of 325 14 | Page EMERGENCY OPERATIONS CENTER PLAN The Emergency Operations Center Plan designates command and support staff positions to operate the Emergency Operations Center. Procedures for these support operations are established and maintained in the Emergency Operations Center Standard Operating Procedures Manual, located in the Emergency Operations Center. In an emergency, there are five stages to activate the Emergency Operations Center: 1. Notification/Activation Stage a. In an emergency, the on-duty Emergency Communications Center Supervisor is instructed to begin the emergency call procedure, by notifying the Director of the Emergency Communications Center. This instruction could originate from a supervisor in any City department. A brief message describing the event is provided to the Communications Supervisor for inclusion in the notification. b. If the incident does not require all of the Emergency Operations Team, Emergency Support Functions, or the Emergency Policy Team, the requesting party should clearly specify to the Communications Supervisor which groups or specific positions are being requested. c. The designated person for each agency, department and non-governmental emergency organization is notified. The level of activation for each notified entity is also specified. If direct voice communication does not occur with the notified parties, a receipt of notification is requested in the message, as well as a brief status report from the notified agency. 2. Mobilization Stage a. Upon receipt of information that an emergency situation is imminent or occurring, the Fire Chief or designee oversees the mobilization process for the Emergency Operations Center and provides an initial informational briefing to the primary agencies of the respective Emergency Support Functions that will be activated to assist with the emergency. b. Assigned City of Lynchburg personnel and non-governmental emergency organizations are dispatched to staff their designated Emergency Operations Center positions. 3. Emergency Operations Stage a. Emergency Operations Center staffing is predicated on the nature of the incident and directed by the Fire Chief or designee at the time of need. b. If directed, the Emergency Operations Team will convene in the Emergency Operations Center and assume their assigned roles. The Emergency Operations Team’s mission is determined and redefined through a planning cycle after each operational period. The length of operational cycles is established by the Strategic Management Team. c. The Emergency Operations Team primarily focuses on providing support to the Strategic Management Team and management of issues outside the scope of the Strategic Management Team. d. The Emergency Operations Team also leads Emergency Operations Center management and planning meetings and operations briefings. The timing of these meetings should be coordinated with the timing of the Strategic Management Team meetings so the Emergency Operations Center operations briefing is held after the Strategic Management Team operations briefing. (See Planning Period Chart Page 15) e. At the conclusion of these meetings, the updated Incident Action Plan is provided to the Emergency Operations Team. Most major press briefings would ideally be held after the Strategic Management Team and Emergency Operations Team have held their respective operations briefings. f. Some of the critical response activities that take place during this stage of the incident include: i. Assuring the inspection of critical City of Lynchburg facilities, equipment and communications systems. ii. Mobilizing personnel and pre-positioning resources and equipment for use by the Strategic Management Team and incident responders. iii. Ensuring appropriate public emergency information and warning efforts. iv. Assisting the Strategic Management Team with alerting any threatened elements of the population, and in conducting necessary or precautionary evacuations in potential impact areas. v. Overseeing/supporting the opening and operation of mass care and pet shelters. Page 181 of 325 15 | Page vi. Restricting unnecessary access to affected areas outside the incident perimeter (the incident perimeter is generally managed by the on-scene Incident Command). vii. Protecting, controlling and allocating vital resources outside of the on-scene Incident Commander’s area of supervision. viii. Conducting initial damage and needs assessments outside the Strategic Management Team scope of activity. ix. Assessing the need for mutual aid beyond the tactical assistance obtained through incident command mechanisms. x. Documenting the situation and expenditures on a Citywide basis. xi. Coordinating information exchange with regional, state and federal agencies to include providing initial and periodic situation reports to the Virginia Department of Emergency Management (VDEM), and monitoring conditions in the City outside the incident site. 4. Demobilization Stage a. As the Emergency Operations Center objectives are achieved and tasks completed, the resources will be demobilized. b. The Emergency Operations Center Planning Team initiates the process early in this phase. c. The process for demobilization is developed and approved by Emergency Operations Center management. (For example: as a general rule, non-Lynchburg assets will be demobilized prior to City of Lynchburg assets performing similar duties). d. The Emergency Operations Center, through both the Emergency Operations Team and relevant Emergency Support Functions, assists the Strategic Management Team with the demobilization of incident assets. 5. Transition to Recovery Stage a. The Emergency Operations Center remains operational while the Strategic Management Team transitions its personnel and structure to the recovery phase of the incident. b. The Emergency Operations Center demobilizes its Emergency Support Function assets according to the Emergency Operations Center demobilization planning, but retains an Emergency Management Operations capability to support the Incident Recovery. c. As recovery progresses, Emergency Operations Center duties may transition to a specific agency or to the Fire Department staff. Page 182 of 325 16 | Page Page 183 of 325 17 | Page ADDITIONAL RESOURCES COORDINATED BY THE EOC Additional resources are available should the emergency exceed the City’s emergency response capabilities. These resources include: 1. Mutual Aid a. In the event an emergency situation exceeds local emergency response capabilities, outside assistance is available through mutual support agreements with nearby jurisdictions and volunteer emergency organizations, or through the Commonwealth of Virginia’s Statewide Mutual Aid Compact. b. For assistance beyond tactical mutual aid (i.e. that which might be used in everyday incidents), a local emergency must be declared and local resources fully committed, with anticipated or actual unmet needs, before state and federal assistance is requested. The Emergency Operations Center coordinates the request for outside assistance. c. Regional mutual aid assistance will be requested in accordance with established mutual aid agreements of which City of Lynchburg is a signatory. Mutual aid for other than Police, EMS and Fire services may be requested through the Virginia Statewide Mutual Aid Compact. d. Identified response needs will be addressed initially with locally available City of Lynchburg and mutual aid resources. With the onset of a major incident or event, requests for State assistance may occur based upon the anticipation of unmet needs, prior to experiencing shortages after deployment of all local resources e. Once it has been determined that state assistance is needed, the City Manager will ensure that the following procedures and requirements are observed: i. A local emergency has been declared. ii. The EOP has been activated. iii. Available resources have been committed, and it is anticipated that critical incident needs will remain unmet despite this commitment of available resources. iv. The type, quantity and time period for the assistance is specified. v. If appropriate, the City Manager requests and recommends the Governor declare a state of emergency. vi. During emergency situations, some state assistance may be provided to individual City of Lynchburg departments and agencies through other channels. vii. Any provision of state assistance through these mechanisms should be reported through the Strategic Management Team or through the appropriate Emergency Support Function in the Emergency Operations Center for accountability and planning purposes. f. Requests for state assistance will be made by the Fire Chief or designee through the Virginia Emergency Operations Center (VEOC) to the State Coordinator of Emergency Management. 2. Virginia Fusion Center a. In accordance with the Virginia Code and recognizing the critical role of the Virginia Fusion Center (VFC) in enhancing statewide preparedness and response capabilities, the EOP outlines robust coordination efforts with the VFC. b. Information Exchange and Analysis: The EOP establishes mechanisms for the timely exchange of information with the VFC, leveraging its expertise in collecting, analyzing, and disseminating intelligence related to terrorism, criminal activities, and cybersecurity threats. This collaboration enhances our situational awareness and supports informed decision-making during emergencies. c. Cyber Threat Intelligence Support: The VFC provides specialized assistance in analyzing and responding to cybersecurity events. Through its partnerships and access to relevant data sources, the VFC offers valuable insights into emerging cyber threats, vulnerabilities, and trends. This intelligence enables our locality to implement proactive measures to mitigate cyber risks and protect critical infrastructure and systems. d. Rapid Information Dissemination: During cybersecurity events, the VFC serves as a key facilitator for the rapid dissemination of threat and protective information affecting Virginia. Through its Page 184 of 325 18 | Page 24/7 operational capability, the VFC ensures that relevant intelligence is promptly shared with our locality and other partners, enabling timely response and mitigation efforts. e. Collaborative Response Planning: The EOP incorporates collaborative response planning with the VFC to address cybersecurity incidents

Text truncated. Open the original for the full document.

Source: City of Lynchburg website. First collected Nov 3, 2026.