Configuration management is a great tool to manage change in documentation, hardware, software, firmware, measurements and many more. Change is expected to have an initial state and next state. The indication of this vital state in a series of various changes is very important. Identifying these states in the revision history in configuration item is the main objective of baseline identification.
Normally, these vital states are the ones that receive an official approval status, sometimes implicitly and explicitly. The approval status can be indicated separately and individually, when the marking is identified, or signified simply by relationship or association to a particular baseline. However, this approval or authorization status is known publicly. Hence, the baseline may also be marked and indicate an approved configuration item. On the other hand, the configuration in a project may also involve more than one baseline. This includes the metrics and the status of the configuration. A baseline may focus on a specific baseline. Examples of it include the following: 1. Allocated Baseline: these are state of work items and products when conditions and requirements are approved. 2. Functional Baseline: this is where the initial specifications are established. 3. Product Baseline: this baseline holds the releasable contents of the item/product. Baselines may also be created to simply imply the progress of work through time. In the development of implementing configuration management and configuration items may be baselined to determine a particular status to interested parties. With this, the baseline work may need particular changes to work products to make sure it agrees with the baseline reference.