The change manager should update the change item with pertinent data
      before it leaves the 
      Classification state. This ensures that the full
      impact of the RFC is taken into account when the impact analysis is initially
      conducted.
 
    Note: Data can be changed as needed throughout the process to adjust the
      impact analysis results. 
    
 
    The impact analysis process involves the following steps:
 
     
      - Associate CIs with the change item. The 
        Primary CI field stores CIs directly acted upon
        by the change request; the 
        Affected CIs field stores CIs that could be
        impacted by the change request. This step can be performed when the RFC is
        submitted or classified, and then adjusted prior to the impact analysis. 
      
 
 
      - Schedule the change by selecting an 
        Implementation Start Date and 
        Implementation End Date on the 
        Implementation tab. 
      
 
 
      - Generate the 
        Impact Analysis Results
        by clicking the 
        Impact Analysis tab. 
      
 
 
      - Review the results. If there are warning icons in the results, rule
        out potential technical problems before proceeding. 
      
 
 
      - Approve the RFC by clicking the 
        Approve button. 
      
 
 
      - Make an initial evaluation of the impact by selecting an 
        Impact Assessment value on the 
        Impact Analysis tab of the Approve transition
        form. 
      
 
 
      - At this point, impact analysis routing is performed. If the RFC does
        not meet the approval criteria described above, it moves to the 
        CAB Review/Planning state so its impact can be
        formally reviewed. Otherwise, it moves to the 
        Approved Changes state. 
        
Note: Standard changes normally skip the 
          CAB Review/Planning state, but if they do not
          meet the approval criteria described above, they are routed to this state
          anyway. 
        
 
       
 
      - Make adjustments and then regenerate the impact analysis to see the
        new results. For example, you can try to change the implementation dates to
        reduce the impact to an acceptable level. 
      
 
 
      - If the impact still does not meet the approval criteria, do one of
        the following: 
        
 
          - Approve the RFC, and on the 
            Impact Analysis tab of the Approve
            transition form, change the 
            Impact Assessment value to 
            Investigated but determined insignificant or
            
            Investigated, no action required. 
          
 
 
          - Keep the RFC in the 
            CAB Review/Planning state by selecting one
            of the other 
            Impact Assessment options. 
          
 
 
        
 
       
 
    
 
    Use the 
      Changes in Range (Impact Analysis) report to see the change items
      with conflicting implementation dates (that is, implementation dates that are
      in the same range). You are prompted to provide query parameters based on
      implementation dates and the item ID before running this report.
 
    CAUTION:
Do not modify this report. 
    
 
   
 
Copyright © 2012–2015 Serena Software, Inc. All rights reserved.