Mission-Critical Industrial: 84 Issues Found

Summary: One document lists the governing code as 'International Building Code (IBC) - 2015 with amendments,' while the partition/project notes require wet-location gypsum board 'AS REQUIRED BY SECTION 1210 OF THE 2021 IBC.' These drawings therefore cite different IBC editions for wall and partition requirements.

Why it matters: Conflicting code editions can change the acceptance criteria for wall board selection and permit review, creating uncertainty about which code standard the contractor and AHJ should follow.

Suggested next step: Confirm the governing IBC edition for the project and whether the wet-location gypsum board requirement is to be based on the 2015 or 2021 IBC, then revise the affected drawing notes so both documents match.

RFI draft: Confirm the governing IBC edition for the project and whether the wet-location gypsum board requirement is to be based on the 2015 or 2021 IBC, then revise the affected drawing notes so both documents match.

Summary: Both sheets identify 'PORTLAND VETERINARY EMERGENCY AND SPECIALTY CARE,' but they carry opposite issue statuses: one states 'ISSUED FOR CONSTRUCTION' and the other states 'NOT FOR CONSTRUCTION.' This is a direct conflict regarding whether the drawings are released for construction use.

Why it matters: If unresolved, contractors and permit reviewers may not know whether the conflicting sheet is part of the active construction set or only a preliminary document, creating risk of using the wrong basis for pricing, approvals, and field work.

Suggested next step: Please confirm the current status of the drawing package and reissue the affected sheet(s) so all sheets for this project carry one consistent construction-status designation.

RFI draft: Please confirm the current status of the drawing package and reissue the affected sheet(s) so all sheets for this project carry one consistent construction-status designation.

Summary: The same utility run is labeled inconsistently on this sheet. In the upper portion of the run, the dashed red line is labeled '3/4\' RHW' alongside '2\' CW,' '1 1/4\' HW,' and '1 1/2\' NG.' In the adjacent continuation below, that same companion set is shown again, but the dashed red line is labeled '3/4\' BHW' instead of RHW. General Note 3...

Why it matters: Because 'RHW' and 'BHW' are different designations, the contractor cannot determine from this page whether the dashed red line is the return line identified in the notes or a different system. That affects system identification, valve requirements, and coordination of the run.

Suggested next step: Please confirm whether this dashed red line is intended to be RHW or BHW and revise the plan and notes to use one consistent system abbreviation on this utility run.

RFI draft: Please confirm whether this dashed red line is intended to be RHW or BHW and revise the plan and notes to use one consistent system abbreviation on this utility run.

Summary: Keynote 11 says '1/2\' NPW-DROP TO HUMIDIFIER (H-1). ROUTE NPW TO HUMIDIFIER CONNECTION AND DRAIN QUENCHER.' On the plan, the area carrying keyed note '11' is labeled 'H-2'. The numbered keynote and the equipment tag therefore do not match on this sheet.

Why it matters: Installers and reviewers cannot reliably determine whether the NPW and drain quencher connection is intended for H-1 or H-2. That creates a real risk of piping the wrong equipment and having the utility connection rejected during coordination or inspection.

Suggested next step: Please confirm whether keynote 11 is intended for H-1 or H-2, and revise either the keynote text or the plan equipment tag so the connection is identified consistently.

RFI draft: Please confirm whether keynote 11 is intended for H-1 or H-2, and revise either the keynote text or the plan equipment tag so the connection is identified consistently.

Summary: Visual review of the one-line shows the diamond callout '12' is placed on the 150A 3P branch dropping from the 600 KW emergency generator. The adjacent 'TEMPORARY GENERATOR HOOKUP' labeled 'MTS-FP 150A' is on a separate line and is not the branch tagged '12'. The cable schedule defines item 12 as '4 #8 AWG & #10 GND, 1\'C', which conflicts with...

Why it matters: The original issue incorrectly associated the callout 12 with MTS-FP based on proximity. The drawing still shows a real mismatch between cable schedule item 12 and the 150A generator branch it actually tags.

Suggested next step: Confirm the intended conductor size for the 150A generator branch tagged cable callout 12, and clarify the correct cable callout for the MTS-FP temporary generator hookup so the one-line and cable schedule are coordinated.

RFI draft: Confirm the intended conductor size for the 150A generator branch tagged cable callout 12, and clarify the correct cable callout for the MTS-FP temporary generator hookup so the one-line and cable schedule are coordinated.

Summary: The code summary states International Building Code (IBC) - 2015 with amendments and NFPA 101 2018, but the same sheet also says Business Areas (IBC 2018) and uses NFPA 5000 2018 in a requirements-table heading.

Why it matters: Because the sheet cites different governing codes and editions, a reviewer cannot tell which criteria control the occupancy and life-safety analysis. That can stop or delay permit review until the compliance basis is corrected.

