Intro
		Configuration

ATS Overview

The [Action Tracking System (ATS)](http://www.eclipse.org/osee/documentation/overview/components.php#ats) is a tightly integrated change tracking system that manages changes throughout a product's lifecycle. ATS provides integrated change management to all OSEE applications through user customizable workflows.

Terms

• Actionable Item (AI) Item that can be impacted by an Action. AIs are what the user has to select from when creating an Action. Examples: Flight Box, Lab Computer, Code Subsystem.
• Team Workflow Definition Teams are the OSEE representation of the group of people expected to perform any work associated with the Action. They are related to the AIs that they are responsible for and are configured with Leads and Members to route the Actions and perform the work. A workflow represents and provides the steps the team will follow to perform the work. The workflow is configurable - the work steps and representation can be changed.
• Workflow Configuration State machine that shows the path the Team will follow to perform the work associated with the Action.
• Action Top level grouping object. An Action is written against any number of AIs. The Team Workflows are then created for each team configured to perform work for an AI.
• Team Workflow Instantiation of a Workflow Diagram needed to perform the work. Each team independently moves through their workflow state machine however ATS can be configured such that certain gates must be met from other Teams or outside events before a workflow can continue.
• Task Within states of a Team Workflow, smaller-light-weight Tasks can be created to further separate the work that needs to be completed for that state. Normally, the state can not continue until the Task is completed.
• Versions ATS has built in project/release planning. Versions are created to group Team Workflows (Actions) into Builds and Releases.

		Configuration