(a) As joint concepts and integrated architectures are developed, straight-forward CRDs that are a clear statement of the military task that must be accomplished will continue to induce the development of interoperable capabilities by describing overarching thresholds/goals and standards in functional areas, especially where an FoS or SoS approach is required. In general, the existence of an approved integrated architecture will obviate the need for a CRD. There may be some instances where CRDs are developed at JROC direction to represent specific, clearly stated tasks (see subparagraph 5a(4)(d) below). Integrated architecture products must be traceable to the pertinent CRD and its KPPs.
(b) The JROC will assign "CRD lead" responsibility to an FCB, a JWCA team, or an appropriate DOD Component. The CRD lead will ensure that the intent of JROC-approved CRDs is captured during the development of the integrated architectures. When an integrated architecture is presented to the JROC, CRD leads will propose retirement of appropriate CRDs that are superseded by the approved integrated architecture.
(c) If a conflict arises between a CDD/CPD satisfying attributes/ KPPs from multiple CRDs or the Department's overall strategy, the sponsor, in collaboration with applicable CRD leads, will prioritize CRD attributes/KPPs for a CDD/CPD to achieve appropriate FoS/SoS integration/capability.
(d) New CRDs will be developed only as the result of
specific JROC direction. Sponsors will not expend resources or efforts
developing a CRD without the written concurrence of the JROC. Updates to
existing CRDs may be initiated by the CRD lead. The CRD is described in
detail in reference