Suggested next step: Confirm the governing adopted codes for this project and revise the code compliance summary so the occupancy references and requirement tables all use one consistent code basis.

RFI draft: Confirm the governing adopted codes for this project and revise the code compliance summary so the occupancy references and requirement tables all use one consistent code basis.

Summary: The room-tag legend identifies the numeric fields as room area, room occupant load factor, and number of occupants. Using the values shown in the tags, several room counts do not reconcile: MECHANICAL shows 1,182 SF / 300 / 5, which is 3.94; STAFF BREAK ROOM shows 799 SF / 15 NET / 51, which is 53.3; ROOF TERRACE shows 1,592 SF / 15 / 118,...

Why it matters: Occupant load is the basis for the egress and life-safety analysis. If the room tags are internally inconsistent, downstream exit-capacity, door, and permitting calculations may also be wrong or unreviewable.

Suggested next step: Verify the correct room areas, occupant-load factors, and occupant counts for the affected spaces, then update the room tags and any dependent life-safety calculations.

RFI draft: Verify the correct room areas, occupant-load factors, and occupant counts for the affected spaces, then update the room tags and any dependent life-safety calculations.

Summary: The code summary states the building is 'B: Business (Section 304) with Assembly Group A-3 (Section 303.4) and S-2 Storage (Section 311.3 Low-Hazard Storage) accessory use.' On Level 2, the sheet also shows a 'STAFF BREAK ROOM' of '799 SF' with a '15 NET' occupant-load factor, and the same code summary lists 'Assembly unconcentrated' at...

Why it matters: This is a fundamental occupancy-classification error. If the A-3 area is carried as accessory when it exceeds the Section 508.2.3 limit, the project's Section 508 compliance path is wrong and the occupancy-based code analysis for the building can be rejected during review, requiring code-summary revisions and possible redesign/resubmittal.

Suggested next step: Please revise the code summary so the Level 2 A-3 area is not treated as an accessory occupancy, or provide a compliant Section 508 mixed-occupancy approach for the A-3 portions and update the code analysis accordingly.

RFI draft: Please revise the code summary so the Level 2 A-3 area is not treated as an accessory occupancy, or provide a compliant Section 508 mixed-occupancy approach for the A-3 portions and update the code analysis accordingly.

Summary: The room tags show 'STAFF BREAK ROOM / 799 SF / 15 NET / 51', 'LOBBY / 2,850 SF / 15 / 189', and 'VET CLINIC / 30,734 SF / 100 / 305'. Under IBC 1004.1.2, occupant load for areas without fixed seating must be at least the floor area divided by the Table 1004.1.2 factor. Based on the stated areas and factors, these spaces calculate to minimum...

Why it matters: These are not harmless rounding differences. Section 1005.3 bases means-of-egress capacity on occupant load, so understated room loads can invalidate downstream life-safety calculations. For the Level 1 tags shown here, LOBBY + VET CLINIC + STORAGE total 499 occupants as drawn, but the minimum total from the stated areas and factors is 503, so...

Suggested next step: Revise the occupant-load tags for STAFF BREAK ROOM, LOBBY, and VET CLINIC to match IBC 1004.1.2, then confirm whether the corrected occupant loads require updates to the means-of-egress sizing and any related life-safety calculations.

RFI draft: Revise the occupant-load tags for STAFF BREAK ROOM, LOBBY, and VET CLINIC to match IBC 1004.1.2, then confirm whether the corrected occupant loads require updates to the means-of-egress sizing and any related life-safety calculations.

Summary: SF101 calls out 'GIRDER REINFORCEMENT SEE 3/SF504.' However, 3/SF504 is shown with '3\' METAL ROOF DECK' and 'ATRIUM BENT FRAME. SEE PLAN,' indicating an atrium roof/bent-frame section rather than a girder reinforcement detail. The cross-reference does not match the subject identified on the framing plan.

Why it matters: This can direct the contractor and steel fabricator to an unrelated detail while leaving the required girder reinforcement unresolved at the plan location, increasing the risk of incorrect fabrication or delayed shop drawing review.

Suggested next step: Please confirm the correct detail number and sheet for the 'GIRDER REINFORCEMENT' note on SF101, or revise 3/SF504 so it explicitly provides the intended girder reinforcement detail.

RFI draft: Please confirm the correct detail number and sheet for the 'GIRDER REINFORCEMENT' note on SF101, or revise 3/SF504 so it explicitly provides the intended girder reinforcement detail.

Summary: The column layout assigns BP-5 to '8x8 HEM' posts and explicitly says 'SEE 6/SF502 FOR BP-5 DETAILS.' On SF502, the front porch section also applies '6 / SF502' to an '8x8 HEM' post condition. However, Detail 6 identifies that referenced post base as '8X8 WESTERN RED CEDAR.' This is a direct material/species conflict for the same referenced...

