JDISS provides automated support for the following:
The core software for JDISS is:
JDISS can be utilized in any context which requires the connectivity and
interoperability with the intelligence systems.This product has been accepted as part of the GCCS suite of products.. This
means that the experts from the GCCS Executive Agent have created and evaluated
the quality and applicability of this product for use within the GCCS domain
for the Department of Defense.
Prior to 1991 military commands and services were pursuing a variety of initiatives to migrate from stovepipe mainframe-based national intelligence systems to COTS and more open systems environments. National intelligence systems had traditinoally been garrisoned, fixed mainframe-terminal architectures, with distant-end systems either teletypes or other mainframes. In the Air Force, USAFE replaced old OJ terminals with DEC 5000s, while EUCOM and others used Sun SPARCstations.
JDISS grew out of LANTDISS, a USLANTCOM (now ACOM) national intelligence workstation. In 1992 the gulf Operation Southern Watch LANTCOM deployed the Sun SPARC 1+ and 2 workstations running Word Perfect and Open Look, and connected either to DSNET 3 or using tactical low-speed comms. The goal was to bridge the gap between tactical and national intelligence systems. This LANTDISS supported chatter, e-mail, and ftp using over the Top Secret backbone, and reach back to national mainframes like the SAFE IDB and imagery servers using simple terminal emulators.
This first forray into open systems within the intelligence community was generally successful, and the initiative's name was changed JDISS as part of a successful marketing strategy
In June 1992 the DoDIIS first draft of the Client Server Environment (CSE) Specification was issued, to bring the commands, services, and agencies together though COTS and open systems to replace existing independent hardware and software which had resulted in non-interoperability. DIA identified the various components of the CSE and allocated responsibility for their implementation.
Various users were reluctant to embrace COTS purchases, given promised SASS savings. By 1993 there were a few hundred workstations configured as JDISS while EUCOM's number was in the 500+ range [even now DoDISS has more than 20,000 workstations world-wide, less than 2000 are JDISS].
JDISS 2.0 was integrated with GCCS as the "Intelligence segment" -- however, JDISS is not an intelligence system, it's an intelligence support system. It has no intelligence database, no strictly intelligence applications, no DoDIIS migration systems, no correlator, no map graphics, and no capability to process NRT intelligence. The JDISS 2.0 configuration is still a stove-pipe, designed to act alone with all the software loaded on each workstation, and not operable in concert with other local systems.
JDISS BASELINE SEGMENTS:
JDISS Account Group JDISS License Manager JDISS Security Segment JDISS Communications JDISS Utilities JDISS Documents IRC Chatter Client (DII COE)JDISS STANDARD SEGMENTS:
IXI X.Desktop Crosswind Synchronize Calandar Paragon ELT/1000 Paragon ImageXChangePix Paragon ELT/4000 Paragon Desktop Chatter Interleaf World View IXI Premier Motif IXI Premier Motif Maintenance Applix Word Applix Mail Applix Spreadsheet Netscape Adobe Acrobat ReaderOPTIONAL:
Vividata PostShop Level 1
|Y2K CORPORATE SERVICES LIST FOR JDISS VERSION 2.01.2|
|Adversary||7.3||SIGINT requires special access|
|Corporate Services Manager||1.0|
|DIEPS Demo Images||5.1|
|Ghostwire||1.2||SIGINT requires special access|
|JIDSS 5D CLIENT||188.8.131.52|
|JDISS INSTALLER PATCH 1|
|JDISS INSTALLER PATCH 2|
|JDISS NSA WWW||1.0||SIGINT requires special access|
|JOINT COLLABORATION environment||1.3|
|NETSCAPE COMMUNICATIOR (INT)||4.51|
|NETSCAPE COMMUNICATOR (US/CAN)||4.51|
|OILSTOCK||4.4.5||SIGINT requires special access|
|Optimized Raster Chart Analyzer||3.1|
|PC File Viewer||1.0|
|PERL PATCH||1 5.003|
|Sensor Harvest Browzer||2.0||SIGINT requires special access|