1 09/20/2022 - v5.3.4.26

09/20/2022 - v5.3.4.26

Publish Updates

The following is a list of updates related to the STRATUS Addin for Revit and AutoCAD used for publishing models to STRATUS. This information will help companies determine if they want to update software or wait until the mandatory quarterly update is made available. Customers who encounter a publish issue that has been fixed by an updated version of the software will be required to install the latest software version.

Fixed a Property to Map to Status Name Issue

Fixed a Property to Map to Status Name for Revit and ITM parts not populating Revit Parameters when Fab statuses do not match STRATUS Statuses. Instances where a fab part gets updated to a tracking status in STRATUS that is not in the FAB DB the STRATUS Status will still import into Revit if the STRATUS Status parameter is setup.

Instances the status is in the FAB DB the statuses will match and both be correct.

Fixed a Deleted File Attachment Issue

When attaching a file Reference (AutoCAD) or Manage Links (Revit) to a model to be published, if the file is modified prior to the model being published, it will not be part of the published model in STRATUS. As long as the file path is correct, the attachment will display under Models > Viewer > Filter > References.

Transition from Processors to Divisions

As advertised, Processor has been changed to Division.

Temporarily STRATUS.*.Processor properties will still display and work in reports.

Company-level Divisions

Under Admin > Company, Processors has been renamed to Divisions. The functionality remains the same.

As a result, Processor has changed to Division throughout STRATUS. Below are a few examples:

Added Conflict Resolution Override Per Model

Added the ability to override Conflict Resolution per model. This option is only available to the Project Admins.

To override Conflict Resolution for a model:

Go to Models > Dashboard.
For the model, click the Conflict Resolution option.
1. By default, all models inherit the Project Default.
  1. The Project Default can be viewed under Admin > Project > Settings > Assembly Conflict Resolution. If the Override Company Option for this Project is checked for the Type of model, then these settings will be used to determine the Assembly Conflict Resolution settings.
  2. If the Override Company Option for this Project is not checked, then STRATUS will get settings from the Company level under Admin > Company > Project > Assembly Conflict Resolution.
2. STRATUS is Always Right - See the Assembly Conflict Resolution section in the Settings (Admin) article.
3. Model is Always Right - See the Assembly Conflict Resolution section in the Settings (Admin) article.
4. Prompt User - See the Assembly Conflict Resolution section in the Settings (Admin) article.

Added Filter Tracking with Date Range

Added to Filters > Tracking a date range option. The date range option can be used to run reports for KPIs. For example, it can be used to display all items that have changed to the “Fabricated” status in the last month. All Tracking statuses are displayed in the list even if they do not have matching parts in the viewer.

To use the date range under Filters > Tracking:

By default, the Tracking date range option is disabled and unchecked.
Click the Changes checkbox to enable the feature.
1. All tracking statuses will be displayed in the list since dates change, different parts can be included and the counts for each will also update.
2. By default, the date range end date is set for today and the start date is set for 30 days in the past.
Set the dates as needed.
Hover over either date to display the number of days, including the end date, that are in the date range.
Disable the Tracking date range option by unchecking the Changes checkbox.

Updated Estimated Hours Automation

Updated how Estimated Hours are entered either manually or automatically by configuring a report field and added STRATUS.Package.HoursEstimated* for reporting.

There are two ways to generate Estimated Hours based on a Report Field. Note: To control the precision of the calculated value displayed, use the round() function when configuring the field.

Estimated Hours Report Field - Shop Only

To automatically generate estimated hours for the Shop Phase from the model based on the package category and a report field:

Configure the Estimated Hours Report Field, but do not click the Advanced checkbox.
Select an existing Report Field in the Estimated Hours Report Field column. In this example, a STRATUS.Field.* was selected for the Fabrication Release Package Category.
Under Models > Viewer > Actions > Packages, in the create new package dialog, select the configured package category (Ex. Fabrication Release). The Hours Estimated field will initially be 0 until parts are selected and then the Hours Estimated will be calculated as each part or a group of parts is selected. Note: In this workflow, Hours Estimated refers to Shop hours.
Once saved, the Shop Hours Estimated under Package’s Properties > Planning will display the calculated value. Note: The Hours Estimated for other Phases can be manually edited and the Total will recalculate.

