Intelligence Systems

US Marine Corps
Command and Control Systems School
1999 COMMAND AND CONTROL APPLICATIONS
COMPENDIUM OF SYSTEMS

Advanced Combat Direction System (ACDS)

Advanced Field Artillery Tactical Data System (AFATDS)

Automatic Identification Technology (AIT)

AIRES (Advanced Imagery Reqs & Exploitation System) Life Extension (ALE)

Amphibious Assault Direction System (AN/KSQ-1)

Aerial Port Automated Command and Control System (APACCS)

Ammunition Prepositioning Planning System (APPS)

Afloat Planning System (APS)

Advanced Tactical Air Reconnaissance System (ATARS)

Asset Tracking, Logistics, and Supply System (ATLASS)

Command and Decision System - AEGIS (Airborne Early Warning Ground Integration Segment) Display System (C&D-ADS)

Command and Control Personal Computer (C2PC)

Computer Aided Embarkation System (CAEMS) Conventional Ammunition Integrated Management System (CAIMS)

Computer Aided Load Manifesting System (CALMS)

Consolidated Air Mobility Planning System (CAMPS)

Combat Cryptologic Support System (CCSS)

Cargo Movement Operations System (CMOS)

Collection Requirements Management Applications (CRMA)

Contingency Theater Automated Planning System (CTAPS)

Combat Terrain Information System (CTIS)

Defense Casualty Information Processing System (DCIPS)

Defense Message System (DMS)

Department of Defense Intelligence Information System (DODIIS)

Defense Red Switched Network (DRSN)

Digital Terrain Analysis System (DTAMS)

Global Command and Control System (GCCS)

Global Command and Control System-Maritime (GCCS-M)

Global Command and Control System-Army (GCCS-A)

Global Command Support System (GCSS)

Ground Mobile Forces (GMF) Network Planning Prototype (NETPLAN)

GCCS Status of Resources and Training System (GSORTS)

Global Transportation Network (GTN)

Intelligence Analysis System (IAS)

Integrated Computerized Deployment System (ICODES)

Improved Emergency Action Message Transmission System (IEMATS)

Initial Fire Support Automated System (IFSAS)

Integrated Marine Multi-Agent Command & Control System (IMMACCS)

Joint Collection Management Tools (JCMT)

Joint Defense Information Infrastructure Communications System-Deployed (JDIICS/D)

Joint Deployable Intelligence Support System (JDISS)

Joint Flow and Analysis System for Transportation (JFAST)

Joint Maritime Command Information System (JMCIS)

Joint Network Management System (JNMS)

Joint Operations Planning and Execution System (JOPES) Joint Service Imagery Processing System (JSIPS)

Joint Tactical Information Distribution System (JTIDS)

Joint Universal Lessons Learned (JULLS)

Joint Visually Integrated Display System (JVIDS)

Joint Worldwide Intelligence Communications System (JWICS)

Local Asset Management System (LAMS)

Logistics Management Information System (LMIS)

Logistics Automated Information System (LOGAIS)

Logistics Sustainment Analysis and Feasibility Estimator (LOGSAFE)

Marine Ammunition Accounting and Reporting System II (MAARS II)

Medical Augmentation Program (MAP)

Marine Corps Ammunition Requirements Management System (MCARMS)

Marine Corps Fire Support System (MCFSS)

Marine Combat Service Support Command and Control (MCSSC2)

Marine Corps Total Force System (MCTFS)

Migration Defense Intelligence Threat Data System (MDITDS)

Military Standard Transportation and Movement Procedures (MILSTAMP)

Multi-spectral Imagery Materials Exploitation System (MIMES)

Marine Corps Integrated Maintenance Management System (MIMMS)

Manpower Mobilization Assignment System (MMAS)

Marine Traffic Management System (MTMS)

Naval Aviation Logistics Command Management Information System (NALCOMIS)

Naval Modular Automated Communications System II (NAVMACS II)

Navy Integrated Environmental Support Subsystem (NITES 2000)

Navy Tactical Command Support System II (NTCSS II)

Port Control Command Center (PCCC)

Position Location Reporting System (PLRS)

Psychological Operations Automated System (POAS)

Retail Ordnance Logistics Management System (ROLMS)

Supported Activity Supply System (SASSY)

Strategic Sealift Analysis System (SEASTRAT)

Secondary Imagery Dissemination System (SIDS)

Special Operations Command, Research, and Threat Evaluation System (SOCRATES)

Systems Planning Engineering and Evaluation Device (SPEED)

Submarine Satellite Information Exchange Subsystem (SSIXS)

Shore Targeting Operational Support System (STOSS)

Shipboard Uniform Automated Data Processing System (SUADPS)

Tactical Digital Information Link-J/NATO LINK-16 (TADIL-J)

T-AVB Automated Load Planning System (TALPS) Tactical Aircraft Mission Planning System (TAMPS) Tactical Airborne Reconnaissance Pod System (TARPS & TARPS Digital Imaging DI) Theater Battle Management Core Systems (TBMCS) Transportation Coordinator's Automated Information for Movement System (TCAIMS)

Tactical Combat Operations (TCO)

Tactical Electronic Reconnaissance Processing and Evaluation System (TERPES)

Tactical Flag Command Center/Flag Data Display System (TFCC/FDDS)

Tactical Network Analysis and Planning System Plus (TNAPS+)

Tactical Reconnaissance Intelligence Exchange System (TRIXS)

Tactical Remote Sensor System (TRSS)

Tomahawk Weapons Control Sys (TWCS)

Unit Diary/Marine Integrated Personnel System (UD/MIPS)

War Reserve System (WRS)

 

 

 

Advanced Combat Direction System

(ACDS)

Primary Purpose: Integrates the ship's sensors, weapons, and intelligence sources to allow command and control of battle group tactical operations. It provides real-time consolidated and correlated tactical information within an individual ship or battle group. ACDS collects displays, evaluates and disseminates information on the constantly changing tactical air, surface, and subsurface environment. Used in conjunction with TADIL-J/LINK 16/JTIDS it manages significantly higher numbers of tracts in support of advanced electronic warfare using artificial intelligence features that continuously analyze the tactical situation providing heightened awareness to the crew.

Sub-Functions: Central repository for all tactically significant tracks for battle/force/battle group as well as the ship in which it resides. Consists of equipment, computer programs, and personnel engaged in collecting, correlating, displaying, and disseminating ship and force track information, evaluating track threat potential, assigning weapons, generating and disseminating force orders, monitoring individual and force engagements, and controlling aircraft.

Equipment Requirements: Data Processing Group: AN/UYK-43A(V) Computer set; RD-358(V)5/UYK or RD-358A(V)/UYK Digital Data Recorder/Reproducer; AN/USQ-69(V) Data Terminal Set: OJ-172(V) I/O Console and associated peripherals. Data Display Group: OJ-451(V)9/UYQ-21 Computer Display Console; OJ-535(V)2/UYQ-21(V) Display Control Console: UYQ-70 Display Console; IP-1357/UYQ-21(V) Digital Data Indicator; LS-653/654A/UYQ21 Console Intercommunications Units, Large Screen Display (LSD); and associated peripherals.

Connectivity Requirements: No Requirement for monitoring Own-ship operations. Communication and data link (LINK 11/14/16) required for monitoring force operations.

Crypto Requirements Encryption required for ship to ship data link.

Normal Locations: Installed on non-Aegis surface combatants.

Information Managed: Tactical air, surface, and subsurface environment. Connectivity to shore based support activities provides operational scenarios with a data library for operations programs.

Products Created: Data analysis and data reduction for operations programs and hardware configurations. The system also creates "picture" based upon software analysis for Detect, Control, and Engage (DCE) functions.

Lead Service/Contractor: US Navy and Raytheon Services, San Diego, Ca.

Current Fielding Status: Block 1 Phase began in FY 97 and completed initial operational deployments on USS WASP (LHD 1) in July 98 and USS DWIGHT D. EISENHOWER (CVN 69) in December 1998. Block 1 currently also installed on USS JOHN F. KENNEDY (CV 67) and to be installed on USS IWO JIMA (LHD 7) and USS NIMITZ (CVN 68).

Known Problems: ACDS Block 1 OPEVAL in February 1998 was unsuccessful and included discrepancies in HMI and Reliability, Maintainability and Availability (RM&A). The most recent program version has demonstrated improved RM&A.

DIICOE Compliance Rating: Not rated.

Point of Contact: CDR J. Heil, PEO (TSC) PMS 461E Phone (703) 602-2161 ext 102, FAX (703) 602-2400.

Updated by: Capt George A. Judd, USAF, CCSC-99.

 

Advanced Field Artillery Tactical Data System

(AFATDS)

Primary Purpose: Automated fire support command, control and coordination functions.

Sub-Functions: Tactical artillery fire direction, target management, fire support planning, fire mission processing, movement control, and artillery mission support.

Equipment Reqs: The Tactical Control Unit (TCU) contains a 1 GB hard disk drive, 144-208 MB RAM, internal/external LAN card, MOD containing optical disk with 650 MB capacity, CD-ROM drive with 600 MB capacity, 1.4MB floppy drive, UPS for 30 min back up, and 2 external Tactical Communications Interface Modules (TCIM) (each allowing for 2 digital nets). Also can be operated on LCU AN/GYK-37.

Connectivity Reqs: VHF and HF radio, STU-III 9600 Baud, UHF/SATCOM capable, JVMF BOM with Mil Std 188-220A protocol to communicate with TCO (uses OTH-Gold).

Crypto Reqs: Vinson family and KG-84.

Normal Locations: Battery Operations Centers, Artillery Fire Direction Centers at battalion level and higher, Fire Support Coordination Centers, Force Fires Coordination Center, Tactical Air Command Center, Direct Air Support Center, Rear Area Operations Center, and Supporting Arms Coordination Centers.

Information Managed: Fire plans, target lists, fire support coordination measures, maneuver control measures, enemy/friendly unit locations, firing unit and ammunition information (FireCaps, GURFs, etc.), meteorological and survey information, battle damage assessment, movement control, and commander’s fire support guidance.

Products Created: Target lists, fire plans, air support requests, order to fire.

Lead Service/Contractor: U. S. Army/Hughes Defense Communications.

Current Fielding Status: Begin fielding to I MEF in FY-99, complete USMC fielding in FY-02. Army fielding began in FY-96 and continues through FY-07.

Known Problems: Inability to directly contribute to Common Tactical Picture in real time.

DIICOE Compliance Rating: Level 6.

Point of Contact: Major Halsey, Marine Corps Systems Command, DSN: 278-2645 ext.2530.

Updated by: Capt Jeffrey H. Hauser, USMC, CCSC-99.

  

Automated Identification Technology

(AIT)

Primary Purpose: Obtain accurate information on status of assets that are in-storage, in-process, or in-transit. Suite of tools facilitating data transfer capture. Strength is ability to rapidly capture information and interface with Automatic Identification Systems with minimal human interaction.

Sub-Functions: Marking devices: Bar codes, magnetic stripes, memory cards, radio frequency identification (RF) tags, and magnetic storage media used for "tagging" individual items, multi-packs, equipment, pallets, or containers. Laser or RF interrogation devices (LOGMARS: Logistics Application Marking And Reading Symbols and MITLA: Micro Circuit Technology & Logistics Applications) provides information to be fed into PCs for updating and/or comparing records.

Equipment Requirements: Standard Suite: Printer, data collection device, reader, and accessories (e.g. batteries). Equipment must be bought through DOD contract (DAHC94-94-D-0003). Each service must contact two offices listed below to ensure equipment is compatible with other services. Tagging devices vary in size and amount of data they can hold. Interrogation devices are either hand-held or stationary. 42 terminal upgrades for Janus terminals available for use with Janus 2010 and 2020 model "C" or earlier. Model "D" units were shipped after August 1997 and are Y2K compliant.

Connectivity Requirements: Dependent upon specialization equipment purchased. PC connectivity requires the use of a RS232 cable or wireless hardware and software for data transfer.

Crypto Requirements: None.

Normal Locations: Warehouse/issue points. Anywhere with a need for tracking physical inventory.

Information Managed: On-hand quantities, equipment, sales, gains, and losses. Captures what is present then compares to what is stored in records on PC.

Products Created: Bar code labels, gain and losses transactions, shopping receipts, etc.

Lead Service/Contractors: Technical consultants (DSN) - USMC: Ricki Morton 426-0892/1073; USN: Frank Murray 430-7527; USAF: Mark Rebolet 787-4118/7181; USA: Susain Vickers PMAIT 656-4110.

Current Fielding Status: Everywhere. Not limited to logistics fields.

Known Problems: Hardware funding, training, and maintenance. Occasionally customers receive faulty labels.

DIICOE Compliance Rating: Not rated.

Point of Contact: (ALL DSN) USMC: Ricki Morton 426-0892/1073; USN: Frank Murray 430-7527; USAF: Mark Rebolet 787-4118; USA: Susain Vickers PMAIT 656-4110.

Internet: www.afmc.wpafb.af.mil/hq-afmc/lg/lso/loa (requires government server to access), http://www.peostamis.belvoir.army.mil/ait/home.htm.

Updated by: CPT James S. Clifford, USA, CCSC-99.

  

Advanced Imagery Requirements and Exploitation System (AIRES) Life Extension

(ALE)

ALE is scheduled to be replaced by NIMA’s National Exploitation System (NES) on/about 1 August 1999.

Primary Purpose: DoD system for imagery exploitation and reporting. ALE is DoD’s link to the National Imagery Community and is used primarily as an exploitation support tool by DoD analysts and managers. Retrieves and disseminates on-line imagery derived data to worldwide users.

Regs Management: Provides authorized users with the ability of validating nominated point targets (received either from RMS of DoD IIR reporting); and placing these items into the ALE database. Allows these new items to be sent to the Modernized Integrated Data Base (MIDB) for inclusion.

Equipment Regs: DIA mainframe host provides the indexing, profiling, and dissemination functions for all data received or generated by ALE to external systems via CAMP. Each user site has its own application servers containing the ALE software which allows interface w/the DIA host. Uses TCP/IP with DSNET 3.

Crypto Regs: Handled by DSNET 3/JWICS.

Normal Locations: SCI Facilities. DIA and external sites in DoD.

Information Managed: Imagery exploitation information.

Products Created: Authorized ALE users may generate either Imagery Interpretation Reports (IIRs) and/or Topic Reports on-line. These reports follow the EARS and NERCM formats. Other products that may be generated are: Imagery Analyst Memorandums (IAMs); exploitation resource accounting; and ad hoc responses to research queries (in either hardcopy or softcopy formats).

Current fielding Status: ALE #2.08 is the current version.

Known Problems: None Significant.

DIICOE Compliance Rating: Not rated.

Point of Contact: Mark J Skiba, DIA/SYI, (202) 231-5063/DSN 428-.

Updated by: Capt Todd V. Bottoms, USMC, CCSC-99.

 

Ammunition Logistics System II

(AMMO LOGS II)

Systems Status: System is no longer in use. It was phased out in 1998 and was replaced by ROLES.

Updated by: Capt Roy Delaney, USMC, CCSC-99.

  

Amphibious Assault Direction System

(AN/KSQ-1)

Primary Purpose: Provides CATF/CLF capability to launch, monitor, and control a surface amphibious assault from ranges up to 100 nautical miles.

Sub-Functions: Digital data communications system.

Equipment Reqs: Uses EPLRS/PLRS system integrated with GPS and GPS Integrated Unit(GPSIU). Any platform with GPS/GPSIU connected to PLRS BUU makes a dynamic reference point; the AN/KSQ-1 enhances EPLRS/PLRS master or net control station capabilities.

Connectivity Reqs: Requires EPLRS or PLRS.

Crypto Reqs: PLRS crypto KG-58.

Normal Locations: Amphibious ships (LCACs and LCUs). EPLRS/PLRS with GPSIU manpack units ashore and for AAVs.

Information Managed: Provides visual display and a map background to display position and location of LCAC and LCUs as well as other units with EPLRS/PLRS capability.

Products Created: None.

DIICOE Compliance Rating: Level 5.

Lead Service/Contractor: EPLRS/PLRS: USA and Raytheon; GPSIU: USA and SECHAN; AN/KSQ-1: USN in combination with GOTS/COTS.

Current Field Status: Currently fielded on six Amphibious Ready Groups with milestone III approval.

Known Problems: Ships without organic PLRS Master Stations have experienced some interface problems. This continues to be reduced with better GOTS/COTS upgrades.

DIICOE Compliance Rating: Not rated.

Internet: Not applicable.

Point of Contact: Program Manager (PMS377) Captain Gorski (703)602-8511.

Updated by: Capt Kenneth M. Lewton, USMC, CCSC-99.

 

Aerial Port Automated Command and Control System

(APACCS)

Primary Purpose: Subsystem of Global Air Transport Execution System (GATES); software program supporting command and control (C2) and port resource management.

Sub-functions:

C2: Maintains and coordinates sequence of events (SOE) tracking, monitoring, and input of desired aerial port data.

Port resource: Manages aerial port manpower and equipment resources.

Equipment Requirements: Local area network and workstations.

Connectivity Requirements: As an Air Force key Theater Battle Management (TBM) system, APACCS interfaces with Global Decision Support System (GDSS)

Crypto Requirements: None.

DII COE Compliance Rating: Not rated.

Normal Locations: All heavy airlift Air Force bases.

Information Managed: Aircraft SOE and Personnel/Equipment availability.

Products Created: Various management tools.

Lead Service/Contractor: USAF (Air Mobility Command).

Current Fielding Status: Fully deployed. APACCS functions has migrated to Global Air Transportation Execution System (GATES); formerly a subsystem of the Consolidated Aerial Port System II (CAPS II). GATES interfaces with GDSS.

Known Problems: No major problems.

Point of Contact: 1st Lt. Shean Ellars(USAF), DSN: 576-3288; Senior Airman Lantz, DSN: 576-3633, FAX: 576-6040.

Updated by: Capt Thomas Bajus, USMC, CCSC-99.

 

Ammunition Prepositioning Planning System (APPS)

(Time-Phased Force Deployment Data (TPFDD) Module)

Primary Purpose: Management of Class V(W) Ground Ammunition in support of contingency deployment and deliberate planning.

Sub-Functions: The Ammunition Prepositioning and Planning System (APPS) performs the following sustainment functions during deliberate planning or crisis action response at the FMF and at MARCORSYSCOM:

a. Accepts force flow information from MAGTF II or permits construction of forces from scratch.

b. Properly computes the Class V(W) time-phased requirement by allowing operator adjustments for non-TPFDDed information and time-phasing which accommodates employment of forces not just deployment of forces.

c. Sources that requirement from the Marine Ammunition Requirements Support Order (MARSO) or actual operational inventory.

d. Allows for sharing of MARSO sourcing among all deployed MEFs.

e. Forwards further sustainment requirements (operational shortfalls) to MARCORSYSCOM via SIPRNET.

f. Allows MARCORSYSCOM to source from retail locations directly from inventory extract out of MAARS II.

g. Constructs submittal to Single Manager for Conventional Ammunition (SMCA) for joint wholesale sourcing.

h. Converts operational, retail and wholesale sourcing into format which can be hand loaded into MAGTF II pending reprogramming of MAGTF II under MAGTF II, Version 4.2 to directly accept the data and build the TPFDD in an automated manner.

I. Analyzes the sourcing to compute the Logistics Supportability Analysis required for the Munitions Matrix in each plan.

j. Will receive data files from Marine Corps Ammunition Accounting and Reporting System (MAARS II), Marine Air-Ground Task Force-II/ Logistics Automated Information System (MAGTF II/LOGAIS), email, SIPRNET via diskette or similar media.

Equipment Requirements: Microcomputer, Pentium 166Mz (minimum), Windows 95 (32 bit operating system), minimum 80Mb available (120 preferred), minimum 32 MB RAM, one CD-ROM drive. If classified data is entered, computer must be suitable for handling classified data.

Connectivity Requirements: Direct connectivity is not required.

Crypto requirements: None.

Normal Locations: MARCORSYSCOM, Program Manager for Ammunition. USMC Ammunition Officer at MARFORLANT, MARFORPAC, MEFs. Marine Corps Detachment, U.S. Army Ordnance Missile and Munitions Center and School.

Information Managed: Retains AWR MARSO data, inventory data, compares requirement to available assets for operational support.

Products Created: Various Reports. Level 4 and Level 2 ULN detail. CIN worksheets.

Lead Service/Contractor: USMC/MKI Inc.

Current Fielding Status: Final delivery pending corrections of errors found during Beta Testing anticipated for late CY98 delivery.

Known Problems: MAGTF II, Version 4.2 was going to have a direct export/import link to APPS. Development of MAGTF II, Version 4.2 is delayed. Ad Hoc queries can provide the data to APPS. However, hand entry of the data developed in APPS (instead of direct automated entry) into MAGTF II is required.

DIICOE Compliance Rating: Not rated.

Point of Contact: Head, Plans Branch, PM for Ammunition, MARCORSYSCOM, GM13 Diane Smith, DSN: 426-0924.

Updated by: Capt Felice Miraglia, Italian Marines, CCSC-99.

 

Afloat Planning System

(APS)

Primary Purpose: Provide shipboard capability for planning, distributing, and employment support of TOMAHAWK Land Attack Missile (TLAM) missions. Provides a three dimensional representation of the target area and flight path, prepares precise aiming points. APS is the shipboard version of a shore-based Cruise Missile Support Activity (CMSA).

Sub-Functions: Mission planning, intelligence, mission analysis, mission route analysis, route planning, and perspective scenes.

Equipment Reqs: Three TAC-4 workstations (TLAM planning system afloat (TPSA) and mission distribution system (MDS)). Digital imagery workstation suite afloat (DIWSA).

Connectivity Reqs: LAN (ETHERNET), STU-III, generic front-end computer processor (GFCP)

Crypto Reqs: NONE.

Normal Locations: US Navy aircraft carriers (CV/CVN’s), four rapid deployment suites (RDS’s), and four shore sites.

Information Managed: National imagery, TLAM missions, and rtes.

Products Created: Intelligence databases, routes, missile route analysis, route planning, and perspective scenes.

Lead Service/Contractor: US Navy/GDE Inc., Boeing Afloat, and TIBURON System Inc.

Current Fielding Status: NSWCDD Dahlgren and NMITC installations completed. All CVNs except Nimitz and Truman have been fielded. RDSPAC and RDSLANT no installations completed.

Known Problems: No known problems. APS completed OPEVAL in FY 94; graded operationally effective and suitable.

DIICOE Compliance Rating: Not Rated.

Point of Contact: LCDR Scott Carlson, USN. TOMAHAWK Command and Control, PMA 281. Phone: (301)757-6146. Web info at: http://www.tci.navy.mil

Updated by: Capt Curtis Carlin, USMC, CCSC-99.

 

 

Advanced Tactical Air Reconnaissance System

(ATARS)

Primary Purpose: Provides an organic aerial reconnaissance platform to Marine Expeditionary Force and subordinate commanders.

Sub-Functions: Collect and record data-link digital electro-optical (EO), infra-red (IR) and High Resolution Synthetic Aperture Radar (HSAR) imagery in a near real-time basis. Provides day, night, and all weather capabilities.

Equipment Reqs: Used in Lot XIV and up F/A-18D. Majority of equipment housed within 20 mm gun space. The Navy has plans to use ATARS in the F/A-18E/F, which is under development.

Connectivity Reqs: To use the ATARS data-link, the ground based Navy-Joint Service Image Process System (N-JSIPS), JSIPS, or Tactical Exploitation Group (TEG) will be required. The wiring for the data link pod will reside solely on station 5 on the aircraft.

Crypto Reqs: To be determined.

Normal Locations: Fixed-wing Marine Aircraft Groups (MAG) within the Marine Aircraft Wings (MAW).

Information Managed: ATARS manages EO, IR, and HSAR imagery.

Products Created: ATARS, working in conjunction with ground based systems, creates digitally exploitable imagery.

Lead Service/Contractor: United States Navy/ Martin Marietta.

Current Fielding Status: Fielding continued during FY99.

Known Problems: Only minor technical problems exist with the prototypes. All known problems should be fixed prior to production.

DIICOE Compliance Rating: Not rated.

Point of Contact: Capt Dukes, NAS China Lake, Comm: (760) 939-0118.

Updated by: Capt Craig R. Doty, USMC, CCSC-99.

 

 

Asset Tracking, Logistics, and Supply System

(ATLASS)

Primary Purpose: Provide fully integrated supply, maintenance, and readiness capability operating in a client-server environment.

Sub-Functions: Supply, maintenance, and readiness.

Equipment Reqs: PC (486) with a Windows-based environment and tape backup.

Connectivity Reqs: Phone line, satellite link (when deployed), or disk transfer.

Crypto Reqs: No internal crypto. Require secure transmission over satellite link, when used.

Normal Locations: Consumer-level user unit. Direct and indirect support to units with feedback and link to headquarters elements. Used in all USMC ground-element units.

Information Managed: Inventory control, supply accountability, supply requisitioning, and maintenance management (within the next 12 months).

Products Created: Status reports for supply and maintenance management.

Lead Service/Contractor: USMC/PRC Corp. ATLASS Development Committee Maj Chezem, (202) 433-3612, DSN: 288-2930, FAX: 288-2497.

Current Fielding Status: ATLASS Phase 1 initially fielded in USMC ground units spring 93. Replaces Landing Force Asset Distribution System (LFADS) which was a Supported Activity Supply System (SASSY) programmed in ADA. The LFADS system was inadequate and needed a format change, initiating the effort to develop and field ATLASS.

Known Problems: Current version incomplete system. Maintenance management aspect of ATLASS will be included in Phase 2, with initial fielding scheduled for March 99. When fielded it will be an integrated supply and maintenance, client-server based application that will enable the Ground Logistics communities to do most of their work in ATLASS without duplicative information on the main frame. Significant capabilities for both maintenance and supply are added in this phase that are not in the mainframe systems of the first phase of ATLASS.

DIICOE Compliance Rating: Not rated.

Point of Contact: Major Bob Rackham and Chief Warrant Officer-4 Dave Lick, HQMC, LPS (706) 784-2645.

Updated by: CPT Thomas Schwab, USA, CCSC-99.

  

 

Command and Decision System - AEGIS Display System

(C&D-ADS)

Primary Purpose: C&D is the central processing element of the AEGIS weapons system, synthesizing all elements of ship and link information. ADS is the system that displays on-ship sensor and datalink information.

Sub-Functions: Mission execution, safety-related, and mission planning decision processing.

Equipment Reqs: ADS equipment organized into seven groups- Embarked Command Display Group; Ownship (O/S) Command Display Group; Tactical Console Group; Support Group; Computational Group; and Test Set Group.

Connectivity Reqs: Connectivity handled within ship assets and passed via C&D.

Crypto Reqs: None, other than those internal to the ship.

Normal Locations: CG-47 (TICONDEROGA) Class Cruisers and DDG-51 (ARLEIGH BURKE) Class Destroyers.

Information Managed: Tactical and strategic situations for all warfare areas, force unit mission readiness status, force-related doctrine, force command structures, and current weapon inventories.

Products Created: Hardcopy printouts of all ADS displays and videotape of displays.

Lead Service/Contractor: USN/Lockheed-Martin.

Current Fielding Status: Currently used by USN vessels per above.

Known Problems: None.

DIICOE Compliance Rating: Not rated.

