Skip to content

Jobs Overview

A job is a small to large project which has a usually either has a definite start date or a delivery date or both. All jobs can have a workflow which specifies what the steps or processes are required to complete the job.

Workflows

All jobs can have a workflow related to it. The workflow defines a set of related processes that a job needs to go through. When a workflow is associated with a job, tasks will automatically be created for each of the manual processes in the workflow. Thus a workflow can be used to quickly tempate a set of dependent steps to complete a job.

Since each process in a workflow can be configured to have a duration, the autogeneration of tasks will also automatically create an approximate schedule based on this information. This provides a very quick way to start up a job, especially which the job type is accurately defined in the workflow. For departments that have a large number of similar jobs coming through, a well defined workflow and approval process leads to efficiency.

Assets

There are two types of assets.

WIP Assets (short for Work In Progress) assets are those files that belong to the job as the the job is being completed. These files are checked into the a processes correspoding to where in the workflow the actaully work was done.

Shared Assets are finished assets produced by the job. These are files that have been deemed reusable and should be exposed to other job.s Other jobs can then search for these shared assets and use them in the new project.

Shared assets are not stored within the project, but rather an Asset Library contained with TACTIC | Project. This means these shared assets will still be available even though the job has been offlined.

This separate of data is extremely useful for managing the overall health of the file system.

Sub-Jobs

Sub-jobs are items contained within a Job that need to be completed to fulfill the Job. The encompassing Job, together with component Sub-jobs ultimately make up a full project. Similar to the job itself, each deliverable has a start and end date and are associated with a set of steps or Tasks that need to be assigned to different users in order to complete the Deliverable.

Completion could potentially mean creating a finished Asset. A different set of Tasks can be set for different Sub-jobs. Any set of tasks is referred to as a Workflow.

Understanding Sub-jobs

A simple example can be used to explain this. Let’s say a user manual needs to be completed for a Customer for one of your products. This user manual consists of many chapters describing setup and how to use your product, much like this documentation on TACTIC | Workflow. The Order that you would create is called “User Manual for Product X” for your Customer.

The Sub-jobs for “User Manual for Product X” could be each of the chapters of the manual, for example, Chapter 1: Introduction, Chapter 2: Getting Started, and so forth. Each one of these chapters would have a set of Tasks that users would have to do to finish writing the chapter. Maybe there was a Task to write a draft, another to add pictures and a final one to revise the content. Once these tasks are complete, the chapter for the manual would be ready to be compiled with the other chapters. Each of the other chapters would be completed in similar ways, until all Sub-jobs are completed, and ultimately fulfilling the Job so that the manual is ready to send to the Customer.

Apps

TODO