to be performed initially, will be

to be performed initially, will be addressed with Retrofit documentation (AVM or Work Orders), which is also part of the “As-To-Be-Built” Baseline.Some of these completed and upcoming changes will be captured by the Target Configuration ETR, as they are vital to the success of the testing phase. See section 0 for more details.5.2.3 CM Baselines ReleaseDuring the project or platform product life cycle the documents included in the CM baseline (refer to (*) Target System of records are listed and shall be used where available.Table 1 p18) are first released and then gradually increasing in scope and maturity in order to reach a full compliance with the source requirements. This “maturing” process is organized, paced and documented using Configuration Baseline releases. Every change from first release being controlled through the change process.The CM Baselines are structured in hierarchical order (Figure 5). As-Required feeds into As-Specified which feeds into As-Designed. They shall always be released in this order so as to ensure consistency between them.A CM Baseline release is an increment of the previous release plus all the changes that have been approved and incorporated for this new release.