2.5.3.3. For each CR, specify the required operational attributes with appropriate quantitative parameters and metrics, e.g., outcomes, time, distance, effect (including scale), obstacles to be overcome, supportability, etc. See Annex A to Appendix B of Enclosure C to the manual for examples of operational attributes.

2.5.3.3.1. Indicate the initial objective value for each operational attribute to provide a discrete value that satisfies the operational need(s) for the capability. This will serve as the starting point for analysis supporting CR trade-offs above and below the initial objective value. In the narrative portion of the requirement, describe the operational implications that drive the value to be proposed at the specified level. Consider the effects of cybersecurity and any required additional support needed from the IC in determining the initial objective values.

2.5.3.3.1.1. Initial objective values are the values necessary to achieve mission objectives with moderate operational risk. The narrative should explain why the CRs are essential to the Sponsor in order to achieve assigned goals and objectives. Include assessment of operational implications - increased or decreased operational risks - which may be a factor as CRs are traded up or down during follow-on analysis and development efforts.

2.5.3.3.1.2. Values listed as To Be Determined (TBD), those specified only as a ratio relative to the value of a legacy capability solution, or operational attributes without quantifiable measures, are not allowed. In such cases, the Sponsor is not ready to document CRs in a SW-ICD and must perform additional analysis based on the applicable Service and Joint Concepts or CONOPS before finalizing the SW-ICD.