Why it matters: Because the referenced 6/SF502 base condition is tied to posts labeled '8x8 HEM' in the plan/section but the detail itself names '8X8 WESTERN RED CEDAR,' the contractor cannot determine the correct wood material to procure or submit for the BP-5 locations. This can lead to incorrect shop drawings and installation of the wrong post/base assembly.

Suggested next step: Please confirm whether the BP-5 / 6-SF502 post-base detail is intended for '8x8 HEM' or for '8X8 WESTERN RED CEDAR,' and revise the plan/section/detail so the wood species is consistent everywhere the condition is referenced.

RFI draft: Please confirm whether the BP-5 / 6-SF502 post-base detail is intended for '8x8 HEM' or for '8X8 WESTERN RED CEDAR,' and revise the plan/section/detail so the wood species is consistent everywhere the condition is referenced.

Summary: On the utility plan, both the storm drain network and the VUSF callout direct the reader to a sheet range that includes this referenced sheet. However, the referenced sheet explicitly states that utilities are not shown and directs the reader back to the utility plan for utility design. This is a cross-reference mismatch because the cited range...

Why it matters: This creates uncertainty about where the governing storm drainage/VUSF information is actually documented, which can delay permitting, bidding, and field layout and can lead to teams relying on the wrong sheet for civil utility coordination.

Suggested next step: Please confirm the correct sheet reference for the storm drain network and the VUSF callout. If this referenced sheet is not intended to govern utility work, revise the utility-plan callouts to remove it from the cited range; otherwise add the missing utility information to that sheet.

RFI draft: Please confirm the correct sheet reference for the storm drain network and the VUSF callout. If this referenced sheet is not intended to govern utility work, revise the utility-plan callouts to remove it from the cited range; otherwise add the missing utility information to that sheet.

Summary: The site plan calls for the accessible parking signage to be provided on bollards: 'PROPOSED BOLLARDS WITH ADA SIGNAGE PER DETAILS, TYP.' The parking layout details route this condition to the barrier-free parking sign detail: 'BARRIER FREE PARKING SIGN PER DETAIL.' But that sign detail does not match bollard mounting; it calls out a '3\' GALV....

Why it matters: If this is not clarified, the contractor could install the accessible parking signs three different ways, which can create ADA inspection problems and rework to pavement, concrete, bollards, or the building façade.

Suggested next step: Please confirm the required mounting/support and location for the accessible parking signs at the ADA spaces, and revise the plan callout and barrier-free sign detail so one consistent installation is shown.

RFI draft: Please confirm the required mounting/support and location for the accessible parking signs at the ADA spaces, and revise the plan callout and barrier-free sign detail so one consistent installation is shown.

Summary: On the roof plan, one scupper location is called out as 'SCUPPER' with '10/A505 Sim', while another scupper on the same sheet is called out as '11/A505 Sim SCUPPER'. On A505, Detail 10 describes a vented roof-edge/fascia condition, while Detail 11 is the detail that explicitly includes an overflow scupper. This makes the 10/A505 reference at...

Why it matters: If the field team follows the 10/A505 callout at that roof drainage opening, the assembly could be built from a roof-edge/fascia detail instead of the intended scupper detail. That creates risk for incorrect opening construction, flashing, waterproofing, and drainage performance.

Suggested next step: Please confirm the correct A505 reference for the roof-plan location labeled 'SCUPPER' with '10/A505 Sim'. Should that callout be revised to 11/A505, or is another scupper detail missing or misnumbered on A505?

RFI draft: Please confirm the correct A505 reference for the roof-plan location labeled 'SCUPPER' with '10/A505 Sim'. Should that callout be revised to 11/A505, or is another scupper detail missing or misnumbered on A505?

Summary: The site plan gives specific construction requirements for the access-drive pedestrian corridor: it calls for 'PROPOSED SLIPFORM CONCRETE CURB ALONG ROADWAY PER DETAIL, TYP.' and a '9' WIDTH SIDEWALK CORRIDOR' with '10\' AGGREGATE BASE MATERIAL'. The corresponding site detail instead shows 'SLIPFORM OR GRANITE CURB PER OWNER' and '8\' AGGREGATE...

Why it matters: This leaves the contractor without a single buildable section for the access-drive pedestrian corridor. The discrepancy affects material selection, pricing, grading, and the future pedestrian connectivity work along the drive.

Suggested next step: Please confirm the required curb type and aggregate-base thickness for the 9' wide sidewalk corridor along the access drive, and revise either the site plan notes or the site detail so both sheets show the same section.

RFI draft: Please confirm the required curb type and aggregate-base thickness for the 9' wide sidewalk corridor along the access drive, and revise either the site plan notes or the site detail so both sheets show the same section.