| | Joint Deployable Intelligence Support System (JDISS) |
| | Primary Purpose | JDISS is responsible for providing three classes |
| | of Information Technology (IT) products: (1) |
| | accredited software baselines, (2) optional |
| | corporate services, and (3) remote and on-site |
| | support functions. The fully interoperable set |
| | of JDISS products work together to meet the |
| | mission requirements of US Intelligence Community |
| | (IC) producers and their US and allied customer |
| | organizations. Through JDISS, the supported IC |
| | producers and consumers achieve full connectivity |
| | with standards-based, community IT |
| | architectures. JDISS provides access to imagery, |
| | finished intelligence products, and assists in |
| | putting together the order of battle. |
| | Sub-Functions | JDISS products and services, allow DoD, Joint, |
| | National and Coalition users to access databases |
| | across the Intelligence Community (IC). With this |
| | connectivity, they gain access to critical |
| | Intelligence Mission Applications (IMA's), |
| | databases, and products. JDISS products perform |
| | their critical mission support functions by |
| | providing secure and reliable access to the |
| | applications, databases, and products that |
| | facilitate intelligence planning and direction, |
| | collection management, processing and |
| | exploitation, production, and integration and |
| | dissemination. |
| | Equipment Requirements | IBM compatible Pentium II 450 Mhz, 128 MB Ram, |
| | and 9 GB removable hard drive for desktop |
| | applications. |
| | Connectivity Requirements | SCI systems require access to JWICS; GENSER |
| | (Secret) systems require access to SIPRNET. |
| | Crypto Requirements | SCI systems on JWICS require no additional |
| | encryption. GENSER (Secret) systems accessing |
| | SIPRNET may use STU-III or other accredited |
| | encryption methods. |
| | Normal Locations | All major Unified Commands, Joint Commands, DoD, |
| | Component Commands and MSCs, National |
| | intelligence community, NATO and Coalition |
| | partners. |
| | Information Managed | Users are able to utilize JDISS to do |
| | Intelligence Collection Management, Signals |
| | Intelligence, Human Intelligence, Imagery |
| | Intelligence, Measurement and Signature |
| | Intelligence, and Electronic Intelligence. |
| | Products Created | JDISS does not create anything. It allows access |
| | to finished intelligence products and provides |
| | the tools to customize intelligence products |
| | "tailored" for unit specific requirements, |
| | utilization and dissemination. |
| | Lead Service/Contractor | Joint Program Office. Staffed by all service |
| | components. Various support contractors support |
| | the program. |
| | Current Fielding Status | JDISS is a perpetual acquisition program. The |
| | JPO is continually improving the system and |
| | services provided to customers. |
| Known Problems | Accessibility is restricted to the connectivity |
| and crypto requirements. No unclassified access. |
| DIICOE Compliance Rating | JDISS Stand Alone Workstations Level 5. |
| Portions of JDISS That Are Segments of GCCS, |
| GCCS-M, TBMCS, Etc. Level 7. |
| JDISS 4.4(2QFY02) Will Be Level 7 for Both NT and |
| Solaris. |
| Point of Contact | LCdr Bernie Stansbury, JDISS Deputy Program |
| Manager, COMM (301) 669-5961 DSN 659-5961, EMAIL |
| <bstansbury@mcic.navy.mil> |
| Updated by | Capt William Shannon, USMC, CCSC-01 |
|
NEWSLETTER
|
| Join the GlobalSecurity.org mailing list |
|
|
|
