BIM_Requirements.pdf

Owner Project Requirements GO TO FRONT PAGE Page | 26

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.

SHEET ANATOMY

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

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

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

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.

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.

Owner Project Requirements GO TO FRONT PAGE Page | 28

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

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.

Owner Project Requirements GO TO FRONT PAGE Page | 29

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.

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.

Owner Project Requirements GO TO FRONT PAGE Page | 30

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.

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

Owner Project Requirements GO TO FRONT PAGE Page | 31

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 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

Owner Project Requirements GO TO FRONT PAGE Page | 32

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 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

Owner Project Requirements GO TO FRONT PAGE Page | 33

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

5. Buildings:

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

Owner Project Requirements GO TO FRONT PAGE Page | 34

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

DEFINITIONS