anchor.diff:  
   12/2016 notes
    continuing confusion over late vs early retirement - clarify
  -
  - fix the double alphabet problem
   
   Version 2, 12/11/2015
   
  
positive.code: 
  The "romeo" system is also questionable. Have a look at it and discuss. What depends on it?
  
  On the other hand, the "pi" system has an aging asset base, technology products close to retirement, and is a well regarded revenue producing system with considerable heft and significant dependencies in column P. Its request should be fully supported. It would be in the bottom right quadrant. This is the money quadrant; systems that land here in general should get some love. Notice that there is an inconsistency between the technical team's opinion and the objective reality of the asset and technology base. This might need further investigation.
  
  The "zeta" system is well regarded technically, but has room for improvement in terms of business fit. It would be top left in the quadrant. Some re-evaluation of its mission might be appropriate. It is not clear why they would want significant enhancement dollars as both the asset base and the technology dependencies are current. Note that the SLAs adherence is poor; this might be why.
  
  
negative.code: * High SLA adherence (incidents)
  ** _Low would indicate low fitness_
  * Current assets & technology platforms
  ** _Older indicates low fitness. An earlier sunset date means the product is more outdated; again, lower fitness._
  * NPS from support teams & architects
  ** _High is good_
  * High/increasing customer/user satisfaction score
  