- Content Managers
- A workflow is comprised of 4 hierarchy levels; Workflow→Process→Task→Step.
- Each level of a workflow presents a different degree of detail for the consumer.
- The Workflow and Process levels are typically high-level overviews
- The Tasks and Steps are more granular and go into step-by-step instructions.
- The definitions below will help to establish a collaborative environment for Content Managers and Authors.
A workflow is a collection of processes, tasks, and steps that define the deliverables, job roles, and detailed instructions required for repeatable projects or work performed. A workflow might take on the name of a specific Project Type, Product Name, Service Type, or Toolbox Name for housing a collection of related Processes. Workflows can be moved and copied between folders, but cannot be re-leveled.
A process is a collection of tasks that need to be completed in order to produce a specific deliverable, reach a certain milestone, or project transition point. The process itself clearly defines the type of deliverable and specifications that must be met upon completion of the tasks. An example of a Process might be Plan and Profile Sheets, a BIM Execution Plan, Survey Plat, 60% Submittal, etc. Processes can be moved and copied between workflows, but cannot be re-leveled.
Tasks are measurable activities that define what is to be accomplished en route to producing a specific deliverable. Tasks often depict a checklist and can be diagrammed in a process to occur in series, concurrently, or in a decision sequence. Task descriptions can be used to convey written instructions and include tool links to trigger technology features and external resources. Detailed and complex tasks can be broken out into individual steps to be executed in sequence. Tasks can be copied between processes, but cannot be re-leveled.
A step is the finite level of a workflow that provides detailed instructions on how to complete a task. Step descriptions can be used to convey written instructions and include tool links to trigger technology features and external resources. Steps are to be completed in sequence and can be renumbered to modify the sequence. Steps can be copied between tasks, but cannot be re-leveled.
Still Need Help?