A Package Category provides the ability to create different packages for different purposes like Office, Purchasing, Shop, and Field work. Package categories accommodate workflows where the same part or assembly needs to be included in multiple packages. A part or assembly can not be included in more than one package within the same package category.  A package category is required for all new packages. In addition, company level Package Category Automation is facilitated by using the features Generate on Tracking Status for generating reports when a tracking status changes, Duration Days (M-F) for calculated Start Dates related to scheduling, Shop Hours Estimated to estimate shop hours, and to Configure Company Level BOM Settings for a Package Category.

Stratus Academy Course Video

To take the Package Categories Admin course, login to Stratus Academy and and locate the course ADM-523: Package Categories.

New Package Category (Basic)

To create a Package Category with basic non-automated values:

1. Go to Admin > Company > Package Categories. The "basic" package category values are highlighted below. The other columns are described in separate sections.

   Open

   

    

   1. Name– The Package Category name is the name that will display in the Category drop-down list when a new package is created. See the next step for examples.

   2. Description (Optional) – A description of the package category to clarify how the category will be used.

   3. Abbreviation – The package category abbreviation can be used as part of the automated package naming referenced under Admin > Company > Naming and Numbering > Naming Conventions.

      1. Note: For Field Orderz users, the Abbreviation field for the associated Package Category must be set to FOZ (in all capital letters). If the abbreviation is not set correctly, packages will fail to publish from Field Orderz to Stratus.

   4. Use Assemblies – Stratus understands parts, assemblies, and packages. Different parts and assemblies can be included in one or more packages. For example, design and fabrication packages should include assemblies, but, purchasing would want packages that include individual parts, not assemblies. For example, let’s say you have a run of pipe that has been packaged.

      1. When checked the package will recognize the assemblies and will remove the individual parts from the package.

      2. When unchecked the package will recognize the individual parts in the package. As a result, a procurement package can be created for all valves, but other connected parts in the assembly will be ignored.

   5. Use Containers - A company doesn't want every package to be exposed to a Container. See the Containers Assign article for more information.

      1. When checked and a package is created using the associated package category, the package will display in the Containers > Assign > Package drop-down.

      2. When unchecked and a package is created using the associated package category, the package will not display in the Containers > Assign > Package drop-down.

   6. Delete a Package Category - When deleting a Package Category, a prompt will display to re-assign packages to another Package Category. Note: The new Package Category must have the same “Use Assemblies” settings as the one being deleted.

      Open

      

       

2. Once created, a Package Category is selected during the package creation process:

   1. Under Models > Viewer > Actions > Packages > New

      Open

      

       

   2. Under Packages > Dashboard > New Package

      Open

      

       

3. Package Categories are used to filter packages on the following pages:

   1. Models > Viewer > Display Mode > Packages > Select Package Category (Ex. Fabrication Production).

   2. Click the Normal tab when done viewing to return the default color of the viewer.

      Open

      

       

   3. Packages Dashboard

      Open

      

       

   4. Packages Schedule

      Open

      

       

   5. Packages Status Board

      Open

      

Generate on Tracking Status (Automation)

