Numbering domains - numbering across projects

In a database containing several projects, you may need some projects to share unique component numbering while allowing others to reuse the same numbers.

Numbering domains define which projects share a uniqueness boundary for occurrence numbers, including component and system component numbers.

Use numbering domains to support workflows such as:

• Keeping coordinated numbering across several buildings in the same facility.

• Maintaining independent numbering for separate facilities in one database.

• Reusing asset numbers in an asset master project and a separate renovation project.

How numbering domains work

A numbering domain contains the projects whose occurrence numbers are validated together.

• Within the same domain: Projects share uniqueness validation. Where the numbering configuration requires unique numbers, a number already used in one project cannot be reused in another project in that domain.

• Across different domains: Projects can reuse the same occurrence numbers.

• Within a project: The configured numbering and uniqueness rules continue to apply.

• Project membership: A project can belong to only one numbering domain.

Numbering domains control where uniqueness is checked. The existing numbering configuration determines the structure of the number and the applicable uniqueness rules.

When comparing numbers, consider the complete occurrence number, not only its serial-number part.

Choose a numbering arrangement

Example: Building portfolio

A database contains three projects:

Projects A and B share a numbering domain. A component number used in A is therefore also considered when validating numbers in B.

Project C belongs to a different domain and can reuse a number used in A or B.

For example, if the complete number 001 already exists in Project A:

• The same number cannot be reused in Project B where uniqueness is required.

• The same number can be used in Project C.

Example: Asset master and renovation project

An asset master project contains the facility’s existing assets. A renovation project contains a subset of those assets for a separate design or delivery workflow.

Placing the projects in different numbering domains allows corresponding assets to retain the same component numbers in both projects.

When communicating or exchanging data across these projects, include the project context as well as the number so that the intended record is clear.

Administrator setup

Administrator access is required to configure numbering domains.

Before configuring the domains:

1. Identify which projects must share unique numbering.

2. Identify which projects may reuse numbers independently.

3. Review the existing component and system component numbering rules.

4. Agree on clear domain names, such as building, facility or portfolio names.

The general setup sequence is:

1. Open Setting and go to Project and database administration → Settings → Project → Numbering domains.

2. Create the required domains.

3. Save the configuration.

4. Then go to Project and database administration → Settings → Project → Settings and find the ‘Numbering domain’ dropdown. Assign current project to a numbering domain.

5. Note that each project must be assigned a numbering domain by logging into the respective project.

6. Reopen the settings and check the project assignments.

For the building portfolio example, create Facility 1 and Facility 2, assign Projects A and B to Facility 1, and assign Project C to Facility 2.

Create and edit component numbers

Continue creating and editing components and system components through your normal workflow.

When a number is validated, the relevant numbering domain determines which projects are included in the uniqueness check.

If a duplicate-number message appears:

1. Check the complete number you are assigning.

2. Check whether that number is already used in the current project.

3. Ask your administrator to check other projects in the same numbering domain.

4. Use an available number, or review the domain arrangement with your administrator if the projects should have independent numbering.

A number can conflict with an occurrence in another project even when it does not appear in the current project’s lists.

Automatic number generation

Automatic numbering uses the relevant numbering domain when determining the next available number.

For example, assume the projects use equivalent numbering sequences:

Generating a number in Project A considers the numbers used in both A and B, but not those used in C.

These examples illustrate the domain boundary. The actual number format and sequence depend on the database’s numbering configuration and classifications used.