Every name OpenBEP fixes, in one place: the rules every name follows, model files, levels and views, Revit shared parameters, materials, line patterns and styles, text and dimension types, and families. Use these names as they are, so the same thing has the same name in every model and from every firm.
Names are code: English, no accents, starting with OB_. French users read the French label next to each name. Each list can be downloaded as a CSV that opens in Excel.
Literal, short, general to specific, and sorted so that what belongs together lists together. Every list on this page follows them; so should anything a project adds.
| Rule | Write | Not | Règle (FR) |
|---|
Revit already has these. Use them for their job and never copy their job into another parameter.
| Parameter | Job | Example | Rôle (FR) |
|---|
OB_X_, so it shows at handover.Discipline codes name the model files. They are the same kind of short codes the BEP Builder's LOD matrix uses to show who models what.
Example:
The Revit version (R24 for Revit 2024) is in the name because a file opened in a newer version can't go back. When the plan uses ISO 19650 file naming fields instead, these codes still fill the role field.
| Discipline code | Model | Modèle (FR) |
|---|
One set of levels for the whole project, owned by the LOCATION model; every other model copy-monitors them under the same names. Short codes that sort the way the building stacks, and never an elevation in the name.
An example building in section. Solid lines are storeys (Building Story ticked, one IFC storey each). The dashed line is a reference level: it has its storey's code first and no storey of its own. Not to scale.
| Code | Level | Building Story | Niveau (FR) |
|---|
L, so L10 sorts after L09. The ground floor is L01.L01M when it counts as a storey for the building code or areas; otherwise it is a reference level. The plan says which.L02_TOS, top of steel), with Building Story off.The project browser groups views in four levels: phase, drawing set, view type, then Revit's own view family. Every view name repeats the phase, set and type, then ends with the level, so names stay consistent and a copied view never needs renaming.
| Code | Revit phase | Phase (FR) |
|---|
One new phase uses N; a phased project numbers them P1, P2.
Revit's own names. Two of Revit's seven are deleted because no drawing needs them, and one is added. Each view template sets the filter, so nobody picks it by hand. Demolition is a status of an element, not a phase.
| Filter | Shows | Use it for | Keep |
|---|
OB_ViewSet)The folder is in full words; the view name carries the short code. Sets starting with Z- sort last, one browser filter hides them all, and they are left out at handover.
| Code in the name | Folder | Holds | Ensemble (FR) |
|---|
OB_ViewType)A three-digit number in front sorts the folders in a fixed order: 3D, site, floor plans, ceilings, sections, elevations, details. The gaps are for a project's own types. The view name carries the type without its number.
| Type | View | Vue (FR) |
|---|
Pattern . A view with no level ends with what tells it apart (N-CON-SECT-STAIR-01); design options end with -OPT1, -OPT2; a person's own views go in their own set (N-Z-USER-SAM-PLAN-L02). Drafting views have no phase, so DRAFT takes its place: DRAFT-CON-DET-PARAPET (a proposal). Title on Sheet carries the printed title, so the codes never reach the drawings.
Example project browser. ??? means a blank parameter. At the top, it holds the drafting views: they have no phase, so Revit can't put them anywhere else, but their set and type folders still sort them. Inside a phase, it holds views nobody filed, so they stand out.
| Browser level | Revit parameter | Set by |
|---|
In Revit: View › User Interface › Browser Organization › Views, new scheme Views (Phase-Set-Type-Family). Group by Phase, then OB_ViewSet, then OB_ViewType, then Family; sort by Associated Level. Both parameters are in the OpenBEP shared parameter file, so they survive in every firm's model, and the view templates fill them so a new view files itself. A filter on OB_ViewSet not beginning with Z- hides everyone's personal and unfinished views.
, for example . Each template sets OB_ViewSet and OB_ViewType.
Sheet numbers use one letter for the discipline, as title blocks and drawing lists expect, then a series digit and a sequence. Plans number from the lowest level up. The sheet name is plain words, the same as the Title on Sheet of its main view.
, for example .
| Letter | Discipline | Discipline (FR) |
|---|
| Series | Holds | Série (FR) |
|---|
Two-digit storeys keep both digits (12015 on L12). Basements, mezzanines and the roof (B1015, 1M015, R001) are a proposal. The number goes in Revit's built-in Number.
The OpenBEP shared parameters, each with one fixed GUID, plus the Revit built-in parameters the plan asks for (built-ins are never duplicated). Load the shared parameter file in Revit under Manage › Shared Parameters.
| Revit name | Label (EN) | Label (FR) | Type | Group | Element types | GUID |
|---|
Every project gets only the parameters its BIM uses and target LODs need: the BEP Builder exports that subset at step Element requirements. Rules and GUIDs: parameter dictionary.
Named OB_<Class>_<Material>_<Detail>: class first so all the wood lists together, then the material, then what sets it apart. Add the use only when it changes the material: oak flooring and oak ceiling slats are two materials, the same concrete in walls and floors is one. Never the brand or the thickness. The names below are examples of the pattern, not a closed list.
| Name | Class | Counted in take-offs | Label (FR) |
|---|
OB_<Class>_Generic (OB_Concrete_Generic) when the class is known but not the exact material, at LOD 100 and 200. Counted.OB_Generic_<Kind> (OB_Generic_Plastic) for materials nobody counts: furniture, equipment, appliances and fixtures. The thirty plastics of a loaded toaster become one. Take-offs skip them.OB_X_ and are reported at handover.Default, <By Category> or a Revit default name counts as no material from LOD 300 on.Revit's own metric line weights stay unchanged; the standard fixes the patterns, the styles and which pen each category uses. Lengths are on paper.
| Name | Dashes and gaps (mm) | Used for | Label (FR) |
|---|
Named OB_<pen>_<Pattern>, one per pen where needed. Site services drawn as lines add _OH (overhead) or _UG (underground), for example OB_2_Hidden_UG. Examples from the standard:
| Name | Pen | Pattern |
|---|
| Pen | 1:10 | 1:20 | 1:50 | 1:100 | 1:200 | 1:500 | Used for | Usage (FR) |
|---|
| Category | Projection pen | Cut pen | Pattern |
|---|
Arial Narrow for notes, dimensions and tags; Arial for titles. Nothing below 2.5 mm, so every sheet reads at half size. Heights are on paper.
| Name | Font | Height (mm) | Used for | Usage (FR) |
|---|
| Name | Units | Text type | Used for |
|---|
| Name |
|---|
The first generic Revit families of the OpenBEP library. They already carry the shared parameters of their element type. The Revit add-in builds the .rfa files from this list on your own machine.
| Family | Label (FR) | Element type | Types |
|---|
Where each list comes from, in the OpenBEP repository: parameters from shared-parameters/; materials, lines and text from the graphics and materials standard, which also gives the reasons and sources; families from library/. This page is rebuilt from those files, so it never drifts from them.
Code under Apache 2.0, text and lists under CC BY 4.0.