Read and extract information from a BEP

00:04

After completion of this video,

00:06

you'll be able to read a BIM execution plan to extract key project details and

00:11

describe how the information in a BIM

00:13

execution plan allows teams to collaborate efficiently.

00:17

The BIM execution plan,

00:19

or BEP for short,

00:20

is the document that translates high-level

00:23

project requirements into actionable workflows.

00:25

It ensures that everyone on the team is on the same page,

00:28

working consistently and collaboratively.

00:31

Think of it like a rulebook for the BIM.

00:33

It details everything from file naming to class detection and metadata.

00:39

It's important to standardize how teams work together.

00:42

Without standardization,

00:43

you'd have chaos,

00:44

different teams using different file names,

00:47

different file formats,

00:48

and workflows.

00:49

The key components of a BEP include workflows,

00:52

how files are stored,

00:54

validated,

00:55

and shared.

00:55

For example,

00:56

working in a work in progress folder before

00:59

validating a project model to a shared folder,

01:02

rules and responsibilities,

01:03

who does what and when,

01:05

and quality assurance processes like model validation to ensure accuracy.

01:10

The BEP standardizes many processes like file naming to avoid confusion,

01:15

for example,

01:16

the project code,

01:17

which is unique to every project,

01:19

the originator code,

01:20

which identifies who created the file,

01:23

the functional and spatial breakdowns,

01:25

communicates whether the building or the group of buildings

01:28

has been split into volumes or by level,

01:31

or if a file only contains part of a model such as the base level floor plan view.

01:37

It also defines file formats.

01:40

For instance,

01:41

all 3D revvit models should be native,

01:43

such as revvit project files,

01:45

IFC for sharing with non-revit users in the project,

01:48

and PDF for any drawings or reports.

01:52

The BEP ensures everyone knows where and how to collaborate,

01:55

for example,

01:56

what common data environment is being used here,

01:60

Autodesk Construction cloud,

02:02

and the BEP explains how the project will be divided

02:04

through a federation strategy such as volumes or assets.

02:09

Is the building split,

02:10

as in this example,

02:11

Volumes 12,

02:12

and 3?

02:13

Is the project model also split by discipline,

02:17

such as a separate architecture,

02:19

structure,

02:19

and building services model?

02:21

This keeps file sizes manageable,

02:24

ensures smooth collaboration,

02:25

and adheres to the BIM execution plan.

02:28

To allow different disciplines to coordinate with each other,

02:31

the BIM execution plan specifies project coordinates

02:35

to ensure all models are aligned correctly.

02:37

For example,

02:38

to allow multiple disciplines to use each other's files in their design task,

02:43

and if set in each project,

02:45

it allows the models to link to each other,

02:47

and they'll come in aligned in the correct location.

02:51

The BEP defines workset names and which works sets are required.

02:54

Works sets allow teams to work in different parts of

02:57

the model simultaneously without getting in each other's way.

03:00

For example,

03:01

one group may be working on walls while another roofs and so on,

03:05

as well as defining status codes to communicate the file status.

03:09

Work in progress,

03:10

for example,

03:11

is S0.

03:12

Shared for coordination is S1,

03:15

while shared for information is S2.

03:17

And when uploading files to the common data environment,

03:20

team members must assign the correct status code to indicate the file's purpose.

03:25

The BEP also contains approved software versions such as RVI version 2025,

03:31

and Teams insure their software and the versions match the BEP requirement.

03:35

The BEP appendix also includes additional details like clash detection settings,

03:40

what clashes or test,

03:42

and what the tolerances might be,

03:44

set up of export settings such as KOI,

03:46

how to structure data exports,

03:48

and IFC export requirements for

03:51

specific interoperability between different softwares,

03:54

as well as user privileges,

03:56

who can access what area in the common data environment,

03:59

and a glossary of terms like work in progress,

04:02

common data environment,

04:03

as well as federated model.