Estimated Hours Report Field - Advanced

To automatically generate estimated hours for one or more project Phases (Office, Purchasing, Shop, and Field) from the model based on the package category and report field(s), use the Advanced Mode option for the Estimated Hours Report Field.

Under Admin > Company > Package Categories, for any Package Category, click the Advanced Mode checkbox. The Hours Estimated Hours Report Field section will display a column for all four project phases.
For any phase or phases, select a Report Field to calculate the Hours Estimated. In the example below, Advanced Mode is checked for the Dimensioning Package Category and one report field was selected to calculate Estimate Hours for the Shop, and a different report field was selected to calculate the Field estimated hours.
1. Notes:
  1. When a Phase is Empty, it means that Hours Estimated can be manually entered while the package is being created or in the Package’s > Properties > Planning area.
  2. In the Estimated Hours Report Field - Shop Only example, a report field had been selected for the Shop Only for the Fabrication Release Package Category which is still valid. However, the same field for the Dimensioning Package Category is now disabled since the Advanced Mode has been checked.
Once set, under Models > Viewer > Actions > Packages, the create new package dialog will include Total Hours Estimated and Package Phases when the configured Package Category (Ex. Dimensioning) is selected. In the example below, since the Dimensioning Category was selected, the Office and Purchasing estimated hours fields can be manually edited while the Shop and Field values will be calculated as parts are added to the package.
As parts are selected in the model, the Shop and Field estimate values are calculated and the Total Hours Estimated recalculated. Similarly, as parts are removed the estimate values are recalculated.
Enter a manual estimate (Ex. Purchasing) and the Total Hours Estimated value will recalculate.
Save the package and open the Package’s > Properties tab. The Hours (Estimated) values will display in the Planning table.

Added STRATUS.Package.HoursEstimated*

For reporting estimated hours, the following properties are available:

STRATUS.Package.HoursEstimatedOffice
STRATUS.Package.HoursEstimatedPurchasing
STRATUS.Package.HoursEstimatedShop
STRATUS.Package.HoursEstimatedField

Added Off-grid Line Dimension Annotation on Labels

Previously, GridOffsetX and GridOffsetY off-grid line dimension properties were added to Properties and to Reports. GridOffsetC.X and GridOffsetC.Y values have also been added. GridOffsetC.X and GridOffsetC.Y variables are also available for label templates in the format used by workstation cut list items (they may be converted to lowercase gridOffsetC.X and gridOffsetC.Y, similar to how the others are handled).

STRATUS.Part.GridOffsetC.X
STRATUS.Part.GridOffsetC.Y

Added to Containers an Exclude Contained Items Option

Added to Containers an Exclude Contained Items option that will exclude items from the Manual Selection list if the item is contained in any container. Checking this option is a device-specific setting and will be cleared when the user unchecks the setting or when the browser cache is cleared.

To use:

Go to the Containers > Assign page and select a Container.
For the Exclude Contained Items option:
1. Unchecked (Default) - When Unchecked, the default behavior of adding/removing items to/from the Contents of the container is that packages, assemblies, parts, and containers that have been added to the currently selected container are filtered out of the lists on the left under Manual Selection.
2. Checked - When checked:
  1. The setting will be saved to the device's local storage.
  2. The Manual Selection drop-down lists will now exclude any items that are included in any Container. In this example, parts of of Package REV-DIM-0001 have been added to Truck B.
  3. Switch to a different Container (Ex. Truck D). Since the Package still includes items that are not yet in a container, the package will still display, but the items that are included in a different container (Ex. Truck B) do not display in the list.

Added Project Roles for Containers and Scan

Added to Project Roles > Containers a View option that provides view-only access.
Added to Project Roles > Scan:
- a View option that provides view-only access.
- an Empty Container option that enables a user to Empty the container

Improved Template Font Size Options

Improved Template Font size options so that sizes under 8 can be used.

Updated Packages > Schedule to Update Automatically

Updated Packages > Schedule to update automatically when a change is made to the Required date on the Packages > Dashboard, or the Packages > Properties.

Fixed a Missing Link to an Assembly

Fixed an issue on the Assemblies > Dashboard where a link was missing to the assembly.