Главная Случайная страница


Полезное:

Как сделать разговор полезным и приятным Как сделать объемную звезду своими руками Как сделать то, что делать не хочется? Как сделать погремушку Как сделать так чтобы женщины сами знакомились с вами Как сделать идею коммерческой Как сделать хорошую растяжку ног? Как сделать наш разум здоровым? Как сделать, чтобы люди обманывали меньше Вопрос 4. Как сделать так, чтобы вас уважали и ценили? Как сделать лучше себе и другим людям Как сделать свидание интересным?


Категории:

АрхитектураАстрономияБиологияГеографияГеологияИнформатикаИскусствоИсторияКулинарияКультураМаркетингМатематикаМедицинаМенеджментОхрана трудаПравоПроизводствоПсихологияРелигияСоциологияСпортТехникаФизикаФилософияХимияЭкологияЭкономикаЭлектроника






D-2. General Guidelines





 

a. A CRD should serve to implement the MNS and layout a proposed solution set (DOTML-P & F) for complex, multiple materiel systems.

 

b. Finally, CRDs are useful when new concepts need 'exposure' opportunities against an array of inter-related deficiencies documented in the MNS (s).

 

D-3. Applicability. The requirements identified for a CRD apply to any DoD component involved in identifying and further articulating requirements for all MNS and ORDs that fall under the CRD.

 

D-4. CRD Identification. CRD initiation is through SOCREB/CDB direction. A USSOCOM Center, Component Command, or TSOC may recommend initiation of a CRD to the SOCREB/CDB during MNS validation and approval or initiation of a CRD may be directed to USSOCOM as an output from the Joint staffing process.

 

-- Component Commands. Component Commands may develop CRDs to manage a unique mission area. Prior to the CRD definition phase the component will forward a memorandum to the SOOP-RV stating the title, mission area, and timeline of the proposed CRD (this will minimize the duplication and undesirable overlap if current CRDs exist for the mission area).

 

D-5. CRD Documentation Phase. The CRD format is found in CJCSI 3170.01A. The CRD lead in coordination with the appropriate Services, CINCs, and DoD agencies, will develop the proposed FoS/SoS capabilities. The CRD will include a description of the operational capability, threat, shortcomings of existing systems, and capabilities required for the family of systems.

 

a. Information Exchange Requirements (IER). The warfighter also needs to identify the top level essential interface requirements for information exchange needed to support the CRD FoS/SoS. IERs identify the elements of warfighter information used in support of a particular activity and between any two activities.



IERs are to be used as the primary basis and measure for FoS/SoS interoperability in defining Interoperability KPP threshold (T) and objective (O) requirements for ORD and CRD. The requirements should reflect both the information needs necessary to satisfy the system(s) under consideration and the information this new capability can provide to enhance fielded systems.

 

 
 

b. Interoperability. Joint Pub 1-02 definition for Interoperability defines it as the ability of systems, units, or forces to provide services to and accept services from other systems, units, or forces and to use the services so exchanged to enable them to operate effectively together. Even though there are many facets of interoperability (e.g., fuel, ammunition, transportation, communications) that need to be identified in the CRD the focus for the interoperability CRD KPP will be the information exchange and level of interoperability for the CRD systems information needs. The CRD IERs and Interoperability KPP will be the CRD lead guidance for future ORD C4ISR development and issues to be addressed in legacy systems. The IERs are one product that is required to support development of the C4ISR operational architecture for the CRD mission area and the continued evolution of the Joint C4ISR Operational Architecture (JOA). The development of the information exchange requirements should cover both the communication requirements for command and control of the CRD systems and the level of integration for cross system operations. Information Assurance (IA) is required for all USSOCOM systems that are used to enter process, store, display, or transmit DoD information regardless of classification or sensitivity. To assure balance or risk and gains, IA requirements must be co-developed and co-evolved with those for Information Interoperability.

 

Date: 2015-08-06; view: 312; Нарушение авторских прав; Помощь в написании работы --> СЮДА...



mydocx.ru - 2015-2024 year. (0.007 sec.) Все материалы представленные на сайте исключительно с целью ознакомления читателями и не преследуют коммерческих целей или нарушение авторских прав - Пожаловаться на публикацию