Point of Contact: Chief of Naval Operations N865E1; Theater Air Warfare, Cdr Pat Roane, DSN 225-7505.

Updated by: Capt Kiraiakos J. Kalogiannis, USMC, CCSC-99.

 

Command and Control Personal Computer

(C2PC)

Primary Purpose: Interface UNIX-based computers with Windows 95 or NT operating systems for personal computer operations.

Sub-Functions: Emulates Tactical Combat Operations (TCO) application in a PC environment.

Equipment Reqs: Pentium processor with 64 MB RAM.

Connectivity Reqs: Connect to SIPRNET or NIPRNET via RJ45 or Category 5 cabling.

Crypto Reqs: Normal network security measures only. No additional security required.

Normal Locations: USMC system for use from MEF operations centers down to squadron and battalion level operations.

Information Managed: Graphical situational awareness. Tactical and strategic situations for all warfare areas, Course of Action (COA) graphics/overlays, and imagery plan overlays.

Products Created: Graphic overlays exportable to Power Point as a .gif file for hardcopy printout. Unlike TCO, C2PC has no text file or log product capabilities.

Lead Service/Contractor: USMC, Marine Corps Tactical Systems Support Agency (MCTSSA)/Inter-National Research Institute (INRI).

Current Fielding Status: Version 5.0.2 is currently fielded to all three MEFs down to the division/wing level. Version 5.4 has been fielded in March 1999. The new version has improved mapping, communications, and overlay capabilities.

Known Problems: Conversion problems regarding color transfer and clean pixel transfers from UNIX to PC. Should improve with new version.

DIICOE Compliance Rating: Level 6.

Point of Contact: Program Manager and Assistant Operations Office, MCTSSA, Edie Renadie DSN: 725-2093.

Updated by: CPT Michael L. Kennedy, USA, CCSC-99.

  

Computer Aided Embarkation Management System

(CAEMS)

Primary Purpose: Assist in planning, execution, and documentation of load plans on amphibious, Maritime Prepositioning, and commercial ships.

Sub-Functions: None.

Equipment Reqs: IBM compatible computer, one high density disk drive, 40 MB hard drive, 4 MB RAM.

Connectivity Requirements: None.

Crypto Reqs: None.

Normal Locations: Landing Support Battalion, deploying units and supporting ships.

Information Managed: Ship characteristics and embarkation data.

Products Created: All reports required to document an amphibious or Maritime Prepositioned Force (MPF) ship’s load plan.

Lead Service/Contractor: USMC/Stanley Associates.

Current Fielding Status: Version 3.3 currently fielded.

Known Problems: No ability for combat cargo officers (CCOs) to modify the standard ship packages. Template and ship configuration libraries not complete. Template and ship configurations cannot be modified by the user. Program parameters restrict user ability to store cargo athwart ship.

DIICOE Compliance Rating: Not rated.

Point of Contact: CWO2 Joey Rice, MARCORSYSCOM DSN 278-5963.

Updated by: Capt Jeffrey C. Smitherman, USMC, CCSC-99.

  

 

Conventional Ammunition Integration Management System

(CAIMS)

Primary Purpose: Provide worldwide status and visibility of the Navy’s conventional ammunition including Marine aviation ammunition.

Sub-Functions: Provide worldwide asset and expenditure tracking controlling allowances, training allocations, and storage plans, allowing stock screening. Provide due-in visibility for procurement, production and encrytpion.

Equipment Requirements: IBM 3090-180E 17.5 MIPS and IBM 3090-300E 44.0 MIPS triple processor. For on-line query: IBM compatible PC, modem, and encryption.

Connectivity Requirements: IBM 3270 protocol.

Crypto Requirements: KG-84, KOI-18

Normal Locations: One central database, 115 remote sites, HQMC, MARFORLANT/PAC, and MAWs.

Information Managed: Ammunition requirements, assets, allowances, production and procurement. Expenditures (financial, technical, and budget). Serial/lot number tracking information.

Products Created: Notices of Reclassification(NAR), activity data, technical data, automated message generation and follow-up.

Lead Service/Contractor: USN/Computer Associates.

Current Fielding Status: Complete. Version: N/A

Known Problems: Not user friendly, i.e. have to print reports to view. Mainframe legacy system. Not joint.

DIICOE Compliance Rating: Migrating to open system environment (OSE) in July 99.

Point of Contact: Dr. Lambros Tzerefos, Naval Ordnance Center, IMSD Information System Department, Mechanicsburg, PA 17055, Comm (717) 605-6537 6313, DSN 430-6537.

Updated by: Capt Larry W. Norman Jr., USAF, CCSC-99.

  

Computer Aided Load Manifesting System

(CALMS)

Primary Purpose: Rapidly generate load plans and manifests for C-130 E/H, MC-130E/H/P, RC-135E/R, C-17A, C-141B, C-5A/B, and transport aircraft.

Sub-Functions: Ensures maximum utilization of aircraft assets. Reports load information in support of in-transit visibility. Provides a standard automated capability to store and edit information on air cargo increments. Allows user to pre-plan cargo loads used in peacetime and times of war.

Equipment Reqs: 486 PC.

Connectivity Reqs: Standalone system. Interfaces with LOGMOD-B, Cargo Movement Operations Systems (CMOS), and MAGTF Deployment Support System (MDSS II).

Crypto Reqs: None.

Normal Locations: Any deploying unit, platoon and above. All services.

Information Managed: Equipment database is created by units. Assignment of aircraft loads.

Products Created: Load plans for C-130, C-141, C-5, and KC-10 aircraft.

Lead Service/Contractor: USAF/Air Force Logistics Management Center (AFLMC)

Current Fielding Status: Version 5.3 fielded July 97 replacing version 5.2. In use with all services, Departments of Energy, Department of Transportation, Defense Logistics Agency, NATO, and other allies. Version 5.3 adds MC-130 E/H/P, and new helicopter templates. Other commercial aircraft under consideration are: B-767, DC10/MD11, DC-8, L100.

Known Problems: None.

DIICOE Compliance Rating: Not rated.

Point of Contact: Air Force: Msgt Fitzpatrick, DSN: 569-5959, Comm: 334) 416-5959, Fax DSN: 278-5916.

Internet: http://www.afca.scott.af.mil/commsys/systems/calm/calm.htm

Updated by: Capt Keith E. Whitehouse, USMC, CCSC-99.

 

 

 

Consolidated Air Mobility Planning System

(CAMPS)

https://214.3.17.154/cris/irc/system-report.cfm?id=37

CAMPS is Air Mobility Command's (AMC) primary C2 planning and scheduling system that provides mobility mission planners with an integrated view for planning and scheduling AMC air mobility resources to support peacetime, contingency, humanitarian, and wartime operations. CAMPS provides separate unclassified and classified planning and scheduling capability, and also provides advanced user capabilities for operational planning and allocation management. CAMPS Migration Completion Date (MCD) was achieved in Feb 02, and Full Operational Capability (FOC) is targeted for Sep 06. Details on CAMPS' functionality are outlined below.

CAMPS provides an integrated architecture that will be Common Operating Environment (COE) Level 5 compliant and will conform to the U. S. Transportation Command (USTRANSCOM) and AMC enterprise architecture environments. A single Oracle database will provide one-time data entry and will be consistent with Department of Defense (DoD) standard data definitions and the AMC Corporate Database architecture. CAMPS presently uses Windows NT and Windows 2000 (and Windows XP in the future) in a client-server environment, and will take advantage of COE software components to provide administration and support services.

