Owner Project Requirements GO TO FRONT PAGE Page | 1

Washington County Owner Project Requirements

April 30, 2025

Owner Project Requirements GO TO FRONT PAGE Page | 2

I: INTRODUCTION

GENERAL OBJECTIVES

ADDITIONAL REFERENCE DOCUMENTS

A/E SERVICE PROVIDER RESPONSIBILITY

COMMENTS OR QUESTIONS

II: BID PACKAGES

PROCURENOW

BID THRESHOLDS

BIDDING PAGES FOR CONSTRUCTION

PROJECT MANUAL FOR CONSTRUCTION

ADDENDA

PROCUREMENT PROCESS

III: FORMAT

SPECIFICATION FORMAT

TECHNICAL SECTION FORMAT

TECHNICAL PAGE FORMAT

ABBREVIATIONS, ACRONYMS AND TERMS

WRITING STYLE

IV: CONTENT

STANDARD REQUIREMENTS

SOLE SOURCE EXEMPTIONS

BASIS OF DESIGN

DELEGATED DESIGN

V: EDITING

PROJECT MODIFICATIONS

PROJECT RECORD DOCUMENTS

VI: QUALITY

EXHIBIT A1: SAMPLE PROJECT DIRECTORY / CERTIFICATION PAGE

EXHIBIT A2: SAMPLE TABLE OF CONTENTS

EXHIBIT A3: SAMPLE PARAGRAPH

EXHIBIT A4: SAMPLE PROJECT MODIFICATIONS

EXHIBIT A5: SAMPLE PROJECT RECORD SPECIFICATIONS

EXHIBIT B1: GENERAL DISCUSSION

Owner Project Requirements GO TO FRONT PAGE Page | 3

GENERAL NARRATIVE

OVERVIEW AND SCOPE

OVERVIEW AND DEFINITION

SUSTAINABILITY

GENERAL

DATA SECURITY

VIRTUAL DESIGN, CONSTRUCTION, AND OPERATIONS

OVERVIEW

SCOPE

REVIT MISSION STATEMENT

SOFTWARE

SHEET ANATOMY

BIM EXECUTION PLANNING

MODELING PRACTICES

TEAM SPECIFIC GUIDELINES

SPECIFICATIONS INTEGRATIONS

INTEGRATING FACILITY MANAGEMENT (FM) DATA

RECORD DOCUMENTS

COBIE

GRAPHIC STANDARDS

STYLE GUIDE

BUILDING CLASSIFICATION LEVELS

GENERAL

LEVEL 1 – “PUBLISHED”

LEVEL 2 – “LIMITED”

LEVEL 3 - “RESTRICTED”

LEVEL 4 – “CRITICAL”

DIVISION 0: PROCUREMENT AND CONTRACTING

00 31 13 - PRELIMINARY SCHEDULES

00 65 36 - WARRANTY

DIVISION 1: GENERAL REQUIREMENTS

GENERAL NARRATIVE

01 31 00 – PROJECT MANAGEMENT AND COORDINATION

Owner Project Requirements GO TO FRONT PAGE Page | 4

01 31 19 – DESIGN PROJECT MEETINGS

01 43 39 - MOCK-UP

01 60 00 – PRODUCT REQUIREMENTS

01 78 00 - CLOSEOUT SUBMITTALS

01 91 00 - COMMISSIONING

01 92 00 - FACILITY OPERATION

DIVISION 2: EXISTING CONDITIONS

02 25 00 - HAZARDOUS MATERIAL

02 32 00 - GEOTECHNICAL

02 41 00 - DEMOLITION

DIVISION 3: CONCRETE

03 30 00 - CAST-IN-PLACE CONCRETE

DIVISION 4: MASONRY

04 01 00 - MASONRY MAINTENANCE:

DIVISION 5: METALS

05 10 00 - STRUCTURAL AND MISCELLANEOUS STEEL

DIVISION 6: WOODS & PLASTICS

06 20 00 - FINISH CARPENTRY

DIVISION 7: THERMAL & MOISTURE PROTECTION

07 00 00 - ENVELOPE FOR NEW CONSTRUCTION

07 21 00 – THERMAL INSULATION

07 25 00 - WEATHER BARRIERS

07 50 00 - ROOFING

07 62 00 - SHEET METAL FLASHING AND TRIM

07 92 00 - JOINT SEALANTS

DIVISION 8: DOORS & WINDOWS

GENERAL

HOLLOW METAL DOORS, DOOR FRAMES & RELITES

PRE-FINISHED, KNOCKED-DOWN METAL DOOR & RELITE FRAMES

08 14 00 - INTERIOR WOOD DOORS

08 40 00 - ALUMINUM ENTRANCES, STOREFRONTS & CURTAIN WALLS

08 70 00 - DOOR HARDWARE

DIVISION 9: FINISHES

Owner Project Requirements GO TO FRONT PAGE Page | 5

09 00 00 - ACOUSTIC PERFORMANCE

09 22 16 - LIGHT GAUGE STEEL STUDS:

09 29 00 - GYPSUM BOARD

09 30 00 - TILING

09 51 00 - ACOUSTICAL CEILING SYSTEMS

09 65 00 - RESILIENT FLOORING & BASE

09 68 00 - CARPETING

09 84 13 - ACOUSTICAL SOUND-ABSORBENT WALL PANELS

09 90 00 - PAINTING, STAINING AND FINISHING

DIVISION 10: SPECIALTIES

10 11 16 - MARKER BOARDS

10 11 23 - TACK BOARDS

10 14 00 – DIGITAL DOOR SIGNAGE

10 14 23 - PANEL SIGNAGE

10 21 13 - TOILET PARTITIONS

10 22 19 – DEMOUNTABLE PARTITIONS

10 26 00 – WALL PROTECTION

DIVISION 11: EQUIPMENT

11 11 36 - VEHICLE CHARGING REQUIREMENTS

11 28 00 - OFFICE EQUIPMENT

11 28 13 – COMPUTERS

11 52 13 - PROJECTION SCREENS

11 20 00 - APPLIANCES

DIVISION 12: FURNISHINGS

12 21 00 - HORIZONTAL LOUVER BLINDS

12 24 00 - ROLLER SHADES

12 30 00 - CASEWORK

12 36 00 - COUNTERTOPS

12 36 61 – INTEGRAL SINKS

