Review Type |
Outcome |
Est. Completion Date |
Completed |
Public Works Streets Review
|
Approved
|
01/07/2025
|
12/09/2024
|
|
|
|
|
Public Works Collection Review
|
Approved
|
01/07/2025
|
12/09/2024
|
|
|
|
|
Public Works Water Review
|
Approved
|
01/07/2025
|
12/09/2024
|
|
|
|
|
Engineering Traffic Review
|
Approved
|
01/07/2025
|
12/09/2024
|
|
|
|
|
Fire Review
|
Approved
|
01/07/2025
|
12/09/2024
|
|
|
|
|
Planning Review
|
Approved
|
01/07/2025
|
12/09/2024
|
|
|
|
Final Landscape Plan - Tree protection plan
Comment partially outstanding: 09/24
Existing trees to be retained must be clearly marked on the final clearing and grading plan, and the final landscape plan. The Large Douglas Fir is shown on the plans, but the street trees on the back of walk are also required to be protected. The sidewalk panels are shown to be replaced. These trees are considered to be existing trees that mut be retained.
Comment outstanding: 08/27
The Large Douglas Fir is still not shown on the TESC & demolition plan set.
Existing trees to be retained must be clearly marked on the final clearing and grading plan, and final landscape plan.
Tree protection fencing and signage shall follow the city standard detail, see appendix 20.5. Standard detail shall be included on all plan sets with vegetation which is scheduled for retention and protection. All critical root protection zones (CRPZ) shall be shown on plan sets in diameter from the center of the tree. In determining tree CRPZ, the following standards shall be used.
In establishing the extent of the Critical Root Protection Zone (CRPZ) for individual significant trees, groupings of significant trees, a stand of significant trees, or a heritage tree the following formula shall be used: Individual tree diameter (in inches) X 2, converted into feet = CRPZ, in diameter (Example: 20” tree X 2 = 40’ CRPZ diameter).
The following minimum performance standards shall be used to determine the extent of allowable impacts to the CRPZ of significant trees: For significant trees, a minimum of 50 percent of the critical root zone must be preserved at natural grade, with natural ground cover. The protection zone may be irregular. The plan set shall provide a total square footage of CRPZ area and show the % of disturbance area. For heritage trees, a minimum of 75 percent of the critical root zone must be preserved at natural grade with natural ground cover. The protection zone may be irregular. The plan set shall provide a total square footage of CRPZ area and show the % of disturbance area.
No cut or fill greater than four (4) inches in depth may be located closer to the tree trunk than ½ the CRPZ radius distance. (Example, 20-inch DBH tree has a 40’ CRPZ area (in diameter) - meaning no cut or fill greater than 4” in depth is allowed within 20’ of the tree trunk). No cut or fill within the distance from the tree which is three (3) times the trunk DBH is allowed. (Example, 20-inch DBH tree X 3 = 60”, meaning no cut is allowed within 60-inches of a tree which has a 20-inch diameter trunk).
These criteria represent minimum standards for determining whether or not a tree may be required to be retained. Greater impacts may be allowed, provided that all design alternatives have been proven unfeasible and that a pre-conditioning and after care mitigation program is established. See section 10.1 of the VMS, and referenced appendices for more information.
|
|
See Document Markup
Add CRPZ protection to ALL retained trees on the TESC plan and demolition plan. [civil plan, C-3 & C-4]
|
|
|
Engineering Civil Review
|
Failed
|
12/10/2024
|
11/26/2024
|
|
|
|
Other/Miscellaneous
Pervious Pavement Comments:
In reviewing BMPT5.15 Permeable Pavements, there is an infeasability criteria that states, "Where infiltrating and ponded water below new permeable pavement area would compromise adjacent impervious pavements." The Applications and Limitations section further states: "No run-on from pervious surfaces is preferred." and “Sheet flow from up gradient impervious areas is not recommended, but permissible if the permeable pavement area is > the impervious pavement area.” From a constructability and a run-on perspective the intermixed design is unlikely to be approved based on this criteria. In addition, we believe the development will exceed recommended traffic volumes for impervious surfaces. With a Starbucks and Taco Time restaurant on the same property, the daily traffic volumes are expected to exceed 400 vehicles per day which exceeds the Manuals definition of 'very low' traffic volumes. Justify the pervious design or provide alternative methods of collection and treatment. **9/18/2024**COMMENT NOT ADDRESSED. The design for the "island" pervious pavement came in fresh on the 3rd submittal, and is subject to any and all corrections and rejections by city reviewers. Redesign the parking lot based on the City's corrections/concerns and the 2019 Storm Water Management Manual for Western Washington.
|
|
Other/Miscellaneous
Add Details 01.01.20 and 02.01.04 to the civil sheets. Resubmit all civil docs with the newest versions including the SWPPP and Cost Estimate that were worked on through the email. Also remove the generic infiltration trench detail on Sheet C12.
|
|
|
Planning Review
|
Failed
|
12/10/2024
|
11/26/2024
|
|
|
|
Final Landscape Plan - Tree protection plan
Comment partially outstanding: 09/24
Existing trees to be retained must be clearly marked on the final clearing and grading plan, and the final landscape plan. The Large Douglas Fir is shown on the plans, but the street trees on the back of walk are also required to be protected. The sidewalk panels are shown to be replaced. These trees are considered to be existing trees that mut be retained.
Comment outstanding: 08/27
The Large Douglas Fir is still not shown on the TESC & demolition plan set.
Existing trees to be retained must be clearly marked on the final clearing and grading plan, and final landscape plan.
Tree protection fencing and signage shall follow the city standard detail, see appendix 20.5. Standard detail shall be included on all plan sets with vegetation which is scheduled for retention and protection. All critical root protection zones (CRPZ) shall be shown on plan sets in diameter from the center of the tree. In determining tree CRPZ, the following standards shall be used.
In establishing the extent of the Critical Root Protection Zone (CRPZ) for individual significant trees, groupings of significant trees, a stand of significant trees, or a heritage tree the following formula shall be used: Individual tree diameter (in inches) X 2, converted into feet = CRPZ, in diameter (Example: 20” tree X 2 = 40’ CRPZ diameter).
The following minimum performance standards shall be used to determine the extent of allowable impacts to the CRPZ of significant trees: For significant trees, a minimum of 50 percent of the critical root zone must be preserved at natural grade, with natural ground cover. The protection zone may be irregular. The plan set shall provide a total square footage of CRPZ area and show the % of disturbance area. For heritage trees, a minimum of 75 percent of the critical root zone must be preserved at natural grade with natural ground cover. The protection zone may be irregular. The plan set shall provide a total square footage of CRPZ area and show the % of disturbance area.
No cut or fill greater than four (4) inches in depth may be located closer to the tree trunk than ½ the CRPZ radius distance. (Example, 20-inch DBH tree has a 40’ CRPZ area (in diameter) - meaning no cut or fill greater than 4” in depth is allowed within 20’ of the tree trunk). No cut or fill within the distance from the tree which is three (3) times the trunk DBH is allowed. (Example, 20-inch DBH tree X 3 = 60”, meaning no cut is allowed within 60-inches of a tree which has a 20-inch diameter trunk).
These criteria represent minimum standards for determining whether or not a tree may be required to be retained. Greater impacts may be allowed, provided that all design alternatives have been proven unfeasible and that a pre-conditioning and after care mitigation program is established. See section 10.1 of the VMS, and referenced appendices for more information.
|
|
Final Landscape Plan - Details
Comment outstanding: 09/24
Landscape details: 01.02.06, 01.02.08 still have not been added.
Comment outstanding: 08/27
Add required landscape details to plan: Detail 01.02.06, 01.02.08
Landscape details can be found at: https://www.cityofpuyallup.org/1445/100---Roadway
|
|
See Document Markup
Comment outstanding: 09/24
The SD lines are on the landscape plans, but they are not labeled on the landscape plan set and only the line itself is shown. The water lines and the sewer lines are not shown on the landscape plan set. Please label the SD, SS lines and the water lines to the landscape plan set as the utility overlay is required.
Comment outstanding: 08/27
The utilities have still not been placed back onto the landscape plan. This is required and in order for a full review, staff needs to be able to see where the utilities are in relation to the proposed landscaping.
Any required trees that are proposed too close to utility lines and are unable to be moved to meet the 10ft spacing requirement from utilities shall be moved to this lawn area if possible. Use root barriers per engineerings direction if necessary. [landscape plan, L-1]
|
|
Final Landscape Plan - Street Tree Site Prep
Comment Outstanding: 11/22
Needs to be Addressed:
Integrate the Street Tree Installation Standards Table (page 25 of the VMS) into plan sets. Please observe required spacing standards, as outlined in the table, when preparing drawings. The city has required species mix requirements based on the quantity of street trees to be planted as a part of the project.
Comments Outstanding: 09/24
Needs to be Addressed:
Integrate the Street Tree Installation Standards Table (page 25 of the VMS) into plan sets. Please observe required spacing standards, as outlined in the table, when preparing drawings. The city has required species mix requirements based on the quantity of street trees to be planted as a part of the project.
Needs to be Addressed:
The ‘Existing Conditions and Demolition Plan’ does not show the utilities along the eastern property you are describing that prevent larger trees from being planted. If utilities are present on site and are part of the reason larger trees cannot be provided please show the utilities. There is a large, private easement on the east side of the property, but no utilities are shown in it:
Please check section 12.11 when specifying species to be planted. The city’s policy is to plant the largest canopy tree for the rooting/overhead space available (section 12.4, VMS). Please note this when specifying tree species for the planter strip.
Partially addressed: 08/27
Needs to be Addressed:
Integrate the Street Tree Installation Standards Table (page 25 of the VMS) into plan sets. Please observe required spacing standards, as outlined in the table, when preparing drawings. The city has required species mix requirements based on the quantity of street trees to be planted as a part of the project.
Needs to be Addressed:
The ‘Existing Conditions and Demolition Plan’ does not show the utilities along the eastern property you are describing that prevent larger trees from being planted. If utilities are present on site and are part of the reason larger trees cannot be provided please show the utilities. There is a large, private easement on the east side of the property, but no utilities are shown in it:
Please check section 12.11 when specifying species to be planted. The city’s policy is to plant the largest canopy tree for the rooting/overhead space available (section 12.4, VMS). Please note this when specifying tree species for the planter strip.
Addressed: Street tree soil requirements. See section 8.2 of the VMS. Copy and paste the applicable section for street tree top soil and place on plans as requirement to meet the city standards. Root barriers, in accordance with city standards, are required for all street trees. A minimum of 8’ of linear protection along the edge of the sidewalk adjacent to the street tree shall be provided, using a minimum 24” deep root barrier panels.
Addressed: Integrate city standard detail 01.02.08a – soil amendment and depth. NOTE: Top soil placement/installation specs, depth and quality standards can be found in section 8.2 of the VMS. For new construction, cut and paste ALL of section 8.2(b) of the VMS into the planting notes/details of the final landscape plan sheets.
Addressed: See section 12.6 of the VMS for more information. Some common species of street trees are prohibited due to overuse and other reasons.
|
|
Other/Miscellaneous
Comment outstanding: 09/24
Comment Outstanding 082124
Applicant has stated that existing and proposed utilities are shown on landscape plan, but they are still not shown. Utilities are required to be shown on the final landscape plan.
Original landscape submittal included utility overlay, but utilities have been removed in the most recent landscape plan submittal. Please resubmit landscape plans with utility overlay.
|
|
See Document Markup
Comment Outstanding: 11/26/24
1. An updated arborist report that establishes a CRPZ for the three (3) existing street trees back of walk be provided.
- The plans note the trees are to be protected, but a CRPZ still has not been established.
2. An updated final civil plan set and updated landscape plan set with utility overlay that shows the CRPZ radius established by your arborist for all trees to be retained:
- Add the CRPZ for the three (3) existing trees back of walk on the following sheets:
-- Demolition plan sheet [C-3]
-- TESC plan sheet [C-4]
-- Landscape plan with utility overlay sheet [L-1]
Add CRPZ protection to ALL retained trees on the TESC plan and demolition plan. [civil plan, C-3 & C-4]
|
|
|
Engineering Traffic Review
|
Approved
|
12/10/2024
|
11/26/2024
|
|
|
|
|
Fire Review
|
Approved
|
12/10/2024
|
11/12/2024
|
|
|
|
|
Public Works Collection Review
|
Approved
|
12/10/2024
|
11/07/2024
|
|
|
|
|
Public Works Streets Review
|
Approved
|
12/10/2024
|
11/07/2024
|
|
|
|
|
Public Works Water Review
|
Approved
|
12/10/2024
|
11/07/2024
|
|
|
|
|
Planning Review
|
Failed
|
10/14/2024
|
09/24/2024
|
|
|
|
Final Landscape Plan - Tree protection plan
Comment partially outstanding: 09/24
Existing trees to be retained must be clearly marked on the final clearing and grading plan, and the final landscape plan. The Large Douglas Fir is shown on the plans, but the street trees on the back of walk are also required to be protected. The sidewalk panels are shown to be replaced. These trees are considered to be existing trees that mut be retained.
Comment outstanding: 08/27
The Large Douglas Fir is still not shown on the TESC & demolition plan set.
Existing trees to be retained must be clearly marked on the final clearing and grading plan, and final landscape plan.
Tree protection fencing and signage shall follow the city standard detail, see appendix 20.5. Standard detail shall be included on all plan sets with vegetation which is scheduled for retention and protection. All critical root protection zones (CRPZ) shall be shown on plan sets in diameter from the center of the tree. In determining tree CRPZ, the following standards shall be used.
In establishing the extent of the Critical Root Protection Zone (CRPZ) for individual significant trees, groupings of significant trees, a stand of significant trees, or a heritage tree the following formula shall be used: Individual tree diameter (in inches) X 2, converted into feet = CRPZ, in diameter (Example: 20” tree X 2 = 40’ CRPZ diameter).
The following minimum performance standards shall be used to determine the extent of allowable impacts to the CRPZ of significant trees: For significant trees, a minimum of 50 percent of the critical root zone must be preserved at natural grade, with natural ground cover. The protection zone may be irregular. The plan set shall provide a total square footage of CRPZ area and show the % of disturbance area. For heritage trees, a minimum of 75 percent of the critical root zone must be preserved at natural grade with natural ground cover. The protection zone may be irregular. The plan set shall provide a total square footage of CRPZ area and show the % of disturbance area.
No cut or fill greater than four (4) inches in depth may be located closer to the tree trunk than ½ the CRPZ radius distance. (Example, 20-inch DBH tree has a 40’ CRPZ area (in diameter) - meaning no cut or fill greater than 4” in depth is allowed within 20’ of the tree trunk). No cut or fill within the distance from the tree which is three (3) times the trunk DBH is allowed. (Example, 20-inch DBH tree X 3 = 60”, meaning no cut is allowed within 60-inches of a tree which has a 20-inch diameter trunk).
These criteria represent minimum standards for determining whether or not a tree may be required to be retained. Greater impacts may be allowed, provided that all design alternatives have been proven unfeasible and that a pre-conditioning and after care mitigation program is established. See section 10.1 of the VMS, and referenced appendices for more information.
|
|
Final Landscape Plan - Details
Comment outstanding: 09/24
Landscape details: 01.02.06, 01.02.08 still have not been added.
Comment outstanding: 08/27
Add required landscape details to plan: Detail 01.02.06, 01.02.08
Landscape details can be found at: https://www.cityofpuyallup.org/1445/100---Roadway
|
|
See Document Markup
Comment outstanding: 08/27
This was a condition of approval for the preliminary site plan. The trees in this northern area should at least be native conifers. An attempt needs to be made to fulfill this condition.
Please re-vegetate the disturbed area with native conifers and shrubs. No native conifers have been proposed in this area. Options for native conifers can be found in VMS 12.7 and must meet spacing standards. [landscape plan, L-1]
|
|
See Document Markup
Comment outstanding: 09/24
The SD lines are on the landscape plans, but they are not labeled on the landscape plan set and only the line itself is shown. The water lines and the sewer lines are not shown on the landscape plan set. Please label the SD, SS lines and the water lines to the landscape plan set as the utility overlay is required.
Comment outstanding: 08/27
The utilities have still not been placed back onto the landscape plan. This is required and in order for a full review, staff needs to be able to see where the utilities are in relation to the proposed landscaping.
Any required trees that are proposed too close to utility lines and are unable to be moved to meet the 10ft spacing requirement from utilities shall be moved to this lawn area if possible. Use root barriers per engineerings direction if necessary. [landscape plan, L-1]
|
|
Final Landscape Plan - Street Tree Site Prep
Comments Outstanding: 09/24
Needs to be Addressed:
Integrate the Street Tree Installation Standards Table (page 25 of the VMS) into plan sets. Please observe required spacing standards, as outlined in the table, when preparing drawings. The city has required species mix requirements based on the quantity of street trees to be planted as a part of the project.
Needs to be Addressed:
The ‘Existing Conditions and Demolition Plan’ does not show the utilities along the eastern property you are describing that prevent larger trees from being planted. If utilities are present on site and are part of the reason larger trees cannot be provided please show the utilities. There is a large, private easement on the east side of the property, but no utilities are shown in it:
Please check section 12.11 when specifying species to be planted. The city’s policy is to plant the largest canopy tree for the rooting/overhead space available (section 12.4, VMS). Please note this when specifying tree species for the planter strip.
Partially addressed: 08/27
Needs to be Addressed:
Integrate the Street Tree Installation Standards Table (page 25 of the VMS) into plan sets. Please observe required spacing standards, as outlined in the table, when preparing drawings. The city has required species mix requirements based on the quantity of street trees to be planted as a part of the project.
Needs to be Addressed:
The ‘Existing Conditions and Demolition Plan’ does not show the utilities along the eastern property you are describing that prevent larger trees from being planted. If utilities are present on site and are part of the reason larger trees cannot be provided please show the utilities. There is a large, private easement on the east side of the property, but no utilities are shown in it:
Please check section 12.11 when specifying species to be planted. The city’s policy is to plant the largest canopy tree for the rooting/overhead space available (section 12.4, VMS). Please note this when specifying tree species for the planter strip.
Addressed: Street tree soil requirements. See section 8.2 of the VMS. Copy and paste the applicable section for street tree top soil and place on plans as requirement to meet the city standards. Root barriers, in accordance with city standards, are required for all street trees. A minimum of 8’ of linear protection along the edge of the sidewalk adjacent to the street tree shall be provided, using a minimum 24” deep root barrier panels.
Addressed: Integrate city standard detail 01.02.08a – soil amendment and depth. NOTE: Top soil placement/installation specs, depth and quality standards can be found in section 8.2 of the VMS. For new construction, cut and paste ALL of section 8.2(b) of the VMS into the planting notes/details of the final landscape plan sheets.
Addressed: See section 12.6 of the VMS for more information. Some common species of street trees are prohibited due to overuse and other reasons.
|
|
Other/Miscellaneous
Comment outstanding: 09/24
Comment Outstanding 082124
Applicant has stated that existing and proposed utilities are shown on landscape plan, but they are still not shown. Utilities are required to be shown on the final landscape plan.
Original landscape submittal included utility overlay, but utilities have been removed in the most recent landscape plan submittal. Please resubmit landscape plans with utility overlay.
|
|
See Document Markup
Stockpile area needs to move away from any retained trees. Stockpile is currently proposed where the retained Douglas Fir is. [civil plan, C-4]
|
|
See Document Markup
Add CRPZ protection to ALL retained trees on the TESC plan and demolition plan. [civil plan, C-3 & C-4]
|
|
See Document Markup
Show Douglas Fir on TESC plan and demolition plan. [civil plan, C-3 & C-4]
|
|
See Document Markup
No more than 8 parking stalls shall be consecutively without a landscaping island [landscape plan, L-1]
|
|
Other/Miscellaneous
This civil application includes the tenant improvement of the existing Taco Time building to be converted to a Starbucks. A total of 55 stalls are required for Taco Time & Starbucks. Parking count is not met. Please update all plans to include 55 stalls. Please note that no more than 8 parking stalls shall be consecutively without a landscaping island. This comment was conveyed to the applicant in an e-mail dated 03/27/2024 as well.
|
|
|
Engineering Civil Review
|
Failed
|
10/14/2024
|
09/24/2024
|
|
|
|
See Document Markup
Original comment: Show trash enclosure roof downspout connection to storm.
Comment not addressed: Downspouts discharging over parking lot is prohibited per City standards. Storm line is directly beneath downspout discharge locations. Add callout for contractor to connect roof downspouts to adjacent storm line. [Civil Plans, C-6]
2024_09_03 - Roof downspout connection to storm from dumpster structure is still not clear. Linetype for perf pipe is not in legend. Use call outs or key notes to describe to the contractor on the plans what is supposed to be built.
|
|
See Document Markup
Based on given spot elevations on grading plan and in trash enclosure detail, pavement appears to slope towards trash enclosure. Show that surfaces around trash enclosure slope away to prevent runoff from entering enclosure.
2024_09_03 - Still not clear that water will slope away from dumpster area. Storm run off cannot enter the sewer connection w sump. Include proposed contours with call outs or key notes to describe to the contractor on the plans what is supposed to be built.
|
|
See Document Markup
Storm Pipes and Storm Key Notes are missing letter C. [CIVIL PLANS - RESUB, Sheet C8]
|
|
Other/Miscellaneous
Pervious Pavement Comments:
In reviewing BMPT5.15 Permeable Pavements, there is an infeasability criteria that states, "Where infiltrating and ponded water below new permeable pavement area would compromise adjacent impervious pavements." The Applications and Limitations section further states: "No run-on from pervious surfaces is preferred." and “Sheet flow from up gradient impervious areas is not recommended, but permissible if the permeable pavement area is > the impervious pavement area.” From a constructability and a run-on perspective the intermixed design is unlikely to be approved based on this criteria. In addition, we believe the development will exceed recommended traffic volumes for impervious surfaces. With a Starbucks and Taco Time restaurant on the same property, the daily traffic volumes are expected to exceed 400 vehicles per day which exceeds the Manuals definition of 'very low' traffic volumes. Justify the pervious design or provide alternative methods of collection and treatment. **9/18/2024**COMMENT NOT ADDRESSED. The design for the "island" pervious pavement came in fresh on the 3rd submittal, and is subject to any and all corrections and rejections by city reviewers. Redesign the parking lot based on the City's corrections/concerns and the 2019 Storm Water Management Manual for Western Washington.
|
|
|
Public Works Streets Review
|
Approved
|
10/14/2024
|
09/20/2024
|
|
|
|
|
Fire Review
|
Approved
|
10/14/2024
|
09/19/2024
|
|
|
|
|
Engineering Traffic Review
|
Approved
|
10/14/2024
|
09/19/2024
|
|
|
|
|
Public Works Water Review
|
Approved
|
10/14/2024
|
09/19/2024
|
|
|
|
|
Public Works Collection Review
|
Approved
|
10/14/2024
|
09/18/2024
|
|
|
|
|
Engineering Civil Review
|
Failed
|
08/21/2024
|
09/06/2024
|
|
|
|
See Document Markup
Original comment: Trees shall not be located within 10-ft horizontally of stormwater pipes unless root barriers are provided.
- Root barriers: trees may be no closer than 3-ft to pipes.
Comment does not appear to be addressed. [Landscape Plans, L1]
|
|
See Document Markup
Original comment: Grease interceptor access manholes must be uncovered and clear of vegetation.
Comment does not appear to be addressed. [Landscape Plans, L1]
|
|
See Document Markup
Original comment: Provide root barriers for proposed trees near existing and proposed infiltration facilities.
Comment does not appear to be addressed. [Landscape Plans, L1]
|
|
See Document Markup
Original comment: Provide clear space for fire hydrant.
Comment does not appear to be addressed. [Landscape Plans, L1]
|
|
See Document Markup
Original comment: Trees shall not be located within 10-ft horizontally of sewer pipes unless root barriers are provided.
- Root barriers: trees may be no closer than 3-ft to pipes.
Comment does not appear to be addressed. [Landscape Plans, L1]
|
|
See Document Markup
Original Comment: Revise 811 label.
Comment not addressed: See comment in plan view with leader pointing to rogue 811 text in conflict with planview. [Civil Plans, C-1]
|
|
See Document Markup
Original comment: Screen (gray) back existing conditions to remain on all sheets.
Comment not addressed: existing and proposed elements appear on the plans to be the same shading and line types. Differentiate from the existing and proposed elements. (includes but not limited to buildings, concrete, utilities, etc.) [Civil Plans, C-1]
|
|
See Document Markup
Original comment: This hatch does not show up well in BlueBeam. Revise proposed pavement hatch to be more visible.
Comment not addressed: Proposed hatching needs to be more visible, not less. I understand it shows clearly when printing on paper, but it disappears when zooming out on bluebeam. Consider a different pattern or solid hatch that will not disappear when zoomed out. Its seems to work on sheet C-7. [Civil Plans, C-1]
|
|
See Document Markup
Original Comment: Show cross hatch symbol for inlet protection on all onsite and offsite inlets within project vicinity to remain.
Comment not addressed: Offsite CBs and some onsite CBs where not marked for inlet protection. [Civil Plans, C-4]
|
|
See Document Markup
Original Comment: Show roof overhang.
Comment not addressed. building layers are missing [Civil Plans, C-6]
2024_09_03 - Include roof overhangs as requested. Roof totals affect stormwater calculations.
|
|
See Document Markup
Original comment: Darken building footprint to increase legibility.
Comment not addressed: building outline layer is missing [Civil Plans, C-6]
|
|
See Document Markup
Original comment: Show Proposed building FFE.
Comment not addressed: FFE was not provided on grading plan. [Civil Plans, C-6]
|
|
See Document Markup
Original Comment: Show Existing building FFE.
Comment not addressed: existing building FFE was not provided on grading plan. [Civil Plans, C-6]
|
|
See Document Markup
Original comment: Freeze all existing elements (like curbing and bioswale) to be removed on all proposed plan sheets.
Comment not addressed: It appears a demo edge of pavement layer is still shown. [Civil Plans, C-6]
|
|
See Document Markup
Original comment: Show trash enclosure roof downspout connection to storm.
Comment not addressed: Downspouts discharging over parking lot is prohibited per City standards. Storm line is directly beneath downspout discharge locations. Add callout for contractor to connect roof downspouts to adjacent storm line. [Civil Plans, C-6]
2024_09_03 - Roof downspout connection to storm from dumpster structure is still not clear. Linetype for perf pipe is not in legend. Use call outs or key notes to describe to the contractor on the plans what is supposed to be built.
|
|
See Document Markup
Original comment: Provide an area table in section 1 to use in determining minimum requirements. The City encourages using the table provided during Preliminary Site Plan to ensure all required areas are tabulated. Email Lance Hollingsworth if you have trouble finding this table again.
Comment not fully addressed: TDA area tables show new areas and existing areas, but it does do not clearly show replaced areas, or new+replaced areas, or pollution generating areas. Refer to previously provided City template based on Ecology surface area definitions to ensure this comment is addressed. [Storm Report, Pg 3]
|
|
See Document Markup
Original comment: If you justify how each TDA effective impervious surface was reduced below the 10K threshold, the flow control standard is not required to be met.
Comment not addressed: It appears the narrative that includes the needed information is in the flow control narrative of the developed site hydrology section. Confirm this and direct reader to refer to this section for additional information used to satisfy MR7. [Storm Report, Pg 6]
|
|
See Document Markup
Original comment: Revise to say 2- Infiltration trenches.
New Comment: The additional infiltration trench to add was the ex infiltration trench To keep operations clean and clear, include the existing infiltration trench and other existing stormwater elements for the site in this as well. [O&M, Pg 2]
|
|
See Document Markup
Ex. easement is in conflict with building and physical ingress/egress appears to be removed in proposed design. Since parcels benefiting from easement are now owned by the same party, provide recorded documentation showing the easement has been released from the parcels. This will be required prior to civil permit issuance. [Civil Plans, C-1]
|
|
See Document Markup
Show all parcel lines for project site in the "Full Site" Plan view. [Civil Plans, C-1]
|
|
See Document Markup
Table is not clearly understandable. Replaced surface area is not shown. Is the "existing" row in the developed table supposed to be replaced surface area? [Civil Plans, C-1]
|
|
See Document Markup
Revise rogue dimension. [Civil Plans, C-2]
|
|
See Document Markup
Sewer layout on sheet C-8 shows sewer outside of trash enclosure. Update sewer layout on Sheet C-8 to match C-10.
[Civil Plans, C-8]
|
|
See Document Markup
Existing edge of pavement layer to remain is missing. [Civil Plans, C-6]
|
|
See Document Markup
Existing edge of pavement layer is missing in Plan view and driveway detail. [Civil Plans, C-7]
|
|
See Document Markup
Place City details in numerical order [Civil Plans, C-11]
|
|
See Document Markup
Put curb cut detail with other Section 1 details on sheet C-11. [Civil Plans, C13]
|
|
See Document Markup
Callout roof downspouts to connect to storm. [Civil Plans, C-7]
|
|
See Document Markup
Original Comment: Pipe cover at CB 2-3 is approximately 0.9 feet. Minimum cover for Ductile Iron Pipe is 1 foot.
Comment not addressed: Cover still shows to be 0.9 feet [Civil Plans, C-8]
|
|
See Document Markup
Original Comment: Provide Station and existing/proposed elevation labels on bottom of each profile view.
Comment not addressed: Stationing is missing on cross section A-A and retaining wall profile. Elevation labels are missing on cross section A-A and B-B. [Civil Plans, C-9]
|
|
See Document Markup
Show pipe connection from filterra to stormtank. [Civil Plans, C-9]
|
|
See Document Markup
Show crossing locations in SS Profile. [Civil Plans, C-10]
|
|
See Document Markup
Missing elevation labels in SS Profile. [Civil Plans, C-10]
|
|
See Document Markup
Is crossing next to trash enclosure accounted for? [Civil Plans, C-10]
|
|
See Document Markup
Freeze ex. bioretention to be removed [Civil Plans, C-10]
|
|
See Document Markup
Water service pipe length in ROW not labeled. [Civil Plans, C10]
|
|
See Document Markup
Water General notes do not match City Standards Section 304. [Civil Plans, C-14]
|
|
See Document Markup
Re-insert Water Standard detail 03.01.01 that was removed from plans. [Civil Plans, C-14]
|
|
See Document Markup
Based on given spot elevations on grading plan and in trash enclosure detail, pavement appears to slope towards trash enclosure. Show that surfaces around trash enclosure slope away to prevent runoff from entering enclosure.
2024_09_03 - Still not clear that water will slope away from dumpster area. Storm run off cannot enter the sewer connection w sump. Include proposed contours with call outs or key notes to describe to the contractor on the plans what is supposed to be built.
|
|
See Document Markup
Original Comment: FYI: commercial min. slope is 1%. [Civil Plans, C-8] (only add if 6" will be required)
New Comment: Apologies for any misunderstanding. Above comment was to note that 1% slopes are the minimum allowable slopes for 6" diameter commercial side sewer. 4" diameter for commercial side sewer connected to trash enclosure is not standard, but will be allowed at 2% min slope.It appears the project may not be able to achieve 2% for the entire pipe run so portions of the system may need to be 6" at between 1-2% slope
|
|
See Document Markup
6 foot pipe run from callout #2 to callout 21 appears to be missing from profile. [Civil Plans, C10]
|
|
See Document Markup
Original Comment: Provide Manufacturer Shallow depth configuration detail.
Comment not addressed: Provide custom shallow depth cut sheets provided by contech. They have the ability to provide this upon request. [Civil Plans, C-10]
|
|
See Document Markup
Freeze ex. bioretention to be removed [Civil Plans, C-6]
|
|
See Document Markup
Freeze ex. bioretention to be removed [Civil Plans, C-8]
|
|
See Document Markup
Original comment:Also see city detail.
Comment not addressed: Storm tank observation port detail references "by others" for observation port design. reference COP detail in these locations. [Civil Plans, C-16]
|
|
See Document Markup
filterra Appears to have "heavenly bamboo" on landscape plans. This plant does not appear to be on the approved plants list for filterra. [Landscape Plans, L1]
|
|
See Document Markup
Remove/relocate tree above stormtanks. [Landscape Plans, L1]
|
|
See Document Markup
Original comment: New plus replaced hard surface area needs to be recorded for all basins. and added in table. Use table from preliminary site plan.
Comment not addressed: Response is understood that basin map is showing the quantities of each surface and which facility if any it is directed to. TDA area tables show new areas and existing areas, but it does do not clearly show replaced areas or new+replaced areas.
[Storm Report, Pg 3]
|
|
See Document Markup
I did not see the Track out mat design, install, and maintenance procedures. Please provide in SWPPP. [SWPPP - Appendix E]
|
|
See Document Markup
0.4043 is listed here for just parking, but the basin table for the total hard surfaces shows roof + parking =0.4043. Revisit and confirm numbers. [Storm Report, Pg 33]
|
|
See Document Markup
Original comment: Show required invert drop per detail. Marked up detail shows 2'-2" drop from inlet to outlet inverts. Confirm invert difference is met after receiving the shallow depth detail.
Comment not addressed: if the inlet is below the permanent settling pond level, the upstream pipe will be permanently underwater. [Civil Plans, C-6]
|
|
See Document Markup
Bypass baffle/weir appears to be above the rim elevation of the lowest upstream catch basin, potentially causing a backwater event of runnoff flowing out of catch basin. Confirm whether backwater conflicts exist and correct if present. [Civil Plans, C-10]
|
|
See Document Markup
Existing edge of pavement layer to remain is missing. [Civil Plans, C-2]
|
|
See Document Markup
Existing driveway edge does not line up with proposed approach. edge of pavement missing on east side of southeastern portion of drive-thru driveway. [Civil Plans, C-2]
|
|
See Document Markup
Grading Plan incomplete: Add a complete set of spot elevations and slope labels. label all grade breaks, low spots, high spots, and any grading feature the contractor needs to construct project. Ensure the labels for spot elevations are clear an legible. [Civil Plans - C6]
|
|
See Document Markup
Callout "F" does not have a key note. [Civil Plans, C4]
|
|
See Document Markup
Callout existing street trees to be protected during construction. [Civil Plans, C4]
|
|
See Document Markup
Remove call out tags that do not belong on this sheet. [Civil Plans, C-6]
|
|
See Document Markup
Label ada accessible path with spot elevations and cross slopes to verify ADA requirements are met [Civil Plans, C-76]
|
|
See Document Markup
Freeze remaining utility layers are still shown on site plan. [Civil Plans, C-7]
|
|
See Document Markup
Callout 24 does not have a keynote. [Civil Plans, C-7]
|
|
See Document Markup
Remove contours and elevation markers from site plan sheet. [Civil Plans, C-7]
|
|
See Document Markup
Will ADA signage and striping details be on architectural plans? [Civil Plans, C-7]
|
|
See Document Markup
Call out covered trash enclosure to be per separate building permit and on architectural plans. [Civil Plans, C-7]
|
|
See Document Markup
Add detectable warnings per where required per ADA standards [Civil Plans, C-7]
|
|
See Document Markup
Confirm ADA standards are met at drive thru crosswalks. [Civil Plans, C-7]
|
|
See Document Markup
Add slopes and elevations at ADA landings that change in direction needed [Civil Plans, C-7]
|
|
See Document Markup
Min slope for storm pipe is 0.50% [Civil Plans, C8]
|
|
See Document Markup
Inspection ports do not appear labeled in plan view [Civil Plans, C8]
|
|
See Document Markup
Infiltration trenches with under-drains and Stormtank system are defined as UIC well per the Ecology Manual and shall be registered following Ecology requirements. Acknowledgement of this noted on plans and report will satisfy this comment. See Design Standards Section 203 for more details. [Civil Plans, C-8]
|
|
See Document Markup
Per City Standard Section 402.3 and GI Notes detail, Grease Interceptors shall be constructed to establish "parallel flow" no radius or bend shall be allowed in the inlet pipe upstream for a minimum of 10 feet. [Civil Plans, C-10]
|
|
See Document Markup
Original comment: Roof downspout Detail is not in plans. Provide City roof downspout infiltration detail 02.05.01 and site specific detail as mentioned in comment on sheet C10.
Comment not addressed: City detail applies and is required on plans. [Civil Plans, C-12]
|
|
See Document Markup
GI structure should be 10 feet from building if possible [Civil Plans, C-10]
|
|
See Document Markup
Existing edge of pavement layer to remain is missing. [Civil Plans, C-8]
|
|
See Document Markup
Existing edge of pavement layer to remain is missing. [Civil Plans, C-10]
|
|
See Document Markup
If inlet/outlet inverts need to be the same, the filterra loses the functionality of the settling pool and sediment will eventually clog the upstream pipes. In lieu of a minimum 18" sum for the filterra settling pool, provide a yard drain or catch basin directly upstream with a solid locking lid (if not used for drainage collection )and 18" sump for sediment control. [Civil Plans, C-10]
|
|
See Document Markup
Where can I find the impervious area to be 0.4192? [Storm Report, Pg 48]
|
|
See Document Markup
Storm Pipes and Storm Key Notes are missing letter C. [CIVIL PLANS - RESUB, Sheet C8]
|
|
See Document Markup
|
|
Other/Miscellaneous
Pervious Pavement Comments:
In reviewing BMPT5.15 Permeable Pavements, there is an infeasability criteria that states, "Where infiltrating and ponded water below new permeable pavement area would compromise adjacent impervious pavements." The Applications and Limitations section further states: "No run-on from pervious surfaces is preferred." and “Sheet flow from up gradient impervious areas is not recommended, but permissible if the permeable pavement area is > the impervious pavement area.” From a constructability and a run-on perspective the intermixed design is unlikely to be approved based on this criteria. In addition, we believe the development will exceed recommended traffic volumes for impervious surfaces. With a Starbucks and Taco Time restaurant on the same property, the daily traffic volumes are expected to exceed 400 vehicles per day which exceeds the Manuals definition of 'very low' traffic volumes. Justify the pervious design or provide alternative methods of collection and treatment.
|
|
|
Public Works Streets Review
|
Approved
|
08/21/2024
|
09/05/2024
|
|
|
|
See Document Markup
show note 3 , full sidewalk panel replacement sheet c-6 sh
|
|
See Document Markup
does not show any street patching related to curb and gutter replacement on driveway removals and replacements.... sheet c-6 sh
|
|
See Document Markup
with this much street cut and patching this should be half road grind/overlay....sheet c-6 sh
|
|
See Document Markup
|
|
See Document Markup
|
|
See Document Markup
|
|
See Document Markup
|
|
|
Planning Review
|
Failed
|
08/21/2024
|
08/27/2024
|
|
|
|
Final Landscape Plan - Soil Req.
Please replace Planting Note #5 (1) with the following note on the landscape plan, “A minimum of eight (8) inches of top soil, containing ten percent dry weight in planting beds, and 5% organic matter content in turf areas, and a pH from 6.0 to 8.0 or matching the pH of the original undisturbed soil. The topsoil layer shall have a minimum depth of eight inches (8”) except where tree roots limit the depth of incorporation of amendments needed to meet the criteria. Subsoils below the topsoil layer should be scarified at least 6 inches with some incorporation of the upper material to avoid stratified layers, where feasible. Installation of the eight inches (8”) of top soil, as described above, shall generally be achieved by placing five inches (5”) of imported sandy-loam top soil into planned landscape areas (sub-base scarified four inches (4”)) with a three-inch (3”) layer of compost tilled into the entire depth.” [landscape plan, L-2]
|
|
Final Landscape Plan - Mulch Req.
Add the following note to the civil plans and update any other notations with anything other than 4" of mulch to be consistent with this requirement, "All planting areas shall be mulched with a uniform four (4”) inch layer of organic compost mulch material or wood chips over a properly cleaned, amended and graded subsurface." [landscape plan, L-2]
|
|
Final Landscape Plan - Min Shrub Size
All shrubs required shall be no smaller than two (2) gallon in size at the time of planting [landscape plan, L-1]
|
|
Final Landscape Plan - Min Coniferous Tree Size
Coniferous evergreen trees shall be a minimum of 5 to 6 feet in height.
|
|
Final Landscape Plan - Plant Quantities
Please spec the total quantity of plants and on-center spacing for all landscape areas in the plant schedule. Shrub spacing is missing from Type IIa on-center call out, tree spacing is missing from Type IIIa on-center call out.
Type IIa Landscaping:
The type IIa treatment standard is intended to apply most often to non-residential
commercial and mixed-use development. A single row of medium to large trees (or small trees if
overhead utilities are present) suitably spaced in association with a 50/50 mix of evergreen and
deciduous shrubs to provide the minimum 75 percent visual separation up to a height of 4.5 feet
above the local grade within three years. Trees shall be planted at intervals of no greater than 30
feet. Appropriate shrub masses and living ground cover shall provide 75 percent ground area
coverage within three years. Shrubs shall be placed at 5–7-foot center intervals throughout the
planting area, with ground cover plantings placed at 18-36” on-center intervals. Shrubs shall be
alternated, modulated and designed to provide a visual variation in height, depth, contrasting
colors and textures. No turf grass shall be planted within the required landscape yard (typically
10-12’ for front and street side yard areas, see PMC 20.58.005 (2). Bio-swales or rain gardens
may be placed within these landscaping areas as long as they are designed to meet the intent of
this section.
For Type IIIa Landscaping:
A minimum of one row of trees, consisting generally of native deciduous trees but may
include up to 50 percent native evergreen conifer trees that will create a grouped cluster of
canopy coverage. Appropriate native flowering shrubs (see list above) shall provide 75 percent
visual buffering from the ground to six feet above abutting area grade. One shrub shall be
provided at 7.5’ minimum on center spacing intervals – species shall be alternated and
successive species of blooming native shrubs for early, mid/early, mid and late season shall be
used. Additional shrubs and live NW native ground cover species shall cover at least 75 percent
of planting area within three years. At least one tree shall be provided for each 40 lineal feet.
Tree spacing may be adjusted to better suit the selected species and installation size while still
achieving the intended result of clustered canopy grouping over the lower planting in a timely
manner. Bio-swales or rain gardens may be placed within these landscaping areas as long as they
are designed to meet the intent of this section.
[landscape plan, L-1]
|
|
Final Landscape Plan - Stormwater Facilities
Storm water facilities, including bioretention areas, swales, and raingardens, shall be landscaped in accordance with SLD-02, contained in the Vegetation Management Standards Manual (VMS).
|
|
Final Landscape Plan - Tree protection plan
Comment outstanding: 08/27
The Large Douglas Fir is still not shown on the TESC & demolition plan set.
Existing trees to be retained must be clearly marked on the final clearing and grading plan, and final landscape plan.
Tree protection fencing and signage shall follow the city standard detail, see appendix 20.5. Standard detail shall be included on all plan sets with vegetation which is scheduled for retention and protection. All critical root protection zones (CRPZ) shall be shown on plan sets in diameter from the center of the tree. In determining tree CRPZ, the following standards shall be used.
In establishing the extent of the Critical Root Protection Zone (CRPZ) for individual significant trees, groupings of significant trees, a stand of significant trees, or a heritage tree the following formula shall be used: Individual tree diameter (in inches) X 2, converted into feet = CRPZ, in diameter (Example: 20” tree X 2 = 40’ CRPZ diameter).
The following minimum performance standards shall be used to determine the extent of allowable impacts to the CRPZ of significant trees: For significant trees, a minimum of 50 percent of the critical root zone must be preserved at natural grade, with natural ground cover. The protection zone may be irregular. The plan set shall provide a total square footage of CRPZ area and show the % of disturbance area. For heritage trees, a minimum of 75 percent of the critical root zone must be preserved at natural grade with natural ground cover. The protection zone may be irregular. The plan set shall provide a total square footage of CRPZ area and show the % of disturbance area.
No cut or fill greater than four (4) inches in depth may be located closer to the tree trunk than ½ the CRPZ radius distance. (Example, 20-inch DBH tree has a 40’ CRPZ area (in diameter) - meaning no cut or fill greater than 4” in depth is allowed within 20’ of the tree trunk). No cut or fill within the distance from the tree which is three (3) times the trunk DBH is allowed. (Example, 20-inch DBH tree X 3 = 60”, meaning no cut is allowed within 60-inches of a tree which has a 20-inch diameter trunk).
These criteria represent minimum standards for determining whether or not a tree may be required to be retained. Greater impacts may be allowed, provided that all design alternatives have been proven unfeasible and that a pre-conditioning and after care mitigation program is established. See section 10.1 of the VMS, and referenced appendices for more information.
|
|
Final Landscape Plan - Sight Distance Standards
Sight Distance standards. Adjacent to public rights-of-way and points of access, no fences or landscape material at maturity, shall exceed three (3) feet above the local finish grade within a clear sight triangle. Please spec plants that meet this standard and, please show the sight distance area on the plans. Current proposed plants exceed the maximum 3-foot maturity. [landscape plan, L-1]
|
|
Final Landscape Plan - Landscape Types
The City's Vegetation Management Standards Manual (VMS) outlines specific treatment “types” that are required to be adhered to, dependent upon the yard area the landscaping is located within. See the VMS, sections 13 and 14 for full details. The VMS can be downloaded here: https://www.cityofpuyallup.org/puyallupvms
|
|
See Document Markup
Verify that the total estimated topsoil required is for the 8-inch minimum soil standard for all landscaped areas. Your contractor will be required to submit delivery sheets and demonstrate compliance with top soil required and specified on plans at the time of final inspection. [landscape plan, L-1]
|
|
Final Landscape Plan - Details
Comment outstanding: 08/27
Add required landscape details to plan: Detail 01.02.06, 01.02.08
Landscape details can be found at: https://www.cityofpuyallup.org/1445/100---Roadway
|
|
Miscellaneous Planning Correction
- Recent resubmittal includes a note to: "see arborist report prepared by WA Forestry Consultants. Cannot locate this document in the resubmittal, please upload.
As a condition of approval of the associated preliminary site plan, we require a tree risk assessment or be performed by a certified arborist:
Existing tree(s) on the site which are larger than 15" in Diameter at Breast Height (DBH) are considered to be a 'significant tree' and must be retained, where possible. If your site includes any significant trees, then you must include a tree risk assessment completed by a certified arborist and provided with your civil permit application.
|
|
See Document Markup
Comment outstanding: 08/27
This was a condition of approval for the preliminary site plan. The trees in this northern area should at least be native conifers. An attempt needs to be made to fulfill this condition.
Please re-vegetate the disturbed area with native conifers and shrubs. No native conifers have been proposed in this area. Options for native conifers can be found in VMS 12.7 and must meet spacing standards. [landscape plan, L-1]
|
|
See Document Markup
Comment outstanding: 08/27
The utilities have still not been placed back onto the landscape plan. This is required and in order for a full review, staff needs to be able to see where the utilities are in relation to the proposed landscaping.
Any required trees that are proposed too close to utility lines and are unable to be moved to meet the 10ft spacing requirement from utilities shall be moved to this lawn area if possible. Use root barriers per engineerings direction if necessary. [landscape plan, L-1]
|
|
Other/Miscellaneous
Silva cells are required around all internal landscape islands. Please show on landscape plans and include silva cell detail on the landscape plan set mirroring the approved storm plans from the preliminary site plan. [landscape plan]
|
|
See Document Markup
Coniferous evergreen trees shall be a minimum of 5-6ft in height per VMS 7.2(f)
[landscape plan, L-1]
|
|
Final Landscape Plan - Street Tree Site Prep
Partially addressed: 08/27
Needs to be Addressed:
Integrate the Street Tree Installation Standards Table (page 25 of the VMS) into plan sets. Please observe required spacing standards, as outlined in the table, when preparing drawings. The city has required species mix requirements based on the quantity of street trees to be planted as a part of the project.
Needs to be Addressed:
The ‘Existing Conditions and Demolition Plan’ does not show the utilities along the eastern property you are describing that prevent larger trees from being planted. If utilities are present on site and are part of the reason larger trees cannot be provided please show the utilities. There is a large, private easement on the east side of the property, but no utilities are shown in it:
Please check section 12.11 when specifying species to be planted. The city’s policy is to plant the largest canopy tree for the rooting/overhead space available (section 12.4, VMS). Please note this when specifying tree species for the planter strip.
Addressed: Street tree soil requirements. See section 8.2 of the VMS. Copy and paste the applicable section for street tree top soil and place on plans as requirement to meet the city standards. Root barriers, in accordance with city standards, are required for all street trees. A minimum of 8’ of linear protection along the edge of the sidewalk adjacent to the street tree shall be provided, using a minimum 24” deep root barrier panels.
Addressed: Integrate city standard detail 01.02.08a – soil amendment and depth. NOTE: Top soil placement/installation specs, depth and quality standards can be found in section 8.2 of the VMS. For new construction, cut and paste ALL of section 8.2(b) of the VMS into the planting notes/details of the final landscape plan sheets.
Addressed: See section 12.6 of the VMS for more information. Some common species of street trees are prohibited due to overuse and other reasons.
|
|
See Document Markup
Type IIIa landscaping requires trees to be selected from the list of Class IV large street trees list. Adjust plans and plant schedule accordingly. (landscape plan, L-1]
|
|
See Document Markup
Plant schedule should propose trees from VMS Chapter 12. Please remove tree types that are not listed and replace with allowed tree types. Please note that Type III perimeter landscaping require trees to be selected from VMS 12.10 Class IV - Large Street Trees.
[landscape plan, L-1]
|
|
See Document Markup
The landscape types (Type I, Type II, etc.) require specific on-center spacing to be met. Please meet on-center spacing standards.
[landscape plan, L-1]
|
|
Add Submittal Item: Misc
Additional Submittal Item Required: As part of the SEPA MDNS The Puyallup Tribe of Indians requested that Archaeological Monitoring be present during ground disturbance as 1115 E Main is located within a high probability area for impacting cultural resources. The city identified this as a mitigation measure in the preparation of the SEPA MDNS. Such a condition requires the applicant to identify this requirement in the civil and building permit applications and to ensure that Archaeological Monitoring is present during ground disturbance.
This requirement cannot be foregone. Planning will attend the pre-con meeting to remind the contractor and inspectors that this requirement must be met. Prior to Planning final inspection approval, we will require a report from the Archaeological Monitor.
|
|
See Document Markup
Call out pedestrian walkway for access from the parking lot. The pedestrian crosswalk for access from the parking lot, through the drive-through lane, to the restaurant is required to be raised, ADA-accessible, and meet the other requirements in PMC 0.31.040 (13)(d).
[civil plans, C-6]
|
|
Other/Miscellaneous
Comment Outstanding 082124
Applicant has stated that existing and proposed utilities are shown on landscape plan, but they are still not shown. Utilities are required to be shown on the final landscape plan.
Original landscape submittal included utility overlay, but utilities have been removed in the most recent landscape plan submittal. Please resubmit landscape plans with utility overlay.
|
|
See Document Markup
Stockpile area needs to move away from any retained trees. Stockpile is currently proposed where the retained Douglas Fir is. [civil plan, C-4]
|
|
See Document Markup
Add CRPZ protection to all retained trees on the TESC plan and demolition plan. [civil plan, C-3 & C-4]
|
|
See Document Markup
Show Douglas Fir on TESC plan and demolition plan. [civil plan, C-3 & C-4]
|
|
See Document Markup
No more than 8 parking stalls shall be consecutively without a landscaping island [landscape plan, L-1]
|
|
Other/Miscellaneous
This civil application includes the tenant improvement of the existing Taco Time building to be converted to a Starbucks. A total of 55 stalls are required for Taco Time & Starbucks. Parking count is not met. Please update all plans to include 55 stalls. Please note that no more than 8 parking stalls shall be consecutively without a landscaping island. This comment was conveyed to the applicant in an e-mail dated 03/27/2024 as well.
|
|
|
Engineering Traffic Review
|
Approved
|
08/21/2024
|
08/22/2024
|
|
|
|
Other/Miscellaneous
Please update sight distance analysis per City geometric standards standards (300ft ESD for 25mph). Assume driver's eye is setback 14.5ft from face of curb. Horizonal profile not provided. Any sight obstructions (signage, trees, fences, etc.) must be identified.
On sheet C-2, driveway striping (white/yellow) should be MMA. Recommend extending the yellow centerline striping farther on-site to help transition inbound vehicles to 24ft wide drive isle.
|
|
|
Public Works Water Review
|
Approved
|
08/21/2024
|
08/13/2024
|
|
|
|
See Document Markup
Civil Resub Sheet C-14: Since a new fire hydrant is no longer part of this plan, remove City Standard detail 03.05.01.
|
|
See Document Markup
Civil C-8: Show 2-inch GV at tap to 12-inch water.
|
|
See Document Markup
Civil C-8: Set meter directly behind sidewalk.
|
|
See Document Markup
Civil C-8: Landscape plans show irrigation point of connection at back of meter. Show this on Civil plans. Insert irrigation tee between meter setter and domestic RPBA. Add DCVA after irrigation tee. Call out size of DCVA. Add City standard detail 03.04.01 to plan set.
|
|
See Document Markup
Civil C-8: Bring existing water service to current City standards. Install ArmorCast meter box and raise box and meter setter to correct height.
|
|
See Document Markup
Civil C-8: Call out 4-inch wet tap on 12-inch water main and show GV at tee.
|
|
See Document Markup
Civil C-8: Call out 6-inch wet tap on 12-inch water main and show GV at tee.
|
|
See Document Markup
Civil C-8: Set center of hydrant 1-foot 6-inch behind sidewalk edge.
|
|
See Document Markup
Civil C-8: FDC shall be 10-foot minimum and 15-foot maximum from fire hydrant.
|
|
|
Public Works Collection Review
|
Approved
|
08/21/2024
|
08/05/2024
|
|
|
|
|
Fire Review
|
Approved
|
08/21/2024
|
07/26/2024
|
|
|
|
|
Public Works Streets Review
|
Failed
|
02/09/2024
|
02/09/2024
|
|
|
|
See Document Markup
show note 3 , full sidewalk panel replacement sheet c-6 sh
|
|
See Document Markup
does not show any street patching related to curb and gutter replacement on driveway removals and replacements.... sheet c-6 sh
|
|
See Document Markup
with this much street cut and patching this should be half road grind/overlay....sheet c-6 sh
|
|
|
Engineering Traffic Review
|
Failed
|
02/09/2024
|
02/08/2024
|
|
|
|
Other/Miscellaneous
Per Preliminary Site Plan approval conditions:
Sight distance analysis will be required during civil review to ensure driveway(s) can meet City standards for entering sight distance. Any sight obstructions (signage, trees, fences, etc.) must be identified.
During civil design channelization/striping plan will be required. Proposed channelization arrows & striping cannot be located on sidewalk. Arrows must be thermoplastic.
During civil design AutoTurn analysis will be required to ensure design vehicles can safely navigate site.
|
|
Other/Miscellaneous
Please update sight distance analysis per City geometric standards standards (300ft ESD for 25mph). Assume driver's eye is setback 14.5ft from face of curb. Horizonal profile not provided. Any sight obstructions (signage, trees, fences, etc.) must be identified.
On sheet C-2, driveway striping (white/yellow) should be MMA. Recommend extending the yellow centerline striping farther on-site to help transition inbound vehicles to 24ft wide drive isle.
|
|
|
Fire Review
|
Approved
|
02/09/2024
|
02/08/2024
|
|
|
|
Other/Miscellaneous
1. Parcel lines do not match Pierce County Assessor’s page or Puyallup’s GIS. Provide exact site plan for review.
2. New Fire Hydrant location will not be approved. Move Fire Hydrant by main entrance.
3. New FDC location will not be approved. FDC Location needs to be accessible onsite and not from Main Street. Move FDC to Westside of structure by drive through leaving enough room for a fire apparatus to park onsite and hook up. FDC should be max 15’ from Fire Hydrant.
4. Provide No Parking Sign / Fire Lane layout with painted and stenciled curbs on both sides of main entrance. Painted curb required at all non-parking stalls and around parking aisles. Show details on plans with sign callouts.
|
|
|
Public Works Collection Review
|
Approved
|
02/09/2024
|
02/05/2024
|
|
|
|
See Document Markup
This would be the location of the commercial side sewer connection with sampling tee. Adjust the 8x6 reducer location until after this point. Civil C-8.
|
|
|
Planning Review
|
Failed
|
02/09/2024
|
02/02/2024
|
|
|
|
Final Landscape Plan - Soil Req.
Please replace Planting Note #5 (1) with the following note on the landscape plan, “A minimum of eight (8) inches of top soil, containing ten percent dry weight in planting beds, and 5% organic matter content in turf areas, and a pH from 6.0 to 8.0 or matching the pH of the original undisturbed soil. The topsoil layer shall have a minimum depth of eight inches (8”) except where tree roots limit the depth of incorporation of amendments needed to meet the criteria. Subsoils below the topsoil layer should be scarified at least 6 inches with some incorporation of the upper material to avoid stratified layers, where feasible. Installation of the eight inches (8”) of top soil, as described above, shall generally be achieved by placing five inches (5”) of imported sandy-loam top soil into planned landscape areas (sub-base scarified four inches (4”)) with a three-inch (3”) layer of compost tilled into the entire depth.” [landscape plan, L-2]
|
|
Final Landscape Plan - Mulch Req.
Add the following note to the civil plans and update any other notations with anything other than 4" of mulch to be consistent with this requirement, "All planting areas shall be mulched with a uniform four (4”) inch layer of organic compost mulch material or wood chips over a properly cleaned, amended and graded subsurface." [landscape plan, L-2]
|
|
Final Landscape Plan - Min Shrub Size
All shrubs required shall be no smaller than two (2) gallon in size at the time of planting [landscape plan, L-1]
|
|
Final Landscape Plan - Min Coniferous Tree Size
Coniferous evergreen trees shall be a minimum of 5 to 6 feet in height.
|
|
Final Landscape Plan - Plant Quantities
Please spec the total quantity of plants and on-center spacing for all landscape areas in the plant schedule. Shrub spacing is missing from Type IIa on-center call out, tree spacing is missing from Type IIIa on-center call out.
Type IIa Landscaping:
The type IIa treatment standard is intended to apply most often to non-residential
commercial and mixed-use development. A single row of medium to large trees (or small trees if
overhead utilities are present) suitably spaced in association with a 50/50 mix of evergreen and
deciduous shrubs to provide the minimum 75 percent visual separation up to a height of 4.5 feet
above the local grade within three years. Trees shall be planted at intervals of no greater than 30
feet. Appropriate shrub masses and living ground cover shall provide 75 percent ground area
coverage within three years. Shrubs shall be placed at 5–7-foot center intervals throughout the
planting area, with ground cover plantings placed at 18-36” on-center intervals. Shrubs shall be
alternated, modulated and designed to provide a visual variation in height, depth, contrasting
colors and textures. No turf grass shall be planted within the required landscape yard (typically
10-12’ for front and street side yard areas, see PMC 20.58.005 (2). Bio-swales or rain gardens
may be placed within these landscaping areas as long as they are designed to meet the intent of
this section.
For Type IIIa Landscaping:
A minimum of one row of trees, consisting generally of native deciduous trees but may
include up to 50 percent native evergreen conifer trees that will create a grouped cluster of
canopy coverage. Appropriate native flowering shrubs (see list above) shall provide 75 percent
visual buffering from the ground to six feet above abutting area grade. One shrub shall be
provided at 7.5’ minimum on center spacing intervals – species shall be alternated and
successive species of blooming native shrubs for early, mid/early, mid and late season shall be
used. Additional shrubs and live NW native ground cover species shall cover at least 75 percent
of planting area within three years. At least one tree shall be provided for each 40 lineal feet.
Tree spacing may be adjusted to better suit the selected species and installation size while still
achieving the intended result of clustered canopy grouping over the lower planting in a timely
manner. Bio-swales or rain gardens may be placed within these landscaping areas as long as they
are designed to meet the intent of this section.
[landscape plan, L-1]
|
|
Final Landscape Plan - Stormwater Facilities
Storm water facilities, including bioretention areas, swales, and raingardens, shall be landscaped in accordance with SLD-02, contained in the Vegetation Management Standards Manual (VMS).
|
|
Final Landscape Plan - Tree protection plan
Existing trees to be retained must be clearly marked on the final clearing and grading plan, and final landscape plan. Tree protection fencing and signage shall follow the city standard detail, see appendix 20.5. Standard detail shall be included on all plan sets with vegetation which is scheduled for retention and protection. All critical root protection zones (CRPZ) shall be shown on plan sets in diameter from the center of the tree. In determining tree CRPZ, the following standards shall be used.In establishing the extent of the Critical Root Protection Zone (CRPZ) for individual significant trees, groupings of significant trees, a stand of significant trees, or a heritage tree the following formula shall be used: Individual tree diameter (in inches) X 2, converted into feet = CRPZ, in diameter (Example: 20” tree X 2 = 40’ CRPZ diameter). The following minimum performance standards shall be used to determine the extent of allowable impacts to the CRPZ of significant trees: For significant trees, a minimum of 50 percent of the critical root zone must be preserved at natural grade, with natural ground cover. The protection zone may be irregular. The plan set shall provide a total square footage of CRPZ area and show the % of disturbance area. For heritage trees, a minimum of 75 percent of the critical root zone must be preserved at natural grade with natural ground cover. The protection zone may be irregular. The plan set shall provide a total square footage of CRPZ area and show the % of disturbance area. No cut or fill greater than four (4) inches in depth may be located closer to the tree trunk than ½ the CRPZ radius distance. (Example, 20-inch DBH tree has a 40’ CRPZ area (in diameter) - meaning no cut or fill greater than 4” in depth is allowed within 20’ of the tree trunk). No cut or fill within the distance from the tree which is three (3) times the trunk DBH is allowed. (Example, 20-inch DBH tree X 3 = 60”, meaning no cut is allowed within 60-inches of a tree which has a 20-inch diameter trunk). These criteria represent minimum standards for determining whether or not a tree may be required to be retained. Greater impacts may be allowed, provided that all design alternatives have been proven unfeasible and that a pre-conditioning and after care mitigation program is established. See section 10.1 of the VMS, and referenced appendices for more information.
|
|
Final Landscape Plan - Sight Distance Standards
Sight Distance standards. Adjacent to public rights-of-way and points of access, no fences or landscape material at maturity, shall exceed three (3) feet above the local finish grade within a clear sight triangle. Please spec plants that meet this standard and, please show the sight distance area on the plans. Current proposed plants exceed the maximum 3-foot maturity. [landscape plan, L-1]
|
|
Final Landscape Plan - Landscape Types
The City's Vegetation Management Standards Manual (VMS) outlines specific treatment “types” that are required to be adhered to, dependent upon the yard area the landscaping is located within. See the VMS, sections 13 and 14 for full details. The VMS can be downloaded here: https://www.cityofpuyallup.org/puyallupvms
|
|
See Document Markup
Verify that the total estimated topsoil required is for the 8-inch minimum soil standard for all landscaped areas. Your contractor will be required to submit delivery sheets and demonstrate compliance with top soil required and specified on plans at the time of final inspection. [landscape plan, L-1]
|
|
Final Landscape Plan - Trash Containers
All trash containers shall be screened from abutting properties and public rights-of-way by substantial sight-obscuring landscaping. Sight-obscuring fences and walls can be substituted for plant materials. Show trash enclosure area on landscape plan set.
|
|
Final Landscape Plan - Details
Add required landscape details to plan: Detail 01.02.06, 01.02.08
Landscape details can be found at: https://www.cityofpuyallup.org/1445/100---Roadway
|
|
Landscaping Req.: General (VMS)
Landscaping Requirements: PMC 20.58 outlines landscaping requirements. All portions of a lot not devoted to building, future building, parking, access drives, walks, storage or accessory uses shall be landscaped in a manner consistent with the requirements of this chapter. The City also has a companion design manual – the Vegetation Management Standards (VMS) manual – found here: www.cityofpuyallup.org/puyallupvms. Please consult both the code landscape code section and the VMS for a full list of landscape requirements.
|
|
Miscellaneous Planning Correction
- Recent resubmittal includes a note to: "see arborist report prepared by WA Forestry Consultants. Cannot locate this document in the resubmittal, please upload.
As a condition of approval of the associated preliminary site plan, we require a tree risk assessment or be performed by a certified arborist:
Existing tree(s) on the site which are larger than 15" in Diameter at Breast Height (DBH) are considered to be a 'significant tree' and must be retained, where possible. If your site includes any significant trees, then you must include a tree risk assessment completed by a certified arborist and provided with your civil permit application.
|
|
See Document Markup
Please re-vegetate the disturbed area with native conifers and shrubs. No native conifers have been proposed in this area. Options for native conifers can be found in VMS 12.7 and must meet spacing standards. [landscape plan, L-1]
|
|
See Document Markup
Any required trees that are proposed too close to utility lines and are unable to be moved to meet the 10ft spacing requirement from utilities shall be moved to this lawn area if possible. Use root barriers per engineerings direction if necessary. [landscape plan, L-1]
|
|
Other/Miscellaneous
Trees are required to be spaced at least 7.5' from the driveway (measured from the outer edge of driveway paving). Please adjust accordingly. [landscape plan, L-1]
|
|
Other/Miscellaneous
Silva cells are required around all internal landscape islands. Please show on landscape plans and include silva cell detail on the landscape plan set mirroring the approved storm plans from the preliminary site plan. [landscape plan]
|
|
Other/Miscellaneous
All tree selection shall follow the concept of ‘right-tree, right-place’; the largest tree should be used for the rooting and overhead space available to improve overall canopy coverage throughout the city. [landscape plan, L-1]
|
|
See Document Markup
Coniferous evergreen trees shall be a minimum of 5-6ft in height per VMS 7.2(f)
[landscape plan, L-1]
|
|
See Document Markup
Eastern landscape buffer required to be a minimum of 6'. Plans measure to be 5'5". [landscape plan, L-1]
|
|
See Document Markup
Label retaining wall on plan set [landscape plan, L-1]
|
|
Final Landscape Plan - Street Tree Site Prep
Street tree soil requirements. See section 8.2 of the VMS. Copy and paste the applicable section for street tree top soil and place on plans as requirement to meet the city standards. Root barriers, in accordance with city standards, are required for all street trees. A minimum of 8’ of linear protection along the edge of the sidewalk adjacent to the street tree shall be provided, using a minimum 24” deep root barrier panels.
Integrate city standard detail 01.02.08a – soil amendment and depth. NOTE: Top soil placement/installation specs, depth and quality standards can be found in section 8.2 of the VMS. For new construction, cut and paste ALL of section 8.2(b) of the VMS into the planting notes/details of the final landscape plan sheets.
Integrate the Street Tree Installation Standards Table (page 25 of the VMS) into plan sets. Please observe required spacing standards, as outlined in the table, when preparing drawings. The city has required species mix requirements based on the quantity of street trees to be planted as a part of the project.
See section 12.6 of the VMS for more information. Some common species of street trees are prohibited due to overuse and other reasons.
Please check section 12.11 when specifying species to be planted. The city’s policy is to plant the largest canopy tree for the rooting/overhead space available (section 12.4, VMS). Please note this when specifying tree species for the planter strip.
|
|
See Document Markup
Add a tree selected from the Class III or Class IV street tree list show in section 12.9 or 12.10 of the VMS in this parking lot landscape island [landscape plan, L-1]
|
|
See Document Markup
Type IIIa landscaping requires trees to be selected from the list of Class IV large street trees list. Adjust plans and plant schedule accordingly. (landscape plan, L-1]
|
|
See Document Markup
Plant schedule should propose trees from VMS Chapter 12. Please remove tree types that are not listed and replace with allowed tree types. Please note that Type III perimeter landscaping require trees to be selected from VMS 12.10 Class IV - Large Street Trees.
[landscape plan, L-1]
|
|
See Document Markup
Tree on east of driveway can be moved slightly further east to meet maximum 30ft spacing standard for Type IIa landscaping requirements. [landscape plan, L-1]
|
|
See Document Markup
The landscape types (Type I, Type II, etc.) require specific on-center spacing to be met. Please meet on-center spacing standards.
[landscape plan, L-1]
|
|
Add Submittal Item: Misc
Additional Submittal Item Required: As part of the SEPA MDNS The Puyallup Tribe of Indians requested that Archaeological Monitoring be present during ground disturbance as 1115 E Main is located within a high probability area for impacting cultural resources. The city identified this as a mitigation measure in the preparation of the SEPA MDNS. Such a condition requires the applicant to identify this requirement in the civil and building permit applications and to ensure that Archaeological Monitoring is present during ground disturbance.
|
|
See Document Markup
Call out pedestrian walkway for access from the parking lot. The pedestrian crosswalk for access from the parking lot, through the drive-through lane, to the restaurant is required to be raised, ADA-accessible, and meet the other requirements in PMC 0.31.040 (13)(d).
[civil plans, C-6]
|
|
Other/Miscellaneous
Original landscape submittal included utility overlay, but utilities have been removed in the most recent landscape plan submittal. Please resubmit landscape plans with utility overlay.
|
|
|
Engineering Civil Review
|
Failed
|
02/09/2024
|
02/01/2024
|
|
|
|
Add Submittal Item: Misc
Additional Submittal Item Required: Add the most recent survey, separate from Civil Plans, to the Survey submittal bucket. The Survey should have existing topography, existing easements, existing storm facilities, etc. This can be used to satisfy existing conditions requirements in civil plans.
|
|
See Document Markup
Original comment: Trees shall not be located within 10-ft horizontally of stormwater pipes unless root barriers are provided.
- Root barriers: trees may be no closer than 3-ft to pipes.
Comment does not appear to be addressed. [Landscape Plans, L1]
|
|
See Document Markup
Show filterra is free of conflict and with an approved tree inside per manufacturer specs. [Landscape Plans, L1]
|
|
See Document Markup
Original comment: Grease interceptor access manholes must be uncovered and clear of vegetation.
Comment does not appear to be addressed. [Landscape Plans, L1]
|
|
See Document Markup
Fire vault acess must be uncovered and clear of vegetation. [Landscape Plans, L1]
|
|
See Document Markup
Original comment: Provide root barriers for proposed trees near existing and proposed infiltration facilities.
Comment does not appear to be addressed. [Landscape Plans, L1]
|
|
See Document Markup
Provide clear space for FDC [Landscape Plans, L1]
|
|
See Document Markup
Original comment: Provide clear space for fire hydrant.
Comment does not appear to be addressed. [Landscape Plans, L1]
|
|
See Document Markup
Original comment: Trees shall not be located within 10-ft horizontally of sewer pipes unless root barriers are provided.
- Root barriers: trees may be no closer than 3-ft to pipes.
Comment does not appear to be addressed. [Landscape Plans, L1]
|
|
See Document Markup
No woody landscape plants shall be planted within 10 feet of any water meter. [Landscape Plans, L1]
|
|
See Document Markup
COP Design Standards Section 2.1(13): Add current zoning of adjacent lots. [Civil Plans, C-1]
|
|
See Document Markup
Erosion & Sediment Inspection is completed through CityView Portal after pre-construction meeting. This note is not required to be on the plans. [Civil Plans, [C-1]
|
|
See Document Markup
COP Design Standards Section 2.1(22): Label Puyallup River on all applicable sheets. [Civil Plans, C-1]
|
|
See Document Markup
COP Design Standards Section 2.1(14): Label property lines with distance and bearings on each sheet with plan view. [Civil Plans, C-1]
|
|
See Document Markup
COP Design Standards Section 2.1(11): Add a brief legal description of the site, in enough detail to locate the property, including parcel number, 1/4 section, township, and range shall be located below the vicinity map. [Civil Plans, C-1]
|
|
See Document Markup
COP Design Standards Section 1.0(1.4): Approval block should be 2-1/4" x 3-1/4". [Civil Plans, C-1]
|
|
See Document Markup
COP Design Standards Section 2.1(10): The vicinity map shall be located on the lower right of the first sheet with the project site approximately centered. A north arrow shall be on the map. The site address shall be shown below the vicinity map. [Civil Plans, C-1]
|
|
See Document Markup
Original Comment: Revise 811 label.
Comment not addressed: See comment in plan view with leader pointing to rogue 811 text in conflict with planview. [Civil Plans, C-1]
|
|
See Document Markup
This additional Vicinity map is not necessary. If it is kept, frame it with scale and north arrow. Freeze utilities, hatches, trees, setbacks, and label street, river, new buildings and ex buildings. [Civil Plans, C-1]
|
|
See Document Markup
Freeze utilities and existing conditions to be removed. [Civil Plans, C-1]
|
|
See Document Markup
COP Design Standards Section 2.1(19): Show and dimension existing and proposed easements on all sheets. Show all Pierce County recording numbers for existing easements. [Civil Plans, C-1]
|
|
See Document Markup
Add legend with existing and proposed lines and sybmols . [Civil Plans, C-1]
|
|
See Document Markup
Add existing and proposed surface area table from Preliminary Site Plan Submital. Use the table format given separately under Docs & Images. Additionally break up new plus replaced hard surfaces and effective new plus replaced hard surfaces into the separate TDAs. Provide [Civil Plans, C-1]
|
|
See Document Markup
Original comment: Screen (gray) back existing conditions to remain on all sheets.
Comment not addressed: existing and proposed elements appear on the plans to be the same shading and line types. Differentiate from the existing and proposed elements. (includes but not limited to buildings, concrete, utilities, etc.) [Civil Plans, C-1]
|
|
See Document Markup
Add Grading plan with spot elevations, slope labels, and proposed topography. [Civil Plans, C-1]
|
|
See Document Markup
Original comment: This hatch does not show up well in BlueBeam. Revise proposed pavement hatch to be more visible.
Comment not addressed: Proposed hatching needs to be more visible, not less. I understand it shows clearly when printing on paper, but it disappears when zooming out on bluebeam. Consider a different pattern or solid hatch that will not disappear when zoomed out. Its seems to work on sheet C-7. [Civil Plans, C-1]
|
|
See Document Markup
Show fill and/or excavation quantities in cubic yards. [Civil Plans, C-1]
|
|
See Document Markup
Add note, "A separate building permit is required for trash enclosure" [Civil Plans, C-1]
|
|
See Document Markup
Add monument protection note. [Civil Plans, C-1]
|
|
See Document Markup
Freeze utilities and existing conditions to be removed. [Civil Plans, C-2]
|
|
See Document Markup
Tie horizontal control to a property corner. [Civil Plans, C-2]
|
|
See Document Markup
Hatch concrete for contrast legibility. [Civil Plans, C-2]
|
|
See Document Markup
Horizontal control Plan looks incomplete. Curb line and curve table showing tagged curb radii and dimensions are not shown. [Civil Plans, C-2]
|
|
See Document Markup
Remove existing bioswale extents. [Civil Plans, C-2]
|
|
See Document Markup
Add 811 note on all Planview sheets. [Civil Plans, C-2]
|
|
See Document Markup
Show offsite improvements dimensions and curb lengths [Civil Plans, C-2]
|
|
See Document Markup
Show wheel stop separation distance from curb. [Civil Plans, C-2]
|
|
See Document Markup
Change Ex. curb linetype to double the length of dashed line or solid Line. line type is too similar to infiltration gallery. [Civil Plans, C-3]
|
|
See Document Markup
Show top and bottom lines of ex curb. [Civil Plans, C-3]
|
|
See Document Markup
It is unclear what is to remain and what is to be removed. Use bold lines for existing conditions to be removed. [Civil Plans, C-3]
|
|
See Document Markup
Show and provide a protection note for the limits of proposed and existing infiltration facilities. [Civil Plans, C-3]
|
|
See Document Markup
Separate structure and pipe removal callouts for clarity. [Civil Plans, C-3]
|
|
See Document Markup
separate plug callout for clarity. [Civil Plans, C-3]
|
|
See Document Markup
Callout what this sawcut patch is for. [Civil Plans, C-3]
|
|
See Document Markup
Show grind an overlay on plans. [Civil Plans, C-3]
|
|
See Document Markup
Clarify through callouts and labels every item to remain and every item to be removed. [Civil Plans, C-3]
|
|
See Document Markup
Are these trees existing or proposed? Callout existing trees to remain and freeze proposed trees from sheet. [Civil Plans, C-3]
|
|
See Document Markup
add all symbols and lines in legend and add callouts in planview. [Civil Plans, C-3]
|
|
See Document Markup
Is this a wall? specify whether is is to remain or be removed. [Civil Plans, C-3]
|
|
See Document Markup
Existing conditions should match most updated Survey. Survey can be used for existing conditions. [Civil Plans, C-3]
|
|
See Document Markup
for clarity, add screened back concrete hatch for existing to remain and bold concrete hatch for concrete to be removed. [Civil Plans, C-3]
|
|
See Document Markup
There are no proposed items on this sheet. update legend to show applicable lines and symbols. [Civil Plans, C-3]
|
|
See Document Markup
Symbols in legend should match symbols in plan. [Civil Plans, C-3]
|
|
See Document Markup
Pavement removal limits don't match proposed pavement limits. Sawcuts should be straight lines. [Civil Plans, C-3]
|
|
See Document Markup
Show street curb as curb and gutter on all sheets. [Civil Plans, C-3]
|
|
See Document Markup
Show Existing FFE on all sheets with contours. [Civil Plans, C-3]
|
|
See Document Markup
Remove water and electrical lines associated with irrigation on all Civil Sheets. Keep Them on the irrigation plan. [Civil Plans, C-3]
|
|
See Document Markup
Remove all proposed conditions from TESC plan except for infiltration facility limits. [Civil Plans, C-4]
|
|
See Document Markup
Callout infiltration facility and excavation limits. Add compaction protection note. Bottom of facility should be scarified per COP soil amendment standards if compacted by heavy equipment. [Civil Plans, C-4]
|
|
See Document Markup
Callout existing elements. [Civil Plans, C-4]
|
|
See Document Markup
Hatch existing concrete in ROW. [Civil Plans, C-4]
|
|
See Document Markup
Clearly show sawcut limits and of area to be disturbed during construction. [Civil Plans, C-4]
|
|
See Document Markup
Designate one entrance for construction entrance. The entrance may move or be adjusted as needed and after inspector notification and approval. [Civil Plans, C-4]
|
|
See Document Markup
An existing stabilized entrance may function as a construction entrance but must have an "approved equal" track-out device/facility installed on it. email Review engineer with track-out facility proposal for approval prior to next submittal. [Civil Plans, C-4]
|
|
See Document Markup
Original Comment: Show cross hatch symbol for inlet protection on all onsite and offsite inlets within project vicinity to remain.
Comment not addressed: Offsite CBs and some onsite CBs where not marked for inlet protection. [Civil Plans, C-4]
|
|
See Document Markup
Label Street. [Civil Plans, C-4]
|
|
See Document Markup
Reference which sheet details are located on in Keynotes. [Civil Plans, C-4]
|
|
See Document Markup
All existing trees 6 inches diameter at breast height or larger, which are proposed to be removed, or retained. The location, size and species of each tree shall be shown. [Civil Plans, C-4]
|
|
See Document Markup
Show type of fill material and compaction requirements. [Civil Plans, C-4]
|
|
See Document Markup
State whether or not the fill material will be placed upon native or stripped vegetation. [Civil Plans, C-4]
|
|
See Document Markup
Clearly show the limits of fill and/or excavation work. [Civil Plans, C-4]
|
|
See Document Markup
Show clearing limits [Civil Plans, C-4]
|
|
See Document Markup
Add excavation note with cut/fill slope limits and when shoring is required. [Civil Plans, C-4]
|
|
See Document Markup
Move #6 before #4. All TESC elements should be in place prior to TESC inspection with the City. [Civil Plans, C-5]
|
|
See Document Markup
Add install construction entrance note between #2 and #3. [Civil Plans, C-5]
|
|
See Document Markup
Resolve large space in Standard notes. [Civil Plans, C-5]
|
|
See Document Markup
use dates from Section City Standards 501.5. [Civil Plans, C-5]
|
|
See Document Markup
Add soil stabilization notes from City Standards Section 501.5 [Civil Plans, C-5]
|
|
See Document Markup
This construction entrance detail is not needed. Add applicable an construction entrance detail. [Civil Plans, C-5]
|
|
See Document Markup
Add Note: No clearing, filling, grading or other alteration occurs within any
critical areas or associated buffer unless specifically authorized
pursuant to Chapter 21.06 Environmentally Critical Areas
Management of the Puyallup Municipal Code. [Civil Plans, C-5]
|
|
See Document Markup
Add Note: There is a potential to encounter groundwater during deep excavations. Provide Dewatering note that complies with City Dewatering standards Section 504. [Civil Plans, C-5]
|
|
See Document Markup
Paving and Storm sheet is busy. Separate Paving Plan from Storm Plan. Remove topography and utility lines from paving plan and rename it as Site Plan. [Civil Plans, C-6]
|
|
See Document Markup
What is JB? Reference detail. [Civil Plans, C-6]
|
|
See Document Markup
Remove structures from keynotes and label structure names and numbers on plans. use a separate structures table for rim and invert elevations. [Civil Plans, C-6]
|
|
See Document Markup
All ADA curb ramps, ADA stalls, and Driveways must have 1:10 scale details showing dimensions, spot elevations, and slope arrows. [Civil Plans, C-6]
|
|
See Document Markup
Show directional pipe-flow arrows. [Civil Plans, C-6]
|
|
See Document Markup
"Disturbed Area Limit" arrow not pointing to anything. [Civil Plans, C-6]
|
|
See Document Markup
Mask all labels and callouts [Civil Plans, C-6]
|
|
See Document Markup
Provide 1:10 scale trash enclosure grading detail with dimensions, slopes, and spot elevations that meets City Design Standard Section 208. You can modify detail on C13 and reference it on site plan. [Civil Plans, C-6]
|
|
See Document Markup
Reference Sheet Number in keynotes where details are located. [Civil Plans, C-6]
|
|
See Document Markup
Original Comment: Show roof overhang.
Comment not addressed. building layers are missing [Civil Plans, C-6]
|
|
See Document Markup
Original comment: Darken building footprint to increase legibility.
Comment not addressed: building outline layer is missing [Civil Plans, C-6]
|
|
See Document Markup
Original comment: Show Proposed building FFE.
Comment not addressed: FFE was not provided on grading plan. [Civil Plans, C-6]
|
|
See Document Markup
Original Comment: Show Existing building FFE.
Comment not addressed: existing building FFE was not provided on grading plan. [Civil Plans, C-6]
|
|
See Document Markup
Show existing CB Rims. [Civil Plans, C-6]
|
|
See Document Markup
Add Retaining wall note "Walls over 4 feet require a separate building permit." [Civil Plans, C-6]
|
|
See Document Markup
Original comment: Freeze all existing elements (like curbing and bioswale) to be removed on all proposed plan sheets.
Comment not addressed: It appears a demo edge of pavement layer is still shown. [Civil Plans, C-6]
|
|
See Document Markup
Pipe cover at CB 1-2 is approximately 0.65 feet. Minimum cover for Ductile Iron Pipe is 1 foot. [Civil Plans, C-6]
|
|
See Document Markup
Add Pipe materials note stating, "Ductile iron pipe shall be Class 50, conforming to AWWA C151. Minimum
cover on ductile iron pipe shall be 1-foot. PVC pipe shall be per ASTM D3034, SDR 35 for pipe size 15-inch and smaller. Minimum cover on PVC pipe shall be 3-feet." [Civil Plans, C-6]
|
|
See Document Markup
Pipe cover at CB 2-3 is approximately 0.9 feet. Minimum cover for Ductile Iron Pipe is 1 foot. [Civil Plans, C-6]
|
|
See Document Markup
Label and hatch each street patch on site plan. [Civil Plans, C-6]
|
|
See Document Markup
Roof downspout Detail is not in plans. Provide City roof downspout infiltration detail 02.05.01 and site specific detail as mentioned in comment on sheet C10. [Civil Plans, C-6]
|
|
See Document Markup
Add Stormwater Plan Notes from City Standard Section 207. [Civil Plans, C-6]
|
|
See Document Markup
Confirm if CB 2-3 is in conflict with new curb and revise if necearry. [Civil Plans, C-6]
|
|
See Document Markup
Freeze all existing elements (like curbing and bioswale) to be removed on all proposed plan sheets. [Civil Plans, C-6]
|
|
See Document Markup
The Silva Cells appear to be in conflict with Stormtanks. Confirm there is no conflict or revise. [Civil Plans, C-6]
|
|
See Document Markup
This says storm-tanks are 2 feet deep, the profile appears to show it at about 3.5 feet deep [Civil Plans, C-6]
|
|
See Document Markup
A fence is required for walls over three feet in height. [Civil Plans, C-6]
|
|
See Document Markup
Call out type of retaining wall. [Civil Plans, C-6]
|
|
See Document Markup
Call out all proposed improvements and reference applicable details. [Civil Plans, C-6]
|
|
See Document Markup
Match proposed contour with existing contour. [Civil Plans, C-6]
|
|
See Document Markup
Reference applicable structure details and Sheet Number where details are located. [Civil Plans, C-6]
|
|
See Document Markup
3.52 foot drop from rim to invert exceeds the 3.3' max drop for the provided detail Revise invert to meet detail specs. [Civil Plans, C-6]
|
|
See Document Markup
Show required invert drop per detail. Marked up detail shows 2'-2" drop from inlet to outlet inverts. Confirm invert difference is met after receiving the shallow depth detail.
Comment not addressed: if the inlet is below the permanent settling pond level, the upstream pipe will be permanently underwater. [Civil Plans, C-6]
|
|
See Document Markup
Show full depth pavement removal limits per curbcut detail. [Civil Plans, C-6]
|
|
See Document Markup
call out bike storage and reference detail. [Civil Plans, C-6]
|
|
See Document Markup
call out what this is. Are these columns? If so, make sure roof outline is shown and accounted for in storm design. [Civil Plans, C-6]
|
|
See Document Markup
Original comment: Show trash enclosure roof downspout connection to storm.
Comment not addressed: Downspouts discharging over parking lot is prohibited per City standards. Storm line is directly beneath downspout discharge locations. Add callout for contractor to connect roof downspouts to adjacent storm line. [Civil Plans, C-6]
|
|
See Document Markup
Show infiltration facility inspection port locations and add callout that references detail and sheet location. [Civil Plans, C-6]
|
|
See Document Markup
Show stormtank facility per detail with correct inlet location and module orientations. [Civil Plans, C-6]
|
|
See Document Markup
Per COP Design Standards Section 2.2, the consistency between the horizontal scale and the vertical scale shall be on a ratio of 10 to 1 (i.e., 1" = 20' horizontal; 1" = 2' vertical). [Civil Plans, C-7]
|
|
See Document Markup
Provide Station and existing/proposed elevation labels on bottom of each profile view. [Civil Plans, C-7]
|
|
See Document Markup
Mask and "bring to front" the order for all Profile View labels and titles to avoid grid lines intersecting text. [Civil Plans, C-7]
|
|
See Document Markup
Label existing and proposed surface. [Civil Plans, C-7]
|
|
See Document Markup
Provide profiles of each proposed storm facility showing other facilities on in close proximity (filterra, silva cells, etc.) cover depth, inverts, storage layers, ponding limits and, high water elevations. show section labels on storm plan Plan. [Civil Plans, C-7]
|
|
See Document Markup
Call out max height of retaining wall. [Civil Plans, C-7]
|
|
See Document Markup
Label stations for each wall corner and do the same on grading plan. [Civil Plans, C-7]
|
|
See Document Markup
clarify by adding "pipe-run" in between storm and profiles.[Civil Plans, C-7]
|
|
See Document Markup
Show depth of cover for infiltration systems in profile for Section A-A.
[Civil Plans, C-7]
|
|
See Document Markup
Show all dimensions for infiltration systems in profile for Section A-A.
[Civil Plans, C-7]
|
|
See Document Markup
show FFE for building in profile for Section A-A. [Civil Plans, C-7]
|
|
See Document Markup
Show profile to Stormtanks. [Civil Plans, C-7]
|
|
See Document Markup
Show all pipe Crossings and crossing Table with a note specifying City separation standards in section 204.4 and. show City standard mitigation measures for locations where separation does not meet standards. [Civil Plans, C-8]
|
|
See Document Markup
Provide Sewer line profile per Design Standards Section 2.0. [Civil Plans, C-8]
|
|
See Document Markup
Callout water connection and reference connection detail. [Civil Plans, C-8]
|
|
See Document Markup
Callout all water pipe sizes and materials and lengths. provide thrust blocks with referenced details where applicable. [Civil Plans, C-8]
|
|
See Document Markup
Add trench bedding and backfill note and reference detail. [Civil Plans, C-8]
|
|
See Document Markup
Add Sanitary Sewer Notes from City Standard Section 405. [Civil Plans, C-8]
|
|
See Document Markup
Add Water System Notes from City Standard Section 304. [Civil Plans, C-8]
|
|
See Document Markup
Add grease interceptor sizing calculations to plans. [Civil Plans, C-8]
|
|
See Document Markup
Add Pipe material and cover Requirements note for sewer pipes per Section 401. [Civil Plans, C-8]
|
|
See Document Markup
Specify ex pipe material. [Civil Plans, C-8]
|
|
See Document Markup
Reference applicable structure details and Sheet Number where details are located. [Civil Plans, C8]
|
|
See Document Markup
100-foot max spacing between cleanouts. [Civil Plans, C-8]
|
|
See Document Markup
FYI: commercial min. slope is 1%. [Civil Plans, C-8] (only add if 6" will be required)
|
|
See Document Markup
Original comment: Show type 1 catch basin symbol for trash enclosure drain.
[Civil Plans, C-8]
|
|
See Document Markup
Show grease interceptor manholes. [Civil Plans, C-8]
|
|
See Document Markup
Callout grease interceptor size per detail and required calculations. [Civil Plans, C-8]
|
|
See Document Markup
03.10.01 is not provided in sheets.
|
|
See Document Markup
Callout gate valves in keynotes and reference detail and sheet location. [Civil Plans, C-8]
|
|
See Document Markup
callout all utility crossings and add crossing table for utilities in ROW. Add Utilities crossing details 03.01.03-1 & 2. [Civil Plans, C-8]
|
|
See Document Markup
add curb and gutter city standard detail 01.02.09. [Civil Plans, C-9]
|
|
See Document Markup
add curb cut city standard detail 01.02.10. [Civil Plans, C-9]
|
|
See Document Markup
Provide City roof downspout infiltration detail 02.05.01, yard drain detail 02.05.02, and complete, scaled site specific section and profile showing length, width, depth of cover, and finished a surface section to confirm construction conflicts do not exist. [Civil Plans, C-10]
|
|
See Document Markup
Provide Manufacturer Shallow depth configuration detail. [Civil Plans, C-10]
|
|
See Document Markup
Provide Site specific inverts in detail. [Civil Plans, C-10]
|
|
See Document Markup
X-out curb inlet detail if not used. [Civil Plans, C-10]
|
|
See Document Markup
Show site specific slopes and spot elevations. [Civil Plans, C-12]
|
|
See Document Markup
Show site specific Rim and invert elevations. [Civil Plans, C-12]
|
|
See Document Markup
distance from nearest cleanout is 23 feet. [Civil Plans, C-12]
|
|
See Document Markup
place bold box around correct size per the required sizing calculations. [Civil Plans, C-12]
|
|
See Document Markup
Also see city detail. [Civil Plans, C-14]
|
|
See Document Markup
Original comment: Provide an area table in section 1 to use in determining minimum requirements. The City encourages using the table provided during Preliminary Site Plan to ensure all required areas are tabulated. Email Lance Hollingsworth if you have trouble finding this table again.
Comment not fully addressed: TDA area tables show new areas and existing areas, but it does do not clearly show replaced areas, or new+replaced areas, or pollution generating areas. Refer to previously provided City template based on Ecology surface area definitions to ensure this comment is addressed. [Storm Report, Pg 3]
|
|
See Document Markup
It appears there may be more than one TDA onsite. Define the different TDAs with a numeric naming convention (TDA 1, TDA 2) and show in a TDA map. Use the TDAs when considering minimum requirements 6,7, and 8 per the Ecology Manual. [Storm Report, Pg 3]
|
|
See Document Markup
Consider MR 6 thresholds for each TDA. [Storm Report, Pg 6]
|
|
See Document Markup
Existing developed areas are never used for sizing BMPs, only for determining minimum requirements. In terms of full infiltration onsite, existing flows are not needed for the sizing design if 100 percent is infiltrated. If the design was detention, the entire site would have to be considered forested for the existing condition. [Storm Report, Pg 10]
|
|
See Document Markup
Remove existing conditions flow calculations. They are not needed for infiltration design. [Storm Report, Pg 10]
|
|
See Document Markup
New plus replaced hard surface area needs to be recorded for all basins. and added in table. Use table from preliminary site plan. [Storm Report, Pg 137]
|
|
See Document Markup
Name the different developed basins with a numeric naming convention for clarity (Basin 1, Basin 2) and define each basin by its drainage characteristics. Tie this back to the developed basin map in the back of the report for clarity. [Storm Report, Pg 10]
|
|
See Document Markup
An infiltration trench cannot be used as a technical equivalent for permeable pavement. Continue feasibility discussion with remaining BMPs in the list. Document the site conditions and Ecology Manual infeasibility criteria used to deem each BMP infeasible to satisfy MR 5. [Storm Report, Pg 6]
|
|
See Document Markup
Original comment: If you justify how each TDA effective impervious surface was reduced below the 10K threshold, the flow control standard is not required to be met.
Comment not addressed: It appears the narrative that includes the needed information is in the flow control narrative of the developed site hydrology section. Confirm this and direct reader to refer to this section for additional information used to satisfy MR7. [Storm Report, Pg 6]
|
|
See Document Markup
When considering MR 7, use the effective impervious area to determine thresholds for Each TDA. Review the supplemental guidelines in the Manual where it specifies the effective impervious area and the converted vegetation areas can be reduced with infiltration facilities such that the TDA Thresholds are not triggered, eliminating the Flow Control BMP requirement. [Storm Report, Pg 6]
|
|
See Document Markup
Reference the basin map that is provided at the end of the report. [Storm Report, Pg 12]
|
|
See Document Markup
Flow frequency is not needed for modeling infiltration facilities that achieve 100 percent infiltration. [Storm Report, Pg 12]
|
|
See Document Markup
Explain how there is an applicable flow frequency discharge off-site if 100% infiltration is achieved. [Storm Report, Pg 14]
|
|
See Document Markup
Correct typo. [Storm Report, Pg 14]
|
|
See Document Markup
Meeting Flow control standard does not appear to be required based on report stating effective impervious area is reduced to under 10,000 SF through infiltraiton. Contact Lance Hollingsworth for clarification of design intent. [Storm Report, Pg 14]
|
|
See Document Markup
If 100 percent infiltration is achieved, predeveloped basin information should be empty and not used in WWHM. Call Lance Hollingsworth if you have any questions. [Storm Report, Pg 26 - WWHM Pg 3]
|
|
See Document Markup
Predeveloped trench performance is not needed if developed existing trench performance infiltrates 100 percent.
|
|
See Document Markup
Should this be POC 2? [Storm Report, Pg 15]
|
|
See Document Markup
Add note for contractor to clean existing infiltration trench per maintenance Manual and Ecology standards prior to end of construction. [Civil Plans, C-6]
|
|
See Document Markup
Show peak groundwater levels and reference geotech report.
[Civil Plans, C-7]
|
|
See Document Markup
Include FEMA Panel number and date.
[Storm Report, Pg 8]
|
|
See Document Markup
Use an "approved equal" track-out device/facility on top of existing paved access. [Storm Report, Pg 16 - SWPPP]
|
|
See Document Markup
Include wheel wash BMP C106 since it is mentioned in narrative. [Storm Report, Pg 16 - SWPPP]
|
|
See Document Markup
Add City Design Standard Section 501.5 to Element 5 narrative. [Storm Report, Pg 16 - SWPPP]
|
|
See Document Markup
Add concrete washout, concrete handling, treating high pH water, and saw cutting BMPs to element 9. [Storm Report, Pg 17 - SWPPP]
|
|
See Document Markup
Add all applicable BMP detail sheets from Ecology Manual to SWPPP. [Storm Report, Pg 21 - SWPPP]
|
|
See Document Markup
|