develop — NOTE: This version of the CDD Writer’s Guide is based upon the instructions outlined in the CJCSI 3170.01G, Joint Capabilities Integration and Development System,1 Mar 09, the online Manual for the Operation of the Joint Capabilities Integration and ...

Downloaded from https://www.everyspec.com http://www.uidsolutions.com/milstd130.aspx requires that all XXXXXXXX capability 680 qualifying components, to include legacy components that transition through organic depots, 681 must be marked with a UII in the form of a machine readable 2D Data Matrix, the contents of 682 which will be encoded in the syntax of ISO/IEC 15434 and the semantics of ISO/IEC 15418 or 683 the Air Transport Association (ATA) Common Support Data Dictionary (CSDD). All 2D Data 684 Matrix bar codes must meet the verification standards for mark quality as established in ISO 685 15415 and SAE AS9132. 686 687 15. Other System Attributes.

This should be considered an “a la carte” menu. Only choose 688 those areas where you have something to say . Do not use the subparagraph heading followed by 689 NA. 690 691 a. Address attributes that tend to be design, cost, and risk drivers, including environment, safety 692 and occupational health, human systems integration, embedded instrumentation, electronic attack, 693 information protection standards, information assurance, and wartime reserve mode requirements. 694 695 b.

Address natural environmental factors (such as climatic, terrain, and oceanographic factors); 696 and unplanned stimuli (such as fast cook-off, slow cook-off, bullet impact, fragment impact, 697 sympathetic detonation, and shape charge jet). 698 699 c. Define the expected mission capability (e.g., full, percent degraded) in the various 700 environments. Include applicable safety parameters, such as those related to system, nuclear, 701 explosive, and flight safety. 702 703 d. Identify physical and operational security needs. 704 705 e. When appropriate, identify the weather, oceanographic and astro-geophysical support needs 706 throughout the program’s expected life cycle. 707 708 f.

Include data accuracy and forecast needs. 709 710 g. For intelligence, surveillance, and reconnaissance platforms, address information protection 711 standards. 712 h. Describe the non-information technology/national security system capabilities required for 714 allied and coalition operations, identify the potentially applicable US-ratified international 715 standardization agreements, and provide an initial indication of which ones will be incorporated in the 716 system requirements. (References DODD 8320.2, Data Sharing in a Net-Centric Department of 717 713 Defense available at:

http://www.dtic.mil/whs/directives/corres/pdf/832002p.pdf and DODD 2010.6, 718 Material Interoperability with Allies and Coalition Partners 720 . 719 i. Address conventional and initial nuclear weapons effects and CBRN survivability In the event 721 the mission requires CBRN survivability, consider elevating this attribute to be a KPP. 722 723 j. The following statements are examples only and information provided should reflect the 724 attributes of the specific system addressed in the CDD. Consider the following areas : 725 20