12 48 13 – ENTRANCE MATS AND FRAMES

12 50 00 - FURNITURE

12 51 23 – SIT-STAND DESK

12 59 00 - SYSTEMS FURNITURE

Owner Project Requirements GO TO FRONT PAGE Page | 6

DIVISION 14: CONVEYING EQUIPMENT

14 20 00 - EXISTING ELEVATORS

DIVISION 21: FIRE SUPPRESSION

21 00 00 - FIRE SUPPRESSION SYSTEMS

DIVISION 22: PLUMBING

22 00 00 - GENERAL

ALL FACILITIES LEASED OR OWNED

COUNTY OCCUPIED NON-RESIDENTAIL BUILDINGS

COUNTY OWNED – LONG LEASE

DIVISION 23: HEATING, VENTILATION & AIR-CONDITIONING (HVAC)

HVAC SYSTEMS CATEGORY 1

HVAC SYSTEMS CATEGORY 2

HVAC SYSTEMS CATEGORY 3

23 01 00 – OPERATION AND MAINTENANCE DATA

23 01 10 – RECORD DRAWINGS AND SUBMITTALS

23 08 00 - COMMISSIONING

23 09 00 – INSTRUMENTATION AND CONTROLS

DIVISION 26: ELECTRICAL

ELECTRICAL SERVICE AND POWER DISTRIBUTION

26 00 00 - SWITCHES, RECEPTACLES & OTHER DEVICES

26 09 00 - LIGHTING CONTROL

26 12 00 - DISTRIBUTION TRANSFORMERS

26 24 16 - PANEL-BOARDS

26 32 00 - GENERATORS

26 32 00 - UNINTERUPTED POWER SUPPLY (UPS)

23 36 00 - TRANSFER SWITCHES

26 50 00 - LIGHTING

26 51 00 – INTERIOR LIGHTING

VARIAL FREQUENCY DRIVE

BUILDING SERVICE

GROUNDING

WORKSPACE, AREA, ROOM

MOTORS

Owner Project Requirements GO TO FRONT PAGE Page | 7

SOLAR

HIGH RISK / DETENTION LOCATIONS

DIVISION 27: COMMUNICATIONS

27 00 00 - GENERAL

DATA SECURITY

COUNTY RADIO COMMUNICATION ANTENNA SYSTEM

ELECTRONIC SERVICES-COMMUNICATION

TELECOM AND IT

27 40 00 - INTEGRATED AUDIO-VISUAL SYSTEM

27 41 16 - SOUND REINFORCEMENT

27 51 13 - TELEPHONE PAGING

27 51 23 - INTERCOM

27 53 19 - DISTRIBUTED ANTENNA SYSTEM

DIVISION 28: ELECTRONIC SAFETY & SECURITY

28 00 00 - GENERAL

28 10 00 - ACCESS CONTROL

28 46 00 - FIRE ALARMS

28 30 00 - SECURITY ALARMS

ELECTRONIC SERVICES

DIVISION 31: EARTHWORK

31 21 13 - RADON MITIGATION

DIVISION 32: EXTERIOR IMPROVEMENTS

32 13 00 - RIGID PAVINGS

32 31 00 – FENCING AND GATES

32 33 00 - FURNISHINGS

32 80 00 - IRRIGATION SYSTEMS

32 90 00 - PLANTINGS

DEFINITIONS

Owner Project Requirements GO TO FRONT PAGE Page | 8

I: INTRODUCTION

Washington County Oregon (hereafter referred to as the County) establishes these standards to provide direction in the design and construction of the project. This includes the selection of building materials and in the preparation of construction specifications for the County. This document identifies those standards that the County considers essential to selecting building materials and to preparing specifications and related documentation in a consistent and acceptable manner. These standards describe specification requirements for bid packages, format, content, editing, and quality.

GENERAL OBJECTIVES

The County issues these standards to:

1. Establish building material requirements and selection.

2. Promote the successful use and control of project specifications and related documentation for Washington County owned buildings.

3. Establish minimum requirements for consistent format, professional appearance, and data interchangeability among specification files and other building documents.

4. Create accurate, accessible, and current building and project documentation.

5. Expedite project delivery and reduce development cost.

ADDITIONAL REFERENCE DOCUMENTS

Additional administrative requirements and related information may be found in:

1. Room and Space Standards

2. Washington County Telecommunications Infrastructure Standards

3. Furniture Design Guide (in progress)

4. COBie Spreadsheets

5. Revit Template

A/E SERVICE PROVIDER RESPONSIBILITY

The County requires that all specifications submitted from the A/E Service Provider comply with these standards. An A/E Service Provider is defined as an organization contracted to provide professional services requiring planning and/or design work, and may include architects, engineers, consultants, drafting services, furniture installers, interior designers, space planners, or design-build contractors (who have professional liability insurance and the capability to produce digital documents).

For any deviation from these standards, submit a written request with specific explanations to the County Project Manager (hereafter referred to as the Project Manager). The Project Manager is the person designated

Owner Project Requirements GO TO FRONT PAGE Page | 9 to represent the County on issues for a specific project. The County will review the request and respond with a written authorization of acceptance or explanation of denial.

COMMENTS OR QUESTIONS

The County welcomes your recommendations to improve our documents and documentation process.

Address comments or questions about the interpretation or use of these standards to:

Bassam Khalifeh Senior Capital Improvements Manager

Phone: (503) 846-4849 Email: bassam_khalifeh@co.washington.or.us

WASHINGTON COUNTY OREGON

Facilities and Parks Services 169 North First Ave Hillsboro, OR 97124

II: BID PACKAGES

Provide specification sections and information, which the County will assemble with their documents and issue as Bid Packages to solicit work on public projects. For samples of County-provided documents and templates, refer to EXHIBIT A1: SAMPLE PROJECT DIRECTORY / CERTIFICATION PAGE. For coordination with drawing documents, refer to the Washington County BIM Standards.

PROCURENOW

The County uses ProcureNow to initiate, manage, and award bids for Construction and services. All questions or substitution requests during the bid process shall be directed to the County via ProcureNow, and not submitted to the A/E.

BID THRESHOLDS

1. Over $50K requires Prevailing Wage Rates

2. Over $100K requires First Tier

3. Over $150K publicly advertised

4. Over $300K requires Board Approval

