Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Task Definitions are process tasks. You can make them as detailed or broad as you like. Task Definitions are required to configure a Task Workflows. A Task Definition can also be used to make Task Workflows more granular by appying status changes at the task level to the Assembly or PackageA Task Definition is the recommended method to generate work package task items.
Warning: Task Definitions and Workflows are an advanced STRATUS feature and are disabled by default. We highly recommend no matter how much experience you have in STRATUS previously that you seek formal training. Contact the STRATUS Service Desk for more information.
Time Saving Note: The STRATUS Customer Success Team has configured and can transfer to your company database Filters, Reports, Task Definitions, Task Workflows, Task Categories, Cost Categories, Cost Types, Tracking Statuses and other Admin configurations. See the STRATUS 07/18/2019 Implementation Webinar - GTP Pre-configured Spool Templates, Reports, and Filters to watch an introduction video, or, contact the STRATUS Service Desk for more information. Screen shots below are taken from the Customer Success Team's configuration.
* See the Task Workflow Examples article for more information.
Transition from Task Workflows to Task Definitions
Note: If your company has not used Task Workflows, skip to the Configure Task Definitions section.
By default, Task Workflows are used to generate work package task items. Customers are encouraged to transition their Task workflows, which still work, to the Task Definitions workflow.
To disable a Task Workflow:
- Change the Initiated by Tracking Status setting associated with the Task Workflow to Manually Initiated.
Image Added - Task Definitions and Task Workflows are diabled by default under Admin > Company > Settings. Check either (preferable) or both to generate tasks.
Image Added - Alternatively, Task Definitions and Task Workflows can be managed at the project level.
Image Added
Table of Contents | ||
---|---|---|
|
Configure Task Definitions
Task Definitions are extensions of Tracking Statuses.
- Whereas Tracking Statuses capture major milestones within your workflow and can be visually overplayed in the Models Viewer, Task Definitions enable you to automate your tracking status changes at granular checkpoints.
- Task Definitions let you track Shop Productivity and time stamping by person, station, or activity.
- A Task Definition combines a filter, a category, and item type to apply a tracking status when tasks are started and completed.
- A Task Definition can appyl status changes to the Assembly or Package.
- A Task Definition can be triggered manually or automatically by a tracking status change.
A Task Definition includes the following:
Image RemovedImage Added
- Sequence – Implies dependencies between tasks and is used for precedence ordering of tasks.
- Name (Required) - The name of the Task Definition. Tip: Use a standardized naming convention that uses a prefix so that the Task Definitions sort in a logical way. The Name is used to select tasks on the Task Workflows page in the Taks Sequence column.
- Description (Required) - The description can be the same or similar to the Name and is only visible on the Task Definitions page.
- Image - A task image, if added, will display wherever the task displays. If an image is not added to the task, then the Name will be used. One advantage to using an image is that task images can be sized the same giving the list of tasks a neat look to the page.
- Upload - Browse to upload the image file from your computer. The image will be used instead of the Name if it is uploaded.
- Assign to (Required) – Is the task created for a Part or Assembly.
- Apply using Filters (Optional) – Select one or more Filters to determine which Parts or Assemblies should get this task. See the Filters (Admin) article for more information.
- Task per Filter – Option to generate separate tasks for each Part Filter that passes. When checked, a separate task for each filter that passes will be created. When unchecked, a single task will be created when any of the part filters pass.
- Example – If you have a cut task and have a filter for copper straight pipe and a filter for steel pipe, you can create one task if either filter passes, or a task for each filter that passes
- Is Join – Is the task joining multiple parts together, like a weld. It Implies dependencies on tasks from connected parts.
- Apply to Package Category – When a Package Category is selected, a task will only be created for packages in the selected package category. See the Package Category (Admin) article for more information.
- Initiated by Package Tracking Status – When a Package’s Tracking Status is updated to the selected tracking status, then tasks get created. By default, tasks are Manually Initiated.
- Auto Complete (Required) – When checked (default), predecessor tasks will be automatically completed with tasks with higher sequence number for same part are completed. When unchecked, tasks will not be automatically completed and will require manual processing.
- Task Category (Required) - Configure Task Categories before Task Definitions. See the Task Categories article for more information. Below are some examples:
- Cost Category (Required) - Configure Cost Categories before Task Definitions. See the Cost Categories article for more information. Below are some examples:
- Cost Type - See the Cost Types article for more information. Below are some examples:
- Apply Tracking Status upon Completion - The tracking status that will be automatically applied when Apply Tracking Status to Assembly and/or Apply Tracking Status to Package is checked. See the Tracking Statuses article for more information. Below are some examples:
- Apply Tracking Status to Assembly
- When checked, after at least one task in an Assembly has been completed for the associated Task Definition, the tracking status set in the Apply Tracking Status column will be automatically applied to the Assembly.
- When unchecked, no tracking status will be applied to the assembly.
- Apply Tracking Status to Package
- When checked, after at least one task in a Package has been completed for the associated Task Definition, the tracking status set in the Apply Tracking Status column will be automatically applied to the Package.
- When unchecked, no tracking status will be applied to the package.
- Bypass (Update) Tracking Status Dialog
- When checked, after each task is completed for the associated Task Definition, the Update Tracking Status dialog will not display.
- When unchecked, after each task is completed for the associated Task Definition, the Update Tracking Status dialog will display if the Apply Tracking Status value is something other than “No Change”.
- Note: The Update Tracking Status dialog is the only dialog where hours can be entered while work is being done.
- Unit of Measure (Optional) – The Unit of Measure drop-down displays the list of Fields. See the Field (Admin) article for more information. For each task, a Field can be selected and used as the Unit of Measure metric for the task (e.g. diameter inches for weld task, or weight for sheet metal task, or length for pipe task).
- Velocity (Units per Day per Station) (Optional) – The Velocity is used for capacity planning and is a numeric value specifying the expected rate of task completion.
- Report (Optional) – The Report setting for each task generates helpful data for describing task on the task card. See the Report (Admin) article for more information.
- Example – Include C1, C2, Diameter, and Service information on Kanban task card.
Image Added
- Example – Include C1, C2, Diameter, and Service information on Kanban task card.
- Color (Required) – Select a color for the Task Defintion.
- Delete - Delete the Task Definition. Deleting the Task Definition will delete it from Task Workflows.
Example: Task Definitions and Task Workflows
See the Task Definitions and Task Workflows example on the Task Workflow Examples page- .