United States Joint Forces Command Joint Concept Development and Experimentation (JCD&E) Interagency and Multinational Information Sharing Architecture and Solutions (IMISAS) Culture Gaps Review 8-9 December 2010 . Mr. Dick McCrillis, CTR TASC Corporation IMISAS Project Facilitator
Joint Concept Development and Experimentation (JCD&E)
Interagency and Multinational Information Sharing Architecture and Solutions (IMISAS)
Culture Gaps Review
8-9 December 2010
Mr. Dick McCrillis, CTR
IMISAS Project Facilitator
Joint Concept Development & Experimentation
1) Combatant Commands (COCOMs) require a validated unclassified information sharing (UIS) Operating Concept.
2) COCOMs require Tactics, Techniques, and Procedures (TTPs) to implement the UIS Operating Concept.
3) COCOMs require a uniform interpretation of policies.
4) COCOMs require policies which balance enclave security concerns with UIS policy intent.
5) COCOMs require standing UIS protocols and procedures for engagement with UIS enduring partners.
6) COCOMs require standing UIS protocol and procedure templates to support rapid integration with non-enduring and ad hoc mission partners.
7) COCOMs require a guidebook for cultural engagement with enduring UIS partners, particularly nongovernmental organizations (NGOs) and international organizations (IOs).
15) COCOMs require an automated cross-domain capability from existing Secret Internet Protocol Router Network (SIPRnet) and the Nonsecure Internet Protocol Router Network (NIPRnet) to the UIS portal to enable agile information sharing and collaboration.
16) COCOMs require a UIS portal capability that integrates/federates synchronous, asynchronous, and multi mode services, including language translation, display fusion, social media integration and collaboration services.
17) COCOMs require a UIS portal emphasizing open source software, enterprise business practices, and modularity which permits integration and federation of rapidly emerging social networks and IO/NGO enclave systems.
18) COCOMs require a UISC with sufficient interoperability at link, transport, network, and application layer.
19) COCOMs require a UISC that enables mobile terminal device users through synchronization services, geographic information system (GIS) integration, sufficient application support for minimal portal collaboration, and a connection interface facilitating low cost bulk provision of devices.
20) COCOMs require a UISC that accommodates through physical or procedural mechanisms, information exchange with non-IP networks such as high frequency (HF) packet or other data signaling protocols, radio voice nets, telephonic information, or face-to-face networks.
21) COCOMs require a Knowledge Management/Information Management (KM/IM) UIS portal structure that reduces learning/training requirements for intended users.
22) COCOMs require clear and simplified lines of authority for managing information sharing risk and adjudicating competing DoD guidance for information release.
23) COCOMs require procedural enablers to make UIS training more efficient and effective, accelerate user access to information, and empower KM/IM (i.e., document retention policy, metadata policy, library structure, document content and labeling standards, file and folder naming conventions, user friendliness, disaster recovery plan, prime source designation, access and control rules for information, help desk provisioning, action tracking, and version control).