Owner Project Requirements GO TO FRONT PAGE Page | 10

BIDDING PAGES FOR CONSTRUCTION

The County prepares separate Bidding Pages (CSI Division 0) to provide information unique to each project. At contract signature, the Bidding Pages are attached to the Project Manual and Addenda to form the “Specification and Contract Agreement”. Bidding Pages for Construction may include:

1. Invitation to Bid.

2. Table of Contents.

3. Instructions to Bidders.

4. Contracts and General Conditions.

5. Bid Forms.

6. Bid Bond.

7. Performance Bond.

8. Payment Bond.

9. Substitution Request Form.

10. State of Oregon First Tier Subcontractor Disclosure Requirements.

Bid and Performance/Payment bonds can be required or waived at any level.

PROJECT MANUAL FOR CONSTRUCTION

The County assembles material from the County (CSI Division 0) and A/E Service Provider (CSI Divisions 1-48) into a Project Manual, organized as follows:

1. Book 1

a. Instructions to Bidders: The County prepares and includes the Instructions to Bidders.

b. Contract: The County prepares documentation and exhibits for the Conditions of the Contract, which may include the following:

i. Contract Agreement

ii. General Conditions

iii. Supplementary Conditions (where applicable)

iv. Prevailing Wage Rates (where BOLI and/or Davis Bacon rates are applicable).

c. General Conditions: The County prepares and includes the General Conditions of the Contract for Construction.

d. Attachments: The County prepares and includes an applicable Attachments.

Owner Project Requirements GO TO FRONT PAGE Page | 11

e. Bid Forms: The County prepares and includes all applicable Bid Forms.

2. Book 2

a. Project Directory/Certification Page: A/E Service Providers (and their associated professional consultants) prepare, stamp, and sign the Project Directory/Certification Page in accordance with state laws, professional practices, and their contract obligations. Refer to EXHIBIT A1:

SAMPLE PROJECT DIRECTORY / CERTIFICATION PAGE

b. Table of Contents: A/E Service Providers prepare a Table of Contents to list all specification division numbers and names, whether used or not. Where not used, the County will indicate “NOT USED” after the division number and name. The Table of Contents will also list specification section numbers and names used for each division. EXHIBIT A2: SAMPLE TABLE OF

CONTENTS

c. Specification Sections: A/E Service Providers have sole responsibility to prepare all general requirements (Division 1) and technical specification sections (Divisions 2-49) using Construction Specifications Institute’s MasterFormat™ 2016 division and section numbering and titles. All specification sections shall be developed with project-specific information.

Consider Basis of Design information found in Appendix B, C, D and E. Follow general principles found in the CSI Manual of Practice. Division 1 general requirements shall be carefully coordinated with the County’s General Requirements of the Contract for Construction.

d. Construction Documents: The A/E Service Providers prepare technical drawings for communicating the design intent to the Contractor. All Construction Documents shall coordinate with the Specification Sections, and not duplicate information in location.

Construction Documents shall include all sections in this document and its reference materials.

ADDENDA

The County may issue addenda during the bid process. Addenda form part of the Contract Documents and may modify previous Addenda, Bidding Pages, Project Manual and Drawings. The County lists items of addition, deletion, change, or clarification for those sections it is responsible. The County refers to and attaches the A/E Service Provider stamped list of items for those sections it is responsible for. Where a Pre- Bid Conference is mandatory, the County will issue the Attendance List in an addendum.

PROCUREMENT PROCESS

The County will use the assembled Project Manual and Drawings to procure bids from contractors for the work. Projects will be posted on Oregon Procurement Information Network (ORPIN) which is located at www.oregon.gov. The low qualified bid will be considered by the Washington County Board of Commissioners.

Bids accepted by the Board of Commissioners will be awarded to the responsive bidder. Should the bidder be unresponsive, the next lowest bid shall be considered.

http://www.oregon.gov/

Owner Project Requirements GO TO FRONT PAGE Page | 12

III: FORMAT

Prepare project-specific technical specification sections using the Construction Specifications Institute’s MasterFormat™ 2016 edition, division and section numbing and titles. For further instructions, refer to the CSI Manual of Practice.

SPECIFICATION FORMAT

The A/E Service Provider shall prepare technical specification sections using MasterFormat™ 2004 Edition. The A/E Service Provider shall format and edit the specification section in accordance with the instructions described below.

TECHNICAL SECTION FORMAT

For specification sections, use the standard CSI three-part format and adhere to the following:

Section Header: See below.

1. Body of specification per technical page formatting below.

2. Center “END OF SECTION” on the last page of each specification section, two lines below the bottom text of the section.

3. Section Footer: See below.

4. All specification sections shall begin on the right side of a book layout. Insert blank pages where required for proper layout.

5. Refer to EXHIBIT A3: SAMPLE PARAGRAPH.

TECHNICAL PAGE FORMAT

Refer to EXHIBIT A3: SAMPLE PARAGRAPH for examples of the following requirements:

1. Text Font Style: Arial

2. Font Type: TrueType Font.

3. Text Color: Automatic (including header and footer)

4. Text Size: 11 point

5. Margins: 1” top, 1” bottom, 1” left, 1” right, 1” header

6. Header & Footer: 0.4” header, 0.4” footer

7. Paragraph Spacing: Set to 0

8. Indentation: Set to 0.5” left

Owner Project Requirements GO TO FRONT PAGE Page | 13

9. Page Header:

SECTION XX XX XX

SECTION NAME

10. Page Footer:

SECTION XX XX XX – Page #

Washington County: Project Name

A/E Job No. / Set Name / Date

ABBREVIATIONS, ACRONYMS AND TERMS

Adhere to the guidelines, standards, and examples found in the CSI Manual of Practice. Use terms defined by the County in the General Conditions and other County publications. Conform to the following:

1. Use “Architect” when referring Architect, Engineer, or A/E Services Provider

2. Use “Owner” when referring to Washington County Oregon; and

3. Use “Project Manager” to refer to Owner representative.

WRITING STYLE

Adhere to the following:

1. Do not use specifications sections or portions thereof directly from previous projects or master specifications that belong to other clients.

2. Do not repeat the general requirements of Division 1 in the technical sections (Divisions 2 through 49).

3. Do not use broad statement requirements, such as, “Electrical requirements shall comply with Division 26”. Instead, list the specific sections which establish the requirements for the subject specification.

