Task Management System
Task Management System (TMS) is a tool that manages the workflow of tasks as they are implemented in an application. TMS provides support for simple and complex business processes as well as integration with automation tools needed for change management execution and verification. The primary goal of the Task Management System (TMS) module is to provide a mechanism to support repeatable processes. The result is improved productivity, reduction in novice errors, and a clear way to define business processes.
The TMS module significantly enhances the capability of the task operation. In addition to the predecessor and successor relationship, TMS supports branching and multiple paths, along with data exchange between tasks.
TMS is used in BMC Change Management, BMC Service Desk, and in the Activity subsystem. It integrates with the Change and Configuration Management (CCM) solution through the Command Automation Interface (CAI).
In the BMC Change Management and BMC Service Desk applications, support staff can create tasks by using TMS directly. Additionally, administrators can create task templates and task group templates that can be used in change, release, and incident management. For problem management, problem analysts can create only ad-hoc tasks directly from TMS.
The following illustration shows the relationships between TMS and Change and Configuration Management.
Task Management System and Change and Configuration Management
Click the following figure to expand it.
Task Management System components
Task Management System consists of the following primary components:
Components | Description |
---|---|
Container objects | Manage all the related associations and flows of its children objects. During the definition stage, the container objects are task group templates. During the runtime stage, the container objects are task groups. |
Task templates | Allow you to create predefined templates for individual work items that you can reuse. |
Task group templates | Allow you to create predefined templates for collections of individual task templates. |
Associations | Define what task templates or task group templates are related to or grouped together under the task group template. |
Sequencing mechanism | Allows you to define associations and sequences with task group templates and task templates. This mechanism is used with basic task group templates. For more information about sequencing, see Sequencing mechanism. |
Flow mechanism | Allows you to qualify the dependencies between the associated task group templates and task templates. This mechanism is used with advanced task group templates. For more information about the flow mechanism, see Flow mechanism. |
Variable templates | Provide a structure that is used to facilitate the passing of information from task group and tasks to flows. These templates are used to create a variable pool for data exchange. |
Web services | The TMS_TaskInterface web service performs task queries, and updates operations, including relationships and work information. |
Task viewer | Allows you to easily see the sequence between tasks as task implementers work on their tasks. The task viewer provides visual context to understand tasks and their relationships to each other. It improves productivity and reduces errors because you now have a clearer understanding of the business process. |
Task assignment | Configures assignments for tasks, based on company, and product and operational categorization. |
Recommendation
BMC Configuration Management integration - Best practice templates are installed to integrate TMS and BMC Change Management with BMC Configuration Management. Many of these templates illustrate important task administration concepts.
TMS supports integration with external applications, primarily using the Command Automation Interface (CAI) module. TMS supports integration with the BMC Configuration Automation for Clients application through a launch mechanism.
Comments
Log in or register to comment.