The primary operating site for CAMPS is Scott Air Force Base (AFB), IL (HQ AMC/DOX/XPY/FMP, AMC's TACC, and USTRANSCOM). Other operating sites that currently use CAMPS software include Travis AFB, CA (Alternate TACC); Hickam AFB, HI (PACAF AMOCC); and Ramstein AB, GE (USAFE AMOCC); Other sites using legacy CAMPS software (CMARPS) include Langley AFB, VA (ACC AOS); USTRANSCOM/J5; USPACOM/J5; and HQ USAF, Washington, D.C. Future CAMPS sites will support AMC's Air Mobility Operations Squadrons (AMOS) at McGuire AFB, NJ (621 AMOS) and Travis AFB, CA (615 AMOS), with a training facility at Air Mobility Warfare Center, Detachment 1 at Hurlburt AFB, FL.

CAMPS FUNCTIONALITIES/APPLICATIONS:

CAMPS has several major functionalities (or applications) that facilitate mobility mission planning by various specialized functional areas. These functionalities are described below, and may be 'known' by separate terms or acronyms.

1. CAMPS Client: The components that support Channels, SAAMs, Barrels, and Air Refueling provide support for many peacetime, contingency, humanitarian, and wartime operations:

(a) CHANNELS provides automated support for the development of Channel airlift schedules. The Channels functionality develops a workable plan (schedule) that will honor frequency or requirements-based airlift and provide the capacity (airlift) to move cargo and passengers using a minimum of flying hours. The Channels component also provides the data files necessary to produce the AMC monthly schedule bulletins for Atlantic/Pacific Cargo/Passenger schedule information. The bulletin reports (and their amendments) are available to many worldwide customers through various evolving methods (AUTODIN, hardcopy mail, web, etc.).

(b) The SPECIAL ASSIGNMENT AIRLIFT MISSION (SAAM) component provides support for the scheduling of 'special' priority mobility missions. It is separated into four user categories: SAAM Requirements, SAAM Directors, SAAM Planners, and SAAM Read-Only users. The SAAM Requirements component provides an automatic SAAM request load capability that verifies the Department of Defense Form 1249 (DD1249) format and the content of a new airlift request to ensure accuracy and completeness of necessary data. It also uses a web-based front end, the SAAM Request System (SRS), by which users submit their airlift requirements (more details below.) The SAAM Directors component provides further editing of SAAM DD1249 forms (splitting, commitment, Mission Operating Directive (MOD) message publication, etc.). The SAAM Planners have access to the SAAM Directors component, but generally use CAMPS' Mission Detail component to plan and schedule missions. SAAM Read-Only users are able to access a limited amount of the SAAM component for viewing SAAM data, report generation, or cost estimation.

(c) The BARRELS (or Barrelmaster) component provides automated support for the tasking of missions (aircraft and crew) to operating units. All missions in the Global Mission Repository (GMR) are available. In addition, Barrels can create notional missions to represent missions not yet contained in the GMR. Barrel users are separated into three categories: Airlift Barrels, Tanker Barrels, and C-130 Barrels, all of which use the system in a similar manner.

(d) The AIR REFUELING component provides tools to coordinate, manage, and report air refueling events and tracks. It also provides an up-to-date view of worldwide air refueling activities by accepting and transmitting air refueling information between CAMPS and GDSS. It has a web-based front end, the Air Refueling Management System (ARMS, further described below), by which receiver units submit their air refueling requirements and tanker units interactively satisfy unsupported requests (more details below).

2. SPECIAL ASSIGNMENT AIRLIFT MISSION (SAAM) REQUEST SYSTEM (SRS): The SRS is a CAMPS web-based application that enables the submission, validation, management, and approval of SAAM mission requests (Form DD1249). Individual unit requestors, in-service validators, combination requestor/validators, and United States Transportation Command (USTRANSCOM or USTC) requirements personnel process SAAM requests via web-based forms. When a requestor submits a SAAM request , the requestor's in-service validator is notified via email. After the in-service validator approves and forwards the SAAM request to USTC, both USTC SAAM Requirements personnel and the original SAAM requestor are notified by email. USTC SAAM Requirements personnel validate airlift requirements and make modal decisions before passing the requirements to the Tanker Airlift Control Center (TACC), where the SAAM directors and planners complete the mission planning and identify mission support resources. When USTC personnel approve the request, the SAAM requirement is loaded by USTC into the Consolidated Air Mobility Planning System (CAMPS) database via electronic transfer. This functionality is planned for migration to USTRANSCOM's Integrated Customer Service (ICS) system in a two phase implementation.

SRS can be accessed at https://ntweb0.scott.af.mil/srswebcls/ (userid and password required)

3. FLOW PLANNING: The CAMPS Flow Planning component assists in creating requirements data, building plansets, and scheduling missions for exercises, contingencies, and Deliberate Planning activities. Flow Planning functionality was migrated to CAMPS from the legacy AMC Deployment Analysis System (ADANS), and is accessed through the CITRIX Metaframe. Flow Planning supports all Deliberate, Contingency/Crisis, and Exercise Planning tasks through three software components: Pre-Planning, Planning, and the Quick Course-of-Action (QCOA) tool kit.

(a) PRE-PLANNING - The Pre-Planning component performs the file conversions necessary for CAMPS to read, load, and assess classified data from the Joint Operation Planning and Execution System (JOPES). Selected TPFDD files, including the Type Unit Characteristics Data File (TUCHA), are imported. CAMPS then loads the TPFDD/Summary Reference File (TPFDD/SRF) and allows the planner to view and to edit TPFDD records, generate airlift requirements, and also print reports.

(b) PLANNING - The Planning component assists planners in developing airlift flows by providing the utilities to create and edit plansets graphically, enter and modify requirements, create requirement sources, and develop air mobility support networks. The planner is able to add or modify station data, aircraft characteristics, force package information, and crew characteristics, and to schedule missions. Once the missions are scheduled, the results may be reviewed, printed, downgraded, and transmitted to GDSS at the appropriate classification level. Planning also permits individual mission building and selective assignment of ULN requirements for a given mission. This capability is used most often during contingencies or crisis response where planner-coordinated load plans are known, assigned to each mission generated by the planning function, and then transmitted to the Global Decision Support System (GDSS).

(c) Quick Course of Action (QCOA) enables mission planners to develop quick-look solutions for mobility problems, allowing for faster mission planning decisions, and creating a more expedient and efficient planning environment. QCOA allows rapid development of scenarios defined by estimates of requests, dates, station data, aircraft Mission/Design/Series (MDS) and configurations, channels, earliest arrival dates, number of planes, or selected combinations of these data. Depending on the data supplied, the tool provides estimates of fleet size, throughput, choke points, minimum operation length, or schedule estimates. The scenario solution can then be converted into a plan for detailed planning and scheduling.

4. CHANNELS WEB BULLETIN: Channels Web Bulletin is a web-based application that enables Channel planners to publish quarterly passenger and cargo mission schedules together with amendments in a central web location for worldwide passenger and cargo booking access by field offices. This replaces the older paper products and email documents previously sent to hundreds of addresses on a monthly basis.

5. AIR REFUELING FUNCTIONS (& CMARPS): Several air refueling planning/scheduling components have been developed in or migrated to CAMPS. The CAMPS sub-components include:

------------------------

CAMPS MIGRATION: CAMPS combined the functionality of two legacy systems, AMC Deployment Analysis System (ADANS) and Combined Mating and Ranging Planning System (CMARPS), into a single, integrated AMC C2 system for both airlift and air refueling missions. Previously, AMC used CAMPS and legacy ADANS for planning and scheduling of airlift missions, and legacy CMARPS for planning and scheduling of air refueling missions. The migration of the legacy ADANS and CMARPS into CAMPS was accomplished in several increments:

1. Increment One (began May 1996, reached IOC in April 1999) migrated legacy ADANS Special Assignment Airlift Mission (SAAM) and Channel scheduling functionality into CAMPS.

2. Increment Two (April 2000) migrated legacy ADANS Barrelmaster (aircraft allocation) functionality, implemented the first stage of the corporate-compliant CAMPS database, and delivered a new resource allocator prototype based on emerging scheduling technologies.

3. Increment Three (March 2001) began the migration of legacy Air Refueling mission planning functionality, and implemented many other C2 functional requirements.

4. Increment Four (January 2002) provided the Air Refueling Management System (ARMS), which included A/R coordination, and the ability to automatically load A/R request information directly into the CAMPS database.

5. Increment Five (Migration Completion Date (MCD), February 2002) migrated user access to the remaining legacy system capabilities (including legacy ADANS flow planning and CMARPS functionality) from a Windows user client.

1.1 Related Web Links.
AMC Comm Group (AMC CG)
https://www.amc.af.mil/amccg/index.cfm
HQ AMC/DOR - CAMPS Functional Management
https://www.amc.af.mil/do/dor/dor.htm

2. Migration Information

2.1 Migration Status. Migration

2.2 Replacement Application. None

2.3 Replacement Date. None

2.4 Migration Notes. ADANS and CMARPS have migrated into CAMPS.

3. Planned Upgrades

Functional and system upgrades for CAMPS FOC (targeted for Sep 06) include:

1. CAMPS for the AMOS: CAMPS will support AMC's in-theater or deployed Air Mobility Operations Squadrons (AMOS) by providing mission planning and scheduling functionality. AMOS mission planners will send unclassified strategic airlift mission data through deployed GDSS/C2IPS to TBMCS for inclusion in the ATO. Missions may also be managed/executed with unclassified GDSS/C2IPS to allow normal CAMPS C2 activities (Barrelmaster, Channels, etc.). A web-based Intra-Theater Airlift Request System (ITARS) will also enable short-notice airlift request load data to be loaded into CAMPS. When available, long-haul "reach back" communications to JOPES (via GCCS), GDSS, and CAMPS TACC node will be provided, or CAMPS may operate autonomously (stand-alone). Target IOC is early CY03.

2. Integrating the Airlift and Air Refueling Capabilities: Current TACC processes and CAMPS functions need to be more integrated to produce a true 'single system' with optimized alternatives and results. This effort will continue over the course of FOC development.

3. State-of-the-World: Real-world data needs to be integrated into the planning process as an initial state for re-planning and scheduling (including current resource locations (aircraft, crews), potential limitations (aircrew, aircraft, and/or airfield restrictions), etc.). This will improve mission planning by formulating options and basing decisions on real-world conditions.

4. Advanced Airlift Scheduler: The present Flow Planning scheduler requires upgrading and inclusion of various 'options' to allow differing mobility scenarios to be used, including hub-and-spoke, crew staging, A/R 'bridge', multiple operations/plans, 'transload' of ULN movements, etc. The AAS may combine the Mission Planner Scheduler, Airlift Allocator, and Air Refueling (AR) Allocator, and will eventually replace Flow Planning.

5. Improving the Barrelmaster Allocator (BA): This will provide a "schedule repair" capability to planners (prior to mission execution) and mission controllers (during execution), allowing "what if" scenarios to be viewed and chosen for "schedule repair" (e.g., insert a new mission requirement, or "fix" a requirement impacted by weather, maintenance, or other real-world events). This tool will also need State-of-the-World data.

6. Incorporating Level 3 and 4 TPFDD data (from JOPES): As the planning functions of CAMPS improve, the functional users have a requirement to use this data to better plan mission loads, allowing more efficient planning and scheduling of mobility assets.

7. Corporate Data Base (CDB), Logical and Physical Data Models (LDM/PDM): Existing databases (legacy Sybase and Oracle) are being migrated to a single database which will consolidate all data to a single architecture, eliminate the need for data replication, be LDM/PDM-compliant, and reduce "back office support" requirements. A unified database will also support improved communications with other C2 systems and improve data integrity. This database effort will continue over the course of FOC development.

8. COE Level 5 compliance will improve the modularity of CAMPS, allowing easier upgrades and decreasing development costs.

9. Human Interaction with Software Agents (HISA): CAMPS is supporting the implementation of a HISA 'tool' in CY02 for Channel planners (but not as part of the CAMPS software). HISA will access planned mission data and various tables from other C2 systems (GDSS, NOTAMS, etc.) for information relevant to mission planning (airfield status, aircraft location, etc.). A HISA-generated 'alert' will be sent to the planner when events may cause a problem with a particular mission. This will allow the user to investigate and resolve problems before they actually occur. The goal is to provide the planner with the timely and advance notification.

Combat Cryptologic Support System

(CCSS)

DISCONTINUED SYSTEM

Primary Purpose: Display and store cryptologic data received from OUTBOARD, combat DF, and shore HFDF sites via TACINTEL. Data is correlated and used as inputs for long-range targeting of Harpoon and Tomahawk.

Capabilities: Provides communications with battle group and shore sites via TACINTEL and other secure teleprinter circuits; Tasking of cryptologic assets, data fusion, and graphic display of the battle group situation through and OK-324 System Supervisor Station; Secure external voice communications circuits; Secure teleprinter send/receive circuits; Receive only capability for Fleet broadcast teleprinter circuits; Secure/plain voice communication; Navigation data via interface between CCSS and C&D computer; Interface between CCSS and the TWCS (CG 52 and follow) to provide navigation data.

Equipment Requirements: Battle Force/Group's organic cryptologic collection and communications assets. Can use SUPPLOT, SSES, OUTBOARD, TACC, and mobile cryptologic vans. There is no standard mix of equipment or assets. Connectivity Reqs: Requires TACINTEL.

Crypto Requirements: Built in.

Normal Locations: CCSS was replaced by SSEE (see "Fielding Status" below) and is located in the Ship's Signal Exploitation Space (SSES aboard AEGIS ships).

Information Managed: Tactical Intelligence (TACINT).

Products Created: Signal of interest. Targeting information.

Lead Service/Contractor: U. S. Navy.

Fielding Status: It has been removed from the AEGIS and discontinued. Point of contact recommends removal of this obsolete system from the compendium. Program lost funding four years ago and exists only as a legacy system on two Aegis-class cruisers.

Known Problems: The correlated information did not assist in targeting the Harpoons and Tomahawks. The system is being phased out.

DIICOE Compliance Rating: Not rated.

Point of Contact: Mark Reinig, SPAWAR, (619) 524-7331.

Updated by: Capt Matthew G. Rau, USMC, CCSC-99.

  

Cargo Movement Operations System

(CMOS)

Primary Purpose: Automates base-level cargo movement.

Sub-functions: Interfaces with Standard Base Supply System (SBSS) and Logistics Module Base (LOGMOD-B) for expedient peacetime-wartime cargo shipment, (CALM) Computer Aided Load Manifesting System

Equipment Reqs: 486 computer, 16 Meg RAM, HP 900/750 (server) and printer.

Connectivity Reqs: AUTODIN; Local Area Network (LAN).

Crypto Reqs: None.

DII COE: Not rated.

Normal Locations: USAF base-level traffic management/freight operations center.

Information Managed: In-transit item visibility, OAS funds, freight hold time, and cargo movement data.

Products Created: Government bills of lading (GBL), air manifest, military shipping labels, and shipping declarations for dangerous goods.

Lead Service/Contractor: HQ USAF/Ogden Professional Services.

Current Fielding Status: On line at all active duty Air Force bases. Full operational status.

Known Problems: None.

Point of Contact: Susan Kirkland DSN 596-5578; Gordon Allbrittion DSN 596-2067: Gunter AF Base, GA.

 

 

Collection Requirements Management Applications

(CRMA)

DISCONTINUED SYSTEM- SEE JCMT

Primary Purpose: Used by Intelligence Collection Managers to produce Requests For Information (REI) tasking messages. Provides information on collection platforms availability, and the information they collect (targets). Verifies a target has been collected against and by what means.

Sub-Functions: Forms management; auto E-mail to correct agency; mapping program; target's previous collection listing; collection platforms available for target; database mgt.

Equipment Req.: Server--Sunsparc 2 GX w/min: 2 GB hard disk storage (5 GB optimum), 32MB RAM (64 MB recommended); Color Monitor 16" or 19"; 8MM Exabyte tape drive; Laser jet Postscript printer; Optional: CD ROM Drive (for Delorme mapping capability), Calcom Postscript color master printer. Can run on JMICS platform/configuration.

Workstations--Any platform you have. Norm is: Color monitor 16" or 19", Sunsparc 2 GX Min: 400 MB hard drive storage, 32 MB RAM.

Software: SYBASE 4.S "OPEN CLIENT C", Delorme Mapping (Vector only), Sun OS 4.1.3 or higher, SYBASE server software for the server only, SYBASE maintenance, MOTIF--license for each workstation, ASTER-X 1.1 word processing or similar type (optional)

Crypto Req.: None. Two feeds required (DSNET 3 & AUTODIN) Both should already have Crypto in place and operating.

Normal Locations: Sensitive Compartmented Information Facility. Unified Commands down to the Tactical 1evel.

Information Managed: 12-14 AUTODIN msg. types and numerous databases.

Products Created: RFI tasking messages.

Lead Service/Contractor: Titan Corp/BTC (subcontractor), San Diego Calif.

Current Fielding Status: Operational at the Unified command level in USAF, USN, and JTF locations worldwide.

Known Problems: None.

DIICOE Compliance Rating: None, program was retired 1 October 1998 and replaced by JCMT.

Point of Contact: Defense Intelligence Agency (DIA), Ms. Mary Ellen Carter, (703) 907-0667.

Updated by: Capt Kelly G. Dobson, USMC, CCSC-99.

 

Combat Terrain Information System

(CTIS)

Sub-Functions: Functions performed by two systems: Digital Topographic Support System (DTSS) and the Quick Response Multicolor Printer (QRMP). Automated assistance in the performance of terrain analysis and production of topographic products within time frames required by Airland Operations Concept.

Equipment Reqs: Support: Army Tactical Command and Control System elements, All Source Analysis System (ASAS), Maneuver Control System (MCS), and other emerging Army tactical weapon systems. Perform extensive digital terrain data base creation, update and revision functions, and interfacing with the Quick Response Multicolor Printer (QRMP).

Connectivity Reqs: S-280 shelter mounted on 5-ton truck. Power provided by standard 30 kilowatt generator.

Crypto Reqs: None.

Normal Locations: Echelons Above Corps (EAC). Utilized by Division terrain teams.

Information Managed: Digital terrain data/Digital Mapping Agency products, imagery. Produces laser terrain base intelligence products, mobility, line of sight, special products, avenues of approach, image maps, and terrain updates.

Products Created: On-off road mobility maps, on-road choke point maps, tactical fording and bridging maps.

Lead Service/Contractor: United States Army/Lockheed Martin.

Current Fielding Status: Low Rate of Initial Production (LRIP).

DIICOE Compliance Rating: Not rated.

Point of Contact: Major Tate (703) 602-8965 Topographic Engineering Center.

Internet: www.tec.army.mil.

Updated by: CPT David A. Thomas, USA, CCSC-99.

 

Defense Casualty Information Processing System

(DCIPS)

Primary Purpose: Tracks casualty data pertaining to service members and their families. DCIPS is the automated migration system for the casualty and mortuary affairs process within the Department of Defense.

Sub-Functions: Information management support to the Casualty and Memorial Affairs Operation Center. Permits automated storage and retrieval of casualty data with links to reporting agencies.

On-line receipt of casualty messages, retrieval of additional personnel information from databases, interactive update and data exchange with Casualty Area commands and Mortuaries. Standardized document formats.

Deployed organizations can produce casualty reports with a user-friendly query function.

Equipment Reqs: Hardware: 486 MHz Personal Computer or higher.

Operating System: Workstation: Windows 95 or Windows NT, Database: UNIX or Windows NT.

Connectivity Reqs: Server and an Ethernet

Crypto Reqs: None (password protected)

Normal Locations: Casualty and Memorial Affairs Operations Center. Casualty Area Commands. Personnel Service Battalion. Point of Embarkment and Overseas Mortuaries.

Information Managed: Casualty data

Products Created: Casualty reports, Mortuary information, repatriation data, next-of-kin notification.

Lead Service/Contractor: The Under Secretary of Defense charged the Deputy Chief of Staff for Personnel with overall responsibility for DCIPS. PERSINSD has technical PM responsibility. The Department of Defense Casualty Advisory Board has functional oversight of the program.

Current Fielding Status: The Office of the Deputy Chief of Staff for Personnel (ODCSPER) is managing the fielding of the system to the services. The Army system has been fielded and is operational. The Air Force has the equipment but is system is not on line. The Navy and Marine Corps equipment has not been fielded.

Known Problems: None. (Y2K compatible)

DIICOE Compliance Rating: Not rated.

Point of Contact: OUSD (P&R) IM, 4015 Wilson Blvd. #1212 Arlington, VA 22203

Task Force for DCIPS Project Manager:

Bonnie B. Bailey Chief, Shared Systems Branch TAPC-PSM-M (703) 325-3600 DSN 221-3600 Technical Contractor: Kathy Johnson

(703) 325-0494, DSN: 221.

Updated by: Capt Alton L. Cochran Jr., USMC, CCSC-99.

 

Defense Message System

(DMS)

Primary Purpose: To provide secure, accountable, faster and more reliable writer-to-reader messaging capability from the office to the warfighter for both organizational and individual messaging at reduced cost.

Sub-Functions: Allows the user to draft and send secure message traffic from a local PC, either commercial or tactical. DMS software will operate using commercial groupware, providing the latest capabilities in information sharing, including multimedia (sound/graphics/video) attachment capability. Replaces the current AUTODIN-based messaging system.

Equipment Reqs: Commercial system: 486 or greater CPU, 16 MB RAM or greater, 500 MB hard disk space or greater, PCMCIA type II card, TCP/IP stack, network access.

Connectivity Reqs: Designed to operate on both commercial and tactical data networks. Supports X.400 and X.500 message and directory protocols.

Crypto Reqs: Fortezza PCMCIA card provides integrated, dual key encryption.

Normal Locations: All users with the requirement and/or authorization to send and receive official message traffic.

Information Managed: Secure messages, including attachments.

Products Created: Viewable/printable messages to the Sensitive-But-Unclassified (SBU) level.

Lead Service/Contractor: Lockheed Martin Federal Systems

Current Fielding Status: Release 1.1, initial functional capability, is currently being deployed. Three more releases (2.0, 2.0A, 2.0B) are planned for FYs 98 and 99. Implementation target year is 2000.

Known Problems: None noted.

DIICOE Compliance Rating: Not rated.

Point of Contact: Mr. Jerry Bennis, Program Manager (703)681-0921 DSN Prefix 761, Direct all questions/comments to (DISA) Helena Robinson,DMSWWW@ncr.disa.mil

Internet: http://www.disa.mil/D2/dms/index2.html

Updated by: CPT Lisa D. Whittaker, USA, CCSC-99.

 

Department of Defense Intelligence Information System

(DODIIS)

Primary Purpose: Consensus building and decision-making body concerned with hardware and software commonality and interactive issues within the intelligence community. Members include: Marine Corps, Navy, Army, Air Force, Defense Intelligence Agency (DIA), NIMA, and DISA

Sub Functions: Often thought of as a network linking intelligence data handling systems. System of applications includes applications such as the Joint Deployable Intelligence Support System (JDISS) currently in use throughout DoD.

Equipment Requirements: Windows NT or Sun Solaris

Crypto Requirements: DOODIIS network is classified and requires proper preauthorized access codes. SCI levels must be properly encrypted. GENSER level must have appropriate level devise.

Normal Locations: Can be found throughout DoD, DIA, NIMA, and DISA. Normally found in intelligence sections and SCIFs and classified work areas both shore based and afloat.

Lead Service/Contractor: DIA.

Known Problems: A lack of any type of multilevel security requires separate terminals for GENSER and SCI information.

DIICOE Compliance Rating: Not rated.

Point of Contact: Capt Dennis Dubois at DIA, (202) 231-2208.

Internet: Intel link only via DIA.

Updated by: Capt Virgilio Gonzalez, USMC, CCSC-99.

 

  

Defense Red Switch Network

(DRSN)

Primary Purpose (Mission): "To provide the ability to transfer or switch secure/nonsecure (RED/BLACK) voice and data between the NCA, services, unified... commands, subordinate organizations (military and civilian) and also Allies (NATO, Canada, etc.), both locally and worldwide; provides: RED/BLACK voice and data capability; Multilevel precedence and preemption..." Joint Staff Operational Requirements Document.

Sub-Functions: Command Center Voice operations functions, including Conference monitoring, Key Personnel Locator, Operator functions, Emergency Action Consoles, etc. Where installed, Red/Black switch pairs provide both secure and non-secure voice services to users on a single instrument. Supports interfaces to other secure voice systems, including, MilSatcom, KY58, KY68, ANDVT, STU-III/STE. Interface implementations vary from site to site.

Equipment Reqs: Raytheon (Electrospace™) DSS and SDS family digital switches and associated remote user equipment. SDS family of switches are found at fixed sites. DSS family of switches are used in both fixed and transportable configurations.

Connectivity Reqs: Depending on configuration, minimum 56KBPS circuit for a remote phone and up to T-1/E-1 for interswitch trunks. Standard Tactical Entry Point (STEP) supports multiple 56KB connections for both remote phone and deployable Red Switch connections to network.

Crypto Reqs: Long Locals (remote phones) use KG-84/KIV-7. Trunks use KG-194/KIV-7HS.

Normal Locations: Switches are located at Major CINC Command centers and designated subordinate commanders command centers world-wide. Remote service to selected offices, quarters and commands not requiring dedicated switches. JCSE has two deployable Red Switches which may be tasked by JS to deploy in support of CINC/JTF requirements.

Information Managed: Secure Voice calls and conferences up to Top Secret SCI.

Lead Service/Contractor: The Defense Information Systems Agency (DISA) is responsible to OSD and the Joint Staff for overall Network and Program Management, with USAF as lead MILDEP for Logistic Support. Depot Logistics Support is provided by Raytheon Systems Company (formerly Electrospace) in Richardson, TX under a Sacramento Air Logistics Center contract.

Current Fielding Status: Fielded. Network is continuously modified as needed to add new users and locations. New user requirements must be submitted to Joint Staff/J6T iaw CJCSI 6215.01.

Known Problems: N/A

DIICOE Compliance Rating: Not rated.

Point of Contact:

Defense Information Systems Agency (DISA)

DISN Secure Voice Branch (D3123)

Mr. Robert F. McLaughlin,

DSN 653-8081

Comm (703) 735-8081

Email: mclaughr@ncr.disa.mil

Joint Staff/J6T

LtCol George Field, USAF

DSN 225-8408

Comm: (703) 695-8408

Email: george.field@js.pentagon.mil

Internet: http://drsnbbs.ncr.disa.mil

Updated by: Capt Crystal T. Pelletier, USMC, CCSC-99.

  

Digital Terrain Analysis System

(DTAMS)

Primary Purpose: Mobile terrain support for forward deployed units. Special mapping and geographic intelligence in support of MAGTF Commanders.

Sub-Functions: Geographic Information System (GIS) collection and processing. Terrain analysis support for Intelligence Preparation of the Battlespace. Component of the topographic set fielded to each Topo Platoon in 1995.

Equipment Reqs: SUN Sparc 2 workstation and associated peripherals.

Connectivity Reqs: LAN Network.

Crypto Reqs: None.

Normal Locations: Primary location: MEF Topographic Platoon. Attached to MEF G-2, MEU S-2, or GCE/ACE/CSSE G-2/S-2 when deployed.

Information Managed: Provides geospatial intelligence for the MAGTF Commander throughout all phases of an operation. The system will supplement normal mapping, by preparing up-to-date map substitutes. It will exploit National Imagery and Mapping Agency (NIMA) Geospatial data.

Products Created: Special Mapping (enlargements/paneling) and geospatial intelligence for Intelligence Preparation of the Battlespace (IPB).

Current Fielding Status: Fielded.

Known Problems: Current system will not run on a Y2K compliant SUN Operating System. Fixing this by adding RAM to handle the new operating systems and allow the processor to run the DTAMS program.

DIICOE Compliance Rating: Not rated.

Point of Contact: MSgt Robert N. Wilkinson

MARCORSYSCOM

DSN: 784-2101

Updated by: Capt William J. Mattes Jr., USMC, CCSC-99.

 

Global Command and Control System

(GCCS)

Primary Purpose: The Defense Information Systems Agency (DISA) officially deactivated the World Wide Military Command and Control System (WWMCCS) Intercomputer Network (WIN) on 30 August, 1996 and replaced it with GCCS. Concurrently, the Chairman of the Joint Chiefs of Staff (JCS) declared GCCS as the joint command and control system of record. GCCS is the joint force commander's principle tool for collecting, processing, and disseminating data and information. GCCS provides a single, seamless command and control structure designed to support the warfighter's decision making process. GCCS allows warfighters to selectively pull and push information they need to plan, coordinate, and execute operations throughout the chain of command through the use of a Common Operating Environment (COE). The COE, created through the use of common component and application interface software, enables users to share, manipulate, and disseminate information regardless of hardware platform or operational system specific requirements. More importantly, the COE provides the warfighter with a Common Operational Picture (COP) that produces a fused battlespace. GCCS consists of all necessary hardware, software, and procedures for worldwide connectivity. The system uses a client server architecture based on commercial open systems standards for both common commercial and government applications. The GCCS operational environment is similar to the MicroSoft Windows operating environment. The GCCS approach focuses on developing the Defense Information Infrastructure Common Operating Environment (DIICOE). The DIICOE establishes C2 interoperability among U.S. military services and governmental agencies through the COE and COP. Under DIICOE, system interoperability between command and control applications and data is facilitated through the use of common core system components. Examples of such common system components are shared word processing, e-mail, and imagery applications. Stand-alone functional systems, such as the Joint Maritime Command Information System (JMCIS), are able to share information with GCCS terminals and other stand-alone systems by accessing core system components through the use of standard Application Program Interfacing (API) software.

Sub-Functions (System Applications): GCCS currently uses 209 information segments to create the COE used to facilitate interoperability between stand-alone operational systems and GCCS terminal. These segments include common system administration functions as well as those associated with stand-alone operational system functions. A list of current system applications is provided below:

Ad Hoc Query (AHQ)

Adobe Acrobat Reader

Airfield Database

APPLIX Office Automation Software

Automated Message Handling System (ANHS)

Computer Misuse Detection (CMD) Client

Dynamic Analysis and Replanning Tool (DART)

Domain Name Server (DNS)

Defense Software Repository System (DSRS)

Electronic Commerce Processing Node (ECPN)

Enhanced Linked Virtual Information System (ELVIS)

Evacuation System (EVAC)

Force Augmentation Planning and Execution System (FAPES)

Fuel Resource and Allocation System (FRAS)

GCCS Reconnaissance Information System (GRIS)

Global Positioning System (GPS) Time

Global Recon Information Database

Global Status of Resources and Training Systems (GSORTS)

GNU Zip Compression Utility (GZIP)

Information Management Subsystems (IMS)

Internet Relay Chatter (IRC)

Joint Deployable Intelligence Support System (JDISS)

Joint Engineer Planning and Execution System (JEPES)

Joint Mapping Tool Kit

Joint Maritime Command Information System (JMCIS)

Joint Operations Planning and Execution System (JOPES)

JOPES Navigation (JNAV)

Joint Tactical Interface Module

Logistics Sustainment Analysis and Feasibility Estimator (LOGSAFE)

Medical Planning and Execution System (MEPES)

Near Real Time Intelligence - GENSER

Netscape

Netsite

Newsgroups and Internet News

ORACLE Relation Database Management System (ORACLE RDBNS)

Predefined Reports Database

Real Property Inventory Database

Requirements Development Analysis (RDA)

Reference File Administration (RFA)

Scheduling and Movement (S&M)

Tactical Information Broadcast System (TIBS)

Theater Analysis and Replanning Execution Tool Kit (TARGET)

Theater Ballistic Missile Warning and Display

Equipment Reqs: GCCS operates using either UNIX or Windows NT based servers with like workstations. SunSPARC 20 application servers are DISA's official GCCS platforms, although any Pentium based PC with the appropriate hardware and software capable of operating in a UNIX or Windows NT environment can be used. The SunSPARC 5, a smaller PC with enhanced capabilities, is being tested as a possible replacement system for the SunSPARC 20 in an effort to migrate from UNIX based workstations to Comm Off the Shelf (COTS) PCs. Limited migration to Windows NT servers/PC based workstations is currently being facilitated using C2PC software. The fielding of GCCS software, Version 4.0, is planned to complete the migration to PC based workstations. This concept is commonly referred to as the "PC solution."

Connectivity Reqs: GCCS operates in an Ethernet (TCP/IP) client server environment. T1/T3 connections are typically used as pathways, however, pathways can be established using a PC dial-in

connection as well (STU-III or other modem and a PC). Large GCCS sites, such as MARFORPAC, generally operate at a data rate of 512 kbs. MSCs, Bns, and Sqdns generally operate at a minimum data rate of 56 kbs. GCCS can be provided to users in a tactical setting using various transmission paths as long as the minimal data rate of 56 kbs is met. GCCS is provided as an application service resident on the Secure Internet Router Protocol Network (SIPRNET).

Crypto Reqs: Network Encryption Systems (NES) are used in support of fixed garrison sites and are connected to the T1/T3 backbone. KG-194s are used in tactical environments or for garrison units not connected using NES-T1/T3 architecture. KG-194s are capable of operating at data rates of 56 kbs or higher. GCCS, to include GCCS-T, must be connected to the SIPRNET or a secure Local Area Network (Secure LAN).

Normal Locations: GCCS sites are located at various levels of the operational chain of command; national, theater, Joint Task Force (JTF), and supporting groups. At the national level, GCCS is used by the National Command Authorities (NCA), the National Security Agency (NSC), the Joint Chiefs of Staff (JCS) and the service headquarters. At the theater level, GCCS is used by the warfighting Commanders in Chiefs (CINCs) and their subordinate commanders. At the JTF level, the designated JTF commander and his subordinate commanders are the primary users of GCCS. The supporting group level includes the supporting CINCs (TRANSCOM, SPACECOM, etc.) and other U.S. government agencies such ads the Central Intelligence Agency (CIA), the Federal Bureau of Investigation (FBI), and the Federal Emergency Management Administration (FEMA). Additionally, GCCS services, through liaison cells, can be provided to coalition partners, United Nations (UN) representatives, and Non-government Organizations (NGOs) during peace keeping or humanitarian operations. Of the 620 worldwide GCCS sites, the USMC has 25 remote sites located at major command echelons. Currently, there are 221 GCCS user terminals in use throughout the Marine Corps.

Information Managed: GCCS, through the COE, is able to manage information along various core functional areas. These core functions, designated by the CINCs, include, but are not limited to, the following: crisis and deliberate planning; force deployment; unit positions; force status; intelligence; fire support; personnel; air operations; logistics; force deployment; and, narrative information.

Products Created: GCCS, in and of itself, does not create a specific GCCS product such as a GCCS display or GCCS report. What it does create however, is the COE in which the COP is developed. GCCS facilitates the rapid, near-real time, development and dissemination of such products as Joint Maritime Command Information System (JMCIS) displays, Time Phase Force Deployment Data (TPFDD), etc. As previously stated, information sharing is conducted using various stand-alone operational systems tied together using the GCCS COE. This shared information can then be displayed on both GCCS and stand-alone system terminals.

Lead Service/Contractor: DISA has been designated as the lead service by the Chairman of the JCS with oversight authority vested in the JCS J6V. Multiple contractors have been, and continue to be, involved in the development, fielding, maintenance, and refinement of GCCS. Science Application International Corporation (SAIC) provides contract support at the Marine Corps' 25 remote sites. The Inter-National Research Institute (INRI) is responsible for integrating mission application software segments.

Current Fielding Status: As previously stated, 221 SunSPARC 20 suites have been fielded Marine Corps wide as of August, 1998. DISA anticipates completing fielding to all designated DoD commands and agencies by year 2003. Concerning software fielding, version 2.2 was replaced by version 3.0 in the spring of 1998. Once approved and implemented, version 4.0 will replace 3.0 and be used to further push GCCS down to the lowest level of command. 4.0's "PC solution will enable commands to use any PC capable of operating in a UNIX or Windows NT environment as a GCCS terminal.

Known Problems: There are five major problem areas associated with GCCS: system capability and synchronization; cross service integration; security; coalition operations; and, system misconceptions. The first problem area, system capacity and synchronization, stems from the architecture's inability to allow for more than one database to be accessed and used at a given time. This has resulted in a need to upgrade database capability

and reduce the number of major database sites to a lower number (currently nine) in order to facilitate system synchronization. Second, a minimal yet persistent level of service parochialism exists in regards to software development and licensing, acquisition processes, and operator and administrator training. Greater coordination among services, driven by J6, will alleviate this problem over time. Third, the biggest threat to the systems security is an enemy's ability to cause GCCS server shut down through "packet bombardment" at NES connections. The use of fire walls and other measures will lessen the likelihood of enemy information warfare practices. Fourth, interoperability with coalition forces poses several problems in regards to both security and architectural design. This can be overcome using various means of sanitation of information shared with coalition forces or by providing GCCS liaison cells to coalition partner staffs. The fifth and final problem area relates to misconceptions about GCCS capabilities and the assumption that it provides real-time information. When GCCS was first fielded in 1994, commanders were not briefed on the systems evolutionary developmental process. Many believed it was already capable of providing all services it was being designed to provide. GCCS received mixed reviews when it was not capable of meeting these expectations. Today, many commanders believe GCCS provides real-time information when it can currently only provide near-real time information. This capability will not be realized until the various stand-alone functional systems tied into GCCS and GCCS operating segments are designated DIICOE Level 8 compliant. These problems will be alleviated as GCCS continues to mature.

Point(s) of Contact: USMC POC: GySgt Tolliver, BSFT, MCCDC at Comm (703) 784-5156 or DSN 278-5156 or e-mail www.mstp.quantico.usmc.mil. DISA POC: Maj Allsbrook at Comm (703)-607-40609 or DSN 327-4060. J6V POC: LtCol Thompson at DSN 227-1209 and DSN FAX 227-4937.

DIICOE Compliance Rating: DIICOE compliance levels were developed to support the creation and evolutionary development of the GCCS architecture. Platform hardware, for both potential GCCS servers/workstations and stand-alone functional operational system, application software, and API software must meet various levels of DIICOE compliance before being added to GCCS. Once added, hardware and software will be refined until they reach full compliance (DIICOE Level 8). There are eight levels of DIICOE compliance. These levels are listed below from Level 1 (lowest) to Level 8 (highest):

Level 1: Standards Compliance

Level 2: Network Compliance

Level 3: Workstation Compliance

Level 4: Bootstrap Compliance

Level 5: Minimal COE Compliance

Level 6: Intermediate Compliance

Level 7: Interoperable Compliance

Level 8: Full Compliance

Internet: http://spider.osfl.disa.mil

Updated by: Capt Roy H. Delaney Jr., USMC, CCSC-99.

  

Global Command and Control System – Maritime

(GCCS-M)

Primary Purpose: GCCS is mandated by the DoD and is the sole Command and Control (C2) Automated Data Processing (ADP) system. GCCS provides a seamless Naval Forces C41, to include MAGTF C4I, capability from the JTF to the Regiment and is anticipated to extend down to the Battalion. GCCS integrates information from all C2 functional areas. GCCS is an open ended architecture system consisting of servers, work stations, routers, hubs, and encryption devices. GCCS is located at both fixed and mobile locations.

Sub-Functions: GCCS-M (Afloat), GCCS-M (Ashore), GCCS-M (OBU/OED), GCCS-M (Tactical Mobile)

Equipment Reqs: Currently UNIX system, migrating to Windows NT based platform. UNIX systems and Windows NT systems are interoperable.

Connectivity Reqs: Uses IP routing over the Secret Internet (SIPRNET). Typically SHF SATCOM. Can use UHF and HF.

DIICOE Compliance Rating: Level 6 (anticipate rating of 7 in near future).

Crypto Reqs: No external equipment required. Uses SIPRNET

Normal Locations: US and NATO CINCs, US Naval Installations, US ships, Marine Corps units down to Regiment level.

Information Managed: TCO, IAS, AFATIDS, JOPES, CTAPS, JOTS, NWSS, FHLT, OSS, TSC, STT, NIPS, TFCC, ACS, EWCM, POST, ATP, FTAS, ASCOMM, ASWOC, ATOS, MAST, MOCC, RMAST, MICFAC, OSIS

Products Created: An integrated common operating picture afloat and ashore.

Lead Service/Contractor: Lead service is US Navy (PMW 171 (SPAWAR)), lead contractor is Enry.

Current Fielding Status: US and NATO CINCs, 16 shore support locations, 28 force level ships, 197 unit level ships, and Marine Corps to Regimental level.

Known Problems: Currently not interoperable with the US Army’s GCCS-A. A fix is currently being developed.

Point of Contact: Capt Gehl, USN, Comm: (619) 537-0264,

e-mail: gehlm@spawar.navy.mil

Internet: http://jdms.spawar.navy.mil/JDMS/index.htm

Updated by: Capt Daniel L. Paris, USMC, CCSC-99.

 

Global Command and Control System - Army

(GCCS-A)

Primary Purpose: The Global Command and Control System - Army (GCCS-A) will provide a single seamless command and control system built around the Joint Common Operating Environment (JCOE) and is being integrated with the Department of Defense Global Command and Control System (GCCS). This integrated acquisition strategy endures software and technology reuse and eliminates duplication among intra and inter-service command and control systems. Integration will be partially achieved from the "best of breed" process as GCCS-A and GCCS share and reuse software modules. GCCS-A is a fundamentally GCCS with additional ARMY functionality.

Sub-Functions (Applications):

Global Status of Resources and Training System (GSORTS)

Joint Operations Planning and Execution System (JOPES)

Common Operating Picture (COP)

GCCS-A can access all other functions of GCCS in a read only mode

Equipment Requirements: UNIX based servers working with UNIX workstations and Pentium based PCs. All current terminals are PC based and operate on a Windows NT environment.

Connectivity Requirements: Ethernet (TCP/IP) client server environment. T1/T3 backbone

Crypto Requirements: Dependent upon individual systems. Crypto is only required to reach the SIPRNET access point

Information Managed: Applications manage information at the MACOM level

Products Created: Common Operating Picture (COP); downloads JOPES information

Lead Service/Contractors: Army

Current Fielding Status: Delivery 1 system fielded. Delivery 2 currently being fielded in Korea. Delivery 3 will consolidate aspects of 1 & 2. Delivery scheduled for early FY 00.

Known Problems/Challenges: System complexity. Shortage of 74B’s with the appropriate skill identifier. No dedicated training plan for users.

DIICOE Compliance Rating: Level 5.

Point of Contact: William Smith, Product Manager, DSN 656-5249, comm (703) 806-5249. Tony Hauschilld, GCCS-A System Manager Project Rep, DSN 552-4545, comm (913) 684-4545

Internet: http://www.stccs-home.army.mil/wsdocs/stccs/gccsa.htm

Updated by: CPT James S. Clifford V, USA, CCSC-99.

 

 

Global Combat Support System

(GCSS)

Primary Purpose: To provide the joint warfighter with focused initiative to accelerate the delivery of improved combat support capabilities by integrating DOD-wide Service/Agency sponsored Combat Support Systems (logistics, medical, finance, personnel, etc).

Sub-Functions: Electronic Commerce/Electronic Data Interface (EC/EDI) is the availability to make electronic transactions utilizing the DISN SIPRNET/NIPRNET

Equipment Reqs: P/C with a secure modem or not if access is below the SECRET level (NIPRNET).

Connectivity Reqs: Secure path-system classified as SECRET (SIPRNET), system applications that are integrated under GCSS will be DII/COE compliant. GCSS uses the DISN connectivity.

Crypto Reqs: KIV-7, STU-III, Secure modem

Normal Locations: Currently being tested at DISA Defense System Testing Facility

Information Managed: GCSS is an automated data base system used to assist functional users (Medical, Logistics, etc) and specifically JTF commanders with combat support information to plan a mission. This information is used for joint or service mobilization/deployment contingencies, as well as readiness planning.

Products Created: JTAV/Joint Theater Asset Visibility (available logistic assets and locations); Weapons System Configuration Management (available weapons and life cycle of weapons systems); Finance (disbursements utilizing EC/EDI); Medical (patient tracking); other combat support systems are being tested for interoperability under GCSS.

Lead Service/Contractor: J-4 has the overall management lead for this system. DISA along with the GCSS project office are currently working on the engineering and fielding aspects of GCSS

Current Fielding Status: System hardware currently being updated for Y2K compliance and version 3.2 is being tested at the DSTF (Defense Services Test Facility). 1998 was the first year that this program was fully funded and 10/99 is the date scheduled for fielding to respective units/agencies.

DIICOE Compliance Rating: Level 5 while in testing, final:Level 8.

Point of Contact: GCSS Project Office = LTC Bouie or Mrs. Angela Jackson, DSN: 761-0394 COMM: 703-681-0271.

Internet: http://www.disa.mil/line/gcss.html

Updated by: CPT Thomas J. Addyman, USA, CCSC-99.

 

Ground Mobile Forces

(GMF)

Network Planning Prototype

(NETPLAN)

Primary Purpose: To assist the planning and implementation of tactical and strategic satellite networks.

Sub-Functions: Produces deployment packages, Satellite Access Requests (SAR), Tactical Satellite Signal Processor (TSSP) and Low Rate Multiplexer (LRM) programming sheets.

Equipment Reqs: 486 computer with 16MB RAM, 25MB hard disk space.

Connectivity Reqs: In normal office or field environment requires computer with printer. Can be interfaced with the Defense Satellite Communications System (DSCS) Network Planning Software used at Regional Satellite Control Centers (RSCC) and the DSCS OC (Operation Centers).

Crypto Reqs: None, unless producing networks above UNCLASSIFIED. This system can be used on workstations/LANs accredited up to SECRET.

Normal Locations: Signal Battalion/Brigade engineer shops.

Information Managed: Mission requests through GMF stations. Terminal data, antenna data, locations (lat and long), satellite data, DSCS OC controller details, network routing, LRM and TSSP configurations, and user configurations.

Products Created: Network diagrams, map of terminal locations, SARs, TSSP and LRM programming sheets.

Lead Service/Contractor: Project initially sponsored by the Army; Mitre Corporation was responsible for development. Contract is now held by CECOM.

Current Fielding Status: Version 2.2.3 has been distributed to all services.

Known Problems: (1) Does not include data entry into Defense communication System (DCS) entry sites for strategic-tactical interface. (2) Can only configure point-to-point links for AN/TSC-143 networks due to the lack of TSSP data. (3) Not used

effectively at RSCC because current version of DNPS, Version 10, is not interoperable with NETPLAN and the Plain Language Addresses.

DIICOE Compliance Rating: Level 5.

Point of Contact: CPT Butler (RA Sigs), 11th Signal Brigade DSN 821-1457/1444 COMM (520) 533-1457/1444

Updated by: CPT Kevin P. Romano, USA, CCSC-99.

  

Global Status of Resources and Training System

(GSORTS)

SYSTEM NAME HAS BEEN CHANGED TO RAS

Primary Purpose: Internal management tool directed by CJCS reflecting the readiness level of selected units’ in terms of training, equipment, and personnel against the level required to undertake assigned missions. Mission will be assumed by GCCS officially on 31 Dec 1998.

Sub-Functions: Provides commanders, auditors, and congress with a semi-objective assessment of units’ ability to execute full wartime missions. Not a true performance appraisal.

Equipment Reqs: Marine Corps uses front-end software called GOMERS requiring a PC with minimum of 486 66MHz processor, 8MB RAM and 750 MB hard drive to create unit reports. Other services have unique requirements for the creation of unit reports.

Connectivity Reqs: Unit report submission requires access to AUTODIN message center or SIPRNET. Access to GSORTS database is achieved only through SIPRNET.

Crypto Reqs: SIPRNET

Normal Locations: Service HQs, CINC HQs, JCS, NCA, combat support agencies.

Information Managed: Information related to the status of a unit’s location, personnel, training, and equipment.

Products Created: None. Provides CINCs with an orientation to the status of forces and is a key tool used in the Joint Monthly Readiness Review and by the Senior Readiness Oversight Council.

Lead Service/Contractor: Joint Sponsored.

Current Fielding Status: All services currently utilize as directed by CJCS. Follow on system, RAS (GCCS), to be fielded in GCCS during FY-99.

Known Problems: Batch processing (30-day cycle) and service inconsistencies degrade accuracy/usefulness of information. RAS addresses these in allowing real-time updates to database and creating uniform reporting procedures throughout the DOD.

DIICOE Compliance Rating: Level 6.

Point of Contact: Bob Bovee, GSORTS Development, DISA, Pentagon (BF715) Washington DC, 20301, Comm (703) 695-0492, DSN 225-0492, FAX 223-3580, email boveer@ncr.disa.mil

Updated by: Capt Baron A. Harrison, USMC, CCSC-99.

 

 

Global Transportation Network

(GTN)

Primary Purpose: U.S. Transportation Command's (USTRANSCOM) Global Transportation Network (GTN) gives its customers located anywhere in the world a seamless, real-time capability to access -- and employ -- both classified and unclassified transportation and deployment information. GTN is an automated command and control information system that supports the family of transportation users and providers (both DoD and commercial) by

providing an integrated system of intransit visibility information and command and control capabilities. GTN collects and integrates transportation information from selected transportation systems. The resulting information is

provided to the National Command Authorities (NCA), CINCs,

USTRANSCOM, its component commands, and to DoD customers to

support transportation planning and decision making during peace and war. Automated command and control information system used by DoD, US. Transportation Command (USTRANSCOM) and its Transportation Components Commands (TCCs) to provide global transportation management.

Sub-Functions: Four major capabilities: Intransit Visibility (ITV), Current Operations, Future Operations, and Patient Movement. Provides detailed common user air and surface movement visibility and intransit visibility by shipment, stock number, unit or passenger name in the logistics pipeline.

Equipment Regs: PC based, server is located at Scott AFB.

Connectivity Regs: TELNET Capability to Internet, MILNET, or DDN. Alternative, modem capability on each computer with 2400 baud or faster.

Crypto Regs: No external crypto required. Depends on connection.

Normal Locations: Client server at USTRANSCOM, Scott AFB. Worldwide clients.

Information Managed: Collects and integrates transportation information from selected Automated Data Processing (ADP) transportation systems on a recurring basis.

Products Created: Gathers transportation related data into a single integrated database that will provide intransit visibility and command and control capabilities to Defense Transportation System customers and providers of lift.

Lead Service/Contractor: Air Force DoD/Lockheed Martin.

Current Fielding Status: Version 2.2 in use with USTRANSCOM. Fully fielded. Additionally, 2.2 and future versions will be on the World Wide Web. 2.2 will be compatible with Netscape 3.0 or higher and Microsoft internet explorer 4.0 and higher.

DIICOE Compliance Rating: Level 3. Segments reach level 5 and 6.

Point of Contact: Col. Ronald Casey USAF, Program Director. GTN PMO, Scott AFB, IL. Phone#: DSN 576-2866 Comm (618) 256-2866, DSN 576-6273.

Internet: www.gtn.transcom.com

Updated by: Capt Todd L. McAllister, USMC, CCSC-99.

  

Intelligence Analysis System

(IAS)

Primary Purpose: Provides a modular, configurable , intelligence information collection, control, processing, and dissemination system that will allow using units to rapidly assess enemy situations and battlefield conditions. The IAS will use current versions of the Marine Air-Ground Task Force (MAGTF) Command, Control, Communications, Computers, and Intelligence (C4I) Software Baseline (MSBL), enhanced with Intelligence segments. The IAS may be deployed as either the IAS Suites, MEF IAS, or IAS workstations. The IAS Suites consist of two variants, V1 and V2. The V1 variant has two work stations while the VG2 has four workstations. IAS suites are Hewlett-Packard UNIX hardware. MEF IAS is a SUN SPARC and the Intelligence Operations Workstation (IOW) Workstation is an IBM Laptop Computer in a Windows NT environment.

Sub-Functions: Intelligence database management, situation maps, desktop publishing, Journal, workbook and message handler, electronic light table, and tactical collection management.

Equipment Regs: Marine Common Hardware Suite (MCHS) Class B Workstation: SUN SPARC for MEF IAS; HP Workstations for IAS Suites, and PC Laptops for the Windows NT IAS Workstations. File/Comm Servers, and Tactical Communications Interface Modules.

Connectivity Regs: STU III. 9600 baud or higher, AUTODIN Mode I/II, HF/VHF/UHF/SATCOM capable, Ethernet LAN with bridge router.

Crypto Regs: KY-58 Radio, KY68 (Telephone) KG-84 (KIV 7), Land Line/STU.

Normal Locations: USMC: MEFs, Divisions, Wings, FSSGs, MEUs, REGTs, MAGs, BNs, SQDNs.

Information Managed: Tactical Intelligence.

Products Created: Various Intelligence Reports, SITMAPS, and Overlays.

Lead Service/Contractor: USMC/Multiple.

Current Fielding Status: Being fielded throughout the FMF. IAS Suites fielding completed 2nd qtr FY 98. MEF IAS fielded to II MEF 4th Quarter FY 98. Units to be fielded to I and III MEF 2nd QTR FY 99. The IOW Workstations IOC is 1st QTR FY 99 with FOC in the 2nd QTR FY 99.

Known Problems: Does not integrate information with IOW and TCO.

DIICOE Compliance Rating: Not rated.

Point of Contact: MARCORSYSCOM, Maj Hubbs, (DSN) 278-2645.

Updated by: Capt Todd V. Bottoms, USMC, CCSC-99.

 

 

Integrated Computerized Deployment System

(ICODES)

Primary Purpose: Provide manual and automatic stow planning in a cooperative environment.

Sub Functions: Accommodates division size mobilization planning for distribution across an available fleet of ships using several different types of load out configurations (combat, preposition, exercise, tactical and administrative).

Equipment Requirements: A 486 or better system workstation with color monitor.

Connectivity Requirements: UNIX operating system. Software package is coded in C, C++, and CLIPS languages including PVM and AutoCAD requirements.

Crypto Requirements: None.

Normal Locations: All MTMC ports and terminal transportation brigades, MTMC Eastern and Western Areas, and MTMCTEA Headquarters.

Information Managed: Ability to simultaneously load up to four empty ships with cargo at one POE destined for one POD. Additionally, contains ship and cargo libraries, cargo marriage/ divorce capability, assisted stow template.

Products Created: Customized reports such as cargo manifests, hazardous cargo manifests, etc.

Lead Service/Contractor: Joint. Developed at California Polytechnic State University. Managed by TRANSCOM’s Military Traffic Management Command (MTMC).

Current Fielding Status: Replacing CODES in late 1998.

Known Problems: None.

DIICOE Compliance Rating: Not rated.

Point of Contact: Marty Lambert, DSN 761-3543, COMM: 703-681-3543. Email: LambertM@Baileys-EMH5.Army.Mil.

Updated by: CPT Neil K. Khatod, USA, CCSC-99.

 

Improved Emergency Message Automatic Transmission System

(IEMATS)

IEMATS system is being replaced by DMS

Primary Purpose: Provide Joint Staff and SIOP CINCs with automated Emergency Action Message (EAM) processing capabilities. Allows rapid message routes from the National Command Structure directly to CINCs. Possesses capability to preferentially route traffic at high precedence. i.e. Flash

Sub-Functions: None.

Equipment Reqs: Automatic Digital Network (AUTODIN) – Primary Route. Alternate routes include: Joint Chiefs of Staff Alerting Network (JCSAN), Air Force Satellite Communications (AFSATCOM), SCTIS, low frequency radio, and high frequency radio

Connectivity Reqs: AUTODIN

Crypto Reqs: KG-94/194 series encryption devices

Normal Locations: Located in Emergency Action Centers worldwide. Such as National Military Command Center and all CINC headquarters.

Information Managed: Emergency Action Message’s (EAM).

Products Created: EAM’s and reports.

Lead Service/Contractor: DISA.

Current Fielding Status: Deployed and operational. AUTODIN, the primary path for IEMATS, will be deactivated within the next few years and Defense Message System (DMS) will be activated. The exact configuration for how IEMATS will be used in relation to DMS has not been identified at this time.

Known Problems: None.

DIICOE Compliance Rating: Not rated.

Point of Contact: Mr. John Stoklosa, DISA, (703) 607-4020, E-mail: STOKLOSJ@NCR.DISA.MIL

Updated by: Capt Peter J. Dillon, USMC, CCSC-99.

 

Initial Fire Support Automated System

(IFSAS)

IFSAS system is being replaced by AFATDS FY99-00

Primary Purpose: Automated fire support command and control functions. Increases the efficiency of fire support available to the maneuver forces.

Sub-Functions: Technical and tactical fire direction, targeting, fire planning, and fire mission execution.

Equipment Reqs: AN/GYK-37 Lightweight Computer Unit (LCU) which can be reprogrammed to support AFATDS, Remington workstation. Tactical Communications Interface Modules (TCIM), ruggedized dot matrix printer, SINGARS.

Connectivity Reqs: VHF and HF single channel radio.

Crypto Requirements: Vinson family.

Normal Locations: USMC Artillery Fire Direction Centers(FDCs) at the battery, battalion and regimental level. USMC GCE Fire Support Coordination Centers (FSCC) and the MAGTF Force Fires Coordination Center (FFCC)at the MEU and MEF level. Additionally, the Direct Air Support Center (DASC) will maintain IFSAS. This system replaced the TACFIRE in heavy Army units and has completely automated the National Guard artillery units.

Information Managed: Conventional fire plans, target information, Fire Support Coordination Measures (FSCMs) and other control measures such as Forward Line of Troops (FLOT) and unit zones. Additionally, IFSAS manages ammunition and Fire Unit(AFU)data, Meteorological (MET) and survey data, and Fire Support Element (FSE) data.

Products Created: Artillery Targeting Intelligence (ATI), target lists, conventional fire plans, and mission fired reports.

Lead Service/Contractor: US Army/Litton Data Systems, Inc

Current Fielding Status: USMC Artillery Fire Direction Centers (FDC’s) at the battery, battalion and regimental level. USMC GCE Fire Support Coordination Centers(FSCC) and the MAGTF Force Fires Coordination Center (FFCC) at the MEU, MEF Forward, and MEF level. Direct Air Support Center (DASC).

This system replaced TACFIRE in heavy Army units and is augmenting Light TACFIRE in Army light units.

This system is currently being replaced by the Advanced Field Artillery System (AFATDS).

Known Problems: Poor hardware reliability. System is outdated before fully fielded. Software is not user friendly and requires extensive training. Graphics difficult to see and manipulate.

DIICOE Compliance Rating: Not rated.

Point of Contact: MARDET Fort Sill, Oklahoma.

Internet: http://hiway1.exit109.com/~fatds/index.shtml

Updated by: Capt Daniel C. Logan, USMC, CCSC-99.

  

Integrated Marine Multi Agent Command & Control System

(IMMACCS)

Primary Purpose: IMMACS is an experimental, object-oriented architecture that provides a common tactical picture and tactical decision aids for the Marine commander in the Enhanced Combat Operations Center (ECOC). It is the core of the Urban Warrior C4I decision-support system, providing ‘near’ real-time situation awareness (i.e., < 12 seconds) at all C2 access nodes.

Sub-Functions: Mapping aids, unit locations, IPB aids, decision support functions, message handling, data base "reachback".

Equipment Reqs: Currently the core system runs on a HP J210 Platforms. It is accessed by Win32 system using any web browser.

Connectivity Reqs: Requires access to a LAN on which core system is attached.

Crypto Reqs: None.

Normal Locations: Core system to be used in Urban Warrior Advanced Warfighting Experiment ECOC with access down to the squad/team level via laptops and Personal Digital Assistants (PDA).

Information Managed: Uses "object-oriented" technology to manage all objects/entities in the battlespace.

Products Created: Decision support aids/products for use by the force commander.

Lead Service/Contractor: USMC/California Polytechnic Institute CAD Research Center, San Luis Obispo, Ca

Current Fielding Status: Currently not fielded. Will be tested at Urban Warrior AWE. Future concept calls for fielding to all MEUs

Known Problems: To be determined

DIICOE Compliance Rating: Level 8.

Point of Contact: LtCol Durham, MCWL, (703)-784-1312

 

 

Joint Collection Management Tool

(JCMT)

Primary Purpose: All Source Collection Management.

Sub-Function: Combines functions of Collection Management Support Tools (CMST), Collection Requirements Management Analysis (CRMA), and Collection Requirements Management System (CRMS).

Joint Collection Management Tools (JCMT) is the DOD Intelligence Information System (DODIIS) migration system for all-source collection management. It provides tools for recording, organizing and tracking intelligence collection requirements for all intelligence disciplines.

JCMT provides automated support for a collection manager to review selected discipline reporting to determine whether existing data might satisfy the collection requirements. If acceptable data are not available, JCMT's various databases and platform/sensor models can be queried for data about asset capabilities and availability's.

Equipment Regs: The server software currently operates on SUN-UNIX SPARC 20, Ultra or higher-level platforms, although an Ultra 2 (for non-production center sites) is recommended. A JCMT server typically requires 256 MB of RAM and 12.6 GB of storage configured in three disk drives. A client should have at least 64 MB of RAM (128 MB is recommended) and 4.2 GB of disk space. Of course, the size of RAM and disk space as well as the number of users determines the system performance. The current version (Capabilities Package 1.0) uses the Solaris 2.5.1 operating system. It operates using the DODIIS Client Server Environment (CSE) Support Services (SS) 1.3. It also uses X Windows 11R5 and Motif 1.2.5 to support the Graphical User Interface (GUI) and Sybase 11 as the database management system (DBMS) (JCMT can support either Sybase 11.0.2 or 11.0.4).

Connectivity Regs: Communications Support Processor - High Order Language (CSP-HOL) Automated Message Handling System (AMHS) Defense Automated Warning System (DAWS) (for communications only; it is a legacy system to be incorporated into the Migration Defense Intelligence Threat Data System (MDITDS). In addition, JCMT can communicate via Simple Mail Transfer Protocol (SMTP) Message Exchange and File Transfer Protocol (FTP)

Crypto Regs: JCMT currently operates at the SCI level. Subject to funding and CRMB approval, JCMT applications, databases, interfaces, and models will be divided into secret collateral/ GENSER and SCI partitions in a future release. The Marine Corps has formally requested that a collateral version be built.

Normal Locations: Army divisions, corps, and echelon-above-corps MI brigades Navy carriers, amphibious assault, and command and control ships. Numbered Air Forces. Marine Expeditionary Forces (MEF), divisions, Marine air wings (MAW), Force Service Support Groups (FSSG), and Marine Expeditionary Units (MEU).

In addition, most special operating forces of all services will receive JCMT capabilities through JDISS.

Information Managed: JCMT provides tools to assist the collection manager to allocate collection requirements to collection assets and to plan collection strategies. These tools include feasibility models, status matrices, look-ahead tools, schedule timelines, and track and coverage displays.

Products Created: JCMT supports the collection manager to develop collection plans and generate tasking and request messages. JCMT parses over 30 collection management messages into its databases; it can also store any message type for user review. JCMT also accesses numerous technical references and national SIGINT and HUMINT standing requirements. Direct access to the MASINT standing requirements will be added to JCMT later.

Lead Service/Contractor: U.S. Army

Fielding Status: JCMT (either CP 1.0 or an earlier version) resides at approximately 50 sites. It will eventually be installed at over 230 sites worldwide.

Integration of JCMT is planned for the All-Source Analysis System (ASAS) - Army Combat Intelligence System (CIS)(of the Theater Battle Management Core System (TBMCS)) - Air Force Global Command and Control System - Maritime (GCCS-M) –Navy.

PM JCMT had also planned to incorporate JCMT into the Intelligence Analysis System (IAS), which the Marine Corps uses. However, because IAS will be incorporated in GCCS-M (and to be called the Marine Air Ground Task Force (MAGTF) Command, Control, Communications, Computer, and Intelligence (C4I) Segment), Marines will be able to access JCMT functionality through GCCS-M.

DIICOE Compliance Rating: Not rated.

Point of Contact: PM is Maj John Quigg at Comm: (703) 275-8024.

Internet: http://www.asaspmo.belvoir.army.mil/jcmt/jcmthome.htm, http://jcmt.clar.dia.ic.gov/jcmt/, ftp://136.196.109.4. SIPRNET http://206.37.11.3.

Updated by: Capt David B. Turcotte, USMC, CCSC-99.

 

Joint Defense Information Infrastructure Control System - Deployed

(JDIICS-D)

JDIICS-D system has been replaced by JNMS

Primary Purpose: Provide a standardized tool for deployed joint task forces to manage their networks in the Defense Information Infrastructure Common Operating Environment (DIICOE)

Sub-Functions: Automated, joint communications planning and management tool, Integrates Government Off-the-shelf (GOTS and Commercial Off-the-shelf (COTS) software tools running on both UNIX and NT platforms.

Equipment Requirements: FY-98 Version UNIX-Processor, Sun Sparcstation Ultra or HP Workstation Operating system, Solaris 2.5.1 or HP-UX 10.20 Hard Drive; 4 GB RAM; 256 MB Additional CD ROM or tape drive; NT Server- Processor 233 MHz Pentium; Hard Drive 2 GB; RAM 32 MB; Additional Ethernet LAN Adapter, CD ROM, ZIP drive or equivalent (100 MB).

FY-99 and Beyond: NT Server- Processor 233 MHz Pentium; Hard Drive 9 GB with expansion capability; RAM 256 MB; Additional Ethernet LAN Adapter, CD ROM, ZIP drive or equivalent (100 MB), tape drive; Additional Equipment HP Laserjet printer 2 LAN probes and 1 WAN probe 3 "Y" cables

Software Used: COTS Apps: HP Openview Network Node Manager, Nvision Graphical Web into HP OV NNM, CiscoWorks for Openview, Net metrix, Remedy ARS, Oracle 7 RDBMS, MS Office, Netscape, WinnDD Server.

GOTS Apps: New-TNAPS+ for Solaris with enhancements, GSOC interface module and SNMP Agents for TTC-39, CDS/SMU, FCC-100 and IDNX, existing Joint Spec Man Sys/W, UHF and SHF Netplan, RBECS, ASPECTS, Pbook II, and Speed.

Normal Locations: Deployed sites.

Information Managed: Network functions and status.

Products Created: Status reports, trend analysis.

Lead Service/Contractor: Defense Information Systems Agency.

Current Fielding Status: Demonstrated at ROVING SANDS 97, JWID 97, and Joint User Switch Exercise (JUSE) 97.

Known Problems: None.

DIICOE Compliance Rating: Level 5.

Point of Contact: LTC Chris Wagner, DISA, Comm (703) 735-3264, wagnerc@ncr.disa.mil. Mr Dunn, Mitre Corp. Comm (703) 883-6382, edunn@mitre.org.

Internet: JDIICS web site: http://jdiics.esinet.org/jdiics-d/

Updated by: Capt Larry Wade Norman, USAF, CCSC-99.

 

Joint Deployable Intelligence Support System

(JDISS)

Primary Purpose: National and Theater level intelligence support to deployed JTF.

Sub-Functions: Electronically extends intelligence products to tactical users. Provides on-demand broad bandwidth intelligence communications connectivity including imagery and electronic intelligence (IMINT and ELINT) database processing. User to user chat mode and high resolution imagery printing/reproduction. Provides data connectivity between users at the Sensitive Compartmented Information (SCI) or SECRET collateral levels. SCI terminals are not legally able to forward their information to collateral terminals.

Equipment Reqs: UNIX based Sun Sparc Terminals and associated peripheral equipment. Both COTS/GOTS hardware and software.

Connectivity Req: SCI systems require access to JWICS. Secret collateral systems require access to SIPRNET.

Crypto Requirements: SCI JDISS suite: none. The path must be encrypted SCI. Secret collateral JDISS suite: May use STU-III or other SECRET accredited equipment.

Normal Locations: All major DOD installations, CINC HQ, MEF HQ, Marine Division/Wing HQ, CVN and deployed MEU Flagships serving as the Flag all have JDISS. Other military and civilian organizations will also utilize this suite.

Information Managed: Provides access to external IMINT and ELINT databases.

Products Created: Tailored intelligence products (hardcopy imagery prints, custom overlays, access to IntelLink).

Lead Service/Contractor: Joint System. General Defense Intelligence Program (GDIP) sponsored.

Current Fielding Status: Not a traditional acquisition item. Hardware and software both COTS/GOTS acquired.

Known Problems: Most terminals located in Sensitive Compartmented Information Facilities (SCIFs) or within the Joint Intelligence Center (JIC). Coordination required for access to the JDISS terminal. Bandwidth accessibility with deployed forces is a limiting factor. 8 or 16 Kbps limits the speed at which imagery may be transferred. JDISS version 3.0 will be Y2K compliant when released. Currently fielded JDISS workstations are in the process of being patched. 2 patches and 7 new releases will make all JDISS systems Y2K compliant.

DIICOE Compliance Rating: JDISS 2.0 and stand alone workstations are DIICOE level 5 or better. The portions of JDISS that are segments of GCCS and GCCS-M are DIICOE level 7 or better.

Point of Contact: LCDR Jim McDougall (PMO), phone (301) 669-5172, e-mail: jmcdouga@nmic.navy.mil. JDISS helpline: security@jdiss-pmo.nmic.ic.gov,

cisso@jdiss-ops.nmic.ic.gov

Updated by: Capt Deirdre A. Houde, USAF, CCSC-99.

  

Joint Flow and Analysis System for Transportation

(JFAST)

Primary Purpose: JFAST is a multimodal transportation analysis model designed for the U.S. Transportation Command (USTRANSCOM) and the Joint Planning Community. JFAST is used to determine transportation requirements, perform course of action analysis, and project delivery profiles of troops and equipment by air, land, and sea.

Sub-Functions: The Notional Requirements Generator (NRG) is a subset of JFAST providing rapid course of action development and estimation of transportation feasibility when Time-Phased Force and Deployment Data (TPFDD) does not exist or its insufficient for conducting gross transportation analysis. The NRG allows selection of major forces to be deployed, specifies approximate time-phasing, identifies combat support/combat service support and develops a sustainment wedge for forces being deployed.

Equipment Reqs: JFAST version 6.3.4 operates on a PC in Windows 3.1. JFAST version 7.0.89 operates on Windows 95 or Windows NT.

Connectivity Reqs: JFAST operates as a stand-alone workstation, in a client-server application, or interfaces with the Global Command and Control System (GCCS).

Crypto Reqs: No internal Crypto. User determines based on data.

Normal Locations: AF Wargaming Center, AF/XOOC, ALCOM/J43, AMC/DOXP, AMCCOM, Armed Forces Staff College, Army/Strategic Mobility Division, Combined Arms Combined, Contingency Wartime Planning Course, Defense Fuel Supply Center, Defense Nuclear Agency, DIMA CELL, DISA, GTN, HQ 21st TAACOM, HQ USA CASCOM, HQMC/LPO, I Corps, Institute for Defense Analyses, Joint Staff/J4-LRC, JOPES Training Organization, Logistics Evaluation Agency, Louisiana Maneuvers Task Force, MSC, MTMC, MTMCTEA, NDU War Gaming & Simulation Center, Office of Aerospace Studies, Strategic Sealift Division, Tactical Training Group Atlantic, US Army War College, US Forces Korea/FKJ4 & FKJ5, USACAC, USAF, AFSAA/SASM, USAOMMCS, USAREUR, USARPAC, USCENTCOM, USACOM, USPACOM, USEUCOM, USFORSCOM, USSOCOM, USSOUTHCOM, and USSSTRATCOM.

Info Managed: Input primarily from JOPES in the form of OPLAN TPFDDs and reference files. Additional data provided by transportation operating commands of AMC, MSC, and MTMC. Functions are trans analysis, data facilities, utilities, and NRG.

Products Created: Data models origin out loading, transit to POE, throughput constraints at POE, airlift and sealift to POD, and throughput constraints at POD. Focus on analysis and identification of transportation bottlenecks. Presents graphic and tabular output showing impact upon transportation resources, vehicles, and ports.

Lead Service/Contractor: Functional OPR is USTRANSCOM/TCJ3-OP.

Current Status: In use within all services and several support agencies of DOD.

DIICOE Compliance Rating: Level 5.

Point of Contact: Project manager is USTRANSCOM/TCJ3-OP, DSN 576-6898. Program developer is Mr. Brian Jones, comm (423) 974-8405.

Internet: http://jfast.prg.utk.edu.

Updated by: CPT David A. Thomas, USA, CCSC-99.

 

 

Joint Maritime Command Information System

(JMCIS)

System status: See Global Command and Control System-Maritime (GCCS-M).

Updated by: Capt Dee S. Rosser, USMC, CCSC-99.

  

Joint Network Management System

(JNMS)

System status: New system to replaced JDIICS-D. See JDIICS-D for details..

Updated by: Capt Larry W. Norman, USAF, CCSC-99.

  

Joint Operations Planning and Execution System

(JOPES)

Primary Purpose: JOPES is the integrated, joint, conventional command and control system used by the Joint Planning and Execution Community (JPEC) to conduct joint planning, execution, and monitoring activities. JOPES supports senior-level decision-makers and their staffs at the National Command Authority (NCA) level and throughout the JPEC. Combatant commanders use JOPES to determine the best Course of Action (COA) to accomplish assigned tasks and direct the actions necessary to accomplish the mission. JOPES is a system that includes people, procedures, policies, communications, and supporting Information System (IS) software.

JOPES is a continuously evolving system that is being developed through the integration and enhancement of earlier planning and execution systems: Joint Operation Planning System and Joint

Deployment System. It provides the foundation for conventional command and control by national-and theater-level commanders and their staffs. It is designed to satisfy their information needs in the conduct of joint planning and operations. JOPES includes joint operation planning policies, procedures, and reporting structures supported by communications and automated data processing systems. JOPES is used to monitor, plan, and execute mobilization, deployment, employment, and sustainment activities associated with joint operations.

Sub-Functions: None.

Equipment Reqs: (Client Servers) SUN Sparc 5 workstations /IBM compatibles and X-terminals that support windows and HTML browser. (Database Servers) Sparc 20 or Sun 1000/2000 computers.

Connectivity Reqs: Dedicated path able to accommodate 64Kbs. Database servers require SIPRNET path to GCCS hardware.

Crypto Reqs: Crypto required for access to SIPRNET and GCCS. Software is unclassified.

Normal Locations:

USAF/Air Combat Command (ACC)

USN/LANT/Atlantic command (ACOM)

USA/United States Army Europe (AREUR)

USA/United States Army Pacific (ARPAC)

USAF/U. S. Central Command (CENT)

United States European command (EUCOM)

USA/Forces Command (FORCE)

Military Traffic Management Command

National Military Command Center (NMCC)

USAF/Pacific Air Forces (PACAF)

United States Southern Command (SOUTH)

U. S. Strategic Command (USSTRATCOM)

U. S. Transportation Command (USTC)

Marine Forces Atlantic (MARFORLANT)

USFK (Yongsan)

Information Managed: Operations Plans (OPLANS), courses of action, deployment operations containing status, concept, scope and detailed time-phased movement requirements for forces and sustainment.

Products Created: OPLAN's and status reports for deployment information.

Lead Service/Contractor: DISA/SRA Corporation.

Current Fielding Status: Existing Legacy System. JOPES is a continuously evolving system that is being developed through the integration and enhancement of earlier planning and execution systems: Joint Operation Planning System and Joint Deployment System.

Known Problems: None.

DIICOE Compliance Rating: Level 5.

Point of Contact: DISA: JOPES Office (Program Management) D-3224) SFC Spurgin, DSN 223-4438/40.

AMC PROGRAM MANAGER, Capt Dominick Ortiz, AMC/SCPC, (618)256-2217 DSN:576-2217, Dominick.Ortiz@scott.af.mil

Updated by: Capt Robert L. Leary, USAF, CCSC-99.

  

Joint Service Imagery Processing System

(JSIPS)

Primary purpose: National imagery analysis support to Marine Forces and other service organizations as directed. Note: only one operational unit currently exists and is located at the Marine Corps Imagery Support Unit, 1st INTEL Battalion, I MEF, Camp Pendleton, CA.

Sub-Functions: Exploit and analyze all-source national imagery to produce Initial Imagery Reports (IIRs) and Secondary imagery Reports (SIRs). Reports are either a quick look or "second" more

in-depth look. Receives sensor data through a Receive Location (RL) data link and processes digital data into imagery. Can archive and format data and link with local area networks. Features electro-optical, radar, and infrared imagery database, softcopy exploitation, voice, and data communications capability. Manage, update, and maintain various national imagery databases.

Equipment Req: Requires power source, communications support for operation.

Equipment Description: Modular design, configured in 11 10ft X8ft deployable shelters with a communication van and a maintenance van. Can deploy on one C-5 and one C-141. Contains 11 workstations for exploitation activities.

Connectivity Req: Designed to be co-located with an RL (Note: only 13 RLs exist in DOD). Satellite communications for RL connectivity required. Communications requirements for RL and JSIPS include one 1.544 Mbps (T-l) simplex (receive only) link and one 56 Bps full duplex link. Other communications include a 2.4 Kbps, four wire, full duplex dedicated circuit, two class A phone lines and four class B lines.

Crypto Req: Existing hardware. KIV-7, KG-84, and KY-68 for SCI and GENSER data/voice communication.

Products Created: Capable of producing hardcopy imagery in various sizes and scales for utilization during the planning process. Enables "demand pull" by MEF major subordinate commands (MSC’s) by posting imagery on organic 5-D server accessible via SIPRNET. Provides search query via MCISU GENSER Secret webpage.

Lead Service/Contractor: Joint system/E-Systems Inc. Garland Division

Normal Locations: Within the Marine Corps, the only operation system is at the MCISU aboard Camp Pendleton, CA.

Current Fielding Status: Both the RL and JSIPS are scheduled for upgrade during 2nd Quarter FY-99. This upgrade will reduce the footprint and logistical support requirements for the two systems. Version 3.1 current.

Known Problems: Not capable of high volume production of hardcopy products. Relies primarily on electronic and digital dissemination of products. Customers must have SIPRNET connectivity to access web based softcopy products. Large logistical support needed. Equipment is moveable, but not mobile. Heavy communications connectivity required. Tasking competition with other elements of DOD for imagery support.

DIICOE Compliance Rating: Under evaluation as of publication of this document.

Point of Contact: Marine Corps Imagery Support Unit, Camp Pendleton, CA. Comm: 619/725-6743/2068 DSN: 365-6743/2068 FAX: (Comm) 619/725-6137 (DSN) 365-6137

Updated by: Capt Scott E. Camden, USMC, CCSC-99.

 

 

Joint Tactical Information Distribution System

(JTIDS)

Primary Purpose: Secure anti-jam digital data and voice communications system for theater, air, ground, and naval forces.

Sub-Functions: Communication, navigation, and identification (CNI) systems.

Equipment Reqs: JTIDS terminals plus modification systems to onboard data processing systems to generate and display JTIDS message formats.

Connectivity Reqs: JTIDS terminal and self-contained L-band radios.

Crypto Reqs: KGV-8 or COMSEC/TRANSEC DS-101 Hybrid (CDH).

Normal Locations:

USAF: Airborne Warning and Control System (AWACS), Rivet Joint aircraft, Joint Surveillance Targeting and Reconnaissance (JSTARS) aircraft, Airborne Command, Control, and Communications (ABCCC) aircraft, Air Operations Centers (AOC), Modular Control Equipment (MCE), and limited F-15’s.

USMC: Tactical Air Operations Modules (TAOM)

USN: F-14D and E2C aircraft, aircraft carriers, Aegis class cruisers, destroyers, and LHD/LHA’s.

USA: Forward Area Air Defense (FAAD) C2I sites.

Allies: UK AWACS and Tornado aircraft, France AWACS aircraft, NATO Control and Reporting Centers (CRC).

Information Managed: Surveillance data including air, ground, and naval track file information; intelligence information; friendly positions and status; and digital voice communications.

Products Created: Real-time situational awareness of integrated air/ground picture from all platforms in theater.

Lead Service/Contractor: USAF/GEC Marconi and Rockwell Collins.

Current Fielding Status: Older class terminals in operation in US, NATO AWACS, and CRCs. New Class II terminals being fielded currently by all services.

Known Problems: Size requirements may delay integration into tactical aircraft and TAOM/MCE.

DIICOE Level of Compliance: Not rated.

Point of Contact: Maj Pat Cox, TBMCS/JTIDS, Hansom AFB, Maine, (781)377-3100 or Capt Dayle L. Wright, TAOM Project Officer, MARCORSYSCOM, DSN 278-2645 ext. 2543. Web info at: http://www.link16.nosc.mil

Updated By: Capt Curtis Carlin, USMC, CCSC-99.

 

Joint Universal Lessons Learned System

(JULLS)

Primary Purpose: An after-action report (AAR) software package allowing users to generate joint lessons learned for the JULLS data base. This data base is distributed semiannually to the Commanders in Chiefs (CINC) of all unified commands, the services and the combat support agencies. Improves CINC's warfighting capabilities by taking advantage of LL's from rea-world operations and exercises.

Sub-Functions: 1. Joint After-Action Reporting System (JAARS). A set of procedures and formats for AAR's which covers all exercises and operations. 2. Remedial Actions Projects Program (RAPS). Identifies significant shortfalls and problems from AAR's. Tracks the identified shortfalls or problems and corrective action to completion or validation.

Equipment Reqs: The software is a MS-DOS IBM-compatible computer program.

Connectivity Reqs: Stand-alone computer software. AAR's are submitted through the CINC's to the Evaluation and Analysis Division (EAD). Operational Plans and Interoperability Directorate (J-7). AAR's must be submitted on electronic media (i.e. disk, e-mail) via mail, courier, or Global Command Control Systems (GCCS).

Crypto Reqs: None. JULLS data base is classified SECRET and below. If the AAR is classified SECRET appropriate security procedures for handling SECRET material must be maintained.

Normal Locations: 12,000 JULLS exist and support all echelons of any Unified Command or any major command of a service component. In the Marine Corps, the software and access to the JULLS data base can be found at MCCDC, the Warfighting Development Integration Division (WDID), the archive's division of the Marine Corps Research Center, Quantico, at Headquarters Marine Corps, Deputy Chief of Staff Plans, Policy and Operations (DC/S PP&O), and at the Marine Expeditionary Force (MEF) G-3's.

Information Managed: Inputted Lessons Learned.

Products Created: Formats between the inputted and outputted JULLS/ARR's are identical.

Lead Service/Contractor: Joint Staff (EAD J-7)/ Institute for Simulation and Training (affiliated with the University of Central Florida).

Current Fielding Status: Program is being update for windows environment. Current version is 6.22.

Known Problems: Access or input to the JULLS software and database at the battalion or squadron level (or below) is difficult.

DIICOE Compliance Rating: Not rated.

Point of Contact: Lieutenant Colonel Richard A. Siebert

Joint Staff, J-7 Operational Plans and Interoperability Directorate Evolution and Analysis Division

Comm: (703) 693-2877 DSN: 223-2877

Internet: http://www.jwfc.js.mil/PAGES/Jcll.htm

Updated by: LT Giuseppe Platania, Italian Marine Corps, CCSC-99.

  

Joint Visually Integrated Display System

(JVIDS)

System Status: System is no longer in use. It was phased out in 1989 to 1990 and was replaced by GCCS.

Updated by: Capt Herman Glover IV, USMC, CCSC-99.

  

Joint Worldwide Intelligence and Command System

(JWICS)

Primary Purpose: Provide transmission path capable of secure video/data within defense intelligence community. At T-1 speed allows: (1) Transmission of imagery files and intelligence documents rapidly between sites; (2) real time two-way video teleconferencing between sites; (3) receipt of the intelligence community’s TV broadcast of the Defense Intelligence Network (DIN). Designed to provide 24 hour TS-SCI multimedia communications to include secure video teleconferencing (VTC). Replaces DISNET 3.

Sub-Functions: JWICS Mobile Integrated Communications System (JMICS) is a deployable JWICS. Equipment is self-contained on a HMMWV.

Equipment Reqs: JWICS hardware is self contained. Requires 120VAC / 60Hz power and satellite connection.

Connectivity Reqs: T1 (1.544 mbps) connection (usually satellite). Often used in conjunction with TROJAN SPIRIT. (1.024 mbps for VTC (2 X 512 kbps channels), 384 kbps designated for data, 136 kbps for serial data channels and system control).

Crypto Reqs: KG-84/KY96/KG-194.

Normal Locations: Over 150 fixed sites to include all major commands. Ten JMICS available for contingency/crisis response - nine currently deployed to support various requirements and one maintained at DIA as a war reserve. Approximately 25 JWICS systems are containerized versions in transit cases, offering greater mobility.

Information Managed: Point to point and multi-point secure VTC service. Broadcast and video programming of Defense Intelligence Network. Standard voice/data terminal connections include Defense Switched Network, Defense Red Switched Network and the National Secure Telephone System. Bulk data transfer of a variety of network services.

Products created: This is a communications path. Products are produced by systems on this path.

Lead Service/Contractor: Defense Intelligence Agency

Current Fielding Status: Operational; planning in progress to increase / upgrade mobile JWICS assets

Known Problems: Slow data rates can result in poor VTC.

Asynchronous Transfer Mode (ATM) multicast is under development to allow an unlimited number of receivers and a limited number of transmitters to participate in a JWICS command brief outside of a JWICS conference room.

DIICOE Compliance Rating: Not applicable, JWICS is a connection path only.

Point of Contact: JWICS Help Desk: Comm: (202) 231-8000, DSN: 428-8000; Mr. Tom Moslener, Deputy Directorate - Crisis Operations (J2O3), The Joint Staff, DSN: 223-7640; JWICS Systems Requirements Management Division, Comm: (703) 695-1999, DSN: 225-1999. GySgt Howe, MCIA Det, Comm: (703) 784-6111 DSN: 278-6111.

Updated by: CPT Christopher J. Pyle, USA, CCSC-99.

  

Local Asset Management System

(LAMS)

Primary Purpose: The LAMS program is a standardized system for the management of Support Equipment (SE) at all three levels of Naval Aviation Maintenance. LAMS enhances the control of inventory through upline reporting of SE assets to the Support Equipment Resources Management Information System commonly referred to as SERMIS. SERMIS contains the master database of equipment for the Aviation Maintenance Material Readiness List (AMMRL) Program. LAMS provides automated methods of tracking SE assets at the local level. LAMS uses the SE Transaction Report (TR) as the source document. TRs are processed in LAMS and the data is submitted to the Support Equipment Controlling Authorities (SECAs) for upload into Support Equipment Resources Management Information System (SERMIS). LAMS references the Individual Material Readiness List (IMRL) data which is downloaded from SERMIS. At the local level, activities are allowed to compute their excesses and deficits according to the authorized allowances in their IMRL. The Activity Inventory Report (AIR) data from SERMIS is used by the LAMS to generate an AIRCOMP Report which compares the inventory reported in SERMIS with the inventory reported in LAMS. LAMS provides real-time automated methods of aviation Support Equipment (SE) management. The LAMS system is comprised of a group of programs designed to manage two primary data files (IMRL and INVENTORY), and several secondary data files. The initial IMRL data file is created from data extracted from SERMIS. The initial and periodic updates to the IMRL data file are provided by the Support Equipment Controlling Authority (SECA). The IMRL Manager uses this initial IMRL data to help establish the INVENTORY data file.

Sub-Functions: LAMS performs the following functions:

-Standardizes inventory control procedures for Naval Aviation Individual Material Readiness List (IMRL) assets.

- Allows real time tracking of an activity's IMRL assets (issue, return, etc.).

- Improves inventory accuracy and reduces man-hours by using barcodes.

- Provides printed reports for all levels of management.

- Provides interface with SERMIS.

Equipment Reqs: 386 or 486 Computer Processing Unit (CPU);  4 Megabytes of Random Access Memory (RAM); 450 Megabytes minimum hard disk drive space free for installation 9440 Barcode Scanner 3.5 inch, high density floppy drive. 

Connectivity Reqs: No special requirement.

Crypto Reqs: None.

Normal Locations: Aviation squadron maintenance departments (afloat and ashore).

Information Managed: Aircraft support equipment (SE) allowances, asset location, availability, inventory, and SE current status.

Products Created: Inventory, asset location, and current status reports.

Lead Service/Contractor: USN (NAVAIR 3.6.2.3)

Current Fielding Status: Version 2.4.1 in use within USN and USMC.

Known Problems: None.

DIICOE Compliance Rating: Program managers do not know (POC Lynn Huett).

Point of Contact: Ms. Brenda Tominack, DSN 757-8845, Comm (301) 757-8845.

Internet: http://pma260.navy.mil/AMMRL

Updated by: Capt Joseph Paguiligan, USAF, CCSC-99.

  

Logistics Management Information System

(LMIS)

Primary Purpose: Provides logistical data on Marine Corps equipment to support budget, acquisition, transportation, embarkation, supply and maintenance planning requirements.

Sub-Functions: Supports annual budget and requirement planning.

Equipment Reqs: IBM compatible PC with 2.2Mb or free hard drive memory and 256Kb of RAM.

Connectivity Reqs: 3270 emulation

Crypto Reqs: None.

Normal Locations: All Marine Corps units with 3270 access.

Information Managed: Ship characteristics and embarkation data. Shipping and embarkation data for USMC. TAMCN’s Acquisition data for all USMC. TAMCN’s Unit equipment allowance files (EAF). Master Inventory History File (e.g. NSN’s, TAMCN’s, Nomenclature, ID number, etc.).

Products created: All reports required to document an amphibious Maritime Preposition Force (MPF) ship’s load plan. Database for the MDSSII (updated monthly). P20 exhibit for the PPBS (total, active duty USMC requirements). P20A exhibit for the PPBS (total, reserve USMC requirements). LMIS Item Data File (Identifying Data, Acquisition Data, Embarkation Data, Fuel Data), Troop List File, and EAF.

Lead Service/Contractor: Current: United States Marine Corps Future: United States Marine Corps/TBD.

Current Fielding Status: Fielded. LMIS is scheduled for redevelopment and consolidation with the family of Force Structure Management systems into the Total Force Structure Management System (TFSMS). The new system is scheduled to begin development in October FY00 with FOC in the first quarter FY03.

Known Problems: The system is over 26 years old and its technology inflexible (cumbersome and not user-friendly). Programmed in the late 60’s – early 70’s and does not come close to contemporary standards. 3270 application is slow and unreliable. Does not adequately support the force structure review and combat development processes. MOA’s take over a year to update and cannot be tracked by the users.

DIICOE Compliance Rating: Not rated.

Point of Contact: GM-14 Paul W. Plant; TFSD, MCCDC; (703) 784-5475, DSN 278-5475. EMail:plantp@quantico.usmc.mil

Updated by: Capt Crystal T. Pelletier, USMC, CCSC-99.

  

Logistics Automated Information System

(LOGAIS)

Primary Purpose: A family of systems used to track people, supplies, and equipment. The coordinated, mutually supporting, personal computer based programs support peacetime operations and immediate, on-hand crisis action/time sensitive operational and logistics planning and execution of deployment and redeployment of MAGTF and NSE in independent, joint and combined operations.

Sub-Functions: Contains MAGTF Deployment Support System II (MDSSII), Transportation Coordinators’ automated Information Management System (TC AIMS), Asset Tracking for Logistics and Supply System (ATLASS), Computer Aided Embarkation Management System (CAEMS), Automated Identification Technology (AIT), and MAGTF Data Library (MDL).

Equipment Reqs: 486 CPU w/16MB RAM, 250 MB disk space, and DOS 6.2 with Windows 4.1A or Windows 95/98.

Connectivity Reqs: Stand-alone system. Interfaces w/JOPES through MAGTF II. Passes data between components via LAN or courier diskette.

Crypto Reqs: None.

Normal Location: USMC, battalion or above. MAGTF II at Regt., MDSS at battalion, and TCAIMS at battalion M.T.

Information Managed: Reference data required to plan and execute deployment and redeployment of forces.

Products Created: TPFDD in JOPS III format, Unit deployment listings, lift and sustainment estimates, embarkation plans, air load plans, real-time tracking of assets, and movement plans.

Lead Service/Contractor: USMC/Stanley Associates.

Current Fielding Status: Version 4.1 fielded

Known Problems: Not all components fully implemented in FMF.

DIICOE Compliance Rating: Not rated.

Point of Contact: Mr. Tom Toth at Albany, DSN: 567-6625/26.

Updated by: Capt Joseph J. Zarba, USMC, CCSC-99.

 

Logistics Sustainment Analysis and Feasibility Estimator

(LOGSAFE)

Primary Purpose: Part of Joint Operation Planning and Execution System (JOPES) executing in the Global Command and Control System (GCCS) common operating environment. Assist logistic planners in determining sustainment requirements of a proposed operation Plan (OPLAN) for deliberate execution or crisis planning.

Sub-Functions: Performs over 5,000 supply functions of Plan Development Phase model (as described in the Joint Staff Officer’s Guide).

Equipment Requirements: GCCS Sun/Solaris workstation

Connectivity Requirements: GCCS JOPES database and SIPRNET.

Crypto Requirements: None.

Normal locations: Installed at all Unified Commands and their service component headquarters.

Information Managed: Non-Unit Related Cargo (NURC) records entered into Time-Phased Force and Deployment Data (TPFDD) as Cargo Increment Numbers (CINs).

Products Created: NURC records for JOPES databases. Places records for NURC cargo into one of two JOPES transition formats: INDXDT or NRNUBT (the principal output for this application).

Lead Service/Contractor: Joint Staff J4/Computer Science Co(CSC).

Current Fielding Status: In use with upgrades.

Known Problems: None. LOGSAFE is Y2K compliant.

DIICOE Compliance Rating: Not rated.

Point of Contact: Major Klotsko, Joint Staff Office/ J-4/ Logistics Information Systems Division, Comm: (703) 695-3397, DSN: 225-3397, email KLOTSKJA@js.pentagon.mil.

Internet: WWW.DISA.MIL (Under the GCCS directory).

Updated by: CPT Neil K. Khatod, USA, CCSC-99.

  

Marine Ammunition Accounting and Reporting System

(MAARS II)

Primary Purpose: Marine Corps Ammunition Tracking and Management System.

Sub-Functions: Requisition, inventory, procurement, and communications.

Equipment Reqs: IBM AS-400 (model E50); Remote users=50, local users=45. Remote users located at each of the MarFor’s, MCPB, NWSC crain.

Connectivity Reqs: Token ring, TCP/IP, Bisynch Dial-up, Async Dial-in.

Crypto Reqs: None. MAARS is a SBU system.

Normal Locations: USMC MARCORSYSCOM (Program manager for Ammunition).

Information Managed: Ammunition location, condition codes, purpose, lot/serial numbers, on-hand/in-transit ordnance, due-in/due-out requirements, classification, and availability.

Products Created: Requisition and Ammunition Reports.

Lead Service/Contract: USMC/Columbia Services Group.

Current Field Status: In use with the USMC.

Known Problems: The sequence of incoming transactions(older transactions coming in before the latest ones; activities transmitting the same transaction more than once (dups); activities using the wrong DIC (Document Identifier Code) for the transaction; policy changes.

DIICOE Compliance Rating: Not rated.

Point of Contact: CWO 5 G D Kjeldahl, MARCORSYSCOM. DSN 426-1163.

Updated by: Capt Daniel C. Logan, USMC, CCSC-99.

  

Medical Augmentation Program

(MAP)

Primary Purpose: Provides a reserve pool of active duty Naval Medical personnel not currently assigned to an operational billet (Claimancy 18 personnel) to augment operational and medical support units deploying to situations ranging from limited contingencies to global warfare.

Sub-Functions: Augmentation Personnel Readiness Checklist.

Equipment Reqs: 386 pc with modem.

Connectivity Req: Data transferred via point-to-point dial up to local/regional medical facility. Will forward consolidated information to Bureau of Medicine and Surgery (BUMED).

Crypto Reqs: None.

Normal Locations: NAVMED major command elements, stand alone medical facilities and hospitals.

Information Managed: Operational platform medical billets. Deployable medical personnel rosters.

Products Created: Command data base of deployable personnel. MAP Readiness Training Requirements Report. MAP Monthly Augmentation Readiness Report. MAP Augmentation Personnel Sourcing Changes Since Last Report. Readiness Improvements Report. Training Status Report.

Lead Service/Contractor: USN/Naval Medical InformationManagementCenter (NAVMEDINFOMGMTCEN).

Current Fielding Status:Continuously upgraded. Change requests from NAVMED units and BUMED sent to NAVMEDINFOMGMTCEN.

Known Problems: None.

DIICOE Compliance Rating: Not rated.

Point of Contact: Cmdr. Dennis Mclane, DSN: 762-3433 COMM: (202) 762-3433, Action Officer, Readiness Operations Branch (MED-272) Bureau of Medicine and Surgery.

  

Marine Corps Ammunition Requirements Management Systems

(MCARMS)

Primary Purpose: Determine and consolidate Marine Corps war and peacetime requirements for ground ammunition, project them against current inventory and derive a preliminary acquisition plan.

Sub-Functions: Combat and peacetime requirement determination. Inventory projection over near term. Procurement requirements. Funds allocation over near term.

Equipment Reqs: Microcomputer with 486 or better processor, 387 Math Co-Processor, 80 Mb Hard disk space, 4 Mb RAM.

Connectivity Reqs: None.

Crypto Reqs: None..

Normal Locations: MARCORSYSCOM: Ammunition Program Manager MCCDC: Studies and Analysis Division and Training and Education Division.

Information Managed: Weapons and ammunition effectiveness and employment data. Ammunition inventory and availability data.

Products Created: Total combat requirement, combat planning factors, total peacetime requirements, inventory projections and master acquisition plan.

Lead Service/Contractor: United States Marine Corps (USMC)/MKI System, Inc.

Current Fielding Status: In use within the USMC.

Known Problems: Excessive file I/O leading to longer than necessary run times. Output formats not IAW DODINST 3000.4. These problems are being addressed in FY99 study effort.

DIICOE Compliance Rating: Not rated.

Point of Contact: Capt Strycharz, S&A Division, MCCDC, Comm: (703) 784-6012.

Updated by: Capt Craig R. Doty, USMC, CCSC-99.

  

Marine Corps Fire Support System

(MCFSS)

 

Primary Purpose: Architectural system comprised of all USMC fire support systems which automate fire support coordination and/or execution through automated devices and data communications.

Sub-Functions: Automated fire support coordination of artillery, close air support (CAS), naval surface fire support (NSFS), and mortars; tactical and technical fire direction; fire support planning; targeting functions; artillery, counterfire, and mortar fire planning; artillery calls for fire; air support requests; meteorological and survey data collection and distribution.

Equipment Reqs: Varies with individual systems.

Connectivity Requirements: VHF/HF single channel radio, 2 and 4 wire, and LAN (AFATDS/IFSAS).

Crypto Reqs: Vinson family

Normal Locations: Systems are located in the following nodes:

AFATDS/IFSAS: Artillery Bn and Regt FDCs, Infantry Bn, Regt, Div FSCCs, DASC, FFCC, TACC.

Battery Computer System (BCS): Artillery Btry FDC Mortar Ballistic Computer (MBC): 81’s platoon FDC; DACT/DMS: Forward Observers; AN/TPQ-36: Counter Mortar Radar; AN/TMQ-31: Meteorological Section.

Information Managed: Conventional fire plans, all supporting arms fire missions, target information, fire support coordinating measures, maneuver geometry, individual firing unit information, JTARS and immediate air requests, met messages, and survey information.

Products Created: Fire Support Plans, fire plans, target lists and other target information, firing data, calls for fire, ASRs, mission fired reports.

Lead Service/Contractor: USMC- IFSAS, MBC, DMS/DACT, AN/TMQ-31; USA- AFATDS, BCS, AN/TPQ-36.

Current Fielding Status: AFATDS replaces IFSAS and fields to I and III MEF by ’01, II MEF in ’02. DACT fields in ’00. All other systems fielded. Version 11 Software package will bring older systems into VMFBOM message formatting.

Known Problems: Minor interoperability problems with systems from different times and contractors.

DIICOE Compliance Rating: AFATDS ’98 level 6.

Point of Contact: Major Halsey, MARCORSYSCOM, DSN 278-2645.

Updated by: Capt Jeffrey C. Smitherman, USMC, CCSC-99.

 

Marine Combat Service Support and Control

(MCSSC2)

Primary Purpose: Will provide MAGTF commanded and automated means of determining personnel and logistics status in near real time, thereby accelerating and improving the tactical decision process.

Sub-Functions: Will request, collect, and integrate operational logistics information from MAGTF II/LOGAIS family of systems and from the Unit Diary/Marine Integrated System (UD/MIPS)

Provide automated decision support aids of logistics and analyze courses of action for logistics feasibility.

Support and automate preparation of logistics plans and annexes. And dissemination and submission of logistics estimates, reports, and requests for support.

Equipment Reqs: SUN Sparc 20.

Connectivity Reqs: Tactical LAN’s more specifically the SIPRNET

Crypto Reqs: No external crypto required.

Normal Locations: USMC battalion level and above

Information Managed: Collect and display the critical information existing within functional, stand alone, personnel, and logistics databases. Logistical readiness.

Products Created: Logistics plans, orders, annexes, reports, and requests.

Lead Service/Contractor: USMC/TRW Boeing.

Current Fielding Status: Under development (Phase 0). IOC 2nd quarter FY 98.

Know Problems: Beginning the acquisition cycle.

DIICOE Compliance Rating: Not rated.

Point of contact: Major Gerichter DSN:792-7129, x2530. Major Morres DSN:328-1081, x405.

Internet: http://www.defenselink.mil/locator/records/00261.html

Updated by: Capt Allen K. Johnson, USMC, CCSC-99.

  

Marine Corps Total Force System

(MCTFS)

Primary Purpose: Recording, processing, and maintenance of personnel and pay data on a continuing basis for all active and reserve personnel, and on retires.

Sub-Functions: As of 6 September 1996, MCTFS replaced the Joint Uniform Military Pay System/Manpower Management System (JUMPS/MM). Is an integrated personnel and pay system, utilizing Unit Diary/Marine Integrated Personnel System (UD/MIPS), On-Line Diary System (OLDS) and Automated Recruit Management System (ARMS) as the major input tools to update information contained within the database. With over 34 systems that interface the database, MCTFS is the only totally integrated personnel and pay system within the DoD.

Equipment Req.: Industry Standard Personal Computer and the Lightweight Computer Unit (LOU), LAN/WAN capability and 3270 emulation.

Connectivity Reqs: MODO, LAN/WAN, SALTS, NIERNET, 3270;

Crypto Req: None. Requires user ID that is controlled by the local TASO.

Normal Locations: Battalion/Squadron or independent unit requiring personnel management capabilities.

Information Managed: Pay and personnel management functions.

Products Created: Rosters (alpha, meal card, rifle/pistol, pay) LES's, etc.

Lead Service/Contractor: MCTFS is jointly owned by the Marine Corps and Defense Finance and Accounting Service (DFAS) Financial

System Activity implements system modifications and maintenance.

Current Fielding Status: Currently in use.

Known Problems: None.

DIICOE Compliance Rating: Level 7.

Point of Contact: Lieutenant Colonel Kay Young, HQMC Manpower, DSN 278-9043.

Updated by: Capt Allen K. Johnson, USMC, CCSC-99.

 

Migration Defense Intelligence Threat Data System

(MDITDS)

Primary Purpose: The information management system and data repository for DoD force protection, threat analysis, and warning.

Sub-Functions: Provides a capability to retrieve information pertaining to terrorist profiles & facilities, facility vulnerability assessments, threat assessments, and country profiles/assessments.

Equipment Reqs: Cross platform/we-based using Netscape Browser 4.0 (SUN, Windows 95/NT, UNIX) Requires Sybase System II for Indications & Warning.

Connectivity Reqs: Deployable Stand alone-Site Specific, JWICS, SIPRNET.

Crypto Reqs: JWICS, SIPRNET

Normal Locations: Unified Commands, JIC, JAC, Intel agencies, AFOSI, INSCOM, NCIS, OSIA, law enforcement agencies.

Information Managed: Terrorist threat analysis information.

Products Created: Single query access to unified databases

Lead Service/Contractor: DoD.

Current Fielding Status: Phase 1: development, integration, evaluation: 3 Qtr FY 98 – 2 Qtr FY 00. Phase 2: development, integration, evaluation: 4 Qtr FY 98 – 2 Qtr FY 02.

Known Problems: None.

DIICOE Compliance Rating: Not rated.

Point of Contact: Dr. Judith Daly, (703) 614-8436, dalyja@acq.osd.net.

Internet: http://www.acq.osd.mil/at/mditds.htm; Intelink: http://mditds.diac.dia.ic.gov

Updated by: Capt Alton L. Cochran Jr., USMC, CCSC-99.

  

Military Standard Transportation and Movement Procedures

(MILSTAMP)

Primary Purpose: DoD regulation provides policy for transportation and movement of material. MILSTAMP prescribes standard data elements, codes, formats, documents, forms, rules, methods, and procedures required by DoD components and other U.S. Government Agencies/civil authorities in the transportation and movement of material to, within, and beyond the Defense Transportation System (DTS).

Sub-Functions: Volume 1 divided into four chapters: Introduction, Shipper Requirements and Procedures, Transshipper Requirements and Procedures, and Receiver Requirements and Procedures. Volume 2 deals exclusively with financial issues. Regulation publishes transportation account codes (TACs) and DTS billing formats.

Equipment Reqs: Heavy reliance on telephone facsimile for communication between DTS nodes.

Connectivity Reqs: Commercial/DSN telephone.

DIICOE Compliance Rating: Not rated.

Crypto Reqs: None.

Normal Locations: DTS comprised of military controlled terminal facilities, AMC controlled or arranged airlift, MSC controlled or arranged sealift, and government controlled air or land transportation.

Information Managed: MILSTAMP policy is designed to facilitate exchange of logistics data between services and agencies. Data managed under MILSTAMP includes: consignee (listed by their 6-digit DoD Activity Address Code), Transportation Priority (reflecting one of four categories), Required Delivery Date, Project Code (if applicable), shipment unit (clearly defines the entity being shipped), Transportation Control Number, size (pieces, weight and cube), dimensions of each shipment unit, mode/method of shipment, National Stock Number, commodity code, Port of Embarkation, Port of Debarkation,

Information Managed (cont): Transportation Account Code, hazardous material (HAZMAT) code, and radioactive material codes.

Products Created: Transportation Control and Movement Document (TCMD).

Lead Service/Contractor: Published by Deputy Assistant Secretary of Defense (Logistics) (DASD(L)).

Current Fielding Status: The regulation in force, change 6, was published in May 1995. The newest version incorporates updates to policy and procedures.

Known Problems: No standard ADPE system supporting MILSTAMP. Each service has created its own automation/data base with minimal interoperability. Internal integration among aerial and surface port systems, e.g., Integrated Booking System (IBS), Worldwide Port System (WPS), Consolidated Aerial Port System (CAPSII), and Global Air Transportation Execution System (GATES) has caused some problems.

DIICOE Compliance Rating: Not rated.

Point of Contact: Ms Lynnette Ju, USMC IT/Y2K,

DSN: 235-5243, Comm: 703-275-5243.

Updated by: Capt Daniel L. Paris, USMC, CCSC-99.

  

Multi-Spectral Imagery Materials Exploitation System

(MIMES)

Primary Purpose: First prototype of a military multi-spectral imagery production system. Is a state of the art digital image processing system. Conceived and developed by the USAF Strategic Air Command with assistance from the Defense Support Program Office (DSPO). Provides the capability to process and exploit multispectral and panchromatic imagery to support mission needs.

Sub-Functions: Support to mission planning and execution in the form of image maps and perspective view products. Support to Unified Commands, DoD, and national assessments of designated missile forces in support of strategic and tactical warning, planning, targeting, and execution. Mapping, charting, and geodesy support to the Single Integrated Operational Plan.

Equipment Requirements: (Hardware) One Sun ULTRA 60 workstation, two SGI ONYX 2s, four Sun/ULTRA 2 workstations, two Sun/SPARC 20 workstations, four Windows NT Dual Chip Pentiums, two Apple Power PCs; (Software) ERDAS Imagine, PCI, ERIPS, CPG, VAX Image Processing Software

Connectivity Requirements: N/A

Crypto Reqs: N/A

Normal Locations: A DoD asset utilized by all Unified Commands

Info Managed: LANDSAT and SPOT imagery

Products Created: Image-based products to support headquarters planning activities, custom products, contingency planning, and training programs. Analysis Image, Image Graphic, Custom Format Graphic, Change Image/Reference Image, Perspective View, Mosaic Image, and Terrain Categorized Graphic are standard products supported by MIMES. Products may be provided in hardcopy, on 8mm and 9 track tapes, or on CD-ROMs. Production times vary depending on factors such as scene availability, process required, and priority of request.

Lead Service/Contractor: USAF (NORAD/USSPACECOM Combined Intel Center)

Current Fielding Status: Operational since 1988

Known Problems: None.

DIICOE Compliance Rating: Not rated.

Point of Contact: Missile Analysis Center, Offutt AFB, DSN: 271-7784, Comm: (402)294-7784/8950, FAX Comm: (402)232-5126,

Internet: http://www/usstratcom.ic.gov/products/mac/macindex.html

Updated by: Capt Richard A. Eckles II, USMC, CCSC-99.

 

Marine Corps Integrated Maintenance Management System

(MIMMS)

Primary Purpose: Increases equipment readiness with minimum expenditure by using uniform maintenance management system.

 

Sub-Functions: Management tool for conduct of ground equipment maintenance. Establishes effective maintenance management programs for maximum readiness.

Equipment Reqs: 486 PC.

Connectivity Reqs: Stand-alone. Data must be passed via courier diskette, LAN, or other means to Maintenance Information System Coordination Office (MISCO).

Crypto Reqs: None.

Normal Locations: USMC battalion level and above.

Information Managed: Equipment repair status.

Products Created: Maintenance Reports: Daily Transaction Listing (DTL), Daily Process Report (DPR), Daily SASSY Transaction Listing, Daily Field Maintenance TAM Report, Semiweekly Milstrip Status Report, Weekly Owning Unit Maintenance TAM Report, Weekly Major Command TAM Report, Weekly Maintenance Exception Report, Weekly Material Report, Field Maintenance Production Report, Weekly Maintenance Shop Summary, Equipment Repair Order (ERO) Billing List, History Process Report, MIMMS Secondary Reparable Expense Summary, Quarterly Using Unit Modification Status Report, Quarterly Major Command Modification Status Report, Serial Number Listing for Unit Activity Code, and ID/SN/NSN RUAF Match Listing.

Lead Service/Contractor: USMC.

Current Fielding Status: In use since Jan 1970. Combined four systems into one standard for the Marine Corps. Will be replaced by Atlass Phase II.

Known Problems: Manual input, labor intensive.

DIICOE Compliance Rating: Not rated.

Point of Contact: GySgt Gibbs, 2nd FSMAO, DSN 484-0883.

Updated by: Capt Kenneth M. Lewton, USMC, CCSC-99.

  

Manpower Mobilization Assignment System

(MMAS)

Primary Purpose: To identify, assign, and process reserve and retired Marines for mobilization in support of warfighting contingencies.

Sub-Functions: An integrated, computer-based system consisting of the following subsystems: Priority of Fill, Casualty Estimation Model, Wartime Verification Extract File, Marine Corps Mobilization Process System, Mailgram Orders System.

Equipment Requirements: PC and Marine Corps Data Network (3270).

Connectivity Requirements: Can be operated as a stand-alone system, but will require 3270 access to transfer data to Marine Corps Total Force System (MCTFS) and other Marine Corps manpower divisions.

Crypto Requirements: None.

Normal Location: HQ, USMC (MPP-60).

Information Managed: A master file of all reserve or retired Marines eligible for assignment to satisfy manpower requirements.

Products Created: Generates authorized reserve manpower strength, establishes notional table of organization based on casualty estimates or a given scenario, creates a consolidated inventory of available Marines to be mobilized, generates a checklist for screening Marines and tracks the overall mobilization process, and generates reserve activation orders for delivery by Western Union and provides data for requesting paychecks and record books.

Lead Service/Contractor: USMC/Computer Sciences Corporation (primary contractor), Ideamatics (subcontractor), Commander, Marine Corps Systems Command (COMMMARCORSYSCOM).

Current Fielding Status: Currently in use. Release of upgrade versions scheduled for FY 99.

Known Problems: Requires man frame (3270) access, but future versions will allow transfer of data via LAN.

DIICOE Compliance Rating: Not rated.

Point of Contact: Major Morgan, HQMC (MPP-60), Comm: (703) 784-9358.

Updated by: Capt Rodney Legowski, USMC, CCSC-99.

Marine Traffic Management System

(MTMS)

SYSTEM HAS BEEN RENAMED PCCC

Primary Purpose: Provides real-time cargo and vessel status visibility to shore and shipboard command and control units.

Sub-Functions: None.

Equipment Reqs: SUN Sparc UNIX based workstation. Secondary sites use laptop PC.

Connectivity Reqs: Workstations interface via an Ethernet LAN. Use radio frequency bridges to link separated operational centers.

Crypto Reqs: None.

Normal Locations: Not fielded yet.

Information Managed: Object oriented customized expert system containing all operating area rules, regulations, and procedures. Has closed circuit television capability to assist in management of loading areas.

Products Created: Graphical display depicts local landmarks and waterways, and displays water craft position, course, and speed. Dedicated windows are available to display sensor data, water craft status, cargo status, and other tabular data to control various sensor processing parameters. System alarms are generated when violations occur, providing an automatic monitoring capability to assist operators.

Lead Service/Contractor: Army/Lockheed Martin.

Current Fielding Status: Fielded as PCCC.

Known Problems: Not ruggedized (mostly off the shelf, this will keep the price down). Tends to over manage cargo loading/shipping process with closed circuit TVs and GPS tracking.

Point of Contact: CWO3 Ray Aube, Fort Lee, (804) 734-2948, DSN: 687-2948

  

Naval Aviation Logistics Command Management Information System

(NALCOMIS)

Primary Purpose: Provides a single automated management information system to organizational level activities that will provide immediate status of the squadron’s aircraft, equipment, and personnel.

Sub-Functions: Two versions – NALCOMIS OMA (Organizational Management Activities) and NALCOMIS IMA (Intermediate Maintenance Activities).

Equipment Requirements: PC with NALCOMIS software.

Connectivity Requirements: LAN/WAN.

Crypto Requirements: None. Password protected.

Normal Locations: NALCOMIS OMA is fielded to every Navy/Marine squadrons and detachments that perform "o-level" maintenance. NALCOMIS IMA is at MALS, AMID/IMA of all Naval air stations and aboard all aviation capable ship, and is being field to Marine Air Traffic Control Detachments.

Information Managed: Oversees aviation supply process.

Products created: Carcass tracking reports; shows the stage parts ordering process is current at and when the parts may be received. Various Management reports and other quarterly - daily key performance indicator reports.

Lead Service/Contractor: US Navy/Contract managed by DISA Simulation and Assessment (D8).

Current fielding status: NALCOMIS OMA is in use at every naval aviation squadron. NALCOMIS IMA is in use at 70 naval sites, 167 support and training sites and is being fielded to Marine Air Traffic Control Detachments. Windows NT upgrade will be fielded to the first ship in June 99 and MALS in Jan 99.

Known Problems: Minor Y2K noncompliance that has minimal effect. Reports are monthly vice yearly.

DIICOE Compliance Rating: Not rated.

Point of Contact: 2dMAW Aviation Logistics Department-B (ALD) DSN 582-2402. Wes Ray, SPAWAR Center, Chesapeake, VA DSN 565-8205.

Inernet: http://www.nets.navy.mil/navresfor/navair/n6/n61.html.

Updated by: Capt Randy W. Ross, USMC, CCSC-99.

  

Naval Modular Automated Communications System II

(NAVMACS II)

CUDIX and NAVMACS systems have been incorporated into NAVMACS II

Primary Purpose: Provide improved message handling for ship-to-shore and ship-to-ship operational communications.

Sub-Functions: None.

Equipment Reqs: AN/UYK 20 computer (or equivalent), IP-1187A video display unit system management/operator interface (or equivalent). TT-624 medium speed line printer, AN/USH-22 reel magnetic tape, backup message input/output if NAVCOMPARS is not functioning. ON-143(V) interconnects box to interface computer and satellite RF equipment.

Connectivity Reqs: UHF satellite 25 Hz wide channels allocated for CUDIX Transmissions. Each channel is half-duplexed UHF link at 2400 bps, SHF Gateguard and/or High Speed Fleet Broadcast.

Crypto Reqs: None, provided by the communications paths/system.

Normal Locations: Distribution Centers: NCTAMS EASTPAC (Honolulu, HI), NCTAMS WESTPAC (Guam), NCTAMS MED (Italy), NCTAMS LANT (Norfolk, VA), NCTAMS EASTPAC (Stockton, CA), Receive Sites: All Navy ships.

Info Managed: Autodin message traffic including USMTF based message traffic, Class D and E messages.

Lead Service/Contractor: Navy.

Current Status: New System fielded: NAVMACS II.

DIICOE Compliance Rating: Not rated.

Point of Contact: David Fuller, SPAWAR Systems Charleston, SC, DSN: 588-4563.

Internet: http://navmacs.nosc.mil.

Updated by: Capt Sylvester Gavins, USMC, CCSC-99.

 

Navy Integrated Environmental Support Subsystem

(NITES 2000)

Primary Purpose: NITES 2000 will provide tactical meteorological and oceanographic (METOC) support to Navy and Marine Corps forces engaged in worldwide operations, ashore and afloat. Though NITES 2000 will be able to operate independently, the prime mode of operations will be through interoperability with C4ISR systems.

Sub-Functions: The basic NITES 2000 missions are:

(a) Host observed and forecast METOC information relevant to ongoing operations,

(b) Assist METOC Professionals assess the impacts of present and forecast environmental conditions on operations,

(c) Provide METOC data to planning and decision support systems.

Equipment Reqs: AN/SMQ 11 Satellite Receiver/Recorder: Provides high-resolution visual and infrared imagery from GEOSAT Follow On, Defense Meteorological Satellite Program(DMSP), Television infrared Observation Satellite (TIROS), Geostationary Operational Environmental Satellite (GOES-NEXT, for future) and National Oceanographic and Atmospheric Administration (NOAA) satellites.

Afloat COMMS & I/O: HF RTT (or NAVTEX), Fleet Broadcast CH 8/15, Dial-up, NIPRNET/SIPERNET Network connections, CKT 9/23 Briefing Systems, MRS, MORIAH (future interface), AN/USQ-119.

SMOOS: Shipboard Meteorological and Oceanographic Observing System. These are five shipboard sensors located on ship’s exterior (i.e. Temp/Dew Pt., Vis/Precip, Cloud Height Indicator, Pressure, Wind). Provides data via serial RS-232/Fiber Optic digital interfaces.

Connectivity Req: Receives data from satellite sensors, regional centers listed below and organic sensors aboard ship. Fiber-optic cables used throughout SMOOS hardware.

Cryptologic Requirements: The Fleet Multi-Channel Broadcast METOC data requires a KWR-46. DMSP satellite interface via KG-44 crypto for Data/Clk & Remote Control.

Normal Locations: Worldwide METOC shore locations, afloat OA Divisions, Mobile Environmental Teams and Tactical Support Centers.

Information Managed: Meteorological and oceanographic data.

Lead Service/Contractor: US Navy.

Current Fielding Status: To begin 4QTR 1999.

Known Problems: None.

DIICOE Compliance Rating: Not rated.

Point of Contact: CDR Jeff Bacon, SPAWAR, phone (619) 524-7169, Kenneth Dropco dropcok@navo.navy.mil.

Updated by: Capt Deidre A. Houde, USAF, CCSC-99.

  

Navy Tactical Command Support System II

(NTCSS II)

Primary Purpose: First step in making non-tactical data processing systems compliant to a Common Operating Environment (COE). Uses the same COE as GCCS-M / JMCIS. Also provides a consistent method of accessing tactical support applications. These applications provide a full range of responsive mission support ADP hardware and software to facilitate management of information, personnel, material, and funds required to maintain and operate surface ships, submarines, and aircraft.

Sub-Functions: Shipboard Non-tactical Automated Program (

SNAP), Maintenance Resources Management System (MRMS), NALCOMIS, Administrative Data Management (ADM), Organizational Maintenance Management Subsystem (OMMS), Supply Financial Management (SFM), Integrated Logistics Management (ILM), Mobile Logistics Support Force Subsystem (MLFS), Food Service Management (FSM) and SNAP Automated Medical System (SAMS).

Equipment Reqs: Commercial of the shelf (COTS) equipment that is compatible with Information Technology for the 21st Century (IT21) standards.

Connectivity Reqs: IT21 network.

Crypto Reqs: None.

Normal Locations: Naval ships and supporting shore locations.

Information Managed: Supply, maintenance, administration, medical and aviation maintenance information for afloat units.

Products Created: Primarily administrative reports as required to support operational needs.

Lead Service/Contractor: USN (CNO N62, Pentagon, 5E523/ SPAWAR).

Known Problems: Ongoing system development and evolutionary changes as required to meet user requirements.

DIICOE Compliance Rating: Not rated.

Updated by: Capt Dan Hanks, USMC, CCSC-99.

  

Port Control Command Center

(PCCC)

Formerly called the Marine Traffic Management System

(MTMS)

Primary Purpose: To provide real-time cargo and vessel status visibility to shore and shipboard command and control units; and to provide a worldwide communications capability for inter/intra theater communications with all maritime assets and agencies.

Sub-Functions: The Asset Tracking Management System is the heart of PCCC.

Equipment Reqs: TBD. Primary site is in the Port (or beach) with the Port Operator, the Harbor Master Detachment, and the Ops Section (all from the Terminal Service Bn) conducting marine ops. Secondary sites TBD, but likely to include Beach Landing Site, Strategic Sealift Ship and Beach Discharge Point. The system must be deployable.

Connectivity Reqs: TBD. Possibilities include workstations interfacing via an Ethernet LAN; the use of radio frequency (FM, marine VHF, UHF), microwave, local portable cellular communications and/or SATCOM to link separated operational centers.

Crypto Reqs: TBD.

Normal Locations: TBD.

Information Managed: Object oriented customized expert system containing all operating area rules, regulations, and procedures. Also proposed to have closed circuit television for security and monitoring assets, and radar and GPS tracking for waterborne craft assets.

Products Created: Graphical display depicts local landmarks and waterways, and displays water craft position, course, and speed. Dedicated windows are available to display sensor data, water craft status, cargo status, and other tabular data to control various sensor processing parameters. System alarms are generated when violations occur, providing an automatic monitoring capability to assist operators.

Lead Service/Contractor: Army/TBD.

Fielding Status: Not fielded yet. Currently continuing with developing the requirement. Fielding will probably be only to the Terminal Service Bn level, and not any higher.

Known Problems: Semi-ruggedized (mostly COTS, but keeps the price down).

DIICOE Compliance Rating: Not rated.

Point of Contact: Maj Jeffrey Flint (USA) Ext 0488; CWO3 Ray Aube (USA) Ext 0337, (auber@lee.army.mil). HQ CASCOM, Attention ATCL-TM CWO Ray Aube, 3901 A Av, Suite 240, Fort LEE, VA 23801-1809. Telephone nos: Comm (804) 734-Ext; DSN: 687-Ext.

Updated by: Capt Neil M. Bennett, UK Royal Marines, CCSC-99.

 

Position Location Reporting System

(PLRS)

Primary Purpose: Provides situational awareness to the CLF/COMMARFOR by creating a network that provides positional/location information on a display Control Console. Also provides means for units to get own position location information and that of other friendly units.

Sub-Functions: Keypad allows short (10 character) text message transmission. Connection to Global Positioning System (GPS) via GPS interface unit (GPSIU).

Equipment Requirements: Basic user unit (BUU) (RT-1343) and master station. Fixed reference units required if not using GPSIU.AN/KSQ-1 can be used in conjunction with an aircraft or landing craft to allow over the horizon employment.

Connectivity Requirements: Multiple BUU’s working in support of a master station (MS) and alternate MS.

Crypto Requirements: KG-58 and embedded crypto in RT-1343.

Information Managed: Relative location of friendly units. Waypoints and predesignated items. Corridor (air) and lane (surface) restrictions, unit boundaries. Restricted zone guidance (mine fields, coordination measures, etc).

Products Created: Limited information for housekeeping via AN/UGC-74.

Lead Service Contractor: USMC/USA/Hughes Fullerton.

Current Fielding Status: HMMWV mounted down sized master station (DSMS) is in testing and was sent to MEF’s for evaluation during FY97. Planned fielding for DSMS is one for replacement of current master station. AN/KSQ-1 fielding will continue through FY02. Tentative plan for FY00 is to phase out PLRS and field EPLRS basic user units to Regimental and Battalion sized units. Eventually, EPLRS will be fielded to company sized units. EPLRS is the Army variation with improved data capabilities, TCP/IP computability, and a SINCGARS interface. It will replace PLRS.

Known Problems: The PLRS communications enhancement package (PCE) improves the electronic data throughput. Need for fixed reference stations when not using GPSIU. DSMS will allow use of hybrid PLRS and EPLRS basic user units.

DIICOE Compliance Rating: Not rated.

Point of Contact: PLRS/EPLRS Project Manager: LtCol Spegele, Ft. Monmouth, NJ, DSN 987-2852/3196; E-Mail: spegele@doim6.monmouth.army.mil, Capt Jay Storms PLRS/EPLRS Project Manager, C4I/CIS, MARCORSYSCOM DSN: 278-4541 (ext. 3021) comm: (703) 784-4541 (ext. 3021).

Updated by: Capt Rodney Legowski, USMC, CCSC-99.

 

Psychological Operations Automated System

(POAS)

Primary Purpose: Produces the Joint Capabilities Plans (JCSP) mandated by the Psychological Operations Studies (PSYOPS). This includes: Basic Psyops Study (BPS), Special Psyops Assessment (SPA), Special Pysops Study (SPS), and Military Capabilities Study (MCS).

Sub-Functions: Planned Civil Affairs database. Installed 12/98 (Note: separate accounts are needed to access this database).

Equipment Reqs: New system of POAS 3 workstations (Ultra) or any P/C with a secure modem (that has POAS software loaded).

Connectivity Reqs: Secure path-system/classified as SECRET (Secure modem, SIPRNET, STU-III, and ATT 1910).

Crypto Reqs: KIV-7, STU-III, and ATT 1910.

Normal Locations: 4th PSYOPS Grp, FT Bragg; Any DOD locations who ask for connectivity (i.e CIA, FBI, and Dept of State). These all require SIPRNET/SECRET connectivity.

Information Managed: POAS is and automated data base system used to assist operations analysts to research and plan missions. POAS provides an all-source document index, intelligence report summaries, Psyops finished Intel products, bio information, and Psyops assessments/studies. POAS has the capability to correspond (send and receive) directly with other POAS users (automated message feed).

Products Created: PSYOP studies, message traffic via SIPRNET, CIA, Department of State, and the FBI.

Lead Service/Contractor: Technotics.

Current Fielding Status: System hardware currently being updated for Y2K compliance.

DIICOE Compliance Rating: Not rated.

Point of Contact: Mrs. Hilmo, DSN: 239-6812/1861.

Updated by: CPT Thomas J. Addyman Jr., USA, CCSC-99.

  

Retail Ordnance Logistics Management System

(ROLMS)

Primary Purpose: Ordnance logistics management and reporting.

Sub-Functions: Inventory, notice of ammunition reclassification (NARs), receipt, issue, and other reporting to ammunition inventory control point (ICP). Requisitioning and other related technical data processing.

Equipment Reqs: IBM-compatible 486/33 MHz PC with at least 12 MB RAM; 200+MB hard disk, MS-DOS 6.0, Windows 3.1, CD ROM, QIC-80 compatible tape back-up, 3.5-inch diskette drive, and laser printer.

Connectivity Reqs: 14.4K Baud FAX/Modem (minimum) and ethernet connection (intermediate and full).

Crypto Reqs: None.

Normal Locations: USN/USMC ship and shore units receiving status, and ammo on-order quantity. Ordnance technical item data, addresses, and NAR's.

Products Created: DD 1348-1, Receipt/Issue Document, transaction item reports (TIRs), ammunition transaction reports (ATRs), requisition for material, shipment status, reports for ordnance management and posture reports.

Lead Contractor: USN (CDA, NAVSURFWARCENDIV, Crane, IN)/CACI, Inc.

Current Status: Has been fielded to primary and intermediate users (level 1 and 2). System is Year 2000 compliant. Full

fielding (level 3) prototyped in Nov 98. Full installation of level 3 capabilities commences in CY99 and is scheduled for

completion in Dec 99.

Known Problems: None.

DIICOE Compliance Rating: Not rated.

Point of Contact: Mr. Jim Werne, NAVSURFWARCENDIV Crane, IN, DSN 482-5015, COMM (812) 654-1358.

Updated by: Capt Kenneth A. Knarr, USMC, CCSC-99.

  

Supported Activity Supply System

(SASSY)

Primary Purpose: Inventory control, supply accountability, and supply requisitioning.

Sub-Functions: Supply planning and budgeting.

Equipment Regs: Mainframe based; server located in St. Louis. Requires microcomputer availability at using unit.

Connectivity Regs: Data exchange between using units and the SASSY Management Unit requires LAN or 3270 connectivity. May be accomplished using courier diskettes.

Crypto Regs: None.

Normal Locations: All Marine Corps Units.

Information Managed: Supply and fiscal data.

Products Created: All standard supply reports to include the Due and Status File (DASF), Mechanized Allowance List (MAL) and Consolidated Memorandum Receipt (CMR).

Lead Service/Contractor: United States Marine Corps.

Current Fielding Status: Currently fielded. Is scheduled to be replaced by the Asset Tracking for Logistics and Supply System (ATLASS).

Known Problems: Not user friendly. Dependant on codes and complicated forms and reports. Information accuracy dependant on supporting activities. Incomplete interface with Marine Corps Integrated Maintenance Management System Automated Information System (MIMMS AIS). The delayed transition to ATLASS has resulted in very few improvements to SASSY to due the fact that the main concentration was to make it Y2K compliant. Therefore, the burdensome disparities between using unit local data and supporting activity data will remain constant.

DIICOE Compliance Rating: Not rated.

Point of Contact: MgySgt Campbell DSN 567-5489.

Updated by: Capt Todd L. McAllister, USMC, CCSC-99.

  

Strategic Sealift Analysis System

(SEASTRAT)

This system has been incorporated into JFAST

Primary Purpose: Generate sea lift schedules in support of Operation Plans. Provides Military Sea lift Command (MSC) capability to develop movement tables rapidly from Time-phased Force and Deployment Data (TPFDD) inserted during planning process. Assists in development of movement schedules for execution and performance of feasibility analysis.

Sub-Functions: OPLAN Analysis (OA) module permits MSC plans analyst to generate multiple sea lift schedules using requirements in OP-Plan’s TPFDD, a file of standard unit characteristics data (TUCHA), a set of ship assets as designated by Joint Strategic Capabilities Plan (JSCP), selected seaport characteristics information, and user- specified parameter variables.

Equipment Reqs: IBM network capability. Windows upgrade coming by end of 1998.

Connectivity Reqs: Ethernet/TCP-IP.

Crypto Reqs: Path must be secure. No internal crypto.

Normal Locations: Military Sealift Command Plans, Programs, and Policy Directorate (N5).

Information Managed: Time-Phased Force and Deployment Data (TPFDD) requirements. Ship characteristics and Location data. Port characteristics.

Products Created: Sealift movement schedules. JSCP Annex J ship assets. Various summary and detailed reports as follows: data validation, ship characteristics and availability, port characteristics, MSCV cargo lift requirements, port workload, ship itinerary, ship usage/cargo scheduling, and statistics. Final output of OA is Joint Operational Planning and Execution System (JOPES) formatted file of sea lift movement schedules transferable to USTRANSCOM via Global Command and Control System (GCCS) File Transfer System. Primary output of the SFMG Module is JSCP annex J ship file in Joint Flow and Analysis System for Transportation (JFAST) format as well as shop files used in OA module.

Lead Service/Contractor: USN, Military Sealift Command.

Current Fielding Status: OA module fully operational in Military Sealift Command. Sealift scheduling and forecast analysis has already been integrated into JFAST. SEASTRAT maintains the files management functions. SEASTRAT is scheduled to be phased out entirely by end of 1998.

DIICOE Compliance Rating: Not rated.

Point of Contact: Mr. Mike Bowler at DSN 325-5345.

Updated by: Capt Joseph J. Zarba Jr., USMC, CCSC-99.

 

Secondary Imagery Dissemination System

(SIDS)

Primary Purpose: SIDS is an umbrella term used to describe equipment and software used to receive, transmit, and exploit imagery products. Can also include any imagery manipulation software hosted on any computer systems. The Fleet Imagery Support Terminal (FIST) is an example of dedicated SIDS equipment. Electronic Light Table (ELT) is a software program hosted on JDISS and IAS systems used as a SIDS device. PC Light and VPF View are commercial versions of SIDS software.

Transmit, receive, and exploit current and archived imagery products electronically throughout the MAGTF (adjacent/higher) using available communications paths.

Sub-Functions: Support intelligence, weaponeering, and targeting for air and ground forces. SIDS provide means to transmit and receive exploited imagery

Equipment Reqs: There are two versions: Intelligence Analysis System (IAS) hosted variant, and a manpack variant. IAS variant consists of the input/output peripherals and software to process imagery from various sources and disseminate imagery to MAGTF elements or National assets. IAS hosts the system and will interface with other C4I systems through resident IAS communication links.

Manpack SIDS variant is self-contained, comprised of a base station and an out station. MAGTF SIDS: (MANPACK SIDS, OUT

STATION) Digital Camera, day and night lenses/image intensifier, Lightweight Digital Image Processor. (MANPACK SIDS BASE STATION) Lightweight Digital Image Processor, keyboard, modem.

(IAS Hosted system) Large Format Color / Black and White Printers, Flat-bed Image-quality Scanners, IAS suite with imagery software, Electronic light table (ELT3000), Paragon Imaging Inc.

Connectivity Reqs: High speed ethernet connections, SIRPNET, JWICS, Single Channel Radio, STU-III.

Crypto Reqs: Security required in conjunction with the transmission medium used and classification desired.

Normal Locations: Intelligence activities to the Battalion level. Unclassified generic SIDS capability may be found on any capable PC if proper software is loaded.

Information Managed: Digitized graphical information, pictures and scanned/archived images.

Products Created: Manipulated imagery, annotated with additional information relating to specific mission needs. Black to white polarization, zoom-in/zoom-out, and rotation. Level of manipulation depends on software being used.

Lead Service/Contractor: MARCORSYSCOM is the program manager. The Marine Corps Tactical Systems Support Activity

(MCTSSA) is responsible for software management. Versions of SIDS exist with all service components. Primary variable between SIDS variants is degree of graphic manipulation and transmission requirements, as well as quantity of information and level of security classification required.

Current Fielding Status: SIDS via IAS is in the Fleet Marine Force at the Regimental/MAG level and above. Plan to field systems to Battalion/Squadron level.

Known Problems: Interoperability between various SIDS terminals and non-standard software is difficult.

DIICOE Compliance Rating: Not rated.

Updated by: Capt Bonifacio Vinfrido, USMC, CCSC-99.

 

Systems Planning Engineering and Evaluation Device

(SPEED)

Primary Purpose: Support USMC tactical communications systems planning, engineering and evaluation processes.

Sub-Functions: Point-to-Point planning (PTP), Graphical User Interface (GUI), Radio Coverage Analysis (RCA), Position Locating Reporting System (PLRS), Enhanced Satellite Planner capability (SATPLAN), SINCGARS co-site planner.

Equipment Reqs: 486 or greater PC, CD-ROM, 16 Megs RAM, Windows 95 O/S, and Math Co-Processor.

Software: SPEED software package - Version 6.1 for Windows 95 on two CD, includes DTED (Digital Terrain Elevation Data) for entire world

Connectivity Reqs/Crypto Reqs: None.

Normal Locations: Distribution to any level.

Information Managed: Path Profiler, PLRS Planner, High Frequency Planner (HF), Switched Network Automated Planner, World-wide Topographic Loader, Tactical Network Automated Planner, Battlefield Electronic, Communications-Electronics Operations (CEOI) Systems, and Equipment Database.

Product Created: Reports, maps and planning matrices.

Lead Service/Contractor: USMC, Joint Spectrum Center (JSC)/IIT Research Institute in conjunction with Marine Corps Tactical Systems Support Activity (MCTSSA).

Known Problems: Topographical information needs to be loaded before each operation. Terrain Data not detailed; doesn't take into account vegetation or man-made objects.

DIICOE Compliance Rating: Not rated.

Point of Contact: Mr. Kenneth Wilson – Commanding Officer MCTSSA (CS-02.1, SPEED Project Officer) Box 555171, Camp Pendelton, CA 92055-5171; DSN: 365-2655 Comm: (760) 725-2655, email: KENNETH.WILSON@mctssa.usmc.mil

Updated by: Kapt Piotr M. Zurawski, Polish Army, CCSC-99.

 

Special Operations Command, Research, Analysis, and Threat Evaluation System

(SOCRATES)

Primary Purpose: Umbrella concept of systems, provides automated intelligence connectivity and functional intelligence support to the SOF community.

Sub-Functions: LAN provides personnel with access to the Defense Intelligence Threat Data System (DITDS), Intelligence Data Handling System (IDHS), Modular Architecture for Exchange of Intelligence (MAXI), Defense Data Network (DDN), and administrative message handling, transferring and formatting functions.

DITDS: combines data bases allowing users to filter through massive amounts of current and historical information/intelligence legend data and select, save, modify and/or transmit as required. Provides access to specialized collection of information on terrorism, counter-narcotics (Emerald) data base, and special operations (SOLOG) data base. Provides tools necessary to generate timely and accurate assessments, warning and threat analyses, and on-line access to record traffic communications system (GENSER/DSSCS and AFAMPE)

IDHS: primary repository of all data required to analyze and maintain information necessary to support normal operations and to adequately respond to a crisis situation. Provides access to the CENTCOM/SOCOM Integrated Data System (CSIDS/IDB), Defense Intelligence Agency's (DIA) and Military Intelligence Information Data System Integrated Data System (MIIDS/ITB).

MAXI/MIDAS: Automated intelligence message handling system; organizes the flow of operational traffic, facilitates review of incoming information, provides access to internal message and work files, intra-communication, report generation capabilities.

DDN/SCAMPI remote host access connects approximately 50 commands and agencies comprising the Department of Defense intelligence Information system (DODIIS).

Equipment Reqs: ADP System is three mainframe computer systems with internet/NIPR/SIPR capability and SCI LAN. Standard stand-alone configuration is a 486 PC with modem and video card, though a Pentium processor is desired.

Connectivity Reqs: USSOCOM SCI LAN, SOCSOUTH LAN, USCENTCOM LAN, VARIOUS COMPONT SCI LAN, SOCEUR LAN, SOCPAT LAN. Remote LANs connected through SCAMPI communications. Deployed terminal connected though tactical communication at 256 Kbps - 1.544 MBPS data rate from CINCSOC to JSOTF.

Crypto Reqs: The same as the SCI LAN or SCAMPI.

Normal Locations: USSOCOM, COMPONENT HEADQUARTERS, USCENTCOM, SOCSOUTH, SOCEUR, and SOCPAC, JSOC, Special Forces Group Military Intelligence Companies, and Ranger Battalions.

Information Managed: Record traffic communications, and a variety of data bases to include: CSIDS/IDB, MIIDS/IDB, SOLOG, and EMERALD.

Products Created: Data, imagery, message traffic, mapping. See sub-functions.

Service/Contractor: USSOCOM.

Current Fielding Status: In system.

Known Problems: The system is slow to respond during the peak hours of use.

DIICOE Compliance Rating: Not rated.

Updated by: CPT Jeffrey D. Lucas, USA, CCSC-99.

 

 

Submarine Satellite Information Exchange Sub-system

(SSIXS)

Primary Purpose: Designed to complement terrestrial Very Low Frequency (VLF) and Medium Frequency / High Frequency (MF/HF) communication links between shore-based submarine Broadcast Control Authorities (BCAs) and submarines.

Sub-Functions: Sub-system of the Navy Ultra High Frequency Satellite Communications System (UHF SATCOM).

Equipment Reqs: Shore based transmission via AN/FSC-79 Satellite Communication Terminal or AN/WSC-5(V) UHF Transceiver. Om-43A/USC PSK Modem, AN/FYK-33/FSQ Smart, ON-143(V)3/USQ or ON-143(V) 4/USQ Interconnecting Group, AN/FYK-29 Processor, SB-4325/FSQ Patch Panel, RD-379B (V)3/U Recorder-Reproducer, RO-600/U Teleprinter, MU-851 (U) 1/U Recorder-Reproducer, TT-835/U system Console, AN/FYK-32/FSQ Operator Console, RP-357/FSQ Recorder-Reproducer.

Shipboard Site: AN/WSC-3 (V) 2 Transceiver, PSK Modem, ON-143(V)5/USQ or ON-143(V) 6/USQ Interconnecting Group, AN/FYK-29 or AN/FYK-20(V) Processor, AN/UGC-20B or AN/UGC-136AX Teletypewriter Set, Recorder-Reproducer (Keyboard Punch), CV-3333/U Converter Audio-Digital, AN/USQ-64(V)3 SSIXS Subscriber Terminal.

Connectivity Reqs: One 25kHz wideband channel on each of the FLTSATCOM satellites is allocated for SSIXS. A single SSIXS network may have up to 120 submarine subscribers. A single network may be established on more than one satellite or two BCAs may share a single satellite channel by offsetting the time of their respective Group Broadcast transmissions.

Crypto Reqs: TSEC/KG-35, 36

Normal Locations: All SSN and SSBN submarines. All five BCA sites:

NCTAMS LANT Norfolk, Virginia

NCTAMS MED Bagnoli, Italy

NCTAMS WESTPAC Finegayan, Guam

NCTAMS EASTPAC Wahiawa, Hawaii

NCTS Stockton Stockton, California

Some NCTS’s are capable of retransmitting the satellite signal via HF.

Information Managed: Ship-to-Shore and Shore-to-Ship communications.

Products Created: Emergency Action Messages, Reports, and voice communications.

Lead Service/Contractor: United States Navy

Known Problems: System only effective if ships are within satellite footprint. Limited world coverage due to orbit tracks of satellites.

DIICOE Compliance Rating: Not rated.

Updated by: Capt Dan Hanks, USMC, CCSC-99.

 

Shore Targeting Operational Support System

(STOSS)

Formerly known as Shore Targeting Terminal (STT)

Primary Purpose: Provides Submarine Operating Authorities (SUBOPAUTHs) essential contact location data and precise, real-time OTH-T data to submarines for targeting in cruise missile employment. Output is used by submarines to compute Tomahawk Anti-Ship Cruise Missile (TASM) OTH-T targeting solutions and to determine best over-the-water flight path for Tomahawk Land Attack (TLAM) missions. Provides contact data to submarines in their ASW role.

Sub-Functions: Integration of shore targeting and requirements for use by submarine forces into Global Command and Control System – Maritime Ashore (GCCS-M Ashore) as a part of the Operational Support System (OSS) software segment. Capable of interfacing with multiple external interfaces to capture ocean surveillance information from supporting sensors and sources. The data is processed, correlated, and distributed to maintain a database of selected tracks.

Equipment Requirements: Same as for GCCS-M Ashore

Connectivity Requirements: Same as for GCCS-M Ashore

Crypto Reqs: Same as for GCCS-M Ashore

Normal Locations: Submarine Operating Authority (SUBOPAUTH), Submarine Operational Command Center (SOCC): COMSUBLANT/Norfolk, COMSUBPAC/Pearl Harbor, COMSUBGRU Seven/Yokosuka, COMSUBGRU Eight/Naples

Info Managed: Surface and subsurface contact information from multiple sources for oceans worldwide. Collects, correlates, stores, and disseminates hostile, neutral, and friendly contact locating data and Allied submarines. OTH-T data to submarines equipped with TASM and TLAM for cruise missile employment.

Products Created: Textual and graphical representations of both surface and sub-surface contacts. Message output interface.

Lead Service/Contractor: US Navy (Space and Naval Warfare Systems Command)

Current Fielding Status: STOSS has been in use by the four SOCCs since 1993.

Known Problems: None.

DIICOE Compliance Rating: Level 5.

Point of Contact: Space and Naval Warfare Systems Command (SPAWAR) – Ashore Program Manager (PMW-157), comm: (619)537-0258, FAX comm: (619)553-6519.

Internet: http://c4iweb.spawar.navy.mil/pm/ashore/ (password needed).

Updated by: Capt Richard A. Eckles II, USMC, CCSC-99.

 

Shipboard Uniform Automated Data Processing System

(SUADPS)

Primary Purpose: Monitor logistical, inventory, and batch transactions. Record and maintain inventory, demand, and requisition data

Sub-Functions: Financial transaction accounting and reporting.

Equipment Reqs: NTCSS AN-UTK 65 mainframe architecture with Windows 3.11/NT workstations.

Connectivity Reqs: LAN/WAN. SALTS (optional w/ LAN or modem). INMARSAT (optional).

Crypto Reqs: None.

Normal Locations: All Marine Aviation Logistics Squadrons (MALS). NSCS Athens, MATSG Meridian. CV/CVNs, LH-hulls, Tenders and TAFS vessels.

Information Managed: General material including repair parts in support of USMC aviation. Inventory management functions. Financial planning and reporting. Logistical and incoming batch transactions.

Products Created: Financial Inventory Reports (FIR). Material Management Reports. Inventor Management Reports. Operating Target (OPTAR) Reports. Requisition Management Aids/Reports. Department of the Navy Stock Fund (DONSF) Reports.

Lead Service/Contractor: USN/SPAWARSYSCEN Chesapeake.

Current Fielding Status: In use with USN and USMC.

Known Problems: Stovepipe system. Restricted data access. High software maintenance costs.

DIICOE Compliance Rating: Not rated.

Point of Contact: Functional Manager; NAVSUP-431 (LCDR Burr) DSN: 430-7437. Software Support; SPAWARSYSCEN-312 (Ray Bowden) DSN: 565-8161.

Updated by: Capt Andrew L. East, USMC, CCSC-99.

  

Tactical Digital Information Link-J/NATO LINK-16

(TADIL-J)

Primary Purpose: Using the Joint Tactical Information Distribution System (JTIDS) equipment provides real-time exchange of tactical digital information between major command and control systems for the United States, North Atlantic Treaty Organization (NATO), and allies. Pseudo random frequency hopping on 51 frequencies, encrypted. Frequency hopping rate is one pulse per 13 microseconds.

Sub-Functions: Joint Tactical Information Distribution System (JTIDS).

Equipment Requirements:

Three groups of terminals: JTIDS Class 1 - First generation, single network; JTIDS Class 2 - Second generation, multiple network capability (AN/VRC-107 V 5-7); Multifunction Information Distribution System Low Volume Terminals (MIDS-LVT); Command and Control Processor (C2P)- Navy.

Connectivity Requirements: JTIDS frequency hopped/spread spectrum system requires at least 150 MHz bandwidth (data rate-28.8 Kbps to 238.1 Kbps). UHF (L Band).

Crypto Requirements: KOI-18 KGV-8B, Secure Data Units AN/CYZ-10, Data Transfer Device

Normal Location: Major command and control facilities; surveillance platforms; fighter and intercept aircraft; and air defense units.

Information Managed: Common Operating Picture (COP) and Common Tactical Picture (CTP).

Products Created: Interim JTIDS Message Specifications (IJMS); J Series messages.

Lead Service/Contractor: USAF.

Current Fielding Status: Major theater assets have or are being fielded. Established as the joint standard for future system and platform development. Other TADILs being consolidated into the TADIL-J format. TADIL-J being incorporated into the GCCS COP.

Known Problems: Dispersed (beyond 300 NM) theater-wide operations requires relay capability for extended line of sight (LOS) maneuvers. Program managers developing satellite based TADIL-J capabilities to eliminate this limitation. Additionally, limited distribution of the assets to conduct these operations.

DIICOE Compliance Rating: Not rated.

Point of Contact: DSN: 524-3170 FAX: x2550, COM: (619) 524-3170 FAX: x2550.

Internet: http://webix.nosc.mil (SPAWAR link 16 support website); http://link 16@spawar.navy.mil (OSC Larry Rucks).

Updated by: Capt Kenneth Knarr, USMC, CCSC-99.

 

T-AVB Automated Load Planning System

(TALPS)

Primary Purpose: Formally T-AVB ALPS. Automated load planning process that considers and incorporates ship characteristics, load and stabilization requirements for T-AVB ships. TALPS automatically calculates ships trim and stability factors and is certified by the American Bureau of Shipping (ABS) to produce "safe" loads.

Sub Functions: Supports deliberate planning. Allows multiple load plan development to meet mission requirements. Assists in the development of embark plan.

Equipment Reqs: T-AVB 3 or 4 (C5-S-78a Sea bridge class container, RO/RO cargo ship). 486DX (or better, recommended P5-133 or above). 16meg RAM (minimum) 20 meg free hard disk space (minimum).

Connectivity Reqs: Telephone line with modem to exchange data with Computer Aided Embarkation and Maintenance Management systems (CAEMS) and the MAGTF II Logistics Automated Information System (LOGAIS).

Crypto Reqs: None.

Normal Locations: Marine Aviation Logistics Squadrons and T-AVB ships.

Information Managed: Load plan data.

Products Created: "SAFE", automated, T-AVB load plans and printouts.

Lead Service/Contractor: HQMC (ASL-34).

Current Fielding Status: In use with the USMC and Maritime Administration (MARAD).

Known Problems: TALPS is not designed to handle "grain" type cargoes. TALPS development is incomplete.

DIICOE Compliance Rating: Not rated.

Point of Contact: Project Officer: LtCol J. M. Thornton, phone (703) 614-1133/1028.

Updated by: Capt William J. Mattes Jr., USMC, CCSC-99.

 

Tactical Automated Mission Planning System

(TAMPS)

Primary Purpose: To assist naval aviators with flight mission planning giving consideration to enemy air defenses and terrain.

Sub-Functions: Can assist in all aviation related MOS's with flight support mission planning (giving consideration to enemy air defense capabilities and terrain) and when planning communications and other terrain affected weaponry.

Equipment Reqs: Stand alone computer system which works on a UNIX based Sun SPARC system.

Connectivity Reqs: Can be configured for use over a LAN. Requires the same type of connectivity system both on the receiving side and on the sending side.

Crypto Reqs: None. Uses a locally controlled password protected system and is classified SECRET/NOFORN.

Normal Locations: Marine Aircraft Group level or higher and MAWTS-1. All squadrons will have the system in the future.

Information Managed: Can be programmed to manage all classified and unclassified enemy and friendly air defense information to be used for future mission planning.

Products Created: Information can be printed as charts (either two or three dimensional) or database reports. Information is only as good as what is in the system (either through software or operator entry).

Lead Service Contractor: United States Navy. Originally developed by the Naval Weapons Center. Software created by TRW & Lockheed Martin, test and evaluation is headed by Brandis Software.

Current Fielding Status: DISA is planning to integrate several other aircraft-unique planning systems into TAMPS. Currently fielded in three different systems; DTC/2, DTC/3, and ACE/VME. ACE/VME will be fielded to the squadrons. Remaining systems are at the Group and Wing Levels.

Known Problems: Some software problems (inaccurate database information for several of the aircraft and air defense in the system). Most problems have been identified and are being corrected.

DIICOE Compliance Rating: Not rated.

Point of Contact: MCTSSA West, Ms. Jazacher, DSN: 365-2371.

Updated by: Capt Keith E. Whitehouse, USMC, CCSC-99.

Tactical Airborne Reconnaissance Pod System and Digital Imaging

(TARPS and TARPS DI)

Primary Purpose: Near-real-time tactical photo reconnaissance.

Sub-Functions: The TARPS pod is presently being used as a test platform by the Navy Research Lab, (NRL) at the Naval Air Station Patuxtent River as a completely digital REAL TIME transmission system. The information gained with these efforts will probably incorporated into the SHARPS program and/or ATARS program.

Equipment Reqs: LA-610: TARPS pod mounted on weapons station #5 on the F-14. Mounted in the TARPS pod: KS-87D Serial Framing camera. KS-153 long range standoff framing camera or the KA-99 Low Altitude panoramic camera. AAD-5: Infrared Line Scanner. Near Real-time Digital Imaging system. AN/ASQ-197: Digital Data sensor control system.

Connectivity Reqs: Film is hand carried to the EH-8 Film processor located either in CVIC or the Photo Lab of the ship. Connectivity: KY-58 UHF one-way transmission link to the Digital Photo Lab aboard the command and control ship.

Crypto Reqs: DI imagery is transmitted through the KY-58 encrypted data channel. Imagery classification depends upon the subject matter of imagery.

Planned Capability: Incorporation of the DI system has been completed. An offshoot version of the TARPS C.D. pod by NRL may also end up incorporated into the current pod

Normal Locations: Four pods in each carrier wing F-14 squadron at all times. Forty-seven total pods in the Navy, and over 110 TARPS capable F-14's in the Navy.

Information Managed: Hard Copy imagery and near real-time DI images.

Products Created: Film and digital photo imagery.

Lead Service/Contractor: USN/ Grumman (production discontinued)
Depot level maintenance conducted at Hill AFB along with various vendors.

Current Fielding Status: TARPS is scheduled to remain in service until it is replaced with SHARPS / ATARS around 2005.

Known Problems: pod unreliability and maintenance problems were increasing until a pod overhaul program was completed recently. Reliability has since then increased twofold. Problems have decreased due to new pod wiring, new sensors and the reduced use of wet film (KS-87 / DI option).

DIICOE Compliance Rating: Not rated.

Point of Contact:
Mr Neil Bellamy TARPS Rep @ NAS Oceana: e-mail
TARPSREP@AOL.COM;
Mr Ron Bowers Natec TARPS Rep @ NAS Oceana e-mail
CFWLTARPS@AOL.COM; Mr Frank Remezki Natec TARPS Rep @ NAS Oceana e-mail CFWLTARPS@AOL.COM; Mr Frankie Vazquez TARPS Rep @ NAS Oceana e-mail CFWLTARPS@AOL.COM (all have the same phone #'s)
757-894-1337 or 757-377-0623.

Updated by: Capt Andrew L. East, USMC, CCSC-99.

 

Theater Battle Management Core Systems

(TBMCS)

Primary Purpose: TBMCS is the Combat Air Force (CAF) information and decision support system supporting combined and joint air operations for the joint forces.

Sub-Functions: TBMCS integrates CTAPS, WCCS and CIS under a common core of services. TBMCS 1.0 will parse standard C2IPS airlift messages and populate its campaign database with airlift information.

Equipment Requirements: GCCS will provide hardware and software standardization.

Normal Locations: Air Operations Center, Air Support Operations Center, Wing Operations Center, Maintenance and Squadron operations center as well as service equivalents

Information Managed: TBMCS functionally will include intelligence processing, air campaign planning, execution and monitoring, aircraft scheduling, unit level maintenance operations, unit and force level logistics planning, and weather monitoring and analysis.

Products Created: Air Tasking Order.

Lead Service/Contractor: USAF/Lockheed-Martin Corporation in Colorado Springs, CO.

Current fielding status: Currently under development, TBMCS 1.0 is due out in Mar 99.

Known Problems: The delivery schedule was changed from Mar 98 to a single release date of Mar 99 due to CTAPS and FY 97 funding problems.

DIICOE Compliance Rating: Level 8.

Point of Contact: Ms. Mary Artz, AMC functional manager (618) 256-4666 DSN 576-4666. Maj. Alex Bays (618) 256-4484 DSN 576-4484.

Internet: http://sctaweb.scott.af.mil/irc/main.html

Updated by: Capt Randy W. Ross, USMC, CCSC-99.

 

Transportation Coordinator’s Automated Information for Movement System

(TCAIMS)

Primary Purpose: Day-to-day material and personnel transportation management. Provides MAGTF Commander with the automated ability to plan, coordinate, manage, and execute MAGTF operations relative to various phases of transportation.

Sub-Functions: Military Standard Transportation and Movement Procedures (MILSTAMP) documentation including Transportation Control Number (TCN) generation and creation of Transportation and Control Movement Documents (TCMDs). Can be used for engineering equipment. Provides the ability to create and maintain an inventory of transportation support assets; and to create, send, receive, and execute transport and support requirements.

Equipment Reqs: IBM compatible Pentium 166 MHz computer.

Connectivity Reqs: Unclassified e-mail may be transmitted via Banyan Vines LAN systems.

Crypto Reqs: None. Classified data must be stored on a removable hard drive.

Normal Locations: G-4, S-4, Transportation Management Offices, Garrison Mobile Equipment (GME) manager, and selected motor pools.

Information Managed: Transportation/Engineer assets, in transit location visibility, identifies hazardous materials (HAZMATs).

Products Created: All required MILSTAMP documentation and Transportation Control Manifest Documents.

Lead Service/Contractor: MARCORSYSCOM, Quantico, VA. Contractor: Stanley Associates.

Current Fielding Status: Version 4.1A fielded to all USMC organization in July 1998. Selected sites and sister services will receive TCAIMS II in the first quarter of FY 1999.

Known Problems: (1) Current software does not possess capability to plan/display route maps. (2) Current users require additional commercial software such as PC MAP MAKER to provide route/weight limitations, etc.

DIICOE Compliance Rating: Level 5.

Point of Contact: CAPT Brierly or Mr. Tom Voth, DSN 567-6625 COMM (703) 784-6625

Updated by: CPT Kevin P. Romano, USA, CCSC-99.

  

Tactical Combat Operations

(TCO)

TCO to be incorporated into IOW FY99-00

Primary Purpose: To enable the establishment and maintenance of the Common Tactical Picture and to process information relative to this purpose from all available sources.

Sub-Functions: Mission, FS planning.

Equipment Reqs(min): DTC-2(Desktop Tactical Computer), TAC-3(Tactical Advanced Computer, version 3) or RSC-1X/2X("gray box").

Connectivity Reqs: The only requirement for connectivity is that the TCO be linked to a TDBM (Track DataBase Manager). This is usually accomplished through the LAN. There are many connectivity options through the TDBM to include: WAN, Link 11, Link 14, STU-III, etc.

Crypto Reqs: No external requirements.

Normal Locations: All commands down to many of the Regiments/Groups. Eventually to the Battalion/Squadron level.

Information Managed: Display, manipulation and coordination of friendly and enemy situation as well as tactical control measures, weapons and Elint platforms via a raster graphic digitized map.

Products Created: Situational overlays and a view of the common tactical picture.

Lead Service/Contractor: USMC/PRB.

Current Fielding Status: Currently at MEF, WING/DIV, MEU and some Regt/Groups. Plan to implement at the Battalion/Squadron level.

Known Problems: Requires dedicated and stable communications.

DIICOE Compliance Rating: Level 5.

Point of Contact: Ms. Jody Truelove, DSN 784-5156, truelovej@mstp.quantico.usmc.mil; MARCORSYSCOM, Capt. Randy Walker, DSN 784-1019 ext 2560.

Internet: http://sscc-commandlab.spawar.navy.mil/usmc/.

Updated by: LT Felice Miraglia, Italian Marine Corps, CCSC-99.

 

 

Tactical EA-6B Mission Planning System

(TEAMS)

Primary Purpose: Compiles radar system libraries, navigation data, and high speed anti-radiation missile (HARM) targeting libraries for download to the EA-6B ALQ-99 On Board System (OBS) used during electronic warfare missions.

Sub-Functions: Intelligence, post-mission analysis, route and fuel planning, and GPS Mission Data Loader support for EA-6B GPS.

Equipment Reqs: AN/TSQ-142 V(5) or 142V(6) (portable or rack-mounted) system, four TAC-3 (HP-735) processors, Raymond Recorder Reproducer Set (RRS) and various input/output hardware including CD-ROM, 8MM digital audio tape (DAT), and Media Assembly consisting of 2 PCMCIA Slots and a 3 ½" Floppy Drive. Laser Jet and Color printers.

Connectivity Reqs: Provides mission libraries to EA-6B via RRS tape. TEAMS is capable of running as a stand-alone system. There is a Data Fusion Processor that is capable of receiving data from Tactical Electronic Reconnaissance Processing and Evaluation System (TERPES) via STU III (2.4 KBPS) and from Military Intelligence. Military Intelligence Integrated Data System/Integrated Data Base (MIDB 1.4) via CD-ROM. TEAMS will transition to MIDB 2.X in order to complete to migration to GCCS-M. Currently fielded to all EA-6B squadrons, both Navy and Marine. Receive intelligence from modernized IDB via 8MM DAT, from GCCS-M central data base, from Air Force Combat Intelligence System (CIS) via Ethernet and from TRAP and TADIXS-B via serial line (4096 baud) to tactical receive equipment (TRE). Possibly, receive intelligence from tactical intelligence broadcast system (TIBS), commander's tactical terminal (CTT), and multi-mission advanced tactical terminal (MATT). (This requirement currently awaiting fleet validation.) Receive ATO form CTAPS and Air Force wing C-2 system via Ethernet. Provides post-mission intelligence to GCCS-M correlator and Air Force CIS via Ethernet.

Crypto Reqs: No crypto used. Removable hard drives and RRS classified SECRET.

Normal Locations: One TEAMS system at each VMAQ and VAQ squadron.

Information Managed: Emitter electronic parameters and location data, Enemy Command and Control Networks planning data, HARM targeting libraries, airfield and navigation aid data, terrain data, digitized graphics map images, specific emitter identification data, communication network databases and Global Positioning System (GPS) almanac and waypoint information.

Products Created: EA-6B mission libraries, navigation and fuel logs, charts, transparencies, and weapon system knee board cards.

Lead Service/Contractor: USN/PRB Associates Inc.

Current Fielding Status: TEAMS versions 205.03 fielded in 1998, which incorporated support for UEU transmitters as well as C2W functions. GCCS-M/DII migration is on going. TEAMS build 206.01 will be a GCCS-M module with an anticipated release of October of 1999. As EA-6B is undergoing 89A and ICAP III migration, TEAMS is conducting a parallel build to support the new functionality. Future improvements will include support for the Low Band Transmitter, HARM improvements, C2W Analysis, and USQ-113V(3) support.

Known Problems: TAMPS migration was scrapped due to the immaturity of the TAMPS hardware compared to TEAMS (1 vs. 4 processors, 4 gigabytes of hard drive storage vs. 16 gigabytes of hard drive storage). As GCCS-M moves toward DIICOE compliance, TEAMS will become a module of GCCS-M.

DIICOE Compliance Rating: TEAMS 206.01 will be level 5 compliant.

Point of Contact: Phil Dupree or Dave Perrin, (301) 373-2360 fax (301) 383-2388X144 w/PRB Associates, Hollywood, MD.

Updated by: Capt Kelly G. Dobson, USMC, CCSC-99.

 

Tactical Electronic Reconnaissance Processing and Evaluation System

(TERPES)

Primary Purpose: The TERPES is a tactical Marine Corps asset designed to process, sort, analyze, display, and correlate digital Electronic Warfare Support (ES) and Electronic Attack (EA) data recorded by EA-6B aircraft. The processed data results in Electronic Intelligence (ELINT) that is used by both the

Air Combat Element (ACE) and Ground Combat Element (GCE) of a Marine Air-Ground Task Force (MAGTF) to determine the extent of the enemy electronic threat and to plan combined arms operations.

Equipment Regs:

1. Sun Ultra Workstation (Qty 2) - 9.1GB removable hard drive, 512MB Random Access Memory (RAM), 12X CD-ROM, 20" flat panel display

2. Sun Ultra File Server (Qty 1) - 512MB RAM, 4mm tape drive, 8mm tape drive, 12X CD-ROM, 20" flat panel display

3. Removable Hard Drives - Seven (7) 9.1GB (63.7GB total)

4. Peripherals - Raymond Recorder-Reproducer Set (RRS) (Qty 2),

Uninterruptible Power Supply (UPS), Red/Black Virtual Memory Extension (VME) chassis, MST-ICOM transceiver (Qty 2), RF-590A High Frequency (HF) receiver, HP 750CM plotter, HP 1600CM printer, MX-512P(V) data terminal set with Panasonic CF-25 laptop computer.

Connectivity Regs: Integrated Contingency Communications System (ICCS) - CGS-100 Lite communications gateway, Local Area Network (LAN) transceiver, Cisco 2514 router.

Crypto Regs: KG-40, KGX-40, KIV-7 (Qty 4), AN/USQ-101(V)5 Tactical Receive Equipment (TRE), STU-III Secure Telephone Unit, 1910 Dataphone.

Normal Locations: Each Marine Tactical Electronic Warfare Squadron (VMAQ) detachment deploys and is based with its parent squadron, including operations at expeditionary airfields with the senior MAGTF air combat element command. The system does not routinely deploy to forward operating bases, unless accompanying a senior MAGTF ACE command. The system shall deploy for use in field environments for the period of time necessary to accomplish the mission.

The system may be used to support the Joint Force Commander (JFC) or Marine Component Commander, if the Marine Expeditionary Force (MEF) Commanding General is assigned those roles. In garrison, the system will support mission planning, contingency

operations, exercise support, and training.

Information Managed: ELINT.

Products Created: The TERPES supports the planning for air missions, provides briefs to aircrews, prepares technical information for the EA-6B Electronic Warfare (EW) mission, processes the EA-6B mission information, and issues ELINT reports to the MAGTF.

Lead Service/Contractor: USMC.

Fielding Status: Initial Operational Capability IOC 09/30/98. Full Operational Capability FOC 03/31/99.

DIICOE Compliance Rating: Not rated.

Point of Contact: Project's APM Office: MAGTF C4I Intelligence Project Officer: CWO Bruce Vickers at Comm: (703) 784-1019 Ex: 2534.

Updated by: Capt David B. Turcotte, USMC, CCSC-99.

  

Tactical Flag Command Center/Flag Data Display System

(TFCC/FDDS)

Primary Purpose: Support OTC/CWC planning and resource management. Also supports battle management in the execution phase.

Sub-Functions: Officer in Tactical Command (OTC)/Composite Warfare Commander (CWC) battle station. One of approximately 10 C2I components/configurations to operate under Joint Maritime Command Information System (JMCIS).

Mission is to filter, correlate, process, manipulate, purge, store, retrieve, and display data to provide OTC/CWC with several interactive data bases, an integrated long-range geographic picture (including sensor and weapon coverage upon request), numerous planning and decision aids, and assistance in generating messages for transmission.

Equipment Reqs: 8-16 Tactical Advanced Computer(TAC)-IIIs used with 3 or 4 projection screens.

Connectivity Reqs: Operates within JMCIS Ethernet LAN/Fiber Comm Ring.

Crypto Reqs: None. JMCIS employs variety of crypto devices (KG-84A/C, KGR-96, KW-84A, KG-81, and KG-194) prior to multiplex transmission.

Normal Locations: All major fleet command ships (CVs, LHA's, LHDs, and LCCs).

Information Managed: Ship movements/ positions, SIGINT displays, OTH radar displays tracked via the Joint Operational Tactical System (JOTS), weather, etc.

Products Created: No unique products created. Is the work center registering information for OTC/CWC through Contingency Theater Air Planning System (CTAPS), JOTS, GCCS, and TFCC Information Management System (TIMS).

Lead Service/Contractor: Naval Inter-Service Engineer-East (NISE EAST), Norfolk, VA DSN 961-0619, FAX 961-0721.

Principle contractor is SEMCOR Corporation, Chesapeake, VA.

Fielding Status: TFCC/FDDS components virtually unlinked to other C4I systems prior to 1993. TFCC began operation in the LAN environment Naval Tactical Control System-Afloat (NTCS-A) in 1993.

Known Problems: NISE EAST unaware of any significant problems with TFCC technical operations.

DIICOE Compliance Rating: Not rated as a separate system (tied to GCCS-M- level 5)

Point of Contact: Mr. Carey Butterworth, SPAWAR Systems Center, Comm: (757) 558 6781; fax 558 0721. DSN: 961-6781 (0619, 0378); fax 961-0721. (butterwo@spawar.navy.mil).

Updated by: Capt Neil M. Bennett, UK Royal Marines, CCSC-99.

  

Tactical Network Analysis and Planning System Plus

(TNAPS+)

Primary Purpose: Computer based desktop System Planning and System Control (SPSC) tool comprised of integrated software modules designed to automate the planning, engineering, database development, network analysis, and management for tactical communication networks. TNAPS+ is a joint communications standard.

Sub-Functions: Ten self-explanatory modules: exercise requirements, circuit switching, message switching, transmission networks, COMSEC, system control and management, reports standard requirements, site mux plans, and system administration.

Equipment Reqs: IBM PC 486/66 or above, color monitor, Windows 95, DOS 6.0 or higher. Program modules are 90% Windows, 10% DOS.

Connectivity Reqs: Stand-alone PC version currently fielded; network version planned for future release (Version 3.0/JAN 98).

Crypto Reqs: None.

Normal Locations: Network planning commands and user level units across the Joint community.

Information Managed: Network and equipment databases for each exercise/operation.

Products Created: Numerous network level and nodal/equipment level output reports describing resulting networks and equipment configurations/status.

Lead Service/Contractor: USAF Electronic Systems Command, Hanscom AFB, MA, Logicon 950 N. Orlando Ave, Winter Park, FL.

Current Fielding Status: TNAPS+ version 3.1 (May 1998), distributed to Air Force and the Joint Community. Two "patch" type releases planned. First patch release scheduled Oct ‘98. Second patch release scheduled Apr ‘99.

DIICOE Compliance Rating: Not rated.

Point of Contact: Joan Wandrei, Program Manager HQ ESC/DIGD, Hanscom Air Force Base DSN: 478-7965.

Internet: http://www.esc-digd.hanscom.af.mil/tnaps.

Updated by: CPT Lisa D. Whittaker, USA, CCSC-99.

 

Tactical Reconnaissance Intelligence Exchange System

(TRIXS)

TRIXS system will migrate to CIB-S by end of year FY01

Primary Purpose: Tactical battlefield broadcast network providing direct near real time (NRT) signals intelligence (SIGINT) for targeting and destroying enemy C3I nodes.

Sub-Functions: Built on existing USA Guardrail Common Sensor System (GCSS, RC-12) intelligence dissemination network. Network receives and processes data from Guardrail, USAF U2R (Senior Span) and Joint Strike Target Attack RADAR System (JSTARS), and USN EP-3 (Storyteller/Aries). Line of sight coverage extends to approximately 350 Km from aircraft. Disseminates tactical intelligence and targeting data (i.e. COMINT and ELINT) to receivers using the Joint Tactical Terminal (JTT). Information designed to flow simultaneously to the Joint Force Commander (JFC), Corps, Division, Brigade, Battalion, and other commanders (i.e., artillery, aviation, ADA, etc) providing each enhanced battlefield situational awareness. Provides dedicated capability to dynamically adjust tasking of selected airborne reconnaissance surveillance and target acquisition systems during ongoing missions through the use of simultaneous secure data and voice capabilities. Interoperable with Army, Navy, Marine Corps, and Air Force C2I nodes. Broadcast information is intended for use at all echelons for targeting, maneuvering, threat avoidance, sensor cueing, mission planning, and situation/threat development.

Equipment Requirements: Network users must have UHF radio receiver/transmitter to connect to the network and host processor (typically a UNIX based workstation) to display the information on a computerized map. Preferred terminal equipment is the Joint Tactical Terminal (JTT, formerly known as the Commander's Tactical Terminal). The terminals allow Army, Air Force, Navy and Marine Corps users to exploit Integrated Broadcast Service (IBS) networks: Tactical Reconnaissance Intelligence eXchange Service (TRIXS), Tactical Information Broadcast Service (TIBS), Tactical Related Applications (TRAP), and Tactical Data Information eXchange System-B (TADIXS-B). In addition to receiving intelligence data, JTT transmits TRIXS or TIBS data. The CTT and other IBS terminals are migrating to a single JTT family. JTT has ten receive and two transmit channels. It receives TRIXS, TIBS, TRAP and TADIXS-B. It transmits TRIXS and TIBS. The JTT will provide interoperation with the future IBS networks, to include NRTD. JTT terminals are composed of Common IBS modules (CIBS-M). JTT terminals will be connected to host systems and stand-alone configurations may also be provided. CIBS-M modules may be integrated directly into systems other than JTT terminals on a module-by-module basis.

Connectivity Requirements: Secure UHF LOS is usual mode of transmission. SATCOM capability exists if necessary. Other characteristics include 25 Khz bandwidth (32 Kbps) with simultaneous secure data and secure voice capability. Uses Have Quick II functionality for EP.

Crypto Requirements: JTT uses embedded crypto for both SCI or GENSER traffic.

Normal Locations: The JTT is integrated into other weapon systems and are transported with the host system. These systems include GSM/CGS, ASAS, ETRAC, THAADS, PATRIOT, JTAGS, Trojan Spirit, AFATDS, and other multi-service systems. The equipment can be mounted in fixed and rotary wing aircraft, surface, and fixed or mobile ground platforms and vehicles. It may be located with Force Component HQ-G2 (or J2), MEF G-2, Wing or Division G-2, Artillery Regts, ADA Bn, SOF units, and Air Force theaters.

Products Created: COMINT and ELINT NRT tactical information at GENSER and SCI levels. JTT can also receive secondary imagery products through the Army’s General Purpose Link (GPL) for Secondary Imagery Dissemination (SID).

Lead Service/Contractor: In 1997 Raytheon won a contract award valued at $133 million from the Army to fulfill joint services requirements for the production and preplanned product improvements of the Joint Tactical Terminal/Common Integrated Broadcast Service-Modules (JTT/CIBS-M). The Air Force is overseeing the implementation of broadcast services and systems.

Current Fielding Status: TRIXS will migrate to CIBS-M in FY99/00. TRIXS network integrated in GCCS, Rivet Joint RC-135, U2 CARS, J-STARS, AEGIS, USS Constellation, and A2C2. JTT/CIBS-M fielding scheduled for 4th quarter of FY98. IBS will introduce a common TDDS/TIBS/TRIXS/NRTD format during the transition phase of 1998-99 with portions of UHF broadcast transitioned to Global Broadcast Service (GBS) and other communications assets after 2000. The objective is to integrate broadcasts and interactive networks into DoD Communications Infrastructure.

Known Problems: None.

DIICOE Compliance Rating: Not rated.

Point of Contact: IBS Broadcast Program Management Office, Hanscom AFB/MITRE. MAJ T. McQuaid, DSN 478-1186 ext 4889, COMM (781) 271-4889. JSTARS/JTT Product Manager, LTC S. Kostek, DSN 987-5165, COMM (908) 427-5165, FAX (908) 427-5120, email sfae-iew-js@doim6.monmouth.army.mil.

Internet: http://huachuca-dcd.army.mil/iewsys/jtthe.htm

www.monmouth.army.mil/prjbk97/pmjstars/18-1.html

www.fas.org/irp/program/disseminate/trixs.htm

Updated by: Capt Matthew G. Rau, USMC, CCSC-99.

  

Tactical Remote Sensor System

(TRSS)

Primary Purpose: Provide continuous all weather location determination and monitoring of activity within a given area of operations.

Sub-Functions: Graphic depiction of objects through thermal graphic optics and classification through rotary wing air-delivered sensors (i.e. tracked vehicle, rotary winged aircraft, battlefield sounds, etc.)

Equipment Reqs: Each Sensor Mobile Monitor System (SMMS) has two monitoring stations located within that are comprised of one Gridcase 1535 and one MSBL HP-UNIX TAC-4 computer terminal.

Connectivity Reqs: LOS for tx/rx (VHF and HF) back to the SMMS. Operates in the VHF (138-153) MHz and UHF (new software). The SMMS includes a HF radio (AN/GRC-231) and two VHF radios.

Crypto Reqs: KY-99, KY-57.

Normal Locations: Sensor Control and Management Platoon (SCAMP). SCAMP will be either co-located with Intel Bn, or MEF’s HQ Bn.

Information Managed: ELINT reports, data derived by analysis of targets total seismic/magnetic/infrared/thermal graphic signature to provide direction, location, relative speed, quantity, length of column and classification type.

Products Created: Positive identification and classification of detected activity. Strip charts and image displays. Sensor reports (SENREP).

Lead Service/Contractor: MarCorSysCom, USMC.

Current Fielding Status: TRSS is 85% fielded. TRSS is awaiting additional funding to migrate to the Win NT environment by FY01.

Known Problems: Reading data created in NT.

DIICOE Compliance Rating: Not rated.

Point of Contact: GySgt Ted Salas, MarCorSysCom. DSN: 278-1019 ext. 2563.

Updated by: Capt Jeffrey H. Hauser, USMC, CCSC-99.

 

Tomahawk Weapons Control System

(TWCS)

Primary Purpose: Provides a capability to control surface launches of the TOMAHAWK Land Attack Missile (TLAM). Encompasses communication support, engagement planning, and launch control functions.

Sub-Functions: Provides the capability for a Battle Group Commander to maintain a common control system of the TOMAHAWK weapon platform. The Commander can arrange his TOMAHAWK platforms to fit the organization, designating which ship will be a active shooter or a non participant. TWCS also correlates and tracks air, surface, and subsurface contact reports from a number of interfacing systems. The system will disseminate force-level track database information and, based on the threat, issue engagement orders to those TOMAHAWK weapon systems identified as participants or shooters.

Equipment Reqs: Operator Interactive Display Terminal (OIDT), AN/SYK-14 computer, AN/SYK-11 random access storage set, AN/UYK-44 launch control unit, AN/SSH-6 Thermal Printer, WSN-5 shipboard gyro, AN/SYK-20 (UYK-64 computer), and Electronic TOMAHAMK Employment Planning Package (ETEPP).

Connectivity Reqs: Must be aligned with WSN-5 gyro for all missions. TWCS requires the following communications circuits for receiving/sharing off-board engagement orders: Officer-in-Tactical-Command Information Exchange System (OTCIXS) and Tactical Data Information Exchange System A (TADIXS A)

Crypto Reqs: Manually entered current day and current week crypto for GPS missions.

Normal Locations: CG 47 (TICONDEROGA) Class Cruisers (CG 52 and higher hull number), DD 963 (SPRUANCE) Class Destroyers, DDG 51 (ARLEIGH BURKE) Class Destroyers, SSN 637 (STURGEON) and 688 (LOS ANGELES) Class Attack Submarines.

Information Managed: Maintains theater ocean surveillance database providing targeting information for TOMAHAWK weapons employment. Engagement planning information and mission data.

Products Created: Copies of TWCS displays and geographic depiction of attack plan. Post launch status report. OPNOTES and SITREPS. INDIGO report to TOMAHAWK strike coordinator (TSC). Consolidated launch report from Launch Area Coordinator (LAC). Also provides mission and missile inventory reports.

Lead Service/Contractor: USN/ Boeing and Raytheon (missile)

Current Fielding Status: Deployed and operational. Advanced TWCS is currently being fielded. Two TICONDEROGA Class Cruisers and two Spruance Class Destroyers are currently equipped with ATWCS. This new system incorporates commercial off the shelf (COTS) equipment including a more capable computer (increased RAM and hard drive space) and enhanced graphics. Advanced TWCS operates in a UNIX based windows environment which allows the user to select functions by simply clicking on an icon. Since the number of key strokes has been reduced, operator workload has also been reduced. The windows environment also offers help keys which allows the operator to access information more efficiently. Finally, advanced TWCS has an embedded computer training system to further aid operator proficiency.

Known Problems: Requires position updates from the WSN-5 gyro. If the shooting platform has a bad gyro, than the TLAM shot opportunity is lost. All TLAM platforms are equipped with two gyros and TWCS can interact with either one.

DIICOE Compliance Rating: Not rated.

Point of Contact: Mr. Chuck Linsey, (301) 757-6241, office code PMA282W9; E-mail: LINSEYCL@navair.navy.mil.

Updated by: Capt Peter J. Dillon, USMC, CCSC-99.

 

Unit Diary/Marine Integrated Personnel System

(UD/MIPS)

Primary Purpose: Primary source for reporting personnel administrative data (i.e. Pay) into the Marine Corps Total Forces System (MCTFS).

Equipment Required: Micro computer using at least Windows 95, 32MB RAM, 1.6G Hard Drive, 8X CD ROM

Connectivity Requirements: Stand alone or network system requiring periodic updates from MCTFS via 3270 access.

Crypto Requirements: None.

Normal Locations: All MEF units.

Information Managed: Routine reports. Specific documents to assist in managing the administrative and training environments, other miscellaneous reports.

Products Created: Any type of administrative or personnel roster.

Lead Service/Contractor: USMC/MI Div (USMC Manpower and Reserve Affairs).

Current Fielding Status: UCPS version 4.0 fielded January 91. Program replaced by UD/MIPS in 92. Current version 297.303. New version was due in October 98, but has been delayed. New release date TBD. This version is windows based and Year 2000 compliant. The new version will operate on an Oracle server.

Known Problems: The stand alone version requires a bulky database. A unit of 2000 personnel requires 190MB database.

DIICOE Compliance Rating: Not rated.

Point of Contact: CW03 Arrington, DSN 278-9051.

Updated by: Capt Baron A. Harrison, USMC, CCSC-99.

 

War Reserve System

(WRS)

Primary Purpose: An automated tool used by the USMC to support operational planning and deployment of forces in a combat environment.

Capabilities: Determines logistical requirements, evaluates availability of assets, acquires assets, and provides those assets to a combat unit during deployment. Capable of sustaining a deployed unit for a minimum of the first 120 days of operations or when normal source of logistics becomes operational.

Sub-Functions: War reserve requirement determination. Pushes sustainment issues to field operators. Supports the following Department of Defense ground supply classes:

Class 1 – Substance

Class 2 – Clothing, individual equipment, organizational equipment, tents, tool kits, admin and housekeeping supplies.

Class 3 – Petroleum, oil, lubricant.

Class 4 – Construction materials

Class 7 – Major end items

Class 9 – Non-medical repair parts

Equipment Reqs: Computer hardware: Any Marine Corps or compatible mainframe computer with a 3270 terminal or a PC with 3270 emulation.

Connectivity Reqs: Interface with 3270 via telephone lines.

Crypto Reqs: None.

Normal Locations: Both MCLBs, MEFs, MARFORs, FSSGs, HQMC, St Louis Mega Center, Florida MPS. Access granted via MCLB Albany.

Information Managed: LOGINT

Products Created: Unit Mount-Out File (UMOF) and Unit Reserve Requirements File (URRF)

Lead Service/Contractor: USMC MCLB Albany.

Current Fielding Status: On-line and fielded.

Known Problems: None.

DIICOE Compliance Rating: Not rated.

Point of Contact: Pamela Bryant, Contingency planning G314, MCLB Albany, DSN 567-6602.

Internet: http://mcsd.ala.usmc.mil/index.html.

Updated by: Capt Dee S. Rosser, USMC, CCSC-99.