Reports can be defined and generated at the the Company level using Package Categories. The Generate on Tracking Status section will generate reports (Ex. MAJ, PCF, or Report (selected) for the associated Package Category when the tracking status changes to a specific tracking status.

Generate on Tracking Status (BOM)

Continued automation development when a package’s tracking status changes configured on the Admin > Company > Package Categories page. This time a package BOM can be automatically generated.

To generate a BOM report for a Package Category when the Tracking Status changes:

1. For the Package Category (Ex. BOM Trigger) click the associated BOM link. 

   Open

   

    

2. The Generate on Tracking Status drop-down will display.

   Open

   

    

3. Select a Tracking Status (Ex. Spooled).

   Open

   

    

4. Change the Tracking Status of any package that uses the associated Package Category (Ex. BOM Trigger) to the selected Tracking Status (Ex. Spooled). This tracking status change can be anywhere a package tracking status can be changed (Ex. Packages > BOM, Packages > Tracking, Packages Dashboard, etc.).

   Open

   

    

5. A BOM will be automatically be generated and will display on the Package’s BOM tab. It will take time to generate the BOM depending on the number of parts. The automation removes the need to manually click Generate BOM button. Also notice that the BOM Required Date uses the package’s Required Date, but these dates can be different.
   Note: This automatically generated BOM only occurs once when no existing BOM has been previously been generated for the package. If a BOM exists for the package and the package’s tracking status is changed to the tracking status that normally triggers a BOM, a new or 2nd BOM will not be generated.

   Open

   

Generate on Tracking Status (Cut Lists)

Continued automation development when a package’s tracking status changes configured on the Admin > Company > Package Categories page. This time a package Cut List can be automatically generated.

To generate a Cut List report for a Package Category when the Tracking Status changes:

1. For the Package Category (Ex. Cut List Trigger) click the associated Cut List link. 

   Open

   

2. The Generate on Tracking Status drop-down will display.

   Open

   

3. Select a Tracking Status (Ex. Issued for Fabrication).

   Open

   

    

4. Change the Tracking Status of any package that uses the associated Package Category (Ex. Cut List Trigger) to the selected Tracking Status (Ex. Issued for Fabrication). This tracking status change can be anywhere a package tracking status can be changed (Ex. Packages > Tracking, Packages Dashboard, etc.).

   Open

   

    

5. A Cut List will be automatically be generated and will display on the Package’s Cut Lists tab. It will take time to generate the Cut List depending on the number of parts. The automation removes the need to manually click Generate Cut Lists button.
   Note: This automatically generated Cut List only occurs once when no existing Cut List has been previously been generated for the package. If a Cut List exists for the package and the package’s tracking status is changed to the tracking status that normally triggers a Cut List, a new or 2nd Cut List will not be generated.

   Open

   

Generate on Tracking Status (MAJ)

To generate a MAJ report for a Package Category when the Tracking Status changes:

1. For the Package Category (Ex. FAB - Mechanical Piping) click the associated MAJ link. 

   Open

   

2. The Generate on Tracking Status drop-down will display.

   Open

   

    

3. Select a Tracking Status (Ex. Packaged).

4. When the Tracking Status of any package that uses the associated Package Category (Ex. FAB - Mechanical Piping) is changed to the selected Tracking Status (Ex. Packaged), a MAJ file will be automatically generated and saved as a package attachment. It will take time to generate the attachment depending on the file size.

Generate on Tracking Status (PCF)

To generate a PCF report for a Package Category when the Tracking Status changes:

1. For the Package Category (Ex. FAB - Mechanical Piping) click the associated PCF link. 

   Open

   

    

2. The Generate on Tracking Status drop-down will display.

   Open

   

    

3. Select a Tracking Status (Ex. Packaged).

4. When the Tracking Status of any package that uses the associated Package Category (Ex. FAB - Mechanical Piping) is changed to the selected Tracking Status (Ex. Packaged), a PCF file will be automatically generated and saved as a package attachment. It will take time to generate the attachment depending on the file size.

Generate on Tracking Status (Report)

To generate one or more Report attachments (CSV/PDF/ZPL) for a Package Category when the Tracking Status changes:

1. For the Package Category (Ex. FAB - Mechanical Piping) click the numeric value associated with the Report link. 
   Note: The numeric value indicates how many reports are triggered for the associated Package Category.

   Open

   

    

2. The Generate Reports for *Package Category* dialog will display.

   Open

   

    

3. Click the New Trigger button. A new row will display.
   

   
   
   

   1. Select the Tracking Status change that will trigger the report generation for a package using the associated Package Category.

   2. Select a Report that will automatically generate and display in the Package’s > Attachments tab.

      1. Note: The list of Reports (right) is restricted to Reports whose Package Viewer checkbox is checked (left). Reports whose Item Type is Master Report, Package, Package Details, Assembly, or Part and whose Package Viewer checkbox is checked will be available.

         Open

         

4. Click Save.

5. To auto generate the report from anywhere a package tracking status can be changed, identify a package associated with the Package Category Report Trigger defined above (Ex. Category = Fabrication Production).

   Open

   

6. Change the Tracking Status to the one selected in the Report Trigger (Ex. Cut). Refresh the page until the report display in the package’s attachment tab.

   Open

   

Duration Days (M-F) Company Level Configuration (Automation)

Summary

When configuring Package Categories, the Duration Days controls the number of days a project phase start date will offset from the Required date and the Default Linking option controls the initial Link Phase Calculations setting.

The Company level Package Categories Duration Days feature offers calculated initial Start Dates for package phases. For each Package Category, Duration Days can be set for each phase (Office, Purchasing, Shop, and Field). When a new package is created, Stratus will check to see if the selected package category includes Duration dates at the Company level (below), and then at the Duration Days Project Level Configuration (which would override the Company settings). In addition, initial Start Dates can be edited at the package level.

Open

To configure Duration Days for a package category:

1. Under Admin > Company > Package Categories, the Purchasing Days columns will display.

   1. Phases - A Duration Day can be set for each Phase and for each Package Category. Phases are also used in Division (Admin) and Tracking Statuses (Admin). 

      1. Office - Detailing Start Date

      2. Purchasing - Purchasing Start Date

      3. Shop - Fabrication Start Date

      4. Field - Field Date

   2. Duration Day - A Duration day is a business day Monday thru Friday. In the current calculation, weekends are excluded while public holidays are included as a business day. For example, if a Start Date for Purchasing Phase is 9/1/2021 and the Duration Day is set to 21, the Start Date for the Shop Phase will be 9/29/2021 where 4 Saturdays and 4 Sundays were excluded, and the public holiday 9/6/2021 was not excluded.

2. Edit the value associated with the phase.

3. For the Duration Day to be applied to a package during the create package process:

   1. Package Category (required) - The package category that includes Duration Days for one or more phases must be selected.

   2. Phase (optional) - Phase defaults to Required, but can be changed to a particular Phase. Selecting a phase will only denote which Start Date will be set with the Start Date entered (below). Initial Start Dates will populate the other Phases based on the Duration Days calculations.

   3. Start Date (optional) - The Start Date is used to set the Start Date of the selected Phase.  If a Start Date is not entered, all Phase Start Dates will be empty.

      1. The meaning of Required is defined by your company.

      2. On the Packages > Dashboard, the Required Date = Required Phase date.

   4. Note: Duration - If the Package Category selected includes Duration (days), then those Phase Start Dates will be calculated based on the Start Date of the selected Phase (#2).

4. See the Package Planning / Actual article for more information.

Edit Duration Days

The Confirm Save dialog will display when editing Duration Days at the company and project level.

After updating a Package Category > Duration Day:

1. Click the Save button.

   Open

   

2. The Confirm Save modal will display.
   

   
   
   

   1. Apply to Existing Packages w/o Duration Days

      1. This option will recalculate package durations that have at least one “Empty” start/end phase date for the specific Package Category/Planning Phase.

      2. Note: For this to trigger and recalculate, their must be at least one start date in the planning phase of the package.

         Open

         

          

   2. Apply to All Existing Packages

      1. This option will recalculate ALL existing package durations across the project that have duration days.

   3. Do Not Apply to Existing Packages

      1. This option will not recalculate any package durations within the project.

3. Select an option and Save.

Default Linking

Default Linking controls the default linked/unlinked behavior for the Package Category. When checked, packages created with that category automatically have Link Phase Calculations enabled; when unchecked, the option defaults to disabled. The Link Phase Calculations button on the right is enabled for the package.

Open

When configuring Package Categories, the Duration Days controls the number of days a project phase start date will offset from the Required date and the Default Linking option controls the initial Link Phase Calculations setting.

Unchecked - When Default Linking is unchecked, saving a new package with a Required Date propagates phase dates based on the Package Category's Duration Days, same as if it were checked. Once the package is created and initial dates set, future date edits from the Package’s Properties tab or from a Packages Dashboard Report will be unlinked and can be independently changed. However, by clicking the Link Phase Calculations button, the package becomes re-linked, project phase dates offset from the Required date, and dates are no longer independently editable.

Checked - When Default Linking is checked, saving a new package with a Required Date propagates phase dates based on the Package Category's Duration Days, same as if it were unchecked. Once the package is created and initial dates set, future date edits from the Package’s Properties tab or from a Packages Dashboard Report will have the Link Phase Calculations enabled and any phase date change automatically updates all other dates based on Duration Days. However, by clicking the Link Phase Calculations button, the package becomes unlinked, project phase dates offset from the Required date, and dates can be independently editable.

Note: The Link Phase Calculations button can be enabled and disabled from the Packages Dashboard. Switching a package from unlinked to linked will recalculate all phase dates from the Required Date next time a date is changed.

Video: Duration Day and Default Linking

Open

Package Reporting

Package Creation Settings

The Package Creation Settings dialog is used to control the fields that display during the Package Creation process (left) and when editing a Package’s Properties (right).

Open

Each Package Category displays a Package Creation Settings dialog where administrators can:

• Add any Stratus.Field.x or Stratus.Package.x field

• Delete any Stratus.Field.x or Stratus.Package.x field

• Control Field visibility for the selected package category

• Control Required fields for the selected package category

• Control Hidden fields during package creation that become editable after package creation

• Control Default values that automatically populate in new packages. These values can be hidden from package creators to prevent editing or remain visible and editable.

• Note: Package Creation Settings apply to new package creation under:

  • Packages > Dashboard > New Package > Select Category

  • Packages > Dashboard > Import CSV

  • Models > Viewer > Actions > Packages > New > Select Category

• Note: Package Creation Settings DO NOT apply to new package creation:

  • Using the OpenAPI

Add Field

To add any Stratus.Field.x or Stratus.Package.x field to a Package Creation Settings dialog:

1. Go to Admin > Company > Package Categories and click the gear icon in the Package Creation Settings column for any Package Category. A Package Creation Settings dialog similar to the following will display.

   Open

   

    

2. Click the New field button. A new Empty field row will be added to the bottom of the list.

   1. Note: In order for the New button to be enabled, the Additional Fields row must not display. See the Additional Fields Row for more information.

      Open

      

       

3. Click the Field drop-down and select a field.

   1. The drop-down list populates with the full Stratus.Field.x or Stratus.Package.x.

      Open

      

       

   2. After changes are saved and the dialog reopened, only the name will display. Note: The Field name presented to package creators is editable.

      Open

      

       

      1. If the Field included a Display Name like it did in this example, then the Field Display Name will be used. Otherwise, the Name will be used.

         Open

         

          

4. Configure the field as needed (e.g., Required, Default value, and/or Hide).

5. When done click Save and Close.

Copy from (Fields)

After opening a Package Category, administrators can copy all fields from an existing configured Package Category into the current one. Copied fields retain their sequence, required status, default values, and visibility settings. See the Add Field section to add individual fields to the Package Category.

To copy all fields from one Package Category into another Package Category:

1. Open the target Package Category.

2. Click the Copy from dropdown. Note: Package Categories that include the "Additional Fields" legacy row will not display in this dropdown.

   Open

   

    

3. Select the Package Category that contains the fields, field sequence, required status, default values, and visibility settings to be copied.

   1. If the selected Package Category includes the "Additional Fields" legacy row, then the legacy "Additional Fields" row will be replaced with the copied field configuration.

   2. If the selected Package Category does not include the "Additional Fields" legacy row, then the Category has already been configured. As a result, the following confirmation will display warning that all existing Package Creation Settings for the selected Category will be replaced.
      Click OK to continue or Cancel to stop the copy field process.

      Open

      

       

4. The Configuration copied successfully message will display.

5. Click Save and Close to save the new field settings or click Discard Changes and Close to cancel those changes.

Field Name

Field names for Stratus.Field.x or Stratus.Package.x fields added to the Package Creation Settings can be edited.

1. After a Field is added to the Package Creation Settings dialog, it displays the default Name or Display Name. In this example, Root Pass is the Field’s Display Name.

   Open

   

    

2. Click the link. The Display Name text displays.

   Open

   

3. Edit the name.

   Open

   

4. Click anywhere on in the dialog. The name will update.

   Open

   

    

5. Click the link again. Edit the name as needed.

   Open

   
   Open

   

    

6. Alternatively, delete the name. The Display name text will display again. Click anywhere in the dialog and the original default Field name (e.g., Root Pass) will display.

   Open

   

Field Order

1. Fields can be reordered by clicking and dragging the row to a new position. Fields display in package creation dialogs according to this configuration.

Field Required

1. Checked - When checked, a value must be entered in the package creation dialog either by the package creator or by the configured Default value.

2. Unchecked - When unchecked, entering a value during the package creation process is optional. Default values, if configured, display in the package creation dialog, after package creation, or at both stages.

3. Checked and Disabled - When a field is Checked and Disabled (e.g., Name) it means the field is required by Stratus.

Field Default

1. Value included - When a value is entered, it automatically populates in the new package dialog.

   1. Hide - If Hide is checked, the Field is removed from the the package creation dialog. After package creation, the field becomes editable in Packages > Properties or, for fields like Division, in the package's tracking section and becomes editable at that point.

   2. Value not included - When a value is not included the new package will not automatically populate with a value.

      1. Hide - If Hide is checked, the Field is removed from the the package creation dialog. After package creation, the field becomes editable in Packages > Properties or, for fields like Division, in the package's tracking section.

Field Hide

1. Checked - When checked, the Field is removed from the the package creation dialog. After package creation, the field becomes editable in Packages > Properties or, for fields like Division, in the package's tracking section.

2. Unchecked - When unchecked, the Field will display in the package creation dialog. After package creation, the field becomes editable in Packages > Properties or, for fields like Division, in the package's tracking section.

3. Unchecked and Disabled - When a field is Unchecked and Disabled (e.g., Name) it means that is a Stratus required field.

Field Delete

1. Delete - When the Delete icon displays, the field can be deleted and not display. Clicking the delete button the field will not display in the package creation dialog under Packages > Properties.

2. Delete disabled - When the Delete icon is disabled it means that is a Stratus required field.

   Open

   

Special Fields

Additional Fields Row

The Additional Fields row needs to be deleted (if it exists) in order to add any new fields to the package creation dialog. The Additional Fields row is a placeholder for certain Legacy Package Creation Report configurations that have been removed from Stratus.

1. If the Additional Fields row displays it will look like the following:

   1. Delete Additional Fields - The message “Delete Additional Fields row to add new fields. NOTE: The Additional Fields row cannot be re-added” displays at the top.

   2. New - The New button is disabled until the Additional Fields row is deleted.

   3. Additional Fields (Row) - The Additional Fields row displays. The hover text notes: “This row indicates that all custom fields are available during package creation. Once deleted, this cannot be re-added.”

      Open

      

       

2. Review Additional Fields - For any Package Category that contains an Additional Fields row the company should review those additional fields during Package Creation using either of these options:

   1. Packages > Dashboard > New Package > Select Category > New Package dialog.

   2. Models > Viewer > Actions > Packages > New > Select Category > the New Package dialog.

3. If the Package Creation fields are not exactly what is needed, required, and in the correct display order, the Additional Fields row needs to be deleted and the list of Package Creation fields rebuilt.

4. Delete the Additional Fields row - Delete the Additional Fields row by clicking the Delete button.

   1. Note: The hover text notes that “This row indicates that custom fields that matched the "Empty" Package Creation Report rules (below), are available during package creation. Once deleted, this cannot be re-added.”

   2. Note: It should also be noted once deleted any Stratus.Field.x or Stratus.Package.x field can be added to the Package Creation Settings for the Package Category.

5. Once the Additional Fields row has been deleted, see the Package Creation Settings section to better control the package creation process!

Add Assemblies and Parts

The Add Assemblies and Parts option applies exclusively to packages created using the New Package button on the Package Dashboard. This option enables package creators to include existing assemblies and parts through Filter and Area drop-downs. Without it, the New Package dialog creates only empty placeholder packages, as it cannot add parts or assemblies from a Viewer.

To add the Add Assemblies and Parts option to a Package Category if it is not already added: