Functions and tasks (i.e., composite tasks and discrete tasks) are components in a taxonomy used to describe the typical activities performed by TMOTs in North America. As illustrated in figure 1, a function is made up of composite tasks, and composite tasks are made up of discrete tasks.
Figure 1. Chart. Generic breakdown of functions into tasks.
Use the following four questions to determine whether an activity is a function, a composite task, or a discrete task.
A function (e.g., Provide Travel Information, Congestion Management) is a capability or ongoing activity that contributes to the accomplishment of the TMC’s mission. A function can be seen as an output or an achievement that the TMC accomplishes as a whole. Each function includes at least one composite task. The base functions contain from 1 to 21 composite tasks, with 4 or 5 composite tasks being a typical number.
Figure 2 provides a schematic representation of aspects of the "Provide Travel Information" function with some of the underlying composite tasks and discrete tasks. To determine whether an activity is a function or task, first consider whether the activity is a general capability of the TMC, or if it a specific activity performed by TMOTs. The TMC performs the function of "Provide Travel Information" as a system. This system may include video cameras and sensor equipment monitoring highway conditions, TMOTs monitoring information from the TMC equipment and receiving cellular phone calls from travelers, and TMOTs posting the information on a website and on VMSs. In contrast, a single TMOT may perform the discrete task "Receive diversion route information for traveler information update." That is, a TMOT is able to "Receive diversion route information for traveler information update," but does not have the capability to "Provide Travel Information" because the latter is a system-level activity.
Figure 2. Chart. Example breakdown of functions into tasks.
Also consider whether the activity is part of the TMC’s mission, or whether it includes a more specific objective with a verifiable outcome. Determining whether a TMC has successfully provided travel information is difficult because of the general nature of the activity. The TMC may have succeeded in some aspects of providing travel information and failed in others. For example, a TMOT may have successfully contacted media outlets for traveler information update and recorded all traveler information update, but failed to selectively keep record of traveler information requests.
Next, consider whether the activity is an ongoing activity performed by the TMC or an activity, possibly recurring, with a more defined timeframe. For example, the TMC continually performs the function of "Provide Travel Information." That is, "Provide Travel Information" is not completed in the sense that a TMOT may complete "Selectively keep record of traveler information request."
Finally, consider whether the activity is divisible into smaller, meaningful components. For example, the function "Provide Travel Information" is easily divisible into "Collect Traveler Information to be Posted" and "Update and Post Traveler Information." Each division represents another meaningful and useful activity of work. "Update and Post Traveler Information" can be further broken down into "Contact (receive automated info) from media outlets for traveler information update," "Record/note all traveler information update," and "Selectively keep record of traveler information request." These divisions are also meaningful and useful. Are these divisions further divisible? Dividing "Selectively keep record of traveler information request" into "open database program," "create new record," and "type in traveler information request" is neither meaningful nor useful. One way to determine whether a discrete task is meaningful is to consider whether it makes sense to ask a co-worker to complete the activity. For example, consider whether it makes sense to ask a co-worker to "record a travel information update" (yes), or to "provide travel information" (no, too macro), or to "open the database program" (no, too micro). Also consider whether the activity stands on its own or is really part of some larger category. "Provide Travel Information" is very general. The larger category of "Provide Information" is so general that it could be associated with just about any position and include an extremely large number of unrelated composite tasks (e.g., manager providing feedback to a subordinate, news anchor reporting a breaking story). In other words, "Provide Information" is too general to be meaningful or useful. The activity is a function because it is (1) a general capability of the TMC, (2) part of the general mission of the TMC without a verifiable outcome, (3) ongoing, and (4) divisible into two lower-order levels and not associated with a meaningful higher-order category.
Tasks are smaller, more distinct activities. There are two types of tasks: composite tasks and discrete tasks. A composite task is a set of one or more related discrete tasks that a TMOT performs to support a function. Consider whether "Collect Traveler Information to be Posted" is a function, a composite task, or a discrete task. Specific TMOTs "Collect Traveler Information to be Posted." The goal and verification of achieving the goal are inherent in the activity. That is, was the traveler information collected, or did the TMOT fail to collect the traveler information. "Collect Traveler Information to be Posted" has a defined timeframe starting with the identification of the traveler information and ending with the collection of the traveler information that will be posted. "Collect Traveler Information to be Posted" can be broken down into multiple lower-order steps (e.g., "Analyze sensor data for speeds and delays for traveler information update," "Receive automated incident information for traveler information update"). Next consider whether those lower-order categories can be further broken down. It is not meaningful or useful to divide "Analyze sensor data for speeds and delays for traveler information update" into "View computer screen," "Determine location," "Consider traffic speed," "Consider traffic speed in location," etc. Does "Analyze sensor data for speeds and delays for traveler information update" stand alone with its own action (respond) and purpose description (road hazards)? No, "Analyze sensor data for speeds and delays for traveler information update" is part of "Provide Travel Information." The activity appears to be a composite task because it (1) is performed by TMOTs, (2) includes a goal with a verifiable outcome, (3) has a defined start and end time, and (4) is divisible into one level of lower-order categories and is associated with one higher-order category.
As discussed above, composite tasks can be further broken down into the individual steps, called discrete tasks, that are taken to accomplish the composite task (e.g., "Record/note all traveler information," "Selectively keep record of traveler information request"). Discrete tasks are the basic meaningful elements of work performed by TMOTs. Consider whether "Record/note all traveler information" is a function, a composite task, or a discrete task. "Record/note all traveler information" is performed by specific TMOTs. Although "Record/note all traveler information" is a reoccurring task, it includes a specific goal with a verifiable outcome for each instance the task is performed. Either the traveler information was recorded or it was not recorded. Although a TMC may not perform the function "Provide Travel Information" at all times, it is not a recurring task. As part of the general mission of the TMC it does not make sense to consider "Provide Travel Information" to be completed. "Record/note all traveler information" clearly has an identifiable start and end time for each instance. The activity of "Record/note all traveler information" is a discrete task grouped into the higher-order composite task "Update and Post Traveler Information," which is grouped in the higher-order function "Provide Traveler Information." Attempts to further divide "Record/note all traveler information" create useless, meaningless divisions. In general, it would not make sense to ask a co-worker to "Sit at their computer," "Open a database program on their computer," "Create a new entry," etc. The activity appears to be a discrete task because it (1) is performed by specific TMOTs, (2) has a specific goal with a verifiable outcome, (3) has a defined start and end time, and (4) is not divisible into lower-order categories and is associated with two higher-order categories.
Return to Main Tutorials Page