1 08/20/2021 - v4.0.4.15

08/20/2021 - v4.0.4.15

Updated How BIM Areas Are Applied

A subtle change has been made to the way Areas are applied to parts in STRATUS. The parts have historically been the primary source of the populated STRATUS.Part.BIMArea property. This was even the case once parts were assembled. Take this case for instance:

You have 10 parts straddling 2 different areas, area A and area B. Area A contains 7 parts and area B contains the other 3. If you were to assemble those, the assembly and its STRATUS.Assembly.BIMArea property would be associated with the part majority area (determined by the average positions of the parts) however the parts would still maintain their 7:3 split. Reapplying areas from the Projects > Areas page would have the effect of pushing that assembly averaged area in the parts.

With the change, the part areas will now be updated on assembly creation, modification, and deletion. This change only affects parts assembled, modified, or deleted in STRATUS and does not yet happen on changes made in AutoCAD or Revit. That will be coming after the Gen2 publisher launches.

Updated Publish for Revit Assemblies

Updated Publish for Revit Assemblies when Revit is always right is selected under Admin > Company > Settings > Assembly Conflict Resolution, parts will never be deleted, added, modified, or removed from the Revit assembly except to import data like QR code URLs, package names, tracking statuses, etc.

Updated Publish to Preserve Assigned Views for Packages and Assemblies

When a model has more than one 3D view and a user manually selects a 3D view on either the Packages Viewer or the Assemblies Viewers, their selection will be preserved after the model is republished.

Updated Packages Dashboard Required Date Filter for Empty

Updated the Packages Dashboard Default report Required Date (STRATUS.Package.RequiredDT) filter for Empty. To filter for Empty Required Dates:

Click the Filter button. A filter will display.
Click the red x for both fields. Empty Required Dates will display.

Updated Lead Days for Deliverables Packages

Updated Lead Days to be applied to Deliverables Packages. For example:

Under Projects > Deliverables, for any deliverable, create a package. See the Projects Deliverables article for more information.
If for the package’s Package Category a Company level Lead Days or a Project level Lead Days has been configured, then Lead Days will be applied in the Package’s Properties in the Planning section.

Updated Packages Schedule to Display the Project Target Start Date and Target End Dates

Updated the project row of the Packages Schedule to display the project Target Start Date and Target End Dates edited under Admin > Company > Projects.

In the Packages > Schedule the Project Target Start Date and Target End Dates display in the project row. The project row includes 2 different Gantt bars:

Thin multicolored bar - The Project Target Start Date and Target End Date are represented by the colored thinner bar in the project row.
1. Red - Indicates the time period before any package phase in the project has a Phase Start Date.
2. Green - Indicates the time period when at least one package has a Phase Start Date.
3. Yellow - Indicates the time period after any package phase in the project has a Phase Start Date.
4. Start Date and End Date column dates - The Start Date (6/15/2021) and End Date (9/28/2021) in the project row correspond to the thin bar (Project Target Start Date and Target End Date).
Thick black bar - All of the Project’s Package Phase Start Dates and Lead Days are represented by a thicker black bar in the project row.

Added Lead Day Report Field Properties

Lead Day Report Field Properties are available under Admin > Company > Reports including Office, Purchasing, and Shop Phase Lead Days as well as Office, Purchasing, and Shop Start Date fields. Note: The RequiredDT field which previously existed is associated with the Field Start Date.

The Lead Day Report Field Properties on the Packages Dashboard are directly linked to each Package > Properties > Planning section and can be edited in the same way. Changes to the Lead Days, Start Dates, cell Lock/Unlock are immediately saved. See the Lead Days Package Level Configuration article for more information.

Updated Property STRATUS.Part.C1ConnectedTo to Display Type and Size for Revit Systems Ductwork

Updated the property STRATUS.Part.C1ConnectedTo and STRATUS.Part.C2ConnectedTo for Revit Systems Ductwork to display the Type and Size properties.

Updated Numbering Incrementor to Increment Beyond XX, XXX, or XXXX

For Naming Conventions under Admin > Company > Naming and Numbering, the Incrementor option has three values, namely XX, XXX, and XXXX. If the numbering reaches 99, 999, or 9999, the next item will be numbered 100, 1000, or 10000 respectively. In the example below, the incrementor is XXX and incremented from 999 to 1000, then 1001.

Updated Processing Queue Management

The method for how items (see below) are processed has been updated in order to eliminate duplicate actions. For any of the following user actions, clicking the associated button will initiate a process that must be completed by the server. While the action is being processed it cannot be stopped or resent, thereby eliminating duplicate requests.

Import model
Backup model
Publish model
Send cut list
Generate MAJ
Generate PCF
A360 user refresh

Updated Error Message for Issues with the Revit ‘Use Parameter Mapping for Assembly Import and Publish’

Under Admin > Company > Settings, when using the Revit Use Parameter Mapping for Assembly Import and Publish option,

and the parameter has not been configured in Revit or is named incorrectly, users will receive the following error and the import process will cancel.

Fixed an Issue Where Parts and Assemblies Were Included in More Than One Package within the Same Package Category

Fixed an issue where parts and assemblies were included in more than one package within the same package category. For example, if:

Package-1 contains Part-A
Package 2 contains Part-B
Then Assembly-X is created and contains Part-A and Part-B
When Assembly-X is added to Package-1 the result is that Package-1 contains Assembly-X and that the loose parts no longer display as items in either package.

Fixed an Issue Creating Master Report PDF

Fixed an issue creating a Master Report PDF when the sub-report format was PDF and Assemblies Viewer was checked.

Fixed an Issue Updating BendWorks File Attachments

Fixed an issue updating BendWorks file attachments on subsequent publishes.