4. Use multiples of 7 days to establish time requirements (e.g. “respond in 14 days”) so that timelines contain multiples not fractions of weeks. Note the General Conditions define each “day” to be a calendar day (not business day or working day).

IV: CONTENT

Produce each individual technical specification section so that the content, intent, and meaning of the specifications incorporate the following.

Owner Project Requirements GO TO FRONT PAGE Page | 14

STANDARD REQUIREMENTS

The County establishes the following standard requirements, which shall be incorporated into individual specification sections wherever related discussion occurs.

1. Warranty: Specify individual product warranties only where greater than the two-year warranty requirement established by the General Conditions.

2. Extra Stock: Specify additional material or parts beyond that required for proper installation and operation, only where required by Code.

3. Recycled Content: Specify recycled content building products to reduce the need for virgin materials and to support product recycling markets where practical. Recycled content products may contain post-consumer or post-industrial recycled content, or a combination of both.

4. Limit PVC Material: Where practical, specify alternatives to polyvinyl chloride (PVC) products (e.g. ABS, HDPE, or recycled plastic).

5. Local Building Material: Where practical, specify locally extracted or manufactured building materials and products to reduce the environmental impact, time, and cost of transportation, and to support the local and regional economy.

6. Fire-Related Material: Specify fire industry approved products for all fire-resistive assemblies (e.g.

dampers, doors) including fire detection, annunciation, and suppression.

7. Lists of Acceptable Products: Promote unlimited competition consistent with the type and quality of work, and to maximize the use of standard products and current models.

a. Product lists with two or less items shall include “or approved substitution” (not “or equal”).

The substitution phrase will invoke requirements of the Request for Substitution (rather than a judgment whether products are equivalent).

b. Product lists greater than two do not need to include the substitution requirement.

c. Product lists shall not exceed five items and should represent the best choices available for the current project.

d. Listed or referenced materials and products shall meet the requirements of the specification section and the current project.

SOLE SOURCE EXEMPTIONS

The Washington County Board of Commissioners has granted exemptions for a limited number of products, which shall be specified as sole source (i.e. no product alternates listed or accepted). These exemptions do not preclude the selection of different or additional products if it is determined to be in the best interest of the County.

1. AMAG Technology, a G4S integrated security company: Access Controls.

Owner Project Requirements GO TO FRONT PAGE Page | 15

a. AUTHORIZING AN EXEMPTION TO SPECIFY THE AMAG TECHNOLOGY BRAND NAME FOR

PURCHASE OF ACCESS CONTROL EQUIPMENT AND COMPONENTS FOR ALL PROJECTS AND

COUNTY BUILDINGS.

b. Term: Perpetuity.

2. Schlage, a business of the Ingersoll-Rand Company LTD.: Pedestrian door locksets, cylinders, and latch sets.

a. AUTHORIZING AN EXEMPTION TO SPECIFY SCHLAGE BRAND LOCKS FOR ALL PROJECTS AND

COUNTY BUILDINGS.

b. Terms: Perpetuity.

3. Steelcase Inc.: System Furniture-Avenir

a. AUTHORIZING AN EXEMPTION TO SPECIFY STEELCASE BRAND SYSTEM FURNITURE FOR ALL

PROJECTS AND COUNTY BUILDINGS.

b. Terms: Perpetuity.

BASIS OF DESIGN

The A/E Service Provider shall use materials, products and systems preferred by the County as the basis-of-design or benchmark for acceptance, when specifying related items.

DELEGATED DESIGN

The A/E Service Provider shall provide specifications for engineered designs (rather than “design/build” or “performance and design” specifications), except where the Project Manager provides written authorization or where delegated design is the most common practice (e.g. pre-engineered metal buildings, fire suppression systems). Where professional design services or certifications by a design professional are required of the Contractor, the A/E Service Provider shall provide specific performance and design criteria for those products and systems. Delegated design submittals shall comply with the following County standards, which the A/E Service Provider shall attach to their specifications.

1. Deliverable Standards: Submittals and Shop Drawings shall comply with the standards in this document.

V: EDITING

Following the issuance of the Project Manual, modifications shall be made by the A/E Service Provider as follows.

Owner Project Requirements GO TO FRONT PAGE Page | 16

PROJECT MODIFICATIONS

During each project, the A/E Service Provider shall use the following editorial directions to issue modifications (e.g. Addenda, Change Orders, Construction Change Directives, or Minor Changes to the Work) as follows:

1. Use Microsoft Word ® Track Changes (in strike-out mode) to provide a written document preserving knowledge of facts or events for authorized additions, deletions, and other modifications. Deleted text shall be struck trough. Added text shall be underlined and shall be colored blue. Update the footer to indicate the revision date and modification Set Name (e.g. Addendum #2).

2. For the next revision to the same specification section, accept the previous insertions and deletions prior to “tracking” new changes. Update the footer to indicate the new revision date and modification Set Name (e.g. Addendum #3).

3. Refer to

Owner Project Requirements GO TO FRONT PAGE Page | 17

EXHIBIT A4: SAMPLE PROJECT MODIFICATIONS

PROJECT RECORD DOCUMENTS

At project closeout where authorized in writing by the Project Manager, the A/E Service Provider shall collect previously issued modifications (i.e. Addenda and Change Orders) and Contractor mark-up documents (i.e.

“as-builts”) into one set of Project Record Documents as follows:

1. Incorporate “as built” information as new insertions, deletions, and other modifications.

2. Indicate products selected and installed or used with bold font (e.g. in product lists).

3. Where Requests for Substitutions granted, use both bold text and “Track Changes”.

4. Refer to EXHIBIT A5: SAMPLE PROJECT RECORD SPECIFICATIONS.

VI: QUALITY

A/E Service Providers shall review and correct their documents prior to submittal to the County. Pay special attention to the following, which lists the most frequent specification quality concerns.

1. Verify that the items in Related Sections exist for the current project.

2. Verify that all product lists end with “or approved substitution” (not “or equal”) unless provided a sole source exemption approved by the Washington County Board of Commissioners or the list contains more than two choices.

3. Verify that mechanical and electrical specification sections do not restate or contradict information in Division 1 – General Requirements.

4. Verify that technical specification sections read clearly and do not create conflicts internally or with other sections.

5. Advise the Project Manager where errors, omissions or discrepancies occur in any County-provided documents, templates, or other building information.

6. Check grammar and spelling in specification sections.

7. Check footers for project name, A/E job no., set name, date, and revision date.

Owner Project Requirements GO TO FRONT PAGE Page | 18

EXHIBIT A1: SAMPLE PROJECT DIRECTORY / CERTIFICATION PAGE

PROJECT DIRECTORY / CERTIFICATION PAGE

Washington County: “Project Name”

Hillsboro, OR

[Architect Logo Here] [Architect Stamp Here]

OWNER: Washington County Facilities and Parks Services 169 North First Ave

Hillsboro, OR 97124 Attn: Bassam Khalifeh, Senior Capital Improvements Projects Manager Ph: (503) 846-4849 Email: bassam_khalifeh@co.washington.or.us

ARCHITECT: Name:

Address:

Attn:

Ph:

Email:

CONSULTANT: Name:

Address:

Attn:

Ph:

Email:

CONSULTANT: Name:

Address:

Attn:

Ph:

Email:

mailto:bassam_khalifeh@co.washington.or.us

Owner Project Requirements GO TO FRONT PAGE Page | 19

EXHIBIT A2: SAMPLE TABLE OF CONTENTS

TABLE OF CONTENTS

Project Directory / Certification Page

Table of Contents

Division 1: GENERAL REQUIREMENTS

01 11 00 Summary of Work 01 23 00 Bid Alternates 01 25 00 Product Substitution 01 26 00 Modification Procedures 01 29 00 Application for Payment 01 29 73 Schedule of Values 01 31 00 Coordination 01 31 19 Project Meetings 01 32 00 Construction Schedules and Daily Reports 01 33 00 Submittals 01 33 50 Bidder Designed and Engineered Systems 01 42 16 Explanations and Definitions 01 42 19 Reference Specifications and Standards 01 45 00 Quality Control 01 56 00 Temporary Facilities & Security Controls 01 60 00 Materials and Equipment 01 61 16 Special Requirements – Sustainable Building Practices 01 71 23 Field Engineering 01 73 29 Cutting and Patching 01 74 00 Cleaning and Waste Management 01 77 00 Contract Closeout 01 78 23 Operation and Maintenance Data 01 78 36 Warranties 01 78 39 Project Record Documents

Division 2: EXISTING CONDITIONS

02 41 19 Selective Demolition

Owner Project Requirements GO TO FRONT PAGE Page | 20

EXHIBIT A3: SAMPLE PARAGRAPH

1.1 SPECIFICATION FORMATS AND CONVENTIONS

A. Specification Content: The specifications use certain conventions for the style of language and the intended meaning of certain terms, words, and phrases:

1. In accordance with CSI Manual of Practice, skip a line between Articles (e.g. 1.1 and 1.2) and between Paragraphs (e.g. A. and B.). Also skip a line between subparagraphs of different indentation (e.g. a. or (1)). Do not skip lines between subparagraphs of same indentation.

2. Imperative mood and streamlined language are generally used in the Specifications.

a. Occasionally, the indicative or subjunctive mood may be used in the Section text for clarity to describe responsibilities to be fulfilled indirectly by Contractor or by others when so noted.

(1) The Words “shall,” “shall be,” or “shall comply with,” depending on the context, are implied where a colon (:) is used within a sentence or phrase.

(2) Refer to CSI Manual of Practice and exhibits included therein for further guidelines and examples.

Owner Project Requirements GO TO FRONT PAGE Page | 21

EXHIBIT A4: SAMPLE PROJECT MODIFICATIONS

1.1 SPECIFICATION FORMATS AND CONVENTIONS

A. Specification Content: The specifications use certain conventions for the style of language and the intended meaning of certain terms, words, and phrases:

1. In accordance with CSI Manual of Practice, skip a line between Articles (e.g. 1.1 and 1.2) and between Paragraphs (e.g. A. and B.). Also skip a line between subparagraphs of different indentation (e.g. a. or (1)). Do not skip lines between subparagraphs of same indentation.

2. Imperative mood and streamlined language are generally used in the Specifications.

a. Occasionally, the indicative or subjunctive mood may be used in the Section text for clarity to describe responsibilities to be fulfilled indirectly by Contractor or by others when so noted.

depending on the context, are implied where a colon (:)

is used within a sentence or phrase.

(2) Refer to CSI Manual of Practice and exhibits included therein for further guidelines and examples.

(3) Language that is incorrect or inadvertently in the section.

B. Acceptable Manufacturers:

1. Carnes.

2. Krueger.

3. Metalaire, Inc.; Metal Industries Inc.

4. Nailor Industries of Texas Inc.

5. Price Industries.

6. Titus.

C. Configuration: Diverting-damper assembly inside unit casing with control components located inside a protective metal or plastic shroud.

Owner Project Requirements GO TO FRONT PAGE Page | 22

EXHIBIT A5: SAMPLE PROJECT RECORD SPECIFICATIONS

1.1 SPECIFICATION FORMATS AND CONVENTIONS

A. Specification Content: The specifications use certain conventions for the style of language and the intended meaning of certain terms, words, and phrases:

1. In accordance with CSI Manual of Practice, skip a line between Articles

(e.g. 1.1 and 1.2) and between Paragraphs (e.g. A. and B.). Also skip a line between subparagraphs of different indentation (e.g. a. or (1)). Do not skip lines between subparagraphs of same indentation.

2. Imperative mood and streamlined language are generally used in the Specifications.

a. Occasionally, the indicative or subjunctive mood may be used in the Section text for clarity to describe responsibilities to be fulfilled indirectly by Contractor or by others when so noted.

depending on the context, are implied where a colon (:) is used within a sentence or phrase.

(2) Refer to CSI Manual of Practice and exhibits included therein for further guidelines and examples.

B. Acceptable Manufacturers:

1. Carnes.

2. Krueger.

3. Metalaire, Inc.; Metal Industries Inc.

4. Nailor Industries of Texas Inc.

5. Price Industries.

6. Titus.

C. Configuration: Diverting-damper assembly inside unit casing with control components located inside a protective metal or plastic shroud.

Owner Project Requirements GO TO FRONT PAGE Page | 23

EXHIBIT B1: GENERAL DISCUSSION

GENERAL NARRATIVE

Washington County has established guidelines of standard materials and finishes that shall be followed by the A/E as a project is being developed. This document identifies those standard materials and finishes that the County feels key to long term efficiency from a maintenance and aesthetic standpoint. The A/E shall use these materials and finishes exclusively unless otherwise approved by the Project Manager. Where material or finishes are not addressed within this standard, the A/E shall specify products that are appropriate for the project and have good long-term durability and are easily maintained. Limit use of polyvinyl chloride (PVC) based materials.

The County is committed the environment and strives to be conscious of the impacts building materials can have on the environment. When possible, specify products that contain recycled materials, can be easily recycled, and have low VOC emissions. Adhesives, sealants, sealants primers, paints, coatings, and flooring shall comply with the following:

1. Adhesives, Sealants and Sealant Primers: VOC content at or below levels allowed by South Coast Air Quality Management District (SMAQMD) Rule #1168. Caulks and Sealants: VOC content at or below levels allowed by Bay Area Air Quality Management District (BAAQMD) Regulation 8, rule 51. Aerosol adhesives: VOC content at or below levels allowed by Green Seal Standard GC-36.

VOC CONTENT (g/liter) Architectural Applications

Indoor Carpet Adhesives 50 Carpet Pad Adhesives 50 Outdoor Carpet Adhesives 150 Wood Flooring Adhesives 100 Rubber Floor Adhesives 60 Subfloor Adhesives 50 Ceramic Tile Adhesives 65 VCT & Asphalt Tile Adhesives 50 Drywall & Panel Adhesives 50 Cove Base Adhesives 50 Multipurpose Construction Adhesives 70 Structural Glazing Adhesives 100 Single-Ply Roof Membrane Adhesive 250 Specialty Applications PVC Welding 510 CPVC Welding 490 ABS Welding 325 Plastic Cement Welding 250 Adhesive Primer for Plastic 550 Contact Adhesive 80

Owner Project Requirements GO TO FRONT PAGE Page | 24

Special Purpose contact Adhesive 250 Structural Wood Member Adhesive 140 Sheet Applied Rubber Lining Operations 850 Top & Trim Adhesive 250 Substrate Specific Applications Metal to Metal 30 Plastic Foams 50 Porous Material (except wood) 50 Wood 30 Fiberglass 80 Sealants Architectural 250 Non-Membrane Roof 300 Roadway 250 Single-Ply Roof Membrane 450 Other 420 Sealant Primers Architectural Non-Porous 250 Architectural Porous 775 Modified Bituminous 500 Other 750 Aerosol Adhesives General Purpose Mist Spray 65% VOCs by weight General Purpose Web Spray 55% VOCs by weight Special Purpose aerosol adhesives (all types) 70% VOCs by weight

2. Paints & Coatings: VOC content at or below levels allowed by Green Seal GS-11 Limits for Paints and Coatings, and Green Seal GS-47 Limits for Stains and Finishes.

VOC CONTENT g/liter Paints and Coatings excluding water and colorants added at the point-of-sale:

Flat Topcoat 50 Non-Flat Topcoat 100 Primer or Undercoat 100 Floor Paint 100 Anti-Corrosive Coating 250 Reflective Wall Coating 50 Reflective Roof Coating 100 Paints and Coatings including water and colorants added at the point-of-sale:

Flat Topcoat 100 Non-Flat Topcoat 150 Primer or Undercoat 150

Owner Project Requirements GO TO FRONT PAGE Page | 25

Floor Paint 150 Anti-Corrosive Coating 300 Reflective Wall Coating 100 Reflective Roof Coating 150 Stains and Finishes Finish: Varnishes 350 Finish: Conjugated Oil Varnish 450 Finish: Lacquer 550 Finish: Clear Brushing Lacquer 680 Finish: Shellacs/Pigmented 550 Finish: Shellacs/Clear 730 Stains 250 Sealer 200 Waterproof Sealers 250 Low Solids Coating 120

3. Flooring Systems: VOC content at or below levels allowed by Carpet and Rug Institute Green Label program for cushion. VOC content at or below levels allowed by Carpet and Rug Institute Green Label Plus program for carpet and carpet adhesives.

EMISSION FACTOR LIMIT Mg/m2/hr. EMISSION FACTOR LIMIT Mg/m2/hr.

Total VOC: Carpets 0.50 Formaldehyde 0.05 4-Phenylcyclohexene 0.05 2-Ethyl-1-Hexanol 0.30 Formaldehyde 0.03 Total VOC: Cushion 1.00 Styrene 0.41 4-Phenylcyclohexene 0.30 Total VOC: Adhesives 10.0 Formaldehyde 0.05 Styrene 0.05

OVERVIEW AND SCOPE

OVERVIEW AND DEFINITION

1. This Owner Project Requirements (OPR) defines essential requirements to the operation and life cycle needs of the project.

2. This OPR is intended to be the first step in the creation of Basis of Design (BOD) documents, which will be provided by the Design Team. BOD documents vary by project, but could be Preliminary Design, Schematic Design, or Design Development drawings.

3. This OPR shall inform the Project Manual, including the Specifications.

4. This document supersedes the “Space Standards for Washington County Revised 2017” document.

Owner Project Requirements GO TO FRONT PAGE Page | 26

SUSTAINABILITY

GENERAL

1. Describe general sustainability goals for this project

2. Describe strategy for achieving sustainability certifications or achievements to make the project eligible for Federal, state, or local tax credits or incentives.

3. Washington County requests project to be designed to sustainability standards, and goals, however we do not seek certifications. It is our preference to redirect that energy and cost into building products and services. We take a ‘Design to the Standards’ approach.

DATA SECURITY

1. Building Data shall not exist on cloud services other than Microsoft 365, or Sharefile. Additional Cloud services that are not approved are, but not limited to, Dropbox, Box, WeTransfer, and Google Drive.

2. Project Information Management services will need to be properly evaluated for data security prior to use.

VIRTUAL DESIGN, CONSTRUCTION, AND OPERATIONS

OVERVIEW

This section defines essential requirements to developing a BIM model for The County’s operation and life cycle needs.

SCOPE

1. This document shall provide minimum requirements for developing a BIM process. The criteria in this section shall be rolled into the Architect’s BIM Execution Plan

2. The VDCO section applies to all projects with a construction valuation over $300,000.

REVIT MISSION STATEMENT

1. The County has developed this BIM Requirements to exploit Revit’s built in, and automated features. Our requirements aid in standardizing digital documents, facilitate development of a Record Model, and simplify data exchanges from Construction to Facilities Management.

2. The County values the relationships we build with our AEC partners. This document aims to minimize any invasive constraints that could create avoidable complexity.

Owner Project Requirements GO TO FRONT PAGE Page | 27

SOFTWARE

1. Revit is the preferred platform for BIM documentation and delivery; however, we recognize that not all partners have invested in this platform. IFC exports are accepted for delivering a BIM when Revit is not used. Please work with the County BIM Manager prior to project kick-off to request approval.

2. AutoCAD is no longer accepted for projects with a construction valuation of more than $200,000. Civil 3D documents are accepted.

3. Revit requires all partners to be on the same version and build for compatibility. Revit 2021 is the required platform build for all new projects.

MODEL TYPES

1. All Models shall be distinct and built on their discipline function.

2. Structural, Architectural, Fire Protection, Fire Alarm, Plumbing, Mechanical, Electrical, Telecommunications, and Security are examples of models that shall be isolated.

SHEET ANATOMY

3. For Title Block, sheet anatomy, and samples, please review the Revit Template document for more information.

4. Architect shall conform sheet layouts with the layout guidelines provided.

5. In cases where there are no specific guidelines provided, we defer to the Architect to provide leadership and coordinate across all disciplines.

6. Paper Size Arch E1 is preferred for all A/S/MEP consultants. ANSI D may be used if required by some AJHs for Civil and Landscape.

BIM EXECUTION PLANNING

1. Architect to facilitate a process for creating a BIM Execution Plan (BEP) no later than the start of Design Development. This process to include all A/E team members.

2. Architect to collaborate with the selected Contractor to create a BEP for their construction effort.

3. Minimum requirements

a. At a minimum, the BEP shall include an execution and planning document, and a Model Element Authorship (MEA) matrix. The MEA shall identify what elements are being modeled by which partner, and when it is to be modeled.

b. A BEP is required for all projects with a construction valuation of more than $750,000.

Owner Project Requirements GO TO FRONT PAGE Page | 28

MODELING PRACTICES

1. Modeling vs Detailing

a. Washington County does not require all detailing to occur in Model Views. We understand that due to software, financial, or time limitations Drafting Views can be used.

2. In-Place Families

a. Limited uses of In-Place families will be permitted. In-Place families shall be accepted when they exist in only 1 place. When families are used in multiple places, Component Families shall be used.

3. Component Families

a. Component families shall not contain dwg elements

4. Levels

a. Levels shall not be used for defining Ceiling location. Ceilings shall be offset from the primary level.

b. 2 or more Levels shall not exist at the same elevation.

5. Phases

a. Phases may be utilized in creation of existing FM models. Phases shall be utilized for documentation and modeling purposes. When the Design professional receives the models from the County, please review and coordinate the name and position of all phases.

6. Family Naming

a. Component and System families shall be named via the format found in the Revit Template. See

ADDITIONAL REFERENCE DOCUMENTS

7. Coordinates

a. When possible, the model coordinates shall be ‘Acquired By’ a Civil file and tied into the Oregon State Plane coordinate system. All models, from all partners, shall be tied into the same coordinate system.

8. Design Options

a. All design options shall be accepted and removed prior to turning the model over during Close-Out.

9. Phases

a. Models shall utilize Revit’s built in Phases workflow.

10. Existing Conditions

Owner Project Requirements GO TO FRONT PAGE Page | 29

a. All models received from the County shall be considered ‘Existing Conditions’ for the purpose of modeling. New work to be added to the New Construction phase. New ‘Phases’ may need to be added, to be determined by project needs and base model provided.

11. Project Parameters

a. Project and Global Parameters shall be removed prior to model deliverable.

TEAM SPECIFIC GUIDELINES

1. Architectural

a. All equipment, toilet accessories, office equipment, and furniture shall be modeled accurately.

b. Ceilings shall be modeled in the Architecture model, however Lights, Air Outlets and Inlets, Speakers and other ceiling components shall live in their respective models. Geometries used for coordination must be removed prior to Construction Documents.

c. Systems Furniture shall be modeled accurately. Washington County has Systems Furniture Families available if needed.

2. Site

a. All site equipment shall be modeled accurately, including furnishings, fences, bollards, slabs, and stairs.

3. Structural

a. Major Steel items shall be modeled, including Framing, Columns, Trusses, Floors, Foundations, Footings and Slabs.

b. Small steel like Strut Chanel and some angle frames may not require modeling, unless it is needed for coordination.

4. Mechanical

a. Mechanical Ducts, Terminal, and Equipment shall be unified under the appropriate System in the Systems Browser.

b. Equipment must have appropriate MEP connectors coupled and sized.

c. All MEP equipment must be properly size and located based on the product cut sheet.

5. Electrical

a. Electrical systems shall be labeled and classified accurately. Panels shall be modeled and labeled properly in their Panel Schedule and Systems.

b. All power and lighting equipment shall be modeled and located accurately

c. Where needed, connectors may be placed to connect with linked elements.

Owner Project Requirements GO TO FRONT PAGE Page | 30

d. Conduit banks are required, however not all conduit is required to be modeled.

e. Cable Trays shall be modeled

6. Plumbing

a. Plumbing equipment, piping, fittings, and accessories shall be modeled and located accurately.

SPECIFICATIONS INTEGRATIONS

1. There is no requirement to link project specifications to the models for bi-directional information exchanges.

2. Specifications will be integrated into the models via Model Component, Detail Component, and Material names.

INTEGRATING FACILITY MANAGEMENT (FM) DATA

1. Quantity Take Offs (QTO)

a. The County shall utilize the Revit model for general material take offs at each milestone. The model shall not be used for construction level quantity take offs unless explicitly written.

2. Laser Scanning

a. Laser Scanning of a building may be provided to the design team, where one exists. Please note:

Laser Scanning, like a photograph, is a snapshot in time, and may not reflect the current condition of the building.

b. When possible, a County commissioned laser scan will be re-modeled in Revit for use by our A/E partners. Washington County utilizes Laser Scanning for:

i. Scanning for existing conditions

ii. Scanning during construction for validation

iii. Scanning for record models

iv. Photogrammetry

RECORD DOCUMENTS

Record Documents could include As-Builts, As-Designed, or As-Constructed level of completion.

COBIE

1. COBie files are being utilized to transfer project data from Architect and Contractor to our Facility Management team. Washington County utilizes a CMMS tool that can employ building assets for digital

FM.

Owner Project Requirements GO TO FRONT PAGE Page | 31

2. At substantial completion the Contractor shall provide the County BIM Manager with preliminary COBie files for all equipment in the scope of work. Additionally, we require all rooms to be scheduled in a COBie format.

3. At Project Close-Out, Contractor to provide final copies of the COBie files.

4. Rooms, Doors, Windows, Curtain Wall, Finishes, Systems, Equipment, Site features are a required deliverable.

5. Examples and templates shall be provided at Contractors Request

GRAPHIC STANDARDS

STYLE GUIDE

Washington County has published a Style Guide (which can be provided upon request) that defines fonts, logos and more. The Washington County logo has 3 colors, defined here:

Color RGB Pantone CMYK Hex Blue 000,115,164 307 94C 48M 18Y 1K #0073a4, Gold 175,143,110 874 31C 41M 60Y 4K #af8f6e Black 000,000,000 Black 60C 40M 40Y 100K #000000

BUILDING CLASSIFICATION LEVELS

GENERAL

1. Building data; created by, commissioned for, and used by Washington County Facilities and Parks Services includes material that could potentially be used for nefarious purposes. This Building Data has traditionally been passed along via physical copies at stages of the project. With the advent and proliferation of digital cloud storage and file transferring services, our Building data has moved to the cloud.

2. A project could potentially employ hundreds of different persons over the life of the project, resulting in increased risk liability. When a project is closed, the digital information could live on a server, unbeknownst to the County. Additionally, it is important to know who is downloading what, and when. By having each user login to download a file, we know that the links, if shared externally to the team, could not be downloaded.

3. Building data can include, but is not limited to:

Drawings: Floor Plans, Elevations and Sections, etc Structural analysis and drawings: Including locations of columns, shear walls, and foundations IT, Plumbing, Mechanical and Electrical System diagrams Product Specifications Operations and Maintenance manuals

Owner Project Requirements GO TO FRONT PAGE Page | 32

Door Hardware configuration Construction drawings that include high level of detail Project BIMs (Building Information Modeling) Material Schedules Contract and Budgeting information Budget sourcing pools And more…

4. This document classifies Building data to better understand the risks we are potentially exposed to. All building projects shall be classified strictly according to their level of sensitivity as follows

LEVEL 1 – “PUBLISHED”

1. This is characterized as being open public building data with no distribution limitations and to which anonymous access is allowed. These data elements form information that is actively made publicly available by County government. It is published and distributed freely, without restriction. This includes information regularly made available to the public via electronic, verbal, or hard copy media.

2. Threat: Unauthorized or unintentional alteration, distortion, or destruction of this data. Security efforts appropriate to the criticality of the system containing this data must be taken to maintain its integrity.

3. Examples:

Press releases Brochures Pamphlets Public access web sites Materials created for public consumption

LEVEL 2 – “LIMITED”

1. These building data elements are the information made available through project design and construction, and open records requests or other formal or legal processes. This category includes most of the data contained within the County “BuildingData” electronic databases. Direct access to this data is restricted to authenticated and authorized individuals who require access to that information while performing their duties. All building data must be removed from cloud services after project completion, and data turned over to the County.

2. Threat: Unauthorized access, alteration, and destruction concerns.

3. Examples:

Most data elements in state personnel records Building code violations data Federal contracts data Historical records repository data Real estate appraisal data Telephone numbers

Owner Project Requirements GO TO FRONT PAGE Page | 33

Email addresses Enterprise risk management planning documents Name (first and last name or first initial and last name) Web Construction Cameras

4. Building:

Adams Crossing Animal Shelter Event Center Facilities Maintenance Building Hillsboro Clinic Juvenile Services Building Public Services Annex Public Services Building Service Center East South Clinic Tigard Recovery Center Walnut Street Center Washington County Museum Washington Street Conference Center

LEVEL 3 - “RESTRICTED”

1. This building data is available only to authorized users and may be protected by State or County regulations. Restricted data is intended for use only by individuals who require the information while performing job functions.

2. Threat: Unauthorized alteration or destruction. If this data were accessed by unauthorized persons, it could compromise locations of sensitive building data. Unauthorized disclosure could provide significant gain to a vendor’s competitors and could pose harm to the County due the departments at risk.

3. All building data must be accessed by authorized and authenticated persons only. All building data must be removed from cloud services after project completion, and data turned over to the County.

4. Examples:

IP addresses Firewall hardening standards and configurations VPN hardening standards Comprehensive law enforcement data Network diagrams Trade secrets data Insurance policy number Driver’s license or state identification card number Signatures Product Specification

Owner Project Requirements GO TO FRONT PAGE Page | 34

5. Buildings:

Blanton Administration Building Community Corrections Center Courthouse Harkin’s House Justice Services Building LEC – Sheriff’s Office Public Safety Building Public Safety Training Center

Owner Project Requirements GO TO FRONT PAGE Page | 35

LEVEL 4 – “CRITICAL”

1. Building data classified as being critical is data whose disclosure or corruption could be hazardous to life or health. These data elements are the most sensitive to integrity and confidentiality risks. Access is tightly restricted with the most stringent security safeguards at the system as well as the user level. Failure to maintain the integrity and confidentiality could have severe financial, health, or safety repercussions. Very strict rules must be adhered to in the usage of this data.

2. All building data must only be located on cloud services with explicit and written approval from the County leadership.

3. All building data must be removed from cloud services after project completion, and data turned over to the County.

4. Threat: Violation of privacy statues and regulations in addition to unauthorized alteration or destruction. If this data were accessed by unauthorized persons, it could have severe financial, health, or safety repercussions.

5. Examples:

Critical infrastructure information Access points to building entry, including doors, windows, and roof penetrations Locations to building services vulnerabilities

6. Buildings:

LEC – Jail Washington County Consolidated Communications Agency

DIVISION 0: PROCUREMENT AND CONTRACTING

00 31 13 - PRELIMINARY SCHEDULES

Show the critical decisions The County needs to make, and by what date to keep the project on schedule.

00 65 36 - WARRANTY

1. The…